Forward Error Correction Control
By switching the FEC settings of different parts in the communication system, the problem of low switching efficiency of FEC settings in the prior art is solved, and more efficient data transmission and stronger error correction capabilities are achieved.
Patent Information
- Application Number
- CN202111198862.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2021-09-09
- Filing Date
- 2021-10-14
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2041-10-14
AI Technical Summary
When using forward error correction (FEC) technology, it is difficult for existing communication systems to effectively switch the FEC settings between data bursts in different parts, resulting in limited communication efficiency and reliability.
By introducing multiple FEC settings in the communication system and switching different FEC settings between the transmitter and receiver through the message delivery mechanism, the encoding method is dynamically adjusted according to the channel characteristics and the requirements of the data part, and different parts of data bursts are supported. Use different FEC codes.
It improves the data transmission efficiency and reliability of the communication system, can dynamically adjust the encoding method according to the requirements of different channel conditions and data parts, and enhances the correction ability and throughput of bit error rates.
Smart Images

Figure CN114374472B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application is based upon and claims the benefit of U.S. patent application serial number 17 / 470,293, filed on September 9, 2021, entitled Forward Error Correction Control, which U.S. application claims the benefit of U.S. Provisional Application Serial Number 63 / 092,473, filed on October 15, 2020, each of which is incorporated herein by reference in its entirety. Technical Field
[0003] Various example embodiments relate generally to communication systems, and more particularly, but not exclusively, to supporting forward error correction (FEC) in communication systems. Background Art
[0004] Forward error correction (FEC) may be used in various communication environments to support improved communications through a communication network. Summary of the invention
[0005] In at least some example embodiments, an apparatus includes at least one processor and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least support communication of a message configured to cause a transmitter of a data burst to use a first forward error correction setting for encoding a first portion of the data burst and to use a second forward error correction setting for encoding a second portion of the data burst, wherein the second forward error correction setting is different from the first forward error correction setting. In at least some example embodiments, a non-transitory computer-readable medium includes computer program code, the computer program code being configured to cause the apparatus to at least support communication of a message configured to cause a transmitter of a data burst to use a first forward error correction setting for encoding a first portion of the data burst and to use a second forward error correction setting for encoding a second portion of the data burst, wherein the second forward error correction setting is different from the first forward error correction setting. In at least some example embodiments, a method includes supporting communication of a message configured to cause a transmitter of a data burst to use a first forward error correction setting for encoding a first portion of the data burst and to use a second forward error correction setting for encoding a second portion of the data burst, wherein the second forward error correction setting is different from the first forward error correction setting. In at least some example embodiments, an apparatus includes means for supporting communication of a message configured to cause a transmitter of a data burst to use a first forward error correction setting for encoding a first portion of the data burst and to use a second forward error correction setting for encoding a second portion of the data burst, wherein the second forward error correction setting is different from the first forward error correction setting. In at least some example embodiments, the message includes at least one of an indication of the first forward error correction setting or an indication of the second forward error correction setting. In at least some example embodiments, the message includes one or more of: at least one of an indication of a location of a first portion of the data burst or an indication of a location of a second portion of the data burst, at least one of an indication of a length of a first portion of the data burst or an indication of a length of a second portion of the data burst, or at least one of an indication of a number of codewords of a first portion of the data burst or an indication of a number of codewords of a second portion of the data burst. In at least some example embodiments, the message is configured to enable the transmitter to calculate information indicating at least one of a location of a first portion of a data burst or a location of a second portion of the data burst. In at least some example embodiments, the message includes forward error correction setting control information. In at least some example embodiments, the forward error correction setting control information indicates that a first forward error correction setting is to be used for the first portion of the data burst and a second forward error correction setting is to be used for the second portion of the data burst.In at least some example embodiments, the forward error correction setting control information is configured to cause the transmitter to switch from using a first forward error correction setting to using a second forward error correction setting, and the message includes an indication of a position within the data burst at which the transmitter switches from using the first forward error correction setting to using the second forward error correction setting. In at least some example embodiments, the message is included in a framing sublayer (FS) frame. In at least some example embodiments, the message is a burst profile message. In at least some example embodiments, the message is a physical layer operation and management (PLOAM) message or an optical network unit (ONU) management and control interface (OMCI) message. In at least some example embodiments, the burst profile message is a Burst_Profile physical layer operation and management (PLOAM) message or an optical network unit (ONU) management and control interface (OMCI) message. In at least some example embodiments, the first forward error correction setting indicates a first code rate and the second forward error correction setting indicates a second code rate. In at least some example embodiments, the first forward error correction setting and the second forward error correction setting are based on forward error correction parameters for a forward error correction mother code. In at least some example embodiments, the forward error correction parameters for the forward error correction mother code include at least one of an amount of puncturing for the forward error correction mother code or an amount of shortening for the forward error correction mother code. In at least some example embodiments, at least one of the first forward error correction setting or the second forward error correction setting includes information for determining a new forward error correction code. In at least some example embodiments, the message is configured to cause the transmitter to use a third forward error correction setting for encoding a third portion of the data burst. In at least some example embodiments, communication of a first portion of the data burst encoded based on the first forward error correction setting is supported, and communication of a second portion of the data burst encoded based on the second forward error correction setting is supported. In at least some example embodiments, support for communication of the message may include receiving the message by the transmitter of the data burst from a receiver or controller of the data burst, or sending the message by the receiver of the data burst to the transmitter of the data burst. In at least some example embodiments, the transmitter includes an optical network unit (ONU) and the associated receiver includes an optical line terminal (OLT), and the ONU and the OLT are associated with a passive optical network (PON). BRIEF DESCRIPTION OF THE DRAWINGS
[0006] The teachings herein may be readily understood by considering the following detailed description in conjunction with the accompanying drawings, in which:
[0007] Figure 1 An example embodiment of a passive optical network (PON) configured to support forward error correction (FEC) for a communication channel is depicted;
[0008] Figure 2 Depicted are example embodiments of a PON configured to support FEC for communication channels;
[0009] Figure 3 depicts an example of a parity check matrix for a low-density parity check (LDPC) code;
[0010] Figure 4 An example of a compact representation of a parity check matrix of a quasi-cyclic (QC) QC LDPC code is depicted;
[0011] Figure 5 An example of a data burst structure that may be used in a PON system is depicted;
[0012] Figure 6 An example of a data burst structure that may be used in a PON system is depicted;
[0013] Figure 7 depicts an example of a burst profile message that may be modified or enhanced to support intra-burst FEC switching;
[0014] Figure 8 Describes the format of the downlink Framing Sublayer (FS) frame format and header fields and the format of the Bandwidth Map (BWmap) partition and allocation structure;
[0015] Fig. 9 depicts the hard decision performance of LDPC (11520, 8448) codes of length 11520 and 8448 information bits with a rate of 0.733 and the hard decision performance of LDPC (11520, 10240) codes with a rate of 0.889;
[0016] Fig.10 plots the code rate as a function of the overall electrical coding gain (ECG) relative to a default value; and
[0017] Fig.11 An example embodiment of a computer suitable for performing the various functions presented herein is depicted.
[0018] To facilitate understanding, identical reference numerals have been used herein, where possible, to designate identical elements that are common among the various figures. DETAILED DESCRIPTION
[0019] Various example embodiments are presented for supporting forward error correction (FEC) in a communication system.
[0020] Various example embodiments for supporting FEC in a communication system may include selection of FEC settings for a communication channel from a transmitter to a receiver, for example, selection of FEC settings for a communication channel, selection of FEC settings for a data burst sent through the communication channel, selection of FEC settings for a portion of a data burst sent through the communication channel, switching between FEC settings for different portions of a data burst through the communication channel, and the like, as well as various combinations thereof.
[0021] Various example embodiments for supporting FEC in a communication system may include selection of FEC settings for a communication channel from a transmitter to a receiver, the selection being based on channel characteristic information of the communication channel from the transmitter to the receiver. The selection of FEC settings may include determining settings for a current FEC code currently being used for communication through a communication channel, for example, applying the amount of puncturing of the selected FEC code, the amount of shortening of the selected FEC code, etc., and various combinations thereof, thus specifying the FEC code to be used for communication through the communication channel, etc., and various combinations thereof. The channel characteristic information of the communication channel that can be used for the selection of FEC settings for the communication channel may include one or more of the following: transfer function information, channel loss information, noise characteristic information, error information (e.g., bit error rate (BER)), error modeling information (e.g., information indicating a received error cluster distribution, information indicating an error-free operation distribution, etc.), etc., and various combinations thereof), etc., and various combinations thereof).
[0022] Various example embodiments for supporting FEC in a communication system may include selecting at least one FEC setting for a data burst on a communication channel, for example, selection of an FEC setting for a data burst on a communication channel, selection of an FEC setting for a portion of a data burst on a communication channel, switching between FEC settings for different portions of a data burst on a communication channel, and the like, and various combinations thereof. Various example embodiments for supporting FEC in a communication system may include supporting intra-burst FEC switching for communications on a communication channel. Various example embodiments for supporting FEC in a communication system may include supporting intra-burst FEC switching for communications on a communication channel by supporting the use of different FEC codes for sending different portions of a data burst on a communication channel. Various example embodiments for supporting FEC in a communication system may include supporting intra-burst FEC switching for communications on a communication channel by supporting the use of different FEC codes for sending different portions of a data burst on a communication channel based on messaging between endpoints using the communication channel for controlling switching between FEC codes within a data burst between endpoints on the communication channel. Various example embodiments for supporting FEC in a communication system may include: based on using messaging between endpoints of the communication channel to control switching between FEC settings within a data burst between endpoints on the communication channel, supporting intra-burst FEC switching for communications on a communication channel by: (1) receiving a message by a transmitter of a data burst from a receiver or controller of the data burst, the message being configured to cause the transmitter of the data burst to use a first FEC setting for encoding a first portion of the data burst and a second FEC setting for encoding a second portion of the data burst, or (2) sending a message by a receiver of the data burst to a transmitter of the data burst, the message being configured to cause the transmitter of the data burst to use a first FEC setting for encoding a first portion of the data burst and a second FEC setting for encoding a second portion of the data burst.
[0023] Based on the selection of FEC settings for the communication channel, various example embodiments for supporting FEC in a communication system can be applied within various types of communication systems, including various types of wired communication systems (e.g., fiber optic networks (e.g., passive optical networks (PON), point-to-point (P2P) fiber optic networks, etc.), Ethernet, digital subscriber line (DSL) networks, cable networks (e.g., DOCSIS 3.1, DOCSIS 3.1FDX, etc.), power line communication networks (e.g., G.hn, etc.), etc., and various combinations thereof), or various types of wireless communication systems (e.g., cellular networks (e.g., fourth generation (4G), 4G long term evolution (LTE), fifth generation (5G), etc.), WiFi networks, WiMAX networks, satellite networks, etc., and various combinations thereof); however, for the sake of clarity, various example embodiments for supporting FEC in communication systems are presented herein primarily in the context of PONs, and more specifically, in the context of supporting FEC between optical line terminals (OLTs) and optical network units (ONUs) via communication channels in an optical distribution network (ODN) of the PON (e.g., downstream from the OLT to the ONU or upstream from the ONU to the OLT). Various example embodiments for supporting FEC between the OLT and the ONU in the PON may be configured to support ONU-specific FEC for the ONU connected to the OLT, such that different FEC settings may be used by different ONUs connected to the same OLT.
[0024] It should be appreciated that advantages or potential advantages of these and various other example embodiments, as well as support for selecting FEC settings for a communication channel from a transmitter to a receiver, may be further appreciated by reference to the various drawings discussed further below.
[0025] Figure 1 An example embodiment of a PON configured to support FEC for communication channels is depicted.
[0026] The PON 100 may be a system for providing network access to a set of customers. For example, the PON 100 may provide network access at the "last mile" (e.g., the last portion of a telecommunications network that provides communications to and supports customer communications). For example, the PON 100 may operate as a point-to-multipoint (P2MP) data distribution system. It should be understood that the PON 100 may be one or more of various types of PONs, such as a time division multiplexing PON (e.g., a gigabit-capable PON (GPON), an Ethernet PON (EPON), etc.), a wavelength division multiplexing (WDM) PON, a time and wavelength division multiplexing (TWDM) PON (e.g., a next generation passive optical network (NG-PON), a next generation passive optical network 2 (NG-PON2), etc.), an orthogonal frequency division multiplexing (OFDM) PON, etc., and various combinations thereof.
[0027] The PON 100 includes an optical line terminal (OLT) 110 and a set of optical network units (ONUs) 120-1-120-N (collectively referred to as ONUs 120) connected via an optical distribution network (ODN) 130. The PON 100 may be configured to support downstream (DS) communications from the OLT 110 to the ONUs 120 via the ODN 130, and upstream (US) communications from the ONUs 120 to the OLT 110 via the ODN 130. It should be understood that the PON 100 may include various other elements that have been omitted for clarity.
[0028] The OLT 110 is configured to support communication between the ONU 120 and one or more upstream networks (omitted for the purpose of clarity). The OLT 110 may be located at a central location, such as a central office (CO) or other appropriate location. For example, the one or more upstream networks may include one or more core communication networks configured to support the OLT 110 and thus support communication of the ONU 120. For example, the OLT 110 may be configured to forward data received from the one or more upstream networks downstream to the ONU 120 via the ODN 130, and forward data received from the ONU 120 upstream to the one or more upstream networks via the ODN 130. The OLT 110 may include one or more communication elements 111 configured to support communication between the OLT 110 and the ONU 120, including one or more transmission elements (e.g., encoders, transmitters, etc.) for DS communication to the ONU 120 and one or more receiving elements (e.g., receivers, decoders, etc.) for US communication from the ONU 120. The OLT 110 may include one or more control elements 115 configured to control various aspects of communication between the OLT 110 and the ONU 120, including one or more transmission controllers (e.g., encoder controllers or other controllers), one or more reception controllers (e.g., decoder controllers, etc.), etc., and various combinations thereof. The OLT 110 including various components of the OLT 110 (e.g., communication elements 111, control elements 115, etc.) may be configured to support various functions for supporting FEC within the PON 100. It should be understood that the OLT 110 may include various other elements for supporting communication with the ONU 120, for supporting FEC for communication between the OLT 110 and the ONU 120, etc., and various combinations thereof.
[0029] Each ONU 120 is configured to support communication between the OLT 110 and one or more downstream networks or devices (omitted for clarity). The ONU 120 may be located at a corresponding user premises or other appropriate location. For example, one or more downstream networks or devices for the ONU 120 may include one or more local area networks (LANs) of the customer, one or more communication devices of the customer (e.g., modems, routers, switches, set-top boxes, smart TVs, game systems, computers, smart phones, etc., and various combinations thereof). For example, the ONU 120 may be configured to forward data received from the OLT 110 to one or more downstream networks or devices via the ODN 130, and to forward data received from one or more downstream networks or devices to the OLT 110 via the ODN 130. Each ONU 120 may include one or more communication elements 121 (respectively described as communication elements 121-1 to 121-N of ONUs 120-1 to 120-N (collectively referred to as communication elements 121)), and the one or more communication elements 121 are configured to support communication between the ONU 120 and the OLT 110, including one or more transmission elements (e.g., encoders, transmitters, etc.) for US communication to the OLT 110 and one or more receiving elements (e.g., receivers, decoders, etc.) for DS communication from the OLT 110). Each ONU 120 may include one or more control elements 125 (depicted as control elements 125-1 to 125-N (collectively, control elements 125) of ONUs 120-1 to 120-N, respectively), the one or more control elements 125 configured to control various aspects of communication between the ONU 120 and the OLT 110, including one or more transmission controllers (e.g., encoder controllers or other controllers), one or more reception controllers (e.g., decoder controllers, etc.), etc., and various combinations thereof. The ONU 120 includes various components of the ONU 120 (e.g., communication element 121, control element 125, etc.), and the ONU 120 may be configured to support various functions for supporting FEC within the PON 100. It should be understood that each ONU 120 may include various other elements for supporting communication with the OLT 110, for supporting FEC for communication between the ONU 120 and the OLT, etc., and various combinations thereof.
[0030] The ODN 130 may be a data distribution system configured to support communications between the OLT 110 and the ONUs 120. The ODN 130 is depicted as being arranged in a branching configuration; however, it should be understood that various other P2MP configurations may be used. The ODN 130 may include various passive optical components (e.g., optical fibers, couplers, splitters, etc.) that do not require power to distribute data signals between the OLT 110 and the ONUs 120; however, it should be understood that the ODN 130 may also include active components (e.g., optical amplifiers, etc.). It should be understood that the ODN 130 may include various other elements for supporting communications between the OLT 110 and the ONUs 120.
[0031] The PON 100 is configured to support FEC for communication between the OLT 110 and the ONU 120. The PON 100 may be configured to support selection of FEC settings for a communication channel between the OLT 110 and the ONU 120 based on channel characteristic information of the communication channel between the OLT 110 and the ONU 120. The communication channel may be a DS channel from the OLT 110 to the ONU 120 or a US channel from the ONU 120 to the OLT 110.
[0032] The selection of FEC settings for the communication channel between OLT 110 and ONU 120 may be performed for various types of FEC codes. For example, the selection of FEC settings for the communication channel between OLT 110 and ONU 120 may be performed for low density parity check (LDPC) codes, Reed-Solomon codes, binary convolutional codes, Hamming codes, etc., and various combinations thereof. It should be understood that although primarily presented herein with respect to example embodiments in which the FEC code is an LDPC code, the various example embodiments presented herein may use or be adapted to use various other types of FEC codes.
[0033] The selection of FEC settings for the communication channel between the OLT 110 and the ONU 120 as indicated above can be performed for an LDPC code. In general, an LDPC code is a block code that takes K information bits and encodes them into an N-bit codeword. Typically, the K information bits do not change in the codeword, and NK parity check bits are added; in this case, the code is also systematic. The code rate of the LDPC code is R = K / N, and its characteristics are completely described by the (NK)×N parity check matrix H. The N columns of H correspond to the bits of the LDPC codeword, with the columns corresponding to the information (data) bits d i The first K bits and the corresponding parity bit p iThe last (NK) bits of the LDPC code. The NK rows correspond to the check constraints that any valid codeword of the LDPC code should satisfy: that is, the XOR sum of all the bits indicated in the row must be 0. This can be formally expressed as (followed by an operation modulo 2, equivalent to the XOR sum): mod(Hc,2)=0, where c is a column vector of data bits d and parity bits p. Modern LDPC codes are typically quasi-cyclic (QC) codes. The parity check matrix of such a code can be subdivided into Z×Z sub-matrices, where each sub-matrix is either a rotated identity matrix or an all-zero matrix. Here, Z is often referred to as the lifting factor. The parity check matrix of a QC code can be expressed using the compact matrix H compact where -1 indicates an all-zero Z×Z submatrix, and any other element m indicates an identity submatrix whose rows have been cyclically right-shifted by m positions. The advantage of QC LDPC codes is that they can be specified using a very compact matrix representation, and they inherently allow parallelization, as indicated by the fact that H compact Each Z-check constraint in a row is the same constraint, but applies to different (independent) sets of bits. Again, it should be understood that although this article is primarily presented with respect to example embodiments in which the FEC code is an LDPC code, the various example embodiments presented herein may use or be adapted to use various other types of FEC codes.
[0034] The selection of FEC settings for the communication channel between OLT 110 and ONU 120 may be performed in various ways. In at least some example embodiments, for example, the selection of FEC settings for the communication channel between OLT 110 and ONU 120 may include determining the settings for the current FEC code currently being used for communications on the communication channel between OLT 110 and ONU 120 (e.g., the amount of puncturing of the current FEC code, the amount of shortening of the current FEC code, etc., and various combinations thereof). It should be understood that the selection of FEC settings for the communication channel between OLT 110 and ONU 120 may take into account the trade-off between user bit rate (FEC overhead) and link conditions, wherein it should be understood that an increase in puncturing may result in an increase in throughput but a decrease in the error correction capability of the code, whereas an increase in shortening may result in a decrease in throughput but an increase in error correction capability. In at least some example embodiments, for example, the selection of an FEC setting for a communication channel between OLT 110 and ONU 120 may include determining a new FEC code (e.g., a new LDPC matrix) to be used for communications on the communication channel, and various combinations thereof. For example, at least one of the first FEC setting or the second FEC setting may include information for determining the new FEC code. It should be understood that the determination of the FEC setting for the communication channel between OLT 110 and ONU 120 may depend on the type of FEC code being used or other factors.
[0035] The selection of the FEC setting for the communication channel between the OLT 110 and the ONU 120 based on the channel characteristic information of the communication channel between the OLT 110 and the ONU 120 can be based on various types of channel characteristic information that can be collected in various ways. For example, the channel characteristic information of the communication channel between the OLT 110 and the ONU 120 can be used as a basis for selecting the FEC setting for the communication channel between the OLT 110 and the ONU 120, and can include one or more of the following information: transfer function information, channel loss information, noise characteristic information, error information (e.g., bit error rate (BER), error modeling information (e.g., information indicating received error cluster distribution (ECD), information indicating error-free operation distribution (EFRD), etc.), etc., and various combinations thereof), etc., and various combinations thereof. It should be understood that various other types of channel characteristic information of the communication channel between the OLT 110 and the ONU 120 can be used as a basis for selecting the FEC setting for the communication channel between the OLT 110 and the ONU 120.
[0036] The selection of FEC settings for the communication channel between the OLT 110 and the ONU 120 may also (e.g., in addition to) or alternatively (e.g., instead of the channel characteristics) be based on one or more of: one or more boundary conditions, one or more communication element capabilities (e.g., transmitter capabilities of a transmitter of the communication channel between the OLT 110 and the ONU 120, receiver capabilities of a receiver of the communication channel between the OLT 110 and the ONU 120, etc., and various combinations thereof), etc., and various combinations thereof.
[0037] The selection of the FEC setting for the communication channel may be performed by the OLT 110 (e.g., the selected FEC setting, or at least an indication thereof, may be communicated by the OLT 110 to the ONU 120), by the ONU 120 (e.g., the selected FEC setting, or at least an indication thereof, may be communicated by the ONU 120 to the OLT 110), by an entity on behalf of the OLT 110 and the ONU 120 (e.g., and the selected FEC setting, or at least an indication thereof, may be communicated to the OLT 110 and the ONU 120), etc., as well as various combinations thereof.
[0038] The indication of the selected FEC setting for the communication channel may be provided to the OLT 110 and the ONU 120 in various ways. The indication of the selected FEC setting for the communication channel may be provided to the OLT 110 and the ONU 120 using various types of signaling or messaging (e.g., using in-band (IB) signaling or messaging, using out-of-band (OOB) signaling or messaging, using various message types, using various types of indicators or information, etc., and various combinations thereof). The indication of the FEC setting (where the selection of the FEC setting for the communication channel is performed by the OLT 110) may be considered to be provided to the OLT 110 by a virtualization of the reality that the OLT 110 has selected the FEC setting, may be considered to be provided to the OLT 110 via some internal messaging between components of the OLT 110, may be provided to the ONU 120 via IB or OOB messaging, etc., and various combinations thereof. The indication of the FEC setting (where the selection of the FEC setting for the communication channel is performed by the ONU 120) may be considered to be provided to the ONU 120 through a virtualization of the reality that the ONU 120 has selected the FEC setting, may be considered to be provided to the ONU 120 via some internal messaging between components of the ONU 120, may be provided to the ONU 110 via IB or OOB messaging, etc., and various combinations thereof. The indication of the FEC setting (where the selection of the FEC setting for the communication channel is performed by an element other than the OLT 110 or the ONU 120) may be provided to the OLT 110 via messaging from the element to the OLT 110, may be provided to the ONU 120 via messaging from the element to the ONU 120, may be provided to the ONU 120 via messaging from the element to the ONU 120, may be provided to the ONU 120 via messaging from the element to the ONU 120, and then a signal is passed from the OLT 110 to the ONU 120, etc., and various combinations thereof. The indication of the FEC setting may be communicated using various message types, such as physical layer operations administration and maintenance (PLOAM) messages, ONU management and control interface (OMCI) messages, etc., as well as various combinations thereof.
[0039] It should be appreciated that the various example embodiments discussed above regarding the configuration of PON 100 to support FEC for communications between OLT 110 and ONU 120 may be further understood by further considering the DS transmission direction within PON 100 and the US transmission direction within PON 100 as further discussed below.
[0040] The PON 100 may be configured to support DS FEC for DS communications from the OLT 110 to the ONU 120. It should be understood that, as discussed further below, supporting DS FEC for DS communications from the OLT 110 to the ONU 120 may be controlled by the OLT 110 (or an element included within or in communication with the OLT 110), may be controlled by the ONU 120 (or an element included within or in communication with the ONU 120), may be controlled by one or more elements on behalf of the OLT 110 and the ONU 120, etc., as well as various combinations thereof.
[0041] In one example, the OLT 110 may be configured to control support of DS FEC for DS communications from the OLT 110 to the ONU 120. In one example, the OLT 110 may obtain channel characteristic information for a channel from the OLT 110 to the ONU 120 (e.g., from the ONU 120, where the ONU 120 determines the channel characteristic information and provides the channel characteristic information to the OLT 110), select an FEC setting for the channel from the OLT 110 to the ONU 120, where the FEC setting is selected based on the channel characteristic information, and provide an indication of the FEC setting from the OLT 110 to the ONU 120 for supporting DS FEC for DS communications from the OLT 110 to the ONU 120.
[0042] In one example, the ONU 120 may be configured to control support of DS FEC for DS communications from the OLT 110 to the ONU 120. In one example, the ONU 120 may obtain channel characteristic information for a channel from the OLT 110 to the ONU 120 (e.g., locally at the ONU 120, where the ONU 120 determines the channel characteristic information based on the DS communications from the OLT 110), select an FEC setting for the channel from the OLT 110 to the ONU 120, where the FEC setting selects the FEC setting based on the channel characteristic information, and provide an indication of the FEC setting from the ONU 120 to the OLT 110 for supporting DS FEC for DS communications from the OLT 110 to the ONU 120.
[0043] In one example, the controller may be configured to control support of DSFEC for DS communications from the OLT 110 to the ONU 120. In one example, the controller may obtain channel characteristics for a channel from the OLT 110 to the ONU 120 (e.g., from the ONU 120, where the ONU 120 determines channel characteristic information and provides it to the controller, from the OLT 110, where the ONU 120 determines channel characteristic information and provides it to the OLT 110, which in turn provides it to the controller, etc.), select an FEC setting for the channel from the OLT 110 to the ONU 120, where the FEC setting is selected based on the channel characteristic information, and provide an indication of the FEC setting from the controller to the OLT 110 and the ONU 120 for use by the OLT 110 and the ONU 120 in supporting DS FEC for DS communications from the OLT 110 to the ONU 120.
[0044] It should be appreciated that PON 100 may be configured in various other ways to support DS FEC for DS communications from OLT 110 to ONU 120 .
[0045] The PON 100 may be configured to support US FEC for US communications from the ONU 120 to the OLT 110. It should be understood that, as discussed further below, supporting US FEC for US communications from the ONU 120 to the OLT 110 may be controlled by the OLT 110 (or an element included in or in communication with the OLT 110), may be controlled by the ONU 120 (or an element included in or in communication with the ONU 120), may be controlled by one or more elements on behalf of the OLT 110 and the ONU 120, etc., and various combinations thereof.
[0046] In one example, the OLT 110 may be configured to control support of US FEC for US communications from the ONU 120 to the OLT 110. In one example, the OLT 110 may obtain channel characteristic information for a channel from the ONU 120 to the OLT 110 (e.g., locally at the OLT 110, where the OLT 110 determines the channel characteristic information based on the US communications from the ONU 120), select an FEC setting for the channel from the ONU 120 to the OLT 110, where the FEC setting selects the FEC setting based on the channel characteristic information, and provide an indication of the FEC setting from the OLT 110 to the ONU 120 for supporting US FEC for US communications from the ONU 120 to the OLT 110.
[0047] In one example, the ONU 120 may be configured to control support of US FEC for US communications from the ONU 120 to the OLT 110. In one example, the ONU 120 may obtain channel characteristic information for a channel from the ONU 120 to the OLT 110 (e.g., from the OLT 110, where the OLT 110 determines the channel characteristic information and provides the channel characteristic information to the ONU 120), select an FEC setting for the channel from the ONU 120 to the OLT 110, where the FEC setting is selected based on the channel characteristic information, and provide an indication of the FEC setting from the ONU 120 to the OLT 110 for use in supporting US FEC for US communications from the ONU 120 to the OLT 110.
[0048] In one example, the controller may be configured to control support of US FEC for US communications from the ONU 120 to the OLT 110. In one example, the controller may obtain channel characteristic information for a channel from the ONU 120 to the OLT 110 (e.g., from the OLT 110, where the OLT 110 determines the channel characteristic information and provides it to the controller, from the ONU 120, where the OLT 110 determines the channel characteristic information and provides it to the ONU 120, which in turn provides it to the controller, etc.), select an FEC setting for the channel from the ONU 120 to the OLT 110, where the FEC setting is selected based on the channel characteristic information, and provide an indication of the FEC setting from the controller to the OLT 110 and the ONU 120 for use by the OLT 110 and the ONU 120 in supporting US FEC for US communications from the ONU 120 to the OLT 110.
[0049] It should be appreciated that PON 100 may be configured in various other ways to support US FEC for US communications from ONU 120 to OLT 110 .
[0050] By supporting selection of FEC settings for a communication channel between the OLT 110 and the ONUs 120, the PON 100 may be configured to support use of different FEC settings by different ONUs 120 connected to the same OLT 110, such as ONU-specific FEC settings on an ONU-by-ONU basis for the ONUs 120 connected to the same OLT 110, group-specific FEC settings for groups of ONUs 120 connected to the same OLT 110 (e.g., two groups of ONUs 120, four groups of ONUs 120, etc.), etc., as well as various combinations thereof. For example, in the case where ONU-specific settings are used for the ONUs 120, channel characteristic information of the communication channel between the OLT 110 and the ONUs 120 may be used to determine the ONU-specific settings to be used for the ONU 120 (e.g., as discussed above for a single ONU 120 connected to the OLT 110). For example, in the case where group-specific FEC settings are used for a group of ONUs 120 connected to the OLT 110, channel characteristic information of the communication channel between the OLT 110 and the ONUs 120 may be used to identify the assignment of the ONUs 120 to different groups of ONUs 120, and then may be used accordingly within the group of ONUs 120 to determine FEC settings for different groups of ONUs 120 to be applied to the ONUs 120 in the group of ONUs 120. For example, in a P2MP network, the channel characteristic information may be used to divide receivers into groups, and accordingly used to apply FEC settings to the receivers in the receiver group.
[0051] The PON 100 is configured to support FEC for communications between the OLT 110 and the ONU 120 by supporting intra-burst FEC switching for communications between the OLT 110 and the ONU 120. The PON 100 may support intra-burst FEC switching for communications between the OLT 110 and the ONU 120 by supporting the use of different FEC codes for different portions of a data burst sent between the OLT 110 and the ONU 120. By supporting the use of different FEC codes for different portions of a data burst sent between the OLT 110 and the ONU 120, the PON 100 may support burst intra-FEC switching for communications between the OLT 110 and the ONU 120 based on using messaging between the OLT 110 and the ONU 120 for controlling switching between FEC codes within a data burst between the OLT 110 and the ONU 120. The PON 100 may support intra-burst FEC switching for communications between the OLT 110 and the ONU 120 by supporting the use of different FEC codes for transmitting different portions of a data burst between the OLT 110 and the ONU 120, based on the use of FEC setting control information indicating that a first FEC setting is to be used for a first portion of a data burst and a second FEC setting is to be used for a second portion of the data burst. The PON 100 may support intra-burst FEC switching for communications between the OLT 110 and the ONU 120 based on the use of FEC setting control information indicating that a first FEC setting is to be used for a first portion of a data burst and a second FEC setting is to be used for a second portion of the data burst, wherein the FEC setting control information may be configured to cause a transmitter to switch from using the first FEC setting to using the second FEC setting, and wherein the message may include an indication of a position within the data burst at which the transmitter is to switch from using the first FEC setting to using the second FEC setting. For example, the ONU 120 may begin transmitting a data burst to the OLT 110 using a first FEC code (using the first FEC code for a first portion of the data burst), and may then switch to using a second FEC code within the data burst (using the second FEC code for a second portion of the data burst). For example, the ONU 120 may begin transmitting a data burst to the OLT 110 using a first FEC code for a first codeword of the data burst or the first few codewords of the data burst, and may then switch to using a second FEC code for the remainder of the data burst. For example, the ONU 120 may begin transmitting a data burst to the OLT 110 using a first FEC code for a majority of the data burst, and may then switch to using a second FEC code for the last few codewords of the data burst.For example, ONU 120 may begin transmitting a data burst to OLT 110 using a first FEC code (using the first FEC code for a first portion of a data burst), may then switch to using a second FEC code within the data burst (using the second FEC code for a second portion of the data burst), and may then switch to using a third FEC code within the data burst (using the third FEC code for a third portion of the data burst). It should be understood that while the use is primarily presented with respect to applying a particular number of FEC codes over a particular number of portions of a data burst (e.g., two FEC codes within a data burst are applied to two portions of a data burst, three FEC codes within a data burst are applied to three portions of a data burst, etc.), any suitable number of FEC codes may be used within a data burst over any suitable number of portions of a data burst, correspondingly for supporting transmission of corresponding portions of a data burst. The OLT 110 may control switching between FEC codes for data bursts of the ONU 120 based on monitoring of a communication channel from the ONU 120 to the OLT 110, evaluation of the communication channel from the ONU 120 to the OLT 110, and the like, and various combinations thereof. The OLT 110 may control switching between FEC codes for data bursts of the ONU 120 based on detection of one or more conditions associated with the communication channel from the ONU 120 to the OLT 110. The OLT 110 may control switching between FEC codes for data bursts of the ONU 120 by sending one or more instructions to the ONU 120 (e.g., sending an instruction with a corresponding FEC code for each portion of a data burst, sending a switching instruction when switching between FEC codes between adjacent portions of a data burst is to be performed, sending a separation instruction with corresponding FEC codes for corresponding portions of a data burst, and the like, and various combinations thereof). The ONU 120 may perform switching between FEC codes within a data burst of the ONU 120 based on one or more instructions received from the OLT 110 (e.g., receiving an instruction with a corresponding FEC code for each portion of the data burst, receiving a switching instruction when switching between FEC codes between adjacent portions of the data burst is to be performed, receiving a separation instruction with corresponding FEC codes for corresponding portions of the data burst, etc., and various combinations thereof). The instruction(s) for performing intra-burst FEC switching may be a general message, a burst profile message (which may be configured to specify, for each FEC code to be used within the burst, a corresponding position within the data burst at or on which the FEC code is to be applied), etc., and various combinations thereof. For example, the burst profile message may be a Burst_Profile physical layer operation and management (PLOAM) message or an optical network unit (ONU) management and control interface (OMCI) message.It should be appreciated that although primarily described with respect to performing internal burst FEC switching for data bursts from ONU 120 to OLT 110 , internal burst FEC switching may also or alternatively be performed for data bursts from OLT 110 to OLT 110 .
[0052] It should be understood that various functions discussed as being performed by specific elements of the PON 100 may be performed by various other elements of the PON 100. For example, various functions described as being performed by the OLT 110 may be performed by one or more components of the OLT 110 (e.g., decoders, decoder controllers, encoders, encoder controllers, OLT controllers, etc., and various combinations thereof), one or more elements in communication with the OLT 110, etc., and various combinations thereof. Similarly, for example, various functions described as being performed by the ONU 120 may be performed by one or more components of the ONU 120 (e.g., decoders, decoder controllers, encoders, encoder controllers, ONU controllers, etc., and various combinations thereof), one or more elements in communication with the ONU 120, etc., and various combinations thereof. It should be understood that such functions may be combined in various ways, distributed in various ways, etc., and various combinations thereof.
[0053] It should be understood that although the various example embodiments presented herein are primarily described with respect to the perspective of OLT and ONU, the various example embodiments presented herein may also be described with respect to the perspective of a transmitter and a receiver (e.g., the various example embodiments presented herein for supporting DS FEC from OLT to ONU may be considered as embodiments for supporting FEC from a transmitter to a receiver, where control of FEC may be provided at the transmitter side or at the receiver side, the various example embodiments presented herein for supporting US FEC from ONU to OLT may be considered as embodiments for supporting FEC from a transmitter to a receiver, where control of FEC may be provided at the transmitter side or at the transmitter side, etc.), the perspective of an encoder and a decoder (e.g., the various example embodiments presented herein for supporting DS FEC from OLT to ONU may be considered as embodiments for supporting FEC from an encoder to a decoder, where control of FEC may be provided at the encoder side or at the decoder side, the various example embodiments presented herein for supporting US FEC from ONU to OLT may be considered as embodiments for supporting FEC from an encoder to a decoder, where control of FEC may be provided at the encoder side or at the decoder side, etc.). Various example embodiments of FEC may be considered as embodiments for supporting FEC from an encoder to a decoder, wherein control of the FEC may be provided on the encoder side or the decoder side, etc.), and various combinations thereof. In other words, the ONU may be a transmitter or a receiver and the OLT may be a transmitter or a receiver, the ONU may be an encoder or a decoder and the OLT may be an encoder or a decoder, etc. It should be understood that the various example embodiments presented herein may be further understood by reference to the communication example embodiments for supporting selection of FEC settings for a communication channel from a transmitter to a receiver and for applying FEC on a communication channel by a transmitter and a receiver for communication.
[0054] It should be understood that further understanding of such example embodiments may be obtained by considering various aspects of such example embodiments as further discussed herein.
[0055] Various example embodiments relate to a next generation passive optical network (PON) for delivering broadband access, for example. A PON system has a point-to-multipoint (P2MP) topology, where one optical line terminal (OLT) on the network side is used to connect to the user side by means of an optical distribution network (ODN) or optical fiber equipment including optical fibers and splitters (see Figure 2The passive optical network 200 of the present invention may be a plurality of (e.g., up to 64) optical network units (ONUs). Most PON technologies (such as G-PON, E-PON, and XGS-PON) are time division multiplexing (TDM) PON technologies, in which the optical fiber medium is shared in time between different ONUs. There are also time division and wavelength division multiplexing (TWDM) PON technologies (such as NG-PON2), in which multiple TDM systems of different wavelengths are stacked on the same PON system. In addition, there are other experimental PON technologies, such as those using orthogonal frequency division multiplexing (OFDM). The various example embodiments presented herein can be applied to both TDM PON systems, TWDM PON systems, or other suitable types of PON systems.
[0056] For upstream (US) transmission, such PON systems typically rely on burst mode operation, where each ONU is assigned a time window within which it can send a burst of data. Only a single ONU can transmit at a given time. A burst typically consists of a preamble, a delimiter, and data.
[0057] The preamble corresponds to a known bit pattern. During the reception of the preamble, the receiver can adjust itself to the incoming burst. For example, during the preamble, the receiver will adjust the analog front end, (i.e., adjust the analog gain to the signal strength of the burst and also set the correct DC offset to compensate for the offset in the incoming burst), lock the clock of the incoming burst (by applying clock and data recovery (CDR)), and possibly train the equalizer to compensate for possible inter-symbol interference caused by fiber dispersion or due to bandwidth limitations of the transmitter or receiver components.
[0058] The delimiter is a short, known bit pattern that is used to indicate the end of the preamble and the beginning of the data.
[0059] Data is the portion of the burst that includes the actual data bits, and possibly control signals to be sent. Data is usually protected by forward error correction (FEC) and is organized in FEC codewords.
[0060] Recently, ITU Q2 has started working on the next-generation TDM-PON standard for 50G downlink and 10G / 12.5G / 25G / 50G uplink in the G.hsp project.
[0061] For the next generation 25G / 50G technology, PON technology will use low-density parity check (LDPC) codes for forward error correction (FEC). LDPC codes are an advanced and popular type of FEC, which is used to correct bit errors that occur during the transmission of data over the physical medium. LDPC codes are used in many modern standards, such as DSL (G.mgfast), WiFi (Wimax), wireless (5GNR), coaxial cable (DOCSIS 3.1 and DOCSIS 3.1 FDX), power line communication (G.hn), etc.
[0062] LDPC code is a block code that takes K information bits and encodes these K bits into an N-bit codeword, which generally includes K information bits in addition to NK parity check bits (meaning it is a systematic code). The code rate of LDPC code is R = K / N, and its characteristics are fully described by the (NK)×N parity check matrix H. Figure 3 An example of a parity check matrix 300 is shown. The N = 9 columns of H correspond to the bits of the LDPC codeword, where the first K = 5 bits correspond to the information (data) bits di, and the last (NK) = 4 bits correspond to the parity check bits pi. The NK = 4 rows correspond to the check constraints that any valid codeword of the LDPC code should satisfy, i.e., the XOR sum of all bits indicated in the row must be 0. This can be formally represented as (followed by the sum of operations modulo 2, equivalent to the XOR sum): mod(Hc, 2) = 0, where c is a column vector of data bits d and parity check bits p.
[0063] Modern LDPC codes are usually quasi-cyclic (QC) LDPC codes. The parity check matrix of such codes can be subdivided into Z×Z submatrices, where each submatrix is either a rotated identity matrix or an all-zero matrix. Here Z is often called the lifting factor. The parity check matrix of a QC code can be written using the compact matrix H compact To express, if Figure 4 400. Here, -1 indicates an all-zero submatrix, and any other element m indicates an identity submatrix that has been cyclically right-shifted by m. An advantage of QC LDPC codes is that they inherently allow parallelization, which can be seen, for example, by the fact that H compact Each Z-check constraint in a row is the same constraint, but applied to a different (independent) set of bits. In the G.hsp standard, LDPC codes are used to reduce the bit error rate from the worst case 1e-2 before LDPC decoding (input BER) to 1e-12 after LDPC decoding (output BER).
[0064] As mentioned above, LDPC codes are characterized by a code rate R = K / N, which is defined by its parity check matrix (ie, by its structure).However, there are two simple techniques that can be used to derive additional LDPC subcodes from a so-called LPDC mother code: shortening and puncturing.
[0065] When shortening, the LDPC code can be modified by setting the information bit to a fixed value (0) and not transmitting the bit. s bits reduces the information rate to R = (KN s ) / (NN s ), and allows the same output BER to be achieved at increased BER values.
[0066] When puncturing, LDPC can be modified by not sending certain bits (information or parity bits). These bits are then treated as erasures (i.e. bits with unknown values) at the receiver and must be retrieved by the LDPC decoder. Puncturing Np increases the information rate to R = K / (NN p ), but requires a lower input BER to achieve the same output BER.
[0067] By combining puncturing and shortening, the rate of LDPC code is R = (KN s ) / (NN p -N s ) can be adjusted within a wide range. For example, if the code length is kept fixed to N', the code length can be adjusted from R min =(K-(NN′)) / N′ changes to R max =K / N′.
[0068] It is important to note that these techniques are not specific to LDPC codes, but can be applied to FEC codes in general.
[0069] For a specific upstream wavelength in a T(W)DM PON system, burst mode transmission in the upstream direction involves one ONU transmitting at any given time. In previous PON systems, such as XGS PON and IEEE 802.3ca, the selection of FEC codes for upstream transmissions was determined by the corresponding standards. All ONUs are expected to transmit based on the selected FEC code. In addition, all codewords in the upstream burst from the ONU use the same FEC code, except for the last codeword of the burst, where additional shortening can be used to provide a finer granularity of burst duration.
[0070] Typically, FEC for upstream transmission is static and does not take into account the variation in the FEC decoder input bit error rate (BER) for different ONUs. It also does not take into account the FEC decoder input BER variation within a burst from a given ONU.
[0071] The first codeword or first few codewords of an uplink burst may experience a higher BER compared to the rest of the burst due to transients associated with laser activation and receiver stabilization, or due to insufficient convergence of the receiver equalizer. When receiver equalization is used, the length of the preamble must be balanced against the convergence level of the equalizer. On the one hand, a longer preamble will result in a better converged equalizer, since a larger preamble comes at the expense of lower efficiency; on the other hand, a shorter preamble improves efficiency, since an insufficiently converged equalizer comes at the expense of a higher BER at the beginning of the burst.
[0072] In addition, bit interleaving over multiple codewords can be used to mitigate the effects of correlated errors with binary LDPC FEC, especially for 50G uplink with receiver equalization. Although bit interleaving does not change the average BER at the LDPC decoder input, it breaks the correlation between errors in the codewords, thereby reducing the correlated error penalty for binary FEC codes. However, applying bit interleaving at the end of a burst can be very inefficient because it requires sending blocks of multiple codewords (as many as the interleaving length); if bit interleaving is not used at the end of a burst, the corresponding codeword may suffer from poor performance due to the negative impact of correlated errors.
[0073] Figure 5 Depicted is an example of a data burst structure that can be used in a PON system. Figure 5 In the data burst structure 500, except for the last codeword, the same FEC code is used by the entire burst. Typically, the last codeword will be shortened to accommodate the allocated burst length. Similarly, the last codeword can be punctured and shortened based on predefined rules for the size of the upstream grant. Additional puncturing is applied to reduce the amount of parity sent in the last codeword. The amount of puncturing and shortening is based on predefined rules that are expected to be applied by all ONUs at all times. There is no indication provided by the OLT to the ONU except for the grant size.
[0074] Various example embodiments may be configured to use different FEC codes in different parts of a burst to enhance throughput and performance of uplink transmissions.
[0075] Various example embodiments may be configured to vary the puncturing and / or shortening based on the position of the codeword in the burst.
[0076] Various example embodiments may be configured to provide tolerance to settling transients and inadequate equalizer convergence. Due to transients associated with laser activation and receiver settling, or due to insufficient convergence of the receiver equalizer, the first codeword or first few codewords of an upstream burst may experience a higher bit error rate than the remainder of the burst. In this case, the OLT may configure the first codeword or first few codewords of the upstream burst to operate with a lower rate code to provide additional margin for these transients. For the remainder of the burst, operation may switch to a higher rate.
[0077] Various example embodiments may be configured to provide performance guarantees in the absence of bit interleaving: Bit interleaving may be used to mitigate the effects of correlated errors, especially for 50G upstream. In case bit interleaving is not adopted by upstream or is not (partially) used in a burst (e.g. to reduce latency or to shorten burst length), a lower rate code may be used instead at the end of the burst to provide increased margin for correlated errors.
[0078] Various example embodiments may be configured to provide better efficiency at the end of a burst. Considerations for improving burst efficiency are typically focused on modifying only the last codeword of a burst; however, such bursts are unbalanced. With such schemes, it is possible to have a full-length codeword followed by a small codeword. However, in this case, a more balanced burst with two shorter codewords of approximately equal length is preferred. The OLT may direct the ONU to apply an appropriate FEC code for the end of a burst, including more than the last codeword of the burst.
[0079] Various example embodiments may be configured to implement a flexible US FEC scheme, wherein the OLT may control the FEC code rate used on a per-ONU basis, and for a given ONU, two or more FEC settings are used on an internal burst basis for two or more parts of a given data burst of the ONU. Various example embodiments may be configured to support the use of FEC settings, wherein a first FEC setting indicates a first code rate and a second FEC setting indicates a second code rate. For example, an upstream operation may start with the transmission of an ONU using a low-rate code with a higher error correction capability to accommodate the worst case. Based on an evaluation of the upstream channel, the OLT may selectively switch the ONU to a higher rate. In addition, a burst profile message may be used to convey the selection of a code on a per-burst basis, or even to signal mid-burst code switching to provide protection against, for example, stable transients and insufficient equalizer convergence, bit interleaving on / off, or for improving the efficiency of the final codeword. Various example embodiments may be configured to enhance or supplement a burst profile configuration message from the OLT to signal each ONU the selection of one or more FEC codes to be used within each burst. This may also include an indication of the exact position in the burst when the FEC code must be changed if necessary.
[0080] Figure 6 Depicted is an example of a data burst structure that may be used in a PON system. Figure 6 In the data burst structure 600, the preamble and delimiter are followed by the data. The data consists of different parts, and different FEC codes are applied in each part. For example, in the figure, the codeword of FEC 1 is used for the head of the data burst (first part), the codeword of FEC 2 is used for the body of the data burst (second part), and the codeword of FEC 3 is used at the tail of the data burst (third part). In general, a burst can consist of less than three parts (e.g., two parts or even a single part) or more than three parts, in which different FEC codes can be applied.
[0081] In order to make the ONU encode the burst in the above manner, multiple example embodiments may be applied. In at least some example embodiments, the OLT may convey an indication of the selected code or code setting and the desired burst structure of the number of codewords for each portion (or at least one portion). In at least some example embodiments, the number of codewords is indicated, and the code setting used is predetermined. In at least some example embodiments, the FEC setting is indicated for one portion, while the other portions have a predetermined FEC setting. In at least some example embodiments, the position (s) of (s) FEC setting is indicated. It should be understood that less or more and different types of information may be indicated.
[0082] In at least some example embodiments, the OLT communicates the details of the burst structure to the ONU using Burst_Profile Physical Layer Operation and Management (PLOAM) messages. Each burst description is assigned a unique index. Additional octets may be added to Figure 7 70 to capture the FEC settings in the burst portion. For example, assume that there are up to 16 possible FEC settings to choose from, and a 4-bit index can be used to select the FEC setting (it will be appreciated that fewer or more codewords can be supported, and smaller or larger bit indices can be used). This example focuses on a 3-part burst structure (although it will be appreciated that fewer or more data burst portions can be supported). In this example, the burst profile may include at least one of the following fields: (1) Indicates the FEC setting of the body ( Figure 6 The second part of the burst, FEC 2), is a 4-bit field in which the FEC setting is used except for the header of the burst (the first part) or the tail of the burst (the third part). (2) FEC setting for the header of the burst ( Figure 6 The first part of the burst is a 4-bit field indicating the number of FEC codewords for FEC 1 to be sent (0-15), and (4) the FEC setting for the end of the burst ( Figure 6 The third part of the burst, a 4-bit field indicating FEC 3), and (5) a 4-bit field indicating the number (0-15) of FEC 3 FEC code words to be sent, where the number of FEC code words can be counted from the back end of the burst.
[0083] In at least some example embodiments, the OLT may indicate the selected burst profile configuration at an index in a BWmap partition of a framing sublayer (FS) header portion of a downstream FS frame. Typically, for a given ONU, the selection of a burst profile will depend on other parameters in the BWmap for the ONU including a GrantSize field. The downstream FS frame format 800 is shown in FIG. Figure 8 By using the above-described enhanced burst profile PLOAM message to configure multiple unique burst profiles (i.e., with unique indexes) in the ONU, the OLT can then use the burst profiles in the BWmap to appropriately select the desired combination of FEC settings and corresponding durations for the ONU at any future time. In addition, this approach also allows the OLT to accurately control the desired combination of FEC settings and corresponding durations for each burst from the ONU.
[0084] It should be noted that the number of codewords used in each part will generally depend on the burst size (grant size). For very short bursts (shorter than the number of codewords assigned to the first part), it may contain only a single part (containing only the head of the burst with a reduced number of codewords, or the part with the highest / lowest code rate). Alternatively, these short bursts may contain two parts (header and tail, both of which may have a reduced number of codewords). Typically, the number of codewords in each part can be adjusted based on the grant size according to predefined rules. Alternatively, different profiles can be established to handle shorter bursts, and these may involve switching between only two types of FEC settings, or using only one FEC setting in a burst.
[0085] It should be appreciated that the various example embodiments discussed above may also be used in conjunction with rules for burst termination.
[0086] It will be appreciated that various other techniques may also be employed. For example, the OLT may specify the amount of shortening and puncturing required to construct each code from the mother code in the Burst_Profile PLOAM message, rather than selecting from an indexed code set or FEC setting. In addition, the size of the Burst Profile field in the BWmap partition may be increased beyond the currently provided 2 bits (see Figure 7 ). It is also possible to use different PLOAM messages (control messages) to signal the FEC settings instead of using the burst profile messages.
[0087] It will be appreciated that signaling using BW mapping may involve indicating a channel quality level to each ONU for each burst. Using the channel quality level and the actual burst length, it may then be automatically calculated at both the OLT and ONU how the data is grouped into codewords and which LDPC codes are used.
[0088] In at least some example embodiments, the different FEC codes are LDPC codes obtained by puncturing and shortening a single mother code.The transmitted FEC setting may be the amount of puncturing and / or shortening, or an index value indicating a predetermined amount of puncturing and shortening.
[0089] In at least some example embodiments, the FEC codes used in the burst profile and how the ONU is assigned to the burst profile can be modified by the FEC controller. For example, the FEC controller can modify the burst error performance of the ONU and thus modify the FEC settings. This can be an attempt based on error statistics (bit errors or codeword errors), or it can be more gradual (one step at a time), or even trial and error (if there is a significant error, then quickly return). The FEC controller can be inside the OLT or outside the OLT (and slower). The FEC settings can be selected based on observed error statistics or based on quality of service (QoS) requirements defined for the ONU or service container.
[0090] In at least some example embodiments, some FEC settings (or burst profiles) can be assigned to each ONU, while other FEC settings (burst profiles) can be broadcast settings, i.e., all ONUs can use them. For example, there may be a default FEC profile that is communicated in a broadcast manner. One use case is to recover the profile (minimum code rate throughout), and if the last few bursts are significant errors, the OLT can apply it to the ONU. Another use case is that the initial profile is used during or immediately after activation. This can also always use the minimum code rate. In at least some example embodiments, the FEC settings can be configured to indicate that the ONU is to do calculations (e.g., for the segmentation process and the selection of the codeword length for each segment).
[0091] In at least some example embodiments, dynamic intra-burst FEC switching may include determining the length of a segment and its FEC setting relative to the total length of the burst. This may be a rule-based approach. There is also the possibility of applying codes with unequal error protection, particularly where the beginning of a codeword is better protected than the "tail" of the same codeword. By segmenting the burst, it is also possible to determine the channel quality by monitoring the number of transmission errors per segment. This then also involves the size of each group of segments relative to the overall size of the burst. For example, if the first part of a data burst is more prone to errors, one option may be to use a higher performance FEC code and / or a longer FEC code to mitigate the effects of errors. Multiple FEC code families may also be supported, such as algebraic codes for short segments and iterative codes for other segments (e.g., for a transceiver that can support both ReedSolomon and LDPC codes). If a burst is too short to have three segments, it may be encoded by default according to the first and third segments and the associated error measurements may be tracked. If the burst is shorter, it may be encoded by default according to the first segment. It should be understood that at least some of this capability may also be provided by allowing one of the segment groups to have zero length.
[0092] In at least some example embodiments, the FEC settings and the process of segmenting the burst into codewords of specific lengths may be related. It should be noted that these may be different for each group of segments. Using the length and error profile for the burst, it is possible to provide an algorithm that uses these inputs to determine the length of each segment in the segment group (first, second, third) and its FEC parameters. This may involve additional shortening and puncturing beyond the basic code (e.g., rate 33 / 45, 40 / 45, etc.). In at least some example embodiments, the FEC settings may include rules for the length of each segment (group) of a data burst.
[0093] In at least some example embodiments, control of the internal burst FEC settings may be based on one or more messages that result in the setting or changing of a particular profile, adding a control field with a per-burst specification of the scheme to be used, sending settings per-group of segments per burst, etc., and various combinations thereof. In at least some example embodiments, the message used to control the internal burst FEC settings may include an indication of a position within a data burst at which the transmitter is to switch from using a first forward error correction setting to using a second forward error correction setting (e.g., where the position may be a bit position, a codeword boundary, etc.).
[0094] It should be understood that although embodiments are primarily presented in which the number of segments relative to a data burst matches the number of FEC settings specified in the FEC profile, in at least some example embodiments, the number of segments of a data burst and the number of FEC settings specified in the FEC profile may be different. For example, a FEC profile may be defined to apply a first FEC setting to a first segment, a second FEC setting to a second segment, and a third FEC setting to a third segment, and the FEC profile may still be applied to a data burst that includes three segments as well as data segments that include only two segments or even a single segment (e.g., for a shorter data burst that includes only a single segment, the first FEC setting of the FEC profile may be applied and the other two FEC settings will not be applied because the second and third segments are essentially empty). It should be understood that various other types of FEC profiles (including various other numbers of FEC settings specified for various data burst segments) may be used to support FEC for data bursts having various numbers of segments.
[0095] As indicated above, the LDPC (17280, 14592) code has been agreed for use in the G.hsp downlink. The code is based on the IEEE 802.3ca mother code with 384 bits of puncturing and no shortening. Based on the same mother code matrix, several shortening and puncturing schemes have been considered to improve the uplink transmission efficiency for short bursts. One such proposal focuses on improving the transmission efficiency of the last codeword in the burst while maintaining the same or better performance as the (17280, 14592) code. Based on the evaluation of the code performance of different shortenings and puncturing of the 802.3ca mother code, the various example embodiments presented herein can be configured to provide more general throughput and performance flexibility in the uplink direction.
[0096] Note that the main motivation for choosing a length of 17280 for downstream transmission is to ensure an integer number of LDPC codewords in a continuous mode frame with a duration of 125μs. This restriction does not apply in the upstream due to burst mode operation. A code length of 11520=45*256=2*17280 / 3 has been chosen for analysis because it provides good code rate flexibility on either side of the downstream LDPC (17280, 14592) code with a rate of 0.844. For length 11520, the lowest code rate is achieved when no parity columns are punctured; this gives a (11520, 8448) code with rate=33 / 45=0.733, and for convenience, this code is referred to as C1. To achieve the highest code rate, puncturing is limited to a maximum of 7 columns; this gives a (11520, 10240) code with rate=40 / 45=0.889, and for convenience, this code is referred to as C2.
[0097] Fig. 9 The hard decision performance of LDPC (11520, 8448) codes of length 11520 and 8448 information bits with a rate of 0.733 and the hard decision performance of LDPC (11520, 10240) code with a rate of 0.889 are depicted. Fig. 9 The performance information 900 shows the hard input BSC performance of the G.hsp downlink code and codes C1 and C2. Table 1 provides the code parameters and their BER performance and electrical coding gain (ECG).
[0098]
[0099] Table 1
[0100] The C1 (rate 0.733) code achieves 1E-12 at 1.85E-2 and can tolerate an electrical SNR 0.84dB lower than the default and results in 13% lower throughput compared to the default rate 0.844 code.
[0101] The C2 (rate 0.889) code achieves 1E-12 at 1.76E-3 and requires 2.08dB more electrical SNR than the default, has better BER performance and higher rate (throughput) than the RS(248,216) at rate 0.871, and provides 5% higher throughput than the default rate 0.844 code.
[0102] Together, these codes accommodate variations in electrical SNR approaching 3 dB; this typically corresponds to 2 dB to 3 dB of optical power. The code rate as a function of the total ECG relative to the default is Fig.10 is shown in .
[0103] Various example embodiments presented herein may be configured to provide a flexible FEC scheme for uplink data bursts.Various example embodiments may be configured to provide a flexible FEC scheme, where the FEC code may be adapted to trade off performance against throughput in the uplink.
[0104] Various example embodiments may be configured to provide tolerance to stable transients. Due to transients associated with laser activation and receiver stabilization, or due to insufficient convergence of the receiver equalizer, the first codeword or first few codewords of an upstream burst may experience a higher bit error rate than the remainder of the burst. In this case, the OLT may configure the first codeword or first few codewords of the upstream burst to operate at a lower rate of 0.73 to provide additional margin for these transients. For the remainder of the burst, operation may switch to a higher rate.
[0105] Various example embodiments may be configured to provide performance guarantees in the absence of bit interleaving. Bit interleaving may be necessary to mitigate the effects of correlated errors, especially for 50G uplinks. If the uplink does not employ bit interleaving or (partially) does not employ bit interleaving in bursts, a rate 0.73 code may provide an increased margin for correlated errors.
[0106] Various example embodiments may be configured to provide better efficiency for the last codeword in a burst. Excessively shortening the last codeword of a burst results in inefficient transmission. For a particular code rate, this inefficiency is higher for longer code lengths because the parity portion scales with length. The rate 0.889 code already provides good efficiency and avoids the need to switch to a specific short or medium codeword due to having only 5 columns of parity. For operation at a rate of 0.733, a specific scheme may use different short and medium code lengths to guarantee an output BER of 1E-12 at an input BER of 1.85E-2 or higher.
[0107] Various example embodiments may be configured to provide increased tolerance to ONU transmitter optics. Low-cost optics on ONU transmitters may exhibit high variability in transmit power. Rate 0.733 codes provide additional margin to accommodate such variations for ONUs operating close to budget limits.
[0108] Various example embodiments may be configured to provide improved US throughput for many ONUs. Many ONUs in a PON are likely to operate with significant margins relative to the loss budget. In the FEC code example considered, such ONUs may utilize the 5% higher throughput provided by the rate 0.889 code.
[0109] Various example embodiments may be configured to provide reduced aging margin. Typically, a significant aging margin must be provisioned to account for excess losses due to, for example, fiber repairs, etc. By using a code of 0.733 for the downgraded ONU rate, the aging margin may be reduced.
[0110] Various example embodiments can be configured to implement a flexible US FEC scheme, wherein the OLT can control the FEC code rate used on a per-ONU basis. Upstream operation can start with ONU transmission using a code of rate 0.73 to accommodate the worst case. Based on the evaluation of the upstream channel, the OLT can selectively switch the ONU to a higher rate. In addition, burst profile messages can be used to convey the selection of codes on a per-burst basis, or even signal mid-burst code switching to provide protection to prevent, for example, stable transients, bit interleaving on / off, or to improve the efficiency of the final codeword.
[0111] Various example embodiments may be configured to implement a flexible FEC scheme based on an evaluation of the performance of 11520 length codes based on the 802.3ca mother code. The performance of the 0.733 and 0.889 rates spans the 3dB electrical SNR range and provides flexibility between throughput and performance. The flexibility provided by these codes can be exploited in a variety of ways to improve the robustness or throughput of upstream transmissions.
[0112] It should be understood that although primarily presented herein with respect to example embodiments, in which support for FEC is provided within the context of communication of a particular type of data over a physical medium (i.e., PON), or adapted for use within the context of communication of data over various other types of physical mediums. For example, the various example embodiments presented herein may be adapted for use within the context of communication of data over various other types of wired mediums, such as other types of fiber optic networks (e.g., point-to-point fiber, etc.), Ethernet, DSL, cable (e.g., DOCSIS 3.1, DOCSIS 3.1FDX, etc.), power line communications (e.g., G.hn, etc.), etc., and various combinations thereof. For example, the various example embodiments presented herein may be used or adapted for use within the context of communication of data over various other types of wireless media, such as cellular (e.g., 4G, 4G LTE, 5G, etc.), WiFi, WiMAX, satellite, etc., and various combinations thereof. It should be understood that the various example embodiments presented herein may be used or adapted for use in the context of communication of data over various other types of physical mediums, interfaces, networks, etc., and various combinations thereof.
[0113] By controlling the FEC settings for the FEC of the communication channel, various example embodiments for supporting FEC on the communication channel can provide various advantages or potential advantages. For example, various example embodiments for supporting FEC on the communication channel can be configured to improve the throughput of the upstream transmission from each ONU that can support mid-burst CW switching. For example, various example embodiments for supporting FEC on the communication channel can be configured to improve the throughput of the upstream transmission from each ONU that can support mid-burst CW switching even when the PON has a mixture of ONUs that support mid-burst FEC switching and ONUs that do not support mid-burst switching (which can be referred to as "legacy" ONUs), the improved throughput experienced by the ONUs that support mid-burst switching can be improved by allowing more transmission time for the traditional ONUs. Various example embodiments for supporting FEC on the communication channel can provide various other advantages or potential advantages.
[0114] Fig.11 An example embodiment of a computer suitable for performing the various functions presented herein is depicted.
[0115] The computer 1100 includes a processor 1102 (e.g., a central processing unit (CPU), a processor, a processor having a processor core set, a processor core of a processor, etc.) and a memory 1104 (e.g., a random access memory, a read-only memory, etc.). The processor 1102 and the memory 1104 may be communicatively connected. In at least some example embodiments, the computer 1100 may include at least one processor and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to use the at least one processor to cause the computer to perform various functions presented herein.
[0116] The computer 1100 may also include a cooperating element 1105. The cooperating element 1105 may be a hardware device. The cooperating element 1105 may be a process that may be loaded into the memory 1104 and executed by the processor 1102 to implement the various functions presented herein (in which case, for example, the cooperating element 1105 (including associated data structures) may be stored in a non-transitory computer-readable storage medium, such as a storage device or other suitable type of storage element (e.g., a magnetic drive, an optical drive, etc.)).
[0117] The computer 1100 may also include one or more input / output devices 1106. The input / output devices 1106 may include one or more user input devices (e.g., keyboard, keypad, mouse, microphone, camera, etc.), user output devices (e.g., display, speaker, etc.), one or more network communication devices or elements (e.g., input ports, output ports, receivers, transmitters, transceivers, etc.), one or more storage devices (e.g., tape drive, floppy disk drive, hard disk drive, optical disk drive, etc.), etc., and various combinations thereof.
[0118] It should be understood that the computer 1100 may represent a general architecture and functionality suitable for implementing the functional elements described herein, portions of the functional elements described herein, etc., and various combinations thereof. For example, the computer 1100 may provide a general architecture and functionality suitable for implementing one or more elements presented herein, such as the OLT 110 or a portion thereof (e.g., the communication element 111, the control element 115, etc., and various combinations thereof), the ONU 120 or a portion thereof (e.g., the communication element 121, the control element 125, etc., and various combinations thereof), a transmitter or a portion thereof (e.g., an LDPC encoder, a SERDES transmitter, an encoder controller, etc., and various combinations thereof), a receiver or a portion thereof (e.g., a SERDES receiver, an LDPC decoder, a channel estimator, a decoder controller, etc., and various combinations thereof), etc., and various combinations thereof.
[0119] It should be understood that at least some of the functionality presented herein may be implemented in software (e.g., via implementing the software on one or more processors for execution on a general-purpose computer (e.g., via execution by one or more processors) to provide a special-purpose computer, etc.) and / or may be implemented in hardware (e.g., using a general-purpose computer, one or more application-specific integrated circuits and / or any other hardware equivalents).
[0120] It should be understood that at least some of the functions presented herein can be implemented in hardware, for example, as circuits that cooperate with a processor to perform various functions. Portions of the functions / elements described herein can be implemented as computer program products, wherein computer instructions, when processed by a computer, adjust the operation of the computer so that the methods and / or techniques described herein are invoked or otherwise provided. Instructions for invoking various methods can be stored in fixed or removable media (e.g., non-transient computer-readable media), transmitted via a data stream in a broadcast or other signal-bearing medium, and / or stored in a memory within a computing device that operates according to the instructions.
[0121] It should be understood that the term "or" as used herein refers to a non-exclusive "or" unless indicated otherwise (eg, using "or otherwise" or "or alternatively").
[0122] It will be appreciated that although various embodiments that incorporate the teachings presented herein have been shown and described in detail, those skilled in the art can readily devise many other varied embodiments that still incorporate these teachings.
Claims
1. An apparatus for a communication system, comprising: at least one processor; as well as at least one memory including computer program code; wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to at least: selecting a first forward error correction setting for encoding a first portion of a data burst transmitted upstream by a transmitter to the device, and selecting a second forward error correction setting for encoding a second portion of the data burst; sending a message from the apparatus to the transmitter, the message being configured to cause the transmitter to use the first forward error correction setting for encoding a first portion of the data burst and to use the second forward error correction setting for encoding a second portion of the data burst, wherein the second forward error correction setting is different from the first forward error correction setting; The message includes at least one of an indication of the first forward error correction setting or an indication of the second forward error correction setting.
2. The apparatus of claim 1, wherein the message comprises one or more of: at least one of an indication of a location of the first portion of the data burst or an indication of a location of the second portion of the data burst; at least one of an indication of a length of the first portion of the data burst or an indication of a length of the second portion of the data burst; or At least one of an indication of a number of codewords of the first portion of the data burst or an indication of a number of codewords of the second portion of the data burst.
3. The apparatus of claim 1, wherein the message is configured to enable the transmitter to calculate information indicative of at least one of a location of the first portion of the data burst or a location of the second portion of the data burst. The apparatus of claim 1 , wherein the message comprises forward error correction setting control information.
5. The apparatus of claim 4, wherein the message is included in a Framing Sublayer (FS) frame.
6. The apparatus of claim 1, wherein the message is a physical layer operations and management (PLOAM) message or an optical network unit (ONU) management and control interface (OMCI) message.
7. The apparatus of claim 1, wherein the first forward error correction setting and the second forward error correction setting are based on forward error correction parameters for a forward error correction mother code.
8. The apparatus according to claim 7, wherein the forward error correction parameter for the forward error correction mother code comprises at least one of a puncturing amount for the forward error correction mother code or a shortening amount for the forward error correction mother code.
9. The apparatus of claim 1, wherein at least one of the first forward error correction setting or the second forward error correction setting includes information for determining a new forward error correction code.
10. The apparatus of claim 1, wherein the message is configured to cause the transmitter to use a third forward error correction setting for encoding a third portion of the data burst.
11. The apparatus of claim 1 , wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: supporting communication of the first portion of the data burst encoded based on the first forward error correction setting; and Communication of the second portion of the data burst encoded based on the second forward error correction setting is supported.
12. The apparatus of claim 1, wherein the transmitter comprises an optical network unit (ONU) and an associated receiver comprises an optical line terminal (OLT), wherein the ONU and the OLT are associated with a passive optical network (PON).
13. A non-transitory computer readable medium comprising computer program code configured to cause an apparatus to at least: selecting a first forward error correction setting for encoding a first portion of a data burst transmitted upstream by a transmitter to a device, and selecting a second forward error correction setting for encoding a second portion of the data burst; sending a message from the apparatus to the transmitter, the message being configured to cause the transmitter to use the first forward error correction setting for encoding a first portion of the data burst and to use the second forward error correction setting for encoding a second portion of the data burst, wherein the second forward error correction setting is different from the first forward error correction setting; The message includes at least one of an indication of the first forward error correction setting or an indication of the second forward error correction setting.
14. A method for a communication system, comprising: selecting a first forward error correction setting for encoding a first portion of a data burst transmitted upstream by a transmitter to a device, and selecting a second forward error correction setting for encoding a second portion of the data burst; sending a message from the apparatus to the transmitter, the message being configured to cause the transmitter to use the first forward error correction setting for encoding a first portion of the data burst and to use the second forward error correction setting for encoding a second portion of the data burst, wherein the second forward error correction setting is different from the first forward error correction setting; The message includes at least one of an indication of the first forward error correction setting or an indication of the second forward error correction setting.
Citation Information
Patent Citations
Forward error correction control
US20220123863A1
Forward error correction control
US63092473P0
Data parsing and data transmission method and apparatus
WO2017113349A1
