WO2021109705A1 - 灵活以太网组的管理方法、设备及计算机可读存储介质 - Google Patents

灵活以太网组的管理方法、设备及计算机可读存储介质 Download PDF

Info

Publication number
WO2021109705A1
WO2021109705A1 PCT/CN2020/119066 CN2020119066W WO2021109705A1 WO 2021109705 A1 WO2021109705 A1 WO 2021109705A1 CN 2020119066 W CN2020119066 W CN 2020119066W WO 2021109705 A1 WO2021109705 A1 WO 2021109705A1
Authority
WO
WIPO (PCT)
Prior art keywords
flexible ethernet
network device
group
ethernet group
target
Prior art date
Application number
PCT/CN2020/119066
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 EP20896202.7A priority Critical patent/EP4054124A4/en
Publication of WO2021109705A1 publication Critical patent/WO2021109705A1/zh
Priority to US17/831,158 priority patent/US11838181B2/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
    • 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/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
    • 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/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • 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
    • 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
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13389—LAN, internet

Definitions

  • This application relates to the field of communication technology, and in particular to a method, equipment and computer-readable storage medium for managing a flexible Ethernet group.
  • Ethernet interface Since the current Ethernet interface standards are all fixed rates, in order to meet the demand for higher bandwidth, flexible ethernet (FlexE) technology creates a media access control (MAC) layer and a physical coding sublayer (physical coding).
  • MAC media access control
  • PCS physical coding sublayer
  • the basic function of FlexE technology is to map the service streams of M FlexE clients (clients) to a physical layer (PHY) based on the time division multiplexing (TDM) mechanism of FlexE mezzanine (shim).
  • TDM time division multiplexing
  • shim FlexE mezzanine
  • the embodiments of the present application provide a method, equipment, and computer-readable storage medium for managing a flexible Ethernet group, so as to adjust the flexible Ethernet group without affecting services.
  • a method for managing a flexible Ethernet group is provided.
  • the method is applied to a first network device.
  • the first network device determines the configuration information of a target flexible Ethernet group that needs to be adjusted.
  • the configuration information is synchronized with the second network device to adjust the target flexible Ethernet group.
  • the second network device communicates with the first network device through a physical layer link in the target flexible Ethernet group.
  • the configuration information of the target flexible Ethernet group includes but is not limited to the standby flexible Ethernet group number and the standby flexible Ethernet map of the target flexible Ethernet group, and the standby flexible Ethernet map includes physical layer link information in the target flexible Ethernet group.
  • the lossless dynamic adjustment of the flexible Ethernet group FlexE Group is realized, which can not only avoid affecting services, but can also be used to realize the adjustment of Ethernet groups in various scenarios.
  • the first network device determines the configuration information of the target flexible Ethernet group that needs to be adjusted, including: the first network device and the second network device negotiate the configuration information of the target flexible Ethernet group that needs to be adjusted through an overhead block ,
  • the overhead block carries the configuration information of the target flexible Ethernet group.
  • the reserved bit field field of the overhead block carries configuration information of the target flexible Ethernet group, or the management channel field of the overhead block carries configuration information of the target flexible Ethernet group.
  • the first network device determines the configuration information of the target flexible Ethernet group that needs to be adjusted, including: the first network device receives the flexible target that needs to be adjusted sent by the controller to the first network device and the second network device The configuration information of the Ethernet group.
  • the first network device determines the configuration information of the target flexible Ethernet group that needs to be adjusted, it further includes: when a new physical layer link needs to be added in the target flexible Ethernet group, the standby flexible Ethernet map includes For the new physical layer link information, the first network device determines that the new physical layer link is valid; in response to the new physical layer link being valid, the first network device executes the configuration information based on the target flexible Ethernet group and communicates with the second network The device synchronizes the adjustment operation of the target flexible Ethernet group.
  • the method further includes: when the target physical layer link in the target flexible Ethernet group needs to be deleted, The backup flexible Ethernet graph does not include the target physical layer link information, and the first network device determines that the target flexible Ethernet group after deleting the target physical layer link can support current traffic; in response to deleting the target The target flexible Ethernet group after the physical layer link can support the current traffic.
  • the first network device executes the configuration information based on the target flexible Ethernet group, and performs synchronization of the target flexible Ethernet group with the second network device. Adjustment operation.
  • the method further includes: when the physical layer links in the target flexible Ethernet group need to be regrouped,
  • the standby flexible Ethernet group number includes the network group number of the regrouped flexible Ethernet group, the standby flexible Ethernet graph includes the regrouped physical layer link information, and the first network device determines the regrouped The flexible Ethernet group can support the corresponding service flow; in response to the flexible Ethernet group after the regrouping can support the corresponding service flow, the first network device executes the configuration information based on the target flexible Ethernet group, and the second The network device synchronously performs the adjustment operation of the target flexible Ethernet group.
  • the first network device synchronizes the adjustment of the target flexible Ethernet group with the second network device based on the configuration information of the target flexible Ethernet group, including: the first network device Negotiate an adjustment time with the second network device. When the adjustment time is reached, the first network device synchronizes with the second network device to perform the target flexibility based on the configuration information of the target flexible Ethernet group. Adjustment of the Ethernet group.
  • a method for managing a flexible Ethernet group includes: a second network device determines configuration information of a target flexible Ethernet group that needs to be adjusted, and the configuration information of the target flexible Ethernet group includes all The standby flexible Ethernet group number and the standby flexible Ethernet map of the target flexible Ethernet group, where the standby flexible Ethernet map includes physical layer link information in the target flexible Ethernet group; and the second network device is based on the The configuration information of the target flexible Ethernet group is synchronized with the first network device to adjust the target flexible Ethernet group, and the first network device communicates with the first network device through the physical layer link in the target flexible Ethernet group. 2. Network equipment communication.
  • the second network device determining the configuration information of the target flexible Ethernet group that needs to be adjusted includes: the second network device and the first network device negotiate the target flexible that needs to be adjusted through an overhead block The configuration information of the Ethernet group, where the overhead block carries the configuration information of the target flexible Ethernet group.
  • the reserved bit field of the overhead block carries configuration information of the target flexible Ethernet group, or the management channel field of the overhead block carries configuration information of the target flexible Ethernet group.
  • the second network device determining the configuration information of the target flexible Ethernet group that needs to be adjusted includes: the second network device receives the controller to send the second network device and the first network The configuration information of the target flexible Ethernet group that needs to be adjusted sent by the device.
  • the second network device synchronizes the adjustment of the target flexible Ethernet group with the first network device based on the configuration information of the target flexible Ethernet group, including: the second network device Negotiate an adjustment time with the first network device, and when the adjustment time is reached, the second network device synchronizes with the first network device to perform the target flexibility based on the configuration information of the target flexible Ethernet group Adjustment of the Ethernet group.
  • a device for managing a flexible Ethernet group is provided, the device is applied to a first network device, and the device includes:
  • the determining module is used to determine the configuration information of the target flexible Ethernet group that needs to be adjusted.
  • the configuration information of the target flexible Ethernet group includes the standby flexible Ethernet group number and the standby flexible Ethernet map of the target flexible Ethernet group.
  • the standby flexible Ethernet graph includes physical layer link information in the target flexible Ethernet group;
  • the adjustment module is configured to adjust the target flexible Ethernet group synchronously with a second network device based on the configuration information of the target flexible Ethernet group, and the second network device uses the information in the target flexible Ethernet group
  • the physical layer link communicates with the first network device.
  • the determining module is configured to negotiate with the second network device the configuration information of the target flexible Ethernet group that needs to be adjusted through an overhead block, and the overhead block carries the configuration information of the target flexible Ethernet group. Configuration information.
  • the reserved bit field of the overhead block carries configuration information of the target flexible Ethernet group, or the management channel field of the overhead block carries configuration information of the target flexible Ethernet group.
  • the determining module is configured to receive the configuration information of the target flexible Ethernet group that needs to be adjusted sent by the controller to the first network device and the second network device.
  • the determining module is further configured to, when a new physical layer link is added to the target flexible Ethernet group, the standby flexible Ethernet graph includes the new physical layer link information, Determining that the new physical layer link is valid;
  • the adjustment module is configured to perform an operation of adjusting the target flexible Ethernet group in synchronization with a second network device based on the configuration information of the target flexible Ethernet group in response to the validity of the new physical layer link .
  • the determining module is further configured to: when the target physical layer link in the target flexible Ethernet group needs to be deleted, the standby flexible Ethernet graph does not include the target physical layer link Information, it is determined that the target flexible Ethernet group after deleting the target physical layer link can support current traffic;
  • the adjustment module is configured to, in response to determining that the target flexible Ethernet group after deleting the target physical layer link can support current traffic, execute configuration information based on the target flexible Ethernet group, and perform synchronization with the second network device The adjustment operation of the target flexible Ethernet group.
  • the determining module is further configured to: when the physical layer links in the target flexible Ethernet group are regrouped, the standby flexible Ethernet group number includes the regrouped flexible Ethernet The network group number of the group, the backup flexible Ethernet graph includes the regrouped physical layer link information, and it is determined that the regrouped flexible Ethernet group can support the corresponding service flow;
  • the adjustment module is configured to respond to the regrouped flexible Ethernet group that can support the corresponding service flow, execute the configuration information based on the target flexible Ethernet group, and synchronize the target flexible Ethernet with the second network device. The adjustment operation of the group.
  • the adjustment module is configured to negotiate an adjustment time with the second network device, and when the adjustment time is reached, based on the configuration information of the target flexible Ethernet group, communicate with the second network device.
  • the network device synchronizes the adjustment of the target flexible Ethernet group.
  • a device for managing a flexible Ethernet group is provided, the device is applied to a second network device, and the device includes:
  • the determining module is used to determine the configuration information of the target flexible Ethernet group that needs to be adjusted.
  • the configuration information of the target flexible Ethernet group includes the standby flexible Ethernet group number and the standby flexible Ethernet map of the target flexible Ethernet group.
  • the standby flexible Ethernet graph includes physical layer link information in the target flexible Ethernet group;
  • the adjustment module is configured to adjust the target flexible Ethernet group synchronously with a first network device based on the configuration information of the target flexible Ethernet group, and the first network device uses the configuration information in the target flexible Ethernet group
  • the physical layer link communicates with the second network device.
  • the determining module is configured to negotiate with the first network device the configuration information of the target flexible Ethernet group that needs to be adjusted through an overhead block, and the overhead block carries the configuration information of the target flexible Ethernet group. Configuration information.
  • the reserved bit field of the overhead block carries configuration information of the target flexible Ethernet group, or the management channel field of the overhead block carries configuration information of the target flexible Ethernet group.
  • the determining module is configured to receive configuration information of the target flexible Ethernet group that needs to be adjusted and sent by the controller to the second network device and the first network device.
  • the adjustment module is configured to negotiate an adjustment time with the first network device, and when the adjustment time is reached, based on the configuration information of the target flexible Ethernet group, communicate with the first network device.
  • the network device synchronizes the adjustment of the target flexible Ethernet group.
  • the above-mentioned new physical layer link is valid and meets the following conditions: the new physical layer link is an independent physical layer link, and the new physical layer link is identical to the existing physical layer link in the target flexible Ethernet group.
  • the layer link has no conflict, and the phases of the new physical layer link and the existing physical layer link in the target flexible Ethernet group can be aligned.
  • a network device comprising: a memory and a processor, and a computer program or at least one instruction is stored in the memory, and the computer program or at least one instruction is loaded and executed by the processor to realize the foregoing The method of any one of the first aspect.
  • a network device comprising: a memory and a processor, and a computer program or at least one instruction is stored in the memory, and the computer program or at least one instruction is loaded and executed by the processor to realize the foregoing The method of any one of the second aspect.
  • a management system for a flexible Ethernet group is also provided.
  • the system includes a first network device and a second network device.
  • the first network device is used to execute the method described in any one of the first aspects.
  • the second network device is used to execute any of the methods in the second aspect.
  • a computer-readable storage medium stores a computer program or at least one instruction, and the computer program or instruction is loaded and executed by a processor to implement any of the above-mentioned methods.
  • Another communication device which includes a transceiver, a memory, and a processor.
  • the transceiver, the memory, and the processor communicate with each other through an internal connection path, the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory to control the transceiver to receive signals and control the transceiver to send signals , And when the processor executes the instructions stored in the memory, the processor is caused to execute the method in any one of the foregoing possible implementation manners.
  • processors there are one or more processors, and one or more memories.
  • the memory may be integrated with the processor, or the memory and the processor may be provided separately.
  • the memory may be a non-transitory (non-transitory) memory, such as a read only memory (ROM), which may be integrated with the processor on the same chip, or may be set in different On the chip, the embodiment of the present application does not limit the type of the memory and the setting mode of the memory and the processor.
  • ROM read only memory
  • a computer program (product) is provided, the computer program (product) includes: computer program code, when the computer program code is run by a computer, the computer executes the methods in the above aspects.
  • a chip including a processor, configured to call and execute instructions stored in the memory from a memory, so that a communication device installed with the chip executes the methods in the foregoing aspects.
  • Another chip including: an input interface, an output interface, a processor, and a memory.
  • the input interface, output interface, the processor, and the memory are connected through an internal connection path, and the processor is used to execute all The code in the memory, when the code is executed, the processor is used to execute the methods in the foregoing aspects.
  • FIG. 1 is a schematic diagram of the structure of the FlexE Group provided by an embodiment of the application.
  • FIG. 2 is a schematic diagram of the data structure of a PHY link provided by an embodiment of the application
  • FIG. 3 is a schematic diagram of the structure of an overhead frame and an overhead multiframe provided by an embodiment of the application;
  • FIG. 4 is a schematic diagram of the structure of an overhead frame and an overhead multiframe provided by an embodiment of the application;
  • FIG. 5 is a flowchart of a method for managing a flexible Ethernet group provided by an embodiment of the application
  • FIG. 6 is a schematic diagram of the structure of an overhead frame and an overhead multiframe provided by an embodiment of the application.
  • FIG. 7 is a schematic diagram of the structure of an overhead frame and an overhead multiframe provided by an embodiment of the application.
  • FIG. 8 is a schematic diagram of the structure of an overhead frame and an overhead multiframe provided by an embodiment of the application.
  • FIG. 9 is a schematic diagram of the structure of an overhead frame and an overhead multiframe provided by an embodiment of the application.
  • FIG. 10 is a schematic structural diagram of a flexible Ethernet group management system provided by an embodiment of the application.
  • FIG. 11 is a flowchart of a method for managing a flexible Ethernet group provided by an embodiment of the application.
  • FIG. 12 is a schematic structural diagram of a flexible Ethernet group management system provided by an embodiment of the application.
  • FIG. 13 is a flowchart of a method for managing a flexible Ethernet group provided by an embodiment of the application.
  • FIG. 14 is a schematic structural diagram of a management system for a flexible Ethernet group provided by an embodiment of the application.
  • FIG. 15 is a flowchart of a method for managing a flexible Ethernet group provided by an embodiment of the application.
  • FIG. 16 is a flowchart of a method for managing a flexible Ethernet group provided by an embodiment of the application.
  • FIG. 17 is a schematic structural diagram of a flexible Ethernet group management system provided by an embodiment of the application.
  • FIG. 18 is a schematic structural diagram of a management device for a flexible Ethernet group provided by an embodiment of the application.
  • FIG. 19 is a schematic structural diagram of a management device for a flexible Ethernet group provided by an embodiment of the application.
  • FIG. 20 is a schematic structural diagram of a management device for a flexible Ethernet group provided by an embodiment of the application.
  • Ethernet interface standard formulation and product development are stepwise, the current Ethernet interface standards are all at a fixed rate, so there will be a gap between the transmission requirements and the actual device interface capabilities. It is often necessary to resolve the current Ethernet interface rate level.
  • OIF Optical Internet Forum
  • FlexE creates an adaptation layer between MAC and PCS, which enables the Ethernet interface rate to flexibly match a variety of business scenarios, and is used in higher bandwidth network processors.
  • the basic function of FlexE is to map the service streams of M FlexE clients to a flexible Ethernet group FlexE Group composed of N physical layer PHY links according to FlexE Shim's time division multiplexing (TDM) mechanism.
  • M and N are both positive integers, and the basic structure of FlexE can be shown in Figure 1.
  • M is 6, N is 4, that is, the FlexE shown in Figure 1 maps the service flows of 6 FlexE clients to a FlexE Group consisting of 4 PHY links according to the FlexE Shim TDM mechanism.
  • each 100G PHY corresponds to 20 time slots corresponding to 64B/66B code blocks, and each code block corresponds to a payload of 5Gbps rate. Rate (payload rate).
  • the current FlexE standard supports FlexE on 100GE, 200GE, 400GE, and 50GE interfaces.
  • the format of a piece of 100GE PHY data is shown in Figure 2.
  • each block is a 64B/66B block encoded according to IEEE 802.3 Clause 82. Every 20 blocks form a time slot table (calendar), and each block is one of the TDM mapping mechanisms. Time slot. After each calendar is repeated 1023 times, a 64B/66B encoded overhead block is inserted.
  • Every 8 overhead blocks form an overhead frame
  • every 32 overhead frames form an overhead multiframe.
  • the entire FlexE traffic time slot mapping (client-slot mapping) and various management are completed in an overhead multiframe.
  • the formats of the overhead frame and the overhead multiframe are shown in Figure 3 or Figure 4.
  • the FlexE overhead (overhead, OH) includes the time slot table configuration information of all FlexE Clients in the FlexE group.
  • OH the FlexE overhead
  • Two time slot tables are used: Calendar A and Calendar B. These two time slot tables have the following characteristics:
  • Feature 1 Only one time slot table is working at any time, that is, at any time, either Calendar A is working or Calendar B is working.
  • Feature 2 At the transmitter (TX) and receiver (RX) ends of the FlexE group, there will be a FlexE OH overhead time slot negotiation mechanism to ensure that the working time slot tables of TX and RX are consistent.
  • Calendar A is in the working state, then Calendar B is in the standby state of the corresponding time slot configuration.
  • TX time slot negotiation
  • RX Recommendation unit
  • CSR time slot negotiation request
  • TX receives the response from RX
  • TX triggers both TX and RX to switch the work table to Calendar B.
  • Figure 3 or Figure 4 also includes the following information:
  • the overhead multiframe indicator (OMFI) is called OMF in standards such as IA OIF-FLEXE-01.0/01.1/02.2/02.1: it is used to indicate the boundary of the multiframe.
  • the bit field numbered 9 in the first block of the overhead frame as shown in Figure 3 or Figure 4 carries the OMF. Among them, in a multi-frame, the OMF value of the first 16 single frames is 0, and the OMF value of the next 16 single frames is 1, and the boundary of the multi-frame can be determined by the conversion between 0 and 1.
  • RPF Remote PHY fault
  • Synchronization control (synchronization control, SC): used for synchronization control.
  • SC Synchronization control.
  • the bit field numbered 11 in the first block of the overhead frame shown in FIG. 3 or FIG. 4 carries the SC.
  • Flexible Ethernet Map Used to control which FlexE instances are members of this group (Control of which Flexe Instances are members of this group).
  • the bit fields numbered 1 to 8 in the second block of the overhead frame as shown in FIG. 3 or FIG. 4 carry the FlexE Map.
  • the FlexE Map includes the physical layer link information in the FlexE Group.
  • Each bit of the FlexE Map corresponds to a physical layer link, and the value of each bit of the FlexE Map is used to indicate the physical layer corresponding to the bit. Whether the layer link is in the FlexE Group. For example, if the value of the bit is the first value, for example, the first value is 1, then the physical layer link corresponding to the bit is considered to be in the FlexEGroup. If the value of the bit is the second value, for example, the second value is 0, it is considered that the physical layer link corresponding to the bit is not in the FlexEGroup.
  • Flexible Ethernet instance number (FlexE instance Number): Represents the identity of this Flexe instance within the group (Identity of this Flexe Instance within the group).
  • the bit field numbered from 9 to 16 in the second block of the overhead frame as shown in FIG. 3 or FIG. 4 carries the FlexE instance Number.
  • Flexible Ethernet Group Number Used to identify a flexible Ethernet group.
  • the bit fields numbered 12 to 31 in the first block of the overhead frame shown in FIG. 3 or FIG. 4 carry the FlexE Group Number.
  • Time slot table switch acknowledgement (calendar switch acknowledgement, CSA): It is called CA in the implementation agreement (implementation agreements, IA) OIF-FLEXE-01.0/01.1/02.2/02.1 and other standards, where 01.0/01.1/02.2/02.1 is Several versions of the IA OIF-FLEXE standard.
  • the bit field numbered 34 in the third block of the overhead frame shown in FIG. 3 or FIG. 4 carries the CA.
  • Time slot table switch request (calendar switch request, CSR): It is called CR in standards such as IA OIF-FLEXE-01.0/01.1/02.2/02.1.
  • the bit field numbered 33 in the third block of the overhead frame shown in FIG. 3 or FIG. 4 carries the CR.
  • Synchronization head (SH): the frame header of the overhead frame as shown in FIG. 3 or FIG. 4.
  • S valid sync header bits: the fields under SH in the fourth block to the eighth block of the overhead frame as shown in FIG. 3 or FIG. 4 carry the S.
  • Management Channel (Management Channel): The fourth block to the eighth block of the overhead frame as shown in FIG. 3 or FIG. 4 carries the management channel.
  • CRC-16 used to perform cyclic redundancy check (CRC) protection on the content of the overhead block.
  • CRC cyclic redundancy check
  • FIG. 3 or FIG. 4 also includes a reserved (reserved) field.
  • a bit field numbered from 17 to 63 is included in the second block of the overhead frame shown in FIG. 3 or FIG. 4.
  • the bit fields numbered 35 to 47 in the third block are reserved fields.
  • the user can change the number of PHYs in the FlexE Group according to the traffic size and number of each FlexE Client for the current network. For example: when the bandwidth provided by the PHY in the FlexE Group is insufficient, one or more PHYs need to be added to the current FlexE Group to support more service streams; or there is a large amount of idle bandwidth in the current FlexE Group, and one or more of them can be removed. One PHY releases network resources for use by other services; or, in the current FlexE Group, there is a need to split the current FlexE Group into two or more to adapt to the current business model.
  • the embodiment of the present application provides a flexible Ethernet group management method, which provides a lossless dynamic FlexE group adjustment management method, so as to achieve adjustments in various scenarios without affecting services. .
  • the method provided by the embodiment of the present application includes the following processes.
  • the first network device determines the configuration information of the target flexible Ethernet group that needs to be adjusted.
  • the configuration information of the target flexible Ethernet group includes the standby flexible Ethernet group number of the target flexible Ethernet group and the standby flexible Ethernet map, and the standby flexible
  • the Ethernet graph includes the physical layer link information in the target flexible Ethernet group.
  • the first network device determines the configuration information of the target flexible Ethernet group that needs to be adjusted, including but not limited to the following two ways:
  • Method 1 The first network device determines the configuration information of the target flexible Ethernet group that needs to be adjusted, including: the first network device and the second network device negotiate the configuration information of the target flexible Ethernet group that needs to be adjusted through the cost block, and the cost block carries The configuration information of the target flexible Ethernet group.
  • the reserved bit field of the overhead block carries the configuration information of the target flexible Ethernet group.
  • the Bak in FlexE Group Number Bak, FlexE Map Bak and FlexE Instance Number Bak is the abbreviation of Backup, which stands for backup.
  • bit field numbered 36 in the third block of the overhead frame shown in Figure 6 or Figure 7 carries GR
  • bit field numbered 37 in the third block of the overhead frame shown in Figure 6 or Figure 7 The bit field carries GA.
  • the embodiment of the present application also provides another way to carry the above information.
  • this way may be as shown in FIG. 8 or FIG. 9. Only 1 bit of FlexE Group Number Bak is transmitted in each overhead frame, as shown in the FB in Figure 8 or Figure 9, this FB represents 1 bit of FlexE Group Number Bak, and all bit fields of FlexE Group Number Bak are transmitted through multi-frames; example sexually, it is also possible to transmit only 1 bit of FlexE Instance Number Bak in each overhead frame, which may occupy only 1 bit in the overhead frame, and transmit all bit fields of FlexE Instance Number Bak through a multi-frame.
  • the embodiment of the present application does not limit the number of bits transmitted in each frame (for example, FlexE Group Number Bak can be transmitted in 4 bits, 5 bits, etc. per frame).
  • the configuration information of the target flexible Ethernet group can also be carried through the management channel field of the overhead block.
  • the management channel may be shown in blocks 4 to 8 in the FlexE overhead.
  • the method provided by the embodiment of the present application supports the first network device and the second network device to negotiate through the management channel to determine the configuration information of the target flexible Ethernet group.
  • the management channel can carry multiple protocols. Therefore, taking the Ethernet packet carried by the management channel as an example, the configuration information of the target flexible Ethernet group can be negotiated through the Ethernet packet. It should be noted that, since the management channel occupies 4 blocks of space in the FlexE overhead, this embodiment of the present application does not limit which fields of the management channel are used to negotiate the configuration information of the target flexible Ethernet group.
  • the protocol that the management channel can carry is a link layer discovery protocol (link layer discovery protocol, LLDP) or a precision time protocol (precision time protocol, PTP).
  • the first network device determines the configuration information of the target flexible Ethernet group that needs to be adjusted, including: the first network device receives the information of the target flexible Ethernet group that needs to be adjusted sent from the controller to the first network device and the second network device Configuration information.
  • a software defined network (software defined network, SDN) controller communicates with the management interfaces of the first network device and the second network device respectively, and then sends out the configuration information of the target flexible Ethernet that needs to be adjusted. .
  • SDN software defined network
  • the first network device determines the configuration information of the target flexible Ethernet group that needs to be adjusted, and adjusts the target flexible Ethernet group according to different adjustment situations.
  • the first network device determines the configuration information of the target flexible Ethernet group that needs to be adjusted, and adjusts the target flexible Ethernet group according to different adjustment situations.
  • three processing methods including but not limited to one or more of the following three processing methods:
  • Processing method 1 When a new physical layer link needs to be added in the target flexible Ethernet group, the standby flexible Ethernet graph includes the new physical layer link information, and the first network device determines whether the new physical layer link is valid;
  • the first network device In response to determining that the new physical layer link is valid, performs an operation of adjusting the target flexible Ethernet group in synchronization with the second network device based on the configuration information of the target flexible Ethernet group.
  • the new physical layer link is a physical layer link that was not included in the target flexible Ethernet group before.
  • the method of determining whether the new physical layer link is valid is not limited in the embodiment of the present application. If the new physical layer link is valid, including but not limited to, the following conditions must be met:
  • the new physical layer link is an independent physical layer link and not in other flexible Ethernet groups.
  • Condition 2 The new physical layer link does not conflict with the existing physical layer link in the target flexible Ethernet group.
  • Condition 3 The phase of the new physical layer link and the existing physical layer link in the target flexible Ethernet group can be aligned.
  • determining whether the new physical layer link is an independent physical layer link includes, but is not limited to, determining whether the Group Number of the new physical layer link is valid. If the Group Number of the new physical layer link is valid, it means that the new physical layer link is in another group and is not an independent physical layer link. If the Group Number of the new physical layer link is invalid, for example, the Group Number is all 0 or all f, it is considered that the new physical layer link is not in another Group, but is an independent physical layer link. In this case, if the new physical layer link wants to join the target flexible Ethernet group, it needs to be separated from the previous flexible Ethernet group, and then the new physical layer link meets other conditions Will be added to the target flexible Ethernet group.
  • the new physical layer link conflicts with the existing physical layer link in the target flexible Ethernet group, including but not limited to judging the new physical layer link Whether the FlexE Instance Number is the same as the FlexE Instance Number of the existing physical layer links in the target flexible Ethernet group. If the FlexE Instance Number of any physical layer link in the existing physical layer links in the target flexible Ethernet group is the same as the FlexE Instance Number of the new physical layer link, it is considered that there is a conflict. If the FlexE Instance Number of any physical layer link in the existing physical layer links in the target flexible Ethernet group is inconsistent with the FlexE Instance Number of the new physical layer link, it is considered that there is no conflict.
  • the FlexE instance number of at least one physical layer link of the conflicting physical layer link and the new physical layer link needs to be changed so that there is no conflict. After that, the new physical layer link will be added to the target flexible Ethernet group only when other conditions are met.
  • the phases of the new physical layer link and the existing physical layer link in the target flexible Ethernet group can be aligned, including but not limited to judging the new physical layer Whether the interval between the frame header of the overhead multiframe of the link and the frame header of the overhead multiframe of each existing physical layer link in the target flexible Ethernet group is within the reference range. If the interval between the header of the overhead multiframe of the new physical layer link and the header of the overhead multiframe of each existing physical layer link in the target flexible Ethernet group is within the reference range, then the new physical layer The phase of the link and the existing physical layer link in the target flexible Ethernet group can be aligned.
  • the new physical layer The phase of the link and the existing physical layer link in the target flexible Ethernet group cannot be aligned. For example, taking the reference range of +/-13us as an example, if the frame header of the overhead multiframe of the new physical layer link and the frame of the overhead multiframe of each existing physical layer link in the target flexible Ethernet group If the interval between the headers is within the reference range of +/-13us, the new physical layer link can be aligned with the phase of the existing physical layer link in the target flexible Ethernet group.
  • the new physical layer link meets the above conditions, it can be added to the target flexible Ethernet group. If the new physical layer link does not meet any of the above conditions, an alarm can be initiated to remind the user that the target cannot be completed. Adjustment of the Ethernet group.
  • Processing method 2 When the target physical layer link in the target flexible Ethernet group needs to be deleted, the standby flexible Ethernet graph does not include the target physical layer link information, and the first network device determines the target flexibility after deleting the target physical layer link Whether the Ethernet group can support the current traffic;
  • the target flexible Ethernet group can support the current traffic
  • the first network device executes the configuration information based on the target flexible Ethernet group, and synchronizes the adjustment of the target flexible Ethernet group with the second network device.
  • the target flexible Ethernet group after deleting the target physical layer link can support current traffic means that the total bandwidth of the remaining physical layer links in the target flexible Ethernet group after deleting the target physical layer link is not less than the target The bandwidth required by the service flow currently carried by the flexible Ethernet group.
  • the method provided in this embodiment of the application deletes the target physical layer link in the target flexible Ethernet group. , First determine whether the target flexible Ethernet group after deleting the target physical layer link can support the current traffic.
  • the first network device determines whether the target flexible Ethernet group after deleting the target physical layer link can support current traffic, including but not limited to determining whether the target flexible Ethernet group after deleting the target physical layer link, the remaining physical Whether the total bandwidth of the layer link is less than the bandwidth required by the service flow currently carried by the target flexible Ethernet group. If the total bandwidth of the remaining physical layer links in the target flexible Ethernet group after the target physical layer link is deleted is not less than the bandwidth required by the service flow that the target flexible Ethernet group should currently carry, then the target physical layer link can be determined to be deleted The target flexible Ethernet group behind the layer link can support current traffic.
  • the target flexible Ethernet group after the target physical layer link is deleted if in the target flexible Ethernet group after the target physical layer link is deleted, the total bandwidth of the remaining physical layer links is less than the bandwidth required by the service flow currently carried by the target flexible Ethernet group, It is determined that the target flexible Ethernet group after deleting the target physical layer link cannot support the current traffic. In this case, an alarm can be raised to inform the user that the adjustment operation will affect the service flow.
  • the target flexible Ethernet group including 5 physical layer links
  • the target flexible Ethernet when one of the physical layer links needs to be deleted, if the total bandwidth of the remaining 4 physical layer links is 100G, and the target flexible Ethernet The bandwidth required for the service flow currently carried by the net group is 90G, and it can be determined that the target flexible Ethernet group after deleting the target physical layer link can support the current traffic.
  • the standby flexible Ethernet group number includes the network group number of the regrouped flexible Ethernet group, and the standby flexible Ethernet map includes the regrouped
  • the first network device determines whether the regrouped flexible Ethernet group can support the corresponding service flow
  • the first network device executes the configuration information based on the target flexible Ethernet group, and synchronizes with the second network device to perform the adjustment operation of the target flexible Ethernet group.
  • the target flexible Ethernet group carries the service flow, if the target flexible Ethernet group is divided, it is necessary to ensure that the divided flexible Ethernet group can still carry the corresponding service flow, so that the service flow is not affected. Split the flexible Ethernet group. Therefore, when the method provided in the embodiment of the present application regroups the physical layer links in the target flexible Ethernet group, it is first determined whether the regrouped flexible Ethernet group can support the corresponding service flow.
  • determining whether the regrouped flexible Ethernet group can support the corresponding service flow including but not limited to determining whether the total bandwidth of the physical layer links in the regrouped flexible Ethernet group is less than the corresponding service flow The required bandwidth. If the total bandwidth of the physical layer links in the regrouped flexible Ethernet group is not less than the bandwidth required to carry the corresponding service flow, it can be determined that the regrouped flexible Ethernet group can support the corresponding service flow.
  • the total bandwidth of the physical layer links in the target flexible Ethernet group before regrouping is 4x100G, a total of 400G, the target flexible Ethernet group is regrouped to obtain two regrouped flexible Ethernet groups, referred to as The first group and the second group.
  • the total bandwidth of the physical layer links in the first group and the second group are both 200G.
  • the target flexible Ethernet group bears three service flows, they are the first service flow of 200G, the second service flow of 150G, and the third service flow of 50G.
  • the first service flow is allocated to the first group, and the second service flow and the third service flow are allocated to the second group.
  • the service flow corresponding to the first packet is the first service flow of 200G
  • the regrouped flexible Ethernet group if the total bandwidth of the physical layer links in the regrouped flexible Ethernet group is less than the bandwidth required to carry the corresponding service flow, it can be determined that the regrouped flexible Ethernet group cannot support the corresponding Business flow. In this case, an alarm can be raised to inform the user that the segmentation operation will affect the business flow.
  • the target flexible Ethernet group before regrouping is 4x100G, a total of 400G
  • the target flexible Ethernet group is regrouped to obtain two regrouped flexible Ethernet groups. Referred to as the first group and the second group.
  • the total bandwidth of the physical layer links in the first group and the second group are both 200G.
  • the target flexible Ethernet group bears three service flows, they are the first service flow of 250G, the second service flow of 125G, and the third service flow of 50G.
  • the first service flow is allocated to the first group, and the second service flow and the third service flow are allocated to the second group.
  • the service flow corresponding to the first packet is the first service flow of 260G
  • the service flow corresponding to the second packet is the second service flow of 125G + the third service flow of 50G.
  • the second packet can support the corresponding second service stream and The third business flow.
  • the target flexible Ethernet group is not regrouped.
  • the service flow corresponding to the regrouped flexible Ethernet group can be randomly allocated, or the service flow size and the total bandwidth of the physical layer link of the regrouped flexible Ethernet group can be used to determine the flexible Ethernet group after each regrouping.
  • the service flow corresponding to the Ethernet group For example, preferentially allocate larger service flows into the regrouped flexible Ethernet group with a larger total bandwidth.
  • Other allocation methods may also be used, and the embodiment of the present application does not limit the manner of how to determine the service flow corresponding to the regrouped flexible Ethernet group.
  • the net group number of the regrouped flexible Ethernet group there can be one net group number that is the same as the net group number of the target flexible Ethernet group before regrouping, and the rest of the regrouped flexible Ethernet group The net group number of is different from the net group number of the target flexible Ethernet group before regrouping. Or, the net group numbers of all flexible Ethernet groups after the regrouping may be different from the net group numbers of the target flexible Ethernet group before the regrouping.
  • the first network device synchronizes the adjustment of the target flexible Ethernet group with the second network device based on the configuration information of the target flexible Ethernet group, and the second network device communicates with the physical layer link in the target flexible Ethernet group.
  • the first network device communicates.
  • the first network device and the second network device are adjusted synchronously, so that the service flow may not be affected.
  • the configuration information of the target flexible Ethernet group includes the standby flexible Ethernet group number of the target flexible Ethernet group and the standby flexible Ethernet map
  • the standby flexible Ethernet map includes the physical layer link information in the target flexible Ethernet group Therefore, when the first network device adjusts the target flexible Ethernet group synchronously with the second network device based on the configuration information of the target flexible Ethernet group, the network group number of the target flexible Ethernet group can be switched to the standby flexible Ethernet group. Ethernet group number, switch the flexible Ethernet graph of the target flexible Ethernet group to the standby flexible Ethernet graph.
  • the first network device synchronizes the adjustment of the target flexible Ethernet group with the second network device based on the configuration information of the target flexible Ethernet group, including:
  • the first network device and the second network device negotiate an adjustment time.
  • the first network device synchronizes the adjustment of the target flexible Ethernet group with the second network device based on the configuration information of the target flexible Ethernet group.
  • the second network device when the second network device performs the flexible Ethernet group management method, it can refer to the above-mentioned first network device management method, which will not be repeated here.
  • the first network device is called Device 1
  • the second network device is called Device 2.
  • Device 1 initiates a FlexE Group change, adding PHY#C to PHY#A and PHY# FlexE Group where B is located.
  • the current FlexE Group Number value corresponding to this Group is X. It will be directly referred to as FlexE Group X in the future.
  • the verification step of PHY#C to determine the PHY #C can be added to FlexE Group X as a valid PHY.
  • the verification process includes but is not limited to: judging whether PHY#C is an independent PHY or in another FlexE Group. If you are in another FlexE Group, you need to leave the other FlexE Group first, and the method of leaving the other FlexE Group is detailed in the embodiment shown in FIG. 13 below, and will not be repeated here.
  • Device 2 copies FlexE Group Number to FlexE Group Number Bak, FlexE Map to FlexE Map Bak, and FlexE Instance Number to FlexE Instance Number Bak.
  • GR/GA/G switches back to 0 to ensure that each time the FlexE Group is adjusted, the initial state is the default state. In other words, GR/GA/G are consistent during normal operation, and only when the FlexE Group is adjusted will there be a difference.
  • the first network device is called device 1
  • the second network device is called device 2
  • the Group change is initiated with device 1, from PHY#A, PHY#B, PHY#C
  • the removal of PHY#C is taken as an example to illustrate the flexible Ethernet group management method provided in the embodiment of the present application.
  • FlexE Group adjustment will be performed, as shown in Figure 13.
  • change the FlexE Group Number to Z, Z! Y, that is, Z is not equal to Y.
  • the first step: GR 1, device 1 modifies the FlexE Group Number Bak of PHY#C, and refreshes the FlexE Map Bak in PHY#A and PHY#B to delete the information of PHY#C from the FlexE Map Bak.
  • the FlexE Map Bak in PHY#C is refreshed, and the FlexE Map Bak in PHY#C only includes PHY#C itself after refreshing, and the FlexE Instance Number Bak of the corresponding PHY#C does not need to be changed.
  • the third step: G 1, starting from the next multi-frame header, device 1 and device 2 form FlexE Group X according to PHY#A/B to deliver the FlexE Clients service flow. And PHY#C becomes FlexE Group Y independently.
  • Step 4 Device 2 copies the FlexE Group Number to FlexE Group Number Bak, and the FlexE Map to FlexE Map Bak.
  • GR/GA/G switches back to 0 to ensure that each time the FlexE Group is adjusted, the initial state starts in the same state. In other words, GR/GA/G are consistent during normal operation, and only when the FlexE Group is adjusted will there be a difference.
  • the FlexE Instance Number in each PHY does not need to be changed, but it can also be modified as needed, which is not limited in the embodiment of the present application.
  • the first network device is called Device 1
  • the second network device is called Device 2.
  • Device 1 initiates a FlexE Group change, and sets PHY#A, PHY#B, PHY#C, FlexE Group X composed of PHY#D is divided into FlexE Group Y composed of PHY#A and PHY#B, and FlexE Group Z composed of PHY#C and PHY#D.
  • the split operation and the delete PHY operation are similar.
  • the first step: GR 1, device 1 modifies the FlexE Group Number Bak of PHY#A/B/C, the FlexE Group Number Bak of PHY#A/B uses Y, and the FlexE Group Number Bak of PHY#C/D uses Z.
  • PHY#A/B is divided into a FlexE Group
  • PHY#C/D is divided into a FlexE Group.
  • the FlexE Map Bak in the PHY#A/B/C/D is refreshed.
  • the FlexE Map Bak of PHY#A/B includes the information of PHY#A/B
  • the FlexE Map Bak of PHY#C/D includes PHY. #C/D information.
  • the Instance Number Bak in PHY#A/B/C/D does not need to be changed.
  • the fourth step Group Number in PHY#A/B/C/D duplicates FlexE Group Number Bak, and FlexE Map duplicates FlexE Map Bak.
  • GR/GA/G switches back to 0 to ensure that each time the FlexE Group is adjusted, the initial state starts with the Group Number in Block#1. In other words, GR/GA/G are consistent during normal operation, and only when the FlexE Group is adjusted will there be a difference.
  • the configuration information of the FlexE Group that needs to be adjusted can also be negotiated between management channels.
  • the management channel can carry multiple protocols. Take Ethernet packets through the management channel and negotiate FlexE Group configuration information through the Ethernet packets as an example:
  • the management channel is used to carry the configuration information of the target flexible Ethernet group that needs to be adjusted.
  • the 3-bit GGG as shown in FIG. 6 or FIG. 7 may not be required to indicate whether to switch, but this embodiment of the application does not limit this. Exclude the use of the 3bitGGG program.
  • the process of negotiating configuration information in this embodiment is shown in Fig. 16, including but not limited to the following steps:
  • the first step the TX in the FlexE Group sends a Request message to the RX to send the standby FlexE Group Number and the new FlexE Map information through the Request message.
  • TX and RX agree on the handover time, that is, agree to adjust the time of the FlexE Group synchronously.
  • the third step Device 1 sends a Request_follow_up message to device 2 to notify the peer when to switch, that is, when to adjust the FlexE Group that needs to be adjusted.
  • the fourth step switch the multi-frame header after the appointed time arrives.
  • the agreed time switching point needs to be bounded by a certain overhead frame header or overhead multiframe header. If the time point does not correspond to the boundary, it needs to be postponed to the next boundary.
  • the adjustments to the FlexE Group involved in Figure 16 include, but are not limited to, adding physical layer links to the target flexible Ethernet group that needs to be adjusted, and existing physical layer links in the target flexible Ethernet group that need to be adjusted.
  • One or more of the adjustment methods such as deleting and dividing the target flexible Ethernet group that needs to be adjusted. For each adjustment method, refer to the above-mentioned corresponding embodiment.
  • the embodiment of this application adopts the management channel to negotiate the target flexible Ethernet.
  • the adjustment process in the mode of the configuration information of the net group is not limited.
  • the advantage of this solution is that there is no need to use the reserved bit fields in the overhead.
  • the bandwidth resource of the management channel is more abundant than the reserved bit field of the overhead block.
  • the method provided in the embodiments of the present application also supports the use of the Management System/SDN controller to configure both ends for synchronous switching.
  • the first network device as device 1
  • the second network device as device 2
  • it contacts the management interfaces of device 1 and device 2 respectively, and delivers the FlexE Group information that needs to be adapted, that is, through the upper-layer controller to Device 1 and Device 2 deliver the configuration information of the target flexible Ethernet that needs to be adjusted.
  • the configuration information including but not limited to the new FlexE Group Number, FlexE Map, etc. as examples, the method provided in the embodiment of the present application will be described as an example.
  • this solution can be used in combination with the embodiments shown in FIG. 11, FIG. 13, FIG. 15, and FIG. 16.
  • the SDN controller delivers the configuration and confirms the success, it causes both ends to perform G-bit switching at the same time, that is, device 1 and device 2 perform Group adjustment simultaneously.
  • the switching can be performed by sending a switching timestamp.
  • the solution shown in FIG. 17 implements flexible Ethernet group management in combination with the embodiment shown in FIG. 11, FIG. 13 or FIG. 15, or implements flexible Ethernet group management in combination with the embodiment shown in FIG.
  • the solution shown can also be used alone, and an alarm mechanism that overrides the two devices can be used for forced switching.
  • a flexible Ethernet group management device which is applied to a first network device, and the device includes:
  • the determining module 1501 is used to determine the configuration information of the target flexible Ethernet group that needs to be adjusted.
  • the configuration information of the target flexible Ethernet group includes the standby flexible Ethernet group number of the target flexible Ethernet group and the standby flexible Ethernet map, and the standby flexible Ethernet map Including the physical layer link information in the target flexible Ethernet group;
  • the adjustment module 1502 is used to adjust the target flexible Ethernet group synchronously with the second network device based on the configuration information of the target flexible Ethernet group.
  • the second network device communicates with the first network device through the physical layer link in the target flexible Ethernet group. Network equipment communication.
  • the determining module 1501 is configured to negotiate the configuration information of the target flexible Ethernet group to be adjusted with the second network device through an overhead block, and the overhead block carries the configuration information of the target flexible Ethernet group.
  • the reserved bit field field of the overhead block carries configuration information of the target flexible Ethernet group, or the management channel field of the overhead block carries configuration information of the target flexible Ethernet group.
  • the determining module 1501 is configured to receive the configuration information of the target flexible Ethernet group that needs to be adjusted sent by the controller to the first network device and the second network device.
  • the determining module 1501 is also used for when a new physical layer link needs to be added in the target flexible Ethernet group, the standby flexible Ethernet graph includes the new physical layer link information to determine the new physical layer link. Link is valid;
  • the adjustment module 1502 is configured to perform an operation of adjusting the target flexible Ethernet group in synchronization with the second network device based on the configuration information of the target flexible Ethernet group in response to the validity of the new physical layer link.
  • the new physical layer link is valid and meets the following conditions: the new physical layer link is an independent physical layer link, and the new physical layer link is the same as the existing physical layer link in the target flexible Ethernet group. There is no conflict between the layer links, and the phases of the new physical layer link and the existing physical layer link in the target flexible Ethernet group can be aligned.
  • the determining module 1501 is also used to determine to delete the target physical layer link when the target physical layer link in the target flexible Ethernet group needs to be deleted, and the standby flexible Ethernet graph does not include the target physical layer link information
  • the target flexible Ethernet group behind the link can support current traffic;
  • the adjustment module 1502 is configured to respond to the target flexible Ethernet group after deleting the target physical layer link that can support current traffic, execute configuration information based on the target flexible Ethernet group, and synchronize the target flexible Ethernet group with the second network device. Adjustment operation.
  • the determining module 1501 is also used for when the physical layer links in the target flexible Ethernet group need to be regrouped, the standby flexible Ethernet group number includes the net group of the regrouped flexible Ethernet group No., the standby flexible Ethernet graph includes the physical layer link information after regrouping, and it is determined that the regrouped flexible Ethernet group can support the corresponding service flow;
  • the adjustment module 1502 is configured to respond to the regrouped flexible Ethernet group that can support the corresponding service flow, execute the configuration information based on the target flexible Ethernet group, and synchronize the adjustment operation of the target flexible Ethernet group with the second network device .
  • the adjustment module 1502 is used to negotiate an adjustment time with the second network device, and when the adjustment time is reached, based on the configuration information of the target flexible Ethernet group, synchronize the target flexible Ethernet group with the second network device. Adjustment.
  • a flexible Ethernet group management device which is applied to a second network device, and the device includes:
  • the determining module 1601 is used to determine the configuration information of the target flexible Ethernet group that needs to be adjusted.
  • the configuration information of the target flexible Ethernet group includes the standby flexible Ethernet group number of the target flexible Ethernet group and the standby flexible Ethernet map, and the standby flexible Ethernet map Including the physical layer link information in the target flexible Ethernet group;
  • the adjustment module 1602 is used to adjust the target flexible Ethernet group synchronously with the first network device based on the configuration information of the target flexible Ethernet group.
  • the first network device communicates with the second network device through the physical layer link in the target flexible Ethernet group. Network equipment communication.
  • the determining module 1601 is configured to negotiate with the first network device the configuration information of the target flexible Ethernet group to be adjusted through an overhead block, and the overhead block carries the configuration information of the target flexible Ethernet group.
  • the reserved bit field field of the overhead block carries configuration information of the target flexible Ethernet group, or the management channel field of the overhead block carries configuration information of the target flexible Ethernet group.
  • the determining module 1601 is configured to receive the configuration information of the target flexible Ethernet group that needs to be adjusted sent by the controller to the second network device and the first network device.
  • the adjustment module 1602 is used to negotiate the adjustment time with the first network device, and when the adjustment time is reached, based on the configuration information of the target flexible Ethernet group, synchronize the target flexible Ethernet group with the first network device. Adjustment.
  • an embodiment of the present application further provides a management device 1000 for a flexible Ethernet group.
  • the management device 1000 for a flexible Ethernet group shown in FIG. 20 is used to perform operations involved in the above-mentioned flexible Ethernet group management method.
  • the management device 1000 of the flexible Ethernet group includes a memory 1001, a processor 1002, and an interface 1003.
  • the memory 1001, the processor 1002, and the interface 1003 are connected by a bus 1004.
  • a computer program or at least one instruction is stored in the memory 1001, and the computer program or at least one instruction is loaded and executed by the processor 1002 to implement any one of the above-mentioned flexible Ethernet group management methods.
  • the interface 1003 is used to communicate with other devices in the network.
  • the interface 1003 may be implemented in a wireless or wired manner.
  • the interface 1003 may be a network card.
  • the management device 1000 of the flexible Ethernet group can communicate with the server through the interface 1003.
  • the network device shown in FIG. 20 is the first network device in FIGS. 5 and 10-17, and the processor 1002 reads the computer program or instruction in the memory 1001, so that the network device shown in FIG. 20 can execute the first network device. All or part of the operations performed by a network device.
  • the network device shown in FIG. 20 is the second network device in FIGS. 5 and 10-17, and the processor 1002 reads the computer program or instruction in the memory 1001 to enable the network device shown in FIG. 20 to execute All or part of the operations performed by the second network device.
  • FIG. 20 only shows a simplified design of the management device 1000 of the flexible Ethernet group.
  • the management device 1000 of the flexible Ethernet group may include any number of interfaces, processors or memories.
  • the above-mentioned processor may be a central processing unit (CPU), other general-purpose processors, digital signal processing (DSP), application specific integrated circuit (ASIC), Field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc.
  • the general-purpose processor may be a microprocessor or any conventional processor. It is worth noting that the processor may be a processor that supports an advanced reduced instruction set machine (advanced RISC machines, ARM) architecture.
  • the foregoing memory may include a read-only memory and a random access memory, and provide computer programs/instructions and data to the processor.
  • the memory may also include non-volatile random access memory.
  • the memory can also store device type information.
  • the memory may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory, wherein the non-volatile memory may be a read-only memory (read-only memory, ROM) , Programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM), which is used as an external cache. By way of exemplary but not limiting illustration, many forms of RAM are available.
  • static random access memory static random access memory
  • dynamic random access memory dynamic random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate synchronous dynamic random access Memory double data date SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • serial link DRAM SLDRAM
  • direct memory bus random access memory direct rambus RAM
  • a management system for a flexible Ethernet group is also provided, the system including a first network device and a second network device;
  • the first network device is used to execute the method executed by the first network device described in any one of FIGS. 5 and 10-17
  • the second network device is used to execute any one of the methods described in FIGS. 5 and 10-17 The method performed by the second network device.
  • a computer-readable storage medium is also provided, and a computer program or at least one instruction is stored in the storage medium.
  • the computer program or instruction is loaded and executed by a processor to implement the flexible Ethernet group management method described above.
  • This application provides a computer program.
  • the processor or the computer can execute the corresponding operations and/or procedures in the above method embodiments.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Abstract

本申请公开一种灵活以太网组的管理方法、设备及计算机可读存储介质，以第一网络设备执行该方法为例，第一网络设备确定需要调整的目标灵活以太网组的配置信息，基于该目标灵活以太网组的配置信息与第二网络设备同步进行目标灵活以太网组的调整。第二网络设备通过目标灵活以太网组内的物理层链路与第一网络设备通信，目标灵活以太网组的配置信息包括目标灵活以太网组的备用灵活以太网组号和备用灵活以太图，备用灵活以太图包括目标灵活以太网组内的物理层链路信息。由于第一网络设备和第二网络设备同步调整，因而本申请实施例提供了无损动态灵活以太网组FlexE Group调整的管理方案，能够避免影响业务，实现各种场景的以太网组的调整。

Description

灵活以太网组的管理方法、设备及计算机可读存储介质
本申请要求于2019年12月06日提交的申请号为201911244655.2、发明名称为“灵活以太网组的管理方法、装置、设备及存储介质”的中国专利申请的优先权，本申请要求于2019年12月31日提交的申请号为201911412030.2、发明名称为“灵活以太网组的管理方法、设备及计算机可读存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，特别涉及一种灵活以太网组的管理方法、设备及计算机可读存储介质。
背景技术
由于当前以太网接口标准都是固定速率，为了满足更高带宽的需求，灵活以太(flexible ethernet，FlexE)技术创建了一个媒体访问控制(media access control，MAC)层和物理编码子层(physical coding sublayer，PCS)之间的适配层，使得以太网接口速率可以灵活匹配多种业务场景。
其中，FlexE技术的基本功能是将M个FlexE用户(client)的业务流按照FlexE夹层(shim)的时分复用(time division multiplexing，TDM)机制映射到一个由N条物理层(physical layer，PHY)链路组成的FlexE网组(group)上，M和N均为正整数。
发明内容
本申请实施例提供了一种灵活以太网组的管理方法、设备及计算机可读存储介质，以在不影响业务的情况下，对灵活以太网组进行调整。
第一方面，提供了一种灵活以太网组的管理方法，该方法应用于第一网络设备，第一网络设备确定需要调整的目标灵活以太网组的配置信息，基于该目标灵活以太网组的配置信息，与第二网络设备同步进行所述目标灵活以太网组的调整。其中，第二网络设备通过目标灵活以太网组内的物理层链路与第一网络设备通信。该目标灵活以太网组的配置信息包括但不限于目标灵活以太网组的备用灵活以太网组号和备用灵活以太图，该备用灵活以太图包括目标灵活以太网组内的物理层链路信息。
通过与第二网络设备同步进行目标灵活以太网组的调整，实现了灵活以太网组FlexE Group的无损动态调整，不仅能够避免影响业务，还可用于实现各种场景的以太网组的调整。
在示例性实施例中，第一网络设备确定需要调整的目标灵活以太网组的配置信息，包括：第一网络设备与第二网络设备通过开销块协商需要调整的目标灵活以太网组的配置信息，该开销块携带目标灵活以太网组的配置信息。
在示例性实施例中，开销块的保留位域字段携带目标灵活以太网组的配置信息，或者，开销块的管理通道字段携带目标灵活以太网组的配置信息。
在示例性实施例中，第一网络设备确定需要调整的目标灵活以太网组的配置信息，包括： 第一网络设备接收控制器向第一网络设备和第二网络设备发送的需要调整的目标灵活以太网组的配置信息。
在示例性实施例中，第一网络设备确定需要调整的目标灵活以太网组的配置信息之后，还包括：当目标灵活以太网组内需要增加新的物理层链路时，备用灵活以太图包括新的物理层链路信息，第一网络设备确定新的物理层链路有效；响应于新的物理层链路有效，第一网络设备执行基于目标灵活以太网组的配置信息，与第二网络设备同步进行目标灵活以太网组的调整的操作。
在示例性实施例中，所述第一网络设备确定需要调整的目标灵活以太网组的配置信息之后，还包括：当所述目标灵活以太网组内的目标物理层链路需要被删除时，所述备用灵活以太图不包括所述目标物理层链路信息，所述第一网络设备确定删除所述目标物理层链路之后的目标灵活以太网组可支撑当前流量；响应于删除所述目标物理层链路之后的目标灵活以太网组可支撑当前流量，所述第一网络设备执行基于所述目标灵活以太网组的配置信息，与第二网络设备同步进行所述目标灵活以太网组的调整的操作。
在示例性实施例中，所述第一网络设备确定需要调整的目标灵活以太网组的配置信息之后，还包括：当所述目标灵活以太网组内的物理层链路需要被重新分组时，所述备用灵活以太网组号包括重新分组后的灵活以太网组的网组号，所述备用灵活以太图包括重新分组后的物理层链路信息，所述第一网络设备确定重新分组后的灵活以太网组可支撑对应的业务流；响应于重新分组之后的灵活以太网组可支撑对应的业务流，所述第一网络设备执行基于所述目标灵活以太网组的配置信息，与第二网络设备同步进行所述目标灵活以太网组的调整的操作。
在示例性实施例中，所述第一网络设备基于所述目标灵活以太网组的配置信息，与第二网络设备同步进行所述目标灵活以太网组的调整，包括：所述第一网络设备和所述第二网络设备协商调整时间，当到达所述调整时间时，所述第一网络设备基于所述目标灵活以太网组的配置信息，与所述第二网络设备同步进行所述目标灵活以太网组的调整。
第二方面，提供了一种灵活以太网组的管理方法，所述方法包括：第二网络设备确定需要调整的目标灵活以太网组的配置信息，所述目标灵活以太网组的配置信息包括所述目标灵活以太网组的备用灵活以太网组号和备用灵活以太图，所述备用灵活以太图包括所述目标灵活以太网组内的物理层链路信息；所述第二网络设备基于所述目标灵活以太网组的配置信息，与第一网络设备同步进行所述目标灵活以太网组的调整，所述第一网络设备通过所述目标灵活以太网组内的物理层链路与所述第二网络设备通信。
在示例性实施例中，所述第二网络设备确定需要调整的目标灵活以太网组的配置信息，包括：所述第二网络设备与所述第一网络设备通过开销块协商需要调整的目标灵活以太网组的配置信息，所述开销块携带所述目标灵活以太网组的配置信息。
在示例性实施例中，所述开销块的保留位域字段携带所述目标灵活以太网组的配置信息，或者，所述开销块的管理通道字段携带所述目标灵活以太网组的配置信息。
在示例性实施例中，所述第二网络设备确定需要调整的目标灵活以太网组的配置信息，包括：所述第二网络设备接收控制器向所述第二网络设备和所述第一网络设备发送的需要调整的目标灵活以太网组的配置信息。
在示例性实施例中，所述第二网络设备基于所述目标灵活以太网组的配置信息，与第一网络设备同步进行所述目标灵活以太网组的调整，包括：所述第二网络设备和所述第一网络设备协商调整时间，当到达所述调整时间时，所述第二网络设备基于所述目标灵活以太网组的配置信息，与所述第一网络设备同步进行所述目标灵活以太网组的调整。
第三方面，提供了一种灵活以太网组的管理装置，所述装置应用于第一网络设备，所述装置包括：
确定模块，用于确定需要调整的目标灵活以太网组的配置信息，所述目标灵活以太网组的配置信息包括所述目标灵活以太网组的备用灵活以太网组号和备用灵活以太图，所述备用灵活以太图包括所述目标灵活以太网组内的物理层链路信息；
调整模块，用于基于所述目标灵活以太网组的配置信息，与第二网络设备同步进行所述目标灵活以太网组的调整，所述第二网络设备通过所述目标灵活以太网组内的物理层链路与所述第一网络设备通信。
在示例性实施例中，所述确定模块，用于与所述第二网络设备通过开销块协商需要调整的目标灵活以太网组的配置信息，所述开销块携带所述目标灵活以太网组的配置信息。
在示例性实施例中，所述开销块的保留位域字段携带所述目标灵活以太网组的配置信息，或者，所述开销块的管理通道字段携带所述目标灵活以太网组的配置信息。
在示例性实施例中，所述确定模块，用于接收控制器向所述第一网络设备和所述第二网络设备发送的需要调整的目标灵活以太网组的配置信息。
在示例性实施例中，所述确定模块，还用于当所述目标灵活以太网组内增加新的物理层链路时，所述备用灵活以太图包括所述新的物理层链路信息，确定所述新的物理层链路有效；
所述调整模块，用于响应于所述新的物理层链路有效，执行基于所述目标灵活以太网组的配置信息，与第二网络设备同步进行所述目标灵活以太网组的调整的操作。
在示例性实施例中，所述确定模块，还用于当所述目标灵活以太网组内的目标物理层链路需要被删除时，所述备用灵活以太图不包括所述目标物理层链路信息，确定删除所述目标物理层链路之后的目标灵活以太网组可支撑当前流量；
所述调整模块，用于响应于确定删除所述目标物理层链路之后的目标灵活以太网组可支撑当前流量，执行基于所述目标灵活以太网组的配置信息，与第二网络设备同步进行所述目标灵活以太网组的调整的操作。
在示例性实施例中，所述确定模块，还用于当所述目标灵活以太网组内的物理层链路被重新分组时，所述备用灵活以太网组号包括重新分组后的灵活以太网组的网组号，所述备用灵活以太图包括重新分组后的物理层链路信息，确定重新分组后的灵活以太网组可支撑对应的业务流；
所述调整模块，用于响应于重新分组之后的灵活以太网组可支撑对应的业务流，执行基于所述目标灵活以太网组的配置信息，与第二网络设备同步进行所述目标灵活以太网组的调整的操作。
在示例性实施例中，所述调整模块，用于和所述第二网络设备协商调整时间，当到达所述调整时间时，基于所述目标灵活以太网组的配置信息，与所述第二网络设备同步进行所述目标灵活以太网组的调整。
第四方面，提供了一种灵活以太网组的管理装置，所述装置应用于第二网络设备，所述装置包括：
确定模块，用于确定需要调整的目标灵活以太网组的配置信息，所述目标灵活以太网组的配置信息包括所述目标灵活以太网组的备用灵活以太网组号和备用灵活以太图，所述备用灵活以太图包括所述目标灵活以太网组内的物理层链路信息；
调整模块，用于基于所述目标灵活以太网组的配置信息，与第一网络设备同步进行所述目标灵活以太网组的调整，所述第一网络设备通过所述目标灵活以太网组内的物理层链路与所述第二网络设备通信。
在示例性实施例中，所述确定模块，用于与所述第一网络设备通过开销块协商需要调整的目标灵活以太网组的配置信息，所述开销块携带所述目标灵活以太网组的配置信息。
在示例性实施例中，所述开销块的保留位域字段携带所述目标灵活以太网组的配置信息，或者，所述开销块的管理通道字段携带所述目标灵活以太网组的配置信息。
在示例性实施例中，所述确定模块，用于接收控制器向所述第二网络设备和所述第一网络设备发送的需要调整的目标灵活以太网组的配置信息。
在示例性实施例中，所述调整模块，用于和所述第一网络设备协商调整时间，当到达所述调整时间时，基于所述目标灵活以太网组的配置信息，与所述第一网络设备同步进行所述目标灵活以太网组的调整。
上述新的物理层链路有效，满足如下条件：所述新的物理层链路是独立的物理层链路，所述新的物理层链路与所述目标灵活以太网组内已有的物理层链路无冲突，所述新的物理层链路与目标灵活以太网组内已有的物理层链路的相位能够对齐。
还提供一种网络设备，所述设备包括：存储器及处理器，所述存储器中存储有计算机程序或至少一条指令，所述计算机程序或至少一条指令由所述处理器加载并执行，以实现上述第一方面任一所述的方法。
还提供一种网络设备，所述设备包括：存储器及处理器，所述存储器中存储有计算机程序或至少一条指令，所述计算机程序或至少一条指令由所述处理器加载并执行，以实现上述第二方面任一所述的方法。
还提供了一种灵活以太网组的管理系统，所述系统包括第一网络设备和第二网络设备，所述第一网络设备用于执行所述第一方面中任一所述的方法，所述第二网络设备用于执行所述第二方面中任一所述的方法。
还提供了一种计算机可读存储介质，所述存储介质中存储有计算机程序或至少一条指令，所述计算机程序或指令由处理器加载并执行以实现如上任一所述的方法。
提供了另一种通信装置，该装置包括：收发器、存储器和处理器。其中，该收发器、该存储器和该处理器通过内部连接通路互相通信，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制收发器接收信号，并控制收发器发送信号，并且当该处理器执行该存储器存储的指令时，使得该处理器执行上述任一种可能的实施方式中的方法。
作为一种示例性实施例，所述处理器为一个或多个，所述存储器为一个或多个。
作为一种示例性实施例，所述存储器可以与所述处理器集成在一起，或者所述存储器与 处理器分离设置。
在一些实施例中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
提供了一种计算机程序(产品)，所述计算机程序(产品)包括：计算机程序代码，当所述计算机程序代码被计算机运行时，使得所述计算机执行上述各方面中的方法。
提供了一种芯片，包括处理器，用于从存储器中调用并运行所述存储器中存储的指令，使得安装有所述芯片的通信设备执行上述各方面中的方法。
提供另一种芯片，包括：输入接口、输出接口、处理器和存储器，所述输入接口、输出接口、所述处理器以及所述存储器之间通过内部连接通路相连，所述处理器用于执行所述存储器中的代码，当所述代码被执行时，所述处理器用于执行上述各方面中的方法。
附图说明
图1为本申请实施例提供的FlexE Group的结构示意图；
图2为本申请实施例提供的PHY链路的数据结构示意图；
图3为本申请实施例提供的开销帧和开销复帧的结构示意图；
图4为本申请实施例提供的开销帧和开销复帧的结构示意图；
图5为本申请实施例提供的灵活以太网组的管理方法流程图；
图6为本申请实施例提供的开销帧和开销复帧的结构示意图；
图7为本申请实施例提供的开销帧和开销复帧的结构示意图；
图8为本申请实施例提供的开销帧和开销复帧的结构示意图；
图9为本申请实施例提供的开销帧和开销复帧的结构示意图；
图10为本申请实施例提供的灵活以太网组的管理系统结构示意图；
图11为本申请实施例提供的灵活以太网组的管理方法流程图；
图12为本申请实施例提供的灵活以太网组的管理系统结构示意图；
图13为本申请实施例提供的灵活以太网组的管理方法流程图；
图14为本申请实施例提供的灵活以太网组的管理系统结构示意图；
图15为本申请实施例提供的灵活以太网组的管理方法流程图；
图16为本申请实施例提供的灵活以太网组的管理方法流程图；
图17为本申请实施例提供的灵活以太网组的管理系统结构示意图；
图18为本申请实施例提供的灵活以太网组的管理装置结构示意图；
图19为本申请实施例提供的灵活以太网组的管理装置结构示意图；
图20为本申请实施例提供的灵活以太网组的管理设备的结构示意图。
具体实施方式
本申请的实施方式部分使用的术语仅用于对本申请的具体实施例进行解释，而非旨在限定本申请。
随着互联网协议(internet protocol，IP)网络应用和业务的多样化，网络流量增加的趋势越来越明显。由于以太网接口标准制定和产品开发中是阶梯型的，当前以太网接口标准都是 固定速率，因而会存在传送需求和实际设备接口能力之间的差距，经常需要解决在当前以太网接口速率等级下，满足更高带宽的需求。对此，光互联网论坛(optical internetworking forum，OIF)FlexE技术创建了一个MAC和PCS之间的适配层，使得以太网接口速率可以灵活匹配多种业务场景，并且在更高带宽的网络处理器(network processor，NP)/转发设备出现时，不必等待新的固定速率以太网标准出台，即可发挥设备的最大性能。
其中，FlexE的基本功能是将M个FlexE clients的业务流按照FlexE Shim的时分复用(time division multiplexing，TDM)机制映射到一个由N条物理层PHY链路组成的灵活以太网组FlexE Group上，M和N均为正整数，FlexE的基本结构可如图1所示。其中，M为6，N为4，即图1所示的FlexE是将6个FlexE clients的业务流按照FlexE Shim的TDM机制映射到一个由4条PHY链路组成的FlexE Group上。
以100GE(吉比特以太网)PHY为例，FlexE的映射机制中，每条100G PHY对应着20个64B/66B码块对应的时隙(time slot)，每个码块对应5Gbps速率的净荷速率(payload rate)。当前FlexE标准支持100GE，200GE，400GE，和50GE接口上的FlexE。经过一条100GE PHY的数据的格式如图2所示。图2中，每个块为一个根据IEEE 802.3 Clause 82编码(encoded)的64B/66B块(block)，每20个blocks组成一个时隙表(calendar)，每个块即TDM映射机制中的一个时隙(time slot)。每个calendar重复1023次之后，插入1个64B/66B encoded开销块(overhead block)。然后，每8个开销块组成一个开销帧，每32个开销帧组成一个开销复帧。整个FlexE的流量时隙映射(client-slot mapping)和各种管理，都在开销复帧内完成。开销帧和开销复帧的格式如图3或图4所示。
如图3或图4所示，FlexE开销(overhead，OH)中包括FlexE group中所有的FlexE Client的时隙表配置信息，为了使FlexEClient在改变时隙带宽配置的时候，不出现流量损失，可采用两张时隙表：Calendar A和Calendar B，这两张时隙表具有如下特点：
特点1：任意时间只有一张时隙表处于工作状态，也就是说，任意时间，要么Calendar A处于工作状态，要么Calendar B处于工作状态。
特点2：在对接FlexE group的发送端(TX)和接收端(RX)两端，会有FlexE OH开销的时隙协商机制来保障TX与RX的工作时隙表是一致的。
例如，Calendar A处于工作状态，那么Calendar B则处于相应时隙配置的备用状态。
特点3：时隙协商的发起端是TX，而RX则处于被动接收状态。假设Calendar A处于工作状态，那么TX会将变化的Calendar B通过FlexE OH开销刷新给RX。随后TX会发起时隙表切换请求(calendar switch request，CSR)时隙协商请求，要求将工作表切换到Calendar B上，TX收到RX的回应后，TX触发TX和RX均将工作表切换到Calendar B。
需要说明的是，在对接FlexE group的TX和RX两端，首次建立连接后，也会触发一次FlexE OH开销的时隙协商，以保证两端处于工作的时隙表是一致的。
图3或图4中除了包括上述Calendar A和Calendar B之外，还包括如下信息：
C：用于指示正在使用的时隙配置(calendar configuration in use)。如图3或图4所示的开销帧的第一个块中编号为8的比特位字段、第二个块中编号为0的比特位字段和第三个块中编号为0的比特位字段均携带C。
开销多帧指示器(overhead multiframe indicator，OMFI)，在IA OIF-FLEXE-01.0/01.1/02.2/02.1等标准中称为OMF：用于指示复帧的边界。如图3或图4所 示的开销帧的第一个块中编号为9的比特位字段携带该OMF。其中，在一个复帧里，前16个单帧的OMF的值为0，后16个单帧的OMF的值为1，通过0和1之间的转换，能够确定复帧的边界。
远程物理故障(remote PHY fault，RPF)：用于指示远程物理故障。如图3或图4所示的开销帧的第一个块中编号为10的比特位字段携带该RPF。
同步控制(synchronization control，SC)：用于同步控制。如图3或图4所示的开销帧的第一个块中编号为11的比特位字段携带该SC。
灵活以太图(FlexE Map)：用于控制哪些FlexE实例是此组的成员(Control of which Flexe Instances are members of this group)。如图3或图4所示的开销帧的第2个块中编号为1至编号为8的比特位字段携带该FlexE Map。示例性地，该FlexE Map包括FlexE Group内的物理层链路信息，FlexE Map的每个比特位对应一个物理层链路，FlexE Map的每个比特位的值用于表示该比特位对应的物理层链路是否在该FlexE Group中。例如，如果比特位的值为第一值，例如该第一值为1，则认为该比特位对应的物理层链路在该FlexEGroup中。如果比特位的值为第二值，例如该第二值为0，则认为该比特位对应的物理层链路不在该FlexEGroup中。
灵活以太实例号(FlexE instance Number)：表示组中此Flexe实例的标识(Identity of this Flexe Instance within the group)。如图3或图4所示的开销帧的第2个块中编号为9至编号为16的比特位字段携带该FlexE instance Number。
灵活以太网组号(FlexE Group Number)：用于标识灵活以太网组。如图3或图4所示的开销帧的第1个块中编号为12至编号为31的比特位字段携带该FlexE Group Number。
时隙表切换确认(calendar switch acknowledgement，CSA)：在执行协议(implementation agreements，IA)OIF-FLEXE-01.0/01.1/02.2/02.1等标准中称为CA，其中，01.0/01.1/02.2/02.1是IA OIF-FLEXE标准的几个版本。如图3或图4所示的开销帧的第3个块中编号为34的比特位字段携带该CA。
时隙表切换请求(calendar switch request，CSR)：在IA OIF-FLEXE-01.0/01.1/02.2/02.1等标准中称为CR。如图3或图4所示的开销帧的第3个块中编号为33的比特位字段携带该CR。
同步头(synchronization head，SH)：如图3或图4所示的开销帧的帧头。
S：有效同步头位(valid sync header bits)：如图3或图4所示的开销帧的第4个块至第8个块中的SH下的字段携带该S。
管理通道(Management Channel)：如图3或图4所示的开销帧的第4个块至第8个块携带该管理通道。
CRC-16：用于对开销块的内容进行循环冗余校验(cyclic redundancy check，CRC)保护。如图3或图4所示的开销帧的第3个块中编号为48至编号为63的比特位字段携带该CRC-16。
除包括上述信息的字段外，图3或图4中还包括预留(reserved)字段，如图3或图4所示的开销帧的第二个块中编号为17至编号为63比特位字段、第三个块中编号为35至编号为47比特位字段均为预留字段。
在一些实施例中，用户可以针对当前的网络根据各FlexE Client的流量大小和数量，更改FlexE Group中PHY的数量。例如：当FlexE Group内PHY所提供带宽不足时，需要增加1个或多个PHY进入当前FlexE Group，支持更多的业务流；或者当前FlexE Group内有大量带宽闲置，可以移除其中一个或者多个PHY，释放网络资源给其他业务使用；又或者，当前的 FlexE Group中，有需求需要将当前FlexE Group拆分为两个或者更多个，以适配当前的业务模型。
无论是上述哪种操作，都涉及到FlexE Group层面的调整。针对需要调整FlexE Group的情况，目前需要先解散当前的FlexE Group，根据需求重新建立一个或者多个新的FlexE Group，每个FlexE Group包括其所需要的PHY。也就是说，该种调整FlexE Group的方式中，针对FlexE Group的动态调整，无论是增删PHY，还是将当前FlexE Group分成多个子FlexE Group等等，都需要先解散当前的FlexE Group，再重新建立新的FlexE Group。因此，会导致当前的FlexE Client业务流无法在调整的过程中继续传输，存在正常传输中的业务断流的情况。
对此，本申请实施例提供了一种灵活以太网组的管理方法，该方法提供了一种无损动态FlexE Group调整的管理方法，从而在避免影响业务的情况下，实现上述各种场景的调整。
如图5所示，本申请实施例提供的方法包括如下几个过程。
在401中，第一网络设备确定需要调整的目标灵活以太网组的配置信息，目标灵活以太网组的配置信息包括目标灵活以太网组的备用灵活以太网组号和备用灵活以太图，备用灵活以太图包括目标灵活以太网组内的物理层链路信息。
在示例性实施例中，第一网络设备确定需要调整的目标灵活以太网组的配置信息，包括但不限于如下两种方式：
方式一：第一网络设备确定需要调整的目标灵活以太网组的配置信息，包括：第一网络设备与第二网络设备通过开销块协商需要调整的目标灵活以太网组的配置信息，开销块携带目标灵活以太网组的配置信息。
该方式一中，开销块的保留位域字段携带目标灵活以太网组的配置信息。如图6或图7所示，在reserved位域中，选取20bits作为备用灵活以太网组号(FlexE Group Number Bak)、8bits作为备用灵活以太图(FlexE Map Bak)，8bits作为备用灵活以太实例号(FlexE Instance Number Bak)，与原有的相应位域形成主备关系。其中，FlexE Group Number Bak、FlexE Map Bak和FlexE Instance Number Bak中的Bak为Back up的缩写，代表备用。例如，在图6或图7所示的开销帧的第2个块中编号为18至编号为37的比特位字段携带FlexE Group Number Bak，与图6或图7所示的开销帧的第1个块中编号为12至编号为31的比特位字段携带的FlexE Group Number形成主备关系。在图6或图7所示的开销帧的第2个块中编号为38至编号为45的比特位字段携带FlexE Map Bak，与图6或图7所示的开销帧的第2个块中编号为1至编号为8的比特位字段携带的FlexE Map形成主备关系。在图6或图7所示的开销帧的第2个块中编号为46至编号为53的比特位字段携带FlexE Instance Number Bak，与图6或图7所示的开销帧的第2个块中编号为9至编号为16的比特位字段携带的FlexE Instance Number形成主备关系。
在reserved位域选取2bit，作为GR、GA，用于request/acknowledge机制。例如，在图6或图7所示的开销帧的第3个块中编号为36的比特位字段携带GR，在图6或图7所示的开销帧的第3个块中编号为37的比特位字段携带GA。
在reserved位域，选择3bits，(例如：Block #2 bit 17&63,Block #3 bit 35)，作为GGG比特，用于指示切换。
在示例性实施例中，除了采用Reserved位域携带上述信息外，本申请实施例还提供了另外一种携带上述信息的方式，例如，该方式可如图8或图9所示。在每个开销帧中仅传输1bits FlexE Group Number Bak，如图8或图9中的FB所示，该FB代表1bit的FlexE Group Number Bak， 通过复帧传输FlexE Group Number Bak所有的位域；示例性地，也可以在每个开销帧中仅传输1bit FlexE Instance Number Bak，可以仅占开销帧中1bit，通过复帧传输FlexE Instance Number Bak所有位域。此外，本申请实施例提供的方法中，还支持仅使用1bit G，而不使用3bit GGG。该种方式仅适用于系统误码率<<1e-12的情况，即适用于系统误码率远小于10 -12。
需要说明的是，以上为节约开销中保留位域的方式，本申请实施例不限定每个帧传输的比特数(例如FlexE Group Number Bak可以采用每帧传4bit，5bit，等等)。
除上述方式外，还可以通过开销块的管理通道字段携带目标灵活以太网组的配置信息。例如，如图3或图4所示，管理通道可以为FlexE开销中第4至第8块所示。本申请实施例提供的方法支持第一网络设备和第二网络设备由管理通道进行协商，来确定目标灵活以太网组的配置信息。该管理通道可以承载多种协议，因此，以管理通道承载以太报文为例，可通过该以太报文来协商目标灵活以太网组的配置信息。需要说明的是，由于管理通道在FlexE开销中占有4个块的空间，因而本申请实施例不对采用管理通道的哪些字段来协商目标灵活以太网组的配置信息进行限定。在一些实施例中，该管理通道可以承载的协议为链路层发现协议(link layer discovery protocol，LLDP)或精确时间协议(precision time protocol，PTP)。
方式二：第一网络设备确定需要调整的目标灵活以太网组的配置信息，包括：第一网络设备接收控制器向第一网络设备和第二网络设备发送的需要调整的目标灵活以太网组的配置信息。
该种方式下，通过上层管理，例如软件定义网络(software defined network，SDN)控制器分别与第一网络设备和第二网络设备的管理接口通信，以下发需要调整的目标灵活以太网的配置信息。
无论是采用上述哪种方式确定需要调整的目标灵活以太网的配置信息，第一网络设备确定需要调整的目标灵活以太网组的配置信息之后，针对不同的调整情况，在调整目标灵活以太网组之前，包括但不限于如下三种处理方式中的一种或多种：
处理方式一：当目标灵活以太网组内需要增加新的物理层链路时，备用灵活以太图包括新的物理层链路信息，第一网络设备确定新的物理层链路是否有效；
响应于确定新的物理层链路有效，第一网络设备执行基于目标灵活以太网组的配置信息，与第二网络设备同步进行目标灵活以太网组的调整的操作。
其中，新的物理层链路是该目标灵活以太网组之前未包括的物理层链路。在将该新的物理层链路加入该目标灵活以太网组之前，先来确定该新的物理层链路是否有效，从而避免冲突。关于确定新的物理层链路是否有效的方式，本申请实施例不进行限定。如果新的物理层链路有效，包括但不限于需要满足如下条件：
条件一：该新的物理层链路是独立的物理层链路，而不在其他灵活以太网组中。
条件二：该新的物理层链路与目标灵活以太网组内已有的物理层链路无冲突。
条件三：该新的物理层链路与目标灵活以太网组内已有的物理层链路的相位能够对齐。
在将新的物理层链路加入该目标灵活以太网组之前，可以先判断该新的物理层链路是否满足上述三个条件。本申请实施例不对这三个条件的判断顺序进行限定。
在示例性实施例中，针对条件一，判断该新的物理层链路是否为独立的物理层链路，包括但不限于确定该新的物理层链路的Group Number是否有效。若该新的物理层链路的Group Number有效，意味着该新的物理层链路在另一个Group里面，不是独立的物理层链路。若该 新的物理层链路的Group Number无效，例如该Group Number为全0或全f，则认为该新的物理层链路不在另一个Group里面，而是独立的物理层链路。该种情况下，如果该新的物理层链路要加入该目标灵活以太网组，需要先从之前所在的灵活以太网组中脱离，之后该新的物理层链路在满足其他条件的情况下才会被加入该目标灵活以太网组。
在示例性实施例中，针对上述条件二，判断该新的物理层链路与目标灵活以太网组内已有的物理层链路有无冲突，包括但不限于判断该新的物理层链路的FlexEInstance Number与目标灵活以太网组内已有的物理层链路的FlexE Instance Number是否一致。如果目标灵活以太网组内已有的物理层链路中任一物理层链路的FlexEInstance Number与该新的物理层链路的FlexE Instance Number一致，则认为存在冲突。如果目标灵活以太网组内已有的物理层链路中任一物理层链路的FlexEInstance Number与该新的物理层链路的FlexE Instance Number均不一致，则认为无冲突。对于存在冲突的情况，需要对存在冲突的物理层链路和该新的物理层链路的中的至少一个物理层链路的FlexE Instance Number进行更改，使得不存在冲突。之后，该新的物理层链路满足其他条件的情况下，才会被加入该目标灵活以太组。
在示例性实施例中，针对上述条件三，判断该新的物理层链路与目标灵活以太网组内已有的物理层链路的相位能否对齐，包括但不限于判断该新的物理层链路的开销复帧的帧头与目标灵活以太网组内已有的各个物理层链路的开销复帧的帧头的间隔是否在参考范围内。如果该新的物理层链路的开销复帧的帧头与目标灵活以太网组内已有的各个物理层链路的开销复帧的帧头的间隔在参考范围内，则该新的物理层链路与目标灵活以太网组内已有的物理层链路的相位能对齐。如果该新的物理层链路的开销复帧的帧头与目标灵活以太网组内已有的各个物理层链路的开销复帧的帧头的间隔不在参考范围内，则该新的物理层链路与目标灵活以太网组内已有的物理层链路的相位不能对齐。例如，以该参考范围为+/-13us为例，如果该新的物理层链路的开销复帧的帧头与目标灵活以太网组内已有的各个物理层链路的开销复帧的帧头的间隔在+/-13us参考范围内，则该新的物理层链路与目标灵活以太网组内已有的物理层链路的相位能对齐。如果该新的物理层链路的开销复帧的帧头与目标灵活以太网组内已有的任一物理层链路的开销复帧的帧头的间隔不在+/-13us参考范围内，则该新的物理层链路与目标灵活以太网组内已有的物理层链路的相位不能对齐。
当该新的物理层链路满足上述条件后，可以被加入该目标灵活以太网组，如果该新的物理层链路不满足上述任一条件，则可以发起告警，以提示用户无法完成目标灵活以太网组的调整。
处理方式二：当目标灵活以太网组内的目标物理层链路需要被删除时，备用灵活以太图不包括目标物理层链路信息，第一网络设备确定删除目标物理层链路之后的目标灵活以太网组是否可支撑当前流量；
响应于删除目标物理层链路之后的目标灵活以太网组可支撑当前流量，第一网络设备执行基于目标灵活以太网组的配置信息，与第二网络设备同步进行目标灵活以太网组的调整的操作。其中，“删除目标物理层链路之后的目标灵活以太网组可支撑当前流量”是指删除目标物理层链路之后的目标灵活以太网组中，剩余物理层链路的总带宽不小于该目标灵活以太网组当前所应承载的业务流所需的带宽。
针对处理方式二，为了在不影响业务流的情况下，删除目标灵活以太网组内的目标物理层链路，本申请实施例提供的方法删除目标灵活以太网组内的目标物理层链路之前，先确定 删除目标物理层链路之后的目标灵活以太网组是否可支撑当前流量。
示例性地，第一网络设备确定删除目标物理层链路之后的目标灵活以太网组是否可支撑当前流量，包括但不限于确定删除目标物理层链路之后的目标灵活以太网组中，剩余物理层链路的总带宽是否小于该目标灵活以太网组当前所应承载的业务流所需的带宽。如果删除目标物理层链路之后的目标灵活以太网组中，剩余物理层链路的总带宽不小于该目标灵活以太网组当前所应承载的业务流所需的带宽，则可以确定删除目标物理层链路之后的目标灵活以太网组可支撑当前流量。
在示例性实施例中，如果删除目标物理层链路之后的目标灵活以太网组中，剩余物理层链路的总带宽小于该目标灵活以太网组当前所应承载的业务流所需的带宽，则确定删除目标物理层链路之后的目标灵活以太网组不可支撑当前流量，该种情况下，可提出告警，以告知用户该调整操作将影响业务流。
例如，以目标灵活以太网组内包括5条物理层链路为例，当其中的一条物理层链路需要删除时，如果剩余4条物理层链路的总带宽为100G，而该目标灵活以太网组当前所应承载的业务流所需的带宽为90G，则可以确定删除目标物理层链路之后的目标灵活以太网组可支撑当前流量。
处理方式三：当目标灵活以太网组内的物理层链路需要被重新分组时，备用灵活以太网组号包括重新分组后的灵活以太网组的网组号，备用灵活以太图包括重新分组后的物理层链路信息，第一网络设备确定重新分组后的灵活以太网组是否可支撑对应的业务流；
响应于重新分组之后的灵活以太网组可支撑对应的业务流，第一网络设备执行基于目标灵活以太网组的配置信息，与第二网络设备同步进行目标灵活以太网组的调整的操作。
由于目标灵活以太网组承载了业务流，如果将该目标灵活以太网组进行分割，则需要保证分割后的灵活以太网组仍然能够承载对应的业务流，从而在不影响业务流的情况下，将灵活以太网组进行分割。因此，本申请实施例提供的方法将目标灵活以太网组内的物理层链路重新分组时，先确定重新分组后的灵活以太网组是否可支撑对应的业务流。
示例性地，确定重新分组后的灵活以太网组是否可支撑对应的业务流，包括但不限于确定重新分组后的灵活以太网组中的物理层链路的总带宽是否小于承载对应的业务流所需的带宽。如果重新分组后的灵活以太网组中的物理层链路的总带宽不小于承载对应的业务流所需的带宽，则可以确定重新分组后的灵活以太网组可支撑对应的业务流。
例如，重新分组前的目标灵活以太网组中的物理层链路的总带宽为4ⅹ100G，共400G，对该目标灵活以太网组进行重新分组，得到两个重新分组后的灵活以太网组，简称第一分组和第二分组。第一分组和第二分组中的物理层链路的总带宽均为200G。如果目标灵活以太网组承载的业务流有三个，分别是200G的第一业务流，150G的第二业务流和50G的第三业务流。对于本次重新分组，第一业务流被分配进入第一分组，第二业务流和第三业务流被分配进入第二分组。也就是说，该第一分组对应的业务流为200G的第一业务流，第二分组对应的业务流为150G的第二业务流+50G的第三业务流。由于第一分组的物理层链路的总带宽为200G，不小于承载200G的第一业务流所需的带宽，因而该第一分组可支撑对应的200G的第一业务流。由于第二分组的物理层链路的总带宽为200G，不小于承载第二业务流+第三业务流所需的带宽150G+50G＝200G，因而该第二分组可支撑对应的第二业务流和第三业务流。因此，可以对目标灵活以太网组进行重新分组。
在示例性实施例中，如果重新分组后的灵活以太网组中的物理层链路的总带宽小于承载对应的业务流所需的带宽，则可以确定重新分组后的灵活以太网组不可支撑对应的业务流。该种情况下，可提出告警，以告知用户该分割操作将影响业务流。
例如，以重新分组前的目标灵活以太网组中的物理层链路的总带宽为4ⅹ100G，共400G，对该目标灵活以太网组进行重新分组，得到两个重新分组后的灵活以太网组，简称第一分组和第二分组。第一分组和第二分组中的物理层链路的总带宽均为200G。如果目标灵活以太网组承载的业务流有三个，分别是250G的第一业务流，125G的第二业务流和50G的第三业务流。对于本次重新分组，第一业务流被分配进入第一分组，第二业务流和第三业务流被分配进入第二分组。也就是说，该第一分组对应的业务流为260G的第一业务流，第二分组对应的业务流为125G的第二业务流+50G的第三业务流。即使第二分组的物理层链路的总带宽为200G，不小于承载第二业务流+第三业务流所需的带宽125G+50G＝175G，该第二分组可支撑对应的第二业务流和第三业务流。但由于第一分组的物理层链路的总带宽为200G，小于承载250G的第一业务流所需的带宽，该第一分组不可支撑对应的250G的第一业务流。因此，不对目标灵活以太网组进行重新分组。
其中，重新分组后的灵活以太网组对应的业务流可以随机分配，也可以按照业务流大小及重新分组后的灵活以太网组的物理层链路的总带宽大小确定每个重新分组后的灵活以太网组对应的业务流。例如，将较大的业务流优先分配进入总带宽较大的重新分组后的灵活以太组。还可以采用其他分配方式，本申请实施例不对如何确定重新分组后的灵活以太网组对应的业务流的方式进行限定。
需要说明的是，重新分组后的灵活以太网组的网组号中，可以有一个网组号与重新分组前的目标灵活以太网组的网组号相同，其余重新分组后的灵活以太网组的网组号与重新分组前的目标灵活以太网组的网组号不同。或者，所有重新分组后的灵活以太网组的网组号可以均与重新分组前的目标灵活以太网组的网组号不同。
在402中，第一网络设备基于目标灵活以太网组的配置信息，与第二网络设备同步进行目标灵活以太网组的调整，第二网络设备通过目标灵活以太网组内的物理层链路与第一网络设备通信。
当灵活以太网组需要调整时，第一网络设备与第二网络设备同步进行调整，从而可以不影响业务流。示例性地，由于目标灵活以太网组的配置信息，包括目标灵活以太网组的备用灵活以太网组号和备用灵活以太图，备用灵活以太图包括目标灵活以太网组内的物理层链路信息，因此，第一网络设备基于目标灵活以太网组的配置信息，与第二网络设备同步进行目标灵活以太网组的调整时，可以将该目标灵活以太网组的网组号切换为该备用灵活以太网组号，将该目标灵活以太网组的灵活以太图切换为该备用灵活以太图。
在示例性实施例中，第一网络设备基于目标灵活以太网组的配置信息，与第二网络设备同步进行目标灵活以太网组的调整，包括：
第一网络设备和第二网络设备协商调整时间，当到达调整时间时，第一网络设备基于目标灵活以太网组的配置信息，与第二网络设备同步进行目标灵活以太网组的调整。
需要说明的是，第二网络设备在进行灵活以太网组的管理方法时，可参照上述第一网络设备管理方式，暂不赘述。
接下来，以不同调整情况为例，对上述灵活以太网组的管理方法进行举例说明。
首先，以图10所示的系统为例，将第一网络设备称为设备1，第二网络设备称为设备2，由设备1发起FlexE Group更改，增加PHY#C进入PHY#A和PHY#B所在的FlexE Group。该Group对应的当前FlexE Group Number值为X。后续将直接称之为FlexE Group X。
基于本申请实施例提供的灵活以太网组的管理方法，在将PHY#C加入PHY#A和PHY#B所在的FlexE Group之前，首先要完成的是对PHY#C的校验步骤，判断PHY#C是否可以作为有效的PHY被加入到FlexE Group X中。其中，校验过程包括但不限于：判断PHY#C是独立的PHY，还是在另一个FlexE Group内。如果在另一个FlexE Group内，需要先脱离该另一个FlexE Group，脱离该另一个FlexE Group的方式详见下面图13所示实施例，此处暂不赘述。还需要判断新增加PHY#C的FlexE Instance Number与PHY#A和PHY#B的FlexE Instance Number有无冲突。有冲突的话需要修改其中一个的FlexE Instance Number。本申请实施例不对修改哪个物理层链路的FlexE Instance Number进行限定，示例性地，可修改新增加的PHY#C对应的FlexE Instance Number Bak。此外，还需要确保PHY#C与PHY#A和#B相位可以对齐。例如，对齐的要求是在FlexE要求的+/-13us以内。本申请实施例对对齐方式不加以限定。
如果无法满足上述条件，则需要发送告警，通知用户本次调整可能无法实现。完成校验之后，具体步骤可参见图11，包括但不限于如下几步。
第一步，设备1发起FlexE Group更改，将该开销块中的GR置为1，则GR＝1，用于启动request机制，即设备1向设备2发起request。由于要加入PHY#C，则设备1修改PHY#C的FlexE Group Number Bak，例如，PHY#A/B/C的FlexE Group Number Bak置为X，即修改PHY#C的FlexE Group Number Bak为X。此外，设备1将FlexE Map Bak刷新加入PHY#C，也即FlexE Map Bak不仅包括PHY#A/B的信息，还包括PHY#C的信息。
需要说明的是，如果PHY#C的FlexE Instance Number与PHY#A/B的FlexE Instance Number没有冲突，则无需刷新PHY#C的FlexE Instance NumberBak。如果PHY#C的FlexE Instance Number与PHY#A/B的FlexE Instance Number有冲突，则需要对PHY#C的FlexE Instance Number Bak进行刷新。例如，将PHY#C的FlexE Instance Number Bak修改为与PHY#A/B的FlexE Instance Number不同。
第二步，如果PHY#A/B/C之间的传输延时skew满足要求，设备2通过PHY#C反馈GA＝1，指示可以使用X在FlexE Group Number Bak位域进行传输。
可选地，如果PHY#A/B/C之间的传输延时skew不满足要求，则设备2不反馈GA＝1，等待超时报错退出流程。
第三步，针对设备2反馈GA＝1的情况，G＝1，从下一个复帧头开始，设备1与设备2按照PHY#A/B/C组成的FlexE Group X传递FlexE Clients。
第四步，设备2将FlexE Group Number复制为FlexE Group Number Bak，将FlexE Map复制为FlexE Map Bak，将FlexE Instance Number复制为FlexE Instance Number Bak。
设备1和设备2对FlexE Group同步调整之后，GR/GA/G重新切换回0，确保每次调整FlexE Group，起始状态都是该默认状态。也就是说，GR/GA/G正常运行时保持一致，只有FlexE Group调整时才会有不同。其中，PHY#A/B的FlexE Group Number Bak也可以改变。例如在GR＝1时，将PHY#A/B/C对应的FlexE Group Number Bak都换成Y。多个PHY可以一起加入某一个FlexE Group。方法相同，此处不再赘述。
接下来，参见图12所示的系统，以将第一网络设备称为设备1，第二网络设备称为设备2，以设备1发起Group更改，从PHY#A、PHY#B、PHY#C组成的FlexE Group X中，移除PHY#C为例，对本申请实施例提供的灵活以太网组的管理方法进行举例说明。从FlexE Group X删除PHY#C前，需要完成判断：当前Client业务流的总流量是否可以由PHY#A和PHY#B来支撑。如果PHY#A+PHY#B总带宽小于Client业务流的总流量，需要提出告警，告知用户该调整(从Group X删除PHY#C)将会影响业务流。如果PHY#A+PHY#B可以支撑Client业务流的总流量，则需要先进行Calendar切换，将Client业务流都放到PHY#A+PHY#B里。
完成上述步骤后，将进行FlexE Group调整，步骤如图13所示。其中，删除PHY#A和B组成的FlexE Group，其FlexE Group Number可以改变，例如将FlexE Group Number改为Z，Z！＝Y，即Z不等于Y。如图13所示，包括但不限于如下几步。
第一步：GR＝1，设备1修改PHY#C的FlexE Group Number Bak，PHY#A和PHY#B中的FlexE Map Bak刷新，以将PHY#C的信息从FlexE Map Bak中删除。此外，PHY#C中的FlexE Map Bak刷新，PHY#C中的FlexE Map Bak刷新之后仅包括PHY#C本身，对应的PHY#C的FlexE Instance Number Bak无需更改。
第二步：设备2通过PHY#A/B/C反馈GA＝1，表示PHY#A/B/C均接收完毕FlexE Map Bak的刷新，并且PHY#C可以接收新的Group Number Y，并使用Y在PHY#C的FlexE Group Number Bak位域进行传输。
第三步：G＝1，从下一个复帧头开始，设备1和设备2按照PHY#A/B组成FlexE Group X传递FlexE Clients业务流。而PHY#C独立成为FlexE Group Y。
第四步：设备2将FlexE Group Number复制为FlexE Group Number Bak，将FlexE Map复制为FlexE Map Bak。
设备1和设备2对FlexE Group同步调整之后，GR/GA/G重新切换回0，确保每次调整FlexE Group，起始状态都是在同一状态下开始。也就是说，GR/GA/G正常运行时保持一致，只有FlexE Group调整时才会有不同。此外，需要说明的是，在切换过程中，各个PHY中的FlexE Instance Number无需更改，但也可以根据需要修改，本申请实施例对此不加以限定。
以图14所示系统为例，将第一网络设备称为设备1，将第二网络设备称为设备2，由设备1发起FlexE Group更改，将PHY#A、PHY#B、PHY#C、PHY#D组成的FlexE Group X，分割为PHY#A和PHY#B组成的FlexE Group Y，以及PHY#C和PHY#D组成的FlexE Group Z。结合上述图13，分割操作和删除PHY操作有类似之处。
在分割之前，此时需要预判Client业务流是否可以在不被影响的情况下完成FlexE Group分割。例如，假设PHY速率100G；如果Client业务流可以被分为两份，每一份都可以在2x100G带宽内容纳，则可以进行无损分割。否则需要告警。操作过程如图15所示，包括但不限于如下几步。
第一步：GR＝1，设备1修改PHY#A/B/C的FlexE Group Number Bak，PHY#A/B的FlexE Group Number Bak使用Y，PHY#C/D的FlexE Group Number Bak使用Z。由此，将PHY#A/B分割为一个FlexE Group，将PHY#C/D分割为一个FlexE Group。此外，该PHY#A/B/C/D中的FlexE Map Bak刷新，例如，PHY#A/B的FlexE Map Bak包括PHY#A/B的信息，PHY#C/D的FlexE Map  Bak包括PHY#C/D的信息。其中，PHY#A/B/C/D中的Instance Number Bak无需更改。
第二步：设备2通过PHY#A/B/C/D反馈GA＝1，表示A/B/C/D均接收完毕FlexE Map Bak的刷新，并且可以接收新的Group Number Y/Z。
第三步：G＝1，从下一个复帧头开始，设备1和设备2按照PHY#A/B组成FlexE Group Y、PHY#C/D组成FlexE Group Z传输对应的FlexE Clients业务流。
第四步：PHY#A/B/C/D中的Group Number复制FlexE Group Number Bak，FlexE Map复制FlexE Map Bak。
设备1和设备2对FlexE Group同步调整之后，GR/GA/G重新切换回0，确保每次调整FlexE Group，起始状态都是在以Block#1中Group Number开始。也就是说，GR/GA/G正常运行时保持一致，只有FlexE Group调整时才会有不同。
除上述采用开销块中的预留位来携带需要调整的目标灵活以太网组的配置信息外，在示例性实施例中，由于FlexE开销中存在管理通道，如图3或图4中block#4～8所示。需要调整的FlexE Group的配置信息也可以由管理通道之间进行协商。管理通道中可以承载多种协议，以通过管理通道承载以太报文，通过该以太报文协商FlexE Group配置信息为例：
定义128字节报文，其中payload位域46+64＝110字节，包括：
1)20bit当前FlexE Group Number(optional)
2)20bit新FlexE Group Number(可以和旧的相同)
3)56bit来表示FlexE Map位域
4)96bit切换时间点(可以某个PTP时戳为参考)
5)至少2bit来表示GR/GA信息
通过管理通道来携带需要调整的目标灵活以太网组的配置信息的方式，可以不需要如图6或图7所示的3bit GGG来表示是否切换，但本申请实施例对此不加以限定，不排除使用该3bitGGG的方案。该实施例协商配置信息的过程详见图16，包括但不限于如下几步：
第一步：FlexE Group中的TX向RX发送Request报文，以通过该Request报文发送备用FlexE Group Number，并发送新FlexE Map信息。此外，TX和RX约定切换的时刻，即约定同步调整FlexE Group的时间。其中，GR＝0，G＝1。
第二步：RX向TX发送Acknowledge报文，接收完毕备用FlexE Group Number，并更新完毕FlexE Map。GA＝0。
第三步：设备1向设备2发送Request_follow_up报文，通知对端何时切换，即何时对需要调整的FlexE Group进行调整。
第四步：约定时刻到达之后的复帧头，进行切换。
其中，约定的时间切换点需要以某个开销帧头或开销复帧头为界。如果时间点对应不到该边界，需要往后顺延到下一个边界。此外，图16涉及的对FlexE Group进行调整，包括但不限于在需要调整的目标灵活以太网组中新增物理层链路、将需要调整的目标灵活以太网组中已有的物理层链路进行删除以及将需要调整的目标灵活以太网组进行分割等调整方式中的一种或多种，每种调整方式可参见上述对应的实施例，本申请实施例对采用管理通道来协商目标灵活以太网组的配置信息的方式下的调整过程不做限定。与通过开销块中的预留位来携带目标灵活以太网组的配置信息的方式相比，该方案优势是不需要使用开销中的保留位域。管 理通道带宽资源相对开销块保留位域更为丰富。
除上述几种实例外，本申请实施例提供的方法还支持采用Management System/SDN controller配置两端，进行同步切换。以第一网络设备为设备1，第二网络设备为设备2，通过上层管理，分别与设备1和设备2的管理接口联系，下发需要适配的FlexE Group信息，即通过上层控制器来向设备1和设备2下发需要调整的目标灵活以太网的配置信息，以配置信息包括但不限于新的FlexE Group Number，FlexE Map等为例，对本申请实施例提供的方法进行举例说明。
如图17所示，该方案可以与图11、图13、图15、图16所示实施例联合使用。例如，结合图11、图13或图15所示实施例，SDN controller下发配置完毕并确认成功后，令两端同时进行G比特的切换，即设备1和设备2同步进行Group的调整。例如，结合图16所示实施例，通过以管理通道承载报文的形式下发配置完毕并确认成功后，可以通过发送切换时间戳进行切换。
此外，图17所示方案除了结合图11、图13或图15所示实施例实现灵活以太网组的管理，或者结合图16所示实施例实现灵活以太网组的管理之外，该图7所示方案还可以单独使用，可以采用覆盖(override)两设备的告警机制进行强制切换。
参见图18，提供了一种灵活以太网组的管理装置，该装置应用于第一网络设备，装置包括：
确定模块1501，用于确定需要调整的目标灵活以太网组的配置信息，目标灵活以太网组的配置信息包括目标灵活以太网组的备用灵活以太网组号和备用灵活以太图，备用灵活以太图包括目标灵活以太网组内的物理层链路信息；
调整模块1502，用于基于目标灵活以太网组的配置信息，与第二网络设备同步进行目标灵活以太网组的调整，第二网络设备通过目标灵活以太网组内的物理层链路与第一网络设备通信。
在示例性实施例中，确定模块1501，用于与第二网络设备通过开销块协商需要调整的目标灵活以太网组的配置信息，开销块携带目标灵活以太网组的配置信息。
在示例性实施例中，开销块的保留位域字段携带目标灵活以太网组的配置信息，或者，开销块的管理通道字段携带目标灵活以太网组的配置信息。
在示例性实施例中，确定模块1501，用于接收控制器向第一网络设备和第二网络设备发送的需要调整的目标灵活以太网组的配置信息。
在示例性实施例中，该确定模块1501，还用于当目标灵活以太网组内需要增加新的物理层链路时，备用灵活以太图包括新的物理层链路信息，确定新的物理层链路有效；
调整模块1502，用于响应于新的物理层链路有效，执行基于目标灵活以太网组的配置信息，与第二网络设备同步进行目标灵活以太网组的调整的操作。
在示例性实施例中，新的物理层链路有效，满足如下条件：新的物理层链路是独立的物理层链路，新的物理层链路与目标灵活以太网组内已有的物理层链路无冲突，新的物理层链路与目标灵活以太网组内已有的物理层链路的相位能够对齐。
在示例性实施例中，确定模块1501，还用于当目标灵活以太网组内的目标物理层链路需要被删除时，备用灵活以太图不包括目标物理层链路信息，确定删除目标物理层链路之后的 目标灵活以太网组可支撑当前流量；
调整模块1502，用于响应于删除目标物理层链路之后的目标灵活以太网组可支撑当前流量，执行基于目标灵活以太网组的配置信息，与第二网络设备同步进行目标灵活以太网组的调整的操作。
在示例性实施例中，确定模块1501，还用于当目标灵活以太网组内的物理层链路需要被重新分组时，备用灵活以太网组号包括重新分组后的灵活以太网组的网组号，备用灵活以太图包括重新分组后的物理层链路信息，确定重新分组后的灵活以太网组可支撑对应的业务流；
调整模块1502，用于响应于重新分组之后的灵活以太网组可支撑对应的业务流，执行基于目标灵活以太网组的配置信息，与第二网络设备同步进行目标灵活以太网组的调整的操作。
在示例性实施例中，调整模块1502，用于和第二网络设备协商调整时间，当到达调整时间时，基于目标灵活以太网组的配置信息，与第二网络设备同步进行目标灵活以太网组的调整。
参见图19，提供了一种灵活以太网组的管理装置，该装置应用于第二网络设备，装置包括：
确定模块1601，用于确定需要调整的目标灵活以太网组的配置信息，目标灵活以太网组的配置信息包括目标灵活以太网组的备用灵活以太网组号和备用灵活以太图，备用灵活以太图包括目标灵活以太网组内的物理层链路信息；
调整模块1602，用于基于目标灵活以太网组的配置信息，与第一网络设备同步进行目标灵活以太网组的调整，第一网络设备通过目标灵活以太网组内的物理层链路与第二网络设备通信。
在示例性实施例中，确定模块1601，用于与第一网络设备通过开销块协商需要调整的目标灵活以太网组的配置信息，开销块携带目标灵活以太网组的配置信息。
在示例性实施例中，开销块的保留位域字段携带目标灵活以太网组的配置信息，或者，开销块的管理通道字段携带目标灵活以太网组的配置信息。
在示例性实施例中，确定模块1601，用于接收控制器向第二网络设备和第一网络设备发送的需要调整的目标灵活以太网组的配置信息。
在示例性实施例中，调整模块1602，用于和第一网络设备协商调整时间，当到达调整时间时，基于目标灵活以太网组的配置信息，与第一网络设备同步进行目标灵活以太网组的调整。
应理解的是，上述图18和图19提供的装置在实现其功能时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将设备的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的装置与方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
参见图20，本申请实施例还提供一种灵活以太网组的管理设备1000，图20所示的灵活以太网组的管理设备1000用于执行上述灵活以太网组的管理方法所涉及的操作。该灵活以太 网组的管理设备1000包括：存储器1001、处理器1002及接口1003，存储器1001、处理器1002及接口1003之间通过总线1004连接。
其中，存储器1001中存储有计算机程序或至少一条指令，计算机程序或至少一条指令由处理器1002加载并执行，以实现上述任一所述的灵活以太网组的管理方法。
接口1003用于与网络中的其他设备进行通信，该接口1003可以通过无线或有线的方式实现，示例性地，该接口1003可以是网卡。例如，灵活以太网组的管理设备1000可通过该接口1003与服务器进行通信。
例如，图20所示的网络设备为图5、图10-图17中的第一网络设备，处理器1002读取存储器1001中的计算机程序或指令，使图20所示的网络设备能够执行第一网络设备所执行的全部或部分操作。
又例如，图20所示的网络设备为图5、图10-图17中的第二网络设备，处理器1002读取存储器1001中的计算机程序或指令，使图20所示的网络设备能够执行第二网络设备所执行的全部或部分操作。
应理解的是，图20仅仅示出了灵活以太网组的管理设备1000的简化设计。在实际应用中，灵活以太网组的管理设备1000可以包含任意数量的接口，处理器或者存储器。此外，上述处理器可以是中央处理器(Central Processing Unit，CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processing，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field－programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者是任何常规的处理器等。值得说明的是，处理器可以是支持进阶精简指令集机器(advanced RISC machines，ARM)架构的处理器。
进一步地，在一种可选的实施例中，上述存储器可以包括只读存储器和随机存取存储器，并向处理器提供计算机程序/指令和数据。存储器还可以包括非易失性随机存取存储器。例如，存储器还可以存储设备类型的信息。
该存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者，其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用。例如，静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic random access memory，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data date SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
还提供了一种灵活以太网组的管理系统，该系统包括第一网络设备第二网络设备；
第一网络设备用于执行图5、图10-图17中任一所述的第一网络设备所执行的方法，第二网络设备用于执行图5、图10-图17中任一所述的第二网络设备所执行的方法。
还提供了一种计算机可读存储介质，存储介质中存储有计算机程序或至少一条指令，计 算机程序或指令由处理器加载并执行以实现如上任一所述的灵活以太网组的管理方法。
本申请提供了一种计算机程序，当计算机程序被计算机执行时，可以使得处理器或计算机执行上述方法实施例中对应的各个操作和/或流程。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk)等。
以上所述仅为本申请的实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (35)

  1. 一种灵活以太网组的管理方法，其特征在于，所述方法包括：
    第一网络设备确定需要调整的目标灵活以太网组的配置信息，所述目标灵活以太网组的配置信息包括所述目标灵活以太网组的备用灵活以太网组号和备用灵活以太图，所述备用灵活以太图包括所述目标灵活以太网组内的物理层链路信息；
    所述第一网络设备基于所述目标灵活以太网组的配置信息，与第二网络设备同步进行所述目标灵活以太网组的调整，所述第二网络设备通过所述目标灵活以太网组内的物理层链路与所述第一网络设备通信。
  2. 根据权利要求1所述的方法，其特征在于，所述第一网络设备确定需要调整的目标灵活以太网组的配置信息，包括：
    所述第一网络设备与所述第二网络设备通过开销块协商需要调整的目标灵活以太网组的配置信息，所述开销块携带所述目标灵活以太网组的配置信息。
  3. 根据权利要求2所述的方法，其特征在于，所述开销块的保留位域字段携带所述目标灵活以太网组的配置信息，或者，所述开销块的管理通道字段携带所述目标灵活以太网组的配置信息。
  4. 根据权利要求1所述的方法，其特征在于，所述第一网络设备确定需要调整的目标灵活以太网组的配置信息，包括：
    所述第一网络设备接收控制器向所述第一网络设备和所述第二网络设备发送的需要调整的目标灵活以太网组的配置信息。
  5. 根据权利要求1-4任一所述的方法，其特征在于，所述第一网络设备确定需要调整的目标灵活以太网组的配置信息之后，还包括：
    当所述目标灵活以太网组内需要增加新的物理层链路时，所述备用灵活以太图包括所述新的物理层链路信息，所述第一网络设备确定所述新的物理层链路有效；
    响应于所述新的物理层链路有效，所述第一网络设备执行基于所述目标灵活以太网组的配置信息，与第二网络设备同步进行所述目标灵活以太网组的调整的操作。
  6. 根据权利要求5所述的方法，其特征在于，所述新的物理层链路有效，满足如下条件：
    所述新的物理层链路是独立的物理层链路，
    所述新的物理层链路与所述目标灵活以太网组内已有的物理层链路无冲突，
    所述新的物理层链路与目标灵活以太网组内已有的物理层链路的相位能够对齐。
  7. 根据权利要求1-4任一所述的方法，其特征在于，所述第一网络设备确定需要调整的目标灵活以太网组的配置信息之后，还包括：
    当所述目标灵活以太网组内的目标物理层链路需要被删除时，所述备用灵活以太图不包括所述目标物理层链路信息，所述第一网络设备确定删除所述目标物理层链路之后的目标灵活以太网组可支撑当前流量；
    响应于删除所述目标物理层链路之后的目标灵活以太网组可支撑当前流量，所述第一网络设备执行基于所述目标灵活以太网组的配置信息，与第二网络设备同步进行所述目标灵活以太网组的调整的操作。
  8. 根据权利要求1-4任一所述的方法，其特征在于，所述第一网络设备确定需要调整的目标灵活以太网组的配置信息之后，还包括：
    当所述目标灵活以太网组内的物理层链路需要被重新分组时，所述备用灵活以太网组号包括重新分组后的灵活以太网组的网组号，所述备用灵活以太图包括重新分组后的物理层链路信息，所述第一网络设备确定重新分组后的灵活以太网组可支撑对应的业务流；
    响应于重新分组之后的灵活以太网组可支撑对应的业务流，所述第一网络设备执行基于所述目标灵活以太网组的配置信息，与第二网络设备同步进行所述目标灵活以太网组的调整的操作。
  9. 根据权利要求1-8任一所述的方法，其特征在于，所述第一网络设备基于所述目标灵活以太网组的配置信息，与第二网络设备同步进行所述目标灵活以太网组的调整，包括：
    所述第一网络设备和所述第二网络设备协商调整时间，当到达所述调整时间时，所述第一网络设备基于所述目标灵活以太网组的配置信息，与所述第二网络设备同步进行所述目标灵活以太网组的调整。
  10. 一种灵活以太网组的管理方法，其特征在于，所述方法包括：
    第二网络设备确定需要调整的目标灵活以太网组的配置信息，所述目标灵活以太网组的配置信息包括所述目标灵活以太网组的备用灵活以太网组号和备用灵活以太图，所述备用灵活以太图包括所述目标灵活以太网组内的物理层链路信息；
    所述第二网络设备基于所述目标灵活以太网组的配置信息，与第一网络设备同步进行所述目标灵活以太网组的调整，所述第一网络设备通过所述目标灵活以太网组内的物理层链路与所述第二网络设备通信。
  11. 根据权利要求10所述的方法，其特征在于，所述第二网络设备确定需要调整的目标灵活以太网组的配置信息，包括：
    所述第二网络设备与所述第一网络设备通过开销块协商需要调整的目标灵活以太网组的配置信息，所述开销块携带所述目标灵活以太网组的配置信息。
  12. 根据权利要求11所述的方法，其特征在于，所述开销块的保留位域字段携带所述目标灵活以太网组的配置信息，或者，所述开销块的管理通道字段携带所述目标灵活以太网组的配置信息。
  13. 根据权利要求10所述的方法，其特征在于，所述第二网络设备确定需要调整的目标灵活以太网组的配置信息，包括：
    所述第二网络设备接收控制器向所述第二网络设备和所述第一网络设备发送的需要调整的目标灵活以太网组的配置信息。
  14. 根据权利要求10-13任一所述的方法，其特征在于，所述第二网络设备基于所述目标灵活以太网组的配置信息，与第一网络设备同步进行所述目标灵活以太网组的调整，包括：
    所述第二网络设备和所述第一网络设备协商调整时间，当到达所述调整时间时，所述第二网络设备基于所述目标灵活以太网组的配置信息，与所述第一网络设备同步进行所述目标灵活以太网组的调整。
  15. 一种灵活以太网组的管理装置，其特征在于，所述装置应用于第一网络设备，所述装置包括：
    确定模块，用于确定需要调整的目标灵活以太网组的配置信息，所述目标灵活以太网组的配置信息包括所述目标灵活以太网组的备用灵活以太网组号和备用灵活以太图，所述备用灵活以太图包括所述目标灵活以太网组内的物理层链路信息；
    调整模块，用于基于所述目标灵活以太网组的配置信息，与第二网络设备同步进行所述目标灵活以太网组的调整，所述第二网络设备通过所述目标灵活以太网组内的物理层链路与所述第一网络设备通信。
  16. 根据权利要求15所述的装置，其特征在于，所述确定模块，用于与所述第二网络设备通过开销块协商需要调整的目标灵活以太网组的配置信息，所述开销块携带所述目标灵活以太网组的配置信息。
  17. 根据权利要求16所述的装置，其特征在于，所述开销块的保留位域字段携带所述目标灵活以太网组的配置信息，或者，所述开销块的管理通道字段携带所述目标灵活以太网组的配置信息。
  18. 根据权利要求15所述的装置，其特征在于，所述确定模块，用于接收控制器向所述第一网络设备和所述第二网络设备发送的需要调整的目标灵活以太网组的配置信息。
  19. 根据权利要求15-18任一所述的装置，其特征在于，所述确定模块，还用于当所述目标灵活以太网组内需要增加新的物理层链路时，所述备用灵活以太图包括所述新的物理层链路信息，确定所述新的物理层链路有效；
    所述调整模块，用于响应于所述新的物理层链路有效，执行基于所述目标灵活以太网组的配置信息，与第二网络设备同步进行所述目标灵活以太网组的调整的操作。
  20. 根据权利要求19所述的装置，其特征在于，所述新的物理层链路有效，满足如下条件：所述新的物理层链路是独立的物理层链路，所述新的物理层链路与所述目标灵活以太网 组内已有的物理层链路无冲突，所述新的物理层链路与目标灵活以太网组内已有的物理层链路的相位能够对齐。
  21. 根据权利要求15-18任一所述的装置，其特征在于，所述确定模块，还用于当所述目标灵活以太网组内的目标物理层链路需要被删除时，所述备用灵活以太图不包括所述目标物理层链路信息，确定删除所述目标物理层链路之后的目标灵活以太网组可支撑当前流量；
    所述调整模块，用于响应于删除所述目标物理层链路之后的目标灵活以太网组可支撑当前流量，执行基于所述目标灵活以太网组的配置信息，与第二网络设备同步进行所述目标灵活以太网组的调整的操作。
  22. 根据权利要求15-18任一所述的装置，其特征在于，所述确定模块，还用于当所述目标灵活以太网组内的物理层链路需要被重新分组时，所述备用灵活以太网组号包括重新分组后的灵活以太网组的网组号，所述备用灵活以太图包括重新分组后的物理层链路信息，确定重新分组后的灵活以太网组可支撑对应的业务流；
    所述调整模块，用于响应于重新分组之后的灵活以太网组可支撑对应的业务流，执行基于所述目标灵活以太网组的配置信息，与第二网络设备同步进行所述目标灵活以太网组的调整的操作。
  23. 根据权利要求15-22任一所述的装置，其特征在于，所述调整模块，用于和所述第二网络设备协商调整时间，当到达所述调整时间时，基于所述目标灵活以太网组的配置信息，与所述第二网络设备同步进行所述目标灵活以太网组的调整。
  24. 一种灵活以太网组的管理装置，其特征在于，所述装置应用于第二网络设备，所述装置包括：
    确定模块，用于确定需要调整的目标灵活以太网组的配置信息，所述目标灵活以太网组的配置信息包括所述目标灵活以太网组的备用灵活以太网组号和备用灵活以太图，所述备用灵活以太图包括所述目标灵活以太网组内的物理层链路信息；
    调整模块，用于基于所述目标灵活以太网组的配置信息，与第一网络设备同步进行所述目标灵活以太网组的调整，所述第一网络设备通过所述目标灵活以太网组内的物理层链路与所述第二网络设备通信。
  25. 根据权利要求24所述的装置，其特征在于，所述确定模块，用于与所述第一网络设备通过开销块协商需要调整的目标灵活以太网组的配置信息，所述开销块携带所述目标灵活以太网组的配置信息。
  26. 根据权利要求25所述的装置，其特征在于，所述开销块的保留位域字段携带所述目标灵活以太网组的配置信息，或者，所述开销块的管理通道字段携带所述目标灵活以太网组的配置信息。
  27. 根据权利要求24所述的装置，其特征在于，所述确定模块，用于接收控制器向所述第二网络设备和所述第一网络设备发送的需要调整的目标灵活以太网组的配置信息。
  28. 根据权利要求24-27任一所述的装置，其特征在于，所述调整模块，用于和所述第一网络设备协商调整时间，当到达所述调整时间时，基于所述目标灵活以太网组的配置信息，与所述第一网络设备同步进行所述目标灵活以太网组的调整。
  29. 一种网络设备，其特征在于，所述网络设备包括：
    存储器及处理器，所述存储器中存储有至少一条指令，所述至少一条指令由所述处理器加载并执行，以实现权利要求1-9中任一所述的方法。
  30. 一种网络设备，其特征在于，所述网络设备包括：
    存储器及处理器，所述存储器中存储有计算机程序或至少一条指令，所述计算机程序或至少一条指令由所述处理器加载并执行，以实现权利要求10-14中任一所述的方法。
  31. 一种灵活以太网组的管理系统，其特征在于，所述系统包括第一网络设备和第二网络设备，所述第一网络设备用于执行所述权利要求1-9中任一所述的方法，所述第二网络设备用于执行所述权利要求10-14中任一所述的方法。
  32. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序或至少一条指令，所述计算机程序或指令由处理器加载并执行以实现如权利要求1-14中任一所述的方法。
  33. 一种计算机程序产品，其特征在于，包括：计算机程序代码，当所述计算机程序代码被计算机运行时，使得所述计算机执行权利要求1-14中任一所述的方法。
  34. 一种芯片，包括处理器，用于从存储器中调用并运行所述存储器中存储的指令，使得安装有所述芯片的通信设备执行权利要求1-14中任一所述的方法。
  35. 根据权利要求34所述的芯片，其特征在于，还包括输入接口、输出接口，所述输入接口、输出接口、所述处理器以及所述存储器之间通信连接。
PCT/CN2020/119066 2019-12-06 2020-09-29 灵活以太网组的管理方法、设备及计算机可读存储介质 WO2021109705A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20896202.7A EP4054124A4 (en) 2019-12-06 2020-09-29 METHOD AND DEVICE FOR FLEXIBLE ETHERNET GROUP MANAGEMENT AND COMPUTER READABLE STORAGE MEDIA
US17/831,158 US11838181B2 (en) 2019-12-06 2022-06-02 Flexible ethernet group management method, device, and computer-readable storage medium

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201911244655 2019-12-06
CN201911244655.2 2019-12-06
CN201911412030.2 2019-12-31
CN201911412030.2A CN112929199A (zh) 2019-12-06 2019-12-31 灵活以太网组的管理方法、设备及计算机可读存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/831,158 Continuation US11838181B2 (en) 2019-12-06 2022-06-02 Flexible ethernet group management method, device, and computer-readable storage medium

Publications (1)

Publication Number Publication Date
WO2021109705A1 true WO2021109705A1 (zh) 2021-06-10

Family

ID=76162206

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/119066 WO2021109705A1 (zh) 2019-12-06 2020-09-29 灵活以太网组的管理方法、设备及计算机可读存储介质

Country Status (4)

Country Link
US (1) US11838181B2 (zh)
EP (1) EP4054124A4 (zh)
CN (1) CN112929199A (zh)
WO (1) WO2021109705A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113364707A (zh) * 2021-08-10 2021-09-07 国网江苏省电力有限公司信息通信分公司 资源分配方法、装置、存储介质以及电子设备
CN115941792A (zh) * 2022-11-30 2023-04-07 苏州异格技术有限公司 灵活以太网的数据块的处理方法及装置、存储介质

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115695190A (zh) * 2021-07-26 2023-02-03 中兴通讯股份有限公司 灵活以太网时隙协商方法、接收端、发送端及存储介质
CN114615136B (zh) * 2022-03-04 2023-10-27 浙江国盾量子电力科技有限公司 一种5G智能电网切片的FlexE接口管理方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108243120A (zh) * 2016-12-26 2018-07-03 北京华为数字技术有限公司 基于灵活以太网的业务流传输方法、装置和通信系统
CN108632061A (zh) * 2017-03-20 2018-10-09 华为技术有限公司 一种带宽调整方法及装置
CN109688016A (zh) * 2019-01-25 2019-04-26 中兴通讯股份有限公司 灵活以太网协议中切换时隙配置的方法及相关设备
US20190173856A1 (en) * 2015-12-11 2019-06-06 Ciena Corporation Flexible ethernet encryption systems and methods
CN109981208A (zh) * 2017-12-27 2019-07-05 华为技术有限公司 基于灵活以太网FlexE传输业务流的方法和装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10135760B2 (en) * 2015-06-30 2018-11-20 Ciena Corporation Flexible Ethernet chip-to-chip inteface systems and methods
CN110719182B (zh) * 2018-07-12 2021-11-16 中兴通讯股份有限公司 一种链路容量的调整方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190173856A1 (en) * 2015-12-11 2019-06-06 Ciena Corporation Flexible ethernet encryption systems and methods
CN108243120A (zh) * 2016-12-26 2018-07-03 北京华为数字技术有限公司 基于灵活以太网的业务流传输方法、装置和通信系统
CN108632061A (zh) * 2017-03-20 2018-10-09 华为技术有限公司 一种带宽调整方法及装置
CN109981208A (zh) * 2017-12-27 2019-07-05 华为技术有限公司 基于灵活以太网FlexE传输业务流的方法和装置
CN109688016A (zh) * 2019-01-25 2019-04-26 中兴通讯股份有限公司 灵活以太网协议中切换时隙配置的方法及相关设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4054124A4

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113364707A (zh) * 2021-08-10 2021-09-07 国网江苏省电力有限公司信息通信分公司 资源分配方法、装置、存储介质以及电子设备
CN115941792A (zh) * 2022-11-30 2023-04-07 苏州异格技术有限公司 灵活以太网的数据块的处理方法及装置、存储介质
CN115941792B (zh) * 2022-11-30 2024-02-02 苏州异格技术有限公司 灵活以太网的数据块的处理方法及装置、存储介质

Also Published As

Publication number Publication date
EP4054124A4 (en) 2023-01-04
EP4054124A1 (en) 2022-09-07
CN112929199A (zh) 2021-06-08
US20220337477A1 (en) 2022-10-20
US11838181B2 (en) 2023-12-05

Similar Documents

Publication Publication Date Title
WO2021109705A1 (zh) 灵活以太网组的管理方法、设备及计算机可读存储介质
US11469844B2 (en) Method and apparatus for transmitting service flow based on flexible ethernet FlexE
WO2018090856A1 (zh) 用于建立灵活以太网群组的方法和设备
US11843452B2 (en) Clock synchronization method and apparatus
WO2019228428A1 (zh) 灵活以太网中调整传输通道的带宽方法和装置
US11271668B2 (en) Data transmission methods, apparatuses, devices, and system
WO2022042743A1 (zh) 数据传输方法和装置、电子设备、计算机可读介质
US20240107366A1 (en) METHOD OF CREATING QoS FLOW FOR TIME SYNCHRONIZATION PROTOCOL IN WIRELESS COMMUNICATION NETWORK
WO2020078203A1 (zh) 数据传输方法、装置及设备
CN105610727B (zh) 一种网络数据传输方法及装置
WO2021169289A1 (zh) 灵活以太网组的绑定方法、设备及计算机可读存储介质
JP7305882B2 (ja) スロットネゴシエーション方法およびデバイス
US20230035379A1 (en) Service flow adjustment method and communication apparatus
EP3923511A1 (en) Clock synchronization message interacting method and apparatus
EP4283888A1 (en) Communication method, device, and chip system
WO2019100982A1 (zh) 数据传输方法和设备
US20230291537A1 (en) Network Synchronization Method, Apparatus, Device, and System, and Readable Storage Medium
US20230209517A1 (en) Resource Configuration Method and Communication Apparatus
US11546221B2 (en) Link capacity adjustment method and device
US20240146433A1 (en) Time slot allocation processing method, device and storage medium
CN104767605A (zh) 一种工业以太网中的同步方法及设备
CN114338831A (zh) 一种网关通信方法、通信设备和存储介质
EP2798790B1 (en) Compression method for tdm frames in a packet network
WO2023226878A1 (zh) 一种带宽调整方法、装置及存储介质
WO2024046465A1 (zh) 一种传输数据的方法和装置

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: 20896202

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020896202

Country of ref document: EP

Effective date: 20220603

NENP Non-entry into the national phase

Ref country code: DE