Changes between Version 35 and Version 36 of Letibee
- Timestamp:
- Nov 5, 2010, 3:28:05 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Letibee
v35 v36 9 9 == Introduction == 10 10 11 This document describes the L etibee-based Wireless Network SENSEI island and in particular how to set it up.12 The L etibeenetwork uses some nodes equipped with the Letibee SoC, on top of which have been put an application11 This document describes the LETIBEE-based Wireless Network SENSEI island and in particular how to set it up. 12 The LETIBEE network uses some nodes equipped with the Letibee SoC, on top of which have been put an application 13 13 program running over Contiki/RIME stack. 14 14 … … 19 19 These information are: 20 20 * Nodes positions 21 * Average value of a measure done at each node side (ieluminance or temperature)22 * An estimated map with the measure s obtained ateach node side.21 * Average value of a measurement carried out at each node side (i.e. luminance or temperature) 22 * An estimated map with the measurements obtained from each node side. 23 23 24 24 [[Image(cea_wsan.png, 30%,center)]] … … 27 27 == Letibee WSAN == 28 28 29 The WSAN does 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).29 The WSAN uses a dedicated communication protocol. Each node communicates with the network not directly but through a virtual connection managed by a gateway ( a sink node and the application platform). 30 30 31 31 … … 35 35 36 36 37 LETIBEE network comprises nodes spatially distributed in a 2D area, including anchors with known locations and blind nodes to be positioned.37 The LETIBEE network comprises nodes spatially distributed in a 2D area, including anchors with known locations and blind nodes to be positioned. 38 38 Among anchors, one node generally plays the role of network coordinator and sink, whereas the other references are fixed routers. 39 39 The application protocol is mainly centralised, giving the sink a central role since it has to collect all data from the different nodes and to deliver them on the PC connected to it. 40 40 41 A specific application protocol was developed for network:41 A specific application protocol has been developed for network : 42 42 * Node discovery. 43 43 * Route discovery. … … 48 48 49 49 === Contiki and RIME === 50 It has been decided to port the RIME stack for Contiki v2.4 from SICS onto the LETIBEE node (CEA-Leti based on the Letibee chip, both of them using a 8051 uC).50 The RIME stack for Contiki v2.4 from SICS has been ported onto the LETIBEE node. The LETIBEE SoC, developped at CEA-Leti, includes a 8051 µC). 51 51 The RIME stack includes the functions for mesh networking including '''neighbour discovery''' (and neighbour table construction), '''route discovery''' (and routing tables construction) and '''multi-hop forwarding''' using the discovered routes. 52 52 A view of the stack is shown in the figure below. … … 55 55 56 56 Modules, used in the application, are described below: 57 * chameleon : The chameleon module manages the RIME headers, that producesbit-optimized headers.58 * abc : The abc module sends packets to all local area neighbors.59 * broadcast : The broadcast module sends packets to all local area neighbors with an a header thatidentifies the sender.60 * unicast : The unicast module sends a packet to an identified single-hop neighbor.61 * ipol ote: The ipolite module sends one local area broadcast packet within one time interval.62 * netflood : The netflood module does best-effort flooding.63 * multihop : The multihop module implements a multihop forwarding mechanism.64 * neighbor : The neighbor module manages the neighbor table.57 * chameleon : The chameleon module manages the RIME headers, which produce bit-optimized headers. 58 * abc : The abc module sends packets to all local area neighbors. 59 * broadcast : The broadcast module sends packets to all local area neighbors with a header which identifies the sender. 60 * unicast : The unicast module sends a packet to an identified single-hop neighbor. 61 * ipolite : The ipolite module sends one local area broadcast packet within one time interval. 62 * netflood : The netflood module does best-effort flooding. 63 * multihop : The multihop module implements a multihop forwarding mechanism. 64 * neighbor : The neighbor module manages the neighbor table. 65 65 * neighbor discovery: The neighbor-discovery module implements a periodic neighbor discovery mechanism. 66 * route : The route module handles the route table in Rime.67 * route discovery : The route-discovery module does route discovery for Rime.68 * mesh : The mesh module sends packets using multi-hop routing to a specified receiver somewhere in the network.66 * route : The route module handles the route table in RIME. 67 * route discovery : The route-discovery module does route discovery for RIME. 68 * mesh : The mesh module sends packets using multi-hop routing to a specified receiver somewhere in the network. 69 69 70 70 === Sequences of operations and protocol aspects === … … 72 72 The mesh operation is built in an ad hoc manner with a “route discovery” routine since the goal is to send frame (resquest/response) to node in the network. 73 73 The “route discovery” routine is used to build the route used to deliver the frames through the network. 74 Once the route is build, the unicast “routing” from the originator to the addressee can be used.74 Once the route has been built, the unicast “routing” from the originator to the addressee can be used. 75 75 76 76 The netflood operation can be used to flood all nodes in the network.
