1 / 13

Towards System Architecture for Tiny Networked Devices

Towards System Architecture for Tiny Networked Devices. David Culler http://www.cs.berkeley.edu/~culler U.C. Berkeley Wireless hoo-hah 5/30/2000. Scalable Infrastructure highly available persistent state (safe) databases, agents service programming environment. Service Path.

demetrius-duran
Télécharger la présentation

Towards System Architecture for Tiny Networked Devices

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Towards System Architecture for Tiny Networked Devices David Culler http://www.cs.berkeley.edu/~culler U.C. Berkeley Wireless hoo-hah 5/30/2000

  2. Scalable Infrastructure • highly available • persistent state (safe) • databases, agents • service programming environment Service Path • Ubiquitous Devices • billions • sensors / actuators • PDAs / smartphones / PCs • heterogeneous An End-to-end Perspective • Desktops • max out at few 100M • in your face • connected to the infrastructure wireless hoo hah

  3. Key Characteristics of TNDs • Small physical size and low power consumption • Concurrency-intensive operation • flow-thru, not wait-command-respond • Limited Physical Parallelism and Controller Hierarchy • primitive direct-to-device interface • Diversity in Design and Usage • application specific, not general purpose • huge device variation => efficient modularity => migration across HW/SW boundary • Robust Operation • numerous, unattended, critical => narrow interfaces wireless hoo hah

  4. ‘Mote’ Initial Platform wireless hoo hah

  5. TOS Tiny OS • Scheduler and Graph of Components • constrained two-level scheduling model: threads + events • Component: • Frame • Threads (concurrency) • Commands, and Handlers (events) • Constrained Storage Model • frame per component, shared stack, no heap • Very lean multithreading • Layering • components issue commands to lower-level components • event signal high-level events, or call lower-level commands wireless hoo hah

  6. send_msg(addr, type, data) power(mode) msg_rec(type, data) msg_send_done (success) init Internal State Messaging Component send_msg_thread TX_packet(buf) Power(mode) RX_packet_done (buffer) init TX_packet_done (success) TOS Component /* Messaging Component Declaration */ //ACCEPTS: char TOS_COMMAND(AM_SEND_MSG)(char addr,char type, char* data); void TOS_COMMAND(AM_POWER)(char mode); char TOS_COMMAND(AM_INIT)(); //SIGNALS: char AM_MSG_REC(char type, char* data); char AM_MSG_SEND_DONE(char success); //HANDLES: char AM_TX_PACKET_DONE(char success); char AM_RX_PACKET_DONE(char* packet); //USES: char TOS_COMMAND(AM_SUB_TX_PACKET)(char* data); void TOS_COMMAND(AM_SUB_POWER)(char mode); char TOS_COMMAND(AM_SUB_INIT)(); wireless hoo hah

  7. Composition mapper router sensor appln appln Active Messages packet Serial Packet Temp Radio Packet SW byte HW UART Radio byte i2c photo bit clocks RFM wireless hoo hah

  8. Timing diagram of event propagation Dynamics of Events and Threads • Message Send Transition wireless hoo hah

  9. Components Packet reception work breakdown Percent CPU Utilization Energy (nj/Bit) AM 0.05% 0.20% 0.33 Packet 1.12% 0.51% 7.58 Ratio handler 26.87% 12.16% 182.38 Radio decode thread 5.48% 2.48% 37.2 RFM 66.48% 30.08% 451.17 Radio Reception - - 1350 Idle - 54.75% - Total 100.00% 100.00% 2028.66 Empirical Breakdown of Effort • can take apart time, power, space, … • 50 cycles threads ovhd, 10 cycle event ovhd wireless hoo hah

  10. Storage Breakdown (C Code) 3450 B code 226 B data wireless hoo hah

  11. Programming CAD • Can assemble overall system using WV structural VHDL • Scripts convert to all the make magic wireless hoo hah

  12. Projects this Term • Device Proxy Architecture • mobile-IP RDP variant • Integration with infrastructure • JINI and Ninja • Multithreaded vs federated archtiecture • Pluggable adaptive MAC layer • often periodic, moment of crisis • sleep cycling • Ad Hoc routing component • Connectivity-based location detection • smart badge + sensor in smart space wireless hoo hah

  13. Looking forward • Mote “designed for experimentation” this summer • Lots of projects now “small matter of programming” • Good basis for incorporating more exciting HW architectures wireless hoo hah

More Related