1 / 39

How Dataflow is opening the Internet Frontier

How Dataflow is opening the Internet Frontier. Dataflow-to-synthesis Retrospective David E. Culler UC Berkeley Arch Rock. The Internet. The Internet Frontier. Save Resources. Improve Productivity. Enable New Knowledge. Enhance Safety & Security. Preventing Failures. Protect Health.

yoshi
Download Presentation

How Dataflow is opening the Internet Frontier

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. How Dataflow is opening the Internet Frontier Dataflow-to-synthesis Retrospective David E. Culler UC Berkeley Arch Rock

  2. The Internet

  3. The Internet Frontier

  4. Save Resources Improve Productivity Enable New Knowledge Enhance Safety & Security Preventing Failures Protect Health Improve Food & H20 Why “Real” Information is so Important? Increase Comfort High-Confidence Transport

  5. …but what has Dataflow got to do with it?

  6. Arvind’s Law: Value derived from concurrent activities is inverse to the cost of integrating communication and computation - so tag it and do it all! all I ever learned … Culler’s Corollary: but storage increases with concurrency - so do it with bounded resources

  7. all I ever learned … TTDA Monsoon

  8. Ninja Staged Event Driven Arch. for massive internet servers Log of Something Time so at the public school … NOW Split-C Active Messages TAM Threaded Abstract Machine - two level scheduling hierarchy - expose network to the compiler - no allocation on arrival

  9. Microcontroller Flash Storage Radio Communication Sensors Enabling Technology IEEE 802.15.4

  10. Enabling Technology • Not your 3M’s • MIPs of proc. • KB of RAM / Prog • kbps of bandwith • uW of power Physical World

  11. Silicon World Wireless Sensors Storage Processing Enabling Research Build an approximation of the future that you imagine and study it to learn what “is true” in that possible world. Berkeley Mote / TinyOS Platform Physical World

  12. zeevo BT Intel MOTE2 Intel iMOTE Intel rene’ Intel/UCB dot TIP Intel cf-mica BTNode trio Eyes SmartDust WeC Sensit / Expeditions Rene NEST Mica Telos XBOW mica XBOW cc-dot XBOW mica2 XBOW rene2 XBOW micaZ digital sun rain-mica Bosch cc-mica Dust Inc blue cc-TI Sensicast nest 6/02 11/00 1/02 3/03 5/04 WSN Research Phenomenon…

  13. NEST SmartDust Wireless Sensor Networks Sensors Storage Wireless Processing Berkeley…and beyond

  14. Applications and Services Over-the-air Programming Network Protocols Blocks, Logs, Files Streaming drivers Scheduling, Management Link Radio Serial Flash MCU, Timers, Bus,… ADC, Sensor I/F Sensors Wireless Processing Storage The Systems Challenge TinyOS 2.0 WSN mote platform Communication Centric Resource-Constrained Event-driven Execution

  15. The Solution • Basically a dataflow engine in disguise • Two-level Scheduling Hierarchy • Asynchronous events integrate external world • Computational Tasks • Collections of Tasks and Events + Bounded State form a Component. • Never, never, never wait. Do work or go to sleep!!!!!!!!!! • Recognition of reality • Zillions of unattended devices embedded in a noisy physical world require an unprecedented level of robustness and SIMPLICITY • Application = Structured Graph of Components connected by Well-Designed Interfaces. • Escape Velocity • Our System and Network Abstractions (ca. Unix + Sockets + TCP) have been essentially unchanged for decades and are deeply steeped in the 3M design point! => Provide a framework for defining boundaries and let the new layers fall where they may.

  16. * System design * Leakage (~RAM) * Nobody fools mother nature What we mean by “Low Power” • 2 AA => 1.5 amp hours (~4 watt hours) • Cell => 1 amp hour (3.5 watt hours) Cell: 500 -1000 mW => few hours active WiFi: 300 - 500 mW => several hours GPS: 50 – 100 mW => couple days WSN: 50 mW active, 20 uW passive 450 uW => one year 45 uW => ~10 years Ave Power = fact * Pact + fsleep * Psleep + fwaking * Pwaking

  17. Wireless Client vs Wireless Server • Wireless Client • needs to last a day or two • has a human to keep them working properly • mostly formats specific incoming data for display • Wireless server • needs to last for long periods • must be self-managing, adaptive, robust • Generates meaningful data for many uses • Often mobile (!!!)

  18. 2 2 2 2 1 1 2 Self-Organized Mesh Routing 0

  19. Appln Transport Routing Scheduling Topology Link Phy Sensor Network “Networking” EnviroTrack Hood TinyDB Regions FTSP Diffusion SPIN TTDD Trickle Deluge Drip MMRP Arrive TORA Ascent MintRoute CGSR AODV GPSR DSR ARA GSR GRAD DBF DSDV TBRPF Resynch SPAN GAF FPS ReORg PC Yao SP100.11a SMAC WooMac PAMAS BMAC TMAC WiseMAC Pico 802.15.4 Bluetooth eyes RadioMetrix CC1000 nordic RFM wHART Zigbee Zwave

  20. What WSNs really look like Deploy Query Command Visualize Client Tools External Tools Excel, Matlab Enshare, etc. Internet GUI Legacy Data analysis Field Tools Gateway Embedded Network

  21. THE Question If Wireless Sensor Networks represent a future of “billions of information devices embedded in the physical world,” why don’t they run THE standard internetworking protocol?

  22. Web Services XML / RPC / REST / SOAP / OSGI HTTP / FTP / SNMP TCP / UDP IP 802.11g 802.11 802.11b 802.11a Ethernet RFM,CC10k,…,802.15.4 Enet 10G Enet 1G Enet 10M Enet 100M GPRS THE Question ? Sonet Serial Self-Contained Plugs and People

  23. The Answer They should • Substantially advances the state-of-the-art in both domains. • Implementing IP requires tackling the general case, not just a specific operational slice • Interoperability with all other potential IP network links • Potential to name and route to any IP-enabled device within security domain • Robust operation despite external factors • Coexistence, interference, errant devices, ... • While meeting the critical embedded wireless requirements • High reliability and adaptability • Long lifetime on limited energy • Manageability of many devices • Within highly constrained resources

  24. LoWPAN - 802.15.4 the low-power wireless IP Link • 1% of 802.11 power, easier to embed, as easy to use. • 8-16 bit MCUs with KBs, not MBs. • Off 99% of the time Web Services XML / RPC / REST / SOAP / OSGI HTTP / FTP / SNMP TCP / UDP IP 802.11 802.15.4, … Ethernet Sonet

  25. Proxy / Gateway Making sensor nets make sense Web Services XML / RPC / REST / SOAP / OSGI HTTP / FTP / SNMP TCP / UDP IP 802.11 802.15.4, … Ethernet Sonet IETF 6lowpan

  26. Challenges for IP over 802.15.4 • Header • Standard IPv6 header is 40 bytes [RFC 2460] • Entire 802.15.4 MTU is 127 bytes [IEEE ] • Often data payload is small • Fragmentation • Interoperability means that applications need not know the constraints of physical links that might carry their packets • IP packets may be large, compared to 802.15.4 max frame size • IPv6 requires all links support 1280 byte packets [RFC 2460] • Allow link-layer mesh routing under IP topology • 802.15.4 subnets may utilize multiple radio hops per IP hop • Similar to LAN switching within IP routing domain in Ethernet • Allow IP routing over a mesh of 802.15.4 nodes • Options and capabilities already well-defines • Various protocols to establish routing tables

  27. A little example Internet WiFi 192.168.1.xxx App Server andPresentation WiFi ArchRockDemo Router Web Services Proxy Server 6LoWPAN Router (6to4) 192.168.1.109 10.97.0.xxx FD97::xxx

  28. Len SFD Fchk FCF Max 127 bytes HC1 dsp IP UDP Dispatch: coexistence HC1 dsp mhop Header compression frag dsp Mesh (L2) routing frag HC1 mhop dsp Message > Frame fragmentation 6LoWPAN Format Design • Orthogonal stackable header format • Almost no overhead for the ability to interoperate and scale. • Pay for only what you use IEEE 802.15.4 Frame Format D pan Dst EUID 64 S pan Src EUID 64 preamble Dst16 Src16 DSN Network Header Application Data IETF 6LoWPAN Format HC1

  29. Proxy Gateway Router A new internet citizen Rich Web View per Node Web Services / WSDL SNMP, Ganglia, Email Adapters Data Warehouse • Sensor & Mgmt Services • HTTPm • Systat, Netstat, Echo • Ping, Traceroute, DHCP • Reboot Browser, Enterprise, Controller IP - layer 7 TCP/UDP IP WiFi GPRS EtherNet LoWPAN High Reliability Triply Redundant Ultra-low power Highly Responsive AES128 Secured IP-based Mesh Network nc, telnet, ping, traceroute…

  30. Low-Power Schedule-Free Routing • Extends preamble sampling [DARPA packet radio, 1984] and low-power listening [UC Berkeley, 2000] to enable battery powered routers. • Simplicity of an “always on” network at low-duty cycle by shifting effort from (frequent) listening to (infrequent) transmission. • Flexible and configurable • Overlay time synchronization service for correlated sampling and scheduling optimizations. • Eliminates need for connectivity / interference survey • Eliminates schedule incompatibility across clusters • Eliminates costly scan for schedule on join / rejoin

  31. Low Impact of 6LoWPAN on Lifetime –Comparison to *Raw* 802.15.4 Frame * * Energy Δ for fixed payload Max Payload * fully compressed header * additional 16-byte IPv6 address

  32. Power of IP Connectivity Firewall Firewall Ethernet WiFi GPRS LoWPAN send (IP_addr, port, UDP, &data, len)

  33. Proxy Gateway Router Still a Role for Proxies Rich Web View per Node Web Services / WSDL SNMP, Ganglia, Email Adapters Data Warehouse • Sensor & Mgmt Services • HTTPm • Systat, Netstat, Echo • Ping, Traceroute, DHCP • Reboot Browser, Enterprise, Controller IP - layer 7 TCP/UDP IP WiFi GPRS EtherNet LoWPAN High Reliability Triply Redundant Ultra-low power Highly Responsive AES128 Secured IP-based Mesh Network nc, telnet, ping, traceroute…

  34. Service Description find publish bind Service Oriented Architecture Service Registry • Service Description => interface & implementation • Operations supported, input/output objects • Bindings to network and data encoding schemes • Network address where service can be invoked • Enough that client can generate code to access the service well Service Requestor Service Provider

  35. <request service> Service Description Sampled Value 11 010110111 11 010010001 int temp; 010010001 Physical Signal Embedded Web Services < get temp … set sample_rate set alarm … > www.weather.com Web Services <value> source=library time=12:53 temp=26.7 <\value> <value> source=library time=12:31 temp=25.1 <\value> XML information Wireless Packets 802.15.4

  36. tier3 SensorNet GW/Proxy physical info net tier4 SensorNet mote Sensor A new WSN world client tier1 AquaLogic server tier2 Perl Python C# NetWeaver Embedded Services Excel

  37. The Next Tier • Today: we can connect essentially everybody • Tomorrow: we will be able to connect and observe essentially everything of value • physical spaces, objects, and their interactions • physical information, not just keystrokes • and we know dataflow is the technology of tomorrow Comp:People 1:1,000,000 Mainframe Mini 1:1,000 Workstation PC 1:1 Laptop PDA Phone 1000:1 Motes years

  38. Happy Birthday and may the dataflowers bloom

  39. …and a new IETF working group • mailto: rsn@ietf.org Thanks

More Related