View Single Post
Posts: 449 | Thanked: 29 times | Joined on Jun 2006
#95
[QUOTE=anidel;163822]
As far as I understand it the WiMAX has a pretty wide range of working frequencies, from 2Ghz up to 66Ghz.
The higher the frequency, the higher the bandwidth, the higher the battery consumption, the lower the penetration...right ?
No bandwidth is related to how much channel width and what modulating encoding scheme is used, so for sake of simplicity say you have a 100 MHz channel width you get 100 Mbps and 50 MHz channel you get 50 MHz. Higher bandwidth just has less ability to penetrate walls, which is why you can hear the bass at 22Hz through the floor, but not the tweeters at 20,000 Hz.

Anyway, the choice of which frequency a WiMAX enabled device can talk on is a matter of the local government, as far as I can tell.
For the most part you're correct, I own a wireless service provider company and we've decided to use the 5.4GHz unlicensed frequency for deployment of WiMAX, but mostly as a last mile link. If one wanted to use the 810 on our network then Nokia would have to deploy it with a 5.4GHz WiMax RF chip.

As usual EU and US looks like are following different paths.
EU is pushing bandwidth, while US penetration/power consumption.
I don't believe that to be the case, but I don't really follow the EU


If all I have written is true, then my WiMAX enabled device is already limited to only those countries that licensed the 3.4Ghz frequency and won't let me chat in the US.
Bingo! But I think a lot of carriers are going to be in for a surprise as the unlicensed versions of WiMax carrier equipment starts appearing allowing for a greater range of competitor alternatives at much lower cost structures with out being tied into one carriers particular network. There was a time when one could only get voice from the telephony company, then VoIP came along and changed that whole game plan completely. The original goal when we started work on WiMax in the 802.16 forums was to have the same impact.
 

The Following User Says Thank You to bac522 For This Useful Post: