Changes between Version 1 and Version 2 of Letibee


Ignore:
Timestamp:
Nov 4, 2010, 11:33:18 PM (14 years ago)
Author:
Sensei
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Letibee

    v1 v2  
    1 ...
     1= Letibee Island =
     2
     3[[PageOutline(2-4,Table of Contents,inline)]]
     4
     5== Introduction ==
     6
     7This document describes how to setup the SENSEI Letibee based island.
     8
     9== Objectives ==
     10
     11The network at CEA-Leti provides information to an end-user located at a gateway or through the Sensei platform. These information are
     12* Nodes position
     13* Average value of a measure done at each node side (ie luminance or temperature)
     14* An estimated map of the measure done at each node side.
     15
     16
     17
     18Figure 1 : CEA WSAN + Gateway for Sensei
     19
     20The WSAN activities do not use standardized communication protocols. Due to this constraint the communication with a node is not direct but through a virtual connection managed by a gateway (ie : a more powerful node included in the network).
     21
     22
     23
     24
     25
     26= Datamanager =
     27
     28The datamanager is a standalone software which have the following objectives:
     29
     30* Gather frames received on the usb port from the Letibee WSN
     31* Put data into database tables (rssi and position - see below)
     32* Remove older data if a time limit is specified
     33
     34
     35= Database =
     36
     37The database is a MySQL database. The script below create the tables and the rows useful for the datamanager and the gateway.
     38
     39
     40{{{
     41CREATE DATABASE sensei;
     42USE sensei;
     43
     44CREATE TABLE rssi (TxNodeId double);
     45ALTER TABLE rssi ADD (RxNodeId double);
     46ALTER TABLE rssi ADD (Rssi double);
     47ALTER TABLE rssi ADD (RelativeTime double);
     48ALTER TABLE rssi ADD (Time time);
     49ALTER TABLE rssi ADD (Date date);
     50
     51CREATE TABLE position (NodeId double);
     52ALTER TABLE position ADD (PositionX double);
     53ALTER TABLE position ADD (PositionY double);
     54ALTER TABLE position ADD (Time time);
     55ALTER TABLE position ADD (Date date);
     56
     57CREATE TABLE measTemperature (NodeId double);
     58ALTER TABLE measTemperature ADD (Temperature double);
     59ALTER TABLE measTemperature ADD (RelativeTime double);
     60ALTER TABLE measTemperature ADD (Time time);
     61ALTER TABLE measTemperature ADD (Date date);
     62
     63CREATE TABLE measLuminance (NodeId double);
     64ALTER TABLE measLuminance ADD (Luminance double);
     65ALTER TABLE measLuminance ADD (RelativeTime double);
     66ALTER TABLE measLuminance ADD (Time time);
     67ALTER TABLE measLuminance ADD (Date date);
     68
     69CREATE TABLE regmapOut (Type text);
     70ALTER TABLE regmapOut ADD (RefPositionX double);
     71ALTER TABLE regmapOut ADD (RefPositionY double);
     72ALTER TABLE regmapOut ADD (Value double);
     73ALTER TABLE regmapOut ADD (PositionX double);
     74ALTER TABLE regmapOut ADD (PositionY double);
     75ALTER TABLE regmapOut ADD (Time time);
     76ALTER TABLE regmapOut ADD (Date date)
     77}}}
     78
     79= Octave algorithms =
     80
     81Octave algorithms are used to compute rssi and position datas in order to generate more accurate positions datas and a regularized map. Different types of algorithm may be available.
     82
     83
     84= Gateway =
     85
     86The Gateway task is to read on demand the information saved in DB tables and send these results by using the appropriate format to the end-user through the Sensei framework.
     87
     88
     89The LetiBee plugin is based on a skeleton plugin and its HandleRequest method. Most of datas are reachable using GET methods, each making a request to the database to get the up-to-date datas. Published datas are listed below.
     90
     91= Published datas: =
     92
     93
     94The communication from the gateway to the end-user will be done using a text file. The Letibee WSAN is thinked like a geographic information database. This database contains nodes identities, positions (§Erreur : source de la référence non trouvée), measures and their histories (§Erreur : source de la référence non trouvée), estimate of others positions values using any kind of algorithms (§Erreur : source de la référence non trouvée). All these information will be send through the Sensei framework using the appropriate protocol and xml format.
     95
     96== WSAN description ==
     97
     98Resource description
     99        Sensors
     100                /letibee/nodes
     101
     102This resource returns the number of nodes in the letibee network and their identities.
     103
     104== Nodes position ==
     105
     106Resource description
     107Sensors
     108/letibee/[nodeid]/[position]
     109
     110Where position = positionX, positionY
     111
     112This resource returns the position of the identified node
     113
     114== Nodes measurements ==
     115
     116Resource description
     117Sensors
     118/letibee/[nodeid]/[scalar_sensor_type]
     119
     120With scalar_sensor_type= luminance, temperature
     121
     122This resource returns the measured value of the sensor and time reference for the considered node.
     123
     124== Regularized map ==
     125
     126Resources description
     127Sensors
     128/letibee/regmap
     129
     130This resource allows the user to choose between differents algorithms for computing the regmap, and the consensusStrength ; returns a VRML file (.wrl) (find a plugin here : http://cic.nist.gov/vrml/vbdetect.html)
     131
     132        Parameters
     133                /letibee/mapdescription
     134
     135This resource returns the name of the algorithm used to compute the last regmap.
     136
     137