Colin - there are basically 3 camps: * 15.4 beacons * some flavor of preamble sampling * time synchronized, e.g. SCP, Dozer, and TSMP
If you wanted to do something really useful, you'd find an abstraction of their layer-two features and limitations that makes it easy for layer-3 and up to do useful things with them. ksjp Colin O'Flynn wrote: > Hello All, > > First a quick question - I found this list on the IETF site. I assume it's a > public list, you don't have to be a member of the working group to submit? > > Anyway, a few of us are working on doing a 6lowpan implementation. I was > looking at doing a 'syncronized wake' to help save power yet get reasonable > response times. By my calculations you could wake every few seconds and still > have an exceptional battery life (year+). > > Since some nodes might need to wake up more often than others they might have > different schedules, and obviously you'd need some sort of beacon to > syncronize. The idea is each node has a "wake schedule" that nearby nodes > know, and will be listening at that time. But any node can TX at almost any > time. > > I don't want to do GTS though, as nodes can talk at any time. But I need a > way > to (a) sync nodes and (b) transmit wake schedule. > > So the question: would their be a standards-compliant way to do this? Or is > it > worth it trying to be standards compliant at this stage? It would be easy > enough to make some simple protocol up to do this for testing. > > Warm Regards, > > -Colin O'Flynn > > PS: If you are interested: hardware is 8-bit AVR devices, using uIP for IPv6 > implementation. The gateway router is AVR32 device, which can route over > ethernet. > _______________________________________________ > 6lowpan mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/6lowpan > _______________________________________________ 6lowpan mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lowpan
