Goal
See why DTN treats disconnection as normal operating state, not as a broken route.
Trace how delay-tolerant networks store a bundle, carry it through disconnection, and forward it during short contacts.
DTN does not assume a live end-to-end route. This animation shows how a bundle survives disconnected time by living in node buffers, moving with mobile carriers, and transferring only during short contact windows.
See why DTN treats disconnection as normal operating state, not as a broken route.
Switch strategies, then lower contact range or bandwidth to watch delivery become buffer-limited.
The bundle token should sit in storage, move with a carrier, and only cross links during contact windows.
Pick the cheapest strategy that still meets the application delay and reliability requirement.
A source stores a bundle while no path exists. Contacts appear as nodes move into radio range.
Spray-and-wait limits extra copies while still giving several mobile carriers a chance to meet the destination.
Select a deployment pattern.
Choose how a contact forwards the bundle.
DTN is not simply slow TCP/IP. Traditional routing expects a contemporaneous path. DTN accepts that the useful path may be spread over time.
| Strategy | Use when | Watch out |
|---|---|---|
| Direct | Source is likely to meet destination and energy is scarce. | Delivery may wait a long time or fail within TTL. |
| Epidemic | Message is critical and buffers, energy, and bandwidth are available. | Copies can overwhelm radios and storage. |
| Spray-and-wait | You need bounded overhead with better delivery odds than direct. | Too few tickets can strand the bundle. |
| PRoPHET-style | Mobility has history or regular patterns. | Bad history gives false confidence. |
This demo uses teaching estimates, not a full simulator. The formulas connect the visible behavior to real design factors.
Use these after the animation to connect the trace to surrounding course material.