Download Impact of Sensor Networks on Future InterNetDesign

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Cracking of wireless networks wikipedia , lookup

Computer network wikipedia , lookup

Network tap wikipedia , lookup

Net neutrality law wikipedia , lookup

Internet protocol suite wikipedia , lookup

Deep packet inspection wikipedia , lookup

Zero-configuration networking wikipedia , lookup

Peering wikipedia , lookup

Net bias wikipedia , lookup

Airborne Networking wikipedia , lookup

Routing in delay-tolerant networking wikipedia , lookup

Piggybacking (Internet access) wikipedia , lookup

Quality of service wikipedia , lookup

Recursive InterNetwork Architecture (RINA) wikipedia , lookup

Transcript
Impact of Sensor Networks on
Future InterNet Design
David E. Culler
University of California, Berkeley
[email protected]
Arched Rock Corporation
[email protected]
NSF FIND Info Meeting
12-5-2005
What does the Internet look like in 10 years?
Low resolution Sensor, Test4, Increasing frequency
1
Acceleration (g)
0.5
0
-0.5
-1
0
2
4
6
8
10
12
14
16
18
Time (sec)
12/5/05
NSF FIND
2
In 10 years…
• 90% of the nodes on the “Internet” will embedded
devices connected to the physical world
• Universal, host-host file-transfer and console
access is the dominant usage pattern…..
NOT!
• So does it make sense to pay attention to the
characteristics of these kind of nodes and
applications in designing the future Internet?
12/5/05
NSF FIND
3
Canonical Sensor Net Architecture Today
Patch
Network
Sensor Node
Sensor Node
Sensor Patch
Gateway
Gateway
Transit Network
(IP or not)
Access point
- Base station
- Proxy
Client Data Browsing
and Processing
Verification
links
Intranet/Internet (IP)
Other information
sources
Data Service
12/5/05
•An Analysis
NSF
FIND of a Large Scale Habitat Monitoring4 Application,
Szewczyk, Polastre, Mainwaring, Anderson, and Culler, Sensys04
The Next Tier
Sensor Nets
• Small sensors will be the most common nodes
on the internet
• How will they be represented and accessed?
12/5/05
NSF FIND
5
How will SensorNets and IP play together?
XML / RPC / REST / SOAP / OSGI
HTTP / FTP / SNMP
TCP / UDP
IP
Ethernet
12/5/05
Sonet
802.11
NSF FIND
802.15.4, CC, …
6
Full IP stack throughout
XML / RPC / REST / SOAP / OSGI
HTTP / FTP / SNMP
TCP / UDP
IP
Ethernet
12/5/05
Sonet
802.11
NSF FIND
802.15.4, CC, …
7
Beware “IP hype”
• Transmitting HTML over a wireless connection to a
serial port attached to a PC is NOT running IP on the
sensor network
12/5/05
NSF FIND
8
Where has Internet Research Reached
and “struggled”?
• Aggregate communication => Multicast
• Resource constraints => QoS, DIFFSERV
• Communicate with data or logical services, not
just devices => URNs (DHTs?)
• Mobility => MobileIP, MANET
• In-network processing and storage => ActiveNets
• Intermittent connectivity => DTN ???
12/5/05
NSF FIND
9
What are the main characteristics of
Sensor Networks?
• Aggregate communication
– dissemination, data collection, aggregation
• Resource constraints
– Limited bandwidth, limited storage, limited energy
• Communicate with data or logical services, not
just devices
– Datacentric
• Mobility
– Devices moving, tags, networks moving through networks
• In-network processing and storage
– Really
• Intermittent connectivity
– Low-power operation, out of range, obstructions
12/5/05
NSF FIND
10
Facing these challenges
• Today, we use a wide range of ad hoc, application
specific techniques in the SensorNet patch
– Zillion different low-power MACs
– Many link-specific, app-specific multihop routing protocols
– Epidemic dissemination, directed diffusion, synopsis
diffusion, …
– All sorts of communication scheduling and power
management techniques
12/5/05
NSF FIND
11
XML / RPC / REST / SOAP / OSGI
HTTP / FTP / SNMP
TCP / UDP
IP
Ethernet
12/5/05
Sonet
Proxy / Gateway
Edge Network Approach
802.11
NSF FIND
802.15.4, CC, …
12
“Hacking it in” may not be so bad
• Security
– No IP to the nodes, attacks have to get through the gateway or
be physically close
• Namespace management
– Name nodes, networks, services
– Hosts, URLs, …
• Mask intermittent connectivity
– Terminate IP on the powered side
– Loosely couple, energy aware protocols on the other
• Distillation proxies
– Small binary packets where constrained
– Expanded to full text, XML, HTML, web services
• Rich suite of networking techniques in the Patch
unimpeded by the “ossification” of the rest
12/5/05
NSF FIND
13
Rethinking at Layer 7
Gateways
IP Overlay Network
SensorNet Patch
12/5/05
NSF FIND
14
Opportunity to rethink more deeply
• No dusty-decks yet
• Not a bunch of laptops running around with their
sockets open trying to route through other
laptops running around…
• Meaningful set of applications and associated
traffic loads
– Environments, individual objects, interactions
• Chance to think through control as well as
monitoring
• Physical embedding matters
• Techniques are likely to apply to the rest of the
Internet
12/5/05
NSF FIND
15
Traditional Analysis
Delivered
Performance
Offered Load
12/5/05
NSF FIND
16
Analysis that really matters
Mobility
Reliability
Changes in network
population
Environmental
variability
Bandwidth
Energy Expended
Delay
Traffic Load
Traffic Variability
12/5/05
NSF FIND
17
SensorNets need the Wisdom of the
“Internet Architecture”
• Design for change!
• Network protocols must work over a wide
variety of links
– Links will evolve
• Network protocols must work for a variety of
applications
– Applications will evolve
• Provide only simple primitives
– Don’t confuse the networking standard with a
programming methodology
• Don’t try to lock-in your advantage in
the spec
• Open process
• Rough consensus AND running code
12/5/05
NSF FIND
18
XETF (Xternet Engineering and Technology Forum) ???
• Mission
– Foster an open, innovative, and technically sound ecosystem around
interconnecting the physical world with modern networking and information
technology through the creation of technical documents, protocols, reference
implementations and APIs.
• Structure
– Lean. Volunteer: BOD, steering comm., working groups.
• Membership
– Individuals, corporate, academic, and gov’t
• Participation
– Open. Role determined by contribution.
• IP Policy
– Non-confidential. Disclosure and Contribution process.
– Companies can develop own implementation.
– BSD? Apache-like credit? MPL? LGPL?
• Output
– RFC-like documents, reference implementations, forum for exchange and viz.
– “Rough consensus AND running code”
12/5/05
NSF FIND
19
Uniting long-lost relatives
Home
Automation
Building
Automation
PC
Workstation
Dedicated Controllers
Minicomputer
VME
Mainframe
Instrumentation Computers
General Purpose Computing
12/5/05
NSF FIND
20
Tides of Change
Innovation
Log Stuff
The successor emerges when prior
regime is at its apex of strength –
not at a point of weakness.
Integration
What was previously hard becomes
easy, but its successor becomes
possible…
The Future Internet probably exists today;
go find it
Time
12/5/05
NSF FIND
21
Discussion
12/5/05
NSF FIND
22