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, [email protected]
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 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 Consortium3
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
SensorDescription Language
PhenomenonDescription Language
Services
Observation Tasking Alerting Analysis
SensorML O&M TML
TML SOS SPS SAS WNS
CS-W
SWE
CAT
SOS
SensorsRegister
Register
Search
SOSSOSBindDB
Publish
O&M
SensorML
Register
SWE
CAT
SOS
Sensors
WNS
SPS
Register
Register
SOSSPS
SensorML
TaskSearch
1
Task2
Notify3
notification
4
GetResults5
O&M6
SWE
CAT
SOS
SAS
Sensors
WNS
SPS
Register
Register
Search
SOSSASGetResults
SensorML
Task
Task
Notify
notification
Register
Publish
Alert
NotifyBind
© 2012 Open Geospatial Consortium
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
16
Existing IoT Applications are Silos
IoT IoT service service
AA
IoT IoT service service
BB
IoT IoT service service
CC
IoT IoT service service
DD
ApplicatiApplication Aon A
ApplicatiApplication Bon B
ApplicatiApplication Con C
ApplicatiApplication Don D
Silo A Silo B Silo C Silo D
17OGC
Let’s say you want to develop the following application
IoT IoT service service
AA
IoT IoT service service
BB
IoT IoT service service
CC
IoT IoT service service
DD
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.
18
Opportunities for Standards
ThingSpeak
Xively (Pachube)
SensorCloud
Others... NumerexOthers...Device Cloud
Evrythng
19OGC
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
20
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
20
21
®
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
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 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
x
Submit your comments here:http://github.com/OGC-IoT/ogc-iot-api/issues
25
®
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
26
®
Brief Introduction: Data Model
®
Timeline
Copyright © 2012 Open Geospatial Consortium
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…
Geneva, Switzerland, 18 February 2014 29
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, …
Geneva, Switzerland, 18 February 2014 30
Questions?
Geneva, Switzerland, 18 February 2014 31