WO2024032191A1 - 一种故障码块处理方法及装置 - Google Patents

一种故障码块处理方法及装置 Download PDF

Info

Publication number
WO2024032191A1
WO2024032191A1 PCT/CN2023/103322 CN2023103322W WO2024032191A1 WO 2024032191 A1 WO2024032191 A1 WO 2024032191A1 CN 2023103322 W CN2023103322 W CN 2023103322W WO 2024032191 A1 WO2024032191 A1 WO 2024032191A1
Authority
WO
WIPO (PCT)
Prior art keywords
code block
inner layer
communication device
code
layer
Prior art date
Application number
PCT/CN2023/103322
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 华为技术有限公司
Publication of WO2024032191A1 publication Critical patent/WO2024032191A1/zh

Links

Classifications

    • 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/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0006—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission format
    • H04L1/0007—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission format by modifying the frame length
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • 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
    • 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/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0061—Error detection codes

Definitions

  • the present application relates to the field of communications, and in particular to a fault code block processing method and device.
  • Flexible Ethernet (FlexE) technology has the advantage of flexibly allocating bandwidth on demand, which can meet the needs of mobile bearer, home broadband, dedicated line access and other network scenarios. Therefore, the application of FlexE technology is becoming more and more widespread.
  • the FlexE technology can support fine-grained services.
  • the time slot (slot) corresponding to the FlexE large bandwidth can be further divided into multiple sub-slots (sub-slots) for carrying fine-grained services.
  • the services carried by the time slots corresponding to the FlexE large bandwidth can also be called large-granularity services
  • the fine-grained services can also be called small-granularity services.
  • small particles and “fine-grained” may be used interchangeably.
  • transmission errors may occur during the transmission of small-grain services.
  • how to handle small-grain services with transmission errors is a problem that has yet to be solved.
  • Embodiments of the present application provide a method and device for processing faulty code blocks, which can avoid error propagation when errors occur in small-grain services during transmission.
  • error diffusion can be understood as the number of identified error code blocks is greater than the actual number of error code blocks. For example, there are actually 3 code blocks with errors, but during code block analysis, all code blocks are are identified as error code blocks.
  • error propagation can be understood as escaping the cyclic redundancy check (CRC) of the Ethernet frame, such as CRC32, when recovering an Ethernet frame based on error code blocks, causing the error code blocks to propagate to the business layer or even application layer.
  • CRC cyclic redundancy check
  • embodiments of the present application provide a fault code block processing method, which can be applied to a first communication device using FlexE fine-grained technology.
  • the first communication device can acquire a first fine-grained basic unit (fgBU), the first fgBU is composed of a plurality of first outer layer code blocks, and the plurality of first outer layer code blocks
  • the first outer layer code block includes an outer layer start (start, S) code block, a plurality of outer layer data (data, D) code blocks and a first outer layer error (error, E) code block.
  • start, S outer layer start
  • data data
  • E error
  • the first outer layer E code block is used to carry data of the first inner layer code block.
  • the first inner layer code block may be restored according to the first fgBU, and the first inner layer code block may be set as the first inner layer E code block.
  • the first inner code block may lead to error diffusion.
  • the E code block when the error correction algorithm cannot perform error correction, the entire first fgBU may be recognized.
  • the first communication device after obtaining the first fgBU, can set the first inner layer code block corresponding to the first outer layer E code block to the first inner layer E code block, thereby avoiding the problem due to the first inner layer E code block.
  • An inner code block error causes error propagation.
  • the inner layer code blocks may include S code blocks, D code blocks, and T code blocks, and may also include idle (Idle, I)) code blocks and/or O code blocks. Therefore, the first inner layer code block may be any one of an S code block, a D code block, a T code block, an idle I code block, and an O code block.
  • the first communication device is a fine-grained service switching node, then in an example, the first inner layer code block can be set to the first Inner E code block.
  • the first inner layer code block may correspond to the first sub-time slot, and the first sub-time slot may correspond to multiple inner layer code blocks.
  • the first inner layer code block If there is an error in the code block, then the entire data carried in the first sub-slot also has an error.
  • “set the first inner layer code block to the first inner layer E code block” In specific implementation, multiple inner layer code blocks corresponding to the first sub-slot may be set as inner layer E code blocks.
  • first inner layer code block and the plurality of inner layer code blocks corresponding to the first sub-slot may be set as Inner layer E code blocks, for another example, all code blocks corresponding to the first sub-slot can be set as E code blocks. In this way, error propagation caused by errors in the first inner layer code block can be avoided.
  • the first outer layer E The code block may be the first outer layer D code block where the error occurs, or the first outer layer T code block where the error occurs.
  • the first communication device may be a fine-grained service switching node.
  • the first communication device sets the first inner layer code block as the first inner layer After the E code block, the first inner layer E code block may be sent to the second communication device.
  • the first communication device may send a code block stream including the first inner layer E code block to the second communication device, wherein the code block stream including the first inner layer E code block , which can be the code block stream after secondary encoding.
  • the first communication device may send the first inner layer E code block to the second communication device instead of sending the first inner layer code block in which the error occurred to the second communication device.
  • the second communication device can, for example, discard the first inner layer E code block, thereby avoiding The second communication device restores the Ethernet frame based on the erroneous first inner layer code block, thereby achieving the effect of avoiding error propagation.
  • the first communication device may be a sink node of fine-grained services.
  • the first communication device sets the first inner layer code block as the first inner layer code block.
  • the first inner layer E code block can be sent to the Ethernet frame client signal recovery module of the first communication device, so that the Ethernet frame client signal recovery module can perform data recovery and obtain each client Corresponding Ethernet frame. Since the first inner layer code block is set as the first inner layer E code block, when the Ethernet frame client signal recovery module recovers the Ethernet frame, the first inner layer E code block can be discarded instead of the first inner layer E code block.
  • An inner E code block is processed as a normal code block, therefore, error propagation can be avoided.
  • the first outer layer E code block can not only carry the first inner layer code block, but also can carry the second inner layer code block.
  • the first communication device can also restore the second inner layer code block according to the first fgBU, and set the second inner layer code block to the second inner layer E code block, thereby avoiding Error propagation occurs due to errors in the second inner layer code block.
  • the first communication device is a fine-grained service switching node.
  • the first communication device sets the second inner layer code block after the second inner layer E code block.
  • the second inner layer E code block may also be sent to the second communication device.
  • the first communication device may send the first inner layer E code block and the second inner layer E code block to the second communication device.
  • the second communication device may, for example, discard all the The first inner layer E code block and the second inner layer E code block are used to prevent the second communication device from recovering the Ethernet frame based on the erroneous first inner layer code block and the erroneous second inner layer code block, thereby achieving Avoid error propagation effects.
  • the first communication device is the sink node of fine-grained services.
  • the first communication device sets the second inner layer code block to the second inner layer E code block.
  • the second inner layer E code block may also be sent to the Ethernet frame client signal recovery module of the first communication device.
  • the first communication device may send the first inner E code block and the second inner E code block to the Ethernet frame client signal recovery module.
  • the Ethernet frame client signal recovery module recovers the Ethernet frame
  • the first inner E code block and the second inner E code block can be discarded instead of the first inner E code block and the second inner E code block.
  • E code blocks are processed as normal code blocks, therefore, error propagation can be avoided.
  • the plurality of first outer layer code blocks also include a second outer layer E code block, and the second outer layer E code block is a second outer layer D code block where an error occurred, The second outer layer E code block is used to carry the data of the third inner layer code block; the method further includes: restoring the third inner layer code block according to the first fgBU, and converting the third inner layer code block to The layer code block is set as the third inner layer E code block.
  • the method further includes: obtaining a second fgBU, the second fgBU is composed of a plurality of second outer layer code blocks, the plurality of second outer layer code blocks include an outer layer S code block, a plurality of outer layer D code blocks, and a fourth outer layer E code block, the fourth outer layer E code block is used to carry the data of the fourth inner layer code block; according to the second fgBU, restore all As for the fourth inner layer code block, the fourth inner layer code block is set as a fourth inner layer E code block.
  • inventions of the present application provide a fault code block processing device, which is applied to the first communication device using FlexE fine-grained technology.
  • the fault code block processing device includes a transceiver unit and a processing unit.
  • the transceiver unit is configured to perform reception and/or transmission-related operations performed by the first communication device in the above-mentioned first aspect and various possible implementations of the first aspect;
  • the processing unit is configured to perform the above-mentioned third aspect. Operations other than reception and/or transmission related operations performed by the first communication device in one aspect and various possible implementations of the first aspect.
  • the transceiver unit may include a receiving unit and/or a sending unit, the receiving unit is used to perform reception-related operations, and the sending unit is used to perform sending-related operations.
  • the first communication device may include a receiving unit and a processing unit.
  • the receiving unit is used to obtain the first fine-grained basic unit fgBU, the first fgBU is composed of a plurality of first outer layer code blocks, and the plurality of first outer layer code blocks include an outer layer starting S code block, multiple an outer data D code block, and a first outer layer error E code block, the first outer layer E code block is used to carry the data of the first inner layer code block; a processing unit, used to carry out the data of the first inner layer code block according to the first fgBU , restore the first inner layer code block, and set the first inner layer code block as the first inner layer E code block.
  • the first inner layer code block corresponds to the first sub-slot
  • setting the first inner layer code block as the first inner layer E code block includes: setting the first inner layer code block A plurality of inner layer code blocks corresponding to the first sub-slot are set as inner layer E code blocks, and the plurality of inner layer code blocks include the first inner layer code block.
  • the plurality of first outer layer code blocks further include an end T code block, and the first outer layer E code block is the first outer layer D code block in which an error occurs.
  • the first outer E code block is a T code block in which an error occurs.
  • the first communication device is a fine-grained service switching node, and the device further includes: a sending unit configured to send the first inner layer E code block to the second communication device.
  • the first communication device is a sink node of fine-grained services
  • the device further includes: a sending unit configured to send the first inner layer E code block to the first Ethernet frame client signal recovery module for communication devices.
  • the first outer layer E code block is also used to carry data of the second inner layer code block
  • the processing unit is also used to: restore the said first fgBU according to the first fgBU.
  • a second inner layer code block, and the second inner layer code block is set as a second inner layer E code block.
  • the first communication device is a fine-grained service switching node
  • the device includes a sending unit further configured to: send the second inner layer E code block to the second communication device.
  • the first communication device is a sink node of fine-grained services
  • the sending unit included in the device is further configured to: send the second inner layer E code block to the third An Ethernet frame client signal recovery module of a communication device.
  • the plurality of first outer layer code blocks also include a second outer layer E code block, and the second outer layer E code block is a second outer layer D code block where an error occurred,
  • the second outer layer E code block is used to carry the data of the third inner layer code block;
  • the processing unit is also used to: restore the third inner layer code block according to the first fgBU, and convert the The third inner layer code block is set as the third inner layer E code block.
  • the receiving unit is further configured to: obtain a second fgBU, the second fgBU is composed of a plurality of second outer layer code blocks, and the plurality of second outer layer code blocks include An outer S code block, a plurality of outer D code blocks, and a fourth outer E code block.
  • the fourth outer E code block is used to carry the data of the fourth inner code block; the processing unit also Used to restore the fourth inner layer code block according to the second fgBU, and set the fourth inner layer code block as a fourth inner layer E code block.
  • the first inner layer code block includes any one of the following types of code blocks: S code block, D code block, T code block, idle I code block, or O code block.
  • the first communication device is a fine-grained service switching node
  • setting the first inner layer code block as a first inner layer E code block includes: the first communication device The outbound interface of the device sets the first inner layer code block as the first inner layer E code block.
  • this application provides a fault code block processing device.
  • the fault code block processing device includes a memory and a processor; the memory is used to store program codes; the processor is used to run the program.
  • the instructions in the code cause the communication device to execute the above first aspect and the method described in any one of the first aspects.
  • this application provides a fault code block processing device, which includes a communication interface and a processor.
  • the communication interface is used to perform the sending and receiving operations performed by the first communication device according to any one of the above first aspect and the first aspect
  • the processor is used to perform the above first aspect and the first aspect.
  • the first communication device described in any one of the embodiments performs other operations other than the sending and receiving operations.
  • embodiments of the present application provide a computer-readable storage medium, including instructions or computer programs that, when run on a processor, execute any of the methods described in the first aspect above.
  • embodiments of the present application provide a computer program product, including a computer program product that, when run on a processor, executes the above first aspect and the method described in any one of the first aspects.
  • Figure 1a is a schematic diagram of an SPN architecture supporting small particle technology provided by an embodiment of the present application.
  • Figure 1b is a schematic diagram of a network architecture provided by an embodiment of the present application.
  • Figure 1c is a schematic diagram of a process for encoding a MAC frame provided by an embodiment of the present application
  • Figure 1d is a schematic diagram of an outer code block and an inner code block provided by an embodiment of the present application
  • Figure 1e is a schematic diagram of an exemplary application scenario provided by the embodiment of the present application.
  • Figure 2 is a schematic flow chart of a fault code block processing method provided by an embodiment of the present application.
  • Figure 3 is a schematic structural diagram of a fault code block processing device provided by an embodiment of the present application.
  • Figure 4 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 5 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Embodiments of the present application provide a method and device for processing faulty code blocks, which can avoid error propagation when errors occur in small-grain services during transmission.
  • FlexE group One or more PHYs included in each FlexE group. When multiple PHYs are included, the multiple PHYs are physically independent. Network equipment that applies FlexE technology can use the PHY number to identify which PHYs are included in a FlexE group to achieve logical bundling of multiple PHYs. For example, each PHY number can be identified by a number between 1 and 254, with 0 and 255 being reserved numbers. A PHY number can correspond to an interface on the network device. Two adjacent network devices need to use the same number to identify the same PHY. The number of each PHY included in a FlexE group does not have to be consecutive.
  • FlexE can be used to carry at least one client, and one client can transmit on at least one PHY.
  • FlexE can support the mapping and transmission of any number of different FlexE Clients on any set of PHYs, thereby realizing functions such as PHY bundling, channelization, and sub-rates.
  • FlexE Client Corresponds to various user interfaces or bandwidth of the network. FlexE Client represents the customer data flow transmitted in the specified time slot (one time slot or multiple time slots) on FlexE Group. One FlexE Group can carry multiple FlexE Clients, and one FlexE Client can correspond to one to multiple user business data flows. (Also known as MAC Client). FlexE client can be flexibly configured according to bandwidth requirements and supports Ethernet media access control (MAC) data flows at various rates (such as 10G, 40G, n*25G data flows, and even non-standard rate data flows), such as The data stream can be passed to the FlexE shim layer through 64B/66B encoding.
  • MAC Ethernet media access control
  • FlexE client also known as the FlexE client interface
  • FlexE client interface is a logical interface.
  • Each FlexE interface can be logically divided into one or more FlexE client interfaces.
  • Each FlexE interface can be divided into multiple time slots in the time domain.
  • Each FlexE client interface occupies at least one of the multiple time slots. time slot.
  • 64/66B refers to the data code block including 66 bits. The first two bits of the 66 bits are synchronization bits, and the last 64 bits are data bits. At the PCS layer, 64/66B can be extracted through the first two synchronization bits. .
  • FlexE shim As an additional logical layer inserted between the MAC and PHY (PCS sublayer) of the traditional Ethernet architecture, it is the core architecture of FlexE technology based on the time slot distribution mechanism.
  • the main function of FlexE shim is Its function is to encapsulate data into pre-divided time slots. Then, according to the FlexE time slot table, each divided time slot is mapped to the PHY in the FlexE group for transmission. Among them, each time slot is mapped to a PHY in the FlexE group.
  • the FlexE Shim layer can divide each 100GE PHY in the FlexE Group into 20 time slots (slots) data carrying channels, and the corresponding bandwidth of each slot is 5Gbps. Every time the PHY sends 1023*20Slot of 64/66B data, an overhead FlexE (Overhead, OH) will be inserted to inform the receiving end how to parse the received data.
  • Small-granularity services In some embodiments, slots corresponding to large bandwidths can be further divided into multiple sub-slots for carrying customer services with smaller bandwidth requirements.
  • the above-mentioned services are also called small-granularity services. Particle business.
  • the above-mentioned large bandwidth can be understood as the bandwidth corresponding to the service layer of small-granularity services.
  • the service layer of the small-granularity service is the MTN channel layer
  • the bandwidth of the MTN channel layer is 5Gbps
  • the slot corresponding to the large bandwidth of 5Gbps is further divided according to the granularity of 10Mbps, and divided into 480 sub-slots. These 480 sub-slots -slot is used to carry small-granule services.
  • the first sub-slot, the third sub-slot, and the fifth sub-slot among the 480 sub-slots are used to carry small-granule services 1.
  • the service layer of small-granularity services is the 10GE Ethernet physical layer
  • the corresponding large bandwidth is further divided into multiple sub-slots according to finer granularity for carrying small-granularity services.
  • the bandwidth granularity of small particles is finer, and small particle services refer to services that have relatively small bandwidth requirements.
  • the bandwidth requirement of the power dedicated line service is 10Mbps.
  • small particle technology can be used to allocate designated bandwidth to the power dedicated line service to carry the business traffic of the power dedicated line service.
  • the above-mentioned power dedicated line service is a small Particle business.
  • FlexE shim When transmitting small-granule services, for the sending end, in one example, FlexE shim can encapsulate the data into pre-divided sub-slots for transmission based on the time slot configuration of the small-granule. For the receiving end, FlexE shim can restore the data received through the slot with a corresponding bandwidth of 5Gbps into the original small-granule service data according to the time slot configuration of the small-granule and continue transmission.
  • the MTN path adaptation function can be used to encapsulate the data into the corresponding sub-slot for transmission. For the receiver, the MTN path adaptation function can be used.
  • the configuration function restores the data received through the slot with a corresponding bandwidth of 5Gbps into the original small-grain service data and continues transmission.
  • fine granularity service data may be carried in fine granularity unit (FGU) base frames.
  • the fine granularity basic unit may also be called a fine granularity basic unit (fgBU). In the following description, the two may be used interchangeably.
  • SPN Slicing Packet Network
  • the SPN architecture includes:
  • SPL Slicing packet layer
  • SCL slicing channel layer
  • STL slicing transport layer
  • SDN integrated management and control software defined network
  • SCL includes FGU layer, MTN path (MTN path, MTNP) layer and MTN section (MTN Section, MTNS) layer.
  • MTN path MTN path
  • MTN section MTN Section, MTNS
  • the FGU layer provides end-to-end deterministic low-latency N*10Mbps granular hard slicing channels for small-granularity services.
  • the FGU layer is an independent sub-layer and can be flexibly carried on the MTN channel layer or the Ethernet physical layer as needed.
  • the service layer of the FGU layer can be the MTN channel layer or the Ethernet physical layer.
  • STL adds a 10GE Ethernet physical layer interface based on the original high-speed Ethernet physical layer interface.
  • the 10GE Ethernet physical layer can be used in customer-premises equipment (CPE) scenarios to directly carry the FGU layer.
  • CPE customer-premises equipment
  • the MTNS and MTNP are introduced from the perspectives of transmitting side behavior and receiving side behavior.
  • MTNS provides point-to-point connections, is responsible for slotting adjacent nodes connected with Ethernet PHY, and provides bonding, sub-rate, channelization Function.
  • MTNS is bidirectionally symmetrical. Here we take one data transmission direction as an example.
  • MTNS inserts a special O code block into the 66B code block sequence.
  • a D code block is inserted after every 1023*20 66B code blocks, and a D code block is inserted after every 1023*20 66B code blocks.
  • a total of 7 D code blocks need to be inserted.
  • a special O code block is inserted. In this way, a total of 8*(1023*20+1) code blocks constitute an MTNS frame.
  • the O code block plus the aforementioned 7 D code blocks constitute the overhead of the MTNS frame.
  • the overhead carries some point-to-point link configuration information indicating MTNS, such as time slot configuration information, segment layer group configuration information, etc.
  • the MTNS continuously sends data to the receiving end according to the above frame structure.
  • the continuous MTNS frame is equivalent to a stream of 66B code blocks, which is converted into bits, optical signals, or other such as electrical pulses according to the lower PHY layer protocol defined by the Institute of Electrical and Electronics Engineers (IEEE) 802.3.
  • the analog signal is sent from the sending side device.
  • the receiving side On the receiving side, first according to the protocol of the Ethernet lower PHY layer, the received signal (such as bits, optical signals, or other analog signals such as electrical pulses) is identified by the O code block, and the MTNS frame is locked. Frame header, according to the fixed count, you can know that the next overhead code block appears after 1023*20 code blocks. Correspondingly, the receiving side can determine the position of the data corresponding to each time slot in the received signal based on the O code block.
  • the received signal such as bits, optical signals, or other analog signals such as electrical pulses
  • MTNS can only provide point-to-point connections, while MTNP is responsible for providing "end-to-end channel connections" from network entrance to network exit.
  • MTNP provides end-to-end rigid hard pipe connections and provides management, maintenance and protection (OAM and protection, OAMP )Function.
  • OAM and protection, OAMP management, maintenance and protection
  • end-to-end MTNP is included between provider edge (PE) 1 and PE2, and point-to-point MTNS is included between PE1 and PE2.
  • the MTNP layer obtains the client signal from the MAC layer, and the client signal can be a MAC frame.
  • the MAC mentioned here may be a processing module of the MAC layer.
  • the MTNP layer After the MTNP layer obtains the MAC frame, it encodes the MAC frame into a sequence of 64/66B code blocks. Specifically, each MAC frame will be encoded into a series of 66B code block sequences defined by a start code block (S code block) and an end code block (i.e. T code block), and a series of MAC frame sequences will be encoded. into a series of 66B code block sequences.
  • S code block start code block
  • T code block end code block
  • MTNP will fill the 66B code block with an I code block, thereby ensuring that MTNP's hard pipeline has data sent at all times.
  • the receiving side of the P node first identifies the MTNS frame according to the above-mentioned receiving side behavior of MTNS. Subsequently, the MTNP data is restored from the designated MTNS time slot according to the pre-configured configuration. The P node next performs MTNP forwarding. It should be noted here that the essential difference between MTNP forwarding, IP forwarding and MAC bridge forwarding is that MTNP forwarding exclusively occupies the device forwarding resources and does not support statistical multiplexing. The entrance and exit of the network node (such as P node) need to be configured the same Number of MTNS slots.
  • the slot corresponding to the large bandwidth can be further divided into multiple sub-slots for carrying small-granularity services.
  • a slot corresponding to a bandwidth of 5Gbps is further divided according to a granularity of 10Mbps and divided into 480 sub-slots. These 480 sub-slots are used to carry small-granularity services.
  • MTN FGU can further divide 480 10Mbps time slots into 5Gbps MTNP in a hierarchical manner.
  • MTNP and MTN FGU can be decoupled.
  • MTNP serves as the service layer of MTN FGU.
  • the fg-BU may include FGU base frame overhead and FGU base frame payload.
  • the FGU base frame overhead may be used to carry time slot information of small particles, and the FGU base frame payload is used to carry the small particle service data.
  • the small-granular time slot information can be the mapping relationship between sub-slot and sub-client.
  • sub-client is similar to FlexE client and also corresponds to various user interfaces or bandwidth of the network. The difference from FlexE client is that sub-client represents the customer data stream transmitted on sub-slot, and one sub-client can correspond to one or more sub-slots.
  • an FGU base frame can include 24 sub-slots, each sub-slot includes 65 bytes, and each sub-slot can carry 8 65-bit code block.
  • 1 S0 code block, 196 D code blocks and 1 T code block can be obtained.
  • the MTN FGU layer is the same as MTNP. It first encodes the MAC frame client signal into a 66B code block sequence, and then inserts the OAM code block. It should be noted at this time that the OAM code blocks of small granular MTNP (fgMTNP) are inserted into the MTN FGU layer, not the OAM code blocks of MTNP. Subsequently, a series of 66B code block sequences containing fgMTNP OAM code blocks are mapped into the 10Mbps time slot specified in the fg-BU according to the pre-configuration.
  • fgMTNP small granular MTNP
  • the fgBU sequence itself is actually a series of 66B code blocks, which can be equivalent to the client signal of MTNP. After inserting the MTNP OAM code block, it is mapped into the time slot designated by MTNS according to the behavior of the MTNS sending side described above.
  • the receiving side of the P node restores the MTNP signal according to the behavior of the receiving side of the MTNP described above, and then extracts the OAM code block in the MTNP. After the receiving side of the P node recovers the MTNP signal, it can complete the framing of the fg-BU by searching for S code blocks.
  • fgMTNP forwarding is the same as MTNP forwarding. It is TDM forwarding. It occupies the device forwarding resources exclusively and does not support statistical multiplexing. The P node will not terminate the OAM code block of fgMTNP.
  • the sending side behavior of P node is the reverse process of the receiving side behavior of P node, which will not be described in detail here.
  • the receiving side behavior of the PE2 node is the reverse process of the sending side behavior of the PE1 node, and will not be explained in detail this time.
  • encoding each MAC frame into a sequence of 64/66B code blocks can include two encodings.
  • the first encoding is to convert the MAC frame into Change to a 66B code block sequence.
  • the second encoding is to fill in the 66B code blocks corresponding to the multi-channel small-grain data into the data payload part of the D code block of fgBU and the data payload part of the T code block of fgBU.
  • Figure 1c is a schematic diagram of a process of encoding a MAC frame provided by an embodiment of the present application.
  • the corresponding 64/66B code block sequence 110 is obtained.
  • the corresponding 64/66B code block sequence 120 can also be obtained.
  • the corresponding 64/66B code block sequence 130 can also be obtained.
  • the multiplexing structure 140 includes a plurality of sub-time slots, and the code block sequence 110, the code block sequence 120, and the code block sequence 130 are filled in the corresponding sub-time slots in the multiplexing structure 140 according to the time slot configuration of small particles.
  • the multiplexing structure 140 is subjected to secondary encoding, and each bit data included in the multiplexing structure is sequentially filled into the 64/66B code block corresponding to the secondary encoding as the asynchronous header bit.
  • the code block stream after secondary encoding is obtained.
  • the "64 bits of the asynchronous header bits in the 64/66B code block corresponding to the secondary encoding" can also be called the "data payload part", and the two can be used interchangeably.
  • the code block stream after secondary encoding includes: I code block, S code block, D code block and T code block.
  • the I code block is used to adapt to the rate difference between different Ethernet interfaces. .
  • the I code block you can refer to the relevant description part of IEEE 802.3, and the description will not be repeated here.
  • code block sequence 110, the code block sequence 120 and the code block sequence 130 after the first encoding may include I code blocks, S code blocks, D code blocks and T code blocks.
  • O code blocks can also be included.
  • the 66B code block obtained after the first encoding can be called the “inner layer code block”
  • the 66B code block obtained after the second encoding can be called the “outer layer code block”.
  • the outer code block may include at least one fgBU.
  • the fgBU mentioned in the embodiment of this application may be the SPN fgBU defined by China Mobile Enterprise Standard, or the MTN fgBU defined by the International Telecommunications Union (International Telecommunication Union, ITU).
  • the data of one inner code block needs to be carried by two outer code blocks.
  • the first 64 bits of data are carried by the 64 bits of the outer code block 1
  • the last 2 bits of the inner code block can be carried by the two bits of the outer code block 2.
  • the other 62 bits in the outer code block 2 that can be used to carry data can be used to carry the 62 bits of data in the inner code block 2 .
  • Figure 1d is a schematic diagram of an outer code block and an inner code block provided by an embodiment of the present application.
  • the first 64 bits of the first inner 66 code block are carried through the 2nd to 63rd bits of the first outer code block, and the last two bits of the first inner 66B code block are carried through The 2nd to 3rd bits of the second outer code block are carried; the first 62 bits of the second inner 66B code block are carried through the 4th to 65th bits of the second outer code block, and the second The last 4 bits of an inner 66B code block are carried by bits 2 to 5 of the third outer code block, and so on.
  • the 64/66B encoding method is used to encode the MAC frame
  • the above is only shown as a possible implementation method.
  • the encoding technology used to encode the MAC frame is not limited to the above-mentioned 64B encoding method. /65B.
  • the 64/65B encoding method can also be used to encode the MAC frame; for example, the 256/257B encoding method can also be used to encode the MAC frame, etc., which will not be listed here.
  • the encoding mode is 64/66B as an example.
  • Figure 1e is a schematic diagram of an exemplary application scenario provided by the embodiment of the present application.
  • PE1 and PE2 also include device P1 and device P2. Although not shown in Figure 1e, other devices may also be included between PE1 and device P1. Correspondingly, other devices may also be included between device P1 and device P2, and between device P2 and device PE2.
  • transmission errors may occur during the transmission of small-grain services.
  • the aforementioned fgBU may have transmission errors, such as D code blocks, I code blocks, O code blocks, and T code blocks in fgBU. All may become E code blocks. If the E code block appears in the outer code block and is not processed, it may cause error propagation and affect the normal transmission of small-granularity services.
  • embodiments of the present application provide a method and device for processing faulty code blocks, which can avoid error propagation.
  • the fault code block processing method shown in Figure 2 can be executed by a first communication device using FlexE fine-grained technology.
  • the first communication device can be a switching node for fine-grained services.
  • the so-called switching node for fine-grained services refers to an intermediate node with the function of parsing small-grained services.
  • the switching node for fine-grained services may be P1 as shown in Figure 1e.
  • the first communication device may also be a sink node for fine-grained services.
  • the so-called sink node of fine-grained services may be a tail node that receives small-grained service packets.
  • the sink node of fine-grained services may be PE2 as shown in Figure 1e.
  • the method 100 may be executed by an inbound interface of the first communication device; in yet another example, the method 100 may be executed by an outbound interface of the first communication device; in another example, the method 100 may be executed by an outbound interface of the first communication device. Some steps of the method 100 may be executed by the incoming interface, and some steps may be executed by the outgoing interface; this is not specifically limited in the embodiments of this application.
  • the communication devices mentioned in the embodiments of this application may be network equipment such as switches and routers, or may be part of the components on the network equipment, such as single boards on the network equipment.
  • the line card may also be a functional module on the network device, or a chip used to implement the method of the present application, which is not specifically limited in the embodiment of the present application.
  • the communication devices may be directly connected through, but not limited to, Ethernet cables or optical cables.
  • the method 100 shown in Figure 1 may include the following S101-S103.
  • outer code blocks and inner code blocks in the method 100 please refer to the description of the outer code blocks and the inner code blocks above, and will not be described in detail here.
  • the first fgBU is composed of a plurality of first outer code blocks.
  • the plurality of first outer code blocks include an outer S code block, a plurality of outer D code blocks, and
  • the first outer layer E code block, the first outer layer E code block is used To carry the data of the first inner code block.
  • the first communication device may first obtain a code block stream including a plurality of outer code blocks, and then analyze the code block stream to obtain the first fgBU.
  • the incoming interface may, for example, receive an upstream node (for example, the PE1 node)
  • the code block stream including a plurality of outer layer code blocks is sent.
  • the "obtaining a code block stream including multiple outer layer code blocks" may be implemented, for example, according to the incoming interface of the first communication device. The data passed by the interface to the outgoing interface is used to obtain the code block stream.
  • the first outer layer E code block in the code block stream can be first identified, and then, the first outer layer E code block can be further determined.
  • the E code block can be matched with the code block stream to determine the first outer E code block in the code block stream. piece.
  • the fgBU to which the first outer E code block belongs For example, you can first identify the FlexE overhead in the code block stream, thereby locating the FlexE frame in the code block stream, and configure the time slot according to the small granularity
  • the MTNP data stream is recovered from each time slot of the FlexE frame, and at least one fgBU is recovered according to the MTNP data stream, and then the fgBU corresponding to the first outer E code block is determined as the first fgBU.
  • At least one fgBU when obtaining the first fgBU according to the code block stream, during specific implementation, for example, at least one fgBU can be obtained first according to the code block stream, and then the at least one fgBU can be analyzed respectively to determine each Whether the E code block is included in the fgBU, thereby obtaining the first fgBU including the aforementioned first outer E code block.
  • the first outer E code block may be the error-prone E code block.
  • An outer layer D code block may also be the first outer layer T code block where an error occurs.
  • the inner layer code blocks may include S code blocks, D code blocks, and T code blocks, and may also include idle I code blocks and/or O code blocks. Therefore, the first inner layer code block may be any one of an S code block, a D code block, a T code block, an idle I code block, and an O code block.
  • the specific implementation of restoring the first inner code block according to the first fgBU is the reverse process of filling the first inner code block into the data payload field of the outer code block.
  • the data payload part in the first fgBU can be extracted, and after splicing the data payload parts, the corresponding inner layer 66B code block can be recovered.
  • the inner layer 66B code block corresponding to the first outer layer E code block can be determined as the first inner layer code block.
  • the first outer layer E code block may be the first outer layer 66B code block shown in Figure 1d
  • the first inner layer code block may be the first inner layer 66B code block
  • the first outer layer code block may be the second outer layer 66B code block shown in Figure 1d
  • the first inner layer code block may be the first inner layer code block shown in Figure 1d 66B code block, or, the second inner 66B code block.
  • the first inner layer code block may be carried through the first sub-slot.
  • the first sub-time slot can be used to carry data corresponding to a certain sub client.
  • the data carried by the first sub-time slot can include multiple inner layer code blocks.
  • the first inner layer code block can be One code block among the plurality of inner layer code blocks.
  • S102 may be executed by the inbound interface of the first communication device or by the outbound interface of the first communication device.
  • the first inner layer code block in order to avoid error propagation due to the first outer layer E code block, after recovering the first inner layer code block, the first inner layer code block can be set to the first inner layer E code piece.
  • S103 may be executed by the inbound interface of the first communication device or by the outbound interface of the first communication device.
  • the incoming interface restores the first communication device.
  • a mark can be added to the first inner layer code block.
  • the outbound interface sets the first inner layer code block as the first inner layer E code block according to the mark.
  • the first inner layer code block may correspond to the first sub-time slot, and the first sub-time slot may correspond to multiple inner layer code blocks.
  • the entire data carried by the first sub-slot also has an error.
  • multiple inner-layer codes corresponding to the first sub-slot can be The blocks are all set to inner E code blocks.
  • the first inner layer code block may be set as the first inner layer E code block, and for the plurality of inner layer code blocks corresponding to the first sub-slot, except for the first Inner code blocks other than one inner code block may not be processed.
  • a partial code block among the plurality of inner layer code blocks corresponding to the first sub-slot may also be set as an inner layer E code block, and the partial code block may include the first inner layer code block. code block.
  • the partial code block may include the first inner layer code block. code block.
  • several inner layer code blocks adjacent to the first inner layer code block may be set as Inner E code block.
  • the first communication device may be a fine-grained service switching node.
  • the first communication device may set the first inner layer code block to the first inner layer E code block.
  • the first inner layer E code block is sent to the second communication device.
  • the first communication device may send a code block stream including the first inner layer E code block to the second communication device, wherein the code block stream including the first inner layer E code block , which can be the code block stream after secondary encoding.
  • the secondary encoding you can refer to the relevant description section above, and will not be described in detail here.
  • the first communication device may be the sink node of the fine-grained service.
  • the first communication device may The first inner layer E code block is sent to the Ethernet frame client signal recovery module of the first communication device.
  • the first communication device may send the multiplexing structure including the first inner E code block to the Ethernet frame client signal recovery module, so that the Ethernet frame client signal recovery module can The received multiplexed structure is used for data recovery, and the data corresponding to each client (sub client) is obtained, that is, the Ethernet frame corresponding to each client is obtained.
  • the Ethernet frame client signal recovery module can discard the first inner layer E code block when recovering the Ethernet frame based on the received multiplexing structure. , instead of processing the first inner layer E code block as a normal code block, therefore, error propagation can be avoided.
  • the process of recovering Ethernet frames according to the multiplexing structure by the Ethernet frame client signal recovery module you can refer to the relevant inner layers of IEEE 802.3, which will not be described in detail here.
  • an outer code block can correspond to one or two inner code blocks. So, in one example, all In addition to carrying the first inner layer code block, the first outer layer E code block can also carry the second inner layer code block. For example, in the scenario shown in Figure 1d, the first outer layer E code block is the second outer layer code block, then the first outer layer E code block can correspond to the first inner layer code block and the second inner layer code block code block. For this situation, in addition to performing the above method 100, the first communication device can also perform the following steps A1-A2.
  • Step A1 Recover the second inner layer code block according to the first fgBU.
  • Step A2 Set the second inner layer code block as a second inner layer E code block.
  • the first communication device is a fine-grained service switching node, after executing A1-A2, in addition to sending the first inner code block to the second communication device,
  • the second inner layer E code block is sent to the second communication device.
  • the first communication device may send a code block stream including the first inner layer E code block and the second inner layer E code block to the second communication device, wherein the code block stream including the first inner layer E code block
  • the code block stream of an inner layer E code block and the second inner layer E code block may be a code block stream after secondary encoding.
  • secondary encoding you can refer to the relevant description section above, and will not be described in detail here.
  • the first communication device is the sink node of the fine-grained service, after executing A1-A2, in addition to sending the first inner layer code block to the first communication device, In addition to the Ethernet frame client signal recovery module, the second inner layer E code block may also be sent to the Ethernet frame client signal recovery module of the first communication device.
  • the first communication device may send a multiplexing structure including the first inner E code block and the second inner E code block to the Ethernet frame client signal recovery module, so that The Ethernet frame client signal recovery module performs data recovery on the received multiplexing structure to obtain data corresponding to each sub client.
  • the plurality of first outer layer code blocks included in the first fgBU may also include a second outer layer E code block.
  • the second outer layer E code blocks The E code block may be the second outer D code block where an error occurred, and the second outer E code block is used to carry the data of the third inner code block.
  • the first communication device may also perform the following steps B1-B2.
  • Step B1 Recover the third inner layer code block according to the first fgBU.
  • Step B2 Set the third inner layer code block as the third inner layer E code block.
  • steps B1-B2 you may refer to the specific implementation part of S102-S103 in the method 100, and the description will not be repeated here.
  • the first communication device is a fine-grained service switching node, after executing B1-B2, in addition to sending the first inner code block to the second communication device,
  • the third inner layer E code block is sent to the second communication device.
  • the first communication device may send a code block stream including the first inner layer E code block and the third inner layer E code block to the second communication device, wherein the code block stream including the third inner layer E code block
  • the code block stream of an inner layer E code block and the third inner layer E code block may be a code block stream after secondary encoding.
  • secondary encoding you can refer to the relevant description section above, and will not be described in detail here.
  • the first inner layer code block may also be sent to the first communication device.
  • Ethernet frame client signal recovery mode In addition to the block, the third inner layer E code block may also be sent to the Ethernet frame client signal recovery module of the first communication device.
  • the first communication device may send a multiplexing structure including the first inner E code block and the third inner E code block to the Ethernet frame client signal recovery module, so that The Ethernet frame client signal recovery module performs data recovery on the received multiplexing structure to obtain data corresponding to each sub client.
  • the first communication device may also perform the following steps C1-C3.
  • Step C1 Obtain a second fgBU, the second fgBU is composed of a plurality of second outer code blocks, the plurality of second outer code blocks include an outer S code block, a plurality of outer D code blocks, and The fourth outer layer E code block is used to carry the data of the fourth inner layer code block.
  • Step C2 Restore the fourth inner layer code block according to the second fgBU.
  • Step C3 Set the fourth inner layer code block as the fourth inner layer E code block.
  • steps C1-C3 please refer to the specific description of the method 100 above, and the description will not be repeated here.
  • the first communication device may also send the fourth inner layer E code block to the second communication device.
  • the first communication device may also send the fourth inner layer E code block to the first Ethernet frame client signal recovery module for communication devices.
  • the embodiment of the present application also provides a fault code block processing device, which can be applied to the first communication device using FlexE fine-grained technology.
  • the fault code block processing device can include a transceiver unit and a processing unit.
  • the transceiver unit is used to perform reception and/or transmission-related operations performed by the first communication device in various possible implementations of the above method embodiment; the processing unit is used to perform various possible implementations of the above method embodiment.
  • operations other than receiving and/or sending related operations are performed by the first communication device.
  • the transceiver unit may include a receiving unit and/or a sending unit, the receiving unit is used to perform reception-related operations, and the sending unit is used to perform sending-related operations.
  • FIG. 3 is a schematic structural diagram of a fault code block processing device provided by an embodiment of the present application.
  • the fault code block processing device 300 may include a receiving unit 301 and a processing unit 302 .
  • the receiving unit 301 is used to obtain the first fine-grained basic unit fgBU.
  • the first fgBU is composed of a plurality of first outer layer code blocks.
  • the plurality of first outer layer code blocks include an outer layer starting S code. block, a plurality of outer layer data D code blocks, and a first outer layer error E code block, the first outer layer E code block is used to carry the data of the first inner layer code block;
  • the processing unit 302 is used to According to the first fgBU, the first inner layer code block is restored, and the first inner layer code block is set as a first inner layer E code block.
  • the first inner layer code block corresponds to the first sub-slot
  • setting the first inner layer code block as the first inner layer E code block includes: setting the first inner layer code block A plurality of inner layer code blocks corresponding to the first sub-slot are set as inner layer E code blocks, and the plurality of inner layer code blocks include the first inner layer code block.
  • the plurality of first outer layer code blocks also include an end T code block, and the first outer layer code blocks
  • the E code block is the first outer D code block where an error occurred.
  • the first outer E code block is a T code block in which an error occurs.
  • the first communication device is a fine-grained service switching node, and the device further includes: a sending unit configured to send the first inner layer E code block to the second communication device.
  • the first communication device is a sink node of fine-grained services
  • the device further includes: a sending unit configured to send the first inner layer E code block to the first Ethernet frame client signal recovery module for communication devices.
  • the first outer layer E code block is also used to carry data of the second inner layer code block
  • the processing unit 302 is also used to: restore the data of the second inner layer code block according to the first fgBU.
  • the second inner layer code block is configured as a second inner layer E code block.
  • the first communication device is a fine-grained service switching node
  • the device includes a sending unit further configured to: send the second inner layer E code block to the second communication device.
  • the first communication device is a sink node of fine-grained services
  • the sending unit included in the device is further configured to: send the second inner layer E code block to the third An Ethernet frame client signal recovery module of a communication device.
  • the plurality of first outer layer code blocks also include a second outer layer E code block, and the second outer layer E code block is a second outer layer D code block where an error occurred,
  • the second outer layer E code block is used to carry the data of the third inner layer code block;
  • the processing unit is also used to: restore the third inner layer code block according to the first fgBU, and convert the The third inner layer code block is set as the third inner layer E code block.
  • the receiving unit 301 is further configured to: obtain a second fgBU, the second fgBU is composed of a plurality of second outer code blocks, and the plurality of second outer code blocks It includes an outer S code block, a plurality of outer D code blocks, and a fourth outer E code block.
  • the fourth outer E code block is used to carry the data of the fourth inner code block; the processing unit, It is also configured to restore the fourth inner layer code block according to the second fgBU, and set the fourth inner layer code block as a fourth inner layer E code block.
  • the first inner layer code block includes any one of the following types of code blocks: S code block, D code block, T code block, idle I code block, or O code block.
  • the first communication device is a fine-grained service switching node
  • setting the first inner layer code block as a first inner layer E code block includes: the first communication device The outbound interface of the device sets the first inner layer code block as the first inner layer E code block.
  • the device 300 is a device corresponding to the method performed by the first communication device provided by the above method embodiments, the specific implementation of each unit of the device 300 is the same concept as the above method embodiments. Therefore, regarding the above For the specific implementation of each unit of the device 300, reference may be made to the description of the above method embodiments, which will not be described again here.
  • this embodiment of the present application also provides a communication device 400, as shown in Figure 4.
  • Figure 4 is a schematic structural diagram of a communication device provided by this embodiment of the present application.
  • the communication device 400 includes a communication interface 401 and a processor 402 connected to the communication interface 401 .
  • the communication device 400 can be used to perform the method 10 in the above embodiment.
  • the communication device 400 can perform the method 100 in the above embodiment.
  • the communication device 400 is equivalent to the first communication device in the method 100.
  • the communication interface 401 is used to perform the sending and receiving operations performed by the first communication device in the method 100.
  • Processor 402 is used for executing In the method 100, the first communication device performs operations other than the sending and receiving operations.
  • the communication interface 401 is used to obtain the first fgBU.
  • the first fgBU is composed of a plurality of first outer layer code blocks.
  • the plurality of first outer layer code blocks include an outer layer S code block, a plurality of outer layer code blocks, and a plurality of outer layer code blocks.
  • the D code block, and the first outer layer E code block, the first outer layer E code block is used to carry the data of the first inner layer code block; the processor 402 is used to restore the first fgBU according to the first fgBU.
  • An inner layer code block, the first inner layer code block is set as the first inner layer E code block.
  • FIG. 5 is a schematic structural diagram of a communication device provided by the embodiment of the present application.
  • the communication device 500 can be used to perform the method 100 in the above embodiment.
  • the communication device 500 may include a processor 510 , a memory 520 coupled to the processor 510 , and a transceiver 530 .
  • the transceiver 530 may be, for example, a communication interface, an optical module, etc.
  • the processor 510 may be a central processing unit (CPU), a network processor (NP), or a combination of CPU and NP.
  • the processor can also be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above-mentioned PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL) or any combination thereof.
  • the processor 510 may refer to one processor or may include multiple processors.
  • the memory 520 may include volatile memory (English: volatile memory), such as random access memory (English: random-access memory, abbreviation: RAM); the memory may also include non-volatile memory (English: non-volatile memory) , such as read-only memory (ROM), flash memory (English: flash memory), hard disk (HDD) or solid-state drive (SSD); the memory 520 may also include the above A combination of types of memory.
  • the memory 520 may refer to one memory or may include multiple memories.
  • computer readable instructions are stored in the memory 520 , and the computer readable instructions include a plurality of software modules, such as a sending module 521 , a processing module 522 and a receiving module 523 .
  • the processor 510 can perform corresponding operations according to the instructions of each software module.
  • the operations performed by a software module actually refer to operations performed by the processor 510 according to the instructions of the software module.
  • the communication device 500 can perform the method 100 in the above embodiment.
  • the communication device 500 is equivalent to the first communication device in the method 100.
  • the transceiver 530 is used to perform the transceiver operation performed by the first communication device in the method 100.
  • the processor 510 is configured to perform operations other than the sending and receiving operations performed by the first communication device in the method 100 .
  • the transceiver 530 is used to obtain the first fgBU.
  • the first fgBU is composed of a plurality of first outer layer code blocks.
  • the plurality of first outer layer code blocks include an outer layer S code block, a plurality of outer layer code blocks, and a plurality of outer layer code blocks.
  • the D code block, and the first outer layer E code block, the first outer layer E code block is used to carry the data of the first inner layer code block; the processor 510 is used to restore the first fgBU according to the first fgBU.
  • An inner layer code block, the first inner layer code block is set as the first inner layer E code block.
  • the present application also provides a computer-readable storage medium that stores instructions that, when run on a computer, cause the computer to execute the method described in the foregoing embodiments (for example, method 100 ) any one or more operations.
  • This application also provides a computer program product, which includes a computer program that, when run on a computer, causes the computer to perform any one or more operations in the method (eg, method 100) described in the previous embodiments.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of units is only a logical service division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • a unit described as a separate component may or may not be physically separate.
  • a component shown as a unit may or may not be a physical unit, that is, it may be located in one place, or it may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each business unit in various embodiments of this 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 integrated units can be implemented in the form of hardware or software business units.
  • Integrated units may be stored in a computer-readable storage medium when implemented in the form of software business units and sold or used as independent products.
  • the technical solution of the present application is essentially or contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program code. .
  • Computer-readable media includes computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • Storage media can be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

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

Abstract

本申请实施例公开了一种故障码块处理方法，应用于使用FlexE细粒度技术的第一通信装置。第一通信装置可以获取第一fgBU，第一fgBU由多个第一外层码块组成，多个第一外层码块包括外层S码块、多个外层D码块以及第一外层E码块。第一外层E码块用于承载第一内层码块的数据。获得第一fgBU之后，可以根据第一fgBU，恢复第一内层码块，并将第一内层码块设置为第一内层E码块。考虑到若不对第一内层码块进行处理，则可能会导致误码扩散。因此，在本申请实施例中，第一通信装置获得第一fgBU之后，可以将第一外层E码块对应的第一内层码块设置成第一内层E码块，从而避免由于第一内层码块误码而导致误码扩散。

Description

一种故障码块处理方法及装置
本申请要求于2022年8月8日提交中国国家知识产权局、申请号为202210945854.1、申请名称为“一种故障码块处理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种故障码块处理方法及装置。
背景技术
灵活以太网(Flexible Ethernet，FlexE)技术具备带宽按需灵活分配的优点，其可以满足移动承载、家庭宽带、专线接入等网络场景需求。因此，FlexE技术的应用越来越广泛。
FlexE技术可以支持细粒度业务。在一个示例中，可以将FlexE大带宽对应的时隙(slot)进一步划分成多个子slot(sub-slot)，用于承载细粒度业务。其中：所述FlexE大带宽对应的时隙所承载的业务也可以被称为大颗粒业务，细粒度业务也可以被称为小颗粒业务。在以下描述中，“小颗粒”和“细粒度”可以交替使用。
目前，小颗粒业务在传输的过程中，可能会出现传输错误，对于这种情况，如何对出现传输错误的小颗粒业务进行处理，是目前尚待解决的问题。
发明内容
本申请实施例提供了一种故障码块处理方法及装置，可以在小颗粒业务在传输过程中出现错误时、避免误码扩散。在一个示例中，误码扩散可以理解成所识别的错误码块的数量大于实际的错误码块数量，例如，实际上有3个码块误码，但是在码块分析时，将所有码块均识别成错误码块。在又一个示例中，误码扩散可以理解成基于错误码块恢复以太网帧时，逃逸以太网帧的循环冗余校验(cyclic redundancy check，CRC)，例如CRC32，使得错误码块扩散至业务层甚至应用层。
第一方面，本申请实施例提供了一种故障码块处理方法，该方法可以应用于使用FlexE细粒度技术的第一通信装置。在一个示、、例中，所述第一通信装置可以获取第一细粒度基本单元(finer granularity basic unit，fgBU)，所述第一fgBU由多个第一外层码块组成，所述多个第一外层码块包括外层起始(start，S)码块、多个外层数据(data，D)码块以及第一外层错误(error，E)码块。其中，所述第一外层E码块用于承载第一内层码块的数据。获得所述第一fgBU之后，可以根据所述第一fgBU，恢复所述第一内层码块，并将所述第一内层码块设置为第一内层E码块。在本申请实施例中，考虑到若不对所述第一内层码块进行处理，则可能会导致误码扩散，例如，纠错算法无法进行纠错时，可能会将整个第一fgBU均识别为E码块。因此，在本申请实施例中，第一通信装置获得第一fgBU之后，可以将第一外层E码块对应的第一内层码块设置成第一内层E码块，从而避免由于第一内层码块误码而导致误码扩散。
在一种可能的实现方式中，内层码块可以包括S码块、D码块、T码块，另外还可以包括空闲(idle，I))码块和/或O码块。因此，所述第一内层码块，可以是S码块、D码块、T码块、空闲I码块以及O码块中的任意一种。
在一种可能的实现方式中，所述第一通信装置为细粒度业务交换节点，则在一个示例中，可以由第一通信装置的出接口将所述第一内层码块设置为第一内层E码块。
在一种可能的实现方式中，第一内层码块可以对应第一子时隙，所述第一子时隙可以对应多个内层码块，对于这种情况，考虑到第一内层码块出现错误，则该第一子时隙所承载的数据整体也发生了错误，对于这种情况，在一个示例中，“将第一内层码块设置为第一内层E码块”在具体实现时，可以将所述第一子时隙对应的多个内层码块均设置为内层E码块。例如，可以将所述第一内层码块以及所述第一子时隙对应的多个内层码块中、与所述第一内层码块相邻的若干个内层码块设置为内层E码块，又如，可以将所述第一子时隙对应的所有码块均设置为E码块。采用这种方式，可以避免由于第一内层码块误码而导致误码扩散。
在一种可能的实现方式中，考虑到在码块流的传输过程中，其包括的D码块、T码块均可能会发生错误变成E码块，因此，所述第一外层E码块，可以是发生错误的第一外层D码块，也可以是发生错误的第一外层T码块。
在一种可能的实现方式中，第一通信装置可以是细粒度业务交换节点，对于这种情况，在一个示例中，第一通信装置将所述第一内层码块设置为第一内层E码块之后，可以将所述第一内层E码块发送给第二通信装置。在一个示例中，第一通信装置可以将包括所述第一内层E码块的码块流发送给所述第二通信装置，其中，所述包括第一内层E码块的码块流，可以是经过二次编码之后的码块流。对于这种情况，第一通信装置可以将第一内层E码块发送给第二通信装置，而不是将发生错误的第一内层码块发送给第二通信装置，相应的，在一个示例中，若第二通信装置为细粒度业务的宿节点，则第二通信装置接收到第一内层E码块之后，第二通信装置例如可以丢弃所述第一内层E码块，从而避免第二通信装置基于发生错误的第一内层码块恢复以太网帧，从而达到避免误码扩散的效果。
在一种可能的实现方式总，第一通信装置可以是细粒度业务的宿节点，对于这种情况，在一个示例中，第一通信装置将所述第一内层码块设置为第一内层E码块之后，可以将所述第一内层E码块发送给所述第一通信装置的以太帧客户信号恢复模块，以便于所述以太帧客户信号恢复模块进行数据恢复，得到各个客户对应的以太网帧。由于第一内层码块被设置为第一内层E码块，因此，以太帧客户信号恢复模块在恢复以太网帧时，可以将第一内层E码块丢弃，而不是将所述第一内层E码块当成正常的码块进行处理，因此，可以避免误码扩散。
在一种可能的实现方式中，所述第一外层E码块除了可以承载第一内层码块之外，还可以承载第二内层码块。对于这种情况，第一通信装置还可以根据所述第一fgBU，恢复所述第二内层码块，并将所述第二内层码块设置为第二内层E码块，从而避免由于第二内层码块误码而导致误码扩散。
在一种可能的实现方式中，所述第一通信装置为细粒度业务交换节点，对于这种情况，第一通信装置将所述第二内层码块设置为第二内层E码块之后，还可以向第二通信装发送所述第二内层E码块。例如，所述第一通信装置可以向第二通信装置发送所述第一内层E码块和所述第二内层E码块。在一个示例中，若第二通信装置为细粒度业务的宿节点，则第二通信装置接收到第一内层E码块和第二内层E码块之后，第二通信装置例如可以丢弃所述第一内层E码块和第二内层E码块，从而避免第二通信装置基于发生错误的第一内层码块和发生错误的第二内层码块恢复以太网帧，从而达到避免误码扩散的效果。
在一种可能的实现方式中，所述第一通信装置为细粒度业务的宿节点，对于这种情况，第一通信装置将所述第二内层码块设置为第二内层E码块之后，还可以将所述第二内层E码块发送给所述第一通信装置的以太网帧客户信号恢复模块。例如，所述第一通信装置可以将所述第一内层E码块和所述第二内层E码块发送给所述以太网帧客户信号恢复模块。，以太帧客户信号恢复模块在恢复以太网帧时，可以将第一内层E码块和第二内层E码块丢弃，而不是将所述第一内层E码块和第二内层E码块当成正常的码块进行处理，因此，可以避免误码扩散。
在一种可能的实现方式中，所述多个第一外层码块还包括第二外层E码块，所述第二外层E码块为发生错误的第二外层D码块,所述第二外层E码块用于承载第三内层码块的数据；所述方法还包括：根据所述第一fgBU，恢复所述第三内层码块，将所述第三内层码块设置为第三内层E码块。
在一种可能的实现方式中，所述方法还包括：获取第二fgBU，所述第二fgBU由多个第二外层码块组成，所述多个第二外层码块包括外层S码块，多个外层D码块，以及第四外层E码块，所述第四外层E码块用于承载第四内层码块的数据；根据所述第二fgBU，恢复所述第四内层码块，将所述第四内层码块设置为第四内层E码块。
第二方面，本申请实施例提供了一种故障码块处理装置，应用于使用灵活以太网FlexE细粒度技术的第一通信装置，所述故障码块处理装置包括收发单元和处理单元。所述收发单元用于执行上述第一方面以及第一方面各种可能的实现方式中由所述第一通信装置所执行的接收和/或发送相关的操作；所述处理单元用于执行上述第一方面以及第一方面各种可能的实现方式中由所述第一通信装置所执行接收和/或发送相关的操作之外的操作。在具体实现中，所述收发单元可以包括接收单元和/或发送单元，接收单元用于执行接收相关的操作，发送单元用于执行发送相关的操作。
在一个具体的示例中，所述第一通信装置可以包括接收单元和处理单元。接收单元，用于获取第一细粒度基本单元fgBU，所述第一fgBU由多个第一外层码块组成，所述多个第一外层码块包括外层起始S码块、多个外层数据D码块、以及第一外层错误E码块，所述第一外层E码块用于承载第一内层码块的数据；处理单元，用于根据所述第一fgBU，恢复所述第一内层码块，将所述第一内层码块设置为第一内层E码块。
在一种可能的实现方式中，所述第一内层码块对应第一子时隙，所述将所述第一内层码块设置为第一内层E码块，包括：将所述第一子时隙所对应的多个内层码块设置为内层E码块，所述多个内层码块包括所述第一内层码块。
在一种可能的实现方式中，所述多个第一外层码块还包括结束T码块，所述第一外层E码块为发生错误的第一外层D码块。
在一种可能的实现方式中，所述第一外层E码块为发生错误的T码块。
在一种可能的实现方式中，所述第一通信装置为细粒度业务交换节点，所述装置还包括：发送单元，用于向第二通信装发送所述第一内层E码块。
在一种可能的实现方式中，所述第一通信装置为细粒度业务的宿节点，所述装置还包括：发送单元，用于将所述第一内层E码块发送给所述第一通信装置的以太网帧客户信号恢复模块。
在一种可能的实现方式中，所述第一外层E码块还用于承载第二内层码块的数据，所述处理单元，还用于：根据所述第一fgBU，恢复所述第二内层码块，并将所述第二内层码块设置为第二内层E码块。
在一种可能的实现方式中，所述第一通信装置为细粒度业务交换节点，所述装置包括的发送单元，还用于：向第二通信装发送所述第二内层E码块。
在一种可能的实现方式中，所述第一通信装置为细粒度业务的宿节点，所述装置包括的发送单元，还用于：将所述第二内层E码块发送给所述第一通信装置的以太网帧客户信号恢复模块。
在一种可能的实现方式中，所述多个第一外层码块还包括第二外层E码块，所述第二外层E码块为发生错误的第二外层D码块,所述第二外层E码块用于承载第三内层码块的数据；所述处理单元，还用于：根据所述第一fgBU，恢复所述第三内层码块，将所述第三内层码块设置为第三内层E码块。
在一种可能的实现方式中，所述接收单元，还用于：获取第二fgBU，所述第二fgBU由多个第二外层码块组成，所述多个第二外层码块包括外层S码块，多个外层D码块，以及第四外层E码块，所述第四外层E码块用于承载第四内层码块的数据；所述处理单元，还用于根据所述第二fgBU，恢复所述第四内层码块，将所述第四内层码块设置为第四内层E码块。
在一种可能的实现方式中，所述第一内层码块包括以下任意一种类型的码块：S码块、D码块、T码块、空闲I码块、或O码块。
在一种可能的实现方式中，所述第一通信装置为细粒度业务交换节点，所述将所述第一内层码块设置为第一内层E码块，包括：所述第一通信装置的出接口将所述第一内层码块设置为第一内层E码块。
第三方面，本申请提供了一种故障码块处理装置，所述故障码块处理装置包括存储器和处理器；所述存储器，用于存储程序代码；所述处理器，用于运行所述程序代码中的指令，使得所述通信装置执行以上第一方面以及第一方面任意一项所述的方法。
第四方面，本申请提供了一种故障码块处理装置，所述故障码块处理装置包括通信接口和处理器。一种具体的实现方式中，所述通信接口用于执行以上第一方面以及第一方面任意一项所述的第一通信装置执行的收发操作，所述处理器用于执行以上第一方面以及第一方面任意一项所述的第一通信装置执行的除收发操作之外的其它操作。
第五方面，本申请实施例提供了一种计算机可读存储介质，包括指令或计算机程序，当其在处理器上运行时，执行以上第一方面任意一项所述的方法。
第六方面，本申请实施例提供了一种计算机程序产品，包括计算机程序产品，当其在处理器上运行时，执行以上第一方面以及第一方面任意一项所述的方法。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1a为本申请实施例提供的一种支持小颗粒技术的SPN架构的示意图；
图1b为本申请实施例提供的一种网络架构示意图；
图1c为本申请实施例提供的一种对MAC frame进行编码的过程示意图；
图1d为本申请实施例提供的一种外层码块和内层码块的示意图；
图1e为本申请实施例提供的一种示例性应用场景示意图；
图2为本申请实施例提供的一种故障码块处理方法的流程示意图；
图3为本申请实施例提供的一种故障码块处理装置的结构示意图；
图4为本申请实施例提供的一种通信装置的结构示意图；
图5为本申请实施例提供的一种通信装置的结构示意图。
具体实施方式
本申请实施例提供了一种故障码块处理方法及装置，可以在小颗粒业务在传输过程中出现错误时、避免误码扩散。
为方便理解，首先对FlexE的相关内容进行介绍。
FlexE group：每个FlexE group包括的一个或多个PHY。当包括多个PHY时，所述多个PHY在物理上是独立的。应用了FlexE技术的网络设备可以通过PHY的编号来标识一个FlexE group中包含哪些PHY，来实现多个PHY的逻辑捆绑。例如，每个PHY的编号可用1～254之间的一个数字来标识，0和255为保留数字。一个PHY的编号可对应网络设备上的一个接口。相邻的两个网络设备之间需采用相同的编号来标识同一个PHY。一个FlexE group中包括的每个PHY的编号不必是连续的。通常情况下，两个网络设备之间具有一个FlexE group，但本申请并不限定两个网络设备之间仅存在一个FlexE group，即两个网络设备之间也可以具有多个FlexE group。一个PHY可用于承载至少一个client，一个client可在至少一个PHY上传输。FlexE可以支持任意多个不同FlexE Client在任意一组PHY上的映射和传输，从而实现PHY捆绑、通道化及子速率等功能。
FlexE Client:对应于网络的各种用户接口或带宽。FlexE Client代表在FlexE Group上指定时隙(一个时隙或多个时隙)传输的客户数据流，一个FlexE Group上可承载多个FlexE Client，一个FlexE Client可对应一个到多个用户业务数据流(也可以称为MAC Client)。FlexE client可根据带宽需求灵活配置，支持各种速率的以太网媒体接入控制(media access control，MAC)数据流(如10G、40G、n*25G数据流，甚至非标准速率数据流)，例如可以通过64B/66B的编码的方式将数据流传递至FlexE shim层。通过同一FlexE group发送的客户需要共用同一时钟，且这些客户需要按照分配的时隙速率进行适配。本申请中，可以通过FlexE client(也可以被称为FlexE client接口)，用于传输相应的FlexE client的业务数据流。FlexE client接口是一个逻辑接口。每个FlexE接口在逻辑上可以划分为一个或多个FlexE client接口，每个FlexE接口在时域上可以划分为多个时隙，每个FlexE client接口占用所述多个时隙中的至少一个时隙。其中：64/66B指的是数据码块包括66比特，该66比特的前两个比特为同步比特，后64比特为数据比特，在PCS层，可以通过前两个同步比特来提取64/66B。
FlexE shim:作为插入传统以太架构的MAC与PHY(PCS子层)中间的一个额外逻辑层，是基于时隙分发机制实现FlexE技术的核心架构。对于发送端而言，FlexE shim的主要 作用是将数据封装至预先划分的时隙(slot)中。然后，根据FlexE时隙表，将划分好的各时隙映射至FlexE group中的PHY上进行传输。其中，每个时隙映射于FlexE group中的一个PHY。以100GE PHY为例，FlexE Shim层可以把FlexE Group中的每个100GE PHY划分为20个时隙(slot)的数据承载通道，每个slot对应的带宽为5Gbps。PHY每发送1023*20Slot的64/66B数据就会插入一个开销FlexE(Overhead，OH)，从而告知接收端如何对接收到的数据进行解析。
小颗粒业务：在一些实施例中，大带宽对应的slot还可以进一步划分成多个子时隙(sub-slots)，用于承载对带宽需求较小的客户业务，上述业务也被称之为小颗粒业务。举例来说，上述大带宽可以理解为小颗粒业务的服务层所对应的带宽。例如，当小颗粒业务的服务层是MTN通道层时，MTN通道层的带宽为5Gbps,将对应大带宽为5Gbps的slot按照10Mbps粒度进行进一步划分，划分成480个sub-slots，这480个sub-slot用于承载小颗粒业务。例如，这480个sub-slot中的第1个sub-slot、第3个sub-slot和第5个sub-slot用于承载小颗粒业务1。再比如，小颗粒业务的服务层为10GE以太网物理层时，将对应的大带宽按照更细的粒度进一步划分为多个sub-slots，用于承载小颗粒业务。由此可见，小颗粒的带宽粒度更细，小颗粒业务是指对带宽相对需求较小的业务。举例来说，电力专线业务的带宽需求为10Mbps，此时，即可利用小颗粒技术为该电力专线业务分配指定的带宽，用于承载电力专线业务的业务流量，上述电力专线业务为一种小颗粒业务。
其中，传输小颗粒业务时，对于发送端而言，在一个示例中，FlexE shim可以根据小颗粒的时隙配置将数据封装至预先划分的sub-slot中传输。对于接收端而言，FlexE shim可以根据小颗粒的时隙配置将通过该对应带宽为5Gbps的slot接收的数据恢复成原始小颗粒业务数据并继续传输。在又一个示例中，对于发送端而言，可以利用MTN通道层适配功能(MTN path adaptation function)将数据封装至对应的sub-slot中传输，对于接收端而言，可以利用MTN通道层适配功能将通过该对应带宽为5Gbps的slot接收的数据恢复成原始小颗粒业务数据并继续传输。在一个示例中，小颗粒业务数据可以携带在小颗粒单元(fine granularity unit，FGU)基帧中。在一个示例中，小颗粒单元，也可以被称为小颗粒基本单元(fine granularity basic unit，fgBU)，在以下描述中，二者可以交替使用。
关于FlexE OH插入方式以及开销帧的结构，一种具体的实现方式中，可以参考电气与光互联网论坛(optical internetworking forum，OIF)关于FlexE的相关描述部分，此处不做详述。
接下来介绍一种可能的支持小颗粒技术的切片分组网(Slicing Packet Network，SPN)架构。参见图1a，该图为本申请实施例提供的一种支持小颗粒技术的SPN架构的示意图。
如图1a所示，所述SPN架构包括：
切片分组层(slicing packet layer，SPL)、切片通道层(slicing channel layer，SCL)、切片传送层(slicing transport layer，STL)、管控一体的软件定义网络(software defined network，SDN)切片控制平面以及超高精度事件频率同步技术。其中：
SCL包括FGU层、MTN通道(MTN path，MTNP)层和MTN段(MTN Section，MTNS)层。其中：FGU层，为小颗粒业务提供端到端的确定性低时延N*10Mbps粒度硬切片通道。FGU层是独立子层，可按需灵活选择承载于MTN通道层或者以太网物理层， 换言之，FGU层的服务层可以是MTN通道层，也可以是以太网物理层。
STL在原有高速以太网物理层接口的基础上，新增了10GE以太网物理层接口。10GE以太网物理层可以应用于客户终端设备(customer-premises equipment，CPE)场景中，直接承载FGU层。
接下来，以MTN通道层承载小颗粒业务为例，从发送侧行为和接收侧行为的角度，对所述MTNS和MTNP进行介绍。
首先对MTNS的发送侧行为和接收侧行为进行介绍。
在一个示例中，以100GBASE-R PHY为例，MTNS提供点到点的连接，负责将用以太网PHY连接起来的相邻节点进行时隙化处理，并提供绑定、子速率、通道化的功能。MTNS是双向对称的，此处以一个数据传输方向为例进行说明。
发送侧，MTNS在66B码块序列中插入一种特殊的O码块，间隔1023*20个66B码块之后插入一个D码块，每隔1023*20个66B码块之后均插入一个D码块，一共需要插入7个D码块。在插入第7个D码块之后，再间隔1023*20个码块后，插入一个特殊的O码块。如此，总共8*(1023*20+1)个码块构成了一个MTNS帧(frame)。
O码块加上前述7个D码块构成了MTNS帧的开销。开销上携带了指示MTNS的一些点到点链路配置信息，例如，时隙配置信息、段层组配置信息等等。
MTNS一直连续不断地按照上述帧结构向接收端发送数据。持续不断的MTNS帧等同于66B码块流，按照以太网电气与电子工程师协会(Institute of Electrical and Electronics Engineers，IEEE)802.3所定义的lower PHY layer协议转变为比特、光信号、或者其它例如电脉冲的模拟信号，从发送侧设备处发送出去。
接收侧，首先按照以太网底层PHY(Ethernet lower PHY layer)的协议，将接收到的信号(例如比特、光信号、或者其它例如电脉冲的模拟信号)通过识别O码块，锁定了MTNS帧的帧头，依照固定计数就可以知道下一个开销码块出现在1023*20个码块之后。相应的，接受侧根据O码块，就可以确定各个时隙对应的数据在接收到的信号中的位置。
MTNS只能提供点到点的连接，而MTNP负责提供从网络入口到网络出口的“端到端通道连接”，MTNP提供端到端的刚性硬管道连接，提供管理维护和保护(OAM and protection，OAMP)功能。一种关于MTNP的典型组网可以参考图1b所示，图1b为本申请实施例提供的一种网络架构示意图。
接下来结合图1b介绍MTNP的发送侧行为和接收侧行为。
如图1b所示，提供者边缘(provider edge，PE)1和PE2之间包括端到端的MTNP，PE1和PE2之间包括点到点的MTNS。
在PE1的网络侧接口(network to network interface，NNI)侧，MTNP层从MAC层中获取客户信号，该客户信号可以是MAC frame。此处提及的MAC可以是MAC层的处理模块。MTNP层获得MAC frame之后，将MAC frame编码成一串64/66B码块序列。具体的，每个MAC frame会被编码成由起始码块(S码块)和结束码块(即T码块)所界定的一串66B码块序列，一连串的MAC frame序列就会被编码成一连串的66B码块序列。
在一个示例中，如果没有有效的MAC frame等待发送，那么MTNP会用I码块填充所述66B码块，从而保证MTNP的硬管道时时刻刻都有数据发送。
P节点的接收侧，首先按照上述所述的MTNS的接收侧行为，识别出MTNS帧。随后，根据预先的配置，从指定MTNS时隙中将MTNP数据恢复。P节点接下来执行MTNP转发。此处需要说明的是，MTNP转发与IP转发以及MAC bridge转发的本质区别在于：MTNP转发独占设备转发资源，不支持统计复用，网络节点(例如P节点)的入口和出口的都需要配置一样数量的MTNS时隙。
如上所述，在一些实施例中，大带宽对应的slot还可以进一步划分成多个sub-slot，用于承载小颗粒业务。例如，将对应带宽为5Gbps的slot按照10Mbps粒度进行进一步划分，划分成480个sub-slot，这480个sub-slot用于承载小颗粒业务。对于这种情况，MTN FGU通过层次化的方式在5Gbps的MTNP中，可以进一步划分出480个10Mbps的时隙。在这种场景下，MTNP和MTN FGU是可以解耦的，此时，MTNP作为MTN FGU的服务层。在一个示例中，所述fg-BU可以包括FGU基帧开销和FGU基帧净荷。其中，所述FGU基帧开销可以用于承载小颗粒的时隙信息，所述FGU基帧净荷用于承载所述小颗粒业务数据。其中，小颗粒的时隙信息，可以是sub-slot与sub-client之间的映射关系。其中，sub-client与FlexE client类似，也对应于网络的各种用户接口或带宽。与FlexE client的区别在于：sub-client代表在sub-slot上传输的客户数据流，一个sub-client可对应一个或者多个sub-slot。
对于将对应带宽为5Gbps的slot按照10Mbps粒度进行进一步划分的场景，在一个示例中，一个FGU基帧可以包括24个子时隙，每个子时隙包括65字节，每个子时隙可以承载8个65比特的码块。换言之，前述基帧净荷120可以包括65*24＝1560字节。20个FGU基帧组成一个复帧，复帧内提供24×20＝480个子时隙。在一个示例中，图1d所示的fg-BU经64/66B编码之后，可以得到1个S0码块、196个D码块和1个T码块。
对于PE1的NNI发送侧，MTN FGU层与MTNP一样，先将MAC frame客户信号编码为66B码块序列，然后插入OAM码块。此时需要说明的是，MTN FGU层中插入的是小颗粒MTNP(fgMTNP)的OAM码块，而不是MTNP的OAM码块。随后，一连串包含了fgMTNP OAM码块的66B码块序列映射进入fg-BU中根据预先配置指定的10Mbps时隙中。
fgBU序列本身实际是一串66B码块，可以等效为MTNP的客户信号，在插入MTNP OAM码块后，按照上述描述的MTNS发送侧的行为，映射进入MTNS指定的时隙中。
P节点的接收侧，按照上述所述的MTNP的接收侧的行为，将MTNP信号恢复，随后将MTNP中的OAM码块提取出来。P节点的接收侧恢复MTNP信号之后，可以通过搜索S码块的方式，完成fg-BU的定帧。
P节点执行fgMTNP转发，fgMTNP转发与MTNP转发一样，都是TDM转发，独占设备转发资源，不支持统计复用。P节点不会终结fgMTNP的OAM码块。
P节点的发送侧行为是P节点接收侧行为的逆过程，此处不再详细说明。另外，PE2节点的接收侧行为是PE1节点发送侧行为的逆过程，此次不做详细说明。
根据以上对MTNS和MTNP的发送侧行为以及接收侧行为可知：
为了使得小颗粒信号能够以“0感知”的方式通过部署大颗粒技术的设备，每个MAC frame编码成一串64/66B码块序列可以包括两次编码。第一次编码是将所述MAC frame转 换成66B码块序列，具体转换方式可以参考IEEE802.3中的条款(clause)81以及clause82，此处不做重复描述。第二次编码则是将多路小颗粒数据对应的66B码块，依次填入fgBU的D码块的数据净荷部分以及fgBU的T码块的数据净荷部分。
可参考图1c进行理解，如图1c所示，图1c为本申请实施例提供的一种对MAC frame进行编码的过程示意图。
如图1c所示，sub client A对应的以太网帧经过第一次编码之后，得到对应的64/66B码块序列110，类似的，sub client B对应的以太网帧经过第一次编码之后，也可以得到对应的64/66B码块序列120，sub client C对应的以太网帧经过第一次编码之后，也可以得到对应的64/66B码块序列130。
而后，根据小颗粒的时隙配置以及所述码块序列110、码块序列120以及码块序列130，得到包括所述码块序列110、码块序列120、码块序列130以及复用结构开销的复用结构140。所述复用结构包括多个子时隙，码块序列110、码块序列120以及码块序列130根据小颗粒的时隙配置，填入所述复用结构140中对应的子时隙中。
进一步地，对所述复用结构140进行二次编码，将所述复用结构所包括的各个比特数据，依次填入二次编码所对应的64/66B码块中、作为非同步头比特的64比特中，得到二次编码后的码块流。其中，所述“二次编码所对应的64/66B码块中、非同步头比特的64比特”也可以被称为“数据净荷部分”，二者可以交替使用。
如图1c所示，二次编码后的码块流包括：I码块、S码块、D码块和T码块，其中，I码块用于适配不同以太网接口之间的速率差异。关于I码块，可以参考IEEE 802.3的相关描述部分，此处不再重复描述。
另外，虽然图1c未示出，但是经过第一次编码后的码块序列110、码块序列120以及码块序列130，除了可以包括I码块、S码块、D码块和T码块之外，还可以包括O码块。
为方便描述，在以下描述中，可以将第一次编码后得到的66B码块称为“内层码块”，将第二次编码后得到的66B码块称为“外层码块”。
在一个示例中，所述外层码块，可以是包括至少一个fgBU。本申请实施例中提及的fgBU，可以是中国移动企业标准所定义的SPN fgBU，也可以是国际电信联盟(international telecommunication union，ITU)定义的MTN fgBU。
由于内层码块的66比特数据要填充在外层码块的64比特中，因此，一个内层码块的数据，需要通过两个外层码块来承载。例如，对于内层码块1而言，其前64比特数据通过外层码块1的64比特来承载，内层码块的后2个比特数据可以通过外层码块2中的两个比特来承载。另外，外层码块2中其它能够用于承载数据的62比特，可以用于承载内层码块2的62比特数据。
可参考图1d进行理解，图1d为本申请实施例提供的一种外层码块和内层码块的示意图。如图1d所示，第一个内层66码块的前64比特通过第一个外层码块的第2比特至第63比特承载，第一个内层66B码块的后两个比特通过第二个外层码块的第2比特至第3比特承载；第二个内层66B码块的前62比特，通过第二个外层码块的第4比特至第65比特承载，第二个内层66B码块的后4个比特通过第三个外层码块的第2比特至第5比特承载，以此类推。
关于图1a所示的SPN架构中的其它内容，可以参考中国移动SPN小颗粒白皮书中的相关描述，此处不做详细描述。
虽然在以上描述中，采用64/66B的编码方式对MAC frame进行编码，但是以上仅作为一种可能的实现方式而示出，对MAC frame进行编码所采用的编码技术不限于以上所述的64/65B。例如，也可以采用64/65B的编码方式对MAC frame进行编码；又如，也可以采用256/257B的编码方式对MAC frame进行编码，等等，此处不一一列举说明。
为方便描述，在以下实施例中，均以编码方式为64/66B为例进行说明。
接下来，结合上述提及的图1e介绍本申请实施例的应用场景。图1e为本申请实施例提供的一种示例性应用场景示意图。
如图1e所示，PE1和PE2之间建立了一条端到端、用于承载小颗粒业务传输路径。其中：PE1和PE2之间还包括设备P1和设备P2。虽然图1e中未示出，但是PE1和设备P1之间，也可以包括其它设备，相应的，设备P1和设备P2之间、设备P2和设备PE2之间，也均可以包括其它设备。
目前，小颗粒业务在传输的过程中，可能会出现传输错误，在一个示例中，前述fgBU可能会出现传输错误，例如，fgBU中的D码块、I码块、O码块以及T码块均可能会变为E码块。若在外层码块出现E码块时不进行处理，可能会导致误码扩散，影响小颗粒业务正常传输。
鉴于此，本申请实施例提供了一种故障码块处理方法及装置，能够避免误码扩散。
接下来，结合附图介绍该方法。
参见图2，该图为本申请实施例提供的一种故障码块处理方法的流程示意图。图2所示的故障码块处理方法，可以由使用FlexE细粒度技术的第一通信装置执行，该第一通信装置，可以是细粒度业务的交换节点。所谓细粒度业务的交换节点，指的是具备小颗粒业务解析功能的中间节点，例如，细粒度业务的交换节点可以是图1e所述的P1。第一通信装置也可以是细粒度业务的宿节点。所谓细粒度业务的宿节点，可以是接收小颗粒业务报文的尾节点，例如，细粒度业务的宿节点可以是图1e所示的PE2。
在一个示例中，所述方法100可以由第一通信装置的入接口执行；在又一个示例中，所述方法100可以由所述第一通信装置的出接口执行；在另一个示例中，所述方法100的部分步骤可以由所述入接口执行、部分步骤可以由所述出接口执行；本申请实施例不做具体限定。
本申请实施例中提及的通信装置，例如第一通信装置以及第二通信装置，可以是交换机、路由器等网络设备，也可以是网络设备上的一部分组件，例如是网络设备上的单板，线卡，还可以是网络设备上的一个功能模块，还可以是用于实现本申请方法的芯片，本申请实施例不做具体限定。通信装置之间例如可以但不限于通过以太网线或光缆直接连接。
在一个示例中，图1所示的方法100，例如可以包括如下S101-S103。
方法100中的外层码块和内层码块，可以参考上文对于外层码块和内层码块的描述部分，此处不做详细描述。
S101：获取第一fgBU，所述第一fgBU是由多个第一外层码块组成，所述多个第一外层码块包括外层S码块、多个外层D码块、以及第一外层E码块，所述第一外层E码块用 于承载第一内层码块的数据。
在一个示例中，所述第一通信装置可以首先获取包括多个外层码块的码块流，而后，对所述码块流进行分析，从而得到所述第一fgBU。
作为一个示例，若S101由第一通信装置的入接口执行，则“获取包括多个外层码块的码块流”在具体实现时，所述入接口例如可以接收上游节点(例如PE1节点)发送的所述包括多个外层码块的码块流。
作为又一个示例，若S101由第一通信装置的出接口执行，则所述“获取包括多个外层码块的码块流”在具体实现时，例如可以根据所述第一通信装置的入接口传递给所述出接口的数据，获得所述码块流。
在一个示例中，根据所述码块流获得第一fgBU在具体实现时，例如可以首先识别所述码块流中的第一外层E码块，而后，进一步确定该第一外层E码块所属的fgBU，从而确定所述第一fgBU。其中：
识别所述码块流中的第一外层E码块在具体实现时，例如可以将E码块与所述码块流进行匹配，从而确定所述码块流中的第一外层E码块。
确定第一外层E码块所属的fgBU在具体实现时，例如可以首先识别出所述码块流中的FlexE开销，从而定位所述码块流中的FlexE帧，根据小颗粒的时隙配置从FlexE帧的各个时隙中恢复出MTNP数据流，并根据所述MTNP数据流恢复得到至少一个fgBU，而后，将所述第一外层E码块对应的fgBU确定为第一fgBU。
在又一个示例中，根据所述码块流获得第一fgBU在具体实现时，例如可以首先根据所述码块流得到至少一个fgBU，而后，分别对所述至少一个fgBU进行分析，以确定各个fgBU中是否包括E码块，从而得到包括前述第一外层E码块的第一fgBU。
考虑到在码块流的传输过程中，其包括的D码块、T码块均可能会发生错误变成E码块，因此，所述第一外层E码块，可以是发生错误的第一外层D码块，也可以是发生错误的第一外层T码块。
如上文对于内层码块的描述可知，内层码块可以包括S码块、D码块、T码块，另外还可以包括空闲I码块和/或O码块。因此，所述第一内层码块，可以是S码块、D码块、T码块、空闲I码块以及O码块中的任意一种。
S102：根据所述第一fgBU，恢复所述第一内层码块。
根据所述第一fgBU恢复所述第一内层码块的具体实现，是将第一内层码块填入至外层码块的数据净荷字段的逆过程。在一个示例中，S102在具体实现时，可以提取所述第一fgBU中的数据净荷部分，对所述数据净荷部分拼接之后，恢复得到对应的内层66B码块。得到所述第一fgBU对应的内层66B码块之后，可以将所述第一外层E码块对应的内层66B码块，确定为所述第一内层码块。
关于所述第一外层E码块和所述第一内层码块，现结合图1d进行举例说明。在一个示例中，所述第一外层E码块可以是图1d所示的第一个外层66B码块，所述第一内层码块可以是第一个内层66B码块。在又一个示例中，所述第一外层码块可以是图1d所示的第二个外层66B码块，所述第一内层码块可以是图1d所示的第一个内层66B码块，或者，第二个内层66B码块。
在一个示例中，所述第一内层码块可以通过第一子时隙承载。其中，第一子时隙可以用于承载某一个sub client对应的数据，所述第一子时隙所承载的数据，可以包括多个内层码块，所述第一内层码块可以是所述多个内层码块中的其中一个码块。
S102可以由第一通信装置的入接口执行，也可以由所述第一通信装置的出接口执行。
S103：将所述第一内层码块设置为第一内层E码块。
在一个示例中，为了避免由于第一外层E码块而导致误码扩散，恢复所述第一内层码块之后，可以将所述第一内层码块设置为第一内层E码块。
在一个示例中，S103可以由所述第一通信装置的入接口执行，也可以由所述第一通信装置的出接口执行。
在一些实施例中，若S102由所述第一通信装置的入接口执行，而S103由所述第一通信装置的出接口执行，则在一个示例中，所述入接口在恢复所述第一内层码块之后，可以为所述第一内层码块添加标记，相应的，所述出接口根据所述标记，将所述第一内层码块设置为第一内层E码块。
如前所述，第一内层码块可以对应第一子时隙，所述第一子时隙可以对应多个内层码块，对于这种情况，考虑到第一内层码块出现错误，则该第一子时隙所承载的数据整体也发生了错误，对于这种情况，在一个示例中，S103在具体实现时，可以将所述第一子时隙对应的多个内层码块均设置为内层E码块。当然，在另一个示例中，可以将所述第一内层码块设置为第一内层E码块，对于所述第一子时隙对应的多个内层码块中、除所述第一内层码块之外的内层码块可以不做处理。在又一个示例中，也可以将所述第一子时隙对应的多个内层码块中的部分码块设置为内层E码块，所述部分码块可以包括所述第一内层码块。例如，可以将所述第一内层码块以及所述第一子时隙对应的多个内层码块中、与所述第一内层码块相邻的若干个内层码块设置为内层E码块。
如前所述，第一通信装置可以是细粒度业务交换节点，则在一个示例中，第一通信装置将所述第一内层码块设置为第一内层E码块之后，可以将所述第一内层E码块发送给第二通信装置。在一个示例中，第一通信装置可以将包括所述第一内层E码块的码块流发送给所述第二通信装置，其中，所述包括第一内层E码块的码块流，可以是经过二次编码之后的码块流。关于二次编码，可以参考上文的相关描述部分，此处不做详细描述。
如前所述，第一通信装置可以是细粒度业务的宿节点，则在一个示例中，第一通信装置将所述第一内层码块设置为第一内层E码块之后，可以将所述第一内层E码块发送给所述第一通信装置的以太帧客户信号恢复模块。在一个示例中，所述第一通信装置例如可以将包括所述第一内层E码块的复用结构发送给所述以太帧客户信号恢复模块，以便于所述以太帧客户信号恢复模块对接收到的复用结构进行数据恢复，得到各个客户(sub client)对应的数据，即得到各个客户对应的以太网帧。由于第一内层码块被设置为第一内层E码块，因此，以太帧客户信号恢复模块在基于接收到的复用结构恢复以太网帧时，可以将第一内层E码块丢弃，而不是将所述第一内层E码块当成正常的码块进行处理，因此，可以避免误码扩散。关于以太帧客户信号恢复模块根据复用结构恢复以太网帧的过程，可以参考IEEE 802.3的相关内层，此处不做详细描述。
如前所述，一个外层码块可以对应一个或者两个内层码块。因此，在一个示例中，所 述第一外层E码块除了可以承载第一内层码块之外，还可以承载第二内层码块。例如，在图1d所示的场景中，第一外层E码块为第二个外层码块，则第一外层E码块可以对应第一个内层码块和第二个内层码块。对于这种情况，第一通信装置除了可以执行以上方法100之外，还可以执行以下步骤A1-A2。
步骤A1：根据所述第一fgBU，恢复所述第二内层码块。
步骤A2：将所述第二内层码块设置为第二内层E码块。
执行步骤A1-A2，可以避免由于第二内层码块未被设置为E码块而导致误码扩散。
关于步骤A1-A2的具体实现，可以参考方法100中关于S102-S103的具体实现部分，此处不再重复描述。
在一个示例中，若所述第一通信装置为细粒度业务交换节点，执行A1-A2之后，除了可以将还可以将所述第一内层码块发送给第二通信装置之外，还可以将所述第二内层E码块发送给第二通信装置。在一个示例中，第一通信装置可以将包括所述第一内层E码块和所述第二内层E码块的码块流发送给所述第二通信装置，其中，所述包括第一内层E码块和所述第二内层E码块的码块流，可以是经过二次编码之后的码块流。关于二次编码，可以参考上文的相关描述部分，此处不做详细描述。
在又一个示例中，若所述第一通信装置为细粒度业务的宿节点，执行A1-A2之后，除了可以将还可以将所述第一内层码块发送给所述第一通信装置的以太网帧客户信号恢复模块之外，还可以将所述第二内层E码块发送给所述第一通信装置的以太网帧客户信号恢复模块。在一个示例中，所述第一通信装置例如可以将包括所述第一内层E码块和所述第二内层E码块的复用结构发送给所述以太帧客户信号恢复模块，以便于所述以太帧客户信号恢复模块对接收到的复用结构进行数据恢复，得到各个sub client对应的数据。
在一个示例中，所述第一fgBU所包括的多个第一外层码块除了包括前述第一外层E码块之外，还可以包括第二外层E码块，该第二外层E码块，可以是发生错误的第二外层D码块，该第二外层E码块用于承载第三内层码块的数据。对于这种情况，第一通信装置还可以执行以下步骤B1-B2。
步骤B1：根据所述第一fgBU，恢复所述第三内层码块。
步骤B2：将所述第三内层码块设置为第三内层E码块。
执行步骤B1-B2，可以避免由于第三内层码块未被设置为E码块而导致误码扩散。
关于步骤B1-B2的具体实现，可以参考方法100中关于S102-S103的具体实现部分，此处不再重复描述。
在一个示例中，若所述第一通信装置为细粒度业务交换节点，执行B1-B2之后，除了可以将还可以将所述第一内层码块发送给第二通信装置之外，还可以将所述第三内层E码块发送给第二通信装置。在一个示例中，第一通信装置可以将包括所述第一内层E码块和所述第三内层E码块的码块流发送给所述第二通信装置，其中，所述包括第一内层E码块和所述第三内层E码块的码块流，可以是经过二次编码之后的码块流。关于二次编码，可以参考上文的相关描述部分，此处不做详细描述。
在又一个示例中，若所述第一通信装置为细粒度业务的宿节点，执行B1-B2之后，除了可以将还可以将所述第一内层码块发送给所述第一通信装置的以太网帧客户信号恢复模 块之外，还可以将所述第三内层E码块发送给所述第一通信装置的以太网帧客户信号恢复模块。在一个示例中，所述第一通信装置例如可以将包括所述第一内层E码块和所述第三内层E码块的复用结构发送给所述以太帧客户信号恢复模块，以便于所述以太帧客户信号恢复模块对接收到的复用结构进行数据恢复，得到各个sub client对应的数据。
在一个示例中，除了第一fgBU中可能包括外层E码块(例如前述第一外层E码块和第二外层E码块)之外，其它fgBU中也可能会包括外层E码块。对于这种情况，第一通信装置还可以执行以下步骤C1-C3。
步骤C1：获取第二fgBU，所述第二fgBU由多个第二外层码块组成，所述多个第二外层码块包括外层S码块，多个外层D码块，以及第四外层E码块，所述第四外层E码块用于承载第四内层码块的数据。
步骤C2：根据所述第二fgBU，恢复所述第四内层码块。
步骤C3：将所述第四内层码块设置为第四内层E码块。
关于步骤C1-C3的具体实现，可以参考上文对于方法100的具体描述部分，此处不做重复描述。
在一个示例中，若所述第一通信装置为细粒度业务交换节点，则执行步骤C1-C3之后，第一通信装置还可以向第二通信装发送所述第四内层E码块。
在一个示例中，若所述第一通信装置为细粒度业务的宿节点，则执行步骤C1-C3之后，第一通信装置还可以将所述第四内层E码块发送给所述第一通信装置的以太网帧客户信号恢复模块。
本申请实施例还提供了一种故障码块处理装置，该装置可以应用于使用FlexE细粒度技术的第一通信装置，所述故障码块处理装置可以包括收发单元和处理单元。所述收发单元用于执行上述方法实施例各种可能的实现方式中由所述第一通信装置所执行的接收和/或发送相关的操作；所述处理单元用于执行上述方法实施例各种可能的实现方式中由所述第一通信装置所执行接收和/或发送相关的操作之外的操作。在具体实现中，所述收发单元可以包括接收单元和/或发送单元，接收单元用于执行接收相关的操作，发送单元用于执行发送相关的操作。
在一个具体的示例中，可参见图3，该图为本申请实施例提供的一种故障码块处理装置的结构示意图。如图3所示，所述故障码块处理装置300可以包括接收单元301和处理单元302。
所述接收单元301，用于获取第一细粒度基本单元fgBU，所述第一fgBU由多个第一外层码块组成，所述多个第一外层码块包括外层起始S码块、多个外层数据D码块、以及第一外层错误E码块，所述第一外层E码块用于承载第一内层码块的数据；所述处理单元302，用于根据所述第一fgBU，恢复所述第一内层码块，将所述第一内层码块设置为第一内层E码块。
在一种可能的实现方式中，所述第一内层码块对应第一子时隙，所述将所述第一内层码块设置为第一内层E码块，包括：将所述第一子时隙所对应的多个内层码块设置为内层E码块，所述多个内层码块包括所述第一内层码块。
在一种可能的实现方式中，所述多个第一外层码块还包括结束T码块，所述第一外层 E码块为发生错误的第一外层D码块。
在一种可能的实现方式中，所述第一外层E码块为发生错误的T码块。
在一种可能的实现方式中，所述第一通信装置为细粒度业务交换节点，所述装置还包括：发送单元，用于向第二通信装发送所述第一内层E码块。
在一种可能的实现方式中，所述第一通信装置为细粒度业务的宿节点，所述装置还包括：发送单元，用于将所述第一内层E码块发送给所述第一通信装置的以太网帧客户信号恢复模块。
在一种可能的实现方式中，所述第一外层E码块还用于承载第二内层码块的数据，所述处理单元302，还用于：根据所述第一fgBU，恢复所述第二内层码块，并将所述第二内层码块设置为第二内层E码块。
在一种可能的实现方式中，所述第一通信装置为细粒度业务交换节点，所述装置包括的发送单元，还用于：向第二通信装发送所述第二内层E码块。
在一种可能的实现方式中，所述第一通信装置为细粒度业务的宿节点，所述装置包括的发送单元，还用于：将所述第二内层E码块发送给所述第一通信装置的以太网帧客户信号恢复模块。
在一种可能的实现方式中，所述多个第一外层码块还包括第二外层E码块，所述第二外层E码块为发生错误的第二外层D码块,所述第二外层E码块用于承载第三内层码块的数据；所述处理单元，还用于：根据所述第一fgBU，恢复所述第三内层码块，将所述第三内层码块设置为第三内层E码块。
在一种可能的实现方式中，所述接收单元301，还用于：获取第二fgBU，所述第二fgBU由多个第二外层码块组成，所述多个第二外层码块包括外层S码块，多个外层D码块，以及第四外层E码块，所述第四外层E码块用于承载第四内层码块的数据；所述处理单元，还用于根据所述第二fgBU，恢复所述第四内层码块，将所述第四内层码块设置为第四内层E码块。
在一种可能的实现方式中，所述第一内层码块包括以下任意一种类型的码块：S码块、D码块、T码块、空闲I码块、或O码块。
在一种可能的实现方式中，所述第一通信装置为细粒度业务交换节点，所述将所述第一内层码块设置为第一内层E码块，包括：所述第一通信装置的出接口将所述第一内层码块设置为第一内层E码块。
由于所述装置300是与以上方法实施例提供的由第一通信装置执行方法对应的装置，所述装置300的各个单元的具体实现，均与以上方法实施例为同一构思，因此，关于所述装置300的各个单元的具体实现，可以参考以上方法实施例的描述部分，此处不再赘述。
此外，本申请实施例还提供了一种通信装置400，参见图4所示，图4为本申请实施例提供的一种通信装置的结构示意图。该通信装置400包括通信接口401和与通信接口401连接的处理器402。该通信装置400可以用于执行以上实施例中的方法10。
在一个示例中，所述通信装置400可以执行以上实施例中的方法100，当通信装置400用于执行以上实施例中的方法100时，通信装置400相当于方法100中的第一通信装置。通信接口401用于执行方法100中第一通信装置执行的收发操作。处理器402用于执行方 法100中第一通信装置执行的除收发操作之外的操作。例如：通信接口401用于获取第一fgBU，所述第一fgBU是由多个第一外层码块组成，所述多个第一外层码块包括外层S码块、多个外层D码块、以及第一外层E码块，所述第一外层E码块用于承载第一内层码块的数据；处理器402用于根据所述第一fgBU，恢复所述第一内层码块，将所述第一内层码块设置为第一内层E码块。
此外，本申请实施例还提供了一种通信装置500，参见图5所示，图5为本申请实施例提供的一种通信装置的结构示意图。该通信装置500可以用于执行以上实施例中的方法100。
如图5所示，通信装置500可以包括处理器510，与所述处理器510耦合连接的存储器520，收发器530。收发器530例如可以是通信接口，光模块等。处理器510可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。处理器还可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic,GAL)或其任意组合。处理器510可以是指一个处理器，也可以包括多个处理器。存储器520可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；存储器也可以包括非易失性存储器(英文：non-volatile memory)，例如只读存储器(read-only memory，ROM)，快闪存储器(英文：flash memory)，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)；存储器520还可以包括上述种类的存储器的组合。存储器520可以是指一个存储器，也可以包括多个存储器。在一个实施方式中，存储器520中存储有计算机可读指令，所述计算机可读指令包括多个软件模块，例如发送模块521，处理模块522和接收模块523。处理器510执行各个软件模块后可以按照各个软件模块的指示进行相应的操作。在本实施例中，一个软件模块所执行的操作实际上是指处理器510根据所述软件模块的指示而执行的操作。
在一个示例中，所述通信装置500可以执行以上实施例中的方法100，当通信装置500用于执行以上实施例中的方法100时，通信装置500相当于方法100中的第一通信装置。收发器530用于执行方法100中第一通信装置执行的收发操作。处理器510用于执行方法100中第一通信装置执行的除收发操作之外的操作。例如：收发器530用于获取第一fgBU，所述第一fgBU是由多个第一外层码块组成，所述多个第一外层码块包括外层S码块、多个外层D码块、以及第一外层E码块，所述第一外层E码块用于承载第一内层码块的数据；处理器510用于根据所述第一fgBU，恢复所述第一内层码块，将所述第一内层码块设置为第一内层E码块。
本申请还提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得所述计算机执行前述实施例中所述的方法(例如方法100)中任意一个或多个操作。
本申请还提供了一种计算机程序产品，包括计算机程序，当其在计算机上运行时，使得所述计算机执行前述实施例中所述的方法(例如方法100)中任意一个或多个操作。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四” 等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑业务划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各业务单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件业务单元的形式实现。
集成的单元如果以软件业务单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明所描述的业务可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些业务存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上仅为本发明的具体实施方式而已。
以上，以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实 施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (17)

  1. 一种故障码块处理方法，其特征在于，应用于使用灵活以太网FlexE细粒度技术的第一通信装置，所述方法包括：
    获取第一细粒度基本单元fgBU，所述第一fgBU由多个第一外层码块组成，所述多个第一外层码块包括外层起始S码块、多个外层数据D码块、以及第一外层错误E码块，所述第一外层E码块用于承载第一内层码块的数据；
    根据所述第一fgBU，恢复所述第一内层码块；
    将所述第一内层码块设置为第一内层E码块。
  2. 根据权利要求1所述的方法，其特征在于，所述第一内层码块对应第一子时隙，所述将所述第一内层码块设置为第一内层E码块，包括：
    将所述第一子时隙所对应的多个内层码块设置为内层E码块，所述多个内层码块包括所述第一内层码块。
  3. 根据权利要求1或2所述的方法，其特征在于，所述多个第一外层码块还包括结束T码块，所述第一外层E码块为发生错误的第一外层D码块。
  4. 根据权利要求1或2所述的方法，其特征在于，所述第一外层E码块为发生错误的T码块。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述第一通信装置为细粒度业务交换节点，所述方法还包括：
    向第二通信装发送所述第一内层E码块。
  6. 根据权利要求1-4任一项所述的方法，其特征在于，所述第一通信装置为细粒度业务的宿节点，所述方法还包括：
    将所述第一内层E码块发送给所述第一通信装置的以太网帧客户信号恢复模块。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述第一外层E码块还用于承载第二内层码块的数据，所述方法还包括：
    根据所述第一fgBU，恢复所述第二内层码块，并将所述第二内层码块设置为第二内层E码块。
  8. 根据权利要求7所述的方法，其特征在于，所述第一通信装置为细粒度业务交换节点，所述方法还包括：
    向第二通信装发送所述第二内层E码块。
  9. 根据权利要求7所述的方法，其特征在于，所述第一通信装置为细粒度业务的宿节点，所述方法还包括：
    将所述第二内层E码块发送给所述第一通信装置的以太网帧客户信号恢复模块。
  10. 根据权利要求1-9任一项所述的方法，其特征在于，所述多个第一外层码块还包括第二外层E码块，所述第二外层E码块为发生错误的第二外层D码块,所述第二外层E码块用于承载第三内层码块的数据；所述方法还包括：
    根据所述第一fgBU，恢复所述第三内层码块，将所述第三内层码块设置为第三内层E码块。
  11. 根据权利要求1-10任一项所述的方法，其特征在于，所述方法还包括：
    获取第二fgBU，所述第二fgBU由多个第二外层码块组成，所述多个第二外层码块包括外层S码块，多个外层D码块，以及第四外层E码块，所述第四外层E码块用于承载第四内层码块的数据；
    根据所述第二fgBU，恢复所述第四内层码块，将所述第四内层码块设置为第四内层E码块。
  12. 根据权利要求1-11任意一项所述的方法，其特征在于，所述第一内层码块包括以下任意一种类型的码块：
    S码块、D码块、T码块、空闲I码块、或O码块。
  13. 根据权利要求1-5任意协议所述的方法，其特征在于，所述第一通信装置为细粒度业务交换节点，所述将所述第一内层码块设置为第一内层E码块，包括：
    所述第一通信装置的出接口将所述第一内层码块设置为第一内层E码块。
  14. 一种故障码块处理装置，其特征在于，应用于使用灵活以太网FlexE细粒度技术的第一通信装置，所述装置包括：
    收发单元和处理单元；
    所述收发单元，用于执行权利要求1-13任意一项所述的由第一通信装置执行的接收和/或发送操作；
    所述处理单元用于执行权利要求1-13任意一项所述的由第一通信装置执行的接收和/或发送操作之外的操作。
  15. 一种通信装置，其特征在于，包括：处理器和存储器；
    所述存储器，用于存储指令；
    所述处理器，用于执行所述指令，使得所述通信装置执行权利要求1-13任意一项所述的方法。
  16. 一种计算机可读存储介质，其特征在于，包括指令，当所述指令在处理器上运行时，实现权利要求1-13任意一项所述的方法。
  17. 一种计算机程序产品，其特征在于，包括计算机程序，当所述计算机程序在处理器上运行时，实现权利要求1-13任意一项所述的方法。
PCT/CN2023/103322 2022-08-08 2023-06-28 一种故障码块处理方法及装置 WO2024032191A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210945854.1A CN117579220A (zh) 2022-08-08 2022-08-08 一种故障码块处理方法及装置
CN202210945854.1 2022-08-08

Publications (1)

Publication Number Publication Date
WO2024032191A1 true WO2024032191A1 (zh) 2024-02-15

Family

ID=89850614

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/103322 WO2024032191A1 (zh) 2022-08-08 2023-06-28 一种故障码块处理方法及装置

Country Status (2)

Country Link
CN (1) CN117579220A (zh)
WO (1) WO2024032191A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112468259A (zh) * 2019-09-09 2021-03-09 华为技术有限公司 一种通信方法、设备及存储介质
CN112491499A (zh) * 2020-10-22 2021-03-12 中兴通讯股份有限公司 数据发送方法及装置、存储介质、电子装置
CN113316037A (zh) * 2017-05-02 2021-08-27 华为技术有限公司 一种业务承载的方法、设备和系统
CN113938247A (zh) * 2020-07-14 2022-01-14 中国移动通信有限公司研究院 一种码块处理方法、节点及介质
CN113938245A (zh) * 2020-07-13 2022-01-14 华为技术有限公司 一种速率适配方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113316037A (zh) * 2017-05-02 2021-08-27 华为技术有限公司 一种业务承载的方法、设备和系统
CN112468259A (zh) * 2019-09-09 2021-03-09 华为技术有限公司 一种通信方法、设备及存储介质
CN113938245A (zh) * 2020-07-13 2022-01-14 华为技术有限公司 一种速率适配方法及装置
CN113938247A (zh) * 2020-07-14 2022-01-14 中国移动通信有限公司研究院 一种码块处理方法、节点及介质
CN112491499A (zh) * 2020-10-22 2021-03-12 中兴通讯股份有限公司 数据发送方法及装置、存储介质、电子装置

Also Published As

Publication number Publication date
CN117579220A (zh) 2024-02-20

Similar Documents

Publication Publication Date Title
JP7282187B2 (ja) フレキシブルイーサネット通信方法及びネットワーク装置
US7693078B2 (en) Method for supporting SDH/SONET OAMP on Ethernet
WO2022022263A1 (zh) 一种传输数据的方法和设备
KR20200103077A (ko) 데이터 전송 방법, 통신 장치, 및 저장 매체
JP7052046B2 (ja) データ伝送方法、通信機器、および記憶媒体
US20210273826A1 (en) Communication method and communications apparatus
US20210385127A1 (en) Flexible ethernet communication method and network device
US6973084B1 (en) Hybrid data transport scheme over optical networks
WO2022062930A1 (zh) 一种码块流的处理方法及装置
CN113497728A (zh) 一种业务流调整方法和通信装置
US11804982B2 (en) Communication method and apparatus
WO2023109424A1 (zh) 一种数据传输的方法以及相关装置
WO2024032191A1 (zh) 一种故障码块处理方法及装置
EP4239918A1 (en) Code block recognition method and apparatus
WO2024087975A1 (zh) 一种通信方法及装置
WO2023197770A1 (zh) 一种故障通告方法及装置
WO2023071249A1 (zh) 一种时隙协商方法及装置
WO2024032269A1 (zh) 通信方法、相关装置及计算机可读存储介质
US20230396353A1 (en) Communication Method and Device, and Chip System
CN116962145A (zh) 一种故障通告方法及装置
CN118055076A (zh) 一种报文处理方法、信息处理方法及装置
Dai et al. An adaptive forward error correction method for TDM over Ethernet

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

Country of ref document: EP

Kind code of ref document: A1