Turbo code

In information theory, turbo codes (originally in French Turbocodes) are a class of high-performance forward error correction (FEC) codes developed around 1990-91 (but first published in 1993), which were the first practical codes to closely approach the channel capacity, a theoretical maximum for the code rate at which reliable communication is still possible given a specific noise level. Turbo codes are finding use in 3G/4G mobile communications (e.g. in UMTS and LTE) and in (deep space) satellite communications as well as other applications where designers seek to achieve reliable information transfer over bandwidth- or latency-constrained communication links in the presence of data-corrupting noise. Turbo codes are nowadays competing with LDPC codes, which provide similar performance.

The name "turbo code" arose from the feedback loop used during normal turbo code decoding, which was analogized to the exhaust feedback used for engine turbocharging. Hagenauer has argued the term turbo code is a misnomer since there is no feedback involved in the encoding process. [IEEE Transactions]

History

The fundamental patent application for turbo codes was filed on April 23, 1991. The patent application lists Claude Berrou as the sole inventor of turbo codes. The patent filing resulted in several patents including US Patent 5,446,747, which expired August 29, 2013.

The first public paper on turbo codes was "Near Shannon Limit Error-correcting Coding and Decoding: Turbo-codes".^[1] This paper was published 1993 in the Proceedings of IEEE International Communications Conference. The 1993 paper was formed from three separate submissions that were combined due to space constraints. The merger caused the paper to list three authors: Berrou, Glavieux, and Thitimajshima (from Télécom Bretagne, former ENST Bretagne, France). However, it is clear from the original patent filing that Claude Berrou is the sole inventor of turbo codes and that the other authors of the paper contributed material other than the core concepts of turbo codes.

Turbo codes were so revolutionary at the time of their introduction that many experts in the field of coding did not believe the reported results. When the performance was confirmed a small revolution in the world of coding took place that led to the investigation of many other types of iterative signal processing.

The first class of turbo code was the parallel concatenated convolutional code (PCCC). Since the introduction of the original parallel turbo codes in 1993, many other classes of turbo code have been discovered, including serial versions Serial concatenated convolutional codes and Repeat-accumulate codes. Iterative turbo decoding methods have also been applied to more conventional FEC systems, including Reed-Solomon corrected convolutional codes, although these systems are too complex for practical implementations of iterative decoders. Turbo equalization also flowed from the concept of turbo coding.

In addition to the invention of Turbo Codes, Claude Berrou also invented recursive systematic convolutional (RSC) codes, which are used in the example implementation of turbo codes described in the patent. Turbo Codes that use RSC codes seems to perform better than Turbo codes that do not use RSC codes.

Prior to turbo codes, the best constructions were serial concatenated codes based on an outer Reed-Solomon error correction code combined with an inner Viterbi-decoded short constraint length convolutional code, also known as RSV codes.

In a later paper, Berrou generously gave credit to the intuition of "G. Battail, J. Hagenauer and P. Hoeher, who, in the late 80s, highlighted the interest of probabilistic processing." He adds "R. Gallager and M. Tanner had already imagined coding and decoding techniques whose general principles are closely related," although the necessary calculations were impractical at that time.^[2]

An example encoder

There are many different instances of turbo codes, using different component encoders, input/output ratios, interleavers, and puncturing patterns. This example encoder implementation describes a classic turbo encoder, and demonstrates the general design of parallel turbo codes.

This encoder implementation sends three sub-blocks of bits. The first sub-block is the m-bit block of payload data. The second sub-block is n/2 parity bits for the payload data, computed using a recursive systematic convolutional code (RSC code). The third sub-block is n/2 parity bits for a known permutation of the payload data, again computed using an RSC code. Thus, two redundant but different sub-blocks of parity bits are sent with the payload. The complete block has m + n bits of data with a code rate of m/(m + n). The permutation of the payload data is carried out by a device called an interleaver.

Hardware-wise, this turbo-code encoder consists of two identical RSC coders, С₁ and C₂, as depicted in the figure, which are connected to each other using a concatenation scheme, called parallel concatenation:

In the figure, M is a memory register. The delay line and interleaver force input bits d_k to appear in different sequences. At first iteration, the input sequence d_k appears at both outputs of the encoder, x_k and y_1k or y_2k due to the encoder's systematic nature. If the encoders C₁ and C₂ are used respectively in n₁ and n₂ iterations, their rates are respectively equal to

$\begin{align} ~R_1 &= \frac{n_1 + n_2}{2n_1 + n_2}\\ ~R_2 &= \frac{n_1 + n_2}{n_1 + 2n_2} \end{align}$

The decoder

The decoder is built in a similar way to the above encoder. Two elementary decoders are interconnected to each other, but in serial way, not in parallel. The $\scriptstyle DEC_1$ decoder operates on lower speed (i.e., $\scriptstyle R_1$), thus, it is intended for the $\scriptstyle C_1$ encoder, and $\scriptstyle DEC_2$ is for $\scriptstyle C_2$ correspondingly. $\scriptstyle DEC_1$ yields a soft decision which causes $\scriptstyle L_1$ delay. The same delay is caused by the delay line in the encoder. The $\scriptstyle DEC_2$'s operation causes $\scriptstyle L_2$ delay.

An interleaver installed between the two decoders is used here to scatter error bursts coming from $\scriptstyle DEC_1$ output. DI block is a demultiplexing and insertion module. It works as a switch, redirecting input bits to $\scriptstyle DEC_1$ at one moment and to $\scriptstyle DEC_2$ at another. In OFF state, it feeds both $\scriptstyle y_{1k}$ and $\scriptstyle y_{2k}$ inputs with padding bits (zeros).

Consider a memoryless AWGN channel, and assume that at k-th iteration, the decoder receives a pair of random variables:

$\begin{align} ~x_k &= (2d_k - 1) + a_k\\ ~y_k &= 2( Y_k - 1) + b_k \end{align}$

where $\scriptstyle a_k$ and $\scriptstyle b_k$ are independent noise components having the same variance $\scriptstyle \sigma^2$. $\scriptstyle Y_k$ is a k-th bit from $\scriptstyle y_k$ encoder output.

Redundant information is demultiplexed and sent through DI to $\scriptstyle DEC_1$ (when $\scriptstyle y_k \;=\; y_{1k}$) and to $\scriptstyle DEC_2$ (when $\scriptstyle y_k \;=\; y_{2k}$).

$\scriptstyle DEC_1$ yields a soft decision; i.e.:

$\Lambda(d_k) = \log\frac{p(d_k = 1)}{p(d_k = 0)}$

and delivers it to $\scriptstyle DEC_2$. $\scriptstyle \Lambda(d_k)$ is called the logarithm of the likelihood ratio (LLR). $\scriptstyle p(d_k \;=\; i),\, i \,\in\, \{0,\, 1\}$ is the a posteriori probability (APP) of the $\scriptstyle d_k$ data bit which shows the probability of interpreting a received $\scriptstyle d_k$ bit as $\scriptstyle i$. Taking the LLR into account, $\scriptstyle DEC_2$ yields a hard decision; i.e., a decoded bit.

It is known that the Viterbi algorithm is unable to calculate APP, thus it cannot be used in $\scriptstyle DEC_1$. Instead of that, a modified BCJR algorithm is used. For $\scriptstyle DEC_2$, the Viterbi algorithm is an appropriate one.

However, the depicted structure is not an optimal one, because $\scriptstyle DEC_1$ uses only a proper fraction of the available redundant information. In order to improve the structure, a feedback loop is used (see the dotted line on the figure).

Soft decision approach

The decoder front-end produces an integer for each bit in the data stream. This integer is a measure of how likely it is that the bit is a 0 or 1 and is also called soft bit. The integer could be drawn from the range [−127, 127], where:

• −127 means "certainly 0"
• −100 means "very likely 0"
• 0 means "it could be either 0 or 1"
• 100 means "very likely 1"
• 127 means "certainly 1"
• etc.

This introduces a probabilistic aspect to the data-stream from the front end, but it conveys more information about each bit than just 0 or 1.

For example, for each bit, the front end of a traditional wireless-receiver has to decide if an internal analog voltage is above or below a given threshold voltage level. For a turbo-code decoder, the front end would provide an integer measure of how far the internal voltage is from the given threshold.

To decode the m + n-bit block of data, the decoder front-end creates a block of likelihood measures, with one likelihood measure for each bit in the data stream. There are two parallel decoders, one for each of the ⁿ⁄₂-bit parity sub-blocks. Both decoders use the sub-block of m likelihoods for the payload data. The decoder working on the second parity sub-block knows the permutation that the coder used for this sub-block.

Solving hypotheses to find bits

The key innovation of turbo codes is how they use the likelihood data to reconcile differences between the two decoders. Each of the two convolutional decoders generates a hypothesis (with derived likelihoods) for the pattern of m bits in the payload sub-block. The hypothesis bit-patterns are compared, and if they differ, the decoders exchange the derived likelihoods they have for each bit in the hypotheses. Each decoder incorporates the derived likelihood estimates from the other decoder to generate a new hypothesis for the bits in the payload. Then they compare these new hypotheses. This iterative process continues until the two decoders come up with the same hypothesis for the m-bit pattern of the payload, typically in 15 to 18 cycles.

An analogy can be drawn between this process and that of solving cross-reference puzzles like crossword or sudoku. Consider a partially completed, possibly garbled crossword puzzle. Two puzzle solvers (decoders) are trying to solve it: one possessing only the "down" clues (parity bits), and the other possessing only the "across" clues. To start, both solvers guess the answers (hypotheses) to their own clues, noting down how confident they are in each letter (payload bit). Then, they compare notes, by exchanging answers and confidence ratings with each other, noticing where and how they differ. Based on this new knowledge, they both come up with updated answers and confidence ratings, repeating the whole process until they converge to the same solution.

Performance

Turbo codes perform well due to the attractive combination of the code's random appearance on the channel together with the physically realisable decoding structure. Turbo codes are affected by an error floor.

Practical applications using turbo codes

Telecommunications:

• Turbo codes are used extensively in 3G and 4G mobile telephony standards; e.g., in HSPA, EV-DO and LTE.
• MediaFLO, terrestrial mobile television system from Qualcomm.
• The interaction channel of satellite communication systems, such as DVB-RCS^[3] and DVB-RCS2.
• New NASA missions such as Mars Reconnaissance Orbiter now use turbo codes, as an alternative to RS-Viterbi codes.
• Turbo coding such as block turbo coding and convolutional turbo coding are used in IEEE 802.16 (WiMAX), a wireless metropolitan network standard.

Bayesian formulation

From an artificial intelligence viewpoint, turbo codes can be considered as an instance of loopy belief propagation in Bayesian networks.^[4]

See also

• Convolutional code
• Viterbi algorithm
• Soft-decision decoding
• Interleaver
• BCJR algorithm
• Low-density parity-check code
• Serial concatenated convolutional codes
• Turbo equalizer

References

1. Berrou, Claude; Glavieux, Alain; Thitimajshima, Punya, Near Shannon Limit Error – Correcting (PDF), retrieved 11 February 2010
2. Berrou, Claude, The ten-year-old turbo codes are entering into service (PDF), Bretagne, France, retrieved 11 February 2010
3. Digital Video Broadcasting (DVB); Interaction channel for Satellite Distribution Systems, ETSI EN 301 790, V1.5.1, May 2009.
4. McEliece, Robert J.; MacKay, David J. C.; Cheng, Jung-Fu (1998), "Turbo decoding as an instance of Pearl's "belief propagation" algorithm", IEEE Journal on Selected Areas in Communications 16 (2): 140–152, doi:10.1109/49.661103, ISSN 0733-8716.

External links

• "Closing In On The Perfect Code", IEEE Spectrum, March 2004
• "The UMTS Turbo Code and an Efficient Decoder Implementation Suitable for Software-Defined Radios" (International Journal of Wireless Information Networks)
• Dana Mackenzie (2005), "Take it to the limit", New Scientist 187 (2507): 38–41, ISSN 0262-4079. (preview, copy)
• "Pushing the Limit", a Science News feature about the development and genesis of turbo codes
• International Symposium On Turbo Codes
• Coded Modulation Library, an open source library for simulating turbo codes in matlab
• "Turbo Equalization: Principles and New Results", an IEEE Transactions on Communications article about using convolutional codes jointly with channel equalization.
• IT++ Home Page The IT++ is a powerful C++ library which in particular supports turbo codes
• Turbo codes publications by David MacKay