GEOINT Huntsville August 14 2013 Dr Mike Botts mikebottsbottsinccom Botts Innovative Research Inc Madison AL What is SWE SWE is technology to enable the realization of Sensor Webs ID: 294568
Download Presentation The PPT/PDF document "Sensor Web Enablement (SWE)" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Sensor Web Enablement (SWE)GEOINT HuntsvilleAugust 14, 2013
Dr. Mike Bottsmike.botts@botts-inc.com Botts Innovative Research, IncMadison, ALSlide2
What is SWE?SWE is technology to enable the realization of Sensor Websmuch like TCP/IP, HTML, and HTTPD enabled the WWW
SWE is a suite of standards from OGC (Open Geospatial Consortium)3 standard XML encodings (SensorML, O&M, SWE Common Data)3 standard web service interfaces (SWE Common Service, SOS, SPS)1 hardware/software interface protocol (PUCK)
SWE is a Service Oriented Architecture (SOA) approach
SWE is an open, consensus-based set of standards
SWE History:
began
in 2000
with SensorML at UAH
developed into a suite of encodings and services over the last 12 yearsSlide3
Sensors are EverywhereSlide4
Why SWE?Break down current stovepipesEnable interoperability not only
within communities but between traditionally disparate communitiesdifferent sensor types: in-situ vs remote sensors, video, models, CBRNE
different disciplines: science, defense, intelligence, emergency management, utilities, etc.
different sciences:
ocean, atmosphere, land, bio, target recognition, signal processing, etc.
different agencies:
government, commercial, private, Joe Public
Leverage benefits of open standards
competitive tool development
more abundant data sources
utilize efforts funded by others
Backed by the Open Geospatial Consortium process
480+ members cooperating in consensus processInteroperability Project testing
CITE compliance testingSlide5
Basic VisionQuickly discover sensors and sensor data
(secure or public) that can meet my needs – based on location, observables, quality, ability to task, etc.Obtain sensor information in a standard encoding that is understandable by my software and enables assessment and processing without a-priori knowledge
Readily access sensor observations in a common manner, and in a form specific to my needs
Task sensors
when possible, to meet my specific needs
Subscribe to and receive alerts
when a sensor measures a particular phenomenonSlide6
Actuator systems
Alarms
Robots
Weapons
Sensor assets
Decision Support Tools
Sensor systems
UGS
Bio/Chem/Rad
Detectors
Surveillance
Airborne
Satellite
Models and Simulations
M. Botts
-2013
Sensor Web Enablement
discover
observe
qualify
task
alert
o
pen standard
web
services and
encodings
Sensor Web Enablement Framework
“Detect,
P
rocess, and React”Slide7
What are the benefits of SWE?Sensor system agnostic - Virtually any sensor, actuator, or modeling system can be supportedNet-centric, SOA-based
Distributed architecture allows independent development of services but enables on-the-fly connectivity between resourcesSemantically tiedRelies on online dictionaries and ontologies for semanticsKey to interoperabilityTraceability (using SensorML)
observation lineagequality of measurement support
Implementation flexibility
wrap existing capabilities and sensors
implement services and processing where it makes sense (e.g. near sensors, closer to user, or in-between)
scalable from single, simple sensor to large sensor collectionsSlide8
SWE StandardsInformation Models and Schema
SWE Common Data – common data models used throughout SWE specsSensor Model Language (SensorML) - Core models and schema for observation processes: supports quality assessment, lineage/provenance, on-demand processingObservations and Measurements (O&M)
– Core models and schema for observations; archived and streaming
Web Services
SWE Common Services –
Supports common base functions for all SWE services
Sensor Observation Service
– Access observations for a sensor or sensor constellation, and optionally, the associated sensor description
Sensor Alert Service
– Publish and subscribe to alerts based upon sensor observations (now supported by SOS)
Sensor Planning Service
– Request collection feasibility and task sensor or actuator systems
Hardware/Software
InterfacePUCK
– “plug-n-play” interface for sensor systemsSlide9
Botts Innovative Research, Inc (Botts-Inc)Established in 2005Evolved from 18+ years as R&D team at University of Alabama in HuntsvilleHeavily involved in the design and development of SWE standards
Developer of open-source library and application software for SWEhttp://www.botts-inc.com Dr. Botts holds TS/SCI clearances in the USThe following are example applications and demonstrations of SWE technology and open-source software from the Botts-Inc / UAH teamSlide10
Simulated Radiation Attack on NYOGC OWS-4 (2006)illustrate discovery, access to and fusing of disparate sensors
Client: Space Time Toolkit Services:SOS – in-situ radiation sensors SOS – Doppler RadarSOS – Lagrangian plume modelWCS – GOES weather satellite
SensorML – discovery and on-demand processing
WMS – Ortho Imagery
view this demoSlide11
Tigershark UAV-HD VideoEmpire Challenge (2008)illustrate on-demand geolocation and display of HD video from Tigershark UAV
Client: Space Time Toolkit Services:SOS – Tigershark video and navigation SOS – Troop MovementSensorML – On-demand processing View this demo
Part 1Part 2Slide12
Tasking SPOT Image SatelliteOGC OWS-6 (2009)illustrate dynamic query of SPS; show on-demand geolocation of JPIP stream using SensorML
Client: Space Time Toolkit Services:SPS – satellite imagery feasibility WCS/JPIP server – streaming J2K image with CSM parameters encoded in SensorML SensorML – on-demand geolocation v
iew this demoSlide13
IED DetectionOGC OWS-7 (2010)illustrate ability to use of SWE services and encodings to support temporal differencing of ground-based video
Client: Space Time Toolkit Services:SOS – video from vehicle-mounted cameraSOS – camera navigation dataSensorML – On-demand processing v
iew this demoSlide14
Using SWE for GPS MessagingOGC OWS-9 (2012)illustrate the potential for using SWE Common data and SWE services for next generation GPS messaging
Client: Small browser appServices:SOS – disparate messages from various GPS correction systemsSOS – on-demand corrected GPSSWE Common – component and encoding description for all messages Slide15
A Few Other Sample ApplicationsDebris flow MonitoringSatellite tasking and imagery accessWeather networksTsunami warningDefense and intelligence
Ocean buoy networksWater managementWeb cameras and securityTraffic managementSmart CitiesIoT/WoT
Copyright © 2011 Open Geospatial ConsortiumSlide16
ConclusionsSWE helps to break down stovepipes in sensor and actuator systems
SWE enables interoperability not only within communities but between traditionally disparate communitiesSWE allows on to leverage benefits of open standardsSWE enables real-time, on-demand access to sensors and actuators
SWE enables workflows for sensing, processing, and reacting
SWE has been tested in various sensor communities and is being implemented around the world for real applications
For more see:
http
://www.opengeospatial.org/domain/
swe
Slide17
ProposalNote: Sensors provide the dynamic, real-time information that much of GEOINT depends uponPropose that we make Huntsville a model smart city for GEOINT research and application byestablishing a sensor web for public and private sensors and actuators using OGC SWE framework
providing and testing cyber security measures for providing multi-level acess to these assetsprovide sensor web access for universities and companies to allow them to propose and develop advanced capabilities for:discovery, processing, filteringpredictive analysis and “tipping and queuing”