1. SensorNet: Wide-Area Infrastructure for Interoperable Sensor Networks - Info-D Use Cases Mallikarjun Shankar, Ph.D. Computational Science and Engineering Division Oak Ridge National Laboratory shankarm@ornl.gov

2. 2 Outline SensorNet Goals –Standards –Typical deployments Operational Prototypes –Node device –Infrastructure Data-Sharing/Dissemination Scenarios

3. 3 Proliferation of IT revolution: Bell’s Law Year Log (people per computer) streaming information to/from physical world number Crunching data Storage productivity interactive Adapted from D. Culler 2004 1980 1

4. 4 SensorNet Goals Distributed Operations Centers Strategic Sites First Responders Automated Hazards Analysis Sensor Systems Control and Enhanced Communications Ubiquitous Sensing for Protection and Utility To catch big fish you need a big net – Ancient Proverb

5. 5 Many Sensors Many Applications Command-and-Control Field and End-User Support Analysis, Modeling, and Prediction Data-Sharing through a Standards based Framework IEEE 1451 & TEDS Net-Centric Enterprise Services/ Global Information Grid Open Geo- spatial Services (OGC’s Web Feature ServicesServices) Plug and Play Pervasive, Securable, Scalable, Interoperable and Reliable Open and Extensible Non-Proprietary

6. 6 Sample Deployments Wireline+Powered Deployments Pre-defined Analysis Integrating Multiple Sources of Data

7. 7 Information-Sharing Clouds

8. 8 SensorNet Node Edge of SensorNet (< few thousand feet control) Sensor Agnostic –Serial cable, Ethernet, Wireless –IEEE 1451 Connectivity with SensorNet –Interaction with Regional Data Center (RDC) –Basic Services (Open Geospatial Consortium, etc.)

9. 9 SensorNet Node TEDS STIM 1451.X Stubs 1451.1 NCAP … (Web) Server Control Auth Data Services Legacy Codes Data Store Config Sensors Wrapper Comm. Mode Control E.g., Sprint Session Other USB Mux. Wireline n Wireless Services are available to Regional Data Centers as well as external users “last-mile” link on CDMA, Ethernet, Wireless LANS, MANS, Satellite, etc. Mounted Node with satellite and CDMA connections: Sensors: CBRNE + Weather + Image +...

10. 10 Networked Deployment Scenario Plant, Region, or Urban Area Sensor Data Alternate Pathways Data Brokers Open Application and Model Access Sensors + Location and Connectivity Data Features First Responders Remote and Field Sensors Data Center and Services Netcentric: Peer-to-Peer Autonomous Decision Making Capability Mobile Node

11. 11 A Sample Architectural View Application to Data-Store Node to Data Center Apps User Node S S S S S S User Apps Portals Collectors/Receivers Data Sets Data Sets S S S S S S Diagram Courtesy: G. Minden, 2003

12. 12 Data-Sharing Services Anomaly? Filter: GeoLocation TimeWindow Type: TrafficData subscription Services Directory - --- --- --- Ontology and Normalization Services SensorNet and External Sources publication

13. 13 Application Context: SensorNet Data Considerations Data Sharing –Naming –Representation/Storage Data Management –Placement/Extraction –Filtering/Caching Security –Auth/Access –Zones

14. 14 Scenario A (Initiation/Startup) Field installation of sensor. Sensor starts collecting and submitting data Sensor data aggregated at a local node which makes it available to (i) local data center and to (ii) applications that access the node. Node sends sensor data periodically to local data-center.

15. 15 Scenario B (Steady State) Sensor to Data-Center –Periodic data from Node arrives at Data- Center –Periodic data from Local Data Center exchanged with peer or higher-level (Regional) Data Center Data-Center to Data-Center and Application to Data-Center –Periodic polling requests for data-subset (spatio-temporal bounding box)

16. 16 Scenario C – Alert Event Alert event takes place and Alert Message is sent from Node to Local-Data Center Local Data Center sends Alert to all subscribers of alert message types

17. 17 Use Cases: Startup and Data-Read Case 1. User Installer sets up field sensor and expects data to appear in data-base for application (Scenario A and B) Case 2. User at operations center expresses interest in certain sensor data. –Scenario B and C (Stop reading is symmetric in reverse)

18. 18 Use Case: Alert Configuration User sets up alert threshold for sensor levels in a spatio-temporal window. –Language as well as specific implementation TBD, currently WNS and SAS Alerts get published to subscribers to the alert service

19. 19 Requirements R0 Subscribers select publishersApplications and Peer-Data Centers select Data Centers (spatio- temporally, with sensor types) R1 Subscribers select messagesData-center selects particular sensor Type/Location/Time-window R2 Publishers select consumersSensors pre-configured to destination R3 Publishers/subscribers use vocab to select messages Standardized format for message transfer. Message types are raw data from software/hardware agents/sensors. R4 Subscribers specify messages published Not clear -- Selection of data-sources automatically selects messages published here. R5 Subscribers define event by querying data src Event-listener subscribes for the interesting event from the sensor alerting service. R6 Subscribers correlate events to form composites N/A. Because this is application internal or service internal. R7 Consumers specify dynamically how/when msgs received Some alert requests are specified at higher priority. R8 Consumers limit messages received R9 Consumers retrieve past messages Historical search from applications to Data-Centers and Nodes. R10 Pubs/Subs/Consumers define QoS Requests must meet performance metrics (Outside Info-D?) R11 Pubs/Subs/Consumers have Identity Managmt Access control. And authorization accompanies all requests. R12 Filters composableQuery request must allow fairly sophisticated query syntax.

20. 20 Use Cases User/operator Common operational picture (COP) application Hazard and effects model Node sensor data update Others?

21. 21 User/Operator Use Cases User views SensorNet assets in a geographic region User views data associated with a SensorNet asset User manipulates overlays

22. 22 User/Operator Use Cases User views SensorNet assets in a geographic region –User navigates the common operational picture (COP) viewer to a region of interest Appearing on the map display are icons representing assets known to SensorNet. If the scale is such that Nodes in an area cannot be shown individually, an icon representing a group of nodes is displayed. The standard icons indicate the type of assets available at a Node or location and which of those assets are active or online. Alert state assets will be indicated by color (red) and other visual means, such as blinking the icon. A list of overlays and themes applicable to the current geographic region and the present time to a user-defined look-ahead is provided. By default, all overlays are visible. –User zooms the display in or out This results in a refresh of the icons representing SensorNet assets to match the new scale. –User clicks on an icon The display zooms to the bounding box of the Node(s) represented by the icon, and the COP is refreshed accordingly.

23. 23 User/Operator Use Cases User views data associated with a SensorNet asset –User clicks on an icon representing a Node or asset A Node display page is brought up in a viewer. The page reports the current status and latest readings from all assets at the Node. For camera assets, the latest frame is displayed. –User selects an individual asset on the page An asset display page is produced in a viewer giving the recent history of readings in textual and/or graphic form for the selected asset. For cameras, the result is a streaming video page if available. –User right-clicks on an icon A popup menu with items for each asset at the Node and any supplemental information or functions is displayed. Selecting a menu item results in the asset display page as described above.

24. 24 User/Operator Use Cases User manipulates overlays –User selects overlays and themes to toggle their display on the COP Display of selected overlays is toggled on and off.

25. 25 User Subscribes to Events Get all events Limit by geographical region Limit by event type Limit by sensor and user defined criteria

26. 26 COP Application Use Cases (Includes a Web application) Application initializes Application updates Application terminates

27. 27 COP Application Use Cases Application initializes –Application obtains the list of service URLs for the region –Application sends a RegisterForEventNotification message to register interest in all sensor-related alerts or events The application instance’s request is stored by the notification service. –Application sends GetAssets (registry [WRS] request?) and GetFeatures messages specifying the geographic region, time, and look-ahead time The service responds with a document containing descriptions of Nodes and their assets including references to URLs for Node and asset pages as well as popup menu items and the like. Overlays are also displayed. –Application displays the assets and other data –SCS DescribeSensor for SensorML on individual sensors

28. 28 COP Application Use Cases Application updates –Either a configuration-defined timeout since the last update expires or the user changes the geographic region (e.g., zoom or pan) and/or the look-ahead time. –Application sends GetAssets and GetFeatures messages specifying the geographic region, time, and look-ahead time The service responds with a document containing descriptions of Nodes and their assets including references to URLs for Node and asset pages as well as popup menu items and the like. Overlays are also displayed. –Application displays the assets and other data

29. 29 COP Application Use Cases Application updates –Application receives an event –Application sends GetAssets and GetFeatures messages specifying the geographic region, time, and look-ahead time The service responds with a document containing descriptions of Nodes and their assets including references to URLs for Node and asset pages as well as popup menu items and the like. Overlays are also displayed. –Application displays the assets and other data

30. 30 COP Application Use Cases Application terminates –Application sends an UnregisterForEventNotification message The notification service removes the application’s registraion.

31. 31 Hazard and Effects Model Use Cases Model initializes Model receives alert notification Model terminates

32. 32 Hazard and Effects Model Use Cases Model receives alert notification –Model not currently activated: Model examines the alert message to determine the source term type. The time of the message becomes the base time for the model scenario. Model sends a GetAssets message specifying a region around the alert location to obtain descriptions of assets Model sends GetAssetData and GetAssetHistory messages to retrieve data applicable for building source term and weather inputs. Model begins the transport and dispersion calculation. –Model currently activated: Model stores the information in the alert message to refine the source term at the next calculation time step, or if the alert occurs sufficiently distant from the current scenario, a new model instance is launched for a new scenario.

33. 33 Hazard and Effects Model Use Cases Model receives alert notification (cont’d) –Model completes a time step Based on the type of source term, the model computes one or more human effects results. The calculation is resumed. –If output data for the simulation time step exist for a previous iteration, they are removed via a UpdateModelData message (keep previous data). –The new results are stored via an InsertModelData message.

34. 34 Node Sensor Data Update Use Cases Node loses sensors/assets –Node sends a RemoveAssets message The message identifies sensors or assets no longer available at the node. Node updates –Node sends an UpdateAssetData message Data for some collection of sensors and/or assets at the Node are provided in an update message to the RDC service. Most likely, these updates will occur according to some established update cycle. Node alerts –Node sends an alert Event message This published event is propogated to all clients whose registered interest matches the event

35. 35 Summary Sensor networks for protection and utility built on a mixed hierarchical and peering- based architecture Middleware requires systematic data- sharing and interoperability over the wide- area http://www.sensornet.gov

36. 36 System Middlewares: OGC, Grid,..., CORBA,... 0.45 0.52 52. From OGC’s OWS3 Standards Drafts

37. 37 OGC SensorML Example Davis Anemometer 7911 Location of weather station on roof of the National Space Science and Technology Center Building at 320 Sparkman Dr., Huntsville, AL 35805 34.72450 -86.94533 20.1169 Wind Speed wind speed <TypedQuantity uom="http://myUnitsDictionary.xml#metersPerSecond"> 0.1 2.25 Source: SensorML Recommendation Paper, Dr. Michael Botts, UAH