One of the key questions in the definition of this space is how much functionality to put into a central device like this and how much to distribute to external devices. Adding content caching might seem like an obvious candidate for a central server like this, but that would mean that it would have to be able to directly handle DRM negotiations with a number of content services and then negotiate with display devices in the local network. A better approach might be to have a central server that provides storage service to a Roku or a smart TV and lets that device handle the negotiations and encrypt the data on that central server.
The same applies for IoT devices on the local network. If the gateway exerts too much control over them it is likely that it will be bypassed. There should be a defined set of services in the gateway that enhances the devices without being too obnoxious about it. Example: A home router provides connectivity and a firewall that limits aspects of that connectivity. It also provides standardized mechanisms for computers and devices on the network to modify the settings on that firewall so that they can provide services.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.