The race for IoT domination is on. The IoT space is already filled with a vast array of technologies and protocols, making the choice of the right IoT communication gateway a fundamental requirement on you path to IoT success. Why ?
Expanding your system’s connectivity options is key to a leveraging the benefits of the IoT.
Communicating with system endpoints across networks and using different communication protocols is unavoidable.
Converting you data into the most appropriate format possibly for more sophisticated downstream processing will enable the right decisions to be made at the right time, unlocking new IoT insights and generating new business value.
If you are looking to develop a future-proof IoT system that is flexible and adaptable to changes driven by constant technological evolution, it is essential that you have a high-performance, extensible and configurable protocol integration framework that can transparently interoperate across different communication technologies.
Vortex Gateway addresses the problem of making data seamlessly flow across systems and technologies while adapting format, content, and QoS. It can used to integrate DDS-based systems with over 100 other messaging technologies, such as MQTT, AMQP, JMS, XMPP and DDSI-RTPS; as well as integrating with Web Technologies such as W3C Web Services and RESTful Web Services and other with proprietary protocols.
Vortex Gateway is the only DDS-based mutli-protocol integration platform available in the market. It allows IoT systems to connect their devices and applications together independent of the underlying technologies used and also to leverage the many other great benefits of the full Vortex Product suite.
Applications running on edge-devices, gateways, enterprise servers, cloud services and mobiles are all valuable data sources and sinks in an IoT world. But new software platforms are needed to connect and leverage all these sub-systems to maximize the business value-add of Enterprise IoT.
For several years, M2M platforms have provided reasonable solutions for connecting machines to cloud services (actually it should be M2C, as M2M platforms generally do not support peer-to-peer device communications). But these platforms have struggled to create large markets or provide strategic enterprise-wide solutions. They have mostly been restricted to providing vertical/tactical applications — in effect self-contained ‘stovepipe’ systems.
But to fully exploit the potential of the IoT, data must be free to flow to wherever in the system it can add value, e.g. between ‘edge’ devices for control purposes, to gateways for data aggregation/ingestion and local analytics, to cloud-based applications for Big Data analytics, to enterprise systems for OT/IT alignment and supply-chain integration, to mobiles for on-demand data delivery to employees (see Figures 1 and 2). The promise of Enterprise IoT is the new value created through ubiquitous data availability (and its processing by applications into actionable insights), but this means a new generation of platforms is required to provide the data-connectivity to support a new generation of distributed IoT applications.
One of the biggest differences between traditional M2M and Enterprise IoT systems is that ‘horizontal’ as well as ‘vertical’ data-flow must be supported. Vertical silos of data do not provide the potential to add value beyond a specific sub-system, so a fundamental feature of next-generation IoT platforms will be a data-connectivity layer that supports system-wide data-delivery as required: the right data, in the right place, at the right time, system-wide.
There are many potential ways (control, analytics, dashboards, event processing, mobile apps, etc.) to exploit all this newly accessible IoT data, but it needs to be delivered to the appropriate application in a timely manner wherever in the system that application may reside (on an edge device, gateway, enterprise server, tablet, or in the cloud). Only then can the data be converted into new ‘actionable insights’ and thus new business value.
To provide this underlying capability, a data-connectivity layer needs to be deployed across all nodes the in the system — at least all the nodes that are required to share data (publish and/or subscribe). An enterprise version of Twitter for Things, in effect.
In simple terms, the diagrams in Figures 3 and 4 show, respectively, how this layer can be deployed both in the cloud (to support cloud services) and on devices (Things, servers, PCs, mobiles, etc.). They also show potential sources of the applications the platform connects (end-user developers, ISVs, SIs, OEMs).
[Note that the data-connectivity layer supports not only inter-node data-sharing, but also data-sharing between the application components of the IoT platform itself, i.e. inter-operability between platform services (such as IDEs, edge-device management, API management, analytics engines, etc.) as well as between Things].