FIRE Federation HOBNET – SmartSantander

1. FIRE FederationHOBNET – SmartSantander Dr Srdjan Krčo Toma Dimčić Stevan Jokić

2. Introduction HOBNET FIRE platform focused on automation and energy efficiency for smart/green buildings 3 sites: CTI Patras, Uni of Geneva and MI building Built for researchers MI site will enable end-users to try out some of the services SmartSantander provides experimental research facility in support of typical applications and services for a smart city 4 sites Santander, Lubeck, Guilford, Pancevo Built for researchers, service providers, users (citizens, city governments)

3. Two domains Application and Building Two RDs Two types of interfaces Embedded Building Interface (EBI) level Open Building Interface (OBI) level Overall HOBNET Architecture

4. Main components • EBI RD • Resource descriptions registered at the EBI RD • Describe physical nodes, their capabilities and their associated building resources • OBI RD • Enables interaction between end users and system • Resource descriptions registered at the OBI RD • Describes building, it’s capabilities and applications (virtual resources ) • BWSP • Provides connection between OBI and EBI domains and their RD’s • Responsible for • Registering appropriate building domain resources in the application domain, • Proxying and caching resource requests • Providing services such as a location service or maintaining a database

5. Protocol and format • On the application layer CoAP protocol is used • Interfaces: discovery: GET coap://XXXX/.well-known/core?rt=core-rd registration: POST coap://XXXX/rd?n=group1&lt=1024 update: PUT /rd/group1 "</node1..." removal: DELETE /rd/group1 lookup: GET /rd?rt=Temperature • CoRE Link Format isused for node descriptions Example: </sensors>;rt="index";title="SensorIndex", </sensors/temp>;rt="TemperatureC";if="sensor",</virtualResources/averageTemp>;rt=“AverageTemerature";if="virtualResource",<http://www.example.com/sensors/t123>;anchor="/sensors/temp";rel="describedby“, </t>;anchor="/sensors/temp";rel="alternate"

6. Typical interactions of HOBNET entities

7. Authentication, Authorisation and Accounting (AAA) Subsystem Testbed management subsystem Experimental support subsystem Application support subsystem Overall SmartSantander Architecture

8. Format Resource descriptions are described in XML format Example: <!--?xml version="1.0" encoding="UTF-8"?--><resource-description> <resource-id>urn:smartsantander:testbed:0x0050</resource-id> <tag><![CDATA[node_rtype # SENSOR_NODE]]></tag> <tag><![CDATA[parent_id # testbed-campusGW.smartsantander.eu]]></tag> <tag><![CDATA[digi_mac_addr # 0x0013A200406F6118]]></tag> <tag><![CDATA[experiment_mac_addr # 0x0013A200406F607C]]></tag> <tag><![CDATA[position # phenomenon:latitude;43.47177;phenomenon:longitude;-3.80055;]]></tag> <tag><![CDATA[node_type # waspmote]]></tag> <tag><![CDATA[node_port # /dev/ttyTestbedRuntime]]></tag> <tag><![CDATA[application_name # WSNDeviceApp]]></tag> <tag><![CDATA[factory_class # de.uniluebeck.itm.tr.runtime.wsnapp.WSNDeviceAppFactory]]></tag> <tag><![CDATA[capability # phenomenon:temperature;uom:celsius;type:float]]></tag> <tag><![CDATA[capability # phenomenon:luminousFlux;uom:lumen;type:integer]]></tag> <rai-description> <rai-id>0</rai-id> <rep-locator>http://something.com</rep-locator> </rai-description></resource-description>

9. Interactions RD InteractionTo retrieve the Resource description of a particular node:http://RD_IP_addr:RD_PORT/rd/rd/id/node_id To retrieve the Resource descriptions of all the nodes under the same GW (i.e. logicalHub):http://RD_IP_addr:RD_PORT/rd/rli?tag=parent_id%20%23%20parent_id&l=10 To retrieve the Resource descriptions of all nodes with temperature capability (for example): http://RD_IP_addr:RD_PORT/rd/rli?tag=capability%20%23%20phenomenon: temperature;uom:celsius;type:float;&l=100

10. How we can combine the two frameworks?

11. Federation Scenario #1 • Make data from HOBNET sites available through SmartSantander framework • HOBNET nodes generate data that can be used by services that run on top of SmartSantander framework • Execution of experiments not possible on HOBNET nodes • HOBNET resources • Service-only nodes from SmartSantander point of view • Resource descriptions of the physical nodes (EBI resources) are registered in SmartSantander RD • Data available through SmartSantander framework

12. FederationScenario #2 • Make it possible to deploy and run experiments on HOBNET nodes through SmartSantander framework • Data generated by HOBNET nodes available through SmartSantander framework • Execution of experiments on HOBNET nodes possible • Authentication of users through SmartSantander framework • Resource descriptions of the physical nodes (EBI resources) and applications (OBI resources) are registered at SmartSantander RD • HOBNET data and virtual resources available through SmartSantander framework • The experimenters could reprogram nodes by writing their own virtual resources and registered them

13. Mapping of components

14. Federation – architecture model

15. The main ISSUE • Resource descriptions are different • Semantics has to be agreed • RDs do not support all formats

16. Potential way forward • SQL as the underlying database not the most suitable • More flexible RD architecture required. supporting various descriptions, formats • Mongo DB • Not a relational database • Relies on collections (tables in the relational databases) • Resource Directory with Mongo DB supports • HTTP and CoAP protocols • serialization of XML and CoRE Link data formats

17. Potential way forward • Mongo DB based RD • Resource Description Collection • Subscriptions • Resources matching the subscriptions • Notifications • Extensible Resource Description serialization

18. Federation – interaction model

19. Thanks. srdjan.krco@ericsson.com