With much legacy equipment existing with older protocols and requiring diverse real-time needs, the Industrial IoT will not soon, if ever, use a single data-connectivity standard.
A great example is the Connected Boulevard program in Nice, France, which uses Industrial Internet technologies, including an innovative data-sharing platform, to help manage and optimize all aspects of city management, including parking and traffic, street lighting, waste disposal and environmental quality.
The key to these benefits is the ability to derive value from the data. The data must be accessible wherever it resides and delivered to wherever it’s needed (edge to the cloud) so that it can be analyzed and acted upon in the right amount of time. There are a range protocols currently used to provide this “data-sharing function” within an Industrial Internet system (see chart above). Chief among them are:
- The Object Management Group’s (OMG) Data Distribution Service for Real-Time Systems (DDS);
- OASIS’ Advanced Message Queuing Protocol (AMQP);
- MQ Telemetry Transport (MQTT), a protocol originally developed by IBM but now an OASIS standard;
- Representational State Transfer (REST), a common style of using HTTP for Web-based applications and not a standard; and,
- Constrained Application Protocol (CoAP), a software protocol to be used in very simple electronics devices such as Wireless Sensor Networks (WSN) that allows them to communicate over the Internet; and,
- The eXtensible Messaging and Presence Protocol (XMPP), the IETF’s formalization of the base XML streaming protocols for instant messaging and presence technology originally developed within the Jabber open-source community.
To read the full report, visit www.eetimes.com