Skip to content

DTN Network Operations Checkpoints

Knowledge check · self-test

DTN Network Operations Checkpoints

Check store-carry-forward fit: distinguish a current route from a future contact.

Back to the chapter →

Check store-carry-forward fit: distinguish a current route from a future contact.

::: {.callout-tip} ## Blueprint Bina, Architecture and system-design domain expertCheckpoint: Store-Carry-Forward Fit {.depth-l0} You now know: - DSDV, DSR, and ZRP assume connected paths; they fail when partitions cannot exchange route messages. - DTN preserves the bundle locally, carries it on a mobile node, and forwards it during a later contact. - The correct fit is a delay-tolerant mission: wildlife tracking, vehicular networks, rural IoT, disaster recovery, or space networks. :::
::: {.callout-tip} ## Blueprint Bina, Architecture and system-design domain expertCheckpoint: Contact and Buffer Budget {.depth-l0} You now know: - The elephant example generates 2,112 bytes/day with headers and needs about 173 KiB after five relay copies. - A 45 second contact at 250 kbps can move 1,406,250 bytes, so contact capacity is not the bottleneck in this scenario. - L=6 source spray-and-wait leaves six holders, including the source, after five relay transfers. - Under the stated independent-contact assumptions, the simplified spray-plus-wait phase means sum to about 17.97 hours; this is not measured field performance. :::

Back to Delay-Tolerant Networks: Disconnected Operations: Back to DTN Network Operations