home  wiki

Diff: MWRPAdhocFrottleDev

--- Version 5 
+++ Version 6 
@@ -190,6 +190,54 @@ 
 
 But multiple tokens following the same rules may be able to circulate in a mesh for a long time without ever meeting each other.  In a static mesh, tweaking the timeouts and search algorithm variables can make it more likely that multiple tokens do not meet.  The protocol itself may be able to specify a method for tokens to automatically tweak their own parameters and pass tweak '''suggestions''' to other nodes to maximise the number of simultaneous tokens circulating, and minimise the number of token collisions. 
 
+!! Current implementation 
+The current implementation of frottle for mesh retains the concept of a master polling known clients. What is diferent to the BSS version is that a Node that is a client of one domain can be a master of another. When that Node registers with the first domain it declares itself as a master. The Master of the first domain now knows it has become a co-master and has to pass control to the second Master when it concludes a poll. 
+An example probably makes this clearer: 
+!!! Scenario 1 
+Domain First D 
+Node A, Master First D 
+Node B, Client First D 
+Node C, Client First D 
+Nodes start in random order, there is no control until Node A is up, then It receoves broadcast register packets from Node B and Node C. Node A starts to regulate transmissions of all nodes according to the RF Rate of the link and the defined parameters. 
+There is another node Node D that is in range of Node A. Node D is a Master of another "cluster" of Nodes 
+Domain Second D 
+Node D, Master Second D, Client First D 
+Node E, Client Second D 
+Node F, Client Second D 
+When Node D starts it will accept registration for Node E and Node F. Because it is also a Client for doamain FirstD it registers as a Client in that domain with Node A. In the registration packet it identifies itself as a Master of Domain Second D. 
+Node A will poll Node B, Node C and Node D. When it reaches Node D it passes conrol in the poll. Node D will transmitt any traffic it has and then do it's poll of Node E, Node F. At this stage Having no Clients registered that are masters it will pass control back to Node A. 
+   Node B )------( Node A )------( Node C     Domain First D 
+                     V 
+                     | 
+                     | 
+                     A 
+   Node E )------( Node D )------( Node F     Domain Second D 
+!!! Scenario 2 
+Same as above but Node A is also a Client of Second D. 
+In this case Node D registers as a client with Node A and Node A registers as a client with Node D. 
+Node A polls its clients then passes control to Node D. Node D polls its clients then passes control to Node A  - we have a ring rather than a out and back. 
+!!! General case 
+This can continue indefinitely with any Master passiing control to a leaf Master  (where it comes back after the leaf Master is done) or a ring Master (where control moves forward all the time). Note, you can configure a very sub-optimal arrangement as it stands, you really need to think about what nodes are Masters and where control passes next. 
+This requires prior identification of the Nodes that will be masters and definition of the domains. Future implementations may be able to derive this information from the routing tables and nodes could dynamicly become Masters if needed. I'm thinking along the lines of what happens in the MAC layer of dot11.15 here, the way PicoNets and ScatterNets are formed and destroyed. 
+!!! Issues 
+* Can cope with lost "token" but need to add duplicate token quenching. 
+* Staticly configuring relationships sucks but makes for a nice controlled environment to get it working 
+* Need to make it smarter so we can partition and have multiple rings in operation at once based on LOS and interference information. 
 
 ---- 
 
[EditText] [Spelling] [Current] [Raw] [Code] [Diff] [Subscribe] [VersionHistory] [Revert] [Delete] [RecentChanges]
> home> about> events> files> members> maps> wiki board   > home   > categories   > search   > changes   > formatting   > extras> site map

Username
Password

 Remember me.
>

> forgotten password?
> register?
currently 0 users online
Node Statistics
building132
gathering192
interested515
operational242
testing216