The recording is available here: https://www.youtube.com/watch?v=O76ACZmQ730 This talk will present the OGC® SensorThings API specification and its MQTT extension, a new OGC® standard for IoT data interoperability that simplifies and accelerates the development of Internet of Things (IoT) applications. The IoT marketplace is a rapidly growing space with companies developing their own version and interpretation of an IoT platform. Unfortunately many IoT silos have emerged. There is a growing need to have a standards-based solution to truly realize the vision of having a connected world where sensors from across different disciplines can utilize a single API and provide enriched metadata to form a system of systems. We will present and demonstrate the OGC® SensorThings API. SensorThings API is semantically rich (based on the OGC/ISO Observation and Measurement), very easy to use (RESTful and JSON), built for real-time applications (MQTT extension) and it allows for simple modeling of the observations, the physical world and the sensors used to observe and measure real phenomena in it. The demonstration will also showcase the OGC® SensorThings API MQTT extension based on Eclipse Paho and Mosquitto.

1. 5
OGC SensorThings: IoT Data
Interoperability with a GeoWeb approach
0.23 litre/minute
0.25 litre/minute
0.27 litre/minuteRH: 85 %
Temp: 18 Celsius
Dr. Steve Liang
Chair, OGC SensorThings API Standard Working Group
Rapporteur, ITU-T Q12/11 on IoT Test Specifications
Founder and CEO, SensorUp Inc.
Associate Professor, University of Calgary

2. sensorup.com@sensorup
Agenda
• Introduction to Open Geospatial Consortium (OGC)
• Why Location (almost always) matters?
• What is IoT interoperability?
• Introduction to OGC Sensor Web Enablement
• Introduction to OGC SensorThings API
• SensorThings API Introduction and Benefits
• Case Studies
• Demo

3. sensorup.com@sensorup
About Dr. Steve Liang
• Associate Professor, Geomatics Engineering, Uni. Calgary
• AITF-Microsoft Industry Chair on Open Sensor Web
• Chair OGC SensorThings API Standard Working Group
• Co-Chair OGC Sensor Web Enablement Domain Working Group
• N.A. Chair, OGC University Domain Working Group
• Rapporteur, ITU-T SG12/11 on Internet of Things Test Specifications
• Founder and CEO, SensorUp Inc, a University of Calgary startup
(http://www.sensorup.com)

4. sensorup.com@sensorup
About SensorUp
• We are a world leader in OGC Sensor Web and IoT
• e.g., we developed the very first integrated SWE client back in 2005.
• Our clients include Lockheed Martin, Natural Resources Canada, Agriculture
and Agri-Food Canada, etc.
• We are leading several international IoT standard development efforts (OGC
and ITU-T)
• We developed world’s first OGC SensorThings API implementation
• We are proud member of Eclipse and OGC.

5. OGC
®
Copyright © 2016 Open Geospatial Consortium
Not-for-profit, international voluntary consensus standards organization;
leading development of geospatial standards
• 20th Anniversary celebrated in 2014
• 515+ members
• 40+ standards
• Many profiles, schema and best practices
• Thousands of product implementations
• Broad user community
implementation worldwide
• Alliances and collaborative activities with many
other organizations
• Every OGC standard at least needs three
independent implementations.
The Open Geospatial Consortium
5
Commercial
41%
Government
18%
NGO
10%
Research
7%
University
24%
Some OGC standards become ISO standards

6. OGC
®
What are OGC standardizing?
6
Web Service A
(or a Client)
Web Service B
2. web service interfaces (also ISO 19119)
1. information models and encodings
In other words, OGC’s IoT work can be
considered as Web of Things (WoT) as well.

7. sensorup.com@sensorup
Why Location (almost always) matters?
Smoke Detector Emergency Evacuation

8. sensorup.com@sensorup
Location Technology Evolution
Region-Centric
Geospatial
Information
Feature-Centric
Geospatial
Information
Human-Centric
Geospatial
Information
Device-Centric
Geospatial
Information
1980s 1990s 2000s 2010s
Georgia

9. sensorup.com@sensorup
number of
users
size of spaceUrban Planning/
Civil Engineering
Car Navigation/
Web Map
Pedestrian
Navigation
??
<1m

10. sensorup.com@sensorup
number of
users
size of spaceUrban Planning/
Civil Engineering
Car Navigation/
Web Map
Pedestrian
Navigation
??
<1m
Region-Centric
Geospatial
Information
Feature-Centric
Geospatial
Information
Human-Centric
Geospatial
Information
Device-Centric
Geospatial
Information

11. sensorup.com@sensorup
number of
users
size of spaceUrban Planning/
Civil Engineering
Car Navigation/
Web Map
Pedestrian
Navigation
??
<1m
Indoor
Space
Region-Centric
Geospatial
Information
Feature-Centric
Geospatial
Information
Human-Centric
Geospatial
Information
Device-Centric
Geospatial
Information

12. sensorup.com@sensorup
number of
users
size of spaceUrban Planning/
Civil Engineering
Car Navigation/
Web Map
Pedestrian
Navigation
??
<1m
Region-Centric
Geospatial
Information
Feature-Centric
Geospatial
Information
Human-Centric
Geospatial
Information
Device-Centric
Geospatial
Information
Indoor
Space
IoT
Space

13. sensorup.com@sensorup
“77% of surveyed IoT experts claimed
that Interoperability is the biggest
challenge currently facing the Internet
of Things”
IoT Nexus Report

14. sensorup.com@sensorup
Why is IoT interoperability important?
• Future Proof
• No Vendor Lock-in, More Choices!
• Lower Capital expenditure (CAPEX)
• Lower Operating expenditure (OPEX)
• Lower Training Cost
• Innovation in Assembly (create
Network Effect)

15. sensorup.com@sensorup
(IEEE) Interoperability is the ability of two or more (IoT)
systems or components to exchange information and to use
the information that has been exchanged.
(Brodie, 1993) Two components X and Y can interoperate
(are interoperable) if X can send requests R for services to Y,
based on a mutual understanding of R by X and Y, and if Y
can similarly return mutually understandable responses S to X.
What is IoT Interoperability?

16. sensorup.com@sensorup
IoT Interoperability, which layer?
Devices
(Hardware)
Local Sensor
Networks
Transit Network
Routing (IP)
Application
Protocol
Device-Cloud
Interfaces (API)
Data Models
Applications
mBed Arduino
Zigbee
SigFox
6lowpan
CoAP HTTP MQTT
LWM2M
OGC
Sensor-
Things
OGC
Sensor-
Things
ISO 19156
(O&M)
LoRa
SigFox LoRa
IPV4/V6
IoT Data
Interoperability
IoT Network
Interoperability
OGC SWE
and
SensorTh
ings API

17. sensorup.com@sensorup
IoT (WoT) Value Chain
Sensor
and
Actuator
Smart
Things
Network
Operator
Device-
Cloud API
Data and
Analytics
APP-Cloud
API
System
Integrator/
Application
Provider
1 2 3 4 5 6 7
OGC SensorThings API
and SWE

18. Service Registry/
Search Engine
OGC Vision: an word wide sensor web
(OGC Sensor Web Enablement)
A Sensor Web Browsersensor system A :Air
sensor system B :Water
sensor system C : Smartphones
station 1
station 2
station 3
station 4
station 5

19. OGC
®
Observation and Measurement (O&M)
OGC/ISO 19156:2011
19

20. OGC
®
O&M Concept
20

21. OGC
®
21
Sensor Web Enablement is a mature standard
https://portal.opengeospatial.org/files/?artifact_id=53823
Proven Working!!
More details: OGC SWE Implementation Maturity Report

22. sensorup.com@sensorup

23. OGC
®
23
OGC SensorThings API

24. sensorup.com@sensorup
“I was impressed with the ‘state of the practical’
where these various industry sensors can be
integrated today using open standards (i.e.,
SensorThings API) that remove the stovepipe
limitations of one-off technologies.”
Dr. Reginald Brothers
Under Secretary for Science and Technology

25. sensorup.com@sensorup
What is SensorThings API
• An Open Geospatial Consortium (OGC) Standard Candidate (approval
vote ends in 5 days!!)
• Part of the mature OGC Sensor Web Enablement standards
• Provide the following functions:
• Sensor Data Management (sensing profile - part I)
• Sensor Data Analytics (sensing profile - part I)
• Command and Control (tasking profile - part II)
• Event Detection and Notification (rules engine profile - part III)

26. sensorup.com@sensorup
Applications or
Devices
Web Server
(e.g., Cloud)
2. SensorThings API RESTful Interfaces for accessing
sensor data, tasking actuators and detect events
1. Standard Data Model based on ISO/OGC
Observation and Measurement
MQTT, HTTP, CoAP

27. sensorup.com@sensorup
SensorThings API Entities

28. HTTP Verbs to CRUD
• POST
• create a new entity
• PATCH
• update partial resources
• DELETE
• remove an entity

29. sensorup.com@sensorup
DEMO - SensorThings Playground
• http://pg.sensorup.com

30. Demo and GIST
• https://gist.github.com/liangsteve/
9bbc095c9e417af63a6e

31. Query Options
31

32. Evaluating System Query Options
32
• Prior to applying any server-driven paging:
• $filter
• $orderby
• $skip
• $top
• After applying any server-driven paging:
• $expand
• $select (reduce data transmitted)

34. • SensorThings API MQTT Extension
• http://jsfiddle.net/nrv4wbhf/4/
• http://jsfiddle.net/0etm8kvn/4/

35. sensorup.com@sensorup
SensorThings API Maturity
• Adoption vote ends on February 1st 2016
• OGC Compliance Test available
• At least four different server implementations
• Being tested in OGC Incident Management Information
Sharing Pilot (sponsored by Department of Homeland
Security and IJIS)

36. sensorup.com@sensorup
FAQ
• Is SensorThings API part of the OGC Sensor Web Enablement?
• YES.
• Is SensorThings API compatible with OGC Sensor Observation Services?
• YES.
• Is SensorThings API compatible with Spatial Data Infrastructure (SDIs)?
• YES.
• Can I use my existing GIS to connect to SensorThings API services?
• YES. For example, we have an ArcGIS plug-in available.

37. Case Study #1
• A pilot project funded by Department of Homeland Security and IJIS
Institute
• Problem:
• lacking a Common Operating Picture (COP) for various first responder
groups and disaster managers
• Solution:
• SensorUp platform allows various group to access heterogeneous
sensing systems
Case Study #1

38. OGC
®
Incident Management Information Sharing
(an OGC Pilot Project)
38
• Project sponsor:

39. Case Study #1
• Opportunities:
• next generation first responders need to be protected, connected,
fully aware.
• sensors are everywhere, including smart shirts, plug-and-play
sensing systems, smart cities infrastructure
• lacking a Common Operating Picture (COP) for various first
responder groups and disaster managers
• Solution and Results:
• SensorThings API allows various groups accessing
heterogeneous IoT-based sensing systems within a coherent
platform
• enable interoperability
• can reduce implementation and training time and cost
significantly in the future

40. sensorup.com@sensorup
Sensor registration

41. sensorup.com@sensorup
Smart Shirt and Wearable Cam

42. sensorup.com@sensorup
Event Notification via MQTT

43. sensorup.com@sensorup
SensorThings API Next Step
• SensorThings Part II - Tasking
• SensorThings Part III - Rules Engine
• ISO
• ITU-T

44. sensorup.com@sensorup
Arctic Citizen Sensors

45. sensorup.com@sensorup
How to learn more?
• Video tutorials: SensorUp YouTube Channel
• Developer Documentations: http://sensorup.com/
docs/
• OGC SensorThings SWG Community Site: http://ogc-
iot.github.io/ogc-iot-api/
• Read our technical blog: http://sensorup.com
• Attend our bi-weekly webinars: http://
www.sensorup.com/index.php/tag/webinar/

46. sensorup.com@sensorup
Acknowledgement

47. sensorup.com@sensorup
Any Questions?