WO2018196600A1 - 配置链路组的方法和设备 - Google Patents

配置链路组的方法和设备 Download PDF

Info

Publication number
WO2018196600A1
WO2018196600A1 PCT/CN2018/082469 CN2018082469W WO2018196600A1 WO 2018196600 A1 WO2018196600 A1 WO 2018196600A1 CN 2018082469 W CN2018082469 W CN 2018082469W WO 2018196600 A1 WO2018196600 A1 WO 2018196600A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
links
receiving
link
compensation
Prior art date
Application number
PCT/CN2018/082469
Other languages
English (en)
French (fr)
Inventor
梅理
钟其文
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to KR1020197034789A priority Critical patent/KR102271493B1/ko
Priority to JP2019558743A priority patent/JP6831927B2/ja
Priority to EP21190454.5A priority patent/EP3975469A1/en
Priority to EP18791648.1A priority patent/EP3609115B1/en
Publication of WO2018196600A1 publication Critical patent/WO2018196600A1/zh
Priority to US16/665,675 priority patent/US11082332B2/en
Priority to US17/390,345 priority patent/US11570088B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/24—Multipath
    • H04L45/245—Link aggregation, e.g. trunking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B10/00—Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/25—Arrangements specific to fibre transmission
    • H04B10/2575—Radio-over-fibre, e.g. radio frequency signal modulated onto an optical carrier
    • H04B10/25752—Optical arrangements for wireless networks
    • H04B10/25753—Distribution optical network, e.g. between a base station and a plurality of remote units
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J14/00—Optical multiplex systems
    • H04J14/02—Wavelength-division multiplex systems
    • H04J14/0227—Operation, administration, maintenance or provisioning [OAMP] of WDM networks, e.g. media access, routing or wavelength allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H04J3/1605—Fixed allocated frame structures
    • H04J3/1652—Optical Transport Network [OTN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H04J3/1605—Fixed allocated frame structures
    • H04J3/1652—Optical Transport Network [OTN]
    • H04J3/1658—Optical Transport Network [OTN] carrying packets or ATM cells
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0852—Delays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/14—Multichannel or multilink protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks

Definitions

  • the present application relates to the field of transport networks and, more particularly, to a method and apparatus for configuring a link set.
  • links multiple physical link links (hereinafter referred to as “links") are bound to one logical link through Link Aggregation Group (LAG) technology to increase Bandwidth and increase link availability.
  • LAG Link Aggregation Group
  • the LAG technology generally binds the physical connection links with the same S bandwidth rate R between adjacent devices to a bandwidth rate of S*R LAG, so as to achieve a linear increase in the bandwidth rate, thereby meeting the bandwidth growth requirement.
  • the LAG appears as a logical interface.
  • the transmission device can classify packets from the MAC layer according to the source MAC address and/or the destination MAC address or the virtual local area network (VLAN) label to distinguish different services. For example, a packet whose source MAC address is the same as the destination MAC address belongs to the same service, and multiple services are allocated to a specific link of the LAG after being processed by the hash algorithm.
  • VLAN virtual local area network
  • Flexible Ethernet (FlexE) or Flexible OTN (FlexO) can form a link aggregation group through link binding cascading to support parallel transmission across multiple links to carry at least one service.
  • the OTN refers to an optical transport network (Optical Transport Network). Since services are transmitted across links, differential delay compensation is required for the transmission delay of each link to align the services transmitted in parallel on multiple links. The differential delay compensation capability of the receiving device is limited in practice. If the differential delay of a link exceeds the differential delay compensation capability of the receiving device, the entire link aggregation group will be invalid.
  • the present application provides a method and apparatus for configuring a link group, which can improve the availability and robustness of links in the transport network.
  • the first aspect provides a method for configuring a link group, where the first device obtains first state information of M links between a source device and a sink device, where the first state information is used to indicate a state of differential delay between any two of the M links, any one of the M links being a flexible Ethernet FlexE physical connection link or a flexible optical transport network FlexO physical connection chain a path, where M is an integer greater than or equal to 2; the first device acquires first capability information of the receiving device, and the first capability information is used to indicate that the receiving device is configured to the M chain a first capability of performing differential delay compensation; the first device, according to the first state information and the first capability information, dividing N links of the M links into a first link group And 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 the second device, where the first configuration information includes, for indicating the first link group information.
  • the first device is a decision device that determines a link group division manner
  • the second device includes a related device that completes the link group configuration with the decision device.
  • the method for configuring a link group in the first aspect is applied to a case where M links cannot be aligned at the receiving end device, or a differential delay compensation for the M links of the receiving end device A capability cannot achieve the alignment of M links.
  • the first device is capable of performing differential delay compensation on M links according to a state of differential delay of M links between the source device and the sink device, and Dividing N links of the M links into the first link group, thereby avoiding the case where all the M links are unavailable when the differential delay of the M links exceeds the differential delay compensation capability of the receiving end device. It can improve the availability and robustness of links in the transport network.
  • the first device is the receiving end device
  • the second device is the source device
  • the first device obtains a source device and a receiving device
  • the method further includes: the first device Performing differential delay compensation on the link in the first link group according to the first configuration information; the first device transmits service data to the second device based on the first link group.
  • the configuration of the link group is determined by the receiving device as the decision device, which is simple and convenient to perform, and the signaling overhead is small when the link group is configured.
  • the acquiring, by the first device, the first status information of the M links between the source device and the receiving device includes: receiving, by the first device, the receiving The first state information sent by the terminal device; the first device acquiring the first capability information of the receiving device, where the first device receives the first capability information sent by the receiving device.
  • the first device is the source device
  • the second device is the receiving device.
  • the source device is used as the decision device
  • the configuration of the link group may be determined by combining related information of the service data, such as the number of services and/or bandwidth.
  • the first device is a management device
  • the second device includes the receiving device and/or the source device.
  • the management device is used as the decision device, and the related information of the source device and the receiving device can be received, and the configuration of the link group can be determined by considering a combination of factors such as the number of services and/or bandwidth; In order to avoid the amount of computation that may be caused by the source device or the receiving device to make a decision, the burden on the source device and the sink device can be reduced.
  • the K upstream devices of the receiving device have the capability of delaying transmission compensation, where K is a positive integer, and the K
  • the upstream device includes the source device and/or at least one intermediate device, and the intermediate device is located between the source device and the receiving device on the M links, and the method further includes: The first device acquires second capability information and second state information of each of the K upstream devices, where the second capability information is used to indicate that each of the upstream devices is in the M links.
  • the at least one link performs a second capability of delaying transmission compensation, and the second state information is used to indicate that the upstream device performs a delayed transmission compensation current state on at least one of the M links; Decoding, by the first device, the N links of the M links to the first link group according to the first state information and the first capability information, including: the first device according to the First state information, the first capability And the second status information and the second capability information, the N links in the M links are divided into the first link group; the method further includes: the Determining, by the device, the delayed transmission compensation that each upstream device should perform on the corresponding link according to the first state information, the first capability information, the second state information, and the second capability information Configuration.
  • the source device and the receiving device in the embodiments of the present application also The device may include the capability of differential delay compensation or delayed transmission compensation.
  • each device implements link group compensation through capability negotiation.
  • the link group is configured so that the source device only delays the aligned link.
  • the uplink carries the service data across the links; or through the cooperative compensation of the devices, the final M links can be aligned at the receiving end device, which can ensure the work of the FlexE Group or the FlexO Group, and can improve the link utilization.
  • the first device is the receiving end device
  • the second device is the source device
  • the first device obtains a source device and a receiving device
  • the first state information of the M links between the first device : the first device measures the differential delay of the M links, and obtains the first state information; the first device acquires the K upstream
  • the second capability information and the second state information of each upstream device of the device including: the first device receiving the second capability information and the second state information sent by each of the upstream devices;
  • the method further includes: sending, by the first device, second configuration information to at least one of the K upstream devices, where the second configuration information is used to indicate that the at least one upstream device should delay the corresponding link Send the compensated configuration.
  • the method further includes: the first device, according to the first configuration information, according to the at least one upstream device in the first link group And performing, by the second configuration information, a link that delays transmission compensation to perform differential delay compensation; and the first device transmits service data to the second device based on the first link group.
  • the first device is the source device
  • the second device is the receiving device
  • the first device acquires a source device and a receiving device.
  • the first state information of the M links, the first device receiving the first state information sent by the receiving device, and the first device acquiring the first capability of the receiving device
  • the information includes: the first device receiving the first capability information sent by the receiving device.
  • the first device is included in the K upstream devices, and the method further includes: determining, by the first device, the corresponding chain according to the determined first device The configuration of the delayed transmission compensation that the path should perform, based on the first link group, transmitting service data to the second device.
  • the K upstream devices include at least one intermediate device, where the first device acquires second capability information and a second capability of each of the K upstream devices
  • the second state information includes: the first device receives the second capability information and the second state information that are sent by each of the at least one intermediate device; the method further includes: the first The device sends second configuration information to at least a part of the at least one intermediate device, where the second configuration information is used to indicate a configuration of the delayed transmission compensation that the at least part of the intermediate devices should perform on the corresponding link.
  • the first device is a management device
  • the second device includes the receiving device, and/or the source device, where the first device acquires a source
  • the first state information of the M links between the device and the receiving device includes: the first device receiving the first state information sent by the receiving device, and the first device acquiring the receiving end
  • the first capability information of the device includes: the first device receiving the first capability information sent by the receiving device, and the first device acquiring a second capability of each upstream device of the K upstream devices
  • the information and the second state information include: the first device receives the second capability information and the second state information that are sent by each of the upstream devices, and the method further includes: the first device The at least one upstream device of the K upstream devices sends the second configuration information, where the second configuration information is used to indicate a configuration of the delayed transmission compensation that the at least one upstream device should perform on the corresponding link.
  • the first configuration information includes a flag indicating that the link belongs to the first link group.
  • the sending, by the first device, the first configuration information to the second device includes: the first device carrying the first configuration information in a reserved field of the overhead code block Transmitted to the second device.
  • the sending, by the first device, the first configuration information to the second device includes: the first device is used to indicate the first one of the N links
  • the first configuration information that belongs to the first link group is sent to the second device by using the first link.
  • the first part of the first configuration information is used to indicate that the first link and other links form the first link group, where the first The second part of the bits in the configuration information is the label of the first link group.
  • the receiving, by the first device, the first status information that is sent by the receiving device the first device receiving, by the receiving device, The first state information in the first type length value TLV unit of the link layer discovery protocol LLDP format of the management channel of the overhead code block.
  • the first TLV unit is further configured to be configured to indicate, when the receiving end device sends service data to the source device, The M links perform information on the current state of delayed transmission compensation.
  • the first TLV unit is further capable of carrying information indicating a configuration of the delayed transmission compensation that the upstream device should perform on the corresponding link.
  • the receiving, by the first device, the first capability information that is sent by the receiving device includes: receiving, by the first device, by the receiving device, The first capability information in the second type length value TLV unit of the link layer discovery protocol LLDP format of the management channel of the overhead code block.
  • the second TLV unit is further configured to be configured to indicate that when the receiving end device sends service data to the source device, the receiving end device Information on the ability of M links to delay transmission of compensation.
  • the second aspect provides a device for configuring a link group, where the device of the link group is a first device, and is used to perform the method in any one of the foregoing first aspect or the first aspect.
  • the device configuring the link group may comprise means for performing the method of the first aspect or any of the possible implementations of the first aspect.
  • the third aspect provides a device for configuring a link group, where the device of the link group is a first device, and the device for configuring the link group includes a processor, a memory, and a network interface, where the memory is used to store an instruction.
  • the processor and network interface are for executing instructions stored by the memory, and execution of instructions stored in the memory causes the processor and network interface to perform any of the first aspect or any possible implementation of the first aspect The method in the way.
  • a fourth aspect provides a device for configuring a link group, where the device of the link group is a first device, and the device for configuring the link group includes a processor, a memory, and a network interface, where the memory is used to store an instruction.
  • the processor and the network interface are configured to execute the instructions stored by the memory, and the execution of the instructions stored in the memory is such that the first device acquires the M links between the source device and the sink device a state information, the first state information is used to indicate a state of differential delay between any two of the M links, and any one of the M links is a flexible Ethernet FlexE a 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 acquires first capability information of the receiving device, and the first capability information is used by a first capability for instructing the receiving end device to perform differential delay compensation on the M links; the first device, according to the first state information and the first capability information, the M links in The N links are divided into the first link group,
  • a fifth aspect provides a computer storage medium having stored thereon instructions that, when executed on a computer, cause the computer to perform the method of any of the first aspect or the first aspect of the first aspect .
  • a sixth aspect provides a computer program product comprising instructions, when the computer runs the finger of the computer program product, the computer performs the method of any of the first aspect or the first aspect of the first aspect .
  • any one of the first state information, the first capability information, the second state information, the second capability information, the first configuration information, and the second configuration information is involved.
  • the status, capability, or configuration information corresponding to the link may be transmitted on each link, that is, the related information is transmitted at the granularity of the link.
  • the aspects of the present application and their corresponding implementations may also transmit related information at other granularities, for example, by using a device as a granularity, which is not limited herein.
  • differential delay compensation refers to delayed reception compensation, that is, compensation in the receiving direction, which is also generally referred to as “deskew”; delayed transmission compensation, that is, compensation in the transmission direction, generally Also known as “remote deskew.”
  • Figure 1 is a schematic diagram of a code block flow on the interface of a 100G FlexE.
  • FIG. 2 is a schematic block diagram of a functional structure of a receiving end device in FlexE.
  • FIG. 3 is a schematic diagram of a code block flow transmitted by a receiving end device in FlexE.
  • FIG. 4 is a schematic diagram of a frame format of a FlexE overhead code block.
  • FIG. 5 is a schematic diagram of an application scenario of FlexE transmission across a transport network.
  • FIG. 6 is a schematic flowchart of a method for configuring a link group according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a state of differential delay of a link of an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a result of configuring a link group according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a process of configuring a link group and performing compensation according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a process of configuring a link group and performing compensation according to an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a process of configuring a link group and performing compensation according to an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a process of configuring a link group and performing compensation according to an embodiment of the present application.
  • FIG. 13 is a schematic block diagram of an apparatus for configuring a link group according to an embodiment of the present application.
  • FIG. 14 is a schematic block diagram of an apparatus for configuring a link group according to another embodiment of the present application.
  • link may be simply referred to as “link”, and the link in FlexE may also be referred to as “PHY link”.
  • the link in the embodiment of the present application refers to a link between a source device and a receiver device, and an intermediate device may exist on the link from the source device to the receiver device.
  • Ethernet has gained widespread adoption and significant growth over the past quite a while.
  • the rate of the Ethernet interface is 10 times faster, and it is evolving from 10 Mbps to 100 Mbps, 1000 Mbps (1 Gbps), 10 Gbps, and 100 Gbps.
  • the rate of the Ethernet interface is further increased.
  • 200 Gbps and so on in order to adapt to the rate requirements of diverse Ethernet interfaces in actual scenarios, 200 Gbps and so on.
  • LAG technology Prior to the birth of a new generation of higher-speed Ethernet interface standards, the bandwidth requirements of the network typically exceeded the existing Ethernet interface rate. In the transition period of the new Ethernet interface standard and the high cost of the new Ethernet interface, LAG technology can realize virtual high-speed Ethernet interface by binding multiple low-rate Ethernet interfaces into one LAG. . However, the LAG technology distributes business data to each interface in the LAG by service through a hash algorithm. Similar to the service-based load balancing method, LAG also has the problem that the interface bandwidth allocation is not balanced. If there is a service that is greater than the rate of a single interface, the hash algorithm can only be assigned to an interface. This causes the interface to be congested and the service transmission rate is limited by the rate of the interface.
  • a forwarding device when a service is forwarded from a low-rate interface to a high-speed interface, packets of the entire service need to be buffered and then forwarded to prevent packet fragmentation. This greatly increases the transmission delay of service data.
  • the Optical Internet Forum OIF
  • MLG Multi Link Gearbox
  • the MLG technology only supports several fixed interface division methods. For example, the 40G Ethernet interface is divided into 4 ⁇ 10G or 2 ⁇ 20G Ethernet interfaces, and the supported sub-interface types are limited, and the flexibility is not high enough.
  • FIG 1 is a schematic diagram of a code block flow on the interface of a 100G FlexE.
  • the FlexE 1.0 standard defines that by dividing the traffic of a 100G Ethernet interface into 20 code blocks for time division multiplexing, FlexE divides the 100G Ethernet interface into 20 time slots with 5G granularity (with 20 codes). One code block in the block period corresponds to). Insert a FlexE overhead (Overhead, OH) code block every 1023 ⁇ 20 data code blocks, as shown in Figure 1.
  • the FlexE can bind the S Ethernet interfaces to one link aggregation group, and the service data can be arbitrarily selected for idle time slot transmission in the 20*S time slots of the link aggregation group.
  • FlexE is a schematic block diagram of a functional structure of a receiving end device in FlexE.
  • FlexE technology inserts a new layer, FlexE Shim layer, on the Physical Coding Sublayer (PCS) of the Ethernet interface.
  • the FlexE Shim layer supports multiple flexible Ethernet services (FlexE Clients) and connects down to multiple 100G Ethernet interfaces.
  • the FlexE 1.0 standard specifies that the FlexE Client is a 64/66B encoded block stream. After rate adaptation by Idle Insert/Delete, the flexible Ethernet service will be in the block stream. The code blocks are placed in turn in the time slots assigned to the flexible Ethernet service.
  • FIG. 3 is a schematic diagram of a code block flow transmitted by a receiving end device in FlexE.
  • a link aggregation group consisting of S physical link links that is, a flexible Ethernet group (FlexE Group) consisting of S physical links (Physical, PHY)
  • FlexE Group Flexible Ethernet group
  • PHY Physical links
  • the FlexE Shim layer uses a 20*S length slot allocation table (Calendar) to assign the location of the 66B code block. For example, the first 20 code blocks in a cycle are sent with PHY1, the next 20 code blocks are sent with PHY2, and so on up to PHYS.
  • Calendar 20*S length slot allocation table
  • 20 code blocks on each PHY may also be referred to as a sub-slot allocation table (Sub-calendar).
  • the 10G flexible Ethernet service occupies two of the 20*S time slots, and then extracts two code blocks from the code stream of the 10G flexible Ethernet service in one cycle. Placed in the corresponding position (1 code block corresponds to 1 5G time slot).
  • the 25G flexible Ethernet service occupies 5 time slots, and each cycle extracts 5 code blocks from the code block stream of the 25G flexible Ethernet service into corresponding positions in the calendar.
  • the configuration information of which flexible Ethernet services are transmitted in each time slot of the FlexE Group is specified on a specific field in the FlexE OH code block.
  • FIG. 4 is a schematic diagram of a frame format of a FlexE overhead code block.
  • 32 consecutive FlexE frames form a FlexE multiframe
  • a FlexE OH frame consists of 8 consecutive FlexE OH blocks.
  • the first code block in the FlexE frame has a "0x4B" or "0x5" field as a tag field for identifying the code block as an OH code block.
  • the receiving end device After the receiving end device recognizes the OH code block, it can receive the next OH code block after receiving 1023 ⁇ 20 64/66B code blocks (data code blocks), and so on, and the entire FlexE can be extracted from the code block stream. frame.
  • the FlexE OH frame transmitted on each link includes a FlexE Group Number, a Physical Link Map (PHY Map), a Physical Link Number (PHY Number), and a Time Slot Allocation Table. (Calendar) A, Calendar B and other fields.
  • the FlexE Group Number is used to indicate the flexible Ethernet group number in which the link is located;
  • the physical link number can be from 1 to 254; Calendar A and Calendar B are used to indicate the current Calendar configuration and the alternate Calendar configuration of the FlexE Group, respectively.
  • each FlexE frame There are 16 bits in the third code block of each FlexE frame to indicate the number of the service data transmitted on the time slot.
  • the first FlexE frame in each FlexE multiframe carries the number of the service data transmitted in slot 0 (slot 0), and so on, until the 20th FlexE frame in the FlexE multiframe carries the corresponding slot 19 The number of the transmitted business data.
  • the receiving device After receiving the FlexE frame information on all links in the FlexE Group, the receiving device can obtain the time slot allocation mode of each service data in the FlexE Group.
  • the receiving device needs to perform differential delay compensation for each link in the FlexE Group before recovering the flexible Ethernet service from multiple time slots. Otherwise, recovering the flexible Ethernet service from the time slot of the cross-link with differential delay will cause the problem of code block out of order.
  • the FlexE 1.0 standard specifies that the FlexE Group marks the first overhead code block of the FlexE frame transmitted on each link, and aligns the transmission delay of each link by the buffer at the receiving end.
  • the differential delay compensation (deskew) capability of each link in the FlexE Group's shim-to-shim direct connection scenario is at least 300 ns, and the link differentials are transmitted over the FlexE Group long-haul transmission network.
  • the delay compensation capability is at least 10us.
  • the FlexE 1.0 standard references the FlexE frame boundary, calculates the differential delay for each link, and aligns the code block streams on each link through the cache.
  • FlexO is a flexible optical transport network group (FlexO Group) by binding multiple standard rate ports (for example, m ⁇ 100G) to carry the standard optical transmission unit Cn (Optical Transport Unit-Cn, OTUCn) (n ⁇ 1). Signal, which supplements the lack of ports in the previous protocol that do not define a bandwidth greater than 100G. Similar to FlexE, since the OTUCn signal is transmitted across multiple links across the link, it is necessary to align the traffic data transmitted on each link to ensure recovery of the transmitted OTUCn signal. Currently, FlexO specifies the alignment of service data on each link in the FlexO Group by the Frame Alignment Signal (FAS) field in the OTUCn frame transmitted on each link. If the differential delay of a link in the FlexO Group exceeds the differential delay compensation capability of the receiving device, the entire FlexO Group will fail.
  • FAS Frame Alignment Signal
  • Embodiments of the present application also relate to LLDP technology.
  • LLDP is the link layer discovery protocol defined in the standard 802.1AB.
  • the transport network device can periodically send multicast packets carrying local information to neighboring other transport network devices through a standard LLDP type length value (TLV) unit.
  • TLV LLDP type length value
  • LLDP specifies that each port of the transport network device has a standard Simple Network Management Protocol (SNMP) Management Information Base (MIB) for storing the status of local and neighboring other transport network devices. information.
  • SNMP Simple Network Management Protocol
  • MIB Management Information Base
  • the LLDP TLV unit is sent and received between the transport network devices to refresh the status information stored in the SNMP MIB.
  • LLDP can easily manage and maintain the status information of network devices.
  • a TLV unit is a 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 is a definition of each field of the TLV unit in a customizable LLDP format. It should be understood that the TLV units shown in Tables 2 to 7 in the present specification are each a specific application form of the TLV unit shown in Table 1.
  • Table 1 TLV units in a customizable LLDP format
  • FIG. 5 is a schematic diagram of an application scenario of FlexE transmission across a transport network. FlexE cross-transport transmission is based on the FlexE Aware Transport mode.
  • the flexible Ethernet slice (FlexE Shim) in the Ethernet router in Figure 5 requires differential delay compensation for the two links in the FlexE Group to which it is connected. FlexO operates at the PHY layer, and similarly to FlexE, differential delay compensation is also required for multiple links.
  • the embodiment of the present application provides a method for configuring a link group.
  • Embodiments of the present application implement compensation negotiation between transport network devices by retrofitting the related FlexE or FlexO related functional components. After the modification of the embodiment of the present application, the transport network device allows a link in the link group to exceed the differential delay compensation capability of the receiving end device when the link group is established.
  • the transport network device involved in the embodiments of the present application may include a source device, an intermediate device, and a sink device.
  • FIG. 6 is a schematic flowchart of a method 100 for configuring a link group according to an embodiment of the present application. As shown in FIG. 6, the method 100 of configuring a link group can include the following steps.
  • the first device acquires first state information of M links between the source device and the receiving device, where the first state information is used to indicate a state of differential delay between any two links 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.
  • the first device acquires 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 the N links in the M links into the first link group according to the first state 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 the second device, where the first configuration information includes information used to indicate the first link group.
  • the first device is a decision device that determines a link group division manner
  • the second device includes a related device that completes the link group configuration with the decision device.
  • differential delay compensation in the embodiments of the present application refers to delayed reception compensation, that is, compensation in the receiving direction, which is also generally referred to as “deskew”; delayed transmission compensation, that is, compensation in the transmission direction, generally also referred to as “remote” Deskew”.
  • the method for configuring a link group in the embodiment of the present application the first device according to the state 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 for the M links Dividing N links of the M links into the first link group, thereby avoiding the case where all the M links are unavailable when the differential delay of the M links exceeds the differential delay compensation capability of the receiving end device Can improve the availability and robustness of links in the transport network.
  • the data stream on each link in the FlexE Group is in the format of a 64/66B code block stream of 1OH block+1023 ⁇ 20 Data blocks, and the first OH block of the FlexE frame transmitted by the receiving device on each link.
  • the 0x4B and 0x5 identification fields in the tag are labeled to align the data code blocks on each link.
  • a FlexO frame is a 128-line 5440-bit data stream, and 8 frames are a multi-frame.
  • the receiving end device marks the data code blocks on each link by marking the FAS field in the OTUCn frame carried in each FlexO frame.
  • the two types of transport networks can uniformly use the configuration link group process of the embodiment of the present application and the subsequent compensation process.
  • the embodiments are described by taking the FlexE as an example.
  • the method for configuring the link group in the embodiment of the present application can also be applied to the FlexO or to the transport network across the FlexE and the FlexO.
  • FIG. 7 is a schematic diagram of a state of differential delay of a link of an embodiment of the present application.
  • there are five links PHY1-PHY5 between the source device and the sink device and each link transmits a FlexE frame between the source device and the sink device independently of each other.
  • the horizontal axis of Fig. 7 indicates the time delay of arrival of the FlexE frame on each link, and the width of the shaded frame indicates the capability of differential delay compensation of the receiving device.
  • the differential delay between PHY1 and PHY2 is similar, and the differential delays of PHY3, PHY4, and PHY5 are similar, but the differential delay compensation capability of the receiving device cannot complete the differential delay to PHY1-PHY5. make up.
  • the first device that is, the decision device
  • the second device is the source device.
  • the receiving device has the ability to delay receiving compensation.
  • the first device that obtains the first state information of the M links between the source device and the receiving device may include: the first device measures the differential delay of the M links, and obtains the first state. information.
  • the receiving end device may measure the differential delay of the M links by using some existing schemes, thereby obtaining the first state information.
  • embodiments of the present application can compare the differential delay between any two links by measuring the transmission delay of each link; or receive the fastest link by adding a counter at the receiving end device. After the tag code block is counted from 0, after receiving the tag code block on other links and recording the counter value x at this time, the transmission delay difference of the two links is the transmission time corresponding to the x code block.
  • the specific manners of measuring the differential delay of the M links are not limited in the embodiments of the present application.
  • the first state information may be similar to the differential delay between PHY1 and PHY2, and the differential delays of PHY3, PHY4, and PHY5 are similar, but the capability of differential delay compensation of the receiving device cannot be completed to PHY1. - PHY5 differential delay compensation.
  • N links can be selected from the M links between the source device and the sink device as "selected", and other MN links. Mark as "standby”.
  • N 3, that is, PHY3, PHY4, and PHY5 are marked as "selected”, and the other two links PHY1 and PHY2 are marked as "standby”.
  • PHY3, PHY4, and PHY5, labeled "selected" form a first link group that can carry traffic across links on three links of the first link group.
  • PHY1 and PHY2, labeled "standby” can be used to transport complete traffic independently, or PHY1 and PHY2 labeled “standby” are in a standby state, and no traffic is transmitted in the standby state. Services are not transmitted in parallel on links marked "standby” and are not transmitted in parallel on two links labeled "standby” and labeled "selected”.
  • FIG. 8 is a schematic diagram showing 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 is used to carry services across links;
  • the links PHY1 and PHY2 are marked as "selected2", that is, the second link group, For carrying services across links. Traffic cannot be transmitted across the link group on the first link group labeled "selected1" and the second link group labeled "selected2".
  • the embodiment of the present application may further have different types of link groups according to the state of differential delay between links and the capability of the receiving device to perform differential delay compensation on the link.
  • the configuration of the application is not limited in this embodiment.
  • the method for configuring a link group in this embodiment may further include: the first device transmits service data with the second device based on the first link group; and the first device uses the first link according to the first configuration information.
  • the links in the group are differentially delayed compensated.
  • FIG. 9 is a schematic diagram of a configuration of a link group and a process 200 for performing compensation in the present embodiment.
  • the process 200 can include the following steps.
  • a link is initiated between the source device and the sink device.
  • S220 The source device separately sends data frames to the receiving device through the M links.
  • the receiving device receives the data frame sent by the source device. It should be understood that alignment marks may be included in these data frames.
  • the receiving end device measures a state of the differential delay of the M links, and obtains the first state information.
  • the receiving end device determines, according to the first state information and the first capability information that can indicate that the receiving end device performs differential delay compensation on the M links, determines how to configure the link group, that is, determines the first configuration information.
  • the specific configuration includes dividing N links among the M links into the first link group.
  • 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 a buffer size of the differential delay. In other words, the receiving end device performs differential delay compensation on the link in the first link group according to the link group configuration determined by itself. It should be understood that S250 can be performed simultaneously with S260, which is not limited in this embodiment.
  • the receiving end device sends first configuration information to the source device, where the first configuration information includes information used to indicate the first link group.
  • the source device receives the first configuration information sent by the receiving device.
  • the form of the first configuration information can be various and will be described in detail below.
  • S270 The source device sends the service data to the receiving device according to the first configuration information.
  • the first configuration information may include a flag for indicating that the link belongs to the first link group, and details are not described in the following embodiments.
  • the first configuration information may include the "selected” flag (used to indicate that the link belongs to the first link group) and the "standby" flag described above.
  • 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.
  • the first device is configured to indicate that the first link of the first link belonging to the first link group of the N links is sent to the second device by using the first link.
  • the information of the link group configuration may be indicated by a link group identifier (for example, "Subgroup ID", where "Subgroup” is to distinguish from the existing "Group”).
  • the service can be transmitted across links. If only one link is marked as a Subgroup ID. ", then the service can only be transmitted independently on the link.
  • the first configuration information may include information indicating a link group to which the M links belong respectively.
  • the first device will be used to indicate the information of the link group to which the M links belong, and send the information to the second device through each link.
  • the sending, by the first device, the first configuration information to the second device may include: the first device transmitting the first configuration information in the data code block to the second device; or A device carries the first configuration information in a management channel of the overhead code block in a Link Layer Discovery Protocol (LLDP) format, a High-Level Data Link Control (HDLC) format, or a peer-to-peer
  • LLDP Link Layer Discovery Protocol
  • HDLC High-Level Data Link Control
  • PPP Point to Point Protocol
  • the first configuration information (e.g., the label of the respective associated link group transmitted on each link) is transmitted by transmitting a message in the LLDP format on the management channel of the OH code block.
  • the first configuration information may be carried in a Type-Length-Value (TLV) unit of the LLDP format, and transmitted through a shim-to-shim management channel in the FlexE OH code block.
  • TLV Type-Length-Value
  • An optional TLV unit for carrying the first configuration information defines the fields of the TLV unit as shown in Table 2.
  • the first 7 bits of byte 1 to 2 are TLV types (TLV type). According to LLDP regulations, the type value of TLV units customized by each organization is 127.
  • TLV length The last 9 bits of byte 1 to 2 are the TLV length (TLV length), indicating how many bytes of the total length of the TLV unit.
  • the bytes 3 to 5 are the Organizationally Unique Identifiers (OUIs) of the organizations specified by the LLDP.
  • the OUIs corresponding to the OIFs are 00-0F-40.
  • Byte6 is a subtype of a custom TLV unit for each organization, which can be 0x? ? (hexadecimal), for example, can be 0x01 (hexadecimal) or 00000001 (binary), and so on.
  • Byte7 is the label of the link group to which the link belongs.
  • 0x00 can indicate the ability of the link differential delay to exceed the differential delay compensation of the receiving device, that is, "standby"
  • 0x01 ⁇ 0xFF may indicate that the link differential delay is within the capability of the differential delay compensation of the receiving device, that is, "selected", and the corresponding value may indicate the number of the link group to which the link belongs.
  • Table 2 TLV units for LLDP format carrying the first configuration information
  • the source device After receiving the TLV unit on the management channel of the OH code block, the source device can complete the configuration of the link group and send the service data according to the indication of the "tag of the link group to which the link belongs".
  • the first configuration information (e.g., the flag of the respective associated link group transmitted on each link) is transmitted through the reserved field of the OH code block.
  • the first part of the first configuration information is used to indicate that the first link and other links constitute the first link group, and the second part of the first configuration information is the first part.
  • Fig. 10 is a diagram showing the format of a reserved field in the present embodiment. Specifically, 11 bits are allocated in the reserved field of the OH code block for carrying the first configuration information. The first 3 bits can carry the "selected" or "standby" flag.
  • the last 8 bits can be used to carry the "tag of the link group to which the link belongs."
  • the first partial bit includes 3 bits
  • the second partial bit includes 8 bits, which is only an example.
  • the first partial bit and the second partial bit may include more or fewer bits, which is not limited by the embodiment of the present application.
  • reserved fields of a plurality of bits are included in the OH code block, and the positions of the reserved fields for carrying the first configuration information shown in FIG. 10 are merely exemplary, and are not intended to limit the embodiments of the present application.
  • the corresponding configuration information of each link may be placed in the management channel of the OH code block of the OTUCn frame for transmission, or may be placed in a general communication channel (GCC) 0 bytes in a general framing procedure ( The Generic Framing Procedure (GFP) format, HDLC format, PPP format, or Reserved (RES) field is transmitted in a custom frame format, or may be placed in the payload of the OTUCn frame, such as in a light payload unit ( The payload of Optical Payload Unit-CnOPUCn) is sent in GFP format or other custom frame format.
  • GFP Generic Framing Procedure
  • HDLC format HDLC format
  • PPP format Physical Reserved
  • RES Reserved
  • the receiving end device has the capability of delaying the receiving compensation, and the receiving end device is used as the determining device to determine the configuration of the link group, which is simple and convenient to perform, and the signaling overhead is small when the link group is configured.
  • the first device that is, the decision device is the source device
  • the second device is the sink device.
  • the receiving device has the ability to delay receiving compensation.
  • the first device that obtains the first state information of the M links between the source device and the receiving device may include: the first device receiving the first state information sent by the receiving device.
  • the acquiring, by the S120, the first capability information of the device at the receiving end may include: the first device receiving the first capability information sent by the receiving device.
  • FIG. 11 is a schematic diagram of a configuration of a link group and a process 300 for performing compensation according to the embodiment.
  • the process 300 can include the following steps.
  • a link is initiated between the source device and the sink device.
  • the source device separately sends data frames to the receiving end device through the M links.
  • the receiving device receives the data frame sent by the source device. It should be understood that alignment marks may be included in these data frames.
  • the receiving end device measures a state of a differential delay of the M links.
  • the receiving end device sends, to the source device, first state information, where the first state information is used to indicate a state of the differential delay of the M links.
  • the source device receives the first state information sent by the receiving device.
  • the receiving device sends the first capability information to the source 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 source device receives the first capability information sent by the receiver device.
  • the source device determines how to configure the link group according to the first state information and the first capability information.
  • the specific configuration includes dividing N links among the M links into the first link group.
  • the source device sends first configuration information to the receiving device, where the first configuration information includes information used to indicate the first link group.
  • the receiving end device receives the first configuration information sent by the source 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 a buffer size of the differential delay. In other words, the receiving end device performs differential delay compensation on the link in the first link group according to the link group configuration determined by itself.
  • the receiving end device returns an acknowledgment message to the source device to indicate that the first configuration information has been received and the corresponding link group configuration is performed.
  • the source device receives the confirmation information returned by the receiving device.
  • S345 is an optional step. Further, the receiving end device may further send the status of the differential delay of each updated link to the source device.
  • the source device sends the service data to the receiving device according to the first configuration information.
  • the sending manner of the first configuration information may be similar to the sending manner of the first configuration information in Embodiment 1, and details are not described herein again.
  • the first configuration information may further include a buffer requirement for performing differential delay compensation on the receiving end device for each link, and the receiving end device directly sets the buffer amount of each link according to the buffer requirement.
  • the source device may further determine a configuration scheme of the link group by combining related information of the service data to be sent to the receiving device, for example, a combination of the number of services and/or the bandwidth.
  • the acknowledgment information returned by the receiving end device in S345 may be transmitted in the form of a message in the LLDP format; or may be transmitted through a reserved field in the OH code block.
  • a reserved field of 2 bits after the OH reserved field carrying the first configuration information in Embodiment 1 can be used to transmit the acknowledgement information.
  • “00” indicates that the receiving device receives the first configuration information and successfully sets the buffer amount of each link; “01” indicates that the buffer amount of each link is not successfully set.
  • the source device may send the service data. If the message “01” is received, the device returns to S330 to re-determine the configuration scheme of the link group.
  • the first capability information may be sent through the data code block, or may be sent in the LLDP format, the HDLC format, or the 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 limit this.
  • the first capability information may be carried in a TLV unit of the LLDP format of the management channel of the overhead code block.
  • the definition of each field of the TLV unit for carrying the LLDP format of the first capability information is as shown in Table 3.
  • Byte7 is defined as the ability to compensate for the differential delay of the link.
  • the first bit can indicate the differential delay compensation capability of the receiving direction of the link.
  • the first bit value is “0”, indicating that the buffer size in the receiving direction is a default value, such as the cache size is defined in FlexE1.0.
  • the 300 ns differential delay compensation capability corresponds to the 469 code block; the first bit value of "1" indicates that the buffer size in the receive direction is a custom value of the link, and the specific value is described in bytes 8-10.
  • the other bits in byte7 can be reserved.
  • Bytes 8 to 10 are defined as the buffer size of the link receiving direction. If the first bit in byte7 is "1" (the buffer size in the receive direction is a custom value), the value x of byte8 to 10 indicates that the buffer size in the receive direction is x code block, and the value range of x is [ 1 ⁇ 0xFFFFFE]. If the first bit in byte7 is "0", the buffer size in the receive direction is the default value, and the value of byte8 to 10 can be set to "0xFFFFFF".
  • the buffer size of the receiving direction defined by bytes 8 to 10 in the TLV unit (for example, may be local deskew buffer size) is an optional parameter.
  • the buffer size of the link receiving direction is the default size, the buffer size information of the receiving direction does not need to be transmitted, and the parameter can be set to “0xFFFFFF”.
  • the buffer size of the reception direction described here by way of example is in units of blocks.
  • the size of the buffer in the receiving direction may be expressed in different description manners such as ns or 10 ns or bytes, or a cache basic unit of different sizes, which is not limited in the embodiments of the present application.
  • the receiving device uses the above TLV unit to advertise the first capability to the source device, and the slice-to-shim management channel through the OH code block (shim-to-shim management) Channel) transmission.
  • the foregoing TLV unit may be transmitted through a section management channel or a shim-to-shim management channel.
  • Table 3 TLV unit for LLDP format carrying the first capability information
  • the first state information may be carried in a TLV unit of the LLDP format of the management channel of the overhead code block.
  • the definition of each field of the TLV unit for carrying the LLDP format of the first state information is as shown in Table 4.
  • Byte7 is defined as the result of the differential delay of the link (for example, it can be "FlexE group PHY deskew status").
  • the first bit represents the result of the current differential delay in the receiving direction of the link, and the "0" indicates that the receiving end device performs differential delay compensation on the links of the M links according to the first configuration information, and the differential delay compensation Success; "1" indicates that the receiving device has not performed differential delay compensation or differential delay compensation failure.
  • the other bits in byte7 can be reserved.
  • Bytes 8 to 10 are defined as the amount of delay of the differential delay of the link.
  • the delay amount of the differential delay indicates that the receiving device receives the data frame on each link, and the link transmits the fastest link among the M links.
  • the amount of delay indicates that the link is the fastest transmission link among the M links.
  • the value x indicates that the delay amount of the differential delay is the transmission time corresponding to the x code block data.
  • the receiving device uses the above TLV unit to advertise its own differential delay state to the source device, and passes the slice-to-chip management channel of the OH code block (shim-to -shim management channel) transmission.
  • the foregoing TLV unit may be transmitted through a section management channel or a shim-to-shim management channel.
  • Table 4 TLV unit for LLDP format carrying the first capability information
  • the source device determines the link group configuration after acquiring the first capability information of the receiving device and the first state information of each link port by using the two TLV units, and sending the first configuration information in a manner similar to Embodiment 1.
  • the receiving end device performs differential delay compensation on each link according to the first configuration information, and details are not described herein.
  • the receiving end device has the capability of delaying the receiving compensation
  • the source device is used as the determining device
  • the configuration of the link group can be determined by combining the related information of the service data, such as the number of services and/or the bandwidth.
  • the first device that is, the decision device is a management device
  • the second device includes a sink device and/or a source device.
  • the receiving device has the ability to delay receiving compensation.
  • the first device that obtains the first state information of the M links between the source device and the receiving device may include: the first device receiving the first state information sent by the receiving device.
  • the acquiring, by the S120, the first capability information of the device at the receiving end may include: the first device receiving the first capability information sent by the receiving device.
  • the process configured by the management device to determine the link group may include the following steps.
  • the link is initiated between the source device and the sink device.
  • the source device separately sends data frames to the receiving device through the M links.
  • the receiving device receives the data frame sent by the source device. It should be understood that alignment marks may be included in these data frames.
  • the receiving device measures the state of the differential delay of the M links.
  • the receiving end device sends first state information to the management device, where the first state information is used to indicate a state of the differential delay of the M links.
  • the management device receives the first state information sent by the receiving device.
  • the receiving device sends the first capability information to the management 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 management device receives the first capability information sent by the receiving device.
  • the management device determines how to configure the link group according to the first state information and the first capability information.
  • the specific configuration includes dividing N links among the M links into the first link group.
  • the management device sends the first configuration information to the source device and the receiving device, where the first configuration information includes information used to indicate the first link group.
  • the source device and the sink device receive the first configuration information sent by the management device.
  • the source device and/or the receiving device may return an acknowledgement message to the management device, indicating that the first configuration information has been received and configured accordingly.
  • the management device receives the confirmation information returned by the source device and/or the sink device. It should be understood that A-8 is an optional step.
  • A-9 After receiving the confirmation information, the management device releases the indication that the link group configuration has been completed to the source device. It should be understood that A-9 is an optional step.
  • A-10 The source device sends the service data to the receiving device according to the first configuration information.
  • A-11 The receiving end device performs differential delay compensation on the link in the first link group corresponding to the service data according to the first configuration information.
  • the first configuration information sent by the management device to the receiving device may further include: a buffer requirement for performing differential delay compensation on the receiving device for each link, and the receiving device directly sets each link according to the buffering requirement.
  • the amount of cache It should be understood that A-12 is an optional step.
  • the communication between the source device and the receiving device and the management device regarding the first state information, the first capability information, and the first configuration information may be transmitted in the management channel of the OH code block of each device and the management device.
  • the above information may be transmitted in a custom frame format in the GFP format, HDLC format, PPP format or RES field of the GCC0 byte of the OH code block.
  • the above information can be transmitted in the form of an Internet Protocol (IP) packet in the management channel of the OH code block. This embodiment does not limit the specific transmission mode.
  • IP Internet Protocol
  • the management device is used as the decision device, and the related information of the source device and the receiving device can be received, and the configuration of the link group can be determined by considering comprehensive factors such as the number of services and/or bandwidth;
  • the amount of computation that may be caused by the decision of the source device or the sink device can reduce the burden on the source device and the sink device.
  • the path of the link from the source device to the receiving device may also pass through some intermediate devices, as shown in FIG. 5, the application scenario of the FlexE transmission across the transport network, that is, based on the FlexE aware transport mode. Transfer the scene.
  • each transmitting port of the intermediate device can also support the ability to delay the transmission of data, or the ability to delay the transmission of the compensation. Therefore, the receiving device and the intermediate device need to implement cooperative compensation through negotiation.
  • the K upstream devices of the receiving end device may have the ability to delay transmission compensation, where K is a positive integer.
  • the K upstream devices may include a source device and/or at least one intermediate device, and the intermediate device is located between the source device and the sink device on the M links.
  • the method 100 may further include: acquiring, by the first device, second capability information and second state information of each upstream device of the K upstream devices,
  • the second capability information is used to indicate a second capability of each upstream device to delay transmission compensation for at least one of the M links
  • the second state information is used to indicate that each upstream device pairs at least one of the M links.
  • the link is configured to delay the transmission of the current state of the compensation; the first device, according to the first state information and the first capability information, the N links of the M links are divided into the first link group, and may include: the first device And dividing the N links of the M links into the first link group according to the first state information, the first capability information, the second state information, and the second capability information.
  • the method 100 may further include: the first device according to the first device The first state information, the first capability information, the second state information, and the second capability information determine a configuration of delayed transmission compensation that each upstream device should perform on the corresponding link.
  • the first device is a receiving device
  • the second device is a source device.
  • the receiving device has the ability to delay receiving compensation.
  • the K upstream devices may include source devices and/or at least one intermediate device with the ability to delay transmission compensation.
  • the first device that obtains the first state information of the M links between the source device and the receiving device may include: the first device measures the differential delay of the M links, and obtains the first state information;
  • the second capability information and the second state information of each of the upstream devices of the K upstream devices may include: the first device receives the second capability information and the second state information that are sent by each of the upstream devices; and the method 100 may further include: A device sends second configuration information to at least one of the K upstream devices, where the second configuration information is used to indicate that at least one upstream device should perform delayed transmission compensation for the corresponding link.
  • the method 100 may further include: the first device transmitting the service data with the second device based on the first link group; and the first device is configured to the first chain according to the first configuration information.
  • a link in the path group that has undergone delay transmission compensation according to the second configuration information by at least one upstream device performs differential delay compensation.
  • the M links cannot be aligned at the receiving end device, the M links cannot form a link group, or the FlexE Group or the FlexO Group fails to work.
  • the device may also include an intermediate device or the like, which may have the capability of differential delay compensation or delayed transmission compensation.
  • Each device in the embodiments of the present application implements link group compensation through capability negotiation.
  • the link group is configured so that the source device only delays the aligned link.
  • the uplink carries the service data across the links; or through the cooperative compensation of the devices, the final M links can be aligned at the receiving end device, which can ensure the work of the FlexE Group or the FlexO Group, and can improve the link utilization.
  • the first device that is, the decision device
  • the second device is the source device.
  • the receiving device has the ability to delay receiving compensation.
  • There is an intermediate device with the capability of delaying transmission compensation between the receiving device and the source device, that is, the K upstream devices are at least one intermediate device.
  • the process of the cooperative compensation between the receiving end device and the intermediate device may include the following steps.
  • the link is initiated between the source device and the sink device.
  • the source device separately sends data frames to the receiving device through the M links.
  • the receiving device receives the data frame sent by the source device. It should be understood that alignment marks may be included in these data frames.
  • the receiving end device measures the state of the differential delay of the M links, and obtains the first state information.
  • the intermediate device sends the second capability information to the receiving device, where the second capability information is used to indicate a second capability of each intermediate device to perform delayed transmission compensation on at least one of the M links.
  • the receiving end device receives the second capability information sent by the intermediate device.
  • the second capability information may be carried in the data frame of the B-2, and may be sent by other means, which is not limited in this embodiment.
  • the intermediate device sends the second state information to the receiving device, where the second state information is used to indicate a current state in which each intermediate device performs delayed transmission compensation on at least one of the M links.
  • the receiving end device receives the second status information sent by the intermediate device.
  • the second state information may be carried in the data frame of the B-2, and may be sent by other means, which is not limited in this embodiment.
  • the receiving end device determines, according to the first state information and the first capability information, the second capability information, and the second state information that can indicate that the receiving device performs differential delay compensation on the M links, how to configure the link. Group and how to configure delayed send compensation.
  • the specific link group configuration includes dividing N links among the M links into the first link group.
  • B-7 The receiving device sends the first configuration information to the intermediate device, where the first configuration information includes information indicating the first link group.
  • the intermediate device receives the first configuration information sent by the receiving device. It should be understood that B-7 is an optional step, and execution B-7 may not be used for the collaborative compensation process, but for other processes.
  • the receiving end device sends the second configuration information to the intermediate device, where the second configuration information includes a configuration for indicating that the upstream device should perform delayed transmission compensation for the corresponding link.
  • the intermediate device receives the second configuration information sent by the receiving device.
  • the intermediate device adjusts the link transmission delay according to the second configuration information.
  • the intermediate device sends, to the receiving end device, information about the current state of the delayed delayed transmission transmission. First, it can prepare for the next coordinated compensation, and secondly, notify the receiving end device that the configuration of delayed transmission compensation has been completed.
  • the receiving device After receiving the information sent by the intermediate device, the receiving device sends the first configuration information to the source device, where the first configuration information includes information indicating the first link group.
  • the source device receives the first configuration information sent by the receiving device.
  • the first configuration information may further include information indicating that the related configuration of the differential delay compensation has been completed.
  • the receiving end device performs differential delay compensation on M links. Specifically, the receiving end device performs differential delay compensation according to the first configuration information, that is, sets a buffer size of the differential delay. In other words, the receiving end device performs differential delay compensation on the link in the first link group according to the link group configuration determined by itself.
  • the source device sends the service data to the receiving device according to the first configuration information.
  • the communication of the related information may be transmitted through the data code block, or may be transmitted in the LLDP format, the HDLC format, or the PPP format in the management channel of the overhead code block, or may be transmitted through the reserved field of the overhead code block. This is not limited.
  • the first configuration information is sent in the same manner as the first configuration information in the first embodiment, and is not described here.
  • the first capability information and the second capability information may be carried in a TLV unit of an LLDP format of a management channel of an overhead code block.
  • the definition of each field of the TLV unit of the LLDP format for carrying capability information is as shown in Table 5.
  • Byte7 is defined as the ability to compensate for this link.
  • the first bit of byte7 can indicate the capability of differential delay compensation in the receiving direction of the link.
  • the first bit value is “0”, indicating that the buffer size in the receiving direction is the default value, such as the cache size and FlexE1.0.
  • the second bit of byte7 can indicate the delay transmission capability of the link in the transmission direction.
  • the second bit value is "0" indicating the default mode of the capability of not supporting delayed transmission compensation; the second bit value is "1".
  • the specific value of the delayed transmission buffer size is described in bytes 11-13.
  • the other bits in byte7 can be reserved.
  • Bytes 8 to 10 are defined as the buffer size of the link receiving direction. If the first bit in byte7 is "1" (the buffer size in the receive direction is a custom value), the value x of byte8 to 10 indicates that the buffer size in the receive direction is x code block, and the value range of x is [ 1 ⁇ 0xFFFFFE]. If the first bit in byte7 is "0", the buffer size in the receive direction is the default value, and the value of byte8 to 10 can be set to "0xFFFFFF".
  • Bytes 11 to 13 are defined as the buffer size of the link transmission direction. If the first bit in byte7 is "1" (the transmission direction supports the ability to delay the transmission of the transmission), the value x of the byte 8 to 10 indicates that the buffer size in the transmission direction is x code block, and the value range of x is [1 ⁇ 0xFFFFFE]. If the first bit in byte7 is "0", it indicates that the transmission direction does not support the delay transmission compensation, and the value of byte8 to 10 can be set to "0xFFFFFF".
  • the buffer size exemplified herein is in units of blocks.
  • the cache size may be expressed in different description manners such as ns or 10 ns or bytes, or a cache basic unit of different sizes, which is not limited in the embodiments of the present application.
  • the TLV unit notification capability is used between the devices, and is transmitted through the shim-to-shim management channel of the OH code block.
  • the foregoing TLV unit may be transmitted through a section management channel or a shim-to-shim management channel.
  • Table 5 TLV unit in LLDP format for carrying capability information
  • the embodiments of the present application can use the TLV unit shown in Table 5 to carry capability information. Since the link is bidirectional in general, in one transmission direction, one device is a receiving device, and in another transmission direction, the device is a source device or an upstream device.
  • the TLV unit for carrying the capability information is designed in the form of Table 5, so that the device can use the TLV unit when reporting the capability information, whether it is the receiving device or the source device or the upstream device. .
  • the link layer discovery protocol LLDP format TLV unit of the management channel of the overhead code block shown in Table 5 can carry the first capability for indicating the receiving end device to perform differential delay compensation for M links.
  • a capability information and information capable of indicating that the receiving device performs delayed transmission compensation on the M links when the receiving device transmits the service data to the source device.
  • This embodiment and other embodiments of the present application relate to reporting or transmitting its own state information, for example, the first state information and the second state information, which may be carried in a TLV unit of the LLDP format of the management channel of the overhead code block.
  • the definition of each field of the TLV unit for the LLDP format for carrying status information is as shown in Table 6.
  • Byte7 is defined as the current state of the differential delay compensation for the link and the current state of the delayed transmission compensation, ie the compensation state of the link.
  • the first bit represents the current state of differential delay compensation in the receiving direction of the link.
  • the first bit value of "0" indicates that the link differential delay compensation is successful in the receiving direction.
  • the link is marked as "selected", and the "subgroup ID” is "3", indicating that the link is differentially compensated with respect to the other links in the subgroup 3.
  • the first bit value of "1" indicates that the link differential delay compensation fails in the receiving direction.
  • the link is marked as "selected", and the "subgroup ID" is "3", indicating that the link fails to compensate for the differential delay of the other links in the subgroup3, the link
  • the differential delay amount is described in bytes 8-10.
  • the second bit in byte7 represents the current state of delayed transmission compensation for the transmission direction of the link.
  • the second bit value of "0” indicates that the link has no delayed transmission capability in the transmission direction; the second bit value is "1", indicating that the delayed transmission capability of the link in the transmission direction is in use.
  • the delayed transmission amount is described in bytes 11 to 13.
  • the other bits in byte7 are reserved fields.
  • Bytes 8 to 10 are defined as the differential delay amount of the ability of the link to exceed the differential delay compensation in the receiving direction when the differential delay compensation in the receiving direction of the link fails, and the value x indicates that the excess differential delay amount is the x code block buffer.
  • the transmission time corresponding to the size, when the differential delay compensation in the receiving direction is successful, x is 0.
  • Bytes 11 to 13 are defined as the delayed transmission amount of the link, and the value x indicates that the buffer size of the currently used delayed transmission is a code block, and when the second bit in byte 7 is "0" (the transmission direction is not delayed in the transmission direction) Ability), x value is "0xFFFFFF".
  • the buffer size exemplified herein is in units of blocks.
  • the cache size may be expressed in different description manners such as ns or 10 ns or bytes, or a cache basic unit of different sizes, which is not limited in the embodiments of the present application.
  • the devices use the above TLV unit to announce the status and transmit through the shim-to-shim management channel of the OH code block.
  • the foregoing TLV unit may be transmitted through a section management channel or a shim-to-shim management channel.
  • the TLV unit shown in Table 6 can use the TLV unit shown in Table 6 to carry status information. Since the link is bidirectional in general, in one transmission direction, one device is a receiving device, and in another transmission direction, the device is a source device or an upstream device.
  • the TLV unit for carrying the status information is designed in the form of Table 6, so that the device can be used as the receiving end device or as the source device or the upstream device, and the TLV unit can be used when reporting status information. .
  • the link layer discovery protocol LLDP format TLV unit of the management channel of the overhead code block shown in Table 6 can carry a state for indicating the differential delay between any two of the M links.
  • the first state information is further capable of carrying information indicating a current state in which the receiving device performs delayed transmission compensation on the M links when the receiving device sends the service data to the source device.
  • the determining device may also use the TLV unit shown in Table 6 to carry the second configuration information. That is, the TLV unit can also carry information indicating the configuration of the delayed transmission compensation that the upstream device should make for the corresponding link.
  • the manner of sending the first configuration information may be similar to the manner of sending the first configuration information in Embodiment 1, and details are not described herein again.
  • this embodiment and other embodiments of the present application relate to reporting or transmitting the status information of the self and the sending configuration information, for example, the first status information, the second status information, the first configuration information, and the second configuration information, which may be Together they are carried in the TLV unit of the LLDP format of the management channel of the overhead code block.
  • the definition of each field of the TLV unit of the LLDP format for carrying status information and configuration information is as shown in Table 7.
  • Bytes 7-8 are defined as the compensated state and link group configuration of the link.
  • the first bit represents the current state of differential delay compensation in the receiving direction of the link.
  • the first bit value of "0" indicates that the link differential delay compensation is successful in the receiving direction.
  • the link is marked as "selected", and the "subgroup ID" is "3", indicating that the link is delayed in differential compensation with respect to other links in the subgroup 3.
  • the first bit value of "1" indicates that the link differential delay compensation fails in the receiving direction.
  • the link is marked as "selected", and the "subgroup ID" is "3", indicating that the link fails to compensate for the differential delay of the other links in the subgroup3, the link
  • the ability to exceed the differential delay compensation of the device the differential delay amount is described in bytes 9-11.
  • the second bit in byte7 represents the current state of delayed transmission compensation for the transmission direction of the link.
  • the second bit value of "0" indicates that the link does not delay transmission in the transmission direction or the ability to delay transmission is not used; the second bit value is "1", indicating that the link is delayed in the transmission direction.
  • the ability is being used.
  • the delayed transmission amount is described in bytes 12 to 14.
  • the other bits in byte7 are reserved fields.
  • the third to thirteenth bits in the bytes 7 to 8 are used to indicate the link group to which the link belongs, that is, the tag information of the link.
  • the 2nd to 4th bits are used to indicate "selected” or "standby". For example, "001" means “selected” and “010” means “standby”.
  • the last 8 bits in the "selected” state can be used to indicate "subgroup ID”.
  • the other bits in byte7 ⁇ 8 are reserved fields.
  • the differential delay amount described in bytes 9 to 11 of Table 7 is the same as the differential delay amount described in bytes 8 to 10 of Table 6; the delayed transmission amount described in bytes 12 to 14 of Table 7 and the delay described in bytes 11 to 13 of Table 6
  • the amount sent is the same and will not be described here.
  • Table 7 TLV unit for LLDP format carrying status information
  • the first device that is, the decision device
  • the second device is the source device.
  • the receiving device has the ability to delay receiving compensation.
  • the source device has the capability of delaying transmission compensation, that is, the K upstream devices are source devices.
  • the process of being configured by the receiving device to determine the link group and coordinated by the receiving device and the source device may include the following steps.
  • the link is initiated between the source device and the sink device.
  • the source device separately sends data frames to the receiving device through the M links.
  • the receiving device receives the data frame sent by the source device. It should be understood that alignment marks may be included in these data frames.
  • the source device sends the second capability information to the receiving device, where the second capability information is used to indicate the second capability of the source device to perform delayed transmission compensation on at least one of the M links.
  • the receiving end device receives the second capability information sent by the source device. It should be understood that the second capability information may be carried in the data frame of the C-2, and may be sent by other means, which is not limited in this embodiment.
  • the source device sends the second state information to the receiving device, where the second state information is used to indicate the current state in which the source device performs delayed transmission compensation on at least one of the M links.
  • the receiving end device receives the second state information sent by the source device. It should be understood that the second state information may be carried in the data frame of the C-2, and may be sent by other means, which is not limited in this embodiment.
  • the receiving end device measures the state of the differential delay of the M links, and obtains the first state information.
  • the receiving end device determines, according to the first state information and the first capability information, the second capability information, and the second state information that can indicate the capability of the receiving device to perform differential delay compensation on the M links, how to configure the link. Group and how to configure delayed send compensation.
  • the specific link group configuration includes dividing N links among the M links into the first link group.
  • the receiving device sends the first configuration information to the source device, where the first configuration information includes information indicating the first link group.
  • the source device receives the first configuration information sent by the receiving device.
  • the receiving end device sends the second configuration information to the source end device, where the second configuration information includes a configuration for indicating that the source end device should perform delayed transmission compensation on the corresponding link.
  • the source device receives the second configuration information sent by the receiving device.
  • the source device adjusts the link sending delay according to the second configuration information.
  • the source device sends, to the receiving end device, information about the status of the updated delayed transmission compensation. First, it can prepare for the next coordinated compensation, and secondly, notify the receiving end device that the configuration of delayed transmission compensation has been completed.
  • the receiving device after receiving the information sent by the source device, the receiving device re-analyzes the differential delay of each link and 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 a buffer size of the differential delay. In other words, the receiving end device performs differential delay compensation on the link in the first link group according to the link group configuration determined by itself. The receiving device feeds back the state of the differential delay of each link and the configuration of the link group to the source device.
  • the source device sends the service data to the receiving device according to the first configuration information.
  • the first state information, the first capability information, the first configuration information, the second state information, the second capability information, and the second configuration information is between the source device and the receiving device.
  • the transmission format and transmission channel are similar to those in Embodiment 4, and details are not described herein.
  • the first device that is, the decision device
  • the second device is the source device.
  • the receiving device has the ability to delay receiving compensation.
  • the source device and the at least one intermediate device have the ability to delay transmission compensation, ie, the K upstream devices include the source device and the at least one intermediate device.
  • the process of cooperatively compensating the receiving end device, the source end device, and the at least one intermediate device may include the following steps.
  • the link is initiated between the source device and the sink device.
  • the source device separately sends data frames to the receiving device through the M links.
  • the receiving device receives the data frame sent by the source device. It should be understood that alignment marks may be included in these data frames.
  • the receiving end device measures the state of the differential delay of the M links, and obtains the first state information.
  • the source device and the at least one intermediate device send second capability information to the receiving device, where the second capability information is used to indicate that each upstream device performs delayed transmission compensation on at least one of the M links.
  • the receiving end device receives the second capability information sent by the source device. It should be understood that the second capability information may be carried in the data frame of the D-2, and may be sent by other means, which is not limited in this embodiment.
  • the source device and the at least one intermediate device send second state information to the receiving device, where the second state information is used to indicate that each upstream device performs delayed transmission compensation on at least one of the M links. status.
  • the receiving end device receives the second state information sent by the source device. It should be understood that the second state information may be carried in the data frame of the D-2, and may be sent by other means, which is not limited in this embodiment.
  • the receiving device determines how to configure the link according to the first state information and the first capability information, the second capability information, and the second state information that can indicate the capability of the receiving device to perform differential delay compensation on the M links. Group and how to configure delayed send compensation.
  • the specific link group configuration includes dividing N links among the M links into the first link group.
  • the receiving device sends the first configuration information to the source device, where the first configuration information includes information indicating the first link group.
  • the source device receives the first configuration information sent by the receiving device.
  • the receiving device sends the first configuration information to the intermediate device, where the first configuration information includes information indicating the first link group.
  • the intermediate device receives the first configuration information sent by the receiving device. It should be understood that D-10 is an optional step, and execution D-8 may not be used for the collaborative compensation process, but for other processes.
  • the receiving end device sends the second configuration information to the source device and the at least one intermediate device, where the second configuration information includes a delay for indicating that the source device and the at least one intermediate device respectively perform corresponding links. Send the compensated configuration.
  • the source device and the at least one intermediate device respectively receive the second configuration information sent by the receiving device.
  • the source device and the at least one intermediate device adjust the link sending delay according to the second configuration information, that is, set a buffer size for delay sending.
  • the source device and the at least one intermediate device send information of the updated delayed transmission compensation state to the receiving device. First, it can prepare for the next coordinated compensation, and secondly, notify the receiving end device that the configuration of delayed transmission compensation has been completed.
  • the receiving end device re-analyzes the differential delay of each link, and performs differential delay compensation for M links. Specifically, the receiving end device performs differential delay compensation according to the first configuration information, that is, sets a buffer size of the differential delay. In other words, the receiving end device performs differential delay compensation on the link 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.
  • the source device sends the service data to the receiving device according to the first configuration information.
  • the first state information, the first capability information, the first configuration information, the second state information, the second capability information, and the second configuration information is between the source device and the receiving device.
  • the transmission format and transmission channel are similar to those in Embodiment 4, and details are not described herein.
  • the first device that is, the decision device is the source device
  • the second device is the receiver device.
  • the receiving device has the ability to delay receiving compensation.
  • the K upstream devices may include source devices and/or at least one intermediate device with the ability to delay transmission compensation.
  • the first capability information may include: the first device receiving the first capability information sent by the receiving device.
  • the method 100 may further include: the first device transmitting the service data with the second device based on the first link group; and the first device is configured to the first chain according to the first configuration information.
  • a link in the path group that has undergone delay transmission compensation according to the second configuration information by at least one upstream device performs differential delay compensation.
  • the first device that is, the decision device is the source device
  • the second device is the sink device.
  • the receiving device has the ability to delay receiving compensation.
  • There is an intermediate device with the capability of delaying transmission compensation between the receiving device and the source device, that is, the K upstream devices are at least one intermediate device.
  • the acquiring, by the first device, the second capability information and the second state information of each of the K upstream devices may include: the first device receiving the second capability information sent by each of the at least one intermediate device And the second state information; the method 100 may further include: the first device sending, to the at least a part of the at least one intermediate device, the second configuration information, where the second configuration information is used to indicate that at least a part of the intermediate devices should perform the corresponding link The delay sends a compensated configuration.
  • the first device sends the second configuration information to the at least one of the at least one intermediate device, where the first device directly sends the second configuration information to the intermediate device, or the first device sends the second configuration information.
  • the receiving device forwards the second configuration information to the intermediate device. That is, the first device sends the second configuration information to the intermediate device, which may be a direct transmission or an indirect transmission, which is not limited in this embodiment.
  • the process of the cooperative compensation between the receiving end device and the intermediate device may include the following steps.
  • the link is initiated between the source device and the sink device.
  • E-2 The source device separately sends data frames to the receiving device through the M links.
  • the receiving device receives the data frame sent by the source device. It should be understood that alignment marks may be included in these data frames.
  • the receiving device measures the state of the differential delay of the M links.
  • the receiving end device sends, to the source device, first state information, where the first state information is used to indicate a state of the differential delay of the M links.
  • the source device receives the first state information sent by the receiving device.
  • the first state information may be transmitted in the FlexE via a shim-to-shim management channel of the OH code block.
  • the receiving end device sends the first capability information to the source 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 source device receives the first capability information sent by the receiver device.
  • the first capability information may be transmitted in the FlexE through a shim-to-shim management channel of the OH code block.
  • the intermediate device sends the second capability information to the source device, where the second capability information is used to indicate a second capability of each intermediate device to perform delayed transmission compensation on at least one of the M links.
  • the source device receives the second capability information sent by the intermediate device.
  • the second capability information may be carried in the data frame of the E-2, and may be sent by other means, which is not limited in this embodiment.
  • the second capability information may be transmitted in the FlexE through a shim-to-shim management channel of the OH code block.
  • the intermediate device sends the second state information to the source device, where the second state information is used to indicate a current state in which each intermediate device performs delayed transmission compensation on at least one of the M links.
  • the source device receives the second state information sent by the intermediate device.
  • the second state information may be carried in the data frame of the E-2, and may be sent by other means, which is not limited in this embodiment.
  • the second status information may be transmitted in the FlexE via the section management channel of the OH code block.
  • the source device determines, according to the first state information, the first capability information, the second capability information, and the second state information, how to configure the link group and how to configure the delayed transmission compensation.
  • the specific link group configuration includes dividing N links among the M links into the first link group.
  • the source device sends the first configuration information and the second configuration information to the receiving device, where the first configuration information includes information indicating the first link group.
  • the receiving end device receives the first configuration information sent by the source device.
  • the receiving end device performs configuration of differential delay compensation according to the first configuration information, for example, setting a buffer of local differential delay compensation.
  • the receiving end device sends the second configuration information to the intermediate device, where the second configuration information includes a configuration for indicating that the intermediate device should perform delayed transmission compensation on the corresponding link.
  • the intermediate device receives the second configuration information sent by the receiving device.
  • E-12 The receiving end device sends the first configuration information to the intermediate device, where the first configuration information includes information indicating the first link group.
  • the intermediate device receives the first configuration information sent by the source device. It should be understood that E-12 is an optional step, and execution of E-12 may not be used for the collaborative compensation process, but for other processes.
  • the intermediate device adjusts the link transmission delay according to the second configuration information, for example, setting a buffer for delaying data transmission.
  • the intermediate device sends the updated information of the current state of the delayed transmission transmission to the receiving device. First, it can prepare for the next coordinated compensation, and secondly, notify the receiving end device that the configuration of delaying the transmission compensation has been completed.
  • the receiving device After receiving the information sent by the intermediate device, the receiving device re-analyzes the differential delay of each link and 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 a buffer size of the differential delay. The receiving device feeds back the configured information to the source device.
  • E-16 The source device sends the service data to the receiving device according to the first configuration information.
  • the source device may further determine a configuration scheme of the link group by combining related information of the service data to be sent to the receiving device, such as a combination of the number of services and/or bandwidth.
  • At least one of the first state information, the first capability information, the first configuration information, the second state information, the second capability information, and the second configuration information is between the source device, the intermediate device, and the receiving device.
  • a transmission format and transmission channel of information are similar to Embodiment 4, and details are not described herein.
  • the first device that is, the decision device is the source device
  • the second device is the sink device.
  • the receiving device has the ability to delay receiving compensation.
  • the source device has the capability of delaying transmission compensation, that is, the K upstream devices are source devices.
  • the method 100 may further include: the first device transmitting the service data to the second device based on the first link group according to the determined configuration that the first device should send the compensation to the corresponding link.
  • FIG. 12 is a schematic diagram of a configuration of a link group and a process 400 for performing compensation in the present embodiment.
  • the process 400 for receiving compensation between the sink device and the source device may include the following steps.
  • a link is initiated between the source device and the sink device.
  • the source device separately sends data frames to the receiving end device through the M links.
  • the receiving device receives the data frame sent by the source device. It should be understood that alignment marks may be included in these data frames.
  • the receiving end device measures a state of a differential delay of the M links.
  • the receiving end device sends first state information to the source device, where the first state information is used to indicate a state of the differential delay of the M links.
  • the source device receives the first state information sent by the receiving device.
  • the first state information may be transmitted in the FlexE via a shim-to-shim management channel of the OH code block.
  • the receiving device sends the first capability information to the source 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 source device receives the first capability information sent by the receiver device.
  • the first capability information may be transmitted in the FlexE through a shim-to-shim management channel of the OH code block.
  • the source device performs, according to the first state information, the first capability information, second capability information, which is used to indicate that the UE performs the delayed transmission compensation for the at least one of the M links, and is used to indicate the M information.
  • At least one link in the link performs second state information that delays transmission of the compensated state, determines how to configure the link group, and how to configure delayed transmission compensation.
  • the specific link group configuration includes dividing N links among the M links into the first link group.
  • the source device adjusts the transmission delay of the corresponding link according to the configuration of the delayed transmission compensation determined by S430. For example, S430 determines to delay transmission compensation for PHY2, and then at S435, modifies the buffer size of the delayed transmission of PHY2.
  • the source device sends the first configuration information to the receiving device, where the first configuration information includes information indicating the first link group.
  • the receiving end device receives the first configuration information sent by the source device.
  • the receiving end device performs configuration of differential delay compensation according to the first configuration information, for example, setting a buffer of local differential delay compensation.
  • S450 The receiving end device sends a confirmation message that the configuration is completed to the source device.
  • the source device receives the acknowledgement information sent by the receiver device.
  • S455 is performed; when the confirmation information indicates that the configuration of the delayed transmission compensation of the source device fails, the process returns to S430.
  • the source device sends the service data to the receiving device according to the first configuration information.
  • the first state information, the first capability information, the first configuration information, the second state information, the second capability information, and the second configuration information is between the source device and the receiving device.
  • the transmission format and transmission channel are similar to those in Embodiment 4, and details are not described herein.
  • the first device that is, the decision device is the source device
  • the second device is the sink device.
  • the receiving device has the ability to delay receiving compensation.
  • the source device and the at least one intermediate device have the ability to delay transmission compensation, ie, the K upstream devices include the source device and the at least one intermediate device.
  • the method 100 may further include: the first device transmitting the service data to the second device based on the first link group according to the determined configuration that the first device should send the compensation to the corresponding link.
  • the process of cooperatively compensating the receiving end device, the source end device, and the at least one intermediate device may include the following steps.
  • the link is initiated between the source device and the sink device.
  • the source device separately sends data frames to the receiving device through the M links.
  • the receiving device receives the data frame sent by the source device. It should be understood that alignment marks may be included in these data frames.
  • the receiving device measures the state of the differential delay of the M links.
  • the receiving end device sends first state information to the source device, where the first state information is used to indicate a state of the differential delay of the M links.
  • the source device receives the first state information sent by the receiving device.
  • the first state information may be transmitted in the FlexE via a shim-to-shim management channel of the OH code block.
  • the receiving end device sends the first capability information to the source 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 source device receives the first capability information sent by the receiver device.
  • the first capability information may be transmitted in the FlexE through a shim-to-shim management channel of the OH code block.
  • the intermediate device sends the second capability information to the source device, where the second capability information is used to indicate a second capability of each intermediate device to perform delayed transmission compensation on at least one of the M links.
  • the source device receives the second capability information sent by the intermediate device.
  • the second capability information may be carried in the data frame of the F-2, and may be sent by other means, which is not limited in this embodiment.
  • the second capability information may be transmitted in the FlexE through a shim-to-shim management channel of the OH code block.
  • the intermediate device sends second state information to the source device, where the second state information is used to indicate a current state in which each intermediate device performs delayed transmission compensation on at least one of the M links.
  • the source device receives the second state information sent by the intermediate device.
  • the second state information may be carried in the data frame of the F-2, or may be sent by other means, which is not limited in this embodiment.
  • the second status information may be transmitted in the FlexE via the section management channel of the OH code block.
  • the source device according to the first state information, the first capability information, the second capability information sent by the intermediate device, and the capability for indicating that the UE performs delayed transmission compensation on at least one of the M links.
  • the specific link group configuration includes dividing N links among the M links into the first link group.
  • the source device adjusts the transmission delay of the corresponding link according to the configuration of the delayed transmission compensation determined by F-8. For example, F-8 determines to delay the transmission of PHY2, so at F-9, modify the buffer size of the delayed transmission of PHY2.
  • the source device sends the first configuration information and the second configuration information to the receiving device, where the first configuration information includes information indicating the first link group.
  • the receiving end device receives the first configuration information sent by the source device.
  • the receiving end device performs configuration of differential delay compensation according to the first configuration information, for example, setting a buffer of local differential delay compensation.
  • the receiving end device sends second configuration information to the intermediate device, where the second configuration information includes a configuration for indicating that the intermediate device should perform delayed transmission compensation on the corresponding link.
  • the intermediate device receives the second configuration information sent by the receiving device.
  • the receiving end device sends the first configuration information to the intermediate device, where the first configuration information includes information indicating the first link group.
  • the intermediate device receives the first configuration information sent by the source device. It should be understood that F-13 is an optional step, and execution of F-13 may not be used for the cooperative compensation process, but for other processes.
  • the intermediate device adjusts the link transmission delay according to the second configuration information, for example, setting a buffer for delaying data transmission.
  • the intermediate device sends, to the receiving end device, information about the current state of the delayed delayed transmission transmission. First, it can prepare for the next coordinated compensation, and secondly, notify the receiving end device that the configuration of delayed transmission compensation has been completed.
  • the receiving device after receiving the information sent by the intermediate 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 a buffer size of the differential delay. The receiving device sends the configured information to the source device.
  • the source device sends the service data to the receiving device according to the first configuration information.
  • At least one of the first state information, the first capability information, the first configuration information, the second state information, the second capability information, and the second configuration information is between the source device, the intermediate device, and the receiving device.
  • a transmission format and transmission channel of information are similar to Embodiment 4, and details are not described herein.
  • the first device that is, the decision device is a management device
  • the second device includes a sink device and/or a source device.
  • the receiving device has the ability to delay receiving compensation.
  • the K upstream devices may include source devices and/or at least one intermediate device with the ability to delay transmission compensation.
  • the acquiring, by the first device, the first state information of the M links between the source device and the receiving device may include: receiving, by the first device, first state information sent by the receiving device;
  • the first capability information of the receiving device may be: the first device receives the first capability information sent by the receiving device, and the first device acquires the second capability information and the second state information of each upstream device of the K upstream devices.
  • the method may further include: the first device receiving the second capability information and the second state information sent by each of the upstream devices; the method 100 may further include: the first device sending the second configuration information to the at least one of the K upstream devices, where The second configuration information is used to indicate a configuration of delayed transmission compensation that the at least one upstream device should perform on the corresponding link.
  • the process configured by the management device to determine the link group and coordinated by the receiving device and other devices may include the following steps.
  • the link is initiated between the source device and the sink device.
  • the source device separately sends data frames to the receiving device through the M links.
  • the receiving device receives the data frame sent by the source device. It should be understood that alignment marks may be included in these data frames.
  • the receiving device measures the state of the differential delay of the M links.
  • the receiving end device sends first state information to the management device, where the first state information is used to indicate a state of the differential delay of the M links.
  • the management device receives the first state information sent by the receiving device.
  • the receiving device sends the first capability information to the management 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 management device receives the first capability information sent by the receiving device.
  • the source device and/or the at least one intermediate device send the second capability information to the management device, where the second capability information is used to indicate that each upstream device performs delayed transmission compensation on at least one of the M links. Second ability.
  • the management device receives the second capability information sent by the source device and/or the at least one intermediate device.
  • the second capability information corresponding to the source device may be carried in the data frame of the G-2, and may be sent by other means, which is not limited in this embodiment.
  • the second capability information may be transmitted in the FlexE through a shim-to-shim management channel of the OH code block.
  • the source device and/or the at least one intermediate device send second state information to the management device, where the second state information is used to indicate that each upstream device performs delayed transmission compensation on at least one of the M links. Current status.
  • the management device receives the second status information sent by the source device and/or the at least one intermediate device.
  • the second state information corresponding to the source device may be carried in the data frame of the G-2, and may be sent by other means, which is not limited in this embodiment.
  • the second status information may be transmitted in the FlexE via the section management channel of the OH code block.
  • the management device determines, according to the first state information, the first capability information, the second state information, and the second capability information, how to configure the link group and how to configure the delayed transmission compensation.
  • the specific configuration includes dividing N links among the M links into the first link group.
  • the management device sends the second configuration information to the upstream device that needs to perform the delayed transmission compensation configuration in the K upstream devices (including the source device and/or the at least one intermediate device) for indicating the configuration of delaying the transmission of the compensation.
  • the upstream device in the K upstream devices (including the source device and/or the at least one intermediate device) that needs to perform the delayed transmission compensation configuration configures the buffer size of the delayed transmission compensation according to the second configuration information.
  • the upstream device that needs to perform the delayed transmission compensation configuration in the K upstream devices returns an acknowledgement information to the management device, to indicate that the second configuration information has been received.
  • the corresponding configuration has been made.
  • the management device receives the confirmation information returned by the source device and/or the sink device. It should be understood that G-11 is an optional step.
  • the management device After receiving the acknowledgement information, the management device sends the first configuration information and the second configuration information to the receiving device, where the first configuration information includes information used to indicate the first link group.
  • the receiving end device receives the first configuration information and the second configuration information sent by the management device.
  • the first configuration information may further include a buffer requirement for performing differential delay compensation on the receiving end device for each link, and the receiving end device directly sets the buffer amount of each link according to the buffering requirement.
  • the receiving end device performs corresponding configuration according to the first configuration information and the second configuration information.
  • the receiving end device may return an acknowledgement message to the management device, to indicate that the first configuration information and the second configuration information have been received and configured accordingly. Accordingly, the management device receives the confirmation information returned by the receiving device. It should be understood that G-13 is an optional step.
  • G-15 After receiving the acknowledgement information returned by the receiving device, the management device sends the first configuration information to the source device. It should be understood that G-15 is an optional step.
  • G-16 The source device sends the service data to the receiving device according to the first configuration information.
  • the communication between the source device and the receiving device and the management device regarding the first state information, the first capability information, the first configuration information, the second state information, the second capability information, and the second configuration information may be It is transmitted in the management channel of the OH code block of each device and management device.
  • the above information may be transmitted in a custom frame format in the GFP format, HDLC format, PPP format or RES field of the GCC0 byte of the OH code block.
  • the foregoing information can be transmitted in the form of an Internet Protocol (IP) packet in the management channel of the OH code block. This embodiment does not limit the specific transmission mode.
  • IP Internet Protocol
  • the source device and the receiving device may further include an intermediate device, which may have the capability of differential delay compensation or delayed transmission compensation.
  • the embodiments of the present application are applied to each device, and the link is implemented through capability negotiation. Group compensation.
  • the link group is configured so that the source device only delays the aligned link.
  • the upper bearer transmits service data across links.
  • the first state information, the first capability information, the second state information, the second capability information, the first configuration information, the second configuration information, and the acknowledgement information are involved.
  • the status, capability, or configuration information corresponding to the link may be transmitted on each link, that is, the related information is transmitted at the link granularity.
  • the embodiments of the present application may also transmit related information at other granularities, for example, by using a device as a granularity, which is not limited herein.
  • FIG. 13 is a schematic block diagram of an apparatus 500 for configuring a link group according to an embodiment of the present application.
  • the device 500 of the link group is configured as a first device.
  • the device 500 for configuring a link group may include:
  • the obtaining module 510 is configured to obtain first state information of the M links between the source device and the receiving device, where the first state information is used to indicate between any two links of the M links.
  • the state of the differential delay, 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 acquiring module 510 is further configured to acquire the first capability information of the receiving end 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.
  • the processing module 520 is configured to divide the N links in the M links according to the first state information acquired by the acquiring module 510 and the first capability information acquired by the acquiring module 510 a first link group, wherein N is an integer less than or equal to M and greater than or equal to 2.
  • the sending module 530 is configured to send first configuration information to the second device, where the first configuration information includes information used to indicate the first link group.
  • the device configuring the link group according to the embodiment of the present application, according to the state 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 for the M links,
  • the N links in the links are divided into the first link group, thereby avoiding the case where the differential delay of the M links exceeds the differential delay compensation capability of the receiving end device, and all the M links are unavailable, which can be improved.
  • the first device is the receiving device
  • the second device is the source device
  • the acquiring module 510 is specifically configured to: measure the M chains.
  • the differential delay of the path obtains the first state information;
  • the device 500 further includes: a compensation module 540, configured to perform differential delay compensation on the link in the first link group according to the first configuration information
  • the transmission module 550 is configured to transmit service data with the second device based on the first link group.
  • the acquiring module 510 is specifically configured to: receive the first state information sent by the receiving device, and receive the first capability information sent by the receiving device.
  • the first device is the source device
  • the second device is the receiving device
  • the first device is a management device
  • the second device is The receiving device and/or the source device are included.
  • the K upstream devices of the receiving device have the capability of delaying transmission compensation, where K is a positive integer, and the K upstream devices
  • the processing Block 520 is further configured to: determine, according to the first state information, the first capability information, the second state information, and the second capability information, that each of the upstream devices should perform on the corresponding link Delayed transmission of the compensated configuration.
  • the M links cannot be aligned at the receiving end device, the M links cannot form a link group, or the FlexE Group or the FlexO Group fails to work.
  • the device may also include an intermediate device or the like, which may have the capability of differential delay compensation or delayed transmission compensation.
  • Each device in the embodiments of the present application implements link group compensation through capability negotiation.
  • the link group is configured so that the source device only delays the aligned link.
  • the uplink carries the service data across the links; or through the cooperative compensation of the devices, the final M links can be aligned at the receiving end device, which can ensure the work of the FlexE Group or the FlexO Group, and can improve the link utilization.
  • the first device is the receiving device
  • the second device is the source device
  • the acquiring module 510 is specifically configured to: measure the M chains. Obtaining the first state information; receiving the second capability information and the second state information sent by each of the upstream devices; the sending module 530 is further configured to: send the K
  • the at least one upstream device of the upstream device sends the second configuration information, where the second configuration information is used to indicate that the at least one upstream device should perform delayed transmission compensation for the corresponding link.
  • the device 500 may further include: a compensation module 540, configured to: pass the at least one upstream device to the first link group according to the first configuration information. Performing differential delay compensation on the link that performs delayed transmission compensation according to the second configuration information; the transmission module 550 is configured to transmit service data with the second device based on the first link group.
  • a compensation module 540 configured to: pass the at least one upstream device to the first link group according to the first configuration information. Performing differential delay compensation on the link that performs delayed transmission compensation according to the second configuration information; the transmission module 550 is configured to transmit service data with the second device based on the first link group.
  • the first device is the source device
  • the second device is the receiving device
  • the acquiring module 510 is specifically configured to: receive the receiving end The first state information sent by the device; and the first capability information sent by the receiving device.
  • the first device is included in the K upstream devices, and the device 500 may further include: a transmission module 540, configured to determine, according to the determined first device pair A configuration of delayed transmission compensation that the link should perform, based on the first link group, transmitting service data to the second device.
  • a transmission module 540 configured to determine, according to the determined first device pair A configuration of delayed transmission compensation that the link should perform, based on the first link group, transmitting service data to the second device.
  • the K upstream devices include at least one intermediate device
  • the obtaining module 510 is specifically configured to: receive the foregoing, sent by each of the at least one intermediate device The second capability information and the second state information; the sending module 530 is further configured to: send, to the at least a part of the at least one intermediate device, second configuration information, where the second configuration information is used to indicate A configuration of delaying transmission compensation that at least a portion of the intermediate devices should perform on the corresponding link.
  • the first device is a management device
  • the second device includes the receiving device and/or the source device
  • the acquiring module 510 may be specifically configured to: Receiving the first state information sent by the receiving device, receiving the first capability information sent by the receiving device, and receiving the second capability information and the second Status information
  • the sending module 530 is further configured to: send, to the at least one upstream device of the K upstream devices, second configuration information, where the second configuration information is used to indicate that the at least one upstream device pairs The link should be delayed to send a compensated configuration.
  • the first configuration information includes a flag indicating that the link belongs to the first link group.
  • the sending module 530 is specifically configured to send the first configuration information to a second device in a reserved field of the overhead code block.
  • the sending module 530 is specifically configured to: indicate that the first link of the N links belongs to the first group of the first link group The configuration information is sent to the second device by using the first link.
  • the first part of the first configuration information is used to indicate that the first link and other links form the first link group, and the first configuration The second part of the bits in the information is the label of the first link group.
  • the acquiring module 510 is specifically configured to: receive, by the receiving end device, a first type of a link layer discovery protocol LLDP format that is carried in a management channel of an overhead code block.
  • the first TLV unit is further configured to be configured to indicate, when the receiving end device sends service data to the source device, the receiving end device pairs the M The link performs information to delay the transmission of the current state of the compensation.
  • the first TLV unit is further capable of carrying information indicating a configuration of the delayed transmission compensation that the upstream device should perform on the corresponding link.
  • the acquiring module 510 is specifically configured to: receive, by the receiving end device, a second type of a link layer discovery protocol LLDP format that is carried in a management channel of an overhead code block.
  • the length value is the first capability information in the TLV unit.
  • the second TLV unit is further configured to be configured to indicate that when the receiving end device sends service data to the source device, the receiving end device pairs the M The link performs the ability to delay the transmission of compensation.
  • the obtaining module 510 in the embodiment of the present application may be implemented by a processor or a processor-related circuit component.
  • Some functions of the acquiring module 510 may be implemented by a network interface or a network interface related circuit component, and the processing module 520 may be implemented by The processor or processor related circuit component is implemented, and the transmitting module 530 can be implemented by a network interface or a network interface related circuit component.
  • the embodiment of the present application further provides a device 600 for configuring a link group, where the device 600 of the link group is a first device, and the device 600 for configuring the link group includes a processor 610, and the memory 620.
  • the memory 620 is used to store instructions
  • the processor 610 and the network interface 630 are used to execute instructions stored by the memory 620.
  • the first device obtains first state information of the M links between the source device and the receiving device, where the first state information is used to indicate a differential delay between any two links of the M links.
  • a state in which 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 acquires 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;
  • N Determining, by the first device, the N links of the M links to the first link group, where N is less than or equal to M and according to the first state information and the first capability information, An integer greater than or equal to 2;
  • the first device sends first configuration information to the second device, where the first configuration information includes information used to indicate the first link group.
  • the device configuring the link group according to the embodiment of the present application, according to the state 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 for the M links,
  • the N links in the links are divided into the first link group, thereby avoiding the case where the differential delay of the M links exceeds the differential delay compensation capability of the receiving end device, and all the M links are unavailable, which can be improved.
  • the device 500 configuring the link group shown in FIG. 13 or the device 600 configuring the link group shown in FIG. 14 may be used to perform operations or processes related to the terminal device in the foregoing method embodiments, and configure the link group.
  • the operations and/or functions of the modules in the device 500 or the device in the configuration of the link group are respectively omitted in order to implement the corresponding processes in the foregoing method embodiments.
  • processors mentioned in the embodiment of the present invention may be a central processing unit (CPU), and may also be other general-purpose processors, digital signal processors (DSPs), and application specific integrated circuits ( Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory referred to 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 memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory.
  • the volatile memory can be a Random Access Memory (RAM) that acts as an external cache.
  • RAM Random Access Memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM). SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Synchronous Connection Dynamic Random Access Memory (Synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (DR RAM).
  • processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) is integrated in the processor.
  • memories described herein are intended to comprise, without being limited to, these and any other suitable types of memory.
  • the embodiment of the present invention further provides a computer readable storage medium storing thereon a method of storing a command, and when the instruction is run on a computer, causing the computer to execute the method for configuring a link group in the foregoing method embodiment.
  • the computer may be the device that configures the link group, that is, the first device.
  • the embodiment of the invention further provides a computer program product comprising instructions, wherein when the computer runs the finger of the computer program product, the computer executes the method for configuring a link group of the method embodiment.
  • the computer program product can be run on the device configuring the link group, that is, the first device.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a high-density digital video disc (DVD)), or a semiconductor medium (for example, a solid state hard disk (Solid State Disk, SSD)) and so on.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a high-density digital video disc (DVD)
  • DVD high-density digital video disc
  • semiconductor medium for example, a solid state hard disk (Solid State Disk, SSD)
  • the size of the serial numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be taken to the embodiments of the present invention.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Environmental & Geological Engineering (AREA)
  • Physics & Mathematics (AREA)
  • Electromagnetism (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)

Abstract

本申请提供一种配置链路组的方法和设备，该方法包括：第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，第一状态信息用于指示M个链路中任意两个链路之间的差分延迟的状态，任一个链路为FlexE或FlexO物理连接链路，M为大于或等于2的整数；第一设备获取接收端设备的第一能力信息，第一能力信息用于指示接收端设备对M个链路进行差分延迟补偿的第一能力；第一设备根据第一状态信息和第一能力信息，将M个链路中的N个链路划分到第一链路组，N为小于或等于M且大于或等于2的整数；第一设备向第二设备发送第一配置信息，其中包括用于指示第一链路组的信息。本申请提供的方法，能够提高传送网中链路的可用性和鲁棒性。

Description

配置链路组的方法和设备
本申请要求于2017年04月28日提交中国专利局、申请号为201710295516.7、申请名称为“配置链路组的方法和设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及传送网领域，并且更具体地，涉及一种配置链路组的方法和设备。
背景技术
当前在以太网传送网中，通常会通过链路聚合组(Link Aggregation Group，LAG)技术，将多个物理连接链路(以下简称“链路”)绑定为一个逻辑链路，以增大带宽并提高链路的可用性。
具体地，LAG技术通常将相邻设备之间的S个带宽速率R相同的物理连接链路绑定为一个带宽速率为S*R LAG，以实现带宽速率的线性提升，从而满足带宽增长的需求。对于介质访问控制(Media Access Control，MAC)层以上的用户业务，LAG表现为一个逻辑接口。传输设备可以根据源MAC地址和/或目的MAC地址、或者虚拟局域网(Virtual Local Area Network，VLAN)标签等信息对来自MAC层的报文进行分类，区分出不同的业务。例如，源MAC地址与目的MAC地址相同的报文归属为同一个业务，多个业务经过哈希算法处理之后被分配约束到LAG的一个特定的链路发送。因为LAG技术中，一个业务的报文只会从一个链路发送，对该业务而言，不存在报文乱序问题，LAG无需对各链路的传输时延差进行补偿。然而也正是由于LAG技术中一个业务的报文只会从一个链路发送，即业务中的一个具体的业务的流量不能超过单个链路的带宽速率R，因此LAG对单个业务并不能体现S*R的带宽速率。
灵活以太网(Flexible Ethernet，FlexE)或灵活光传送网(Flexible OTN，FlexO)可以通过链路的绑定级联形成链路聚合组，以支持跨多个链路并行传输，来承载至少一个业务。其中，OTN是指光传送网(Optical Transport Network)。由于业务跨链路传输，因此需要对各个链路的传输时延进行差分延迟补偿，以对齐多个链路上并行传输的业务。接收端设备的差分延迟补偿能力在实际中受到一定的工程限制，如果某个链路的差分延迟超过该接收端设备的差分延迟补偿能力，将导致整个链路聚合组失效。
发明内容
本申请提供一种配置链路组的方法和设备，能够提高传送网中链路的可用性和鲁棒性。
第一方面，提供了一种配置链路组的方法，包括：第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，所述第一状态信息用于指示所述M个链路中任意两 个链路之间的差分延迟的状态，所述M个链路中的任意一个链路为灵活以太网FlexE物理连接链路或者灵活光传送网FlexO物理连接链路，其中，M为大于或等于2的整数；所述第一设备获取所述接收端设备的第一能力信息，所述第一能力信息用于指示所述接收端设备对所述M个链路进行差分延迟补偿的第一能力；所述第一设备根据所述第一状态信息和所述第一能力信息，将所述M个链路中的N个链路划分到第一链路组，其中，N为小于或等于M且大于或等于2的整数；所述第一设备向第二设备发送第一配置信息，所述第一配置信息包括用于指示所述第一链路组的信息。
应理解，第一设备是决定链路组划分方式的决策设备，第二设备包括配合决策设备完成链路组配置的相关设备。
还应理解，第一方面的配置链路组的方法应用于在接收端设备处，M个链路无法对齐的情况，或者说接收端设备的对所述M个链路进行差分延迟补偿的第一能力不能实现将M个链路对齐的情况。
第一方面的配置链路组的方法，第一设备根据源端设备和接收端设备之间的M个链路的差分延迟的状态和接收端设备对M个链路进行差分延迟补偿的能力，将M个链路中的N个链路划分到第一链路组，从而避免了M个链路的差分延迟超出接收端设备的差分延迟补偿能力时所有的M个链路不可用的情况，可以提高传送网中链路的可用性和鲁棒性。
在第一方面的一种可能的实现方式中，所述第一设备为所述接收端设备，所述第二设备为所述源端设备，所述第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，包括：所述第一设备测量所述M个链路的差分延迟，获得所述第一状态信息；所述方法还包括：所述第一设备根据所述第一配置信息，对所述第一链路组中的链路进行差分延迟补偿；所述第一设备基于所述第一链路组，与所述第二设备传输业务数据。在本可能的实现方式中，由接收端设备作为决策设备确定链路组的配置，执行简单方便，进行链路组配置时信令开销小。
在第一方面的一种可能的实现方式中，所述第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，包括：所述第一设备接收所述接收端设备发送的所述第一状态信息；所述第一设备获取所述接收端设备的第一能力信息，包括：所述第一设备接收所述接收端设备发送的所述第一能力信息。
其中，一种可能的实现方式中，所述第一设备为所述源端设备，所述第二设备为所述接收端设备。在本可能的实现方式中，由源端设备作为决策设备，可以结合业务数据的相关信息，例如业务数量和/或带宽等综合因素确定链路组的配置。
其中，另一种可能的实现方式中，所述第一设备为管理设备，所述第二设备包括所述接收端设备和/或所述源端设备。在本可能的实现方式中，由管理设备作为决策设备，一来可以接收源端设备和接收端设备的相关信息，能够考虑例如业务数量和/或带宽等综合因素确定链路组的配置；二来能够避免由源端设备或接收端设备做决策时可能引发的计算量，可以减轻源端设备和接收端设备的负担。
在第一方面的一种可能的实现方式中，在所述M个链路上，所述接收端设备的K个上游设备具有延迟发送补偿的能力，其中，K为正整数，所述K个上游设备包括所述源端设备和/或至少一个中间设备，所述中间设备在所述M个链路上位于所述源端设备与所述 接收端设备之间，所述方法还包括：所述第一设备获取所述K个上游设备的每个上游设备的第二能力信息和第二状态信息，所述第二能力信息用于指示所述每个上游设备对所述M个链路中的至少一个链路进行延迟发送补偿的第二能力，所述第二状态信息用于指示所述每个上游设备对所述M个链路中的至少一个链路进行延迟发送补偿的当前状态；所述第一设备根据所述第一状态信息和所述第一能力信息，将所述M个链路中的N个链路划分到第一链路组，包括：所述第一设备根据所述第一状态信息、所述第一能力信息、所述第二状态信息和所述第二能力信息，将所述M个链路中的所述N个链路划分到所述第一链路组；所述方法还包括：所述第一设备根据所述第一状态信息、所述第一能力信息、所述第二状态信息和所述第二能力信息，确定所述每个上游设备对相应的链路应进行的延迟发送补偿的配置。
在接收端设备处M个链路无法对齐时，M个链路不能组成一个链路组，或者说FlexE Group或FlexO Group崩溃无法工作，本申请各实施例的源端设备、接收端设备，还可以包括中间设备等均可能有差分延迟补偿或延迟发送补偿的能力，本可能的实现方式各设备通过能力协商实现链路组的补偿。使得当源端设备、接收端设备之间的FlexE Group或FlexO Group中各设备的补偿能力无法补偿各链路的差分延迟时，通过配置链路组，使得源端设备只在延迟对齐的链路上承载跨链路传输业务数据；或者通过各设备协同补偿，使得最终M个链路在接收端设备处可以对齐，能够保证FlexE Group或FlexO Group的工作，可以提高链路的利用率。
在第一方面的一种可能的实现方式中，所述第一设备为所述接收端设备，所述第二设备为所述源端设备，所述第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，包括：所述第一设备测量所述M个链路的差分延迟，获得所述第一状态信息；所述第一设备获取所述K个上游设备的每个上游设备的第二能力信息和第二状态信息，包括：所述第一设备接收所述每个上游设备发送的所述第二能力信息和所述第二状态信息；所述方法还包括：所述第一设备向所述K个上游设备中的至少一个上游设备发送第二配置信息，所述第二配置信息用于指示所述至少一个上游设备对相应的链路应进行延迟发送补偿的配置。
在第一方面的一种可能的实现方式中，所述方法还包括：所述第一设备根据所述第一配置信息，对所述第一链路组中已经过所述至少一个上游设备根据所述第二配置信息进行延迟发送补偿的链路进行差分延迟补偿；所述第一设备基于所述第一链路组，与所述第二设备传输业务数据。
在第一方面的一种可能的实现方式中，所述第一设备为所述源端设备，所述第二设备为所述接收端设备，所述第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，包括：所述第一设备接收所述接收端设备发送的所述第一状态信息；所述第一设备获取所述接收端设备的第一能力信息，包括：所述第一设备接收所述接收端设备发送的所述第一能力信息。
在第一方面的一种可能的实现方式中，所述K个上游设备中包括所述第一设备，所述方法还包括：所述第一设备根据确定的所述第一设备对相应的链路应进行的延迟发送补偿的配置，基于所述第一链路组，向所述第二设备传输业务数据。
在第一方面的一种可能的实现方式中，所述K个上游设备中包括至少一个中间设备， 所述第一设备获取所述K个上游设备的每个上游设备的第二能力信息和第二状态信息，包括：所述第一设备接收所述至少一个中间设备中的每个中间设备发送的所述第二能力信息和所述第二状态信息；所述方法还包括：所述第一设备向所述至少一个中间设备中的至少部分中间设备发送第二配置信息，所述第二配置信息用于指示所述至少部分中间设备对相应的链路应进行的延迟发送补偿的配置。
在第一方面的一种可能的实现方式中，所述第一设备为管理设备，所述第二设备包括所述接收端设备和/或所述源端设备，所述第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，包括：所述第一设备接收所述接收端设备发送的所述第一状态信息；所述第一设备获取所述接收端设备的第一能力信息，包括：所述第一设备接收所述接收端设备发送的所述第一能力信息；所述第一设备获取所述K个上游设备的每个上游设备的第二能力信息和第二状态信息，包括：所述第一设备接收所述每个上游设备发送的所述第二能力信息和所述第二状态信息；所述方法还包括：所述第一设备向所述K个上游设备中的至少一个上游设备发送第二配置信息，所述第二配置信息用于指示所述至少一个上游设备对相应的链路应进行的延迟发送补偿的配置。
在第一方面的一种可能的实现方式中，所述第一配置信息包括用于指示链路属于所述第一链路组的标记。
在第一方面的一种可能的实现方式中，所述第一设备向第二设备发送第一配置信息，包括：所述第一设备将所述第一配置信息承载在开销码块的保留字段中发送给所述第二设备。
在第一方面的一种可能的实现方式中，所述第一设备向第二设备发送第一配置信息，包括：所述第一设备将用于指示所述N个链路中的第一链路属于所述第一链路组的所述第一配置信息，通过所述第一链路发送给所述第二设备。
在第一方面的一种可能的实现方式中，所述第一配置信息中的第一部分比特用于指示所述第一链路与其他链路组成所述第一链路组，所述第一配置信息中的第二部分比特为所述第一链路组的标记。
在第一方面的一种可能的实现方式中，所述第一设备接收所述接收端设备发送的所述第一状态信息，包括：所述第一设备接收由所述接收端设备发送的，承载在开销码块的管理通道的链路层发现协议LLDP格式的第一类型长度值TLV单元中的所述第一状态信息。
在第一方面的一种可能的实现方式中，所述第一TLV单元还能够承载用于指示在所述接收端设备向所述源端设备发送业务数据时，所述接收端设备对所述M个链路进行延迟发送补偿的当前状态的信息。
在第一方面的一种可能的实现方式中，所述第一TLV单元还能够承载用于指示上游设备对相应的链路应进行的延迟发送补偿的配置的信息。
在第一方面的一种可能的实现方式中，所述第一设备接收所述接收端设备发送的所述第一能力信息，包括：所述第一设备接收由所述接收端设备发送的，承载在开销码块的管理通道的链路层发现协议LLDP格式的第二类型长度值TLV单元中的所述第一能力信息。
在第一方面的一种可能的实现方式中，所述第二TLV单元还能够承载用于指示在所述接收端设备向所述源端设备发送业务数据时，所述接收端设备对所述M个链路进行延迟发送补偿的能力的信息。
第二方面，提供了一种配置链路组的设备，该配置链路组的设备为第一设备，用于执行上述第一方面或第一方面的任一可能的实现方式中的方法。具体地，所述配置链路组的设备可以包括用于执行第一方面或第一方面的任一可能的实现方式中的方法的模块。
第三方面提供一种配置链路组的设备，该配置链路组的设备为第一设备，所述配置链路组的设备包括处理器、存储器和网络接口，所述存储器用于存储指令，所述处理器和网络接口用于执行所述存储器存储的指令，并且对所述存储器中存储的指令的执行使得所述处理器和网络接口执行第一方面或第一方面的任一可能的实现方式中的方法。
第四方面提供一种配置链路组的设备，该配置链路组的设备为第一设备，所述配置链路组的设备包括处理器、存储器和网络接口，所述存储器用于存储指令，所述处理器和网络接口用于执行所述存储器存储的指令，并且对所述存储器中存储的指令的执行使得：第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，所述第一状态信息用于指示所述M个链路中任意两个链路之间的差分延迟的状态，所述M个链路中的任意一个链路为灵活以太网FlexE物理连接链路或者灵活光传送网FlexO物理连接链路，其中，M为大于或等于2的整数；所述第一设备获取所述接收端设备的第一能力信息，所述第一能力信息用于指示所述接收端设备对所述M个链路进行差分延迟补偿的第一能力；所述第一设备根据所述第一状态信息和所述第一能力信息，将所述M个链路中的N个链路划分到第一链路组，其中，N为小于或等于M且大于或等于2的整数；所述第一设备向第二设备发送第一配置信息，所述第一配置信息包括用于指示所述第一链路组的信息。
第五方面提供一种计算机存储介质，其上存储有指令，当所述指令在计算机上运行时，使得所述计算机执行第一方面或第一方面的任一种可能的实现方式所述的方法。
第六方面提供一种包括指令的计算机程序产品，当计算机运行所述计算机程序产品的所述指时，所述计算机执行第一方面或第一方面的任一种可能的实现方式所述的方法。
第二方面至第六方面所能获得的效果与第一方面所能获得的效果对应，此处不再一一赘述。
应理解，本申请各方面及其相应的实现方式中，涉及到第一状态信息、第一能力信息、第二状态信息、第二能力信息、第一配置信息和第二配置信息中的任意一种的传输时，可以在每个链路上传输该链路对应的状态、能力或配置信息，即以链路为粒度传输相关信息。当然，本申请各方面及其相应的实现方式也可以以其他粒度传输相关信息，例如，以设备为粒度，此处不作限定。
还应理解，本申请各方面及其相应的实现方式中差分延迟补偿是指延迟接收补偿，即接收方向上的补偿，一般也称为“deskew”；延迟发送补偿即发送方向上的补偿，一般也称为“remote deskew”。
附图说明
图1是100G的FlexE的接口上的码块流的示意图。
图2是FlexE中接收端设备的功能结构的示意性框图。
图3是FlexE中接收端设备发送码块流的示意图。
图4是FlexE开销码块的帧格式的示意图。
图5是FlexE跨传送网传输的应用场景的示意图。
图6是本申请一个实施例的配置链路组的方法的示意性流程图。
图7是本申请一个实施例的链路的差分延迟的状态的示意图。
图8是本申请一个实施例的一种配置链路组的结果的示意图。
图9是本申请一个实施例的配置链路组以及进行补偿的流程的示意图。
图10是本申请一个实施例的配置链路组以及进行补偿的流程的示意图。
图11是本申请一个实施例的配置链路组以及进行补偿的流程的示意图。
图12是本申请一个实施例的配置链路组以及进行补偿的流程的示意图。
图13是本申请一个实施例的配置链路组的设备的示意性框图。
图14是本申请另一个实施例的配置链路组的设备的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
应理解，本申请实施例的技术方案可以应用于FlexO或FlexE等网络，本申请实施例对此不作限定。
应理解，本申请实施例的物理连接链路可以简称为“链路”，在FlexE中链路也可以称为“PHY链路”。本申请实施例的链路是指源端设备和接收端设备之间的链路，从源端设备到接收端设备的链路上可以存在中间设备。
下面对本说明书中涉及的概念进行简单的介绍。
FlexE技术：
以太网在过去的相当一段时间内获得了广泛的应用和长足的发展。以太网接口的速率以10倍的速度提升，从10Mbps向100Mbps、1000Mbps(1Gbps)、10Gbps、100Gbps不断演进发展。随着以太网接口的速率的不断提升，进一步提高以太网接口的速率在技术上逐渐遇到瓶颈。同时，为了适应实际场景中多样化的以太网接口的速率需求，200Gbps等。发展出了40Gbps、200Gbps和400Gbps的以太网接口。
在新一代更高速率的以太网接口的标准诞生之前，网络对于带宽的需求通常会超过现有以太接口速率。在新的以太网接口的标准诞生及新的以太网接口成本较高的过渡期，LAG技术通过将多个低速率的以太网接口绑定为一个LAG，可以实现虚拟的高速率的以太网接口。然而LAG技术是通过哈希算法，将业务数据按业务分配到LAG中的各个接口上。与基于业务的负载均衡方法类似，LAG也具有接口带宽分配不均衡利用率不高的问题。如果有大于单一接口速率的业务，通过哈希算法也只能分配到某一个接口上，这会造成该接口拥塞且业务传输速率受限于该接口的速率。
在转发设备中，业务从低速率的接口向高速率的接口转发时，需要缓存整个业务的报文再转发以防止报文断裂，这就使得业务数据的传输时延大大增加。为提高不同速率接口之间的转发效率，光联网论坛(Optical Internet Forum，OIF)发布了多链路变速箱(Multi Link Gearbox，MLG)技术，可以反向复用高速率的以太网接口将其划分为若干个低速率的以太网接口。但是，MLG技术只支持几种固定的接口划分方式，例如，将40G以太网接口划分为4×10G或2×20G以太网接口，支持的子接口类型有限，灵活性不够高。
FlexE技术即为面向上述需求所开发的灵活以太网的接口技术。图1是100G的FlexE的接口上的码块流的示意图。FlexE 1.0标准定义，通过将100G以太网接口的业务以20 个码块(block)为周期进行时分复用，FlexE将100G以太网接口划分为以5G为颗粒的20个时隙(与20个码块周期中的1个码块对应)。每间隔1023×20个数据码块插入一个FlexE开销(Overhead，OH)码块，具体如图1所示。FlexE可以将S个以太网接口绑定为一个链路聚合组，业务数据可以在链路聚合组的20*S个时隙中任意选择空闲的时隙传输。
图2是FlexE中接收端设备的功能结构的示意性框图。如图2所示，FlexE技术在以太网接口的物理编码子层(Physical Coding Sublayer，PCS)上插入一个新的层，灵活以太网片(FlexE Shim)层。FlexE Shim层向上承接多个灵活以太网业务(FlexE Client)，向下连接多个100G以太网接口。FlexE 1.0标准规定FlexE Client为64/66B编码的码块流(block stream)，经过空闲码块插入/删除(Idle Insert/Delete)进行速率适配之后，将灵活以太网业务的码块流中的码块轮流放入分配给该灵活以太网业务的时隙中。
图3是FlexE中接收端设备发送码块流的示意图。如图3所示，在FlexE中，对于S个物理连接链路组成的链路聚合组，即由S个物理链路(Physical，PHY)组成的灵活以太网组(FlexE Group)，共有20*S个时隙。灵活以太网片(FlexE Shim)层用一个20*S长度的时隙分配表(Calendar)来分派66B码块的位置。例如，一个周期中前20个码块用PHY1发送，后续的20个码块用PHY2发送，以此类推直到PHYS。这里每个PHY上的20个码块也可称为一个子时隙分配表(Sub-calendar)。在一个具体的例子中，10G的灵活以太网业务占据20*S个时隙中的某两个时隙，则在一个周期中从10G的灵活以太网业务的码块流中提取两个码块置于对应的位置(1个码块对应1个5G时隙)。在另一个具体的例子中，25G的灵活以太网业务则占据5个时隙，每个周期将从25G的灵活以太网业务的码块流中提取5个码块置于calendar中对应的位置。FlexE Group中各个时隙分别传输哪些灵活以太网业务的配置信息在FlexE OH码块中的特定字段上来指定。
图4是FlexE开销码块的帧格式的示意图。如图4所示，32个连续的FlexE帧构成一个FlexE复帧，一个FlexE OH帧由8个连续的FlexE OH码块组成。FlexE帧中第一个码块以“0x4B”或“0x5”字段作为标记字段，以用于识别该码块为OH码块。当接收端设备识别到该OH码块后，再接收1023×20个64/66B码块(数据码块)后可收到下一个OH码块，依次类推可从码块流中提取出整个FlexE帧。
如图4所示，各个链路上传输的FlexE OH帧中包括灵活以太网组编号(FlexE Group Number)、物理链路图(PHY Map)、物理链路编号(PHY Number)、时隙分配表(Calendar)A、Calendar B等字段。FlexE Group Number用于指示该链路所在的灵活以太网组编号；PHY Map(一个FlexE复帧中共需8×32＝256bits来指示)用于指示该链路所在的灵活以太网组中包括的PHY的分布；物理链路编号可以是1～254；Calendar A与Calendar B分别用于指示该FlexE Group的当前Calendar配置与备用Calendar配置。每个FlexE帧的第三个码块中有16bit用于指示时隙上所传输的业务数据的编号。每个FlexE复帧中的第一个FlexE帧携带对应时隙0(slot 0)中所传输的业务数据的编号，以此类推，直到FlexE复帧中第20个FlexE帧携带对应slot 19中所传输的业务数据的编号。接收端设备收到FlexE Group中所有链路上的FlexE帧信息后，即可得到该FlexE Group中各个业务数据的时隙分配方式。
由于在FlexE中业务数据可以在跨链路的多个时隙上传输，接收端设备在从多个时隙 中恢复灵活以太网业务之前就需要对FlexE Group中的各个链路进行差分延迟补偿，否则从存在差分延迟的跨链路的时隙中恢复灵活以太网业务就会产生码块乱序的问题。FlexE1.0标准规定：FlexE Group以各链路上传输的FlexE帧的第一个开销码块为标记，通过在接收端设备缓存(Buffer)对各链路的传输时延进行对齐。通常，在FlexE Group片对片(shim-to-shim)直连的传输场景下各链路的差分延迟补偿(deskew)能力至少为300ns，在FlexE Group长距跨传送网传输时各链路差分延迟补偿能力至少为10us。
由于业务数据可以在FlexE Group内跨链路的多个时隙上传输，因而在接收端设备需要将多个链路上的FlexE帧对齐，以保证业务数据能从对应的时隙中以正确的顺序恢复出来。FlexE 1.0标准以FlexE帧边界为参考，计算各链路的差分延迟并通过缓存将各链路上的码块流对齐。如前所述，对于FlexE Group片对片(shim-to-shim)直连的传输场景，FlexE标准规定的FlexE Group内各链路的差分延迟应<＝300ns；对于长距跨传送网传输场景，各链路的差分延迟应<＝10us。如果FlexE Group内某个链路上的差分延迟超过接收端设备的差分延迟补偿能力，则整个FlexE Group将失效。
FlexO技术：
FlexO是通过绑定多个标准速率的端口(例如m×100G)，组成灵活光传送网组(FlexO Group)，以承载标准光传输单元Cn(Optical Transport Unit-Cn，OTUCn)(n≥1)信号，这补充了之前的协议中没有定义带宽大于100G的端口的不足。类似FlexE地，由于OTUCn信号会在多个链路上跨链路传输，因而需要将各链路上传输的业务数据对齐，以保证所传输OTUCn信号的恢复。目前FlexO规定通过各链路上所传输的OTUCn帧中的帧定位信号(Frame Alignment Signal，FAS)字段实现FlexO Group中各链路上的业务数据的对齐。如果FlexO Group中某条链路的差分延迟超过接收端设备的差分延迟补偿能力，则整个FlexO Group将失效。
链路层发现协议(Link Layer Discovery Protocol，LLDP)技术：
本申请实施例还涉及LLDP技术。LLDP是标准802.1AB中定义的链路层发现协议。通过LLDP，传送网设备可通过标准LLDP类型长度值(Type Length Value，TLV)单元定期向相邻的其他传送网设备发送承载有本地信息的组播报文。LLDP规定传送网设备的每个端口上都有标准的简单网络管理协议(Simple Network Management Protocol，SNMP)管理信息库(Management Information Base)MIB，用于存储本地和相邻的其他传送网设备的状态信息。传送网设备之间通过发送和接收LLDP TLV单元以刷新SNMP MIB中存储的状态信息。通过LLDP可方便传送网设备的状态信息的管理和维护。
TLV单元是LLDP中的基本信息单元，不同类型的TLV可以承载不同的信息。其中，LLDP预留了一种可供各标准组织自定义的TLV单元。表1是可自定义的LLDP格式的TLV单元各字段的定义。应理解，本说明书中的表2至表7示出的TLV单元均是表1示出的TLV单元的具体应用形式。
表1 可自定义的LLDP格式的TLV单元
Figure PCTCN2018082469-appb-000001
Figure PCTCN2018082469-appb-000002
下面结合图2和图5介绍应用本申请实施例的配置链路组的方法的场景。如图2所示，FlexE工作于MAC层与PHY层之间。FlexE通过修改原有的协调子层(Reconciliation Sublayer，RS)及PCS，来实现将传统以太网端口划分时分复用(Time Division Multiplexing，TDM)的通道及多个以太网端口绑定的功能。LLDP以及LAG技术则工作于MAC层。FlexE 1.0标准定义了FlexE的以太网传输以及跨传送网传输的应用场景。图5是FlexE跨传送网传输的应用场景的示意图。FlexE跨传送网传输是基于FlexE可感知传输(FlexE Aware Transport)模式的。图5中以太网路由器中的灵活以太网片(FlexE Shim)需要对与其相连的FlexE Group中的两条链路进行差分延迟补偿。FlexO工作于PHY层，与FlexE类似地，同样需要对多条链路进行差分延迟补偿。
基于FlexE中FlexE Group可能失效的情况和FlexO中FlexO Group可能失效的情况，本申请实施例提供了一种配置链路组的方法。本申请实施例通过对涉及的FlexE或FlexO相关的功能部件的改造来实现传送网设备之间的补偿协商。经本申请实施例的改造之后，传送网设备在链路组建立时允许链路组中存在超出接收端设备的差分延迟补偿能力的链路。应理解，本申请实施例涉及的传送网设备可以包括源端设备、中间设备和接收端设备。
图6是本申请一个实施例的配置链路组的方法100的示意性流程图。如图6所示，配置链路组的方法100可以包括以下步骤。
S110，第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，第一状态信息用于指示M个链路中任意两个链路之间的差分延迟的状态，M个链路中的任意一个链路为灵活以太网FlexE物理连接链路或者灵活光传送网FlexO物理连接链路，其中，M为大于或等于2的整数。
S120，第一设备获取接收端设备的第一能力信息，第一能力信息用于指示接收端设备对M个链路进行差分延迟补偿的第一能力。
S130，第一设备根据第一状态信息和第一能力信息，将M个链路中的N个链路划分到第一链路组，其中，N为小于或等于M且大于或等于2的整数。
S140，第一设备向第二设备发送第一配置信息，第一配置信息包括用于指示第一链路组的信息。
应理解，第一设备是决定链路组划分方式的决策设备，第二设备包括配合决策设备完成链路组配置的相关设备。
还应理解，本申请各实施例中差分延迟补偿是指延迟接收补偿，即接收方向上的补偿，一般也称为“deskew”；延迟发送补偿即发送方向上的补偿，一般也称为“remote deskew”。
本申请实施例的配置链路组的方法，第一设备根据源端设备和接收端设备之间的M个链路的差分延迟的状态和接收端设备对M个链路进行差分延迟补偿的能力，将M个链路中的N个链路划分到第一链路组，从而避免了M个链路的差分延迟超出接收端设备的差分延迟补偿能力时所有的M个链路不可用的情况，可以提高传送网中链路的可用性和鲁棒性。
在FlexE中，FlexE Group中各链路上的数据流为1OH block+1023×20Data blocks的 64/66B码块流的格式，接收端设备以各链路上传输的FlexE帧的第一个OH block中的0x4B和0x5标识字段为标记，对各链路上的数据码块进行对齐。
同样地，FlexO帧为128行5440bits的数据流，8个帧为一个复帧。接收端设备以各FlexO帧中承载的OTUCn帧中的FAS字段为标记，对各链路上的数据码块进行对齐。
两种传送网可以统一使用本申请实施例的配置链路组过程以及后续的补偿过程。各实施例以FlexE为例进行说明，当然本申请实施例的配置链路组的方法也可以应用于FlexO中，或者应用于跨FlexE和FlexO的传送网中。
图7是本申请一个实施例的链路的差分延迟的状态的示意图。如图7所示，源端设备和接收端设备之间有5条链路PHY1-PHY5，各条链路相互独立地在源端设备和接收端设备之间发送FlexE帧。图7的横轴表示各链路上FlexE帧到达的时间延迟，阴影框的宽度表示接收端设备的差分延迟补偿的能力。如图7所示的5条链路，PHY1和PHY2之间的差分延迟相近，PHY3、PHY4和PHY5的差分延迟相近，但是接收端设备的差分延迟补偿的能力无法完成对PHY1-PHY5的差分延迟补偿。
下面结合几个实施例对本申请的配置链路组的方法进行详细的描述。
实施例1：
在本实施例中，第一设备即决策设备为接收端设备，第二设备为源端设备。接收端设备具有延迟接收补偿的能力。
在本实施例中，S110第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，可以包括：第一设备测量M个链路的差分延迟，获得第一状态信息。具体地，接收端设备可以通过现有的一些方案测量M个链路的差分延迟，从而获得第一状态信息。
具体而言，本申请各实施例可以通过测量各链路传输时延从而比较出任意两条链路之间的差分延迟；或者通过在接收端设备处增加一个计数器，收到最快的链路的标记码块之后从0开始计数，收到其他链路上的标记码块后记下此时计数器值x，则这两条链路的传输时延差为x码块对应的传输时间。本申请各实施例对测量M个链路的差分延迟的具体方式不作限定。
在图7示出的具体例子中，第一状态信息可以是PHY1和PHY2之间的差分延迟相近，PHY3、PHY4和PHY5的差分延迟相近，但是接收端设备的差分延迟补偿的能力无法完成对PHY1-PHY5的差分延迟补偿。
受到接收端设备的差分延迟补偿的能力的限制，接收端设备无法支持所有的PHY1-PHY5的差分延迟补偿。考虑最大化支持跨链路的业务的成员链路的数量，可以从源端设备和接收端设备之间的全部M个链路中选择N个链路标记为“selected”，其他M-N个链路标记为“standby”。本实施例例中N＝3，即PHY3、PHY4和PHY5标记为“selected”，其他2个链路PHY1和PHY2标记为“standby”。标记为“selected”的PHY3、PHY4和PHY5组成第一链路组，在第一链路组的3个链路上可以承载跨链路的业务。标记为“standby”的PHY1和PHY2可以用于独立传输完整的业务，或者标记为“standby”的PHY1和PHY2处于备用状态，在备用状态时不传输业务。业务不在被标记为“standby”的链路上并行传输，也不在分别标记为“standby”和标记为“selected”的两个链路上并行传输。
另外，也可以考虑建立两个链路组。图8是本实施例的一种配置链路组的结果的示意图。将链路PHY3、PHY4和PHY5标记为“selected1”，即第一链路组，用于承载跨链路的 业务；将链路PHY1和PHY2标记为“selected2”，即第二链路组，用于承载跨链路的业务。业务不能在标记为“selected1”的第一链路组和标记为“selected2”的第二链路组上跨链路组传输。
除以上两种配置链路组的方案外，本申请实施例还可以有更多不同的根据链路之间的差分延迟的状态以及接收端设备对链路进行差分延迟补偿的能力确定链路组的配置方案，本申请实施例对此不作限定。
应理解，以上仅是以M＝5为例对本申请实施例的配置链路组的方法进行的说明，而非对本申请实施例的配置链路组的方法的限定。
可选地，本实施例的配置链路组的方法还可以包括：第一设备基于第一链路组，与第二设备传输业务数据；第一设备根据第一配置信息，对第一链路组中的链路进行差分延迟补偿。
图9是本实施例的配置链路组以及进行补偿的流程200的示意图。该流程200可以包括以下步骤。
S210，源端设备和接收端设备之间启动链路。
S220，源端设备通过M个链路分别独立地向接收端设备发送数据帧。相应地，接收端设备接收源端设备发送的数据帧。应理解，这些数据帧中可以包括对齐标记。
S230，接收端设备测量M个链路的差分延迟的状态，获得第一状态信息。
S240，接收端设备根据第一状态信息以及可以表示接收端设备对M个链路进行差分延迟补偿的能力的第一能力信息，确定如何配置链路组，即确定第一配置信息。具体地配置中包括将M个链路中的N个链路划分到第一链路组。
S250，接收端设备对M个链路进行差分延迟补偿。具体地，接收端设备根据第一配置信息进行差分延迟补偿，即设置差分延迟的缓存大小。换而言之，接收端设备根据自身确定的链路组配置对第一链路组中的链路进行差分延迟补偿。应理解，S250可以和S260同时进行，本实施例对此不作限定。
S260，接收端设备向源端设备发送第一配置信息，第一配置信息包括用于指示第一链路组的信息。相应地，源端设备接收接收端设备发送的第一配置信息。第一配置信息的形式可以有多种，将在下文中进行详细描述。
可选地，
S270，源端设备根据第一配置信息向接收端设备发送业务数据。
应理解，在本申请各实施例中，第一配置信息可以包括用于指示链路属于第一链路组的标记，后边的实施例中不再赘述。
例如，第一配置信息可以包括上文中描述的“selected”标记(用于指示链路属于第一链路组)和“standby”标记。
再如，第一配置信息可以包括上文中描述的“selected1”标记(用于指示链路属于第一链路组)和“selected2”标记(用于指示链路属于第二链路组)。具体地，第一设备将用于指示N个链路中的第一链路属于第一链路组的第一配置信息，通过第一链路发送给第二设备。换而言之，可以通过链路组标识(例如“Subgroup ID”，这里“Subgroup”是为了与现有的“Group”进行区分)的方式指示链路组配置的信息。为M个链路添加“Subgroup ID”，对标记有同一“Subgroup ID”的各链路可以进行差分延迟补偿操作，可以跨链路传输业务；如 果仅有一个链路标记为某一“Subgroup ID”，则只能在该链路上独立传输业务。
又如，第一配置信息可以包括用于指示M个链路分别所属的链路组的信息。第一设备将用于指示M个链路分别所属的链路组的信息，通过每个链路分别发送给第二设备。
应理解，在本申请各实施例中，S140第一设备向第二设备发送第一配置信息，可以包括：第一设备将第一配置信息承载在数据码块中发送给第二设备；或第一设备将第一配置信息承载在开销码块的管理通道中以链路层发现协议(Link Layer Discovery Protocol，LLDP)格式、高级数据链路控制(High-Level Data Link Control，HDLC)格式或点对点通信协议(Point to Point Protocol，PPP)格式的报文发送给第二设备；或第一设备将第一配置信息承载在开销码块的保留字段中发送给第二设备。后边的实施例中不再赘述。
在一个具体的例子中，第一配置信息(例如，在每个链路上传输各自的所属的链路组的标记)通过在OH码块的管理通道发送LLDP格式的报文的形式来传输。具体地，第一配置信息可以承载在LLDP格式的类型长度值(Type-Length-Value，TLV)单元中，通过FlexE OH码块中的shim-to-shim管理通道(management channel)来传输。
一种可选的用于承载第一配置信息的LLDP格式的TLV单元各字段的定义如表2所示。TLV单元中，
byte1～2的前7bit为TLV类型(TLV type)，根据LLDP规定，各组织自定义的TLV单元的type值为127。
byte1～2的后9bit为TLV长度(TLV length)，指示该TLV单元的总长度有多少字节。
byte3～5为LLDP规定的各组织的组织唯一标识码(Organizationally Unique Identifier，OUI)，其中，OIF所对应的OUI为00-0F-40。
byte6为各组织自定义的TLV单元的子类型(subtype)，可以为0x？？(十六进制)，例如可以为如0x01(十六进制)或者00000001(二进制)，等等。
byte7为该链路所属的链路组的标记。
0x00可以表示该链路差分延迟超出接收端设备的差分延迟补偿的能力，也即“standby”
0x01～0xFF可以表示该链路差分延迟在接收端设备的差分延迟补偿的能力范围内，也即“selected”，具体对应的值可以指示该链路所属的链路组的编号。
应理解，表2给出的用于承载第一配置信息的LLDP格式的TLV单元各字段的定义仅是实例性的，可以根据需要进行相应的变形，本申请各实施例对此不作限定。
表2 用于承载第一配置信息的LLDP格式的TLV单元
Figure PCTCN2018082469-appb-000003
源端设备在OH码块的管理通道上接收到此TLV单元后即可按照“链路所属的链路组的标记”的指示完成链路组的配置并发送业务数据。
在另一个具体的例子中，第一配置信息(例如，在每个链路上传输各自的所属的链路组的标记)通过OH码块的保留字段来传输。所述第一配置信息中的第一部分比特用于指 示所述第一链路与其他链路组成所述第一链路组，所述第一配置信息中的第二部分比特为所述第一链路组的标记。图10是本实施例的保留字段的格式的示意图。具体地，在OH码块的保留字段中可划分出11bits用于承载第一配置信息。前3个bit可以承载“selected”或者“standby”标记，在“selected”状态下后8个bit可用来承载“链路所属的链路组的标记”。应理解，第一部分比特包括3bit，第二部分比特包括8bit仅是示例，第一部分比特和第二部分比特可以包括更多或更少的bit，本申请实施例对此不作限定。
应理解，OH码块中包括多个bit的保留字段，图10所示出的用于承载第一配置信息的保留字段的位置仅为示例性的，而不是对本申请各实施例的限定。
对于FlexO，各链路分别对应的配置信息可以放置于OTUCn帧的OH码块的管理通道中进行发送，或者可以放在通用通信信道(General Communication Channel，GCC)0字节以通用成帧规程(Generic Framing Procedure，GFP)格式、HDLC格式、PPP格式或者保留(Reserved，RES)字段以自定义的帧格式进行发送，或者也可以放置于OTUCn帧的净荷中，例如放置在光净荷单元(Optical Payload Unit-CnOPUCn)的净荷中以GFP格式或者其他自定义的帧格式发送。
本实施例，接收端设备具有延迟接收补偿的能力，由接收端设备作为决策设备确定链路组的配置，执行简单方便，进行链路组配置时信令开销小。
实施例2：
在本实施例中，第一设备即决策设备为源端设备，第二设备为接收端设备。接收端设备具有延迟接收补偿的能力。
在本实施例中，S110第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，可以包括：第一设备接收接收端设备发送的第一状态信息。S120第一设备获取接收端设备的第一能力信息，可以包括：第一设备接收接收端设备发送的第一能力信息。
图11是本实施例的配置链路组以及进行补偿的流程300的示意图。该流程300可以包括以下步骤。
S305，源端设备和接收端设备之间启动链路。
S310，源端设备通过M个链路分别独立地向接收端设备发送数据帧。相应地，接收端设备接收源端设备发送的数据帧。应理解，这些数据帧中可以包括对齐标记。
S315，接收端设备测量M个链路的差分延迟的状态。
S320，接收端设备向源端设备发送第一状态信息，该第一状态信息用于指示M个链路的差分延迟的状态。相应地，源端设备接收接收端设备发送的第一状态信息。
S325，接收端设备向源端设备发送第一能力信息，该第一能力信息用于指示接收端设备对M个链路进行差分延迟补偿的第一能力。相应地，源端设备接收接收端设备发送的第一能力信息。
S330，源端设备根据第一状态信息以及第一能力信息，确定如何配置链路组。具体地配置中包括将M个链路中的N个链路划分到第一链路组。
S335，源端设备向接收端设备发送第一配置信息，第一配置信息包括用于指示第一链路组的信息。相应地，接收端设备接收源端设备发送的第一配置信息。
S340，接收端设备对M个链路进行差分延迟补偿。具体地，接收端设备根据第一配置信息进行差分延迟补偿，即设置差分延迟的缓存大小。换而言之，接收端设备根据自身 确定的链路组配置对第一链路组中的链路进行差分延迟补偿。
S345，接收端设备向源端设备返回确认信息，用于指示已经收到上述第一配置信息并进行了相应的链路组配置。相应地，源端设备接收接收端设备返回的确认信息。应理解，S345为可选的步骤。进一步地，接收端设备还可以将更新后的各链路的差分延迟的状态发送到源端设备。
S350，源端设备根据第一配置信息向接收端设备发送业务数据。
其中，第一配置信息的发送方式可以与实施例1中第一配置信息的发送方式类似，此处不再赘述。
可选地，S335中，第一配置信息中还可以包括针对各链路，对接收端设备进行差分延迟补偿时的缓存需求，接收端设备根据该缓存需求直接设置各链路的缓存量。
可选地，S330中，源端设备还可以结合将要发送给接收端设备的业务数据的相关信息，例如业务数量和/或带宽等综合因素确定链路组的配置方案。
应理解，S345中接收端设备返回的确认信息可以通过LLDP格式的报文的形式来传输；也可通过OH码块中的保留字段来传输。例如，在实施例1中承载第一配置信息的OH保留字段之后还有2个bit的保留字段可以用来传输该确认信息。例如，“00”表示接收端设备接收到第一配置信息，并且成功设置各链路的缓存量；“01”表示未成功设置各链路的缓存量。源端设备接收到确认信息“00”后可以发送业务数据，如接收到“01”的消息则回到S330重新确定链路组的配置方案。
在S325中，第一能力信息可以通过数据码块发送，也可以通过开销码块的管理通道中以LLDP格式、HDLC格式或PPP格式的报文发送，还可以通过开销码块的保留字段发送，本实施例对此不作限定。
在一个具体的例子中，第一能力信息可以承载在开销码块的管理通道的LLDP格式的TLV单元中。该用于承载第一能力信息的LLDP格式的TLV单元的各字段的定义如表3所示。
其中，表3的byte1～6字段的定义与表2的byte1～6字段的定义相同。
byte7定义为对该链路的差分延迟补偿的能力。其中，第一个bit可以表示该链路的接收方向的差分延迟补偿的能力，第一个bit值为“0”表示接收方向的缓存大小为默认值，如缓存大小为与FlexE1.0中定义的300ns差分延迟补偿能力相对应的469码块；第一个bit值为“1”表示接收方向的缓存大小为该链路自定义的值，具体值在byte8～10中描述。byte7中其他bit可以为保留字段。
byte8～10定义为该链路接收方向的缓存大小。如果byte7中的第一个bit为“1”(接收方向的缓存大小为自定义的值)，则byte8～10的值x表示接收方向的缓存大小为x码块，x的取值范围为[1～0xFFFFFE]。如果byte7中的第一个bit为“0”，则接收方向的缓存大小为默认值，byte8～10的值可以设为“0xFFFFFF”。
应理解，该TLV单元中byte8～10所定义的接收方向的缓存大小(例如可以为local deskew buffer size)为可选参数。当该链路接收方向的缓存大小为默认大小时，不需传递接收方向的缓存大小信息，其参数可设为“0xFFFFFF”。
这里举例描述的接收方向的缓存大小以码块(block)为单位。同样地，接收方向的缓存大小可以ns或10ns或者bytes等不同描述方式或不同大小的缓存基本单位来表示，本 申请各实施例不作限定。
在FlexE Aware Transport的传输模式下，即跨传送网传输场景下，接收端设备使用上述TLV单元向源端设备通告第一能力，通过OH码块的片对片管理通道(shim-to-shim management channel)传输。其他场景下，上述TLV单元可以通过分段管理通道(section management channel)传输也可以通过shim-to-shim management channel传输。
表3 用于承载第一能力信息的LLDP格式的TLV单元
Figure PCTCN2018082469-appb-000004
在一个具体的例子中，第一状态信息可以承载在开销码块的管理通道的LLDP格式的TLV单元中。该用于承载第一状态信息的LLDP格式的TLV单元的各字段的定义如表4所示。
其中，表4的byte1～6字段的定义与表2的byte1～6字段的定义相同。
byte7定义为该链路的差分延迟的结果(例如，可以为“FlexE group PHY deskew status”)。其中，第一个bit表示该链路的接收方向的当前差分延迟的结果，“0”表示接收端设备对M个链路的各链路按第一配置信息进行差分延迟补偿，且差分延迟补偿成功；“1”表示接收端设备未进行差分延迟补偿或差分延迟补偿失败。byte7中其他bit可以为保留字段。
byte8～10定义为该链路的差分延迟的延迟量。差分延迟的延迟量(例如，可以为“FlexE group PHY skew”)参数表示接收端设备收到各链路上的数据帧时，本链路相对于M个链路中传输最快的链路的延迟量。此时，例如某链路的“FlexE group PHY skew”为0，则表示该链路即为M个链路中传输最快的链路。其值x表示差分延迟的延迟量为x码块数据所对应的传输时间。
在FlexE Aware Transport的传输模式下，即跨传送网传输场景下，接收端设备使用上述TLV单元向源端设备通告自身的差分延迟的状态，通过OH码块的片对片管理通道(shim-to-shim management channel)传输。其他场景下，上述TLV单元可以通过分段管理通道(section management channel)传输也可以通过shim-to-shim management channel传输。
表4 用于承载第一能力信息的LLDP格式的TLV单元
Figure PCTCN2018082469-appb-000005
源端设备通过上述两个TLV单元获取接收端设备的第一能力信息及各链路口的第一状态信息之后确定链路组配置，并通过与实施例1类似的方式将第一配置信息发送到接收 端设备。接收端设备根据第一配置信息对各链路进行差分延迟补偿，此处不再进行赘述。
本实施例中，接收端设备具有延迟接收补偿的能力，由源端设备作为决策设备，可以结合业务数据的相关信息，例如业务数量和/或带宽等综合因素确定链路组的配置。
实施例3：
在本实施例中，第一设备即决策设备为管理设备，第二设备包括接收端设备和/或源端设备。接收端设备具有延迟接收补偿的能力。
在本实施例中，S110第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，可以包括：第一设备接收接收端设备发送的第一状态信息。S120第一设备获取接收端设备的第一能力信息，可以包括：第一设备接收接收端设备发送的第一能力信息。
由管理设备决策链路组配置的流程可以包括以下几个步骤。
A-1，源端设备和接收端设备之间启动链路。
A-2，源端设备通过M个链路分别独立地向接收端设备发送数据帧。相应地，接收端设备接收源端设备发送的数据帧。应理解，这些数据帧中可以包括对齐标记。
A-3，接收端设备测量M个链路的差分延迟的状态。
A-4，接收端设备向管理设备发送第一状态信息，该第一状态信息用于指示M个链路的差分延迟的状态。相应地，管理设备接收接收端设备发送的第一状态信息。
A-5，接收端设备向管理设备发送第一能力信息，该第一能力信息用于指示接收端设备对M个链路进行差分延迟补偿的第一能力。相应地，管理设备接收接收端设备发送的第一能力信息。
A-6，管理设备根据第一状态信息和第一能力信息，确定如何配置链路组。具体地配置中包括将M个链路中的N个链路划分到第一链路组。
A-7，管理设备向源端设备和接收端设备发送第一配置信息，第一配置信息包括用于指示第一链路组的信息。相应地，源端设备和接收端设备接收管理设备发送的第一配置信息。
A-8，源端设备和/或接收端设备可以向管理设备返回确认信息，用于指示已经收到上述第一配置信息并进行了相应的配置。相应地，管理设备接收源端设备和/或接收端设备返回的确认信息。应理解，A-8为可选的步骤。
A-9，管理设备收到确认信息之后向源端设备下达链路组配置已完成的指示。应理解，A-9为可选的步骤。
A-10，源端设备根据第一配置信息向接收端设备发送业务数据。
A-11，接收端设备根据第一配置信息，对业务数据对应的第一链路组中的链路进行差分延迟补偿。
A-12，管理设备向接收端设备发送的第一配置信息中还可以包括针对各链路，对接收端设备进行差分延迟补偿时的缓存需求，接收端设备根据该缓存需求直接设置各链路的缓存量。应理解，A-12为可选的步骤。
应理解，源端设备和接收端设备与管理设备之间的，关于第一状态信息、第一能力信息和第一配置信息的通信可以在各设备与管理设备的OH码块的管理通道中传输。可选地，在FlexO中，上述信息可以在OH码块的GCC0字节以GFP格式、HDLC格式、PPP格式或RES字段以自定义的帧格式进行传输。在FlexE中，上述信息可以在OH码块的管理通 道以网络协议(Internet Protocol，IP)报文的形式传输，本实施例对具体的传输方式不作限定。
本实施例中，由管理设备作为决策设备，一来可以接收源端设备和接收端设备的相关信息，能够考虑例如业务数量和/或带宽等综合因素确定链路组的配置；二来能够避免由源端设备或接收端设备做决策时可能引发的计算量，可以减轻源端设备和接收端设备的负担。
应理解，在实际场景中，链路从源端设备到接收端设备的路径上可能还经过一些中间设备，如图5所示的FlexE跨传送网传输的应用场景，即基于FlexE aware transport模式的传输场景。除接收端设备能进行差分延迟补偿之外，中间设备的各发送端口也可以支持延迟发送数据的能力，或者称为延迟发送补偿的能力，因而需要接收端设备和中间设备通过协商实现协同补偿。
在本申请的一些实施例中，在M个链路上，接收端设备的K个上游设备可以具有延迟发送补偿的能力，其中，K为正整数。K个上游设备可以包括源端设备和/或至少一个中间设备，中间设备在M个链路上位于源端设备与接收端设备之间。
在接收端设备的K个上游设备具有延迟发送补偿的能力的情况下，方法100还可以包括：第一设备获取K个上游设备的每个上游设备的第二能力信息和第二状态信息，第二能力信息用于指示每个上游设备对M个链路中的至少一个链路进行延迟发送补偿的第二能力，第二状态信息用于指示每个上游设备对M个链路中的至少一个链路进行延迟发送补偿的当前状态；S130第一设备根据第一状态信息和第一能力信息，将M个链路中的N个链路划分到第一链路组，可以包括：第一设备根据第一状态信息、第一能力信息、第二状态信息和第二能力信息，将M个链路中的N个链路划分到第一链路组；方法100还可以包括：第一设备根据第一状态信息、第一能力信息、第二状态信息和第二能力信息，确定每个上游设备对相应的链路应进行的延迟发送补偿的配置。
应说明的是，并不是所有的M个链路均会经过所有的上游设备。对K个上游设备中的任一个上游设备而言，可能只有M个链路中的部分链路(至少一个链路)经过。
下面结合几个实施例说明当接收端设备的K个上游设备具有延迟发送补偿的能力时，本申请实施例的配置链路组的方法。
实施例4、实施例5和实施例6中，第一设备即决策设备为接收端设备，第二设备为源端设备。接收端设备具有延迟接收补偿的能力。K个上游设备可以包括源端设备和/或至少一个中间设备，具有延迟发送补偿的能力。
S110第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，可以包括：第一设备测量M个链路的差分延迟，获得第一状态信息；第一设备获取K个上游设备的每个上游设备的第二能力信息和第二状态信息，可以包括：第一设备接收每个上游设备发送的第二能力信息和第二状态信息；方法100还可以包括：第一设备向K个上游设备中的至少一个上游设备发送第二配置信息，第二配置信息用于指示至少一个上游设备对相应的链路应进行延迟发送补偿的配置。
在至少一个上游设备完成延迟发送补偿的配置后，方法100还可以包括：第一设备基于第一链路组，与第二设备传输业务数据；第一设备根据第一配置信息，对第一链路组中已经过至少一个上游设备根据第二配置信息进行延迟发送补偿的链路进行差分延迟补偿。
应理解，在接收端设备处M个链路无法对齐时，M个链路不能组成一个链路组，或者说FlexE Group或FlexO Group崩溃无法工作，本申请各实施例的源端设备、接收端设备，还可以包括中间设备等均可能有差分延迟补偿或延迟发送补偿的能力，本申请各实施例各设备通过能力协商实现链路组的补偿。使得当源端设备、接收端设备之间的FlexE Group或FlexO Group中各设备的补偿能力无法补偿各链路的差分延迟时，通过配置链路组，使得源端设备只在延迟对齐的链路上承载跨链路传输业务数据；或者通过各设备协同补偿，使得最终M个链路在接收端设备处可以对齐，能够保证FlexE Group或FlexO Group的工作，可以提高链路的利用率。
实施例4：
在本实施例中，第一设备即决策设备为接收端设备，第二设备为源端设备。接收端设备具有延迟接收补偿的能力。接收端设备和源端设备之间有具有延迟发送补偿的能力的中间设备，即K个上游设备为至少一个中间设备。
接收端设备和中间设备协同补偿的流程可以包括以下步骤。
B-1，源端设备和接收端设备之间启动链路。
B-2，源端设备通过M个链路分别独立地向接收端设备发送数据帧。相应地，接收端设备接收源端设备发送的数据帧。应理解，这些数据帧中可以包括对齐标记。
B-3，接收端设备测量M个链路的差分延迟的状态，获得第一状态信息。
B-4，中间设备向接收端设备发送第二能力信息，第二能力信息用于指示每个中间设备对M个链路中的至少一个链路进行延迟发送补偿的第二能力。相应地，接收端设备接收中间设备发送的第二能力信息。应理解，第二能力信息可以携带在B-2的数据帧中，也可以通过其他方式发送，本实施例对此不作限定。
B-5，中间设备向接收端设备发送第二状态信息，第二状态信息用于指示每个中间设备对M个链路中的至少一个链路进行延迟发送补偿的当前状态。相应地，接收端设备接收中间设备发送的第二状态信息。应理解，第二状态信息可以携带在B-2的数据帧中，也可以通过其他方式发送，本实施例对此不作限定。
B-6，接收端设备根据第一状态信息和可以表示接收端设备对M个链路进行差分延迟补偿的能力的第一能力信息、第二能力信息和第二状态信息，确定如何配置链路组以及如何配置延迟发送补偿。具体的链路组配置中包括将M个链路中的N个链路划分到第一链路组。
B-7，接收端设备向中间设备发送第一配置信息，第一配置信息包括指示第一链路组的信息。相应地，中间设备接收接收端设备发送的第一配置信息。应理解，B-7为可选的步骤，执行B-7可以不用于协同补偿流程，而是用于其他过程。
B-8，接收端设备向中间设备发送第二配置信息，第二配置信息包括用于指示上游设备对相应的链路应进行的延迟发送补偿的配置。相应地，中间设备接收接收端设备发送的第二配置信息。
B-9，中间设备根据第二配置信息调整链路发送延迟。
B-10，中间设备向接收端设备发送更新后的延迟发送补偿的当前状态的信息。一来可以为下次协同补偿做准备，二来通知接收端设备已经完成延迟发送补偿的配置。
B-11，接收端设备接收到中间设备发送的信息后，向源端设备发送第一配置信息，第 一配置信息包括指示第一链路组的信息。相应地，源端设备接收接收端设备发送的第一配置信息。同时，可选地，第一配置信息中还可以包括用于指示已经完成差分延迟补偿的相关配置的信息。
B-12，接收端设备对M个链路进行差分延迟补偿。具体地，接收端设备根据第一配置信息进行差分延迟补偿，即设置差分延迟的缓存大小。换而言之，接收端设备根据自身确定的链路组配置对第一链路组中的链路进行差分延迟补偿。
B-13，源端设备根据第一配置信息向接收端设备发送业务数据。
应理解，源端设备、中间设备和接收端设备之间的，关于第一状态信息、第一能力信息、第一配置信息、第二状态信息、第二能力信息和第二配置信息以及其他的相关信息的通信可以通过数据码块传输，也可以通过开销码块的管理通道中以LLDP格式、HDLC格式或PPP格式的报文传输，还可以通过开销码块的保留字段传输，本实施例对此不作限定。
其中，第一配置信息的发送方式与实施例1中第一配置信息的发送方式类似，此处不再赘述。
本实施例以及本申请的其他实施例涉及上报或传输自身的能力信息，例如，第一能力信息和第二能力信息，可以承载在开销码块的管理通道的LLDP格式的TLV单元中。该用于承载能力信息的LLDP格式的TLV单元的各字段的定义如表5所示。
其中，表5的byte1～6字段的定义与表2的byte1～6字段的定义相同。
byte7定义为对该链路的补偿的能力。其中，byte7的第一个bit可以表示该链路的接收方向的差分延迟补偿的能力，第一个bit值为“0”表示接收方向的缓存大小为默认值，如缓存大小为与FlexE1.0中定义的300ns差分延迟补偿能力相对应的469码块；第一个bit值为“1”表示接收方向的缓存大小为该链路自定义的值，具体值在byte8～10中描述。byte7的第二个bit可以表示该链路的发送方向的延迟发送补偿的能力，第二个bit值为“0”表示不支持延迟发送补偿的能力的默认模式；第二个bit值为“1”表示支持延迟发送补偿的能力，延迟发送缓存大小的具体值在byte11～13中描述。byte7中其他bit可以为保留字段。
byte8～10定义为该链路接收方向的缓存大小。如果byte7中的第一个bit为“1”(接收方向的缓存大小为自定义的值)，则byte8～10的值x表示接收方向的缓存大小为x码块，x的取值范围为[1～0xFFFFFE]。如果byte7中的第一个bit为“0”，则接收方向的缓存大小为默认值，byte8～10的值可以设为“0xFFFFFF”。
byte11～13定义为该链路发送方向的缓存大小。如果byte7中的第一个bit为“1”(发送方向支持延迟发送补偿的能力)，则byte8～10的值x表示发送方向的缓存大小为x码块，x的取值范围为[1～0xFFFFFE]。如果byte7中的第一个bit为“0”，则标识发送方向不支持延迟发送补偿的能力，byte8～10的值可以设为“0xFFFFFF”。
这里举例描述的缓存大小以码块(block)为单位。同样地，缓存大小可以ns或10ns或者bytes等不同描述方式或不同大小的缓存基本单位来表示，本申请各实施例不作限定。
在FlexE Aware Transport的传输模式下，即跨传送网传输场景下，各设备之间使用上述TLV单元通告能力，通过OH码块的片对片管理通道(shim-to-shim management channel)传输。其他场景下，上述TLV单元可以通过分段管理通道(section management channel)传输也可以通过shim-to-shim management channel传输。
表5 用于承载能力信息的LLDP格式的TLV单元
Figure PCTCN2018082469-appb-000006
应注意的是，本申请各实施例均可使用表5所示的TLV单元来承载能力信息。由于通常而言链路是双向的，因此在一个传输方向上，某设备为接收端设备，在另一个传输方向上，该设备则为源端设备或上游设备。本实施例将用于承载能力信息的TLV单元设计为如表5的形式，使得该设备不论是作为接收端设备，或是作为源端设备或上游设备，上报能力信息时均可使用该TLV单元。
换而言之，表5所示的开销码块的管理通道的链路层发现协议LLDP格式的TLV单元可以承载用于指示接收端设备对M个链路进行差分延迟补偿的第一能力的第一能力信息；还能够承载用于指示在接收端设备向源端设备发送业务数据时，接收端设备对M个链路进行延迟发送补偿的能力的信息。
本实施例以及本申请的其他实施例涉及上报或传输自身的状态信息，例如，第一状态信息和第二状态信息，可以承载在开销码块的管理通道的LLDP格式的TLV单元中。该用于承载状态信息的LLDP格式的TLV单元的各字段的定义如表6所示。
其中，表6的byte1～6字段的定义与表2的byte1～6字段的定义相同。
byte7定义为该链路的差分延迟补偿的当前状态和延迟发送补偿的当前状态，即链路的补偿状态。其中，第一个bit表示该链路的接收方向的差分延迟补偿的当前状态。第一个bit值为“0”表示接收方向上该链路差分延迟补偿成功。例如，在OH码块的保留字段中该链路标记为“selected”，“subgroup ID”为“3”，则表示该链路相对于subgroup 3中的其他各链路差分延迟补偿成功。第一个bit值为“1”表示接收方向上该链路差分延迟补偿失败。例如，在OH码块的保留字段中该链路标记为“selected”，“subgroup ID”为“3”，则表示该链路相对于subgroup3中的其他各链路差分延迟补偿失败，该链路超出设备的差分延迟补偿的能力，差分延迟量在byte8～10中描述。byte7中第二个bit表示该链路的发送方向的延迟发送补偿的当前状态。第二个bit值为“0”表示发送方向上该链路没有延迟发送的能力；第二个bit值为“1”，表示该发送方向上该链路的延迟发送的能力正在使用。延迟发送量在byte11～13中描述。byte7中其他bit为保留字段。
byte8～10定义为在该链路的接收方向的差分延迟补偿失败时，该链路超出接收方向的差分延迟补偿的能力的差分延迟量，其值x表示超出的差分延迟量为x码块缓存大小所对应的传输时间，当接收方向的差分延迟补偿成功时，x为0。
byte11～13定义为该链路的延迟发送量，其值x表示当前使用的延迟发送的缓存大小为码块，byte7中第二个bit为“0”时(发送方向上该链路没有延迟发送的能力)，x值为“0xFFFFFF”。
这里举例描述的缓存大小以码块(block)为单位。同样地，缓存大小可以ns或10ns或者bytes等不同描述方式或不同大小的缓存基本单位来表示，本申请各实施例不作限定。
在FlexE Aware Transport的传输模式下，即跨传送网传输场景下，各设备之间使用上述TLV单元通告状态，通过OH码块的片对片管理通道(shim-to-shim management channel) 传输。其他场景下，上述TLV单元可以通过分段管理通道(section management channel)传输也可以通过shim-to-shim management channel传输。
表6 用于承载状态信息的LLDP格式的TLV单元
Figure PCTCN2018082469-appb-000007
应注意的是，本申请各实施例均可使用表6所示的TLV单元来承载状态信息。由于通常而言链路是双向的，因此在一个传输方向上，某设备为接收端设备，在另一个传输方向上，该设备则为源端设备或上游设备。本实施例将用于承载状态信息的TLV单元设计为如表6的形式，使得该设备不论是作为接收端设备，或是作为源端设备或上游设备，上报状态信息时均可使用该TLV单元。
换而言之，表6所示的开销码块的管理通道的链路层发现协议LLDP格式的TLV单元可以承载用于指示M个链路中任意两个链路之间的差分延迟的状态的第一状态信息；还能够承载用于指示在接收端设备向源端设备发送业务数据时，接收端设备对M个链路进行延迟发送补偿的当前状态的信息。
此外，决策设备在确定第二配置信息后，还可以采用表6所示的TLV单元来承载第二配置信息。即，TLV单元还能够承载用于指示上游设备对相应的链路应进行的延迟发送补偿的配置的信息。
第一配置信息的发送方式可以与实施例1中第一配置信息的发送方式类似，此处不再赘述。此外，本实施例以及本申请的其他实施例涉及上报或传输自身的状态信息和下发配置信息，例如，第一状态信息、第二状态信息、第一配置信息和第二配置信息，可以将其一起承载在开销码块的管理通道的LLDP格式的TLV单元中。该用于承载状态信息和配置信息的LLDP格式的TLV单元的各字段的定义如表7所示。
其中，表7的byte1～6字段的定义与表2的byte1～6字段的定义相同。
byte7～8定义为该链路的补偿的状态和链路组配置。其中，第一个bit表示该链路的接收方向的差分延迟补偿的当前状态。第一个bit值为“0”表示接收方向上该链路差分延迟补偿成功。例如，在byte7～8的后续字段中标记该链路为“selected”，“subgroup ID”为“3”，则表示该链路相对于subgroup 3中的其他各链路差分延迟补偿成功。第一个bit值为“1”表示接收方向上该链路差分延迟补偿失败。例如，在byte7～8的后续字段中标记该链路为“selected”，“subgroup ID”为“3”，则表示该链路相对于subgroup3中的其他各链路差分延迟补偿失败，该链路超出设备的差分延迟补偿的能力，差分延迟量在byte9～11中描述。byte7中第二个bit表示该链路的发送方向的延迟发送补偿的当前状态。第二个bit值为“0”表示发送方向上该链路没有延迟发送的能力或延迟发送的能力没有使用；第二个bit值为“1”，表示该发送方向上该链路的延迟发送的能力正在使用。延迟发送量在byte12～14中描述。byte7中其他bit为保留字段。
byte7～8中的第三至第十三bit用于表示该链路所属的链路组，即为该链路的标记信息。其中第2～4bit用于表示“selected”或者“standby”，如“001”表示“selected”，“010”表示 “standby”。在“selected”状态下后8个bit可用来表示“subgroup ID”。byte7～8中其他bit为保留字段。
表7的byte9～11所描述的差分延迟量与表6的byte8～10所描述的差分延迟量相同；表7的byte12～14所描述的延迟发送量与表6的byte11～13所描述的延迟发送量相同，此处不再赘述。
表7 用于承载状态信息的LLDP格式的TLV单元
Figure PCTCN2018082469-appb-000008
实施例5：
在本实施例中，第一设备即决策设备为接收端设备，第二设备为源端设备。接收端设备具有延迟接收补偿的能力。源端设备具有延迟发送补偿的能力，即K个上游设备为源端设备。
由接收端设备决策链路组配置，并由接收端设备和源端设备协同补偿的流程可以包括以下步骤。
C-1，源端设备和接收端设备之间启动链路。
C-2，源端设备通过M个链路分别独立地向接收端设备发送数据帧。相应地，接收端设备接收源端设备发送的数据帧。应理解，这些数据帧中可以包括对齐标记。
C-3，源端设备向接收端设备发送第二能力信息，第二能力信息用于指示源端设备对M个链路中的至少一个链路进行延迟发送补偿的第二能力。相应地，接收端设备接收源端设备发送的第二能力信息。应理解，第二能力信息可以携带在C-2的数据帧中，也可以通过其他方式发送，本实施例对此不作限定。
C-4，源端设备向接收端设备发送第二状态信息，第二状态信息用于指示源端设备对M个链路中的至少一个链路进行延迟发送补偿的当前状态。相应地，接收端设备接收源端设备发送的第二状态信息。应理解，第二状态信息可以携带在C-2的数据帧中，也可以通过其他方式发送，本实施例对此不作限定。
C-5，接收端设备测量M个链路的差分延迟的状态，获得第一状态信息。
C-6，接收端设备根据第一状态信息和可以表示接收端设备对M个链路进行差分延迟补偿的能力的第一能力信息、第二能力信息和第二状态信息，确定如何配置链路组以及如何配置延迟发送补偿。具体的链路组配置中包括将M个链路中的N个链路划分到第一链路组。
C-7，接收端设备向源端设备发送第一配置信息，第一配置信息包括指示第一链路组的信息。相应地，源端设备接收接收端设备发送的第一配置信息。
C-8，接收端设备向源端设备发送第二配置信息，第二配置信息包括用于指示源端设备对相应的链路应进行的延迟发送补偿的配置。相应地，源端设备接收接收端设备发送的 第二配置信息。
C-9，源端设备根据第二配置信息调整链路发送延迟。
C-10，源端设备向接收端设备发送更新后的延迟发送补偿的状态的信息。一来可以为下次协同补偿做准备，二来通知接收端设备已经完成延迟发送补偿的配置。
C-11，接收端设备接收到源端设备发送的信息后，重新分析各链路的差分延迟，对M个链路进行差分延迟补偿。具体地，接收端设备根据第一配置信息进行差分延迟补偿，即设置差分延迟的缓存大小。换而言之，接收端设备根据自身确定的链路组配置对第一链路组中的链路进行差分延迟补偿。接收端设备反馈各链路的差分延迟的状态及链路组的配置到源端设备。
C-12，源端设备根据第一配置信息向接收端设备发送业务数据。
应理解，源端设备和接收端设备之间的，关于第一状态信息、第一能力信息、第一配置信息、第二状态信息、第二能力信息和第二配置信息中的至少一种信息的传输格式和传输通道与实施例4类似，此处不再进行赘述。
实施例6：
在本实施例中，第一设备即决策设备为接收端设备，第二设备为源端设备。接收端设备具有延迟接收补偿的能力。源端设备和至少一个中间设备具有延迟发送补偿的能力，即K个上游设备包括源端设备和至少一个中间设备。
接收端设备、源端设备和至少一个中间设备协同补偿的流程可以包括以下步骤。
D-1，源端设备和接收端设备之间启动链路。
D-2，源端设备通过M个链路分别独立地向接收端设备发送数据帧。相应地，接收端设备接收源端设备发送的数据帧。应理解，这些数据帧中可以包括对齐标记。
D-3，接收端设备测量M个链路的差分延迟的状态，获得第一状态信息。
D-4，源端设备和至少一个中间设备向接收端设备发送第二能力信息，第二能力信息用于指示每个上游设备对M个链路中的至少一个链路进行延迟发送补偿的第二能力。相应地，接收端设备接收源端设备发送的第二能力信息。应理解，第二能力信息可以携带在D-2的数据帧中，也可以通过其他方式发送，本实施例对此不作限定。
D-5，源端设备和至少一个中间设备向接收端设备发送第二状态信息，第二状态信息用于指示每个上游设备对M个链路中的至少一个链路进行延迟发送补偿的当前状态。相应地，接收端设备接收源端设备发送的第二状态信息。应理解，第二状态信息可以携带在D-2的数据帧中，也可以通过其他方式发送，本实施例对此不作限定。
D-6，接收端设备根据第一状态信息和可以表示接收端设备对M个链路进行差分延迟补偿的能力的第一能力信息、第二能力信息和第二状态信息，确定如何配置链路组以及如何配置延迟发送补偿。具体的链路组配置中包括将M个链路中的N个链路划分到第一链路组。
D-7，接收端设备向源端设备发送第一配置信息，第一配置信息包括指示第一链路组的信息。相应地，源端设备接收接收端设备发送的第一配置信息。
D-8，接收端设备向中间设备发送第一配置信息，第一配置信息包括指示第一链路组的信息。相应地，中间设备接收接收端设备发送的第一配置信息。应理解，D-10为可选的步骤，执行D-8可以不用于协同补偿流程，而是用于其他过程。
D-9，接收端设备向源端设备和至少一个中间设备发送各自的第二配置信息，第二配置信息包括用于指示源端设备和至少一个中间设备分别对相应的链路应进行的延迟发送补偿的配置。相应地，源端设备和至少一个中间设备分别接收接收端设备发送的第二配置信息。
D-10，源端设备和至少一个中间设备根据第二配置信息调整链路发送延迟，即设置延迟发送的缓存大小。
D-11，源端设备和至少一个中间设备向接收端设备发送更新后的延迟发送补偿的状态的信息。一来可以为下次协同补偿做准备，二来通知接收端设备已经完成延迟发送补偿的配置。
D-12，接收端设备重新分析各链路的差分延迟，对M个链路进行差分延迟补偿。具体地，接收端设备根据第一配置信息进行差分延迟补偿，即设置差分延迟的缓存大小。换而言之，接收端设备根据自身确定的链路组配置对第一链路组中的链路进行差分延迟补偿。接收端设备反馈各各链路的差分延迟的状态及链路组的配置到源端设备。
D-13，源端设备根据第一配置信息向接收端设备发送业务数据。
应理解，源端设备和接收端设备之间的，关于第一状态信息、第一能力信息、第一配置信息、第二状态信息、第二能力信息和第二配置信息中的至少一种信息的传输格式和传输通道与实施例4类似，此处不再进行赘述。
实施例7、实施例8和实施例9中，第一设备即决策设备为源端设备，第二设备为接收端设备。接收端设备具有延迟接收补偿的能力。K个上游设备可以包括源端设备和/或至少一个中间设备，具有延迟发送补偿的能力。
S110第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，可以包括：第一设备接收接收端设备发送的第一状态信息；S120第一设备获取接收端设备的第一能力信息，可以包括：第一设备接收接收端设备发送的第一能力信息。
在至少一个上游设备完成延迟发送补偿的配置后，方法100还可以包括：第一设备基于第一链路组，与第二设备传输业务数据；第一设备根据第一配置信息，对第一链路组中已经过至少一个上游设备根据第二配置信息进行延迟发送补偿的链路进行差分延迟补偿。
实施例7：
在本实施例中，第一设备即决策设备为源端设备，第二设备为接收端设备。接收端设备具有延迟接收补偿的能力。接收端设备和源端设备之间有具有延迟发送补偿的能力的中间设备，即K个上游设备为至少一个中间设备。
具体地，第一设备获取K个上游设备的每个上游设备的第二能力信息和第二状态信息，可以包括：第一设备接收至少一个中间设备中的每个中间设备发送的第二能力信息和第二状态信息；方法100还可以包括：第一设备向至少一个中间设备中的至少部分中间设备发送第二配置信息，第二配置信息用于指示至少部分中间设备对相应的链路应进行的延迟发送补偿的配置。
应理解，第一设备向至少一个中间设备中的至少部分中间设备发送第二配置信息，可以是第一设备直接向中间设备发送第二配置信息，也可以是第一设备将第二配置信息发送给接收端设备，由接收端设备转发第二配置信息给中间设备。即，第一设备向中间设备发 送第二配置信息可以是直接发送也可以是间接发送，本实施例对此不作限定。
接收端设备和中间设备协同补偿的流程可以包括以下步骤。
E-1，源端设备和接收端设备之间启动链路。
E-2，源端设备通过M个链路分别独立地向接收端设备发送数据帧。相应地，接收端设备接收源端设备发送的数据帧。应理解，这些数据帧中可以包括对齐标记。
E-3，接收端设备测量M个链路的差分延迟的状态。
E-4，接收端设备向源端设备发送第一状态信息，该第一状态信息用于指示M个链路的差分延迟的状态。相应地，源端设备接收接收端设备发送的第一状态信息。可选地，第一状态信息可以在FlexE中通过OH码块的shim-to-shim management channel传输。
E-5，接收端设备向源端设备发送第一能力信息，该第一能力信息用于指示接收端设备对M个链路进行差分延迟补偿的第一能力。相应地，源端设备接收接收端设备发送的第一能力信息。可选地，第一能力信息可以在FlexE中通过OH码块的shim-to-shim management channel传输。
E-6，中间设备向源端设备发送第二能力信息，第二能力信息用于指示每个中间设备对M个链路中的至少一个链路进行延迟发送补偿的第二能力。相应地，源端设备接收中间设备发送的第二能力信息。应理解，第二能力信息可以携带在E-2的数据帧中，也可以通过其他方式发送，本实施例对此不作限定。可选地，第二能力信息可以在FlexE中通过OH码块的shim-to-shim management channel传输。
E-7，中间设备向源端设备发送第二状态信息，第二状态信息用于指示每个中间设备对M个链路中的至少一个链路进行延迟发送补偿的当前状态。相应地，源端设备接收中间设备发送的第二状态信息。应理解，第二状态信息可以携带在E-2的数据帧中，也可以通过其他方式发送，本实施例对此不作限定。可选地，第二状态信息可以在FlexE中通过OH码块的section management channel传输。
E-8，源端设备根据第一状态信息、第一能力信息、第二能力信息和第二状态信息，确定如何配置链路组以及如何配置延迟发送补偿。具体的链路组配置中包括将M个链路中的N个链路划分到第一链路组。
E-9，源端设备向接收端设备发送第一配置信息和第二配置信息，第一配置信息包括指示第一链路组的信息。相应地，接收端设备接收源端设备发送的第一配置信息。
E-10，接收端设备根据第一配置信息进行差分延迟补偿的配置，例如设置本地差分延迟补偿的缓存。
E-11，接收端设备向中间设备发送第二配置信息，第二配置信息包括用于指示中间设备对相应的链路应进行的延迟发送补偿的配置。相应地，中间设备接收接收端设备发送的第二配置信息。
E-12，接收端设备向中间设备发送第一配置信息，第一配置信息包括指示第一链路组的信息。相应地，中间设备接收源端设备发送的第一配置信息。应理解，E-12为可选的步骤，执行E-12可以不用于协同补偿流程，而是用于其他过程。
E-13，中间设备根据第二配置信息调整链路发送延迟，例如，设置延迟数据发送的缓存。
E-14，中间设备向接收端设备发送更新后的延迟发送补偿的当前状态的信息。一来可 以为下次协同补偿做准备，二来通知接收端设备已经完成延迟发送补偿的配置。
E-15，接收端设备接收到中间设备发送的信息后，，重新分析各链路的差分延迟，对M个链路进行差分延迟补偿。具体地，接收端设备根据第一配置信息进行差分延迟补偿，即设置差分延迟的缓存大小。接收端设备反馈配置已完成的信息到源端设备。
E-16，源端设备根据第一配置信息向接收端设备发送业务数据。
可选地，E-8中，源端设备还可以结合将要发送给接收端设备的业务数据的相关信息，例如业务数量和/或带宽等综合因素确定链路组的配置方案。
应理解，源端设备、中间设备和接收端设备之间的，关于第一状态信息、第一能力信息、第一配置信息、第二状态信息、第二能力信息和第二配置信息中的至少一种信息的传输格式和传输通道与实施例4类似，此处不再进行赘述。
实施例8：
在本实施例中，第一设备即决策设备为源端设备，第二设备为接收端设备。接收端设备具有延迟接收补偿的能力。源端设备具有延迟发送补偿的能力，即K个上游设备为源端设备。
具体地，方法100还可以包括：第一设备根据确定的第一设备对相应的链路应进行的延迟发送补偿的配置，基于第一链路组，向第二设备传输业务数据。
图12是本实施例的配置链路组以及进行补偿的流程400的示意图。接收端设备和源端设备协同补偿的流程400可以包括以下步骤。
S405，源端设备和接收端设备之间启动链路。
S410，源端设备通过M个链路分别独立地向接收端设备发送数据帧。相应地，接收端设备接收源端设备发送的数据帧。应理解，这些数据帧中可以包括对齐标记。
S415，接收端设备测量M个链路的差分延迟的状态。
S420，接收端设备向源端设备发送第一状态信息，该第一状态信息用于指示M个链路的差分延迟的状态。相应地，源端设备接收接收端设备发送的第一状态信息。可选地，第一状态信息可以在FlexE中通过OH码块的shim-to-shim management channel传输。
S425，接收端设备向源端设备发送第一能力信息，该第一能力信息用于指示接收端设备对M个链路进行差分延迟补偿的第一能力。相应地，源端设备接收接收端设备发送的第一能力信息。可选地，第一能力信息可以在FlexE中通过OH码块的shim-to-shim management channel传输。
S430，源端设备根据第一状态信息、第一能力信息、用于指示自身对M个链路中的至少一个链路进行延迟发送补偿的能力的第二能力信息和用于指示自身对M个链路中的至少一个链路进行延迟发送补偿的状态的第二状态信息，确定如何配置链路组以及如何配置延迟发送补偿。具体的链路组配置中包括将M个链路中的N个链路划分到第一链路组。
S435，源端设备根据S430确定的延迟发送补偿的配置，调整相应的链路的发送延迟。例如，S430确定对PHY2进行延迟发送补偿，于是在S435，修改PHY2的延迟发送补偿的缓存大小。
S440，源端设备向接收端设备发送第一配置信息，第一配置信息包括指示第一链路组的信息。相应地，接收端设备接收源端设备发送的第一配置信息。
S445，接收端设备根据第一配置信息进行差分延迟补偿的配置，例如设置本地差分延 迟补偿的缓存。
S450，接收端设备向源端设备发送配置已完成的确认信息。相应地，源端设备接收接收端设备发送的确认信息。当确认信息指示源端设备的延迟发送补偿的配置成功时，执行S455；当确认信息指示源端设备的延迟发送补偿的配置失败时，重新回到S430。
S455，源端设备根据第一配置信息向接收端设备发送业务数据。
应理解，源端设备和接收端设备之间的，关于第一状态信息、第一能力信息、第一配置信息、第二状态信息、第二能力信息和第二配置信息中的至少一种信息的传输格式和传输通道与实施例4类似，此处不再进行赘述。
实施例9：
在本实施例中，第一设备即决策设备为源端设备，第二设备为接收端设备。接收端设备具有延迟接收补偿的能力。源端设备和至少一个中间设备具有延迟发送补偿的能力，即K个上游设备包括源端设备和至少一个中间设备。
具体地，方法100还可以包括：第一设备根据确定的第一设备对相应的链路应进行的延迟发送补偿的配置，基于第一链路组，向第二设备传输业务数据。
接收端设备、源端设备和至少一个中间设备协同补偿的流程可以包括以下步骤。
F-1，源端设备和接收端设备之间启动链路。
F-2，源端设备通过M个链路分别独立地向接收端设备发送数据帧。相应地，接收端设备接收源端设备发送的数据帧。应理解，这些数据帧中可以包括对齐标记。
F-3，接收端设备测量M个链路的差分延迟的状态。
F-4，接收端设备向源端设备发送第一状态信息，该第一状态信息用于指示M个链路的差分延迟的状态。相应地，源端设备接收接收端设备发送的第一状态信息。可选地，第一状态信息可以在FlexE中通过OH码块的shim-to-shim management channel传输。
F-5，接收端设备向源端设备发送第一能力信息，该第一能力信息用于指示接收端设备对M个链路进行差分延迟补偿的第一能力。相应地，源端设备接收接收端设备发送的第一能力信息。可选地，第一能力信息可以在FlexE中通过OH码块的shim-to-shim management channel传输。
F-6，中间设备向源端设备发送第二能力信息，第二能力信息用于指示每个中间设备对M个链路中的至少一个链路进行延迟发送补偿的第二能力。相应地，源端设备接收中间设备发送的第二能力信息。应理解，第二能力信息可以携带在F-2的数据帧中，也可以通过其他方式发送，本实施例对此不作限定。可选地，第二能力信息可以在FlexE中通过OH码块的shim-to-shim management channel传输。
F-7，中间设备向源端设备发送第二状态信息，第二状态信息用于指示每个中间设备对M个链路中的至少一个链路进行延迟发送补偿的当前状态。相应地，源端设备接收中间设备发送的第二状态信息。应理解，第二状态信息可以携带在F-2的数据帧中，也可以通过其他方式发送，本实施例对此不作限定。可选地，第二状态信息可以在FlexE中通过OH码块的section management channel传输。
F-8，源端设备根据第一状态信息、第一能力信息、中间设备发送的第二能力信息、用于指示自身对M个链路中的至少一个链路进行延迟发送补偿的能力的第二能力信息、中间设备发送的第二状态信息和用于指示自身对M个链路中的至少一个链路进行延迟发 送补偿的状态的第二状态信息，确定如何配置链路组以及如何配置延迟发送补偿。具体的链路组配置中包括将M个链路中的N个链路划分到第一链路组。
F-9，源端设备根据F-8确定的延迟发送补偿的配置，调整相应的链路的发送延迟。例如，F-8确定对PHY2进行延迟发送补偿，于是在F-9，修改PHY2的延迟发送补偿的缓存大小。
F-10，源端设备向接收端设备发送第一配置信息和第二配置信息，第一配置信息包括指示第一链路组的信息。相应地，接收端设备接收源端设备发送的第一配置信息。
F-11，接收端设备根据第一配置信息进行差分延迟补偿的配置，例如设置本地差分延迟补偿的缓存。
F-12，接收端设备向中间设备发送第二配置信息，第二配置信息包括用于指示中间设备对相应的链路应进行的延迟发送补偿的配置。相应地，中间设备接收接收端设备发送的第二配置信息。
F-13，接收端设备向中间设备发送第一配置信息，第一配置信息包括指示第一链路组的信息。相应地，中间设备接收源端设备发送的第一配置信息。应理解，F-13为可选的步骤，执行F-13可以不用于协同补偿流程，而是用于其他过程。
F-14，中间设备根据第二配置信息调整链路发送延迟，例如，设置延迟数据发送的缓存。
F-15，中间设备向接收端设备发送更新后的延迟发送补偿的当前状态的信息。一来可以为下次协同补偿做准备，二来通知接收端设备已经完成延迟发送补偿的配置。
F-16，接收端设备接收到中间设备发送的信息后，对M个链路进行差分延迟补偿。具体地，接收端设备根据第一配置信息进行差分延迟补偿，即设置差分延迟的缓存大小。接收端设备向源端设备发送配置已完成的信息。
F-17，源端设备根据第一配置信息向接收端设备发送业务数据。
应理解，源端设备、中间设备和接收端设备之间的，关于第一状态信息、第一能力信息、第一配置信息、第二状态信息、第二能力信息和第二配置信息中的至少一种信息的传输格式和传输通道与实施例4类似，此处不再进行赘述。
实施例10中，第一设备即决策设备为管理设备，第二设备包括接收端设备和/或源端设备。接收端设备具有延迟接收补偿的能力。K个上游设备可以包括源端设备和/或至少一个中间设备，具有延迟发送补偿的能力。
具体地，S110第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，可以包括：第一设备接收接收端设备发送的第一状态信息；S120第一设备获取接收端设备的第一能力信息，可以包括：第一设备接收接收端设备发送的第一能力信息；第一设备获取K个上游设备的每个上游设备的第二能力信息和第二状态信息，可以包括：第一设备接收每个上游设备发送的第二能力信息和第二状态信息；方法100还可以包括：第一设备向K个上游设备中的至少一个上游设备发送第二配置信息，第二配置信息用于指示至少一个上游设备对相应的链路应进行的延迟发送补偿的配置。
由管理设备决策链路组配置，并由接收端设备和其他设备协同补偿的流程可以包括以下几个步骤。
G-1，源端设备和接收端设备之间启动链路。
G-2，源端设备通过M个链路分别独立地向接收端设备发送数据帧。相应地，接收端设备接收源端设备发送的数据帧。应理解，这些数据帧中可以包括对齐标记。
G-3，接收端设备测量M个链路的差分延迟的状态。
G-4，接收端设备向管理设备发送第一状态信息，该第一状态信息用于指示M个链路的差分延迟的状态。相应地，管理设备接收接收端设备发送的第一状态信息。
G-5，接收端设备向管理设备发送第一能力信息，该第一能力信息用于指示接收端设备对M个链路进行差分延迟补偿的第一能力。相应地，管理设备接收接收端设备发送的第一能力信息。
G-6，源端设备和/或至少一个中间设备向管理设备发送第二能力信息，第二能力信息用于指示每个上游设备对M个链路中的至少一个链路进行延迟发送补偿的第二能力。相应地，管理设备接收源端设备和/或至少一个中间设备发送的第二能力信息。应理解，源端设备对应的第二能力信息可以携带在G-2的数据帧中，也可以通过其他方式发送，本实施例对此不作限定。可选地，第二能力信息可以在FlexE中通过OH码块的shim-to-shim management channel传输。
G-7，源端设备和/或至少一个中间设备向管理设备发送第二状态信息，第二状态信息用于指示每个上游设备对M个链路中的至少一个链路进行延迟发送补偿的当前状态。相应地，管理设备接收源端设备和/或至少一个中间设备发送的第二状态信息。应理解，源端设备对应的第二状态信息可以携带在G-2的数据帧中，也可以通过其他方式发送，本实施例对此不作限定。可选地，第二状态信息可以在FlexE中通过OH码块的section management channel传输。
G-8，管理设备根据第一状态信息、第一能力信息、第二状态信息和第二能力信息，确定如何配置链路组以及如何配置延迟发送补偿。具体地配置中包括将M个链路中的N个链路划分到第一链路组。
G-9，管理设备向K个上游设备(包括源端设备和/或至少一个中间设备)中需要进行延迟发送补偿配置的上游设备发送第二配置信息，用于指示延迟发送补偿的配置。
G-10，K个上游设备(包括源端设备和/或至少一个中间设备)中需要进行延迟发送补偿配置的上游设备根据第二配置信息，配置延迟发送补偿的缓存大小。
G-11，K个上游设备(包括源端设备和/或至少一个中间设备)中需要进行延迟发送补偿配置的上游设备向管理设备返回确认信息，用于指示已经收到上述第二配置信息并进行了相应的配置。相应地，管理设备接收源端设备和/或接收端设备返回的确认信息。应理解，G-11为可选的步骤。
G-12，管理设备收到确认信息之后向接收端设备发送第一配置信息和第二配置信息，第一配置信息包括用于指示第一链路组的信息。相应地，接收端设备接收管理设备发送的第一配置信息和第二配置信息。可选地，第一配置信息中还可以包括针对各链路，对接收端设备进行差分延迟补偿时的缓存需求，接收端设备根据该缓存需求直接设置各链路的缓存量。
G-13，接收端设备根据第一配置信息和第二配置信息进行相应的配置。
G-14，接收端设备可以向管理设备返回确认信息，用于指示已经收到上述第一配置信息和第二配置信息并进行了相应的配置。相应地，管理设备接收接收端设备返回的确认信 息。应理解，G-13为可选的步骤。
G-15，管理设备收到接收端设备返回的确认信息之后向源端设备发送第一配置信息。应理解，G-15为可选的步骤。
G-16，源端设备根据第一配置信息向接收端设备发送业务数据。
应理解，源端设备和接收端设备与管理设备之间的，关于第一状态信息、第一能力信息、第一配置信息、第二状态信息、第二能力信息和第二配置信息的通信可以在各设备与管理设备的OH码块的管理通道中传输。可选地，在FlexO中，上述信息可以在OH码块的GCC0字节以GFP格式、HDLC格式、PPP格式或RES字段以自定义的帧格式进行传输。在FlexE中，上述信息可以在OH码块的管理通道以网络协议(Internet Protocol，IP)报文的形式传输，本实施例对具体的传输方式不作限定。
本申请各实施例，源端设备、接收端设备，还可以包括中间设备等均可能有差分延迟补偿或延迟发送补偿的能力，本申请各实施例应用于各设备中，通过能力协商实现链路组的补偿。使得当源端设备、接收端设备之间的FlexE Group或FlexO Group中各设备的补偿能力无法补偿各链路的差分延迟时，通过配置链路组，使得源端设备只在延迟对齐的链路上承载跨链路传输业务数据。
应理解，本申请各实施例中，涉及到第一状态信息、第一能力信息、第二状态信息、第二能力信息、第一配置信息、第二配置信息和确认信息中的任意一种的传输时，可以在每个链路上传输该链路对应的状态、能力或配置信息，即以链路为粒度传输相关信息。当然，本申请各实施例也可以以其他粒度传输相关信息，例如，以设备为粒度，此处不作限定。
上文描述了本申请实施例提供的配置链路组的方法，下文将描述本申请实施例提供的配置链路组的设备。
图13是本申请一个实施例的配置链路组的设备500的示意性框图。该配置链路组的设备500为第一设备，如图13所示，配置链路组的设备500可以包括：
获取模块510，用于获取源端设备和接收端设备之间的M个链路的第一状态信息，所述第一状态信息用于指示所述M个链路中任意两个链路之间的差分延迟的状态，所述M个链路中的任意一个链路为灵活以太网FlexE物理连接链路或者灵活光传送网FlexO物理连接链路，其中，M为大于或等于2的整数。
所述获取模块510还用于获取所述接收端设备的第一能力信息，所述第一能力信息用于指示所述接收端设备对所述M个链路进行差分延迟补偿的第一能力。
处理模块520，用于根据所述获取模块510获取的所述第一状态信息和所述获取模块510获取的所述第一能力信息，将所述M个链路中的N个链路划分到第一链路组，其中，N为小于或等于M且大于或等于2的整数。
发送模块530，用于向第二设备发送第一配置信息，所述第一配置信息包括用于指示所述第一链路组的信息。
本申请实施例的配置链路组的设备，根据源端设备和接收端设备之间的M个链路的差分延迟的状态和接收端设备对M个链路进行差分延迟补偿的能力，将M个链路中的N个链路划分到第一链路组，从而避免了M个链路的差分延迟超出接收端设备的差分延迟补偿能力时所有的M个链路不可用的情况，可以提高传送网中链路的可用性和鲁棒性。
可选地，作为一个可选实施例，所述第一设备为所述接收端设备，所述第二设备为所述源端设备，所述获取模块510具体用于：测量所述M个链路的差分延迟，获得所述第一状态信息；所述设备500还包括：补偿模块540，用于根据所述第一配置信息，对所述第一链路组中的链路进行差分延迟补偿；传输模块550，用于基于所述第一链路组，与所述第二设备传输业务数据。
可选地，作为一个可选实施例，所述获取模块510具体用于：接收所述接收端设备发送的所述第一状态信息；接收所述接收端设备发送的所述第一能力信息。
可选地，作为一个可选实施例，所述第一设备为所述源端设备，所述第二设备为所述接收端设备；或所述第一设备为管理设备，所述第二设备包括所述接收端设备和/或所述源端设备。
可选地，作为一个可选实施例，在所述M个链路上，所述接收端设备的K个上游设备具有延迟发送补偿的能力，其中，K为正整数，所述K个上游设备包括所述源端设备和/或至少一个中间设备，所述中间设备在所述M个链路上位于所述源端设备与所述接收端设备之间，所述获取模块510还用于：获取所述K个上游设备的每个上游设备的第二能力信息和第二状态信息，所述第二能力信息用于指示所述每个上游设备对所述M个链路中的至少一个链路进行延迟发送补偿的第二能力，所述第二状态信息用于指示所述每个上游设备对所述M个链路中的至少一个链路进行延迟发送补偿的当前状态；所述处理模块520具体用于：根据所述第一状态信息、所述第一能力信息、所述第二状态信息和所述第二能力信息，将所述M个链路中的所述N个链路划分到所述第一链路组；所述处理模块520还用于：根据所述第一状态信息、所述第一能力信息、所述第二状态信息和所述第二能力信息，确定所述每个上游设备对相应的链路应进行的延迟发送补偿的配置。
应理解，在接收端设备处M个链路无法对齐时，M个链路不能组成一个链路组，或者说FlexE Group或FlexO Group崩溃无法工作，本申请各实施例的源端设备、接收端设备，还可以包括中间设备等均可能有差分延迟补偿或延迟发送补偿的能力，本申请各实施例各设备通过能力协商实现链路组的补偿。使得当源端设备、接收端设备之间的FlexE Group或FlexO Group中各设备的补偿能力无法补偿各链路的差分延迟时，通过配置链路组，使得源端设备只在延迟对齐的链路上承载跨链路传输业务数据；或者通过各设备协同补偿，使得最终M个链路在接收端设备处可以对齐，能够保证FlexE Group或FlexO Group的工作，可以提高链路的利用率。
可选地，作为一个可选实施例，所述第一设备为所述接收端设备，所述第二设备为所述源端设备，所述获取模块510具体用于：测量所述M个链路的差分延迟，获得所述第一状态信息；接收所述每个上游设备发送的所述第二能力信息和所述第二状态信息；所述发送模块530还用于：向所述K个上游设备中的至少一个上游设备发送第二配置信息，所述第二配置信息用于指示所述至少一个上游设备对相应的链路应进行延迟发送补偿的配置。
可选地，作为一个可选实施例，所述设备500还可以包括：补偿模块540，用于根据所述第一配置信息，对所述第一链路组中已经过所述至少一个上游设备根据所述第二配置信息进行延迟发送补偿的链路进行差分延迟补偿；传输模块550，用于基于所述第一链路组，与所述第二设备传输业务数据。
可选地，作为一个可选实施例，所述第一设备为所述源端设备，所述第二设备为所述接收端设备，所述获取模块510具体可以用于：接收所述接收端设备发送的所述第一状态信息；接收所述接收端设备发送的所述第一能力信息。
可选地，作为一个可选实施例，所述K个上游设备中包括所述第一设备，所述设备500还可以包括：传输模块540，用于根据确定的所述第一设备对相应的链路应进行的延迟发送补偿的配置，基于所述第一链路组，向所述第二设备传输业务数据。
可选地，作为一个可选实施例，所述K个上游设备中包括至少一个中间设备，所述获取模块510具体用于：接收所述至少一个中间设备中的每个中间设备发送的所述第二能力信息和所述第二状态信息；所述发送模块530还用于：向所述至少一个中间设备中的至少部分中间设备发送第二配置信息，所述第二配置信息用于指示所述至少部分中间设备对相应的链路应进行的延迟发送补偿的配置。
可选地，作为一个可选实施例，所述第一设备为管理设备，所述第二设备包括所述接收端设备和/或所述源端设备，所述获取模块510具体可以用于：接收所述接收端设备发送的所述第一状态信息；接收所述接收端设备发送的所述第一能力信息；接收所述每个上游设备发送的所述第二能力信息和所述第二状态信息；所述发送模块530还可以用于：向所述K个上游设备中的至少一个上游设备发送第二配置信息，所述第二配置信息用于指示所述至少一个上游设备对相应的链路应进行的延迟发送补偿的配置。
可选地，作为一个可选实施例，所述第一配置信息包括用于指示链路属于所述第一链路组的标记。
可选地，作为一个可选实施例，所述发送模块530具体可以用于：将所述第一配置信息承载在开销码块的保留字段中发送给所述第二设备。
可选地，作为一个可选实施例，所述发送模块530具体可以用于：将用于指示所述N个链路中的第一链路属于所述第一链路组的所述第一配置信息，通过所述第一链路发送给所述第二设备。
可选地，作为一个可选实施例，所述第一配置信息中的第一部分比特用于指示所述第一链路与其他链路组成了所述第一链路组，所述第一配置信息中的第二部分比特为所述第一链路组的标记。
可选地，作为一个可选实施例，所述获取模块510具体用于：接收由所述接收端设备发送的，承载在开销码块的管理通道的链路层发现协议LLDP格式的第一类型长度值TLV单元中的所述第一状态信息。
可选地，作为一个可选实施例，所述第一TLV单元还能够承载用于指示在所述接收端设备向所述源端设备发送业务数据时，所述接收端设备对所述M个链路进行延迟发送补偿的当前状态的信息。
可选地，作为一个可选实施例，所述第一TLV单元还能够承载用于指示上游设备对相应的链路应进行的延迟发送补偿的配置的信息。
可选地，作为一个可选实施例，所述获取模块510具体用于：接收由所述接收端设备发送的，承载在开销码块的管理通道的链路层发现协议LLDP格式的第二类型长度值TLV单元中的所述第一能力信息。
可选地，作为一个可选实施例，所述第二TLV单元还能够承载用于指示在所述接收 端设备向所述源端设备发送业务数据时，所述接收端设备对所述M个链路进行延迟发送补偿的能力的信息。
应理解，本申请实施例中的获取模块510的部分功能可以由处理器或处理器相关电路组件实现，获取模块510的部分功能可以由网络接口或网络接口相关电路组件实现，处理模块520可以由处理器或处理器相关电路组件实现，发送模块530可以由网络接口或网络接口相关电路组件实现。
如图14所示，本申请实施例还提供一种配置链路组的设备600，该配置链路组的设备600是第一设备，该配置链路组的设备600包括处理器610，存储器620与网络接口630，该存储器620用于存储指令，该处理器610与网络接口630用于执行该存储器620存储的指令。
配置链路组的设备600的处理器610与网络接口630执行该存储器620存储的指令时，使得：
第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，所述第一状态信息用于指示所述M个链路中任意两个链路之间的差分延迟的状态，所述M个链路中的任意一个链路为灵活以太网FlexE物理连接链路或者灵活光传送网FlexO物理连接链路，其中，M为大于或等于2的整数；
所述第一设备获取所述接收端设备的第一能力信息，所述第一能力信息用于指示所述接收端设备对所述M个链路进行差分延迟补偿的第一能力；
所述第一设备根据所述第一状态信息和所述第一能力信息，将所述M个链路中的N个链路划分到第一链路组，其中，N为小于或等于M且大于或等于2的整数；
所述第一设备向第二设备发送第一配置信息，所述第一配置信息包括用于指示所述第一链路组的信息。
本申请实施例的配置链路组的设备，根据源端设备和接收端设备之间的M个链路的差分延迟的状态和接收端设备对M个链路进行差分延迟补偿的能力，将M个链路中的N个链路划分到第一链路组，从而避免了M个链路的差分延迟超出接收端设备的差分延迟补偿能力时所有的M个链路不可用的情况，可以提高传送网中链路的可用性和鲁棒性。
应理解，图13所示的配置链路组的设备500或图14所示的配置链路组的设备600可用于执行上述方法实施例中与终端设备相关的操作或流程，并且配置链路组的设备500或配置链路组的设备600中的各个模块的操作和/或功能分别为了实现上述方法实施例中的相应流程，为了简洁，在此不再赘述。
应理解，本发明实施例中提及的处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本发明实施例中提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可 擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)集成在处理器中。
应注意，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本发明实施例还提供一种计算机可读存储介质，其上存储有存储有指令，当所述指令在计算机上运行时，使得所述计算机执行上述方法实施例的配置链路组的方法。具体地，该计算机可以为上述配置链路组的设备，即第一设备。
本发明实施例还提供一种包括指令的计算机程序产品，其特征在于，当计算机运行所述计算机程序产品的所述指时，所述计算机执行上述方法实施例的配置链路组的方法。具体地，该计算机程序产品可以运行于上述配置链路组的设备，即第一设备上。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(Digital Video Disc，DVD))、或者半导体介质(例如，固态硬盘(Solid State Disk，SSD))等。
应理解，本文中涉及的第一、第二以及各种数字编号仅为描述方便进行的区分，并不用来限制本申请的范围。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (41)

  1. 一种配置链路组的方法，其特征在于，包括：
    第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，所述第一状态信息用于指示所述M个链路中任意两个链路之间的差分延迟的状态，所述M个链路中的任意一个链路为灵活以太网FlexE物理连接链路或者灵活光传送网FlexO物理连接链路，其中，M为大于或等于2的整数；
    所述第一设备获取所述接收端设备的第一能力信息，所述第一能力信息用于指示所述接收端设备对所述M个链路进行差分延迟补偿的第一能力；
    所述第一设备根据所述第一状态信息和所述第一能力信息，将所述M个链路中的N个链路划分到第一链路组，其中，N为小于或等于M且大于或等于2的整数；
    所述第一设备向第二设备发送第一配置信息，所述第一配置信息包括用于指示所述第一链路组的信息。
  2. 根据权利要求1所述的方法，其特征在于，所述第一设备为所述接收端设备，所述第二设备为所述源端设备，所述第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，包括：
    所述第一设备测量所述M个链路的差分延迟，获得所述第一状态信息；
    所述方法还包括：
    所述第一设备根据所述第一配置信息，对所述第一链路组中的链路进行差分延迟补偿；
    所述第一设备基于所述第一链路组，与所述第二设备传输业务数据。
  3. 根据权利要求1所述的方法，其特征在于，所述第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，包括：
    所述第一设备接收所述接收端设备发送的所述第一状态信息；
    所述第一设备获取所述接收端设备的第一能力信息，包括：
    所述第一设备接收所述接收端设备发送的所述第一能力信息。
  4. 根据权利要求3所述的方法，其特征在于，所述第一设备为所述源端设备，所述第二设备为所述接收端设备；或
    所述第一设备为管理设备，所述第二设备包括所述接收端设备和/或所述源端设备。
  5. 根据权利要求1所述的方法，其特征在于，在所述M个链路上，所述接收端设备的K个上游设备具有延迟发送补偿的能力，其中，K为正整数，所述K个上游设备包括所述源端设备和/或至少一个中间设备，所述中间设备在所述M个链路上位于所述源端设备与所述接收端设备之间，所述方法还包括：
    所述第一设备获取所述K个上游设备的每个上游设备的第二能力信息和第二状态信息，所述第二能力信息用于指示所述每个上游设备对所述M个链路中的至少一个链路进行延迟发送补偿的第二能力，所述第二状态信息用于指示所述每个上游设备对所述M个链路中的至少一个链路进行延迟发送补偿的当前状态；
    所述第一设备根据所述第一状态信息和所述第一能力信息，将所述M个链路中的N 个链路划分到第一链路组，包括：
    所述第一设备根据所述第一状态信息、所述第一能力信息、所述第二状态信息和所述第二能力信息，将所述M个链路中的所述N个链路划分到所述第一链路组；
    所述方法还包括：
    所述第一设备根据所述第一状态信息、所述第一能力信息、所述第二状态信息和所述第二能力信息，确定所述每个上游设备对相应的链路应进行的延迟发送补偿的配置。
  6. 根据权利要求5所述的方法，其特征在于，所述第一设备为所述接收端设备，所述第二设备为所述源端设备，所述第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，包括：
    所述第一设备测量所述M个链路的差分延迟，获得所述第一状态信息；
    所述第一设备获取所述K个上游设备的每个上游设备的第二能力信息和第二状态信息，包括：
    所述第一设备接收所述每个上游设备发送的所述第二能力信息和所述第二状态信息；
    所述方法还包括：
    所述第一设备向所述K个上游设备中的至少一个上游设备发送第二配置信息，所述第二配置信息用于指示所述至少一个上游设备对相应的链路应进行延迟发送补偿的配置。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    所述第一设备根据所述第一配置信息，对所述第一链路组中已经过所述至少一个上游设备根据所述第二配置信息进行延迟发送补偿的链路进行差分延迟补偿；
    所述第一设备基于所述第一链路组，与所述第二设备传输业务数据。
  8. 根据权利要求5所述的方法，其特征在于，所述第一设备为所述源端设备，所述第二设备为所述接收端设备，所述第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，包括：
    所述第一设备接收所述接收端设备发送的所述第一状态信息；
    所述第一设备获取所述接收端设备的第一能力信息，包括：
    所述第一设备接收所述接收端设备发送的所述第一能力信息。
  9. 根据权利要求8所述的方法，其特征在于，所述K个上游设备中包括所述第一设备，所述方法还包括：
    所述第一设备根据确定的所述第一设备对相应的链路应进行的延迟发送补偿的配置，基于所述第一链路组，向所述第二设备传输业务数据。
  10. 根据权利要求8或9所述的方法，其特征在于，所述K个上游设备中包括至少一个中间设备，所述第一设备获取所述K个上游设备的每个上游设备的第二能力信息和第二状态信息，包括：
    所述第一设备接收所述至少一个中间设备中的每个中间设备发送的所述第二能力信息和所述第二状态信息；
    所述方法还包括：
    所述第一设备向所述至少一个中间设备中的至少部分中间设备发送第二配置信息，所述第二配置信息用于指示所述至少部分中间设备对相应的链路应进行的延迟发送补偿的配置。
  11. 根据权利要求5所述的方法，其特征在于，所述第一设备为管理设备，所述第二设备包括所述接收端设备和/或所述源端设备，所述第一设备获取源端设备和接收端设备之间的M个链路的第一状态信息，包括：
    所述第一设备接收所述接收端设备发送的所述第一状态信息；
    所述第一设备获取所述接收端设备的第一能力信息，包括：
    所述第一设备接收所述接收端设备发送的所述第一能力信息；
    所述第一设备获取所述K个上游设备的每个上游设备的第二能力信息和第二状态信息，包括：
    所述第一设备接收所述每个上游设备发送的所述第二能力信息和所述第二状态信息；
    所述方法还包括：
    所述第一设备向所述K个上游设备中的至少一个上游设备发送第二配置信息，所述第二配置信息用于指示所述至少一个上游设备对相应的链路应进行的延迟发送补偿的配置。
  12. 根据权利要求1至11中任一项所述的方法，其特征在于，所述第一配置信息包括用于指示链路属于所述第一链路组的标记。
  13. 根据权利要求1至12中任一项所述的方法，其特征在于，所述第一设备向第二设备发送第一配置信息，包括：
    所述第一设备将所述第一配置信息承载在开销码块的保留字段中发送给所述第二设备。
  14. 根据权利要求1至13中任一项所述的方法，其特征在于，所述第一设备向第二设备发送第一配置信息，包括：
    所述第一设备将用于指示所述N个链路中的第一链路属于所述第一链路组的所述第一配置信息，通过所述第一链路发送给所述第二设备。
  15. 根据权利要求14所述的方法，其特征在于，所述第一配置信息中的第一部分比特用于指示所述第一链路与其他链路组成所述第一链路组，所述第一配置信息中的第二部分比特为所述第一链路组的标记。
  16. 根据权利要求3、4、8、9和11中任一项所述的方法，其特征在于，所述第一设备接收所述接收端设备发送的所述第一状态信息，包括：
    所述第一设备接收由所述接收端设备发送的，承载在开销码块的管理通道的链路层发现协议LLDP格式的第一类型长度值TLV单元中的所述第一状态信息。
  17. 根据权利要求16所述的方法，其特征在于，所述第一TLV单元还能够承载用于指示在所述接收端设备向所述源端设备发送业务数据时，所述接收端设备对所述M个链路进行延迟发送补偿的当前状态的信息。
  18. 根据权利要求16或17所述的方法，其特征在于，所述第一TLV单元还能够承载用于指示上游设备对相应的链路应进行的延迟发送补偿的配置的信息。
  19. 根据权利要求3、4、8、9和11中任一项所述的方法，其特征在于，所述第一设备接收所述接收端设备发送的所述第一能力信息，包括：
    所述第一设备接收由所述接收端设备发送的，承载在开销码块的管理通道的链路层发现协议LLDP格式的第二类型长度值TLV单元中的所述第一能力信息。
  20. 根据权利要求19所述的方法，其特征在于，所述第二TLV单元还能够承载用于 指示在所述接收端设备向所述源端设备发送业务数据时，所述接收端设备对所述M个链路进行延迟发送补偿的能力的信息。
  21. 一种配置链路组的设备，其特征在于，所述设备为第一设备，包括：
    获取模块，用于获取源端设备和接收端设备之间的M个链路的第一状态信息，所述第一状态信息用于指示所述M个链路中任意两个链路之间的差分延迟的状态，所述M个链路中的任意一个链路为灵活以太网FlexE物理连接链路或者灵活光传送网FlexO物理连接链路，其中，M为大于或等于2的整数；
    所述获取模块还用于获取所述接收端设备的第一能力信息，所述第一能力信息用于指示所述接收端设备对所述M个链路进行差分延迟补偿的第一能力；
    处理模块，用于根据所述获取模块获取的所述第一状态信息和所述获取模块获取的所述第一能力信息，将所述M个链路中的N个链路划分到第一链路组，其中，N为小于或等于M且大于或等于2的整数；
    发送模块，用于向第二设备发送第一配置信息，所述第一配置信息包括用于指示所述第一链路组的信息。
  22. 根据权利要求21所述的设备，其特征在于，所述第一设备为所述接收端设备，所述第二设备为所述源端设备，所述获取模块具体用于：
    测量所述M个链路的差分延迟，获得所述第一状态信息；
    所述设备还包括：
    补偿模块，用于根据所述第一配置信息，对所述第一链路组中的链路进行差分延迟补偿；
    传输模块，用于基于所述第一链路组，与所述第二设备传输业务数据。
  23. 根据权利要求21所述的设备，其特征在于，所述获取模块具体用于：
    接收所述接收端设备发送的所述第一状态信息；
    接收所述接收端设备发送的所述第一能力信息。
  24. 根据权利要求23所述的设备，其特征在于，所述第一设备为所述源端设备，所述第二设备为所述接收端设备；或
    所述第一设备为管理设备，所述第二设备包括所述接收端设备和/或所述源端设备。
  25. 根据权利要求21所述的设备，其特征在于，在所述M个链路上，所述接收端设备的K个上游设备具有延迟发送补偿的能力，其中，K为正整数，所述K个上游设备包括所述源端设备和/或至少一个中间设备，所述中间设备在所述M个链路上位于所述源端设备与所述接收端设备之间，所述获取模块还用于：
    获取所述K个上游设备的每个上游设备的第二能力信息和第二状态信息，所述第二能力信息用于指示所述每个上游设备对所述M个链路中的至少一个链路进行延迟发送补偿的第二能力，所述第二状态信息用于指示所述每个上游设备对所述M个链路中的至少一个链路进行延迟发送补偿的当前状态；
    所述处理模块具体用于：
    根据所述第一状态信息、所述第一能力信息、所述第二状态信息和所述第二能力信息，将所述M个链路中的所述N个链路划分到所述第一链路组；
    所述处理模块还用于：
    根据所述第一状态信息、所述第一能力信息、所述第二状态信息和所述第二能力信息，确定所述每个上游设备对相应的链路应进行的延迟发送补偿的配置。
  26. 根据权利要求25所述的设备，其特征在于，所述第一设备为所述接收端设备，所述第二设备为所述源端设备，所述获取模块具体用于：
    测量所述M个链路的差分延迟，获得所述第一状态信息；
    接收所述每个上游设备发送的所述第二能力信息和所述第二状态信息；
    所述发送模块还用于：
    向所述K个上游设备中的至少一个上游设备发送第二配置信息，所述第二配置信息用于指示所述至少一个上游设备对相应的链路应进行延迟发送补偿的配置。
  27. 根据权利要求26所述的设备，其特征在于，所述设备还包括：
    补偿模块，用于根据所述第一配置信息，对所述第一链路组中已经过所述至少一个上游设备根据所述第二配置信息进行延迟发送补偿的链路进行差分延迟补偿；
    传输模块，用于基于所述第一链路组，与所述第二设备传输业务数据。
  28. 根据权利要求25所述的设备，其特征在于，所述第一设备为所述源端设备，所述第二设备为所述接收端设备，所述获取模块具体用于：
    接收所述接收端设备发送的所述第一状态信息；
    接收所述接收端设备发送的所述第一能力信息。
  29. 根据权利要求28所述的设备，其特征在于，所述K个上游设备中包括所述第一设备，所述设备还包括：
    传输模块，用于根据确定的所述第一设备对相应的链路应进行的延迟发送补偿的配置，基于所述第一链路组，向所述第二设备传输业务数据。
  30. 根据权利要求28或29所述的设备，其特征在于，所述K个上游设备中包括至少一个中间设备，所述获取模块具体用于：
    接收所述至少一个中间设备中的每个中间设备发送的所述第二能力信息和所述第二状态信息；
    所述发送模块还用于：
    向所述至少一个中间设备中的至少部分中间设备发送第二配置信息，所述第二配置信息用于指示所述至少部分中间设备对相应的链路应进行的延迟发送补偿的配置。
  31. 根据权利要求25所述的设备，其特征在于，所述第一设备为管理设备，所述第二设备包括所述接收端设备和/或所述源端设备，所述获取模块具体用于：
    接收所述接收端设备发送的所述第一状态信息；
    接收所述接收端设备发送的所述第一能力信息；
    接收所述每个上游设备发送的所述第二能力信息和所述第二状态信息；
    所述发送模块还用于：
    向所述K个上游设备中的至少一个上游设备发送第二配置信息，所述第二配置信息用于指示所述至少一个上游设备对相应的链路应进行的延迟发送补偿的配置。
  32. 根据权利要求21至31中任一项所述的设备，其特征在于，所述第一配置信息包括用于指示链路属于所述第一链路组的标记。
  33. 根据权利要求21至32中任一项所述的设备，其特征在于，所述发送模块具体用 于：
    将所述第一配置信息承载在开销码块的保留字段中发送给所述第二设备。
  34. 根据权利要求21至33中任一项所述的设备，其特征在于，所述发送模块具体用于：
    将用于指示所述N个链路中的第一链路属于所述第一链路组的所述第一配置信息，通过所述第一链路发送给所述第二设备。
  35. 根据权利要求34所述的设备，其特征在于，所述第一配置信息中的第一部分比特用于指示所述第一链路与其他链路组成所述第一链路组，所述第一配置信息中的第二部分比特为所述第一链路组的标记。
  36. 根据权利要求23、24、28、29和31中任一项所述的设备，其特征在于，所述获取模块具体用于：
    接收由所述接收端设备发送的，承载在开销码块的管理通道的链路层发现协议LLDP格式的第一类型长度值TLV单元中的所述第一状态信息。
  37. 根据权利要求36所述的设备，其特征在于，所述第一TLV单元还能够承载用于指示在所述接收端设备向所述源端设备发送业务数据时，所述接收端设备对所述M个链路进行延迟发送补偿的当前状态的信息。
  38. 根据权利要求36或37所述的设备，其特征在于，所述第一TLV单元还能够承载用于指示上游设备对相应的链路应进行的延迟发送补偿的配置的信息。
  39. 根据权利要求23、24、28、29和31中任一项所述的设备，其特征在于，所述获取模块具体用于：
    接收由所述接收端设备发送的，承载在开销码块的管理通道的链路层发现协议LLDP格式的第二类型长度值TLV单元中的所述第一能力信息。
  40. 根据权利要求39所述的设备，其特征在于，所述第二TLV单元还能够承载用于指示在所述接收端设备向所述源端设备发送业务数据时，所述接收端设备对所述M个链路进行延迟发送补偿的能力的信息。
  41. 一种计算机存储介质，其特征在于，其上存储有指令，当所述指令在计算机上运行时，使得所述计算机执行权利要求1至20中任一项所述的方法。
PCT/CN2018/082469 2017-04-28 2018-04-10 配置链路组的方法和设备 WO2018196600A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
KR1020197034789A KR102271493B1 (ko) 2017-04-28 2018-04-10 링크 그룹을 구성하는 방법 및 디바이스
JP2019558743A JP6831927B2 (ja) 2017-04-28 2018-04-10 リンクグループ構成方法及びデバイス
EP21190454.5A EP3975469A1 (en) 2017-04-28 2018-04-10 Link group configuration method and device
EP18791648.1A EP3609115B1 (en) 2017-04-28 2018-04-10 Method and device for configuring link group
US16/665,675 US11082332B2 (en) 2017-04-28 2019-10-28 Link group configuration method and device
US17/390,345 US11570088B2 (en) 2017-04-28 2021-07-30 Link group configuration method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710295516.7A CN108809674B (zh) 2017-04-28 2017-04-28 配置链路组的方法和设备
CN201710295516.7 2017-04-28

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/665,675 Continuation US11082332B2 (en) 2017-04-28 2019-10-28 Link group configuration method and device

Publications (1)

Publication Number Publication Date
WO2018196600A1 true WO2018196600A1 (zh) 2018-11-01

Family

ID=63919453

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/082469 WO2018196600A1 (zh) 2017-04-28 2018-04-10 配置链路组的方法和设备

Country Status (6)

Country Link
US (2) US11082332B2 (zh)
EP (2) EP3609115B1 (zh)
JP (1) JP6831927B2 (zh)
KR (1) KR102271493B1 (zh)
CN (3) CN111147298B (zh)
WO (1) WO2018196600A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI757967B (zh) * 2019-11-12 2022-03-11 新加坡商聯發科技（新加坡）私人有限公司 資料發送的裝置和方法
JP2022520281A (ja) * 2019-02-19 2022-03-29 華為技術有限公司 フレキシブルイーサネット通信方法及びネットワーク装置
WO2022089245A1 (zh) * 2020-11-02 2022-05-05 中兴通讯股份有限公司 一种业务传输方法、通信设备及存储介质

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111147298B (zh) * 2017-04-28 2022-04-05 华为技术有限公司 一种能力发现以及状态发现的方法和设备
WO2019119388A1 (en) 2017-12-22 2019-06-27 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatus for configuring a flex ethernet node
CN110635931B (zh) 2018-06-22 2021-05-14 华为技术有限公司 链路组配置方法和装置
CN110719182B (zh) * 2018-07-12 2021-11-16 中兴通讯股份有限公司 一种链路容量的调整方法及装置
CN111211957B (zh) * 2018-11-21 2021-10-01 华为技术有限公司 通信方法和装置
CN111263250B (zh) * 2018-11-30 2021-03-23 华为技术有限公司 业务数据处理方法及设备
CN111294226B (zh) * 2018-12-10 2023-05-09 华为技术有限公司 通信方法和装置
CN111314404B (zh) * 2018-12-12 2022-08-02 深圳市中兴微电子技术有限公司 一种基于FlexE的数据处理的方法及装置、设备及存储介质
CN111342983B (zh) * 2018-12-18 2022-07-12 深圳市中兴微电子技术有限公司 成员动态处理方法、系统、接收端、管理实体及存储介质
CN109688016B (zh) * 2019-01-25 2022-06-03 中兴通讯股份有限公司 灵活以太网协议中切换时隙配置的方法及相关设备
CN111585779B (zh) * 2019-02-19 2021-10-15 华为技术有限公司 一种灵活以太网通信方法及网络设备
US11150963B2 (en) * 2019-02-28 2021-10-19 Cisco Technology, Inc. Remote smart NIC-based service acceleration
US11128742B2 (en) 2019-03-08 2021-09-21 Microsemi Storage Solutions, Inc. Method for adapting a constant bit rate client signal into the path layer of a telecom signal
CN111817986B (zh) * 2019-04-11 2023-05-09 中国移动通信有限公司研究院 一种报文处理方法、装置及计算机可读存储介质
US11108895B2 (en) * 2019-08-23 2021-08-31 Microchip Technology Inc. Method for providing path signal overhead in the 64B/66B character stream of an itu-t metro transport network using micro-packets
MX2022002975A (es) * 2019-09-12 2022-04-06 Huawei Tech Co Ltd Metodo de negociacion de intervalos y dispositivo.
CN112532522B (zh) * 2019-09-19 2023-09-05 中兴通讯股份有限公司 一种业务路径的建立方法、装置、电子设备
CN115039358A (zh) * 2020-04-29 2022-09-09 华为技术有限公司 一种数据传输方法及装置
US11916662B2 (en) 2021-06-30 2024-02-27 Microchip Technology Inc. System and method for performing rate adaptation of constant bit rate (CBR) client data with a fixed number of idle blocks for transmission over a metro transport network (MTN)
US11838111B2 (en) 2021-06-30 2023-12-05 Microchip Technology Inc. System and method for performing rate adaptation of constant bit rate (CBR) client data with a variable number of idle blocks for transmission over a metro transport network (MTN)
US11736065B2 (en) 2021-10-07 2023-08-22 Microchip Technology Inc. Method and apparatus for conveying clock-related information from a timing device
US11799626B2 (en) 2021-11-23 2023-10-24 Microchip Technology Inc. Method and apparatus for carrying constant bit rate (CBR) client signals
CN116996871B (zh) * 2023-09-26 2023-12-22 深圳市微克科技有限公司 一种基于LoRa协议的无线通讯方法、系统及介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3113502A1 (en) * 2015-06-30 2017-01-04 Ciena Corporation Flexible ethernet systems and methods for switching, oam, multi-service, chip-to-chip interface, time transfer, and encryption
CN106341207A (zh) * 2015-07-06 2017-01-18 华为技术有限公司 一种编码块数据流的发送和接收方法、设备和系统
CN106452812A (zh) * 2015-08-10 2017-02-22 华为技术有限公司 灵活以太网子链路的自协商方法及装置

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6892334B2 (en) * 2002-08-06 2005-05-10 Lsi Logic Corporation Method for determining deskew margins in parallel interface receivers
US7467056B2 (en) * 2007-03-09 2008-12-16 Nortel Networks Limited Method and apparatus for aligning multiple outputs of an FPGA
US20090116404A1 (en) * 2007-11-01 2009-05-07 Telefonaktiebolaget Lm Ericsson (Publ) Topology discovery in heterogeneous networks
CN101242238B (zh) * 2008-03-24 2011-04-20 华为技术有限公司 测量最小克服歪斜能力的方法、系统及装置
JP5038207B2 (ja) * 2008-03-27 2012-10-03 日本オクラロ株式会社 伝送システム及びデータ伝送方法
CN101729940B (zh) * 2008-10-22 2013-06-05 华为技术有限公司 向多路通信通道发送数据的方法及接收数据的方法
US8161210B1 (en) * 2008-11-03 2012-04-17 Integrated Device Technology Inc. Multi-queue system and method for deskewing symbols in data streams
US8201005B2 (en) * 2009-03-17 2012-06-12 Intel Corporation Negotiating a transmit wake time
US9819546B2 (en) * 2011-07-07 2017-11-14 Ciena Corporation Data connectivity systems and methods through packet-optical switches
JP5301643B2 (ja) 2011-12-20 2013-09-25 アンリツ株式会社 異常レーン検出回路及び方法並びにデスキュー回路及び方法
US9929829B1 (en) * 2012-02-15 2018-03-27 Cisco Technology, Inc. System and method for provisioning resources for lossless operation in a network environment
JP5252361B2 (ja) 2012-03-29 2013-07-31 株式会社日立製作所 伝送システム
US8913705B2 (en) * 2012-08-27 2014-12-16 Oracle International Corporation Dynamic skew correction in a multi-lane communication link
US9961668B2 (en) * 2014-10-16 2018-05-01 Qualcomm Incorporated Communication between devices of a neighbor aware network
US9806950B2 (en) * 2015-02-26 2017-10-31 Cisco Technology, Inc. System and method for automatically detecting and configuring server uplink network interface
US10218823B2 (en) * 2015-06-30 2019-02-26 Ciena Corporation Flexible ethernet client multi-service and timing transparency systems and methods
US9825696B2 (en) * 2016-01-13 2017-11-21 Ciena Corporation Ethernet link state signaling for packet flows mapped into optical transport network with generic framing procedure
US10313917B2 (en) * 2017-04-24 2019-06-04 Huawei Technologies Co., Ltd. UE load-sensitive front-haul controller
CN111147298B (zh) * 2017-04-28 2022-04-05 华为技术有限公司 一种能力发现以及状态发现的方法和设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3113502A1 (en) * 2015-06-30 2017-01-04 Ciena Corporation Flexible ethernet systems and methods for switching, oam, multi-service, chip-to-chip interface, time transfer, and encryption
CN106341207A (zh) * 2015-07-06 2017-01-18 华为技术有限公司 一种编码块数据流的发送和接收方法、设备和系统
CN106452812A (zh) * 2015-08-10 2017-02-22 华为技术有限公司 灵活以太网子链路的自协商方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LAN/MAN: "IEEE Std 802.3", IEEE STD 802.3, 3 September 2015 (2015-09-03), pages 1 - 4017, XP009519518 *
See also references of EP3609115A4

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2022520281A (ja) * 2019-02-19 2022-03-29 華為技術有限公司 フレキシブルイーサネット通信方法及びネットワーク装置
JP7282187B2 (ja) 2019-02-19 2023-05-26 華為技術有限公司 フレキシブルイーサネット通信方法及びネットワーク装置
US11792067B2 (en) 2019-02-19 2023-10-17 Huawei Technologies Co., Ltd. Flexible ethernet communication method and network device
TWI757967B (zh) * 2019-11-12 2022-03-11 新加坡商聯發科技（新加坡）私人有限公司 資料發送的裝置和方法
WO2022089245A1 (zh) * 2020-11-02 2022-05-05 中兴通讯股份有限公司 一种业务传输方法、通信设备及存储介质

Also Published As

Publication number Publication date
CN111147298A (zh) 2020-05-12
CN111147298B (zh) 2022-04-05
US11570088B2 (en) 2023-01-31
JP2020519098A (ja) 2020-06-25
CN108809674A (zh) 2018-11-13
CN108809674B (zh) 2020-01-10
KR20200003002A (ko) 2020-01-08
EP3609115B1 (en) 2021-08-11
US11082332B2 (en) 2021-08-03
JP6831927B2 (ja) 2021-02-17
EP3975469A1 (en) 2022-03-30
EP3609115A1 (en) 2020-02-12
CN111106964A (zh) 2020-05-05
KR102271493B1 (ko) 2021-06-30
US20210359934A1 (en) 2021-11-18
EP3609115A4 (en) 2020-04-29
US20200067827A1 (en) 2020-02-27

Similar Documents

Publication Publication Date Title
WO2018196600A1 (zh) 配置链路组的方法和设备
JP6666051B2 (ja) データ伝送方法、デバイスおよびシステム
WO2018090856A1 (zh) 用于建立灵活以太网群组的方法和设备
KR102342286B1 (ko) Dcn 메시지 처리 방법, 네트워크 디바이스, 및 네트워크 시스템
US20150092780A1 (en) Label Distribution Method and Device
WO2018210169A1 (zh) 数据传输方法、装置、设备及系统
WO2010031324A1 (zh) 数据传输的方法、装置和系统
WO2018184496A1 (zh) 多归接入方法、装置及多归属节点
JP2006087107A (ja) 回復力のあるパケット・リング・ネットワークにおいてトラフィックをブリッジする方法及びシステム
WO2019076046A1 (zh) 传输路径配置方法、装置及设备
WO2021197208A1 (zh) 一种业务流调整方法和通信装置
WO2012088962A1 (zh) 自动发现ODUflex带宽无损调整能力的方法及系统
WO2020103530A1 (zh) 通信方法和装置
CN103188151A (zh) 一种分组传送网络和在分组传送网络中传输业务的方法
WO2019114544A1 (zh) 一种数据传送的方法、设备和系统
WO2009086774A1 (zh) 数据传输方法、传输装置及传输系统
US8018839B2 (en) Synchronizing packet sequence numbers for line card redundancy
US20240187350A1 (en) Device and method for transferring identification and/or data flow control information between devices
WO2019179161A1 (zh) 一种数据流量处理方法、设备及系统
WO2013107323A1 (zh) 通告链路信息的方法和设备
WO2020083285A1 (zh) 端口配置检测方法、终端和计算机可读存储介质
WO2024045537A1 (zh) 报文传输的方法和网络设备
US8976812B2 (en) Communication apparatus and band control method
CN116156556A (zh) 一种面向电力通道spn网络传送sdh信号方法、装置、spn设备
Yongjun et al. Service Adaptation and Label Forwarding Mechanism for MPLS-TP

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18791648

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019558743

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018791648

Country of ref document: EP

Effective date: 20191108

ENP Entry into the national phase

Ref document number: 20197034789

Country of ref document: KR

Kind code of ref document: A