CenSCIR and Sensor Andrew Overview

1. CenSCIR and Sensor Andrew Overview

2. PITA High-Impact Cluster Update • CenSCIR Overview • Update on Sensor Andrew – “Most Sensed Campus” Project

3. Unfortunately, recent news speaks for itself…

4. Critical Infrastructures • "Critical infrastructures are those physical and cyber-based systems essential to the minimum operations of the economy and government. … their incapacity or destruction would have a debilitating impact on the defense or economic security of the United States." - President William J. Clinton, 1998 • They Include: • Transportation infrastructure • Water distribution and treatment • Power generation and distribution • Telecommunications infrastructure

5. The Need - Manageability • The Federal Real Property Initiative – A Top 10 Critical issues along with Medicare and Social Security in 2003 by the Whitehouse • Established by Executive Order, a Senior Real Property Officer was designated within each agency • The US government also owns or manages one in every four acres of land in the United States (According to its fiscal year 2003 financial statements)

6. The Need – Privatization/Profit • A wave of road privatization is about to hit the US. This will fundamentally change the way that a road is constructed, operated, marketed and maintained. • The road will be operated like any other private business, and that will require active real-time technology to maximize efficiency, safety and profit. • For similar reasons rail, some utilities, and other asset owners are also in this opportunity. • According to the CATO Institute “With private operators responsible for maintenance as well as improvement of the highways, gasoline taxes and other government charges for roads could be phased out. New ideas and new technologies would be applied.”

7. The Need – Maintenance/Safety • In Jan 2006, a bridge collapsed onto I-70 • Interstate 70 was closed for several days. • The bridge had been recently inspected and given a rating of 4 out of 10. • Extensive corrosion damage to the pre-stressing cables and reinforcing bars in the concrete beam is believed to have contributed to the failure. • The extent of this damage was not detected during visual inspection. It will require modern sensing technologies to reduce this kind of accident.

8. The Need – Operations • On August 14, 2003, a blackout, twice as large as any in US history, left 50M people without electrical power • Affected 250 power plants, 62 Gigawatts of generating capacity and occurred in less than 8 min • Started with a few plants seeing excessive demand • “Before it was over, three people were dead. 1.5M people in Ohio had no running water for 2 days….Twelve airports closed in eight states/Canadian provinces. • The estimated economic damage was $4.5-$10 billion.” [Mansueti 2004]

9. The Need - Assessment • Most of infrastructure assessments are based on human visual inspection • Problems: • Inspector training inconsistent • Some conditions go visually undetected • Actual usage unknown • History = numeric condition ratings& textual report • Do we really know the true state of this infrastructure?

10. The Need - Environmental • Major Undetected Pipe Leak in 2006 • The largest oil spill occurred on the tundra of Alaska's North Slope • 270k gallons of thick crude oil spilled over two acres • Oil escaped through a pinprick-size hole in a corroded 34-inch pipe • Most of the oil seeped beneath the snow without attracting the attention of workers monitoring alarm systems. • The spill went undetected for as long as five days … New York Times, March 15, 2006 [Berringer 2006]:

11. The Need for CenSCIR - Construction • Construction deviations and defects occur frequently on construction sites: • Material quality • Geometric • When detected late in construction process, constitutes 8-12% of construction cost • 54% of defects attributed to human factors: • unskilled workers • insufficient supervision

13. CenSCIR is beginning a broad research project called Sensor Andrew Sensor Andrew is a PITA-Seeded Project: • a “living laboratory” for researching infrastructure sensing technologies and processes • a sensor network that will enable the dense instrumentation of the whole of Carnegie Mellon’s campus • a public sensor network that can support a broad set of applications. • Infrastructure monitoring, first-responder support, quality of life for the disabled, water distribution systems monitoring and optimization, social networks, and biometric sensors for campus security are some of the applications under progress. • Goal is to make Carnegie Mellon “the most sensed” campus in the world

14. Key Differences • Fully heterogeneous • Different components • Distinct data sources • New merged data • Different applications • Non-centralized architecture • Highly scalable and adaptable • Not purpose-specific • Evolvable • Easy to expand and reconfigure

15. Applications • Infrastructure monitoring • First-responder support: Towards an intelligent facility: Development and testing of an RFID-based guidance approach for locating building components • Improved quality of life for the disabled • Infrastructure usage optimization • Security and Surveillance • Continuous Monitoring of Distributed Pipeline Systems • Coordination of Sensing and Diagnostic Platforms for Long-term Temperature, Light, Humidity, and Energy Use • Face Camera Network Prototype • Social Network

16. Ethernet End-User Central Hub Ethernet / 802.11 Ethernet 802.11 Gateway Gateway IP Camera End-User Web Server RS-232 RS-232 Sensor Node Sensor Node IP Camera Mobile Node RFID RX 802.15.4 Bluetooth Sensor Card Sensor Andrew Campus Network * Protocols listed are examples

17. Sensor Andrew Layers Middleware/ Central Hub Campus Network Gateway Gateway IP Camera User/ Application Layer IP Camera RFID RX Gateway Layer Sensor Layer

18. New! New! S Marmite Visual FireFly System S MAPLES Current Component Projects Aggregated Data Query and Visualization • Infrastructure monitoring • First-responder support: • Improved quality of life for the disabled • Infrastructure usage optimization • Security and Surveillance • Continuous Monitoring of Distributed Pipeline Systems • Coordination of Sensing and Diagnostic Platforms for Long-term Temperature, Light, Humidity, and Energy Use • Face Camera Network Prototype • Social Network Applications Middleware New! New! New! Gateways/Nodes Aruba AP70 FireFly PCs Gumstix Sensors FireFly, RFID, EnerSure, Critter, Hobo, cameras, others

19. Sensor Layer Component Examples • Infrastructure nodes • FireFly nodes • MicaZ/TelOS Motes • RFID readers/tags • EnerSure • Mobile nodes • Battery Operated Nodes • RFID Readers/Tags • Cell phones (w/ BT, …) • Critters • …

20. Current Sensors / Actuators • FireFly • Light, Temperature, Sound, Acceleration (default) • Motion, Humidity, Ultrasound, Line Voltage Power Control, Image Processor (expansion) • Smart Camera • BF537e Camera • Wireless IP Camera • PZT Transducer • Motes • Light, Temperature, Humidity (default ) • Magnetometer, Ultrasound, Acceleration (expansion) • Critters • EnerSures • HOBOs • RFID Tags

21. Key = 1 Sensor/Node Type = 2 Sensor/Node Types = 3 or more Sensor/Node Types

22. Scalable Sensor Network Platform • Extend the next-generation version of the FireFly sensor hardware platform developed at Carnegie Mellon University. • Support a large-scale wireless sensor network • Provide a very capable and affordable platform • A comprehensive software development environment • Extensive documentation and training material • Extensive evaluation will also be carried out

23. Gateway Gateway IP Camera IP Camera RFID RX Gateway Layer Components • Single Board Computers • Gumstix • Linux, 400MHz X-Scale • 64MB RAM, 32MB flash • Blackfin Media Processor • uCLinux, 600MHz BF537 • 32MB RAM, 8MB flash • … (could be PC, laptop) • IP Camera Nodes • RFID Readers

24. Middleware Layer: Goals • Standard Messaging Format • Extensible Message Types • Support sensors, images, audio with various application specific formatting • Fusion of Multiple Data Sources • Security / Privacy • Encryption, Authentication, Access Control • Internet Scale Performance

25. Middleware Layer: XMPP • XMPP (eXtensible Messaging and Presence Protocol): • Scalable XML based Messaging and Presence Protocol • Evolved from the Jabber Instant Messaging Protocol • Provides a way to securely send messages • Point to Point • Point to Multipoint • Provides a way to organize event messaging • Stores in Database • Publish / Subscribe

26. Middleware Layer: XMPP Clients/Servers Client Web Gateway Map / Data Viewing Client Server Client Server Gateway Mobile Node Database Server Client Gateway Notification

27. MEAD/MAPLES - Proactively Reconfigurable, Adaptive, Reliable Middleware • The MEAD system aims to enhance distributed middleware applications with new capabilities such as: • transparent, yet tunable, fault tolerance with configurable performance and timing guarantees • proactive dependability • resource-aware system adaptation to crash, communication and timing faults with • scalable and fast fault-detection and fault-recovery • As a part of the research on MEAD, we are investigating failure prediction, zero-downtime software upgrades, automated finger-pointing in distributed systems, and resource-constrained (embedded) survivability

28. Towards an intelligent facility: Development and testing of an RFID-based guidance approach for locating building components • An intelligent facility will be able to guide a first responder through it. • Active Radio Frequency Identification (RFID) technology: • Enables facility components to achieve some intelligence • Provides an opportunity to explore the development of an approach for guiding first responders.

29. Continuous Monitoring of Distributed Pipeline Systems • The use of lamb waves (which can travel long distances with little attenuation) to continuously monitor pipelines. • Apply damage detection techniques developed for thin plates, to hollow cylinders. • Cracks and other defects will be detected and located in pipelines, in an online fashion.

30. Coordination of Sensing and Diagnostic Platforms for Long-term • Vision: “One Thousand Spaces on Campus Sensed for Temperature, Light, Humidity, and Energy Use” • Goals: • Detect trends and predict values of various energy efficiency investments. • Understand current building operation • Discover knowledge from existing conditions • Manage sensor and sensor networks • Develop tools for diagnosis.

31. Surveillance • Surveillance of public spaces is an effective way to: • Monitor and respond to incidents. • Provide evidence should any incidents occur. • The final deployment of the system will result in a campus with secure public spaces, in particular walkways and park lots. • Key features: • Modularized algorithms • Hidden identity for privacy • Reconfigurable camera array

32. Face Camera Network Prototype • Secure access to critical infrastructure currently mostly achieved through passwords, swipe cards, RFID tags, etc. • Passwords can be forgotten and pass cards can be lost or stolen • A prototype of a face camera network • Distributed, integrated biometric-based. • Secure access to campus buildings.

33. Social Network • A social network application whose purpose is to engage a wide community of users. • Extends to the physical space of a University campus the degree of social interaction that Face Book or MySpace have provided in cyber space. • Combination of a camera network with cell phones or RFID tags to provide better localization of users.

34. Sensor Layer Default Operation • Sensor Reporting • Send sensor data to hub through gateway • Neighborhood Reporting • Send neighbor list information • Send Link Information • RSSI and sensor data from mobile nodes can be used for location tracking • Scripting Language Interpreter • Support custom processing • Sent over network

35. Sensor Layer Development • Programming Paradigm • Compiled C Code (Systems Developer) • OS, Routing Protocols, Live Update • Updates Database Information • Dangerous, Requires Physical Access • Scripting Language (Algorithm Developer) • Application Level Tasks • Can be easily deployed across network • Safe, will not harm underlying OS/Network • Custom Data Retrieval • Does not Require Physical Access • Development Environment • Nano-RK on FireFly • GCC, C code, Multi-tasking, power-aware, real-time • TinyOS (Super Users) • nesC, Event-Driven

36. Sensor Layer Networking • Addressing • 32-bit Sensor Node Addresses • Naming • Gateway provides DNS (human-readable names for sensor nodes) • Link Layer • RT-Link (FireFly, MicaZ nodes) • LPL-CSMA ( FireFly, Telos, MicaZ ) • Location Service • CMU / Porter / B Level / Moura Corridor / Prof. Moura’s Office • Network Attributes (extensible, static vs. dynamic) • Sensor Node (type, sensors, actuators, battery) • Link (wireless link properties) • Micronet (properties of entire sensor subnet connected to a gateway) • Routing • Static Routing • Ad-Hoc Routing • Physical Layer • 802.15.4 (250 Kbps) micronet micronet

37. Sensor Layer Properties • Scalability • Goal is to support 10’s of thousands of nodes • E.g. a single micronet can contain 255 nodes • Reliability • (Mostly) stateless (constantly push information to database) • Multiple Path Routing • Physical Space • Indoors (with/without Antennas) • Outdoors (with external Antennas) • Mobile (small package) • Security • AES 128 for links • Access Control through Gateway

38. Gateway Gateway IP Camera IP Camera RFID RX Gateway Layer Networking • Addressing • Static IP addresses for each gateway (managed by Andrew) • Naming • IP DNS (managed by Andrew) • Location Service • Porter, B Level, B-33 Lab • Routing • IP Network Routing (Managed by Andrew) • Link Layer • CSMA (standard) or Switched Ethernet • Physical Layer • Ethernet, 802.11 a/b/g

39. Gateway Gateway IP Camera IP Camera RFID RX Gateway Layer Development • Programming • (Currently) Unix Environment • Remote Management • Direct SSH / SCP Access to Gateway Nodes • Local OS • Linux or mClinux • Local Flash File System

40. Gateway Gateway IP Camera IP Camera RFID RX Gateway Layer Properties • Scalability • Limited by Wired Network • Reliability • Periodic Heart-Beat • ACKed Messages • Security • Leverage Standard Unix Security • Optional Encryption • Access Control Lists • Group Permissions • Physical Space • Indoors Only (to start) • Hidden as best as possible

41. Central Hub • Database • Public Database Access • Authorized Database Access • Sensor Data Logged With Timestamps • Web Server • HTTP Access to data • Configure Event Manager • Manage Nodes • Event Manager • Thresholds for detecting events of interest • E-mail / SMS Event Notification • Request for notification of events • Triggered by user-configurable thresholds • Fire, Water Pipe Burst, Sunny Weather etc. • Person of interest in neighborhood

42. Central Hub • Cluster of Machines • Distributed File System • Application-Specific Servers • User Interface (Website) • Plot Data • Check System Status • Account Management • Set Access Control • Event Manager Configurations • Node Addition / Deletion • Configure Sensor Update Rates

43. Central Hub • Access Control Rights • Nodes, micronets and data can all have access control rights • Account Management • Add, delete or modify accounts • Security • Authenticated Communication • Gateways and Clients • Encryption • Provide Simple APIs for developers • Key Management • Node Management • Add / Delete Node • Relay Node State to Gateways • Update Sensor Sampling Rates

44. Gateway Gateway IP Camera IP Camera RFID RX Layer Communication • Sensor Layer  Gateway Layer • RS-232 or custom raw byte transfer • SLIP(-like) Protocol • Custom Design • Gateway Layer  Central Hub • XMPP Server/Clients • TCP/IP Socket • XML Data Descriptions • XML Data interpreted with wrapper -> Database • Central Hub  Clients • HTTP • Remote Database Queries • Client  Gateway Layer • Socket-based Protocol • Custom Design, Typically for Debugging

45. Types of Users • Super User (Kernel / Network) • Reprogram node at all levels (dangerous) • Requires Authorization / Physical Interaction • Experimentation Users (Algorithm / Application) • Requires Authorization / Schedule • Run contained scripts • Change Sensor Layer Parameters • Sampling Rates • General User • Accesses Database / Web • Open to campus community

46. Goals for a Communication Infrastructure • Standard Messaging Format • Extensible Message Types • Support sensors, images, audio with various application specific formatting • Fusion of Multiple Data Sources • Security / Privacy • Encryption, Authentication, Access Control • Internet Scale Performance

47. XMPP (eXtensible Messaging and Presence Protocol) • Scalable XML based Messaging and Presence Protocol • Evolved from the Jabber Instant Messaging Protocol • Provides a way to securely send messages • Point to Point • Point to Multipoint • Provides a way to organize event messaging • Stores in Database • Publish / Subscribe

48. XMPP History • Jabber started in 1998 • Adopted by Google Talk in 2005 • Used for Messaging, Voice and File Transfer Protocols • 2007 AOL Instant Messenger Switches to XMPP • 2008 Multiple Open Source Projects Emerging using XMPP • OLPC using XMPP for buddy presence • Navy Using XMPP for battleship system presence notification • Multiple Open Source and Commercial Servers Available

49. XMPP Features • Simple Standardized Message Passing • Standard Addressing Scheme • gateway-34@sensor-andrew.cmu.edu/sensors/temp • someDatabase@sensors.ices.ece.cmu.edu • Allows for various message types • short messages • file transfer • Presence Information • Server Keeps Track of what is online and passes that information to interested services

50. XMPP Decentralized Operation XMPP Client User-X@ sensor.andrew.cmu.edu XMPP Server XMPP Server profile sensors.andrew.cmu.edu sensors.ices.ece.cmu.edu Gateway-Y@ sensors.ices.ece.cmu.edu XMPP Client profile