Jump to content

WiWavelength

S4GRU Staff Member
 View Profile  See their activity

  • Posts

    18,133

  • Joined

  • Last visited

  • Days Won

    429

 Content Type 

Everything posted by WiWavelength

  1. WiWavelength
    I would like to see some documentation. Do you have any stats to corroborate this assertion? AJ
  2. WiWavelength
    Recalcitrant iDEN users, pay your penance, convert to the CDMA2000 faith, or get out. Done. AJ
  3. WiWavelength
    LTE Advanced will be worse because it switches the uplink to OFDMA, which has a greater peak to average power ratio. I will be happy to have someone rebut this assertion, but there is no good reason to use LTE Advanced for voice. AJ
  4. WiWavelength
    EV-DO Rev B single carrier is likely just a software upgrade, as it adds in 64-QAM DRCs. But EV-DO Rev B multi carrier is a hardware upgrade, since the number of carrier channels is scalable, and those multiple carrier channels have to coordinate data throughput. AJ
  5. WiWavelength
    When it comes to phone upgrades, this is the sound of Robert in the Herron household: AJ
  6. WiWavelength
    A candid photo? I can do better than that. Here is a video clip: We will be expecting your PayPal donation shortly. AJ
  7. WiWavelength
    I have been following T-Mobile spectrum policy rather closely for the last year, ever since the merger started to dissolve and T-Mobile started to refarm PCS MHz spectrum. I have found no evidence thus far to indicate that T-Mobile will take out of service DC-HSPA+ 42 (which requires fully 20 MHz of contiguous spectrum) in any markets and reduce it to HSPA+ 21 (which requires only 10 MHz of spectrum). That said, T-Mobile may shift DC-HSPA+ from AWS to PCS in some markets, but that matters little, as all T-Mobile DC-HSPA+ capable devices also support W-CDMA band 2 (PCS). The other W-CDMA band 4 (AWS) only devices will be left at least one HSPA+ carrier in all markets for the next several years. And this will all still be quite the awkward juggling act for T-Mobile, as it has enough AWS spectrum for fully 15-20 MHz FDD LTE in some markets, for 10 MHz FDD LTE in some markets, for 5 MHz FDD LTE in some markets, and for no LTE in some markets. AJ
  8. WiWavelength
    ...and not the Twin Bells. AJ
  9. WiWavelength
    Part of SouthernLINC's rebanded spectrum is below ESMR but part of it is in ESMR, thus eating into Sprint's 14 MHz max allocation. AJ
  10. WiWavelength
    Off the top of my head, downlink modulation is QPSK, 16-QAM, or 64-QAM. Without looking at supporting data, I could not tell you the SINR threshold for each modulation scheme, but that data should be publicly available online. AJ
  11. WiWavelength
    PCS 1900 MHz is unaffected. Those international agreements are based on field strength at the international boundaries, not on narrowband channel coordination. And from personal experience, I have used native Sprint voice and data at my aunt's house roughly two miles into British Columbia. AJ
  12. WiWavelength
    To be clear, Sprint controls its usual full complement of 14 MHz of rebanded SMR 800 MHz spectrum in border markets. However, not all of that may be usable for LTE because of international channel coordination that is based on iDEN 25 kHz channelization. So, the issue in border markets is not lack of SMR 800 MHz spectrum but potential inability to use some of that spectrum without violating international agreements. AJ
  13. WiWavelength
    No, Sprint controls plenty of SMR 800 MHz spectrum in the Southeast, but not quite as much as the 7 MHz x 7 MHz that it controls across much of the country. For that reason, Sprint may deploy 3 MHz FDD LTE in Atlanta, Birmingham, etc. However, I am hopeful that SouthernLINC -- despite how omnipotent and omniscient the Southern Company reportedly is -- will see that it faces an iDEN dead end and will strike a spectrum sharing agreement with Sprint to deploy 5 MHz FDD LTE. AJ
  14. WiWavelength
    Robert will correct me if I am wrong, but most of the sites that cannot utilize RRUs are in high density urban areas, hence SMR 800 MHz propagation is fortunately less of a concern. AJ
  15. WiWavelength
    Agreed. Sometimes, you get the girl. Sometimes, you don't. Sometimes, your team wins. Sometimes, it doesn't. You can't always be first. At least every once in a while, you're at the back of the pack. That's life. Those are the breaks. Get used to it, folks. AJ
  16. WiWavelength
    I do not know how much time I will have today to contribute to this thread, but I appreciate its intent. Keep the exchange of information flowing as a learning/teaching exercise for everyone. AJ
  17. WiWavelength
    Scott, by posting only an isolated clip, you are depriving members of a greater overview of the cinematic landmark that is "Joe Dirt." AJ
  18. WiWavelength
    More cowbell? AJ
  19. WiWavelength
    Something similar happened a while back in another forum that I frequent. The response to being threatened was particularly well played: AJ
  20. WiWavelength
    To be clear, those peak speeds are possible on a 10 MHz FDD LTE carrier -- twice the bandwidth that Sprint is initially deploying. AJ
  21. WiWavelength
    Ahem, a Festivus miracle... AJ
  22. WiWavelength
    I would like to see some AAU backhaul. Put those Nike and Adidas sponsored traveling basketball teams to some real purpose. AJ
  23. WiWavelength
    Be thankful that sectors do "interfere" with one another. Though such is not entirely desirable, it is by design. If sectors did not overlap at all, then every cell would contain two or three several degree slices of no service. AJ
  24. WiWavelength
    Yeah, I believe I saw the same speed test. And that led me to conjecture that the Nexus 4 could be gimped by no MIMO, as that would limit it to roughly 18 Mbps downlink throughput on a 5 MHz FDD carrier. But none other than Howard Chui himself, of HowardForums fame, has demonstrated undeniably MIMO enhanced Nexus 4 LTE throughput: AJ
  25. WiWavelength
    Your SINR at home is 8 dB, which is very good for EV-DO. Over the river and through the wood to grandmother's house, your SINR is only 2 dB, which is just okay. I have to wonder -- based on your map -- if grandmother's house is very near the boundary between the N and SE facing sectors of the site. If so, interference from the N sector will degrade signal from the SE sector, which is almost assuredly the serving sector in question. As for Network Vision, it may improve signal strength. But such will also increase interference between sectors/sites, so any SINR improvement will likely be minimal. AJ
×
×
  • Create New...