Download Update 1

Sparse Network Data
Collection
Starring:
Dan Hoke
Also starring:
Waylon Brunette
And introducing: Jason Jenks
Motivation
• Extend current network models to include
unconnected subcomponents
• Create a solution for short-term data
collection needs
– High priority data
– Low priority time-delay
System Overview
• Sparse, arbitrary mica-mote network
• Central data collection facility (distant)
• Arbitrarily moving personal servers
function as transport layer
– Collect data
– Distribute ACKs
Project Application
Collect traffic data
• Use mica motes to collect data
– Use IR sensor for automobiles
– Simulate using a reed switch on Sieg Hall doors
• Personal servers will pass through the network and
collect data
– Could be attached to busses, police cars, or service
vehicles in application
• Use a PC to collect, archive, and report data
MULE
Personal
Server
DATA SERVER
(SQL)
Bluetooth
dongle
Serial
comms
Bluetooth
32
11
16
103
113
138
66
Mote
21
3
42
97
210
88
112
RFM
Mote
Mote
h
ug
ro
th rk
th two
pa ne
m e
do ars
an p
R s
Mote
Sparse Mote
Network
Mote
Mote
Mote
Data Flow
SERVER
Archives data and
generates ACKs
E
N
C
R
Y
P
T
Bluetooth
ACKS
AND
KEYS
MULE:
Does not attempt to
decrypt or interpret
data
TRAFFIC
DATA
Authentication
RFM
E
N
C
R
Y
P
T
TRAFFIC MOTE
Collects data and
encrypts prior
to transmission
TinyOS Command/Event
Relations
TRAFFIC_MOTE
ENCRYPT
GENERIC_COMM
RFM
RFM
STACK
LED
LED HARD
WARE
CLOCK
INTERNAL
TIMER
COUNTER
EVENT_COUNTER
INTERRUPT
COUNTER
Major Design Unknowns
• Mote useful battery life
– We will know more after we get a prototype up
• Time delays
– ACK wait time vs. mote data hoarding time
• Encryption Algorithm
– Light weight algorithms might not be secure enough
• Mica mote interrupt/counter mechanism
– Motes do not offer an edge triggered interrupt
• Final personal server configuration is unknown
Area Assignments
Waylon:
• SQL (server)
• Motes
• Mote routing
• MULE routing
Jason:
• MULE
• Bluetooth
• Security
• Control interface to server
Dan:
• Cryptography
• Graphic design
• Sample application (data
mining)
• Hardware (physical
wiring)
Milestones
Milestone
Proposed Due Date
API Definitions
February 2
Mote Framework – Initial ground work
February 9
MULE Simulator
February 9
Integrate Mote
February 16
MULE/Mote testing
February 16
Move MULE from PC to personal Server
February 22
Server Development
February 22
System Testing
March 1
Encryption
March 1
MULE to MULE communication
March 1
Final Testing/Debugging
March 8