[Tinyos-devel] LPL API for protocols

[Vlado Handziski]

On Mon, May 19, 2008 at 7:29 PM, David Moss <dmm at rincon.com> wrote:

>
> Many practical networks today require heterogeneous low power communication
> intervals.  In fact, _all_ of my network deployments have been
> heterogeneous, simply because the networking nodes are only one part of the
> system.  Networking nodes are usually on their own homogeneous duty cycling
> schedule, but they must interact with other nodes that are not: like the
> PDA
> in your hand, or the non-network node responsible for detecting or
> controlling, or the node plugged into the wall.  Being able to communicate
> with nodes that are on different receive check intervals than your local
> node is critical for many practical systems. This necessitates a per-packet
> low power configuration.
>
>
Are you handing all this on application level or from some lower protocol
component, integrated in the radio stack, that matches the node IDs and
select a proper interval?

I am trying to understand if there is any benefit from tunneling these
control interfaces all the way to the AM components. Traditionally we have
been using the packet metadata as a blackboard that help us pass this kind
of information between the different components of the stack, without
forcing us to settle on a fixed composition or layering. Moving away from
this approach will make things more simple but at the same time it will
constrain the freedom to experiment with composition. In this sense, I agree
with your conclusion that fixing the current LPL control interface is
probably the best way to proceed.

Vlado
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.millennium.berkeley.edu/pipermail/tinyos-devel/attachments/20080519/b82c17c3/attachment.htm