Jan 28
iruwbdesign.jpg

Ultra-Wideband (UWB) is widely misunderstood technology, at least for us consumers. It’s also a technology that I’ve been interested in since the first white papers from companies like Intel started rolling out in early 2000’s. That being said, you now know that I’m pro UWB.

But, what I think is cool doesn’t necessarily make it to market, though. It would be like Homer Simpson designing a car. It’d probably break a company and some monstrosity like this would come to market:

homersimpsoncar.gif

(I would buy this car)

These days though, UWB gets thrown around like it’s a four letter word and that’s sad. Not because UWB is dead, but because UWB is still so misunderstood by those who report on it and even some who market wireless USB products. So we’ll take the most common misconceptions we’ve heard in our research and try to clear up each of them.

UWB can’t replace existing wireless technologies:
UWB, at its core is a radio technology. It’s a low-power, short-range wireless technology that has hi bandwidth. It operates around 3.1 GHz to 10.Ghz, so it covers a wide spectrum. Keep in mind it’s low power, so UWB allows hi-data rates between a host and devices in a range of about 30 feet. It’s not intended to replace WiFi, rather UWB is complimentary to existing wireless infrastructure and systems.

Short range? Wireless USB, Bluetooth, why UWB?
UWB is not a technology like Bluetooth or wireless USB. Where those are protocol based technologies, UWB is protocol independent. A lot of on-line sources don’t really make this clear. UWB can “carry” multiple protocols. Wireless USB, IP, bluetooth, whatever (of course within reason). So, if you have a USB product and want to go wireless with it, UWB can carry a USB stack or bluetooth stack.

Too much wireless, I get enough interference already
UWB is intended to be complimentary to existing wireless technologies. In fact, running USB or bluetooth over UWB offers a tremendous amount of increase in bandwidth. Also running those various protocols (USB, etc)over UWB, none of the devices will interfere with each other because they will only detect their related protocols.

No thanks, Wireless USB FTW!!!
That’s okay too! Keep in mind wireless USB products use UWB technology. UWB is a carrier for the USB stack. In one sentence, that’s really how wireless USB is implemented today (and going forward).

That’s fine, but you can’t touch my wireless HDMI with your UWB
Again, keep in mind that UWB is really protocol independent. Wireless USB can do video and audio today because video and audio can be pushed through USB. Thus, UWB can carry the same USB video/audio data wirelessly. This is essentially what’s driving wireless USB into your TV sets today. That being said, HDMI can also be carried by UWB. UWB is protocol independent, so wireless HDMI products use UWB technology to carry the data. It’s that simple.

So it doesn’t matter if I want it or not, I’m getting it
Yup. That’s true. But now you’re a more educated consumer and understand just a little more about what you’re buying.

Look, we’re not trying to change the world here. We just want you to understand a little bit more about UWB and its applications. UWB hasn’t died. It really hasn’t. It just sort of disappeared for a little bit because of the nature of the kinds of products that UWB goes into. It’s an enabling technology that’s not really going to be at the front of everyone’s minds, but it’s in there making it happen.

If you did buy something and think, “I want UWB in here”, then we’d think you’re one well informed consumer. Fact of the matter is, UWB enables a lot of the exciting stuff we’re seeing in man-cave (home-theater) applications.

When you’re shopping around and pick-up that wireless USB or wireless HDMI device, now you’ll know a little more about one thing that’s helping it do its magic.

(Editor’s Note: There’s a lot more about UWB that we haven’t covered. For more information visit Alereon and Intel’s site for additional white papers and product specific information.)

Leave a Reply

Tech Bucket Blog LLC
preloadabc preload preload