Changes between Version 13 and Version 14 of EMR


Ignore:
Timestamp:
Oct 12, 2010, 4:14:01 PM (14 years ago)
Author:
Sensei
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • EMR

    v13 v14  
    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) 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. 
     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 illustrating how to install the EMR resource, it briefly explains how to run this routing solution. 
    44
    55[[PageOutline(2-3,Table of Contents,inline)]]
    … …  
    99=== Hot-spot issue in WSNs
    1010
    11 In 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.
     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 network and drain energy at an uneven rate is referred to as 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.
    1212
    13 Though 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.
     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 existing after some nodes have depleted energy. 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 the 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 information of 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 SENSEI framework and thus needs to be addressed.
    1414
    1515=== Objectives of EMR
    1616
    17 The 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.
     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 deployed sensor nodes are able to cover the entire network) 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.
    1818
    19 The 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.
     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. These rangea are then applied in EMR for CH selection.
    2020
    2121=== Operation of EMR
    … …  
    4141We 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.
    4242
    43 EMR 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:
     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 software packages for normal nodes and the sink are separated. The following provides the detailed information about the structure and the content of the EMR software package:
    4444
    4545* For a normal node \\
    … …  
    6464=== Installation
    6565
    66 The 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.
     66The installation of EMR is rather simple and the following briefly introduces how the EMR resource could be loaded to the normal nodes and the sink node.
    6767
    6868* 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.
    … …  
    102102
    103103* Operation\\
    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.\\
     104  * First, turn on all normal nodes. Please note that after a normal node is powered on, its red led will be on, meaning that this node is waiting for clustering indication from the sink node.\\
    105105  * 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.\\
     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 and are finally forwarded to the sink after data aggregation by the CHs.\\
     107  * Please note that as the operation of EMR is separated into rounds. During each round different CHs will be selected and different clusters will be formed. Therefore, during the operation, you should be able to see that from time to time, different leds of the nodes will be on, where a blue 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 led colour of the node means a novel round and the novel role that the node takes during this round.\\
    108108
    109109 
    … …  
    116116}}}
    117117
    118       The debug messages should start to be shown in the terminal as below:
     118      The debug messages should start to be shown in the terminal as following:
    119119
    120120[[Image(debug_msg.png, 50%, center)]]
    … …  
    122122       
    123123* Change parameters\\
    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.
     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 during the network operation.