Method and device for configuring a link group

Abstract

The present application provides a method and device for configuring a link group. The method includes: a first device obtains first status information of M links between a source device and a receiving device, where the first status information is used to indicate the status of the differential delay between any two of the M links, and any one of the links is a FlexE or FlexO physical connection link, and M is an integer greater than or equal to 2; the first device obtains first capability information of the receiving device, where the first capability information is used to indicate the first capability of the receiving device to perform differential delay compensation on the M links; the first device divides N links among the M links into a first link group according to the first status information and the first capability information, where N is an integer less than or equal to M and greater than or equal to 2; the first device sends first configuration information to a second device, including information for indicating the first link group. The method provided by the present application can improve the availability and robustness of links in a transport network.

Description

Technical Field

[0001] This application relates to the field of transport networks, and more particularly, to a method and device for configuring a link group. Background Art

[0002] Currently in an Ethernet transport network, generally, through the Link Aggregation Group (LAG) technology, multiple physical connection links (hereinafter referred to as "links") are bound into a logical link to increase bandwidth and improve link availability.

[0003] Specifically, the LAG technology usually binds S physical connection links with the same bandwidth rate R between adjacent devices into a LAG with a bandwidth rate of S*R to achieve a linear increase in bandwidth rate, thereby meeting the demand for bandwidth growth. For user services above the Media Access Control (MAC) layer, the LAG appears as a logical interface. The transmission device can classify the packets from the MAC layer according to information such as the source MAC address and / or destination MAC address, or Virtual Local Area Network (VLAN) tag, etc., to distinguish different services. For example, packets with the same source MAC address and destination MAC address belong to the same service, and multiple services are assigned and constrained to be sent through a specific link of the LAG after being processed by a hash algorithm. Since in the LAG technology, the packets of a service are only sent through one link, for this service, there is no problem of packet out-of-order, and the LAG does not need to compensate for the transmission delay difference of each link. However, it is also precisely because the packets of a service in the LAG technology are only sent through one link, that is, the traffic of a specific service in the service cannot exceed the bandwidth rate R of a single link. Therefore, the LAG cannot reflect the bandwidth rate of S*R for a single service.

[0004] Flexible Ethernet (FlexE) or Flexible Optical Transport Network (FlexO) can form a link aggregation group through link binding and cascading to support parallel transmission across multiple links to carry at least one service. Among them, OTN refers to Optical Transport Network. Since the service is transmitted across links, it is necessary to perform differential delay compensation on the transmission delays of each link to align the services transmitted in parallel on multiple links. The differential delay compensation ability of the receiving end device is subject to certain engineering limitations in practice. If the differential delay of a certain link exceeds the differential delay compensation ability of the receiving end device, the entire link aggregation group will fail. Summary of the Invention

[0005] The present application provides a method and a device for configuring a link group, which can improve the availability and robustness of links in a transport network.

[0006] In a first aspect, a method for configuring a link group is provided, including: a first device obtains first status information of M links between a source device and a receiving device, where the first status information is used to indicate the status of differential delays between any two of the M links, and any one of the M links is a Flexible Ethernet (FlexE) physical connection link or a Flexible Optical Transport Network (FlexO) physical connection link, where M is an integer greater than or equal to 2; the first device obtains first capability information of the receiving device, where the first capability information is used to indicate a first capability of the receiving device to perform differential delay compensation on the M links; the first device divides N links among the M links into a first link group according to the first status information and the first capability information, where N is an integer less than or equal to M and greater than or equal to 2; and the first device sends first configuration information to a second device, where the first configuration information includes information for indicating the first link group.

[0007] It should be understood that the first device is a decision-making device that determines the link group division method, and the second device includes related devices that cooperate with the decision-making device to complete link group configuration.

[0008] It should also be understood that the method for configuring a link group in the first aspect is applied to a situation where the M links cannot be aligned at the receiving device, or in other words, a situation where the first capability of the receiving device to perform differential delay compensation on the M links cannot achieve alignment of the M links.

[0009] For the method for configuring a link group in the first aspect, the first device divides N links among the M links into a first link group according to the status of differential delays of the M links between the source device and the receiving device and the capability of the receiving device to perform differential delay compensation on the M links, thereby avoiding the situation where all M links are unavailable when the differential delays of the M links exceed the differential delay compensation capability of the receiving device, and can improve the availability and robustness of links in the transport network.

[0010] In a possible implementation of the first aspect, the first device is the receiving device, and the second device is the source device. The first device obtains first status information of M links between the source device and the receiving device, including: the first device measures differential delays of the M links to obtain the first status information. The method further includes: the first device performs differential delay compensation on the links in the first link group according to the first configuration information; the first device transmits service data with the second device based on the first link group. In this possible implementation, it is simple and convenient for the receiving device to be the decision-making device to determine the configuration of the link group, and the signaling overhead is small when configuring the link group.

[0011] In a possible implementation of the first aspect, the first device obtains first status information of M links between the source device and the receiving device, including: the first device receives the first status information sent by the receiving device; the first device obtains first capability information of the receiving device, including: the first device receives the first capability information sent by the receiving device.

[0012] Among them, in a possible implementation, the first device is the source device, and the second device is the receiving device. In this possible implementation, with the source device as the decision-making device, the configuration of the link group can be determined by combining relevant information of the service data, such as comprehensive factors like the number of services and / or bandwidth.

[0013] Among them, in another possible implementation, the first device is a management device, and the second device includes the receiving device and / or the source device. In this possible implementation, with the management device as the decision-making device, on the one hand, it can receive relevant information of the source device and the receiving device, and can determine the configuration of the link group by considering comprehensive factors such as the number of services and / or bandwidth; on the other hand, it can avoid the possible computational complexity caused by the source device or the receiving device making decisions, and can reduce the burden on the source device and the receiving device.

[0014] In a possible implementation of the first aspect, among the M links, K upstream devices of the receiving end device have the ability to compensate for delayed transmission, where K is a positive integer, and the K upstream devices include the source end device and / or at least one intermediate device. The intermediate device is located between the source end device and the receiving end device among the M links. The method further includes: the first device obtains second capability information and second status information of each of the K upstream devices. The second capability information is used to indicate the second capability of each upstream device to compensate for delayed transmission on at least one of the M links, and the second status information is used to indicate the current status of each upstream device to compensate for delayed transmission on at least one of the M links; the first device divides N of the M links into a first link group according to the first status information and the first capability information, including: the first device divides the N of the M links into the first link group according to the first status information, the first capability information, the second status information, and the second capability information; the method further includes: the first device determines, according to the first status information, the first capability information, the second status information, and the second capability information, the configuration of the delayed transmission compensation that each upstream device should perform on the corresponding link.

[0015] When the M links cannot be aligned at the receiving end device, the M links cannot form a link group, or in other words, the FlexEGroup or FlexO Group crashes and cannot work. The source end device and the receiving end device of the embodiments of the present application may further include an intermediate device, etc., and all may have the ability of differential delay compensation or delayed transmission compensation. In this possible implementation, each device realizes the compensation of the link group through capability negotiation. When the compensation capabilities of the devices in the FlexE Group or FlexOGroup between the source end device and the receiving end device cannot compensate for the differential delay of each link, by configuring the link group, the source end device only bears the cross-link transmission service data on the links with delay alignment; or through the collaborative compensation of each device, the final M links can be aligned at the receiving end device, which can ensure the operation of the FlexE Group or FlexO Group and improve the utilization rate of the links.

[0016] In a possible implementation of the first aspect, the first device is the receiving device, the second device is the source device, and the first device obtains first status information of M links between the source device and the receiving device, including: the first device measures differential delays of the M links to obtain the first status information; the first device obtains second capability information and second status information of each of the K upstream devices, including: the first device receives the second capability information and the second status information sent by each of the upstream devices; the method further includes: the first device sends second configuration information to at least one of the K upstream devices, and the second configuration information is used to indicate that the at least one upstream device should perform configuration for delay transmission compensation on a corresponding link.

[0017] In a possible implementation of the first aspect, the method further includes: the first device performs differential delay compensation on the links in the first link group that have undergone delay transmission compensation by the at least one upstream device according to the second configuration information according to the first configuration information; the first device transmits service data with the second device based on the first link group.

[0018] In a possible implementation of the first aspect, the first device is the source device, the second device is the receiving device, and the first device obtains first status information of M links between the source device and the receiving device, including: the first device receives the first status information sent by the receiving device; the first device obtains first capability information of the receiving device, including: the first device receives the first capability information sent by the receiving device.

[0019] In a possible implementation of the first aspect, the K upstream devices include the first device, and the method further includes: the first device transmits service data with the second device based on the first link group according to the determined configuration for delay transmission compensation that the first device should perform on a corresponding link.

[0020] In a possible implementation of the first aspect, the K upstream devices include at least one intermediate device, and the first device obtains second capability information and second status information of each of the K upstream devices, including: the first device receives the second capability information and the second status information sent by each of the at least one intermediate devices; the method further includes: the first device sends second configuration information to at least some of the at least one intermediate devices, and the second configuration information is used to indicate that the at least some intermediate devices should perform configuration for delay transmission compensation on a corresponding link.

[0021] In a possible implementation of the first aspect, the first device is a management device, and the second device includes the receiving-end device and / or the source-end device. The first device obtains first status information of M links between the source-end device and the receiving-end device, including: the first device receives the first status information sent by the receiving-end device; the first device obtains first capability information of the receiving-end device, including: the first device receives the first capability information sent by the receiving-end device; the first device obtains second capability information and second status information of each of the K upstream devices, including: the first device receives the second capability information and the second status information sent by each of the upstream devices; the method further includes: the first device sends second configuration information to at least one of the K upstream devices, and the second configuration information is used to instruct the at least one upstream device to perform configuration of delay transmission compensation for the corresponding link.

[0022] In a possible implementation of the first aspect, the first configuration information includes a mark for indicating that a link belongs to the first link group.

[0023] In a possible implementation of the first aspect, the first device sends the first configuration information to the second device, including: the first device sends the first configuration information to the second device by carrying the first configuration information in a reserved field of an overhead code block.

[0024] In a possible implementation of the first aspect, the first device sends the first configuration information to the second device, including: the first device sends the first configuration information for indicating that a first link among the N links belongs to the first link group to the second device through the first link.

[0025] In a possible implementation of the first aspect, a first part of bits in the first configuration information is used to indicate that the first link forms the first link group with other links, and a second part of bits in the first configuration information is a mark of the first link group.

[0026] In a possible implementation of the first aspect, the first device receives the first status information sent by the receiving-end device, including: the first device receives the first status information sent by the receiving-end device and carried in a first type length value (TLV) unit in the link layer discovery protocol (LLDP) format of the management channel of the overhead code block.

[0027] In a possible implementation of the first aspect, the first TLV unit is further capable of carrying information indicating the current state of the delay transmission compensation for the M links by the receiving-end device when the receiving-end device sends service data to the source-end device.

[0028] In a possible implementation of the first aspect, the first TLV unit is further capable of carrying information indicating the configuration of the delay transmission compensation that the upstream device should perform on the corresponding link.

[0029] In a possible implementation of the first aspect, the first device receives the first capability information sent by the receiving-end device, including: the first device receives the first capability information carried in a second type-length-value (TLV) unit in the link layer discovery protocol (LLDP) format of the management channel of the overhead code block and sent by the receiving-end device.

[0030] In a possible implementation of the first aspect, the second TLV unit is further capable of carrying information indicating the capability of the receiving-end device to perform delay transmission compensation on the M links when the receiving-end device sends service data to the source-end device.

[0031] In a second aspect, a device for configuring a link group is provided. The device for configuring a link group is a first device and is used to execute the method in the first aspect or any possible implementation of the first aspect. Specifically, the device for configuring a link group may include a module for executing the method in the first aspect or any possible implementation of the first aspect.

[0032] In a third aspect, a device for configuring a link group is provided. The device for configuring a link group is a first device. The device for configuring a link group includes a processor, a memory, and a network interface. The memory is used to store instructions. The processor and the network interface are used to execute the instructions stored in the memory, and the execution of the instructions stored in the memory causes the processor and the network interface to execute the method in the first aspect or any possible implementation of the first aspect.

[0033] A fourth aspect provides a device for configuring a link group. The device for configuring the link group is a first device. The device for configuring the link group includes a processor, a memory, and a network interface. The memory is used for storing instructions. The processor and the network interface are used for executing the instructions stored in the memory, and the execution of the instructions stored in the memory causes: the first device to obtain first status information of M links between a source device and a receiving device, where the first status information is used to indicate the status of the differential delay between any two of the M links, and any one of the M links is a Flexible Ethernet (FlexE) physical connection link or a Flexible Optical Transport Network (FlexO) physical connection link, and M is an integer greater than or equal to 2; the first device to obtain first capability information of the receiving device, where the first capability information is used to indicate the first capability of the receiving device to perform differential delay compensation on the M links; the first device to divide N links of the M links into a first link group according to the first status information and the first capability information, where N is an integer less than or equal to M and greater than or equal to 2; and the first device to send first configuration information to a second device, where the first configuration information includes information used to indicate the first link group.

[0034] A fifth aspect provides a computer storage medium, on which instructions are stored. When the instructions are run on a computer, the computer is caused to execute the method according to the first aspect or any one of the possible implementation manners of the first aspect.

[0035] A sixth aspect provides a computer program product including instructions. When a computer runs the instructions of the computer program product, the computer is caused to execute the method according to the first aspect or any one of the possible implementation manners of the first aspect.

[0036] The effects achievable by the second aspect to the sixth aspect correspond to those achievable by the first aspect, and will not be elaborated one by one here.

[0037] It should be understood that in each aspect of the present application and its corresponding implementation manners, when transmitting any one of the first status information, the first capability information, the second status information, the second capability information, the first configuration information, and the second configuration information, the status, capability, or configuration information corresponding to the link may be transmitted on each link, that is, the relevant information is transmitted in terms of the link granularity. Of course, in each aspect of the present application and its corresponding implementation manners, the relevant information may also be transmitted in other granularities, for example, in terms of the device granularity, which is not limited herein.

[0038] It should also be understood that in various aspects of the present application and their corresponding implementations, differential delay compensation refers to delay reception compensation, that is, compensation in the receiving direction, which is generally also called "deskew"; delay transmission compensation, that is, compensation in the transmitting direction, is generally also called "remote deskew". Brief Description of the Drawings

[0039] Figure 1 It is a schematic diagram of a code block stream on a 100G FlexE interface.

[0040] Figure 2 It is a schematic block diagram of the functional structure of a receiving-end device in FlexE.

[0041] Figure 3 It is a schematic diagram of a receiving-end device in FlexE transmitting a code block stream.

[0042] Figure 4 It is a schematic diagram of the frame format of a FlexE overhead code block.

[0043] Figure 5 It is a schematic diagram of an application scenario of FlexE transmission across a transport network.

[0044] Figure 6 It is a schematic flowchart of a method for configuring a link group according to an embodiment of the present application.

[0045] Figure 7 It is a schematic diagram of the state of differential delay of a link according to an embodiment of the present application.

[0046] Figure 8 It is a schematic diagram of the result of configuring a link group according to an embodiment of the present application.

[0047] Figure 9 It is a schematic diagram of the process of configuring a link group and performing compensation according to an embodiment of the present application.

[0048] Figure 10 It is a schematic diagram of the process of configuring a link group and performing compensation according to an embodiment of the present application.

[0049] Figure 11 It is a schematic diagram of the process of configuring a link group and performing compensation according to an embodiment of the present application.

[0050] Figure 12 It is a schematic diagram of the process of configuring a link group and performing compensation according to an embodiment of the present application.

[0051] Figure 13 It is a schematic block diagram of a device for configuring a link group according to an embodiment of the present application.

[0052] Figure 14Schematic block diagram of a device for configuring a link group according to another embodiment of the present application. Detailed implementation

[0053] The technical solutions in the present application will be described below with reference to the accompanying drawings.

[0054] It should be understood that the technical solutions of the embodiments of the present application can be applied to networks such as FlexO or FlexE, and the embodiments of the present application do not limit this.

[0055] It should be understood that the physical connection link in the embodiments of the present application can be simply referred to as a "link", and in FlexE, the link can also be referred to as a "PHY link". The link in the embodiments of the present application refers to the link between the source device and the receiving device, and intermediate devices may exist on the link from the source device to the receiving device.

[0056] The concepts involved in this specification will be briefly introduced below.

[0057] FlexE technology:

[0058] Ethernet has been widely used and developed significantly in the past quite a long time. The rate of Ethernet interfaces has increased by a factor of 10, evolving from 10 Mbps to 100 Mbps, 1000 Mbps (1 Gbps), 10 Gbps, and 100 Gbps. With the continuous increase in the rate of Ethernet interfaces, it has gradually encountered technical bottlenecks in further increasing the rate of Ethernet interfaces. At the same time, in order to adapt to the diverse rate requirements of Ethernet interfaces in actual scenarios, such as 200 Gbps, 40 Gbps, 200 Gbps, and 400 Gbps Ethernet interfaces have been developed.

[0059] Before the birth of the standard for the new generation of higher-rate Ethernet interfaces, the network's demand for bandwidth usually exceeded the rate of existing Ethernet interfaces. During the transitional period when the new Ethernet interface standard was born and the cost of the new Ethernet interface was relatively high, the LAG technology could achieve a virtual high-rate Ethernet interface by binding multiple low-rate Ethernet interfaces into a LAG. However, the LAG technology distributes service data to each interface in the LAG according to the service through a hash algorithm. Similar to the service-based load balancing method, the LAG also has the problems of uneven interface bandwidth allocation and low utilization rate. If there is a service with a rate greater than that of a single interface, it can only be allocated to a certain interface through the hash algorithm, which will cause congestion of this interface and the service transmission rate will be limited by the rate of this interface.

[0060] In forwarding equipment, when a service is forwarded from a low-rate interface to a high-rate interface, it is necessary to cache the entire service message before forwarding to prevent message breakage, which greatly increases the transmission delay of service data. In order to improve the forwarding efficiency between interfaces of different rates, the Optical Internet Forum (OIF) released the Multi Link Gearbox (MLG) technology, which can reverse multiplex a high-rate Ethernet interface to divide it into several low-rate Ethernet interfaces. However, MLG technology only supports a few fixed interface division methods, for example, dividing a 40G Ethernet interface into 4×10G or 2×20G Ethernet interfaces, and the supported sub-interface types are limited, and the flexibility is not high enough.

[0061] FlexE technology is a flexible Ethernet interface technology developed to meet the above requirements. Figure 1 This is a schematic diagram of the code block flow on the 100G FlexE interface. The FlexE 1.0 standard defines that by time-division multiplexing the services of the 100G Ethernet interface with a period of 20 code blocks, FlexE divides the 100G Ethernet interface into 20 time slots with 5G as the granularity (corresponding to 1 code block in the 20 code block period). A FlexE overhead (OH) code block is inserted every 1023×20 data code blocks, as shown in the following figure. Figure 1 FlexE can bind S Ethernet interfaces into a link aggregation group, and service data can be transmitted in any idle time slot among the 20*S time slots in the link aggregation group.

[0062] Figure 2 This is a schematic block diagram of the functional structure of the receiving device in FlexE. Figure 2 As shown in the figure, FlexE technology inserts a new layer, the FlexE Shim layer, on the Physical Coding Sublayer (PCS) of the Ethernet interface. The FlexE Shim layer accepts multiple Flexible Ethernet services (FlexE Client) upward and connects multiple 100G Ethernet interfaces downward. The FlexE 1.0 standard specifies that the FlexE Client is a 64 / 66B encoded block stream. After the idle block insertion / deletion (Idle Insert / Delete) is used for rate adaptation, the blocks in the block stream of the Flexible Ethernet service are placed in turn in the time slots allocated to the Flexible Ethernet service.

[0063] Figure 3 This is a schematic diagram of the code block stream sent by the receiving device in FlexE. Figure 3As shown in the figure, in FlexE, for a link aggregation group composed of S physical connection links, that is, a Flexible Ethernet group (FlexE Group) composed of S physical links (Physical, PHY), there are a total of 20*S time slots. The Flexible Ethernet Shim layer uses a time slot allocation table (Calendar) with a length of 20*S to dispatch the positions of 66B code blocks. For example, in one cycle, the first 20 code blocks are sent by PHY1, the subsequent 20 code blocks are sent by PHY2, and so on until PHYS. The 20 code blocks on each PHY can also be called a sub-calendar. In a specific example, if a 10G Flexible Ethernet service occupies two of the 20*S time slots, then two code blocks are extracted from the code block stream of the 10G Flexible Ethernet service and placed at the corresponding positions in one cycle (1 code block corresponds to 1 5G time slot). In another specific example, a 25G Flexible Ethernet service occupies 5 time slots, and 5 code blocks are extracted from the code block stream of the 25G Flexible Ethernet service and placed at the corresponding positions in the calendar in each cycle. The configuration information of which Flexible Ethernet services are transmitted in each time slot in the FlexE Group is specified in a specific field in the FlexE OH code block.

[0064] Figure 4 is a schematic diagram of the frame format of the FlexE overhead code block. As Figure 4 shown, 32 consecutive FlexE frames form a FlexE multiframe, and a FlexE OH frame consists of 8 consecutive FlexE OH code blocks. The first code block in the FlexE frame uses the "0x4B" or "0x5" field as a marker field to identify that this code block is an OH code block. When the receiving device recognizes this OH code block, it can receive the next OH code block after receiving 1023×20 64 / 66B code blocks (data code blocks). By analogy, the entire FlexE frame can be extracted from the code block stream.

[0065] As Figure 4As shown, the FlexE OH frames transmitted on each link include fields such as FlexE Group Number, PHY Map, PHY Number, Calendar A, and Calendar B. The FlexE Group Number is used to indicate the FlexE group number to which the link belongs; the PHY Map (a total of 8×32 = 256 bits are required in a FlexE superframe to indicate) is used to indicate the distribution of the PHYs included in the FlexE group to which the link belongs; the physical link number can be from 1 to 254; Calendar A and Calendar B are respectively used to indicate the current Calendar configuration and the standby Calendar configuration of the FlexE Group. 16 bits in the third code block of each FlexE frame are used to indicate the number of the service data transmitted in the time slot. The first FlexE frame in each FlexE superframe carries the number of the service data transmitted in the corresponding time slot 0 (slot 0), and so on, until the 20th FlexE frame in the FlexE superframe carries the number of the service data transmitted in the corresponding slot 19. After the receiving device receives the FlexE frame information on all links in the FlexE Group, it can obtain the time slot allocation method of each service data in the FlexE Group.

[0066] Since service data in FlexE can be transmitted on multiple time slots across links, the receiving device needs to perform differential delay compensation on each link in the FlexE Group before recovering the flexible Ethernet service from multiple time slots. Otherwise, there will be a problem of code block disorder when recovering the flexible Ethernet service from the time slots across links with differential delay. The FlexE 1.0 standard stipulates that the FlexE Group is marked by the first overhead code block of the FlexE frames transmitted on each link, and the transmission delays of each link are aligned through the buffer in the receiving device. Usually, in the transmission scenario of direct connection of FlexE Group shim-to-shim, the differential delay compensation (deskew) ability of each link is at least 300 ns, and in the long-distance cross-transport network transmission of the FlexE Group, the differential delay compensation ability of each link is at least 10 us.

[0067] Since service data can be transmitted across multiple time slots on different links within a FlexE Group, at the receiving end device, the FlexE frames on multiple links need to be aligned to ensure that the service data can be recovered from the corresponding time slots in the correct order. The FlexE 1.0 standard uses the FlexE frame boundary as a reference to calculate the differential delay of each link and aligns the code block streams on each link through buffering. As mentioned above, for the transmission scenario of shim-to-shim direct connection within a FlexE Group, the differential delay of each link within the FlexE Group specified by the FlexE standard should be <= 300 ns; for the long-distance cross-transport network transmission scenario, the differential delay of each link should be <= 10 us. If the differential delay on a certain link within the FlexE Group exceeds the differential delay compensation capability of the receiving end device, the entire FlexE Group will fail.

[0068] FlexO technology:

[0069] FlexO forms a Flexible Optical Transport Network Group (FlexO Group) by binding multiple ports with standard rates (such as m×100G) to carry the signals of the standard optical transport unit Cn (Optical Transport Unit-Cn, OTUCn) (n≥1), which makes up for the deficiency that ports with a bandwidth greater than 100G were not defined in the previous protocols. Similarly to FlexE, since the OTUCn signal is transmitted across multiple links, it is necessary to align the service data transmitted on each link to ensure the recovery of the transmitted OTUCn signal. Currently, FlexO stipulates that the alignment of the service data on each link in the FlexO Group is achieved through the Frame Alignment Signal (FAS) field in the OTUCn frames transmitted on each link. If the differential delay of a certain link in the FlexO Group exceeds the differential delay compensation capability of the receiving end device, the entire FlexO Group will fail.

[0070] Link Layer Discovery Protocol (LLDP) technology:

[0071] The embodiments of the present application are also related to the LLDP technology. LLDP is a Link Layer Discovery Protocol defined in the standard 802.1AB. Through LLDP, a transport network device can regularly send multicast packets carrying local information to other adjacent transport network devices through standard LLDP Type Length Value (TLV) units. LLDP stipulates that each port of a transport network device has a standard Simple Network Management Protocol (SNMP) Management Information Base (MIB) for storing the status information of local and other adjacent transport network devices. The transport network devices refresh the status information stored in the SNMP MIB by sending and receiving LLDP TLV units. Through LLDP, the management and maintenance of the status information of transport network devices can be facilitated.

[0072] The TLV unit is the basic information unit in LLDP, and different types of TLVs can carry different information. Among them, LLDP reserves a TLV unit that can be customized by each standard organization. Table 1 shows the definitions of each field of the TLV unit in the customizable LLDP format. It should be understood that the TLV units shown in Tables 2 to 7 in this specification are all specific application forms of the TLV unit shown in Table 1.

[0073] Table 1 TLV Unit in the Customizable LLDP Format

[0074]

[0075] The following combines Figure 2 and Figure 5 to introduce the scenario of applying the method for configuring a link group in the embodiments of the present application. As Figure 2 shown, FlexE works between the MAC layer and the PHY layer. FlexE realizes the function of dividing the traditional Ethernet port into Time Division Multiplexing (TDM) channels and binding multiple Ethernet ports by modifying the original Reconciliation Sublayer (RS) and PCS. The LLDP and LAG technologies work at the MAC layer. The FlexE 1.0 standard defines the application scenarios of FlexE for Ethernet transmission and cross-transport network transmission. Figure 5 is a schematic diagram of the application scenario of FlexE cross-transport network transmission. FlexE cross-transport network transmission is based on the FlexE Aware Transport mode. Figure 5In an Ethernet router, the Flexible Ethernet Shim (FlexE Shim) connected thereto needs to perform differential delay compensation on two links in the FlexE Group connected thereto. FlexO operates at the PHY layer. Similarly to FlexE, it also needs to perform differential delay compensation on multiple links.

[0076] Based on the possible failure situations of the FlexE Group in FlexE and the possible failure situations of the FlexO Group in FlexO, the embodiments of the present application provide a method for configuring a link group. The embodiments of the present application implement compensation negotiation between transport network devices by modifying the functional components related to FlexE or FlexO involved. After being modified by the embodiments of the present application, the transport network devices allow links with differential delay compensation capabilities exceeding those of the receiving-end device to exist in the link group when the link group is established. It should be understood that the transport network devices involved in the embodiments of the present application may include a source-end device, an intermediate device, and a receiving-end device.

[0077] Figure 6 It is a schematic flowchart of a method 100 for configuring a link group according to an embodiment of the present application. As Figure 6 shown, the method 100 for configuring a link group may include the following steps.

[0078] S110, a first device obtains first status information of M links between a source-end device and a receiving-end device. The first status information is used to indicate the status of the differential delay between any two of the M links. Any one of the M links is a Flexible Ethernet (FlexE) physical connection link or a Flexible Optical Transport Network (FlexO) physical connection link, where M is an integer greater than or equal to 2.

[0079] S120, the first device obtains first capability information of the receiving-end device. The first capability information is used to indicate the first capability of the receiving-end device to perform differential delay compensation on the M links.

[0080] S130, the first device divides N links among the M links into a first link group according to the first status information and the first capability information, where N is an integer less than or equal to M and greater than or equal to 2.

[0081] S140, the first device sends first configuration information to a second device. The first configuration information includes information used to indicate the first link group.

[0082] It should be understood that the first device is a decision-making device that determines the link group division method, and the second device includes related devices that cooperate with the decision-making device to complete the link group configuration.

[0083] It should also be understood that in the embodiments of the present application, differential delay compensation refers to delay reception compensation, that is, compensation in the receiving direction, which is generally also called "deskew"; delay transmission compensation is compensation in the sending direction, which is generally also called "remotedeskew".

[0084] In the method for configuring a link group according to an embodiment of the present application, the first device divides N links among the M links into a first link group according to the state of the differential delays of the M links between the source device and the receiving device and the ability of the receiving device to perform differential delay compensation on the M links, thereby avoiding the situation where all M links are unavailable when the differential delays of the M links exceed the differential delay compensation ability of the receiving device, and improving the availability and robustness of the links in the transport network.

[0085] In FlexE, the data stream on each link in the FlexE Group is in the format of a 64 / 66B code block stream of 1 OH block + 1023×20 Datablocks. The receiving device aligns the data code blocks on each link with the 0x4B and 0x5 identification fields in the first OH block of the FlexE frames transmitted on each link.

[0086] Similarly, the FlexO frame is a data stream of 128 rows and 5440 bits, and 8 frames form a multiplex frame. The receiving device aligns the data code blocks on each link with the FAS field in the OTUCn frame carried in each FlexO frame.

[0087] The two transport networks can uniformly use the process of configuring a link group and the subsequent compensation process according to the embodiments of the present application. Each embodiment is described by taking FlexE as an example. Of course, the method for configuring a link group according to the embodiments of the present application can also be applied to FlexO, or to a transport network that spans FlexE and FlexO.

[0088] Figure 7 is a schematic diagram of the state of the differential delays of the links according to an embodiment of the present application. As Figure 7 shown, there are 5 links PHY1 - PHY5 between the source device and the receiving device, and each link independently sends FlexE frames between the source device and the receiving device. Figure 7 The horizontal axis of represents the time delay of the FlexE frames arriving on each link, and the width of the shaded box represents the ability of the receiving device to perform differential delay compensation. As Figure 7 shown in the 5 links, the differential delays between PHY1 and PHY2 are similar, and the differential delays of PHY3, PHY4, and PHY5 are similar, but the ability of the receiving device to perform differential delay compensation cannot complete the differential delay compensation for PHY1 - PHY5.

[0089] The method for configuring a link group of the present application will be described in detail below in conjunction with several embodiments.

[0090] Embodiment 1:

[0091] In this embodiment, the first device, i.e., the decision-making device, is a receiving-end device, and the second device is a source-end device. The receiving-end device has the ability to compensate for delayed reception.

[0092] In this embodiment, in S110, the first device obtains first status information of M links between the source-end device and the receiving-end device, which may include: the first device measures the differential delay of the M links to obtain the first status information. Specifically, the receiving-end device can measure the differential delay of the M links through some existing solutions to obtain the first status information.

[0093] Specifically, in each embodiment of the present application, the differential delay between any two links can be compared by measuring the transmission delay of each link; or by adding a counter at the receiving-end device, starting counting from 0 after receiving the marker code block of the fastest link, and recording the counter value x at this time after receiving the marker code blocks on other links. Then the transmission delay difference between these two links is the transmission time corresponding to x code blocks. Each embodiment of the present application does not limit the specific method for measuring the differential delay of the M links.

[0094] In Figure 7 In the specific example shown, the first status information may be that the differential delays between PHY1 and PHY2 are similar, and the differential delays of PHY3, PHY4, and PHY5 are similar. However, the ability of the receiving-end device to compensate for differential delays cannot complete the differential delay compensation for PHY1 - PHY5.

[0095] Limited by the differential delay compensation capability of the receiving device, the receiving device cannot support differential delay compensation for all of PHY1 - PHY5. Considering maximizing the number of member links that support cross - link services, N links can be selected from all M links between the source device and the receiving device and marked as "selected", and the other M - N links are marked as "standby". In this embodiment, N = 3, that is, PHY3, PHY4, and PHY5 are marked as "selected", and the other two links, PHY1 and PHY2, are marked as "standby". The marked "selected" PHY3, PHY4, and PHY5 form the first link group, and cross - link services can be carried on the 3 links of the first link group. The marked "standby" PHY1 and PHY2 can be used to independently transmit complete services, or the marked "standby" PHY1 and PHY2 are in a standby state and do not transmit services in the standby state. Services are not transmitted in parallel on the links marked as "standby", nor are they transmitted in parallel on the two links marked as "standby" and "selected" respectively.

[0096] In addition, it is also possible to consider establishing two link groups. Figure 8 It is a schematic diagram of the result of configuring a link group in this embodiment. The links PHY3, PHY4, and PHY5 are marked as "selected1", that is, the first link group, for carrying cross - link services; the links PHY1 and PHY2 are marked as "selected2", that is, the second link group, for carrying cross - link services. Services cannot be transmitted across link groups between the first link group marked as "selected1" and the second link group marked as "selected2".

[0097] In addition to the above two link group configuration schemes, the embodiments of the present application can also have more different link group configuration schemes determined according to the differential delay status between links and the differential delay compensation capability of the receiving device for links. The embodiments of the present application do not limit this.

[0098] It should be understood that the above is only an illustration of the method for configuring link groups in the embodiments of the present application with M = 5 as an example, rather than a limitation on the method for configuring link groups in the embodiments of the present application.

[0099] Optionally, the method for configuring link groups in this embodiment may further include: the first device transmits service data with the second device based on the first link group; the first device performs differential delay compensation on the links in the first link group according to the first configuration information.

[0100] Figure 9It is a schematic diagram of the process 200 for configuring a link group and performing compensation in this embodiment. The process 200 may include the following steps.

[0101] S210, Start a link between the source device and the receiving device.

[0102] S220, The source device independently sends data frames to the receiving device through M links respectively. Correspondingly, the receiving device receives the data frames sent by the source device. It should be understood that these data frames may include alignment markers.

[0103] S230, The receiving device measures the differential delay status of the M links to obtain first status information.

[0104] S240, The receiving device determines how to configure the link group according to the first status information and first capability information that can represent the ability of the receiving device to perform differential delay compensation on the M links, that is, determines first configuration information. Specifically, the configuration includes dividing N of the M links into a first link group.

[0105] S250, The receiving device performs differential delay compensation on the M links. Specifically, the receiving device performs differential delay compensation according to the first configuration information, that is, sets the buffer size of the differential delay. In other words, the receiving device performs differential delay compensation on the links in the first link group according to the link group configuration determined by itself. It should be understood that S250 may be performed simultaneously with S260, and this embodiment does not limit this.

[0106] S260, The receiving device sends the first configuration information to the source device, and the first configuration information includes information for indicating the first link group. Correspondingly, the source device receives the first configuration information sent by the receiving device. The form of the first configuration information can be various, which will be described in detail below.

[0107] Optionally,

[0108] S270, The source device sends service data to the receiving device according to the first configuration information.

[0109] It should be understood that in various embodiments of the present application, the first configuration information may include a marker for indicating that a link belongs to the first link group, which will not be elaborated in the subsequent embodiments.

[0110] For example, the first configuration information may include the "selected" marker (for indicating that a link belongs to the first link group) and the "standby" marker described above.

[0111] For another example, the first configuration information may include the "selected1" flag (used to indicate that the link belongs to the first link group) and the "selected2" flag (used to indicate that the link belongs to the second link group) described above. Specifically, the first device sends the first configuration information indicating that the first link among the N links belongs to the first link group to the second device through the first link. In other words, the information indicating the link group configuration can be indicated by a link group identifier (such as "Subgroup ID", where "Subgroup" is used to distinguish from the existing "Group"). Adding a "Subgroup ID" to the M links, differential delay compensation operations can be performed on the links marked with the same "Subgroup ID", and services can be transmitted across the links; if only one link is marked with a certain "Subgroup ID", services can only be independently transmitted on that link.

[0112] For yet another example, the first configuration information may include information indicating the link groups to which the M links respectively belong. The first device sends the information indicating the link groups to which the M links respectively belong to the second device through each link respectively.

[0113] It should be understood that in the embodiments of the present application, when the first device in S140 sends the first configuration information to the second device, it may include: the first device sends the first configuration information carried in a data code block to the second device; or the first device sends the first configuration information carried in the management channel of the overhead code block in a message in Link Layer Discovery Protocol (LLDP) format, High-Level Data Link Control (HDLC) format, or Point to Point Protocol (PPP) format to the second device; or the first device sends the first configuration information carried in the reserved field of the overhead code block to the second device. This will not be elaborated in the subsequent embodiments.

[0114] In a specific example, the first configuration information (for example, the flag indicating the link group to which each link belongs) is transmitted in the form of sending a message in LLDP format through the management channel of the OH code block. Specifically, the first configuration information can be carried in a Type-Length-Value (TLV) unit in LLDP format and transmitted through the shim-to-shim management channel in the FlexE OH code block.

[0115] The definitions of the fields of an optional TLV unit in LLDP format for carrying the first configuration information are shown in Table 2. In the TLV unit,

[0116] The first 7 bits of byte1 to byte2 are the TLV type. According to the LLDP specification, the type value of the TLV unit customized by each organization is 127.

[0117] The last 9 bits of byte1 to byte2 are the TLV length, indicating the total length of this TLV unit in bytes.

[0118] Byte3 to byte5 are the Organizationally Unique Identifier (OUI) of each organization as specified by LLDP. Among them, the OUI corresponding to OIF is 00-0F-40.

[0119] Byte6 is the subtype of the TLV unit customized by each organization, which can be 0x?? (hexadecimal), for example, it can be 0x01 (hexadecimal) or 00000001 (binary), etc.

[0120] Byte7 is the label of the link group to which this link belongs.

[0121] 0x00 can indicate that the differential delay of this link exceeds the differential delay compensation capability of the receiving device, that is, "standby"

[0122] 0x01 to 0xFF can indicate that the differential delay of this link is within the differential delay compensation capability of the receiving device, that is, "selected". The specific corresponding value can indicate the number of the link group to which this link belongs.

[0123] It should be understood that the definitions of each field of the TLV unit in the LLDP format for carrying the first configuration information given in Table 2 are only exemplary and can be deformed accordingly as needed. The embodiments of the present application do not limit this.

[0124] Table 2 TLV unit in the LLDP format for carrying the first configuration information

[0125]

[0126] After receiving this TLV unit on the management channel of the OH code block, the source device can complete the configuration of the link group according to the indication of the "label of the link group to which the link belongs" and send service data.

[0127] In another specific example, the first configuration information (e.g., the label of the link group to which each link belongs is transmitted on each link) is transmitted through the reserved field of the OH code block. The first part of the bits in the first configuration information is used to indicate that the first link and other links form the first link group, and the second part of the bits in the first configuration information is the label of the first link group. Figure 10 It is a schematic diagram of the format of the reserved field in this embodiment. Specifically, 11 bits can be divided in the reserved field of the OH code block to carry the first configuration information. The first 3 bits can carry the "selected" or "standby" label, and in the "selected" state, the next 8 bits can be used to carry the "label of the link group to which the link belongs". It should be understood that the first part of the bits includes 3 bits and the second part of the bits includes 8 bits are only examples, and the first part of the bits and the second part of the bits can include more or fewer bits, which is not limited in the embodiments of the present application.

[0128] It should be understood that the OH code block includes a reserved field with multiple bits. Figure 10 The position of the reserved field shown for carrying the first configuration information is only exemplary and not a limitation on the embodiments of the present application.

[0129] For FlexO, the configuration information corresponding to each link can be placed in the management channel of the OH code block of the OTUCn frame for transmission, or can be placed in the 0 byte of the General Communication Channel (GCC) and transmitted in the Generic Framing Procedure (GFP) format, HDLC format, PPP format or in the Reserved (RES) field in a custom frame format, or can also be placed in the payload of the OTUCn frame, for example, placed in the payload of the Optical Payload Unit-Cn (OPUCn) and transmitted in the GFP format or other custom frame formats.

[0130] In this embodiment, the receiving end device has the ability of delay receiving compensation. The receiving end device is used as the decision device to determine the configuration of the link group, which is simple and convenient to execute, and the signaling overhead is small when performing the link group configuration.

[0131] Embodiment 2:

[0132] In this embodiment, the first device, i.e., the decision device, is the source end device, and the second device is the receiving end device. The receiving end device has the ability of delay receiving compensation.

[0133] In this embodiment, S110 where the first device obtains first status information of M links between the source device and the receiving device may include: the first device receives the first status information sent by the receiving device. S120 where the first device obtains first capability information of the receiving device may include: the first device receives the first capability information sent by the receiving device.

[0134] Figure 11 It is a schematic diagram of process 300 for configuring a link group and performing compensation in this embodiment. This process 300 may include the following steps.

[0135] S305, Start a link between the source device and the receiving device.

[0136] S310, The source device independently sends data frames to the receiving device through M links respectively. Correspondingly, the receiving device receives the data frames sent by the source device. It should be understood that these data frames may include alignment markers.

[0137] S315, The receiving device measures the status of the differential delays of M links.

[0138] S320, The receiving device sends first status information to the source device, and this first status information is used to indicate the status of the differential delays of M links. Correspondingly, the source device receives the first status information sent by the receiving device.

[0139] S325, The receiving device sends first capability information to the source device, and this first capability information is used to indicate the first capability of the receiving device to perform differential delay compensation on M links. Correspondingly, the source device receives the first capability information sent by the receiving device.

[0140] S330, The source device determines how to configure the link group according to the first status information and the first capability information. Specifically, in the configuration, N links out of M links are divided into the first link group.

[0141] S335, The source device sends first configuration information to the receiving device, and the first configuration information includes information for indicating the first link group. Correspondingly, the receiving device receives the first configuration information sent by the source device.

[0142] S340, The receiving device performs differential delay compensation on M links. Specifically, the receiving device performs differential delay compensation according to the first configuration information, that is, sets the buffer size of the differential delay. In other words, the receiving device performs differential delay compensation on the links in the first link group according to the link group configuration determined by itself.

[0143] S345. The receiving device returns an acknowledgment message to the source device to indicate that the above first configuration information has been received and the corresponding link group configuration has been performed. Correspondingly, the source device receives the acknowledgment message returned by the receiving device. It should be understood that S345 is an optional step. Further, the receiving device may also send the status of the differential delay of each updated link to the source device.

[0144] S350. The source device sends service data to the receiving device according to the first configuration information.

[0145] Among them, the sending method of the first configuration information may be similar to the sending method of the first configuration information in Embodiment 1, and will not be elaborated here.

[0146] Optionally, in S335, the first configuration information may further include the buffer requirements for the receiving device when performing differential delay compensation for each link. The receiving device directly sets the buffer amount of each link according to the buffer requirements.

[0147] Optionally, in S330, the source device may also combine relevant information of the service data to be sent to the receiving device, such as comprehensive factors such as the number of services and / or bandwidth, etc., to determine the configuration scheme of the link group.

[0148] It should be understood that the acknowledgment message returned by the receiving device in S345 may be transmitted in the form of a message in LLDP format; it may also be transmitted through the reserved field in the OH code block. For example, in Embodiment 1, there are still 2 bits of reserved fields after the OH reserved field carrying the first configuration information that can be used to transmit this acknowledgment message. For example, "00" indicates that the receiving device has received the first configuration information and successfully set the buffer amount of each link; "01" indicates that the buffer amount of each link has not been successfully set. After receiving the acknowledgment message "00", the source device may send service data. If it receives the message "01", it returns to S330 to re-determine the configuration scheme of the link group.

[0149] In S325, the first capability information may be sent through a data code block, or may be sent in the form of a message in LLDP format, HDLC format or PPP format in the management channel of the overhead code block, or may be sent through the reserved field of the overhead code block. This embodiment does not make a limitation in this regard.

[0150] In a specific example, the first capability information may be carried in the TLV unit in LLDP format in the management channel of the overhead code block. The definitions of the fields of the TLV unit in LLDP format for carrying the first capability information are shown in Table 3.

[0151] Among them, the definitions of the byte1-6 fields in Table 3 are the same as the definitions of the byte1-6 fields in Table 2.

[0152] Byte7 is defined as the ability for differential delay compensation of the link. Among them, the first bit can represent the ability for differential delay compensation in the receive direction of the link. When the value of the first bit is "0", it means that the buffer size in the receive direction is the default value. For example, the buffer size is 469 code blocks corresponding to the 300ns differential delay compensation ability defined in FlexE1.0. When the value of the first bit is "1", it means that the buffer size in the receive direction is a value customized for this link, and the specific value is described in bytes 8 to 10. The other bits in byte7 can be reserved fields.

[0153] Bytes 8 to 10 are defined as the buffer size in the receive direction of the link. If the first bit in byte7 is "1" (the buffer size in the receive direction is a customized value), then the value x of bytes 8 to 10 represents that the buffer size in the receive direction is x code blocks, and the value range of x is [1 to 0xFFFFFE]. If the first bit in byte7 is "0", then the buffer size in the receive direction is the default value, and the values of bytes 8 to 10 can be set to "0xFFFFFF".

[0154] It should be understood that the buffer size in the receive direction defined by bytes 8 to 10 in this TLV unit (for example, it can be the local deskew buffer size) is an optional parameter. When the buffer size in the receive direction of the link is the default size, there is no need to transmit the buffer size information in the receive direction, and its parameter can be set to "0xFFFFFF".

[0155] The buffer size in the receive direction described by way of example here is in units of code blocks (block). Similarly, the buffer size in the receive direction can be expressed in different description methods such as ns or 10ns or bytes or different basic buffer size units, and the embodiments of the present application do not make limitations.

[0156] In the transmission mode of FlexE Aware Transport, that is, in the cross-transport network transmission scenario, the receiving end device uses the above TLV unit to notify the source end device of the first ability, and transmits it through the shim-to-shim management channel of the OH code block. In other scenarios, the above TLV unit can be transmitted through the section management channel or through the shim-to-shim management channel.

[0157] Table 3 TLV unit in LLDP format for carrying the first ability information

[0158]

[0159] In a specific example, the first status information may be carried in a TLV unit in the LLDP format in the management channel of the overhead code block. The definitions of the fields of the TLV unit in the LLDP format for carrying the first status information are shown in Table 4.

[0160] Among them, the definitions of the byte1-6 fields in Table 4 are the same as those of the byte1-6 fields in Table 2.

[0161] Byte7 is defined as the result of the differential delay of the link (for example, it can be "FlexE group PHY deskewstatus"). Among them, the first bit represents the result of the current differential delay in the receiving direction of the link. "0" means that the receiving device compensates the differential delay of each link among the M links according to the first configuration information, and the differential delay compensation is successful; "1" means that the receiving device does not perform differential delay compensation or the differential delay compensation fails. Other bits in byte7 can be reserved fields.

[0162] Byte8-10 are defined as the delay amount of the differential delay of the link. The delay amount of the differential delay (for example, it can be "FlexE group PHY skew") parameter indicates the delay amount of this link relative to the link with the fastest transmission among the M links when the receiving device receives the data frames on each link. At this time, for example, if the "FlexE group PHY skew" of a certain link is 0, it means that this link is the link with the fastest transmission among the M links. Its value x indicates that the delay amount of the differential delay is the transmission time corresponding to x code block data.

[0163] In the transmission mode of FlexE Aware Transport, that is, in the cross-transport network transmission scenario, the receiving device uses the above TLV unit to notify the source device of the status of its own differential delay, and transmits it through the shim-to-shim management channel of the OH code block. In other scenarios, the above TLV unit can be transmitted through the section management channel or through the shim-to-shim management channel.

[0164] Table 4 TLV unit in the LLDP format for carrying the first capability information

[0165]

[0166] After the source device obtains the first capability information of the receiving device and the first status information of each link port through the above two TLV units, it determines the link group configuration and sends the first configuration information to the receiving device in a manner similar to that in Embodiment 1. The receiving device performs differential delay compensation on each link according to the first configuration information, which will not be elaborated here.

[0167] In this embodiment, the receiving device has the ability of delayed reception compensation. The source device serves as the decision-making device and can determine the configuration of the link group in combination with relevant information of the service data, such as comprehensive factors such as the number of services and / or bandwidth.

[0168] Embodiment 3:

[0169] In this embodiment, the first device, i.e., the decision-making device, is the management device, and the second device includes the receiving device and / or the source device. The receiving device has the ability of delayed reception compensation.

[0170] In this embodiment, for S110 where the first device obtains the first status information of M links between the source device and the receiving device, it may include: the first device receives the first status information sent by the receiving device. For S120 where the first device obtains the first capability information of the receiving device, it may include: the first device receives the first capability information sent by the receiving device.

[0171] The process of the management device making decisions on the link group configuration may include the following steps.

[0172] A-1, Start the link between the source device and the receiving device.

[0173] A-2, The source device independently sends data frames to the receiving device through M links respectively. Correspondingly, the receiving device receives the data frames sent by the source device. It should be understood that these data frames may include alignment marks.

[0174] A-3, The receiving device measures the differential delay status of M links.

[0175] A-4, The receiving device sends the first status information to the management device, and the first status information is used to indicate the differential delay status of M links. Correspondingly, the management device receives the first status information sent by the receiving device.

[0176] A-5, The receiving device sends the first capability information to the management device, and the first capability information is used to indicate the first capability of the receiving device to perform differential delay compensation on M links. Correspondingly, the management device receives the first capability information sent by the receiving device.

[0177] A-6. The management device determines how to configure the link group according to the first status information and the first capability information. Specifically, in the configuration, N links out of M links are divided into the first link group.

[0178] A-7. The management device sends the first configuration information to the source device and the receiving device. The first configuration information includes information for indicating the first link group. Correspondingly, the source device and the receiving device receive the first configuration information sent by the management device.

[0179] A-8. The source device and / or the receiving device may return confirmation information to the management device, which is used to indicate that the above first configuration information has been received and the corresponding configuration has been performed. Correspondingly, the management device receives the confirmation information returned by the source device and / or the receiving device. It should be understood that A-8 is an optional step.

[0180] A-9. After receiving the confirmation information, the management device issues an instruction to the source device indicating that the link group configuration has been completed. It should be understood that A-9 is an optional step.

[0181] A-10. The source device sends service data to the receiving device according to the first configuration information.

[0182] A-11. The receiving device performs differential delay compensation on the links in the first link group corresponding to the service data according to the first configuration information.

[0183] A-12. The first configuration information sent by the management device to the receiving device may also include, for each link, the buffer requirements when the receiving device performs differential delay compensation. The receiving device directly sets the buffer capacity of each link according to the buffer requirements. It should be understood that A-12 is an optional step.

[0184] It should be understood that the communication between the source device, the receiving device and the management device regarding the first status information, the first capability information and the first configuration information can be transmitted in the management channel of the OH code block of each device and the management device. Optionally, in FlexO, the above information can be transmitted in the GCC0 byte of the OH code block in GFP format, HDLC format, PPP format or in the RES field in a custom frame format. In FlexE, the above information can be transmitted in the management channel of the OH code block in the form of Internet Protocol (IP) packets. The specific transmission method in this embodiment is not limited.

[0185] In this embodiment, the management device serves as the decision-making device. On the one hand, it can receive relevant information of the source device and the receiving device, and can determine the configuration of the link group by considering comprehensive factors such as the number of services and / or bandwidth. On the other hand, it can avoid the possible computational complexity caused by the source device or the receiving device making decisions, and can reduce the burden on the source device and the receiving device.

[0186] It should be understood that in an actual scenario, the link may also pass through some intermediate devices on the path from the source device to the receiving device, such as Figure 5 the application scenario of FlexE cross-transport network transmission shown, that is, the transmission scenario based on the FlexE aware transport mode. In addition to the receiving device being able to perform differential delay compensation, each sending port of the intermediate device can also support the ability to delay sending data, or the ability of delay sending compensation. Therefore, it is necessary for the receiving device and the intermediate device to achieve collaborative compensation through negotiation.

[0187] In some embodiments of the present application, among M links, K upstream devices of the receiving device may have the ability of delay sending compensation, where K is a positive integer. The K upstream devices may include the source device and / or at least one intermediate device, and the intermediate device is located between the source device and the receiving device among the M links.

[0188] In the case where the K upstream devices of the receiving device have the ability of delay sending compensation, method 100 may further include: the first device obtains the second ability information and the second status information of each upstream device among the K upstream devices, the second ability information is used to indicate the second ability of each upstream device to perform delay sending compensation for at least one of the M links, and the second status information is used to indicate the current status of each upstream device to perform delay sending compensation for at least one of the M links; S130 the first device divides N links among the M links into the first link group according to the first status information and the first ability information, which may include: the first device divides N links among the M links into the first link group according to the first status information, the first ability information, the second status information and the second ability information; method 100 may further include: the first device determines the configuration of the delay sending compensation that each upstream device should perform for the corresponding link according to the first status information, the first ability information, the second status information and the second ability information.

[0189] It should be noted that not all of the M links will pass through all the upstream devices. For any one of the K upstream devices, only some of the M links (at least one link) may pass through.

[0190] The following describes several embodiments to illustrate the method for configuring a link group in an embodiment of the present application when the K upstream devices of the receiving device have the ability of delay sending compensation.

[0191] In Embodiment 4, Embodiment 5, and Embodiment 6, the first device, i.e., the decision-making device, is a receiving-end device, and the second device is a source-end device. The receiving-end device has the ability to compensate for delayed reception. The K upstream devices may include the source-end device and / or at least one intermediate device, and have the ability to compensate for delayed transmission.

[0192] S110 The first device obtains first status information of M links between the source-end device and the receiving-end device, which may include: the first device measures the differential delay of the M links to obtain the first status information; the first device obtains second capability information and second status information of each of the K upstream devices, which may include: the first device receives the second capability information and second status information sent by each upstream device; Method 100 may further include: the first device sends second configuration information to at least one of the K upstream devices, and the second configuration information is used to instruct at least one upstream device to perform configuration for compensating for delayed transmission on the corresponding link.

[0193] After at least one upstream device completes the configuration for compensating for delayed transmission, Method 100 may further include: the first device transmits service data with the second device based on the first link group; the first device performs differential delay compensation on the links in the first link group that have been compensated for delayed transmission by at least one upstream device according to the second configuration information according to the first configuration information.

[0194] It should be understood that when the M links cannot be aligned at the receiving-end device, the M links cannot form a link group, or in other words, the FlexE Group or FlexO Group crashes and cannot work. The source-end device, receiving-end device, and other devices in the embodiments of the present application may all have the ability to compensate for differential delay or delayed transmission. The devices in the embodiments of the present application achieve link group compensation through capability negotiation. When the compensation capabilities of the devices in the FlexE Group or FlexO Group between the source-end device and the receiving-end device cannot compensate for the differential delay of each link, by configuring the link group, the source-end device only bears cross-link transmission service data on the links with delayed alignment; or through the collaborative compensation of each device, the final M links can be aligned at the receiving-end device, which can ensure the operation of the FlexE Group or FlexO Group and improve the utilization rate of the link.

[0195] Embodiment 4:

[0196] In this embodiment, the first device, i.e., the decision-making device, is a receiving-end device, and the second device is a source-end device. The receiving-end device has the ability to compensate for delayed reception. There is an intermediate device with the ability to compensate for delayed transmission between the receiving-end device and the source-end device, that is, the K upstream devices are at least one intermediate device.

[0197] The process of collaborative compensation between the receiving-end device and the intermediate device may include the following steps.

[0198] B-1. Start a link between the source-end device and the receiving-end device.

[0199] B-2. The source-end device independently sends data frames to the receiving-end device through M links respectively. Correspondingly, the receiving-end device receives the data frames sent by the source-end device. It should be understood that these data frames may include alignment marks.

[0200] B-3. The receiving-end device measures the state of the differential delays of the M links to obtain first state information.

[0201] B-4. The intermediate device sends second capability information to the receiving-end device, and the second capability information is used to indicate the second capability of each intermediate device to perform delay transmission compensation on at least one of the M links. Correspondingly, the receiving-end device receives the second capability information sent by the intermediate device. It should be understood that the second capability information may be carried in the data frames of B-2 or sent in other ways, and this embodiment does not limit this.

[0202] B-5. The intermediate device sends second state information to the receiving-end device, and the second state information is used to indicate the current state of each intermediate device to perform delay transmission compensation on at least one of the M links. Correspondingly, the receiving-end device receives the second state information sent by the intermediate device. It should be understood that the second state information may be carried in the data frames of B-2 or sent in other ways, and this embodiment does not limit this.

[0203] B-6. The receiving-end device determines how to configure the link group and how to configure the delay transmission compensation according to the first state information, the first capability information that can represent the capability of the receiving-end device to perform differential delay compensation on the M links, the second capability information, and the second state information. Specifically, in the link group configuration, N of the M links are divided into the first link group.

[0204] B-7. The receiving-end device sends first configuration information to the intermediate device, and the first configuration information includes information indicating the first link group. Correspondingly, the intermediate device receives the first configuration information sent by the receiving-end device. It should be understood that B-7 is an optional step, and executing B-7 may not be used for the collaborative compensation process but for other processes.

[0205] B-8. The receiving-end device sends second configuration information to the intermediate device, and the second configuration information includes the configuration for indicating the delay transmission compensation that the upstream device should perform on the corresponding link. Correspondingly, the intermediate device receives the second configuration information sent by the receiving-end device.

[0206] B-9. The intermediate device adjusts the link transmission delay according to the second configuration information.

[0207] B-10. The intermediate device sends information about the updated current state of the delay transmission compensation to the receiving device. On the one hand, it can prepare for the next collaborative compensation. On the other hand, it notifies the receiving device that the configuration of the delay transmission compensation has been completed.

[0208] B-11. After receiving the information sent by the intermediate device, the receiving device sends the first configuration information to the source device. The first configuration information includes information indicating the first link group. Correspondingly, the source device receives the first configuration information sent by the receiving device. Meanwhile, optionally, the first configuration information may also include information used to indicate the relevant configuration of the completed differential delay compensation.

[0209] B-12. The receiving device performs differential delay compensation on the M links. Specifically, the receiving device performs differential delay compensation according to the first configuration information, that is, sets the buffer size of the differential delay. In other words, the receiving device performs differential delay compensation on the links in the first link group according to the link group configuration determined by itself.

[0210] B-13. The source device sends service data to the receiving device according to the first configuration information.

[0211] It should be understood that the communication between the source device, the intermediate device and the receiving device regarding the first status information, the first capability information, the first configuration information, the second status information, the second capability information and the second configuration information and other related information can be transmitted through data code blocks, or through the management channel of the overhead code blocks in the form of LLDP format, HDLC format or PPP format messages, or through the reserved fields of the overhead code blocks. This embodiment does not limit this.

[0212] Among them, the sending method of the first configuration information is similar to that in Embodiment 1 and will not be elaborated here.

[0213] This embodiment and other embodiments of the present application involve reporting or transmitting its own capability information. For example, the first capability information and the second capability information can be carried in the TLV unit of the LLDP format in the management channel of the overhead code blocks. The definitions of the fields of the TLV unit of the LLDP format for carrying the capability information are shown in Table 5.

[0214] Among them, the definitions of the byte1-6 fields in Table 5 are the same as those in Table 2.

[0215] Byte7 is defined as the ability to compensate for this link. Among them, the first bit of byte7 can represent the ability to compensate for the differential delay in the receive direction of this link. When the value of the first bit is "0", it means that the buffer size in the receive direction is the default value, such as the buffer size corresponding to the 300ns differential delay compensation ability defined in FlexE1.0 is 469 code blocks; when the value of the first bit is "1", it means that the buffer size in the receive direction is the custom value of this link, and the specific value is described in byte8-10. The second bit of byte7 can represent the ability to compensate for the delayed transmission in the transmit direction of this link. When the value of the second bit is "0", it means the default mode that does not support the ability to compensate for the delayed transmission; when the value of the second bit is "1", it means the ability to support the compensation for the delayed transmission, and the specific value of the delayed transmission buffer size is described in byte11-13. Other bits in byte7 can be reserved fields.

[0216] Byte8-10 is defined as the buffer size in the receive direction of this link. If the first bit in byte7 is "1" (the buffer size in the receive direction is the custom value), then the value x of byte8-10 represents the buffer size in the receive direction is x code blocks, and the value range of x is [1~0xFFFFFE]. If the first bit in byte7 is "0", then the buffer size in the receive direction is the default value, and the value of byte8-10 can be set to "0xFFFFFF".

[0217] Byte11-13 is defined as the buffer size in the transmit direction of this link. If the first bit in byte7 is "1" (the transmit direction supports the ability to compensate for the delayed transmission), then the value x of byte8-10 represents the buffer size in the transmit direction is x code blocks, and the value range of x is [1~0xFFFFFE]. If the first bit in byte7 is "0", it indicates that the transmit direction does not support the ability to compensate for the delayed transmission, and the value of byte8-10 can be set to "0xFFFFFF".

[0218] The buffer size described by way of example here is in units of code blocks (block). Similarly, the buffer size can be expressed in different description methods such as ns or 10ns or bytes or different basic buffer size units, and the embodiments of this application do not make limitations.

[0219] In the transport mode of FlexE Aware Transport, that is, in the scenario of cross-transport network transmission, the above TLV units are used to announce capabilities between devices and are transmitted through the shim-to-shim management channel of the OH code block. In other scenarios, the above TLV units can be transmitted through the section management channel or through the shim-to-shim management channel.

[0220] Table 5 TLV unit in LLDP format for carrying capacity information

[0221]

[0222] It should be noted that the TLV units shown in Table 5 can be used in each embodiment of the present application to carry capacity information. Since generally the link is bidirectional, in one transmission direction, a certain device is the receiving-end device, and in the other transmission direction, this device is the source-end device or the upstream device. The TLV unit for carrying capacity information in this embodiment is designed in the form shown in Table 5, so that whether this device is used as the receiving-end device or as the source-end device or the upstream device, the TLV unit can be used when reporting capacity information.

[0223] In other words, the TLV unit in the LLDP format of the management channel of the overhead code block shown in Table 5 can carry the first capacity information for indicating the first capacity of the receiving-end device to perform differential delay compensation on M links; it can also carry the information on the capacity of the receiving-end device to perform delayed transmission compensation on M links when the receiving-end device sends service data to the source-end device.

[0224] This embodiment and other embodiments of the present application involve reporting or transmitting its own status information. For example, the first status information and the second status information can be carried in the TLV unit in the LLDP format of the management channel of the overhead code block. The definitions of the respective fields of the TLV unit in the LLDP format for carrying status information are shown in Table 6.

[0225] Among them, the definitions of the byte1-6 fields in Table 6 are the same as the definitions of the byte1-6 fields in Table 2.

[0226] Byte7 is defined as the current state of differential delay compensation and the current state of delayed transmission compensation for this link, that is, the compensation state of the link. Among them, the first bit represents the current state of differential delay compensation in the receiving direction of this link. When the first bit value is "0", it indicates that the differential delay compensation of this link in the receiving direction is successful. For example, if this link is marked as "selected" in the reserved field of the OH code block and the "subgroup ID" is "3", it means that the differential delay compensation of this link is successful compared to other links in subgroup 3. When the first bit value is "1", it indicates that the differential delay compensation of this link in the receiving direction fails. For example, if this link is marked as "selected" in the reserved field of the OH code block and the "subgroup ID" is "3", it means that the differential delay compensation of this link fails compared to other links in subgroup 3, this link exceeds the differential delay compensation capability of the device, and the differential delay amount is described in bytes 8 - 10. The second bit in byte7 represents the current state of delayed transmission compensation in the sending direction of this link. When the second bit value is "0", it indicates that this link has no ability to delay transmission in the sending direction; when the second bit value is "1", it indicates that the ability to delay transmission of this link in the sending direction is in use. The delayed transmission amount is described in bytes 11 - 13. Other bits in byte7 are reserved fields.

[0227] Bytes 8 - 10 are defined as the differential delay amount when the differential delay compensation in the receiving direction of this link fails, that is, the differential delay amount by which this link exceeds the differential delay compensation capability in the receiving direction. Its value x represents that the exceeded differential delay amount is the transmission time corresponding to x code block caches. When the differential delay compensation in the receiving direction is successful, x is 0.

[0228] Bytes 11 - 13 are defined as the delayed transmission amount of this link. Its value x represents that the currently used delayed transmission cache size is x code blocks. When the second bit in byte7 is "0" (this link has no ability to delay transmission in the sending direction), the value of x is "0xFFFFFF".

[0229] The cache size described by way of example here is in units of code blocks (block). Similarly, the cache size can be represented in different description methods such as ns or 10ns or bytes, or different basic cache units of different sizes. The embodiments of this application do not make limitations.

[0230] In the transport mode of FlexE Aware Transport, that is, in the cross-transport network transmission scenario, the above TLV units are used to announce the status between devices and are transmitted through the shim-to-shim management channel of the OH code block. In other scenarios, the above TLV units can be transmitted through the section management channel or through the shim-to-shim management channel.

[0231] Table 6 TLV units in LLDP format for carrying status information

[0232]

[0233]

[0234] It should be noted that the TLV units shown in Table 6 can be used in each embodiment of the present application to carry status information. Since generally the link is bidirectional, in one transmission direction, a certain device is the receiving-end device, and in the other transmission direction, this device is the source-end device or the upstream device. In this embodiment, the TLV unit for carrying status information is designed in the form shown in Table 6, so that whether this device is used as the receiving-end device, or as the source-end device or the upstream device, the TLV unit can be used when reporting status information.

[0235] In other words, the TLV units in the link layer discovery protocol LLDP format of the management channel of the overhead code block shown in Table 6 can carry the first status information for indicating the status of the differential delay between any two of the M links; and can also carry the information on the current status of the receiving-end device compensating for the delayed transmission of the M links when the receiving-end device sends service data to the source-end device.

[0236] In addition, after determining the second configuration information, the decision device can also use the TLV units shown in Table 6 to carry the second configuration information. That is, the TLV unit can also carry the information on the configuration of the upstream device for compensating the delayed transmission of the corresponding link.

[0237] The sending method of the first configuration information can be similar to the sending method of the first configuration information in Embodiment 1, which will not be elaborated here. In addition, this embodiment and other embodiments of the present application involve reporting or transmitting their own status information and sending down configuration information. For example, the first status information, the second status information, the first configuration information, and the second configuration information can be carried together in the TLV units in the LLDP format of the management channel of the overhead code block. The definitions of the respective fields of the LLDP format TLV unit for carrying status information and configuration information are shown in Table 7.

[0238] Among them, the definitions of the byte1-6 fields in Table 7 are the same as those of the byte1-6 fields in Table 2.

[0239] Byte7-8 is defined as the compensation status of the link and the link group configuration. Among them, the first bit represents the current status of the differential delay compensation in the receiving direction of the link. The first bit value of "0" indicates that the differential delay compensation of the link in the receiving direction is successful. For example, if the link is marked as "selected" and the "subgroup ID" is "3" in the subsequent fields of byte7-8, it means that the differential delay compensation of the link is successful relative to other links in subgroup 3. The first bit value of "1" indicates that the differential delay compensation of the link in the receiving direction fails. For example, if the link is marked as "selected" and the "subgroup ID" is "3" in the subsequent fields of byte7-8, it means that the differential delay compensation of the link fails relative to other links in subgroup 3, the link exceeds the differential delay compensation ability of the device, and the differential delay amount is described in byte9-11. The second bit in byte7 represents the current status of the delayed transmission compensation in the transmitting direction of the link. The second bit value of "0" indicates that the link has no ability to delay transmission or the ability to delay transmission is not used in the transmitting direction; the second bit value of "1" indicates that the ability to delay transmission of the link in the transmitting direction is being used. The delayed transmission amount is described in byte12-14. Other bits in byte7 are reserved fields.

[0240] The third to thirteenth bits in byte7-8 are used to represent the link group to which the link belongs, that is, the marking information of the link. Among them, the 2-4 bits are used to represent "selected" or "standby", such as "001" represents "selected" and "010" represents "standby". In the "selected" state, the latter 8 bits can be used to represent the "subgroup ID". Other bits in byte7-8 are reserved fields.

[0241] The differential delay amount described in byte9-11 of Table 7 is the same as the differential delay amount described in byte8-10 of Table 6; the delayed transmission amount described in byte12-14 of Table 7 is the same as the delayed transmission amount described in byte11-13 of Table 6, which will not be elaborated here.

[0242] Table 7 is a TLV unit in LLDP format for carrying status information

[0243]

[0244] Embodiment 5:

[0245] In this embodiment, the first device, i.e., the decision-making device, is the receiving-end device, and the second device is the source-end device. The receiving-end device has the ability to compensate for delayed reception. The source-end device has the ability to compensate for delayed transmission, i.e., K upstream devices are source-end devices.

[0246] The process of configuring the link group by the receiving-end device and compensating jointly by the receiving-end device and the source-end device may include the following steps.

[0247] C-1. Start a link between the source-end device and the receiving-end device.

[0248] C-2. The source-end device independently sends data frames to the receiving-end device through M links respectively. Correspondingly, the receiving-end device receives the data frames sent by the source-end device. It should be understood that these data frames may include alignment markers.

[0249] C-3. The source-end device sends second capability information to the receiving-end device. The second capability information is used to indicate the second capability of the source-end device to perform delayed transmission compensation for at least one of the M links. Correspondingly, the receiving-end device receives the second capability information sent by the source-end device. It should be understood that the second capability information may be carried in the data frames of C-2 or sent in other ways. This embodiment does not limit this.

[0250] C-4. The source-end device sends second status information to the receiving-end device. The second status information is used to indicate the current status of the source-end device to perform delayed transmission compensation for at least one of the M links. Correspondingly, the receiving-end device receives the second status information sent by the source-end device. It should be understood that the second status information may be carried in the data frames of C-2 or sent in other ways. This embodiment does not limit this.

[0251] C-5. The receiving-end device measures the status of the differential delay of the M links to obtain first status information.

[0252] C-6. The receiving-end device determines how to configure the link group and how to configure the delayed transmission compensation according to the first status information, the first capability information that can represent the ability of the receiving-end device to perform differential delay compensation for the M links, the second capability information, and the second status information. In the specific link group configuration, N of the M links are divided into the first link group.

[0253] C-7. The receiving-end device sends first configuration information to the source-end device. The first configuration information includes information indicating the first link group. Correspondingly, the source-end device receives the first configuration information sent by the receiving-end device.

[0254] C-8. The receiving device sends second configuration information to the source device. The second configuration information includes a configuration for instructing the source device to perform delay transmission compensation for the corresponding link. Accordingly, the source device receives the second configuration information sent by the receiving device.

[0255] C-9. The source device adjusts the link transmission delay according to the second configuration information.

[0256] C-10. The source device sends information on the updated status of the delay transmission compensation to the receiving device. On the one hand, it can prepare for the next collaborative compensation. On the other hand, it notifies the receiving device that the configuration of the delay transmission compensation has been completed.

[0257] C-11. After receiving the information sent by the source device, the receiving device re-analyzes the differential delays of each link and performs differential delay compensation on the M links. Specifically, the receiving device performs differential delay compensation according to the first configuration information, that is, sets the cache size of the differential delay. In other words, the receiving device performs differential delay compensation on the links in the first link group according to the link group configuration determined by itself. The receiving device feeds back the status of the differential delays of each link and the configuration of the link group to the source device.

[0258] C-12. The source device sends service data to the receiving device according to the first configuration information.

[0259] It should be understood that the transmission format and transmission channel of at least one of the first status information, first capability information, first configuration information, second status information, second capability information, and second configuration information between the source device and the receiving device are similar to those in Embodiment 4, and will not be elaborated here.

[0260] Embodiment 6:

[0261] In this embodiment, the first device, i.e., the decision-making device, is the receiving device, and the second device is the source device. The receiving device has the ability of delay reception compensation. The source device and at least one intermediate device have the ability of delay transmission compensation, that is, the K upstream devices include the source device and at least one intermediate device.

[0262] The process of collaborative compensation among the receiving device, the source device, and at least one intermediate device may include the following steps.

[0263] D-1. Start a link between the source device and the receiving device.

[0264] D-2. The source device independently sends data frames to the receiving device through M links respectively. Accordingly, the receiving device receives the data frames sent by the source device. It should be understood that these data frames may include alignment marks.

[0265] D-3. The receiving device measures the differential delay status of M links and obtains first status information.

[0266] D-4. The source device and at least one intermediate device send second capability information to the receiving device. The second capability information is used to indicate the second capability of each upstream device to perform delay transmission compensation for at least one of the M links. Correspondingly, the receiving device receives the second capability information sent by the source device. It should be understood that the second capability information can be carried in the data frame of D-2 or sent in other ways, and this embodiment does not limit this.

[0267] D-5. The source device and at least one intermediate device send second status information to the receiving device. The second status information is used to indicate the current status of each upstream device to perform delay transmission compensation for at least one of the M links. Correspondingly, the receiving device receives the second status information sent by the source device. It should be understood that the second status information can be carried in the data frame of D-2 or sent in other ways, and this embodiment does not limit this.

[0268] D-6. The receiving device determines how to configure the link group and how to configure the delay transmission compensation according to the first status information, the first capability information that can represent the capability of the receiving device to perform differential delay compensation for the M links, the second capability information, and the second status information. Specifically, in the link group configuration, N of the M links are divided into the first link group.

[0269] D-7. The receiving device sends first configuration information to the source device. The first configuration information includes information indicating the first link group. Correspondingly, the source device receives the first configuration information sent by the receiving device.

[0270] D-8. The receiving device sends first configuration information to the intermediate device. The first configuration information includes information indicating the first link group. Correspondingly, the intermediate device receives the first configuration information sent by the receiving device. It should be understood that D-10 is an optional step. Executing D-8 may not be used for the collaborative compensation process but for other processes.

[0271] D-9. The receiving device sends respective second configuration information to the source device and at least one intermediate device. The second configuration information includes configurations used to indicate the delay transmission compensation that the source device and at least one intermediate device should perform for the corresponding links respectively. Correspondingly, the source device and at least one intermediate device respectively receive the second configuration information sent by the receiving device.

[0272] D-10. The source device and at least one intermediate device adjust the link transmission delay according to the second configuration information, that is, set the buffer size for delay transmission.

[0273] D-11. The source device and at least one intermediate device send information on the updated status of the delayed transmission compensation to the receiving device. On the one hand, it can prepare for the next collaborative compensation, and on the other hand, it notifies the receiving device that the configuration of the delayed transmission compensation has been completed.

[0274] D-12. The receiving device re-analyzes the differential delays of each link and performs differential delay compensation on M links. Specifically, the receiving device performs differential delay compensation according to the first configuration information, that is, sets the buffer size of the differential delay. In other words, the receiving device performs differential delay compensation on the links in the first link group according to the link group configuration determined by itself. The receiving device feeds back the status of the differential delay of each link and the configuration of the link group to the source device.

[0275] D-13. The source device sends service data to the receiving device according to the first configuration information.

[0276] It should be understood that the transmission format and transmission channel of at least one of the first status information, first capability information, first configuration information, second status information, second capability information, and second configuration information between the source device and the receiving device are similar to those in Embodiment 4, and will not be elaborated here.

[0277] In Embodiment 7, Embodiment 8, and Embodiment 9, the first device, i.e., the decision-making device, is the source device, and the second device is the receiving device. The receiving device has the ability of delayed reception compensation. The K upstream devices may include the source device and / or at least one intermediate device, and have the ability of delayed transmission compensation.

[0278] S110. The first device obtains the first status information of M links between the source device and the receiving device, which may include: the first device receives the first status information sent by the receiving device; S120. The first device obtains the first capability information of the receiving device, which may include: the first device receives the first capability information sent by the receiving device.

[0279] After at least one upstream device completes the configuration of the delayed transmission compensation, Method 100 may further include: the first device transmits service data with the second device based on the first link group; the first device performs differential delay compensation on the links in the first link group that have been subjected to delayed transmission compensation by at least one upstream device according to the second configuration information according to the first configuration information.

[0280] Embodiment 7:

[0281] In this embodiment, the first device, i.e., the decision-making device, is the source device, and the second device is the receiving device. The receiving device has the ability of delayed reception compensation. There is an intermediate device with the ability of delayed transmission compensation between the receiving device and the source device, that is, the K upstream devices are at least one intermediate device.

[0282] Specifically, for the first device to obtain the second capability information and the second status information of each of the K upstream devices, it may include: the first device receiving the second capability information and the second status information sent by each of at least one intermediate device; Method 100 may further include: the first device sending second configuration information to at least some of the at least one intermediate device, where the second configuration information is used to indicate the configuration of the delay transmission compensation that at least some of the intermediate devices should perform on the corresponding links.

[0283] It should be understood that when the first device sends the second configuration information to at least some of the at least one intermediate device, it may be that the first device directly sends the second configuration information to the intermediate device, or it may be that the first device sends the second configuration information to the receiving end device, and the receiving end device forwards the second configuration information to the intermediate device. That is, the first device sending the second configuration information to the intermediate device can be either direct or indirect, and this embodiment does not limit this.

[0284] The process of the receiving end device and the intermediate device collaborating for compensation may include the following steps.

[0285] E-1, Start a link between the source device and the receiving end device.

[0286] E-2, The source device independently sends data frames to the receiving end device through M links respectively. Correspondingly, the receiving end device receives the data frames sent by the source device. It should be understood that these data frames may include alignment markers.

[0287] E-3, The receiving end device measures the differential delay status of the M links.

[0288] E-4, The receiving end device sends first status information to the source device, where the first status information is used to indicate the differential delay status of the M links. Correspondingly, the source device receives the first status information sent by the receiving end device. Optionally, the first status information may be transmitted through the shim-to-shim management channel of the OH code block in FlexE.

[0289] E-5, The receiving end device sends first capability information to the source device, where the first capability information is used to indicate the first capability of the receiving end device to perform differential delay compensation on the M links. Correspondingly, the source device receives the first capability information sent by the receiving end device. Optionally, the first capability information may be transmitted through the shim-to-shim management channel of the OH code block in FlexE.

[0290] E-6. The intermediate device sends second capability information to the source device. The second capability information is used to indicate the second capability of each intermediate device to perform delay transmission compensation for at least one of the M links. Accordingly, the source device receives the second capability information sent by the intermediate device. It should be understood that the second capability information can be carried in the data frame of E-2 or sent in other ways, and this embodiment does not limit this. Optionally, the second capability information can be transmitted through the shim-to-shim management channel of the OH code block in FlexE.

[0291] E-7. The intermediate device sends second status information to the source device. The second status information is used to indicate the current status of each intermediate device to perform delay transmission compensation for at least one of the M links. Accordingly, the source device receives the second status information sent by the intermediate device. It should be understood that the second status information can be carried in the data frame of E-2 or sent in other ways, and this embodiment does not limit this. Optionally, the second status information can be transmitted through the section management channel of the OH code block in FlexE.

[0292] E-8. The source device determines how to configure the link group and how to configure the delay transmission compensation according to the first status information, the first capability information, the second capability information, and the second status information. Specifically, in the link group configuration, N of the M links are divided into the first link group.

[0293] E-9. The source device sends first configuration information and second configuration information to the receiving device. The first configuration information includes information indicating the first link group. Accordingly, the receiving device receives the first configuration information sent by the source device.

[0294] E-10. The receiving device configures differential delay compensation according to the first configuration information, such as setting the cache for local differential delay compensation.

[0295] E-11. The receiving device sends second configuration information to the intermediate device. The second configuration information includes the configuration for indicating the delay transmission compensation that the intermediate device should perform on the corresponding link. Accordingly, the intermediate device receives the second configuration information sent by the receiving device.

[0296] E-12. The receiving device sends first configuration information to the intermediate device. The first configuration information includes information indicating the first link group. Accordingly, the intermediate device receives the first configuration information sent by the source device. It should be understood that E-12 is an optional step. Executing E-12 may not be used for the collaborative compensation process but for other processes.

[0297] E-13. The intermediate device adjusts the link transmission delay according to the second configuration information. For example, it sets the buffer for delaying data transmission.

[0298] E-14. The intermediate device sends the information on the updated current state of the delay transmission compensation to the receiving device. On the one hand, it can prepare for the next collaborative compensation. On the other hand, it notifies the receiving device that the configuration of the delay transmission compensation has been completed.

[0299] E-15. After receiving the information sent by the intermediate device, the receiving device re-analyzes the differential delays of each link and performs differential delay compensation on the M links. Specifically, the receiving device performs differential delay compensation according to the first configuration information, that is, it sets the buffer size for the differential delay. The receiving device feeds back the information indicating that the configuration has been completed to the source device.

[0300] E-16. The source device sends service data to the receiving device according to the first configuration information.

[0301] Optionally, in E-8, the source device can also determine the configuration scheme of the link group by combining the relevant information of the service data to be sent to the receiving device, such as comprehensive factors like the number of services and / or bandwidth.

[0302] It should be understood that the transmission formats and transmission channels of at least one of the first status information, first capability information, first configuration information, second status information, second capability information, and second configuration information between the source device, the intermediate device, and the receiving device are similar to those in Embodiment 4, and will not be elaborated here.

[0303] Embodiment 8:

[0304] In this embodiment, the first device, i.e., the decision-making device, is the source device, and the second device is the receiving device. The receiving device has the ability of delay receiving compensation. The source device has the ability of delay sending compensation, that is, the K upstream devices are the source devices.

[0305] Specifically, Method 100 may further include: The first device transmits service data to the second device based on the first link group according to the determined configuration of the delay sending compensation that the first device should perform on the corresponding link.

[0306] Figure 12 It is a schematic diagram of the process 400 for configuring the link group and performing compensation in this embodiment. The process 400 for collaborative compensation between the receiving device and the source device may include the following steps.

[0307] S405. Start the link between the source device and the receiving device.

[0308] S410, The source device independently sends data frames to the receiving device through M links respectively. Correspondingly, the receiving device receives the data frames sent by the source device. It should be understood that alignment markers may be included in these data frames.

[0309] S415, The receiving device measures the state of the differential delays of the M links.

[0310] S420, The receiving device sends first status information to the source device, and the first status information is used to indicate the state of the differential delays of the M links. Correspondingly, the source device receives the first status information sent by the receiving device. Optionally, the first status information can be transmitted through the shim-to-shim management channel of the OH code block in FlexE.

[0311] S425, The receiving device sends first capability information to the source device, and the first capability information is used to indicate the first capability of the receiving device to perform differential delay compensation for the M links. Correspondingly, the source device receives the first capability information sent by the receiving device. Optionally, the first capability information can be transmitted through the shim-to-shim management channel of the OH code block in FlexE.

[0312] S430, The source device determines how to configure the link group and how to configure the delayed transmission compensation according to the first status information, the first capability information, the second capability information indicating its own capability to perform delayed transmission compensation for at least one of the M links, and the second status information indicating the state of its own delayed transmission compensation for at least one of the M links. In the specific link group configuration, N of the M links are divided into the first link group.

[0313] S435, The source device adjusts the transmission delay of the corresponding link according to the configuration of the delayed transmission compensation determined in S430. For example, if S430 determines to perform delayed transmission compensation on PHY2, then in S435, the cache size of the delayed transmission compensation of PHY2 is modified.

[0314] S440, The source device sends first configuration information to the receiving device, and the first configuration information includes information indicating the first link group. Correspondingly, the receiving device receives the first configuration information sent by the source device.

[0315] S445, The receiving device configures the differential delay compensation according to the first configuration information, such as setting the local differential delay compensation cache.

[0316] S450. The receiving device sends a confirmation message indicating that the configuration is complete to the source device. Correspondingly, the source device receives the confirmation message sent by the receiving device. When the confirmation message indicates that the configuration of the delay transmission compensation of the source device is successful, S455 is executed; when the confirmation message indicates that the configuration of the delay transmission compensation of the source device fails, it returns to S430 again.

[0317] S455. The source device sends service data to the receiving device according to the first configuration information.

[0318] It should be understood that the transmission format and transmission channel of at least one of the first status information, first capability information, first configuration information, second status information, second capability information, and second configuration information between the source device and the receiving device are similar to those in Embodiment 4, and will not be elaborated here.

[0319] Embodiment 9:

[0320] In this embodiment, the first device, i.e., the decision-making device, is the source device, and the second device is the receiving device. The receiving device has the ability of delay reception compensation. The source device and at least one intermediate device have the ability of delay transmission compensation, that is, the K upstream devices include the source device and at least one intermediate device.

[0321] Specifically, Method 100 may further include: The first device transmits service data to the second device based on the first link group according to the determined configuration of the delay transmission compensation that the first device should perform on the corresponding link.

[0322] The process of collaborative compensation among the receiving device, the source device, and at least one intermediate device may include the following steps.

[0323] F-1. Start a link between the source device and the receiving device.

[0324] F-2. The source device independently sends data frames to the receiving device through M links respectively. Correspondingly, the receiving device receives the data frames sent by the source device. It should be understood that these data frames may include alignment markers.

[0325] F-3. The receiving device measures the differential delay status of the M links.

[0326] F-4. The receiving device sends the first status information to the source device, and the first status information is used to indicate the differential delay status of the M links. Correspondingly, the source device receives the first status information sent by the receiving device. Optionally, the first status information may be transmitted through the shim-to-shim management channel of the OH code block in FlexE.

[0327] F-5. The receiving device sends first capability information to the source device, and the first capability information is used to indicate the first capability of the receiving device to perform differential delay compensation on M links. Accordingly, the source device receives the first capability information sent by the receiving device. Optionally, the first capability information can be transmitted through the shim-to-shim management channel of the OH code block in FlexE.

[0328] F-6. The intermediate device sends second capability information to the source device, and the second capability information is used to indicate the second capability of each intermediate device to perform delay transmission compensation on at least one of the M links. Accordingly, the source device receives the second capability information sent by the intermediate device. It should be understood that the second capability information can be carried in the data frame of F-2 or sent in other ways, and this embodiment does not limit this. Optionally, the second capability information can be transmitted through the shim-to-shim management channel of the OH code block in FlexE.

[0329] F-7. The intermediate device sends second status information to the source device, and the second status information is used to indicate the current status of each intermediate device to perform delay transmission compensation on at least one of the M links. Accordingly, the source device receives the second status information sent by the intermediate device. It should be understood that the second status information can be carried in the data frame of F-2 or sent in other ways, and this embodiment does not limit this. Optionally, the second status information can be transmitted through the section management channel of the OH code block in FlexE.

[0330] F-8. The source device determines how to configure the link group and how to configure the delay transmission compensation according to the first status information, the first capability information, the second capability information sent by the intermediate device, the second capability information used to indicate its own capability to perform delay transmission compensation on at least one of the M links, the second status information sent by the intermediate device, and the second status information used to indicate its own status to perform delay transmission compensation on at least one of the M links. In the specific link group configuration, N of the M links are divided into the first link group.

[0331] F-9. The source device adjusts the transmission delay of the corresponding link according to the configuration of the delay transmission compensation determined in F-8. For example, if F-8 determines to perform delay transmission compensation on PHY2, then in F-9, the cache size of the delay transmission compensation of PHY2 is modified.

[0332] F-10. The source device sends first configuration information and second configuration information to the receiving device, and the first configuration information includes information indicating the first link group. Accordingly, the receiving device receives the first configuration information sent by the source device.

[0333] F-11. The receiving-end device configures differential delay compensation according to the first configuration information, for example, sets the buffer for local differential delay compensation.

[0334] F-12. The receiving-end device sends the second configuration information to the intermediate device. The second configuration information includes the configuration for instructing the intermediate device to perform delay transmission compensation on the corresponding link. Correspondingly, the intermediate device receives the second configuration information sent by the receiving-end device.

[0335] F-13. The receiving-end device sends the first configuration information to the intermediate device. The first configuration information includes the information indicating the first link group. Correspondingly, the intermediate device receives the first configuration information sent by the source-end device. It should be understood that F-13 is an optional step. Executing F-13 may not be used for the collaborative compensation process, but for other processes.

[0336] F-14. The intermediate device adjusts the link transmission delay according to the second configuration information. For example, it sets the buffer for delaying data transmission.

[0337] F-15. The intermediate device sends the information on the updated current state of the delay transmission compensation to the receiving-end device. On the one hand, it can prepare for the next collaborative compensation. On the other hand, it notifies the receiving-end device that the configuration of the delay transmission compensation has been completed.

[0338] F-16. After receiving the information sent by the intermediate device, the receiving-end device performs differential delay compensation on the M links. Specifically, the receiving-end device performs differential delay compensation according to the first configuration information, that is, sets the buffer size of the differential delay. The receiving-end device sends the information indicating that the configuration has been completed to the source-end device.

[0339] F-17. The source-end device sends service data to the receiving-end device according to the first configuration information.

[0340] It should be understood that the transmission format and transmission channel of at least one of the first state information, first capability information, first configuration information, second state information, second capability information, and second configuration information among the source-end device, intermediate device, and receiving-end device are similar to those in Embodiment 4, and will not be elaborated here.

[0341] In Embodiment 10, the first device, i.e., the decision-making device, is the management device, and the second device includes the receiving-end device and / or the source-end device. The receiving-end device has the ability of delay reception compensation. The K upstream devices may include the source-end device and / or at least one intermediate device, and have the ability of delay transmission compensation.

[0342] Specifically, S110 where the first device obtains first status information of M links between the source device and the receiving device may include: the first device receives the first status information sent by the receiving device; S120 where the first device obtains first capability information of the receiving device may include: the first device receives the first capability information sent by the receiving device; the first device obtains second capability information and second status information of each of the K upstream devices, which may include: the first device receives the second capability information and second status information sent by each upstream device; Method 100 may further include: the first device sends second configuration information to at least one of the K upstream devices, and the second configuration information is used to instruct at least one upstream device to perform configuration of delay transmission compensation for the corresponding link.

[0343] The process of the management device making decisions on link group configuration and the receiving device and other devices collaborating for compensation may include the following steps.

[0344] G-1, Start the link between the source device and the receiving device.

[0345] G-2, The source device independently sends data frames to the receiving device through M links respectively. Correspondingly, the receiving device receives the data frames sent by the source device. It should be understood that these data frames may include alignment markers.

[0346] G-3, The receiving device measures the status of the differential delay of M links.

[0347] G-4, The receiving device sends first status information to the management device, and the first status information is used to indicate the status of the differential delay of M links. Correspondingly, the management device receives the first status information sent by the receiving device.

[0348] G-5, The receiving device sends first capability information to the management device, and the first capability information is used to indicate the first capability of the receiving device to perform differential delay compensation for M links. Correspondingly, the management device receives the first capability information sent by the receiving device.

[0349] G-6, The source device and / or at least one intermediate device sends second capability information to the management device, and the second capability information is used to indicate the second capability of each upstream device to perform delay transmission compensation for at least one of the M links. Correspondingly, the management device receives the second capability information sent by the source device and / or at least one intermediate device. It should be understood that the second capability information corresponding to the source device may be carried in the data frame of G-2 or sent in other ways, and this embodiment does not limit this. Optionally, the second capability information may be transmitted through the shim-to-shim management channel of the OH code block in FlexE.

[0350] G-7. The source device and / or at least one intermediate device send second status information to the management device. The second status information is used to indicate the current status of at least one link in the M links for which each upstream device performs delay transmission compensation. Correspondingly, the management device receives the second status information sent by the source device and / or at least one intermediate device. It should be understood that the second status information corresponding to the source device can be carried in the data frame of G-2 or sent by other means, and this embodiment does not limit this. Optionally, the second status information can be transmitted through the section management channel of the OH code block in FlexE.

[0351] G-8. The management device determines how to configure the link group and how to configure the delay transmission compensation according to the first status information, the first capability information, the second status information, and the second capability information. Specifically, the configuration includes dividing N links out of the M links into the first link group.

[0352] G-9. The management device sends second configuration information to the upstream devices (including the source device and / or at least one intermediate device) among the K upstream devices that need to perform delay transmission compensation configuration, for indicating the configuration of the delay transmission compensation.

[0353] G-10. The upstream devices (including the source device and / or at least one intermediate device) among the K upstream devices that need to perform delay transmission compensation configuration configure the cache size of the delay transmission compensation according to the second configuration information.

[0354] G-11. The upstream devices (including the source device and / or at least one intermediate device) among the K upstream devices that need to perform delay transmission compensation configuration return confirmation information to the management device, for indicating that the above second configuration information has been received and the corresponding configuration has been performed. Correspondingly, the management device receives the confirmation information returned by the source device and / or the receiving device. It should be understood that G-11 is an optional step.

[0355] G-12. After receiving the confirmation information, the management device sends the first configuration information and the second configuration information to the receiving device. The first configuration information includes information for indicating the first link group. Correspondingly, the receiving device receives the first configuration information and the second configuration information sent by the management device. Optionally, the first configuration information may further include the cache requirements for the receiving device to perform differential delay compensation for each link, and the receiving device directly sets the cache amount for each link according to the cache requirements.

[0356] G-13. The receiving device performs corresponding configuration according to the first configuration information and the second configuration information.

[0357] G-14. The receiving device may return an acknowledgment message to the management device to indicate that the above first configuration information and second configuration information have been received and corresponding configurations have been made. Correspondingly, the management device receives the acknowledgment message returned by the receiving device. It should be understood that G-13 is an optional step.

[0358] G-15. After the management device receives the acknowledgment message returned by the receiving device, it sends the first configuration information to the source device. It should be understood that G-15 is an optional step.

[0359] G-16. The source device sends service data to the receiving device according to the first configuration information.

[0360] It should be understood that the communication between the source device and the receiving device and the management device regarding the first status information, first capability information, first configuration information, second status information, second capability information, and second configuration information can be transmitted in the management channel of the OH code block of each device and the management device. Optionally, in FlexO, the above information can be transmitted in the GCC0 byte of the OH code block in GFP format, HDLC format, PPP format, or in the RES field in a custom frame format. In FlexE, the above information can be transmitted in the management channel of the OH code block in the form of Internet Protocol (IP) packets. The specific transmission method in this embodiment is not limited.

[0361] In each embodiment of the present application, the source device, the receiving device, and may also include intermediate devices, etc., may all have the ability of differential delay compensation or delayed transmission compensation. Each embodiment of the present application is applied to each device, and the compensation of the link group is achieved through capability negotiation. So that when the compensation capabilities of the devices in the FlexE Group or FlexO Group between the source device and the receiving device cannot compensate for the differential delays of each link, by configuring the link group, the source device only bears cross-link transmission service data on the delay-aligned links.

[0362] It should be understood that in each embodiment of the present application, when transmitting any one of the first status information, first capability information, second status information, second capability information, first configuration information, second configuration information, and acknowledgment information, the status, capability, or configuration information corresponding to the link can be transmitted on each link, that is, the relevant information is transmitted in terms of the link granularity. Of course, each embodiment of the present application can also transmit the relevant information in other granularities, for example, in terms of the device granularity, which is not limited here.

[0363] The method for configuring a link group provided by the embodiments of the present application is described above. The device for configuring a link group provided by the embodiments of the present application will be described below.

[0364] Figure 13FIG. 0 is a schematic block diagram of a device 500 for configuring a link group according to an embodiment of the present application. The device 500 for configuring the link group is a first device, such as Figure 13 As shown, the device 500 for configuring the link group may include:

[0365] An obtaining module 510, configured to obtain first status information of M links between a source device and a receiving device, where the first status information is used to indicate a status of a differential delay between any two of the M links, and any one of the M links is a Flexible Ethernet (FlexE) physical connection link or a Flexible Optical Transport Network (FlexO) physical connection link, where M is an integer greater than or equal to 2.

[0366] The obtaining module 510 is further configured to obtain first capability information of the receiving device, where the first capability information is used to indicate a first capability of the receiving device to perform differential delay compensation on the M links.

[0367] A processing module 520, configured to divide N links among the M links into a first link group according to the first status information obtained by the obtaining module 510 and the first capability information obtained by the obtaining module 510, where N is an integer less than or equal to M and greater than or equal to 2.

[0368] A sending module 530, configured to send first configuration information to a second device, where the first configuration information includes information for indicating the first link group.

[0369] The device for configuring a link group according to the embodiment of the present application divides N links among the M links into a first link group according to the status of the differential delay of the M links between the source device and the receiving device and the capability of the receiving device to perform differential delay compensation on the M links, thereby avoiding the situation where all M links are unavailable when the differential delay of the M links exceeds the differential delay compensation capability of the receiving device, and improving the availability and robustness of the links in the transport network.

[0370] Optionally, as an alternative embodiment, the first device is the receiving device, the second device is the source device, and the obtaining module 510 is specifically configured to: measure the differential delay of the M links to obtain the first status information; the device 500 further includes: a compensation module 540, configured to perform differential delay compensation on the links in the first link group according to the first configuration information; and a transmission module 550, configured to transmit service data with the second device based on the first link group.

[0371] Optionally, as an alternative embodiment, the obtaining module 510 is specifically configured to: receive the first status information sent by the receiving-end device; receive the first capability information sent by the receiving-end device.

[0372] Optionally, as an alternative embodiment, the first device is the source-end device, and the second device is the receiving-end device; or the first device is a management device, and the second device includes the receiving-end device and / or the source-end device.

[0373] Optionally, as an alternative embodiment, among the M links, K upstream devices of the receiving-end device have the ability to perform delay transmission compensation, where K is a positive integer, and the K upstream devices include the source-end device and / or at least one intermediate device. The intermediate device is located between the source-end device and the receiving-end device among the M links. The obtaining module 510 is further configured to: obtain the second capability information and the second status information of each of the K upstream devices. The second capability information is used to indicate the second capability of each upstream device to perform delay transmission compensation on at least one of the M links, and the second status information is used to indicate the current status of each upstream device to perform delay transmission compensation on at least one of the M links; the processing module 520 is specifically configured to: divide the N links among the M links into the first link group according to the first status information, the first capability information, the second status information, and the second capability information; the processing module 520 is further configured to: determine the configuration of the delay transmission compensation that each upstream device should perform on the corresponding link according to the first status information, the first capability information, the second status information, and the second capability information.

[0374] It should be understood that when the M links cannot be aligned at the receiving-end device, the M links cannot form a link group, or in other words, the FlexE Group or FlexO Group crashes and cannot work. The source-end device, the receiving-end device, and may also include intermediate devices, etc. in the embodiments of the present application may all have the ability of differential delay compensation or delay transmission compensation. The devices in the embodiments of the present application achieve link group compensation through capability negotiation. When the compensation capabilities of the devices in the FlexE Group or FlexO Group between the source-end device and the receiving-end device cannot compensate for the differential delays of the links, by configuring the link group, the source-end device only bears cross-link transmission service data on the delay-aligned links; or through the collaborative compensation of each device, the final M links can be aligned at the receiving-end device, which can ensure the operation of the FlexE Group or FlexO Group and improve the utilization rate of the links.

[0375] Optionally, as an alternative embodiment, the first device is the receiving-end device, the second device is the source-end device, and the obtaining module 510 is specifically configured to: measure the differential delay of the M links to obtain the first status information; receive the second capability information and the second status information sent by each upstream device; the sending module 530 is further configured to: send second configuration information to at least one of the K upstream devices, where the second configuration information is used to instruct the at least one upstream device to perform configuration for delay transmission compensation on the corresponding link.

[0376] Optionally, as an alternative embodiment, the device 500 may further include: a compensation module 540, configured to perform differential delay compensation on the links in the first link group that have been subjected to delay transmission compensation by the at least one upstream device according to the second configuration information according to the first configuration information; a transmission module 550, configured to transmit service data with the second device based on the first link group.

[0377] Optionally, as an alternative embodiment, the first device is the source-end device, the second device is the receiving-end device, and the obtaining module 510 may specifically be configured to: receive the first status information sent by the receiving-end device; receive the first capability information sent by the receiving-end device.

[0378] Optionally, as an alternative embodiment, the first device is included in the K upstream devices, and the device 500 may further include: a transmission module 540, configured to transmit service data to the second device based on the first link group according to the determined configuration for delay transmission compensation that the first device should perform on the corresponding link.

[0379] Optionally, as an alternative embodiment, at least one intermediate device is included in the K upstream devices, and the obtaining module 510 is specifically configured to: receive the second capability information and the second status information sent by each of the at least one intermediate devices; the sending module 530 is further configured to: send second configuration information to at least some of the at least one intermediate devices, where the second configuration information is used to instruct the at least some intermediate devices to perform configuration for delay transmission compensation on the corresponding link.

[0380] Optionally, as an alternative embodiment, the first device is a management device, and the second device includes the receiving-end device and / or the source-end device. The obtaining module 510 may specifically be configured to: receive the first status information sent by the receiving-end device; receive the first capability information sent by the receiving-end device; receive the second capability information and the second status information sent by each upstream device; The sending module 530 may further be configured to: send second configuration information to at least one upstream device among the K upstream devices, where the second configuration information is used to instruct the at least one upstream device to perform configuration of delay transmission compensation for the corresponding link.

[0381] Optionally, as an alternative embodiment, the first configuration information includes a flag indicating that the link belongs to the first link group.

[0382] Optionally, as an alternative embodiment, the sending module 530 may specifically be configured to: send the first configuration information to the second device by carrying it in a reserved field of an overhead code block.

[0383] Optionally, as an alternative embodiment, the sending module 530 may specifically be configured to: send the first configuration information indicating that the first link among the N links belongs to the first link group to the second device through the first link.

[0384] Optionally, as an alternative embodiment, the first part of the bits in the first configuration information is used to indicate that the first link forms the first link group with other links, and the second part of the bits in the first configuration information is the flag of the first link group.

[0385] Optionally, as an alternative embodiment, the obtaining module 510 is specifically configured to: receive the first status information sent by the receiving-end device and carried in a first type-length-value (TLV) unit in the link layer discovery protocol (LLDP) format of the management channel of the overhead code block.

[0386] Optionally, as an alternative embodiment, the first TLV unit can further carry information indicating the current status of the receiving-end device performing delay transmission compensation for the M links when the receiving-end device sends service data to the source-end device.

[0387] Optionally, as an alternative embodiment, the first TLV unit can further carry information indicating the configuration of the upstream device performing delay transmission compensation for the corresponding link.

[0388] Optionally, as an alternative embodiment, the obtaining module 510 is specifically configured to: receive the first capability information carried in a type-length-value (TLV) unit in the link layer discovery protocol (LLDP) format of the management channel of the overhead code block and sent by the receiving end device.

[0389] Optionally, as an alternative embodiment, the second TLV unit is further capable of carrying information indicating the capability of the receiving end device to perform delay transmission compensation on the M links when the receiving end device sends service data to the source end device.

[0390] It should be understood that some functions of the obtaining module 510 in the embodiments of the present application can be implemented by a processor or processor-related circuit components, some functions of the obtaining module 510 can be implemented by a network interface or network interface-related circuit components, the processing module 520 can be implemented by a processor or processor-related circuit components, and the sending module 530 can be implemented by a network interface or network interface-related circuit components.

[0391] As Figure 14 shown, an embodiment of the present application further provides a device 600 for configuring a link group. The device 600 for configuring a link group is a first device. The device 600 for configuring a link group includes a processor 610, a memory 620, and a network interface 630. The memory 620 is used to store instructions, and the processor 610 and the network interface 630 are used to execute the instructions stored in the memory 620.

[0392] When the processor 610 and the network interface 630 of the device 600 for configuring a link group execute the instructions stored in the memory 620, it is caused that:

[0393] The first device obtains first status information of M links between a source end device and a receiving end device. The first status information is used to indicate the status of the differential delay between any two of the M links. Any one of the M links is a flexible Ethernet (FlexE) physical connection link or a flexible optical transport network (FlexO) physical connection link, where M is an integer greater than or equal to 2;

[0394] The first device obtains first capability information of the receiving end device. The first capability information is used to indicate the first capability of the receiving end device to perform differential delay compensation on the M links;

[0395] The first device divides N links among the M links into a first link group according to the first status information and the first capability information, where N is an integer less than or equal to M and greater than or equal to 2;

[0396] The first device sends first configuration information to the second device, and the first configuration information includes information for indicating the first link group.

[0397] In the device for configuring a link group according to an embodiment of the present application, based on the state of the differential delays of M links between the source device and the receiving device and the ability of the receiving device to perform differential delay compensation on the M links, N links among the M links are divided into a first link group, thereby avoiding the situation where all M links are unavailable when the differential delays of the M links exceed the differential delay compensation ability of the receiving device, and improving the availability and robustness of the links in the transport network.

[0398] It should be understood that Figure 13 the device 500 for configuring a link group shown or Figure 14 the device 600 for configuring a link group shown can be used to perform operations or processes related to the terminal device in the above method embodiments, and the operations and / or functions of each module in the device 500 for configuring a link group or the device 600 for configuring a link group are respectively for implementing the corresponding processes in the above method embodiments. For the sake of brevity, they will not be elaborated here.

[0399] It should be understood that the processor mentioned in the embodiments of the present invention may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0400] It should also be understood that the memory mentioned in the embodiments of the present invention may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink dynamic random access memory (SLDRAM), and direct rambus random access memory (DR RAM).

[0401] It should be noted that when the processor is a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, the memory (storage module) is integrated in the processor.

[0402] It should be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0403] The embodiments of the present invention also provide a computer-readable storage medium, on which instructions are stored. When the instructions are run on a computer, the computer is caused to execute the method of configuring a link group in the above method embodiments. Specifically, the computer may be the device for configuring a link group as described above, that is, the first device.

[0404] The embodiments of the present invention also provide a computer program product including instructions, characterized in that when a computer runs the instructions of the computer program product, the computer executes the method of configuring a link group in the above method embodiments. Specifically, the computer program product may run on the device for configuring a link group as described above, that is, the first device.

[0405] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more integrated available media. The available medium can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a Digital Video Disc (DVD)), or a semiconductor medium (such as a Solid State Disk (SSD)), etc.

[0406] It should be understood that the first, second, and various numerical numbers involved herein are only for the convenience of description and are not used to limit the scope of the present application.

[0407] It should be understood that the term "and / or" herein is merely an association relationship describing associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " herein generally represents an "or" relationship between the associated objects before and after.

[0408] It should be understood that in various embodiments of the present application, the magnitudes of the sequence numbers of the above processes do not mean the order of execution. The order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

[0409] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0410] Those skilled in the art can clearly understand that for the convenience and conciseness of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

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

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

[0413] In addition, the functional units in each embodiment of this application can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.

[0414] As described above, it is only the specific implementation manner of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application, and all should be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

1. A method for capability discovery. There are M links between a source device and a receiving device, where M is an integer greater than or equal to 2. Characterized in that: It includes: The first device receives first capability information carried in a second type-length-value (TLV) unit in the Link Layer Discovery Protocol (LLDP) format of the management channel of an overhead code block and sent by the receiving device. The first capability information is used to indicate a first capability of the receiving device to perform differential delay compensation on the M links. The first device obtains the first capability of the M links to perform differential delay compensation according to the first capability information.

2. The method according to claim 1, Characterized in that: The second TLV includes a TLV type field, a TLV length field, an organizationally unique identifier field, a subtype field, a capability field for differential delay compensation, and a buffer size field for the receiving direction.

3. The method according to claim 2, Characterized in that: One bit value in the capability field for differential delay compensation being "0" indicates that the buffer size for the receiving direction is the default value. When the bit value is "1", the value of the buffer size field for the receiving direction represents the number of code blocks.

4. The method according to claim 1, Characterized in that: The second TLV includes a TLV type field, a TLV length field, an organizationally unique identifier field, a subtype field, a result field for differential delay, and a delay amount field for differential delay.

5. The method according to claim 4, Characterized in that: The result field for differential delay represents the result of the current differential delay in the receiving direction, and the delay amount field for differential delay represents the delay amount of the differential delay.

6. The method according to claim 1, Characterized in that: The second TLV includes a TLV type field, a TLV length field, an organizationally unique identifier field, a subtype field, a compensation capability field for the link, a buffer size field for the receiving direction, and a buffer size field for the sending direction.

7. The method according to claim 1, Characterized in that: The second TLV unit can also carry information used to indicate the capability of the receiving device to perform delay transmission compensation on the M links when the receiving device sends service data to the source device.

8. A method for status discovery. There are M links between a source device and a receiving device, where M is an integer greater than or equal to 2. Characterized in that: It includes: The first device receives first status information carried in a first type-length-value (TLV) unit in the Link Layer Discovery Protocol (LLDP) format of the management channel of an overhead code block and sent by the receiving device. The first status information is used to indicate the status of the differential delay between any two of the M links. The first device obtains the status of the differential delay between any two of the M links according to the first status information.

9. The method according to claim 8, Characterized in that: The first TLV unit is further capable of carrying information indicating a current state of the receiving end device performing differential delay compensation on the M links when the receiving end device sends service data to the source end device.

10. The method according to claim 8 or 9, wherein, the first TLV unit is further capable of carrying information indicating a configuration of the upstream device performing differential delay compensation on the corresponding link.

11. A capability discovery device, applied to a first device, where there are M links between a source end device and a receiving end device, and M is an integer greater than or equal to 2, wherein, it includes: a receiving module, configured to receive first capability information carried in a second type length value (TLV) unit in a link layer discovery protocol (LLDP) format of a management channel of an overhead code block and sent by the receiving end device, where the first capability information is used to indicate a first capability of the receiving end device performing differential delay compensation on the M links; a processing module, configured to obtain a first capability of the M links performing differential delay compensation according to the first capability information.

12. The device according to claim 11, wherein, the second TLV includes a TLV type field, a TLV length field, an organization unique identifier field, a subtype field, a differential delay compensation capability field, and a receive direction buffer size field.

13. The device according to claim 12, wherein, a bit value of "0" in the differential delay compensation capability field indicates that the receive direction buffer size is a default value, and when the bit value is "1", a value of the receive direction buffer size field represents the number of code blocks.

14. The device according to claim 11, wherein, the second TLV includes a TLV type field, a TLV length field, an organization unique identifier field, a subtype field, a differential delay result field, and a differential delay amount field.

15. The device according to claim 14, wherein, the differential delay result field represents a result of a current differential delay in the receive direction, and the differential delay amount field represents an amount of differential delay.

16. The device according to claim 11, wherein, the second TLV includes a TLV type field, a TLV length field, an organization unique identifier field, a subtype field, a link compensation capability field, a receive direction buffer size field, and a transmit direction buffer size field.

17. The device according to claim 11, wherein, the second TLV unit is further capable of carrying information indicating a capability of the receiving end device performing differential delay compensation on the M links when the receiving end device sends service data to the source end device.

18. A state discovery device, where there are M links between a source end device and a receiving end device, and M is an integer greater than or equal to 2, wherein, it includes: A receiving module, configured to receive first status information carried in a first type-length-value (TLV) unit in a link layer discovery protocol (LLDP) format of an overhead code block management channel and sent by a receiving-end device, where the first status information is used to indicate the status of the differential delay between any two of the M links; A processing module, configured to obtain the status of the differential delay between any two of the M links according to the first status information.

19. The device according to claim 18, wherein, the first TLV unit can further carry information indicating the current status of the delay transmission compensation performed by the receiving-end device on the M links when the receiving-end device sends service data to the source-end device.

20. The device according to claim 18 or 19, wherein, the first TLV unit can further carry information indicating the configuration of the delay transmission compensation that an upstream device should perform on a corresponding link.

Images