Jump to content

WiWavelength

S4GRU Staff Member
 View Profile  See their activity

  • Posts

    18,133

  • Joined

  • Last visited

  • Days Won

    429

 Content Type 

Blog Entries posted by WiWavelength

  1. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, October 5, 2012 - 2:00 PM MDT
     
    Earlier this week, the Samsung SPH-L900 authorization filing hit the FCC OET (Office of Engineering and Technology) database. Judging by the handset's expansive 150 mm x 80 mm dimensions, S4GRU firmly expects this device to be the upcoming Sprint version of the Samsung Galaxy Note 2 "phablet." In keeping with our previous articles on the HTC EVO 4G LTE, Samsung Galaxy S3, Motorola Photon Q 4G, and yet to be released LG Eclipse, here is an RF focused breakdown of the presumed Note 2's FCC disclosed tech specs:
    CDMA1X + EV-DO band classes 0, 1, 10 (i.e. CDMA1X + EV-DO 850/1900/800)
    LTE band 25 (i.e. LTE 1900; PCS A-G blocks)
    LTE 5 MHz FDD carrier bandwidth
    LTE UE category 3
    W-CDMA/HSPA band 2 (i.e. W-CDMA/HSPA 1900)
    GSM/GPRS/EDGE 850/1900
    GPRS/EDGE multislot class 10 (i.e. max 4 downlink, 2 uplink, 5 total timeslots)
    802.11a/b/g/n Wi-Fi
    SVLTE support, including SVLTE and simultaneous Wi-Fi tether (2.4 GHz only)
    SVDO support absent
    Maximum RF ERP/EIRP: 20.03 dBm (CDMA1X/EV-DO 850), 24.46 dBm (CDMA1X/EV-DO 1900), 20.25 dBm (CDMA1X/EV-DO 800), 28.35 dBm (GSM 850), 25.05 dBm (EDGE 850), 29.44 dBm (GSM 1900), 24.13 dBm (EDGE 1900), 21.41 dBm (W-CDMA 1900), 19.63 dBm (LTE 1900)
    NFC antenna integrated into battery cover
    CDMA1X/EV-DO Rx antenna diversity
    Antenna locations: (see FCC OET diagram below)


     
    Besides the incorporation of GSM/GPRS/EDGE 850/1900 and W-CDMA/HSPA 1900 capabilities, the most notable feature of the Note 2 is the lack of SVDO capability. That absence appears to be related to the inclusion of W-CDMA/HSPA, which coexists on a transmit path with LTE. In typical SVDO capable handsets, CDMA1X/EV-DO has one transmit path, but EV-DO has a second possible transmit path that it shares with LTE. That is not the case with the Note 2, as can be seen in the antenna locations and simultaneous transmission paths diagrams:
     

     
    Within each transmission path, only one airlink can be active at any given time. This is a hardware restriction that precludes SVDO but allows SVLTE. Additionally, some other simultaneous transmission scenarios that are technically supported by the hardware (e.g. CDMA1X voice + W-CDMA data) are locked out in software. For all of the possible and permissible simultaneous transmission scenarios, see the included table from the FCC filing:
     

     
    In conclusion, if SVDO truly was sacrificed in order to include W-CDMA, that is a curious compromise, especially for a handset otherwise geared (e.g. band class 10 CDMA1X, band 25 LTE) specifically for Sprint.
     
    Source: FCC
  2. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Thursday, March 22, 2012 - 10:50 AM MDT
     
    Update 2: See below for potentially all SMR 800 MHz SIDs.
     
    Two weeks ago, S4GRU reported that the FCC had just issued a proposed rulemaking that would officially allow Sprint to launch non iDEN, wideband operations (CDMA1X and/or LTE) in its rebanded SMR 800 MHz spectrum. In that article, we referenced Sprint Network Vision internal documents that S4GRU used to determine where in the SMR 800 MHz band Sprint planned to deploy CDMA1X 800 carrier channel(s):
     
     
    Today, in an S4GRU exclusive, we bring you an intriguing follow up to that article.
     
    S4GRU has acquired internal Sprint Network Vision 3G plans for additional markets and confirmed that Sprint will necessarily deploy CDMA1X 800 on a higher carrier channel in those markets in which it shares the ESMR portion of the SMR 800 MHz band with SouthernLINC. Furthermore, Sprint will not reuse its existing PCS 1900 MHz network SIDs but instead will utilize a unique set of new SIDs for its SMR 800 MHz overlay. Both of these developments have important ramifications for band class 10 Sprint network acquisition and custom PRL editing.
     
    In most markets across the country, Sprint is not encumbered by any other ESMR licensees. In those markets, Sprint will deploy a CDMA1X Advanced carrier centered at channel 476. See the band plan graphic (modified for Sprint ESMR single licensee markets):
     

     
    However, in several markets in the Southeast, Sprint splits ESMR bandwidth with SouthernLINC. In those markets, SouthernLINC's spectrum holdings extend as high as 818 MHz x 863 MHz. As a result, Sprint has shifted its CDMA1X 800 carrier up 50 channels to be centered at channel 526 in order to stay out of the SouthernLINC allotment and provide adequate guard bands. See the band plan graphic (modified for Sprint/SouthernLINC ESMR dual licensee markets):
     

     
    For CDMA1X 800 network acquisition, therefore, Sprint band class 10 capable PRLs will have to include ACQ indices containing at least channels 476 and 526.
     
    Moreover, as S4GRU has unearthed, band class 10 PRLs will also have to include separate SID entries for SMR 800 MHz. For example, in the Dallas-Fort Worth market, Sprint has long used SID 04120, but CDMA1X 800 will fall under new SID 22407. In the Atlanta market, Sprint operates under SID 04274, while CDMA1X 800 will take on SID 22437. NIDs, though, appear to be consistent between PCS 1900 MHz and SMR 800 MHz. Expect Sprint to establish a second SID for each one of its markets, hence just under 50 new SMR 800 MHz SIDs in total.
     
    We surmise that Sprint will use the distinct new SIDs to control access and network loading on the lone CDMA1X 800 carrier channel in each market. By Sprint placing SMR 800 MHz SIDs at lower priority in PRLs, the vast majority of Sprint devices will remain on CDMA1X 1900 in almost all native coverage settings. Devices will seek out CDMA1X 800 only when CDMA1X 1900 is unusable or unavailable. Savvy PRL builders, however, could certainly take advantage of this situation by editing PRLs to invert priority and favor CDMA1X 800 instead, thereby directing devices to remain on SMR 800 MHz wherever possible.
     
    S4GRU will continue to dig up CDMA1X 800 SIDs for additional markets. As we do, we will post updates. So, stay tuned.
     
    Update: We have learned new SMR 800 MHz SIDs for several West Coast markets: San Francisco-Oakland-San Jose, Portland, and potentially Seattle or Spokane, too. In the Bay Area, Sprint's CDMA1X 1900 network uses SID 04183, while the upcoming CDMA1X 800 overlay will use SID 22431. Similarly, in Portland, Sprint will continue to utilize SID 04174 for PCS 1900 MHz and will add SID 22428 for SMR 800 MHz. Sprint in Seattle and Spokane uses SID 04186 and SID 04188, respectively. S4GRU has discovered SMR 800 MHz SID 22408 linked to rural parts of the Seattle and Spokane MTAs, but we are currently uncertain if this SID will apply to one or both actual metro areas.
     
    Update 2: Special thanks go to S4GRU reader and sponsor autoprime for reminding us of the IFAST national SID list web page, which just so happens to contain all of the SMR 800 MHz SIDs that we have announced, as well as ostensibly all of the other SMR 800 MHz SIDs for Sprint's remaining MTA based markets. The 224xx series SIDs were actually assigned to Sprint for its PCS G block nationwide collection of licenses, spectrum that was assigned to Nextel as compensation for SMR 800 MHz bandwidth it lost during the 800 MHz public safety rebanding effort. Sprint originally intended to deploy band class 14 CDMA1X/EV-DO in that PCS G block 10 MHz spectrum but now will use it exclusively for band class 25 LTE (5 MHz x 5 MHz), the initial LTE carrier that Sprint will launch in its Network Vision initiative. Since band class 14 CDMA1X/EV-DO is now off the table, Sprint appears to have carried over the 224xx series SIDs to its SMR 800 MHz band class 10 CDMA1X deployment. Keep in mind, however, that these remaining SIDs have yet to be verified, so there may be some differences between the list and actual use. S4GRU will endeavor to confirm additional SIDs as we analyze further information from our internal Sprint sources. In the meantime, we have condensed all assigned 224xx SIDs to this Google Docs spreadsheet.
     
    Sources: Sprint, SouthernLINC, FCC, 3GPP, author's graphics, autoprime, IFAST
  3. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, August 10, 2012 - 6:54 PM MDT
     
    Update: The previously dubbed LG Eclipse is being released November 11 as the Optimus G. Additionally, the LTE 1900 EIRP figures that were missing from the original FCC filing were added six weeks later in a Class II Permissive Change application. Max LTE 1900 EIRP is 23.51 dBm -- though with substantial variability (up to 4.5 dB) due to differences in carrier frequency, bandwidth, and modulation (QPSK/16-QAM). Furthermore, CDMA1X/EV-DO 800 max ERP has been increased by approximately 2 dB to 23.17 dBm.
     
    To quote the inimitable Yogi Berra, "It's déjà vu all over again." And here we go again. S4GRU is happy to announce yet another breakdown of an FCC OET (Office of Engineering and Technology) authorization filing for a major device headed to Sprint's upcoming Network Vision enhanced LTE overlay. Since this spring, we have analyzed the FCC authorizations for the HTC EVO 4G LTE, Samsung Galaxy S3, and yet to be released Motorola Photon Q 4G. Today, the expected LG Eclipse 4G hit the FCC database under the model number LG LS970, and here are the RF facets that we have been able to glean:
    CDMA1X + EV-DO band classes 0, 1, 10 (i.e. CDMA1X + EV-DO 850/1900/800) LTE band 25 (i.e. LTE 1900; PCS A-G blocks) LTE 5 MHz and 10 MHz carrier bandwidths 802.11a/b/g/n Wi-Fi; max MCS index 7 (i.e. 20 MHz channel, 400 ns guard interval, single spatial channel) SVLTE support, including SVLTE and simultaneous Wi-Fi tether SVDO support absent Maximum RF ERP/EIRP: 21.86 dBm (CDMA1X/EV-DO 850), 25.33 dBm (CDMA1X/EV-DO 1900), 21.68 dBm (CDMA1X/EV-DO 800) NFC antenna integrated into battery cover Antenna locations: (see FCC OET diagrams below)

     
    Notably missing from the presumed LG Eclipse's FCC filing are two things: SVDO capability and LTE band 25 EIRP test results.
    Rumor has it that the Eclipse will utilize Qualcomm's upcoming and highly anticipated APQ8064 quad core 28 nm "Krait" processor. The quad core difference is noteworthy compared to the dual core MSM8960 chipset that has proven very successful in the EVO LTE and Galaxy S3, et al. But the MSM8960 incorporates a multimode modem, while the APQ8064 is a naked processor. If rumor has it right, then the Eclipse will also have to utilize at least one separate modem chipset. And it would seem that LG has chosen at least one CDMA1X/EV-DO modem that is not capable of voice "Fusion," which would enable SVDO with a second modem. So, like its Viper predecessor, the Eclipse appears to be a multiple chipset design. But unlike the Viper, the Eclipse is absent SVDO.
    Furthermore, the FCC OET filing includes requisite CDMA1X + EV-DO 850/1900/800 ERP/EIRP figures but lacks LTE 1900 EIRP figures. So, do not hold your breath for a release date. We will leave it to other sources to speculate/report on the ergonomics and other technical attributes of the upcoming LG device. But we expect that LG and its authorized testing lab will have to file supplemental results before the supposed Eclipse makes its way into the hands of eager Sprint subscribers.
     
    Source: FCC
  4. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Thursday, September 3, 2015 - 3:28 AM MDT
     
    Ladies and gentlemen, C Spire has left the building. In Memphis. Or so it seems.
     
    Based on an FCC spectrum lease filing that came down the pike earlier this week, Cellular South dba C Spire has applied to lease all of its spectrum in Memphis to Sprint. S4GRU has not been able to confirm yet, but this almost certainly appears to signal a C Spire exit from Memphis -- its largest urban market into which it expanded just a few years ago.
     
    Disclaimer: the FCC ULS (Universal Licensing System) -- which is the parent database for all spectrum licenses and applications and is what I access directly to do spectrum research -- is down for a server migration over the Labor Day holiday weekend, not back online until sometime next week. In fact, the FCC ULS went offline right in the midst of my research a night ago. Fortunately, I was able to gather the relevant info on the Memphis spectrum to be leased to Sprint. However, the entirety of the transaction also involves Sprint leasing spectrum elsewhere back to C Spire -- more on that later. As more information becomes available, we will publish an update or a follow up, if warranted.
     
    In Memphis, the spectrum to be leased to Sprint is the PCS 1900 MHz C2 block 15 MHz (7.5 MHz FDD) and Lower 700 MHz A block 12 MHz (6 MHz FDD) licenses. From a CDMA2000 standpoint, the PCS would be band class 1 spectrum; the Lower 700 MHz is irrelevant for CDMA2000. For LTE, the PCS would be band 2 or band 25 spectrum, which Sprint would utilize as band 25, and the Lower 700 MHz would be band 12, which Sprint has not held in any other market. That last piece is a key point -- more on that later, too.
     
    At this point, S4GRU cannot definitively comment on C Spire's motivation to leave its largest market -- if that indeed is what is happening. Albeit, similar regional operator USCC faced struggles with expansion into Chicago and St. Louis, eventually closing down those markets and selling off spectrum to Sprint. Likely, that is what is happening in Memphis.
     
    Along possibly related lines, USCC faced spectrum constraints with launching LTE in Chicago and St. Louis, potentially rendering them dead end markets in the current LTE focused environment. From Spectrum Gateway's interactive map, we can see that UHF channel 51 presently conflicts with Lower 700 MHz A block deployment in Memphis. With its Lower 700 MHz A block license encumbered and decent but not large PCS spectrum holdings in Memphis, C Spire likely faced a difficult road to LTE there.
     
    S4GRU may try to seek official comment from C Spire on this matter. Presumably, though, C Spire will address the Memphis issue in the coming days, providing some clarity on the matter. If C Spire is truly exiting the Memphis market, it will have to notify its existing subscribers.
     
    All of that ambiguity aside, Sprint's motivation is clearly understandable. After the USCC transaction in Chicago and the Revol transaction in Cleveland and Indianapolis, Memphis is one of the last few top markets where Sprint holds only 20 MHz total of PCS A-F block spectrum -- even more dire, that 20 MHz in Memphis is broken up into two non contiguous 10 MHz (5 MHz FDD) blocks. Though a minimal amount of info has changed in the intervening years or decades since I did the pro bono work, you can view some of my Sprint spectrum documentation, including Memphis, in this spreadsheet, this map, and this spreadsheet.
     
    What that means presently for Sprint in Memphis is additional guard bands are required because of the interrupted spectrum blocks and no chance of LTE carrier bandwidth greater than 5 MHz FDD, nor any band 25 second carrier until after significant CDMA2000 thinning or shutdown. But this spectrum from C Spire changes everything.
     
    At the very least, Sprint will have increased its PCS A-F block Memphis spectrum holdings from just two non contiguous 10 MHz (5 MHz FDD) blocks to those two blocks plus another non contiguous 15 MHz (7.5 MHz FDD) block. A band 25 second carrier in Memphis is coming down the river.
     
    However, what I think -- and what other S4GRU staff members have independently concurred -- is that Sprint will swap this C Spire spectrum with AT&T.
     
    First, the spectrum lease application with C Spire is for a long term, de facto transfer lease. We could be wrong, but this lease smacks of a prelude to a full sale of C Spire spectrum licenses in Memphis to Sprint. In that case, Sprint would have options to rearrange its position in the PCS band plan. Primarily, both Sprint and AT&T would be advantaged to swap their PCS C1 and PCS C2 blocks for greater contiguity for both parties. Continue reading.
     
    Just as S4GRU documented in the Columbus, OH market a month ago, the PCS G block LTE 5 MHz FDD carrier probably would be redeployed as a 10 MHz FDD carrier bridged across portions of the PCS C block and PCS G block. That still would leave room in the potentially acquired spectrum for up to two additional CDMA2000 carriers, which would replace two of the three CDMA2000 carriers lost in the PCS D block or PCS B5 block, one of which would be refarmed for an LTE 5 MHz FDD carrier to ensure continued LTE access to any early band 25 devices that do not support LTE in anything but 5 MHz FDD -- the same process that we saw in Columbus.
     
    For illustration of the present, post transaction, and possible PCS spectrum future in Memphis, see this S4GRU graphic:
     

     
    Other possibilities exist for Sprint and AT&T spectrum "horse trading" in Memphis -- such as Sprint getting the AT&T PCS F block in exchange for effectively returning to AT&T the PCS B5 disaggregation that Sprint acquired from AT&T predecessor AT&TWS in a spectrum transaction over a decade ago. But those other spectrum transaction possibilities would be more disruptive to current service, so I and other S4GRU staff do not think those band plan rearrangements likely in the near future.
     
    To start to wrap matters up for now -- but probably to be continued later -- that Memphis BEA Lower 700 MHz A block is the proverbial elephant in the room. As noted earlier, that is band 12 spectrum. And Sprint now has plenty of band 12 compatible devices previously released, currently available, or upcoming. Indeed, band 12 is part of the CCA/RRPP device procurement plan.
     
    However, we do not expect Sprint to deploy band 12 in Memphis. The Lower 700 MHz A block is not immediately compatible with Sprint's Network Vision infrastructure, and it is currently encumbered by adjacent UHF broadcasting. If, as S4GRU expects, a full spectrum transfer ultimately results from this Memphis spectrum lease, then look for Sprint to flip the Lower 700 MHz A block license to T-Mobile, which has shown its motivation and money to get UHF channel 51 broadcasters relocated -- or paid to accept some adjacent channel interference.
     
    As an exchange for that low band spectrum -- which T-Mobile has now started to value so greatly -- Sprint could gain some of the excess T-Mobile-Metro PCS spectrum that S4GRU pointed out almost three years ago, shoring up Sprint's PCS A-F block 20 MHz holdings in the likes of important markets San Francisco, Atlanta, or Miami.
     
    To return to and conclude with C Spire, our article starter, we cannot precisely document what SMR 800 MHz, PCS 1900 MHz, and/or BRS/EBS 2600 MHz spectrum C Spire will lease from Sprint. Because the FCC ULS frustratingly is out of commission for several more days. Cursory examination when the leases were still accessible online, though, did not indicate any major markets. Rather, this could be tied in with a CCA/RRPP agreement to expand Sprint coverage -- since C Spire infrastructure and handsets typically do not support band 26 nor band 41.
     
    So, the real prize in this transaction is spectrum in Memphis. My apologies to Marc Cohn for ham handedly paraphrasing his 1990s ballad, but it is also all too fitting…in those blue suede shoes...
     
    Leasing in Memphis -- leasing in Memphis
    Sprint's getting PCS on and off of Beale
    Leasing in Memphis -- leasing in Memphis
    How does that really make you feel?
     
    https://www.youtube.com/watch?v=KK5YGWS5H84
     
    Sources: FCC, Marc Cohn
  5. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Tuesday, July 3, 2012 - 2:54 PM MDT
     
    S4GRU continues with the third in a series of short articles on the FCC OET (Office of Engineering and Technology) authorization filings for "tentpole" devices headed to Sprint's upcoming Network Vision enhanced LTE overlay. Over the past few months, we have brought you the scoop on the FCC authorizations for the HTC EVO 4G LTE and the Samsung Galaxy S3. Today, the Motorola model number XT897 hits the FCC OET database with FCC ID IHDT56NL2, and we expect this mystery handset ultimately to be the Photon Q. Without further ado, here is the RF rundown:
     
    CDMA1X + EV-DO band classes 0, 1, 10 (i.e. CDMA1X + EV-DO 850/1900/800) LTE band 25 (i.e. LTE 1900; PCS A-G blocks) LTE 5 MHz and 10 MHz carrier bandwidths world phone international roaming capability 802.11b/g/n Wi-Fi; max MCS index 7 (i.e. 20 MHz channel, 400 ns guard interval, single spatial channel) SVDO and SVLTE support, including SVDO or SVLTE and simultaneous Wi-Fi tether Maximum RF ERP/EIRP: 22.45 dBm (CDMA1X 850), 19.89 dBm (EV-DO 850), 27.12 dBm (CDMA1X 1900), 24.03 dBm (EV-DO 1900), 21.72 dBm (CDMA1X 800), 19.33 dBm (EV-DO 800), 25.22 dBm (LTE 1900) NFC capability Antenna locations: CDMA1X bottom, EV-DO/LTE top, Wi-Fi/Bluetooth bottom  
    The Photon Q's FCC filing makes mention of world phone international roaming capability, albeit latent inside the handset. Presumably, it will include at least GSM 900/1800 and W-CDMA 900/2100+1900 (a la the international roaming capabilities announced to be unlocked in several VZW handsets). But, before anyone asks, do not expect any LTE international roaming capability.
    RF uplink output looks to be healthy. It is generally a bit higher than what we have seen recently from the EVO LTE and Galaxy S3.
    However, unlike the EVO LTE and Galaxy S3, the Photon Q lacks 802.11a/n Wi-Fi 5 GHz band capability. The filing indicates that the hardware is present, but 5 GHz operation is locked out. So, the Photon Q will be stuck in the increasingly overcrowded 2.4 GHz band.
    At this point, the LTE UE category remains unknown. Recent Motorola RAZR LTE handsets on VZW have used Moto's own Wrigley LTE baseband chipset, which has limited those devices to LTE UE category 2. We hope that the Photon Q will utilize the Qualcomm MSM8960 as a single chipset modem, as that should enable UE category 3.
    Perhaps the most interesting and potentially controversial aspect of the Photon Q's FCC authorization is the inclusion of two references to the Motorola Admiral, a front facing QWERTY handset currently available on Sprint. One reference cites the Admiral as a "similar transmitter;" the other reference flat out calls the Photon Q the Admiral. Thus, while some sites have leaked photos of what purports to be the Photon Q in the expected QWERTY slider design, we leave open the possibility, however modest, that the Photon Q may arrive as an LTE refreshed Admiral clone with a front facing QWERTY keyboard.
     

     
    Sources: FCC
  6. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, November 14, 2014 - 7:46 AM MST
     
    'Tis the season for turkey and tablets, pumpkin pie and "phablets." So, whet your appetites, and get ready for a movable feast -- or should I say, a mobile feast.
     
    Welcome to the first annual S4GRU holiday shopping guide. This may be nothing more than a one year tradition. We shall see. But we have definitely fallen behind this fall on publishing articles following FCC OET (Office of Engineering and Technology) authorizations of notable devices headed to or at least compatible with the Sprint network.
     
    Playing catch up, here is a quick rundown on the RF capabilities of the Motorola Nexus 6, Samsung Galaxy Edge, and cellular variant HTC Nexus 9 -- all of which have passed through the FCC OET and been released in the past few weeks or are to be released in the next few weeks.
     
    Not the purview of S4GRU, but all of the processor, RAM, screen resolution, and other specs are already out there on the Interwebs. If you need that info, refer to those sources. Thus, these brief looks at two "phablets" and one cellular tablet will be focused on their tested/projected RF performance -- particularly as that pertains to the Sprint network.
     
    To begin, the Motorola Nexus 6 ends up being the first fully CCA/RRPP compliant LTE handset -- supporting domestic LTE bands 2/4/5/12/25/26/41 -- and, for good measure, adding in LTE bands 7/13/17 for use in Canada, on VZW, and on AT&T. S4GRU first reported that CCA/RRPP band abundance of the supposed Sprint variant 2014 Motorola X a few months ago, but for unknown reasons, that handset never saw the light of day after it passed through the FCC OET. Its Motorola brother, which suffers from the hormonal disorder gigantism, though, picks up that slack and then some.
     
    Yes, the Nexus 6 represents a gigantic increase in size and price -- a curious decision if there ever was one. But it does appear to hold up its very large end of the bargain in RF prowess, maxing out in the roughly the 20-26 dBm range across all supported LTE bands. That is pretty good performance, particularly for band 41, which appears to enjoy an approximately 3 dBi antenna gain. This projects to be the strong performer that many had hoped for based on Motorola's RF reputation.
     
    Next up, the Samsung Galaxy Edge is truly on the cutting edge. And that refers not to just its curvy edged screen form factor. It is the first North American handset to support band 41 carrier aggregation. See the FCC OET filing table below:
     

     
    In fact, it is the first North American handset known to support LTE TDD carrier aggregation and intra band LTE carrier aggregation -- rather than inter band carrier aggregation, as we have seen in several AT&T variant handsets this year. That said, it is limited to two carrier aggregation with a maximum total bandwidth of 40 MHz TDD. Three carrier aggregation devices with a maximum total bandwidth of 60 MHz TDD will not make an appearance until sometime next year.
     
    And that is basically the good news. The rest of the news is not as good. The Galaxy Edge supports none of the additional CCA/RRPP bands -- not even bands 2/5, which are just subsets of bands 25/26, respectively. Moreover, the LTE ERP/EIRP is not very impressive. Fortunately, it looks hardly as poor in that regard as last year's VZW variant Galaxy Note 3 -- maybe the worst that we have ever seen in a flagship caliber smartphone -- but it averages just 17-20 dBm max output across bands 25/26/41. And, for reference, that runs about 2-3 dB worse than that of its recent Sprint variant Galaxy Note 4 sibling.
     
    The news could be worse, however. To conclude, just look at the cellular variant HTC Nexus 9 tablet. On the bright side, it, too, is a fully CCA/RRPP compliant device -- bands 2/4/5/12/25/26/41 -- also adding bands 7/13/17 like its Nexus 6 cousin. That band 12 tablet inclusion trumps even all Apple iPads for likely the next year. But the bright side does not extend beyond that in terms of actual RF.
     
    Originally, Google proclaimed the Nexus 9 to be a 3GPP/3GPP2 device. Since then, Google has pared that back to a 3GPP only device -- with the odd inclusion of EV-DO. The latter is almost assuredly yet another proofreading error, as the FCC OET authorization docs show no support for 3GPP2. Furthermore, reports are that the Nexus 9 uses a non Qualcomm baseband modem. Not good -- especially for a device that now rivals the iPad in price.
     
    For those who want the shorthand explanation, the cellular variant Nexus 9 looks to be compatible with Sprint -- but only Sprint LTE. It will have no support for Sprint CDMA2000. Additionally, the ERP/EIRP leaves much, much to be desired, averaging only 15-19 dBm maximum across all LTE bands. We generally expect more from antenna design in tablets because of their added size. However, that is certainly not the case with the Nexus 9.
     
    In summation, if you are making your shopping list, checking it twice, everything new in the Sprint stocking this holiday season is at least partly naughty, nothing entirely nice. Too big, too expensive, too focused on form over function, and/or too weak RF. Take your pick.
     
    Happy Thanksgiving? Or Bah Humbug?
     
    Source: FCC
  7. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, August 17, 2012 - 1:14 PM MDT
     
    CDMA1X and EV-DO carrier channels are shared resources. In CDMA1X, many subscribers share the same carrier channel, their individual traffic kept theoretically orthogonal by code division. Likewise, in EV-DO, individual traffic is separated by time division. But what happens when Sprint (or any other CDMA2000 network provider) has deployed greater than one CDMA1X and/or EV-DO carrier channel on a given cell site? How does your handset determine which carrier channel to utilize?
    You might like to think that your handset would automatically choose the least loaded CDMA1X and/or EV-DO carrier channel. But that is not really the case. Instead, when multiple carrier channels are available, each cell site broadcasts a channel list message of the available carrier channels on that site. Upon receiving this list of multiple carrier channels, each handset then invokes a hashing algorithm to select which carrier channel to use. Think of it like a multi lane highway, but each car must choose a particular lane based on the car's license plate number.
    For CDMA1X, the hashing algorithm -- which is a kind of pseudo random number generator -- is seeded with the handset's ESN or the subscriber's MDN/MSID (i.e. phone number). Unless the subscriber changes devices or phone numbers, these values remain static, hence the carrier channel hash is quite predictable. And Sprint, for reference, seems to use MDN/MSID based hashing. Nearly a decade ago, I built a spreadsheet that emulates the CDMA1X hashing algorithm, downloadable as an XLS file.
    However, for EV-DO, the carrier channel hash is not quite so outwardly predictable. To seed the hashing algorithm, EV-DO uses a session number, which obviously varies from data session to data session. Each time that a handset powers up, crosses a SID/NID boundary, or even toggles airplane mode, for example, generates a new EV-DO data session, hence a new session number. And it is this session number that determines the output of the hashing algorithm.
    To demonstrate this process, I positioned myself in one location about a quarter of a mile distant from the north sector of a local cell site. Over the course of several minutes, I grabbed three screen caps of the EV-DO engineering screen on one of my handsets. In between each screen cap, I cycled airplane mode at least once, each cycle generating a new data session. In the span of four minutes, I was able to get my handset to hash to each of the three EV-DO carrier channels deployed on this site. When I arrived at the site, my handset hashed to PCS 0175, which is the third EV-DO carrier channel (F3) in the channel list message. The second and third hashes after toggling airplane mode several times were to PCS 0150 (F2) and to PCS 0100 (F1). See the Channel Number field depicted in the screen caps:
     

    In addition, here is a raw RF look with a spectrum analyzer at the seven CDMA2000 carrier channels deployed on this cell site sector:

    The four CDMA1X carrier channels are PCS 0050, PCS 0075, PCS 0125, and PCS 0200. As is oft the case, the three aforementioned EV-DO carrier channels -- PCS 0100, PCS 0150, PCS 0175 -- are distinguishable by their slightly higher RF power output. Furthermore, for those curious, PCS 0025 (at the far left of the graph) and PCS 0225, PCS 0250, and PCS 0275 (at the right of the graph) are fallow spectrum on this site. If deployed, PCS 0025 would be the next EV-DO carrier channel (F4), PCS 0275 the final EV-DO carrier channel (F5), while PCS 0225 and PCS 0250 would be additional CDMA1X carrier channels.
    Back to the hashing algorithm, while it attempts to distribute users more or less evenly among available EV-DO carrier channels, it does not take into account several other factors, such as loading and backhaul. For example, if you are stuck on a carrier channel and sector with a few data hogs who have stronger signal than you do, your data speeds will likely suffer as the "fair and proportional" scheduler integral to the EV-DO airlink attempts to maximize total throughput by allocating greater time slots to the users with better signal quality. Additionally, backhaul may not be distributed evenly among deployed carrier channels, so it is possible that some carrier channels may have inherently greater data capacity than others do.
    Another benefit of rehashing to a different carrier channel is that you may be able to connect to a closer cell site. Because not all cell sites have the same number of deployed EV-DO carrier channels, carrier channel hashing is an imperfect process. To illustrate, the cell site (call it cell site "A") that I detailed above for this trial has three EV-DO carrier channels (F1, F2, F3), as duly noted. But the adjacent cell site to the north (call it cell site "B") has only two EV-DO carrier channels (F1, F2). A handset that hashes to F3 on cell site "A" will cling to carrier channel PCS 0175 even as it moves north well into the coverage area of cell site "B." Interference will not be a problem, as cell site "B" does not transmit PCS 0175, but signal strength (and data speeds) will diminish until cell site "A" drops below a network defined threshold, at which point the handset will handoff to cell site "B" and hash to PCS 0150. This can require substantial movement and/or time. So, if you always want the most crisp EV-DO handoffs, you can try to ensure that your handset always hashes to F1, the EV-DO carrier deployed on essentially every site in the market.
    To conclude, by no means is airplane mode a panacea for slow 3G data ills. EV-DO carrier channel deployment and backhaul can vary from site to site, while loading can also vary from site to site, even from minute to minute. And EV-DO networks in some cities are just generally overloaded. But if you are at work, in a restaurant, at a park, etc., and find yourself with unbearably slow 3G data or lower than usual signal strength for that location, try toggling airplane mode. A 30 second on/off cycle of airplane mode will start a new data session and could get your handset to rehash to another EV-DO carrier channel that is on a closer site, has better backhaul, and/or is currently less loaded.
     
    Sources: Qualcomm, author's field data
  8. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, March 9, 2012 - 1:15 PM MST
     
    Sprint may soon be gaining some clarity regarding its Network Vision plans to deploy CDMA1X Advanced to replace Nextel iDEN in its rebanded SMR 800 MHz spectrum. The FCC today announced a proposed rulemaking that would explicitly allow SMR 800 MHz licensees (e.g. Sprint, SouthernLINC, and a few others) to utilize greater than 25 kHz channel spacing.
     
    Currently, Part 90 SMR 800 MHz rules and regulations could be interpreted to prohibit channel spacing exceeding 25 kHz, effectively disallowing any airlink other than iDEN, which is designed to operate in 25 kHz channelization. Meanwhile, Sprint has petitioned that Part 90 does not automatically bar larger channel bandwidths in contiguous channel blocks and that it has enacted improved filtering techniques to satisfy out of band emissions concerns due to wideband operations.
     
    To reconcile the current rules and regulations with Sprint's contentions, the proposed rulemaking would amend Part 90 as follows:
     
     
    More simply put, Sprint would be able to use its lower band SMR 800 MHz spectrum below 821 MHz x 866 MHz right away to deploy CDMA1X and/or LTE. Then, after all public safety relocation in a region has been completed, Sprint could utilize its upper band SMR 800 MHz spectrum 821-824 MHz x 866-869 MHz for further wideband operations.
     
    The proposed rulemaking aligns with and helps to explain Sprint Network Vision 3G plans that S4GRU has obtained. Those plans indicate that Sprint intends to deploy at least one CDMA1X Advanced band class 10 carrier channel centered at channel 476 (817.9 MHz x 862.9 MHz) and/or channel 526 (819.15 MHz x 864.15 MHz). This would place one or both CDMA1X carrier(s) within the lower band 817-820 MHz x 862-865 MHz spectrum and leave >1 MHz guard bands between it and 821-824 MHz x 866-869 MHz spectrum, in which public safety reconfiguration is still ongoing in some regions.
     
    To illustrate how Sprint proposes to roll out CDMA1X 800 at the lower end of its SMR 800 MHz spectrum allotment, see our band plan and channel assignment graphic:
     

     
    Sources: FCC, Sprint, author's graphic
  9. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Wednesday, October 24, 2012 - 12:05 PM MDT
     
    Over the past six months, Apple's iPad 3 has racked up millions of sales, yet Google's (and Asus') Nexus 7 and Microsoft's Surface tablets have grabbed the headlines over the summer and into the fall. Yesterday, Apple struck back by not only rolling out iPad 4 the same year as iPad 3 but also introducing the long rumored iPad mini. S4GRU readers will recall that Sprint was left out of the iPad 3 sweepstakes, Sprint's nascent LTE network making its debut a few months after iPad 3's announcement. Certainly, some will bemoan that iPad 3 has been replaced in only half the usual yearly upgrade cycle, but Sprint users definitely benefit, as Sprint is fully in the fold this time with LTE support on the VZW/Sprint/global versions of both iPad 4 (A1960) and iPad mini (A1955).
    As soon as Apple's announcement event concluded yesterday, authorization filings for the new Sprint compatible iPads (iPad 4, iPad mini) started popping up in the FCC OET (Office of Engineering and Technology) database. So, joining our series of articles on on the HTC EVO 4G LTE, Samsung Galaxy S3, Motorola Photon Q 4G, and soon to be released LG Eclipse and Samsung Galaxy Note 2 is an RF capability focused look at Sprint's first two iPads:
    CDMA1X/EV-DO band classes 0, 1, 10 (i.e. CDMA1X/EV-DO 850/1900/800) EV-DO Rev B Multi Carrier (i.e. 2xEV-DO, 3xEV-DO) LTE bands 1, 3, 5, 13, 25 (i.e. LTE 2100+1900/1800/850/750/1900) LTE 1900 1.4/3/5/10/15/20 MHz FDD carrier bandwidths W-CDMA bands 1, 2, 5, 8 (i.e. W-CDMA 2100+1900/1900/850/900) DC-HSPA+ (i.e. Dual Carrier) GSM/GPRS/EDGE 850/900/1800/1900 802.11a/b/g/n Wi-Fi Wi-Fi hotspot (2.4 GHz only) support for all cellular airlinks Maximum RF ERP/EIRP (iPad 4): 23.10 dBm (CDMA1X 850), 22.90 dBm (EV-DO 850), 30.12 dBm (CDMA1X 1900), 29.08 dBm (EV-DO 1900), 23.30 dBm (CDMA1X 800), 23.40 dBm (EV-DO 800), 29.78 dBm (LTE 1900) Antenna gain (iPad 4): -1.58 dBi (Cellular 850 MHz), 2.44 dBi (PCS 1900 MHz), -2.24 dBi (SMR 800 MHz) Antenna locations (iPad 4): (see FCC OET diagram below)
    The inclusion of EV-DO Rev B Multi Carrier and the imposed limitations -- Cellular 850 MHz only, no 64-QAM -- are a bit curious. But these limitations will have no ramifications for use in North America, where EV-DO Rev B has not been deployed. All told, though, both iPad 4 and iPad mini look to be solid RF performers. Not surprisingly, since they share the same Qualcomm MDM9615 modem with iPhone 5, both iPads carry over basically the same airlink capabilities from the Sprint compatible iPhone 5 -- see S4GRU writer Ian Littman's article. And it should be noted that iPad mini, despite its diminutive size, does not lag behind its larger sibling. All ERP/EIRP figures are within ~1 dB between both iPads. In fact, for both EV-DO 1900 and LTE 1900 maximum EIRP, iPad mini trumps iPad 4 by ~0.5 dB. Furthermore, both iPads in their high ERP/EIRP outputs are less like power and size constrained handsets, more like mobile hotspots. Indeed, both iPads appear to be very capable hotspot devices.
     
    Sources: FCC, Apple
  10. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, August 19, 2016 - 2:04 AM MDT
     
    Earlier this week, the two HTC 2016 Nexus handsets -- codenamed "Marlin" and "Sailfish" -- were caught in the net of the FCC OET (Office of Engineering and Technology) authorization database.
     
    While Google has yet to reveal them officially as Nexus handsets, that HTC is the manufacturer of choice this year has been a heavily leaked secret the past few months. And the circumstantial evidence now is overwhelming.
     
    The FCC grantee code, NM8G, appends a "G" to the usual NM8 grantee code for HTC branded devices, and the user manual declaration document posits that the final draft manual will be available publicly on the Google web site in the Nexus support section. Neither handset has been identified or named individually, though the 2PW4100 likely is the larger "Marlin," the 2PW2100, the smaller "Sailfish."
     
    Both are at least the domestic variants with airlink support across the board for VZW, AT&T, T-Mobile, and Sprint. No international variants have passed through the FCC OET. Unless international variants do get authorized in the coming days/weeks, the two HTC Nexus handsets could end up in uncharted waters as single variants for the world, covering all supported international LTE bands, too. Full disclosure, however, probably will have to wait until the Google announcement event when accompanying tech specs are published.
     
    In the meantime, the domestic RF uplink test results and declarations are out in the world. S4GRU will not run down every last RF capability. But, just to confirm, some of the highlights are...
    LTE bands 2/4/5/7/12/13/17/25/26/29/30/41 VoLTE bands 2/4/5/12/13 (for VZW, AT&T, and T-Mobile) Downlink 2x/3x CA Dual, switched WWAN Tx antennas 0 and 1, bottom and top 802.11ac 2x MIMO The primary purpose of this article is to present a retrospective on the uplink RF powers of the current 2013-2016 era of 3GPP/3GPP2, Sprint compatible Nexus handsets as well as two recent HTC handsets. Those domestic variant Nexus handsets and the Sprint variant HTC One A9 and HTC 10 are the RF and design forebears of the 2016 Nexus handsets. So, how do the new kids on the block hold up to their predecessors?
     
    S4GRU culled relevant data across all eight handsets from thousands of pages of authorization documents in the FCC OET. For the radiated power figures, the usual clauses about lab testing versus real world performance and uplink versus downlink always apply. The figures represent best averaged and rounded estimates of maximum uplink ERP/EIRP test results provided to the FCC OET in the authorization filings for the domestic variant Nexus devices and Sprint variant HTC devices. See below:
     

     
    The numbers can speak for themselves. The LG, Motorola, and Huawei manufactured handsets generally are more powerful. The HTC handsets are not blatantly deficient -- though the One A9 comes uncomfortably close -- but the 2016 Nexus do spec out typically average or slightly below.
     
    Source: FCC
  11. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, May 8, 2015 - 12:15 PM MDT
     
    Update: A week after the Sprint variant LG G4 original authorization documents were released at the FCC OET and S4GRU published this RF performance article, a Class II Permissive Change filing was added to the G4's docket. In writing the article last week, we did not detect anything amiss with the original filing, so this represents an optional change, which the filing discloses as hardware modification affecting the main antenna. Interestingly, none of the previous antenna gain figures have been altered, but the ERP/EIRP figures have increased or decreased. See the smoothed and averaged differences below:
    Band class 0: -1 dB Band class 10: -2 dB Band 4: -3 dB Band 5: -2 dB Band 12: -2 dB Band 26: -2 dB Band 41: +2 dB So, you win some, you lose some. Overall, the Sprint variant G4 has become weaker in tested RF performance. Those negative differences, however, are limited mostly to lower frequencies in the 700-1700 MHz range. The 1900 MHz range is unaffected, and the 2600 MHz range is increased. The other win is that a Class II filing before a device is released generally means that release is imminent. Look for the G4 on shelves and online soon.
     
    Yes, I know it is no longer May 4th. And we are not in a Samsung Galaxy far, far away. But this is episode IV in the LG G handset series, just four days removed from May 4th. That should be enough of the number four to satisfy anyone. Even if this isn't the Motorola Droid you're looking for, is the LG G4 a new hope for a flagship Sprint handset this spring?
     
    S4GRU staff has been watching the FCC OET (Office of Engineering and Technology) authorization database over the past week as different G4 variants were revealed. The VZW variant came earlier in the week, and the Sprint variant ZNFLS991 documents were uploaded yesterday. Of course, we are going to write an article about it, so let us get started.
     
    Right away, the G4 adheres to what has become the standard Sprint variant configuration: tri band LTE, non SVLTE, single RF path with e/CSFB. Additionally, it covers the CCA/RRPP LTE bands. And it was tested for domestic GSM/W-CDMA bands -- phone unlockers rejoice. Finally, it does officially support downlink carrier aggregation as its lone Release 10 feature. More on CA later.
     
    Next, it is fairly well known and somewhat controversial that the G4 opted not for the top of the line Qualcomm Snapdragon 810 but for the lesser Snapdragon 808, taking some performance hits in graphics and memory departments, for example. S4GRU does not involve itself in that debate -- that is not the place of this cellular RF focused article. But the chipset choice is relevant because both the Snapdragon 808 and Snapdragon 810 incorporate the same Category 9 X10 LTE baseband on die. So, rest assured, the choice of the Snapdragon 808 does not lessen any RF capabilities.
     
    On that topic, if you need a refresher on the new Qualcomm LTE baseband naming/numbering scheme, see this sidebar from our earlier article on the HTC One M9 and Samsung Galaxy S6:
     
     
    Back to discussion of CA support, we have stated previously that FCC OET authorization filings are not required to disclose downlink CA -- because that is only reception, not transmission. But the G4 filing does include an explicit attestation letter, stating its inclusion of downlink CA. What the G4 filing does not divulge is specifically 2x or 3x downlink CA support in band 41. For various reasons, S4GRU believes the former, that the G4 is capable of band 41 2x CA.
     
    First, the Snapdragon X10 LTE baseband natively supports up to 60 MHz of 3x downlink CA. However, that requires some help. An RF transceiver sits ahead of the baseband, and presently, the Qualcomm WTR3925 can handle 2x CA -- but 3x CA necessitates the inclusion of a second transceiver. See this excerpt from an AnandTech article on the new Snapdragon chipsets:
     
     
    Moreover, the other G4 variants that support CA are explicitly limited to 2x CA, suggesting that all variants are using the single WTR3925 transceiver. This is all educated conjecture, barring a teardown of the Sprint variant that probably will never happen. But if you are waiting on 3x CA, that likely will require a next generation Qualcomm transceiver to do 3x CA all in one.
     
    Finally, straight from the horse's mouth, Sprint CTO Stephen Bye stated the following in a recent FierceWireless article:
     
     
    Now, honestly, most read our FCC OET authorization articles for ERP/EIRP figures and analysis. So, without further ado, here are the numbers:
    Band class 0: 22 dBm Band class 1: 26 dBm Band class 10: 23 dBm Band 2: 25 dBm Band 4: 24 dBm Band 5: 22 dBm Band 12: 17 dBm Band 25: 25 dBm Band 26: 22 dBm Band 41: 23 dBm For reference, the above figures represent our best averaged and rounded estimates of max uplink ERP/EIRP -- with uniquely Sprint frequencies receiving heavier weighting, if possible, in band class 10, band 25, and band 26. Of course, the usual disclaimers about lab testing versus real world performance apply.
     
    As for analysis, max RF output looks quite healthy across the board, comparing very favorably with that of the One M9 and soundly thrashing that of the disappointing Galaxy S6. In particular, the power output for CDMA2000 band classes is a good 3 dB higher than most.
     
    Note, if you are using the smart cover for wireless charging, though, ERP/EIRP is affected roughly -1 dB across the board. I am not a fan of wireless charging because of the power inefficiency involved, but the RF loss from the smart cover on the G4 appears considerably less than what we have seen from some previous handsets.
     
    If there is any caveat about the G4's RF capabilities, that would be its antenna gain, broken down by frequency range as follows:
    700 MHz: -5.9 dBi 800 MHz: -7.1 dBi 1700 MHz: -5.2 dBi 1900 MHz: -3.5 dBi 2600 MHz: 1.7 dBi Except for 2600 MHz, all are negative, significantly negative. And for comparison, again except for 2600 MHz, the VZW variant antenna gain in all bands tracks about 3 dB higher. The head scratcher, however, is that the lab performance between the two variants is remarkably similar, despite the differences in antenna gain.
     
    We have seen something like this before -- an LG handset that showed strong lab power output yet weak real world performance. Remember the LG Viper? That is the challenge in interpreting lab results. Low output always indicates weak performance. However, high output can be a mixed bag. But LG has a pretty good Sprint track record since the Viper, as the LG Optimus G, LG G2, and LG G3 were all at least average to good in the real world. And the LG manufactured Nexus 5 was practically a Jedi knight for its RF performance at the time.
     
    In the end, only many trials on Dagobah will tell if the G4 lives up to its powerful promise. Use the 4th, LG, use the 4th.
     
    Source: FCC, AnandTech, FierceWireless
  12. WiWavelength
    by Josh McDaniel
    Sprint 4G Rollout Updates
    Thursday, May 2, 2013 - 9:35 AM MDT
     
    Last year, LG released a mid-range device that made its way from one CDMA carrier to another. This year appears to be no exception. The LG LG870 recently passed through the FCC OET (Office of Engineering and Technology) with Sprint LTE and band 10 CDMA2000 on board.
    If the LG Viper (LS840) last year is any indication, it was released as the Connect (MS840) on MetroPCS, and then as the Lucid (VS840) on Verizon before it came to Sprint. In January of this year, MetroPCS released the Spirit (MS870), and earlier this month, Verizon released the Lucid 2 (VS870). Now, it seems to be Sprint’s turn again.
    However, it currently appears that Sprint is releasing this handset on its Boost brand under the codename FX1, as the model number is LG870, not LS870. (As of now, the name and that it may be released only on Boost has not been confirmed.) But all previous Sprint LG phones from last year have model numbers beginning with LS.
    The Bluetooth 4.0 profile supports HSP, HFP 1.6, A2DP, AVRCP 1.3, OPP, FTP, PBAP, SPP, HID, GAVDP, SDAP, PAN, and MAP, according to the Bluetooth SIG, which also lists the phone as “(LG870 (for Sprint/Wholesale)).” Sprint wholesale partner Ting, anyone?
    As for specs, if this phone is like its 870 model counterparts, it will have a 1.2 GHz dual core processor (possibly Qualcomm Snapdragon S4 Plus MSM8960) with 1 GB RAM, 5 MP rear camera with 1080p HD video recording, and 1.3 MP front facing camera.
    According to the FCC authorization docs, LG sent the handset to testing with Android 4.0.4 on board, but according to cloud4sites mtest, it has Jelly Bean 4.1.2 on board. So, hopefully it will be released with 4.1.2.
    CDMA1X + EV-DO band classes 0, 1, 10 (i.e. CDMA1X + EV-DO 850/1900/800) LTE band class 25 (LTE 1900; PCS A-G blocks) LTE 3, 5, 10 MHz FDD channel bandwidths SVLTE support, including SVLTE and simultaneous 802.11b/g/n 2.4GHz Wi-Fi tether Maximum RF ERP/EIRP: 26.60 dBm (CDMA1X 850), 26.26 dBm (EV-DO 850), 26.53 dBm (CDMA1X 1900), 26.16 dBm (EV-DO 1900), 25.06 dBm (CDMA1X 800), 25.20 (EV-DO 800), 25.11 dBm (LTE 1900, 3MHz FDD), 24.93 dBm (LTE 1900, 5MHz FDD), 24.70 dBm (LTE 1900, 10 MHz FDD) 802.11a/b/g/n Wi-Fi NFC In their FCC OET authorization filings, OEMs customarily request temporary confidentiality regarding internal and external photos of their devices. But in an unusual move, LG has requested permanent confidentiality for, among other things, antenna distance and simultaneous scenarios for SAR analysis. So, no antenna diagram is available at this time, nor maybe ever unless a teardown review is forthcoming.
     
    Sources: FCC, Bluetooth SIG, Cloud4sites mtest
  13. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Wednesday, February 22, 2012 - 4:20 PM MST
     
    While the name of the bill might seem to suggest otherwise, the Middle Class Tax Relief and Job Creation Act of 2012 currently working its way through Congress contains several provisions that have direct bearing on the wireless industry.
     
    One, it assigns directly to public safety the Upper 700 MHz D block 10 MHz (5 MHz x 5 MHz) nationwide license—which had been intended for a public-private national network partnership but failed to reach its reserve price at FCC auction in 2008—and provides financing for the construction of a national public safety network.
     
    Two, it authorizes the FCC to conduct incentive auctions in which UHF TV broadcasters can voluntarily give up their broadcast channels in exchange for compensation so that their spectrum may be repurposed for wireless broadband.
     
    Three, it directs the FCC to auction within the next three years additional spectrum between 1600 MHz and 2200 MHz, including the creation of yet another PCS 1900 MHz block, the ostensibly named PCS "H" 10 MHz (5 MHz x 5 MHz) block. See the relevant portion of the draft bill:
     

    REALLOCATION AND AUCTION.— (1) IN GENERAL.—Notwithstanding paragraph (15)(A) of section 309(j) of the Communications Act of 1934 (47 U.S.C. 309(j)), not later than 3 years after the date of the enactment of this Act, the Commission shall, except as provided in paragraph (4)— (A) allocate the spectrum described in paragraph (2) for commercial use; and ( through a system of competitive bid- ding under such section, grant new initial li- censes for the use of such spectrum, subject to flexible-use service rules. (2) SPECTRUM DESCRIBED.—The spectrum de- scribed in this paragraph is the following: (A) The frequencies between 1915 mega- hertz and 1920 megahertz. ( The frequencies between 1995 mega- hertz and 2000 megahertz.
     
    Recall that, in the 800 MHz public safety reconfiguration order, Sprint (Nextel) was awarded newly created PCS G 10 MHz (5 MHz x 5 MHz) licenses nationwide to compensate for the SMR 800 MHz spectrum it gave up in the reconfiguration effort and that Sprint plans to deploy 5 MHz x 5 MHz LTE in its PCS G spectrum as part of the Network Vision initiative over the next two years. The PCS "H" block would be of particular interest to Sprint and to S4GRU readers because it would be adjacent to the PCS G licenses that Sprint holds nationwide. See a snapshot of the band plan (the PCS "H" block would take the place of the Proposed AWS-2 Block adjacent to the Nextel allocation):
     

     
     
    Prior to auction, the PCS "H" block would most probably be divided into geographic licenses, and any current or future wireless carrier could bid on one or all licenses. So, Sprint would not be guaranteed to win any PCS "H" spectrum. But Sprint would gain the greatest utility from PCS "H" spectrum because it could be most easily combined with Sprint's existing PCS G spectrum for 10 MHz x 10 MHz LTE. Thus, consider this a brief, early look at how Sprint could likely augment its spectrum portfolio in the coming years.
     
    Sources: US House of Representatives, FCC, author's notes; special thanks to TMF Associates, Public Knowledge
  14. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Thursday, November 12, 2015 - 3:07 PM MST
     
    Yes, you read that correctly. Thanks to the mid range Qualcomm Snapdragon 617 (MSM8952), the HTC One A9 is the first Sprint handset to include a modem that supports uplink 2x CA (carrier aggregation). That comes on die via the X8 LTE modem, which is a Category 7 LTE baseband, capable of aggregating up to 40 MHz FDD/TDD 2x CA on both the uplink and downlink. Now, before anyone gets too excited, Sprint has no imminent plans to enable uplink 2x CA at the network level. So, the uplink 2x CA support is mostly a proof of concept novelty.
     
    If you have been reading The Wall at S4GRU for a while, you probably know where this is headed. It is another in our classic series of FCC OET (Office of Engineering and Technology) RF authorization analysis articles. We do not dwell on processor benchmarks, screen qualities, etc. If you want that info, read reviews or visit the HTC tech specs site. Instead, we cut right to the heart of what a cellphone is -- a cellular RF device -- and rundown its lab tested cellular RF performance.
     
    The One A9 filed its FCC OET authorizations over a month ago, but with Sprint selling the handset as we speak and HTC shipping the unlocked Sprint variant next week, we should take a look. Let us start with the band/class support:
    CDMA2000 Band Class 0/1/10 GSM 850/900/1800/1900 W-CDMA Band 1/2/4/5 LTE Band 2/4/5/12/25/26/41 The Sprint and CCA/RRPP band support is expected at this point. But all of the GSM/W-CDMA band support info comes directly from the HTC tech specs. I state that explicitly because there is no testing of domestic GSM/W-CDMA in the FCC OET documents. Barring a Class II Permissive Change filing with the FCC, the GSM/W-CDMA support purely is for international roaming. While the Sprint variant One A9 can be unlocked or even purchased unlocked, it is not authorized for use on AT&T or T-Mobile -- unless you can live with no GSM/W-CDMA, only band 2/4/5/12 LTE.
     
    For an unlocked One A9, HTC proactively has addressed the to/from Sprint provider switch issue by including that in its one time courtesy UH OH Protection program:
     
    In other words, want to switch from Sprint to AT&T, T-Mobile, or VZW with your unlocked One A9? HTC will swap out for the other domestic variant. Want to switch from AT&T, T-Mobile, or VZW to Sprint with your unlocked One A9? HTC will swap out for the Sprint variant. While on the subject of the AT&T, T-Mobile, and VZW variant, it is 3GPP only, thus VoLTE only for voice on VZW. HTC even acknowledges that fact:
     
    The other domestic variant has some further relevance as we delve into the FCC authorized lab tested ERP/EIRP performance of the Sprint variant.
     
    The FCC OET documents, per usual, do not disclose an antenna diagram. But they do note that the One A9 uses a dual antenna system -- antenna 0 and antenna 1, presumably top and bottom or vice versa. The handset will switch between the antennas at will based upon varying signal metrics. Much like Apple with the iPhone, HTC has implemented this dual antenna setup since the debut of the One M7 in 2013. In this case, however, the dual antennas are still single radio path, so SVLTE is not supported.
     
    Now, for the main attraction, let us look at the Sprint variant One A9 radiated power figures. I may sound like a broken record, but the usual clauses about lab testing versus real world performance and uplink versus downlink always apply. The figures represent my best averaged and rounded estimates of maximum uplink ERP/EIRP test results provided to the FCC OET in the authorization filings for the device. See below:
    Band Class 0: 17 dBm Band Class 1: 22 dBm Band Class 10: 18 dBm Band 2: 16-19 dBm Band 4: 13-16 dBm Band 5: 14-16 dBm Band 12: 14 dBm Band 25: 17-19 dBm Band 26: 16-17 dBm Band 41: 21-22 dBm The CDMA2000 performance is good, about average. And the band 41 output is along the same lines. That is about the best S4GRU can say regarding the tested results of the One A9. It does not quite hit the lows of the VZW variant Samsung Galaxy Note 3 -- the most anemic RF test results that S4GRU has ever seen in any notable handset -- but the One A9 is not far off. The band 4 output that maxes out as low as 13 dBm, for example, is very weak. It is mid band spectrum that needs greater EIRP. The positive is that band 4 roaming never may be a factor with this handset. And band 2/25 is a bit better, though still at least 4-5 dB below the desired level.
     
    Now, back to the other domestic variant headed to AT&T, T-Mobile, and VZW. The picture does not get much rosier. Comparing the 3GPP bands in common, the other domestic variant is superior by 2-7 dB in band 2, 6-9 dB in band 4, 2-4 dB in band 5, and 2 dB in band 12. Wow, those are big differences nearly across the board. The Sprint variant does get one minor victory -- it is 1-2 dB better in band 41 than the other domestic variant is in band 7, as both band 41 and band 7 operate in the same BRS/EBS 2600 MHz spectrum.
     
    What happened, HTC? The Sprint variant seems to have gotten shortchanged. Was that a compromise to optimize band 41 by 1-2 dB? We can hope for better returns in real world performance. But early returns from lab tested performance are not good.
     
    Sources: FCC, HTC, Qualcomm
  15. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, May 10, 2013 - 12:35 PM MDT
     
    Welcome back to S4GRU's continuing series focused on understanding many of the signal metrics displayed on your devices' engineering screens. If you missed part one a few weeks ago, that is a good place to start for background info.
    Last time out, we covered 3GPP2 band class 1 PCS 1900 MHz, in which Sprint has long operated its CDMA2000 network, and 3GPP band 25 PCS 1900 MHz, in which Sprint is currently deploying its LTE network.
    Today, let us begin with the last of Sprint's current native spectrum usage -- 3GPP2 band class 10 SMR 800 MHz. This is what 3GPP2 also calls the "Secondary 800 MHz band," and we will understand why when we finish up with band class 0 Cellular 850 MHz a bit later today.
    First, take a look at the following CDMA1X engineering screenshot:
     

     
    This handset is camped on Sprint's brand new band class 10 CDMA1X 800 overlay, which is replacing iDEN 800 and is currently available in select markets around the country.
    Now, as we did last time, we can take into account the band class and carrier channel number, then use the appropriate formulas to calculate both uplink and downlink center frequencies:
         uplink center frequency (MHz) = 806 + (0.025 × carrier channel)
         downlink center frequency (MHz) = 851 + (0.025 × carrier channel)
    In other words, the spacing in between potential carrier channel assignments in band class 10 is 0.025 MHz (or 25 kHz). This is due to the SMR 800 MHz band's legacy of dispatch and iDEN, both of which conform to 25 kHz channelization. And the band class 10 range of channel numbers extends from 0-719.
    So, using our formulas, band class 10 carrier channel 476 in the included screenshot has an uplink center frequency of 817.9 MHz, a downlink center frequency of 862.9 MHz. This is the one and only band class 10 carrier channel that Sprint will employ across most of the country. In parts of the Southeast where SouthernLINC also operates in rebanded SMR 800 MHz spectrum, Sprint users will instead see band class 10 channel 526, which has uplink and downlink center frequencies of 819.15 MHz and 864.15 MHz, respectively, just as S4GRU detailed in an article a year ago.
    As for band 26 LTE 800, well, that should be coming online in the next several months, but no devices are yet available. So, for both of those reasons, we cannot post any engineering screenshots. What we can anticipate, however, based on SMR 800 MHz spectrum constraints, is that Sprint's 5 MHz FDD LTE 800 carrier likely will be centered somewhere in the 821.1-821.5 MHz x 866.1-866.5 MHz ranges, translating to uplink and downlink EARFCN ranges of 26761-26765 and 8761-8765, respectively.
    I will be out in the field with my spectrum analyzer in the coming months, ready to capture and publish a first peek at the LTE 800 carrier. And expect a follow up article on LTE 800 engineering later this year.
    Now, let us conclude with a look at Sprint roaming service in 3GPP2 band class 0 Cellular 850 MHz. Or this is what 3GPP2 has traditionally referred to as the "800 MHz band." And that, as I piqued earlier, is why the "Secondary 800 MHz band" name comes into play for band class 10 SMR 800 MHz.
    In more recent years, the "800 MHz" nomenclature has become problematic, as it makes distinguishing between band class 0 and band class 10 difficult for less informed users. For a good example of this, see the iPhone 4S tech specs, which mislead many into thinking that it supports Sprint's band class 10 CDMA1X 800 overlay. For this reason, I have long advocated using "Cellular 850 MHz" as distinct terminology.
    That background aside, let us examine a CDMA1X engineering screen of a Sprint device roaming on VZW:
     

     
    This handset is idling on channel assignment 425. Again, we can use the appropriate formulas to calculate both uplink and downlink center frequencies:
         uplink center frequency (MHz) = 825 + (0.03 × carrier channel)
         downlink center frequency (MHz) = 870 + (0.03 × carrier channel)
    So, that VZW channel 425 is centered at 837.75 MHz x 882.75 MHz, which is toward the bottom of the Cellular B block license, as we will see in just a moment.
    First, in the Cellular 850 MHz band, channelization is 0.03 MHz (or 30 kHz), as that dates back to the original analog AMPS standard, which used 30 kHz FM channels and got us all started on this cellularized wireless network journey.
    Second, we encounter a complication with band class 0. The above formula works only for a subset of channel assignments, 1-799. For channel assignments 991-1023, we have to use slightly modified formulas:
         uplink center frequency (MHz) = 825 + [0.03 × (carrier channel − 1023)]
         downlink center frequency (MHz) = 870 + [0.03 × (carrier channel − 1023)]
    The reason for this complication is complicated itself. When the FCC originally created the Cellular 850 MHz band plan in the 1980s, it was 825-845 MHz x 870-890 MHz, divided into two equal 10 MHz FDD (10 MHz x 10 MHz) licenses: Cellular A block (825-835 MHz x 870-880 MHz) and Cellular B block (835-845 MHz x 880-890 MHz). Each block consists of 333 AMPS channels, A block covering 1-333, B block running 334-666.
    Not long after, the FCC expanded the Cellular 850 MHz band, but it could not do so by simply adding spectrum exclusively at the bottom or the top of the band plan. Because of spectrum constraints and equal license bandwidth, the FCC had to add a sliver at the bottom of the band plan and two at the top of the band plan. The additions became known as "A low," "A high," and "B high." See my band plan graphic below:

    Since "A high" (1.5 MHz FDD) and "B high" (2.5 MHz FDD) continue as upper end extensions of the band plan, they follow the original center frequency formula, adding channels 667-799. "A low" (1 MHz FDD) tacked on at the bottom of the original plan is the anomaly. It requires its own center frequency formula and adds channels 991-1023. Also, note the missing channels 800-990. Those are a mystery, unbeknownst even to me.
    Additionally, because it is only 1 MHz FDD, "A low" is not frequently used for CDMA2000 carrier channels, which are always 1.25 MHz FDD in bandwidth. So, many of the carrier channel assignments in "A low" are invalid, since they would cause the CDMA1X or EV-DO carrier to extend off the lower edge of the band. If "A low" is utilized, the only permissible channel assignments are 1013-1023, all of which cause the CDMA2000 carrier to extend into the original A block. So, if you ever encounter a band class 0 channel assignment in the 1013-1023 range, you have found something of a rare bird.
    Well, that covers the relationships among bands, band classes, carrier channel assignments, EARFCNs, and center frequencies. Next time, we will turn our attention to another signal metric. I am thinking maybe SIDs and NIDs or PN offsets but have not decided yet. See you then...
     
    Sources: 3GPP, 3GPP2, FCC
  16. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Wednesday, February 15, 2012 - 4:45 PM MST
     
    Clearwire released its fourth quarter and full year 2011 results in a conference call with investors, analysts, and the media this afternoon. S4GRU was on the call to bring you this report.
     
    Clearwire highlighted its 8-K report with the following statistics:
    Record Fourth Quarter 2011 Revenue of $361.9 Million, Up 107% Year Over Year From $175.2 Million Full Year Revenues of $1.25 Billion, Up 134% Year Over Year From $535.1 Million Full Year Wholesale Revenues Up 876% Year Over Year to $493.7 million 2011 Total Ending Subscribers of 10.4 Million, Up 140% Year Over Year from 4.3 Million Achieves Positive Quarterly Adjusted EBITDA For the First Time of $22.5 Million Average Smartphone 4G Usage Increased 88% Year Over Year in Fourth Quarter 2011 Much of the rest of the report is focused on business metrics that may not be of particular use to anyone without an investment in Clearwire. But we did pore over the report to glean the following numbers of interest to S4GRU readers:
    BRS 2500-2600 MHz licensed spectrum valuation remained steady at $4.3 billion EBS 2500-2600 MHz spectrum lease costs totaled $309 million for 2011 WiMAX covered POPs increased year over year from 112 million to 132 million but plateaued at that level by the end of the second quarter Wholesale (e.g. Sprint) churn almost doubled from 1.5 percent to 2.9 percent during the fourth quarter To provide some analysis of the four points above, first and second, Clearwire holds an average of ~160 MHz of BRS/EBS spectrum bandwidth in the top 100 markets. However, as noted above, some of this spectrum (EBS) is leased from educational institutions, not licensed directly to Clearwire. Additionally, higher frequency spectrum is generally less valuable than is lower frequency spectrum. Otherwise, Clearwire's ~160 MHz of spectrum would be valued in the tens of billions of dollars.
    Third, as Robert has detailed in a forum post about "protection sites," Clearwire faced a May 1, 2011 FCC deadline to demonstrate at least minimum coverage in numerous Basic Trading Areas (BTA) across the country. As a result, Clearwire lit up numerous license "protection sites" around the country during the first few months of last year, leading to the 20 million POPs increase that then stalled for the remainder of the year, as Clearwire made the decision to cease WiMAX deployment and switch to LTE.
    Fourth, Sprint is Clearwire's largest wholesale partner. Any Sprint retail subscriber who has a WiMAX capable device is technically also counted as a Clearwire wholesale subscriber. While Clearwire churn remained relatively flat through the first three quarters, it spiked in the fourth quarter. Clearwire attributed the increase in wholesale churn in large part to Sprint offering the iPhone 4S, which is not WiMAX capable.
    Lastly, Clearwire addressed some of its plans for its TD-LTE 2500-2600 overlay. Clearwire reiterated its commitment to the TDD "ecosystem," alongside strategic partners China Mobile, et al., and to TDD/FDD interoperability that will allow for seamless roaming on both types of LTE networks. Clearwire expects to start build out on its LTE Advanced ready TD-LTE overlay in the second quarter, spending $400 million this year and $200 million next year, keeping costs low because much of the WiMAX infrastructure can be reused for TD-LTE. Build out goals in phase one include 8000 TD-LTE sites, at least 5000 of which are to be live by June 2013. In the WiMAX build out, Clearwire selected its own independent site locations, and this led to great inconsistencies between Clearwire and Sprint coverage. But in the TD-LTE build out, Clearwire and Sprint will work together to identify sites within the Sprint portfolio that exhibit the "highest 4G data usage potential" with fallback to the Sprint FDD LTE 800/1900 network outside of those Clearwire data "hotspots." Finally, both Clearwire and Sprint project multi-band, multi-mode TDD/FDD LTE devices that can utilize the Clearwire TD-LTE overlay to be available by June 2013, by the same time that the first 5000 sites should be online.
     
    Source: Clearwire
  17. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Monday, February 3, 2014 - 8:47 AM MST
    Yes, it has been a while, but welcome to S4GRU's third installment in an ongoing series about the many signal metrics available on those engineering screens hidden inside most mobile devices. Both part one and part two date back to last spring, so check those out if you have not already or if you need a refresher.
    Part three has been a long time coming mostly for lack of a really relevant topic. But a question was just recently posed in The Forums here at S4GRU about EARFCNs and center frequencies for band 41 TD-LTE 2600. Previously, we covered that 3GPP relationship for band 25 LTE 1900 and touched upon it for band 26 LTE 800, but when we did so, band 41 had not yet made its domestic debut. So, now that band 41 -- christened Sprint Spark -- is being overlaid on Clearwire WiMAX sites in the top 100 markets and tri band LTE handsets are finding their way into more and more Sprint users' hands, it is due time for an educational look at those 20 MHz TDD carriers being deployed across the massive BRS/EBS 2600 MHz band.
    First, let us take a look at the BRS/EBS band plan itself. Both it and band 41 encompass 2496-2690 MHz for a total of 194 MHz. The BRS spectrum is licensed -- mostly but not entirely in every market to Sprint subsidiaries. The EBS spectrum is also licensed but to educational institutions, which may then choose to lease the spectrum to commercial entities. So, even though band 41 is maximally 194 MHz wide, Sprint does not necessarily control all of that spectrum. And some of that spectrum -- such as the EBS J block and BRS/EBS K block -- is not intended for broadband uses. In other words, contiguity is periodically interrupted. Plus, WiMAX carriers still occupy much of that BRS/EBS spectrum. All told, band 41 in the US is not quite the huge blank slate that some make it out to be for Sprint to deploy 20 MHz TDD carriers.
    For reference, see the BRS/EBS band plan:

    Next, we will examine a couple of band 41 engineering screenshots drawn from The Forums:

    Just as we did for band 25 in part one of this series, we can extract the channel numbers (i.e. EARFCNs) and enter them into an equation to calculate the band 41 center frequencies:
    uplink/downlink center frequency (MHz) = 2496 + [0.1 × (EARFCN - 39650)]
    Because this is TDD, not FDD, we need to use only the "DL" channel number. In TDD, there are no separate frequencies for uplink and downlink. The LG screenshot on the left properly indicates the same EARFCN for both uplink and downlink. But good old Samsung "enginerring" on the right registers a different channel for the uplink, EARFCN 58978, a number which is an invalid value. So, when working with TDD, disregard any spurious "UL" channel number.
    To finish up our calculations, the range for band 41 EARFCNs is 39650-41589, so EARFCN 39991 is toward the low end of the the band, equating to a center frequency of 2530.1 MHz. And EARFCN 40978 comes out to a center frequency of 2628.8 MHz. Separated by nearly 100 MHz, the former is in the lower EBS segment, while the latter is in the contiguous BRS segment, as depicted in the aforementioned band plan graphic.
    Now, that 20 MHz TDD carrier at EARFCN 40978 is the one that we have documented most commonly across Sprint Spark markets. This was not surprising, since it is deployed in the up to 55.5 MHz of contiguous BRS spectrum that Sprint is licensed, not EBS spectrum that Sprint just leases. That said, we are seeing more and more reports of other EARFCNs, such as EARFCN 39991 detailed above. In other words, the band 41 EARFCN -- unlike the one and only PCS G block band 25 EARFCN -- can vary from market to market because of differences in spectrum licensing/leasing and remaining WiMAX carriers.
    Sprint's ultimate plan is to deploy multiple 20 MHz TDD carriers per market, putting it in an enviable position for satisfying the public's rapidly growing appetite for mobile data. However, do not misinterpret the multitude of current EARFCNs. We have no evidence to this point that the various EARFCNs indicate multiple 20 MHz TDD carriers in the same market. That is coming but probably will not be widespread prior to the WiMAX sunset slated for no earlier than 2015.
    In conclusion, S4GRU has created a tracking thread for the various band 41 EARFCNs as they pop up from market to market. Additionally, in our DL Center, we have made available a comprehensive WiMAX/TD-LTE carrier bandwidth and center frequency spreadsheet (screenshot below) that is continually updated as new EARFCNs get reported. If you are interested, we hope that many of you will continue to help us "crowdsource" this band 41 data so that we can get a clearer picture on Sprint Spark and BRS/EBS spectrum utilization.
     

    Sources: 3GPP, FCC

×
×
  • Create New...