DECT encryption has long been developed. It is not a strong encryption though. With the data rate, even software encryption can do the work.
There is no doubt that DECT is a mature technology. Power consumption is low. However, would the data rate be a stumbling block for the application? What's the range of the automatic power adjustment?
Seems to me that the easiest way to understand what DECT is, what roles it might play in the future, and how it differs from "personal area network" schemes like Bluetooth, is to understand that DECT was designed to be a cellular telephone standard. With all the handover protocols that entails.
Its metropolitan area aspirations were challenged by a host of other then-emerging cell telephone systems, but interestingly enough, its in-home use succeeded.
I think of it now as being the original version of femtocells. Only these days, because the outdoor macrocells are on different cell standards, the DECT "femtocells" don't allow roaming from your regular cell phone. That aside, they are indeed femtocells.
I like the idea of a low power RF local network, but I did not see anything mentioned about encryption or security for the devices. They need to clarify if they are including any hardware encryption capability for a secure local network.
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.