Geneva, Switzerland, 18 February 2014 OGC Where the Internet of Things touches Location/Space Bart De Lathouwer, OGC, ITU Workshop on the “Internet of Things - Trend and Challenges in Standardization” (Geneva, Switzerland, 18 February 2014)

© 2012 Open Geospatial Consortium Topics OGC Introduction IoT touches Location/Space SWE SWE for IoT Conclusions and Recommendations

The Open Geospatial Consortium Not-for-profit, international voluntary consensus standards organization; leading development of geospatial standards Founded in members and growing 33 “core” standards 15 extensions/profiles Hundreds of product implementations Alliances and collaborative activities with ISO and many other SDO’s Copyright © 2014 Open Geospatial Consortium 3

4

Sensor Web Desires  Quickly discover sensors and sensor data (secure or public) that can meet my needs – location, observables, quality, ability to task  Obtain sensor information in a standard encoding that is understandable by me and my software  Readily access sensor observations in a common manner, and in a form specific to my needs

Sensor Web Desires II  Task sensors, when possible, to meet my specific needs  Subscribe to and receive alerts when a sensor measures a particular phenomenon

Sensor Web Vision I  Sensors will be web accessible  Sensors and sensor data will be discoverable  Sensors will be self-describing to humans and software (using a standard encoding)  Most sensor observations will be easily accessible in real time over the web

Sensor Web Vision II  Standardized web services will exist for accessing sensor information and sensor observations  Sensor systems will be capable of real- time mining of observations to find phenomena of immediate interest  Sensor systems will be capable of issuing alerts based on observations, as well as be able to respond to alerts issued by other sensors

Sensor Web Vision III  Software will be capable of on-demand geolocation and processing of observations from a newly-discovered sensor without a priori knowledge of that sensor system  Sensors, simulations, and models will be capable of being configured and tasked through standard, common web interfaces  Sensors and sensor nets will be able to act on their own (i.e. be autonomous)

Building Blocks: OGC SWE Registries & Dictionaries Sensor Description Language Phenomenon Description Language Services ObservationTaskingAlertingAnalysis SensorMLO&M TML SOSSPSSASWNS CS-W

SWE CAT SOS Sensors Register Search SOS Bind DB Publish O&M SensorML Register

SWE CAT SOS Sensors WNS SPS Register SOS SPS SensorML Task Search 1 Task 2 Notify 3 notification 4 GetResults 5 O&M 6

SWE CAT SOS SAS Sensors WNS SPS Register Search SOS SAS GetResults SensorML Task Notify notification Register Publish Alert Notify Bind

© 2012 Open Geospatial Consortium

Sensors Everywhere (Things or Devices) 50 billions Internet-connected things by 2020 OGC SWE-IoT Focus

16 Existing IoT Applications are Silos IoT service A IoT service B IoT service C IoT service D Applicatio n A Applicatio n B Applicatio n C Applicatio n D Silo ASilo BSilo CSilo D

17 OGC Let ’ s say you want to develop the following application IoT service A IoT service B IoT service C IoT service D Applicatio n When my body temperature is high and hours of sleep is low, the light cannot be turned on and room temperature will be set to 15 degree Celsius.

18 Opportunities for Standards ThingSpeak Xively (Pachube) SensorCloud Others...Numerex Others... Device Cloud Evrythng

19 OGC OGC SW-IoT Goal IoT service A IoT service B IoT service C Many more innovative applications by mashing-up the IoT data infrastructure

20 Why OGC? Every thing has a location Location information needs to be carefully described. e.g., outdoor, indoor, geometry, topology, semantics, sensor space, etc. OGC Sensor Web Enablement is widely adopted and implemented e.g., OGC/ISO Observation and Measurements, OGC SensorML, OGC Sensor Observation Service, etc. The OGC SensorThings API is built based on the OGC SWE 20

21 ® Example: GML Point Profile Describe the location of a THING using geographic coordinates

22 ® Example: OGC CityGML – Semantic 3D city and building models provide the geometry and a thematic differentiation of the indoor areas (at least separation in building parts, levels and rooms) Describe the location of a THING in a building

23 ® Example: OGC Indoor GML Goal of IndoorGML – Common schema framework for Interoperability between indoor navigation applications Describe the location of a THING indoor

® OGC SensorThings API Status Current draft on GitHub a reference service implementation ready a simple client ready a.NET Micro Framework ready (Netduino) a Javascript library almost ready an Interactive SDK ready x Submit your comments here:

25 ® Brief Introduction: URI Components URI Components – based on OASIS OData service root URIresource pathquery options

26 ® Brief Introduction: Data Model

® Timeline Copyright © 2012 Open Geospatial Consortium Finalization and signed-off standard Draft API January 2013 OGC IoT Workshop Brussels Sensors4 IoT ad hoc meeting March 2012 in Austin, TX Sensors4 IoT first meeting June 2012 in Exeter UK Use cases for Public Review October 2012 Draft API v.0.2 March 2013 We are here!! Draft Spec February 2014

Conclusions OGC and IoT Mature SWE stack SWE Implementation Maturity ER CityGML, IndoorGML, AR Light-weight SWE OGC SensorThings API Geneva, Switzerland, 18 February

Next steps Democratize IoT Semantic interoperability & mediation Security Opportunistic networks … Geneva, Switzerland, 18 February

Recommendations Influence the standards Participate in standards making process Work with other SDO and initiatives Interoperability across the OSI stack ITU, IEEE, OASIS, W3C, M2M, ISO, ETSI, IERC, IoTA, … Geneva, Switzerland, 18 February

Questions? Geneva, Switzerland, 18 February