Smarter Cities with Stream IoT-X, ARM mbed Device Server, and wot.io (part 2)
Recall that in a previous post, we discussed a collection of ARM-based devices and open data sources that comprised the basis for wot.io's demonstration at Mobile World Congress 2015 last Spring. Today we will continue our deeper look into the technology behind that demonstration by examining the device management platforms that were employed.
Managing Devices with Stream Technologies IoT-Xtend™
In a large organization or municipality, the issue of just simply managing all of the connected devices is usually the first challenge one encounters before all of the resulting data can be collected and analyzed.
This is where Stream Technologies comes in. Their IoT-Xtend™ Platform is an award winning connected device management platform designed to monitor, manage and monetize device endpoints, manage subscriptions, and provide robust billing and Advanced Data Routing. Xtend provides Multi Network Technology capability in one comprehensive platform. Xtend serves and supports complex multi-tenant and multi-tiered sales channels. Its web-based user interface can be used to view which devices are actively transferring data and allow for the management, routing, and metering of data.
Previously we described how we created embedded applications to run on each of the demonstration devices and could then connect to our device management platform.
In fact, what we were doing was leveraging the extensive device integration capabilities of Stream and their IoT-Xtend™ Platform. Specifically, Stream has integrated numerous cellular, satellite, LPWA, and Wi-Fi devices into their platform. In cases like our demonstration, where an integration did not already exist, creating a new integration was simply a matter of sharing the schema to which our messages would conform, and the communication protocol it would be using.
So the notification messages being sent from the devices to IoT-Xtend looked something like this for devices containing GPS sensors (like the u-blox C027):
When the device is powered on, it connects to Stream using its LISA-C200 CDMA cellular modem and begins to send it's location data from the GPS receiver. Because its SIM card has been provisioned and managed in IoT-X, the device telemetry data is received by and made visible in the IoT-X web-based user interface.
Connecting Stream IoT-Xtend™ to the wot.io Data Service Exchange
wot.io and Stream have fully integrated the Stream IoT-Xtend™ device management platform with the wot.io data service exchange™. This means that notification and telemetry data from the managed devices can be routed to and from any wot.io data services for analysis, visualization, metering and monitoring, business rules, etc.
In part 3 of this series, we will explore a few of the many data services demonstrated at Mobile World Congress.
ARM mbed Device Server
Of course, wot.io is all about choice and selecting the best-of-breed services fit for specific needs. As such, one might be interested in exploring one of the other device management platforms on the data service exchange.
Whether your ARM mbed Device Server needs are to bridge the CoAP protocol gap, combine it with other connectivity or device management platforms, manage device identities and authorizations, send complex command-and-control messages to devices, or simply subscribe to device notifications, or to host production-scale deployments and handle your data service routing needs, wot.io has you covered.
Connecting Stream IoT-Xtend™ with ARM mbed Device Server
In addition to a direct integration between IoT-Xtend™ and wot.io, the devices managed in Stream Technologies IoT-Xtend™ platform can also be integrated with other device management platforms. In particular, at Mobile World Congress we demonstrated a configuration in which devices were registered in both the Stream IoT-Xtend™ and ARM mbed Device Server platforms.
Real-world IoT solutions will often involve multiple device management platforms. In such situations, it is often desirable to consolidate the number of interfaces used by operations staff, or to leverage the unique strengths of different platforms. For example, an organization or municipality deploying a smart city initiative may elect to use IoT-Xtend™ for its SIM-management and billing-related capabilities while standardizing on ARM mbed Device Server for device provisioning and security. Or as another example, perhaps they would like to standardize on ARM mbed Device Server, but a vendor or partner uses another device management platform like IoT-Xtend™.
wot.io provides enterprise customers with the powerful ability to interoperate between and across device management platforms, sharing both device data and command and control messages with data services in either direction.
In our final post in this series, we will discuss some of the data services that were used to analyze, visualize, and manipulate the Smart City data coming from the devices managed by IoT-Xtend™ and ARM mbed Device Server, and the London Datastore project.