1. Architecture Overview Tiny OS Layering Communication – Physical Medium & Media Access Control Protocols Infrastructure Based Communication Protocols Device Proxies – Infrastructure support

2. Tiny OS Possibilities Glorified Bus Controllers Provides simplicity and adaptability, infrastructure provides usability Simplistic Servers More difficult to program, possible communication benefits Micro-Linux Boxes Flexible, general purpose tools

3. Communication Protocols must support Use RF Monolithics – Low Power/Cost Should not determine lowest power consumption of devices (i.e. Require device to be active minimum amounts of time.) Are there any standards we should try to comply with?

4. Infrastructure Based Communication Protocols Support mobility in a transparent way Provide tiny devices the illusion of IP connectivity Make brief periods of disconnection invisible to the real world Buffering and Caching information for clients Attempt to optimize delivery overheads

5. Possible Architecture Traditional Clients/Services Infrastructure Based Services IP Device Drivers Comm. Layers Delivery Qs Device Proxies Base Stations

6. Strengths… Complex Device drivers are pushed into the infrastructure where they are easy to write, debug, & upgrade Devices can be composed by the infrastructure (Speaker + Camera + Display Video Conference Device) Allow small devices to reliably service many clients (device proxies/surrogates) Heterogeneity can be masked by software adapters

7. Optimizations…. Ninja style code migration allows layers to collapse as an optimization Higher power devices can take on additional functionality Complex base stations can perform protocol translations for clients