Network Coding and Wireless Physical-layer ... - Jacobs University
Network Coding and Wireless Physical-layer ... - Jacobs University
Network Coding and Wireless Physical-layer ... - Jacobs University
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
33<br />
The emergence of scalable video coding st<strong>and</strong>ard means that some parts of transmitted<br />
data should be better protected than others. This concept is called unequal error/erasure<br />
protection (UEP). We will show in Chapter 4 that network coding inherently supports<br />
this concept. However, this will inevitably leads to conflicts among receiving nodes in a<br />
multicast session. We provide an economic analysis of the conflicts as well as an auction<br />
algorithm to resolve them.<br />
Rateless codes, such as LT-codes <strong>and</strong> Rapter codes, are originally designed to guarantee<br />
that erasures in the network do not affect data recovery. This seems, at first thought,<br />
to imply that they do not support UEP, since the recovery of every data priority seems<br />
to be guaranteed. However, a subsequent work by Rahnavard, vellambi, <strong>and</strong> Fekri, shows<br />
that UEP can still be implemented using a similar concept of unequal recovery time<br />
(URT) [47]. Their technique ensures that, for an unlimited time, data of all priorities is<br />
recovered, but for a specific time range, higher-priority data will be recovered before the<br />
lower-priority one. This allows the receiving nodes to decide how long they want to spend<br />
time receiving data, according to the number of priorities that they need.<br />
However, when rateless codes are used in a network with network coding, another<br />
problem arises. We call it the degree distribution distortion problem. This will make the<br />
recovery time of every data priority longer than the normal case without network coding.<br />
In Chapter 5, we investigate this problem in LT-codes with the simplest case of a butterfly<br />
network <strong>and</strong> gives a solution.