Slashdot Mirror


IEEE Developments in Wireless Networking

JamesAlfaro writes "After much wrangling between opposing interests among the members of the IEEE, a first draft for the Wi-Fi IEEE 802.11n specification received approval in a Thursday meeting. Final ratification of the standard is not expected until next year." Relatedly, judgecorp writes "The IEEE has disbanded its working group on ultrawideband. They are leaving the marketplace to decide between two competing approaches." From the article: "Freescale, first to the market with UWB products, believes its headstart will give it a long-term victory, while WiMedia, with the backing of industry heavyweights including Intel and Microsoft, reckons its punch will eventually win through, even without a formal IEEE standard."

19 of 79 comments (clear)

  1. Wait faster by Anonymous Coward · · Score: 4, Funny

    So now I can wait on the hotel's 1.544 DSL line even faster?

  2. Pre-n compatiblity by SeanMon · · Score: 2, Interesting

    Are the various 802.11 "Pre-n" routers compatible with the draft standard? That would be unfortunate if they aren't, because they are rather expensive compared to b/g ones.

    --
    "Scud Storm!" -- Jeremy of PurePwnage.com
    1. Re:Pre-n compatiblity by amazon10x · · Score: 2, Informative

      However, I have read some articles that are saying the hardware in pre-n equipment may not even be compatible with pre-n. If the hardware won't work with it then a firmware update won't help.

    2. Re:Pre-n compatiblity by jimicus · · Score: 2, Informative

      They'd better allow for a free tradein/swap if their pre-n routers aren't compatible with the final spec.

      Like they have so many times in the past, yes?

      </sarcasm>

    3. Re:Pre-n compatiblity by amazon10x · · Score: 4, Informative
      I found a page about being unable to upgrade the firmware to fix it:

      http://www.thechannelinsider.com/article2/0,1895,1 754056,00.asp

      Towards the end of the article:
      Making matters even more problematic is that, unlike 802.11g, where many early devices could be upgraded to the real standard with a firmware upgrade, that's less likely to be the case with the pre-N MIMO devices, depending on who wins the standard war.

  3. Think of the consumers! by plbland · · Score: 3, Insightful

    I think it would be quite nice if they could at least co-operate to some degree with these UWB WiFi technologies. It's easy for the /. crowd to understand these compatibility issues but it can only be hassle for the general consumer who barely understand the current wireless standards/speeds.

  4. How bout *Nix support for 'b' ??? by smokestacklightning · · Score: 3, Funny

    Great, another wireless standard whose lack of *nix Driver support will undoubtedly make my machine act all twitchy ...

    How about out-of-the-box *nix support that doesn't involve me devoting my spare time, work hours and waking moments getting it to run, or run as it should ...

    Ran with NDISWrapper for a long time on my laptop, gave up after my last upgrade when Ubuntu dicked me. Now I've just got this really long, really sad cat5 cable that follows me around the house... My dog thinks it's his pal ...

  5. Subspace Communication within the S-T Continuum! by digitaldc · · Score: 2, Funny

    Another technology called Space Time Block Coding (STBC) will reduce signal dropout by using multiple antennas for redundancy.

    I knew all those years of Star Trek would eventually lead to every day applications.
    Now we can use our wireless routers for subspace communication with strange new worlds and new life forms, and boldly route where no one has routed before.

    --
    He who knows best knows how little he knows. - Thomas Jefferson
  6. Not needed for VoIP by hey · · Score: 3, Insightful
    Its cool and all that they are making a faster standard but the article says:

    This technology in particular is key to enhancing the VoIP user experience.

    I get 54Mbps on WiFi now. That's more than fast enough for VoIP.

    1. Re:Not needed for VoIP by Yahweh+Doesn't+Exist · · Score: 2, Interesting

      I remember using voice chat rooms best part of a decade ago, so yeah VoIP is basic so far as bandwidth needs. I expect they're using "VoIP" as the trendy name for chat in general (c.f. mp3 vs. audio file) and thinking of conferencing like iChat AV with multiple video streams but higher resolution so that you can see useful stuff rather than just have the pleasure of seeing a moving face.

    2. Re:Not needed for VoIP by tpgp · · Score: 4, Informative
      I get 54Mbps on WiFi now. That's more than fast enough for VoIP.

      Throughput is not the only requirements for VOIP.

      From the article:
      Another technology called Space Time Block Coding (STBC) will reduce signal dropout by using multiple antennas for redundancy.

      This technology in particular is key to enhancing the VoIP user experience.
      The article also mentions power management improvements (for devices running on batteries - like cell phones), longer range and better collision management.

      Together, these would make a significant difference to VOIP - even if Mbps were lower.
      --
      My pics.
    3. Re:Not needed for VoIP by Epicyon · · Score: 2, Informative

      Current wifi is sufficient for a single user on a single AP. However, with the current environment there is no provision for QoS in the shared media environment. VoIP requires consistent data delivery for a good user experience which is provided through QoS. It's not purely a matter of bandwidth.

    4. Re:Not needed for VoIP by fwr · · Score: 2, Informative

      No you don't. No one gets 54Mbps throughput on 802.11a/b/g wireless. That may be the advertized rate, but it's not your typical or even maximum bandwidth.

      Still, you are correct that even 802.11b at low speeds is good enought for VoIP as far as throughput. It's more SNR and the (lack of real) QoS that are the problems areas.

  7. Great, just great.... by 10Ghz · · Score: 3, Interesting

    More technologies that do the same thing, yet are incompatible with each other. "Oh, we'll let the market sort this one out". translation: "MWAHAHAHAHAA! Screw the consumers! It's up to the little guy to figure this one out, because we will have nothing to do with it!".

    --
    Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
  8. I'd abandon ultra-wideband too by Anonymous Coward · · Score: 2, Informative

    The practical problems with ultra-wideband are huge. This is probably a technology that should be approached incrementally rather than all at once.

    We've played with an ultra-wideband RF link in the lab. It's not pretty. Between the top of the band and the bottom of the band, the propagation changes a lot. Ditto for the noise profile. We used discone antennas (because they are inherently wideband) but those aren't practical for mobile use.

    We were successful in the lab for low data rates but, of course, that isn't the real world.

  9. Relevant UWB Link by writertype · · Score: 3, Informative
    Given that the CNET link above seems tied to the 802.11n standard, here's a link on the whole IEEE UWB story, from ExtremeTech.

    UWB Standards Group Calls It Quits "

    Unable to resolve a deadlock between two competing proposals, the IEEE working group responsible for the ultrawideband technology threw in the towel Thursday.

    The Institute of Electrical and Electronics Engineers (IEEE) 802.15.3a task group (TG3a), which oversaw the formation of the UWB standard agreed to withdraw the Jan. 2003 project authorization request that formed the group. Instead, the two competing technologies - MB-OFDM, championed by the Intel-led WiMedia Forum, and DS-UWB, promoted by Freescale Semiconductor and its UWB Forum - will be left to fight it out in the marketplace.

  10. Re:Pre-n compatiblity is NOT N-Ready by ArchAbaddon · · Score: 2, Informative
    I work in the networking industry. Certain companies came out with wonderful "Pre-N" marketing gimmickery in order to sell products. However, the rest of the industry was mostly appaled by this naming, because most if not all products labaled as "Pre-N" have little to no chance of being upgraded to 802.11n standards, due to the hardware limitations of these devices.

    I think a lot of customers will be disspaointed when they discover this, perhaps having bought this equipment under false pretenses.

  11. Faster then 100 mbit? by tecker · · Score: 5, Interesting
    If I am correct in thinking that "pre-n" and the new 802.11n will be faster then 100mbits that most people have in their house.This article shows that over the air will be 200mbps+ and the MAC SAP would peg out at 100mbps.

    That is all well and good for corperate environments that need network access to programs from a server but seriously. This speed is 40 times faster then the connection I have at home for my internet. Unless you are doing things over your home network (Streaming video I suppose) there is no reason to upgrade.

    The trouble is that theses companies will be pushing "N" routers like crazy when noone needs it. Unless it offers super Encryption of 802.11i then count me out.

    --
    Procrastinating life a way at a rapid rate of speed.
  12. While we're getting facts straight... by Ungrounded+Lightning · · Score: 2, Interesting

    Lets get some facts straight:
    UWB has been around since the early 1950's when the military started developing it. It is ACTUALLY a simplier radio than an 802.11 radio,


    While we're getting facts straight...

    Actually there were TWO major types of UWB being considered by the IEEE group. One I'd characterize as an orthogonal-wavelet direct-sequence spread spectrum approach, plowsharing older military tech, which appears to be the one you're describing. The other was a orthogonal-frequency-division-multiplexing approach, very much like WiFi, DVB, and a number of other systems (such as the Ricochet wireless network and the Telebit Trailblazer modems.)

    The systems had different technical advantages and disadvantages. (For instance: The DS system was simpler and lower power hardware, but needed notch filters on transmit to avoid interfering with other services that were still active in its band and depended on forward error correction to compensate for pattern sensitivity from the notch filters and the propagation differences across the band. The OFDM system could notch out on transmit just by chosing not to send on those segments of the band and processed each chunk of band separately so wasn't bothered by selective propagation conditions, but required a lot of DSP power on both transmit and recieve, and still needed filters to keep narrow-band interference from saturationg the receiver A-to-D converter.)

    A bigger issue, though, was that the engineering talents required to work with the two systems were different. A WiFi OFDM team could just move to the OFDM system with little new knowlege. The DS system requried a somewhat different skill set to engineer - a digital/analog interface mix. There were plenty of engineers with skills availabe for each system. But they were largely DIFFERENT engineers.

    Each system had several companies - at least one a major player - backing it. And of course each player was backing their bet with advance engineering on their approach, and so was heavily invested. Since both systems would perform very well (alone), the choice became more a matter of politics, protecting the companys' investments and technical lead, than of the technical merits of the respective systems.

    Since a supermajority of the players in the standards voting was needed to make a pick, neither side had it, and neither was willing to bend, the process bogged down. It became apparent a couple years ago that the standards effort would fail, the working group would throw in the towel, "the marketplace would decide". And without a standard in place only the big guys would be able to play. (The chip companies were ahead and were giving advanced chip info only to major, established, partners. So even a startup intending only to assemble a device was out in the cold.)

    The two systems, however, would NOT share the band well. Each would tend to jam the other. The DS side (the smaller faction) tried to salvage the train wreck. They proposed a slower, robust, common transmission mode that could be handled by either system with trivial additions to its hardware and firmware (and less effort on the OFDM faction's part than their own), to be used for the short bursts of communication involved in time-slicing the channels. And for the standard to prescirbe using this and standardizing a version of each of the two approaches.

    But the OFDM group was not interested. They had more players, and the players had gotten together to do their own, internal standardization effort of their own systems. For them the standardization effort was mainly an exercise in keeping the DS group (which needed less time to get equipment ready for market) from moving until they were ready to go with their stuff. (Within their approach and with the OFDM version of the draft standard as a reference, they could go to market once they had something ready and tune out any minor incompatibilites among themselves with firmware tweaks, and there were more of them so they had the odds down,

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way