Semantic IoT Solutions - A Developer Perspective

Semantic technologies have recently gained significant support in a number of communities, in particular the IoT community. An important problem to be solved is that, on the one hand, it is clear that the value of IoT increases significantly with the availability of information from a wide variety of domains. On the other hand, existing solutions target specific applications or application domains and there is no easy way of sharing information between the resulting silos. Thus, a solution is needed to enable interoperability across information silos. As there is a huge heterogeneity regarding IoT technologies on the lower levels, the semantic level is seen as a promising approach for achieving interoperability (i.e. semantic interoperability) to unify IoT device description, data, bring common interaction, data exploration, etc.This work has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreements No.732240 (SynchroniCity) and No. 688467 (VICINITY); from ETSI under Specialist Task Forces 534, 556, 566 and 578. This work is partially funded by Hazards SEES NSF Award EAR 1520870, and KHealth NIH 1 R01 HD087132-01

Towards Semantic Interoperability Standards based on Ontologies

The paper is structured as follows: Section 2 introduces semantic interoperability and its benefits; Section 3 provides industry requirements for semantic interoperability practice; Section 4 describes various initiatives for ontology-driven interoperability; Section 5 explains the various life cycles for ontology-driven interoperability; and finally, Section 6 provides recommendations on ontology-based semantic interoperability.This work has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreements No.732240 (SynchroniCity) and No. 688467 (VICINITY); from ETSI under Specialist Task Forces 534, 556, and 566. This work is partially funded by Hazards SEES NSF Award EAR 1520870, and KHealth NIH 1 R01 HD087132-01

Standard to facilitate Smart Body Area Networks

The ETSI Technical Committee Smart BAN has recently published ETSI TS 103 327, a standard for Smart Body Area Networks, to establish standardized service and application interfaces and facilitators, APIs (Application Programming Interfaces) and infrastructure for interoperability management and secure interaction and access to any SmartBAN data/entities. The resulting SmartBAN reference architecture is a global and more integrated IoT reference architecture that: is specified on top of the SmartBAN reference model (see ETSI TS 103 378), is oneM2M and Multi-Agent based, is provided with cross-functional components for allowing non SmartBAN enabled environments to interoperate with SmartBAN, addresses network/syntactic/informational/semantic interoperabilit

Standardizing Smart Body Area Networks

ETSI SmartBAN TC is a Technical Committee that was created in 2013 for developing and maintaining an ETSI Standard and Specification, reports, guides, etc. relating to smart, wireless Body Area Networks (BANs). It addresses everything related to BANs in a holistic way, i.e. from tiny medical sensors located inside/on the body up to remote end user devices (e.g. hospital Medical Information System - MIS -, caregiver' tablet, helper' Smartphone …), as well as from Physical (PHY) and medium access control (MAC) layers up to application layers. The addressed verticals are currently mainly related to eHealth, wellbeing/wellness and personal safety, but other use cases related to e.g. automotive are also envisione

General semantic system for monitoring & assisting diabetes patient "MySmart diabetes OntoREFerence" ontology

International audienceDiabetes is becoming a major health problem all over the world. Diabetes is a long-life disease that leads to many complications such as kidney failure, high blood pressure, high cholesterol, heart diseases, blindness, stroke, and even death. Diabetic patients need to manage their disease to stay healthy by eating healthier, taking medicine as directed, taking care of their body, reducing stress, being active, and checking the blood sugar daily by using on body and/or home monitoring devices. Thus, to avoid diabetes complications, diabetic patients need to be early diagnosed, monitored, and assisted. This can be achieved by building a general, user friendly, smart, and reliable system. This paper presents a general semantic system relying on a modular ontology annotating the daily activities, food, symptoms, and diabetes patients in order to monitor the parameters related to diabetes patients and assist him/her to avoid medical crisis. This modular ontology is conceived using OWL language and inference engine (Pellet reasoner) in order to fill the gap between diabetic patients, medical staff, and daily life activities systems. Pre-evaluation scenarios are discussed to prove the efficiency of the proposed ontologie

SmartM2M; Extension to SAREF; Part 8: eHealth/Ageing-well Domain

The present document presents SAREF4EHAW, an extension of SAREF for the eHealth/Ageing-well Domain

Smart Body Area Networks (SmartBAN) : service and application standardized enablers and interfaces, APIs and infrastructure for interoperability management

ETSI TS 103 327 V1.1.1. The present document describes and specifies the high level infrastructure, its building blocks and associated APIs providing interoperability management solutions for SmartBAN. The architecture described in the present document also enables generic interaction and access to BAN data and entities, and thus paves the way to interoperability (networks and syntactic interoperability). Since the SmartBAN reference architecture specified and formatized in the present document fully relies on SmartBAN open semantic data model and corresponding ontologies as already standardized in [1], it therefore also addresses data and semantic interoperability. The present document is applicable to a BAN and/or a SmartBAN comprising wearable sensors/actuators devices, a relay/coordinator device and a Hub. The relay/Coordinator and the Hub functionalities may be handled by a single device or by two distinct devices. The present document is also addressing syntactic interoperability by defining unified data transfer and message format