Abstract
The IoT protocols used for data transfer in the application layer, namely the Constraint Application Protocol (CoAP) and Message Queue Telemetry Transport (MQTT) have dependencies to the transport layer. The choice of transport, Transmission Control Protocol (TCP) or the User Datagram Protocol (UDP), on the other hand, has an impact on the Internet of Things (IoT) application level performance, especially over a wireless medium. Furthermore, we touch upon the impact of different security solutions. The motivation of this work is to look at the impact of the protocol stack on performance over a narrowband IoT (NB-IoT) link. The use case studied is infrequent small reports sent from the sensor device to a central cloud storage over a last mile radio access link. We find that while CoAP/UDP based transport performs consistently better both in terms of latency, coverage, and system capacity, MQTT/TCP also works when the system is less loaded.
Highlights
The core idea of the Internet of Things (IoT) is to use the Internet Protocol (IP), mainly IPv6, to communicate between connected devices and services in the cloud
We focus on the low power wide area technologies and especially to cellular network links realized with the narrowband IoT (NB-IoT) technology
LoRa differ from NB-IoT in that they run over the unlicensed spectrum while NB-IoT runs over licensed spectrum
Summary
The core idea of the Internet of Things (IoT) is to use the Internet Protocol (IP), mainly IPv6, to communicate between connected devices and services in the cloud. If the use case involves collecting large amounts of sensor data for statistical purposes, and the traffic is mostly from the sensor to the cloud, it may be acceptable to lose occasional packets. Even in such scenarios, reliable transport may be required on occasion when firmware updates or security patches are done on devices. LoRa differ from NB-IoT in that they run over the unlicensed spectrum while NB-IoT runs over licensed spectrum Both technologies have an optimized last hop where the use of TCP, or even IP, is not common.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.