language-icon Old Web
English
Sign In

Luby transform code

In computer science, Luby transform codes (LT codes) are the first class of practical fountain codes that are near-optimal erasure correcting codes. They were invented by Michael Luby in 1998 and published in 2002. Like some other fountain codes, LT codes depend on sparse bipartite graphs to trade reception overhead for encoding and decoding speed. The distinguishing characteristic of LT codes is in employing a particularly simple algorithm based on the exclusive or operation ( ⊕ {displaystyle oplus } ) to encode and decode the message. In computer science, Luby transform codes (LT codes) are the first class of practical fountain codes that are near-optimal erasure correcting codes. They were invented by Michael Luby in 1998 and published in 2002. Like some other fountain codes, LT codes depend on sparse bipartite graphs to trade reception overhead for encoding and decoding speed. The distinguishing characteristic of LT codes is in employing a particularly simple algorithm based on the exclusive or operation ( ⊕ {displaystyle oplus } ) to encode and decode the message. LT codes are rateless because the encoding algorithm can in principle produce an infinite number of message packets (i.e., the percentage of packets that must be received to decode the message can be arbitrarily small). They are erasure correcting codes because they can be used to transmit digital data reliably on an erasure channel. The next generation beyond LT codes are Raptor codes (see for example IETF RFC 5053 or IETF RFC 6330), which have linear time encoding and decoding. Raptor codes use two encoding stages for encoding, where the second stage is an LT encoding.Information about availability of an efficient software implementation of the RaptorQ code specified in IETF RFC 6330 (the most advanced fountain code), can be found at thewebsite for the Codornices project at ICSI .

[ "Linear code", "Error floor", "Hamming code", "Concatenated error correction code", "Reed–Solomon error correction" ]
Parent Topic
Child Topic
    No Parent Topic