Rest-based sensor networks with OData

Abstract

RESTful services gained a lot of attention recently, even in the enterprise world, which is traditionally more webservice centric. Data centric RESfFul services, as previously mainly known in web environments, established themselves as a second paradigm complementing functional WSDL-based SOA. In the Internet of Things, and in particular when talking about sensor motes, the Constraint Application Protocol (CoAP) is currently in the focus of both research and industry. In the enterprise world a protocol called OData (Open Data Protocol) is becoming the future RESTful data access standard. To integrate sensor motes seamlessly into enterprise networks, an embedded OData implementation on top of CoAP is desirable, not requiring an intermediary gateway device. In this paper we introduce and evaluate an embedded OData implementation. We evaluate the OData protocol in terms of performance and energy consumption, considering different data encodings, and compare it to a pure CoAP implementation. We were able to demonstrate that the additional resources needed for an OData/JSON implementation are reasonable when aiming for enterprise interoperability, where OData is suggested to solve both the semantic and technical interoperability problems we have today when connecting systems.

Internet of Things - a study on the security challenges

“…Among the various models proposed on loT by various researchers, Semantic middleware and Service Oriented Architecture (SOA) [4] oriented middleware seem to be the most popular. The Semantic middleware based technologies are based on the Extensible Markup Language (XML) metadata exchange [6] for interoperability while the SOA and Representational State Transfer (REST) based [7] systems are more popular in the enterprise environment because of the advantage that it offers is that, it addresses both semantic and technical interoperability problems.…”

Software Defined Unified Device Management for Smart Environments

“…Matching adapters can be sequenced to handle the CoAP interactions non-intrusively providing security and other services which otherwise can strain the devices. An embedded OData implementation on top of CoAP without requiring an intermediary gateway device is presented in [14]. Additional resources required for an OData/JSON implementation are justified considering the issues in interoperability in enterprise networks.…”