Changes between Version 12 and Version 13 of EMR


Ignore:
Timestamp:
Oct 11, 2010, 5:23:34 PM (14 years ago)
Author:
Sensei
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • EMR

    v12 v13  
    11= EMR – Energy-efficient Multi-hop Routing for Clustered WS&ANs Cookbook =
    22
    3 This document aims to introduce about how to use the resource of Energy-efficient Multi-hop Routing (EMR). It first gives some background about EMR about its main objective and how it operates. Then the required devices and soft wear environment to install EMR are provided. After illustrate how to install the codes, it briefly explains how to run this routing solution. 
     3This document aims to introduce about how to use the resource of Energy-efficient Multi-hop Routing (EMR) for Clustered WSNs, e.g. how to install the codes of routing solution and how to run it. It first gives some background about EMR, for instance the main issue it aims to addres, its objective and its operation. Then the required devices and soft wear environment to install EMR resource are described. After illustrate how to install the EMR resource, it briefly explains how to run this routing solution. 
    44
    55[[PageOutline(2-3,Table of Contents,inline)]]
    … …  
    77== Introduction ==
    88
    9 Hot-spot issue means the phenomenon that some nodes in a WSN drain energy more rapidly than others, due to the higher load, and thus deplete energy earlier. Therefore hot-spot issue may differ node lifetime in the network. The main purpose of EMR is to address the hot-spot issue in WSNs via individual node lifetime equalization across the network, so that the network energy could be better utilized.
     9=== Hot-spot issue in WSNs
     10
     11In a typical WSN, raw data packets from sensor nodes are typically sent to sink for further process, resutling in that nodes in the network may have different loads. In a WSN where data packets are relayed to the sink via multi-hop routing (typically in large-scale WSNs), those nodes nearer the sink may required to relay more data and thus will have higher load; whereas in a WSN where data packets are forwarded to the sink directly (typically in small-scale WSNs), those nodes that are farther away from the sink require higher power to access the sink and thus will have higher load. Such phenomenon that senor nodes have different loads in the next and drain energy at an uneven rate is referred to hot-spot issue. In a WSN with uniform inital energy distribution, hot-spot issue may differ node lifetime, i.e. those nodes with higher load will deplete energy earliers than others.
     12
     13Though the hot-spot issue may differ the node lifetime in a network, the connectivity between the WSN island and the sink may be still present after some nodes have depleted energy earlier than others. In a WSN with multi-hop routing towards the sink, in case the nodes deployed in the area next to the sink have depleted energy, the nodes in neighboring areas, e.g. with longer distance to the sink, could increase the power for routing discovery and could probably still be able to access the sink. IN a WSN with single-hop between the sensor nodes and the sink, those nodes with longer distance to the sink are more likely to die, yet their earlier death will not bring any effect to the snesor nodes nearer the sinks in this case. To summarize, the death of some nodes in the network due to energy depletion may not disconnect the island and the sink. This means that a user is still able to enquire the network after some network nodes died due to energy failure. However, in case the users enquire the area where the deployed sensor nodes have depleted energy, the SENSEI system may fail to provide the quality informaiton. From this point of view, hot-spot issue will degrade the performance of the SENSRI framework and thus needs to be addressed.
     14
     15=== Objectives of EMR
     16
     17The EMR solution is proposed for such purpose to address the hot-spot issue. It mainly aims to extend the stable operation period (SOP) of the network during which all sensor nodes are alive with avaialbe energy. The SOP is important for a WSN as during the SOP period, the whole island is supposed to be covered by the active sensor nodes i.e. with avaialbe energy (assuming that the network has a good coverage during the deployment stage) and the SENSEI system is able to provide the quality infroamtion to the user. Therefore, extending SOP means longer continuity of the SENSEI system duirng which the system could provide quality informaiton.
     18
     19The proposed EMR includes two main parts, the first is to conduct the mathematical analysis to theoriotically address the hot-spot issue. With the analysis, the competetion range to be a clusterhead (CH) is output. This range is then applied in EMR for CH selection.
     20
     21=== Operation of EMR
    1022 
    11 The operation of EMR is summarized as following:
    12  * First of all, some CH candidates are selected;
    13  * Then, these candidates compete to be the final CH;
    14  * After the CHs are selected, they announce their role and allow non-CH nodes to join them as member nodes to form the clusters;
    15  * Then each CH gives a slot to each member node belongs it and collects the data packets from its respective member nodes;
    16  * Finally, each CH aggregates these packets as one summary packet of its cluster and delivers them to the sink.
    17 
    18 Please note that the competition ranges of the CH candidates to be the CHs are determined by the probability of the nodes to be the CH, acquired by the mathematical analysis about how the node lifetime could be equalized across the network.
     23The operation of EMR is separated into rounds of data collection. During each round, the following operations happen.
     24 * First of all, some CH candidates are selected among the nodes.
     25 * Then, these candidates announce their willing to be the CH and compete to be a final CH. Typically, those candidates with more avaialbe enregy will be a fianl CH.
     26 *  After the CHs are selected, they announce their role and allow non-CH nodes to join them as member nodes to form the clusters.
     27 * Then each CH gives a slot to each member node in its cluster and collects the data packets from its respective member nodes;
     28 * Finally, each CH aggregates these packets from the member nodes as one summary packet of its cluster and delivers this summary packet to the sink.
    1929
    2030== Installation ==
    … …  
    2737 * [http://docs.tinyos.net/index.php/Getting_started TinyOS-2.x]
    2838 * [https://ncit-cluster.grid.pub.ro/trac/Sensei-Cookbook/wiki/emr/emr.tar.gz EMR software package]
    29  * At least 11 TelosB sensor nodes (one as sink, and others as normal nodes consisting a network)
     39 * As hierarchical clustering-based topology is applied in EMR, we suggest that at least 11 TelosB sensor nodes (one as sink, and others as normal nodes consisting a network) are required, which could be organized into two clusters.
    3040
    3141We assume that the installation PC is running a Linux operating system, and the [http://docs.tinyos.net/index.php/Getting_started TinyOS-2.x] and [http://weblogs.java.net/blog/opinali/archive/2010/08/21/jdk-6u21-javafx-131-and-deployment JAVA environment] have been installed and configured properly. We skip the installation of TinyOS. A user could refer to [http://docs.tinyos.net/index.php/Getting_started TinyOS-2.x] about the installation if necessary. Please note that the description about how to install the EMR routing solution is based on the [http://www.ubuntu.com/ Ubuntu] operating system.
    3242
    33 In a WSN, there are two types of nodes, the normal sensor nodes which form the network, and the sink. The data packets from the normal nodes are periodically collected by the sink after some basic processing at the CH, e.g. data aggregation. The following provides the detailed information about the structure and the content of the EMR software package:
    34 * Node \\
     43EMR assumes that there are two types of nodes in a WSN, the normal nodes (please note that a normal node in EMR could be either a member node or a CH) and the sink. The normal nodes form the WSN island and periodically send data packet to the sink after some basic processing by the CHs, e.g. data aggregation. The software packages for normal nodes and the sink are different. The following provides the detailed information about the structure and the content of the EMR software package:
     44
     45* For a normal node \\
    3546 * {{{EMRAPPc.nc}}}\\ Contains the configuration files and  the wiring between interfaces
    36  * {{{EMRCHC.nc}}}\\ Contains all relevant actions and behavior of the Cluster Head (CH), e.g. collecting the informaiton of the member nodes like how many member nodes belong it, receiving the data packets from the member nodes, and forwarding the summary packet of the cluster towards the sink
     47 * {{{EMRCHC.nc}}}\\ Contains all relevant actions and behavior of the CH, e.g. collecting the informaiton of the member nodes like how many member nodes belong it, receiving the data packets from the member nodes, and forwarding the summary packet of the cluster towards the sink
    3748 * {{{EMRClusteringC.nc}}}\\ Contains the procedure about how the clusters are formed
    3849 * {{{EMRInitC.nc}}}\\ Contains all initializations of each round across the network operation, and how to process the received message
    … …  
    4152 * {{{EMRRouting.nc}}}\\ Contains the process about how to determine the routing towards the sink in multi-hop scenario
    4253 * Interface\\ Contains the defination of all involved interfaces
    43  * include\\ Contains all header files
     54 * Include\\ Contains all header files
    4455
    45 * Sink \\
     56* For a sink node \\
    4657 * {{{EMRSinkAppc.nc}}}\\ Contains the configuration files and the wiring between interfaces
    4758 * {{{EMRSinkC.nc}}}\\ Contains the actions and behavior of the sink
    … …  
    5364=== Installation
    5465
    55 * First of all, a user needs to install and configure [http://docs.tinyos.net/index.php/Getting_started TinyOS-2.x] and [http://weblogs.java.net/blog/opinali/archive/2010/08/21/jdk-6u21-javafx-131-and-deployment JAVE Environment jdk-6u21] properly
     66The installation of EMR is rather simple and the following briefly introduces how the EMR resrouce could be loaded to the normal nodes and the sink node.
    5667
    57 * Then the user could copy the {{{build}}}  folder and the {{{Makefile}}}  into a new folder under the tinyOS directory for normal node
     68* First of all, a user needs to install and configure [http://docs.tinyos.net/index.php/Getting_started TinyOS-2.x] and [http://weblogs.java.net/blog/opinali/archive/2010/08/21/jdk-6u21-javafx-131-and-deployment JAVE Environment jdk-6u21] properly.
     69
     70* Then the user could copy the {{{build}}}  folder and the {{{Makefile}}}  into a new folder under the tinyOS directory for a normal node
    5871
    5972        {{{
    … …  
    6275}}}
    6376
    64 * Thirdly, copy the source code into a new folder for sink node
     77* Thirdly, copy the source code into a new folder for the sink node
    6578
    6679        {{{
    … …  
    8699== Running EMR==
    87100
    88 The following describes about how to run EMR step by step and how to test whether it is installed properly.
     101The following describes about how to run the EMR routing solution step by step and how to test whether it is installed properly.
    89102
    90103* Operation\\
    91    * First, turn on all normal nodes. After a normal node is powered on, its red led will on, meaning that this node is waiting for clustering indication from the sink node\\
    92    * Then, turn on the Sink node\\
    93    * When the sink node is on, the network starts operation, e.g. the CHs are selected, the clusters are organized and the data packets from the member nodes are collected by the CHs\\
    94    * During the operation, you should be able to see that different leds are on on the nodes from time to time, where a bue led means a CH, a green led means a member node and a red led means that this node has depleted its energy and died. Please note that each change of the node led means a novel round.\\
     104  * First, turn on all normal nodes. Please that after a normal node is powered on, its red led will on, meaning that this node is waiting for clustering indication from the sink node.\\
     105  * Then, turn on the Sink node.\\
     106  * When the sink node is on, the network starts operation, e.g. the CHs are selected, the clusters are organized and the data packets from the member nodes are collected by the CHs\\
     107  * Please note that as the operation of EMR is separted into rounds. Each each round different CHs will be selection and different clusters will be formed. Therefore, during the operation, you should be able to see that different leds are on on the nodes from time to time, where a bue led means a CH, a green led means a member node and a red led means that this node has depleted its energy and died. Please note that each change of the node led means a novel round.\\
    95108
    96109 
    … …  
    109122       
    110123* Change parameters\\
    111       A user is able to change the parameters, e.g. {{{control_packet_size}}}, {{{data_packet_size}}} freely in the funciton {{{send_parameter()}}} in the file {{{EMRSinkC.nc}}}
     124      A user is able to change the parameters, e.g. {{{control_packet_size}}}, {{{data_packet_size}}} freely in the funciton {{{send_parameter()}}} in the file {{{EMRSinkC.nc}}}. For instance, the user could change the competetion range of the CH, smaller competetion range will generate more CHs and more blue led will be on.