1 / 11

Building Embedded IP

Building Embedded IP. Raffi Krikorian Physics and Media. Building Internet 0. Traditional networking hardware research focuses on bigger and faster pipes (Internet 2 ) We focus on bit-dribbling hardware. Bridging the bandwidth divide. Bringing IP to the leaf node

kitty
Download Presentation

Building Embedded IP

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. Building Embedded IP Raffi Krikorian Physics and Media

  2. Building Internet0 • Traditional networking hardware research focuses on bigger and faster pipes (Internet2) • We focus on bit-dribbling hardware

  3. Bridging the bandwidth divide • Bringing IP to the leaf node • Revisiting hardware transports and redesigning logical transports • Cheap, low bandwidth IP (a level below Ethernet)

  4. Going really small • Distributed scalable system – no central point of control/servers are “bad” • Devices own their data and own their threads • Self organizing • Growing

  5. Building the first embodiment of small things • RS-485 communication • mature industrial practice • no active joints • media access costs pennies • PIC microcontrollers • built in UARTs • plenty of space for networking code • just a few dollars

  6. Building more small things • Different physical transports • DSSS over powerlines • Wireless RF • Ultrasonic • Revisiting old transports – slowing them down makes them a lot more accessible

  7. Cramming bits is nothing new • “Delayered” software stacks • ARP, IP, ICMP, UDP, TCP – IPv4 compliant in 2K code • HTTPd 0.9 server – 1K code

  8. Naming, Classifying, Communication • IDs for each device – unified or multiple • For today, use Zeroconf – sub-DHCP • For tomorrow, possibly use IPv6 as the unique address through mini-routing? • Schema for identifying devices • Communication standards

  9. Programming and Coordinating a mass of devices • Programming arbitrary massively parallel distributed systems is hard, building simple ones is easier • These systems exhibit • Scale complexity • Interaction complexity • Minimal resources • Spatial relations

  10. Building higher level systems • Make it easy to cause complex behavior to occur • “Google-like” services • Hive • JXTA • Make it simple for complex behavior to emerge

  11. How do you test all of this? • First test installation was in Barcelona, moving towards second • … • CBA’s new home is first permanent testbed

More Related