Hybrid NarrowBand-internet of things protocol for real time data optimization

The level of dependence on data communication in the modern era is increasing exponentially. The internet of things (IoT) plays a very important role in the advancement of the industrial revolution 4.0 that utilizes data communication systems. IoT deployments require data communication protocols, such as hypertext transfer protocol (HTTP), and message queuing telemetry transport (MQTT) as well as network communication protocols (wireless) to meet the network needs of devices with limited resources. Optimization of data communication in IoT is needed to maintain the quality of sending and receiving data in real time. This research proposes a hybrid NarrowBand-IoT (NB-IoT) protocol designed using NarrowBand communication network technology with optimization of data communication using MQTT and HTTP protocols. In this research, the hybrid NB-IoT protocol has the best packet loss value of 0.010% against the HTTP NB-IoT protocol which has a value of 0.017%, and the MQTT NB-IoT protocol of 0.024%. The hybrid NB-IoT protocol has a latency value of 8.7 seconds compared to the HTTP NB-IoT protocol which has a latency of 10.9 seconds. Meanwhile, the throughput value of the hybrid NB-IoT protocol is 158906.1 byte/s and is better than the MQTT NB-IoT protocol which is only 158898.6 bytes/s

Enabling seamless communication over several IoT messaging protocols in OpenFlow network

The most prominent protocols for data transfer in internet of things (IoT) are message queuing telemetry transport (MQTT) and constrained application protocol (CoAP). The existing clients from both sides are unable to communicate directly because of the packet’s header structure difference in application and transport layer. In response, this paper aims to develop a bidirectional conversion server used to translate the specified messaging protocol interchangeably in the OpenFlow network and transmit the converted packet from both sides. The conversion server integrated the MQTT subscriber and CoAP POST object for converting the MQTT message into CoAP data. Similarly, the CoAP-MQTT translation was processed by CoAP GET and MQTT publisher object. The research was evaluated by analysing the round trip time (RTT) value, conversion delay, and power consumption. The RTT value for MQTT-CoAP required 0.5 s while the CoAP-MQTT was accumulated in 0.1 s for single-packet transmission. In addition, the SDN controller and the conversion server only consumed less than 1% central processing unit (CPU) usage during the experiment. The result indicated that the proposed conversion server could handle the translation even though there was an overwhelming request from the clients

Enabling seamless communication over several IoT messaging protocols in OpenFlow network

The most prominent protocols for data transfer in internet of things (IoT) are message queuing telemetry transport (MQTT) and constrained application protocol (CoAP). The existing clients from both sides are unable to communicate directly because of the packet’s header structure difference in application and transport layer. In response, this paper aims to develop a bidirectional conversion server used to translate the specified messaging protocol interchangeably in the OpenFlow network and transmit the converted packet from both sides. The conversion server integrated the MQTT subscriber and CoAP POST object for converting the MQTT message into CoAP data. Similarly, the CoAP-MQTT translation was processed by CoAP GET and MQTT publisher object. The research was evaluated by analysing the round trip time (RTT) value, conversion delay, and power consumption. The RTT value for MQTT-CoAP required 0.5 swhile the CoAP-MQTT was accumulated in 0.1 s for single-packet transmission. In addition, the SDN controller and the conversion server only consumed less than 1% central processing unit (CPU) usage during the experiment. The result indicated that the proposed conversion server could handle the translation even though there was an overwhelming request from the clients