Konferenzen und Rahmenprogramm
Dotdot Unifies Legacy Device Networks
Electronic device connectivity started with personal computers, then evolved to mobile devices. In five years almost every device will be connected through communication pipes using an array of IoT technologies, protocols and ecosystems. Today we are in a similar scenario that the mobile phone industry faced in the late 1990s when mobile operators chose either CDMA or GSM. Consumers choosing a different service found themselves with phones unable to interoperate on the chosen network. To understand the interoperability issues for IoT devices, consider a large corporate building remote from its headquarters. Its lighting may have been upgraded with a control system leveraging Zigbee while the HVAC system is controlled by Modbus. Portable assets are tracked using Bluetooth beacon tags. None of these systems likely interact with each other. If the head corporate office established a new end-of-day policy to shut down half the lights, throttle the HVAC and perform a final scan to ensure all portable assets were in their secure location, each of these systems must be individually programmed with the same set of rules unique to their system. To remotely check policy adherence, the head of building operations would have to log into each system over the Internet and discern different forms of similar information, per remote building. Replacing or retrofitting every device to ensure they use a single protocol is not possible. The reality is a device’s chosen connectivity is optimal for its application. Bluetooth beacons, for example, are optimal for battery-powered tags used in asset tracking. A Zigbee mesh topology is a better choice for connecting hundreds of commercial lighting nodes installed above a large commercial floor space. Instead of finding the perfect protocol, dotdot can be augmented as a language to unify the array of connected devices. Dotdot gives a connected lighting unit a lighting profile, regardless if it uses Wi-Fi or Zigbee. Its behavior and attributes are specified so that a Wi-Fi lighting dimmer panel using dotdot can interact with a Zigbee light. Adding dotdot to each system is relatively simple. For new devices using Wi-Fi or Thread, dotdot resides within the device to control and respond to commands. In the case of existing protocols such as Zigbee and Bluetooth, language translation APIs can be added to an application to translate protocol commands into the dotdot language. A translation plugin, for example, has a very low-memory footprint requiring only kilobits of memory and minimal processor usage. Further adaptions of translating UDP to TCP or a RESTful protocol may require a little more planning, but its complexities are hardly difficult for most firmware-savvy engineers to implement onto a low-cost wireless connected device. Dotdot give IoT legacy systems the language to communicate with their devices. Dotdot enables an array of innovations for device control agnostic to the underlying IoT protocols within each device.
--- Datum: 27.02.2018 Uhrzeit: 16:00 Uhr - 16:30 Uhr Ort: Conference Counter NCC Ost