Slashdot Mirror
Will 802.11 Kill Bluetooth?
joshwa writes "NYTimes (free reg. required) has an article about the struggles of the Bluetooth folks to fine-tune their technology and get the costs down far enough. The most interesting part is that analysts seem to think that 802.11's (what is this new 'Wi-Fi' moniker?) growing popularity will overshadow Bluetooth's entrance into the marketplace, and will beat Bluetooth into the small devices market. Can 802.11 actually work in a Palm or a cell phone?" The article, IMHO, misses the difference in uses - if you've got a small device that you want to conserve power on, and only communicate small distances, Bluetooth's ideal. If you've got a lot of power, a la a notebook computer, and want to communicate 150 ft., then 802.11 is what you want. Imagine that: Different uses! Different standards! Amazing!
There are ways around it - by having APs that can handle both protocols and thus can deal with both protocols being active at once. But given teh amount of 802.11 equipment out there already, I expect many places will resist Bluetooth devices since they don't want to have to buy new APs. Thus Bluetooth will have a tough time gaining ground.
I think its a neat idea, but heck - USB was supposed to reduce the rats nest around my PC too and hasn't so far - I'm still waiting for monitors with USB ports that your keyboard and mouse connect to - I knwo they exist, but its not widely done (nor are keyboards and mice over USB)
Top Most Bizarre/Disturbing Error Messages
I work in the wireless industry myself, and can say that there is quite a bit of debate over this.
What will probably happen (as seems to happen a lot) is that one major vendor or provider will choose a certain standard, regardless of its value, or without a thought as to whether or not two technologies can be mutually compatible (as the writer above mentions). Then its time to push it down everyone's throats until the other one disappears.
Sad, but true.
"Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth
... then all you have to do is own a Handspring. There is a module to do that from Xircom (Intel)
Somebody turned me onto this page that talks about how a group of guys are making a mission out of setting up localized, free wireless access to the Internet, with the ultimate goal being able to fire up your laptop anywhere within your city and get on the net for free. All it takes is a couple hundred dollars (which isnt much when shared between 20 people who pitch in, initially) and a guy who controls anything as meager as a DSL line willing to "donate" some of his bandwidth to the antenna.
If anything, stuff like this will kill Bluetooth from a purely VHS vs. Beta sort of way. When it comes down to a fight between popular acceptance versus quality of technology, popular acceptance always wins.
Cheers,
Bowie J. Poag
The article, IMHO, misses the difference in uses - if you've got a small device that you want to conserve power on, and only communicate small distances, Bluetooth's ideal.
This sounds like the same arguments people were using for infrared ports a few years back, and that caught on like sandpaper pantyhose.
Bluetooth devices are failing for the same reasons infrared ports don't get used: they're just not that useful. Sure, when I want to print, it's awesome to be able to hold my PDA or laptop up to an HP printer and just fire away - but I have to hold it just so to maintain connectivity.
Bluetooth is the same way - you have to be so close that it's not really useful for much other than wireless keyboards and headphones. Don't even get me started about Bluetooth connections between a cell phone and a PDA: why shouldn't I just get out the cable and save even more battery power? No sense in burning extra power just to have the convenience of leaving my cell phone in my holster.
Am I wrong? Is there anything here that infrared didn't try to solve? Is there something that you would actually pay an extra $30 to add to your small battery-operated device, something that you wouldn't just use a cable or infrared for?
What's your damage, Heather?
Which one do I use if I have a medium sized device with a middlin' amount of power and want to communicate a moderate distance. Do I need both?
It gets worse. Even if you have a high-powered device like a laptop, the industry expects you to have both. You'll need Bluetooth to talk to your cell phone and PDA, and 802.11 to talk to your wireless lan. Forget that! Laptops are pricey enough as it is.
What's your damage, Heather?
Bluetooth is an interesting technology. When you start looking into it, the possibilities are enormous. A lot of people were bitten by the Bluetooth bug, and it's understandable why. It would be VERY cool if it worked out.
One of the huge problems is that people keep comparing 802.11b (WI-FI) to Bluetooth.
They are NOT the same thing. Go read the Bluetooth spec. Bluetooth is a cable replacement technology that can, if necessary, do some ad-hoc networking. 802.11b is wireless Ethernet. Not the same thing, not intended to do the same thing.
There have been a couple of companies that have been deliberately muddying the waters about this. Bluetooth is NOT an acceptable replacement or even a good substitute for 802.11b. Bluetooth is limited to 1megabit per second, which means throughput of about 650k to 800k real, depending on conditions. 802.11b is 11megabits max, and about 5megabits in the real world. (Shared bandwidth, retransmissions, and Ethernet overhead)
Bluetooth is staggeringly bad at providing traditional Ethernet services, just as 802.11b is awful as a cable replacement technology. 802.11b has too much power usage, and dependency on Ethernet for cable replacement. It was NOT designed to replace the cable going from your cell phone to your headset. Bluetooth was. It was just overly hyped and generally misunderstood. Too bad, it could have been cool.
Gedvondur
It's been pointed out that 802.11 could have a low-power mode. 802.11 HAS a low-power mode: it's called PCF, and nobody uses it. But really, if you don't mind the power drain on the slave (the master can't sleep anyways), you can even use a low-power transmitted with DCF.
/. attitude towards Bluetooth. When MS creates proprietary standards, cool or otherwise, everyone rails on them. When Intel does it in cooperation with a couple other big names, but shuts out public participation, some people here seem to frown on the demise of the standard. While the IEEE standards process is not quite as open as the IETF, I'd take an IEEE standard over a Bluetooth SIG standard any day.
The point is Bluetooth screws up 802.11, and which is more important, your LAN that allows people to get work done when they're not in their cube, or Bluetooth which lets people talk on their cell phone using an earpiece without wires? That's a tough call, Intel.
I can't understand the
Actually, we're better off using the same standard for different uses, wherever possible. Do you want to go back to TCP/IP, IPX, and NetBEUI on every LAN? Ethernet and token ring? They all have different uses, but they're close enough that we should just pick one pretending that it will work in all situations, then make the best of it.
Bluetooth and 802.11 are clearly in this situation, IMO. The main difference between them: one is for near and one for far. This makes sense by strict engineering standards, but in the big picture it's a detail. If 802.11 becomes the standard, we'll make it scale down to "near". Not to mention (as did another poster), what do I do if I'm "in between"? There are other parts to Bluetooth, but nothing that can't be layered on top of another network (in the Internet tradition of "dumb network, smart endpoints").
The evaluation of an action as 'practical' . . . depends on what it is that one wishes to practice.
My esteemed Slashdot colleagues have already pointed out that 802.11b can have verious modes, from 1 to 11mbps. But there also is no standard for 802.11b radio output power. You can have a 100mW radio like the Cisco Aironet LCM352, or you can have a 30mW radio like the Lucent Orinoco Silver. You could have 1W or 1mW, as well. I suspect that if your range requirement is only 10 meters, you could use a 5mW radio and a short dipole antenna at 1mbps for a low-power 802.11b device. If you could get 1 or 2 dBi gain out of the antenna, you'd be doing even better.
And I like them,
:-)
I went to Ericsson once where they showed us a bunch of stuff working over bluetooth (vending machines, connections to pda's, laptops, internet radios, web pads and overhead beamers) and I must say I was impressed.
Interference may be an issue though but in the long run I think a technology like Bluetooth (not necesarily Bluetooth itself) will reach a large market. At some point in the future we will all probably have some fiber/DSL X megabit line into our home which is hooked up to some routing thing that sends the whole stream into the air thru some shortish range technology. From that point on we can access that broadband line from every Bluetooth enables device in our home. You don't need a high power 150' range wireless lan for that, you'd just upset the neighbourhood then.
Wireless lan may be able to do the same thing but as far as I know it's probably going to be a lot more expensive, Bluetooth and wireless lan are 2 different things (which was one of the first things I heard from the Ericsson people) with different uses. The Bluetooth organisation thingy whatever comittee or something wants to get the price of a chip under $5 so practically every manufacturer will throw in bluetooth, if only as a marketing thing. I don't see that happening with wireless lan.
Besides all that LAN's Ethernet, AFAIK, and Bluetooth makes individual connections to different devices on different frequencies, again AFAIK. Bluetooth just seems a lot more efficient to hook up devices that don't need a gazillion bits to operate at an acceptable level.
Ok, I'll stop ranting now, it's the end of the working day and I can't say I'm feeling very coherent
-- Si hoc legere scis nimium eruditionis habes.
802.15 and 802.11 have very different purposes. 802.11 is designed from the ground up to be "wireless ethernet" while 802.15 is really a replacement for IR ports and for wire replacement. For instance, 802.15 has an SDP, a Service Discovery Protocol, which is basically a way do discover what the other bluetooth devices in your piconet can do. The original idea was for you to press the "Print" button and your bluetooth device goes out and asks who can handle something called a "print job". The local BT enabled printer pipes up and they negotiate automatically (The 802.15 spec also has provisions for authentication and encryption), and your print job automagically appears on the printer. To do this with 802.11, you would have to make some sort of Service Discovery layer on top of the 802.11 standard, and most 802.11 devices wouldn't support it. Bluetooth devices also draw much less power than 802.11 devices in general, and the 802.15 spec even has provisions for cutting down on your tx power if you are close enough to the piconet master (although I don't think most devices implement this yet).
In a nutshell this article is the equivlent of saying that Ethernet is going to kill off USB, because it's obviously so much faster and stuff.
I read the internet for the articles.
"...if you've got a small device that you want to conserve power on, and only communicate small distances, Bluetooth's ideal. If you've got a lot of power, a la a notebook computer, and want to communicate 150 ft., then 802.11 is what you want. "
These aren't "different uses". Different uses would be something like "walking the dog" vs "picking my teeth" or "flying the space shuttle" vs "trimming the hedges". Both of *your* examples are "using a portable computer to communicate wirelessly".
I mean, consider this. You go to Circuit City and ask to buy some speakers. The guy there says "Well, for DVDs or for VHS?" Ummmm....does it matter? "Of course. They are totally different technologies. One uses magnetic tape while the other is an optical disk technology. Totally incompatible. Don't even try playing VHS tape sound through DVD-compatible speakers."
Obviously different devices have different *optimal* solutions. But keep in mind that no device exists in a vacuum. If laptops are running 802.11 then handhelds better do the same or I simply won't buy one. It's not like the two camps having nothing to say to each other and can be fully partitioned.
324006
Remember those "friendly" aliens from Mars in "Mars Attacks"? Swap in Bill Gates for each alien and then think about what's the fuss about Bluetooth....
The problem is this: Microsoft is dis'ing Bluetooth and pushing 802.11 for all the wrong reasons. 802.11 is a good technology but it forces the small device( ie Palms ) to be bigger. WinCE devices are already FAT because the OS and the plethora of capabilities pre-packaged. This is why Microsoft is pushing 802.11 over Bluetooth. It takes care of two big headaches it has.....Palm based handhelds are becoming the place were users keep their data and the computer/network is a backup or copy of the PDA. This isn't what Microsoft wants because it wants to own your data and charge you to access it. By pushing for the death of Bluetooth it stalls Palms move into wireless, leaves Palm handhelds stranded by requiring it be "tethered" to a computer they can keep track of, and gets another shot at moving your data into it's hands instead of yours.
Another technology attacked to preserve the almighty Microsoft corporation.....
"Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
There were just too many threads I wanted to reply to, so I figured I'd just put everything I had to say in one post, so here goes:
1. The statement that Bluetooth is lower power than 802.11 is currently false. Okay, it has a lower power transmitter, yes, but so far, last I knew, nobody had produced a Bluetooth radio that wasn't at least as much of a power hog as an 802.11 radio... and any 802.11 radio that has a power-saving mode does _much_ better than a Bluetooth radio. Bluetooth was also supposed to be cheaper, but the manufacturers are discovering that they are having a tough time bringing down the cost on that, too. Given time, these problems can be overcome, however, 802.11 happens to have a large headstart on both the cost and power fronts, and therefore has a good chance of preventing Bluetooth from being able to compete (nobody wants to invest a bunch of resources into a standard that the market hasn't yet truly clamored for).
2. Bluetooth and 802.11b interoperability. Without breaking one standard or the other, it ain't going to happen. And even if you do break one standard, it won't be backwards compatible. The two standards conflict too much. 802.11b has a back-off mechanism. Bluetooth doesn't. I actually did some work looking into building a Bluetooth/802.11b AP that would try to cleanly give both Bluetooth and 802.11b time on the air without breaking either standard. It's too difficult. Bluetooth is just to strict on the timing (not to mention the big problem that some Bluetooth cards refuse to give up being the Master).
3. 802.11 security was not broken. WEP was broken. Badly. But WEP is not the end-all, be-all of security. And yes, the industry _is_ working on better security, and has been for some time. IEEE 802.11 Task Group e is still in the process of agreeing upon a method for point-to-point security, with dynamically session keys, including a username/password setup. This is what the industry has wanted for some time. WEP was only meant to slow down the script kiddies who would just sit in parking lots with their cards set to associate to "ANY". I really wish people would stop assuming that WEP is the entirety of wireless security. It is not, and was never intended to be. One more note on this: it was not 802.11x that was broken. I'm not sure what 802.11x is, but it isn't a security standard. 802.1x is a LAN security standard, but even that isn't what was broken. Just WEP.
4. 802.11, 802.11a, 802.11b, 802.11. 802.11 is the general IEEE group for Wireless LAN networking. 802.11b is the 11Mbps standard. 802.11a is the 5GHz 54Mbps standard (once they decide exactly what that standard is). TGe, which should translate to 802.11e will be the new security standard. There are others (including a standard for 22Mbps in the 2.4GHz band, which I _think_ is 802.11h), but I don't remember what most of them are.
5. Wi-Fi stands for "Wireless Fidelity". Basically, a bunch of 802.11 card manufacturers got tired of the fact that different cards that implemented IEEE 802.11 were not interoperable. So WECA was born (Wireless Ethernet Compatibility Alliance). WECA decided that "IEEE 802.11" wasn't a marketing-friendly name, so they came up with "Wireless Fidelity" or "Wi-Fi" for short. Despite the marketing speak, this is actually a good organization. They have a whole slew of tests to determine whether an 802.11 radio is compatible with others that have passed the tests. If they pass, they get to put the Wi-Fi logo on their product. If a product has the Wi-Fi logo, then it can interoperate with any other radio that has passed the WECA tests. So there is a very minor distinction between Wi-Fi and 802.11. Basically, it is possible for a radio to implement 802.11 and not be Wi-Fi, but at this point, no company in their right mind would do so.
Well, that pretty much ends my rant. Take it for what you will.
-Freeptop