Geneva, Switzerland, 18 February 2014 OGC Where the Internet of Things touches Location/Space Bart...

transcript

Geneva, Switzerland, 18 February 2014

OGCWhere the Internet of Things

touches Location/Space

Bart De Lathouwer,OGC, bdelathouwer@opengeospatial.org

ITU Workshop on the “Internet of Things - Trend and Challenges in Standardization”

(Geneva, Switzerland, 18 February 2014)

Topics

Introduction

IoT touches Location/Space

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

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

SensorDescription Language

PhenomenonDescription Language

Services

Observation Tasking Alerting Analysis

SensorML O&M TML

TML SOS SPS SAS WNS

SensorsRegister

Register

Search

SOSSOSBindDB

Publish

SensorML

Register

Sensors

Register

SOSSPS

SensorML

TaskSearch

Notify3

notification

GetResults5

Sensors

Register

Search

SOSSASGetResults

SensorML

Notify

notification

Register

Publish

NotifyBind

Sensors Sensors EverywhereEverywhere(Things or Devices)(Things or Devices)

50 billions Internet-connected things by 50 billions Internet-connected things by 20202020

OGC SWE-IoT Focus

Existing IoT Applications are Silos

IoT IoT service service

ApplicatiApplication Aon A

ApplicatiApplication Bon B

ApplicatiApplication Con C

ApplicatiApplication Don D

Silo A Silo B Silo C Silo D

Let’s say you want to develop the following application

IoT IoT service service

ApplicatiApplicationon

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.

Opportunities for Standards

ThingSpeak

Xively (Pachube)

SensorCloud

Others... NumerexOthers...Device Cloud

Evrythng

OGC SW-IoT Goal

IoT service A IoT service B IoT service C IoT service C

Many more innovative applications by mashing-up the IoT data infrastructure

Why OGC?

Every thing has a locationLocation 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

Example: GML Point Profile

<gml:Point srsName=”urn:ogc:def:crs:EPSG:6.6:4326”>

<gml:pos>45.256 -110.45</gml:pos>

</gml:Point>

Describe the location of a THING using geographic coordinates

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

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 StatusOGC SensorThings API Status

Current draft on GitHubhttp://ogcnetwork.net/sensorthings

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:http://github.com/OGC-IoT/ogc-iot-api/issues

Brief Introduction: URI Components

• URI Components– based on OASIS OData

http://service_root_URI/Things(1)/Sensors?$top=2&orderby=ID

service root URI resource path query options

Brief Introduction: Data Model

Timeline

201420142013201320112011 20122012

Finalization and signed-off standard

Draft APIJanuary 2013

OGC IoT WorkshopBrussels

Sensors4 IoT ad hoc meeting March 2012 in Austin, TX

Sensors4 IoT first meetingJune 2012 in Exeter UK

Use cases for Public ReviewOctober 2012

Draft API v.0.2March 2013

We are here!!

Draft SpecFebruary 2014

Conclusions

OGC and IoTMature SWE stack

SWE Implementation Maturity ER

CityGML, IndoorGML, ARLight-weight SWE

OGC SensorThings APIOGC SensorThings API

Geneva, Switzerland, 18 February 2014 28

Next steps

Democratize IoTSemantic interoperability & mediationSecurityOpportunistic networks…

Recommendations

Influence the standardsParticipate in standards making process

Work with other SDO and initiativesInteroperability across the OSI stackITU, IEEE, OASIS, W3C, M2M, ISO, ETSI, IERC, IoTA, …

Questions?

Geneva, Switzerland, 18 February 2014 OGC Where the Internet of Things touches Location/Space Bart...

Documents