Thanks for this simple explanation: "Speaking simply, the topology of an IoT deployment reaches from local sensors and actuators to the cloud. The sensors and actuators attach to a local controller. Controllers link to gateways at the customer premises, which connect to the service-provider's access and edge networks. These networks connect to the cloud. The cloud can analyze data and make decisions." I'm going to be referring folks to this blog.
This nice blog is like a tutorial for a dummy like me on IoT. The de-mystification of the overly hyped subject brings it a ground level where a technician will be able to grasp the exact essence of what it means and how it can be applied.
Though , I have not exactly understood this SDN concept - who creates this software gateways and who manages them?
The gateways referenced here are IOT gateways. The SDN target software they run could be something like OpenFlow and would be supplied by the OEM or the service provider. Freescale has demoed OpenFlow on its processors and can help our customers with system design.
I can see SDN being an integral component of the IOT, especially when there's a lot of variability in a fixed facility, i.e., many mobile devices coming and going at a specific site. It could be similarly integral when centered around a mobile devices that travels to different sites.
Joe, it seems like this also provides a framework by which security concerns of IoT can be addressed. Would proper SDN design also include access controls into the IoT subnet? That should provide the tools to tailor security around potentially sensitive control systems while still providing access if appropriate.