The Internet of Things (IoT) is set to occupy a substantial component of future Internet. The IoT connects sensors and devices that record physical observations to applications and services of the Internet[1]. As a successor to technologies such as RFID and Wireless Sensor Networks (WSN), the IoT has stumbled into vertical silos of proprietary systems, providing little or no interoperability with similar systems. As the IoT represents future state of the Internet, an intelligent and scalable architecture is required to provide connectivity between these silos, enabling discovery of physical sensors and interpretation of messages between the things. This paper proposes a gateway and Semantic Web enabled IoT architecture to provide interoperability between systems, which utilizes established communication and data standards. The Semantic Gateway as Service (SGS) allows translation between messaging protocols such as XMPP, CoAP and MQTT via a multi-protocol proxy architecture. Utilization of broadly accepted specifications such as W3Cs Semantic Sensor Network (SSN) ontology for semantic annotations of sensor data provide semantic interoperability between messages and support semantic reasoning to obtain higher-level actionable knowledge from low-level sensor data.
Link to the paper: http://knoesis.org/library/resource.php?id=2154
Citation:
Pratikkumar Desai, Amit Sheth, Pramod Anantharam, 'Semantic Gateway as a Service architecture for IoT Interoperability', IEEE 4th International Conference on Mobile Services, June 27 - July 2, 2015, New York, USA.
Semantic Gateway as a Service architecture for IoT Interoperability
1. Semantic Gateway as Service for IoT
Interoperability
Pratik Desai*, Amit Sheth**, Pramod Anantharam**
*Imbue Inc.,
**Ohio Center of Excellence in Knowledge-enabled
Computing(Kno.e.sis),
Wright State University, USA
Presentation for: IEEE 4th International Conference on Mobile Services, June 27 – July 2, 2015, NY, USA
3. IoT has resulted in multiple vertical silos
3
App
Fitbit
Home Router
NEST
IoT
Platform
Fitbit activity
tracker
Health
sensor
Weighing
scale
NEST
4. Interoperability is an issue at each level
4
Network level Messaging level Data Annotation level
- Mostly sink nodes are
resource constrained
devices.
- In major cases, low
power networking
protocols such as
ZigBee, Zwave,
Bluetooth, etc. are
used.
- Traditional protocols
are also used i.e.
Ethernet and WiFi.
- Applications and
vendor dependent.
- Competing protocols
for resource
constrained devices
are CoAP, MQTT and
XMPP.
- Traditional HTTP
RESTful methods are
utilized at service
level.
- Major IoT products
have propriety data
models.
- In most cases,
without semantic
annotations.
- Few attempts have
been made to
standardize data
models, though still
scattered.
5. Attempts in similar vein
5
SemSOSSSN OntologyOGC SWE
Messaging Level:
Data Level:
6. SGS: Semantic Gateway as Service as a
semantic web based IoT solution
• Addresses the interoperability challenges at messaging
and data model level.
• Enables knowledge based annotation of raw sensor data
with seamless integration between heterogeneous
architectures.
• Provides interface for high-level, semantic web enabled
IoT services.
• Assists resource constrained devices by transferring
complex computation to the gateway level.
6
10. SGS: Semantic Data Annotation converts raw
data into semantically annotated information
12
11. SSW Introduction
lives in
has
pet
is ahas pet
Person Animal
Concrete Facts
Resource Description Framework
Semantic Web
(according to Farside)
General Knowledge
Web Ontology Language
“Now! – That should clear up a few things around here!”
is a
12. 14
RDF OWL
Semantic Sensor Networks (SSN)
How are machines supposed to integrate and interpret sensor data?
13. 15Lefort, L., Henson, C., Taylor, K., Barnaghi, P., Compton, M., Corcho, O., Garcia-Castro, R., Graybeal, J., Herzog, A., Janowicz, K.,
Neuhaus, H., Nikolov, A., and Page, K.: Semantic Sensor Network XG Final Report, W3C Incubator Group Report (2011).
W3C Semantic Sensor Network Ontology
14. 16Lefort, L., Henson, C., Taylor, K., Barnaghi, P., Compton, M., Corcho, O., Garcia-Castro, R., Graybeal, J., Herzog, A., Janowicz, K.,
Neuhaus, H., Nikolov, A., and Page, K.: Semantic Sensor Network XG Final Report, W3C Incubator Group Report (2011).
W3C Semantic Sensor Network Ontology
18. Conclusion
• Proposes a novel solution that integrates semantic web
technology with existing sensor communication protocols
and service standards.
• Enables translation of messages between widely used
messaging protocols for resource-constrained devices.
• Enhances service level interoperability such as
integration with SemSOS.
• Addresses various interoperability challenges faced by
real-world IoT deployments.
20
19. Thank you, and please visit us at http://knoesis.org
For more information on kHealth, please visit us at http://knoesis.org/projects/ssw
Thanks
Link to the paper: http://knoesis.org/library/resource.php?id=2154
Editor's Notes
Time series observations are readily and naturally available in domains such as finance, health care, smart cities, and system health monitoring. Increasingly, time series observations include both sensor and textual data generated in the same spatio-temporal context creating both challenges for dealing with heterogeneous data and opportunities for obtaining comprehensive situational awareness. For example, in a city, there are machine sensors and citizen sensors observing the city infrastructure (e.g., bridges, power grids) and city dynamics (e.g., traffic flow, power consumption). In this research, we investigate extraction of city events from textual observations and utilize them explain variations in the sensor observations. This will improve our understanding of city events and their manifestations due to the complementary nature of observations provided by the machine sensors and citizen sensors.
IoT platform can be DIY projects
ZigBee, Zwave – resource constrained protocols
We are not solving Network Level problem
XMPP pubsub
http://www.xmpp.org/extensions/xep-0060.html
CoAP
http://coap.technology/
Ponte
https://eclipse.org/ponte/
OGC SWE
M. Botts, G. Percivall, C. Reed, and J. Davidson, “Ogc⃝R sensor web enablement: Overview and high level architecture,” in GeoSensor networks. Springer, 2008, pp. 175–190.
SSN Ontology
L. Lefort, C. Henson, K. Taylor, P. Barnaghi, M. Compton, O. Corcho, R. Garcia-Castro, J. Graybeal, A. Herzog, K. Janowicz et al., “Semantic sensor network xg final report,” W3C Incubator Group Report, vol. 28, 2011.
SemSOS
C. A. Henson, J. K. Pschorr, A. P. Sheth, and K. Thirunarayan, “Semsos: Semantic sensor observation service,” in Collaborative Technologies and Systems, 2009. CTS’09. International Symposium on. IEEE, 2009, pp. 44–53.
Three main building blocks of the SGS
Multi-protocol proxy
Semantic annotation service
Gateway service interface
Multi-protocol proxy is assisted by the Message store and Topic routers
It basically translate messages coming from MQTT, XMPP and CoAP protocols to REST or Pubsub.
Semantic annotation service annotate raw sensor data into semantically annotated data using standard semantic ontologies and domain specific ontologies.
Gateway service interface convert data from RDF to json-ld and prepare it to further deliver it to external services using REST or pubsub interface.
This is a software architecture of the Multi-protocol proxy
On internal side, the multi-protocol proxy has interfaces to receive messages from different messaging clients such as CoAP, MQTT and XMPP.
Once the message is received from the Message broker, it saves it in the Message Store if the it needs to be delivered later. Meanwhile, it also register the resource as a topic in the Topic router to be later used in the protocol translation.
The data at this point is in the JSON format.
After Multi-protocol proxy, the data is sent to Semantic Annotation Service to semantically annotated using standard ontologies and domain specific ontology.
The data is converted into RDF at this point and send back to Multi-protocol proxy.
With the help of standard annotation techniques, now the data is comprehendible for the external services that are going to utilize it.
A thing to note that, the SGS will have to communicate the domain specific ontologies with the external services it going to communicate as these ontologies may vary from gateway to gateway and application to application.
The problem of Domain specific ontology can be also solved by having a central repository of these ontologies.