European Standardization. CLC TC205 - Home Electronics Systems and the IoT EN Joost Demarest - KNX Association.

Transcription

1 European Standardization CLC TC205 - Home Electronics Systems and the IoT EN Joost Demarest - KNX Association

2 Overall Agenda CLC TC205 HBES and the IoT HBES KNX Web Services Current HBES Standardization Landscape Internet of Things: what is it? HBES: is it already part of the Internet of Things? Home automation: a changing landscape HBES and the Internet how is it solved today - disadvantages HBES and the Internet aims of the HBES Web Service (EN ) Project target groups and use cases HBES Web Services technical solution HBES Web Services what will be offered? HBES Web Services the complete technical picture! Page No. 2

3 European Home Automation Standardization (1) CENELEC (1) European Committee for Electro-technical Standardization Responsible committee = Technical Committee (TC) 205 Scope: Home and Building Electronic Systems Standard series for home and building control = EN KNX Association Partner Organization to CENELEC = important player in the field of home and building control Possibility to submit standardization proposals without need for New Work Item proposal by national committees Before 2003: EN Only existing part of EN series documenting hardware requirements EMC, Electrical Safety, Environmental conditions System independent Page No. 3

4 European Home Automation Standardization (2) CENELEC (2) Since 2003: approval of European TC 205 national mirror committees of KNX media (TP, PL, RF) KNX protocol (LL, NL, TL, A(I)L) Management procedures KNX Interworking model and KNX standardized data types All part of the EN series Since 2010: Out-phasing of EN Replacing by new standard series EN EN becomes fully KNX EN collects hardware requirements for any HBES solution, even systems that are not EN compliant IEC SC23 new working group: internationalization of EN to IEC standard IEC : product standard for HBES electronic switches Page No. 4

5 The Internet of Things: Definition Internet of Things: Definition According Wikipedia Network of physical objects or things embedded with electronics, software, sensors and network connectivity Objects able to collect and exchange data Enabling connection between physical world and computer based systems Each thing uniquely identifiable Each thing able to interoperate with internet infrastructure 2020: 50 billion such objects Page No. 5

6 The Internet of Things: Is HBES part of it? IP Router TP Area End Device TP Line IP Backbone Line Coupler IP Router TP Area Media Coupler End Device Is HBES not already long part of the IoT? Since more than 10 years, EN allows to integrate HBES into IP based networks Already since then, there is a HBES of Things compare previous definition Wikipedia Physical objects HBES devices Network connectivity TP, RF, PL, IP Collect and exchange data group objects/interface objects properties Connection between devices and computers HBES data interfaces Each thing uniquely identifiable HBES serial number and/or individual address Each thing able to interoperate with internet HBES IP routers Page No. 6

7 A changing Home automation landscape Page No. 7

8 Current trends USB receiver per system Engineered links GW per product/system Current trend: APIs Reunite different home automation solutions via a unified interface In a central device in the installation In your Smart Phone In the Cloud Drawbacks of these solutions compared to HBES Increased complexity of the installation No proven reliability of these solutions (yet) Central device is weak spot in these concepts But: Data is power! Information on the user profiles of the smart thermostat could provide business opportunities Offering of additional services data mining But: there is no strict need to be able to access every single data element in a home/building (e.g. occupancy mode) Page No. 8

9 Today: App on Mobile platform accesses HBES installation A)HBES IP Frame BC D0 E IP router B) Manufacturer specific IP Frame format IP client IP Gateway BC D0 E Possible implementations A) App talks directly HBES by integrating the HBES telegram into IP frames sent from the IP Client (e.g. with installed App) via the HBES/IP router to the desired HBES end device B) IP client talks manufacturer specific IP Frame format to manufacturer specific IP Gateway: this converts proprietary format into HBES frame to the desired HBES end device Drawbacks Every IP client has to support HBES/ IP or is specific to the used IP Gateway No standardization HBES installations are seen as Fort Knox by IT experts as HBES protocol unknown to them complicated integration of HBES and other protocols Page No. 9

10 HBES Web Services, Intention Create a possibility that IT systems and HBES networks can be interlinked by means of a HBES Gateway. Skill Factor HBES terminology like GAs or GOs are unknown to a person unfamiliar with HBES Integration Factor How easy can an IT expert integrate an HBES based system in an(y) IT infrastructure? By default such Gateways are interesting for two target groups. Web Client developers Defined interface to implement Web Clients Gateway manufacturers Provide the Web Client developers with a common and standardized interface Development and sales of gateways Page No. 10

11 HBES Web Services, Use Cases The Web Service gateway should be able to answer questions like: Question directed to the HBES system only Give me the room temperature of the meeting room on the ground floor Temperate value Which rooms are currently occupied by someone, in which the temperature is lower than 20? Combination of presence and temperate value Question to the entire Building Automation System Give me all apartments in my hotel that are currently rented out? Occupancy value in addition to the room information post processed (value not available in HBES ) Where are the MCBs assembled in wiring schema (geographically) located (which room/ floor)? Combination of room/ floor and MCB position Page No. 11

12 With HBES Web Services: App on Mobile platform accesses HBES installation GET all%20devices/.../temperature%20controller / datapoints/temperature%20value/d%2d01/ RESTful Web Services IP router Web client KNX Web Service Gateway Implementation Web Client (e.g. with installed App) browses data held by the Web Service Gateway by using common web services The Web services do not embed the HBES protocol Data in the Web Service Gateway only reflects the statuses of the devices inside the connected HBES network Is modelled according obix, OPC UA or BACnet WS Can be exported by configuration tool based on the project data represented according a standardized (tagged) HBES information model non HBES data could even be modelled according to it (e.g. localization info of project devices) Gateway can be realized on simple Raspberry PI Advantages The web client realization is much more versatile, it must only adapt to the information modelling supported by the web server (obix, OPC UA or BACnet WS) Software for the realization of web clients for OBIX, OPC UA or BACnet WS readily available Very simple integration of HBES with other protocols Data could even be googled in the gateway through support of query language by web client and web service gateway Page No. 12

13 HBES Web Services, Technology Concept of EN Page No. 13

14 Detailed technical presentation Interface 6: HBES Information model Entity = something you know from HBES: a device, a Line, a Datapoint, a manufacturer Tag = An entity can have multiple tags, to tell more about the entity. A tag can be: a marker: to tell what the entity is EXAMPLE This entity is an installation. This entity is a Group Object a tag/value pair: to give a specific name or identifier to an entity EXAMPLE name= Light Switching Actuator a reference: to refer to another entity EXAMPLE name= Light Switching Actuator Page No. 14

15 Detailed Technical presentation Interface 6: HBES Information model: animated example. These are entities: a device, a buildingpartfloor, a Room, a Manufacturer Page No. 15

16 Detailed technical presentation Interface 6: HBES Information model: animated example. These are tags: device, name=, order number=, datapoint... Some say what the entity is: device, datapoint = Marker tags Some have a value: physical address= = Tag/Value pairs Some refer to another entity = Reference tags 80 tags are defined so far Page No. 16

17 Detailed technical presentation Interface 6: KNX Information model It is the task of the HBES gateway to present the HBES information model in the way as required by the web service technology (obix, OPC UA, BACnet/WS). The Information Model of a project will be loaded in the gateway, as an XML file. The way how this is done, can vary (over IP, memory card ). Advantages More easy to extend than an Object Model (classes, attributes). Allows presenting the installation in other ways than the classic Topology, Group Address View, etc. Own views are possible. Allows including devices and data ( additional data ) that do not come from the installation, in one common way! Tags and entities follow a meta-model (not explained here) to allow extensions of this model, which can automatically be interpreted by the gateway. Allows hiding the specificities. HBES specific features (Individual Address, Line, Group Object ) are available, but are not necessary to use the model. Independent of the gateway technology (obix, OPC UA, BACnet/WS). One file format Page No. 17

18 Detailed technical presentation Interface 8: obix the web interface Everything is modelled as a small object. New object types are defined through contracts. EXAMPLE Reading a device description GET The gateway responds as follows <obj name="temperature_controller" is="/knx/device" displayname="temperature controller" href="/installations/demo/views/view_devices/.../temperature_controller/"> <int name="physicaladdress" href="physicaladdress" val="43"/> <str name="ordernumber" href="ordernumber" val=" "/> <str name="serialnumber" href="serialnumber" val="sn "/> <ref name="manufacturer" href="manufacturer_gmbh" is="/knx/manufacturer"/> <list name="datapoints" href="datapoints" of="obix:ref /knx/datapoint"> <ref name="temperature_value" href="datapoints/temperature_value" displayname="temperature value" is="/knx/dpst_9_001 /knx/datapoint"/> </list> </obj> Also this is transferred using http. Page No. 18

19 Detailed technical explanation Interface 8: obix the web interface The value of the temperature can finally be read as follows. GET /temperature_controller/datapoints/temperature_value/ The gateway reads the value of the Group Object in the installation, and responds as follows. <obj name="temperature_value" is="/knx/dpst_9_001 /knx/datapoint" href="/installations/demo/views/view_devices/.../datapoints/temperature_value/" displayname="temperature value"> <real name="temperature" href="temperature" displayname="temperature" val="23.4" This example uses XML. min="-273.0" max=" " unit="/units/celsius"/> Note that JSON, EXI and </obj> CBOR are possible as well. I thought the gateway would not expose HBES specific things? True. This is just a contract definition, saying that the data has been converted from a type that is not known in obix (HBES F 16 ). And the gateway returns a readable value! Page No. 19

20 Thank you for your attention! For more information Joost Demarest KNX Association cvba Tel: joost.demarest@knx.org Web: