Simulation of MQTT Communication in NS-3

These days message queuing telemetry protocol (MQTT) has become widespread to be used in the digital transformation of the manufacturing industry. Smart factory, Cyber-Physical Systems, and Industry 4.0 are all different initiatives but depends heavily on one common thing i.e. a large number of sensors and devices. Analysts have a strong belief that a global share of IoT will account for billions of dollars. It doesn’t matter whether the interaction in these devices will take place among sensors, motors, controllers, or HMIs, they all will be needing to be connected across hundreds or even thousands of users via PLCs, SCADA, OEMs, or third-party reliability services. Just having data from this plethora of sources isn’t enough but a timely consumption of this data matters profoundly. This is where MQTT came into place. Current communication in the industry is right now dependent on various communication protocols that are not really flexible and scalable to account for new data-driven scenarios. In opposition, MQTT is based on a machine to machine communication in smart industries. Its focused network architecture and minimally weighted payload specification make it the right fit as far as flexibility and scalability are concerned for reconfigurable factories. Thus making it a right paradigm suitable for manufacturing. MQTT in this sense is replacing the industrial complexity of point-to-point communication via a broker. Thus, taking care of agile connections. As many experts in industries have highlighted that decoupled integration of nodes/devices is the solution to complex industries and MQTT allows this decoupling mechanism better than any other commutation protocol. MQTT is widely acceptable for dynamic industrial operations where subscribers can subscribe to any telemetry for varying analytics. As all the ups of MQTT have been discussed we will carry out its simulation in ns-3