Changeset 2791

Show
Ignore:
Timestamp:
10/30/09 17:04:00 (4 weeks ago)
Author:
jortiz
Message:

first draft of final copy

Location:
code/Multichannel/docs/mobisys/doc
Files:
10 modified

Legend:

Unmodified
Added
Removed
  • code/Multichannel/docs/mobisys/doc/abstract.tex

    r2713 r2791  
    1313%hopping. 
    1414 
    15 We study the utility of dynamic frequency agility in real-world wireless sensor networks, 
    16 which many view as essential to obtaining reliability in industrial environments. 
    17 We introduce three graph-theoretic objects -- Multichannel Links (MCLs) 
    18 and Multichannel Triangles (MCTs) -- 
    19 that identify instances in the network where considering multiple 
    20 frequencies enables reliable communication.  We examine connectivity graphs 
     15We study the utility of dynamic frequency agility in real-world wireless sensor networks. 
     16Many view such agility as essential to obtaining adequate reliability in industrial environments. 
     17We quantify the actual utility by identifying the two facets of connectivity graph that 
     18yield potential benefits called Multichannel Links (MCLs) and Multichannel Triangles (MCTs), 
     19study how frequently these occur empirically and determine whether multihop provides 
     20a comparable solution without the complexity of switching channels. 
     21We examine connectivity graphs 
    2122of live networks over each 802.15.4 channel and find that MCLs and MCTs 
    2223are extremely rare in practice.  Almost no MCLs are found in any 
    23 connectivity graph while MCTs occur between 0-500 parts per million (ppm). 
     24connectivity graph while MCTs occur between 0-200 parts per million (ppm). 
    2425Furthermore, we show that MCLs are rarely important for routing while each 
    2526MCT has a single-channel routing solution.  We also find that there are channels 
    2627that are always good for connectivity and offer comparable routing costs, with respect 
    2728to transmission count, in comparison to multichannel communication. 
     29Thus, the justification for channel agility in industrial environments applies in the  
     30absence but not in the presence of multihop routing. 
    2831%with the same cost in the expected 
    2932%number of transmissions as the multichannel solution. 
  • code/Multichannel/docs/mobisys/doc/conc.tex

    r1679 r2791  
    33 
    44In this study, we examined the utility of dynamic frequency agility in real-world wireless sensor networks. 
    5 To quantify the need for multichannel we examined Sexton's study on wireless links in the industrial  
    6 environment and pulled out a set of graphical facets, a Sexton Triangle, that could be directly tested for on 
    7 live networks.  We also examined the related artifact, a Sexton Link. 
     5%To quantify the need for multichannel we examined Sexton's study on wireless links in the industrial  
     6%environment and pulled out a set of graphical facets, a Sexton Triangle, that could be directly tested for on 
     7%live networks.  We also examined the related artifact, a Sexton Link. 
     8% 
     9%Our findings establish the following: 
     10% 
     11%\begin{itemize} 
     12%       \item Instances where a multichannel solution is necessary are 
     13%               extremely rare.  The graphical facet -- a Sexton 
     14%               Triangle -- occurs only about 20-50 parts per million (ppm).  
     15%       \item In every instance where a multichannel solution is necessary 
     16%               for directional communication 
     17%               there is a single-channel routing solution available. 
     18%       \item The single-channel routing transmission cost is the same as the  
     19%               multichannel transmission cost.   
     20%\end{itemize} 
     21% 
     22%These results suggest that in the presence of routing, frequency agility is of marginal value 
     23%in improving reliability. 
     24We analyzed the set of assumptions related to the benefit of multichannel with respect to reliable 
     25packet transmission.  We reduced the problem to graph-theoretic facets that are searchable on network 
     26connectivity graphs -- multichannel links and multichannel triangles.  Our results suggest that  
     27MCLs are rare in practice. 
     28Also, when the graph is disconnected, it is disconnected on \emph{every} channel. 
     29We also find that MCTs are extremely rare in practice and that there is a routing solution to every 
     30MCT on a single channel.  We demonstrated this on channel $26$. 
     31Furthermore, free channels are not difficult to find.  We easily determined which 
     32was the good channel. 
    833 
    9 Our findings establish the following: 
     34These results show that, in the well-connected networks, multichannel communication is not necessary 
     35for reliable communication.  The standards bodies recommend the use of well connected networks and  
     36provide a list of rules-of-thumb.  Yet, they also recommend the use of FH, which may only be of marginal 
     37value if the network setup is done correctly. 
    1038 
    11 \begin{itemize} 
    12         \item Instances where a multichannel solution is necessary are 
    13                 extremely rare.  The graphical facet -- a Sexton 
    14                 Triangle -- occurs only about 20-50 parts per million (ppm).  
    15         \item In every instance where a multichannel solution is necessary 
    16                 for directional communication 
    17                 there is a single-channel routing solution available. 
    18         \item The single-channel routing transmission cost is the same as the  
    19                 multichannel transmission cost.   
    20 \end{itemize} 
    21  
    22 These results suggest that in the presence of routing, frequency agility is of marginal value 
    23 in improving reliability. 
  • code/Multichannel/docs/mobisys/doc/intro.tex

    r2713 r2791  
    44Reliability is of great concern for wireless sensing in 
    55industrial settings -- rooms with lots of metal surfaces and rotating 
    6 machinery that make  
     6machinery make  
    77it a harsh environment for radio-frequency (RF) communication.   
    88In~\cite{sexton}, Sexton et al. show that RF signals in this environment 
     
    1414it~\cite{propwireless,fading}, 
    1515these standards bodies have agreed that frequency diversity is absolutely 
    16 necessary to provide high levels of reliable wireless communication. 
     16necessary to provide high levels of reliability in wireless communication. 
    1717 
    18 Beyond the standards groups, there has been much work in the sensornet 
     18Beyond the standards groups, there has been much work in the research 
    1919community to develop multichannel protocols. 
    20 Many are evaluated in simulation~\cite{crowded, mmsn, mcmac_cit2006} while 
    21 others have been implemented and evaluated in practice~\cite{ymac, pracmac,tsmp}.  
    22 Each work states various assumptions about the value of multiple channels, 
     20Many are evaluated in simulation~\cite{mcmac_cit2006,mmsn,crowded} while 
     21others have been implemented and evaluated in practice~\cite{tsmp,ymac,pracmac}.  
     22Each study states various assumptions about the value of multiple channels, 
    2323with some implicit validation.  However, the validation is mostly with respect to  
    2424network capacity.  None of the studies closely examine the contribution of multiple 
    25 channels with respect to reliability. 
     25channels with respect to the primary motivation -- reliability. 
    2626 
    2727%but none evaluate the underlying validity and importance of those assumption.  
     
    3030 
    3131Furthermore, these wireless devices form mesh networks and route over multiple hops. 
    32 Routing is an alternative to frequency diversity in enabling communication among 
    33 devices that cannot communicate directly.  It also provides receiver diversity. 
     32Routing enables communication among devices that cannot communicate directly.   
     33Thus, it is an alternative to frequency diversity even for nodes that are in close 
     34proximity. It also provides receiver diversity. 
    3435In this paper we find frequency diversity is not necessary for high reliability 
    3536in the presence of routing. 
    3637In practice, we show that even on a single channel, route diversity --   
    37 mulitple choices for routing at  
     38multiple choices for routing at  
    3839each hop -- offers the same level of reliability 
    3940% at the same transmission cost 
    4041as the multichannel solution. 
    4142 
    42 To show this we distill the multichannel reliability assumption into two 
     43To show this we distill the multichannel reliability assumption into two observable  
    4344graph-theoretic objects that we can explicitly test for on live networks: 
    4445Multichannel Links (MCLs) and Multichannel Triangles (MCTs).%, and Multichannel Paths (MCPs).   
    4546These objects capture locations  in the network where channel-switching is necessary for  
    46 reliable transmission.  After identifying instances of these objects 
    47 we examine them with respect to routing on a \emph{single channel} to determine if there is routing  
    48 solution. 
     47the reliability of communication.  After identifying instances of these objects 
     48we examine them with respect to routing on a \emph{single channel} to determine if there is  
     49also a routing solution. 
    4950Our results establish the following: 
    5051 
    5152\begin{itemize} 
    5253        \item Although there are many unidirectional links, MCLs --  
    53                 links that are unidirectional or non-existant on some channel 
    54                 and bidirectional on another -- are rare.  This allows 
    55                 for reachability between all nodes in the network through the  
    56                 underlying connectivity graph on every channel. 
     54                links that are unidirectional or nonexistent on some channel 
     55                and bidirectional on another -- are rare.   
     56                %This allows 
     57                %for reachability between all nodes in the network through the  
     58                %underlying connectivity graph on every channel. 
    5759        \item Instances where a multichannel solution is necessary are 
    58                 extremely rare.  The graphical facet, an MCT -- 
    59                 instances in the network where three nodes are pairwise-connected on  
    60                 some channel but there is no single channel that connects all three 
    61                 -- occurs only about 0-500 parts per million (ppm).  
     60                extremely rare.  The graphical facet, an MCT  
     61                %-- 
     62                %instances in the network where three nodes are pairwise-connected on  
     63                %me channel but there is no single channel that connects all three 
     64                %--  
     65                occurs only about 0-200 parts per million (ppm).  
    6266        \item In every instance where a multichannel solution is necessary 
    63                 for directional communication 
     67                for communication 
    6468                there is a single-channel routing solution available. 
    6569        %\item Although MCPs -- paths between nodes that only exist with links 
     
    7680 
    7781This study focuses on communication \emph{reliability}.  That is, the successful 
    78 delivery of data between nodes.   Reliability is a seperate concern from latency and 
     82delivery of data between nodes.   Reliability is a separate concern from latency and 
    7983throughput.  One can obtain perfect reliability with high latency and low throughput 
    80 (i.e. low duty-cycled applications).  Furthermore, we examine the deeper implications,  
    81 trade-offs, and associated costs between single and multichannel communication from a  
     84by re-transmitting forever, but we want to achieve efficient reliability. 
     85Thus, we examine the   
     86trade-offs and associated costs between single and multichannel communication from a  
    8287reliability stand-point. 
    8388To the best of our knowledge this is the first study to systematically assess 
  • code/Multichannel/docs/mobisys/doc/motivation.tex

    r2661 r2791  
    11\section{Motivation} 
    22 
    3 Sensornets are deployed in real-world environments and often 
    4 use batteries as their main power source. 
    5 On mote-class devices, the radio consumes the most energy~\cite{prabalbatch}. 
    6 Therefore, reducing communication cost can significantly lengthen the lifetime of a deployment. 
    7 This section discusses the challenges in efficient packet delivery 
    8 and describes 
    9 general approaches to dealing with the unpredictability of wireless 
    10 signal propagation. 
     3Sensornets are deployed in real-world environments, often 
     4use batteries as their main power source, and 
     5on mote-class devices, the radio consumes the most energy~\cite{prabalbatch}. 
     6Communication cost is essential. 
     7As background, we describe general approaches to dealing with unpredictability 
     8of wireless signal propagation to obtain efficient packet delivery. 
    119 
    1210\subsection{Wireless Propagation} 
    1311 
    14 \begin{figure}[t] 
    15 \begin{center} 
    16 \includegraphics[width=1.0\columnwidth]{../figs/80211_802154_spectrum} 
    17 \caption{This figure shows the 2.4 GHz spectrum interval where both 802.11 
    18 and 802.15.4 radios transmit.  The 802.11 channels shown are used most often 
    19 in planned deployments.  When these are set there are four non-overlapping 
    20 802.15.4 channels.} 
    21 \label{fig:80211_802154_spectrum} 
    22 \end{center} 
    23 \end{figure} 
     12%\begin{figure}[t] 
     13%\begin{center} 
     14%\includegraphics[width=1.0\columnwidth]{../figs/80211_802154_spectrum} 
     15%\caption{This figure shows the 2.4 GHz spectrum interval where both 802.11 
     16%and 802.15.4 radios transmit.  The 802.11 channels shown are used most often 
     17%in planned deployments.  When these are set there are four non-overlapping 
     18%802.15.4 channels.} 
     19%\label{fig:80211_802154_spectrum} 
     20%\end{center} 
     21%\end{figure} 
    2422 
    2523Sensornets are deployed in various types of environments over extended 
    26 periods of time.  As such, they are subject to unpredictable  
     24periods of time and they are subject to unpredictable  
    2725internal and external interference, collisions, physical obstructions, and 
    28 multipath fading.  Furthermore, these 
     26multipath fading.  These 
    2927factors change over time and are non-uniform throughout the network. 
    3028Different parts of the network may experience different phenomena 
    3129that cause the connectivity to vary. 
    3230 
    33 Internal interference occurs when nodes in the same network do not hear one another 
    34 and interfere each other's transmission.  Collisions are a form of internal  
     31Internal interference may occur when nodes in the same network transmit simultaneously. 
     32Collisions are a form of internal  
    3533interference -- multiple senders, within transmission distance of one another, transmitting 
    3634simultaneously to the same receiver -- and is avoided with 
    3735Carrier Sense Multiple Access (CSMA).  However, hidden terminal problems 
    3836may occur and CSMA does not solve the problem entirely.  
    39 Internal interference can be largely avoided by scheduling all transmissions  
    40 in the network, known as time-division multiple access (TDMA).  Still, if the schedule is 
    41 not unique for all nodes, TDMA remains susceptible. 
     37Internal interference can be largely avoided by scheduling transmissions  
     38in the network (e.g. time-division multiple access (TDMA)).   
    4239 
    4340External interference occurs when devices outside the network generate RF 
    44 that interferes with transmissions in the network.  
    45 For example, 802.11 shares the same RF frequency range as 802.15.4 
    46 (shown in Figure~\ref{fig:80211_802154_spectrum}).  When a mote and an 802.11 client 
    47 transmit on any overlapping frequency simultaneously, interference may occur.  Microwaves,  
    48 chordless phones 
     41signals that prevent reception.  
     42For example, 802.11 shares the same RF frequency range as 802.15.4.  
     43%(shown in Figure~\ref{fig:80211_802154_spectrum}).   
     44When a mote and an 802.11 client 
     45transmit on any overlapping frequency, simultaneously, interference may occur.  Microwaves,  
     46cordless phones 
    4947and Bluetooth devices also transmit RF signals in the same frequency range 
    5048and serve as external interferers to 802.15.4 networks. 
     49In industrial environments there may be many unintended source of RF interference. 
    5150 
    52 Mote placement also contributes to loss. Non-line-of-site  
    53 (NLOS) transmission causes a signal to fade faster as it bounces off surfaces in the environment lengthening 
    54 the distance the signal propagates and weakening its strength by time it reaches the receiver.   
     51Placement also contributes to loss.  When there is Non-line-of-site  
     52(NLOS) communication, signals bounce off surfaces in the environment lengthening 
     53the propagation distance, weakening its strength by time the signal reaches the receiver.   
    5554Moreover, reflections can cause destructive interference in certain locations 
    5655and these locations change with changes in the environment. 
     
    6160\subsection{Diversity Helps} 
    6261 
    63 To improve comunication robustness and reliability,  we introduce diversity  
    64 in time, space, and frequency.  Time diversity involves transmission retries and 
    65 is implemented with a maximum bound (i.e. maximum of three retries).  The medium access control  
    66 (MAC), network, and transport 
    67 layers, may all implement retries.  This allows the system to hide  
    68 much of the underlying packet delivery uncertainty.  
     62To improve communication robustness and reliability,  diversity  
     63in time, space, and frequency is utilized.  Time diversity involves transmission retries.   
     64The link , network, and transport 
     65layers, may all implement retries.   
    6966 
    70 Spatial diversity transforms the propogation phenomenon that causes multipath fading into 
     67Spatial diversity transforms the propagation problem that causes multipath fading into 
    7168a feature by using either multiple antennas or various choices for receivers in 
    7269the network.  Multiple-input multiple-output (MIMO) technology uses  
     
    7875 
    7976Frequency diversity is used in various forms at different layers of the communication 
    80 stack.  Modulation techniques such as direct-sequence spread spectrum (DSSS) and phase-shift 
    81 keying (PSK), are used at the physical layer in order to minimize the effects of noise 
    82 on a given channel.  Radios may also use frequency-hopping spread spectrum (FHSS). 
    83 The sender and receiver share the same pseudorandom frequency-hop sequence in order to 
    84 communicate across multiple channels.  Most multichannel MACs run on radios  
    85 using wideband modulation techniques and provide the additional frequency diversity at the  
    86 MAC layer.  Diversity helps to hide the wireless communication errors.  
     77stack.  Modulation techniques, such as direct-sequence spread spectrum (DSSS), are used  
     78at the physical layer in order to minimize the effects of noise 
     79on a given channel.  Radios may also use frequency-hopping spread spectrum (FHSS) 
     80to communicate using multiple channels. 
     81%The sender and receiver share the same pseudorandom frequency-hop sequence in order to 
     82%communicate across multiple channels.   
     83Most multichannel MACs run on radios using wideband modulation techniques and provide  
     84the additional frequency diversity by explicit channel hopping at the link layer.  
     85 
     86Diversity helps to hide the wireless communication errors.  
    8787However, it is not clear how much each level of diversity improves communication reliability, 
    8888as many of the mechanisms are redundant. 
    89  
    90 Early version of the 802.11 standard used FHSS~\cite{80211_fhss}.  However, studies 
     89Early versions of the 802.11 standard used both FHSS and DSSS.  However, studies 
    9190indicated 802.11 FHSS did not coexist well with other FHSS systems~\cite{80211_bluetooth}  
    92 and the standard eventually changed the modulation scheme to DSSS~\cite{80211_standard}. 
     91and the standard eventually changed the modulation scheme to only DSSS~\cite{80211_standard}. 
    9392 
    9493\subsection{Standardization} 
     
    9695Three standards bodies have formed to address some of the issues just discussed (mostly in the context 
    9796of WSN deployments in industrial settings).   
    98 In their proposals~\cite{802154e_ppt, whart} and standards~\cite{sp10011a}, they introduce many forms 
     97In their proposals~\cite{15_4e, whart} and standards~\cite{sp10011a}, they introduce many forms 
    9998of diversity.  One is frequency diversity and the other is receiver diversity.  Many reasons are 
    10099given to justify each level of redundancy.  With largely overlapping sets of goals, we 
    101100examine the reasons more closely and analyze the underlying assumptions and related issues. 
    102101 
    103 Since the goals of the standards bodies are largely overlapping, so are the mechanisms to facilitate them. 
    104 They include reliabile packet delivery, long deployment lifetime, adjustable quality-of-service (QoS),  
    105 and fault tolerance.  However, some goals are fundamentally at odds in their extreme, so the  
    106 mechanisms that are used must be composed such that the system performance falls in the right region  
    107 in the trade-off space.  Several claims can be pulled directly from the standards documents and  
     102The goals of the standards efforts are include reliable packet delivery, long deployment lifetime,  
     103adjustable quality-of-service (QoS),  
     104and fault tolerance.  However, some goals are fundamentally at odds in their extreme, so  
     105mechanisms are proposed to provide a compromise. 
     106Several claims can be pulled directly from the standards documents and  
    108107associated presentations. 
    109108 
    110 % FH by iteself 
     109% FH by itself 
    111110First, it is stated that ``channel hopping [is used] to provide a level of immunity against interference 
    112111from other RF devices operating in the same band, as well as robustness to mitigate multipath interference 
     
    119118\end{enumerate} 
    120119 
    121 If these are the communication conditions then frequency-hopping (FH) \emph{may} help.  FH may be of no help 
     120If these communication conditions hold then frequency-hopping (FH) \emph{may} help.  FH may be of no help 
    122121if it switches to another congested channel or may even \emph{hurt} performance by switching from a good 
    123 channel to a congested one. 
     122channel to a congested one.  The non-zero cost of switching is wasted when there is nothing to send. 
    124123 
    125124% FH + mesh + TDMA 
    126125Second, they explicitly state the use of TDMA ``to allow a device to access the RF medium without having to 
    127126wait for other devices''~\cite{sp10011a} and multihop mesh networking to ``support end-to-end network  
    128 reliability in the face of changing RF and environmental conditions''~\cite{sp10011a}.  TDMA prevents 
    129 collisions when two senders want to send to the same receiver, however, it is still susceptible to 
     127reliability in the face of changing RF and environmental conditions''~\cite{sp10011a}.  TDMA  
     128does reduce internal interference by explicitly causing devices to wait.  Local scheduling 
     129is sufficient to prevent collisions to a common receiver but more global scheduling is required to avoid 
     130hidden terminals.  Still external interference remains.  FH is natural to include with TDMA but is 
     131orthogonal and does not come for free.  The more sparse the channel usage, the more costly is the join 
     132operation. 
     133TDMA prevents 
     134collisions when two senders want to send to the same receiver but is still susceptible to 
    130135hidden and exposed terminal problems, as well as external interference.  Multihop mesh networking 
    131 provides a way to route over the underlying connectivity graph. 
    132 It is important to note that reliability, when routing over multiple hops, is about reachability in the  
    133 graph.  This is important to consider, as FH fundamentally affects the perceived connectivity 
    134 graph, which may also affect overall reliability. 
     136allows for communication between nodes that are not directly connected for reasons of distance 
     137or interference. 
     138It is important to note that reliability, when routing over multiple hops is about reachability in the  
     139connectivity graph.  This is important to consider, as FH fundamentally affects the available connectivity 
     140graph, which may also affect overall reliability.  Section~\ref{subsec:other_costs} examines the effects 
     141of FH on the connectivity graph and link quality. 
    135142 
    136 % Contraints -- battery life, predictability 
    137 Third, we pull out a statement about the constraints, not the underlying assumptions.  Each standard's goals 
     143% Constraints -- battery life, predictability 
     144Third, each standard's goals 
    138145includes a network lifetime constraint.  802.15.4e states that they wish to obtain ``long operational life 
    139 for battery powered device ($>$ 5 years)''~\cite{802154e_ppt}.  This has deep implications on protocol 
     146for battery powered device ($>$ 5 years)''~\cite{15_4e}.  This has deep implications on protocol 
    140147efficiency.  Given a fixed energy budget and lifetime constraints, 
    141 you want to maximize the transmit efficiency.  How does FH affect the  
     148we want to maximize the transmit efficiency.  How does FH affect the  
    142149communication efficiency and how does it compare with the single-channel case? 
    143  
    144 %The next study played an important role establishing the ground-truth for adding FH to the standard(s). 
    145 The next section discusses an important study that played a role in the ISA standard, SP100.11a.  The authors 
    146 examine the behavior of wireless links in industrial environments and recommends the use of various forms 
    147 of diversity -- FH being one of them.  We revisit the results of the study and argue that the conclusions 
    148 would have been different had they considered routing as an alternative to FH. 
    149  
    150150 
    151151 
    152152%The reliability argument is supported by several studies~\cite{sexton, propwireless, fading} characterizing 
    153 %link behavior and signal propogation properties.  These findings, coupled with the strict 
     153%link behavior and signal propagation properties.  These findings, coupled with the strict 
    154154%delivery requirements in industrial settings, have motivated the formation of several standards bodies. 
    155155%These standard bodies --  802.15.4e~\cite{15_4e}, SP100.11a~\cite{sp10011a}, and WirelessHART~\cite{whart} -- 
     
    157157%and use frequency diversity (as per the recommendation in~\cite{sexton}) to improve communication predictability  
    158158%while extracting all the data from the network successfully.  The reliability argument based entirely on the  
    159 %studies cited, however none of the studies considers the effects of route diversity for reliabile communication 
     159%studies cited, however none of the studies considers the effects of route diversity for reliable communication 
    160160%in a multihop wireless mesh network setting -- typical for sensornet deployments in industrial and  
    161161%non-industrial settings alike. 
  • code/Multichannel/docs/mobisys/doc/references.bib

    r1714 r2791  
    699699} 
    700700 
    701 @misc{80211_fhss, 
    702         title = "IEEE 802.11 wireless lan medium access control (MAC) and physical 
    703                 layer (PHY) specifications.", 
    704         author={IEEE} 
    705         year = {1999}, 
    706 } 
    707  
    708701@INPROCEEDINGS{80211_bluetooth, 
    709702        title={Throughput of IEEE 802.11 FHSS networks in the presence of strongly interfering Bluetooth networks}, 
     
    18231816} 
    18241817 
    1825 @misc{cc2420_datasheet, 
    1826   title = "Chipcon CC2420.  CC2420 2.4 GHz IEEE 802.15.4/Zigbee-ready RF Transceiver Datasheet.", 
    1827   note = "\url{http://focus.ti.com/lit/ds/symlink/cc2420.pdf}" 
    1828 } 
    1829  
    18301818@article{SunlightModel, 
    18311819  author = "Jaein Jeong",  
  • code/Multichannel/docs/mobisys/doc/related.tex

    r1679 r2791  
    22\label{sec:related} 
    33 
    4 With the increased ubiquity of wireless communication and the ever 
    5 increasing saturation of the wireless spectrum, there has been a gold-rush 
    6 effect in networking research communities to explore the multichannel 
    7 protocol design space.  In the 802.11 research community there have 
    8 been numerous publications in theory~\cite{optimal_mcmac,mcmac_eval}, 
    9 simulation~\cite{so03multichannel,ssch, apclient-driven},  
    10 and practice~\cite{freemac,aptraffic-aware,apcoloring}. 
     4%There has been a gold-rush 
     5%effect in networking research community to explore the multichannel 
     6%protocol design space.  In the 802.11 research community there have 
     7%been numerous publications in theory~\cite{optimal_mcmac,mcmac_eval},  
     8%simulation~\cite{ssch,so03multichannel}, %, apclient-driven},  
     9%and practice~\cite{aptraffic-aware,apcoloring}%freemac,apcoloring}. 
    1110 
    12 %In the 802.11 research community, scientists 
    13 %and engineers have been studying the ways to use frequency diversity 
    14 %to increase throughput by decreasing losses related to internal 
    15 %interference (in-network interference), external interference (micorwave, 
    16 %phones, etc), and increase throughput by decreasing competition among nodes  
    17 %in the same collision domain (increased spatial reuse).  There have 
    18 %been numerous publications theory~\cite{optimal_mcmac,mcmac_eval}, 
    19 %simulation~\cite{so03multichannel,ssch, apclient-driven},  
    20 %and practice~\cite{freemac,aptraffic-aware,apcoloring}. 
    21  
    22 %In 802.11-hotspot 
    23 %locations where competition among clients and access points (AP) is high, 
    24 %several protocol proposals have been made~\cite{apcoloring,apclient-driven, 
    25 %aptraffic-aware} to increase the throughput seen per client. 
    26 %Furthermore, with the proposal to use 802.11 devices in multihop, mesh 
    27 %networks, there has been much work in multichannel MAC protocols 
    28 %and their evaluation in theory~\cite{optimal_mcmac,mcmac_eval}, 
    29 %simulation~\cite{so03multichannel,ssch}, and  
    30 %practice~\cite{freemac}. 
    31  
    32 %Naturally, multichannel research moved into the low-power wireless  
    33 %sensor networking community.  However,  
    34 The transition of multichannel MAC protocols into sensor networks  
    35 has not been straight-forward because of the fundamental differences between  
    36 802.11 and 802.15.4.  802.11 network devices are either plugged 
    37 into a power source or recharged daily (laptops, smart phones, etc) and 
    38 have radios that are always on. 
    39 802.15.4 devices run at a much lower transmission power and generally run at very  
    40 low  duty cycles (between 1-7\%)~\cite{prabalbatch}. 
    41 %in environments where energy is scarce the radio frequency environment is harsh.   
    42 802.11 radios transmit with more power and are more sophisticated than low-power 
    43 802.15.4 radios, such at the CC2420~\cite{cc2420}.  802.11 wireless networks 
    44 handle streaming data while most 802.15.4 networks transmit small amounts  
    45 of data once every dozens of minutes. 
    46  
    47 While much effort in the sensornet community has  
    48 focused on link characterization~\cite{betafactor, SrinivasanDTL06,ZhouHKS06,lof,zuniga_trans}  
    49 and estimation~\cite{prabalbatch,rodrigo4bit} in the context 
    50 of a single channel, these efforts have led to the most recent work in multichannel 
    51 MAC protocols~\cite{crowded, mmsn, mcmac_cit2006,ymac, pracmac}. 
    52 Since energy consumption is of highest priority and communication comsumes the most 
    53 energy, reliability and efficiency is of utmost importance. 
    54 Therefore, the focus of multichannel work has been to increase packet-delivery 
     11In sensornets, energy consumption is of highest priority and communication comsumes the most 
     12energy. Therefore reliability and efficiency is of utmost importance. 
     13The focus of multichannel work has been to increase packet-delivery 
    5514reliability.  Throughput is a secondary goal as sensor networks mostly 
    5615transmit at very low data rates and operate at low duty cycles. 
     16Several multichannel MACs have been built and studied for sensornets~\cite{mcmac_cit2006, 
     17ymac, pracmac, mmsn,crowded}. 
    5718 
    5819Y-MAC~\cite{ymac} and the Time Synchronized Mesh Protocol (TSMP)~\cite{tsmp} --  
     
    7839to achieve better reliability.   
    7940 
    80 Multipath is not the only problem for 802.15.4 networks.  802.11 interference 
    81 is also a concern as both types of radios transmit in the same frequency 
    82 and have channels that directly overlap, as shown in  
    83 figure~\ref{fig:80211_802154_spectrum}.  A few multichannel schemes have been  
    84 developed to minimize the effects of 802.11 intereference~\cite{80211_80154_testreport,  
    85 802_11_154_razvan, coexist_80211_802154}. 
    86  
    87 There is no doubt that real-world RF behavior is unpredictable and that link qualities 
    88 can vary quite drastically over time, space, and frequency.  However, fundamentally, 
     41Real-world RF behavior is unpredictable and that link qualities 
     42can vary over time.  However, fundamentally, 
    8943protocols are constructing connectivity graphs over which to perform routing. 
    9044We contend that RF and link qualities should not be evaluated in isolation.  Instead,  
  • code/Multichannel/docs/mobisys/doc/report.tex

    r2688 r2791  
    6060%\crdata{978-1-60558-096-8/08/09}  
    6161 
    62 \title{Cost-Benefit Evaluation of Multiple Channels in Real World WSNs} 
     62%\title{Cost-Benefit Evaluation of Multiple Channels for Reliability in Real World WSNs} 
     63\title{Multichannel Reliability Assessment in Real World WSNs} 
    6364 
    6465%\title{Alternate {\ttlit ACM} SIG Proceedings Paper in LaTeX 
     
    133134\input{setupandmeth} 
    134135\input{results} 
    135 %\input{related} 
     136\input{related} 
    136137%\input{notes} 
    137138%\input{methodology} 
  • code/Multichannel/docs/mobisys/doc/results.tex

    r2713 r2791  
     1\begin{figure*}[!tbh] 
     2\centering 
     3\subfigure[Links found in the industrial setting.]{ 
     4\includegraphics[width=0.3\textwidth]{../figs/basement_sextonlinks_view2} 
     5\label{fig:basement_sextonlinks} 
     6} 
     7\subfigure[Links found in the computer room.]{ 
     8\includegraphics[scale=0.33]{../figs/machineroom_sextonlinks_view2} 
     9\label{fig:machineroom_sextonlinks} 
     10} 
     11\subfigure[Links found on the tested.]{ 
     12\includegraphics[scale=0.33]{../figs/testbed_sextonlinks_view2} 
     13\label{fig:testbed_sextonlinks} 
     14} 
     15\caption[Optional caption for list of figures]{ 
     16%A subset of the MCLs found in each environment.   
     17Properties found in these links match those found in each industrial setting examined in~\cite{sexton}. 
     18However, we observe much wider bands of fading links. 
     19} 
     20\label{fig:expsextonlinks} 
     21\end{figure*} 
     22 
    123\section{Experimental Results} 
    224\label{sec:results} 
     
    1638%For each MCT there exists a routing solution of comparable cost. 
    1739 
    18 \begin{figure*}[!tbh] 
    19 \centering 
    20 \subfigure[Links found in the industrial setting.]{ 
    21 \includegraphics[scale=0.33]{../figs/basement_sextonlinks_view2} 
    22 \label{fig:basement_sextonlinks} 
    23 } 
    24 \subfigure[Links found in the computer room.]{ 
    25 \includegraphics[scale=0.33]{../figs/machineroom_sextonlinks_view2} 
    26 \label{fig:machineroom_sextonlinks} 
    27 } 
    28 \subfigure[Links found on the tested.]{ 
    29 \includegraphics[scale=0.33]{../figs/testbed_sextonlinks_view2} 
    30 \label{fig:testbed_sextonlinks} 
    31 } 
    32 \caption[Optional caption for list of figures]{ 
    33 %A subset of the MCLs found in each environment.   
    34 Properties found in these links match those found in each industrial setting examined in~\cite{sexton}. 
    35 However, we observe much wider bands of fading links. 
    36 } 
    37 \label{fig:expsextonlinks} 
    38 \end{figure*} 
    39  
    40  
    4140Figure~\ref{fig:expsextonlinks} shows the equivalent of the connectivity measurements in \cite{sexton} 
    4241for our test environments.  Since we have many more nodes in our networks, in the figure 
     
    4544connectivity is nearly perfect on some channels while there is almost no connectivity on others.   
    4645The band of this fading is much less 'narrow' than in the Sexton study.  In general, there is  
    47 less connectivity between our nodes.  This does imply that the toplogy of connectivity seen 
     46less connectivity between our nodes.  This does imply that the topology of connectivity seen 
    4847on one channel may be very different from that on other channels, which is likely to have 
    4948a serious impact of routing protocols that use multiple channels.  Below we study the  
    50 observed connectivity under these graphs in much greater detail. 
     49observed connectivity under these graphs in greater detail. 
    5150 
    5251\subsection{Multichannel Links in Practice} 
    5352\label{subsec:sextonlinksexp} 
    5453 
    55 Asymmentric links are indeed common in our networks.  The number of them also and varies substantially  
     54Asymmetric links are indeed common in our networks.  The number of them also and varies substantially  
    5655by node placement, channel, link-quality threshold, and time.  We define a link between 
    5756a pair of nodes as unidirectional if the PRR is greater than some threshold, $T$, in one direction  
    58 and less than $T$ in the other.  Although this may seem weak, it is effectively what occurs when 
    59 a protocol sets a maximum transmission count.  For example, a maximum transmission count of 3 
    60 implies a threshold of 33\% PRR. 
    61  
    62 In examining our connectivity graphs in all environments and thresholds between $T=1$ and $T=90$ (with 
    63 a step of 10), we observed that 32-36\% of the links in the machine room are 
    64 unidirectional, 18-34\% of the links in the computer room are undirectional, and 10-46\% of  
     57and less than $T$ in the other.  Although stranger criteria would be require a difference 
     58of $\epsilon$ around threshold $T$, we allow even a small difference to be most generous to the 
     59prevalence of situations where FH provides benefit.  The vast majority of potential links 
     60lie far from the threshold regardless. 
     61 
     62%Although this may seem weak, it is effectively what occurs when 
     63%a protocol sets a maximum transmission count.  For example, a maximum transmission count of 3 
     64%implies a threshold of 33\% PRR. 
     65 
     66In examining our connectivity graphs in all environments and thresholds between $T=1$ and $T=90$ with 
     67a step of 10, we observed that 32-36\% of the links in the machine room are 
     68unidirectional, 18-34\% of the links in the computer room are unidirectional, and 10-46\% of  
    6569the links on the testbed are unidirectional.   
    6670%These ranges are for all links and all runs 
     
    8993sparse networks.  
    9094 
    91 This may also suggest a small grey region in our deployments~\cite{zhao, SrinivasanDTL06}  
     95This may also suggest a small gray region in our deployments~\cite{zhao,zuniga_trans}  
    9296-- locations in the network where connectivity 
    9397between the sender and receiver are at the edge of radio connectivity.  Generally, the 
    94 population of links in the grey region is small, since reliable communication 
    95 is desirable and grey-region links have more unpredictable link quality~\cite{churn}.  Sparser networks  
     98population of links in the gray region is small, since reliable communication 
     99is desirable and gray-region links have more unpredictable link quality~\cite{churn}.  Sparser networks  
    96100have more links at the edge of network connectivity 
    97101and thus there may be some links that are above the goodness threshold on some channels 
     
    116120 
    117121This may indicate much wider noise correlation across channels in the operating frequency band.  This also 
    118 directly addresseses the assumption made in the standards about FH's ability to avoid interference.  It can only 
     122directly addresses the assumption made in the standards about FH's ability to avoid interference.  It can only 
    119123improve reliability if there is an opportunity to transmit on \emph{some} channel that is interference free.   
    120124According to our data,  that opportunity is quite rare.  Furthermore, this number is 
     
    127131%graphs that were disconnected and there exists a connected multichannel graph. 
    128132 
    129 %disconnected graph occured on channel 17 and only a single node was disconnected.  However, the missing 
     133%disconnected graph occurred on channel 17 and only a single node was disconnected.  However, the missing 
    130134%edge is not a member of an MCT, although it exists on other channels.  Therefore a multichannel solution 
    131135%exists where a single-channel solution does not.  In order to capture these instances in the network, we 
    132 %examine the prevalence of Mulichannel Paths (MCPs). 
     136%examine the prevalence of Multichannel Paths (MCPs). 
    133137 
    134138 
     
    169173 
    170174%From our data we were able to match the results found by Sexton et al.  However, this is not enough to declare 
    171 %frequency diversity indepensible.  In order to get a better understanding of value for frequency agility in 
     175%frequency diversity indispensable.  In order to get a better understanding of value for frequency agility in 
    172176%real networks, we have to examine cases where routing may be problematic.  In order to do this we examine 
    173177%the second piece of the assertion, namely, the existence of MCTs. 
     
    181185%In addition to this evaluation, we must also consider whether multichannel is the best or only solution 
    182186%to communicate data over an MCT.  Therefore, we also examine how often we can communicate to each node 
    183 %by simply considering the existence of a route path the includes all the nodes in the the instance of  
     187%by simply considering the existence of a route path the includes all the nodes in the instance of  
    184188%an MCT.  We present the details of this analysis in section~\ref{sec:routingresults}. 
    185189 
     
    191195\centering 
    192196\subfigure[Machine room multichannel triangle-set count.]{ 
    193 \includegraphics[angle=90,scale=0.14]{../figs/basement_mctrigs} 
     197\includegraphics[scale=0.26]{../figs/basement_mctrigs} 
    194198\label{fig:basement_mc_demo} 
    195199} 
    196200\subfigure[Machine room triangle-set count.]{ 
    197 \includegraphics[angle=90,scale=0.14]{../figs/basement_sextontrigs} 
     201\includegraphics[scale=0.26]{../figs/basement_sextontrigs} 
    198202\label{fig:basement_sexton_demo} 
    199203} 
    200204\subfigure[Computer room multichannel triangle-set count.]{ 
    201 \includegraphics[angle=90,scale=0.14]{../figs/machineroom_mctrigs} 
     205%\includegraphics[angle=90,scale=0.14]{../figs/machineroom_mctrigs} 
     206\includegraphics[scale=0.26]{../figs/machineroom_mctrigs} 
    202207\label{fig:machineroom_mc_demo} 
    203208} 
    204209\subfigure[Computer room MCT-set count.]{ 
    205 \includegraphics[angle=90,scale=0.14]{../figs/machineroom_sextontrigs} 
     210\includegraphics[scale=0.26]{../figs/machineroom_sextontrigs} 
    206211\label{fig:machineroom_sexton_demo} 
    207212} 
    208213\subfigure[Testbed multichannel triangles.]{ 
    209 \includegraphics[angle=90,scale=0.14]{../figs/motescope_run3_mctrigs} 
     214\includegraphics[scale=0.26]{../figs/motescope_run3_mctrigs} 
    210215\label{fig:testbed_mc_demo} 
    211216} 
    212217\subfigure[MCTs on with N hop solution on testbed.]{ 
    213 \includegraphics[angle=90,scale=0.14]{../figs/motescope_run3_sextontrigs_diffchans} 
     218\includegraphics[scale=0.26]{../figs/motescope_run3_sextontrigs_diffchans} 
    214219\label{fig:testbed_sexton_demo} 
    215220} 
     
    223228and all thresholds.  As a working example, when the threshold is set to 50\%,  
    224229the diameter of the machine room network is between 5-6 hops, the diameter of the computer room 
    225 is between 2-3 hops and the diamter of the testbed is between 3-4 hops. 
     230is between 2-3 hops and the diameter of the testbed is between 3-4 hops. 
    226231 
    227232%In order to count MCTs, we first had to construct a connectivity graph on each 
    228 %channel.  To do this we set the link PRR threhold to 50\% and remove all links that are not bi-directional. 
     233%channel.  To do this we set the link PRR threshold to 50\% and remove all links that are not bi-directional. 
    229234%The 50\% threshold was set arbitrarily, however, in section~\ref{subsec:thresholding} we see that our results 
    230235%hold true no matter what threshold is chosen.  The reason we include only bi-directional links 
     
    233238%implemented at some layer of the stack (software or hardware). 
    234239%The diameter of the machine room network is between 5-6 hops, the diameter of the computer room 
    235 %is between 2-3 hops and the diamter of the testbed is between 3-4 hops. 
     240%is between 2-3 hops and the diameter of the testbed is between 3-4 hops. 
    236241 
    237242% What's the diameter of the network? 
    238243 
    239 %Sexton triangle demonstration in Industrial envrionment. 
     244%Sexton triangle demonstration in Industrial environment. 
    240245 
    241246Figure~\ref{fig:basement_mc_demo} and figure~\ref{fig:basement_sexton_demo} show the set of non-unique multichannel 
     
    263268\label{fig:testbed_mctrates} 
    264269} 
    265 \label{fig:mcts_thresh_distro} 
    266270\caption[Optional caption for list of figures]{MCT occurrence rate distribution for all experimental 
    267271runs and link-quality thresholds.} 
     272\label{fig:mcts_thresh_distro} 
    268273\end{figure*} 
    269274 
    270275Figure~\ref{fig:mcts_thresh_distro} summarizes our results. The boxplot shows the distribution of MCT 
    271276occurrence rates for each run and threshold.  Observe that for all three environments, the MCT occurrence rate 
    272 is extremely small.  The rates range from 0-550 ppm.  This indicates that MCTs are actually not that 
     277is extremely small.  The rates range from 0-200 ppm.  This indicates that MCTs are actually not that 
    273278important to consider if your deployment is provisioned to be connected on a single channel -- since 
    274279they occur so infrequently. 
    275 Also observe the effects of thresholding on the MCT occurrence rate.  The general trend indicates that 
    276 as the threshold increases, the rate of MCT occurrence increases by a multiplicative factor. 
    277 In the machine room, the average rate increases by a factor of 10 from $T=1$ to $T=80$.  The general  
    278 trend repeats in the computer room and the testbed.  In the latter, the rate increases by a factor 
    279 of 3 from $T=80$ to $T=90$. 
    280  
    281 This results is rather counter-intuitive.  Initially, one might expect to observe more MCTs as the link population 
    282 admits more grey-region links.  However, it is pricisely because of this that it MCTs are not found. 
    283 Although there are many more non-unique multichannel triangles, the likelihood of an MCT decreases as the link 
    284 choices increase since there are more choices for communication on every channel.  The reason it rises 
     280Also observe the effects of thresholding on the MCT occurrence rate.  In the machine room, the occurrence 
     281rate increases by almost a factor of 6 from $T=1$ to $T=80$. Only 2 MCTs were found in the computer room 
     282and the testbed did not significant variations. 
     283 
     284%The general trend indicates that 
     285%as the threshold increases, the rate of MCT occurrence increases by a multiplicative factor. 
     286%In the machine room, the average rate increases by a factor of 10 from $T=1$ to $T=80$.  The general  
     287%trend repeats in the computer room and the testbed.  In the latter, the rate increases by a factor 
     288%of 3 from $T=80$ to $T=90$. 
     289 
     290%This results is counter-intuitive.   
     291Initially, one might expect to observe more MCTs as the link population 
     292admits more gray-region links.   
     293%However, it is precisely because of this that MCTs are not found. 
     294%Although there are many more non-unique multichannel triangles, the likelihood of an MCT decreases as the link 
     295%choices increase since there are more choices for communication on every channel.   
     296The reason it rises 
    285297so sharply is related to the link population distribution.  A vast majority of the link population is either 
    286 really high quality or really poor (non-existant).  This is often referred to as a bimodal link distribution. 
    287 As the threshold increases, we start excluding more and more links from the population at a faster rate  
     298very high quality or very poor (nonexistent), i.e. a bimodal distribution. 
     299As the threshold increases, we exclude more links from the population at a faster rate  
    288300(for all the links on the ``good'' portion of the bimodal distribution). 
     301On the testbed, this is not as pronounced. 
    289302 
    290303Another interesting observation is the differences in the MCT occurrence rates across the three environments. 
     
    303316%MCTs are extremely rare in our industrial facility. 
    304317% 
    305 %The network diameter changes as a function of threshold, as does the population of links in the grey region 
     318%The network diameter changes as a function of threshold, as does the population of links in the gray region 
    306319%of connectivity~\cite{SrinivasanDTL06, ZhouHKS06, churn}.  As the number of nodes in at the edge of connectivity 
    307320%decrease one might expect for the instance of MCTs to also decrease as the set of links 
    308321%in the population improve in quality by definition.  By setting the threshold at 50\% we include links 
    309 %that usually fall this is grey region.  In section~\ref{subsec:thresholding} we show that changing the threshold  
     322%that usually fall this is gray region.  In section~\ref{subsec:thresholding} we show that changing the threshold  
    310323%does not affect the results. 
    311324 
     
    345358%that they are common, we did not find this to be true in our environments.  It is also interesting that 
    346359%the rate at which they occur was actually \emph{higher} in the testbed than either of the other two environments. 
    347 %The effects of having more nodes, with a larger set of nodes in the grey region, and significant  
     360%The effects of having more nodes, with a larger set of nodes in the gray region, and significant  
    348361%802.11 interference may all contribute to this finding.  Still, the rate of occurrence of an MCT is 
    349362%extremely small and calls to question the motivation for multichannel for reliability. 
     
    378391\begin{table} 
    379392\centering 
     393\begin{small} 
    380394\begin{tabular}{|c|c|c|c|} \hline 
    381395\textbf{Run ID}&\textbf{MCTs}&\textbf{2-Hop}&\textbf{N-hop}\\ \hline 
     
    39841217 &   81  &  75&     6 \\ \hline 
    399413\end{tabular} 
    400 \caption{Routing Solutions on Testbed.} 
     414\end{small} 
     415\caption{Routing solutions on testbed with threshold set at 50.} 
    401416\label{tab:testbedroutingsoln} 
    402417\end{table} 
     
    405420\subsubsection{Channel Distribution} 
    406421Table~\ref{tab:testbedroutingsoln} shows the associated routing solution count for each MCT found on 
    407 testbed ($T=50$).  Notice, every MCT has a single-channel routing solution.  Furthmore, the vast majority  
     422testbed ($T=50$).  Notice, \emph{every MCT has a single-channel routing solution}.  The vast majority  
    408423of routing solutions are two hops in length.  Similar results are seen for all thresholds in each 
    409424all environments tested.  This demonstrates that there is \emph{some channel} channel that provides 
     
    411426that is good for the entire network to use. 
    412427 
    413 Due to a lack of space, we did not include the channel distribution graph.  However, we observe that 
    414 there are route solutions on every channel where the MCT has an edge.  Furthermore, as stated earlier, 
     428We observe that the channel distribution graph shows that every channel where an MCT has an edge 
     429there is also a route solution. 
     430Furthermore,  
    415431the machine room and computer rooms connectivity graphs were connected for all experimental runs 
    416 and the testbed was connected over 98\% of the time.  This means that every channel was good for routing 
    417 almost all the time, except on the testbed.  Even on the testbed, channels 25, and 26 were free 
    418 and connected the entire time, for all runs and all experiments. 
    419 Finding the best communication channel might be easier than expected.  With a spectrum analyzer and 
     432and the testbed was connected over 98\% of the time.  On the testbed, channels 25 and 26 were free,  
     433for all runs and all experiments. 
     434Finding the best communication channel was easier than expected.  With a spectrum analyzer and 
    420435an engineered network deployment (i.e. Wireless HART's recommendation to have 3 neighbors per node),  
    421 one can choose a single channel over which to route over reliably for the lifetime of the network. 
     436one can choose a single channel over which to route over, reliably, for the lifetime of the network. 
    422437 
    423438%The channel distribution graphs show the total number of routing solutions (2, 3, and n-hop) on 
     
    455470%\end{figure*} 
    456471 
    457 In this section we take a closer examination of the use of routing in cases where an MCT is present. 
     472%In this section  
     473We take a closer examination of the use of routing in cases where an MCT is present. 
    458474In our evaluation, we make two important assumptions. First, we assume 
    459475expected transmission count (ETX) can serve as a proxy for energy consumption.  Second, 
     
    485501\begin{figure}[!tb] 
    486502\centering 
    487 \includegraphics[width=\columnwidth,scale=0.25]{../figs/2hopdemo} 
    488 \caption{Two-Hop single-channel solutions in a Multichannel Triangle instance. 
     503\includegraphics[scale=0.25]{../figs/2hopdemo} 
     504\caption{Two-hop single-channel solutions in a Multichannel Triangle instance. 
    489505} 
    490506\label{fig:routingdemo} 
     
    579595\label{fig:testbed_cost_cdf} 
    580596} 
    581 \label{fig:routingcosts} 
    582597\caption[Optional caption for list of figures]{Single-channel to multichannel communication cost ratio 
    583 comparison.} 
     598comparison.  The connectivity graph constructed with threshold T=50 and the routing channel is 26. 
     599} 
     600\label{fig:costratios} 
    584601\end{figure*} 
    585602 
     
    593610%case. 
    594611 
    595 Figure~\ref{fig:routingcosts} and ~\ref{tab:costratio_machine} shows the routings costs for all 
     612Figure~\ref{fig:costratios} shows the routings costs for all 
    596613routing solutions in the each of our environments.  These were calculated with the link-quality 
    597614threshold set at 50\%. 
     
    605622 
    606623Of course, this is only part of the cost comparison as there are many other protocol-dependent factors 
    607 that may lead to inefficiencies in energy consumption for either single or multichannel communication. 
    608 However, this sets a basis for comparison based on transmission links alone and can be used as a guidance 
    609 for understanding the tradeoffs between both choices. 
    610  
    611 The next section considers how changes in the connectivity graph, by changing the threshold, affects  
    612 the routing solutions and associated costs. 
     624that may lead to inefficiencies in energy consumption.  
     625%for either single or multichannel communication. 
     626However, this sets a basis for comparison based on transmission links.% and can be used  
     627%as a guidance 
     628%kfor understanding the tradeoffs between both choices. 
     629 
     630%The next section considers how changes in the connectivity graph, by changing the threshold, affects  
     631%the routing solutions and associated costs. 
    613632 
    614633%\begin{figure}[tb!] 
     
    625644\begin{table} 
    626645\centering 
     646\begin{small} 
    627647\begin{tabular}{|c|c|c|} \hline 
    628648\textbf{Run ID}&\textbf{Best}&\textbf{Worst}\\ \hline 
     
    6346546 & 1.5 & 1.5  \\ \hline 
    635655\end{tabular} 
    636 \caption{Cost ratio comparison for the machine room.} 
     656\end{small} 
     657\caption{Cost ratio comparison for the machine room.  Threshold set to 50, routing solutions channel 
     658set to 26.} 
    637659\label{tab:costratio_machine} 
    638660\end{table} 
    639  
    640661 
    641662\subsubsection{Link Threshold Effects On Ratio} 
     
    657678\label{fig:testbed_threshold_costratio} 
    658679} 
     680\caption[Optional caption for list of figures]{Cost ratios in each environment as a function of 
     681link-quality threshold on the connectivity graph.} 
    659682\label{fig:testbed_threshold_costratios} 
    660 \caption[Optional caption for list of figures]{Cost Ratios in each environment as a function of 
    661 link-quality threshold on the connectivity graph.} 
    662683\end{figure*} 
    663684 
    664 Recall that to contruct a connectivity graph, one must set an initial threshold 
     685Recall that to construct a connectivity graph, one must set an initial threshold 
    665686on the population of links in the traces.  For the results that have thus far been shown,  
    666687the link threshold was set at 50\%. 
     
    679700of threshold.  Note the slight increase in cost for the testbed routing solution. 
    680701As the threshold increases, the link-population choice becomes shorter in length and the choices 
    681 available are essentially the same for both the multichannel and single-channel solutions 
    682 and the ratios do not change very much. 
     702available are essentially the same for both the multichannel and single-channel solutions, 
     703so the ratios do not change very much. 
    683704 
    684705%However, this may suggest that routing is more expensive if there is high link-quality threshold 
     
    699720 
    700721\subsection{Other Associated Costs} 
     722\label{subsec:other_costs} 
    701723 
    702724\begin{table} 
    703725\centering 
     726\begin{small} 
    704727\begin{tabular}{|c|c|c|} \hline 
    705728\textbf{Protocol}&\textbf{ROM}&\textbf{RAM}\\ \hline 
     
    709732B-MAC w/LPL + ACK & 4386 & 277 \\ \hline 
    710733\end{tabular} 
    711 \caption{Example code size comparsion in bytes between single and multichannel 
     734\end{small} 
     735\caption{Example code size comparison in bytes between single and multichannel 
    712736MAC protocols.~\cite{pracmac, bmac} 
    713737} 
     
    715739\end{table} 
    716740 
    717 A good indication of code complexity is code size, and it matters. 
     741A good indication of code complexity is code size. %, and it matters. 
    718742Reducing the complexity of the protocol reduces the state and the likelihood of race  
    719743conditions~\cite{bmac}.  Therefore it is desirable to keep code size small.  Table \ref{tab:codesize} 
    720 shows the code sizes of the default single-channel MAC is TinyOS and compare the size against 
    721 an implemetation of a multichannel MAC protocol also written in TinyOS.  Notice the difference 
    722 in code size.  PracMac is almost 5 times larger in RAM and more than twice as large in ROM. 
    723 Furthermore, motes are resource contrained, and the larger the stack, the smaller the space 
     744shows the code sizes of the default single-channel MAC in TinyOS, B-MAC, and compares the size against 
     745an implementation of a multichannel MAC protocol also written in TinyOS, PracMac~\cite{pracmac}.   
     746PracMac is almost 5 times larger in RAM and more than twice as large in ROM. 
     747Furthermore, motes are resource constrained, and the larger the stack, the smaller the space 
    724748for applications. 
    725749 
    726 We simulated FH on the testbed data set, run ID 1,  using first of five pre-set hop sequences. 
    727 The link qualities using this hop sequence, we were able to construct a sparse connectivity graph with 
    728 poor links.  Although the simulation is not realistic, it may indicate a problem with FH in an 802.11-rich 
     750We also simulated FH on the testbed data set, run ID 1,  using first of five pre-set hop  
     751sequences~\cite{sp10011a}. 
     752The links formed by this process were of very poor quality (about 25\% or below PRR) 
     753We were able to construct a sparse, poorly connected graph.   
     754Although the simulation is not realistic, it may indicate a problem with FH in an 802.11-rich 
    729755environment.  As mentioned earlier, there are 7 access points sitting amongst the nodes on the testbed. 
    730756With the access point center frequencies set to 802.11 channels 1, 6, and 11, there are only 4 of the possible 16 
    731 channels that do not overlap 802.11 transmissions.  Therefore, the hop sequence, chooses a ``bad'' channel 
    732 75\% of the time.  SP100.11a and Wireless Hart are certainly aware of this and make explicit recommendations 
    733 to blacklist the 802.11 channel a priori.  We suspect that if this is done in the testbed environment, the 
    734 links qualities will not differ from remaining on a single, good channel (since FH is left to choose 
     757channels that do not overlap 802.11 transmissions.  Therefore, the hop sequence chooses a ``bad'' channel 
     758with about 75\% of the time.  SP100.11a and Wireless Hart are certainly aware of this and make explicit recommendations 
     759to blacklist the 802.11 channels a priori.  We suspect that if this is done in the testbed environment, the 
     760links qualities will not differ from that of remaining on a single, good channel (since FH is left to choose 
    735761from only top remaining channels). 
    736762 
     
    747773data-exchange channel, the scanning and negotiation overhead is non-negligible. 
    748774 
    749 Another multichannel approach couples time-synchronization with multichannel communication  
    750 and schedules both frequency and transmission-time slots.  This scheme removes the need for scanning,  
    751 however, it requires message-exchange synchronization overhead (usually 1 packet sent by every node  
    752 every 30 seconds~\cite{ftsp} -- 
    753 with the 30-second period adjusted according to clock-drift and deployment size).  
    754 At this rate each node sends 2880 synchronization packets per day and in the worst case receives 
    755 some fraction of that from each neighbor.  Packet reception incurs slightly more cost (19.7 mA) 
    756 on the CC2420 then transmitting (17.4 mA)~\cite{cc2420} making the synchronization-flood 
    757 overhead non-negligible. 
    758 Furthermore, without active channel-noise observations 
    759 the schedule may choose poor channels while hopping which can potentially drive up the communication 
    760 cost unnecessarily. 
    761  
    762  
     775In the FH case, the overhead is still non-negligable.  SP100.11a uses a send frame of 10 ms. 
     776In this frame, approximately 5 packets can be sent.  If the offered load is greater than 5 packets 
     777($>$ 300 bytes) the sender and receiver must both switch channels.  Switching channels 
     778takes 1.4 ms, or 14\% overhead.  Single-channel communication would not incur any extra overhead 
     779if a good channel is chosen. 
     780 
     781Of course, single-channel communication is not free.  Some pre-provisioning and planning is necessary. 
     782One must survey the deployment environment, choose the right channel, and test the connectivity over time. 
     783One must also set up the network.  However, you have to do this anyway, according to SP100.11a and WirelessHART, 
     784as both make recommendations about topology properties and blacklisting. 
     785Still, FH may offer higher network capacity, as multiple senders in the same space can transmit simultaneously 
     786with interfering with one another. 
     787 
     788%Another multichannel approach couples time-synchronization with multichannel communication  
     789%and schedules both frequency and transmission-time slots.  This scheme removes the need for scanning,  
     790%however, it requires message-exchange synchronization overhead (usually 1 packet sent by every node  
     791%every 30 seconds~\cite{ftsp} -- 
     792%with the 30-second period adjusted according to clock-drift and deployment size).  
     793%At this rate each node sends 2880 synchronization packets per day and in the worst case receives 
     794%some fraction of that from each neighbor.  Packet reception incurs slightly more cost (19.7 mA) 
     795%on the CC2420 then transmitting (17.4 mA)~\cite{cc2420} making the synchronization-flood 
     796%overhead non-negligible. 
     797%Furthermore, without active channel-noise observations 
     798%the schedule may choose poor channels while hopping which can potentially drive up the communication 
     799%cost unnecessarily. 
     800 
     801 
  • code/Multichannel/docs/mobisys/doc/setupandmeth.tex

    r2713 r2791  
    33 
    44%Three different environments, many motes covering each space. 
    5 In this section we describe our experimental setup.  To examine RF characteristics 
     5To examine RF characteristics 
    66and connectivity we placed a set of  
    77motes in three distinct environments: an industrial machine room environment  
     
    1515and narrowband fading.   The main source of loss in the industrial setting 
    1616is due to NLOS communication and multipath-induced narrowband fading.  We 
    17 observed some external interference but activity was sporatic and short-lived. 
     17observed some external interference but activity was sporadic and short-lived. 
    1818Most of the communication between motes in the computer room and testbed 
    1919is NLOS.  Furthermore, both settings are subject to 802.11 interference 
     
    2222%Placement of motes in the industrial setting is 
    2323%a factor as NLOS communication, metal surfaces, and rotating machinery affect wireless 
    24 %signal propogation. 
     24%signal propagation. 
    2525%Both the computer room and testbed are subject to 
    2626%802.11 traffic and NLOS communication.   
     
    3232the b6lowpan~\cite{b6lowpan} stack.   Motes handle various experiment commands which 
    3333are delivered over the routing tree constructed by the stack.  Data is also collected  
    34 over the routing tree after each experiment.  For the testbed we used the ethernet  
    35 backchannel for command delivery and data collection. 
     34over the routing tree after each experiment.  For the testbed we used the Ethernet  
     35back-channel for command delivery and data collection. 
    3636 
    3737%For both the industrial setting and machine room we used the b6lowpan~\cite{b6lowpan} 
     
    4848%placed in sensing and routing-relevant locations. 
    4949For the machine room and computer room we placed motes in locations in the network  
    50 where sensing might take place.  In the machine room(s), we placed motes on top of moving engines 
    51 and between pipes.  The machine room deployment in seperated into two 
    52 seperate rooms that are side by side.  Both rooms have similar equipment and are seperated 
    53 by a wall.  We placed motes in both rooms and tested connetivity among all the motes 
     50where sensing might take place.  In the machine room, we placed motes on top of moving engines 
     51and between pipes.  The machine room deployment in separated into two 
     52separate rooms that are side by side.  Both rooms have similar equipment and are separated 
     53by a wall.  We placed motes in both rooms and tested connectivity among all the motes 
    5454in the deployment.  Similarly, we placed motes inside computer racks, next to active 
    5555air conditioning units, and at varying heights inside the computer room. 
    5656 
    5757On the testbed we had no choice in node placement.  Nodes are scatter on the ceiling across 
    58 an entire floor in an office environment.  The motes sit amongst active 802.11 acces points 
     58an entire floor in an office environment.  The motes sit amongst active 802.11 access points 
    5959that see a varying number of clients and activity throughout the day.  Since 
    6060the floor is partitioned into several rooms, many of the links are NLOS. 
     
    7373which uses the CC2420 radio. 
    7474 
    75 \begin{figure}[h!] 
    76 \begin{center} 
    77 \includegraphics[width=0.7\columnwidth]{../figs/basement_node_placement} 
    78 \caption{Industrial Environment Nodes Placement map. 
    79 } 
    80 \label{fig:basement_node_placement} 
    81 \end{center} 
    82 \end{figure} 
    83  
     75%\begin{figure}[h!] 
     76%\begin{center} 
     77%\includegraphics[width=0.7\columnwidth]{../figs/basement_node_placement} 
     78%\caption{Industrial Environment Nodes Placement map. 
     79%} 
     80%\label{fig:basement_node_placement} 
     81%\end{center} 
     82%\end{figure} 
     83% 
    8484\begin{figure}[h!] 
    8585\begin{center} 
    8686\includegraphics[width=0.8\columnwidth]{../figs/basement_pic} 
    87 \caption{Industrial environment setting. 
     87\caption{Machine room setting. 
    8888} 
    8989\label{fig:basement_pic} 
    9090\end{center} 
    9191\end{figure} 
     92% 
     93%\begin{figure}[h!] 
     94%\begin{center} 
     95%\includegraphics[width=0.9\columnwidth]{../figs/machine_room_node_placement} 
     96%\caption{Machine room node placement.  The larger dot on the map denotes an 
     97%802.11 access point. 
     98%} 
     99%\label{fig:machine_room_node_placement} 
     100%\end{center} 
     101%\end{figure} 
     102 
     103%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 
     104%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 
     105%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 
     106 
     107\begin{figure*}[!tbh] 
     108\centering 
     109 
     110\subfigure[Machine room node placement map.]{ 
     111\includegraphics[width=0.3\textwidth]{../figs/basement_node_placement} 
     112\label{fig:basement_node_placement} 
     113}  
     114\subfigure[Computer room node placement.  The larger dot on the map denotes an 
     115802.11 access point.]{ 
     116\includegraphics[width=0.3\textwidth]{../figs/machine_room_node_placement} 
     117\label{fig:machine_room_node_placement} 
     118}  
     119\subfigure[Testbed node placement.  The larger dots on the map denote the placement 
     120of 802.11 access points.]{ 
     121\includegraphics[width=0.3\textwidth]{../figs/testbed_placement} 
     122\label{fig:basementlayout} 
     123} 
     124 
     125\label{fig:node_placement_maps} 
     126\caption[Optional caption for list of figures]{} 
     127\end{figure*} 
    92128 
    93129We use the WiSpy spectrum analyzer~\cite{wispy24} to characterize the RF environment  
    94130and find some RF noise generated near engines in the room. 
    95 RF activity is sporatic and spread throughout the frequency band however we do not  
     131RF activity is sporadic and spread throughout the frequency band however we do not  
    96132examine this data very closely, since it does not seem to affect our results.   
    97133 
    98134\subsubsection{Computer Room Setup} 
    99135Like the machine room, motes were placed in locations where sensing might take place. 
    100 For example, motes were placed inside racks, near air conditioners, at the extremeties of the 
     136For example, motes were placed inside racks, near air conditioners, at the extremities of the 
    101137room and at different heights.  The room is 28x28 feet and we placed 23 telosb motes throughout 
    102138the room. 
     
    108144shows the node placement overlayed on the map of the room. 
    109145 
    110 \begin{figure}[h!] 
    111 \begin{center} 
    112 \includegraphics[width=0.9\columnwidth]{../figs/machine_room_node_placement} 
    113 \caption{Machine room node placement.  The larger dot on the map denotes an 
    114 802.11 access point. 
    115 } 
    116 \label{fig:machine_room_node_placement} 
    117 \end{center} 
    118 \end{figure} 
    119  
    120 There is an access point sitting on the ceiling in the middle of the computer room.  We actually 
     146There is an access point sitting on the ceiling in the middle of the computer room.  We 
    121147ran the experiments in the evening during the spring break session, so the RF activity was 
    122148fairly low for each run. 
    123149 
    124150\subsubsection{Testbed Setup} 
    125 On the testbed mote are placed to allow for full network connectivity.  This is the largest  
     151On the testbed, motes are placed to allow for full network connectivity.  This is the largest  
    126152of the 3 deployments we examined, with 55-60 MicaZ~\cite{MicaZ} motes. Floor dimensions are  
    127 128x128 and it is partitioned into multiple rooms in an office environment. 
     153128x128 feet and it is partitioned into multiple rooms in an office environment. 
    128154Since the testbed is inside the computer science building of the university it sees 
    129155lots of human traffic and 802.11 activity.   There are 7 access points  
     
    131157the day. 
    132158 
    133 \begin{figure}[h!] 
    134 \begin{center} 
    135 \includegraphics[width=0.9\columnwidth]{../figs/testbed_placement} 
    136 \caption{Testbed node placement.  The larger dots on the map denote the placement 
    137 of 802.11 access points. 
    138 } 
    139 \label{fig:basementlayout} 
    140 \end{center} 
    141 \end{figure} 
     159%\begin{figure}[h!] 
     160%\begin{center} 
     161%\includegraphics[width=0.9\columnwidth]{../figs/testbed_placement} 
     162%\caption{Testbed node placement.  The larger dots on the map denote the placement 
     163%of 802.11 access points. 
     164%} 
     165%\label{fig:basementlayout} 
     166%\end{center} 
     167%\end{figure} 
    142168 
    143169%RF environment description. 
     
    186212three times and the testbed 17 times continuously over the span of a week. 
    187213 
     214\subsubsection{Analytical Approach} 
     215\label{subsec:analytical} 
     216 
     217 
     218Each broadcast packet contains a sender ID and a local sequence number.  When a node receives  
     219a broadcast packet it extracts both of these values and logs them along with its own ID 
     220and  current channel.  The testbed experiment also logs timestamp and received signal-strength 
     221indicator (RSSI) values.  Using this information we separate the data set into bins  
     222separated by channel and use each subset to study the connectivity graph on 
     223each channel. 
     224 
     225For each directional link in the connectivity graph we calculate the PRR 
     226and set a threshold on link quality to construct the connectivity graph. 
     227We then run the MCL and MCT locaters on the traces as well as  
     228Dijkstra's shortest-path algorithm.  In calculating the cost of transmission 
     229over a link, we use the expected transmission count (ETX) metric and compute the sum for all links 
     230along a path to determine its cost.  Equation~\ref{eqn:etx} shows how to calculate 
     231ETX; $l_f$ is the forward link PRR and $l_b$ is the backward link PRR. 
     232 
     233\begin{equation} 
     234ETX = \frac{1}{l_{f} * l_{b}} 
     235\label{eqn:etx} 
     236\end{equation} 
     237 
     238After the construction of a graph for each channel we count the number MCLs. 
     239For each link on a particular channel, we search for the same link the exists in only one 
     240direction on any channel.  If the link is either not found or it exists 
     241unidirectionally on some channel, it is added to the set of MCLs.  This 
     242set enumerates the number of opportunities there are for multichannel to enable communication 
     243between a pair of nodes.  In addition, we ran connectivity tests for all the observed 
     244connectivity graphs using Tarjan's connectivity algorithm.%~\cite{}. 
     245 
     246In the search for MCTs we create various sets that  
     247consist of 3-tuples of unique nodes in the network that share bi-directional links  
     248between each other.  The first set, the \emph{single-channel set}, takes every set  
     249of three nodes in the network that are bi-directionally connected on a \emph{single} channel.   
     250For example, if there exists bi-directional links $(i,j)$, $(i,k)$, 
     251and $(j,k)$ for unique nodes $i$, $j$, and $k$ and each link is on the same channel, then it  
     252is included in the single-channel triangle set, also referred to as set $S$. 
     253 
     254We also construct another set, similar to set $S$, except that the constraints on the links  
     255are loosened to include triangles that occur across channels.  Therefore, if there exists  
     256bi-directional links $(i,j)$, $(i,k)$, and $(j,k)$ for unique nodes $i$, $j$, and $k$ on  
     257\emph{any} channel, then it is included in the global multichannel triangle set, hereafter referred  
     258to as set $M$. 
     259 
     260Finally we construct the set of interest, the \emph{MCT set}.  This set includes  
     261all element in set $M$ that are not in set $S$.  In other words, it includes all sets of 3 nodes  
     262that are not connected on a single channel but are connected on multiple channels -- the  
     263definition of an MCT.  We refer to this set at set $M_u$ (unique multichannel  
     264triangles). 
     265 
     266%For each element in set $M_u$, the MCT set, we examine if there exists a routing  
     267%solution and separate each solution into the number of hops in the shortest path route.   
     268%The 2-hop routing solution is each element of $M_u$ where any two bi-directional links are  
     269%on the same channel.  This assume that the sender wants to send the same data to each node  
     270%in the triangle.  The multichannel solution is only possible by switching channels, however,  
     271%routing over a 2-hop path using the links in the triangle also works. 
     272%Figure~\ref{fig:2hopdemo} shows a demonstration of the 2-hop solution to an MCT 
     273%where $i$ is the source and either $j$ or $k$ is the destination. 
     274 
     275%Similarly, we construct the sets for routing solutions that consist of 3 hops and N hops.   
     276%The route must be on a single channel and include all three nodes, $i, j, $ and $k$ where  
     277%one of the three nodes is considered the source, another is considered the destination, and  
     278%the last node is on the path from the source  to the destination.  For each route calculation  
     279%we use Dijkstra's shortest path algorithm using the link ETX's as the link weights. 
     280%The key is to minimize the ETX sum between the source and destination. 
     281%Figure~\ref{fig:Nhopdemo} shows a demonstration of the N-hop solution to an MCT 
     282%where $i$ is the source and $j$ or $k$ is the destination. 
     283 
     284 
    188285\subsubsection{How representative are samples?} 
    189286Commands from the experiment 
     
    204301 
    205302In capturing directional properties of links it may be worrisome that each link samples  
    206 (100 packets) in either direction may be seperated by at $2N + \epsilon$ sample times,  
     303(100 packets) in either direction may be separated by at $2N + \epsilon$ sample times,  
    207304where $N$ is the number of nodes 
    208305in the network and $\epsilon$ is the a small random wait time caused by stalls and retries. 
    209 This kind of seperation between samples may statistically decorrelate the measurements in 
     306This kind of separation between samples may statistically de-correlate the measurements in 
    210307either direction.  However, by taking many samples we can bound of the error for 
    211 the PRR measured in each direction of a bi-directional link.  Furthermore, the main 
     308the packet reception rate (PRR) measured in each direction of a bi-directional link.  Furthermore, the main 
    212309source of uncertainty -- external interference and changes in the environment -- are effectively 
    213310removed from the two experiments with the least number of samples.  The industrial 
     
    224321% 
    225322%\emph{Each direction of a link between a pair of nodes is not done consecutively 
    226 %or interleaved.  They are seperated by at most $2N + \epsilon$ seconds apart where 
     323%or interleaved.  They are separated by at most $2N + \epsilon$ seconds apart where 
    227324%$N$ is the number of motes in the experiment and $\epsilon$ is some random period 
    228325%for command-send retries.} 
     
    231328% 
    232329%Basement had little to no RF 
    233 %interference, location of motes and orientation of mote attenas did not change. 
    234  
    235 \subsubsection{Analytical Approach} 
    236 \label{subsec:analytical} 
    237  
    238  
    239 Each broadcast packet contains a sender ID and a local sequence number.  When a node receives  
    240 a broadcast packet it extracts both of these values and logs them along with its own ID 
    241 and  current channel.  The testbed experiment also logs timestamp and received signal-strength 
    242 indicator (RSSI) values.  Using this information we seperate the data set into bins  
    243 seperated by channel and use each subset to study the connectivity graph on 
    244 each channel. 
    245  
    246 For each directional link in the connectivity graph we calculate the packet reception rate (PRR) 
    247 and set a threshold on link quality to construct the connectivity graph. 
    248 We then run the MCL and MCT locaters on the traces as well as  
    249 Dijkstra's shortest-path algorithm.  In calculating the cost of transmission 
    250 over a link, we use the expected transmission count metric and compute the sum for all links 
    251 along a path to determine its cost.  Equation~\ref{eqn:etx} shows how to calculate 
    252 ETX; $l_f$ is the forward link PRR and $l_b$ is the backward link PRR. 
    253  
    254 \begin{equation} 
    255 ETX = \frac{1}{l_{f} * l_{b}} 
    256 \label{eqn:etx} 
    257 \end{equation} 
    258  
    259 After the construction of a graph for each channel we count the number MCLs. 
    260 For each link on a particular channel, we search for the same link the exists in only one 
    261 direction on any channel.  If the link is either not found or it exists 
    262 unidirectionally on some channel, it is added to the set of MCLs.  This 
    263 set enumerates the number of opportunities there are for multichannel to enable communication 
    264 between a pair of nodes.  In addition, we ran ran connectivity tests for all the observed 
    265 connectivity graphs using Tarjan's connectivity algorithm.%~\cite{}. 
    266  
    267 In the search for MCTs we create various sets that  
    268 consist of 3-tuples of unique nodes in the network that share bi-directional links  
    269 between each other.  The first set, the \emph{single-channel set}, takes every set  
    270 of three nodes in the network that are bi-directionally connected on a \emph{single} channel.   
    271 For example, if there exists bi-directional links $(i,j)$, $(i,k)$, 
    272 and $(j,k)$ for unique nodes $i$, $j$, and $k$ and each link is on the same channel, then it  
    273 is included in the single-channel triangle set, also referred to as set $S$. 
    274  
    275 We also construct another set, similar to set $S$, except that the constraints on the links  
    276 are loosened to include triangles that occur across channels.  Therefore, if there exists  
    277 bi-directional links $(i,j)$, $(i,k)$, and $(j,k)$ for unique nodes $i$, $j$, and $k$ on  
    278 \emph{any} channel, then it is included in the global multichannel triangle set, hereafter referred  
    279 to as set $M$. 
    280  
    281 Finally we construct the set of interest, the \emph{MCT set}.  This set includes  
    282 all element in set $M$ that are not in set $S$.  In other words, it includes all sets of 3 nodes  
    283 that are not connected on a single channel but are connected on multiple channels -- the  
    284 definition of an MCT.  We refer to this set at set $M_u$ (unique multichannel  
    285 triangles). 
    286  
    287 %For each element in set $M_u$, the MCT set, we examine if there exists a routing  
    288 %solution and seperate each solution into the number of hops in the shortest path route.   
    289 %The 2-hop routing solution is each element of $M_u$ where any two bi-directional links are  
    290 %on the same channel.  This assume that the sender wants to send the same data to each node  
    291 %in the triangle.  The multichannel solution is only possible by switching channels, however,  
    292 %routing over a 2-hop path using the links in the triangle also works. 
    293 %Figure~\ref{fig:2hopdemo} shows a demonstration of the 2-hop solution to an MCT 
    294 %where $i$ is the source and either $j$ or $k$ is the destination. 
    295  
    296 %Similarly, we construct the sets for routing solutions that consist of 3 hops and N hops.   
    297 %The route must be on a single channel and include all three nodes, $i, j, $ and $k$ where  
    298 %one of the three nodes is considered the source, another is considered the destination, and  
    299 %the last node is on the path from the source  to the destination.  For each route calculation  
    300 %we use Dijkstra's shortest path algorithm using the link ETX's as the link weights. 
    301 %The key is to minimize the ETX sum between the source and destionation. 
    302 %Figure~\ref{fig:Nhopdemo} shows a demonstration of the N-hop solution to an MCT 
    303 %where $i$ is the source and $j$ or $k$ is the destination. 
    304  
     330%interference, location of motes and orientation of mote antennas did not change. 
     331 
     332 
  • code/Multichannel/docs/mobisys/doc/sexton.tex

    r2713 r2791  
    11\section{Guiding Study} 
    22\label{sec:sexton_study} 
     3%The next study played an important role establishing the ground-truth for adding FH to the standards). 
     4An important study that played a role in the ISA standard, SP100.11a.  The authors 
     5examine the behavior of wireless links in industrial environments and recommend various forms 
     6of diversity -- FH being one of them.  We revisit the results of the study and argue that the conclusions 
     7would have been different had they considered routing as an alternative to FH. 
    38 
    49In~\cite{sexton}, Sexton et al. measure the multipath delay spread and link 
     
    611may suffer in these types of environments.   
    712The CC2420 transmits at 250 kbps with a chip rate of  
    8 2000 kChips/sec~\cite{cc2420_datasheet}.  Therefore each chip takes 
     132000 kChips/sec~\cite{cc2420}.  Therefore each chip takes 
    914500 nanoseconds to transmit.  If the delay spread is greater than 50 nanoseconds 
    1015it could present a problem for the CC2420, since it has no equalization.   
     
    5560We may observe that the study focuses on direct connectivity between all pairs 
    5661of nodes in the network.  In this context, the conclusions are, in fact, sound. 
    57 However,  we do not expect that to be present in most wireless meshes. 
     62However,  we do not expect direct links between all nodes to be present in wireless meshes. 
    5863Communication between widely separated pairs of nodes is accomplished by routing 
    5964over multiple hops.  Sometimes multiple hops are required even for nodes in close 
     
    124129 
    125130It is important to note that link-level acknowledgements in 802.15.4 utilize the same 
    126 channel as the packet they cover, so bidirectionality on a single channel is essential 
    127 for reliability through retransmissions.  Therefore, the ability of multichannel communication 
     131channel as the packet they cover, so bi-directionality on a single channel is essential 
     132for reliability through re-transmission.  Therefore, the ability of multichannel communication 
    128133to construct good bi-directional communication from two unidirectional links 
    129134is not possible in practice. %; the second possibility is the only viable option. 
     
    170175agility is required for all nodes to communicate with one another in the absence of routing. 
    171176An example is shown in Figure~\ref{fig:sextrigdemo}, where $i$ can communicate bi-directionally  
    172 with $j$ and $k$ on $c_{1}$ and $i$ can communicate bi-directionally with $k$ and $j$ on $c_{2}$ 
     177with $j$ on $c_{1}$, $i$ can communicate bi-directionally with $k$ on $c_{2}$, and  
     178$j$ can communicate bi-directionally with $k$ on $c_{3}$ 
    173179but there is no channel where all three can communicate. 
    174180