CS 525M Mobile and Ubiquitous Computing Seminar A Survey on Sensor - - PowerPoint PPT Presentation

cs 525m mobile and ubiquitous computing seminar
SMART_READER_LITE
LIVE PREVIEW

CS 525M Mobile and Ubiquitous Computing Seminar A Survey on Sensor - - PowerPoint PPT Presentation

CS 525M Mobile and Ubiquitous Computing Seminar A Survey on Sensor Networks presented by Jeffrey R. Bacon Background Info Published in 2002 At the Georgia Institute of Technology Authors: Ian F. Akyildiz Weilian Su


slide-1
SLIDE 1

CS 525M – Mobile and Ubiquitous Computing Seminar

A Survey on Sensor Networks

presented by

Jeffrey R. Bacon

slide-2
SLIDE 2

Background Info

  • Published in 2002
  • At the Georgia Institute of Technology
  • Authors:
  • Ian F. Akyildiz
  • Weilian Su
  • Yogesh Sankarasubramaniam
  • Erdal Cayirci
slide-3
SLIDE 3

What’s a sensor network?

  • Large number of sensor nodes
  • Multifunction sensors
  • Low-cost
  • Low-power
  • Tiny
  • Mobile
slide-4
SLIDE 4

Uses

  • Military
  • Command
  • Control
  • Communications
  • Intelligence
  • Surveillance
  • Reconnaissance
  • Targeting
  • Health
  • Monitor patients
  • Assist disabled patients
  • Commercial
  • Manage inventory
  • Monitor product quality
  • Monitor disaster/dangerous areas
slide-5
SLIDE 5

How is this different?

  • Not a traditional ad-hoc network
  • Number of nodes can be orders of

magnitude higher

  • Sensors densely deployed
  • Sensor nodes prone to failure
  • Topology changes frequently
  • Broadcast paradigm (not point-to-point)
  • Limited power, computing, memory
  • No global identification
slide-6
SLIDE 6

Network Parts

  • Sensor Field: The area that the sensors

can examine

  • Sensor Nodes: The sensors & other

physical components

  • Sink: A local workstation that gathers data

and manages the network

  • The Internet/Satellite: Sends data gathered

by sink to other locations

  • Task Manager/User: End user

controlling/receiving data

slide-7
SLIDE 7

Network Diagram

Sensor Field: The area the sensors are studying

slide-8
SLIDE 8

Network Diagram

Sensor Nodes: The sensors and the accompanying components

slide-9
SLIDE 9

Network Diagram

Sink: A local workstation that manages and gathers data from the network

slide-10
SLIDE 10

Network Diagram

Internet & Satellite: Communicates the data back to the end users

slide-11
SLIDE 11

Network Diagram

Task Manager: The end user who is using the data

slide-12
SLIDE 12

Typical Sensor Node

Power the Sensor Node Senses Environment Analog to Digital Converter Process Data Communication

Always present components

Store Data

slide-13
SLIDE 13

Typical Sensor Node

Generate it’s own power (solar, heat, etc) Determine Location Move the sensor

Optional Components

slide-14
SLIDE 14

Issues to Consider

  • Fault Tolerance

(Fragile devices in rough terrain will break often)

  • Scalability

(Hundreds or thousands of nodes)

  • Production Costs

(Bluetooth is 10x the target cost)

  • Topology

(Up to 20 nodes per cubic meter)

  • Deployment

(Thrown or even launched from missles)

  • Environment

(Inside machinery, biohazards, behind enemy lines)

  • Transmission Media

(Radio has interference, infrared and optical require line of sight)

  • Power Consumption

(Less than 0.5A, 1.2V, power can cut out and change the network)

slide-15
SLIDE 15

Protocol Stack

Physical Layer Data Link Layer Network Layer Transport Layer Application Layer Power Management Plane Mobility Management Plane Task Management Plane

slide-16
SLIDE 16

Protocol Stack

Physical Layer Data Link Layer Network Layer Transport Layer Application Layer Power Management Plane Mobility Management Plane Task Management Plane

slide-17
SLIDE 17

Physical Layer Issues

  • 915 MHz Industrial/Scientific/Medical band
  • Power Consumption
  • Most important Issue
  • Communication is very expensive
  • Sometimes can be replenished
  • Solar or other means
slide-18
SLIDE 18

Open Research

  • Need better power modulation schemes
  • Need to overcome signal propagation

effects

  • The usual hardware issues:
  • Smaller!
  • Faster!
  • Cheaper!
slide-19
SLIDE 19

Protocol Stack

Physical Layer Data Link Layer Network Layer Transport Layer Application Layer Power Management Plane Mobility Management Plane Task Management Plane

slide-20
SLIDE 20

Medium Access Control

  • Existing MAC protocols inadequate
  • Very large number of nodes
  • Transmission power is very low
  • Topology changes frequent
  • Power consumption requirements
  • MAC for Sensor Networks
  • Power saving modes required
  • Timeouts preferred to

acknowledgements

slide-21
SLIDE 21

SMACS

  • SMACS: “Self-Organizing MAC for Sensor

Networks”

  • Link Layer organization
  • Discover neighbors automatically
  • Establishes schedules without global

master node

  • How it works:
  • Random fixed time slots
  • Takes advantage of low bandwidth

requirements

  • Turns off radio transmitter when not in

use

slide-22
SLIDE 22

EAR Algorithm

  • EAR: Eavesdrop and Register algorithm
  • Works with SMACS
  • Establishes seamless connection
  • Nodes control own connections
  • Drops when necessary
  • Saves messaging overhead
slide-23
SLIDE 23

CSMA-Based Mac

  • CSMA: Carrier Sense Multiple Access
  • Listening mechanism and backoff

scheme

  • Energy-efficient “listen periods”
  • Random delays help prevent collisions
  • ARC: Adaptive Transmission Rate

Controls

  • Balances rates of originating and

route-through traffic

  • Makes all nodes favored roughly

equally

slide-24
SLIDE 24

Hybrid TDMA/FDMA

  • Centrally controlled
  • Requires nearby high power base

station

  • Combines:
  • TDMA
  • Time Division Multiple Access
  • All bandwidth to one sensor at a

time

  • FDMA
  • Frequency Division Multiple Access
  • Minimal bandwidth to every node
  • Hybrid method:
  • Finds optimal division
  • Divides channels AND frequencies up

Time Frequency Time Frequency Time Frequency

slide-25
SLIDE 25

Power Saving at Link Level

  • Simple off/on can cost more energy
  • Short, frequent packets mean many

starts and stops

  • Startup energy could cost more
slide-26
SLIDE 26

Error Control

  • Automatic Repeat Request (ARQ)
  • Bad! Too much energy!
  • More power to signals
  • Bad! Too much energy!
  • Forward Error Correction (FEC)
  • Good! … but inefficient and costly to

microprocessor.

  • Built in FEC chips recommended
slide-27
SLIDE 27

Open Research

  • Better MAC protocols needed
  • Research on energy lower bound
  • Error control coding research
  • Power-saving research
slide-28
SLIDE 28

Protocol Stack

Physical Layer Data Link Layer Network Layer Transport Layer Application Layer Power Management Plane Mobility Management Plane Task Management Plane

slide-29
SLIDE 29

Routing

  • Maximum Power Available (PA)
  • Minimum Energy (ME)
  • Minimum Hop (MH)
  • Maximum Minimum Power Available
  • Data-Centric
slide-30
SLIDE 30

Routing

  • Maximum Power Available Route
slide-31
SLIDE 31

Routing

  • Minimum Energy Route
slide-32
SLIDE 32

Routing

  • Minimum Hop Route
slide-33
SLIDE 33

Routing

  • Maximum Minimum Power Available Node

Route

slide-34
SLIDE 34

Data Aggregation

  • Aggregate data at sensor level
  • Requires more processor power
  • Requires less transmission power
slide-35
SLIDE 35

Attribute-Based Naming

  • Only get data from specific nodes
  • Don’t send data from other nodes to save

power

  • Attribute-value pairs requested by name
slide-36
SLIDE 36

Overview of methods

  • Small Minimum Energy Communication

Network

  • Create network subgraphs that connect

all nodes but using the least energy

  • Flooding
  • Saves overhead of topology change and

route discovery

  • High energy, data implosion
  • Gossiping
  • Like flooding, but sends to a random

neighbor

  • No data implosion, but slow
slide-37
SLIDE 37

SPIN

  • Sensor Protocols for Information via

Negotiation

  • Get requested data only
  • ADV (descriptor), REQ (request), DATA
slide-38
SLIDE 38

Overview of methods, cont.

  • Sequential Assignment Routing (SAR)
  • Create multiple trees
  • Root of each tree is one-hop neighbor of the

sink

  • Avoids nodes with low quality of service
  • Low-Energy Adaptive Clustering Heirarchy

(LEACH)

  • Randomly select nodes as “clusterheads” that

send to the sink

  • Clusterheads inform other nodes
  • Other nodes determine their own cluster
  • Change clusterheads on a regular basis

SINK SINK

slide-39
SLIDE 39

Overview of methods, cont.

  • Directed Diffusion
  • Base station sends out interest to

nearest nodes

  • Nodes propogate message outwards
  • Directed graph formed
slide-40
SLIDE 40

Protocol Stack

Physical Layer Data Link Layer Network Layer Transport Layer Application Layer Power Management Plane Mobility Management Plane Task Management Plane

slide-41
SLIDE 41

Transport Layer

  • Hasn’t really been addressed by anyone

yet!

  • TCP/UDP don’t address some concerns:
  • Power consumption
  • Lack of global addressing
  • Attribute-based naming
  • Likely answer:
  • TCP or UDP between sink and end user
  • UDP-like protocol between sink and

sensor nodes

slide-42
SLIDE 42

Protocol Stack

Physical Layer Data Link Layer Network Layer Transport Layer Application Layer Power Management Plane Mobility Management Plane Task Management Plane

slide-43
SLIDE 43

Application Layer Overview

  • Sensor Management Protocol
  • Makes lower levels transparent
  • Handles:
  • Data aggregation
  • Attribute based naming
  • Clustering
  • Location finding
  • Time Synchonization
  • Mobilization
  • Turning nodes off and on
  • Getting status
  • Reconfiguring
  • Authentication
  • Key Distribution
  • Security
slide-44
SLIDE 44

Application Layer Overview

  • Task Assignment and Data Advertisement

Protocol (TADAP)

  • Send out interest
  • Nodes only return data that user is

interested in

slide-45
SLIDE 45

Query Languages

  • Sensor Query and Data Dissemination

Protocol

  • Like SQL for sensor networks
  • “Get the locations of the nodes that sense

temperature higher than 70 degrees”

  • Sensor Query And Tasking Language
  • A larger query project that includes things

SQDDP does not

  • Only in the proposal stage
slide-46
SLIDE 46

Conclusion

  • We’re not there yet!
  • Main issues that need work:
  • Fault tolerance
  • Scalability
  • Cost
  • Hardware
  • Topology Changes
  • Environment
  • Power Consumption
slide-47
SLIDE 47

Questions?