Explore chapters and articles related to this topic
IoT End Devices
Published in Rebecca Lee Hammons, Ronald J. Kovac, Fundamentals of Internet of Things for Non-Engineers, 2019
To control and manage the stream of information coming from sensors and going to actuators, there are messaging protocols. These messaging protocols control the pace of information flow, the syntax of the flow, and generally manage and provide structure to all the information flow there is for the IoT world. There are many types of messaging protocols for sensors and actuators, and here, we will introduce you to a few of the common ones found these days. These protocols guide the information flow from the sensors. MQTT—Message Queuing Telemetry Transport is an ISO Standard. It works on top of the TCP/IP protocol and is often used for remote connections that do not have a lot of information (such as a temperature probe). Therefore, it requires limited network bandwidth which is appreciated. Facebook Messenger used MQTT. https://en.wikipedia.org/wiki/MQTTAdvanced Message Queuing Protocol (AmQP)—creates a standard of interoperability between various pieces, parts, and systems. It is open standard based and has a high degree of reliability and security. This is often used to connect servers to servers.Extensible Messaging and Presence Protocol (XMPP)—is often used to connect devices to people. Extensible Messaging and Presence Protocol is based on the very popular markup language XML. Designed in 1999 for near real-time communications, it has been used for publish–subscribe systems, signaling systems, gaming, file transfer and, of course, the IoT. It has an extensive set of middleware programs to talk with any other protocol that exists.Streaming Text-Oriented Messaging Protocol (STOMP)—Formerly known as TTMP is a text-based protocol designed to be interoperable and therefore talk with any message broker. Like the other protocols listed above, it works above TCP/IP in the Open Systems Interconnection (OSI) model. It is easily implemented and therefore very well liked.Application Program Interface (API)—You may have heard of this term as it is popular these days as it acts like a universal translator. It allows different systems to talk to each other. APIs’ make it easier for people to use programs and developers to use technologies in building applications, by abstracting the underlying implementation, and only using the elements needed. This allows for easy integration between the various types of systems that are prevalent in today’s world. Like a universal translator seen in past episodes of Star Trek, it abstracts the conversation into ideas and not specific words. API, unlike the aforementioned messaging protocols, is a concept and not necessarily a messaging protocol.
Development of machine tool communication method and its edge middleware for cyber-physical manufacturing systems
Published in International Journal of Computer Integrated Manufacturing, 2023
S M Nahian Al Sunny, Xiaoqing “Frank” Liu, Md Rakib Shahriar
It is noteworthy to mention that there are other Internet-based communication protocols, such as Data Distribution Service (DDS), Advanced Message Queuing Protocol (AMQP), Constrained Application Protocol (CoAP), Message Queue Telemetry Transport (MQTT), Simple/Streaming Text Oriented Messaging Protocol (STOMP), Extensible Messaging and Presence Protocol (XMPP) etc., which have been explored by many researchers in recent years for IoT and CPS applications in different domains including manufacturing (Parto Dezfouli 2017). However, the research presented here is solely focused on improving MTConnect’s capabilities to make it more robust and feasible for SOA-based CPSs and thus allowing easier transformation of existing MTConnect-compatible manufacturing machine tools and systems into cloud-based scalable CPMSs capable of both monitoring and operating factory floors remotely. The potential of using other aforementioned protocols for CPMSs instead of MTConnect is beyond the scope of this paper and therefore not discussed below.