Protocols play real role in IoT communication

The IoT envisions hundreds or thousands of end-devices with sensing, actuating, processing, and communication capabilities able to be connected to the Internet. These devices can be directly connected using cellular technologies such as 2G/3G/Long Term Evolution and beyond (5G) or they can be connected through a gateway, forming a local area network, to get connection to the Internet.

The latter is the case where the end-devices usually form Machine to Machine (M2M) networks using various radio technologies, such as Zigbee (based on the IEEE 802.15.4 Standard), Wi-Fi (based on
the IEEE 802.11 Standard), 6LowPAN over Zigbee (IPv6 over Low Power Personal Area Regardless the specific wireless technology used to deploy the M2M network, all the end-devices should make their data available to the Internet. This can be achieved either by sending the information to a proprietary web server accessible from the Internet or by employing the cloud.

#The role of protocols in IoT

Online platforms such as ThingSpeak.com or Open.Sen.se, among any other alternatives, are virtual clouds able to receive, store, and process data. Besides acting as remote data bases, M2M clouds also offer the following key services:

1. They offer Application Programming Interfaces (API) with built-in functions for end-users, thus providing the option to monitor and control end-devices remotely from a client device.

2. They act as asynchronous intermediate nodes between the end-devices and final applications running on devices such as smart phones, tablets or desktops. Our paper focuses on the protocols that handle the communication between the gateways, the public Internet, and the final applications (Figure 1). They are application layer protocols that are used to update online servers with the latest end-device values but also to carry commands from applications to the end-device actuators.