Abstract
Recently, researchers are focusing on a new use of the Internet called the Internet of Things (IoT), in which enabled electronic devices can be remotely accessed over the Internet. As the realization of IoT concept is still in its early stages, manufacturers of Internet-connected devices and IoT web service providers are defining their proprietary protocols based on their targeted applications. Consequently, IoT becomes heterogeneous in terms of hardware capabilities and communication protocols. Addressing these heterogeneities by following open standards is a necessary step to communicate with various IoT devices. In this research, we assess the feasibility of applying existing open standards on resource-constrained IoT devices. The standard protocols developed in this research are OGC PUCK over Bluetooth, TinySOS, SOS over CoAP, and OGC SensorThings API. We believe that by hosting open standard protocols on IoT devices, not only do the devices become self-describable, self-contained, and interoperable, but innovative applications can also be easily developed with standardized interfaces. In addition, we use memory consumption, request message size, response message size, and response latency to benchmark the efficiency of the implemented protocols. In all, this research presents and evaluates standard-based solutions to better understand the feasibility of applying existing standards to the IoT vision.
Highlights
IntroductionEach sensor becomes self-describable and self-contained by providing web interfaces for applications to retrieve sensor’s capabilities
By using the resource-constrained and cost-effective nodes, we can explore the lowest boundaries of the resources that are required for Internet of Things (IoT) applications
After looking at the responses generated by Open Geospatial Consortium (OGC) SensorThings data service, we identified several JSON attribute-value pairs that were repeated in all sensor readings
Summary
Each sensor becomes self-describable and self-contained by providing web interfaces for applications to retrieve sensor’s capabilities It means the device does not depend on other network nodes (e.g., hosts) to publish its data or to receive requests. In order to achieve the interoperability between sensors and applications, one solution is to using standard-based web service interfaces and widely-used data encodings in information communication. We clearly demonstrated that the existing protocols of Sensor Web and WSNs can be implemented on resource-constrained IoT devices Whilst these efforts are moving the Internet of Things toward greater interoperability, they do not fit well with the processing load of IoT devices or their interconnection with other Internet nodes. Since the SensorThings API is slightly different from the REST principles in terms of URI definition, we call it “REST-like”
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have