CN116962145A

CN116962145A - Fault notification method and device

Info

Publication number: CN116962145A
Application number: CN202210552411.6A
Authority: CN
Inventors: 余伟伟; 李日欣; 周勇波
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-04-15
Filing date: 2022-05-20
Publication date: 2023-10-27

Abstract

The embodiment of the application discloses a fault notification method, wherein after a first communication device determines that the FGU layer works abnormally, fault indication information can be sent to an upstream node, and the fault indication information is used for indicating a remote fault. Therefore, by using the scheme, the first communication device can notify the upstream node of the remote fault after determining that the FGU layer is abnormal, so that the upstream node can quickly determine the remote fault based on the fault indication information sent by the first communication device. Compared with the prior art, the scheme comprises a mechanism for notifying the upstream node of the far-end fault, and compared with the prior art that the edge node only carrying the small-particle service can sense the fault, the upstream node of the first communication device sensing the FGU layer fault can learn the far-end fault, and the upstream node of the first communication device learns the far-end fault, thereby being beneficial to quickly positioning the reason of the far-end fault and reducing the influence of the FGU layer fault of the first communication device on the small-particle service.

Description

Fault notification method and device

The present application claims priority from the chinese patent office, application number 202210399017.3, chinese patent application entitled "a communication method and apparatus" filed on day 15, 4, 2022, the entire contents of which are incorporated herein by reference.

Technical Field

The present application relates to the field of communications, and in particular, to a method and apparatus for notifying a fault.

Background

The flexible Ethernet (Flexible Ethernet, flexE) technology has the advantage of flexible bandwidth allocation as required, and can meet network scene requirements such as mobile bearing, home broadband, private line access and the like. Thus, flexE technology is becoming increasingly popular.

FlexE technology can support fine-grained traffic. In one example, a slot (slot) corresponding to a FlexE large bandwidth may be further divided into a plurality of sub-slots for carrying fine-grained traffic. Wherein: the service carried by the timeslot corresponding to the FlexE large bandwidth may also be referred to as a large-grain service, and the fine-grain service may also be referred to as a small-grain service. In the following description, "small particles" and "fine particle size" may be used interchangeably.

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

Disclosure of Invention

The embodiment of the application provides a fault notification method which can enable part of other communication devices carrying small-particle service to quickly determine remote faults.

In a first aspect, embodiments of the present application provide a fault notification method, which in one example may be performed by a first communication device, the first communication device may determine that a fine-grained unit (Fine Granularity Unit, FGU) layer is malfunctioning, and after the first communication device determines that the FGU layer is malfunctioning, fault indication information may be sent to an upstream node, where the fault indication information is used to indicate a remote fault. Therefore, by using the scheme, the first communication device can notify the upstream node of the remote fault after determining that the FGU layer is abnormal, so that the upstream node can quickly determine the remote fault based on the fault indication information sent by the first communication device. Compared with the prior art, the scheme comprises a mechanism for notifying the upstream node of the far-end fault, and correspondingly, compared with the situation that the edge node only carrying the small-particle service in the prior art can sense the fault, the upstream node of the first communication device sensing the FGU layer fault can learn the far-end fault, and correspondingly, the upstream node of the first communication device learns the far-end fault, thereby being beneficial to quickly positioning the reason of the far-end fault and reducing the influence of the FGU layer fault of the first communication device on the small-particle service. For example, an upstream node of the first communication device may perform fault location related measures, and so on.

In one possible implementation, in order for the upstream node to determine the specifics of the far-end failure, the far-end failure may be embodied as a far-end FGU layer failure.

In one possible implementation, the first communication device may send the fault indication information to the upstream node in a base frame overhead, so that the upstream node may obtain the fault indication information by parsing the base frame overhead.

In one possible implementation, the fault indication information may be carried by a reserved field of the base frame overhead. In this way, a new field in the base frame overhead may not be required to carry the fault indication information.

In one possible implementation, the fault indication information may be carried by a flag field of the base frame overhead, considering that the flag field has not been used. In this way, a new field in the base frame overhead may not be required to carry the fault indication information.

In one possible implementation, the fault indication information may be carried by an operation and maintenance management (operations administration maintenance, OAM) code block of a metro transport network (metro transport network, MTN) channel layer. In this way, the first communication device may send the fault indication information to the upstream node through the OAM code block of the MTN channel layer, and correspondingly, the upstream node may obtain the fault indication information by parsing the OAM code block of the MTN channel layer.

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

In one possible implementation, the OAM code block of the MTN channel layer may be an existing basic (basic) OAM code block. In this way, the basic OAM code block of the existing MTN channel layer may be used to carry the fault indication information without extending the OAM code block of the new MTN channel layer. For this case, in one example, the fault indication information may be carried using a reserved field in the basic OAM code block, and in yet another example, the fault indication information may be carried using a remote defect indication (remote defect indication, RDI) in the basic OAM code block.

In one possible implementation, considering that a multiframe loss (loss of multiframe, LOM), a frame Loss (LOF), and a service layer anomaly of the FGU layer may all represent an FGU layer anomaly, the first communication device may determine that the FGU layer is working anomaly when one or more of the LOM, the LOF, and the FGU layer is detected, and further, the first communication device may send fault indication information to an upstream node when determining that the FGU layer is working anomaly.

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

In one possible implementation, the first communication device is an intermediate node of an end-to-end path of small particle traffic carried by the FGU layer. For this case, when the intermediate node of the end-to-end path determines that the FGU layer is operating abnormally, the upstream node may be notified of the far-end failure, so that the upstream node quickly determines the far-end failure based on the failure indication information notified by the first communication device.

In one possible implementation, the upstream node is an intermediate node of an end-to-end path of small particle traffic carried by the FGU layer. For this case, when the FGU layer of the downstream node of the intermediate node is abnormal, the intermediate node may learn the remote fault information, and further, the intermediate node may further perform corresponding measures, so as to reduce the influence of the remote fault on the small particle service packet transmission as much as possible.

In one possible implementation, the first communication device may continuously detect an operation state of the FGU layer, and after determining that the FGU layer is operating normally, the first communication device may send fault recovery information to the upstream node, where the fault recovery information is used to indicate that a far-end is normal. In this way, after the upstream node receives the fault recovery information, corresponding processing measures, for example, slot synchronization with the first communication device, may be further performed, so that the small-particle service resumes normal transmission as soon as possible.

In one possible implementation, the far-end normalization may be embodied as a far-end FGU layer normalization.

In a second aspect, embodiments of the present application provide a fault notification method, which may be applied to a second communication device in one example. The second communication device and the first communication device are nodes on a path carrying small-particle service, and the second communication device is an upstream node of the first communication device. The second communication device may receive fault indication information sent by the first communication device, where the fault indication information is used to indicate a remote fault, and then, the second communication device may determine that the first communication device fails based on the fault indication information. Therefore, by using the scheme, the second communication device serving as the upstream node of the first communication device can receive the fault indication information sent by the first communication device, so that the second communication device can quickly determine the remote fault based on the fault indication information sent by the first communication device. Compared with the prior art, the scheme comprises a mechanism that a downstream node announces a far-end fault to an upstream node, and correspondingly, the upstream node of the first communication device knows the far-end fault, thereby being beneficial to quickly positioning the reason of the far-end fault and reducing the influence of the fault of the FGU layer of the first communication device on small particle service. For example, a second communication device, which is an upstream node of the first communication device, may perform measures related to fault localization, and so on.

In one possible implementation, the remote failure includes: far-end fine grain base unit FGU layer failure.

In one possible implementation, the fault indication information is carried by a base frame overhead.

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

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

In one possible implementation manner, the fault indication information is carried by an operation maintenance management OAM code block of an MTN channel layer of the metro transport network.

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

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

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

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

In one possible implementation manner, after the second communication device receives the fault indication information, alarm information may also be sent to the control management device, where the alarm information is used to indicate that the first communication device is abnormal. And notifying the alarm information to the control management equipment, so that the control management equipment can determine that the first communication device works abnormally, and correspondingly, the control management equipment executes corresponding processing measures. For example, advertising to other nodes on the end-to-end path carrying the small particle traffic that the first communication device is malfunctioning, etc

In one possible implementation, the first communication device is abnormally operated, including: the FGU layer of the first communication device operates abnormally.

In one possible implementation, the method further includes: and receiving fault recovery information sent by the first communication device, wherein the fault recovery information is used for indicating that the far end is normal.

In one possible implementation, after the second communication device receives the failure recovery information sent by the first communication device, the second communication device may perform slot synchronization with the first communication device, so as to transmit small particle service based on a slot after the slot synchronization is performed.

In one possible implementation, the first communication device is an intermediate node of an end-to-end path of small particle traffic carried by the FGU layer.

In one possible implementation, the upstream node is an intermediate node of an end-to-end path of small particle traffic carried by the FGU layer.

In a third aspect, an embodiment of the present application provides a method for status notification, which may be applied to a first communication device. In one example, a first communication device may determine an operating state of an FGU layer and then send state indication information to an upstream node, where the state indication information is used to indicate the operating state of the FGU layer. Therefore, by using the scheme, the first communication device can inform the upstream node of the working state of the FGU layer, and the upstream node can quickly determine the working state of the FGU layer of the first communication device. Compared with the prior art, the scheme comprises a mechanism for informing the upstream node of the state of the far-end FGU layer, and correspondingly, the upstream node of the first communication device can execute corresponding processing measures based on the state indication information. For example, in one example, the status indication information indicates a remote failure, the upstream node may learn of the remote failure and perform relevant measures for failure localization, and so on. As another example, in one example, the status indication information indicates that the FGU layer is working properly, the upstream node may send traffic data to the downstream node normally, or send information related to small particle slot negotiation.

In one possible implementation, the operating state of the FGU layer may be specifically that the FGU layer is operating normally. For this case, the upstream node may determine that the FGU layer of the first communication device is working properly based on the status indication information.

In one possible implementation, the status indication information is carried by a base frame overhead.

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

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

In one possible implementation, the status indication information may be carried by an operation, maintenance and administration OAM code block of the MTN channel layer. In this way, the first communication device may send the status indication information to the upstream node through the OAM code block of the MTN channel layer, and correspondingly, the upstream node may obtain the status indication information by parsing the OAM code block of the MTN channel layer.

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

In one possible implementation, the OAM code block of the MTN channel layer may be an existing basic (basic) OAM code block. In this way, the state indication information can be carried along with the basic OAM code block of the existing MTN channel layer, without extending the OAM code block of the new MTN channel layer. For this case, in one example, the status indication information may be carried with a reserved field in the basic OAM code block.

In a fourth aspect, embodiments of the present application provide a status notification method, which may be applied to a second communication device in one example. The second communication device and the first communication device are nodes on a path carrying small-particle service, and the second communication device is an upstream node of the first communication device. The second communication device can receive state indication information sent by the first communication device, wherein the state indication information is used for indicating the working state of the far-end FGU layer; the second communication device may then determine an operating state of the FGU layer of the first communication device based on the state indication information. Compared with the prior art, the scheme comprises a mechanism for informing the upstream node of the state of the far-end FGU layer, and correspondingly, the second communication device serving as the upstream node of the first communication device can execute corresponding processing measures based on the state indication information. For example, in one example, the status indication information indicates a remote failure, the second communication device may learn of the remote failure and perform relevant measures for failure localization, and so on. As another example, in one example, the status indication information indicates that the FGU layer is working properly, and the second communication device may send traffic data to the downstream node normally, or send information related to small particle slot negotiation.

In one possible implementation, the operating state of the FGU layer includes: FGU layers work properly.

In one possible implementation manner, the status indication information is carried by an operation maintenance management OAM code block of an MTN channel layer of the metro transport network.

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

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

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

In a fifth aspect, an embodiment of the present application provides a first communication apparatus, where the first communication apparatus includes a transceiver unit and a processing unit. The transceiver unit is configured to perform operations related to receiving and/or transmitting performed by the first communication device in the foregoing first aspect and various possible implementations of the first aspect; the processing unit is configured to perform operations other than the operations related to receiving and/or transmitting performed by the first communication device in the above first aspect and various possible implementations of the first aspect. In a specific implementation, the transceiver unit may include a receiving unit and/or a transmitting unit, where the receiving unit is configured to perform a reception-related operation, and the transmitting unit is configured to perform a transmission-related operation.

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

The processing unit is used for determining that the fine granularity unit FGU layer works abnormally; the sending unit is used for sending fault indication information to the upstream node, wherein the fault indication information is used for indicating a remote fault.

In one possible implementation, the remote failure includes: remote FGU layer failure.

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

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

In a possible implementation manner, the processing unit is further configured to: determining that the FGU layer works normally; the sending unit is further configured to send fault recovery information to the upstream node, where the fault recovery information is used to indicate that a far end is normal.

In one possible implementation, the distal end normally includes: the far-end FGU layer is normal.

In a sixth 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 the operations related to receiving and/or transmitting performed by the second communication device in the foregoing second aspect and various possible implementation manners of the second aspect; the processing unit is configured to perform operations other than the operations related to receiving and/or transmitting performed by the second communication device in the above 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 transmitting unit, where the receiving unit is configured to perform a reception-related operation, and the transmitting unit is configured to perform a transmission-related operation.

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

The receiving unit is used for receiving fault indication information sent by the first communication device, and the fault indication information is used for indicating a remote fault; the processing unit is used for determining that the first communication device fails based on the failure indication information.

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

In one possible implementation, the apparatus further includes:

and the sending unit is used for sending alarm information to the control management equipment, wherein the alarm information is used for indicating that the first communication device works abnormally.

In a possible implementation manner, the receiving unit is further configured to: and receiving fault recovery information sent by the first communication device, wherein the fault recovery information is used for indicating that the far end is normal.

In a possible implementation manner, the processing unit is further configured to: and carrying out time slot synchronization with the first communication device.

In a seventh aspect, an embodiment of the present application provides a first communication apparatus, where the first communication apparatus includes a transceiver unit and a processing unit. The transceiver unit is configured to perform operations related to receiving and/or transmitting performed by the first communication device in the third aspect and various possible implementations of the third aspect; the processing unit is configured to perform operations other than the operations related to receiving and/or transmitting 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 transmitting unit, where the receiving unit is configured to perform a reception-related operation, and the transmitting unit is configured to perform a transmission-related operation.

The processing unit is used for determining the working state of the fine granularity unit FGU layer; the sending unit is configured to send status indication information to an upstream node, where the status indication information is used to indicate an operating status of the FGU layer.

In one 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 operations related to receiving and/or transmitting performed by the second communication device in the fourth aspect and various possible implementation manners of the fourth aspect; the processing unit is configured to perform operations other than the operations related to receiving and/or transmitting 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 transmitting unit, where the receiving unit is configured to perform a reception-related operation, and the transmitting unit is configured to perform a transmission-related operation.

The receiving unit is used for receiving state indication information sent by the first communication device, wherein the state indication information is used for indicating the working state of a fine granularity unit FGU layer at the far end; the processing unit is configured to determine an operating state of an FGU layer of the first communication device based on the state indication information.

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

In a ninth aspect, the present application provides a communication device comprising a memory and a processor; the memory is used for storing program codes; the processor is configured to execute instructions in the program code, to cause the communication device to perform the method according to any one of the first aspect and the first aspect, or to cause the communication device to perform the method according to any one of the second aspect and the second aspect, or to cause the communication device to perform the method according to any one of the third aspect and the third aspect, or to cause the communication device to perform the method according to any one of the fourth aspect and the fourth aspect.

In a tenth aspect, the present application provides a communication device comprising a communication interface and a processor, through which the communication device is caused to perform the method of any one of the preceding aspects and part or all of the operations of any implementation of the method of any one of the preceding aspects. In a specific implementation manner, the communication interface is configured to perform the transceiving operations performed by the communication device according to any one of the above first aspect and the first aspect, and the processor is configured to perform other operations performed by the communication device according to any one of the above first aspect and the first aspect, except for the transceiving operations; alternatively, the communication interface is configured to perform the transceiving operation performed by the communication device according to any of the above second aspect and the second aspect, and the processor is configured to perform the other operation than the transceiving operation performed by the communication device according to any of the above second aspect and the second aspect; alternatively, the communication interface is configured to perform a transceiving operation performed by the communication device according to any one of the above third aspect and the third aspect, and the processor is configured to perform an operation other than the transceiving operation performed by the communication device according to any one of the above third aspect and the third aspect; alternatively, the communication interface is configured to perform the transceiving operation performed by the communication device according to any one of the fourth aspect and the fourth aspect, and the processor is configured to perform the operation other than the transceiving operation performed by the communication device according to any one of the fourth aspect and the fourth aspect.

In an eleventh aspect, embodiments of the present application provide a computer readable storage medium comprising instructions or a computer program which, when run on a processor, performs the method of any one of the first aspects above, or performs the method of any one of the second aspects above, or performs the method of any one of the third aspects above, or performs the method of any one of the fourth aspects above.

In a twelfth aspect, embodiments of the present application provide a computer program product comprising a computer program product which, when run on a processor, performs the method of any one of the above first aspect and the first aspect, or performs the method of any one of the above second aspect and the second aspect, or performs the method of any one of the above third aspect and the third aspect, or performs the method of any one of the above fourth aspect and the fourth aspect.

In a thirteenth aspect, an embodiment of the present application provides a communication system including: a communication device performing the method of the first aspect above and any of the first aspects above and a communication device performing the method of the second aspect above and any of the second aspects above; alternatively, a communication device performing the method of the third aspect above and any of the third aspects above and a communication device performing the method of the fourth aspect above and any of the fourth aspects above.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings may be obtained according to the drawings without inventive effort to those skilled in the art.

FIG. 1a is a schematic diagram of an SPN architecture supporting small particle technology according to an embodiment of the present application;

fig. 1b is a schematic diagram of a network architecture according to an embodiment of the present application;

fig. 1c is an OAM insertion schematic diagram of an MTNP according to an embodiment of the present application;

FIG. 1d is a schematic diagram of a fg-BU structure according to an embodiment of the present application;

FIG. 1e is a schematic diagram of another FGU base frame according to an embodiment of the present application;

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

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

fig. 2 is a signaling interaction diagram of a fault notification method according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of an OAM code block according to an embodiment of the present application;

Fig. 4 is a schematic flow chart of a fault notification method according to an embodiment of the present application;

fig. 5 is a signaling interaction diagram of a state notification method according to an embodiment of the present application;

fig. 6 is a schematic flow chart of a fault notification method according to an embodiment of the present application;

fig. 7 is a schematic flow chart of a fault notification method according to an embodiment of the present application;

fig. 8 is a schematic flow chart of a status notification method according to an embodiment of the present application;

fig. 9 is a schematic flow chart of a status notification method according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of a communication device according to an embodiment of the present application.

Detailed Description

The embodiment of the application provides a fault notification method and a fault notification device, which can enable part of other communication devices carrying small-particle service to quickly determine a remote fault.

The embodiment of the application provides a time slot negotiation method for small-granule business in FlexE, which can ensure that the small-granule time slots between two network devices transmitting the small-granule business are kept consistent.

For ease of understanding, the relevant contents of FlexE will be described first.

FlexE group: each FlexE group includes one or more PHYs. When multiple PHYs are included, the multiple PHYs are physically independent. The network device to which the FlexE technology is applied can identify which PHYs are included in one FlexE group by the number of the PHYs to implement logical bundling of the PHYs. For example, the number of each PHY may be identified by a number between 1 and 254, with 0 and 255 being reserved numbers. The number of one PHY may correspond to one interface on the network device. The same number is used between two adjacent network devices to identify the same PHY. The numbering of each PHY included in one FlexE group need not be contiguous. Normally, there is one FlexE group between two network devices, but the present application is not limited to only one FlexE group between two network devices, i.e. there may be multiple FlexE groups between two network devices. One PHY may be used to carry at least one client, and one client may transmit on at least one PHY. The FlexE can support mapping and transmission of any number of different FlexE clients on any set of PHYs, thereby implementing functions such as PHY bundling, channelization, and subrate.

FlexE Client: various user interfaces or bandwidths corresponding to the network. FlexE clients represent customer data streams transmitted in a specified time slot (time slot or slots) on a FlexE Group, one FlexE Group may carry multiple FlexE clients thereon, and one FlexE Client may correspond to one to multiple user traffic data streams (also referred to as MAC clients). FlexE clients can be flexibly configured according to bandwidth requirements, and ethernet media access control (media access control, MAC) data streams supporting various rates (e.g., 10G, 40G, n x 25G data streams, and even non-standard rate data streams) can be delivered to the FlexE shim layer, for example, by 64B/66B coding. Clients transmitting through the same FlexE group need to share the same clock and these clients need to adapt according to the allocated slot rate. In the present application, the FlexE client (also referred to as FlexE client interface) may be used to transmit the service data stream of the corresponding FlexE client. The FlexE client interface is a logical interface. Each FlexE interface may be logically divided into one or more FlexE client interfaces, each FlexE interface may be divided into a plurality of time slots in the time domain, each FlexE client interface occupying at least one of the plurality of time slots. Wherein: 64/66B means that the data code block includes 66 bits, the first two bits of the 66 bits are sync bits, the last 64 bits are data bits, and at the PCS layer, 64/66B can be extracted by the first two sync bits.

FlexE shim, an additional logical layer interposed between the MAC and PHY (PCS sublayers) of the conventional ethernet architecture, is a core architecture that implements FlexE technology based on a slot distribution mechanism. For the transmitting end, the main role of FlexE shim is to encapsulate data into pre-divided slots (slots). Then, according to the FlexE slot table, each divided slot is mapped to PHY in FlexE group for transmission. Wherein each slot maps to one PHY in the FlexE group. Taking 100GE PHY as an example, the FlexE shimm layer may divide each 100GE PHY in the FlexE Group into data-carrying channels of 20 slots (slots), where each slot corresponds to a bandwidth of 5Gbps. An Overhead FlexE (OH) is inserted every time the PHY transmits 1023 x 20slot 64/66B data, thereby informing the receiving end how to parse the received data.

Small particle traffic: in some embodiments, slots corresponding to a large bandwidth may be further divided into a plurality of sub-slots (sub-slots) for carrying customer traffic with smaller bandwidth requirements, which is also referred to as small-particle traffic. For example, the large bandwidth may be understood as a bandwidth corresponding to a service layer of the small-particle service. For example, when the service layer of the small-particle service is an MTN channel layer, the bandwidth of the MTN channel layer is 5Gbps, slots corresponding to the large bandwidth of 5Gbps are further divided into 480 sub-slots according to the granularity of 10Mbps, and the 480 sub-slots are used for carrying the small-particle service. For example, the 1 st sub-slot, the 3 rd sub-slot, and the 5 th sub-slot of the 480 sub-slots are used to carry the small particle service 1. For another example, when the service layer of the small-particle service is a 10GE ethernet physical layer, the corresponding large bandwidth is further divided into a plurality of sub-slots according to finer granularity, and the sub-slots are used for carrying the small-particle service. It follows that small particle bandwidth granularity is finer, small particle traffic refers to traffic that has relatively less bandwidth requirements. For example, the bandwidth requirement of the dedicated power line service is 10Mbps, and at this time, the dedicated power line service can be allocated with a specified bandwidth by using a small-grain technology, so as to be used for carrying the service traffic of the dedicated power line service, where the dedicated power line service is a small-grain service.

When transmitting the small-granule service, for the transmitting end, in an example, the FlexE shim may encapsulate data into pre-divided sub-slots according to the time slot configuration of the small granule for transmission. For the receiving end, the FlexE shim can restore the data received through the slot with the corresponding bandwidth of 5Gbps into the original small-granule service data according to the slot configuration of the small-granule and continue to transmit. In yet another example, for a transmitting end, data may be encapsulated into a corresponding sub-slot for transmission by using an MTN channel layer adaptation function (MTN path adaptation function), and for a receiving end, data received through the slot with a corresponding bandwidth of 5Gbps may be recovered into original small-particle service data by using the MTN channel layer adaptation function and transmitted continuously. In one example, the small particle business data may be carried in a small particle unit (fine granularity unit, FGU) base frame. In one example, small particle units, which may also be referred to as small particle base units (fine granularity basic unit, fg-BU), are used interchangeably in the following description.

Regarding the FlexE OH insertion approach and the structure of the overhead frames, in a specific implementation, reference may be made to the relevant description section of the electrical and optical internet forum (optical internetworking forum, OIF) regarding FlexE, which is not described in detail here.

Next, one possible slice packet network (Slicing Packet Network, SPN) architecture supporting small particle technology is presented. Referring to fig. 1a, a schematic diagram of an SPN architecture supporting small particle technology according to an embodiment of the present application is shown.

As shown in fig. 1a, the SPN architecture includes:

slice packet layer (slicing packet layer, SPL), slice lane layer (slicing channel layer, SCL), slice transport layer (slicing transport layer, STL), control-in-one software defined network (software defined network, SDN) slice control plane and ultra-high precision event frequency synchronization techniques. Wherein:

the SCL includes an FGU layer, an MTN path (MTNP) layer, and an MTN segment (MTNS) layer. Wherein: FGU layer provides end-to-end deterministic low-delay N10 Mbps granularity hard slice channel for small particle service. The FGU layer is an independent sublayer, and can be flexibly carried on an MTN channel layer or an Ethernet physical layer according to requirements, in other words, a service layer of the FGU layer can be the MTN channel layer or the Ethernet physical layer.

The 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 applied to customer-terminal equipment (CPE) scenes to directly bear the FGU layer.

Next, taking the MTN channel layer as an example to carry small particle service, from the perspective of the sending side behavior and the receiving side behavior, the MTNs and the MTNP will be described.

First, the transmission-side behavior and the reception-side behavior of the MTNS will be described.

In one example, taking a 100GBASE-R PHY as an example, MTNS provides point-to-point connectivity, is responsible for time-slotted processing of neighboring nodes that connect Ethernet PHYs together, and provides binding, subrate, and tunneling functions. The MTNS is bi-directionally symmetric and is described herein as one data transmission direction.

On the transmitting side, the MTNS inserts a special O code block in the 66B code block sequence, inserts a D code block after 1023×20 66B code blocks, inserts a D code block after every 1023×20 66B code blocks, and needs to insert 7D code blocks in total. After inserting the 7 th D code block, a special O code block is inserted after another 1023 x 20 code blocks are spaced apart. Thus, a total of 8 x (1023 x 20+1) code blocks constitute one MTNS frame.

The O code block plus the 7D code blocks described above constitutes the overhead of the MTNS frame. Overhead carries some point-to-point link configuration information, e.g., slot configuration information, segment layer group configuration information, etc., indicating the MTNS.

The MTNS continuously transmits data to the receiving end according to the above frame structure. The continuous MTNS frame is equivalent to a 66B code block stream, and is converted into a bit, an optical signal, or other analog signals such as an electrical pulse according to the lower PHY layer protocol defined by the ethernet IEEE 802.3, and transmitted from the transmitting device.

The receiving side first locks the frame header of the MTNS frame by identifying the O code blocks by passing the received signal (e.g., bits, optical signals, or other analog signals such as electrical pulses) according to the protocol of the ethernet layer PHY (Ethernet lower PHY layer), and knows that the next overhead code block occurs after 1023 x 20 code blocks according to a fixed count. Correspondingly, the receiving side can determine the position of the data corresponding to each time slot in the received signal according to 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 ingress to network egress, with MTNP providing end-to-end rigid hard pipe connections, providing management maintenance and protection (OAM and protection, OAMP) functions. A typical network related to MTNP may be shown in fig. 1b, and fig. 1b is a schematic diagram of a network architecture according to an embodiment of the present application.

The transmit side behavior and the receive side behavior of the MTNP are described next in connection with fig. 1 b.

As shown in fig. 1b, an end-to-end MTNP is included between Provider Edge (PE) 1 and PE2, and a point-to-point MTNS is included between PE1 and PE 2.

On the network side interface (network to network interface, NNI) side of PE1, the MTNP layer obtains a client signal from the MAC layer, which may be a MAC frame. The MAC referred to herein may be a processing module of the MAC layer. After the MTNP layer obtains the MAC frame, the MAC frame is encoded into a series of 64/66B code block sequences. Specifically, each MAC frame is 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 is encoded into a series of 66B code block sequences. If there is no valid MAC frame waiting to be sent, the MTNP fills the 66B code block with an idle (I) code block, thereby ensuring that the hard pipe of the MTNP has data to send from time to time. Regarding OAM & P functions provided by MTNP, reference is made to fig. 1 c. Fig. 1c is an OAM insertion schematic diagram of an MTNP according to an embodiment of the present application.

As shown in fig. 1c, OAM & P is implemented by inserting a special O-code block, which may also be referred to as an OAM-code block, in the 66B code block sequence. OAM adopts special codes and is loaded with OAM information, so that OAM functions including connectivity detection, error code monitoring, protection switching and the like are realized.

The MTNP OAM code block can only be inserted at the source and extracted at the sink, and currently, intermediate nodes located between the source and sink do not support modification and parse the information carried in the OAM code block. In other words, PE1 maps the 66B code block sequence containing the OAM code block into the MTNS slot specified according to the pre-configuration after the MTNP OAM insertion is completed in the MTNP. Then, the NNI transmitting side of the PE1 transmits the data according to the above-described behavior of the MTNS transmitting side.

The receiving side of the P node first recognizes the MTNS frame according to the above-described receiving side behavior of the MTNS. The MTNP data is then recovered from the designated MTNS slot according to the pre-configuration. The P node then performs MTNP forwarding. Here, the essential difference between MTNP forwarding and IP forwarding and MAC bridge forwarding is that: MTNP forwards exclusive device forwarding resources without supporting statistical multiplexing, both the ingress and egress of a network node (e.g., P-node) require configuration of the same number of MTNS slots.

As described above, in some embodiments, slots corresponding to a large bandwidth may be further divided into a plurality of sub-slots for carrying small particle traffic. For example, slots with the corresponding bandwidth of 5Gbps are further divided according to the granularity of 10Mbps, and 480 sub-slots are divided, and the 480 sub-slots are used for carrying small-particle service. For this case, the MTN FGU may further divide 480 slots of 10Mbps in the MTNP of 5Gbps in a hierarchical manner. In this scenario, the MTNP and MTN FGU may be decoupled, in which case the MTNP acts as a service layer for the MTN FGU. In an example, the structure of the fg-BU may be shown in fig. 1d, and fig. 1d is a schematic structural diagram of the fg-BU according to an embodiment of the present application.

As shown in fig. 1d, the fg-BU includes an FGU base frame overhead 110 and an FGU base frame payload 120. Wherein the FGU base frame overhead 110 may be used to carry small particle timeslot information, and the FGU base frame payload 120 is used to carry the small particle traffic data. The time slot information of the small particles can be a mapping relation between sub-slots and sub-clients. Wherein sub-clients are similar to FlexE clients and also correspond to various user interfaces or bandwidths of the network. The difference from FlexE Client is: the sub-clients represent client data streams transmitted on sub-slots, and one sub-client may correspond to one or more sub-slots.

For a scenario in which slots with a corresponding bandwidth of 5Gbps are further partitioned at a granularity of 10Mbps, in one example, one FGU base frame may include 24 sub-slots, each sub-slot including 65 bytes, each sub-slot may carry 8 65-bit code blocks. In other words, the aforementioned base frame payload 120 may include 65×24=1560 bytes. The 20 FGU base frames constitute a multiframe in which 24×20=480 sub-slots are provided. In one example, after the fg-BU shown in FIG. 1D is 64/66B encoded, 1S 0 code block, 196D code blocks, and 1T code block may be obtained.

For the NNI transmission side of PE1, the MTN FGU layer, like the MTNP, encodes the MAC frame client signal into a 66B code block sequence and then inserts the OAM code block. At this time, inserted into the MTN FGU layer is an OAM code block of a small particle MTNP (fgMTNP) instead of an OAM code block of the MTNP. Then, a series of 66B code block sequences containing the fgMTNP OAM code blocks are mapped into 10Mbps slots designated according to the pre-configuration in fg-BU.

The fg-BU sequence itself is actually a series of 66B code blocks, which can be equivalently referred to as a MTNP client signal, and after being inserted into the MTNP OAM code block, is mapped into the MTNS assigned time slot according to the above-described MTNS transmitting side behavior.

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

The P node executes the fgMTNP forwarding, which is the same as the MTNP forwarding, is TDM forwarding, and the resource is forwarded by the exclusive equipment, and the statistical multiplexing is not supported. The P-node does not terminate the OAM code block of the fgMTNP.

The sender-side behavior of the P-node is the inverse of the receiver-side behavior of the P-node and will not be described in detail here. In addition, the receiving-side behavior of the PE2 node is the inverse of the transmitting-side behavior of the PE1 node, which is not described in detail here.

FGU base frame overhead 110 in FGU base frames is described next.

Referring to fig. 1e, the structure of FGU base frame overhead is shown. The FGU base frame overhead shown in fig. 1e includes 56 bits (bits), wherein:

bits 0 and 1 are reserved fields.

Bits 2 to 7 are multiframe indication (multi frame indication, MFI) fields, which are used for indicating the number of each FGU base frame in a multiframe, in the scenario that the above 20 FGU base frames form one multiframe, the value of the MFI 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, for the last FGU base frame in the multiframe, the value of the MFI field is 19.

Bits 8 to 9 are an identification (flag) field for indicating contents carried by bits 16 to 48 of the base frame overhead. In one example, bits 16 to 48 of the base frame overhead are used to carry a general communication channel (general communications channel, GCC) field; in yet another example, the 16 th bit to 48 th bit of the base frame overhead are used to carry information such as a client Identifier (ID), and a sub-slot ID. In the embodiment of the application, the client ID carried in FGU base frame overhead is referred to as sub-client ID. For example, the client ID 1 mentioned below refers to sub-client ID 1.

Bit 10 is the reserved field.

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

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

Referring to fig. 1f, fig. 1f is a schematic structural diagram of still another FGU base frame overhead according to an embodiment of the present application. As described in fig. 1 f:

bit 11 is the reserved field.

Bit 12 is a Downstream Done (DD) indicator bit, and the DD indicator bit is a slot increase adjustment notification indicator bit, which is used to notify the upstream of triggering slot negotiation when the slot needs to be increased. The DD indicator bit may also be referred to as the S indicator bit.

Bit 13 is a configuration active (configuration commit, CMT) indicator bit, which indicates that the slot configuration is active. The CMT indicator bit may also be referred to as the C indicator bit.

Bit 14 is a configuration request (configuration request, CR) indication bit for indicating a slot adjustment request.

Bit 15 is a configuration acknowledgement (configuration acknowledge, CA) indication bit, which is used to indicate a slot adjustment response, where the receiving device sends the slot adjustment response to the transmitting device after receiving the slot adjustment request.

The content carried by the 16 th bit to the 48 th bit is indicated by a flag field; for example, the GCC field may be carried, and the client ID, sub-slot ID, and reserved field may be carried, for example.

Bits 49 to 55 are cyclic redundancy check (cyclic redundancy check, CRC) fields that are used to carry, in one example, CRC values for data carried by bits 8 to 48.

For other content in the SPN architecture shown in fig. 1a, reference may be made to the relevant description in the chinese mobile SPN small particle white paper, which is not described in detail here. Next, an application scenario of the embodiment of the present application is described with reference to fig. 1 g. Fig. 1g is a schematic diagram of an exemplary application scenario provided in an embodiment of the present application.

As shown in fig. 1g, an end-to-end transmission path for carrying small-particle traffic is established between PE1 and PE 2. Wherein: and a device P1, a device P2 and a device P3 are further arranged between the PE1 and the PE 2. Although not shown in fig. 1g, other devices may be included between PE1 and P1, and correspondingly, between P1 and P2, between P2 and P3, and between P3 and PE 2.

At present, when a node in a small-particle bearing service detects a small-particle fault, a Local Fault (LF) signal can be transmitted to a downstream node, and a node that receives the LF signal does not parse the LF signal, but continues to transmit the LF signal to the downstream node until a tail node of the end-to-end transmission path receives the LF signal, and then parses the LF signal. After the tail node analyzes the LF signal, the tail node sends a small-particle basic OAM message carrying RDI to the head node of the end-to-end transmission path. When the tail node sends the small-particle basic OAM message carrying RDI to the head node, the intermediate node does not parse the small-particle basic OAM message. After receiving the small-particle basic OAM message, the head node parses the small-particle basic OAM message, thereby determining that a small-particle failure has occurred.

However, in this way, the intermediate node cannot quickly determine that the node with the small particle failure has failed, and accordingly, normal transmission of the small particle service may be affected.

Illustrating:

device P2 determines that a small particle fault has occurred and device P2 generates an LF signal to device P3, which is further forwarded by device P3 to PE2. After the PE2 parses the LF signal, a small particle basic OAM message carrying RDI is sent to PE 1. After receiving the small-particle basic OAM message carrying RDI, PE1 determines that a small-particle fault, such as abnormal operation of the FGU layer, occurs, and further, PE1 may perform corresponding measures, such as fault locating measures, to locate a specific node where the fault occurs. However, the intermediate node, for example, P1, cannot determine that a fault occurs, and accordingly, the transmission of a service packet corresponding to the small-particle service is affected. For example, before the device P2 determines that the small particle failure occurs, the device P1 and the device P2 perform slot negotiation, and the device P1 transmits slot validation instruction information to the device P2. However, since the device P2 fails to successfully receive the time slot validation indication information, when the service message of the small-particle service is subsequently transferred, the device P1 uses the time slot configuration after negotiation to send the service message to the device P2, and the device P2 uses the time slot configuration before negotiation to parse the received service message. Namely: the time slot configuration used by the device P1 to send the service message is inconsistent with the time slot configuration used by the device P2 to receive the service message, so that the transmission of the service message fails.

In view of this, the embodiment of the application provides a fault notification method. Next, the method is described with reference to the drawings.

It should be noted that, the "small particle failure" mentioned in the embodiments of the present application refers to a failure related to small particle service, and the small particle failure includes, but is not limited to, FGU layer failure.

In the embodiment of the application, the FGU layer refers to a small particle layer, and is used for processing small particle service, and related operations such as time slot mapping, demapping and the like can be performed on the small particle service through the FGU layer. "FGU layer failure" may also be expressed as "FGU layer operational anomaly" or "small particle layer operational failure" which may be used interchangeably. As technology evolves and related standards evolve, those skilled in the art will appreciate that small particle layers and small particle technologies may have different designations in different standards. Referring to fig. 2, fig. 2 is a signaling schematic diagram of a fault notification method according to an embodiment of the present application. The communication device 1 and the communication device 2 in the failure notification method 100 shown in fig. 2 are nodes in an end-to-end transmission path carrying small particle traffic. The communication device 2 is an upstream node of the 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 shown in fig. 1e with PE1 as the head node and PE2 as the tail node: the communication apparatus 1 may be a PE1 and the communication apparatus 2 may be a device P3; alternatively, the communication apparatus 1 may be the device P3, and the communication apparatus 2 may be the device P2; alternatively, the communication apparatus 1 may be the device P2, and the communication apparatus 2 may be the device P1; alternatively, the communication apparatus 1 may be the device P1, and the communication apparatus 2 may be the PE1.

The communication device mentioned in the embodiment of the present application may be a network device such as a switch, a router, or a part of components on the network device, for example, a board, a line card on the network device, or a functional module on the network device, or a chip for implementing the method of the present application, and the embodiment of the present application is not specifically limited. The communication devices may be directly connected to each other, for example, but not limited to, via an ethernet cable or an optical cable.

The method 100 may include, for example, S101-S104 as follows.

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

In one example, the FGU layer mentioned in the embodiment of the present application may be the FGU layer located at SCL shown in fig. 1 d. For this case, the service layer of the FGU layer may be an MTN channel layer or an ethernet physical layer, as is known from the description of fig. 1d above.

In the embodiment of the present application, the communication device 1 may detect the working state of the FGU layer. In one example, the FGU layer operation anomaly may be determined when one or more of LOM is detected by the communication device 1, LOF is detected by the communication device 1, and FGU layer service anomaly is detected by the communication device 1. Wherein:

The communication device 1 detecting LOM may be that the communication device 1 determines that fg-BU framing failed. Wherein: the fg-BU framing requires searching to identify the correct S0 code block carried by one or several consecutive fg-BU before extracting the overhead information in the fg-BU and the contained intra-slot data. When the communication device 1 does not search for the correct S0 code block carried by one or several consecutive fg-BU, it causes that the fg-BU cannot be framed.

The detection of the LOF by the communication apparatus 1 may be such that the numbers of the plurality of fg-BU received by the communication apparatus 1 are not consecutive. Wherein the number of fg-BU may be carried by the MFI field in the FGU base frame overhead.

The communication device 1 may detect an abnormality in the service layer of the FGU layer, and the service layer itself of the FGU layer of the communication device 1 may detect the abnormality. For example, when the service layer of the FGU layer is an MTN channel layer, the destination of the MTN channel layer may determine whether the MTN channel layer fails by detecting whether the basic OAM code block is received in a fixed period. As another example, whether the MTN channel layer is malfunctioning may be determined by a service layer of the MTN channel layer, such as a detection means of the MTN segment layer, where the detection means of the MTN segment layer includes, but is not limited to, detecting a FlexE LOF and/or a FlexE LOM.

The embodiment of the application is not particularly limited to the reasons for causing the abnormal operation of the FGU layer, and the reasons for causing the abnormal operation of the FGU layer include but are not limited to: large particle channel failure, fiber failure, etc., carrying small particle traffic, are not explicitly described herein.

S102: the communication device 1 transmits fault indication information for indicating a remote fault to the communication device 2.

After determining that the FGU layer is operating abnormally, the communication device 1 may send fault indication information to its upstream node (i.e., the communication device 2). The fault indication information is used to indicate a remote fault. In one example, the far-end failure may be a far-end small particle failure, or a large particle channel failure carrying small particles. In one example, the fault indication information may be used to indicate a far-end FGU layer fault in order for an upstream node to determine the specifics of the far-end fault.

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

In one example, the reserved field in the base frame overhead may be utilized to carry the above-described fault indication information, considering that the reserved field in the base frame overhead has not been used. For example, the fault indication information is carried by a bit in the reserved field, and when the bit has a value of 1, the indication 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 far-end is normal (e.g., indicates that the far-end FGU layer is normal). In one example, when the fault indication information is used to indicate a far-end FGU layer fault:

In one example, the reserved field may be used to indicate a far-end FGU layer failure. In yet another example, the reserved field is used to indicate a far-end failure, and another field in the base frame overhead is used to indicate that the far-end failure is specifically a far-end FGU layer failure. The embodiment of the present application is not particularly limited to the other field, and the other field may be a field different from any one of the reserved fields that has not been used. For example, the other field may be a flag field in the base frame overhead.

In yet another example, the above-described fault indication information may be carried using a flag field in the base frame overhead, considering that the flag field in the base frame overhead has not been used. For example, for the base frame overhead shown in fig. 1b or 1c, the flag field includes 2 bits, and one or two bits of the flag field may be used to carry the foregoing fault indication information. For example, the foregoing fault indication information is carried by using 1 bit, and when the value of the bit is 1, the fault indication information is carried by the indication base frame overhead. When the value of this bit is 0, this field has no special meaning or indicates that the far-end is normal (e.g., indicates that the far-end FGU layer is normal). In one example, when the fault indication information is used to indicate a far-end FGU layer fault:

In one example, the flag field may be used to indicate a far-end FGU layer failure. In yet another example, the flag field is used to indicate a far-end failure, and another field in the base frame overhead is used to indicate that the far-end failure is specifically a far-end FGU layer failure. The embodiment of the present application is not particularly limited to the other field, and the other field may be any field that is different from the flag field and has not been used. For example, the further 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.

In one implementation, a new OAM code block may be extended to carry the fault indication information. For this case, a 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 far-end FGU layer fault:

in one example, the type field of the OAM code block may be used to indicate a far-end FGU layer failure. In yet another example, the type field is used to indicate a far-end failure, and another field in the OAM code block is used to indicate that the far-end failure is specifically a far-end FGU layer failure. The embodiment of the present application is not particularly limited to the other field, and the other field may be a field different from any one of the type fields that has not been used. For example, the further field may be a reserved field in the OAM code block.

In yet another implementation, the OAM code block may be an existing basic OAM code block. In this way, the basic OAM code block of the existing MTN channel layer may be used to carry the fault indication information. In one example, the fault indication information may be carried using a reserved field in the basic OAM code block, and in yet another example, the fault indication information may be carried using an RDI in the basic OAM code block. In one example, when the fault indication information is used to indicate a far-end FGU layer fault:

in one example, the reserved field of the basic OAM code block may be used to indicate a far-end FGU layer failure. In yet another example, a reserved field in the basic OAM code block is used to indicate a far-end failure, and another field in the basic OAM code block is used to indicate that the far-end failure is specifically a far-end FGU layer failure. The embodiment of the present application is not particularly limited to the other field, and the other field may be a field different from any one of the reserved fields that has not been used.

In yet another example, the RDI of the basic OAM code block may be used to indicate a far-end FGU layer failure. In yet another example, the RDI in the basic OAM code block is used to indicate a far-end fault, and another field in the basic OAM code block is used to indicate that the far-end fault is specifically a far-end FGU layer fault. The embodiment of the present application is not particularly limited to the additional field, and the additional field may be any field that is different from the RDI and has not been used. For example, the further 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 is not limited specifically, and in an example, the structure of the basic OAM code block may be shown with reference to fig. 3, and fig. 3 is a schematic structural diagram of an OAM code block according to an embodiment of the present application. As shown in fig. 3, the OAM code block includes 66 bits, and the first two bits are synchronization header bits, and have a value of 01. The last 64 bits include: a type (type) field, a Reserved (RES) field, a value (value) field, a C-code field, a sequence number (seq) field, and a cyclic redundancy check (cyclic redundancy check, CRC) 4 field.

Wherein:

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. The MTN channel layer OAM message types include the following:

basic (basic), connectivity verification (connectivity verification, CV), latency measurement (delay measurement, DM), automatic protection switching (auto 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, which includes 32 bits, indicates a specific value of the OAM message carried by the OAM code block.

And C, code: a control code block of type 0x4B is indicated as an OAM code block of the MTN channel layer using a 4-bit fixed 0xC value. The difference of the C codes can distinguish the MTNP OAM code block from the MTNS overhead code block.

seq: the sequence number of the OAM code block in the OAM message formed by combining multiple code blocks is indicated by 4 bits, and the typical application is connectivity verification and delay measurement.

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

In yet another example, the basic OAM code block may be MTN path basic OAM block, and its structure may be referred to in the related description section of chapter 8 of the international telecommunications union telecommunication standardization sector (internatial telecommunication union telecommunication standardization sector, ITU-T) g.8312, which is not described in detail herein.

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

S104: the communication device 2 determines that the communication device 1 has failed based on the failure instruction information.

After the communication device 1 transmits the failure indication information to the communication device 2, the communication device 2 may receive the failure indication information transmitted by the communication device 1. Further, the communication apparatus 2 may determine that the communication apparatus 1 has failed based on the failure indication information. As described above, in one example, the fault indication information may be used to indicate a far-end FGU layer fault. For this case, the notification device 2 may determine that the far-end FGU layer fails based on the failure indication information.

In one example, after receiving the fault indication information, the communication apparatus 2 may send alarm information to the control management device, the alarm information being used to indicate that the communication apparatus 1 is working abnormally. In one example, if the foregoing fault indication information is used to indicate a remote FGU layer fault, the alert information may be used to indicate that the FGU layer of the communication device 1 is malfunctioning. The alarm information is announced to the control management device, so that the control management device can determine that the communication device 1 works abnormally, and correspondingly, the control management device executes corresponding processing measures. For example, other nodes on the end-to-end path carrying the small particle traffic are notified of an abnormal operation of the communication device 1, etc.

The control management device mentioned in the embodiments of the present application may be, for example, a device running a network management system (network manage system, NMS), and may be, for example, a controller.

The communication device 1 may continuously detect the operating state of the FGU layer. In one example, if the FGU layer failure is not recovered, the communication device 1 may continuously or periodically send the foregoing failure indication information to the communication device 2.

In one example, after the communication device 1 determines that the FGU layer is working properly, the fault indication information may no longer be sent to the communication device 2, and correspondingly, the communication device 2 may determine that the communication device 1 is working properly if the fault indication information is not received.

In yet another example, after the communication device 1 determines that the FGU layer is functioning properly, fault recovery information may be sent to the communication device 2 indicating that the far-end is normal. In one example, the far-end normal may include a far-end FGU layer normal, i.e.: after the communication device 1 determines that the FGU layer is working properly, fault recovery information indicating that the far-end FGU layer is working properly may be sent to the communication device 2. In one example, the communication device 1 may determine that the FGU layer is working properly if no LOM and LOF are detected.

In some embodiments, the communication device 1 may send the failure recovery information to the communication device 2 in a base frame overhead.

In one example, the reserved field in the base frame overhead may be utilized to carry the above-described failure recovery information, considering that the reserved field in the base frame overhead has not been used. For example, the fault recovery information is carried by a bit in the reserved field, and when the value of the bit is 0, the base frame overhead is indicated to carry the fault recovery information. When the value of this bit is 1, this field has no special meaning or indicates a far-end failure (e.g., indicates a far-end FGU layer failure). In one example, when the fault recovery information is used to indicate that the far-end FGU layer is working properly:

In one example, the reserved field may be used to indicate that the far-end FGU layer is working properly. In yet another example, the reserved field is used to indicate that the far-end is normal, and another field in the base frame overhead indicates that the far-end is normal, in particular that the far-end FGU layer is working properly. The embodiment of the present application is not particularly limited to the other field, and the other field may be a field different from any one of the reserved fields that has not been used. For example, the other field may be a flag field in the base frame overhead.

In yet another example, the above-described failure recovery information may be carried using a flag field in the base frame overhead, considering that the flag field in the base frame overhead has not been used. For example, for the base frame overhead shown in fig. 1b or 1c, the flag field includes 2 bits, and one or two bits of the flag field may be used to carry the aforementioned failure recovery information. For example, the foregoing failure recovery information is carried with 1 bit, and when the value of this bit is 0, the base frame overhead is indicated to carry the failure recovery information. When the value of this bit is 1, this field has no special meaning or indicates a far-end failure (e.g., indicates a far-end FGU layer failure). In one example, when the fault recovery information is used to indicate that the far-end FGU layer is working properly:

In one example, the flag field may be used to indicate that the far-end FGU layer is working properly. In yet another example, the flag field is used to indicate that the far-end is normal, and another field in the base frame overhead indicates that the far-end is normal, specifically, that the far-end FGU layer is working properly. The embodiment of the present application is not particularly limited to the other field, and the other field may be any field that is different from the flag field and has not been used. For example, the further 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.

In one implementation, a new OAM code block may be extended to carry the fault recovery information. For this case, a 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 far-end FGU layer is working properly:

in one example, the type field of the OAM code block may be used to indicate that the far-end FGU layer is working properly. In yet another example, the type field is used to indicate that the far-end is normal, and another field in the OAM code block indicates that the far-end is normal, and in particular that the far-end FGU layer is operating properly. The embodiment of the present application is not particularly limited to the other field, and the other field may be a field different from any one of the type fields that has not been used. For example, the further field may be a reserved field in the OAM code block.

In yet another implementation, the OAM code block may be an existing basic OAM code block. In this way, the fault recovery information may be carried along with the basic OAM code block of the existing MTN channel layer. In one example, the fault recovery information may be carried using a reserved field in the basic OAM code block. In one example, when the fault recovery information is used to indicate that the far-end FGU layer is working properly:

in one example, the reserved field of the basic OAM code block may be used to indicate that the far-end FGU layer is working properly, e.g., when the value of the reserved field in the basic OAM code block is 0, it indicates that the far-end FGU layer is working properly. In yet another example, a reserved field in the basic OAM code block is used to indicate that the far-end is normal, and another field in the basic OAM code block is used to indicate that the far-end is normal, specifically, that the far-end FGU layer is working properly. The embodiment of the present application is not particularly limited to the other field, and the other field may be a field different from any one of the reserved fields that has not been used.

Regarding the structure of the basic OAM code block, reference may be made to the above related description, and the description will not be repeated.

After the communication device 2 receives the failure recovery information, it can be determined that the communication device 1 is functioning normally. In one example, if the failure recovery information is used to indicate that the far-end FGU layer is normal, the communication device 2 may determine that the FGU layer of the communication device 1 is working properly based on the failure recovery information.

In one example, the time slots between communication device 1 and communication device 2 may not be synchronized in view of the abnormal operation of communication device 2. Thus, in one example, after receiving the failure recovery information, the communication device 2 may perform slot synchronization with the first communication device. The embodiment of the present application is not particularly limited to a specific implementation manner in which the communication device 2 performs slot synchronization with the communication device 1, and in one example, the communication device 2 may perform full-scale slot synchronization with the communication device 1 for small-particle traffic.

As can be seen from the above description, with the method 100 provided by the embodiment of the present application, compared with the conventional technology, the method 100 includes a mechanism for notifying the upstream node of the remote fault, and accordingly, compared with the conventional technology in which only the edge node carrying the small-particle service can sense the fault, the upstream node of the communication device 1 that senses the FGU layer fault can learn the remote fault, and accordingly, the upstream node of the communication device 1 learns the remote fault, which is also beneficial to quickly locating the cause of the remote fault. For example, an upstream node of the communication apparatus 1 may perform a fault location related measure, and so on. Accordingly, the impact on small particle traffic transmission can be reduced.

When the communication device 2 is an intermediate node of the end-to-end transmission path carrying the small particle service, by using the method 100, when the FGU layer of the downstream node of the intermediate node works abnormally, the intermediate node may learn the far-end fault information, further, the intermediate node may further perform corresponding measures, so as to reduce the influence on the transmission of the small particle service message due to the far-end fault as much as possible, for example, the intermediate node may determine whether to perform time slot synchronization before determining the far-end fault, and if time slot synchronization is performed with the downstream node before determining the far-end fault, further determine whether the time slot synchronization is successful.

Referring to fig. 4, the flow chart of a fault notification method according to an embodiment of the present application is shown. The fault notification method 200 shown in fig. 4 may be performed by the communication device 1, and the communication device 1 may include the following steps S201-S202.

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

Regarding S201, reference may be made to the relevant description section above for S101, which is not described in detail here.

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

In one example, the local end failure is a local end FGU layer failure.

After receiving the alarm information, the control management device may determine that the communication apparatus 1 is faulty, and in one example, if the local fault is a local FGU layer fault, the control management device may determine that the communication apparatus 1 is faulty. Accordingly, the control management device may perform the corresponding processing measures. For example, the other nodes on the end-to-end path carrying the small particle traffic are notified of the communication device 1 operating anomaly, or the other nodes on the end-to-end path carrying the small particle traffic are notified of the communication device 1FGU layer operating anomaly.

By utilizing the method 200, when the local FGU layer of the communication device 1 works abnormally, alarm information can be sent to the control management equipment so as to facilitate the control management equipment to further execute corresponding measures, thereby improving the efficiency of fault location or fault recovery as much as possible and reducing the influence of the work abnormality of the FGU layer of the communication device 1 on small particle business.

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

Referring to fig. 5, the diagram is a signaling interaction diagram of a state notification method according to an embodiment of the present application. With regard to the communication device 1 and the communication device 2 shown in fig. 5, reference is made to the relevant description of the method 100 above, which is not described in detail here.

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

S301: the communication device 1 determines the operating state of the FGU layer.

The operating state of the FGU layer may include both cases of FGU layer operating normally and FGU layer operating abnormally.

With respect to a specific implementation of the communication device 1 in determining FGU layer operational anomalies, reference may be made to the relevant description part of the manner 100, which is not described in detail here.

With respect to the specific implementation of the communication device 1 to determine that the FGU layer is working properly, reference may be made to the relevant description section of the manner 100, which is not described in detail here.

S302: the communication device 1 sends status indication information to the communication device 2, the status indication information being used to indicate the operating status of the FGU layer.

And when the FGU layer works abnormally, the state indication information is fault indication information for indicating that the remote FGU layer works abnormally. For a specific implementation of the communication device 1 sending the communication device 2 fault indication information indicating that the far-end FGU layer is abnormal in operation, reference may be made to the relevant description part in the method 100, and the description will not be repeated here.

When the FGU layer works normally, the state indication information indicates that the far-end FGU layer works normally. As for a specific implementation of the communication device 1 to send status indication information to the communication device 2 indicating that the far-end FGU layer is working properly, reference may be made to the relevant description part of the method 100 regarding "the communication device 1 sends failure recovery information to the communication device 2", which is not repeated here.

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

S304: the communication device 2 determines the operating state of the FGU layer of the communication device 1 based on the state indication information.

And when the FGU layer works abnormally, the state indication information is fault indication information for indicating that the remote FGU layer works abnormally. For this case, the communication apparatus 2 may determine that the communication apparatus 1FGU layer is operating abnormally based on the status indication information.

When the FGU layer works normally, the state indication information indicates that the far-end FGU layer works normally. For this case, the communication apparatus 2 may determine that the communication apparatus 1FGU layer is operating abnormally based on the status indication information.

The embodiment of the application also provides a fault notification method, and referring to fig. 6, the diagram is a schematic flow chart of the fault notification method provided by the embodiment of the application. The fault notification method 400 shown in fig. 6 may be performed by a 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 S401-S402 as follows.

S401: and determining that the fine granularity unit FGU layer works abnormally.

S402: and sending fault indication information to an upstream node, wherein the fault indication information is used for indicating a remote fault.

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

In one possible implementation, the determining FGU layer operational anomalies includes:

one or more of detecting a multiframe loss LOM, detecting a frame loss LOF, and detecting a service layer anomaly of the FGU layer.

In one possible implementation, the method further includes: determining that the FGU layer works normally; and sending fault recovery information to the upstream node, wherein the fault recovery information is used for indicating that the far end is normal.

With respect to the specific implementation of the method 400, reference may be made to the relevant description of the method 100 above, and the description is not repeated here.

The embodiment of the application also provides a fault notification method, and referring to fig. 7, the diagram is a flow diagram of the fault notification method provided by the embodiment of the application. The fault notification method 500 shown in fig. 7 may be performed by a 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 S501-S502 as follows.

S501: and receiving fault indication information sent by the first communication device, wherein the fault indication information is used for indicating a remote fault.

S502: and determining that the first communication device fails based on the failure indication information.

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

In one possible implementation, the method further includes:

and sending alarm information to control management equipment, wherein the alarm information is used for indicating that the first communication device works abnormally.

In one possible implementation, the method further includes: and carrying out time slot synchronization with the first communication device.

With respect to the specific implementation of the method 500, reference may be made to the relevant description of the method 100 above, which is not repeated here.

The embodiment of the application also provides a state notification method, and referring to fig. 8, the diagram is a schematic flow chart of the state notification method provided by the embodiment of the application. The state advertisement method 600 shown in fig. 8 may be performed by a first communication device.

The state 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, S601-S602 as follows.

S601: the operating state of the fine grain unit FGU layer is determined.

S602: and sending state indication information to an upstream node, wherein the state indication information is used for indicating the working state of the FGU layer.

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

With respect to the specific implementation of the method 600, reference may be made to the relevant description of the method 300 above, and the description will not be repeated here.

The embodiment of the application also provides a state notification method, and referring to fig. 9, the diagram is a schematic flow chart of the state notification method provided by the embodiment of the application. The state advertisement method 700 shown in fig. 9 may be performed by a 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, S701-S702 as follows.

S701: and receiving state indication information sent by the first communication device, wherein the state indication information is used for indicating the working state of the fine granularity unit FGU layer at the far end.

S702: and determining the working state of the FGU layer of the first communication device based on the state indication information.

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

With respect to the specific implementation of the method 700, reference may be made to the relevant description of the method 300 above, which is not repeated here.

The embodiment of the application also provides a first communication device, and referring to fig. 10, the fig. is a schematic structural diagram of the communication device provided by the embodiment of the application. The first communication device 1000 shown in fig. 10. The fault notification apparatus may include a processing unit 1001 and a transmitting unit 1002.

In one example, the first communication device may be configured 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. For this case:

the processing unit 1001 is configured to determine that the fine granularity unit FGU layer is abnormal;

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 one possible implementation, the OAM code block is a basic OAM code block.

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

In a possible implementation manner, the processing unit 1001 is further configured to: determining that the FGU layer works normally; the sending unit is further configured to send fault recovery information to the upstream node, where the fault recovery information is used to indicate that a far end is normal.

In yet another example, the first communication device may be configured 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. For this case:

the processing unit 1001 is configured to determine an operating state of the fine grain 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 an operating status of the FGU layer.

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

The embodiment of the application also provides a second communication device, and referring to fig. 11, the diagram is a schematic structural diagram of the communication device provided by the embodiment of the application. The second communication device 1100 shown in fig. 11 may include a receiving unit 1101 and a processing unit 1102.

In one example, the second communication device may be configured to perform the steps performed by the communication device 2 in the method 100 above, or to perform the steps performed by the second communication device in the method 500 above. For 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 the first communication device fails based on the failure indication information.

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

In one possible implementation, the apparatus further includes: and the sending unit is used for sending alarm information to the control management equipment, wherein the alarm information is used for indicating that the first communication device works abnormally.

In a possible implementation manner, the receiving unit 1101 is further configured to: and receiving fault recovery information sent by the first communication device, wherein the fault recovery information is used for indicating that the far end is normal.

In a possible implementation manner, the processing unit 1102 is further configured to: and carrying out time slot synchronization with the first communication device.

In yet another example, the second communication device may be configured 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. For this case:

the receiving unit 1101 is configured to receive status indication information sent by the first communication device, where the status indication information is used to indicate an operating status of a fine granularity unit FGU layer at a far end;

the processing unit 1102 is configured to determine an operating state of an FGU layer of the first communication device based on the state indication information.

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

In addition, the embodiment of the application further provides a communication device 1200, as shown in fig. 12, and fig. 12 is a schematic structural diagram of the communication device according to the embodiment of the 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 the method 100, method 200, method 300, method 400, method 500, method 600, or method 700 of the above embodiments.

In one example, the communication device 1200 may perform the method 100 in the above embodiment, and when the communication device 1200 is used to perform the method 100 in the above embodiment, the communication device 1200 corresponds to the communication device 1 in the method 100. The communication interface 1201 is used to perform transceiving operations performed by the communication device 1 in the method 100. The processor 1202 is configured to perform operations of the method 100 other than the transceiving operations performed by the communication device 1. For example: the processor 1202 is configured to determine that the FGU layer is operating abnormally; the communication interface 1201 is configured to transmit fault indication information for indicating a remote fault to the communication apparatus 2.

In one example, the communication device 1200 may perform the method 100 in the above embodiment, and when the communication device 1200 is used to perform the method 100 in the above embodiment, the communication device 1200 corresponds to the communication device 2 in the method 100. The communication interface 1201 is used to perform transceiving operations performed by the communication device 2 in the method 100. The processor 1202 is configured to perform operations other than the transceiving operations performed by the communication device 2 in the method 100. For example: the communication interface 1201 is configured to receive fault indication information sent by the communication device 1, where the fault indication information is used to indicate a remote fault; the processor 1202 is configured to determine that the communication device 1 is malfunctioning.

In one example, the communication device 1200 may perform the method 200 in the above embodiment, and when the communication device 1200 is used to perform the method 200 in the above embodiment, the communication device 1200 corresponds to the communication device 1 in the method 200. The communication interface 1201 is used to perform the transceiving operations performed by the communication device 1 in the method 200. The processor 1202 is configured to perform operations other than the transceiving operations performed by the communication device 1 in the method 200. For example: the processor 1202 is configured to determine that the FGU layer is operating abnormally; the communication interface 1201 is configured to send alarm information to the control management device, where the alarm information is used to indicate a local end failure.

In one example, the communication device 1200 may perform the method 300 of the above embodiment, and when the communication device 1200 is used to perform the method 300 of the above embodiment, the communication device 1200 corresponds to the communication device 1 of the method 300. The communication interface 1201 is used to perform transceiving operations performed by the communication device 1 in the method 300. The processor 1202 is configured to perform operations of the method 300 other than the transceiving operations performed by the communication device 1. For example: the processor 1202 is configured to determine an operating state of the FGU layer; the communication interface 1201 is configured to send status indication information to the communication device 2, the status indication information being used to indicate an operating status of the FGU layer.

In one example, the communication device 1200 may perform the method 300 of the above embodiment, and when the communication device 1200 is used to perform the method 300 of the above embodiment, the communication device 1200 corresponds to the communication device 2 of the method 300. The communication interface 1201 is used to perform transceiving operations performed by the communication device 2 in the method 300. The processor 1202 is configured to perform operations other than the transceiving operations performed by the communication device 2 in the method 300. For example: the communication interface 1201 is configured to receive status indication information sent by the communication device 1, where the status indication information is used to indicate an operating status of the FGU layer; the processor 1202 is configured to determine an operating state of an FGU layer of the communication device 1.

In one example, the communication device 1200 may perform the method 400 of the above embodiment, and when the communication device 1200 is used to perform the method 400 of 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 transceiving operations performed by the first communication device in the method 400. The processor 1202 is configured to perform operations other than the transceiving operations performed by the first communication device in the method 400. For example: the processor 1202 is configured to determine that the FGU layer is operating abnormally; the communication interface 1201 is configured to send fault indication information to an upstream node, where the fault indication information is used to indicate a remote fault.

In one example, the communication device 1200 may perform the method 500 of the above embodiment, and when the communication device 1200 is used to perform the method 500 of the above embodiment, the communication device 1200 is equivalent to the second communication device of the method 500. The communication interface 1201 is used to perform the transceiving operations performed by the second communication device in the method 500. The processor 1202 is configured to perform operations other than the transceiving 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, where the fault indication information is used to indicate a remote fault; the processor 1202 is configured to determine that the first communication device is malfunctioning based on the failure indication information.

In one example, the communication device 1200 may perform the method 600 in the above embodiment, and when the communication device 1200 is used to perform the method 600 in the above embodiment, the communication device 1200 corresponds to the first communication device in the method 600. The communication interface 1201 is used to perform the transceiving operations performed by the first communication device in the method 600. The processor 1202 is configured to perform operations other than the transceiving operations performed by the first communication device in the method 600. For example: the processor 1202 is configured to determine an operating state of the fine grain unit FGU layer; the communication interface 1201 is configured to send status indication information to an upstream node, where the status indication information is used to indicate an operating status of the FGU layer.

In one example, the communication device 1200 may perform the method 700 of the above embodiment, and when the communication device 1200 is used to perform the method 700 of the above embodiment, the communication device 1200 is equivalent to the second communication device of the method 700. The communication interface 1201 is used to perform the transceiving operations performed by the second communication device in the method 700. The processor 1202 is configured to perform operations other than the transceiving operations performed by the second communication device in the method 700. For example: the communication interface 1201 is configured to receive status indication information sent by the first communication device, where the status indication information is used to indicate a working status of a fine granularity unit FGU layer at a far end; the processor 1202 is configured to determine an operating state of an FGU layer of the first communication device based on the state indication information.

In addition, the embodiment of the application further provides a communication device 1300, as shown in fig. 13, and fig. 13 is a schematic structural diagram of the communication device according to the embodiment of the application. The communications apparatus 1300 can be configured to perform the method 100, method 200, method 300, method 400, method 500, method 600, or method 700 of the above embodiments.

As shown in fig. 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 processor (English: central processing unit, abbreviated: CPU), a network processor (English: network processor, abbreviated: NP) or a combination of CPU and NP. The processor may also be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD) or a combination thereof (English: programmable logic device). The PLD may be a complex programmable logic device (English: complex programmable logic device, abbreviated: CPLD), a field programmable gate array (English: field-programmable gate array, abbreviated: FPGA), a general-purpose array logic (English: generic array logic, abbreviated: GAL), or any combination thereof. Processor 1310 may refer to one processor or may include multiple processors. Memory 1320 may include volatile memory (English) such as random-access memory (RAM); the memory may also include a nonvolatile memory (english: non-volatile memory), such as a read-only memory (ROM), a flash memory (english: flash memory), a hard disk (HDD) or a Solid State Disk (SSD); memory 1320 may also include combinations of the above types of memory. Memory 1320 may refer to one memory or may include multiple memories. In one embodiment, memory 1320 stores computer readable instructions that include a plurality of software modules, such as a transmit module 1321, a process module 1322, and a receive module 1323. The processor 1310, after executing the respective software modules, may perform corresponding operations as directed by the respective software modules. In this embodiment, the operations performed by one software module actually refer to operations performed by the processor 1310 according to instructions of the software module.

In one example, the communications apparatus 1300 can perform the method 100 of the above embodiment, and when the communications apparatus 1300 is used to perform the method 100 of the above embodiment, the communications apparatus 1300 corresponds to the communications apparatus 1 of the method 100. The transceiver 1330 is configured to perform a transceiving operation performed by the communication device 1 in the method 100. The processor 1310 is configured to perform operations of the method 100 other than the transceiving operations performed by the communication device 1. For example: the processor 1310 is configured to determine that the FGU layer is operating abnormally; the transceiver 1330 is configured to send fault indication information to the communication device 2, where the fault indication information is used to indicate a remote fault.

In one example, the communications apparatus 1300 can perform the method 100 of the above embodiment, where the communications apparatus 1300 is configured to perform the method 100 of the above embodiment, the communications apparatus 1300 corresponds to the communications apparatus 2 of the method 100. The transceiver 1330 is configured to perform transceiving operations performed by the communication device 2 in the method 100. The processor 1310 is configured to perform operations other than the transceiving operations performed by the communication device 2 in the method 100. For example: the transceiver 1330 is configured to receive fault indication information sent by the communication device 1, where the fault indication information is used to indicate a remote fault; the processor 1310 is configured to determine that the communication apparatus 1 is malfunctioning.

In one example, the communications apparatus 1300 can perform the method 200 of the above embodiment, and when the communications apparatus 1300 is used to perform the method 200 of the above embodiment, the communications apparatus 1300 corresponds to the communications apparatus 1 of the method 200. The transceiver 1330 is configured to perform a transceiving operation performed by the communication device 1 in the method 200. The processor 1310 is configured to perform operations of the method 200 other than the transceiving operations performed by the communication device 1. For example: the processor 1310 is configured to determine that the FGU layer is operating abnormally; the transceiver 1330 is configured to send alarm information to the control management device, where the alarm information is used to indicate a local failure.

In one example, the communications apparatus 1300 can perform the method 300 of the above embodiment, where the communications apparatus 1300 is equivalent to the communications apparatus 1 of the method 300 when the communications apparatus 1300 is used to perform the method 300 of the above embodiment. The transceiver 1330 is configured to perform a transceiving operation performed by the communication device 1 in the method 300. The processor 1310 is configured to perform operations of the method 300 other than the transceiving operations performed by the communication device 1. For example: the processor 1310 is configured to determine an operating state of the FGU layer; the transceiver 1330 is configured to send status indication information to the communication device 2, where the status indication information is used to indicate an operating status of the FGU layer.

In one example, the communications apparatus 1300 can perform the method 300 of the above embodiment, where the communications apparatus 1300 is equivalent to the communications apparatus 2 of the method 300 when the communications apparatus 1300 is used to perform the method 300 of the above embodiment. Transceiver 1330 is configured to perform transceiving operations performed by communication device 2 in method 300. The processor 1310 is configured to perform operations other than the transceiving operations performed by the communication device 2 in the method 300. For example: the transceiver 1330 is configured to receive status indication information sent by the communication device 1, where the status indication information is used to indicate an operating status of the FGU layer; the processor 1310 is for determining an operating state of an FGU layer of the communication device 1.

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

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

In one example, the communications apparatus 1300 can perform the method 600 of the above embodiment, where the communications apparatus 1300 is configured to perform the method 600 of the above embodiment, the communications apparatus 1300 is equivalent to the first communications apparatus of the method 600. The transceiver 1330 is configured to perform a transceiving operation performed by the first communication device in the method 600. The processor 1310 is configured to perform operations other than the transceiving operations performed by the first communication device in the method 600. For example: the processor 1310 is configured to determine an operating state of the fine grain unit FGU layer; the transceiver 1330 is configured to send status indication information to an upstream node, where the status indication information is used to indicate an operating status of the FGU layer.

In one example, the communications apparatus 1300 can perform the method 700 of the above embodiment, where the communications apparatus 1300 is configured to perform the method 700 of the above embodiment, the communications apparatus 1300 is equivalent to the second communications apparatus of the method 700. The transceiver 1330 is configured to perform a transceiving operation performed by the second communication device in the method 700. The processor 1310 is configured to perform operations other than the transceiving 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 communications device, where the status indication information is used to indicate a working status of the fine granularity unit FGU layer at the far end; the processor 1310 is configured to determine an operating state of an FGU layer of the first communication device based on the state indication information.

The application also provides a computer readable storage medium having instructions stored therein, which when run on a computer, cause the computer to perform any one or more of the operations of the methods described in the previous embodiments (e.g., method 100, method 200, method 300, method 400, method 500, method 600, or method 700).

The application also provides a computer program product comprising a computer program which, when run on a computer, causes the computer to perform any one or more of the operations of the methods described in the previous embodiments (e.g. method 100, method 200, method 300, method 400, method 500, method 600 or method 700).

The present application also provides a communication system comprising the communication device 1 and the communication device 2 mentioned in the above embodiment method 100.

The present application also provides a communication system comprising the communication device 1 and the communication device 2 mentioned in the above embodiment method 300.

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

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

The present application also provides a communication system comprising at least one memory and at least one processor, the at least one memory storing instructions that, when executed, cause the communication system to perform any one or more of the operations of the method (e.g., method 100, method 200, method 300, method 400, method 500, method 600, or method 700) of any of the preceding embodiments of the present application.

The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.

In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, e.g., the division of units is merely a logical service division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

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

In addition, each service unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software business units.

The integrated units, if implemented in the form of software business units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods of the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

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

The objects, technical solutions and advantageous effects of the present application have been described in further detail in the above embodiments, and it should be understood that the above are only embodiments of the present application.

The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the application.

Claims

1. A method of fault notification, for use with a first communication device, the method comprising:

determining that the fine granularity unit FGU layer works abnormally;

and sending fault indication information to an upstream node, wherein the fault indication information is used for indicating a remote fault.

2. The method of claim 1, wherein the remote failure comprises:

remote FGU layer failure.

3. The method according to claim 1 or 2, characterized in that the fault indication information is carried by a base frame overhead.

4. A method according to claim 3, characterized in that the fault indication information is carried by a reserved field of the base frame overhead.

5. A method according to claim 3, characterized in that the fault indication information is carried by an identification flag field of the base frame overhead.

6. The method according to claim 1 or 2, wherein the fault indication information is carried by an operation maintenance management OAM code block of an MTN channel layer of a metropolitan area transport network.

7. The method of claim 6, wherein a type field in the OAM code block is used to indicate that the OAM code block carries the fault indication information.

8. The method of claim 6, wherein the OAM code block is a basic OAM code block.

9. The method of claim 8, wherein the fault indication information is remote fault indication information RDI.

10. The method of claim 8, wherein the fault indication information is carried by a reserved field in the basic OAM code block.

11. The method of any of claims 1-10, wherein the determining FGU layer operational anomalies comprises:

12. The method according to any of claims 1-11, wherein the service layer of the FGU layer is an MTN channel layer or an ethernet physical layer.

13. The method according to any of claims 1-12, wherein the first communication device is an intermediate node of an end-to-end path of small particle traffic carried by the FGU layer.

14. The method according to any of claims 1-13, wherein the upstream node is an intermediate node of an end-to-end path of small particle traffic carried by the FGU layer.

15. The method according to claim 1, wherein the method further comprises:

determining that the FGU layer works normally;

and sending fault recovery information to the upstream node, wherein the fault recovery information is used for indicating that the far end is normal.

16. The method of claim 15, wherein the distal end normally comprises:

the far-end FGU layer is normal.

17. A method of failure notification applied to a second communication device, the method comprising:

receiving fault indication information sent by a first communication device, wherein the fault indication information is used for indicating a remote fault;

and determining that the first communication device fails based on the failure indication information.

18. The method of claim 17, wherein the remote failure comprises: far-end fine grain base unit FGU layer failure.

19. The method according to claim 17 or 18, wherein the fault indication information is carried by a base frame overhead.

20. The method of claim 19, wherein the fault indication information is carried by a reserved field of the base frame overhead.

21. The method of claim 19, wherein the fault indication information is carried by an identification flag field of the base frame overhead.

22. The method according to claim 17 or 18, wherein the fault indication information is carried by an operation maintenance management OAM code block of an MTN channel layer of a metropolitan area transport network.

23. The method of claim 22, wherein a type field in the OAM code block is used to indicate that the OAM code block carries the fault indication information.

24. The method of claim 22, wherein the OAM code block is a basic OAM code block.

25. The method of claim 24, wherein the fault indication information is remote fault indication information RDI.

26. The method of claim 24, wherein the fault indication information is carried by a reserved field in the basic OAM code block.

27. The method according to any of the claims 17-26, wherein the service layer of the FGU layer is an MTN channel layer or an ethernet physical layer.

28. The method of claim 18, wherein the method further comprises:

29. The method of claim 28, wherein the first communication device is operating abnormally, comprising:

The FGU layer of the first communication device operates abnormally.

30. The method according to any one of claims 17-29, further comprising:

and receiving fault recovery information sent by the first communication device, wherein the fault recovery information is used for indicating that the far end is normal.

31. The method of claim 30, wherein the method further comprises:

and carrying out time slot synchronization with the first communication device.

32. The method according to any of claims 17-31, wherein the first communication device is an intermediate node of an end-to-end path of small particle traffic carried by the FGU layer.

33. The method according to any of claims 17-32, wherein the upstream node is an intermediate node of an end-to-end path of small particle traffic carried by the FGU layer.

34. A method of status notification applied to a first communication device, the method comprising:

determining the working state of a fine grain unit FGU layer;

and sending state indication information to an upstream node, wherein the state indication information is used for indicating the working state of the FGU layer.

35. The method of claim 34, wherein the operating state of the FGU layer comprises:

FGU layers work properly.

36. The method according to claim 34 or 35, wherein the status indication information is carried by a base frame overhead.

37. The method of claim 36, wherein the status indication information is carried by a reserved field of the base frame overhead.

38. The method of claim 36, wherein the status indication information is carried by an identification flag field of the base frame overhead.

39. The method according to claim 34 or 35, wherein the status indication information is carried by an operation maintenance management OAM code block of an MTN channel layer of the metropolitan area transport network.

40. The method of claim 39, wherein a type field in the OAM code block is used to indicate that the OAM code block carries the status indication information.

41. The method of claim 39, wherein the OAM code block is a basic OAM code block.

42. The method of claim 41, wherein the status indication information is carried by a reserved field in the basic OAM code block.

43. The method of any of claims 34-42, wherein the service layer of the FGU layer is an MTN channel layer or an ethernet physical layer.

44. The method of any one of claims 34-43, wherein the first communication device is an intermediate node of an end-to-end path of small particle traffic carried by the FGU layer.

45. The method according to any one of claims 34-44, wherein the upstream node is an intermediate node of an end-to-end path of small particle traffic carried by the FGU layer.

46. A method of status notification applied to a second communication device, the method comprising:

receiving state indication information sent by a first communication device, wherein the state indication information is used for indicating the working state of a fine granularity unit FGU layer at a far end;

and determining the working state of the FGU layer of the first communication device based on the state indication information.

47. The method of claim 46, wherein the operating state of the FGU layer comprises:

FGU layers work properly.

48. The method of claim 46 or 47, wherein the status indication information is carried by a base frame overhead.

49. The method of claim 48, wherein the status indication information is carried by a reserved field of the base frame overhead.

50. The method of claim 48, wherein the status indication information is carried by an identification flag field of the base frame overhead.

51. The method of claim 46 or 47, wherein the status indication information is carried by an operation, maintenance and administration OAM code block of an MTN channel layer of the metropolitan area transport network.

52. The method of claim 51, wherein a type field in the OAM code block is used to indicate that the OAM code block carries the status indication information.

53. The method of claim 51, wherein the OAM code block is a basic OAM code block.

54. The method of claim 53, wherein the status indication information is carried by a reserved field in the basic OAM code block.

55. The method of any of claims 46-54, wherein the service layer of the FGU layer is an MTN channel layer or an ethernet physical layer.

56. The method of any one of claims 46-55, wherein the first communication device is an intermediate node of an end-to-end path of small particle traffic carried by the FGU layer.

57. The method according to any one of claims 46-56, wherein the upstream node is an intermediate node of an end-to-end path of small particle traffic carried by the FGU layer.

58. A first communication device, the device comprising:

a transceiver unit and a processing unit;

the transceiver unit for performing 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 transmitting operations performed by the first communication device as claimed in any of claims 1-16.

59. A second communication device, the device comprising:

a transceiver unit and a processing unit;

the transceiver unit for performing 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 transmitting operations performed by the second communication device according to any of claims 17-33.

60. A first communication device, the device comprising:

a transceiver unit and a processing unit;

the transceiver unit for performing the receiving and/or transmitting operations performed by the first communication device of 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 of any of claims 34-45.

61. A second communication device, the device comprising:

a transceiver unit and a processing unit;

the transceiver unit for performing 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 as claimed in any of claims 46-57.

62. A communication device, comprising: a processor and a memory;

the memory is used for storing instructions;

the processor configured to execute the instructions to cause the communication device to perform the method of any one of claims 1-57.

63. A computer readable storage medium comprising instructions which, when executed on a processor, implement the method of any one of claims 1-57.

64. A communication system, the communication system comprising:

a first communication device performing the method of any of the preceding claims 1-16 and a second communication device performing the method of any of the claims 17-33; or alternatively, the process may be performed,

a first communication device performing the method of any of the preceding claims 34-45 and a second communication device performing the method of any of the claims 46-57.