WO2022133938A1 - 一种灵活以太网开销帧处理方法及装置 - Google Patents

一种灵活以太网开销帧处理方法及装置 Download PDF

Info

Publication number
WO2022133938A1
WO2022133938A1 PCT/CN2020/139132 CN2020139132W WO2022133938A1 WO 2022133938 A1 WO2022133938 A1 WO 2022133938A1 CN 2020139132 W CN2020139132 W CN 2020139132W WO 2022133938 A1 WO2022133938 A1 WO 2022133938A1
Authority
WO
WIPO (PCT)
Prior art keywords
overhead frame
phase
phy
frame
board
Prior art date
Application number
PCT/CN2020/139132
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 EP20966510.8A priority Critical patent/EP4254843A4/en
Priority to PCT/CN2020/139132 priority patent/WO2022133938A1/zh
Priority to CN202080108101.4A priority patent/CN116746093A/zh
Publication of WO2022133938A1 publication Critical patent/WO2022133938A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/40169—Flexible bus arrangements
    • H04L12/40176—Flexible bus arrangements involving redundancy
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/22—Arrangements for detecting or preventing errors in the information received using redundant apparatus to increase reliability

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method and device for processing a flexible Ethernet overhead frame.
  • Flexible ethernet (FlexE) technology is based on high-speed Ethernet (ethernet) interface, through the ethernet media access control (media access control, MAC) layer and physical layer decoupling to achieve low-cost, high-reliability carrier-class interface technology.
  • FlexE technology realizes the decoupling of the MAC layer and the physical layer by introducing a flexible Ethernet slicing (FlexE shim) layer on the basis of IEEE802.3, thereby realizing flexible rate matching.
  • FlexE technology meets the port application requirements of flexible bandwidth by binding multiple Ethernet physical layers (PHYs) into a flexible Ethernet group (FlexE group) and physical layer channelization. Therefore, the MAC rate provided by FlexE can be greater than that of a single PHY (achieved by bundling) or less than that of a single PHY (achieved by channelization).
  • the network device mainly implements the transmission of service data streams through the protection switching mechanism of the main board and the standby board. Specifically, both the main board and the backup board in the network device send service data streams through the FlexE group; when the main board is working normally, the switch selects the service data stream carried on the FlexE group of the main board to send to other devices; When one or more PHYs in the FlexE group of the main board are in a fault state, the switch selects the service data stream carried on the FlexE group of the standby board to send to other devices.
  • the above protection switching mechanism will cause interruption of the service data flow carried by the normally working PHY in the FlexE group of the main board, and the interruption duration may reach several tens of milliseconds, thus causing damage to the service data flow carried by the normally working PHY. Therefore, how to reduce the impact of the PHY in the faulty state on the service data flow carried by the PHY in the normal state in the FlexE group has become an urgent problem to be solved at present.
  • the present application provides a flexible Ethernet overhead frame processing method and device, which are used to reduce the impact of a PHY in a fault state on a service data stream carried by a PHY in a normal state in a FlexE group.
  • a first aspect provides a flexible Ethernet overhead frame processing method, which is applied to a network device including a main board and a backup board.
  • the method includes: the main board sends first indication information to the backup board, and the first indication information is used to indicate The phase of the first overhead frame of the service data stream carried on the first physical layer interface PHY of the mainboard, the mainboard and the network may correspond to the first FlexE group, may include multiple PHYs, and the first PHY may be the first FlexE Any one of the multiple PHYs bound by the group; the standby board receives the first indication information, and determines the second overhead frame of the service data stream carried on the second PHY of the standby board according to the phase of the first overhead frame phase, the second overhead frame is the next overhead frame of the first overhead frame; wherein, the standby board and the network may correspond to the second FlexE group, and the second PHY may be one of the multiple PHYs bound to the second FlexE group One PHY for carrying the service data stream, that is, the service data stream borne by the second
  • the phase of the overhead frame of the service data stream on the standby board can be tracked. Align the phase of the overhead frame of the service data flow on the main board.
  • the first network device can send the service data stream to the second network device through the backup board, because the phases of the overhead frames of the service data stream sent by the main board and the backup board are aligned , so that the second network device can still lock the overhead frames in the service data stream, thereby reducing the influence of damage to service data streams on other normally working PHYs due to the failure of one PHY in the mainboard.
  • the method further includes: when the mainboard does not fail, the mainboard sends the service data stream in the phase of the first overhead frame on the first PHY; when the mainboard fails In the event of a failure, the standby board sends the service data stream on the second PHY in the phase of the second overhead frame.
  • the first network device can send the service data flow to the second network device through the backup board, because the main board and the backup board send the overhead frame of the service data flow.
  • the phases are aligned, so that the second network device can still lock the overhead frames in the service data flow, thereby reducing the damage to the service data flow on other normal PHYs due to the failure of a PHY in the main board. influences.
  • the first indication information is information encoded in a single-bit encoding format.
  • the first indication information includes a frame header position of the first overhead frame; further, the first indication information further includes at least one of the following: an encoding version number, and feature information of the first overhead frame.
  • the first indication information further includes: a cyclic redundancy check code CRC8, where the CRC8 is used to check the encoded version number and/or feature information of the first overhead frame.
  • CRC8 cyclic redundancy check code
  • the standby board determines the phase of the second overhead frame of the service data stream carried on the second PHY on the standby board according to the phase of the first overhead frame, including: the The backup board determines the frame header position of the second overhead frame on the first PHY according to the frame header position of the first overhead frame and the overhead frame interval; and determines the backup board according to the frame header position of the second overhead frame on the first PHY
  • the method further includes: the backup board compensates the service data carried on the second PHY on the backup board according to the inter-board transmission delay and/or the codec delay Phase of the second overhead frame of the stream.
  • the phase accuracy of the second overhead frame on the standby board is improved.
  • the characteristic information includes a padding block PAD phase
  • the method further includes: determining a PAD phase of the service data stream in a second overhead frame on the second PHY according to the PAD phase and/or, the feature information further includes the AM phase of the alignment flag word, and the method further includes: determining the AM phase of the service data stream in the second overhead frame on the second PHY according to the AM phase.
  • the standby board can ensure that the PAD phase and the AM phase in the second overhead frame on the first PHY of the main board are respectively the same as the second overhead frame on the second PHY of the standby board.
  • the PAD phase and the AM phase are aligned, so as to ensure the consistency of the PAD and AM insertion of the main board and the standby board.
  • the method further includes: the standby board determines, according to the frame header of the same overhead frame of the service data stream carried on the first PHY and the second PHY, the main board and the The frame header phase deviation between the standby boards; when the frame header phase deviation is greater than the preset deviation, the standby board triggers an alarm message.
  • the standby board sends alarm information to the processor in the network device, so that overhead frames are realigned between the main board and the standby board.
  • a flexible Ethernet overhead frame processing device in a second aspect, includes a main board and a backup board; wherein the main board is used to send first indication information to the backup board, and the first indication information is used to indicate the main board.
  • the phase of the first overhead frame of the service data stream carried on the first physical layer interface PHY; the standby board is configured to receive the first indication information, and determine, according to the phase of the first overhead frame, the second PHY of the standby board. is the phase of the second overhead frame of the service data stream, where the second overhead frame is the next overhead frame of the first overhead frame.
  • the main board is further configured to send the service data stream in the phase of the first overhead frame on the first PHY when the main board is not faulty;
  • the backup board is further configured to When the main board fails, the standby board sends the service data stream in the phase of the second overhead frame on the second PHY.
  • the first indication information is information encoded in a single-bit encoding format.
  • the first indication information includes a frame header position of the first overhead frame.
  • the backup board is further configured to: determine the frame header position of the second overhead frame on the first PHY according to the frame header position of the first overhead frame and the overhead frame interval; The frame header position of the second overhead frame on the first PHY determines the phase of the second overhead frame of the service data stream carried on the second PHY on the standby board.
  • the backup board is further configured to: compensate the second overhead frame of the service data stream carried on the second PHY according to the inter-board transmission delay and/or the codec delay phase.
  • the first indication information further includes at least one of the following: an encoding version number, and feature information of the first overhead frame.
  • the first indication information further includes: a cyclic redundancy check code CRC8, where the CRC8 is used to check the encoded version number and/or feature information of the first overhead frame.
  • the feature information includes a padding block PAD phase
  • the standby board is further configured to: determine, according to the PAD phase, the service data stream in the second overhead frame on the second PHY PAD phase; and/or, the feature information further includes the AM phase of the alignment flag
  • the standby board is further configured to: determine the AM phase of the service data stream in the second overhead frame on the second PHY according to the AM phase.
  • the standby board is further configured to: determine the main board and the standby board according to the frame header of the same overhead frame of the service data stream carried on the first PHY and the second PHY Frame header phase deviation between boards; when the frame header phase deviation is greater than the preset deviation, an alarm message is triggered.
  • a readable storage medium is provided, and instructions are stored in the readable storage medium, and when the readable storage medium runs on a device, the device causes the device to execute the first aspect or any one of the first aspects possible implementations of the provided methods.
  • Another aspect of the present application provides a computer program product, which when the computer program product runs on a computer, causes the computer to execute the method provided by the first aspect or any possible implementation manner of the first aspect.
  • any of the above-mentioned devices, computer storage media or computer program products for the flexible Ethernet overhead frame processing methods are used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be achieved. With reference to the beneficial effects in the corresponding methods provided above, details are not repeated here.
  • FIG. 1 is a schematic diagram of transmitting a service data flow through a protection switching mechanism
  • FIG. 2 is a schematic diagram of a FlexE OH frame provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a FlexE group provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a 100GBASE-R FlexE multiplexer function provided by an embodiment of the present application
  • FIG. 5 is a schematic diagram of a 100GBASE-R FlexE demultiplexer function provided by an embodiment of the present application
  • FIG. 6 is a schematic diagram of an application scenario of a FlexE communication system provided by an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a method for processing a flexible Ethernet overhead frame provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of encoding of first indication information according to an embodiment of the present application.
  • FIG. 9 is a schematic flowchart of another flexible Ethernet overhead frame processing method provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of determining a phase of a second overhead frame on a second PHY according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a first network device according to an embodiment of the present application.
  • At least one means one or more
  • plural means two or more.
  • And/or which describes the association relationship of the associated objects, indicates that there can be three kinds of relationships, for example, A and/or B, which can indicate: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects are an “or” relationship.
  • At least one item(s) below” or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s).
  • At least one (a) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c may be single or multiple .
  • words such as “first” and “second” are used to distinguish the same items or similar items with basically the same functions and functions.
  • the first threshold and the second threshold are only used to distinguish different thresholds, and the sequence of the first threshold is not limited. Those skilled in the art can understand that words such as “first” and “second” do not limit the quantity and execution order.
  • an Ethernet port usually appears as a data-oriented logical concept, called a logical port or simply called a port, and an Ethernet physical interface appears as a hardware concept, called a physical interface or simply called an interface.
  • the rate of an Ethernet port is determined based on the rate of an Ethernet physical interface.
  • the maximum bandwidth of one Ethernet port corresponds to the bandwidth of one Ethernet physical interface.
  • the rate of Ethernet ports has been increased by 10 times, from 10 megabit per second (Mbps) to 100Mbps, 1000Mbps (ie 1Gbps), 10Gbps, 40Gbps , 100Gbps, 400Gbps, etc.
  • logical ports can share one or several Ethernet physical interfaces. For example, two 40GE ports and two 10GE ports share one 100G physical interface; To make flexible rate adjustments according to changes in demand, for example, from 200Gbps to 330Gbps, or from 50Gbps to 20Gbps, to improve port usage efficiency or extend its life cycle.
  • For fixed-rate physical links they can be cascaded and bundled to support stacking of logical port rates (for example, two 100GE physical interfaces can be cascaded and bundled to support 200GE logical ports).
  • FlexE supports sub-rate, channelization, inverse multiplexing and other functions for Ethernet services.
  • FlexE can support the transmission of 250G Ethernet services (MAC code stream) using three existing 100GE physical interfaces.
  • FlexE can support the transmission of 200G Ethernet services using two 100GE physical medium dependent (PMD) sublayers.
  • PMD physical medium dependent
  • FlexE can support several logical ports to use one or more physical interfaces together, and can support multiplexing multiple low-rate Ethernet services into high-rate flexible Ethernet.
  • the introduction of the sub-rate, channelization and inverse multiplexing functions of FlexE greatly expands the application scenarios of Ethernet, enhances the flexibility of Ethernet applications, and enables Ethernet technology to gradually penetrate into the field of transport networks.
  • FlexE draws on synchronous digital hierarchy (SDH)/optical transfer network (OTN) technology, constructs a fixed frame format for physical interface transmission, and divides time division multiplexing (TDM) time slots .
  • SDH synchronous digital hierarchy
  • OTN optical transfer network
  • TDM time division multiplexing
  • the following is an example of the existing FlexE frame format.
  • the TDM time slot division granularity of FlexE is 66 bits (bits), corresponding to carrying a 64B/66B bit block.
  • a FlexE frame contains 8 flexible Ethernet overhead (FlexE overhead, FlexE OH) blocks (also called OH blocks, each OH block is a 64B/66B bit block), the first FlexE OH The block is the frame header position of the FlexE OH frame, and between the FlexE OH block and the FlexE OH block is the payload area for time slot division. That is, 1023 groups of time slots, each group has 20 time slots, each time slot is 66 bits), the bandwidth of the 100GE interface is divided into 20 time slots, and the bandwidth of each time slot is about 5Gbps.
  • FIG. 2 only shows a schematic diagram of two adjacent FlexE OH blocks in one FlexE frame and a payload area between the two FlexE OH blocks.
  • FlexE implements multiple transmission channels on a single physical interface by means of interleaving and multiplexing, that is, multiple time slots.
  • Several physical interfaces can be bundled, and all the time slots of the several physical interfaces can be combined to carry one Ethernet logical port. For example, 10GE needs two time slots, 25GE needs 5 time slots, etc.
  • the 64B/66B bit blocks that can be seen on the logical port are still sequentially transmitted.
  • Each logical port corresponds to a MAC and transmits the corresponding Ethernet message.
  • the identification of the start and end of the message and the identification of idle padding are the same as those of traditional Ethernet. .
  • FlexE is only an interface technology, and the related switching technology can be implemented based on existing Ethernet packets or based on FlexE cross-connect, which will not be repeated here.
  • FlexE technology realizes the decoupling of the MAC layer and the physical layer by introducing the flexible Ethernet slicing (FlexE shim) layer on the basis of IEEE802.3, and realizes flexible rate matching.
  • FlexE can bind one or more physical layers (PHYs) together to form a FlexE group, and transmit multiple FlexE clients (FlexE clients) from different MACs through a FlexE group. client) to achieve flexible matching of Ethernet interface rates.
  • PHYs physical layers
  • FlexE clients FlexE clients
  • FlexE group It can also be called a binding group.
  • the multiple PHYs included in each FlexE group have a logical binding relationship.
  • the multiple PHYs can be physically independent, and there is no physical connection relationship.
  • the network device in FlexE can identify which PHYs are included in a FlexE group through the PHY number, so as to realize the logical bundling of multiple PHYs.
  • the number of each PHY can be identified by a number between 1-254, and 0 and 255 are reserved numbers.
  • a PHY number corresponds to a physical interface on a network device. The same number should be used between two adjacent network devices to identify the same PHY.
  • the numbers of the individual PHYs included in a FlexE group do not have to be consecutive.
  • FlexE client Corresponds to various user interfaces of the network, and is consistent with the existing Internet Protocol or traditional business interfaces in networks such as Ethernet. FlexE client can be flexibly configured according to bandwidth requirements, and supports Ethernet MAC data streams of various rates. For example, data streams can be transmitted to FlexE shim through 64B/66B encoding. A FlexE client can be interpreted as an Ethernet stream based on a physical address. Clients sent through the same FlexE group need to share the same clock, and these clients need to be adapted according to the assigned slot rate.
  • FlexE shim As an additional logical layer inserted between the MAC and the PHY (PCS sublayer), the core architecture of the FlexE technology is realized through a time slot distribution mechanism based on a daily table (calendar). The main function of FlexE shim is to slice data according to the same clock, and encapsulate the sliced data into pre-divided time slots. Then, according to the preconfigured time slot configuration table, the divided time slots are mapped to the PHYs in the FlexE group for transmission. Among them, each time slot is mapped to one PHY in the FlexE group.
  • the processing procedure may include: for each data stream in the plurality of data streams, by adding or deleting idle patterns to complete the rate adaptation of the data stream, that is, adapting the rate of the data stream from the rate of the MAC to the rate of the PHY ; Map multiple data streams after rate adaptation to the time slots of FlexE shim to obtain a calendar data stream, the total bandwidth corresponding to the calendar data stream can be N ⁇ 20 ⁇ 5Gbps; multiple PHYs in a FlexE group Insert an OH frame (also referred to as a FlexE frame or a Flex
  • the data carried on each PHY in the multiple PHYs is mapped from the frame header position of the OH frame of the PHY, and the transmission starts after the OH frame headers of the multiple PHYs are aligned, and the data carried on the multiple PHYs
  • the data can be represented as FlexE#1 100G instance (instance) to FlexE#N 100G instance respectively, and this instance can also be called sub-calendar data stream.
  • FIG. 6 shows a schematic diagram of an application scenario of the FlexE communication system involved in this application.
  • the FlexE communication system includes user equipment 1, network equipment 1, network equipment 2, and user equipment 2.
  • Network equipment 1 and network equipment 2 may be logically related. two adjacent network devices.
  • the network device 1 may be an intermediate node, in which case the network device 1 is connected to the user equipment 1 through other network devices; or, the network device 1 is an edge node, in which case the network device 1 is directly connected to the user equipment 1.
  • the network device 2 may be an intermediate node, in which case the network device 2 is connected to the user equipment 2 through other network devices; or, the network device 2 is an edge node, in which case the network device 2 is directly connected to the user equipment 2.
  • the network device 1 may include a network card 11 and a network card 12 serving as a main board and a backup board respectively, and a switch 13 for switching the network card 11 and the network card.
  • the network card 11 has a FlexE interface a
  • the network card 12 has a FlexE interface b
  • the network device 2 includes a network card 21, and the network card 21 has a FlexE interface c.
  • Each FlexE interface can also be called a FlexE group.
  • the difference from a traditional Ethernet interface is that a FlexE interface can carry multiple clients, and a FlexE interface as a logical interface can be composed of multiple physical interfaces.
  • a network card in each network device may have one or more FlexE interfaces, and the network device 2 may also include two network cards as the main board and the backup board respectively.
  • one network card has one FlexE interface
  • the network device 2 has one network card as an example for description.
  • the process of communicating between the network device 1 and the network device 2 through the protection switching mechanism may include: when the network device 1 sends data to the network device 2, the network card 11 and the network card 12 can switch to the network device 1 through the FlexE interface a and the FlexE interface b respectively.
  • the switch 13 sends two paths of data, and the two paths of data are the same data.
  • the switch 13 selects one of the two paths of data to send to the network device 2, that is, the data sent by the network device 1 is selected at the switch 13.
  • the Receive that is, select the data of the network card 11 or the network card 12 to send to the network device 2, usually select the data of the network card 11 (ie the main board), and select the data of the network card 12 (ie the backup board) when the network card 11 fails;
  • the switch 13 will send the received data to the network card 11 and the network card 12 through the FlexE interface a and the FlexE interface b respectively. Both the network card 11 and the network card 12 receive the data.
  • the system shown in FIG. 6 only takes two user equipments and two network devices as an example for description, and the FlexE communication system may also include a larger number of user equipments and network devices. Not limited.
  • the FlexE communication system shown in FIG. 6 is for illustration only, and the application scenario of the FlexE communication system provided by the present application is not limited to the scenario shown in FIG. 6 .
  • the technical solution provided in this application is applicable to all network scenarios in which the FlexE technology is used for data transmission.
  • FIG. 7 is a schematic flowchart of a method for processing a flexible Ethernet overhead frame provided by an embodiment of the present application.
  • the method is applied to a first network device including a main board and a backup board.
  • the first network device is shown in FIG. 6 above.
  • the network device 1, the method includes the following steps.
  • the main board sends first indication information to the standby board, where the first indication information is used to indicate the phase of the first overhead frame of the service data stream carried on the first PHY of the main board.
  • the mainboard and the network may correspond to a first FlexE group (also referred to as a first FlexE interface), the first FlexE group may include multiple PHYs, and the first PHY may be any one of the multiple PHYs.
  • the service data stream carried on the first PHY may include data of one or more clients.
  • the first network device sends the service data stream to the second network device through the mainboard (that is, the switch in the first network device selects the data of the mainboard to send to the second network device).
  • the main board may send first indication information to the standby board, where the first indication information is used to indicate the phase of the first overhead frame of the service data stream carried on the first PHY of the main board.
  • the first overhead frame may be an overhead frame currently sent by the mainboard (also referred to as a FlexE frame), and the phase of the first overhead frame may refer to the time domain position of the currently sent first overhead frame, for example, the time domain position may be for the time slot.
  • the first indication information may include the position of the frame header of the first overhead frame; wherein, the first overhead frame may include 8 overhead blocks, and the frame header of the first overhead frame may refer to the first overhead block in the 8 overhead blocks.
  • An overhead block, the frame header position is the time domain position of the first overhead block, so the phase of the first overhead frame can be the frame header position of the first overhead frame (or called the time domain position of the first overhead block) .
  • the first indication information may also include feature information of the first overhead frame, and the specific information may include a padding block PAD phase and/or an alignment marker (aligment marker, AM) phase; wherein, PAD and AM are Ethernet are used for rate matching and data alignment respectively, the PAD and the AM will be inserted into the service data stream according to a certain rule during the sending process of the service data stream.
  • the first network device may insert overhead frames according to interval a1, PAD according to interval a2, and AM according to interval a3 in the service data stream.
  • the phases of overhead frames, PAD and AM are aligned during initialization, the After the service data stream is transmitted through the least common multiple of a1, a2 and a3, the phases of the overhead frame, PAD and AM will be aligned again, so that the second network device can receive the service data stream based on the overhead frame, the PAD Or any one of the AMs can achieve data alignment.
  • the PAD and the AM reference may be made to the description in the related art, and details are not described herein again in this embodiment of the present application.
  • the motherboard may sample the first overhead frame to determine the frame header position of the first overhead frame included in the first indication information; further The mainboard can also count the number of bit blocks from the frame header position to determine the number of bit blocks of the PAD and the AM relative to the frame header of the first overhead frame, that is, to determine the first indication information
  • the mainboard may also use a single-bit encoding format to encode the first indication information.
  • the mainboard can start coding from the frame header position of the first overhead frame, and pass M (M is a positive integer) coding cycles (for example, using a coding frequency of 10MHz, that is, one coding cycle is 100ns) to complete the encoding of the frame header, the frame header may include N periods of high level and N periods of low level, for example, M is equal to 20, and N is equal to 10.
  • M is a positive integer
  • the first indication information may also include an encoding version number; the first indication information may also include a cyclic redundancy check code CRC8, which can be used to check the encoding version.
  • the standby board determines the phase of the second overhead frame of the service data stream carried on the second PHY of the standby board according to the phase of the first overhead frame, and the second overhead A frame is the next overhead frame of the first overhead frame.
  • the backup board and the network may correspond to a second FlexE group (also referred to as a second FlexE interface), the second FlexE group may include multiple PHYs, and the second PHY may be one of the multiple PHYs for carrying the One PHY of the service data stream, that is, the service data stream borne by the second PHY and the service data stream borne by the first PHY are the same service data stream.
  • the standby board receives the first indication information, the standby board can determine the phase of the first overhead frame according to the first indication information, so as to determine the second phase of the service data stream on the second PHY according to the phase of the first overhead frame Phase of the overhead frame.
  • the standby board can use the frame header position of the first overhead frame and the interval between two overhead frames (the interval is fixed, such as , the interval can be 163688 (ie 20 ⁇ 1023 ⁇ 8+8) 64B/66B bit blocks), determine the frame header position of the second overhead frame of the service data stream on the first PHY; after that, the backup board can Align the header position of the second overhead frame of the service data stream on the second PHY according to the header position of the second overhead frame on the first PHY, for example, align the header position of the second overhead frame on the first PHY As the frame header position of the second overhead frame of the data stream on the second PHY, the alignment of the phases of the second overhead frame of the service data stream on the second PHY is implemented.
  • the standby board may also determine the PAD phase of the service data stream in the second overhead frame on the second PHY according to the PAD phase, if the PAD phase is the PAD phase and the frame header of the first overhead frame, the standby board can determine the second overhead frame on the second PHY according to the PAD phase, the interval between the two PADs, and the interval between the two overhead frames. the PAD phase.
  • the standby board can also determine the AM phase of the service data stream in the second overhead frame on the second PHY according to the AM phase, if the AM phase is the AM phase and the frame header of the first overhead frame, the standby board can determine the second overhead frame on the second PHY according to the AM phase, the interval between two AMs, and the interval between two overhead frames AM phase in . In this way, the standby board can ensure that the PAD phase and AM phase in the second overhead frame on the first PHY of the main board are respectively the same as the PAD phase and AM phase in the second overhead frame on the second PHY of the standby board according to the above method.
  • the phases are aligned to ensure the consistency of the insertion of the main board and the standby board for the PAD and AM.
  • the standby board may decode the first indication information when receiving the first indication information to obtain the first indication information. Relevant information in the instructions. Exemplarily, taking the encoding method shown in FIG.
  • the standby board can start decoding after detecting that the signal of the data stream from the main board jumps up, and after continuously receiving N cycles of high levels, it can detect When the signal jumps downward, it is determined that the position of the downward jump is the frame header position of the first overhead frame; after that, the low level of N cycles is continuously detected, if the low level of N consecutive cycles is detected, then The position of the frame header of the first overhead frame is correct, and the position of the frame header of the first overhead frame is re-determined if the low level of N consecutive cycles is not detected.
  • the standby board can decode the encoding version number, the characteristic information of the first overhead frame (for example, PAD phase and AM phase) and CRC8 according to the encoding mode of the data "0" and the data "1" respectively, and the encoded version number.
  • the number can be used to indicate the encoding version, so that the standby board can identify the difference between different encoding versions according to the encoding version number.
  • the standby board can also check the characteristic information of the first overhead frame according to the CRC8. If the check succeeds, it is determined that the characteristic information of the first overhead frame is correct. If the check fails, it starts to check the first indication information again.
  • the standby board detects the low level of N cycles or the high level of N cycles, the signal will jitter due to the influence of the wiring between the boards, so that the low level or high level is actually detected.
  • the period of the flat will be greater or less than N, for example, the number of detected surroundings is N+1 or N-1. Therefore, as long as the absolute value of the difference between N and the number of periods of the detected low level is smaller than the preset threshold, it can be considered that N periods of low level or N periods of high level are detected.
  • the method may further include: S203.
  • the standby board compensates the phase of the second overhead frame of the service data stream on the second PHY according to the inter-board transmission delay and/or the codec delay.
  • the inter-board transmission delay may refer to the transmission delay of the phase of the first overhead frame (for example, the frame header position of the first overhead frame) from the main board to the standby board, and the inter-board transmission delay may be determined in advance It is configured to the standby board after measurement by an external hardware device such as an oscilloscope, so that when the phase of the second overhead frame on the second PHY needs to be compensated, the standby board can directly obtain the inter-board transmission delay according to the corresponding configuration.
  • the encoding and decoding delay includes encoding delay and decoding delay.
  • the encoding delay refers to the delay when the main board encodes the phase of the first overhead frame
  • the decoding delay refers to the standby board decoding the first overhead frame. time delay at the phase.
  • the encoding delay and the decoding delay can be obtained by measurement in advance, and can be configured to the standby board.
  • the standby board determines that the service data stream is on the second PHY
  • the phase of the second overhead frame may include: the frame header position of the first overhead frame, the encoding delay, the inter-board transmission delay, the decoding delay, the transmission delay and overhead of the characteristic information of the first overhead frame
  • the frame interval determines the phase of the second overhead frame of the service data stream on the second PHY, where the phase of the second overhead frame is the frame header position of the second overhead frame.
  • the standby board determines the first PHY
  • t5 ⁇ t-t1-t2-t3-t4, that is, the interval from the second overhead frame after compensating the phase of the first overhead frame.
  • the standby board determines the phase of the second overhead frame of the service data stream on the second PHY in the above manner, the phases of the same overhead frame of the service data stream on the first PHY and the second PHY can be aligned, It can also be understood that the phase tracking of the overhead frame of the service data stream on the second PHY aligns the phase of the overhead frame of the service data stream on the first PHY.
  • the first network device can send the service data stream to the second network device through the backup board, for example, the backup board sends the phase of the aligned second overhead frame on the second PHY the business data flow.
  • the second network device since the phases of the overhead frames of the service data streams sent by the main board and the standby board are aligned, when the main board fails and the second network device receives the service data flow sent by the standby board, the second network device still remains The overhead frame in the service data stream can be locked, and data alignment in multiple PHYs can be realized based on the locked overhead frame, and then the customer's data can be extracted from the aligned data.
  • the first indication information further includes the PAD phase or AM phase of the first overhead frame
  • the second network device may also implement data alignment in multiple PHYs based on the PAD phase or the AM phase.
  • the second network device locks the overhead frame, implements data alignment in multiple PHYs based on the locked overhead frame, and extracts the client's data from the aligned data.
  • the specific process can refer to the relevant description of the prior art, which is implemented in this application. The example will not be repeated here.
  • the method may further include: S204-S205.
  • S204-S205 and S201-S203 may be in no particular order.
  • S204-S205 is located after S203 as an example for description.
  • the standby board determines the frame header phase deviation between the main board and the standby board according to the frame header of the same overhead frame of the service data stream carried on the first PHY and the second PHY.
  • the standby board can be used to detect the phase deviation of the service data stream between the frame headers of the same overhead frame on the main board and the standby board.
  • a counter may be integrated in the standby board, and the counter can be used to start counting at the frame header position of an overhead frame on the main board determined by the standby board, and start counting at the frame header of the same overhead frame on the standby board. Stop counting when the position (or the frame header position of the same overhead frame on the standby board is calculated), and the accumulated value of the counter is the frame header of the same overhead frame of the service data stream on the main board and the standby board. phase deviation between.
  • the counter first starts to count when "the header of the first overhead frame on the main board is calculated by the standby board” , and then stop counting when the frame header of the first overhead frame on the standby board arrives, and the accumulated value corresponding to the counter is the phase deviation of the frame header.
  • the standby board can send alarm information to the processor in the first network device, so that there is a gap between the main board and the standby board. Realign overhead frames.
  • the preset deviation may be set in advance.
  • the preset deviation may be determined according to the alignment capability of the switch used for switching the main board and the standby board in the first network device, which is not specifically limited in this embodiment of the present application .
  • the following uses the structure of the first network device shown in FIG. 11 as an example to illustrate the method provided by this embodiment of the present application.
  • the FlexE group between the main board and the network is the first FlexE group (also called a working group)
  • the FlexE group between the standby board and the network is the second FlexE group (also called the standby group) (backup group)
  • the first FlexE group and the second FlexE group may include a receive (receive, RX) decoding (decode) unit, a frame header locking and checking unit, a PHY phase alignment unit, and a transmit (transmit, TX) encoding unit (code) unit and sampling unit.
  • the main board and the backup board may also be respectively connected with a programmable device for compiling or decoding the data they interact with each other.
  • the sampling unit in the main board can be used for the frame header of the first overhead frame of the service data stream carried on the first PHY in the first FlexE group sampling;
  • the TX encoding unit in the main board can be used to encode the frame header of the sampled first overhead frame and send it to the standby board;
  • the RX decoding unit in the standby board can decode the received data;
  • the frame header locking and checking unit can lock the frame header of the first overhead frame according to the decoded data, and check the frame header phase deviation of the same overhead frame in the main board and the standby board;
  • the PHY phase alignment unit in the standby board It can be used to align the frame header of the second overhead frame of the standby board according to the frame header of the first overhead frame.
  • the main board and the standby board in the embodiment of the present application can be interchanged.
  • the standby board when the standby board is upgraded to the main board, the standby board can also send the phase of the currently sent overhead frame to the main board, so that the The main board tracks the phase of the overhead frame that aligns the standby board.
  • the above description only takes the phase of the overhead frame of the main board that is tracked and aligned by the standby board as an example. No longer.
  • the main board sends first indication information to the standby board, where the first indication information is used to indicate the phase of the first overhead frame of the service data stream on the main board.
  • the phase of the second overhead frame of the service data flow on the standby board can be determined according to the phase of the first overhead frame, so that the phase tracking of the overhead frame of the service data flow on the standby board is aligned with the service The phase of the overhead frame of the data stream on this board.
  • the first network device can send the service data stream to the second network device through the backup board, because the phases of the overhead frames of the service data stream sent by the main board and the backup board are aligned , so that the second network device can still lock the overhead frames in the service data stream, thereby reducing the influence of damage to service data streams on other normally working PHYs due to the failure of one PHY in the mainboard.
  • the first network device includes corresponding hardware structures and/or software modules for performing each function.
  • the present application can be implemented in hardware or a combination of hardware and computer software with reference to the network elements and algorithm steps of each example described in the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.
  • the first network device may be divided into functional modules according to the foregoing method examples.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. It should be noted that, the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation.
  • An embodiment of the present application provides a first network device, and a schematic structural diagram of the first network device may be as shown in network device 1 in FIG. 6 .
  • the first network device includes: a network card 11 and a network card 12, the network card 11 can be used as a main board, and the network card 12 can be used as a backup board.
  • the network card 11 is used to support the first network device to perform S201 in the above method embodiments;
  • the network card 12 is used to support the first network device to perform one or more of S202-S205 in the above method embodiments, and/or use Other procedures for the techniques described herein.
  • the first network device further includes: a switch 13; wherein the switch 13 is used to support the first network device to select the data sent by the network card 11 to send to the second network device when the network card 11 is not faulty, and when the network card 11 fails The data sent by the network card 12 is selected to be sent to the second network device.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are only illustrative.
  • the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be Incorporation may either be integrated into another device, or some features may be omitted, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place, or may be distributed to multiple different places . Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a readable storage medium.
  • the technical solutions of the embodiments of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, which are stored in a storage medium , including several instructions to make the terminal execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk and other mediums that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供一种灵活以太网开销帧处理方法及装置，用于减少处于故障状态下的PHY对FlexE group中正常状态的PHY所承载的业务数据流的影响。该方法应用于包括主板和备板的网络设备中，该方法包括：该主板向该备板发送第一指示信息，第一指示信息用于指示该主板的第一PHY上承载的业务数据流的第一开销帧的相位；该备板接收第一指示信息，并根据第一开销帧的相位确定该备板的第二PHY上承载的该业务数据流的第二开销帧的相位，第二开销帧是第一开销帧的下一个开销帧。

Description

一种灵活以太网开销帧处理方法及装置 技术领域
本申请涉及通信技术领域，尤其涉及一种灵活以太网开销帧处理方法及装置。
背景技术
灵活以太网(flexible ethernet，FlexE)技术是基于高速以太网(ethernet)接口，通过ethernet媒体接入控制(media access control，MAC)层与物理层解耦而实现的低成本、高可靠的电信级接口技术。FlexE技术通过在IEEE802.3基础上引入灵活以太网切片(FlexE shim)层实现了MAC层与物理层解耦，从而实现了灵活的速率匹配。
FlexE技术通过将多个以太网物理层(physical layer，PHY)绑定成一个灵活以太网组(FlexE group)以及物理层通道化等功能，满足灵活带宽的端口应用需求。因此，FlexE提供的MAC速率可以大于单个PHY的速率(通过捆绑实现)，也可以小于单个PHY的速率(通过通道化实现)。
按照当前FlexE标准以及相关现有技术的方案，对于FlexE中存在安全保障需求的网络设备，如图1所示，该网络设备主要通过主板和备板的保护倒换机制来实现业务数据流的传输。具体的，该网络设备中的主板和备板均通过FlexE group发送业务数据流；当该主板正常工作时，由切换开关选择主板的FlexE group上承载的该业务数据流发送给其他设备；当该主板的FlexE group中的一个或多个PHY处于故障状态时，由该切换开关选择备板的FlexE group上承载的该业务数据流发送给其他设备。
但是，上述保护倒换机制会导致主板的FlexE group中正常工作的PHY所承载的业务数据流发生中断，中断时长可能达到几十毫秒，从而造成正常工作的PHY所承载的业务数据流受损。因此，如何能够减少处于故障状态下的PHY对FlexE group中正常状态的PHY所承载的业务数据流的影响，成为目前亟待解决的问题。
发明内容
本申请提供一种灵活以太网开销帧处理方法及装置，用于减少处于故障状态下的PHY对FlexE group中正常状态的PHY所承载的业务数据流的影响。
为达到上述目的，本申请的实施例采用如下技术方案。
第一方面，提供一种灵活以太网开销帧处理方法，应用于包括主板和备板的网络设备中，该方法包括：该主板向该备板发送第一指示信息，第一指示信息用于指示该主板的第一物理层接口PHY上承载的业务数据流的第一开销帧的相位，该主板与网络之间可以对应第一FlexE group，可以包括多个PHY，第一PHY可以是第一FlexE group绑定的多个PHY中的任意一个PHY；该备板接收第一指示信息，并根据第一开销帧的相位确定该备板的第二PHY上承载的该业务数据流的第二开销帧的相位，第二开销帧是第一开销帧的下一个开销帧；其中，该备板与网络之间可以对应第二FlexE group，第二PHY可以是第二FlexE group绑定的多个PHY中用于承载该业务数据流的一个PHY，即第二PHY承载的业务数据流与第一PHY上承载的业务数据流为同一业务数据流。
上述技术方案中，该备板根据第一开销帧的相位确定第二PHY上的该业务数据流的第二开销帧相位之后，可以使得该业务数据流在该备板上的开销帧的相位跟踪对齐该业务数据流在该主板上的开销帧的相位。这样，当该主板发生故障时，第一网络设备可以通过该备板向第二网络设备发送该业务数据流，由于该主板和该备板发送的该业务数据流的开销帧的相位是对齐的，从而第二网络设备仍然可以锁定该业务数据流中的开销帧，进而降低了因为该主板中的某一PHY故障而导致其他正常工作的PHY上的业务数据流受损的影响。
在第一方面的一种可能的实现方式中，该方法还包括：当该主板未发生故障时，该主板在第一PHY上以第一开销帧的相位发送该业务数据流；当该主板发生故障时，该备板在第二PHY上以第二开销帧的相位发送该业务数据流。上述可能的实现方式中，当该主板发生故障时，第一网络设备可以通过该备板向第二网络设备发送该业务数据流，由于该主板和该备板发送的该业务数据流的开销帧的相位是对齐的，从而第二网络设备仍然可以锁定该业务数据流中的开销帧，进而降低了因为该主板中的某一PHY故障而导致其他正常工作的PHY上的业务数据流受损的影响。
在第一方面的一种可能的实现方式中，第一指示信息是以单比特编码格式编码后的信息。可选的，第一指示信息包括第一开销帧的帧头位置；进一步，第一指示信息还包括以下至少一项：编码版本号、第一开销帧的特征信息。上述可能的实现方式中，可以提高该备板确定第一开销帧的高效性。
在第一方面的一种可能的实现方式中，第一指示信息还包括：循环冗余校验码CRC8，该CRC8用于校验该编码版本号和/或第一开销帧的特征信息。上述可能的实现方式中，通过该CRC8校验该编码版本号和/或第一开销帧的特征信息，可以提高上述信息的安全性。
在第一方面的一种可能的实现方式中，该备板根据第一开销帧的相位确定该备板上的第二PHY上承载的该业务数据流的第二开销帧的相位，包括：该备板根据第一开销帧的帧头位置和开销帧间隔，确定第一PHY上的第二开销帧的帧头位置；根据第一PHY上的第二开销帧的帧头位置，确定该备板上的第二PHY上承载的该业务数据流的第二开销帧的相位。上述可能的实现方式中，提供了一种简单有效的确定该备板上的第二开销帧的相位的方式。
在第一方面的一种可能的实现方式中，该方法还包括：该备板根据板间传输时延和/或编解码时延，补偿该备板上的第二PHY上承载的该业务数据流的第二开销帧的相位。上述可能的实现方式中，提高了该备板上的第二开销帧的相位的准确性。
在第一方面的一种可能的实现方式中，该特征信息包括填充块PAD相位，该方法还包括：根据该PAD相位确定该业务数据流在第二PHY上的第二开销帧中的PAD相位；和/或，该特征信息还包括对齐标志字AM相位，该方法还包括：根据该AM相位确定该业务数据流在第二PHY上的第二开销帧中的AM相位。上述可能的实现方式中，该备板按照上述方式可以保证该主板的第一PHY上的第二开销帧中的PAD相位和AM相位分别与该备板的第二PHY上的第二开销帧中的PAD相位和AM相位是对齐的，从而保证该主板和该备板对于PAD和AM的插入的一致性。
在第一方面的一种可能的实现方式中，该方法还包括：该备板根据第一PHY和第 二PHY上承载的该业务数据流的同一个开销帧的帧头，确定该主板与该备板之间的帧头相位偏差；当该帧头相位偏差大于预设偏差时，该备板触发告警信息。上述可能的实现方式中，该备板向该网络设备中的处理器发送告警信息，以使该主板和该备板之间重新对齐开销帧。
第二方面，提供一种灵活以太网开销帧处理装置，述装置包括主板和备板；其中，该主板，用于向该备板发送第一指示信息，第一指示信息用于指示该主板的第一物理层接口PHY上承载的业务数据流的第一开销帧的相位；该备板，用于接收第一指示信息，并根据第一开销帧的相位确定该备板的第二PHY上承载的该业务数据流的第二开销帧的相位，第二开销帧是第一开销帧的下一个开销帧。
在第二方面的一种可能的实现方式中，该主板还用于当该主板未发生故障时，该主板在第一PHY上以第一开销帧的相位发送该业务数据流；该备板还用于当该主板发生故障时，该备板在第二PHY上以第二开销帧的相位发送该业务数据流。
在第二方面的一种可能的实现方式中，第一指示信息是以单比特编码格式编码后的信息。
在第二方面的一种可能的实现方式中，第一指示信息包括第一开销帧的帧头位置。
在第二方面的一种可能的实现方式中，该备板还用于：根据第一开销帧的帧头位置和开销帧间隔，确定第一PHY上的第二开销帧的帧头位置；根据第一PHY上的第二开销帧的帧头位置，确定该备板上的第二PHY上承载的该业务数据流的第二开销帧的相位。
在第二方面的一种可能的实现方式中，该备板还用于：根据板间传输时延和/或编解码时延，补偿第二PHY上承载的该业务数据流的第二开销帧的相位。
在第二方面的一种可能的实现方式中，第一指示信息还包括以下至少一项：编码版本号、第一开销帧的特征信息。
在第二方面的一种可能的实现方式中，第一指示信息还包括：循环冗余校验码CRC8，该CRC8用于校验该编码版本号和/或第一开销帧的特征信息。
在第二方面的一种可能的实现方式中，该特征信息包括填充块PAD相位，该备板还用于：根据该PAD相位确定该业务数据流在第二PHY上的第二开销帧中的PAD相位；和/或，该特征信息还包括对齐标志字AM相位，该备板还用于：根据该AM相位确定该业务数据流在第二PHY上的第二开销帧中的AM相位。
在第二方面的一种可能的实现方式中，该备板还用于：根据第一PHY和第二PHY上承载的该业务数据流的同一个开销帧的帧头，确定该主板与该备板之间的帧头相位偏差；当该帧头相位偏差大于预设偏差时，触发告警信息。
本申请的又一方面，提供一种可读存储介质，该可读存储介质中存储有指令，当可读存储介质在设备上运行时，使得设备执行第一方面或者第一方面的任一种可能的实现方式所提供的方法。
本申请的又一方面，提供一种计算机程序产品，当计算机程序产品在计算机上运行时，使得计算机执行第一方面或者第一方面的任一种可能的实现方式所提供的方法。
可以理解地，上述提供的任一种灵活以太网开销帧处理方法的装置、计算机存储介质或者计算机程序产品均用于执行上文所提供的对应的方法，因此，其所能达到的有 益效果可参考上文所提供的对应的方法中的有益效果，此处不再赘述。
附图说明
图1为一种通过保护倒换机制来传输业务数据流的示意图；
图2为本申请实施例提供的一种FlexE OH帧的示意图；
图3为本申请实施例提供的一种FlexE group的示意图；
图4为本申请实施例提供的一种100GBASE-R FlexE复用器功能的示意图；
图5为本申请实施例提供的一种100GBASE-R FlexE解复用器功能的示意图；
图6为本申请实施例提供的一种FlexE通信系统的应用场景示意图；
图7为本申请实施例提供的一种灵活以太网开销帧处理方法的流程示意图；
图8为本申请实施例提供的一种第一指示信息的编码示意图；
图9为本申请实施例提供的另一种灵活以太网开销帧处理方法的流程示意图；
图10为本申请实施例提供的一种确定第二PHY上的第二开销帧的相位的示意图；
图11为本申请实施例提供的一种第一网络设备的结构示意图。
具体实施方式
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。另外，本申请实施例采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。例如，第一阈值和第二阈值仅仅是为了区分不同的阈值，并不对其先后顺序进行限定。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定。
需要说明的是，本申请中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
在介绍本申请的技术方案之前，首先对本申请实施例所涉及的相关技术和概念进行介绍说明。
在以太网中，以太网端口通常作为面向数据的逻辑上的概念出现，称为逻辑端口或简称为端口，以太网物理接口作为硬件上的概念出现，称为物理接口或简称为接口。通常以太网端口的速率的确定以以太网物理接口的速率为基础，一般情况下一个以太网端口最大带宽对应一个以太网物理接口的带宽。随着以太网在过去的一段时间内的发展和应用，以太网端口的速率以10倍提升，从10兆比特每秒(megabit per second，Mbps)向100Mbps、1000Mbps(即1Gbps)、10Gbps、40Gbps、100Gbps、400Gbps等不断演进发展，而实际应用需求的带宽增长并不呈现这样的10倍增长特征，例如50Gbps、75Gbps、200Gbps等，从而造成以太网端口的速率与实际应用需求期望的偏差不断增大。因此，业界一方面希望能够提供一些灵活带宽的逻辑端口，这些逻辑端 口可以共同使用一个或者若干个以太网物理接口，例如2个40GE端口和2个10GE端口共同使用一个100G物理接口；并能够随着需求的变化做出灵活的速率调整，例如从200Gbps调整为330Gbps，或者50Gbps调整为20Gbps，以提高端口使用效率或者延长其使用生命周期。对于固定速率的物理链路，可以将其级联捆绑，以支持逻辑端口速率的堆叠增加(例如，将2个100GE物理接口堆叠级联捆绑以支持200GE逻辑端口)。另一方面，希望能够将物理接口灵活堆叠所得到的带宽资源池化，将其带宽按照颗粒(例如，5G为一个颗粒)分配给特定的以太网逻辑端口，实现若干以太网虚拟连接对堆叠级联的物理链路组的高效共享。
由此，灵活以太网(flexible ethernet，FlexE)的概念应运而生，灵活以太网又称为灵活虚拟以太网。FlexE支持针对以太网业务的子速率、通道化、反向复用等功能。例如，针对以太网业务的子速率应用场景，FlexE能够支持将250G的以太网业务(MAC码流)采用3路现有的100GE的物理接口进行传送。针对以太网业务的反向复用场景，FlexE能够支持将200G的以太网业务采用2路100GE的物理媒质相关(physical medium dependent，PMD)子层进行传送。针对以太网业务的通道化场景，FlexE能够支持若干个逻辑端口共同使用一个或者多个物理接口，能够支持将多路低速率的以太网业务复用到高速率的灵活以太网的中。FlexE的子速率、通道化和反向复用功能的引入，极大的扩展了以太网的应用场合，增强了以太网应用的灵活性，并使得以太网技术逐渐向传送网领域渗透。
FlexE借鉴同步数字体系(synchronous digital hierarchy，SDH)/光传输网络(optical transfer network，OTN)技术，对物理接口传输构建固定帧格式，并进行时分复用(time division multiplexing，TDM)的时隙划分。下面以现有的FlexE帧格式举例说明。FlexE的TDM时隙划分粒度是66比特(bits)，对应承载一个64B/66B比特块。如图2所示，一个FlexE帧包含8个灵活以太网开销(FlexE overhead，FlexE OH)块(也可以称为OH块，每个OH块为一个64B/66B比特块)，第一个FlexE OH块为该FlexE OH帧的帧头位置，FlexE OH块与FlexE OH块之间为进行时隙划分的净荷区域，该净荷区域以66比特为粒度，对应1023×20个66比特承载空间(即1023组时隙，每组20个时隙，每个时隙为66比特)，100GE接口的带宽划分20个时隙，每个时隙的带宽约为5Gbps。图2中仅示出了一个FlexE帧中相邻的两个FlexE OH块、以及这两个FlexE OH块之间的净荷区域的示意图。FlexE通过交织复用的方式在单个物理接口上实现了多个传输通道，即实现了多个时隙。若干个物理接口可以捆绑，该若干个物理接口的全部的时隙可以组合承载一个以太网逻辑端口。例如10GE需要两个时隙，25GE需要5个时隙等。逻辑端口上可见的仍为顺序传输的64B/66B比特块，每个逻辑端口对应一个MAC，传输相应的以太网报文，对报文的起始结束和对空闲填充的识别与传统以太网相同。FlexE只是一种接口技术，相关的交换技术可以基于现有的以太网包进行，也可以基于FlexE交叉进行，此处不再赘述。
FlexE技术通过在IEEE802.3基础上引入灵活以太网切片(FlexE shim)层实现了MAC层与物理层解耦，实现灵活的速率匹配。如图3所示，FlexE可以将一个或者多个物理层接口(physical layer，PHY)绑定在一起构成一个FlexE组(FlexE group)，通过一个FlexE组传输来自不同MAC的多个FlexE客户(FlexE client)，以实现以太 网接口速率的灵活匹配。图3中以四个PHY绑定在一起构成一个FlexE组为例进行说明。
FlexE group：也可以称为捆绑组，每个FlexE group包括的多个PHY具有逻辑上的捆绑关系，该多个PHY在物理上可以是独立的，不存在物理连接关系。FlexE中的网络设备可以通过PHY的编号来标识一个FlexE group中包含哪些PHY，来实现多个PHY的逻辑捆绑。例如，每个PHY的编号可用1-254之间的一个数字来标识，0和255为保留数字。一个PHY的编号可对应网络设备上的一个物理接口。相邻的两个网络设备之间需采用相同的编号来标识同一个PHY。一个FlexE group中包括的各个PHY的编号不必是连续的。
FlexE client：对应于网络的各种用户接口，与现有的因特网协议或以太网等网络中的传统业务接口一致。FlexE client可根据带宽需求灵活配置，支持各种速率的以太网MAC数据流，例如可以通过64B/66B的编码的方式将数据流传递至FlexE shim。FlexE client可以被解释为基于一个物理地址的以太网流。通过同一FlexE group发送的客户需要共用同一时钟，且这些客户需要按照分配的时隙速率进行适配。
FlexE shim：作为插入MAC与PHY(PCS子层)中间的一个额外逻辑层，通过基于日常表(calendar)的时隙分发机制实现FlexE技术的核心架构。FlexE shim的主要作用是根据相同的时钟对数据进行切片，并将切片后的数据封装至预先划分的时隙中。然后，根据预先配置的时隙配置表，将划分好的各时隙映射至FlexE group中的PHY上进行传输。其中，每个时隙映射于FlexE group中的一个PHY。
示例性的，对于发送端，以图4所示的100GBASE-R FlexE复用器(mux)功能为例，对于来自MAC层(对应客户时钟域(client clock domain))的多个数据流(分别表示为cl#1至cl#M)，在对该多个数据流进行客户处理(client processing)后进入FlexE shim(对应FlexE时钟域(FlexE clock domain))，FlexE shim对该多个数据流的处理过程可以包括：对于该多个数据流中的每个数据流，通过增加或删除idle码型以完成该数据流的速率适配，即将数据流的速率从MAC的速率适配到PHY的速率；将速率适配后的多个数据流映射到FlexE shim的时隙中以得到calendar数据流，该calendar数据流对应的总带宽可以为N×20×5Gbps；在一个FlexE group中的多个PHY上插入OH帧(也可以称为FlexE帧或FlexE OH帧)；将该calendar数据流分发到该多个PHY上。其中，该多个PHY中每个PHY上承载的数据是从该PHY的OH帧的帧头位置开始映射的，且在该多个PHY的OH帧头对齐后开始传输，该多个PHY上承载的数据可以分别表示为FlexE#1 100G实例(instance)至FlexE#N 100G实例，该实例也可以称为子日常表(sub-calendar)数据流。
示例性的，对于接收端，以图5所示的100GBASE-R FlexE解复用器(demux)功能为例，FlexE shim的处理过程可以包括：对于接收到的多个子calendar数据流(分别表示为FlexE#1 100G实例至FlexE#N 100G实例)，锁定每个PHY上的OH帧；按照OH帧的边界对齐同一FlexE group中的多个PHY上的数据，在对齐过程中可以去掉多个PHY之间的相位偏差；将该多个PHY上的数据重新排列成calendar数据流；通过client的映射信息，从该calendar数据流中抽取多个数据流：对于该多个数据流中的每个数据流，通过增加或删除idle码型以完成该数据流的速率适配，即将数据流 的速率从PHY的速率适配到MAC的速率，即得到多个数据流(分别表示为cl#1至cl#M)。
图6示出了本申请涉及的FlexE通信系统的应用场景示意图，该FlexE通信系统包括用户设备1、网络设备1、网络设备2和用户设备2，网络设备1和网络设备2可以是逻辑上相邻的两个网络设备。其中，网络设备1可以是中间节点，此时网络设备1通过其他网络设备与用户设备1连接；或者，网络设备1是边缘节点，此时网络设备1直接与用户设备1连接。同理，网络设备2可以是中间节点，此时网络设备2通过其他网络设备与用户设备2连接；或者，网络设备2是边缘节点，此时网络设备2直接与用户设备2连接。
其中，网络设备1可以包括分别作为主板和备板的网卡11和网卡12、以及用于切换网卡11和网卡的切换开关13。网卡11具有FlexE接口a，网卡12具有FlexE接口b。网络设备2包括网卡21，网卡21具有FlexE接口c。每个FlexE接口也可以称为一个FlexE group，与传统以太网接口的区别在于一个FlexE接口可以承载多个客户(client)，且作为逻辑接口的FlexE接口可以由多个物理接口组合而成。可选的，每个网络设备中的一个网卡可以具有一个或者多个FlexE接口，网络设备2也可以包括分别作为主板和备板的两个网卡，图6中以一个网卡具有一个FlexE接口、以及网络设备2具有一个网卡为例进行说明。
具体的，假设网络设备1处于安全保障的需要，将网卡11作为主板、网卡12作为备板，以实现主板和备板的保护。这样网络设备1通过保护倒换机制与网络设备2之间进行通信的过程可以包括：网络设备1在向网络设备2发送数据时，网卡11和网卡12可以分别通过FlexE接口a和FlexE接口b向切换开关13发送两路数据，这两路数据为同一数据，由切换开关13选择这两路数据中的一路数据发送给网络设备2，即网络设备1发送的数据在切换开关13处实现数据的选收，即选择网卡11或网卡12的数据发送给网络设备2，通常选择网卡11(即主板)的数据，在网卡11故障时选择网卡12(即备板)的数据；网络设备1在接收来自网络设备2的数据时，切换开关13会将接收到的数据分别通过FlexE接口a和FlexE接口b发送给网卡11和网卡12，即接收到的数据在切换开关13处实现数据的双发，以使网卡11和网卡12均接收到该数据。
应理解，图6中所示的系统仅以2个用户设备和2个网络设备为例进行说明，该FlexE通信系统中还可以包括更多数量的用户设备和网络设备，本申请实施例对此不做限定。图6中所示的FlexE通信系统仅是举例说明，本申请提供的FlexE通信系统的应用场景不限于图6所示的场景。本申请提供的技术方案适用于所有应用采用FlexE技术进行数据传输的网络场景。
图7为本申请实施例提供的一种灵活以太网开销帧处理方法的流程示意图，该方法应用于包括主板和备板的第一网络设备中，比如，第一网络设备为上述图6所示的网络设备1，该方法包括以下几个步骤。
S201：主板向备板发送第一指示信息，第一指示信息用于指示该主板的第一PHY上承载的业务数据流的第一开销帧的相位。
其中，该主板与网络之间可以对应第一FlexE group(也可以称为第一FlexE接口)， 第一FlexE group可以包括多个PHY，第一PHY可以是该多个PHY中的任意一个PHY。第一PHY上承载的业务数据流可以包括一个或者多个客户的数据。具体的，在该主板未发生故障，第一网络设备通过该主板向第二网络设备发送该业务数据流(即第一网络设备中的切换开关选择该主板的数据发送给第二网络设备)的过程中，该主板可以向该备板发送第一指示信息，第一指示信息用于指示该主板的第一PHY上承载的业务数据流的第一开销帧的相位。第一开销帧可以是该主板当前发送的开销帧(也可以称为FlexE帧)，第一开销帧的相位可以是指当前发送的第一开销帧的时域位置，比如，该时域位置可以为时隙。
可选的，第一指示信息可以包括第一开销帧的帧头位置；其中，第一开销帧可以包括8个开销块，第一开销帧的帧头可以是指这8个开销块中的第一个开销块，该帧头位置即为第一开销块的时域位置，从而第一开销帧的相位可以为第一开销帧的帧头位置(或称为第一开销块的时域位置)。进一步的，第一指示信息还可以包括第一开销帧的特征信息，该特定信息可以包括填充块PAD相位、和/或对齐标志字(aligment marker，AM)相位；其中，PAD和AM是以太网中分别用于做速率匹配和数据对齐的，在该业务数据流的发送过程中该PAD和该AM会按照一定规律插入该业务数据流中。比如，第一网络设备在该业务数据流中可以按照间隔a1插入开销帧，按照间隔a2插入PAD，按照间隔a3插入AM，若开销帧、PAD和AM在初始化时的相位是对齐的，则该业务数据流在经过a1、a2和a3的最小公倍数的传输后，开销帧、PAD和AM的相位会再次对齐，这样第二网络设备在接收到该业务数据流时可基于该开销帧、该PAD或者该AM中的任意一个即可实现数据对齐。需要说明的是，关于该PAD和AM的相关描述可以参见相关技术中的阐述，本申请实施例在此不再赘述。
具体的，在第一网络设备通过该主板发送第一开销帧的过程中，该主板可以对第一开销帧进行采样，以确定第一指示信息中包括的第一开销帧的帧头位置；进一步的，该主板还可以从该帧头位置开始统计比特块(block)的数量，以确定该PAD和该AM分别相对于第一开销帧的帧头的比特块的数量，即确定第一指示信息中包括的第一开销帧中的PAD相位和AM相位；之后，该主板可以向该备板发送第一指示信息。
在一种可能的实施例中，该主板还可以使用单比特编码格式对第一指示信息进行编码。示例性的，如图8所示，该主板可以从第一开销帧的帧头位置开始编码，通过M(M为正整数)个编码周期(比如，采用10MHz的编码频率，即一个编码周期为100ns)完成该帧头的编码，该帧头可以包括N个周期的高电平和N个周期的低电平，比如，M等于20、N等于10。此外，如图8所示，对于第一指示信息中的其他信息(比如，第一开销帧的特征信息)，可以采用一个编码周期内“x”长度的高电平和“y”长度的高电平的编码方式表示数据“0”，及采用一个编码周期内“y”长度的高电平和“x”长度的高电平的编码方式表示数据“1”的方式，比如，x＝25ns、y＝75ns。进一步的，当每次使用的编码版本不同时，第一指示信息中还可以包括编码版本号；第一指示信息中还可以包括循环冗余校验码CRC8，该CRC8可用于校验该编码版本号和第一开销帧的特征信息(以长度为86比特(bits)为例)，以保证该编码版本号和第一开销帧的特征信息的安全性。此外，第一指示信息中还可以包括结束字段，比如，该结束字段可以为k个编码周期的低电平，比如，k＝30。
S202：当该备板接收到第一指示信息时，该备板根据第一开销帧的相位确定该备板的第二PHY上承载的该业务数据流的第二开销帧的相位，第二开销帧是第一开销帧的下一个开销帧。
其中，该备板与网络之间可以对应第二FlexE group(也可以称为第二FlexE接口)，第二FlexE group可以包括多个PHY，第二PHY可以是该多个PHY中用于承载该业务数据流的一个PHY，即第二PHY承载的业务数据流与第一PHY上承载的业务数据流为同一业务数据流。当该备板接收到第一指示信息时，该备板可以根据第一指示信息确定第一开销帧的相位，从而根据第一开销帧的相位确定该业务数据流在第二PHY上的第二开销帧的相位。
具体的，当第一指示信息包括第一开销帧的帧头位置时，该备板可以根据第一开销帧的帧头位置、以及两个开销帧之间的间隔(该间隔是固定的，比如，该间隔可以为163688(即20×1023×8+8)个64B/66B比特块)，确定该业务数据流在第一PHY上的第二开销帧的帧头位置；之后，该备板可以根据第一PHY上的第二开销帧的帧头位置对齐该业务数据流在第二PHY上的第二开销帧的帧头位置，比如，将第一PHY上的第二开销帧的帧头位置作为该数据流在第二PHY上的第二开销帧的帧头位置，即实现该业务数据流在第二PHY上的第二开销帧的相位的对齐。进一步的，当第一指示信息还包括PAD相位时，该备板还可以根据该PAD相位确定该业务数据流在第二PHY上的第二开销帧中的PAD相位，若该PAD相位为该PAD与第一开销帧的帧头之间的间隔，则该备板可以根据该PAD相位、两个PAD之间的间隔和两个开销帧之间的间隔确定第二PHY上的第二开销帧中的PAD相位。同理，当第一指示信息还包括AM相位时，该备板还可以根据该AM相位确定该业务数据流在第二PHY上的第二开销帧中的AM相位，若该AM相位为该AM与第一开销帧的帧头之间的间隔，则该备板可以根据该AM相位、两个AM之间的间隔和两个开销帧之间的间隔确定第二PHY上的确定第二开销帧中的AM相位。这样，该备板按照上述方式可以保证该主板的第一PHY上的第二开销帧中的PAD相位和AM相位分别与该备板的第二PHY上的第二开销帧中的PAD相位和AM相位是对齐的，从而保证该主板和该备板对于PAD和AM的插入的一致性。
在一种可能的实施例中，当该主板使用单比特编码格式对第一指示信息进行编码时，该备板可以在接收到第一指示信息时对第一指示信息进行解码，以得到第一指示信息中的相关信息。示例性的，以图8所示的编码方式为例，该备板可以在检测到来自主板的数据流的信号向上跳变后开始解码，当连续接收到N个周期的高电平后，检测到信号向下跳变时确定该向下跳变的位置为第一开销帧的帧头位置；之后，连续检测到N个周期的低电平，若检测到连续N个周期的低电平则第一开销帧的帧头位置正确，若未检测到连续N个周期的低电平则重新确定第一开销帧的帧头位置。进一步的，该备板可以根据数据“0”和数据“1”的编码方式分别解码出编码版本号、第一开销帧的特征信息(比如，PAD相位和AM相位)和CRC8等，该编码版本号可用于指示编码版本，以使该备板可以根据该编码版本号识别不同编码版本之间的差异。相应的，该备板还可以根据CRC8对第一开销帧的特征信息进行校验，若检验成功即确定第一开销帧的特征信息正确，若校验失败，则重新开始检测第一指示信息。最后，当该备 板检测到结束字段，比如，检测到k(比如，k＝30)个编码周期的低电平时，该备板即可确定第一指示信息解码完成。
需要说明的是，该备板在检测N个周期的低电平或N个周期的高电平时，会由于板间走线的影响等导致信号发生抖动，从而实际检测到低电平或高电平的周期会大于或小于N，比如检测到的周围数为N+1或N-1。因此，只要N与检测到的低电平的周期数之差的绝对值小于预设阈值，即可认为检测到N个周期的低电平或N个周期的高电平。
进一步的，如图9所示，该方法还可以包括：S203。
S203：该备板根据板间传输时延和/或编解码时延，补偿该业务数据流在第二PHY上的第二开销帧的相位。
其中，该板间传输时延可以是指第一开销帧的相位(比如，第一开销帧的帧头位置)从该主板传输至该备板的传输时延，该板间传输时延可以事先通过诸如示波器等外部硬件设备测量后配置给该备板，从而在需要补偿第二PHY上的第二开销帧的相位时，该备板即可根据相应的配置直接获取该板间传输时延。另外，该编解码时延包括编码时延和解码时延，该编码时延是指该主板编码第一开销帧的相位时的时延，该解码时延是指该备板解码第一开销帧的相位时的时延。该编码时延和该解码时延可以事先通过测量得到，并可以配置给该备板。
具体的，当第一指示信息包括第一开销帧的帧头位置，该主板将单比特编码后的第一指示信息发送给该备板时，该备板确定该业务数据流在第二PHY上的第二开销帧的相位可以包括：根据第一开销帧的帧头位置、该编码时延、该板间传输时延、该解码时延、第一开销帧的特征信息的传输时延和开销帧间隔，确定该业务数据流在第二PHY上的第二开销帧的相位，该第二开销帧的相位为第二开销帧的帧头位置。示例性的，如图10所示，以第一PHY和第二PHY为100G PHY为例，若第一PHY上的第一开销帧的帧头为T0、该编码时延为t1、该板间传输时延为t2、该解码时延为t3、第一开销帧的特征信息的传输时延为t4(t4小于开销帧的间隔)，开销帧的间隔为Δt，则该备板确定第一PHY上的第二开销帧的相位为T1(比如，T1＝T0+Δt-t1-t2-t3-t4)，从而将第二PHY上的第二开销帧的相位确定为T1。图10中的t5＝Δt-t1-t2-t3-t4，即补偿第一开销帧的相位后实际距离第二开销帧的间隔。
该备板通过上述方式确定该业务数据流在第二PHY上的第二开销帧的相位后，可以使得该业务数据流在第一PHY和第二PHY上的同一开销帧的相位是对齐的，也可以理解为该业务数据流在第二PHY上的开销帧的相位跟踪对齐该业务数据流在第一PHY上的开销帧的相位。这样，当该主板发生故障时，第一网络设备可以通过该备板向第二网络设备发送该业务数据流，比如，该备板在第二PHY上以对齐后的第二开销帧的相位发送该业务数据流。由于该主板和该备板发送的业务数据流的开销帧的相位是对齐的，从而在该主板发生故障，第二网络设备接收到该备板发送的该业务数据流时，第二网络设备仍然可以锁定该业务数据流中的开销帧，并基于锁定的开销帧实现多个PHY中的数据对齐，进而从对齐的数据中抽取客户的数据。可选的，当第一指示信息中还包括第一开销帧的PAD相位或AM相位时，第二网络设备也可以基于该PAD相位或该AM相位实现多个PHY中的数据对齐。
需要说明的是，第二网络设备锁定开销帧、基于锁定的开销帧实现多个PHY中的数据对齐、以及从对齐的数据抽取客户的数据具体过程可以参考现有技术的相关描述，本申请实施例在此不再赘述。
进一步的，如图9所示，该方法还可以包括：S204-S205。其中，S204-S205与S201-S203可以不分先后顺序，图9中以S204-S205位于S203之后为例进行说明。
S204：该备板根据第一PHY和第二PHY上承载的该业务数据流的同一个开销帧的帧头，确定该主板与该备板之间的帧头相位偏差。
其中，该备板可用于检测该业务数据流在该主板和该备板上的同一开销帧的帧头之间的相位偏差。比如，该备板中可以集成有一个计数器，该计数器可用于在该备板确定的该主板上的某一开销帧的帧头位置开始计数，并在该备板上的同一开销帧的帧头位置(或者在计算得到的该备板上的同一开销帧的帧头位置)时停止计数，该计数器的累加值即为该业务数据流在该主板和该备板上的同一开销帧的帧头之间的相位偏差。例如，在该主板的第一开销帧早于该备板的第一开销帧的场景下，该计数器首先在“该备板计算得到的该主板上的第一开销帧的帧头”时开始计数，之后在该备板上的第一开销帧的帧头到来时停止计数，该计数器对应的累加值即为该帧头相位偏差。
S205：当该帧头相位偏差大于预设偏差时，该备板触发告警信息。
比如，该预设偏差为5ns，该备板通过计算器得到的相位偏差为7ns，则该备板可以向第一网络设备中的处理器发送告警信息，以使该主板和该备板之间重新对齐开销帧。其中，该预设偏差可以事先进行设置，比如，该预设偏差可以根据第一网络设备中用于切换该主板和该备板的切换开关的对齐能力确定，本申请实施例对此不作具体限制。
为便于理解，下面以图11所示的第一网络设备的结构为例，对本申请实施例提供的方法进行举例说明。假设该主板与网络之间的FlexE group为第一FlexE group(也可以称为工作组(working group))、该备板与网络之间的FlexE group为第二FlexE group(也可以称为备用组(backup group))，则第一FlexE group和第二FlexE group中可以包括接收(receive，RX)解码(decode)单元、帧头锁定和检查单元、PHY相位对齐单元、发送(transmit，TX)编码(code)单元和取样单元。该主板与该备板还可以各自连接有一个可编程器件，用于对各自交互的数据进行编译或译码等。具体的，以该主板向该备板发送第一指示信息为例，该主板中的取样单元可用于对第一FlexE group中的第一PHY上承载的业务数据流的第一开销帧的帧头进行采样；该主板中的TX编码单元可用于对采样的第一开销帧的帧头进行编码并发送给该备板；该备板中的RX解码单元可以对接收的数据进行解码；该备板中的帧头锁定和检查单元可根据解码后的数据锁定第一开销帧的帧头，以及检查该主板和该备板中同一开销帧的帧头相位偏差；该备板中的PHY相位对齐单元可用于根据第一开销帧的帧头对齐该备板的第二开销帧的帧头。
需要说明的是，本申请实施例中的主板和备板可以互换，比如，该备板升级为主板时，该备板也可以将当前发送的开销帧的相位发送给该主板，以使该主板跟踪对齐该备板的开销帧的相位。上述仅以该备板跟踪对齐该主板的开销帧的相位为例进行说明，本申请实施例所提供的技术方案同样适用于该主板跟踪对齐该备板的开销帧的相 位的方案中，在此不再赘述。
在本申请实施例中，该主板向该备板发送第一指示信息，第一指示信息用于指示该主板上的该业务数据流的第一开销帧的相位，该备板在接收到第一指示信息时，可以根据第一开销帧的相位确定该备板上的该业务数据流的第二开销帧的相位，从而使得该业务数据流在该备板上的开销帧的相位跟踪对齐该业务数据流在该主板上的开销帧的相位。这样，当该主板发生故障时，第一网络设备可以通过该备板向第二网络设备发送该业务数据流，由于该主板和该备板发送的该业务数据流的开销帧的相位是对齐的，从而第二网络设备仍然可以锁定该业务数据流中的开销帧，进而降低了因为该主板中的某一PHY故障而导致其他正常工作的PHY上的业务数据流受损的影响。
上述主要从第一网络设备的角度对本申请实施例提供的方法进行了介绍。可以理解的是，第一网络设备为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的网元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对第一网络设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
本申请实施例提供了一种第一网络设备，第一网络设备的结构示意图可以如图6中的网络设备1所示。第一网络设备包括：网卡11和网卡12，网卡11可以作为主板，网卡12可以作为备板。其中，网卡11用于支持第一网络设备执行上述方法实施例中的S201；网卡12用于支持第一网络设备执行上述方法实施例中的S202-S205中的一个或者多个，和/或用于本文所描述的技术的其他过程。进一步的，第一网络设备还包括：切换开关13；其中，切换开关13用于支持第一网络设备在网卡11未故障时选择网卡11发送的数据发送给第二网络设备，在网卡11故障时选择网卡12发送的数据发送给第二网络设备。上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是一个物理单元或多个物理单元，即可以位于一个地方，或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施 例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该软件产品存储在一个存储介质中，包括若干指令用以使得终端执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是：以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (20)

  1. 一种灵活以太网开销帧处理方法，其特征在于，应用于包括主板和备板的网络设备中，所述方法包括：
    所述主板向所述备板发送第一指示信息，所述第一指示信息用于指示所述主板的第一物理层接口PHY上承载的业务数据流的第一开销帧的相位；
    所述备板接收所述第一指示信息，并根据所述第一开销帧的相位确定所述备板的第二PHY上承载的所述业务数据流的第二开销帧的相位，所述第二开销帧是所述第一开销帧的下一个开销帧。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    当所述主板未发生故障时，所述主板在所述第一PHY上以所述第一开销帧的相位发送所述业务数据流；
    当所述主板发生故障时，所述备板在所述第二PHY上以所述第二开销帧的相位发送所述业务数据流。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一指示信息是以单比特编码格式编码后的信息。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述第一指示信息包括所述第一开销帧的帧头位置。
  5. 根据权利要求4所述的方法，其特征在于，所述备板根据所述第一开销帧的相位确定所述备板的第二PHY上承载的所述业务数据流的第二开销帧的相位，包括：
    所述备板根据所述第一开销帧的帧头位置和开销帧间隔，确定所述第一PHY上的第二开销帧的帧头位置；
    根据所述第一PHY上的第二开销帧的帧头位置，确定所述备板上的第二PHY上承载的所述业务数据流的第二开销帧的相位。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述方法还包括：
    所述备板根据板间传输时延和/或编解码时延，补偿所述备板上的第二PHY上承载的所述业务数据流的第二开销帧的相位。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述第一指示信息还包括以下至少一项：编码版本号、所述第一开销帧的特征信息。
  8. 根据权利要求7所述的方法，其特征在于，所述第一指示信息还包括：循环冗余校验码，所述循环冗余校验码用于校验所述编码版本号和/或所述第一开销帧的特征信息。
  9. 根据权利要求7或8所述的方法，其特征在于，所述特征信息包括填充块PAD相位，所述方法还包括：根据所述PAD相位确定所述业务数据流在所述第二PHY上的所述第二开销帧中的PAD相位；
    和/或，
    所述特征信息还包括对齐标志字AM相位，所述方法还包括：根据所述AM相位确定所述业务数据流在所述第二PHY上的所述第二开销帧中的AM相位。
  10. 根据权利要求1-9任一项所述的方法，其特征在于，所述方法还包括：
    所述备板根据所述第一PHY和所述第二PHY上承载的所述业务数据流的同一个开销帧的帧头，确定所述主板与所述备板之间的帧头相位偏差；
    当所述帧头相位偏差大于预设偏差时，所述备板触发告警信息。
  11. 一种灵活以太网开销帧处理装置，其特征在于，所述装置包括主板和备板；其中，
    所述主板，用于向所述备板发送第一指示信息，所述第一指示信息用于指示所述主板的第一物理层接口PHY上承载的业务数据流的第一开销帧的相位；
    所述备板，用于接收所述第一指示信息，并根据所述第一开销帧的相位确定所述备板的第二PHY上承载的所述业务数据流的第二开销帧的相位，所述第二开销帧是所述第一开销帧的下一个开销帧。
  12. 根据权利要求11所述的装置，其特征在于，
    所述主板，还用于当所述主板未发生故障时，所述主板在所述第一PHY上以所述第一开销帧的相位发送所述业务数据流；
    所述备板，还用于当所述主板发生故障时，所述备板在所述第二PHY上以所述第二开销帧的相位发送所述业务数据流。
  13. 根据权利要求11或12所述的装置，其特征在于，所述第一指示信息是以单比特编码格式编码后的信息。
  14. 根据权利要求11-13任一项所述的装置，其特征在于，所述第一指示信息包括所述第一开销帧的帧头位置。
  15. 根据权利要求14所述的装置，其特征在于，所述备板还用于：
    根据所述第一开销帧的帧头位置和开销帧间隔，确定所述第一PHY上的第二开销帧的帧头位置；
    根据所述第一PHY上的第二开销帧的帧头位置，确定所述备板上的第二PHY上承载的所述业务数据流的第二开销帧的相位。
  16. 根据权利要求11-15任一项所述的装置，其特征在于，所述备板还用于：
    根据板间传输时延和/或编解码时延，补偿所述第二PHY上承载的所述业务数据流的第二开销帧的相位。
  17. 根据权利要求11-16任一项所述的装置，其特征在于，所述第一指示信息还包括以下至少一项：编码版本号、所述第一开销帧的特征信息。
  18. 根据权利要求17所述的装置，其特征在于，所述第一指示信息还包括：循环冗余校验码，所述循环冗余校验码用于校验所述编码版本号和/或所述第一开销帧的特征信息。
  19. 根据权利要求17或18所述的装置，其特征在于，所述特征信息包括填充块PAD相位，所述备板还用于：根据所述PAD相位确定所述业务数据流在所述第二PHY上的所述第二开销帧中的PAD相位；
    和/或，
    所述特征信息还包括对齐标志字AM相位，所述备板还用于：根据所述AM相位确定所述业务数据流在所述第二PHY上的所述第二开销帧中的AM相位。
  20. 根据权利要求11-19任一项所述的装置，其特征在于，所述备板还用于：
    根据所述第一PHY和所述第二PHY上承载的所述业务数据流的同一个开销帧的帧头，确定所述主板与所述备板之间的帧头相位偏差；
    当所述帧头相位偏差大于预设偏差时，触发告警信息。
PCT/CN2020/139132 2020-12-24 2020-12-24 一种灵活以太网开销帧处理方法及装置 WO2022133938A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP20966510.8A EP4254843A4 (en) 2020-12-24 2020-12-24 METHOD AND APPARATUS FOR PROCESSING FLEXIBLE ETHERNET OVERHEAD FRAME
PCT/CN2020/139132 WO2022133938A1 (zh) 2020-12-24 2020-12-24 一种灵活以太网开销帧处理方法及装置
CN202080108101.4A CN116746093A (zh) 2020-12-24 2020-12-24 一种灵活以太网开销帧处理方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/139132 WO2022133938A1 (zh) 2020-12-24 2020-12-24 一种灵活以太网开销帧处理方法及装置

Publications (1)

Publication Number Publication Date
WO2022133938A1 true WO2022133938A1 (zh) 2022-06-30

Family

ID=82157168

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/139132 WO2022133938A1 (zh) 2020-12-24 2020-12-24 一种灵活以太网开销帧处理方法及装置

Country Status (3)

Country Link
EP (1) EP4254843A4 (zh)
CN (1) CN116746093A (zh)
WO (1) WO2022133938A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024002188A1 (zh) * 2022-07-01 2024-01-04 华为技术有限公司 用于灵活以太网的方法、网络设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101043309A (zh) * 2007-04-13 2007-09-26 华为技术有限公司 主备倒换的控制方法以及装置
CN101277164A (zh) * 2008-05-15 2008-10-01 中兴通讯股份有限公司 一种同步数字体系业务总线无损切换的方法
WO2011022883A1 (zh) * 2009-08-26 2011-03-03 华为技术有限公司 光网络倒换保护方法、装置及系统
CN109688016A (zh) * 2019-01-25 2019-04-26 中兴通讯股份有限公司 灵活以太网协议中切换时隙配置的方法及相关设备

Family Cites Families (3)

* 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
CN110719143A (zh) * 2015-07-30 2020-01-21 华为技术有限公司 用于数据传输的方法、发送机和接收机
US10454610B2 (en) * 2017-11-13 2019-10-22 Fujitsu Limited 1+1 Ethernet fabric protection in a disaggregated optical transport network switching system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101043309A (zh) * 2007-04-13 2007-09-26 华为技术有限公司 主备倒换的控制方法以及装置
CN101277164A (zh) * 2008-05-15 2008-10-01 中兴通讯股份有限公司 一种同步数字体系业务总线无损切换的方法
WO2011022883A1 (zh) * 2009-08-26 2011-03-03 华为技术有限公司 光网络倒换保护方法、装置及系统
CN109688016A (zh) * 2019-01-25 2019-04-26 中兴通讯股份有限公司 灵活以太网协议中切换时隙配置的方法及相关设备

Non-Patent Citations (1)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024002188A1 (zh) * 2022-07-01 2024-01-04 华为技术有限公司 用于灵活以太网的方法、网络设备及存储介质

Also Published As

Publication number Publication date
EP4254843A4 (en) 2023-12-27
EP4254843A1 (en) 2023-10-04
CN116746093A (zh) 2023-09-12

Similar Documents

Publication Publication Date Title
EP3393136B1 (en) Flexible ethernet node and method for oam
US8412040B2 (en) Method and apparatus for mapping traffic using virtual concatenation
CN113508543B (zh) 用于将恒定比特率客户端信号适配到电信信号的路径层中的方法
EP2819362B1 (en) Multi-lane transmission device and multi-lane transmission method
US6584535B1 (en) Configurable serial interconnection
JP5111591B2 (ja) 複数ギガビットイーサネット（登録商標）アーキテクチャの方法および装置
JP5943221B2 (ja) ネットワークデバイスおよび情報送信方法
US7813271B2 (en) Aggregated link traffic protection
JP7282187B2 (ja) フレキシブルイーサネット通信方法及びネットワーク装置
US20040136711A1 (en) Optical fiber ring communication system
WO2019128887A1 (zh) 一种灵活以太网中故障指示方法以及装置
EP3909209A1 (en) Ethernet signal format using 256b/257b block encoding
CN113574826B (zh) 交互时钟同步报文的方法及装置
WO2019029419A1 (zh) 透传业务频率的方法和设备
WO2017121158A1 (zh) 处理弹性以太网信号的方法和装置
JP7163508B2 (ja) フレキシブルイーサネット通信方法とネットワークデバイス
US20200288468A1 (en) Data transmission method and device
WO2022133938A1 (zh) 一种灵活以太网开销帧处理方法及装置
US6973072B1 (en) High performance protocol for an interconnect system of an intermediate network node
Ethernet Implementation agreement
US20200169350A1 (en) Method And Apparatus For Processing Bit Block Stream, Method And Apparatus For Rate Matching Of Bit Block Stream, And Method And Apparatus For Switching Bit Block Stream
US7039073B1 (en) Bound mode technique for accommodating high-bandwidth data flow within an intermediate network node
WO2023141777A1 (zh) 通信方法及网络设备
WO2024002188A1 (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: 20966510

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202080108101.4

Country of ref document: CN

ENP Entry into the national phase

Ref document number: 2020966510

Country of ref document: EP

Effective date: 20230627

NENP Non-entry into the national phase

Ref country code: DE