Link processing method and related equipment

Abstract

The invention provides a link processing method and related equipment, relates to the technical field of communication, and can shorten the duration required by the through-flow of a link group when a link in the link group has a fault, thereby shortening the damaged time of a service running on the link group. In the method, when a first link has a first fault, a first device acquires the type of the first fault; when the type of the first fault is a first type and a second link does not have a fault, the speed of the second link is adjusted to a first speed, the first speed is smaller than the speed of the second link, the difference value between the first speed and the speed of the first link is smaller than a first threshold value, and the duration of the first type of fault is smaller than a second threshold value; the first link and the second link are in a first link group.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to a link processing method and related equipment. Background Technology

[0002] Currently, Flexible Ethernet (FlexE) is becoming increasingly widely used. FlexE is a low-cost, highly reliable, and dynamically configurable interface technology based on high-speed Ethernet interfaces, achieved by decoupling the Ethernet Media Access Control (MAC) layer from the Physical (PHY) layer. In FlexE technology, the path through which data or information is transmitted via the PHY interface is also called a link. By binding multiple links, greater transmission performance can be achieved. Multiple bound links together form a link group. FlexE technology allows for flexible adjustment of the links used for data transmission to adapt to different network transmission needs.

[0003] Link failures can occur in FlexE. For example, if a link failure is short-lived, such as a brief interruption of a link, the entire link group to which that link belongs will be disconnected (link down), causing service interruptions within the link group. To ensure normal service operation, the link group needs to resume operation. However, resuming operation in a link group usually involves a series of processes, which can lead to prolonged service disruptions.

[0004] Therefore, how to shorten the time required for the link group to process data when a link in the link group fails is an urgent technical problem that needs to be solved. Summary of the Invention

[0005] This application provides a link processing method and related equipment, which can shorten the time required for the link group to process traffic when a link in the link group fails, thereby shortening the time when services running on the link group are damaged.

[0006] This application provides a link processing method in its first aspect. This method is executed by a first device, or by a component (e.g., a processor, chip, or chip system) within the first device, or by a logic module or software capable of implementing all or part of the functions of the first device. In the first aspect and its possible implementations, the link processing method is described as being executed by the first device. When a first fault occurs in the first link, the first device obtains the type of the first fault. When the type of the first fault is a first type and a second link does not experience a fault, the speed of the second link is adjusted to a first speed, wherein the first speed is less than the speed of the second link, the difference between the first speed and the speed of the first link is less than a first threshold, the duration of the first type of fault is less than a second threshold, and the first link and the second link are in a first link group.

[0007] In the first aspect, when the first link experiences a Type I failure, the speed of the normal link (e.g., the speed of the second link) is adjusted to be as close as possible to the speed of the first link. During the period of link failure, this speed adjustment method can maintain the phase between the normal link and the link experiencing the Type I failure. For example, because the speeds of the first and second links are as close as possible, the difference in buffer watermarks between the second and first links can remain consistent, and the difference in overhead frame arrival times between the second and first links can remain consistent. After overhead locking and multiframe locking are performed, because the link group achieves phase maintenance, the link group can directly transmit traffic, shortening the time consumed by traffic transmission in the link group, thereby shortening the time when services running on the link group are impaired.

[0008] In one alternative implementation of the first aspect, the first speed is equal to the speed of the first link.

[0009] Based on the above implementation, by controlling the speed of the second link to be consistent with that of the first link, the difference between the buffer waterlines of the second link and the first link will be consistent, and the arrival time of the overhead frames of the second link and the first link will be consistent. Therefore, the phase of the second link and the first link can be maintained, thereby shortening the time consumed by group flow.

[0010] Optionally, the first speed is the reference speed for establishing the link.

[0011] In one alternative implementation of the first aspect, the first device sends a first message to a first interface, the first message being used to instruct the first interface to adjust the speed of the second link to the first speed, the first interface being the interface of the second link.

[0012] Based on the above implementation, the first device adjusts the speed of the second link by sending a first message control interface so that the speed of the second link is as consistent as possible with the speed of the first link, thereby achieving phase maintenance.

[0013] Optionally, the first interface can be the interface of the first device, and "the first device sends a first message to the first interface" can be the CPU of the first device sending a first message to the PHY interface of the first device.

[0014] Optionally, the first message can also be used to instruct the first link group to enter a second state, where the second state indicates that the first link group will rapidly process data. The first interface will adjust its exit speed to a first speed according to the instruction of the first message, that is, by adjusting the exit speed, it achieves "adjusting the speed of the second link to the first speed".

[0015] Optionally, the first device can distinguish the type of the first fault based on the duration of the fault.

[0016] Optionally, when the duration of the first link failure is less than the second threshold, the first link failure is classified as the first type; when the duration of the first link failure is not less than the second threshold, the first link failure is classified as the second type.

[0017] Optionally, the first device can distinguish the type of the first fault based on the duration of the fault.

[0018] Optionally, when the duration of the first link failure is less than the second threshold, the first link failure is classified as the first type; when the duration of the first link failure is not less than the second threshold, the first link failure is classified as the second type.

[0019] Optionally, the first device can distinguish the type of the first fault based on the historical status of the first link or the link group to which the first link belongs.

[0020] Optionally, the aforementioned historical states include: whether the first link is in a first state, and the status information of the first link. When the first link is in the first state, the first fault type of the first link is considered to be the second type; when the first link is not in the first state, the first fault type of the first link is considered to be the first type. Alternatively, if the status information of the first link indicates that the duration of the link down interruption exceeds a second threshold, the fault of the first link is considered to be the second type. If the status information of the first link indicates that the duration of the link down interruption does not exceed the second threshold, the fault of the first link is considered to be the first type.

[0021] In one alternative implementation of the first aspect, when the type of the first fault is the first type and the second link is not faulty, the status information of the second link indicates that the first link is in a connected state.

[0022] Based on this implementation method, when the first link experiences a first type of failure, the second link can be controlled to maintain the connection, that is, the links in the first link group that have not experienced a failure can be controlled to maintain the connection. As a result, the services on the links that have not experienced a failure can operate normally. In other words, in this solution, normal services, that is, normal services running on the links that have not experienced a failure, will not be damaged due to the failure of the first link. This solution can reduce the scope of service damage caused by the failure of the first link, or reduce the time of service damage.

[0023] Alternatively, to keep the second link connected, group linkdown may not be performed.

[0024] In one alternative implementation of the first aspect, the first link is the link with the last phase order in the first link group.

[0025] Based on the above implementation, when the first link is the last link in the first link group in terms of phase order, the phase order of the second link in the first link group is earlier than that of the first link. At this time, by adjusting the speed of the second link, so that the speed of the second link is as consistent as possible with that of the first link, the phase of the second link relative to the first link can remain unchanged.

[0026] Optionally, different links in the first link group may have phase ordering. The first link may be determined as the last link in the phase ordering of the first link group by one or more of the following methods: when the buffer waterline of the first link in the first link group is the lowest, the first link is considered to be the last link in the phase ordering of the first link group; or when the oh of the first link in the first link group is the last to arrive, the first link is considered to be the last link in the phase ordering of the first link group.

[0027] Optionally, the second link is one or more channels of Flexible Ethernet, and optionally, each link in the first link group is one or more channels of Flexible Ethernet.

[0028] Optionally, "the second link is not faulty" can mean that the second link is not faulty of the first type and not faulty of the second type, or that the second link is not faulty of the first type or not faulty of the second type or the second link is normally connected.

[0029] Optionally, the first device can adjust the speed of the first link group at the link group level. Alternatively, it can adjust the speed of the links in the first link group at the link level.

[0030] Optionally, if the second link does not experience a fault or is not in a fault recovery state during the period from the occurrence of the first fault in the first link to the establishment of the first link, then it is not necessary to adjust the speed of the second link.

[0031] Optionally, if the second link fails before the first link fails and the second link is re-established after the first link is re-established, it is not necessary to reduce the speed of the second link.

[0032] Optionally, if the second link fails before the first link fails, and the second link is established before the first link is established, then when the first link fails, there is no need to slow down the second link; and when the second link is established, there is no need to accelerate it. It should be noted that when the second link is established, it is generally necessary to accelerate it. However, in this case, because the first link has experienced a type-one fault, phase maintenance is required to prevent acceleration of the second link.

[0033] Optionally, if the second link fails after the first link fails, and the second link is established after the first link is established, then the second link needs to be slowed down when the first link fails.

[0034] Optionally, if the second link fails after the first link fails but is established before the first link is established, then the second link needs to be slowed down when the first link fails, and it does not need to be accelerated when the second link is established.

[0035] In one alternative implementation of the first aspect, before the first link is established, the calendar information of the first link group is the first information, which includes: the domain segment information or the mapping relationship between time slots and ports in the overhead frame when the first link experiences the first failure.

[0036] Based on the above implementation, after the first link fails and before the first link is re-established, the calendar information is always the same as the calendar information at the time of the first link failure. Therefore, during the period from the first link failure to the re-establishment of the first link, the first device keeps the calendar information of the first link group unchanged. This shortens the time required to refresh the calendar information, thereby reducing the time consumed for group flow and minimizing the time of service disruption on the group.

[0037] Optionally, the overhead frame mentioned above is an overhead frame in the first link group, and the "mapping relationship between time slots and ports" mentioned above can be a mapping relationship between time slots and ports in the first link group. The mapping relationship between time slots and ports includes: a mapping relationship between internal ports and time slots or a mapping relationship between external ports and time slots. The internal port can be a port within the first link group, and the external port can be a port outside the first link group or a port outside the first device.

[0038] In one optional implementation of the first aspect, after the first link is established, if the second information is different from the first information, the calendar information is updated based on the second information. The second information includes: the domain segment information or the mapping relationship between time slots and ports in the overhead frame after the first link is established; if the second information is the same as the first information, the calendar information is the first information.

[0039] Based on the above implementation, when the second information is different from the first information, that is, when it is different from the calendar information received before the first link failure, updating the calendar information based on the second information can ensure that the domain segment information or time slot and port in the overhead frame saved by the first device are consistent with those sent by the sending end, which is beneficial to the stability of the link connection. When the second information is different from the first information, the calendar information is still consistent with the first information, which can shorten the time used to refresh the first information, that is, the calendar information, thereby shortening the time required for group flow and reducing the damage time of services executed on the group.

[0040] In one alternative implementation of the first aspect, when the type of the first fault is the second type and the first link group is switched to the second link group, the second device deletes the third information of the first link, wherein the third information is related to a first state, the first state indicating that the services running on the first link are isolated from the services running on the links in the first link group that have not experienced a fault.

[0041] Based on the above implementation, when the first link experiences a second type of failure, i.e., a prolonged link interruption, a link group switch will occur, switching from the first link group to the second link group. During this switch, the link group typically experiences a brief interruption, requiring the entire link group to be re-established. Secondly, by releasing the first state of the first link, it's possible to re-establish the first link normally, and other fault-free links within the group can also re-establish links normally, thus enabling full service recovery and shortening the duration of service disruption.

[0042] Optionally, the second link group is a backup link group when any link in the first link group fails. When the first link is in the first state, the services running on the first link are isolated from the services running on the links in the first link group that have not failed.

[0043] Optionally, the second link group may overlap with all or some of the links in the first link group, or the second link group may not overlap with all or some of the links in the first link group.

[0044] Optionally, when a link fails and the link group used for information transmission switches from the first link group to the second link group, the first state of the first link will be synchronized to the second link group through the interface of the second link group. That is, after the link group switch, the first link in the second link group will still be in the first state.

[0045] In one alternative implementation of the first aspect, the third information includes: historical information, link isolation signal, or anomaly source signal used to indicate the first fault.

[0046] Based on the above implementation method, by deleting historical information, link isolation signals, or abnormal source signals used to indicate the first fault, the second device can release the signal used to isolate the second link and the signal used to set the first link to the first state. That is, the first link can no longer be in the first state, so the first link can be established normally and the services running on the first link can be restored, thereby shortening the service recovery time.

[0047] In one alternative implementation of the first aspect, after the second link group begins establishing a link, the second device sets the link in the second link group that experiences the second type of fault to the first state.

[0048] In this implementation, once the link group starts establishing a link, the link experiencing the second type of failure is set to the first state. For example, the link that cannot establish a link for a long time after switching links is set to the first state. This isolates the services on the links experiencing the second type of failure from the services on the normal links. This allows the links that do not experience the second type of failure to successfully establish a link, and also allows the services on the links that do not experience the second type of failure to operate normally, thereby shortening the time that the services running on the normal links are damaged.

[0049] In one alternative implementation of the first aspect, the first link is one or more channels of a flexible Ethernet.

[0050] The above implementation is an example of the application of this solution in flexible Ethernet. In this example, if any one or more PHYs among the multiple PHYs bound in the flexible Ethernet fail, the second aspect can delete the information related to the first state of the failed PHY, so that the failed PHY can establish a link normally, and the services in the PHY group to which the multiple bound PHYs belong can be fully restored.

[0051] Optionally, the second device can determine whether a link in the second link group has experienced a second type of fault by: starting from the moment when the first link in the second link group is established, if a link has not been established after exceeding a threshold, then a second type of fault is considered to exist.

[0052] A second aspect of this application provides a link processing method, which is executed by a second device, or by some components (e.g., a processor, chip, or chip system) of the second device, or by a logic module or software capable of implementing all or part of the functions of the second device. In the second aspect and its possible implementations, the link processing method is described as being executed by a second device. When a first link experiences a first fault, the second device obtains the type of the first fault. When the type of the first fault is a second type, and the first link group switches to the second link group, the second device deletes third information about the first link. The duration of the second type of fault is less than a second threshold. The third information is related to a first state, which indicates that the services running on the first link are isolated from the services running on links in the first link group that have not experienced a fault.

[0053] In an alternative implementation of the second aspect, after the second link group begins establishing a link, the second device sets the link in the second link group that experiences the second type of fault to the first state.

[0054] In this implementation, once the link group starts establishing a link, the link experiencing the second type of failure is set to the first state. For example, the link that cannot establish a link for a long time after switching links is set to the first state. This isolates the services on the links experiencing the second type of failure from the services on the normal links. This allows the links that do not experience the second type of failure to successfully establish a link, and also allows the services on the links that do not experience the second type of failure to operate normally, thereby shortening the time that the services running on the normal links are damaged.

[0055] In one alternative implementation of the second aspect, the first link is one or more channels of a flexible Ethernet.

[0056] The above implementation is an example of the application of this solution in flexible Ethernet. In this example, if any one or more PHYs among the multiple PHYs bound in the flexible Ethernet fail, the second aspect can delete the information related to the first state of the failed PHY, so that the failed PHY can establish a link normally, and the services in the PHY group to which the multiple bound PHYs belong can be fully restored.

[0057] In one alternative implementation of the second aspect, the first link is one or more channels of a flexible Ethernet.

[0058] The above implementation is an example of the application of this solution in flexible Ethernet. In this example, if any one or more PHYs among the multiple PHYs bound in the flexible Ethernet fail, the second aspect can delete the information related to the first state of the failed PHY, so that the failed PHY can establish a link normally, and the services in the PHY group to which the multiple bound PHYs belong can be fully restored.

[0059] A third aspect of this application provides a communication device, which includes a transceiver unit and a processing unit for performing all or part of the operations described in the first or second aspect. The communication device may be a network device such as a router or switch, or a component within a network device for performing related operations, such as a line card or interface board, or a chip system for performing related operations, which may include one or more chips. When the communication device is a chip system, the receiving module and the transmitting module may be, for example, the interface circuitry of the chip, and the processing module may be, for example, the processing circuitry of the chip.

[0060] For example, when performing the method described in the first aspect, the transceiver unit is configured to obtain the type of the first fault when a first fault occurs in the first link; the processing unit is configured to adjust the speed of the second link to a first speed when the type of the first fault is a first type and the second link does not fail, the first speed is less than the speed of the second link, the difference between the first speed and the speed of the first link is less than a first threshold, the duration of the first type of fault is less than a second threshold, and the first link and the second link are in a first link group.

[0061] In one alternative implementation of the third aspect, the first speed is equal to the speed of the first link.

[0062] In an optional implementation of the third aspect, the transceiver unit is further configured to: send a first message to a first interface, the first message being used to instruct the first interface to adjust the speed of the second link to the first speed, the first interface being the interface of the second link.

[0063] In one alternative implementation of the third aspect, the first link is the link with the last phase order in the first link group.

[0064] In one alternative implementation of the third aspect, when the type of the first fault is the first type and the second link is not faulty, the status information of the second link indicates that the first link is in a connected state.

[0065] In one alternative implementation of the third aspect, before the establishment of the first link, the calendar information of the first link group is the first information, which includes: the domain segment information or the mapping relationship between time slots and ports in the overhead frame when the first link experiences the first failure.

[0066] In an optional implementation of the third aspect, the processing unit is further configured to: after the first link is established, if the second information is different from the first information, update the calendar information based on the second information, wherein the second information includes: the domain segment information or the mapping relationship between time slots and ports in the overhead frame after the first link is established; if the second information is the same as the first information, the calendar information is the first information.

[0067] In an optional implementation of the third aspect, the processing unit is further configured to: when the type of the first fault is the second type, the duration of the second type of fault is not less than the second threshold; when the first link group is switched to the second link group, delete the third information of the first link, the third information being related to the first state, the first state indicating that the services running on the first link are isolated from the services running on the links in the first link group that have not experienced a fault.

[0068] In one alternative implementation of the third aspect, the third information includes: historical information indicating the first fault, a link isolation signal, or an anomaly source signal.

[0069] In an alternative implementation of the third aspect, the processing unit is further configured to: set the link in the second link group that experiences the second type of fault to the first state after the second link group begins link establishment.

[0070] In one alternative implementation of the third aspect, the first link is one or more channels of a flexible Ethernet.

[0071] For example, when performing the method described in the second aspect, the transceiver unit is configured to obtain the type of the first fault when a first fault occurs in the first link; the processing unit is configured to delete the third information of the first link when the duration of the second type of fault is not less than the second threshold when the first link group is switched to the second link group, the third information being related to a first state, the first state indicating that the services running on the first link are isolated from the services running on the links in the first link group that have not experienced a fault.

[0072] In one alternative implementation of the third aspect, the third information includes: historical information indicating the first fault, a link isolation signal, or an anomaly source signal.

[0073] In an alternative implementation of the third aspect, the processing unit is further configured to: set the link in the second link group that experiences the second type of fault to the first state after the second link group begins link establishment.

[0074] In one alternative implementation of the third aspect, the first link is one or more channels of a flexible Ethernet.

[0075] A fourth aspect of this application provides a communication system comprising a first device and a third device. The first device is configured to perform the method described in the first aspect and any possible implementation or design thereof. Upon receiving a message, the first device forwards the message to the third device via all or part of a first link, or the third device sends the message to the third device via all or part of the first link. Alternatively, the communication system comprises a second device and a fourth device. The second device is configured to perform the method described in the second aspect and any possible implementation or design thereof. Upon receiving a message, the second device forwards the message to the fourth device via all or part of a first link, or the fourth device sends the message to the second device via all or part of the first link.

[0076] A fifth aspect of this application provides a communication device, including a processor and a communication interface. The processor and communication interface are used to execute methods implementing the first or second aspect described above, and any possible implementation or design thereof.

[0077] Optionally, the processor is coupled to a memory, for example, a memory used to store programs or instructions. The at least one processor is used to execute the program or instructions to cause the device to perform all or part of the operations described in the first or second aspect and any possible implementation or design thereof.

[0078] The sixth aspect of this application provides a computer-readable storage medium storing a program or instructions that, when run on a processor, execute the methods described in the first or second aspect and any possible implementation or design thereof.

[0079] The seventh aspect of this application provides a computer program product, including a program or instructions that, when run on a processor, implement all or part of the operations described in the first or second aspect and any possible implementation or design thereof.

[0080] In one specific design, the computer program product may be a computer-readable storage medium as mentioned in the eighth aspect above.

[0081] The eighth aspect of this application provides a chip system including at least one processor for supporting all or part of the functions of the communication device as described in the first or second aspect and any possible implementation or design thereof.

[0082] Optionally, the chip system includes a flexible Ethernet shim, which supports all or part of the functionality of the communication device as described in the first or second aspect and any possible implementation or design thereof.

[0083] The technical effects of any one of the third to eighth aspects can be referred to in the above-mentioned first or second aspects and any possible implementation or design methods, and will not be repeated here. Attached Figure Description

[0084] Figure 1a A schematic diagram of a system architecture provided for an embodiment of this application;

[0085] Figure 1b A schematic diagram of a flexible Ethernet system architecture provided in this application embodiment;

[0086] Figure 2 A schematic diagram of another flexible Ethernet system architecture provided in the embodiments of this application;

[0087] Figure 3 A flowchart illustrating a method 100 provided in an embodiment of this application;

[0088] Figure 4 A schematic diagram illustrating the phase and speed processing of the link provided in an embodiment of this application;

[0089] Figures 5a to 5e This is a schematic diagram illustrating the speed processing of the second link provided in an embodiment of this application;

[0090] Figure 6 A schematic diagram illustrating the execution sequence of each process step or operation provided in the embodiments of this application;

[0091] Figure 7 A flowchart illustrating a method 200 provided in an embodiment of this application;

[0092] Figure 8 A schematic diagram illustrating the type of first fault provided in an embodiment of this application;

[0093] Figure 9 A schematic diagram illustrating primary / backup link switching provided in an embodiment of this application;

[0094] Figure 10 A schematic diagram of link switching provided in an embodiment of this application;

[0095] Figure 11 This is a schematic diagram illustrating the process of determining link failure provided in an embodiment of this application;

[0096] Figure 12 A schematic diagram of a communication device provided in an embodiment of this application;

[0097] Figure 13 This is yet another structural schematic diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0098] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the implementation methods of the embodiments of this application will be further described in detail below with reference to the accompanying drawings.

[0099] The following explanations are provided for some of the terms used in the embodiments of this application.

[0100] 1. FlexE

[0101] FlexE technology, based on high-speed Ethernet interfaces, decouples Ethernet MAC and PHY rates to achieve flexible control of interface rates, adapting to different network transmission structures. Network hard slicing technology, primarily used in wide area networks (WANs) and transport networks, meets the differentiated needs of various services on the same network through network slicing. This allows operators to build multiple dedicated, virtualized, and isolated logical networks on top of a common physical network. FlexE technology belongs to third-generation Ethernet technology, and its most important function is to decouple the physical layer (rate) and MAC layer to meet the high-bandwidth, flexible access requirements of 5G mobile communication systems (such as New Radio (NR) systems), future communication systems, or other similar communication systems.

[0102] 2. FlexE Client

[0103] The FlexE Client corresponds to the traditional interface in an Ethernet network. It is an Ethernet data stream based on the MAC layer rate, and its rate is not fixed. It is used to interface with UNI (User Network Interface) with different rate requirements. The FlexE Client data stream is encoded in 64B / 66B to form multiple data blocks. These blocks are inserted into the Sub-Calendar at a certain location in the FlexE group.

[0104] 3. FlexE Shim

[0105] The FlexE Shim sits between the MAC and PHY layers and is the core processing logic layer of FlexE. It maps the FlexEClient data stream from the MAC layer to the PHY of the FlexE group for transmission; it also supports reverse mapping of data transmitted by the PHY within the FlexE group back to the FlexE Client data stream at the MAC layer. The FlexE Shim can perform bandwidth bundling, sub-rate processing, and channelization based on the group-to-group PHY bandwidth.

[0106] 4. FlexE Calendar

[0107] FlexE Calendar is the mechanism used by FlexE Shim to handle mapping and demapping. A 100G PHY within a FlexE group is divided into 20 slots. Each PHY's set of slots is called a Sub-Calendar, and each slot carries a 5G bandwidth. FlexE Calendar allocates the 66B data blocks carried on the Sub-Calendar of each PHY within the FlexE group to designated FlexE Clients. Theoretically, each FlexE Client can be configured with a bandwidth that is a multiple of 5G.

[0108] 5. FlexE bonding

[0109] FlexE supports bundling multiple IEEE 802.3 standard PHY interfaces, enabling them to work together to support higher speeds. For example, bundling two 100G PHY interfaces can achieve a MAC layer speed of 200G. The path through which data or information is transmitted via PHY interfaces is also called a link. By bundling multiple low-speed PHY interfaces, or by bundling multiple links, a FlexE group can be formed. Each FlexE group consists of one or more (up to 254) Ethernet PHYs based on the 802.3 standard. All PHYs within the group use the same physical layer, and each PHY has a unique number within the FlexE group.

[0110] 6. In this application, information, data, and data stream can be used interchangeably. Information, data, and data stream are exemplary names and can be replaced with any possible names, such as message, signaling, data packet, protocol data unit (PDU), or information stream.

[0111] 7. In this application, PHY is an exemplary name and can be replaced with any possible name, such as channel, physical interface, physical chip, physical link or physical path, etc.

[0112] 8. In this application, saving can be done to a buffer, storage area, register, etc., and the form is not limited.

[0113] 9. The terms "system" and "network" in the embodiments of this application can be used interchangeably. "Including" means "including but not limited to". When A includes multiple elements or situations, A can be one or more of those elements or situations. For example, if A includes B or C, then A can be B, A can be C, and A can also be B and C. "At least one" means one or more, and "more than" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, "at least one of A, B, and C" includes A, B, C, AB, AC, BC, or ABC. Furthermore, unless otherwise specified, the ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the order, sequence, priority or importance of multiple objects.

[0114] The system architecture on which the embodiments of this application are based is illustrated below.

[0115] To facilitate understanding of the embodiments of this application, Figure 1a A possible, non-limiting system schematic diagram is shown. Figure 1a The communication system 10 shown includes a transmitter 101 and a receiver 102.

[0116] For example, sender 101 can also be called source 101, and receiver 102 can also be called destination 102. Sender 101 and receiver 102 can transmit data or information, as well as signaling, messages, or signals. The following description uses information transmission between sender 101 and receiver 102 as an example. Sender 101 can be the initial node or an intermediate node in the information transmission process, and receiver 101 can be the terminating node or an intermediate node in the information transmission process. Sender 101 and receiver 102 can be located on the same device or on different devices.

[0117] For example, the transmitter 101 and the receiver 102 can transmit information via link #0, link #2, link #4, or link #6. Links #0, #2, #4, or #6 are bundled into a link group.

[0118] Please see Figure 1b , Figure 1b yes Figure 1a The diagram shown illustrates the system's application in FlexE. Figure 1b The system shown includes: FlexE Shim. Among them, Figure 1b The two FlexE Shims shown can be located at the receiving end and the transmitting end respectively, for example, with Figure 1b Applied to Figure 1a For example, Figure 1b One of the FlexE Shim can be found in Figure 1a In the sender 101, another FlexEShim can be... Figure 1a In the receiver 102.

[0119] Optionally, Figure 1b The FlexE Shim in the FlexE group can map FlexE Client data streams at the MAC layer to the PHYs of a FlexE group for transmission. A FlexE group includes one or more bound Ethernet PHYs, such as 50GBASE-R PHYs, 100GBASE-R PHYs, 200GBASE-R PHYs, or 400GBASE-R PHYs. Here, "PHYs" represents multiple PHYs. A single PHY can constitute a link, or multiple PHYs can collectively form a link.

[0120] Optionally, multiple FlexE Clients can be configured under a single FlexE Group. Each configured FlexE Client generates a FlexE service interface. The PHY FlexE Shim divides the PHY into equal time slots. For example, the FlexE Shim can divide each 100GE PHY in the FlexE Group into 20 time slots for data transport channels, with each time slot corresponding to a bandwidth of 5G. The FlexE Group flexibly provides different bandwidth interfaces (collectively referred to as FlexE Clients) to different users according to different service requirements, with each interface having dedicated bandwidth. For example, if two 100G PHYs constitute two links respectively, and these two 100G PHYs are bound to the FlexE Group, and if each time slot in the FlexE Group is set to 5G, the FlexE Group includes 40 time slots. At this point, these 40 time slots can be flexibly allocated based on business requirements in integer multiples of 5G, meaning one or more time slots can be assigned to multiple FlexE Clients. For example, they can be divided into 3 FlexE service interfaces, i.e., 3 FlexE Clients. These 3 FlexE Clients can each correspond to their own bandwidth. For example, FlexE Client 1 can correspond to a bandwidth of 75G, FlexE Client 2 can also correspond to 75G, or FlexE Client 3 can correspond to 75G and 50G respectively. Among them, the 75G bandwidth consists of 15 time slots, and the 50G bandwidth consists of 10 time slots.

[0121] Optionally, the information structure transmitted on any PHY in a FlexE Group is called a FlexE instance.

[0122] One or more links in the link group can be used to transmit information of one service between sender 101 and sender 102, or they can be used to transmit information of multiple services between sender 101 and sender 102.

[0123] Please see Figure 2 , Figure 2 A possible, non-limiting system schematic diagram is shown. Figure 2 Yes Figure 1a The system shown is yet another alternative example of an application to Flexible Ethernet. Figure 2The system 20 shown includes a transmitter 201 and a receiver 202. The transmitter 201 includes a FlexE Shim (TX) and a serializer / deserializer (serdes) (TX). The receiver 202 includes a FlexE Shim (RX) and serdes (RX). Here, tx represents transmission, rx represents reception, FlexE Shim (TX) indicates that the FlexE Shim is located at the transmitter, FlexE Shim (RX) indicates that the FlexE Shim is located at the receiver, serdes (TX) indicates that the serdes is located at the transmitter, and serdes (RX) indicates that the serdes is located at the receiver.

[0124] like Figure 2 As shown, multiple PHYs exist between the FlexE Shim (TX) and serdes (TX), such as PHY#0, PHY#2, PHY#4, and PHY#6. Optionally, PHY#0, PHY#2, PHY#4, and PHY#6 can be bound to the same FlexE group by the FlexE Shim. The FlexE Shim (TX) can map the data stream of the FlexE Client at the MAC layer to the PHYs of the FlexE group for transmission, that is, map it to PHY#0, PHY#2, PHY#4, and / or PHY#6 for transmission. Figure 2 In this diagram, the transmitting PHY#0 corresponds to lanes #0 and #1. That is, the serial data stream transmitted on transmitting PHY#0 is converted by serdes(TX) and then transmitted in parallel on lanes #0 and #1. Similarly, transmitting PHY#2 corresponds to lanes #2 and #3, transmitting PHY#4 corresponds to lanes #4 and #5, and transmitting PHY#6 corresponds to lanes #6 and #7. The data stream received by serdes(TX) is transmitted to serdes(RX) via lanes #0, etc. Lanes #0 and #1 correspond to receiving PHY#0. That is, the parallel data stream transmitted on lanes #0 and #1 is converted by serdes(RX) and then transmitted in high-speed serial on PHY#0. Similarly, lanes #2 and #3 correspond to receiving PHY#2. The correspondences of other paths are not detailed here.

[0125] Optionally, the transmitting end PHY#0, lane#0, lane#1, and the receiving end PHY#0 can together form one or more links. For example, PHY#0 can form one link, and PHY#0, lane#0, lane#1, and the receiving end PHY#0 as a whole can form one link.

[0126] It should be noted that PHY can be a physical interface, physical channel, physical link, or chip. The fact that both the transmitting PHY#0 and the receiving PHY#0 are named PHY#0 does not mean they are necessarily the same. For example, transmitting PHY#0 could be physical interface 1 in device 1, while receiving PHY#0 could be physical interface 2 in device 1. Similarly, transmitting PHY#0 could be physical interface 1 in device 1, while receiving PHY#0 could be physical interface 3 in device 2.

[0127] exist Figure 1a , Figure 1b or Figure 2 In the system shown, link failures may occur, for example... Figure 2 Lane #2 in the network may fail. When the link failure is short-lived, such as a brief interruption in a link, the entire group to which that link belongs will be disconnected, causing service interruptions within the group. To ensure normal service operation, the group needs to maintain flow. However, group flow maintenance typically involves a series of processes, which can lead to prolonged service disruptions.

[0128] Therefore, how to shorten the time required for the link group to process data when a link in the group fails is a technical problem that urgently needs to be solved.

[0129] To address the aforementioned technical problems, this application proposes a link processing method 100. In method 100, when a first link experiences a first type of failure, the speed of the normal link (i.e., the second link) is adjusted to be as close as possible to the speed of the first link. This maintains the phase between the normal and failed links during the period of link failure. To ensure uninterrupted service, group flow is typically achieved only after phase alignment. However, this solution maintains the phase during link failure, thereby shortening the time consumed by group flow.

[0130] The network systems to which this application can be applied include: Flexible Ethernet, Ethernet, optical networks, optical transport networks (OTN networks), optical distribution networks (ODN), automatically switched optical networks (ASON), automatically switched transport networks (ASTN), passive optical networks (PON), data center networks (DCN), optical access networks (OAN), synchronous digital hierarchy (SDH), Gigabit-capable PON (GPON), Ethernet passive optical network (EPON), 10-Gigabit-capable symmetric passive optical network (XGS-PON), or wavelength division multiplexing (WDM) networks.

[0131] The following is combined Figure 3 This section will specifically introduce the method 100 provided in the embodiments of this application. Optionally, when Figure 3 The method shown is applied to Figure 1a When the system is shown, Figure 3 The first device in the process can be either the receiver 102 or the transmitter 101, when Figure 3 The method shown is applied to Figure 1b When the system is shown, Figure 3 The first device in the process can be a FlexE Shim or a FlexE Shim as... Figure 3 One module of the first device in the middle, when Figure 3 The method shown is applied to Figure 2 When the system is shown, Figure 3 The first device in the process can be a transmitter 201 or a receiver 202. Figure 3The method is illustrated using the first device as the execution subject in the interactive illustration, but this application does not limit the execution subject of the interactive illustration. For example, the execution subject of S301-S302 and related implementations can be the first device. Optionally, the first device includes: a virtual switch, a virtual router, a physical switch, a physical router, a network interface card (NIC), a firewall, a repeater, a hub, a bridge, a gateway, a packet transmission network device, or an optical transmission network device. The execution subject of S301-S302 and related implementations can also be a chip, chip system, or processor that supports the first device in implementing the method, or it can be a logic module or software that can implement all or part of the functions of the first device. The first device in S301-S302 and related implementations can also be replaced by a chip, chip system, or processor that supports the first device in implementing the method, or it can be replaced by a logic module or software that can implement all or part of the controller functions.

[0132] like Figure 3 As shown, the method 100 provided in this application embodiment includes the following steps:

[0133] S301. When a first fault occurs in the first link, the first device obtains the type of the first fault;

[0134] It should be noted that the term "link" in this application is an exemplary designation and can be replaced with any possible designation, such as channel, path, line, interface, or transmission path. Taking Figure 1 as an example, the first link could be link #0 or link #2, etc. Figure 2 For example, optionally, the transmitting end PHY#0, lane#0, lane#1, and the receiving end PHY#0 can together form one or more links. For example, the receiving end PHY#0 can form a link; for example, the transmitting end PHY#0, lane#0, lane#1, and the receiving end PHY#0 as a whole can form a link. Optionally, a link can include one or more PHYs.

[0135] Optionally, in this application, the link can be an interface used for transmitting data or information, or it can be a path for transmitting data or information via optical fiber, optical cable, or copper wire, or it can be a logical channel. The link may include one or more PHYs, for example, it may include 50GBASE-R PHYs, 100GBASE-R PHYs, 200GBASE-R PHYs, or 400GBASE-R PHYs.

[0136] As mentioned above, this application can be applied to the system shown in Figure 1 and can also be used for... Figure 2The system shown is typically applied in Flexible Ethernet. Accordingly, in one optional implementation, the first link is one or more channels of Flexible Ethernet. This implementation is an example of the application of this solution in Flexible Ethernet. In this example, if any one or more links bound in a FlexE group fail, this solution can shorten the FlexE group's throughput time, or in other words, shorten the time required to restore the FlexE group's data flow transmission, i.e., shorten the FlexE shim throughput time, thereby shortening the service loss time.

[0137] First, we will introduce the "fault", the "type of the first fault" and the method of judgment in this application.

[0138] Optionally, the term "fault" in this application is an exemplary designation and can be replaced with any possible designation, such as exception, interruption, link down, disconnection, or disconnection. For example, a first fault in the first link in this application could be signal loss, inability to implement block lock or alignment lock, high bit error rate, or causing the physical coding sublayer (PCS) status to be false. Alternatively, it could be due to a fault in the interface, chip, logic module, or device related to the first link, or a fault in the operating environment such as the network, causing the link to be unable to transmit information or data normally, or causing the task executed on the first link to malfunction. For example, a fault in this application could be a partial fault of the link, such as only the PHY of the first device malfunctioning, or it could be a complete fault of the link.

[0139] Optionally, if one or more PHYs in a FlexE Group fail, the remote PHY failure bit is set to 1 in the 50G FlexE instance or the first 100G FlexE instance carried on that PHY. Optionally, the remote PHY failure bit can be set to 1 within the FlexE overhead frame.

[0140] Optionally, if one or more FlexE instances fail to achieve overhead frame locking or overhead multi-frame locking, if there are inconsistencies between the FlexE mappings, FlexE instance numbers, or FlexE group numbers received by different FlexE instances in the group, or if the offset between FlexE instances from different PHYs exceeds the provided de-offset buffer, this can also be considered a link failure or a network failure. Optionally, in this case, all FlexE clients can continuously transmit the Ethernet local fault ordered set at the FlexE client rate.

[0141] Optionally, the aforementioned fault can be a local fault (LF) or a remote fault (RF). A local fault indicates that the local device encountered a problem while attempting to establish a link, such as being unable to communicate normally with the peer device. For example, the transmitting end cannot communicate with the first device. When the local device's PCS fails to recognize a specific synchronization header, it will send a local fault sequence. A remote fault, on the other hand, indicates that the peer device encountered a problem while attempting to establish a link; that is, the local device receives a remote fault sequence sent by the peer device, indicating that the peer device failed to establish a link normally.

[0142] Optionally, the first device may mistake the LF or RF sent to a single FlexE Client of the first link for the LF or RF of the first link, thereby causing the first link to fail.

[0143] To distinguish the type of the first fault, this application provides several optional examples:

[0144] Example 1

[0145] Optionally, the first device can distinguish the type of the first fault based on the duration of the fault.

[0146] Optionally, if the duration of the first link failure is less than the second threshold, the first link failure is classified as type one; if the duration of the first link failure is not less than the second threshold, the first link failure is classified as type two. For example, starting from the moment the first link experiences its first failure, if after 10H frames the first link still fails to establish a connection or fails to establish a connection successfully, the first link failure is considered to be type two; if within 10H frames the first link establishes a connection or successfully establishes a connection, the first link failure is considered to be type one.

[0147] Example 2

[0148] Optionally, the first device can distinguish the type of the first fault based on the historical status of the first link or the link group to which the first link belongs.

[0149] Optionally, the aforementioned historical status includes: whether the first link is in the first state, and the status information of the first link.

[0150] It should be noted that the term "first state" in this application is an exemplary designation and can be replaced with any possible designation, such as an isolation state. Optionally, the first state indicates that the services running on the first link are isolated from the services running on the links in the first link group that have not experienced a failure, where "isolation" means no interference or influence between them; or the first state indicates that the links in the first link group that have not experienced a failure remain connected; or the first state indicates the isolation of the first link from the links in the first link group that have not experienced a failure; or the first state indicates the isolation of abnormal services on the first link from normal services on the links in the first link group that have not experienced a failure. It is understood that the first state can isolate the first link (the link that has experienced a failure) from the links that have not experienced a failure, thereby ensuring that the services on the links that have not experienced a failure are not affected, and preventing the services on the links that have not experienced a failure in the link group from being damaged due to the failure of the first link. For example, the first device can isolate links in the second link group that experience the second type of fault by controlling the scheduling of the outgoing links. For instance, the bitstream on links that do not experience the second type of fault is a normal bitstream, while the bitstream on links that experience the second type of fault is completely replaced with a local fault. This bitstream replacement prevents normal service data from being transmitted through faulty links, thus avoiding damage to normal services.

[0151] Optionally, when the first link is in the first state, the first fault of the first link is considered to be of the second type; when the first link is not in the first state, the first fault of the first link is considered to be of the first type.

[0152] Optionally, if the status information of the first link indicates that the duration of the link down exceeds a second threshold, for example, exceeding 1.2 ohms, then the failure of the first link is considered to be of the second type. If the status information of the first link indicates that the duration of the link down does not exceed the second threshold, then the failure of the first link is considered to be of the first type. This method can be combined with Example 1, but there can also be some distinctions between the two. For example, in this method, the type of failure can be determined directly by checking the historical status, while in Example 1, the type of failure is determined by determining whether the first link is re-established after exceeding the second threshold.

[0153] When the first link experiences its first failure, the following implementation method can be adopted to avoid the failure affecting normal services:

[0154] In one alternative implementation, when the first fault is of the first type and the second link is not faulty, the status information of the second link indicates that the first link is in a connected state.

[0155] Based on this implementation method, when the first link experiences a first type of failure, the second link can be controlled to maintain the connection, that is, the links in the first link group that have not experienced a failure can be controlled to maintain the connection. As a result, the services on the links that have not experienced a failure can operate normally. In other words, in this solution, the services running on the links that have not experienced a failure will not be damaged due to the failure of the first link. This solution can reduce the scope of service damage caused by the failure of the first link, or reduce the time of service damage.

[0156] Alternatively, to keep the second link connected, group link down can be omitted, or the normal connection of other links can be controlled through egress scheduling, such as maintaining the egress scheduling of the second link, that is, the egress of the second link can send or receive data normally.

[0157] In one alternative implementation, the first link is the link with the last phase order in the first link group.

[0158] Based on the above implementation, when the first link is the last link in the first link group in terms of phase order, it can be understood that the phase order of the second link in the first link group is earlier than that of the first link. At this time, by adjusting the speed of the second link, so that the speed of the second link is as consistent as possible with the speed of the first link, the phase of the second link relative to the first link can remain unchanged.

[0159] Optionally, different links in the first link group may have phase ordering. Whether the first link is the last link in phase order within the first link group can be determined using one or more of the following methods: when the buffer level of the first link in the first link group is the lowest, then the first link is considered the last link in phase order within the first link group. It should be noted that when using buffers, they are generally requested from bottom to top. Figure 4 As shown, the buffer consists of multiple blocks, and the block size is called the "waterline". Figure 4 As shown, in the link group consisting of PHY#0, PHY#2, PHY#4, and PHY#6, PHY#2 has the smallest buffer block, meaning its waterline is the lowest. Therefore, PHY#2 is considered the link with the last phase order in this link group. Within one cycle, when the OH of the first link in the first link group arrives last, the first link is considered the link with the last phase order in that first link group. Figure 4As shown, in the link group consisting of PHY#0, PHY#2, PHY#4, and PHY#6, if the oh signal of PHY#2 arrives last within a period, then PHY#2 is considered the link with the last phase sequence in that link group. For example, when all the overhead multiframes (OMFs) of all PHYs in the first link group transition in one direction, the PHY whose OMF transitions last is considered the link with the last phase sequence in that first link group.

[0160] S302. When the type of the first fault is type 1 and the second link does not have a fault, adjust the speed of the second link to the first speed.

[0161] Wherein, the first speed is less than the speed of the second link, the difference between the first speed and the speed of the first link is less than a first threshold, the duration of the first type of fault is less than a second threshold, and the first link and the second link are in a first link group.

[0162] It should be noted that the speed of the second link is an exemplary term and can be replaced with any possible term, such as the speed of scheduling the second link, the rate of scheduling the second link, the rate of the second link's output, the speed of the second link's output, the data transmission speed of the second link, or the data transmission rate of the second link. Optionally, by controlling the speed of the second link, the speed of the second link's output can be controlled, for example, the speed of the second link's PHY interface can be controlled, or the data transmission speed of the second link can be controlled.

[0163] Optionally, the second link is one or more channels of Flexible Ethernet, and optionally, each link in the first link group is one or more channels of Flexible Ethernet.

[0164] Optionally, step S302 can be replaced by: when the type of the first fault is the first type, and the second link is not faulty and is not in the fault recovery state, the first device adjusts the speed of the second link to the first speed, or sets the speed of the second link to the first speed, or sets the speed of any link in the first link group to the first speed, or sets the speed of the link in the first link group that is not faulty to the first speed.

[0165] Optionally, "the second link has not failed" can mean that the second link has not experienced a first type of failure and no second type of failure. This is a typical scenario of this application, but this application does not limit it. For example, "the second link has not failed" can also mean that the second link has not experienced a first type of failure, or the second link has not experienced a second type of failure, or the second link is normally connected.

[0166] It should be noted that when a link fails, the link is in a "fault recovery state" during the period from when the link is re-established, which can also be called the filtering period or the re-establishment phase.

[0167] It should be noted that the phrase "the first link and the second link are in the first link group" could mean that the first link and the second link are bound to the first link group. In this application, "bound" is an exemplary term and can be replaced with any possible term, such as bundle, merge, or link aggregation.

[0168] Alternatively, the first link and the second link can be bound to the first link group in one or more of the following ways:

[0169] Method 1

[0170] Optionally, when the first link or the second link is located in a data center network, the first link and the second link can be bound to a first link group through network multi-link bonding technology. For example, when the first link and the second link are physical links, the first link, the second link, and other possible links can be combined into a logical link to improve network bandwidth and reliability.

[0171] Optionally, to combine the first link, the second link, and other possible links into a single logical link, specific protocols and technologies can be used, such as Multilink-PPP (MLPPP) protocols, and either manual configuration or automatic protocols. Manual configuration requires network administrators to manually configure the parameters and load distribution for each link. Automatic protocols, such as the Link Aggregation Control Protocol (LACP), allow network devices to automatically negotiate and distribute the load.

[0172] Method 2

[0173] Optionally, when the first and second links are located in an optical network, they can be bound together using link bonding. Link bonding is a fundamental concept in the Generalized Multiprotocol Label Switching (GMPLS) control plane. The first and second links are bonded when they begin and end at the same pair of adjacent nodes, or when they have the same characteristics and attributes defined by the routing protocol, such as the same link type (point-to-point or multiplexed access), the same traffic engineering parameters (e.g., administrative costs), or when they have maximum bandwidth or maximum allocable bandwidth.

[0174] Method 3

[0175] Optionally, when the first and second links are located on Ethernet, they can be bound together using link aggregation. Link aggregation, also known as port aggregation, port bonding, Ethernet bonding, or port binding, is a technique for binding multiple physical links (interfaces) into a single logical link. An aggregation group (link group) can be created first, and the physical interfaces of the first and second links can be bound to this group, thus achieving the binding of the first and second links.

[0176] Method 4

[0177] Optionally, when the first link and the second link are located on Flexible Ethernet, the method of link bonding can be referred to the technical terminology section of this application, and will not be repeated here.

[0178] In one alternative implementation, the first speed is equal to the speed of the first link.

[0179] Based on the above implementation method, phase preservation is achieved by controlling the speed of the second link to be consistent with that of the first link, thereby shortening the time consumed by group flow.

[0180] Optionally, the first speed is the reference speed for establishing the link.

[0181] It should be noted that the so-called baseline speed is the speed of the link before acceleration. When the link needs to be accelerated, it is accelerated based on this baseline speed. For example, in Flexible Ethernet, the baseline speed is the physical interface speed (PHYrate). When acceleration is required, it is usually accelerated based on the PHYrate. For example, the accelerated speed can be PHYrate + 50ppm.

[0182] For example, in Flexible Ethernet, when the first link fails, the speed of the first link is usually set to the first speed, i.e., the PHY rate. At this time, the speed of the second link is also set to the first speed, i.e., the PHY rate, so as to ensure that the speed of the second link is consistent with the speed of the first link.

[0183] To adjust the speed of the second link to the first speed, the following method can be used:

[0184] In one alternative implementation, the first device sends a first message to a first interface, the first message being used to instruct the first interface to adjust the speed of the second link to the first speed, the first interface being the interface of the second link.

[0185] Based on the above method, the first device adjusts the speed of the second link by sending a first message control interface so that the speed of the second link is as consistent as possible with the speed of the first link, thereby achieving phase maintenance.

[0186] Optionally, the first interface can be the interface of the first device, and "the first device sends a first message to the first interface" can be the CPU of the first device sending a first message to the PHY interface of the first device.

[0187] Optionally, the first message can also be used to instruct the first link group to enter a second state, where the second state indicates that the first link group will rapidly process data. The first interface will adjust its exit speed to a first speed according to the instruction of the first message, that is, by adjusting the exit speed, it achieves "adjusting the speed of the second link to the first speed".

[0188] Optionally, step S302 provides a state of the second link and the corresponding speed processing method. Several examples are given below to illustrate in detail how the first device controls the second link:

[0189] In one example, the first device can adjust the speed of a first link group at the link group level. For instance, during the period from the occurrence of a first link failure to the re-establishment of the first link, the first device can set the speed of all links in the first link group to a first speed, such as the speed of the first link itself. Correspondingly, during the period from the occurrence of a first link failure to the re-establishment of the first link, the speed of the second link is the first speed.

[0190] In yet another example, the first device can adjust the speed of links in a first link group at the link level. For instance, the first device can adjust the speed of a second link based on its status, specifically in the following ways:

[0191] like Figure 5a As shown, if the second link does not experience a fault or is not in a fault recovery state during the period from the occurrence of the first fault in the first link to the establishment of the first link, then it is not necessary to reduce the speed of the second link, for example, it is not necessary to adjust the speed of the second link to the first speed.

[0192] like Figure 5b As shown, when the second link fails before the first link fails, and when the second link is re-established after the first link is re-established, there is no need to reduce the speed of the second link.

[0193] like Figure 5cAs shown, if the second link fails before the first link fails, and the second link is established before the first link is established, then when the first link fails, there is no need to slow down the second link; similarly, when the second link is established, there is no need to accelerate it. It should be noted that when the second link is established, it is generally necessary to accelerate it. However, because the first link has experienced a type-one fault, phase maintenance is required to prevent acceleration of the second link.

[0194] like Figure 5d As shown, if the second link fails after the first link fails, and the second link is established after the first link is established, then the second link needs to be slowed down when the first link fails.

[0195] like Figure 5e As shown, if the second link fails after the first link fails but is established before the first link is established, then the second link needs to be slowed down when the first link fails, and it does not need to be accelerated when the second link is established.

[0196] Please see Figure 6 , Figure 6 This illustrates one possible, non-limiting, execution order of the process steps or operations in this application, specifically:

[0197] First, when the first link experiences its first failure, the following steps need to be performed before the first link is re-established:

[0198] Preparing to establish a blockchain involves attempting to restore the first link due to its failure. This process, or attempting to rebuild the blockchain using FlexE linkup, involves trying to restore the first link. At this point, the first link has either not yet been established or has been successfully established.

[0199] Locking, optionally, includes overhead locking or multiframe locking.

[0200] Speed ​​adjustment, that is, to make the speed of the non-faulty links in the first link group as consistent as possible with the speed of the first link, for example, through step S302 and its possible implementation.

[0201] It should be noted that this application does not restrict the execution order of speed adjustment, locking, and chain preparation. For example, speed adjustment can be performed first, followed by locking or chain preparation, or locking or chain preparation can be performed first, followed by speed adjustment.

[0202] also, Figure 6An optional implementation method not shown in the figure is as follows: before the establishment of the first link, the calendar information of the first link group is the first information, which includes: the domain segment information or the mapping relationship between time slots and ports in the overhead frame when the first link experiences the first failure.

[0203] Based on the above implementation, after the first link fails and before the first link is re-established, the calendar information is always the same as the calendar information at the time of the first link failure. Therefore, during the period from the first link failure to the re-establishment of the first link, the first device keeps the calendar information of the first link group unchanged. This shortens the time required to refresh the calendar information, thereby reducing the time consumed for group flow and minimizing the time of service disruption on the group.

[0204] Optionally, the aforementioned overhead frame is an overhead frame in the first link group, for example, it can be an overhead frame of the first link. Taking the first link as a FlexE PHY as an example, the domain segment information of the overhead frame includes: control characters and "O Code" characters, etc. During the information transmission process, the two connected FlexE interfaces determine the first FlexE overhead frame by matching the control character containing "0x4B" with the "O Code" character containing "0x5", thereby establishing a management information channel between the two, realizing the pre-negotiation and handshake of configuration information between the two connected interfaces.

[0205] Optionally, the aforementioned "mapping relationship between time slots and ports" can be a mapping relationship between time slots and ports in the first link group. This mapping relationship includes: a mapping relationship between internal ports and time slots or a mapping relationship between external ports and time slots. The internal ports can be ports within the first link group, such as... Figure 2 In China, for Figure 2 For the link group in the first link group, the internal port can be the transmitting end PHY#0 or the receiving end PHY#0, etc., and the external port can be a port outside the first link group or a port outside the first device.

[0206] For example, the above implementation method is applied to FlexE. As described in technical terminology, FlexE Calendar is the mechanism for FlexE Shim to handle mapping and demapping. Its specific implementation mechanism involves constructing a calendar of size 20*n 64 / 66b blocks, where n is the number of bound Ethernet physical ports. Each 64 / 66b block represents a 5GHz time slot. On the multiplexing side, services with different MAC rates are packed into the corresponding number of 64 / 66b blocks according to their multiples of 5GHz. Every 20 64 / 66b blocks constitute a sub-calendar, and the 20*n calendars are distributed across n sub-calendars. For each sub-calendar, an overhead frame (overhead frame) is added every 20*1023 64 / 66b blocks to store the relevant mapping relationship, which is the domain segment information or the mapping relationship between time slots and ports in the overhead frame. Each sub-calendar is transmitted within a single 100g Ethernet PHY. On the demultiplexing side, n sub-calendars form a 20*n calendar, from which the corresponding customer services are extracted from the corresponding number of 64 / 66b blocks according to the mapping relationship stored in the overhead.

[0207] Optionally, the first device does not refresh or update the calendar information according to the information maintained in the past, that is, the first information is consistent with the information maintained in the past before the failure of the first link, that is, it is consistent with the first information, or the first device does not write the new calendar information into its own stored calendar information after receiving new calendar information.

[0208] Second, after the first link is established but before the group begins flow, there are several possible steps. Specifically, the following implementation methods can be adopted:

[0209] In one optional implementation, after the first link is established, if the second information is different from the first information, the calendar information is updated based on the second information. The second information includes: the domain segment information or the mapping relationship between time slots and ports in the overhead frame after the first link is established; if the second information is the same as the first information, the calendar information is the first information.

[0210] Based on the above implementation, when the second information is different from the first information, that is, when it is different from the calendar information received before the first link failure, updating the calendar information based on the second information can ensure that the domain segment information or time slot and port in the overhead frame saved by the first device are consistent with those sent by the sending end, which is beneficial to the stability of the link connection. When the second information is different from the first information, the calendar information is still consistent with the first information, which can shorten the time used to refresh the first information, that is, the calendar information, thereby shortening the time required for group flow and reducing the damage time of services executed on the group.

[0211] It should be noted that the above statement "updating the calendar information based on the second information" is an exemplary statement and can be replaced with any possible statement, such as writing the second information into the calendar information or adjusting the saved calendar information based on the second information. Optionally, regardless of which statement is used, the mapping relationship between the domain segment information or time slot and port in the overhead frame of the final calendar information needs to match the mapping relationship between the domain segment information or time slot and port in the overhead frame of the second information.

[0212] by Figure 2 For example, the first device can be a receiver 202, while the second information is sent by a sender 201. Calendar information is stored or written within the first device, such as the mapping relationship between time slots and ports. After the first link is established, the first device receives the second information from the first link group. At this point, the first device needs to determine whether the calendar information needs to be updated based on the second information. The above implementation provides a method for this determination: the second information is compared to the information received from the first link group before the first link failure. If the second information is the same as the information received from the first link group before the first link failure, the calendar information remains consistent with the first information, meaning it is not updated based on the second information. If the second information is different from the information received from the first link group before the first link failure, the first device will update the calendar information based on the second information.

[0213] Optionally, the first device can initiate a "fast wake-up" mode. Low-power Idle States (LPI) control characters used during fast wake-up can be assigned to the 64 / 66b payload block location of each FlexEClient based on calendar information.

[0214] When the first fault is of the second type, that is, the duration of the first fault is greater than the second threshold, and the first link group is switched to the second link group, the first device can delete the third information of the first link. For details, please refer to the following method 200, which will not be repeated here.

[0215] Through the aforementioned method 100 and its possible implementations, when a first type of fault occurs, i.e., a brief interruption, this application, on the one hand, ensures uninterrupted normal service. In method 100, even if the first link experiences a first type of fault, i.e., a brief interruption, the links within the link group to which the first link belongs remain connected, thus allowing services on the uninterrupted links to continue operating normally. Furthermore, during the first link fault period, i.e., from the onset of the fault to the re-establishment of the first link, by adjusting the speed of the second link, i.e., the uninterrupted links within the first link group, to keep it as consistent as possible with the speed of the first link, phase preservation can be achieved, thus enabling lossless recovery of normal services. On the other hand, this application can shorten the time of service disruption. Phase preservation in this application can also shorten the time required for group flow. Furthermore, during the first link fault period, this application keeps the calendar information in the first device unchanged, shortening the time for calendar information refresh. After the first link fault ends, when the received second information is unchanged from the previously received first information, this application does not update the calendar information, further shortening the time for calendar information refresh. Phase alignment and calendar information refresh are usually necessary steps for link group flow. This application can shorten the time required for link group flow by maintaining phase and shortening the time for calendar information refresh, thereby shortening the time that services running in the link group are damaged.

[0216] To shorten the time of service disruption, this application proposes a link processing method 200. In method 200, when a second type of fault occurs in the first link of a first link group, and the transmission switches from the first link group to the second link group, the entire link group needs to be re-established because the link group usually experiences a brief interruption during the switch. Method 200 removes the third information of the first link, so that the first link is no longer in the first state. That is, the services running on the first link are no longer isolated from the services running on the links in the first link group that have not experienced a fault. This allows the first link to establish a normal connection, and all the links in the group that have not experienced a fault can establish a normal connection. Therefore, the services can be fully restored, thereby shortening the time of service disruption.

[0217] The following is combined Figure 7 This paper will specifically introduce the method 200 provided in the embodiments of this application. It should be noted that... Figure 7 The method is illustrated by taking the second device as the execution subject of the interaction, but this application does not limit the execution subject of the interaction.

[0218] like Figure 7 As shown, the method 200 provided in this application embodiment includes the following steps:

[0219] S701. When a first fault occurs in the first link, the second device obtains the type of the first fault.

[0220] It should be noted that step S701 can be referred to the description of step S301 in method 100, and will not be repeated here.

[0221] It should be noted that the first device in method 100 and the second device in method 200 can be the same device or different devices.

[0222] S702. When the type of the first fault is the second type and the first link group is switched to the second link group, the second device deletes the third information of the first link.

[0223] The third piece of information is related to the first state, which indicates that the services running on the first link are isolated from the services running on the links in the first link group that have not experienced a failure.

[0224] Optionally, the second link group is a backup link group when any link in the first link group fails. When the first link is in the first state, the services running on the first link are isolated from the services running on the links in the first link group that have not failed.

[0225] It should be noted that "first link group" in this application is an exemplary name and can be replaced with any possible name, such as primary path, preferred path, default path, primary link, preferred link, or default link, etc. Similarly, "second link group" in this application is an exemplary name and can be replaced with any possible name, such as backup path, alternative link group, protection path, backup link, alternative link, or protection link, etc.

[0226] It should be noted that "second type" in this application is an exemplary designation and can be replaced with any possible designation, such as continuous fault, continuous Ethernet local fault, or continuous Ethernet remote fault. In this application, the first fault is divided into two types, such as... Figure 8 As shown, black stars represent the first type of fault, whose duration is less than the first threshold, and white stars represent the second type of fault, whose duration is not less than the first threshold.

[0227] It should be noted that the description of the first state in step S702 can be found in the description of the first state in method 100.

[0228] Optionally, please refer to Figure 9The first and second link groups form a ring network for link protection. If the first link group fails, the system can quickly switch to the second link group, enabling rapid data link failover and resolving prolonged service interruptions caused by link failures. This process of switching from the first link group to the second link group is also known as primary / backup failover.

[0229] Optionally, the second link group may overlap with all or part of the links in the first link group, such as... Figure 10 As shown, the PHY of the receiving end of the second link group is the same as that of the receiving end of the first link group. For example, they can share receiving end PHY#0, receiving end PHY#2, or receiving end PHY#4. All or some links in the second link group may not overlap with those in the first link group; this application does not impose any restrictions on this.

[0230] Optionally, taking the faulty link, i.e., the link where PHY#2 is located, as an example, the link where PHY#2 is located is within the first link group. At this time, the link where PHY#2 is located will be in the first state. When the link group used for transmitting information is switched from the first link group to the second link group, the first state of the link where PHY#2 is located will be synchronized to the second link group through the interface of the second link group. That is, after the link group switch, the link where PHY#2 is located in the second link group will still be in the first state. When the link group used for transmitting information is switched from the first link group to the second link group, for example, when CDR switchover is initiated to switch the first link group to the second link group, the second link group will be temporarily interrupted and needs to be re-established. At this time, releasing the first state can prevent the link where PHY#2 is located in the second link group from being isolated and allow normal link establishment.

[0231] In one alternative implementation, the third information includes: historical information indicating the first fault, a link isolation signal, or an anomaly source signal.

[0232] Based on the above implementation, by deleting historical information indicating the first fault, link isolation signals, or abnormal source signals, the second device can release the signals used to isolate the second link and the signals that set the first link to the first state. That is, the first link can no longer be in the first state, allowing the first link to be re-established normally and the services running on the first link to resume, thereby shortening the service time.

[0233] In one alternative implementation, after the second link group begins establishing links, the second device sets the links in the second link group that experience the second type of fault to the first state.

[0234] It should be noted that the initiation of link establishment in the second link group does not usually mean that the links in the second link group have already been established, but rather that the second link group is preparing to establish a link or attempting to establish a link. At this time, by isolating the links in the second link group that have the second type of fault, the links that do not have the second type of fault can establish a link.

[0235] Understandably, when the data transmission path switches from the first link group to the second link group, the second link group will be temporarily interrupted and needs to re-establish the link. Releasing the first state of the faulty links at this time allows them to re-establish the link normally. However, some links may still fail to establish a link even after switching link groups and releasing the first state. These links may have faults, such as physical port connection failures at the receiving end, causing them to fail to establish a link normally. These faulty links will affect the link group's link establishment. The above implementation method can solve this problem. When the link group starts establishing a link, links experiencing a second type of fault are set to the first state. For example, links that have been unable to establish a link for a long time after switching are set to the first state. This isolates the services on links experiencing a second type of fault from the services on normal links. Links without this type of fault can then successfully establish a link, allowing services on these links to operate normally, thereby shortening the time that services on normal links are damaged.

[0236] Optionally, the second device can determine whether a link in the second link group has experienced a second type of fault by: starting from the moment the first link in the second link group is established, if a link fails to establish a connection after exceeding a threshold, then a second type of fault is considered to exist. Figure 11 For example, suppose the first link to establish a link in the second link group is PHY#2. If there is still no link established 1.2OH frames after the time when PHY#2 established a link, it can be regarded as a link with a second type of failure. This link is considered to be a link timeout link.

[0237] Using the aforementioned method 200 and its possible implementations, when a second type of fault occurs, i.e., a prolonged link interruption, a link group switch will be performed, switching from the primary link group (first link group) to the backup link group (second link group). During link group switching, the link group typically experiences a brief interruption, requiring the entire link group to be re-established. This application, by releasing the first state of the first link, enables the first link to establish a normal connection, and the fault-free links within the group can also establish connections normally, thus allowing for full service recovery and shortening the time of service loss. Furthermore, for links that remain faulty after the switch, this application will isolate them, setting them to the first state to prevent these links from affecting the establishment of the entire link group, thereby shortening the group's throughput time and reducing the time of service loss.

[0238] The embodiments of this application have been described above from the perspective of methodology. The communication devices in the embodiments of this application will be introduced below from the perspective of specific device implementation.

[0239] Please see Figure 12 This application provides a schematic diagram of a communication device 1200. Optionally, the communication device 1200 can be... Figure 1a The receiving end 102 or the transmitting end 101 in the middle, the communication device 1200 can be Figure 1b FlexEShim in, or Figure 1b The FlexE Shim is a module of the communication device 1200, which can be... Figure 2 The communication device 1200 can be a transmitter 201 and a receiver 202. Figure 3 The first device or communication device 1200 in the middle can be Figure 7 The second device in the communication device 1200 includes at least a processing unit 1201 and a transceiver unit 1202.

[0240] As an example, the communication device 1200 can perform the function of the first device in the method 100 described above, and thus can also achieve the beneficial effects of the method 100 described above.

[0241] The transceiver unit 1202 is used to obtain the type of the first fault when the first link experiences a first fault; the processing unit 1201 is used to adjust the speed of the second link to a first speed when the type of the first fault is a first type and the second link does not experience a fault, the first speed is less than the speed of the second link, the difference between the first speed and the speed of the first link is less than a first threshold, the duration of the first type of fault is less than a second threshold, and the first link and the second link are in a first link group.

[0242] In one alternative implementation, the first speed is equal to the speed of the first link.

[0243] In one alternative implementation, the transceiver unit 1202 is further configured to: send a first message to a first interface, the first message being used to instruct the first interface to adjust the speed of the second link to the first speed, the first interface being the interface of the second link.

[0244] In one alternative implementation, the first link is the link with the last phase order in the first link group.

[0245] In one alternative implementation, when the first fault is of the first type and the second link is not faulty, the status information of the second link indicates that the first link is in a connected state.

[0246] In one alternative implementation, before the first link is established, the calendar information of the first link group is the first information, which includes: the domain segment information or the mapping relationship between time slots and ports in the overhead frame when the first link experiences the first failure.

[0247] In one optional implementation, the processing unit 1201 is further configured to: after the first link is established, if the second information is different from the first information, update the calendar information based on the second information, wherein the second information includes: the domain segment information or the mapping relationship between time slots and ports in the overhead frame after the first link is established; if the second information is the same as the first information, the calendar information is the first information.

[0248] In an optional implementation, the processing unit 1201 is further configured to: when the type of the first fault is the second type, the duration of the second type of fault is not less than the second threshold; when the first link group is switched to the second link group, delete the third information of the first link, the third information being related to the first state, the first state indicating that the services running on the first link are isolated from the services running on the links in the first link group that have not experienced a fault.

[0249] In one alternative implementation, the third information includes: historical information indicating the first fault, a link isolation signal, or an anomaly source signal.

[0250] In an optional implementation, the processing unit 1201 is further configured to: set the links in the second link group that experience the second type of fault to the first state after the second link group begins to establish a link.

[0251] In one alternative implementation, the first link is one or more channels of a flexible Ethernet.

[0252] As another example, the communication device 1200 can perform the function of the second device in the method 200 described above, and thus can also achieve the beneficial effects of the method 200 described above.

[0253] Specifically, the transceiver unit 1202 is used to obtain the type of the first fault when a first fault occurs in the first link;

[0254] The processing unit 1201 is configured to, when the type of the first fault is the second type and the duration of the second type of fault is not less than the second threshold, delete the third information of the first link when the first link group is switched to the second link group. The third information is related to the first state, which indicates that the services running on the first link are isolated from the services running on the links in the first link group that have not experienced a fault.

[0255] In one alternative implementation, the third information includes: historical information indicating the first fault, a link isolation signal, or an anomaly source signal.

[0256] In an optional implementation, the processing unit 1201 is further configured to: set the links in the second link group that experience the second type of fault to the first state after the second link group begins to establish a link.

[0257] In one alternative implementation, the first link is one or more channels of a flexible Ethernet.

[0258] The processing unit 1201 is specifically used to: release relevant information and / or relevant signals of the first state, wherein the relevant information includes: historical states related to the fault, and the relevant signals include: link isolation signals or abnormal source signals.

[0259] In an alternative implementation, the processing unit 1201 is further configured to: set the links in the fourth link group that have experienced the second type of fault to the second state after the fourth link group begins to establish a link.

[0260] In one alternative implementation, the third link and / or the fourth link is one or more physical channels of a flexible Ethernet network.

[0261] It should be noted that the information execution process of the unit of the above-mentioned communication device 1200 can be specifically described in the method embodiment shown above in this application, and will not be repeated here.

[0262] Please see Figure 13 , Figure 13 The schematic diagram of the communication device involved in the above embodiments provided for the embodiments of this application may optionally include... Figure 13 The communication device 1300 in the middle can be Figure 1aThe receiving end 102 or the transmitting end 101 in the middle, the communication device 1300 can be Figure 1b FlexE Shim, or Figure 1b The FlexE Shim in the text is a module of the communication device 1300, or Figure 1b The FlexE Shim is a module of the communication device 1300, which can be... Figure 2 The communication device 1300 can be a transmitter 201 and a receiver 202. Figure 3 The first device or communication device 1300 in the middle can be Figure 7 The second device in the system. The structure of the communication device 1300 can be referenced. Figure 13 The structure shown.

[0263] The communication device includes at least one processor 1301, at least one communication port 1302, at least one memory 1303, and one or more buses 1304. The processor 1301, memory 1303, and communication port 1302 are connected, for example, via a bus. In this embodiment, the connection may include various interfaces, transmission lines, or buses, etc., and this embodiment is not limited thereto. The bus 1304 is connected to the communication port 1302.

[0264] As an implementation example, Figure 13 The communication device shown is the aforementioned Figure 3 In the case of the first device in the related embodiments, the communication port 1302 is used to obtain the type of the first fault when the first link has a first fault; the processor 1301 is used to adjust the speed of the second link to a first speed when the type of the first fault is a first type and the second link has not had a fault, the first speed is less than the speed of the second link, the difference between the first speed and the speed of the first link is less than a first threshold, the duration of the first type of fault is less than a second threshold, and the first link and the second link are in a first link group.

[0265] As yet another implementation example Figure 13 The communication device shown is the aforementioned Figure 7 In the case of the second device in the related embodiments, the communication port 1302 is used to obtain the type of the first fault when the first link experiences a first fault; the processor 1301 is used to delete the third information of the first link when the first fault is of the second type and the duration of the second type of fault is not less than the second threshold, when the first link group is switched to the second link group, the third information is related to the first state, the first state indicates that the service running on the first link is isolated from the service running on the link in the first link group that has not experienced a fault.

[0266] It should be noted that the aboveFigure 13 The execution process of each device in the communication device shown can be found in the description of the method embodiments shown above in this application, and will not be repeated here.

[0267] The processor 1301 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process data from the software programs, for example, to support the communication device in performing the actions described in the embodiments. The communication device may include a baseband processor and a central processing unit. The baseband processor is mainly used to process communication protocols and communication data, while the central processing unit is mainly used to control the entire first or second device, execute software programs, and process data from the software programs. Figure 13 The processor 1301 can integrate the functions of a baseband processor and a central processing unit. Those skilled in the art will understand that the baseband processor and the central processing unit can also be independent processors interconnected via technologies such as buses. Those skilled in the art will understand that the first or second device can include multiple baseband processors to adapt to different network standards, and the first or second device can include multiple central processing units to enhance its processing capabilities. The various components of the first or second device can be connected via various buses. The baseband processor can also be described as a baseband processing circuit or a baseband processing chip. The central processing unit can also be described as a central processing circuit or a central processing chip. The function of processing communication protocols and communication data can be built into the processor or stored in memory as a software program, with the processor executing the software program to implement the baseband processing function.

[0268] The memory 1303 is primarily used to store software programs and data. The memory 1303 can exist independently or be connected to the processor 1301. Optionally, the memory 1303 can be integrated with the processor 1301, for example, integrated within a single chip. The memory 1303 can store program code that executes the technical solutions of the embodiments of this application, and its execution is controlled by the processor 1301. The various types of computer program code being executed can also be considered as drivers for the processor 1301.

[0269] Figure 13 Only one memory and one processor are shown. In the actual first or second device, there may be multiple processors and multiple memories. Memory may also be called storage medium or storage device, etc. Memory can be a storage element on the same chip as the processor, i.e., an on-chip storage element, or it can be a separate storage element; this application does not limit this.

[0270] Communication port 1302 can be used to support the reception or transmission of radio frequency (RF) signals between the communication device and the terminal. Communication port 1302 can be connected to bus 1304. Communication port 1302 includes a transmitter Tx and a receiver Rx. Specifically, one or more buses 1304 can receive RF signals. The receiver Rx of communication port 1302 is used to receive the RF signals from the antenna, convert the RF signals into digital baseband signals or digital intermediate frequency (IF) signals, and provide the digital baseband signals or IF signals to the processor 1301 so that the processor 1301 can perform further processing on the digital baseband signals or IF signals, such as demodulation and decoding. In addition, the transmitter Tx in communication port 1302 is also used to receive modulated digital baseband signals or IF signals from processor 1301, convert the modulated digital baseband signals or IF signals into RF signals, and transmit the RF signals through one or more buses 1304. Specifically, the receiver Rx can selectively perform one or more stages of downmixing and analog-to-digital conversion on the radio frequency signal to obtain a digital baseband signal or a digital intermediate frequency (IF) signal. The order of the downmixing and IF conversion processes is adjustable. The transmitter Tx can selectively perform one or more stages of upmixing and digital-to-analog conversion on the modulated digital baseband signal or digital IF signal to obtain a radio frequency signal. The order of the upmixing and IF conversion processes is also adjustable. The digital baseband signal and the digital IF signal can be collectively referred to as digital signals.

[0271] A transceiver can also be called a transceiver unit, transceiver, or transceiver device. Optionally, the device in the transceiver unit that performs the receiving function can be considered as the receiving unit, and the device in the transceiver unit that performs the transmitting function can be considered as the transmitting unit. That is, the transceiver unit includes a receiving unit and a transmitting unit. The receiving unit can also be called a receiver, input port, or receiving circuit, and the transmitting unit can be called a transmitter, transmitter, or transmitting circuit, etc.

[0272] It should be noted that, Figure 13 The communication device shown can be used to implement the steps of the first or second device in any of the foregoing method embodiments, and to achieve the corresponding technical effects of the first or second device. Figure 13 The specific implementation of the communication device shown can be referred to the description in any of the foregoing method embodiments, and will not be repeated here.

[0273] This application also provides a computer-readable storage medium storing one or more computer-executable instructions. When the computer-executable instructions are executed by a processor, the processor executes the method described in the possible implementation of the communication device in the foregoing embodiments, wherein the communication device may specifically be the first device or the second device in the foregoing embodiments.

[0274] This application also provides a computer program product (or computer program) that stores one or more computers. When the computer program product is executed by the processor, the processor executes the method of the communication device that may be implemented as described above. The communication device may specifically be the first device or the second device in the foregoing embodiments.

[0275] This application also provides a chip system including a processor for supporting a communication device in implementing the functions involved in the possible implementations of the communication device described above. In one possible design, the chip system may further include a memory for storing necessary program instructions and data for the communication device. The chip system may be composed of chips or may include chips and other discrete devices, wherein the communication device may specifically be the first device or the second device described in the foregoing embodiments.

[0276] Optionally, the chip system includes a flexible Ethernet shim, for example, the FlexE shim in the chip system can be... Figure 1b The FlexE shim in the chip system. For example, the FlexE shim in this chip system can be... Figure 2 The FlexE Shim(TX) or FlexE Shim(RX) in the chip system. For example, the chip system used to support Figure 3 The first device in the process executes method 100 and any possible implementation or design of the method described therein, or the FlexE shim is used to support Figure 7 The second device in the method executes method 200 and the method described in any possible implementation or design.

[0277] This application provides a communication system, which includes a third device and Figure 3 The first device in the system is configured to perform method 100 and any possible implementation or design thereof. Upon receiving a message, the first device forwards the message to the third device via all or part of the first link, or the third device sends the message to the third device via all or part of the first link; or the communication system includes a fourth device and... Figure 7 The second device in the method is used to perform the method 200 and any possible implementation or design of the method. After receiving the message, the second device forwards the message to the fourth device through all or part of the links in the first link, or the fourth device sends the message to the second device through all or part of the links in the first link.

[0278] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.

[0279] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0280] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit 1201, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0281] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the essential contribution of the technical solution of this application, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a server, or a first or second device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0282] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A link processing method, characterized in that, The method includes: When a first failure occurs in the first link, obtain the type of the first failure; When the first fault is of type one and the second link does not fail, the speed of the second link is adjusted to a first speed, the first speed is less than the speed of the second link, the difference between the first speed and the speed of the first link is less than a first threshold, the duration of the first type of fault is less than a second threshold, and the first link and the second link are in a first link group.

2. The link processing method according to claim 1, characterized in that, The first speed is equal to the speed of the first link.

3. The link processing method according to claim 1 or 2, characterized in that, The method further includes: Send a first message to the first interface, the first message being used to instruct the first interface to adjust the speed of the second link to the first speed, the first interface being the interface of the second link.

4. The link processing method according to any one of claims 1 to 3, characterized in that, The first link is the link with the last phase order in the first link group.

5. The link processing method according to any one of claims 1 to 4, characterized in that, When the first fault is of the first type and the second link is not faulty, the status information of the second link indicates that the first link is in a connected state.

6. The link processing method according to any one of claims 1 to 5, characterized in that, Before the first link is established, the calendar information of the first link group is the first information, which includes: the domain segment information or the mapping relationship between time slots and ports in the overhead frame when the first link experiences the first failure.

7. The link processing method according to claim 6, characterized in that, The method further includes: After the first link is established, if the second information is different from the first information, the calendar information is updated based on the second information. The second information includes: the domain segment information or the mapping relationship between time slots and ports in the overhead frame after the first link is established; if the second information is the same as the first information, the calendar information is the first information.

8. The link processing method according to any one of claims 1 to 7, characterized in that, When the type of the first fault is the second type, the duration of the second type of fault is not less than the second threshold, and the method further includes: When the first link group switches to the second link group, the third information of the first link is deleted. The third information is related to the first state, which indicates that the services running on the first link are isolated from the services running on the links in the first link group that have not experienced a failure.

9. The link processing method according to claim 8, characterized in that, The third information includes: historical information indicating the first fault, link isolation signal, or anomaly source signal.

10. The link processing method according to claim 8 or 9, characterized in that, The method further includes: Once the second link group begins establishing a link, the links in the second link group that experience the second type of fault will be set to the first state.

11. The link processing method according to any one of claims 1 to 10, characterized in that, The first link is one or more channels of Flexible Ethernet.

12. A communication device, characterized in that, include: Communication interface and processor; The communication interface and the processor perform the method as described in any one of claims 1 to 11.

13. A computer-readable storage medium, characterized in that, The medium stores instructions that, when executed by a processor, implement the method of any one of claims 1 to 11.

14. A computer program product, characterized in that, Includes instructions that, when executed on a processor, perform the method as described in any one of claims 1 to 11.

15. A chip, characterized in that, It includes at least one processing unit and an interface circuit, the interface circuit being used to provide program instructions or data to the at least one processing unit, the at least one processing unit being used to execute the program instructions to implement the method of any one of claims 1 to 11.

Images