IoT access protocol-MQTT

fish001

IoT access protocol-MQTT [Copy link]

MQTT (Message Queuing Telemetry Transport) is an instant messaging protocol developed by IBM that has the potential to become an important part of the Internet of Things. In fact, most current IoT access services will support the MQTT protocol as standard. MQTT is a publish/subscribe protocol. Compared with other protocols such as HTTP, it is very simple and lightweight, designed for restrictive devices and low-traffic, narrow bandwidth (unreliable networks), and low-latency scenarios. MQTT is designed to use minimal bandwidth and computing resources, and to ensure certain reliability and varying degrees of quality assurance. MQTT caters to the needs of M2M and IOT, especially in the case of mobile networks, where traffic is relatively expensive and battery-powered scenarios. MQTT was created in 1999 by Dr. Andy Stanford-Clark of IBM and Arlen Nipper of Arcom (now Eurotech). Since 1999, the MQTT protocol has been used in many fields. OASIS, the organization for the advancement of structured information standards, has announced MQTT (Message Queuing Telemetry Transport) as the preferred standard for the emerging Internet of Things messaging protocol. The protocol specification has been publicly available for many years under a royalty-free license, and Eurotech (formerly ARCOM) has implemented the MQTT protocol in its products. IBM has announced its participation in the Eclipse M2M industry working group and the donation of MQTT code to the Eclipse Paho project. Both the "SCADA protocol" and the "MQ Integrator SCADA Device Protocol" (mqisdp) are old names for what is now called the MQ Telemetry Transport Protocol (MQTT). The protocol was also known as "WebSphere MQTT" (wmqtt), although this name is no longer used. Now most MQ middleware supports MQTT protocol, but the middleware on the market are general products, which are not optimized for the characteristics of IoT. IoT has relatively high requirements for access. Since the amount of data of access devices can be very large, there can be various access types, and the frequency of data upload will be relatively intensive, it puts forward relatively high requirements for device access. Many IoT service providers will conduct secondary development of middleware products to meet their own needs. Capable enterprises can re-implement MQTT protocol to meet higher requirements.