UWB is not only meant to high data throughput. Impulse UWB encodes input data to series of very-short radio impulses. Within a given power budget, you can use low-power / high-density impulses for short range / high speed communication, or high-power / low-density impulses for long range / low speed communication. This flexibility is one of the beauty of pure-impulse radio.
However in the UWB boom few years ago, most of chip designers abandoned impulse UWB and adopted much ordinary radio methods (namely OFDM). That was because impulse radio has many limitations and difficulties, as much as its benefits.
It is interesting how IMEC overcame those difficulties. I still love beauty of impulse radio and want to see if it can hit the market this time.
" It could power an MP3 player or headset for more than 17 or 33 hours respectively."
Not to pick nits, but this is EE Times. This wireless technology doesn't power devices for certain periods of time. What was intended was to say that this technology would extend the battery life of these devices.
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.