InitRech 2015/2016, sujet 24

De Wiki d'activités IMA
Révision datée du 17 juin 2016 à 19:50 par Acuadros (discussion | contributions) (Page créée avec « = Summary = <br>This article is talking about Integrating wireless sensor networks with the web. <br>The paper describes the design and development of an end-to-end IP base... »)
(diff) ← Version précédente | Voir la version actuelle (diff) | Version suivante → (diff)

Summary


This article is talking about Integrating wireless sensor networks with the web.


The paper describes the design and development of an end-to-end IP based architecture integrating a Constrained Application Protocol (CoAP) over 6LowPAN Contiki based Wireless Sensor Network (WSN) with an HTTP over IP based application and showing the benefits of COAP compared to HTTP. The idee is to allow a user to access WSN data simply from a Web browser.


The Authors introduces first the subject, the use of the Internet Protocol in resource constrained devices has radically changed the Internet landscape and the number of connected object is increasingly growing.
Then, they explain some new standards like 6LoWPAN , RPL, the terms WOT and M2M and the architectures REST to show the major benefits and advantages of this one’s. The article show different works which propose differents architectures and after this, they will present their work concerning a RESTful WSN based on CoAP.


Firstly, it describes the major difference between CoAP and HTTP and compares the two protocols in terms of power consumption and overhead.


Secondly, the paper describes the design and development of an end-to-end IP based architecture integrating a CoAP over 6LowPAN Contiki based WSN with an HTTP over IP based application.


After an explanation of the a RESTful WSN based on CoAP, the paper describes the major functionalities of CoAP highlighting the differences with HTTP.


Then, they explains the results of an experiment illustrating the benefit of CoAP in terms of power consumption compared to HTTP.


Finally, We can see that CoAP offers the same methods for the resource manipulation as HTTP but supports additional functionalities typical of IoT and M2M applications, such as multicast, asynchronous communication and subscriptions. The gateway is still in prototype phase and it requires the development of proxy and observation functionalities. Nearly, the application will be deployed and tested in a greenhouse monitoring testbed.