Method and system for encoding short block length low density parity check (LDPC) codes

FIELD OF THE INVENTION

The present invention relates to communication systems, and more particularly to coded systems.

BACKGROUND OF THE INVENTION

Communication systems employ coding to ensure reliable communication across noisy communication channels. For example, in a wireless (or radio) system, such as a satellite network, noise sources abound, from geographic and environmental factors. These communication channels exhibit a fixed capacity that can be expressed in terms of bits per symbol at certain signal to noise ratio (SNR), defining a theoretical upper limit (known as the Shannon limit). As a result, coding design has aimed to achieve rates approaching this Shannon limit. This objective is particularly germane to bandwidth constrained satellite systems. One such class of codes that approach the Shannon limit is Low Density Parity Check (LDPC) codes.

Traditionally, LDPC codes have not been widely deployed because of a number of drawbacks. One drawback is that the LDPC encoding technique is highly complex. Encoding an LDPC code using its generator matrix would require storing a very large, non-sparse matrix. Additionally, LDPC codes require large blocks to be effective; consequently, even though parity check matrices of LDPC codes are sparse, storing these matrices is problematic.

From an implementation perspective, a number of challenges are confronted. For example, storage is an important reason why LDPC codes have not become widespread in practice. Length LDPC codes, thus, require greater storage space. Also, a key challenge in LDPC code implementation has been how to achieve the connection network between several processing engines (nodes) in the decoder. Further, the computational load in the decoding process, specifically the check node operations, poses a problem.

Therefore, there is a need for an LDPC communication system that employs simple encoding and decoding processes. There is also a need for using LDPC codes efficiently to support high data rates, without introducing greater complexity. There is also a need to improve performance of LDPC encoders and decoders. There is also a need to minimize storage requirements for implementing LDPC coding.

SUMMARY OF THE INVENTION

These and other needs are addressed by the present invention, wherein an approach for encoding Low Density Parity Check (LDPC) codes is provided. An encoder generates a LDPC code having an outer Bose Chaudhuri Hocquenghem (BCH) code according to one of Tables 2-8 for transmission as the LDPC coded signal. Each of the Tables 2-8 specifies the address of parity bit accumulators. Short LDPC codes are output by utilizing LDPC mother codes that are based on Tables 2-8. <i>k</i>_<i>ldpc</i> of the BCH encoded bits are preceded by <i>k</i>_<i>m</i><i> -k</i>_<i>ldpc</i> dummy zeros. The resulting <i>k</i>_<i>m</i> bits are systematically encoded to generate <i>n</i>_<i>m</i> bits. The first <i>k</i>_<i>m</i><i> -k</i>_<i>ldpc</i> dummy zeros are then deleted to yield the shortened code. For an LDPC code with code rate of 3/5 utilizing 8-PSK (Phase Shift Keying) modulation, an interleaver provides for interleaving bits of the output LDPC code by serially writing data associated with the LDPC code column-wise into a table and reading the data row-wise from right to left. The approach advantageously provides expedient encoding as well as decoding of LDPC codes, while minimizing storage and processing resources.

According to one aspect of an embodiment of the present invention, a method for supporting transmission of a Low Density Parity Check (LDPC) coded signal is disclosed. The method includes receiving information bits. The method also includes generating, based on the information bits, 16,000 Low Density Parity Check (LDPC) coded bits according a parity check matrix of short LDPC codes, wherein the parity check matrix ensures that information regarding partitioned groups of bit nodes and check nodes are always placed contiguously in Random Access Memory (RAM).

According to another aspect of an embodiment of the present invention, the LDPC codes are represented by signals that are modulated according to a signal constellation that includes one of 8-PSK (Phase Shift Keying), 16-QAM (Quadrature Amplitude Modulation), QPSK (Quadrature Phase Shift Keying), 16-APSK (Amplitude Phase Shift Keying) and 32-APSK.

According to yet another aspect of an embodiment of the present invention, the modulated LDPC coded signal is transmitted over a satellite link in support of a broadband satellite application.

Still other aspects, features, and advantages of the present invention are readily apparent from the following detailed description, simply by illustrating a number of particular embodiments and implementations, including the best mode contemplated for carrying out the present invention. The present invention is also capable of other and different embodiments, and its several details can be modified in various obvious respects, all without departing from the spirit and scope of the present invention. Accordingly, the drawing and description are to be regarded as illustrative in nature, and not as restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:

FIG. 1 is a diagram of communications system configured to utilize Low Density Parity Check (LDPC) codes, according to an embodiment of the present invention;

FIGs. 2A and 2B are diagrams of exemplary LDPC encoders deployed in the transmitter of FIG. 1;

FIGs. 2C and 2D are flowcharts of the encoding process of the LDPC encoder of FIG. 2B for generating short frame length LDPC codes, according to an embodiment of the present invention;

FIG. 3 is a diagram of an exemplary receiver in the system of FIG. 1;

FIG. 4 is a diagram of a sparse parity check matrix, in accordance with an embodiment of the present invention;

FIG. 5 is a diagram of a bipartite graph of an LDPC code of the matrix of FIG. 4;

FIG. 6 is a diagram of a sub-matrix of a sparse parity check matrix, wherein the sub-matrix contains parity check values restricted to the lower triangular region, according to an embodiment of the present invention;

FIG. 7 is a graph of performance of the LDPC codes at the various code rates and modulation schemes supported by the transmitter of FIG. 2B;

FIG. 8 is a graph of performance of the short LDPC codes at the various code rates supported by the transmitter of FIG. 2B; and

FIG. 9 is a diagram of a computer system that can perform the LDPC encoding process, in accordance with embodiments of the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENT

A system, method, and software for efficiently encoding short frame length Low Density Parity Check (LDPC) codes are described. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It is apparent, however, to one skilled in the art that the present invention may be practiced without these specific details or with an equivalent arrangement. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the present invention.

FIG. 1 is a diagram of a communications system configured to utilize Low Density Parity Check (LDPC) codes, according to an embodiment of the present invention. A digital communications system 100 includes a transmitter 101 that generates signal waveforms across a communication channel 103 to a receiver 105. In this discrete communications system 100, the transmitter 101 has a message source that produces a discrete set of possible messages; each of the possible messages has a corresponding signal waveform. These signal waveforms are attenuated, or otherwise altered, by communications channel 103. To combat the noise channel 103, LDPC codes are utilized.

By way of example, the channel 103 is a satellite link serving satellite terminals (e.g., Very Small Aperture Terminals (VSATs)) in support of broadband satellite applications. Such applications include satellite broadcasting and interactive services (and compliant with the Digital Video Broadcast (DVB) - S2 standard). The Digital Video Broadcasting via Satellite (DVB-S) standard has been widely adopted worldwide to provide, for instance, digital satellite television programming.

The LDPC codes that are generated by the transmitter 101 enable high speed implementation without incurring any performance loss. These structured LDPC codes output from the transmitter 101 avoid assignment of a small number of check nodes to the bit nodes alreadyvulnerable to channel errors by virtue of the modulation scheme (e.g., 8-PSK).

Such LDPC codes have a parallelizable decoding algorithm (unlike turbo codes), which advantageously involves simple operations such as addition, comparison and table look-up. Moreover, carefully designed LDPC codes do not exhibit any sign of error floor.

According to one embodiment of the present invention, the transmitter 101 generates, using a relatively simple encoding technique, LDPC codes based on parity check matrices (which facilitate efficient memory access during decoding) to communicate with the receiver 105. The transmitter 101 employs LDPC codes that can outperform concatenated turbo+RS (Reed-Solomon) codes, provided the block length is sufficiently large.

FIGs. 2A and 2B are diagrams of exemplary LDPC encoders deployed in the transmitter of FIG. 1. As seen in FIG. 2A, a transmitter 200 is equipped with an LDPC encoder 203 that accepts input from an information source 201 and outputs coded stream of higher redundancy suitable for error correction processing at the receiver 105. The information source 201 generates k signals from a discrete alphabet, X. LDPC codes are specified with parity check matrices. On the other hand, encoding LDPC codes require, in general, specifying the generator matrices. Even though it is possible to obtain generator matrices from parity check matrices using Gaussian elimination, the resulting matrix is no longer sparse and storing a large generator matrix can be complex.

The encoder 203 generates signals from alphabet <i>Y</i> to a modulator 205 using a simple encoding technique that makes use of only the parity check matrix by imposing structure onto the parity check matrix. Specifically, a restriction is placed on the parity check matrix by constraining certain portion of the matrix to be triangular. The construction of such a parity check matrix is described more fully below in FIG. 6. Such a restriction results in negligible performance loss, and therefore, constitutes an attractive trade-off.

The modulator 205 maps the encoded messages from encoder 203 to signal waveforms that are transmitted to a transmit antenna 207, which emits these waveforms over the communication channel 103. Accordingly, the encoded messages are modulated and distributed to a transmit antenna 207. The transmissions from the transmit antenna 207 propagate to a receiver (shown in FIG. 3), as discussed below.

FIG. 2B shows an LDPC encoder utilized with a Bose Chaudhuri Hocquenghem (BCH) encoder and a cyclic redundancy check (CRC) encoder, according to one embodiment of the present invention. Under this scenario, the codes generated by the LDPC encoder 203, along with the CRC encoder 209 and the BCH encoder 211, have a concatenated outer BCH code and inner low density parity check (LDPC) code. Furthermore, error detection is achieved using cyclic redundancy check (CRC) codes. The CRC encoder 209, in an exemplary embodiment, encodes using an 8-bit CRC code with generator polynomial (x⁵+x⁴+x³+x²+1)(x²+x+1)(x+1). The CRC code is output to the BCH encoder 211.

The LDPC encoder 203 systematically encodes an information block of size <i>k</i>_<i>ldpc</i><i> , i=</i>(<i>i</i>₀<i>,i</i>₁<i>,...,i</i>_{<i>k</i><sub2><i>ldpc</i></sub2>}_-1) onto a codeword of size <i>n</i>_<i>ldpc</i>, <i>c</i> = (<i>i</i>₀<i>,i</i>₁,..., <i>i</i>_{<i>k</i><sub2><i>ldpc</i></sub2>}_-1, <i>p</i>₀_<i>,</i><i>p</i>₁<i>,...p</i>_{<i>n</i><sub2><i>ldpc</i></sub2>}_-_{<i>k</i><sub2><i>ldpc</i></sub2>}_-1) The transmission of the codeword starts in the given order from <i>i</i>₀ and ends with <i>p</i>_{<i>n</i><sub2><i>ldpc</i></sub2>}-_{<i>k</i><sub2><i>ldpc</i></sub2>}_-1. LDPC code parameters (<i>n</i>_<i>ldpc</i><i>, k</i>_<i>ldpc</i>) are given in Table 1 below. <tables id="tabl0001" num="0001"><table frame="all"><title>Table 1</title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52.50mm" /><colspec colnum="2" colname="col2" colwidth="52.50mm" /><colspec colnum="3" colname="col3" colwidth="52.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col3" align="center"><b>LDPC Code Parameters</b> (<i>n</i>_<i>ldpc</i> , <i>k</i>_<i>ldpc</i>)</entry></row><row><entry namest="col1" nameend="col1" align="center"><b>Code Rate</b></entry><entry namest="col2" nameend="col2" align="center"><b>LDPC Uncoded Block Length</b><i>k</i>_<i>ldpc</i></entry><entry namest="col3" nameend="col3" align="center"><b>LDPC Coded Block Length</b><i>n</i>_<i>ldpc</i></entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="center">1/2</entry><entry namest="col2" nameend="col2" align="center">32400</entry><entry namest="col3" nameend="col3" align="center">64800</entry></row><row><entry namest="col1" nameend="col1" align="center">2/3</entry><entry namest="col2" nameend="col2" align="center">43200</entry><entry namest="col3" nameend="col3" align="center">64800</entry></row><row><entry namest="col1" nameend="col1" align="center">3/4</entry><entry namest="col2" nameend="col2" align="center">48600</entry><entry namest="col3" nameend="col3" align="center">64800</entry></row><row><entry namest="col1" nameend="col1" align="center">4/5</entry><entry namest="col2" nameend="col2" align="center">51840</entry><entry namest="col3" nameend="col3" align="center">64800</entry></row><row><entry namest="col1" nameend="col1" align="center">5/6</entry><entry namest="col2" nameend="col2" align="center">54000</entry><entry namest="col3" nameend="col3" align="center">64800</entry></row><row><entry namest="col1" nameend="col1" align="center">3/5</entry><entry namest="col2" nameend="col2" align="center">38880</entry><entry namest="col3" nameend="col3" align="center">64800</entry></row><row rowsep="1"><entry namest="col1" nameend="col1" align="center">8/9</entry><entry namest="col2" nameend="col2" align="center">57600</entry><entry namest="col3" nameend="col3" align="center">64800</entry></row></tbody></tgroup></table></tables>

The task of the LDPC encoder 203 is to determine <i>n</i>_<i>ldpc</i><i> - k</i>_<i>ldpc</i> parity bits (<i>p</i>₀<i>, p</i>₁<i>,..., p</i>_{<i>n</i><sub2><i>ldpc</i></sub2>} - _{<i>k</i><sub2><i>ldpc</i></sub2>}_-1) for every block of <i>k</i>_<i>ldpc</i> information bits, (<i>i</i>₀,<i>i</i>₁,...,<i>i</i>_{<i>k</i><sub2><i>ldpc</i></sub2>}_-1) . The procedure is as follows. First, the parity bits are initialized; <i>p</i>₀ = <i>p</i>₁ = <i>p</i>₂ = ... = <i>p</i>_{<i>n</i><sub2><i>ldpc</i></sub2>}_-_{<i>k</i><sub2><i>ldpc</i></sub2>}_-1 = 0 . The first information bit, <i>i</i>₀ , are accumulated at parity bit addresses specified in the first row of Tables 2 - 8. For example, for rate 2/3 (Table 4), the following results:<maths id="math0001" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>0</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>0</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>0</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0001.tif" /></maths><maths id="math0002" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>10491</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>10491</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>0</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0002.tif" /></maths><maths id="math0003" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>16043</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>16043</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>0</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0003.tif" /></maths><maths id="math0004" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>506</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>506</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>0</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0004.tif" /></maths><maths id="math0005" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>12826</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>12826</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>0</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0005.tif" /></maths><maths id="math0006" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>8065</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>8065</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>0</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0006.tif" /></maths><maths id="math0007" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>8226</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>8226</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>0</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0007.tif" /></maths><maths id="math0008" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>2767</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>2767</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>0</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0008.tif" /></maths><maths id="math0009" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>240</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>240</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>0</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0009.tif" /></maths><maths id="math0010" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>18673</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>18673</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>0</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0010.tif" /></maths><maths id="math0011" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>9279</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>9279</mtext></mrow></msub><mtext> ⊕</mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>0</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0011.tif" /></maths><maths id="math0012" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>10579</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>10579</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>0</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0012.tif" /></maths><maths id="math0013" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>20928</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>20928</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>0</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0013.tif" /></maths><maths id="math0014" num=""><math display="block"><mrow><mtext>(All additions are in GF(2)).</mtext></mrow></math><img file="EP1513258A2_D0014.tif" /></maths>

Then, for the next 359 information bits, <i>i</i>_<i>m</i>,<i>m</i> = 1,2,...,359 , these bits are accumulated at parity bit addresses {<i>x</i> + <i>m</i> mod 360 × <i>q</i>} mod(<i>n</i>_<i>ldpc</i><i> - k</i>_<i>ldpc</i>) <i>,</i> where <i>x</i> denotes the address of the parity bit accumulator corresponding to the first bit <i>i</i>₀ , and <i>q</i> is a code rate dependent constant specified in Table 9. Continuing with the example, <i>q</i> = 60 for rate 2/3. By way of example, for information bit <i>i</i>₁ , the following operations are performed:<maths id="math0015" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>60</mtext></mrow></msub><mtext></mtext><msub><mrow><mtext mathvariant="italic">= p</mtext></mrow><mrow><mtext>60</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>1</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0015.tif" /></maths><maths id="math0016" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>10551</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>10551</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>1</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0016.tif" /></maths><maths id="math0017" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>16103</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>16103</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>1</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0017.tif" /></maths><maths id="math0018" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>566</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>566</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>1</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0018.tif" /></maths><maths id="math0019" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>12886</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>12886</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>1</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0019.tif" /></maths><maths id="math0020" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>8125</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>8125</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>1</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0020.tif" /></maths><maths id="math0021" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>8286</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>8286</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>1</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0021.tif" /></maths><maths id="math0022" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>2827</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>2827</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>1</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0022.tif" /></maths><maths id="math0023" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>300</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>300</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>1</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0023.tif" /></maths><maths id="math0024" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>18733</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>18733</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>1</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0024.tif" /></maths><maths id="math0025" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>9339</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>9339</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>1</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0025.tif" /></maths><maths id="math0026" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>10639</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>10639</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>1</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0026.tif" /></maths><maths id="math0027" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>20988</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>20968</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>1</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0027.tif" /></maths>

For the 361^st information bit <i>i</i>₃₆₀ , the addresses of the parity bit accumulators are given in the second row of the Tables 2 - 8. In a similar manner the addresses of the parity bit accumulators for the following 359 information bits <i>i</i>_<i>m</i><i>, m</i> = 361,362,...,719 are obtained using the formula {<i>x</i> + <i>m</i> mod 360 × <i>q</i>} <i>mod(n</i>_<i>ldpc</i><i> - k</i>_<i>ldpc</i>), where <i>x</i> denotes the address of the parity bit accumulator corresponding to the information bit <i>i</i>₃₆₀, i.e., the entries in the second row of the Tables 2 - 8. In a similar manner, for every group of 360 new information bits, a new row from Tables 2 - 8 are used to find the addresses of the parity bit accumulators.

[36] Addresses of parity bit accumulators are given in Tables 2 - 8. <tables id="tabl0002" num="0002"><img file="EP1513258A2_D0028.tif" /></tables><tables id="tabl0003" num="0003"><img file="EP1513258A2_D0029.tif" /></tables><tables id="tabl0004" num="0004"><img file="EP1513258A2_D0030.tif" /></tables><tables id="tabl0005" num="0005"><img file="EP1513258A2_D0031.tif" /></tables><tables id="tabl0006" num="0006"><img file="EP1513258A2_D0032.tif" /></tables><tables id="tabl0007" num="0007"><img file="EP1513258A2_D0033.tif" /></tables><tables id="tabl0008" num="0008"><img file="EP1513258A2_D0034.tif" /></tables>

After all of the information bits are exhausted, the final parity bits are obtained as follows. First, the following operations are performed, starting with <i>i</i> = 1<maths id="math0028" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext mathvariant="italic">i</mtext></mrow></msub><mtext> = </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext mathvariant="italic">i</mtext></mrow></msub><mtext> ⊕ </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext mathvariant="italic">i</mtext><mtext>-1</mtext></mrow></msub><mtext>, </mtext><mtext mathvariant="italic">i</mtext><mtext> = 1,2,..., </mtext><msub><mrow><mtext mathvariant="italic">n</mtext></mrow><mrow><mtext mathvariant="italic">ldpc</mtext></mrow></msub><mtext> - </mtext><msub><mrow><mtext mathvariant="italic">k</mtext></mrow><mrow><mtext mathvariant="italic">ldpc</mtext></mrow></msub><mtext> - 1.</mtext></mrow></math><img file="EP1513258A2_D0035.tif" /></maths> Final content of <i>p</i>_<i>i</i><i> , i</i> = 0,1,.., <i>n</i>_<i>ldpc</i><i> - k</i>_<i>ldpc</i> -1 is equal to the parity bit <i>p</i>_<i>i</i><i> .</i><tables id="tabl0009" num="0009"><table frame="all"><title>Table 9</title><tgroup cols="2" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="78.75mm" /><colspec colnum="2" colname="col2" colwidth="78.75mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center"><b>Code Rate</b></entry><entry namest="col2" nameend="col2" align="center"><b><i>q</i></b></entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="center">2/3</entry><entry namest="col2" nameend="col2" align="center">60</entry></row><row><entry namest="col1" nameend="col1" align="center">5/6</entry><entry namest="col2" nameend="col2" align="center">30</entry></row><row><entry namest="col1" nameend="col1" align="center">1/2</entry><entry namest="col2" nameend="col2" align="center">90</entry></row><row><entry namest="col1" nameend="col1" align="center">3/4</entry><entry namest="col2" nameend="col2" align="center">45</entry></row><row><entry namest="col1" nameend="col1" align="center">4/5</entry><entry namest="col2" nameend="col2" align="center">36</entry></row><row><entry namest="col1" nameend="col1" align="center">3/5</entry><entry namest="col2" nameend="col2" align="center">72</entry></row><row rowsep="1"><entry namest="col1" nameend="col1" align="center">8/9</entry><entry namest="col2" nameend="col2" align="center">20</entry></row></tbody></tgroup></table></tables>

The generator polynomial of the <i>t</i> error correcting BCH encoder 211 is obtained by multiplying the first t polynomials in the following list of Table 10: <tables id="tabl0010" num="0010"><table frame="all"><title>Table 10</title><tgroup cols="2" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="78.75mm" /><colspec colnum="2" colname="col2" colwidth="78.75mm" /><tbody valign="top"><row><entry namest="col1" nameend="col1" align="center">g₁(x)</entry><entry namest="col2" nameend="col2" align="left">1+x²+x³+x⁵+x¹⁶</entry></row><row><entry namest="col1" nameend="col1" align="center">g₂(x)</entry><entry namest="col2" nameend="col2" align="left">1+x+x⁴+x⁵+x⁶+x⁸+x¹⁶</entry></row><row><entry namest="col1" nameend="col1" align="center">g₃(x)</entry><entry namest="col2" nameend="col2" align="left">1+x²+x³+x⁴+x⁵+x⁷+x⁸+x⁹+x¹⁰+x¹¹+x¹⁶</entry></row><row><entry namest="col1" nameend="col1" align="center">g₄(x)</entry><entry namest="col2" nameend="col2" align="left">1+x²+x⁴+x⁶+x⁹+x¹¹+x¹²+x¹⁴+x¹⁶</entry></row><row><entry namest="col1" nameend="col1" align="center">g₅(x)</entry><entry namest="col2" nameend="col2" align="left">1+x+x²+x³+x⁵+x⁸+x⁹+x¹⁰+x¹¹+x¹²+x¹⁶</entry></row><row><entry namest="col1" nameend="col1" align="center">g₆(x)</entry><entry namest="col2" nameend="col2" align="left">1+x²+x⁴+x⁵+x⁷+x⁸+x⁹+x¹⁰+x¹²+x¹³+x¹⁴+x¹⁵+x¹⁶</entry></row><row><entry namest="col1" nameend="col1" align="center">g₇(x)</entry><entry namest="col2" nameend="col2" align="left">1+x²+x⁵+x⁶+x⁸+x⁹+x¹⁰+x¹¹+x¹³+x¹⁵+x¹⁶</entry></row><row><entry namest="col1" nameend="col1" align="center">g₈(x)</entry><entry namest="col2" nameend="col2" align="left">1+x+x²+x⁵+x⁶+x⁸+x⁹+x¹²+x¹³+x¹⁴+x¹⁶</entry></row><row><entry namest="col1" nameend="col1" align="center">g₉(x)</entry><entry namest="col2" nameend="col2" align="left">1+x⁵+x⁷+x⁹+x¹⁰+x¹¹+x¹⁶</entry></row><row><entry namest="col1" nameend="col1" align="center">g₁₀(x)</entry><entry namest="col2" nameend="col2" align="left">1+x+x²+x⁵+x⁷+x⁸+x¹⁰+x¹²+x¹³+x¹⁴+x¹⁶</entry></row><row><entry namest="col1" nameend="col1" align="center">g₁₁(x)</entry><entry namest="col2" nameend="col2" align="left">1+x²+x³+x⁵+x⁹+x¹¹+x¹²+x¹³+x¹⁶</entry></row><row rowsep="1"><entry namest="col1" nameend="col1" align="center">g₁₂(x)</entry><entry namest="col2" nameend="col2" align="left">1+x+x⁵+x⁶+x⁷+x⁹+x ¹¹+x¹²+x¹⁶</entry></row></tbody></tgroup></table></tables>

BCH encoding of information bits <i><b>m</b> =</i> (<i>m</i>_{<i>k</i><sub2><i>bch</i></sub2>}_-1, <i>m</i>_{<i>k</i><sub2><i>bch</i></sub2>}_-2,..., <i>m</i>₁<i>, m</i>₀ ) onto a codeword <i>c</i>=(m_{<i>k</i><sub2><i>bch</i></sub2>}_-1, <i>m</i>_{<i>k</i><sub2><i>bch</i></sub2>}_-2,...,<i>m</i>₁, <i>m</i>₀,<i>d</i>_{<i>n</i><sub2><i>bch</i></sub2>}_-_{<i>k</i><sub2><i>bch</i></sub2>}_-1,<i>d</i>_{<i>n</i><sub2><i>bch</i></sub2>}_-_{<i>k</i><sub2><i>bch</i></sub2>}_-2,...,<i>d</i>₁,<i>d</i>₀)is achieved as follows. The message polynomial <i>m</i>(<i>x</i>) = <i>m</i>_{<i>k</i><sub2><i>bch</i></sub2>}_-1<i>x</i>^{<i>k</i><sub2><i>bch</i></sub2>-1} + <i>m</i>_{<i>k</i><sub2><i>bch</i></sub2>}_-2<i>x</i>^{<i>k</i><sub2><i>bch</i></sub2>-2} +...+ <i>m</i>₁<i>x</i> + <i>m</i>₀ is multiplied by x^{<i>n</i><sub2><i>bch</i></sub2> -<i>k</i><sub2><i>bch</i></sub2>}. Next, <i>x</i>^{<i>n</i><sub2><i>bch</i></sub2><i>-k</i><sub2><i>bch</i></sub2>}<i> m</i>(<i>x</i>) divided by <i>g</i>(<i>x</i>). With <i>d</i>(<i>x</i>) = <i>d</i>_{<i>n</i><sub2><i>bch</i></sub2><i>-k</i><sub2><i>bch</i></sub2>}_-1<i>x</i>^{<i>n</i><sub2><i>bch</i></sub2><i>-k</i><sub2><i>bch</i></sub2>-1} +... <i>+ d</i>₁<i>x</i> + <i>d</i>₀ as the remainder, the codeword polynomial is set as follows: <i>c</i>(<i>x</i>) = <i>x</i>^{<i>n</i><sub2><i>bch</i></sub2><i>-k</i><sub2><i>bch</i></sub2>}<i>m</i>(<i>x</i>)+<i>d</i>(<i>x</i>).

As seen in FIG. 2B, the LDPC encoder 203 outputs to a bit interleaver 213. By way of example, 8-PSK, 16-APSK, and 32-APSK modulation formats are utilized. Data is serially written into the interleaver column-wise (from the top to the bottom), and serially read out row-wise (from the left to the right). However, in the case of code rate 3/5 with 8-PSK, it has been determined that reading the data out from the right to the left, instead of left to right, yields better performance (as illustrated in FIG. 7).

The configuration of the block interleaver for each modulation format is specified in Table 11. <tables id="tabl0011" num="0011"><table frame="all"><title>Table 11</title><tgroup cols="4" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="39.37mm" /><colspec colnum="2" colname="col2" colwidth="39.37mm" /><colspec colnum="3" colname="col3" colwidth="39.37mm" /><colspec colnum="4" colname="col4" colwidth="39.37mm" /><thead valign="top"><row><entry namest="col1" nameend="col4" align="center"><b>Bit Interleaver Structure</b></entry></row><row><entry namest="col1" nameend="col1" align="left">Modulation</entry><entry namest="col2" nameend="col2" align="left">Rows (for <i>n</i>_<i>ldpc</i> =64800)</entry><entry namest="col3" nameend="col3" align="left">Rows (for <i>n</i>_<i>ldpc</i> =16200)</entry><entry namest="col4" nameend="col4" align="left">Columns</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">8-PSK</entry><entry namest="col2" nameend="col2" align="left">21600</entry><entry namest="col3" nameend="col3" align="left">5400</entry><entry namest="col4" nameend="col4" align="left">3</entry></row><row><entry namest="col1" nameend="col1" align="left">16-APSK</entry><entry namest="col2" nameend="col2" align="left">16200</entry><entry namest="col3" nameend="col3" align="left">4050</entry><entry namest="col4" nameend="col4" align="left">4</entry></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">32-APSK</entry><entry namest="col2" nameend="col2" align="left">12960</entry><entry namest="col3" nameend="col3" align="left">3240</entry><entry namest="col4" nameend="col4" align="left">5</entry></row></tbody></tgroup></table></tables>

FIGs. 2C and 2D are flowcharts of the encoding process of the LDPC encoder of FIG. 2B for generating short frame length LDPC codes, according to an embodiment of the present invention. In step 211, information bits are received and processed to the chain of encoders 209, 211, and 203. Consequently, the LDPC encoder 203 generates LDPC codes with outer BCH codes based on the received information bits, as in step 223. The codes also contain the CRC code. In step 225, the coded bits are altered by the bit interleaver 213, as described above. Next, the LDPC codes are represented by signals that are modulated, per step 227, for transmission over the channel 103, which in an exemplary embodiment, is a satellite link to one or more satellite terminals (step 229).

As discussed, <i>k</i>_<i>ldpc</i> bits are systematically encoded to generate <i>n</i>_<i>ldpc</i> bits. According to one embodiment of the present invention, <i>n</i>_<i>ldpc</i> is 16200 bits, which is a short block length. Given the relatively short length of such codes, LDPC codes having approximate lengths of 16200 bits or less are deemed "short" block length codes.

In accordance with an embodiment of the present invention, short blocks codes are generated by shortening versions of slightly longer (<i>k</i>_<i>m</i><i>, n</i>_<i>m</i>) "mother" codes of block size <i>n</i>_<i>m</i> &gt; 16200 . As shown in FIG. 2D, <i>k</i>_<i>ldpc</i> of the BCH encoded bits are preceded by <i>k</i>_<i>m</i><i>-k</i>_<i>ldpc</i> dummy zeros (per step 251). The resulting <i>k</i>_<i>m</i> bits are systematically encoded to generate <i>n</i>_<i>m</i> bits, as in step 253. The first <i>k</i>_<i>m</i><i> -k</i>_<i>ldpc</i> dummy zeros are then deleted, as in step 255, and the resulting <i>n</i>_<i>ldpc</i> =16200 bits will be transmitted (step 257). It is noted that <i>k</i>_<i>m</i><i> - k</i>_<i>ldp</i><i> = n</i>_<i>m</i><i> - n</i>_<i>ldpc</i><i> .</i>

The parameters of short frame length codes are provided in Table 12 as follows. <tables id="tabl0012" num="0012"><table frame="all"><title>Table 12</title><tgroup cols="7" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="22.50mm" /><colspec colnum="2" colname="col2" colwidth="22.50mm" /><colspec colnum="3" colname="col3" colwidth="22.50mm" /><colspec colnum="4" colname="col4" colwidth="22.50mm" /><colspec colnum="5" colname="col5" colwidth="22.50mm" /><colspec colnum="6" colname="col6" colwidth="22.50mm" /><colspec colnum="7" colname="col7" colwidth="22.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center"><b>Mother Code Rate <i>k</i></b>_{<b><i>m</i></b>}<b>/<i>n</i></b>_{<b><i>m</i></b>}</entry><entry namest="col2" nameend="col2" align="center"><b><i>k</i></b>_{<b><i>ldpc</i></b>}</entry><entry namest="col3" nameend="col3" align="center"><b><i>k</i></b>_{<b><i>m</i></b>}</entry><entry namest="col4" nameend="col4" align="center"><b><i>n</i></b>_{<b><i>m</i></b>}</entry><entry namest="col5" nameend="col5" align="center"><b><i>k</i></b>_{<b><i>bch</i></b>}</entry><entry namest="col6" nameend="col6" align="center"><b>BCH Correction (bits)</b></entry><entry namest="col7" nameend="col7" align="center"><b>Effective Rate <i>k</i></b>_{<b><i>bch</i></b>}<b>/16200</b></entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="center">1/2</entry><entry namest="col2" nameend="col2" align="center">7200</entry><entry namest="col3" nameend="col3" align="center">9000</entry><entry namest="col4" nameend="col4" align="center">18000</entry><entry namest="col5" nameend="col5" align="center">7032</entry><entry namest="col6" nameend="col6" align="center">12</entry><entry namest="col7" nameend="col7" align="char" char=".">0.434</entry></row><row><entry namest="col1" nameend="col1" align="center">3/5</entry><entry namest="col2" nameend="col2" align="center">9720</entry><entry namest="col3" nameend="col3" align="center">9720</entry><entry namest="col4" nameend="col4" align="center">16200</entry><entry namest="col5" nameend="col5" align="center">9552</entry><entry namest="col6" nameend="col6" align="center">12</entry><entry namest="col7" nameend="col7" align="char" char=".">0.589</entry></row><row><entry namest="col1" nameend="col1" align="center">2/3</entry><entry namest="col2" nameend="col2" align="center">10800</entry><entry namest="col3" nameend="col3" align="center">10800</entry><entry namest="col4" nameend="col4" align="center">16200</entry><entry namest="col5" nameend="col5" align="center">10632</entry><entry namest="col6" nameend="col6" align="center">12</entry><entry namest="col7" nameend="col7" align="char" char=".">0.656</entry></row><row><entry namest="col1" nameend="col1" align="center">3/4</entry><entry namest="col2" nameend="col2" align="center">11880</entry><entry namest="col3" nameend="col3" align="center">12960</entry><entry namest="col4" nameend="col4" align="center">17280</entry><entry namest="col5" nameend="col5" align="center">11712</entry><entry namest="col6" nameend="col6" align="center">12</entry><entry namest="col7" nameend="col7" align="char" char=".">0.722</entry></row><row><entry namest="col1" nameend="col1" align="center">4/5</entry><entry namest="col2" nameend="col2" align="center">12600</entry><entry namest="col3" nameend="col3" align="center">14400</entry><entry namest="col4" nameend="col4" align="center">18000</entry><entry namest="col5" nameend="col5" align="center">12432</entry><entry namest="col6" nameend="col6" align="center">12</entry><entry namest="col7" nameend="col7" align="char" char=".">0.767</entry></row><row><entry namest="col1" nameend="col1" align="center">5/6</entry><entry namest="col2" nameend="col2" align="center">13320</entry><entry namest="col3" nameend="col3" align="center">14400</entry><entry namest="col4" nameend="col4" align="center">17280</entry><entry namest="col5" nameend="col5" align="center">13152</entry><entry namest="col6" nameend="col6" align="center">12</entry><entry namest="col7" nameend="col7" align="char" char=".">0.811</entry></row><row rowsep="1"><entry namest="col1" nameend="col1" align="center">8/9</entry><entry namest="col2" nameend="col2" align="center">14400</entry><entry namest="col3" nameend="col3" align="center">14400</entry><entry namest="col4" nameend="col4" align="center">16200</entry><entry namest="col5" nameend="col5" align="center">14232</entry><entry namest="col6" nameend="col6" align="center">12</entry><entry namest="col7" nameend="col7" align="char" char=".">0.878</entry></row></tbody></tgroup></table></tables>

Simulations of the performance of these codes were conducted, as shown in FIG. 8.

Tables 13-15 provide other exemplary code rates, 1/3, 1/5 and 2/5 for <i>n</i>_<i>ldpc</i> of 16200 bits: <tables id="tabl0013" num="0013"><img file="EP1513258A2_D0036.tif" /></tables><tables id="tabl0014" num="0014"><img file="EP1513258A2_D0037.tif" /></tables><tables id="tabl0015" num="0015"><img file="EP1513258A2_D0038.tif" /></tables>

The above approach to designing LDPC codes, as provided in Tables 2-8 and 13-15, advantageously permits storage and retrieval of relevant information regarding partitioned groups of bit nodes and check nodes to be always placed in contiguously memory locations within memory (e.g., Random Access Memory (RAM)). Further, this enables use of a single RAM bank, thereby minimizing size of the integrated circuit. As mentioned, the above LDPC codes, in an exemplary embodiment, can be used to variety of digital video applications, such as MPEG (Motion Pictures Expert Group) packet transmission.

FIG. 3 is a diagram of an exemplary receiver in the system of FIG. 1. At the receiving side, a receiver 300 includes a demodulator 301 that performs demodulation of received signals from transmitter 200. These signals are received at a receive antenna 303 for demodulation. After demodulation, the received signals are forwarded to a decoder 305, which attempts to reconstruct the original source messages by generating messages, <i>X</i>', in conjunction with a bit metric generator 307. The bit metric generator 307 may exchange information with the decoder 305 back and forth (iteratively) during the decoding process. These decoding approaches are more fully described in co-pending application, entitled "Method and System for Routing in Low Density Parity Check (LDPC) Decoders," filed July 3, 2003 (Serial No. 10/613,824; Attorney Docket PD-203009), which is incorporated herein in its entirety. To appreciate the advantages offered by the present invention, it is instructive to examine how LDPC codes are generated, as discussed in FIG. 4.

FIG. 4 is a diagram of a sparse parity check matrix, in accordance with an embodiment of the present invention. LDPC codes are long, linear block codes with sparse parity check matrix <i>H</i>₍_<i>n</i>_-_<i>k</i>₎_<i>xn</i>. Typically the block length, <i>n</i>, ranges from thousands to tens of thousands of bits. For example, a parity check matrix for an LDPC code of length <i>n</i>=8 and rate ½ is shown in FIG. 4. The same code can be equivalently represented by the bipartite graph, per FIG. 5.

FIG. 5 is a diagram of a bipartite graph of an LDPC code of the matrix of FIG. 4. Parity check equations imply that for each check node, the sum (over GF (Galois Field)(2)) of all adjacent bit nodes is equal to zero. As seen in the figure, bit nodes occupy the left side of the graph and are associated with one or more check nodes, according to a predetermined relationship. For example, corresponding to check node m₁, the following expression exists <i>n</i>₁ + <i>n</i>₄ + <i>n</i>₅ + <i>n</i>₈ = 0 with respect to the bit nodes.

Returning the receiver 303, the LDPC decoder 305 is considered a message passing decoder, whereby the decoder 305 aims to find the values of bit nodes. To accomplish this task, bit nodes and check nodes iteratively communicate with each other. The nature of this communication is described below.

From check nodes to bit nodes, each check node provides to an adjacent bit node an estimate ("opinion") regarding the value of that bit node based on the information coming from other adjacent bit nodes. For instance, in the above example if the sum of <i>n</i>₄, <i>n</i>_<i>5</i> and n₈ "looks like" 0 to <i>m</i>₁, then m₁ would indicate to n₁ that the value of <i>n</i>₁ is believed to be 0 (since <i>n</i>₁ + <i>n</i>_<i>4</i> + <i>n</i>₅ + <i>n</i>₈ = 0 ); otherwise <i>m</i>₁ indicate to <i>n</i>₁ that the value of <i>n</i>₁ is believed to be 1. Additionally, for soft decision decoding, a reliability measure is added.

From bit nodes to check nodes, each bit node relays to an adjacent check node an estimate about its own value based on the feedback coming from its other adjacent check nodes. In the above example <i>n</i>₁ has only two adjacent check nodes <i>m</i>₁ and <i>m</i>₃ . If the feedback coming from <i>m</i>₃ to <i>n</i>₁ indicates that the value of <i>n</i>₁ is probably 0, then <i>n</i>₁ would notify <i>m</i>₁ that an estimate of <i>n</i>₁ 's own value is 0. For the case in which the bit node has more than two adjacent check nodes, the bit node performs a majority vote (soft decision) on the feedback coming from its other adjacent check nodes before reporting that decision to the check node it communicates. The above process is repeated until all bit nodes are considered to be correct (i.e., all parity check equations are satisfied) or until a predetermined maximum number of iterations is reached, whereby a decoding failure is declared.

FIG. 6 is a diagram of a sub-matrix of a sparse parity check matrix, wherein the sub-matrix contains parity check values restricted to the lower triangular region, according to an embodiment of the present invention. As described previously, the encoder 203 (of FIGs. 2A and 2B) can employ a simple encoding technique by restricting the values of the lower triangular area of the parity check matrix. According to an embodiment of the present invention, the restriction imposed on the parity check matrix is of the form:<maths id="math0029" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">H</mtext></mrow><mrow><mtext>(</mtext><mtext mathvariant="italic">n</mtext><mtext>-</mtext><mtext mathvariant="italic">k</mtext><mtext>)</mtext><mtext mathvariant="italic">xn</mtext></mrow></msub><mtext> = [</mtext><msub><mrow><mtext mathvariant="italic">A</mtext></mrow><mrow><mtext>(</mtext><mtext mathvariant="italic">n</mtext><mtext>-</mtext><mtext mathvariant="italic">k</mtext><mtext>)</mtext><mtext mathvariant="italic">xk</mtext></mrow></msub><mtext></mtext><msub><mrow><mtext mathvariant="italic">B</mtext></mrow><mrow><mtext>(</mtext><mtext mathvariant="italic">n</mtext><mtext>-</mtext><mtext mathvariant="italic">k</mtext><mtext>)</mtext><mtext mathvariant="italic">x</mtext><mtext>(</mtext><mtext mathvariant="italic">n</mtext><mtext>-</mtext><mtext mathvariant="italic">k</mtext><mtext>)</mtext></mrow></msub><mtext>]</mtext></mrow></math><img file="EP1513258A2_D0039.tif" /></maths> , where B is lower triangular.

Any information block <i>i=</i> (<i>i</i>_<i>0</i><i>,i</i>_<i>1</i><i>,...,i</i>_<i>k-1</i>) is encoded to a codeword c= (<i>i</i>₀<i>, i</i>₁<i>,..., i</i>_<i>k-</i>₁<i>, p</i>₀<i>, p</i>₁<i>,...p</i>_<i>n-k-</i>₁) using <i>H</i>c^T = 0, and recursively solving for parity bits; for example,<maths id="math0030" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">a</mtext></mrow><mrow><mtext>00</mtext></mrow></msub><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>0</mtext></mrow></msub><mtext> +</mtext><msub><mrow><mtext mathvariant="italic">a</mtext></mrow><mrow><mtext>01</mtext></mrow></msub><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>1</mtext></mrow></msub><mtext> + ... + </mtext><msub><mrow><mtext mathvariant="italic">a</mtext></mrow><mrow><mtext>0,</mtext><mtext mathvariant="italic">k</mtext><mtext>-1</mtext></mrow></msub><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext mathvariant="italic">k</mtext><mtext>-1</mtext></mrow></msub><mtext> + </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>0</mtext></mrow></msub><mtext> = 0 ⇒ </mtext><msub><mrow><mtext mathvariant="italic">Solve p</mtext></mrow><mrow><mtext>0</mtext></mrow></msub><mtext> ,</mtext></mrow></math><img file="EP1513258A2_D0040.tif" /></maths><maths id="math0031" num=""><math display="block"><mrow><msub><mrow><mtext mathvariant="italic">a</mtext></mrow><mrow><mtext>10</mtext></mrow></msub><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>0</mtext></mrow></msub><mtext> + </mtext><msub><mrow><mtext mathvariant="italic">a</mtext></mrow><mrow><mtext>11</mtext></mrow></msub><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext>1</mtext></mrow></msub><mtext> + ... + </mtext><msub><mrow><mtext mathvariant="italic">a</mtext></mrow><mrow><mtext>1,</mtext><mtext mathvariant="italic">k</mtext><mtext>-1</mtext></mrow></msub><msub><mrow><mtext mathvariant="italic">i</mtext></mrow><mrow><mtext mathvariant="italic">k</mtext><mtext>-1</mtext></mrow></msub><mtext> + </mtext><msub><mrow><mtext mathvariant="italic">b</mtext></mrow><mrow><mtext>10</mtext></mrow></msub><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>0</mtext></mrow></msub><mtext> + </mtext><msub><mrow><mtext mathvariant="italic">p</mtext></mrow><mrow><mtext>1</mtext></mrow></msub><mtext> = 0 ⇒ </mtext><msub><mrow><mtext mathvariant="italic">Solve p</mtext></mrow><mrow><mtext>1</mtext></mrow></msub></mrow></math><img file="EP1513258A2_D0041.tif" /></maths>    and similarly for <i>p</i>₂, <i>p</i>₃,...,<i>p</i>_n-k-1.

FIG. 7 is a graph of performance of the LDPC codes at the various code rates and modulation schemes supported by the transmitter of FIG. 2B. As seen, the 3/5 rate, 8-PSK scenario rivals the performance of the LDPC codes employing QPSK.

FIG. 8 shows the simulation results for short block size LDPC codes, in accordance with an embodiment of the present invention. Table 16 provides the estimated performance at Packet Error Rate (PER) of 10^-7 for the short codes (<i>n</i>_<i>ldpc</i><i>=</i> 16200). <tables id="tabl0016" num="0016"><table frame="all"><title>Table 16</title><tgroup cols="2" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="78.75mm" /><colspec colnum="2" colname="col2" colwidth="78.75mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center"><b>Mode</b></entry><entry namest="col2" nameend="col2" align="center"><b>Estimated Es/No (dB)</b></entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="center">QPSK 0.444</entry><entry namest="col2" nameend="col2" align="center">0.65</entry></row><row><entry namest="col1" nameend="col1" align="center">QPSK 3/5</entry><entry namest="col2" nameend="col2" align="center">2.45</entry></row><row><entry namest="col1" nameend="col1" align="center">QPSK 2/3</entry><entry namest="col2" nameend="col2" align="center">3.35</entry></row><row><entry namest="col1" nameend="col1" align="center">QPSK 0.733</entry><entry namest="col2" nameend="col2" align="center">4.35</entry></row><row><entry namest="col1" nameend="col1" align="center">QPSK 0.777</entry><entry namest="col2" nameend="col2" align="center">4.90</entry></row><row><entry namest="col1" nameend="col1" align="center">QPSK 0.822</entry><entry namest="col2" nameend="col2" align="center">5.40</entry></row><row rowsep="1"><entry namest="col1" nameend="col1" align="center">QPSK 8/9</entry><entry namest="col2" nameend="col2" align="center">6.50</entry></row></tbody></tgroup></table></tables>

FIG. 9 illustrates a computer system upon which an embodiment according to the present invention can be implemented. The computer system 900 includes a bus 901 or other communication mechanism for communicating information, and a processor 903 coupled to the bus 901 for processing information. The computer system 900 also includes main memory 905, such as a random access memory (RAM) or other dynamic storage device, coupled to the bus 901 for storing information and instructions to be executed by the processor 903. Main memory 905 can also be used for storing temporary variables or other intermediate information during execution of instructions to be executed by the processor 903. The computer system 900 further includes a read only memory (ROM) 907 or other static storage device coupled to the bus 901 for storing static information and instructions for the processor 903. A storage device 909, such as a magnetic disk or optical disk, is additionally coupled to the bus 901 for storing information and instructions.

The computer system 900 may be coupled via the bus 901 to a display 911, such as a cathode ray tube (CRT), liquid crystal display, active matrix display, or plasma display, for displaying information to a computer user. An input device 913, such as a keyboard including alphanumeric and other keys, is coupled to the bus 901 for communicating information and command selections to the processor 903. Another type of user input device is cursor control 915, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to the processor 903 and for controlling cursor movement on the display 911.

According to one embodiment of the invention, generation of LDPC codes is provided by the computer system 900 in response to the processor 903 executing an arrangement of instructions contained in main memory 905. Such instructions can be read into main memory 905 from another computer-readable medium, such as the storage device 909. Execution of the arrangement of instructions contained in main memory 905 causes the processor 903 to perform the process steps described herein. One or more processors in a multi-processing arrangement may also be employed to execute the instructions contained in main memory 905. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the embodiment of the present invention. Thus, embodiments of the present invention are not limited to any specific combination of hardware circuitry and software.

The computer system 900 also includes a communication interface 917 coupled to bus 901. The communication interface 917 provides a two-way data communication coupling to a network link 919 connected to a local network 921. For example, the communication interface 917 may be a digital subscriber line (DSL) card or modem, an integrated services digital network (ISDN) card, a cable modem, or a telephone modem to provide a data communication connection to a corresponding type of telephone line. As another example, communication interface 917 may be a local area network (LAN) card (e.g. for Ethernet™ or an Asynchronous Transfer Model (ATM) network) to provide a data communication connection to a compatible LAN. Wireless links can also be implemented. In any such implementation, communication interface 917 sends and receives electrical, electromagnetic, or optical signals that carry digital data streams representing various types of information. Further, the communication interface 917 can include peripheral interface devices, such as a Universal Serial Bus (USB) interface, a PCMCIA (Personal Computer Memory Card International Association) interface, etc.

The network link 919 typically provides data communication through one or more networks to other data devices. For example, the network link 919 may provide a connection through local network 921 to a host computer 923, which has connectivity to a network 925 (e.g. a wide area network (WAN) or the global packet data communication network now commonly referred to as the "Internet") or to data equipment operated by service provider. The local network 921 and network 925 both use electrical, electromagnetic, or optical signals to convey information and instructions. The signals through the various networks and the signals on network link 919 and through communication interface 917, which communicate digital data with computer system 900, are exemplary forms of carrier waves bearing the information and instructions.

The computer system 900 can send messages and receive data, including program code, through the network(s), network link 919, and communication interface 917. In the Internet example, a server (not shown) might transmit requested code belonging to an application program for implementing an embodiment of the present invention through the network 925, local network 921 and communication interface 917. The processor 903 may execute the transmitted code while being received and/or store the code in storage device 99, or other non-volatile storage for later execution. In this manner, computer system 900 may obtain application code in the form of a carrier wave.

The term "computer-readable medium" as used herein refers to any medium that participates in providing instructions to the processor 903 for execution. Such a medium may take many forms, including but not limited to non-volatile media, volatile media, and transmission media. Non-volatile media include, for example, optical or magnetic disks, such as storage device 909. Volatile media include dynamic memory, such as main memory 905. Transmission media include coaxial cables, copper wire and fiber optics, including the wires that comprise bus 901. Transmission media can also take the form of acoustic, optical, or electromagnetic waves, such as those generated during radio frequency (RF) and infrared (IR) data communications. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, CDRW, DVD, any other optical medium, punch cards, paper tape, optical mark sheets, any other physical medium with patterns of holes or other optically recognizable indicia, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave, or any other medium from which a computer can read.

Various forms of computer-readable media may be involved in providing instructions to a processor for execution. For example, the instructions for carrying out at least part of the present invention may initially be borne on a magnetic disk of a remote computer. In such a scenario, the remote computer loads the instructions into main memory and sends the instructions over a telephone line using a modem. A modem of a local computer system receives the data on the telephone line and uses an infrared transmitter to convert the data to an infrared signal and transmit the infrared signal to a portable computing device, such as a personal digital assistance (PDA) and a laptop. An infrared detector on the portable computing device receives the information and instructions borne by the infrared signal and places the data on a bus. The bus conveys the data to main memory, from which a processor retrieves and executes the instructions. The instructions received by main memory may optionally be stored on storage device either before or after execution by processor.

Accordingly, the various embodiments of the present invention provide an LDPC encoder generates a LDPC code having an outer Bose Chaudhuri Hocquenghem (BCH) code according to one of Tables 2-8 for transmission as a LDPC coded signal. Each of the Tables 2-8 specifies the address of parity bit accumulators. Short LDPC codes are output by utilizing LDPC mother codes that are based on Tables 2-8. <i>k</i>_<i>ldpc</i> of the BCH encoded bits are preceded by <i>k</i>_<i>m</i> - <i>k</i>_<i>ldpc</i> dummy zeros. The resulting <i>k</i>_<i>m</i> bits are systematically encoded to generate <i>n</i>_<i>m</i> bits. The first <i>k</i>_<i>m</i> - <i>k</i>_<i>ldpc</i> dummy zeros are then deleted to yield the shortened code. For an LDPC code with code rate of 3/5 utilizing 8-PSK (Phase Shift Keying) modulation, an interleaver provides for interleaving bits of the output LDPC code by serially writing data associated with the LDPC code column-wise into a table and reading the data row-wise from right to left. The above approach advantageously yields reduced complexity without sacrificing performance.

While the present invention has been described in connection with a number of embodiments and implementations, the present invention is not so limited but covers various obvious modifications and equivalent arrangements, which fall within the purview of the appended claims.