FEDER:ESP8266 Experimentation: Difference between revisions

From UNamur InfoSec
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
We have constructed a complete Wifi network with ESP8266 Huzzah micro-controller with different type of sensors such as: Temperature, movement, humidity, luminosity, vibration sensors. We have also developed the access control module to be used to control different devices (sensors) for different testing scenarios. Below is our functional smart home architecture:  
We have constructed a Wifi sensor network with ESP8266 Huzzah micro-controllers with different type of sensors such as: Temperature, movement, humidity, luminosity, vibration sensors. We have also developed the access control module to be used to control different devices (sensors) for different testing scenarios. The scenarios are connected to smart home system environment, which is built based on our defined smart home system architecture shown below. It is the functional smart home architecture:  
[[File:IoT_SH_F_architecture.png]]
[[File:IoT_SH_F_architecture.png]]



Revision as of 07:39, 4 March 2017

We have constructed a Wifi sensor network with ESP8266 Huzzah micro-controllers with different type of sensors such as: Temperature, movement, humidity, luminosity, vibration sensors. We have also developed the access control module to be used to control different devices (sensors) for different testing scenarios. The scenarios are connected to smart home system environment, which is built based on our defined smart home system architecture shown below. It is the functional smart home architecture: IoT SH F architecture.png

1. Device controller is responsible for controlling all the sensors and actuators installed the network. Context-handler is responsible for forming/constructing the request query for access control engine. The structure of query depends on the access control engine used and language supported by the engine. For example, XACML engine (https://en.wikipedia.org/wiki/XACML) uses XML language to express the access query and access control policies.

2. Access controller engine is responsible for validating access control policies based on the request from device controller. It is worth noting that in our proposed architecture, multiple access control engine can be used in a network.

3. MQTT Broker is a MQTT server allowing devices (other system components) to publish or subscribe for information.

4. End-Devices are the sensors or actuators installed in the network. Those devices can act as subscriber or publisher.

5. Request-entities are the medium for accessing/controlling/interacting with the system such as, web-app or app-smart-devices.

I. Implementation description

II..Scenarios

III.Technologies used

IV. Performance analysis and observation