Changeset 2751
- Timestamp:
- 10/30/09 00:51:21 (4 weeks ago)
- Location:
- docs/Lowthane/ipsn10
- Files:
-
- 4 modified
-
abstract.tex (modified) (2 diffs)
-
design.tex (modified) (1 diff)
-
intro.tex (modified) (2 diffs)
-
lowthane.tex (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
docs/Lowthane/ipsn10/abstract.tex
r2560 r2751 2 2 During the past decade, collection and dissemination have emerged as 3 3 the two dominant communication patterns in sensor networks. Going 4 forward, these basic services will remain important, but manyemerging4 forward, these basic services will remain important, but emerging 5 5 applications also require point-to-point communication for interactive 6 use, sensor /actuator pairing, end-to-end acknowledgements, and many7 other reasons, raising the question of how best to satisfy the 8 increasingly diverse set of communication patterns within the severe9 resourceconstraints of typical nodes.6 use, sensor-actuator pairing, end-to-end acknowledgements, and other 7 reasons, raising the question of how best to satisfy the increasingly 8 diverse set of communication patterns within the severe resource 9 constraints of typical nodes. 10 10 11 11 In this paper, we begin with collection routing as our foundation and … … 17 17 workloads, and especially on the factors important in this regime -- 18 18 code and memory footprint, routing stretch, and protocol overhead. We 19 fully implement our proposed protcol to route IPv6 traffic, evaluate 20 it inboth simulation and on multiple deployments, and compare it with19 implement our proposed protocol to route IPv6 traffic, evaluate it in 20 both simulation and on multiple deployments, and compare it with 21 21 TinyAODV in controlled settings. 22 22 -
docs/Lowthane/ipsn10/design.tex
r2733 r2751 1 \section{\ lowthane~Overview}\label{sec:overview}1 \section{\LOWTHANE~Overview}\label{sec:overview} 2 2 3 3 Before diving into the details, we begin by providing an overview of -
docs/Lowthane/ipsn10/intro.tex
r2707 r2751 24 24 period of active research that produced many pioneering 25 25 contributions~\cite{trickle,mintroute}, and influence collection and 26 dissemination research to this day~\cite{flashflood,ctp,dip}. Perhaps 27 equally important, the early efforts established the canonical system 28 architecture of stationary sensor networks: a bevy of resource-poor 29 sensor nodes streaming data to a resource-rich root node. 26 dissemination research to this day~\cite{flashflood,ctp,dip}. 30 27 31 Collection routing continues to play an important role today but its 28 Over time and with experience, the community began to conclude that 29 reasoning about (and implementing) localized algorithms proved to be 30 more challenging and less important than originally anticipated. 31 Perhaps equally important, through many application deployments, the 32 community converged on a canonical system architecture for stationary 33 sensor networks: a bevy of resource-poor sensor nodes streaming data 34 to a resource-rich root node. Eventually, centralized implementations 35 would leverage this architecture and exhibit competitive performance 36 without the complexity overhead common to localized algorithms. And, 37 the early proponents of directed diffusion would argue for centralized 38 routing~\cite{centroute} and application logic~\cite{tenet}, and 39 others would converge on this architecture approach~\cite{koala}. 40 41 Today, collection routing continues to play an important role, but its 32 42 best effort reliability semantics -- due to its lack of end-to-end 33 43 acknowledgements -- proved insufficient for many scientific … … 61 71 space~\cite{?}. Some require non-trivial state or frequent 62 72 messaging~\cite{?}. Some require stable landmarks~\cite{?}. And all 63 have non-trivial code overhead .73 have non-trivial code overhead in excess of collection. 64 74 65 75 This paper embraces a third path that preserves collection routing, 66 76 leverages the contemporary architecture of resource-poor sensor nodes 67 77 reporting to one (or more) resource-rich root node(s), and provides a 68 pragmatic, evolutionary, and architecturally-principled pathforward.78 pragmatic, evolutionary, and architecturally-principled way forward. 69 79 Our design begins where collection ends: by creating a collection tree 70 80 link state database at the root, itself populated using a collection -
docs/Lowthane/ipsn10/lowthane.tex
r2741 r2751 19 19 %Defines 20 20 \def\lowthane{{Hydro}} 21 \def\LOWTHANE{{HYDRO}} 21 22 \def\Controller{{Border Router}} 22 23 \def\controller{{border router}}
