EECS194 The Internet of Everyday Things

1
EECS-194 The Internet of Everyday Things

• David E. Culler
• Jonathan Hui
• EECS
• University of California Berkeley

2
Introductions EECS194 Staff
David E. Culler - Instructor culler_at_cs.berkeley.ed
u http//www.eecs.berkeley.edu/culler 627 Soda
Hall, 643-7572 Office hours W 1-3, Th
1-3 Jonathan Hui - TA jwhui_at_cs.berkeley.edu http
//www.eecs.berkeley.edu/jwhui/ Prabal Dutta
development TA prabal_at_eecs.berkeley.edu
3
Plan for Today

• 11-12 Introduction to the Course
• Broad concepts and Technology Trends
• Term plan
• Logistics
• Discussion
• 1-4 Interactive Embedded Internet Lab
• Break for lunch about 1230
• 1-1 Interviews wrt Survey
• Scheduling
• Launch between lab study
• 3-4 Repeat parts of Intro for those not here yet

4
1997 - The Internet of Every Computer
5
2007 - The Internet of Every Body
6
2017 - The Internet of Everyday Things
7
Why Real Information is so Important
Enable New Knowledge
Increase Comfort
Enhance Safety Security
Preventing Failures
High-Confidence Transport
8
Everyday Things

• Appliance
• Stand-alone electrical, mechanical, informational
  system integrated for a particular function
• Why stand-alone?
• Why so particular?

9
Universality of Information Technology

• Computing
• Communication
• What is it used for?

10
Example Every Day Thing
User Control Loop
UI Sensors - Knob position - Timer
UI Display - Temp - Time - Status
Inner Control Loop
Sensors - thermocouples - gas flow - door open
Actuators -relay / valve -relay / light
Set Point
Controller
11
A Programmable Networked Thing
Network
12
Broad Technology Trends
Moores Law transistors on cost-effective chip
doubles every 18 months
Bells Law a new computer class emerges every 10
years

• Today 1 million transistors per

Same fabrication technology provides CMOS radios
for communication and micro-sensors
13
Low-Tech Enabling Technology
Network
IEEE 802.15.4
14
The Systems Challenge

• Monitoring Managing Spaces and Things

applications
Store
Comm.
actuate
sensing
Proc
Power
technology
Miniature, low-power connections to the physical
world
15
UCB gt A worldwide community
16
The Berkeley Mote
WINS(UCLA/ROckwell)
Intel rene
SmartDust WeC
Rene
00
01
03
02
04
06
05
07
97
99
98
LWIM
Expedition
NEST
Cyber-Physical
SENSIT
NETS/ NOSS
CENS STC
DARPA
NSF
17
Example for today TelosB
18
Mote the Next Generation - EPIC

• http//www.eecs.berkeley.edu/prabal/projects/epic
  /

19
TinyOS
TinyOS 2.0
WSN mote platform
Communication Centric Resource-Constrained Event-d
riven Execution
20
Self-Organized Mesh Routing
0
21
Why Multihop Routing

• Power!
• to transmit D grows as D3 or worse
• to route distance D grows linearly
• Bandwidth (spatial multiplexing)
• With n nodes in a single cell, each gets at most
  1/n bandwidth
• Many small cells gt many simultaneous
  transmissions.
• Reliability (spatial diversity)
• Individual links experience interference,
  obstacles, and multipath effects
• Even short-range wireless wires require human
  nurturing
• IRDA, Bluetooth, WiFi, Cell
• Provides spatial diversity and receiver diversity
• rather than antenna diversity
• Protocol level reliability

22
What we mean by Low Power

• 2 AA gt 1.5 amp hours (4 watt hours)
• Cell gt 1 amp hour (3.5 watt hours)
• Cell 500 -1000 mW gt few hours active
• WiFi 300 - 500 mW gt several hours
• GPS 50 100 mW gt couple days
• WSN 50 mW active, 20 uW passive
• 450 uW gt one year
• 45 uW gt 10 years
• Ave Power fact Pact fsleep Psleep
  fwaking Pwaking

23
Routing Mechanism

• Upon each transmission, one of the recipients
  retransmits.
• Which one?
• What determines a link?

24
Question
If Wireless Sensor Networks represent a future of
billions of information devices embedded in the
physical world, why dont they run THE standard
internetworking protocol?
?
Sonet
Serial
Self-Contained
Plugs and People
25
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

26
Emerging Standards

• LoWPAN 802.15.4
• 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.15.4,
802.11
Ethernet
Sonet
IETF 6lowpan
27
6LoWPAN IPv6 over IEEE 802.15.4
IEEE 802.15.4 Frame Format
S pan
D pan
Dst EUID 64
Src EUID 64
preamble
Dst16
Src16
DSN
Network Header
Application Data
dsp
IETF 6LoWPAN Format
01
1
Uncompressed IPv6 address RFC2460
0
40 bytes
0
0
0
0
01
0
1
0
0
0
0
HC1
Fully compressed 1 byte
Source address derived from link
address Destination address derived from link
address Traffic Class Flow Label zero Next
header UDP, TCP, or ICMP

• Deep compression by breaking the layering
  abstraction and putting it all back together
  again.

28
Extending the Internet to the Real World
29
Embedded Web Services
lt get temp set sample_rate set alarm gt
www.weather.com
Web Services
ltvaluegt sourcelibrary time1253
temp26.7 lt\valuegt
ltvaluegt sourcelibrary time1231
temp25.1 lt\valuegt
XML information
Wireless Packets
802.15.4
30
Real World Signals and Information

• What is the bandwidth of the weather?
• What is the nyquist of the soil?
• What is the placement noise?
• What is the sampling jitter error?
• How do you classify it?
• How do you search it?

31
The Macroscope - Keck HydroWatch
Sagehen wireless data infrastructure
32
Networking the Physical World
Bi-directional Patch Antenna
Mote Accelerometer Board)
Battery
33
Ambient Vibration
SF (south)
500 ft
4200 ft
1125 ft
246 ft
Sausalito (north)
8 nodes
51 nodes
Vertical Sensor at Quarter-span 365m North of the
South Tower
Vertical Sensor at Quarter-span 335m South of the
North Tower
34
Bonus Spectacular Views
35
Real World
36
Networking Every Day Things
37
Kitchen
38
Bath / Health / Clinic
39
Fitness
40
Typical Week

• Meet on Monday
• 1st Hour student presentations on results of
  previous weeks Team Activity Assignment
• Brief Presentation providing technical background
  for Lab
• Interactive Lab with 1-1 and whole class
  discussion
• Team Activity Assignment
• Office and lab hours during the week

41
Plan for the Term

• http//www.eecs.berkeley.edu/culler/eecs194/
• W1 Embedded Internet
• W2 Embedded Applications / MCUs / PCB design
• W3 Sensing
• W4 Networking and Web Services
• W5 Actuation / HW Fab
• W7-9 Class Starter Project
• W10-15 Team Projects

42
Discussion