1 / 23

OWS-4 SWE Overview 28 November 2006 @NIST

OWS-4 SWE Overview 28 November 2006 @NIST. Mark Reichardt / George Percivall / John Davidson. Topics. OGC Process OWS-4 SWE Project Participants OWS-4 CONOPS and Use Cases SWE Specification Baseline SWE Information Model SWE Service Model OWS-4 SWE Demo Overview.

eden
Download Presentation

OWS-4 SWE Overview 28 November 2006 @NIST

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OWS-4 SWE Overview 28 November 2006@NIST Mark Reichardt / George Percivall / John Davidson

  2. Topics • OGC Process • OWS-4 SWE Project Participants • OWS-4 CONOPS and Use Cases • SWE Specification Baseline • SWE Information Model • SWE Service Model • OWS-4 SWE Demo Overview

  3. OGC Process – Iterative DevelopmentYielding Tested Specifications

  4. POP: 6months (May -> December 2006) Participants 3eTI CSIRO-EM CSIRO-ICT Ecosystems Associates EUSC IFGI (Uni. Muenster) IRIS UAH (Uni. Alabama Huntsville) Vightel Washington University Sponsors, Additional Participants and Observers LMCO, NGA, NASA, ORNL IEEE 1451 OWS-4 SWE Participants and Stakeholders

  5. SWE Concept

  6. Enabling Sensor Webs with SWE Framework

  7. Seek to automate and shorten the decision-action loop. Focus on: automated sensor management and sensor data processing to produce actionable information for decision makers. 1 subscribe Controller SAS 2 3 Decision Support System  change ! alert! 4 5 SPS 6 task submitRequest 8 7 put getObservation SOS Viewer 9 display observation 10 Obs DB get 14 11 get execute WPS Sensor Data Systems 12 result 13 OWS-4 Scenario: Alert-driven Processing of Sensor Data • The approach must be modular, extensible and standards-based (i.e., not a “point solution”)

  8. A SOA Workflow for Sensor Data (1) SWE O&M – ANSI 42.42 Schema Mapping Algorithm IEEE 1451NCAP WFS (Rad Feature) Client WPS (transform + fusion) SOS (IEEE1451 – SensorML) Observation Object (e.g., measurement of temperature, rad. spectrum, velocity, etc + metadata) Radiation Event Feature Raw Sensor Data (e.g., IEE1451) Composite map ANSI 42.42 GML Feature IEEE 1451 TEDS + Sensor Channel Data

  9. SOS A SOA Workflow for Sensor Data (2) Schema Mapping Algorithm SAS GeoRSS | (CAP + EDXL-DE) Server Client WPS (transform + fusion) Notification / Warning message Raw Sensor Alert (e.g., IEE1451, TML, proprietary) GeoRSS | CAP Message Composite map Sensor-Triggered Alert (e.g., location, status, measured results)

  10. SWE Use Cases • OWS1.2 Use Cases • UCArch1_FindData.doc • UCArch2_FindServices.doc • UCArch3_BindData2Service.doc • UCReg10_PublishAssociation.doc • UCReg1_FindExtrObject.doc • UCReg2_FindQueryExtrObject.doc • UCReg3_FindQueryClassExtrObject.doc • UCReg4_PublishClassObject.doc • UCReg5_PublishData.doc • UCReg6_PublishService.doc • UCReg7_PublishServiceType.doc • UCReg8_PublishDataType.doc • UCReg9_PublishTaxonomy.doc • UCSW1_FindTerrorist.doc • UCSW2_FindBorderEvent.doc • UCSW3_FindSports.doc • UCSW4_FindSensor.doc • UCSW5_RequestObservation.doc

  11. DraftORNLSensorNetSWEUseCases.doc UC1.1: Steady-State (all nodes and sensors are known) UC1.2: New Sensor Plugged In UC1.3: Sensor “alerts” (threshold exceeded) GeoVideo_Use-cases_draft.doc UC2.1: Sensor In Area UC2.2: Track Sensor Feed UC2.3: Change Sensor Target UC2.4: Stop, Rewind, Play NASA_Ames_SPS_UseCases-20050508.doc UC3.1: UAV1 Sensor Planning and Tasking in R-T with Remote Manual Intervention UC3.2: UAV2 Sensor System Planning and Tasking in R-T w/o Manual Intervention UC3.3: UAV3 SPS Feasibility Req/Resp Detail OWS-3 Use Cases-ACTM.ppt UC4.1: Need Imagery Quick UC4.2: Multi-spectral Imagery On Point Target UC4.3: HiRes Optical/Full-Motion Video on Point Target UC4.4: Optical Area Target w/ Time Constraint & Multiple Looks UC4.5: Optical Point Target w/ Viewing Constraint UC4.6: Dual Tasking w/ Optical & SAR LOC Target w/ Time, Multiple Looks OWS-3-RFQ-UseCases.doc UC5.1: Airborne Collection (discovery, tasking, notification and access of sensor data) UC5.2: Airborne Collection Federated Context (sensors and platforms can be shared across organizational boundaries) UC5.3: Tasking Airborne Collection (need information from sensor not currently available) UC5.3.1: Tasking Airborne Collection with Bids UC5.3.2: Tasking Airborne Collection with Federation UC5.4: Airborne Processing Chain (task, process, exploit) UseCasesfor1451Sensors.pdf UC6.1: Register new sensor/TIM UC6.2: System unregisters TIM UC6.3: Plugin 1451.2 Sensor with TIM UC6.4: Plugin 802.11-based SensorML with TIM UC6.5: Plugin 1451.4 Sensor with TIM UC6.6: Applicatioin Selects a Transducer Channel from the NCAP UC6.7: Request Discrete Sensor Measurement UC6.8: Request Steaming Sensor Measurements More SWE Use Cases

  12. OWS-4 SWE Specification Baseline

  13. OWS-4 SWE Baseline (external specifications) • ISO • ISO 19101-2 - Reference model - Part 2: Imagery • ISO 19123 - Schema for Coverage Geometry and Functions • ISO 19130 - Sensor and data models for imagery and gridded data • ISO 19136 - Geography Markup Language (GML 3.2.0 – OGC 05-108r1) • ISO/IEC JTC1/SC29/WG11 N4668, Coding of Moving Pictures and Audio (MPEG 4). http://www.chiariglione.org/mpeg/standards/mpeg-4/mpeg-4.htm • IEEE-1451 (http://www.motion.aptd.nist.gov/) • IEEE Std 1451.1-1999, Network Capable Application Processor (NCAP) Information Model for smart transducers • IEEE P1451.0, Common Functions, Communication Protocols, and Transducer Electronic Data Sheet (TEDS) Formats • IEEE Std 1451.2-1997, Transducer to Microprocessor Communication Protocols and Transducer Electronic Data Sheet (TEDS) Formats • IEEE Std 1451.3-2003, Digital Communication and Transducer Electronic Data Sheet (TEDS) Formats for Distributed Multidrop Systems d • IEEE Std 1451.4-2004, Mixed-mode Communication Protocols and Transducer Electronic Data Sheet (TEDS) Formats • IEEE P1451.5, Wireless Communication and Transducer Electronic Data Sheet (TEDS) Formats – • IEEE P1451.6, A High-speed CANopen-based Transducer Network Interface • OASIS (http://www.oasis-open.org) • Common Alerting Protocol (CAP) • Emergency Data Exchange Language (EDXL) Distribution Element, (EDXL-DE)

  14. SPS SAS WNS O&M SOS SWE Common SensorML TML SWE Information Model Views

  15. O&M Observation Model An om:Observation instance is a gml:FeatureType::Event generated by a Procedure <<gml:Event>> om:Observation • TypedValue • name • value • <<ObsProcedure>> Procedure • General • Sensor • SensorSystemDescription • SensorML Document • TML Document <<Phenomenon>> observedProperty <<AbstractFeature>> featureOfInterest • Kinds of Observations include: • Measurement • Category • Count • Truth • Coverage • Properties • event parameters • time • quality • responsible party • “Measured” results • Result (the data value) • resultDefinition (data encoding desc.)

  16. SWE “Common” (Commonly used data encodings) • Basic Types • Temporal Aggregates • Phenomenon • Position Data • Record • RecordSchema • Data • Parameters

  17. SWE Services SOS = Sensor Observation Service SAS = Sensor Alert Service SPS = Sensor Planning Service CSW = Catalog Service (for Sensor Resources) SWE Data Center Composition of integrated SOS, SPS and SAS service implementations Tasking of sensors, access to sensor system observation data and alerting of sensor system state changes and measurements. Support the requirements for sensor systems and protocols (IEEE1451, MPEG4, ANSI 42.42, XMPP, OASIS CAP/EDXML) Descriptions of the sensors systems, observation offerings and services must be published to CSW implementations CSW SWE Service Model (A Data Center View)

  18. SWE Demo Site: NYNJ Port Authority

  19. Hospital Site at Airport

  20. Sensors Integrated in the SWE Demo Network • ORNL Rad Sensor • ORNL-SAS, 3eTI-SOS • IRIS and IFGI Video Sensors/Actuators • IFGI-SPS, 3eTI-SOS • Smart Sensor Systems Light Sensor (TinyTIM™ 1451 Bluetooth) • 3eTI-SOS • NASA EO1 Hyperion Imagery Sensor • Vightel-SOS, Vightel-SAS, Vightel-SPS • Environment Sensors (Moisture, AmbTemp, SoilTemp, Solar Voltage/Current) • CSIRO-ICTC SAS and SOS • NWS Weather Sensors • IFGI-SOS • Doppler Radar Sensors • UAH-SOS • GOES Imagery Sensor • UAH-WCS

  21. OWS-4 Sensor Network @ PANYNJ

  22. Tasking TML Camera in Warehouse

  23. EO-1 User Story • DHS analyst requests satellite imagery in disaster area to validate potential site. Catalog returns EO-1 as possible source.[via CSW service]. • Access to high resolution EO-1 data is granted based on user/role permission • No data is available, so satellite tasking is required and achieved (at no cost to DHS) [via SPS service]. • Analyst is notified via IM that Hyperion/ALI data products are available. High resolution imagery is retrieved [via SOS and WCS and WFS services].

More Related