HTTP-CoAP cross protocol proxy: an implementation viewpoint

Automated synthesis of mediators for middleware-layer protocol interoperability in the IoT

“…By extending QEST, Ponte [14], which is developed as part of the Eclipse IoT open source community [82], provides APIs to application developers that enable automatic conversion between REST, CoAP and MQTT protocols. Similar gateways exist in the literature providing a cross-protocol proxy, such as in [83] for HTTP-CoAP interoperability and in [70] for DPWS-REST interoperability. Other Eclipse IoT projects proposing IoT gateways are Kura [84], NeoSCADA [85], and SmartHome [86].…”

eWoT: A Semantic Interoperability Approach for Heterogeneous IoT Ecosystems Based on the Web of Things

“…There are many proposals addressing the challenges associated with semantic interoperability. However, it is important to distinguish between: (a) those proposals that implement semantic interoperability for just one specific IoT device [16][17][18][19][20][21][22][23][24][25][26][27][28], and (b) those that aim at implementing a semantically interoperable IoT ecosystem in which transparent mechanisms to interact with the IoT devices within are provided [8,[29][30][31][32][33][34][35].…”

“…Proposals [16][17][18][19][20][21][22][23][24][25][26][27][28] -Guinard et al [29] Text Indexing Wei and Jin [30] Centralised Cassar et al [31] Centralised Gyrard and Serrano [8,34] Federation Zarko et al [35] Federation eWoT Decentralised…”

GoThings - An Application-layer Gateway Architecture for the Internet of Things

“…Our proposal is directly related with the WoT Smart Gateway, but it is not limited to a REST-like interface. (Castellani et al, 2012) discuss about problems and solutions in mapping between HTTP and CoAP protocols regarding the implementation of a cross proxy between these protocols. This kind of proxy can transparently interconnect protocols maintaining most of semantics, but it has the drawbacks of being locked to only two and limited to very closer protocols.…”