1. CEOS WGISS, Hanoi May 2007 1 OSCAR Prototyping the sensor web Wyn Cudlip BNSC/QinetiQ wcudlip@qinetiq.com Presentation to WGISS Hanoi May 2007 (Slides courtesy of Comsine)

2. CEOS WGISS, Hanoi May 2007 2 Introduction o BNSC, as part of its International Co-operation Programme, funds a number of small “Exploitation Projects” aimed at allowing UK companies to exploit and contribute to international activities. o OSCAR is one such project. n Duration: Jan to Aug 2007.

3. CEOS WGISS, Hanoi May 2007 3 OSCAR – OGC Compliant Sensor Control & Access Resource

4. CEOS WGISS, Hanoi May 2007 4 Project Objectives o Work with user partners to understand requirements and determine focus of the project o Build a UK software resource that supports the major aspects of the OGC Sensor Web Enablement (SWE) specifications o Look at the role Satellite Communication can play in a Sensor Web architecture o Investigate the integration of in-situ sensor measurements with Earth Observation (EO) data resources o Provide a live demonstration of the OSCAR framework based on use case scenarios o Use feedback from the user partners to understand the future direction of OSCAR

5. CEOS WGISS, Hanoi May 2007 5 Partners o Comsine n Small UK software development company o Critical Software n Portuguese software development company n Sensor Web interests: operational service for fire hazards o Hydromod n Portuguese technical consulting company n Sensor Web Interests: monitoring coastal waters o UK Environment Agency n already operate an extensive network of in-situ sensors o Satamatics n UK Satellite Communications Company n Suppliers of terminals operating under the Inmarsat D+ service n Sensor Web Interests: Oil Pipeline Monitoring

6. CEOS WGISS, Hanoi May 2007 6 Plans o 2 Sensor Nodes (one in UK, one in Australia) o Each node will host a weather station sensor and a webcam for taking stills imagery o Australia Node will use Satellite Communications over the Inmarsat D+ service o UK Node will be directly connected to the Internet via Ethernet o Use subset of the O&M and SensorML XML encodings n Describe both sensors and their observations o Code major elements of the SOS, SPS, SAS and WNS web services n Obtain sensor descriptions and sensor observations n Issue a tasking request for a sensor (will be partially simulated) n Register to receive alerts for “alarming conditions” from a sensor

7. CEOS WGISS, Hanoi May 2007 7 OGC SWE Components o Observations & Measurements (O&M) n XML Encoding compliant with OGC Best Practices Document 05-087r4 n Subset of encoding to handle the following observations – Temperature, Rainfall, Wind Speed/Direction, Humidity, Air Pressure o Sensor Modelling Language (SensorML) n XML Encoding compliant with OGC Implementation Specification 05-086r2 n Subset of encoding to describe the following sensors – Weather Station (WS-2300) – WebCam (e.g. Logitech QuickCam Messenger) o Transducer Markup Language (TML) n XML Encoding compliant with OGC Implementation Specification 06-010r2 n TML will not be implemented for this phase of OSCAR (will be simulated)

8. CEOS WGISS, Hanoi May 2007 8 OGC SWE Components o Sensor Observation Service (SOS) n XML Encoding compliant with OGC Implementation Specification 06- 009r1 n A web service for describing Sensors and obtaining their Observations

9. CEOS WGISS, Hanoi May 2007 9 OGC SWE Components o Sensor Planning Service (SPS) n XML Encoding compliant with OGC Implementation Specification 05-089r3 n A web service for tasking a sensor

10. CEOS WGISS, Hanoi May 2007 10 OGC SWE Components o Sensor Alert Service (SAS) n XML Encoding compliant with OGC Discussion Paper 06-028 n A web service that allows a sensor to be monitored for an “alarming condition”, e.g. temperature exceeds a given value n A user may subscribe to receive alerts

11. CEOS WGISS, Hanoi May 2007 11 OGC SWE Components o Web Notification Service (WNS) n XML Encoding compliant with OGC Best Practices Document 06-095 n Web Service for mediating asynchronously between web services, e.g. –Confirmation of a tasking request from an SPS –Issuing an alert from an SAS when an “alarming condition” occurs

12. CEOS WGISS, Hanoi May 2007 12 OSCAR Client o Web based client application for demonstrating the use case scenarios n Background mapping for viewing Sensor Node locations and details n Getting sensor descriptions and observations from an SOS n Obtain task-able parameters and submit a tasking request to an SPS n Subscribe to receive alerts from an SAS

13. CEOS WGISS, Hanoi May 2007 13 System Context o Sensor Node n Laptop PC with Weather Station and WebCam sensors attached via RS-232 or USB n A Data Logger will record observations n Sensor Node will send observations via some communications protocol n Communications via SATCOM and Internet will be demonstrated o OSCAR Server n The OSCAR Server will periodically scan the Data Repository for new observations n The Data Loader will load new observations into Data Storage n Data Storage will store observations using SWE O&M n Data Storage will also store description of the sensor using SWE SensorML o OSCAR SWE and Client n A set of OGC SWE compliant web services accessible over the internet n Sensor Observation Service – Obtain O&M and SensorML n Sensor Planning Service – Issue planning requests n Sensor Alert Service – Monitor sensors for “alarming conditions” n Web Notification Service – Alert user of “alarming condition” – Mediate with user for planning requests

14. CEOS WGISS, Hanoi May 2007 14 Communications o Australian Demo Site n Satamatics SAT-201 terminal via Inmarsat D+ n Sensor Node will load SAT-201 with latest observations n Observations are sent via satellite to the LES n The MHS (gateway) will retrieve messages from the LES n Message Client on the OSCAR Server will use ASPI-XML to look for new observations n New Observations are written to the Data Repository o UK Demo Site n Sensor Node connected to the internet via a wired Ethernet connection n New observations will be sent directly over the internet to the Data Repository (e.g. FTP)

15. CEOS WGISS, Hanoi May 2007 15 Web Services Architecture o O&M and SensorML are stored in a PostGres/PostGIS relational database o Data exposed to upper layers using Java Data Objects (Object Persistence) o Web Service is implemented as Java objects o OGC SWE XML requests and responses are marshalled and un- marshalled into objects using Apache XML Beans (Data Binding) o Client passes XML requests and responses using SOAP over HTTP o Non XML messages handled via Java Servlet, e.g. GetCapabilities

16. CEOS WGISS, Hanoi May 2007 16 Demonstrator implementation o Due to begin early-July o Demonstration of use cases to partners n Extreme Weather Warnings n Hazardous Waste Monitoring o The majority of the components will be demonstrated through a real software implementation o Where an implementation is not available (e.g. tasking requests), the demonstration will be partially simulated o Real and Simulated aspects of the demonstration are identified in the User Requirements Document (CSL- OSCAR-URD-001) o Feedback will be provided from all the user partners