1 / 8

GWS 2014 – Aalborg

GWS 2014 – Aalborg. BETaaS Training Session. Building the Environment for the Things as a Service. Training Content. Using the BETaaS platform to:. From Laptop. Access sensors data. From Mobile Phone. Create a network of BETaaS gateways. Run applications to access the BETaaS platform.

pascal
Download Presentation

GWS 2014 – Aalborg

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GWS 2014 – Aalborg BETaaS Training Session Building the Environment forthe Things as a Service

  2. Training Content • Using the BETaaS platform to: • From Laptop • Access sensors data • From Mobile Phone • Create a network of BETaaS gateways • Run applications to access the BETaaS platform

  3. Components Deployment GW3 Laptop Ethernet connection GW1 GW2 Laptop Laptop USB connection USB connection Ethernet connection Ethernet connection Switch Zigbee Coordinator Zigbee Coordinator ZigBee ZigBee ZigBee End Device End Device End Device Arduino Arduino Arduino Presence Infrared Sensor Presence Infrared Sensor Presence Infrared Sensor

  4. Development Tools • Karaf • Maven BETaaS • Tomcat External Components (for Training) • Arduino • Android

  5. Presence Detection • 2 BETaaS GWs placed one on each floor • 1 external BETaaS GW • Each GW manages its own PIRs connected through ZigBee • Sensors send context info to GWs • The first GW creates the BETaaS Instance • Second and third GWs join the Instance • The instance is visible as a single platform sharing all available resources

  6. Resources Allocation • When sensors are recognized: • Things Services are created based on context info (data type, location, etc) • Big Data Manager starts storing incoming data • The application requests resources allocation through a manifest file specifying: • Semantic request (e.g. “presence” at “home”) • Credentials • QoS specifications • Type of Service (push/pull, real time, etc)

  7. Application Execution • Once installed, the application requests data (home presence) through SOAP interfaces • BETaaS selects the relevant Thing Services currently available, also considering equivalence and workload • Results from Thing Services are combined and sent to the application

  8. References • BETaaS - http://www.betaas.eu/ • Karaf - http://karaf.apache.org/ • Arduino XBee - http://arduino.cc/en/Main/ArduinoXbeeShield • Distributed OSGi - http://cxf.apache.org/dosgi-releases.html

More Related