Hi Robert,

I don't know if Colin is interested in more details, but I certainly am.

How frequently do you have to exchange sync. messages? Every 10/60/.. 
seconds?
How are your sync. messages scheduled? Via a distributed assignment?

Do you use CSMA/CA in a time slot?

Pieter

----- Original Message ----- 
From: "Robert Assimiti" <[EMAIL PROTECTED]>
To: "Colin O'Flynn" <[EMAIL PROTECTED]>; <[email protected]>
Sent: Thursday, March 06, 2008 10:17 PM
Subject: Re: [6lowpan] Syncronized Wake


Hello Colin,

The currently undergoing ISA100.11a standardization effort would be the 
perfect paradigm for what you are trying to accomplish. It is a standard 
geared towards industrial process and automation, but it definitely has 
applicability in commercial applications as well.

Currently employing the 802.15.4 PHY/MAC (although alternate PHY/MACs are 
being considered), the Field Devices (FFD/RFDs in 802.15.4 semantics) 
communicate during strictly enforced "time slots" without using beacons. 
This allows for prolonged battery life although frequent time 
synchronization messages must be exchanged.

Let me know if you are interested in more details.





"The nice thing about standards is that there are so many to choose from." - 
Andrew S. Tanenbaum
Robert Assimiti
Executive Staff Engineer
Office: [678]-202-6859
Mobile: [404]-578-0205
[EMAIL PROTECTED]


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf 
Of Colin O'Flynn
Sent: Sunday, March 02, 2008 9:21 AM
To: [email protected]
Subject: [6lowpan] Syncronized Wake

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


This e-mail (including any attachments to it) is confidential, proprietary, 
legally privileged, subject to copyright and is sent for the personal 
attention of the intended recipient only. If you have received this e-mail 
in error, please reply to advise us immediately, delete it and destroy any 
printed copies of it. You are notified that reading, disclosing, copying, 
distributing or taking any action in reliance on the contents of this 
information is strictly prohibited. No employee is authorized to conclude 
any binding agreement on behalf of NIVIS LLC with another party by e-mail 
without express written confirmation by an officer of the company. Although 
we have taken reasonable precautions to ensure no viruses are present in 
this e-mail, we cannot accept responsibility for any loss or damage arising 
from the viruses in this e-mail or attachments.
_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan


_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan

Reply via email to