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

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

3. The Open Geospatial Consortium
Not-for-profit, international voluntary consensus standards organization; leading development of geospatial standards
Founded in 1994.
480+ 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 3

4. Sensors Are Everywhere

5. 5
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

6. Task sensors, when possible, to meet my specific needs 6
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

7. Sensor Web Vision I Sensors will be web accessible7
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

8. 8
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

9. 9
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)

10. Building Blocks: OGC SWE
1010
Observations & Measurements (O&M) - Standard models and XML Schema for encoding observations and measurements from a sensor, both archived and real-time.
Sensor Model Language (SensorML) - Standard models and XML Schema for describing sensors systems and processes associated with sensor observations; provides information needed for discovery of sensors, location of sensor observations, processing of low-level sensor observations, and listing of taskable properties, as well as supports on-demand processing of sensor observations.
Transducer Model Language (TransducerML or TML) - The conceptual model and XML Schema for describing transducers and supporting real-time streaming of data to and from sensor systems.
Sensor Observations Service (SOS) - Standard web service interface for requesting, filtering, and retrieving observations and sensor system information. This is the intermediary between a client and an observation repository or near real-time sensor channel.
Sensor Planning Service (SPS) - Standard web service interface for requesting user-driven acquisitions and observations. This is the intermediary between a client and a sensor collection management environment.
Sensor Alert Service (SAS) - Standard web service interface for publishing and subscribing to alerts from sensors.
Web Notification Services (WNS) - Standard web service interface for asynchronous delivery of messages or alerts from SAS and SPS web services and other elements of service workflows.
Building Blocks: OGC SWE
Services
Observation
Tasking
Alerting
Analysis
TML
SOS
SPS
SAS
WNS
Registries & Dictionaries
Sensor
Description Language
Phenomenon
Description Language
SensorML
CS-W
O&M
TML

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

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

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

14. © 2012 Open Geospatial Consortium

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

16. Existing IoT Applications are Silos
Silo A
Silo B
Silo C
Silo D
Application B
Application C
Application D
Application A
IoT service A
IoT service B
IoT service C
IoT service D

17. Let’s say you want to develop the following application
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.
Application
IoT service A
IoT service B
IoT service C
IoT service D
OGC

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

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

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
<gml:Point srsName=”urn:ogc:def:crs:EPSG:6.6:4326”>
<gml:pos> </gml:pos>
</gml:Point>

22. Describe the location of a THING in a building
Example: OGC CityGML
Describe the location of a THING in a building
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)

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

24. 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
Submit your comments here: x

25. Brief Introduction: URI Components
based on OASIS OData
service root URI
resource path
query options

26. Brief Introduction: Data Model

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

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

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

30. Influence the standards Work with other SDO and initiatives
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 2014

31. Questions?
Geneva, Switzerland, 18 February 2014