European Commision s Smart Appliances REFerence ontology (SAREF)

Transcription

1 1 European Commision s Smart Appliances REFerence ontology (SAREF) Frank den Hartog frank.denhartog@tno.nl Tel June 2015, Ultrafast Broadband Seminar, TNO

2 2 Demonstrator at CES 2013 Frank den Hartog, et al, Enabling new e-health business models by converging IP-based and non-ip-based home networks, IEEE CCNC 2013 and CES 2013.

3 3 And many other control networks exist and are still being invented low-cost ($-range) low-bandwidth (order 100 kbps) low energy (battery operated) non-ip Example technologies: Zigbee Z-Wave BT Low Energy Wireless M-Bus DECT ULE P1 And many many more!

4 4 Smart Phone is not a success because it s a phone but because it s SMART!

5 5 What is the current situation? More and more devices become smart and are connected to the Internet (of Things) Smart Home Devices only connect to devices and servers from the same (group of) vendorspecific eco-system in a closed way IoT applications offered in silos on application layer End users are forced to use multiple apps and gateways to control their home or to invest in devices from only a few manufacturers that are interoperable These systems cannot be used for 3 rd (or rather: 4 th ) - party applications, e.g. such as developed by the developer community for open platforms 5

6 6 What is our vision? Abstraction layer Sub-ecosystems: Zigbee, Zwave, Thread, Bluetooth LE, ULE, Enable interoperability at the semantic level and automatically apply the concepts of an extensible ontology to the abstraction layer on any type of API, be it a programming language or a protocol Ontology technology, language Abstraction layer Shared sensors Shared screens Field buses Applications Embedded APIs OSGi, Linux Abstraction layer Execution environment Abstraction layer Cloud APIs OneM2M, OMA NGSI, Remote Access Business service platforms Cloud Execution environment Shared objects Abstraction layer High rate IP buses Smart Home box Smart Home Cloud Platforms AllJoyn, IoTivity, UPnP End users can control all smart devices in their home from one app and is not forced to buy all their devices from one (group of) manufacturer(s) Application developers can develop apps using open platforms that allow to control all devices within a home Holy Grail: entice the software developers community 6

7 7 Semantic interoperability Reports from NIST a.o. indicate that well over US$100 billion per year is lost because of the lack of a widely used semantic interoperability standard in the US alone Syntactic interoperability is a prerequisite for semantic interoperability Semantic interoperability is the ability of computer systems to exchange data with unambiguous, shared meaning This is accomplished by adding meaning to the data, linking each data element to a controlled, shared vocabulary This shared vocabulary is linked to an ontology

8 8 Ontologies An ontology is: a set of concepts used to describe the reality under consideration e.g., the concepts of household appliance, task and function ; precise definitions of these concepts in natural language relations among these concepts e.g., a household appliance of type washing machine accomplishes the task cleaning and to accomplish this task performs the function start and stop axioms to constrain the intended meaning of these concepts e.g., a washing machine is always a device A data model is a data base implementation (expressed e.g. in XML) of an ontology (typically expressed in OWL), adding e.g. syntax

9 9 TNO recently executed the EC Semantics of Smart Appliances project Goal: Support ETSI SMART M2M as an organization. Provide the material needed to define the relevant tools and data models for the collection of devices that helps the EU to reach its 2020 goals regarding the reduction of greenhouse gas emission and buildings energy consumption. Tasks: 1. Take stock of existing semantic assets and use case assets 2. Perform a translation exercise of each model or use case to a common ontology language and subsequently a mapping between these models 3. Propose a common ontology and document it into ETSI M2M architecture Timing: finished on 1 April 2015

10 10 10 Why a reference ontology? With 48 assets, 48x47=2256 translations are required without the reference ontology. The mappings allow translation from the reference ontology to specific assets, reducing the need to create translations between all individual assets. DECT/ ULE DECT/ ULE

11 11 27 assets already identified by the EC From E2BA and the eesemantics community: FIEMSER Data Model for Monitoring & control network ediana (ARTEMIS) ontology for device discovery and interoperability ENERsip M2M Communications Infrastructure Modelling Ontology SmartCoDe EUP classification with respect to energy management TIBUCON SEEMPubS Ontology SEIPF ontology DEHEMS Digital Environment Home Energy Management System project AIM* Ebbits SESAME Demonstrator LinkSmart ontologies Adapt4EE MIRABEL Flex eesemantics EupP VoCamP Hydra From CECED, EDI-SERVICE, EDI-WHITE, IRIS PI From Lighting Europe CEN/TC 169 CIE Newsletter International Lighting Vocabulary buidlingsmart s Industry Foundation Classes (IFC) FIPA Semantic Sensor Network Ontology (SSN) CEN/CLC/ETSI Smart Grid CG M490 BACnet, KNX, LonWorks, and assets produced by Eu.bac and various CENELEC TCs obix SensorML

12 12 21 additional assets identified during project ECHONET Broadband Forum HGI OSGi UPnP Agora FAN DomoML-env OpenIoT ZigBee Home Automation ZigBee Light Link OMA Lightweight M2M DECT ULE SEP2 (Zigbee, HomePlug, Wi-Fi) Z-wave Enocean DLMS/COSEM OMS IETF CoAP CENELEC-CEM, Technical Report IEC , Draft version Technical Standard of CLC TC205 WG18

13 13 13 Short list of most relevant models Model Reference URL DECT ULE HAN FUN ECHO NET HF-Overview, HF-Protocol, HF-Service, HF-Interface, HF-Profile, V1.00, ECHONET Specifications Appendix Detailed Requirements for ECHONET Device Objects Release C, 31 May ndixc_e.pdf ediana D2.2-A Ontology for Device Awareness, 30 November ness_m10_imsml.pdf EnOcean EP EnOcean Equipment Profiles (EEP), Version 2.6, 17 December FAN FPAI HEGRID AD1305 Interface description: Interface report, Version 1.0 (final), 7th January, FIEMSER D5 FIEMSER Data Model, February FIPA FIPA Device Ontology Specification, SC00091E, 3 December or KNX KNX System Specifications Interworking Datapoint Types, Version , 26 April 2012 MIRABEL D7.5 MIRABEL-ONE: Initial draft of the MIRABEL Standard, version1.0, 22 December 2011 OMA Lightweight Machine-to-Machine Technical Specification Candidate version 1.0, 10 December 2013 OMA Light weight M2M OMS Open Metering System Specification Vol.2 Primary Communication Issue 4.0.2, and OMS-Data Point List RELEASE A, Annex B to Volume 2: Primary Communication Issue 4.0.2, 27 January %20KNX%20Standard/KNX%20Standard%20Public%20Document s/03_07_02%20datapoint%20types%20v %20as.zip ocs/lightweightm2m/v1_ c/oma-ts-lightweightm2m- V1_ C.pdf Spec_Vol2_Primary_v402.pdf, OSGi DAL RFC-196 OSGi Alliance Device Abstraction Layer, Draft, February DeviceAbstractionLayer.pdf SEEMPubs Deliverable D5.1 Data Format Definition, version 1.0, 30 September PowerOnt Dario Bonino, Fulvio Corno, Faisal Razzak Enabling Machine Understandable Exchange of Energy Consumption Information in Smart Environments, Energy and Buildings 43 (2011) SEP2 Smart CoDE UPnP Zigbee Alliance / HomePlug Alliance Smart Energy Profile 2 Application Protocol Standard, ZigBee Public Document , April 2013 Deliverable D1.1.2 Model of local energy resource cluster, 31 December 2012 UPnP Device Architecture 1.1, SolarProtectionBlind:1, HVAC:1, Lighting Controls:1 Selected NOT on the basis of market relevance Energy20Standard.aspx W3C SSN Semantic Sensor Network Ontology, Z-Wave Z-Wave Technical Basics Chapter 4 Application Layer, 1 June Wave%20Technical%20Basics-small.pdf

14 14 14 Short listed assets are converted to OWL Work done by hand rather than automatically Only for the top classes Tools exist to convert XML to OWL and vv, but lots of details checking needs to be done afterwards Results can be found on Ontologies can be read with various tools, from simple web browsers, up to more advanced visualization tools such as Protégé (open source)

15 15 15 Core concepts of the Smart Appliances REFerence ontology (SAREF) Device Device category Sensor, Actuator, Meter, Load, storage, generator, Function Function category Service Has input and output parameter Command Time (Instant and Interval) Building Unit of Measure Property Energy, Power, Temperature, Commodity Electricity, gas, water, State Energy profile Smart Appliances Reference ontology available: and for documentation.

16 device service device cat. function cat. function command parameter mode/status energy profile energy power time/duration building sensor actuator meter load storage generator unit of measure 16 Initial mapping between assets and the core concepts of SAREF DECT ULE x x x x x x x x x x x PowerOnt x x x x x x x x ECHONET x x x x x x ediana x x x x x x x x EnOcean x x x x x x FAN FPAI x x x x x x x x x x x x FIEMSER x x x x x x x x FIPA x KNX x x x x x MIRABEL x x x x x x x x x OMA M2M x x x OMS x x x x x x OSGi DAL x x x x x x x x SEEMpubs x x x x x x x x SEP2 x x x x x x x x SmartCoDE x x x x x x UPnP x x x x x W3C SSN x x x x Z-Wave x x x x x x x

17 Smart Appliances REFerence ontology (SAREF) 17

18 18 And then SAREF well received by industry Especially telecom, white good, energy, and lighting industry Thanks to interactive bottom-up approach we took Studied and used by ETSI Smart M2M, OneM2M, and HGI Extend SAREF to more devices, services, and application areas e-health, home automation, e-security, multimedia, Create generic gold standard abstraction layer plus open source reference implementation based on business models and application scenarios obtained by continuous interaction with all relevant standardization bodies Create a lasting, dynamic Open and Agile Smart Homes (OASH) community of industry partners, policy makers, academia, and end users, driving and managing the platform innovation TNO is actively seeking for funding and partners to set up OASH

19 19 Resources EC Smart Appliances Project deliverables: SAREF: nce-ontology ETSI workshop presentations: