Professional Documents
Culture Documents
IEEE WirelessComms Apr2010 ReliableData
IEEE WirelessComms Apr2010 ReliableData
IEEE WirelessComms Apr2010 ReliableData
net/publication/225005828
Reliable Data Delivery over Deep Space Networks: Benefits of Long Erasure
Codes over ARQ Strategies
CITATIONS READS
37 820
2 authors:
Some of the authors of this publication are also working on these related projects:
All content following this page was uploaded by Mario Marchese on 22 December 2014.
CFDP
Figure 1. CCSDS protocol architecture: higher (light blue) and lower layer pro- The CCSDS File Delivery Protocol (CFDP) [13]
tocols (dark blue) [4]. aims at transferring files from one filestore to
another, located in spacecraft and space stations.
The file to be transmitted is encoded into a
the channel quality, provided that information file delivery unit (FDU), composed of the file
about the signal degradation is available from itself and metadata necessary for data manage-
the physical layer. Also in this case, modifica- ment. The CFDP entity splits the FDU into
tions of different data link layer protocol specifi- CFDP protocol data units (PDUs) of variable
cations would be required, with an impact on the length. CFDP PDUs are structured into payload,
flexibility of the overall system design. containing up to 65,536 bytes, and header, con-
taining CFDP source and destination identifiers,
THE REFERENCE PROTOCOL ARCHITECTURE transfer file sequence number, as well as other
fields suited to allow the reconstruction of the
CCSDS PROTOCOL STACK: AN OVERVIEW FDU at the destination. Data transmission is
performed by CFDP entities according to two
CCSDS activity is primarily focused on the defi- operative modes, unacknowledged and acknowl-
nition and implementation of a protocol archi- edged. The former implements no mechanisms
tecture alternative to the existing ones (e.g., to ensure complete data delivery; communica-
TCP/ IP suite) to support effective data transfer tion reliability, where required, should be
over long delay and lossy networks, as in the ensured by proper mechanisms implemented
case of interplanetary networks. A full protocol within the underlying layers. The latter provides
stack, including all the protocols from the appli- reliable delivery of data by means of ARQ strate-
cation to the physical layer, has been recom- gies, relying on negative acknowledgment
mended, designed, and deployed in spacecraft, (NAK). The detection of missing CFDP PDUs is
satellites, and Earth stations. The protocol stack performed by the receiver, which notifies the
composition is shown in Fig. 1, where the sepa- loss of data to the sender by issuing NAK blocks
ration between higher- and lower-layer protocols according to four different algorithms: Immedi-
is highlighted. A short summary of each layer is ate, Deferred, Asynchronous, and Prompted. In
reported in the following. the first case a NAK issuance is performed as
Physical layer: CCSDS recommendations on soon as the loss of CFDP PDUs is detected.
RF and modulation systems focus on the most Deferred mode allows postponing the issuance
suitable transmission schemes to be adopted in of NAKs to the end of the file transfer. As far as
space missions, where either long-haul links (long- prompted and asynchronous modes are con-
range and bidirectional), established to allow com- cerned, the detection of missing blocks is trig-
munication between spacecraft and satellites very gered by external events, such as explicit
far from each other, or proximity links (short- (asynchronous mode) or periodical (prompted
range and bidirectional) are employed. mode) requests by the sender.
Data link layer: CCSDS has developed four
protocols: Telemetry (TM), Telecommand (TC), PROPOSED PROTOCOL SOLUTIONS
Advanced Orbiting Systems (AOS), and Proxim- The advantages offered by erasure codes, point-
ity-1 space link protocol-data link [4]. Their ed out in the previous section, support the idea
basic function is to forward transfer frames of of implementing a packet-layer coding strategy
fixed or variable length to the physical layer, by within the CCSDS protocol stack, as proposed
taking care of synchronization and channel cod- by the LEC BOF working group [8]. The frame
ing functions, along with encapsulation and error detection and correction functions per-
framing operations. formed by the CCSDS data link layer, depending
The efficiency of them over the space link. The use of coding
techniques also during the recovery phase is con-
at the application layer (i.e., CFDP), the success-
ful delivery of data alternates with occurrences
packet-layer coding sidered beneficial to increase the robustness of missed PDUs. Given the correlated nature of
against packet erasures, thus reducing the num- the deep space link, the erasure channel can be
has to be checked ber of retransmission loops. This solution is modeled as a first order two-state discrete-time
hereafter referred to as CFDP — Acknowledged Markov chain (DTMC) embedded in the trans-
against different Deferred with Coding (CFDP-ADC). mission of each PDU at the application layer.
Using erasure codes to ensure reliable data Two states, ON and OFF, are considered: no
performance delivery is expected to be an effective alternative information loss is observed in state ON, where-
indicators, according to ARQ schemes since retransmission strategies
performed over deep space links are likely to
as erasures are experienced in state OFF.
According to [15], erasure rates ranging from 0.1
to specific service degrade because of very large propagation up to 0.4 can be considered by varying the aver-
delays. On the other hand, the implementation age duration of the OFF state depending on the
requirements such as of coding techniques alone is not sufficient to frame length; on the other hand, the average
guarantee successful file delivery, because there duration of the ON state is kept fixed. In this
information loss and is some residual information loss that might be way, it is possible to relate the performance of
fully recovered by ARQ schemes. Nevertheless, the application layer to the length of the data
data delivery latency. it is also worth noting that the importance of file link layer frames. In particular, frame lengths
transfer reliability and respect for delivery con- ranging from 128 to 1024 bytes are considered,
straints basically depend on the specific file con- with a corresponding average number of erased
tent. Images and measurement file transfers can symbols ranging from 300 kb up to 1 Mb (in line
tolerate some information loss, but emergency with values presented in [15]).
or system messages should be delivered in a As far as propagation delay configurations
timely manner and without any information loss. are concerned, attention is focused on delays
This differentiation opens the door to QoS man- ranging from 1 up to 200 s, in order to consider
agement performed at the CFDP entity by tun- both near-Earth and deep space missions. The
ing protocol settings in order to match specific link bandwidth is set to 1 Mb/s and 1 kb/s for
file transfer requirements. Also, power consump- downlink and uplink, respectively.
tion and implementation complexity issues can-
not be neglected because spacecrafts and remote CASE STUDY: MAIN RESULTS
planet stations (landers and rovers) have strict The efficiency of packet-layer coding has to be
system design constraints. The implementation checked against different performance indicators
of erasure codes may imply waste of bandwidth according to specific service requirements such
and power roughly proportional to the amount as information loss and data delivery latency.
of generated redundancy symbols, thus requiring The comparison of the proposed CFDP enhance-
attentive configuration of the coding parameters. ments, CFDP-UC and CFDP-ADC, with respect
In addition, the encoding process requires the to standard CFDP-Deferred is performed
storage of CFDP PDUs in proper buffers, per- accordingly. In particular, the following protocol
formed before the encoding process. At the configurations have been considered in order to
receiver side, decoding operations need memory identify the role played by the key parameters in
space sufficient to accommodate the symbols system performance:
actually necessary to successfully reconstruct the • CFDP-UC and CFDP-ADC: CFDP PDUs are
original CFDP PDUs. In addition, if the erasure aggregated into information vectors carrying 1
codes are complemented by retransmission oper- Mbyte. Code rates varying between 0.125 and
ations (as for CFDP-ADC), the source side has 0.875 are considered. LDPC codes achieving
to provide space sufficient to store the entire near-Shannon limits are considered, with code
file. Bandwidth and power waste is approximate- inefficiency (ε) equal to 0.04
ly proportional to the amount of retransmitted • CFDP-Deferred. The CFDP PDU length is
data. varied between 1024 and 65,536 bytes.
All these factors along with performance fig- • As reported earlier, the length of data link
ures (i.e., file transfer reliability and delivery layer frames ranges between 128 and 1024
delay) play a fundamental role in the design of bytes. Encapsulation issues and overhead
an effective space telecommunication system. introduced by the overlying layers are consid-
Some relevant case studies are illustrated in the ered accordingly.
following in order to identify the most effective Three metrics are considered primarily: infor-
protocol configurations. mation loss (ILoss), data delivery latency (DDLa-
tency), and normalized goodput (NGoodput).
PROTOCOL PERFORMANCE EVALUATION ILoss is defined as the ratio between the number
of correctly received and transmitted CFDP
DEEP SPACE LINK MODELING PDUs; DDLatency as the time duration elapsing
from the transmission of the first CFDP PDU
As introduced earlier, the physical peculiarities and the correct reception of all the CFDP PDUs.
of deep space environments (solar winds, flares, NGoodput is defined as the ratio between the
thermal noise), the reduction of the link budget amount of data correctly received at the destina-
margin due to atmospheric events occurring on tion and the time duration required by the trans-
the downlink, along with the possible loss of syn- fer, normalized to the available bandwidth. The
chronization at the receiver side give rise to cor- performance of the protocol solutions is tested
related symbol erasures, which may range from a by considering transfers of 100-Mbyte files,
few up to hundreds of data link layer frames. achieved between two space nodes that imple-
From the viewpoint of the performance observed ment a full CCSDS protocol stack.
ILoss
0.6
redundancy packets is not able to counteract the 0.875
erasures caused by link errors independent of 0.5
the coded packet size. If the code-rate is equal 0.4
to 0.750, registered performance starts with 0.3
ILoss equal to 1 when the sent frames carry 128
0.2
bytes; then the loss falls down below 0.3 as the
frame size increases its length to 256 bytes. ILoss 0.1
increases again while the coded packet size 0
increases its length from 384 to 768 bytes and 128 256 384 512 640 768 1024
keeps approximately the same value for 1024. Datalink frame length (bytes)
Concerning the other code rates, all registered
ILoss values overlap for any frame size, even if it Figure 3. CFDP-UC performance: information loss vs. data link frame size for
is possible to observe that when the frame size is different code-rates.
set to 512 bytes, the most satisfactory result is
achieved: ILoss of 0.07.
DDLatency and NGoodput performance is
obviously dependent on the propagation delay, 3500
especially in the case of CFDP-ADC and CFDP- CFDP-UP
CFDP-ADC
Deferred since they can resort to retransmission 3000 CFDP-Deferred
procedures in case of CFDP PDU erasures.
Besides, the CFDP PDU and frame length
play an important role in CFDP-Deferred per- 2500
formance. In general, large PDUs at both appli-
DDLatency (s)
gation delay of 200 s. DDLatency values regis- dancy and retransmitted bytes) is considered as a
tered for CFDP-UC are always below 1000 s rough measure of expended power. Storage
since no retransmission is performed, at cost of requirements are considered in terms of buffer
partial data delivery, as shown in Fig. 4. space availability, which is needed by each consid-
The NGoodput is depicted in Fig. 5: CFDP- ered protocol solutions to either perform retrans-
Deferred allows using network resources effi- missions or coding/decoding operations. The sum
ciently (NGoodput varies between 0.9 and 0.6) of these two factors (both measured in Mbytes),
when the propagation delay is lower than 50 s. referred to as Network Resource Cost (NRCost)
As the delay increases (i.e., from 50 s up to 200 allows shedding light on the relation between
s), the use of pure ARQ schemes is not effective. achieved performance and implementation cost.
CFDP-UC and CFDP-ADC are less efficient for In particular it is interesting to see how NRCost
low delays but offer better results, varying from scales in correspondence of different ILoss targets.
0.6 to 0.4, depending on the propagation delay In particular three ILoss targets were considered:
(Fig. 5); larger delays highlight the main perfor- 0.025, 0.05, and 0.15 respectively. These ILoss tar-
mance limits of pure ARQ mechanisms. gets are referred in terms of three different pro-
Finally, a very important factor that impacts on files: A (ILoss ≤ 0.025), B (0.025 < ILoss ≤ 0.05),
system design is given by hardware/software con- and C (0.05 < ILoss ≤ 0.15).
straints, considered here in terms of power budget It is relevant for space system design to identi-
and storage capacity. In order to take into account fy the cost components (in terms of retransmitted
power consumption issues, the total number of data and storage requirements) needed by the
transmitted data (comprehensive of both redun- protocol configurations to minimize the data
delivery delay, subject to the ILoss constraints
imposed by profiles A, B, and C. The perfor-
mance offered by the protocol solutions in terms
1 of the NRCost is shown in Fig. 6 vs. the propaga-
CFDP-UP
0.9 CFDP-ADC tion delay and the profile that can be satisfied. All
CFDP-Deferred profiles in Fig. 6 implies that profile A (the most
0.8 demanding) is satisfied together with the other
0.7 two, which are less restrictive. The differentiation
between the number of transmitted bytes and the
NGoodput
0.6
storage capability required by each node is high-
0.5 lighted through two different colors. Immediately
we see that CFDP-Deferred and CFDP-ADC can
0.4
match all ILoss targets as they allow reliable com-
0.3 munications. On the contrary, CFDP-UC can
0.2 match only profiles B and C, but with very limited
cost, whereas CFDP-ADC and CFDP-Deferred
0.1 require higher cost because of the retransmission
0 procedures that imply a larger amount of data to
1 10 50 100 200 be transmitted along with increased storage
Propagation delay (s)
capacity. Nevertheless, it is important to point out
that only CFDP-ADC and CFDP-Deferred can
Figure 5. Protocol solution performance: normalized goodput. match profile A’s target; in this view, CFDP-
ADC, especially for long propagation delays,
offers a better trade-off between retransmitted
data and storage space. This observation further
350
Storage space confirms the advantages offered by erasure cod-
300 Transmitted data ing, which is helpful in matching profiles B and C
at low cost (CFDP-UC) and also profile A
250
NRCost (Mbytes)
0
DISCUSSION OF RESULTS
The performance figures presented in the previ-
CFDP-UC(Profile B)
CFDP-UC (Profile C)
CFDP-ADC (All profiles)
CFDP-Deferred (All profiles)
CFDP-UC (Profile B)
CFDP-UC (Profile C)
CFDP-ADC (All profiles)
CFDP-Deferred (All profiles)
CFDP-UC (Profile B)
CFDP-UC (Profile C)
CFDP-ADC (All profiles)
CFDP-Deferred (All profiles)
CFDP-UC (Profile B)
CFDP-UC (Profile C)
CFDP-ADC (All profiles)
CFDP-Deferred (All profiles)
CFDP-UC (Profile B)
CFDP-UC (Profile C)
CFDP-ADC (All profiles)
CFDP-Deferred (All profiles)