Changes between Version 7 and Version 8 of Letibee

Timestamp:

Nov 5, 2010, 1:16:33 AM (14 years ago)

Author:

Sensei

Comment:

--

Letibee

@@ -71 +71 @@
 Figure 3 : Frame format over the air on the different protocol layers
 
-=== Gateway frame format ===
+==== Gateway frame format ====
 
 On the USB port, the APDU is appended with a frame delimiter 0xFF at its beginning, followed by the frame length.
 
-[[Image(frame_usb.png, 60%, center)]]
+[[Image(frame_usb.png, 40%, center)]]
 
 Figure 4 : Frame format over the USB port.
 
 To sink from gateway, the source address is added at its beginning of the APDU, the rest of the frame being unchanged. To gateway from sink, ‘/0’ ascii characters is added at its ending of the APDU.
-LOOKUP operation
+
+==== LOOKUP operation ====
+
 If the sink receives a Lookup Request from the Gateway:
-Send a Lookup Request Frame (with echoes) via netflood module.
-Waits for a Ping Response Frame from nodes.
-
-HELLO/BYE operations
+* Send a Lookup Request Frame (with echoes) via netflood module.
+* Waits for a Ping Response Frame from nodes.
+
+==== HELLO/BYE operations ====
 When a node join the network: 
-Send a Hello Request Frame (with echoes) via mesh module.
+* Send a Hello Request Frame (with echoes) via mesh module.
 When a node leave the network: 
-Send a Bye Request Frame (with echoes) via mesh module.
-
-PING operations
+* Send a Bye Request Frame (with echoes) via mesh module.
+
+==== PING operations ====
 If the sink receives a Ping Request from the Gateway:
-For each node
-Send a Ping Request Frame (with echoes if no response is received) via mesh module.
-Waits for a Ping Response Frame from the node (other responses are ignored) or the timeout
-Ping request
+* For each node
+** Send a Ping Request Frame (with echoes if no response is received) via mesh module.
+** Waits for a Ping Response Frame from the node (other responses are ignored) or the timeout
+
+# Ping request
 The Ping Request frame is initiated by a sink to ping a node so has for instance to check it is still alive. It can also be initiated by a node. 
-Ping response
+
+# Ping response
 The Ping Response frame is sent in response to a Ping request frame. It provides the number of hops to reach the node which initiated the ping request.
 
-DV-HOP operation
+==== DV-HOP operation ====
 If the sink receives an Anchor Request from the Gateway:
-For each node
-Send an Anchor Request Frame (with echoes if no response is received)
-Waits for an Anchor Response Frame from the node (other responses are ignored) or the timeout
+* For each node
+** Send an Anchor Request Frame (with echoes if no response is received)
+** Waits for an Anchor Response Frame from the node (other responses are ignored) or the timeout
+
 The nodes, including the anchor nodes, do not embed a scheduler. However, when they receive an Anchor Request Frame, they perform the following sequence of operations:
-If an Anchor Request Frame is received
-For each anchor node (listed in the Anchor Request Frame)
-Send a Ping Request Frame
-Waits for a Ping Response Frame from the anchor node (other responses are ignored) or the timeout
-Anchor request
+
+* If an Anchor Request Frame is received
+** For each anchor node (listed in the Anchor Request Frame)
+*** Send a Ping Request Frame
+*** Waits for a Ping Response Frame from the anchor node (other responses are ignored) or the timeout
+
+# Anchor request
 The Anchor Request frame is initiated by a sink to request a node to issue a ping request command frame towards a list of anchor nodes. This frame aims at being used by the DV-HOP location algorithm which requires the knowledge of the number of hops between any node in the network and any anchor in the network.
-Anchor response
+
+# Anchor response
 The Anchor Response frame is initiated by a node in response to Anchor Request received from a sink. This frame aims at being used by the DV-HOP location algorithm which requires the knowledge of the number of hops between any node in the network and any anchor in the network.
 The header contains the number of anchors seen by the node, and the payload contains for each seen anchor the (anchor address, number of hops) doublet.
 
-LOCALIZATION operation
+==== LOCALIZATION operation ====
 Each node also performs neighbour discovery in a nearly periodic manner by broadcasting advertisement frames. This operation is used to collect the RSSI information from the 1-hop neighbours. Note that 
-The advertisement frames are sent after a time comprised between 1 and 2 seconds in our setup and randomly chosen for each frame.
-The RSSI information corresponds to the RSSI measured during reception of advertisement frames from other nodes in the network.
-The advertisement frames sent by the nodes do not trigger any response from the nodes which receives it.
+
+* The advertisement frames are sent after a time comprised between 1 and 2 seconds in our setup and randomly chosen for each frame.
+
+* The RSSI information corresponds to the RSSI measured during reception of advertisement frames from other nodes in the network.
+
+* The advertisement frames sent by the nodes do not trigger any response from the nodes which receives it.
+
 The Gateway performs the start (or stop) operation. The sink will therefore poll each node in the network in a round robin manner to collect neighbours RSSI information from all the nodes.
-While stop request is not received:
-Every second
-For each node
-Send a Neighbour Request Frame
-Waits for a Neighbour Response Frame from the node (other responses are ignored) or the timeout
-Neighbor request
+
+* While stop request is not received:
+
+** Every second
+*** For each node
+**** Send a Neighbour Request Frame
+**** Waits for a Neighbour Response Frame from the node (other responses are ignored) or the timeout
+
+# Neighbor request
 The Neighbor request frame is initiated by a sink to request a node to send its table made of the (neighbour address, RSSI time, RSSI value, LQI value) quadruplets.
-Neighbor response
+
+# Neighbor response
 The Neighbor response frame is initiated by a node in response to a Neighbor request command frame received form a sink. It contains its table of neighbours and is made of the (neighbour address, RSSI time, RSSI value, LQI value) quadruplets as requires by the RSSI based location algorithm. The RSSI time field indicates in seconds the age of the RSSI and LQI entries. 
 Moreover the frame payload contains the values of the sensor readings of the node (8 bytes, fixed with 1 byte per sensor according to the bitmap field “active_sensors” of the header.
@@ -136 +152 @@
 The header also gives the number of hops from the node to the sink which sent the neighbour request command frame.
 
-ROUTE operation
+==== ROUTE operation ====
 If the sink receives a Route Request from the Gateway:
-For each node
-Send a Route Request Frame (with echoes if no response is received) via mesh module.
-Waits for a Route Response Frame from the node (other responses are ignored) or the timeout
-Route request
+* For each node
+** Send a Route Request Frame (with echoes if no response is received) via mesh module.
+** Waits for a Route Response Frame from the node (other responses are ignored) or the timeout
+
+# Route request
 The Route Request frame is initiated by a sink to request a node to send its routing table made of the entries (destination address, next hop adress, route cost, route time). This frame shall not be confounded with the RREQ frames that are classically used in the networking layer of the protocol.
-Route response
+
+# Route response
 The Route Request frame is initiated by a node in response to a Route request command frame received from a sink. It contains the entries of the routing table (destination address, next hop adress, route cost, route time). This frame shall not be confounded with the RREP frames that are classically used in the networking layer of the protocol.
 The route cost contains a cost metric for the corresponding route, whereas the route time contains a value in seconds about the age of the route.
-
-
 
 == Datamanager ==