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, 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
  2. 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
  3. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Monday, September 28, 2015 - 10:40 AM MDT
     
    Update: Now that Google has released the full tech specs for the Nexus 6P, we can write a few addenda. While the FCC OET authorization filings disclosed support for several GSM, W-CDMA, and LTE international bands -- something that they are not required to do -- they curiously omitted W-CDMA band 8, which is the GSM 900 MHz band. Add that one to the W-CDMA list. Additionally, we can confirm that the Nexus 6P will require a 4FF nano SIM. For Sprint activation, will it be a USIM or a CSIM? That remains to be seen. Stay tuned.
     
    Late last Friday afternoon, the LG manufactured Google Nexus 5X made its debut in the FCC OET (Office of Engineering and Technology) authorization database. S4GRU staffers quickly got down to work and broke the story with RF analysis that very evening.
     
    Following hot on the heels of its smaller sibling, the Huawei manufactured Google Nexus 6P made a bright and early morning FCC OET appearance today. S4GRU was on the case right away. So, let us dive right in to the RF nitty gritty.
     
    The Nexus 6P band support currently covers all major domestic operators -- VZW, AT&T, T-Mobile, Sprint, USCC, C Spire, etc. It even future proofs itself for AT&T usage to an extent by including nascent band 30 (WCS 2300 MHz), a band not present in the Nexus 5X.
     
    Moreover, it includes some notable international bands, which the authorization filing discloses. (Most FCC OET filings do not disclose international bands, as they are not required to be tested for US authorization.) For example, W-CDMA band 1 (IMT 1900+2100 MHz) is the primary W-CDMA band worldwide, and LTE band 3 (DCS 1800 MHz) is an emerging LTE band in many international markets.
     
    For your perusal, the many bands/classes...
    GSM 850/900/1800/1900 W-CDMA band 1/2/4/5 CDMA2000 band class 0/1/10 LTE band 2/3/4/5/7/12/13/17/25/26/29(Rx only)/30/41 From a physical standpoint, the Nexus 6P incorporates a dual antenna system. All LTE handsets that support 2x2 downlink MIMO must have at least two Rx antennas. But the Nexus 6P also utilizes a dynamic antenna capability on uplink Tx, switching between the two antennas at will, depending upon handset orientation and signal conditions.
     
    Interestingly, though, the dynamic antenna Tx capability is limited to low band spectrum. Only bands/classes below 1 GHz are supported. Lastly, in another twist, the Nexus 6P authorization filings did include an antenna diagram -- something that has become increasingly rare due to cited confidentiality concerns. On the other hand, the antenna gain figures were not apparent anywhere in the filing. For the diagram, see below:
     

     
    In keeping with most of this year's handsets based on the Snapdragon 808 or 810 -- both of which incorporate on die the Snapdragon X10 LTE modem -- the Nexus 6P supports 2x carrier aggregation on the downlink in both intra band and inter band configurations. In the case of inter band 2x CA, either band can be operated as the PCC (primary) or SCC (secondary).
     
    2x CA downlink bands:
    2-2 4-4 41-41 2-4 2-5 2-12 2-13 2-17 2-29 4-5 4-12 4-13 4-17 4-29 To wrap things up, let us examine the LTE band RF output. The usual provisos about lab testing versus real world performance and uplink versus downlink 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.
     
    Overall, the ERP/EIRP figures are fairly consistent within each band and across all bands. In terms of tested performance relative to other handsets, the measurements are roughly average. The P in Nexus 6P is not for RF "powerhouse," but it certainly could stand for "proficient." Compared to the Nexus 5X, the Nexus 6P has a 2-3 dB tested advantage in high band, while the Nexus 5X has a 2-3 dB lead across most of the mid and low band.
     
    ERP/EIRP:
    Band 2: 21-22 dBm Band 4: 21-23 dBm Band 5: 18-19 dBm Band 7: 21-23 dBm Band 12: 17-18 dBm Band 13: 17-18 dBm Band 17: 17-18 dBm Band 25: 21-22 dBm Band 26: 18-19 dBm Band 30: 20-21 dBm Band 41: 21-22 dBm 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
    Wednesday, August 5, 2015 - 1:28 PM MDT
     
    Columbus. But not 1492. Just 8640. And 26640, too.
     
    This discovery did not require an Italian navigator sailing under the Spanish flag, nor the Niña, the Pinta, and the Santa Maria. Instead, the explorers were an intrepid S4GRU Columbus membership group (sorry, restricted to S4GRU sponsors), some handsets, some screenshots, and some speed tests.
     
    Those last two numbers 8640 and 26640 are the paired EARFCNs 8640/26640 of a band 25 additional carrier found this week in the Columbus, OH BTA. Seemingly, not such a big deal. S4GRU and its members have been finding band 25 additional carriers with different EARFCNs in multiple markets for months now. We even have two tracking threads for additional LTE carriers -- one for all three bands, one for band 25.
     
    However, this band 25 additional carrier discovery represents truly a New World for Sprint. It is 10 MHz FDD. Now, that alone is a big deal. But it is actually just the second finding of a 10 MHz FDD carrier that we have had in the past four days. The Champaign-Urbana, IL BTA came first. We hope to follow up with an article on that later.
     
    More importantly, though, the Columbus 10 MHz FDD carrier is a complete refarming of the PCS G block. The standard 5 MHz FDD carrier at EARFCNs 8665/26665 that is omnipresent across the Sprint LTE network is gone -- it is gone forever where this new carrier has appeared in the Columbus BTA.
     
    To dive right in, let us take a look at two screenshots from the Columbus area...
     

     
    The engineering screenshot shows the new EARFCN pair of 8640/26640. That in and of itself is not evidence of 10 MHz FDD. But you have to understand that those EARFCNs put the center frequencies of the LTE carrier at 1990 MHz (downlink) and 1910 MHz (uplink), which is precisely the dividing line between the PCS C5 block and the PCS G block. Even as Sprint controls both blocks, there is no reason to make that move -- unless to expand LTE carrier bandwidth across both blocks. We will take a deeper look at this with Sprint spectrum holdings in a moment.
     
    Moreover, look at the speed test. With 2x2 downlink MIMO, a 5 MHz FDD carrier maxes out at 37 Mbps. This speed test -- and others gathered by the Columbus network trackers -- greatly exceeds that number. Add up the evidence. It is clearly a 10 MHz FDD carrier.
     
    Back to the spectrum issue, we should have an extensive look at the Sprint spectrum provenance in the Columbus market. Yes, it will be extensive, but I think that you will enjoy the history lesson. The reason is that Columbus holdings are somewhat unique, so this 10 MHz FDD fervor should not be extended elsewhere -- for now.
     
    The PCS D 10 MHz (5 MHz FDD) block and PCS E 10 MHz (5 MHz FDD) block were Sprint's original FCC auction winnings back in 1997. The PCS G 10 MHz (5 MHz FDD) block was awarded to Nextel as compensatory spectrum for its SMR 800 MHz rebanding. Of course, Sprint acquired that nationwide set of licenses in the merger. The PCS C4 10 MHz (5 MHz FDD) block is the most recent acquisition, as low budget wireless operator Revol went kaput and sold off its spectrum.
     
    The PCS C5 10 MHz (5 MHz FDD) block is worth a separate discussion -- because it has an interesting history on several fronts. It was FCC auctioned three times. The first winner was NextWave, which later filed for bankruptcy protection. So, the FCC canceled licenses and auctioned again. Meanwhile, the growth of the wireless industry had caused NextWave's licenses to increase in value, leading to a Supreme Court ruling that the FCC was outside its bounds to confiscate the licenses from the bankrupt NextWave. Thus, that re auction was invalidated. Finally, NextWave reached a financial settlement with the FCC to return some of its licenses, which were "re re auctioned" in 2005. And Wirefree Partners, a DE (Designated Entity) working with Sprint, won the PCS C5 block in Columbus.
     
    That brings us to the second interesting point of spectrum provenance. And this part will certainly veer into editorial content. In FCC auctions, a DE is a small business or minority/woman controlled business that qualifies for bidding discounts. Additionally, the PCS C and F blocks typically were reserved or positioned for DEs. The idea was to increase diversity in the wireless industry. The predecessors of both T-Mobile and AT&T -- through the notorious likes of Cook Inlet PCS, Salmon PCS, et al. -- garnered many of their PCS licenses by way of DEs. Just this year, though, the FCC officially shot down Dish for its use of several DE bidders in the recent AWS-3 auction. No discount for Dish!
     
    VZW and Sprint rarely used such underhanded tactics, but this is one such case for Sprint. Wirefree Partners was a Sprint collaborator, qualified as a DE, won the Columbus license at auction, then later sold the license in full to Sprint.
     
    For a complete Sprint PCS 1900 MHz band plan in Columbus, see the following graphic:
     

     
    From a historical perspective, what we can see is that Sprint held three non contiguous blocks: PCS D, E, and C5. The additional guard bands due to lack of contiguity of those three blocks were not a great situation, but the total amount of spectrum was more than good enough for CDMA2000. However, when LTE entered the mix, things got truly interesting. That is when the PCS G and C4 blocks entered the stage.
     
    Next, let us look at deployment within Sprint's PCS spectrum holdings in Columbus. Think of the two graphs as before and after. The first, before, and the second, after Columbus 10 MHz FDD discovery:
     

     
    In the second graph, see how the PCS G block 5 MHz FDD carrier that Sprint users across the country are familiar with has been refarmed, then a new 10 MHz FDD carrier put in its place that spans both the PCS C5 and G blocks.
     
    An almost prophetic piece to all of this comes from the early history of S4GRU. In an article that we published over three years ago, S4GRU identified Columbus as a market that could run a 10 MHz FDD carrier through a combination of the PCS C5 block + PCS G block. Some spectrum holdings have changed that we could not have predicted at that time -- notably, the USCC and Revol spectrum acquisitions. But, remarkably, that possibility of a 10 MHz FDD carrier in Columbus has come to fruition. Read the article if you have not (yes, I wrote it), but you can view the table from it below:
     

     
     
    With the elimination of the band 25 carrier at EARFCNs 8665/26665, some may be worried that early single band Sprint LTE handsets will be forced back to EV-DO in the Columbus area. That is a legitimate concern, as many of those single band handsets were originally authorized with the FCC for only 5 MHz FDD, thus cannot use 10 MHz FDD. In refarming all of band 4 W-CDMA to LTE across multiple markets, for a similar example, T-Mobile certainly required affected users to upgrade to new devices or be hung out to dry on GSM.
     
    To provide just one key Sprint illustration, here is S4GRU's FCC OET article on the Samsung Galaxy S4. Note the 5 MHz FDD limitation. But here is the kicker. Most/all of those early single band handsets with LTE bandwidth limitations have had Class II Permissive Change filings at the FCC in the intervening years. Above is the linked filing for the Galaxy S4. Below is a pertinent screenshot from said filing. Note the "additional bandwidths" language.
     

     
    Even without the Class II filings, though, the expansion to 10 MHz FDD in Columbus should pose no harm to single band handsets. Long before this 10 MHz FDD carrier came to light, S4GRU members found evidence of an additional 5 MHz FDD band 25 carrier located at EARFCNs 8565/26565. See the engineering screenshot below:
     

     
    In a nutshell, the 5 MHz FDD carrier in the PCS G block has been replaced by an equivalent 5 MHz FDD carrier in the PCS C4 block -- as depicted in the deployment graph and screenshot above.
     
    Now, keep in mind, band 41 remains the high capacity priority for Sprint. This 10 MHz FDD refarming is not yet everywhere even in Columbus -- it has been popping up on various sites, spreading from the outside into the city. And while many other Sprint markets will have an additional 5 MHz FDD carrier in band 25, few will see 10 MHz FDD anytime soon. So, Columbus may serve as something of a testbed. But S4GRU has some educated insight as to where this might be headed next.
     
    As mentioned earlier, downstate Illinois around Champaign-Urbana also has unique spectrum holdings and got the 10 MHz FDD treatment a few days ago. Chicago has a similarly unique yet different spectrum set. But as S4GRU published in another article in 2012, it has a contiguous, green field USCC block of spectrum that now seems to be begging for 10 MHz FDD.
     

     
    A band 25 additional carrier already resides in that USCC PCS B block disaggregation -- but it is presently 5 MHz FDD. And an additional EV-DO carrier has been added at the bottom of the block. Still, there may be enough spectrum left to expand that 5 MHz FDD to 10 MHz FDD very soon.
     
    The Windy City, are you ready for it? We shall see if S4GRU's short term prediction proves as accurate as its spectrum analysis did three years ago.
     
    To be continued...
     
    Sources: FCC, S4GRU members and staff
  6. 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
  7. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Thursday, March 5, 2015 - 12:15 PM MST
     
    I got my first real smartphone.
    Bought it at the five and dime.
    Browsed S4GRU 'til my fingers bled.
    Was the summer of 6&9.
     
    Spring has not quite yet sprung for a few more weeks. But with the annual Mobile World Congress just wrapping up today in Barcelona, new smartphones that likely will dominate the mobile landscape through most of the summer are starting to sprout. Germinating at the FCC OET (Office of Engineering and Technology) over the past few days have been authorization filings for the Sprint variants of the Samsung Galaxy S6, Samsung Galaxy S6 Edge, and HTC One M9. Get ready for the summer of 6&9.
     
    S4GRU started a tradition of FCC OET authorization articles right around this time in 2012 with the debut of Sprint's first LTE devices. So, to celebrate the third birthday in our long running series, let us take a look at the cellular RF capabilities of this latest threesome of Samsung Galaxy and HTC One handsets.
     
    To begin, all three devices follow what has been for the past 18 months the standard Sprint variant configuration: tri band LTE, non SVLTE, single RF path with e/CSFB. No surprises there. On top of Sprint tri band LTE, the three handsets also cover the CCA/RRPP LTE bands -- with one possible caveat for the One M9. More details on that later.
     
    As an aside, Qualcomm is changing up its baseband modem branding and numbering schemes. Previously, branding was Gobi and numbering was, to use one example, MDM9625 for standalone modem chipsets. Then, many Snapdragon processor chipsets also included the same modems on die -- a la the Snapdragon 800, aka MSM8974, which integrated the same stack as in the standalone MDM9625. Branding is now changing universally to Snapdragon and numbering, to use just one example again, will follow the X10 LTE pattern. That last example is the Snapdragon 810's brand new LTE category 9 modem, which has no standalone modem precursor. But other rebranded and renumbered examples with their standalone precursors include the Snapdragon X5 LTE (MDM9625), Snapdragon X7 LTE (MDM9635), and Snapdragon X12 LTE (MDM9645).
     
    That Qualcomm background is useful as we will start the rundown with the One M9, which incorporates the Snapdragon 810 with X10 LTE chipset. To cut straight to the chase, below are the tested ERP/EIRP figures:
    Band class 0: 20 dBm Band class 1: 25 dBm Band class 10: 20 dBm Band 2: 25 dBm Band 4: 23 dBm Band 12: 18 dBm Band 25: 25 dBm Band 26: 17 dBm Band 41: 23 dBm For reference, and this will pertain to the ERP/EIRP figures cited later for the Samsung devices, too, the above figures represent our best averaged and rounded estimates of max uplink ERP/EIRP -- with uniquely Sprint frequencies receiving heavier weighting in band class 10, band 25, and band 26. Of course, the usual disclaimers about lab testing versus real world performance apply.
     
    Now, to provide some analysis, RF output looks relatively healthy, somewhere in the better than average range. And it generally, albeit minimally trumps that of its HTC One M8 predecessor -- see our S4GRU article from last year.
     
    The aforementioned caveat about CCA/RRPP bands is that the FCC OET filing for the One M9 does not include separate testing of band 5. Now, that may not indicate omission of band 5 -- because band 26 is a superset of all band 5 frequencies. But we cannot guarantee that the One M9 will attach to band 5 roaming networks without MFBI for band 26.
     
    Two other omissions are worthy of note. First, the FCC OET documents offer no mention of band 41 carrier aggregation capabilities. This may or may not be cause for concern. Current carrier aggregation is downlink reception only, not uplink transmission. And FCC OET testing is just the opposite -- uplink transmission only, not downlink reception. As such, the testing is not required to include carrier aggregation. We do know that the Snapdragon 810 with X10 LTE supports up to 3x 20 MHz FDD/TDD carrier aggregation, so we expect that 2x or 3x band 41 carrier aggregation is on board. S4GRU will follow up if more info becomes available.
     
    Second, the One M9 was not tested, thus is not authorized for domestic GSM/W-CDMA bands. Rabid phone unlockers under the new Sprint domestic unlocking policy, consider yourselves forewarned.
     
    Finally, the One M9 docs suggest VoLTE support at launch. But Sprint has no established timeline for VoLTE, so take that with a grain of salt. It could be just a latent capability.
     
    Moving on to the galactic federation, Samsung has split its Galaxy S6 offerings in two this year, offering a separate Galaxy S6 Edge as a step up version. With one possible exception, both Galaxy S6 handsets have the same RF capabilities. However, their ERP/EIRP figures are not identical, so they are broken out separately below:
     
    Samsung Galaxy S6:
    Band class 0: 17 dBm Band class 1: 23 dBm Band class 10: 17 dBm Band 2: 22 dBm Band 4: 23 dBm Band 5: 16 dBm Band 12: 21-17 dBm (declining with increasing carrier bandwidth) Band 25: 22 dBm Band 26: 16 dBm Band 41: 16 dBm Samsung Galaxy S6 Edge:
    Band class 0: 18 dBm Band class 1: 22 dBm Band class 10: 18 dBm Band 2: 22 dBm Band 4: 24 dBm Band 5: 17 dBm Band 12: 17 dBm Band 25: 22 dBm Band 26: 17 dBm Band 41: 19-11 dBm (declining with decreasing center frequency) As for analysis, both Galaxy S6 variants are about average -- with the Galaxy S6 Edge holding generally a 1 dB "edge," pun intended. Neither, though, holds up to the tested RF output of the One M9. Some surmise that Samsung's much debated shift in handset materials this year from largely cheap feeling plastic to more premium metal and glass has had a detrimental effect on RF design and performance. We cannot jump to that conclusion, but the RF falloff does become even more apparent in comparison to last year's Samsung Galaxy S5 -- again, see our article.
     
    In particular, band 41 EIRP is disappointing. A higher frequency band should precipitate higher RF output. But that is not the case this year, as the band 41 uplink maximum for both Samsung handsets drops 4-7 dB below that of the One M9 and fully 6-9 dB below that of the Galaxy S5.
     
    Also, the band 41 extreme frequency differential in the Galaxy S6 Edge is disconcerting. It is up to 8 dB better in high BRS spectrum than in low EBS spectrum. Meanwhile, multiple band 41 center frequencies in BRS/EBS spectrum will vary from market to market, so performance will also vary. If using the Galaxy S6 Edge on band 41, you better hope for EARFCN 40978 or greater.
     
    Alright, that less than good news out of the way, let us move on to more positive things. The Samsung Galaxy S6 handsets are LTE category 6 -- with explicitly noted support for 2x band 41 carrier aggregation. More on that, too, later. They also have been tested and authorized for domestic GSM/W-CDMA bands, so unlocking in the future for use on other domestic operators may be possible. VoLTE, though, is noted as not supported out of the box. It is, however, on board other Galaxy S6 variants, thus could be added later with a Class II Permissive Change filing and potentially a software update.
     
    Now, back to LTE category 6. In addition to its material design change this year, Samsung has also broken lockstep with Qualcomm, choosing to forgo the 64 bit, octa core Snapdragon 810 processor in favor of its in house 64 bit, octa core Exynos 7420. S4GRU does not traffic in application processor chipset holy wars -- there are plenty of other sites for that. But this chipset change has other ramifications. Unlike the Snapdragon 810, the Exynos does not have a baseband modem on die. Thus, Samsung has had to include a separate modem chipset. And, unfortunately, the full identity of that modem remains a mystery. We know of another Samsung in house chipset -- the Exynos Modem 333 or SS333 -- that could provide the category 6 LTE connectivity, possibly even full 3GPP connectivity.
     
    However, for Sprint, that still leaves lingering 3GPP2 (CDMA2000). Is it provided by a second modem, meaning a third chipset? Could it be a reappearance of the notorious VIA Telecom CDMA2000 modem? S4GRU sincerely hopes not. Or maybe Qualcomm is still on board, not in the processor, but in its aforementioned Snapdragon X7 LTE (MDM9635) category 6 LTE standalone 3GPP/3GPP2 baseband, which supports the same 2x 20 MHz FDD/TDD carrier aggregation. Time will tell.
     
    Well, that is a wrap for this set. If you are young and restless with the Samsung Galaxy S6s and HTC One M9, will you wonder what went wrong? Or will the summer of 6&9 be the best days of your mobile life?
     
    Discuss in the comments.
     
     
    Sources: FCC, Bryan Adams
  8. 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
  9. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Tuesday, September 9, 2014 - 12:21 PM MDT
     
    As many of you know, Sprint recently established a partnership with members of the Competitive Carriers Association (CCA) as sort of a quid pro quo. This partnership is called the Rural Roaming Preferred Program (RRPP), and S4GRU wrote about the nascent RRPP in a recent article on The Wall.
     
    In a nutshell, Sprint will gain pseudo native LTE coverage outside of its standard footprint, as RRPP members overlay Sprint's PCS 1900 MHz, SMR 800 MHz, and even BRS/EBS 2600 MHz spectrum on their existing networks. In turn, RRPP members will get access to Sprint's LTE footprint, and maybe even more importantly for many of these small scale operators, they will benefit from Sprint's and SoftBank's economy of scale in device procurement.
     
    Going forward, Sprint will create a device ecosystem that supports not only its native CDMA2000 band classes and LTE bands but also its RRPP partner LTE bands, namely band 2 LTE 1900, band 4 LTE 1700+2100, band 5 LTE 850, and band 12 LTE 700. The Nexus 5 almost pulled off that quadruple play last year, but that last LTE band has been a sticky wicket for CCA members, since AT&T was able to get its boutique band 17 LTE 700 pushed through the 3GPP. It left many CCA members that hold Lower 700 MHz A block licenses out in the cold, as they lacked access to some of the most popular devices created by the AT&T economy of scale.
     
    Today, that changes. Trumping a presumed iPhone reveal in the FCC OET (Office of Engineering and Technology) later this afternoon, Motorola unleashed the authorization documents this morning for the IHDT56QA3, the third variant of the 2014 Moto X to pass through the FCC OET. The big takeaway, as indicated in the title of this article, is that this Moto X with the expected model number XT1092 is the first Sprint/CCA/RRPP fully compliant LTE handset -- even if an iPhone variant possibly joins the group here in the next few hours.
     
    In conclusion for this short Teaser, the FCC OET docs can speak for themselves. This table tells the whole LTE story for Sprint and its RRPP partners.
     

     
    We wanted to bring you the scoop as soon as possible, but stay tuned. S4GRU may expand this article as more information is gleaned from the FCC OET docs or becomes available elsewhere.
     
    Source: FCC
  10. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Monday, March 10, 2014 - 8:47 AM MDT
     
    After official unveiling at Mobile World Congress in Barcelona a few weeks ago, the Samsung Galaxy S5 made public its authorizations in the FCC OET (Office of Engineering and Technology) database at the start of this weekend. All of the domestic variants are there, including the A3LSMG900P, which in its tri band LTE configuration and "P" designation is the obvious Sprint variant.
     
    As expected of a Sprint high end handset, the Galaxy S5 ticks off all of the checkboxes: tri band LTE, UE category 4, global roaming capability, 802.11ac, NFC, wireless charging, etc. It also appears to improve upon the RF output of last year's single band Samsung Galaxy S4 and Galaxy Note 3. From a common uplink EIRP standpoint, the Galaxy S5 can max out up to 3-4 dB greater on band 25 LTE 1900, hitting 26.85 dBm in the middle of the PCS band, falling off 1-2 dB at the extremes of the band. Additionally, band 41 LTE max output looks relatively healthy at 25.03 dBm.
     
    In a pleasing move, the FCC authorization docs for the Galaxy S5 do include an antenna diagram -- something that is unfortunately becoming less common, per my mention in the recent HTC M8 FCC article. But in this case, we are able to show a visual of the dual WLAN antennas required for Wi-Fi 2x2 MIMO support, allowing MCS index raw data rates up to 300 Mbps over 802.11n and 866.7 Mbps over 802.11ac. Previously, two spatial stream Wi-Fi has been limited to some laptops and a select few tablets. Thus, the Galaxy S5 is pushing the handset envelope in that regard. See the antenna diagram below:
     

     
    Of course, with no separate CDMA2000 and LTE antennas, as depicted in the diagram above, the Galaxy S5 does not support SVDO nor SVLTE. No surprises there, since Sprint tri band LTE handsets have all been single radio path with e/CSFB.
     
    But continuing on the Wi-Fi front, the Galaxy S5 does include a unique simultaneous transmission mode: Wi-Fi and LTE. Now, this is not simultaneous Wi-Fi and LTE in the typical sense that Wi-Fi is used to tether an LTE connection. This is a dual IP stack connection over both Wi-Fi and LTE that Samsung dubs Download Booster, allowing packets to be split up and delivered by both connections, thereby increasing data speeds.
     
    Editorially, S4GRU has some concerns about inclusion of the bonded connection Download Booster, since it may engender "unlimited" data users to remain connected to LTE, too, while on secure Wi-Fi at home, work, school, etc. In most cases, Wi-Fi alone is sufficiently fast for all smartphone activities. And that is why S4GRU has long advocated offloading to Wi-Fi -- when/where possible and secure -- so as to help maintain valuable LTE capacity for truly mobile users. That said, we are curious to see the real world implementation of Download Booster before passing judgment.
     
    Finally, many hoped that the Galaxy S5 might be the first Sprint handset to support LTE Advanced carrier aggregation because Sprint plans to use its acquired Clearwire spectrum to aggregate multiple band 41 20 MHz TDD carriers. That capability, though, will have to wait for the presumed Samsung Galaxy Note 4, Galaxy S6, or some other device.
     
    The carrier aggregation omission is worth mentioning only because the A3LSMG900A variant headed to AT&T does support inter band downlink carrier aggregation. This allows the Galaxy S5 to bond up to 10 MHz FDD of AT&T's low frequency band 17 LTE 700 with up to 10 MHz FDD of its mid frequency band 2 LTE 1900 or band 4 LTE 2100+1700. Indeed, AT&T carrier aggregation is already in use in Chicago, as Gigaom's Kevin Fitchard reported last week.
     
    Well, that is the FCC skinny on the upcoming Sprint variant Galaxy S5. Nothing revolutionary on the cellular side of things, but with MIMO and Download Booster, it does offer up some interesting Wi-Fi enhancements.
     
    Sources: FCC, Samsung
  11. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Monday, March 3, 2014 - 5:37 PM MST
     
    No one is publicly sure what the codenamed HTC M8 will finally be called. HTC One 2, HTC One More, or maybe pull an Apple move and just call it yet again the HTC One. Regardless, all of the big four domestic variants were added to the FCC OET (Office of Engineering and Technology) database today. The last to have its authorizations appear online this afternoon was none other than NM80P6B700 -- the tri band LTE variant undeniably headed to Sprint.
     
    As has been our trend over the past six months, we will still call this a teaser article -- albeit make it more extensive than usual. And we may not do a full RF breakdown in the future. Now that tri band LTE and 802.11ac, for example, are de facto standards among top of the line handsets, while SVDO and SVLTE have been laid to rest, there is less news to report on the RF side.
     
    But we do want to run a brief RF ERP/EIRP numbers comparison among the high end HTC handsets that have graced the Sprint lineup over the past two years because, well, HTC has developed a bit of a reputation among S4GRU members for losing its lead in the RF performance department. Despite its moniker, the HTC EVO LTE was downright poor on LTE, and the follow up Sprint variant HTC One and HTC One max were average at best.
     
    Numbers wise, the HTC M8 looks like a step in the right direction. Per the customary caveats, the available test bench measurements represent only maximum uplink ERP/EIRP, so they do not necessarily reflect the full two way RF performance equation. However, they can provide a decent advance peek inside at the RF proficiency of a handset.
     
    In that regard, the HTC M8 offers some improvements over its predecessors. See the table snapshot below (or link to it on Google Docs):
     

     
    https://docs.google.com/spreadsheet/ccc?key=0ArY31Mr219-ydHh0c2xsUWFmbE1udW5vSnlSMjA3TFE&usp=sharing
     
    More and more, OEMs are hiding behind the shroud of confidentiality and not allowing public inspection of the antenna diagrams in their FCC OET filings. HTC now appears to have jumped on that bandwagon. Fortunately, the Sprint variant HTC M8 docs do reveal some antenna gain figures, and those numbers are not always divulged, diagrams or not. Of note are unity 0 dBi or positive 1 dBi antenna gains for >1 GHz bands. Compare these to the -3.5 dBi antenna gain for PCS 1900 MHz in the HTC EVO LTE.
     
    Additionally, though this is not apparent in the table because it lists only maximum figures, the ranges of max and min ERP/EIRP within the various frequencies in each CDMA2000 band class and within the various carrier bandwidths in each LTE band are more tightly clustered, more consistent than usual. This, likewise, could indicate enhanced antenna engineering.
     
    And, finally, the single radio path handsets that have arrived in conjunction with Sprint tri band LTE so far have generally been better RF performers. Will the HTC M8 -- or whatever it gets called -- follow suit? Early returns indicate so, but once S4GRU membership gets its hands on a few samples, field testing in the coming weeks will tell the full story.
     
    Source: FCC
    Thread: http://s4gru.com/index.php?/topic/5008-htc-m8new-flagship/
  12. 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

  13. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Thursday, December 19, 2013 - 2:12 PM MST
     
    As most of our S4GRU readers are aware, Sprint is pursuing a three pronged approach to LTE. Tri band 25/26/41 LTE 1900/800/2600 -- the first two bands operating as FDD in Sprint and Nextel PCS 1900 MHz and SMR 800 MHz spectrum, the last operating as TDD in Clearwire BRS/EBS 2600 MHz spectrum.
     
    A year and a half ago in the early days of Network Vision, S4GRU was the first web site to offer a peek at a live Sprint LTE downlink carrier. We did likewise in running tri band hotspot field tests upon the emergence of Sprint/Clearwire TD-LTE 2600 in Denver this past summer.
     
    But the missing piece in the tri band LTE strategy has been the 800 MHz spectrum and the decisive propagation advantages it brings to the table. Then, three weeks ago, S4GRU was able to start sourcing inside info on a few but growing number of band 26 site acceptances around the country. And today, S4GRU presents an exclusive first look at a live Sprint LTE 800 carrier.
     

     
    From the spectrum analyzer RF sweep, we can see that this site has achieved SMR 800 MHz deployment completion. On the left is the 1.25 MHz FDD CDMA1X 800 downlink carrier at band class 10 channel assignment 476, which equates to center frequency 862.9 MHz. On this site, CDMA1X 800 was deployed earlier this year just prior to the Nextel iDEN 800 shutdown. But LTE 800 did not follow -- until now.
     
    On the right is the newborn 5 MHz FDD LTE 800 downlink carrier. Temporarily, connections to the LTE 800 carrier are not yet allowed, so an exact EARFCN cannot be determined. But frequency domain analysis suggests a downlink EARFCN 8763, which equates to center frequency 866.3 MHz and is smack dab in the middle of the EARFCN 8761-8765 range that I predicted in one of my engineering screen articles earlier this year.
     
    In our Premier sponsors section, S4GRU continues to track ongoing band 26 LTE 800 site acceptances, which should accelerate rapidly over the next several weeks and months. Most progress thus far is in the Chicago, Houston, Kansas, Jacksonville, and North Wisconsin markets. However, LTE 800 will continue to sprout up across the Sprint network -- outside of those areas encumbered by IBEZ restrictions with Canada and Mexico. Below is today's snapshot of the evolving LTE 800 site map.
     

     
    Source: author's field test, S4GRU map data
  14. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Monday, October 21, 2013 - 3:55 PM MDT
     
    Clarification: Many readers seem to be confusing the previously authorized and officially announced tri band Samsung Galaxy S4 Mini with this tri band Galaxy S4 reboot, which is full size. The two have quite different model numbers -- the Mini is SPH-L520, while as stated below, the tri band Galaxy S4 is SPH-L720T. Sprint has not yet formally acknowledged the latter, but it has passed FCC OET authorization. And S4GRU expects it to be another tri band handset available before the end of the year.
     
    To alleviate the confusion, we are planning an overview article on Sprint Spark tri band handsets, probably to coincide with the November 8 street date next week for the first group of released handsets.
     
    Six months ago, S4GRU published an article breaking down the FCC authorization documents for the Sprint variant Samsung Galaxy S4.
     
    Many were disappointed that the Galaxy S4, like all other Sprint LTE devices for the past year, was limited to single band 25 LTE 1900. It was not a Sprint tri band LTE handset -- even though band 26 LTE 800 and band 41 TD-LTE 2600 seemed to be right on the horizon because of the impending shutdown of the Nextel iDEN network and the likely approval of the SoftBank-Sprint-Clearwire transaction. Indeed, with the arrival of several Sprint tri band mobile hotspots, TD-LTE 2600 started to become available in metros around the country late this past summer.
     
    Today, we bring you another teaser article. The FCC OET database this afternoon uploaded the authorizations for this Samsung model number: SPH-L720T. Now, if you are familiar with the Galaxy S4, you know that its Sprint variant model number is SPH-L720. So, it does not take a genius to put 2 + 2 together. Or in this case, to put S4 + 2 together.
     
    Yes, Samsung has just revealed a Sprint tri band Galaxy S4. It carries very similar specs to those of the original Galaxy S4, but it adds two additional Sprint bands: band 26 LTE 800 and band 41 TD-LTE 2600.
     
    So, between the previous release of the single band Galaxy S4 and the almost inevitable upcoming release of the tri band Galaxy "S5," look for a tri band updated variant for the Sprint Galaxy S4 in the coming months, probably before the end of the year.
     
    Rest assured, this handset will be of popular interest among the faithful -- and possibly despised among those who already used a subsidized upgrade on a single band Galaxy S4 -- so we will run a full FCC OET RF breakdown in the coming days. To head off the obvious questions in the meantime, no SVDO, no SVLTE, as expected.
     
    Before we go, though, view the antenna diagram below to see the Sprint tri band LTE goodness.
     
    As always, stay tuned...
     

    Source: FCC
  15. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Monday, September 30, 2013 - 4:41 PM MDT
     
    Phew, what a September it has been for discovery/announcement of new devices likely headed to Sprint! S4GRU staff has been busy keeping a watchful eye on the FCC OET. And in an egalitarian way, we have covered nearly the gamut of mobile operating systems: Android, iOS, and now, the latest OS version for BlackBerry.
     
    Yes, ahead of a potential government shutdown tomorrow that will reportedly include FCC device authorization, a Sprint relevant BlackBerry Z30 variant was added to the FCC OET database today. This will be another teaser article, not a full RF analysis, but BlackBerry devices usually have healthy ERP/EIRP. Regardless, we have gleaned from the FCC OET documents some important details to share with you.
     
    In a nutshell, this BlackBerry Z30 hardware variant supports the following airlinks:
    GSM 850/1900 band 2/5 W-CDMA 1900/850 band class 0/1/10 CDMA1X/EV-DO 850/1900/800 band 4/13/25 LTE 2100+1700/750/1900 Anyone familiar with the current state of the domestic wireless industry can put two and two together to see that this hardware variant covers the CDMA2000 and LTE capabilities of both VZW and Sprint. Additionally, because of the inclusion of the GSM/W-CDMA modes, the Z30 is probably a world phone, including GSM 900/1800 and at least band 1 W-CDMA 2100+1900. But as we have noted previously, FCC OET filings may divulge band support outside the US but are not required to do so.
     
    The twist is that, within this single hardware Z30 variant, there do seem to exist two wireless operator versions: RFX101LW for VZW and RGB141LW for Sprint. In short, the Sprint version will include CDMA2000 band class 10 but ostensibly use firmware to lockout LTE band 4/13. So, any potential thoughts of CSIM swapping between Sprint and VZW accounts for LTE access with this handset are probably nipped in the bud. See the note from the FCC OET filing:
     

     
    To sum up, the BlackBerry Z30 coming to Sprint will be effectively limited to single band 25 LTE 1900. It will definitely not be among the upcoming tri band LTE Sprint devices. And its VZW supported LTE bands will likely be inaccessible. On the upshot, it does still support SVLTE.
     
    In only a few years, BlackBerry née RIM has gone from being the leader in smartphones to being a former champ nearly down for the count. So, do these developments -- single band LTE, VZW LTE CSIM compatibility lockout -- matter to you? If so, well, place the blame where it lies. Blame Canada.
     
     
    (just barely NSFW)
     
     
    Source: FCC
  16. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, September 13, 2013 - 3:15 PM MDT
     
    The teaser articles continue. But this is a big one -- in a quite literal way.
     
    The presumed Sprint variant Samsung Galaxy Note 3 passed through the FCC OET (Office of Engineering and Technology) on Wednesday this week. We have an article already started on it, so look for that full length rundown soon.
     
    But since that SM-N900P variant hit the FCC OET, the cries about it being single band 25 LTE 1900 have been strong among the S4GRU faithful. Well, here is something potentially to make the disappointed forget those concerns.
     
    Just within the last hour or two this Friday afternoon, another Samsung handset has revealed itself at the FCC OET. But this is no Galaxy Note 3. It is even larger than that. The model number SPH-L600 and dimensions (see the diagram below) suggest that this is a Galaxy Mega 6.3 headed to Sprint. The size exceeds that of the Galaxy Note 3, and in an interesting twist, the FCC OET filing even refers to the device as a "phablet."
     
    The grand pronouncement, though, is that this Samsung "phablet" is indeed a tri band LTE device: band 25 LTE 1900, band 26 LTE 800, band 41 TD-LTE 2600 -- plus the usual Sprint CDMA2000 band classes.
     
     

     
    In conclusion, the "SPH" model number and the specs add up. This is a huge handset for Sprint, it is tri band LTE, and it may render the Galaxy Note 3 irrelevant.
     
    Enjoy! And know that there is more detailed RF info to come...
     
    Source: FCC
    Thread: http://s4gru.com/index.php?/topic/4368-samsung-galaxy-mega-tri-band-sph-l600/
  17. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Wednesday, September 18, 2013 - 2:40 PM MDT
     
    S4GRU has been on a bit of a roll of late. We had an unusually quiet summer here on The Wall, as our writing staff was frequently away on summer vacation. But we have come back with a vengeance.
     
    Earlier this month, we got the next Nexus handset scoop on the rest of the tech press with our discovery of the reappearance of the LG D820 authorization docs at the FCC OET (Office of Engineering and Technology) and supposition that the D820 circumstantially has a striking amount in common with the presumed upcoming Nexus 5. Additionally, last week, we brought you a quick dissection of the two new Sprint variant iPhone models with dual band LTE only minutes after Apple released the specs, not to mention, another FCC OET discovery -- a tri band LTE Samsung Galaxy Mega 6.3 clearly headed to Sprint
     
    All three of those articles were "Teasers." We have decided to publish shorter articles more often when longer articles may not be immediately feasible for our writing staff. Then, down the road, expect more in depth follow up pieces, such as on the Nexus 5, iPhone 5S/5C, and Galaxy Mega 6.3. Today, though, we bring you another full length FCC OET airlink article on the presumed Sprint variant Samsung Galaxy Note 3.
     
    Late on Wednesday last week, authorizations for multiple Samsung Galaxy Note 3 variants -- all bearing the SM-N900 base numbering scheme -- started appearing in the FCC OET database. Other tech outlets had previously gotten a list of the model numbers and tied the N900A to AT&T, N900T to T-Mobile, N900V to VZW, and N900S to Sprint. But while the "A," "T," and "V" variants all arrived in the FCC OET, the "S" variant did not make an appearance, and additional info suggested that the "S" variant is instead for SK Telecom in South Korea.
     
    Meanwhile, the N900R4, the "R4" variant, also had its authorizations posted to the FCC OET. And at least one tech site incorrectly pegged it as the one for Sprint and other CDMA2000 operators. But that clearly missed the absence of band class 10 CDMA1X 800, which has been a staple of Sprint devices for roughly two years now. In the end, the "R4" variant is coming to CDMA2000 operators, but USCC and C Spire are the likely destinations.
     
    So, that left the N900P, the "P" variant, for Sprint, and the circumstantial evidence of being the only version with band class 10 CDMA1X 800 supports that inference. Thus, adding to S4GRU's continuing series of articles on the FCC OET authorizations for the HTC EVO 4G LTE, Samsung Galaxy S3, Motorola Photon Q 4G, LG Optimus G, Samsung Galaxy Note 2, HTC One, Samsung Galaxy S4, and LG G2 is Sprint's expected Samsung Galaxy Note 3:
    CDMA1X/EV-DO band classes 0, 1, 10 (i.e. CDMA1X/EV-DO 850/1900/800) LTE band 25 (i.e. LTE 1900) LTE 5/10 MHz FDD carrier bandwidth LTE UE category 4 W-CDMA bands 2, 5 (i.e. W-CDMA 1900/850) GSM 850/1900 802.11a/b/g/n/ac Wi-Fi 802.11n MCS index 7 (single spatial stream, 40 MHz carrier bandwidth, 400 ns guard interval) 802.11ac MCS index 9 (single spatial stream, 80 MHz carrier bandwidth, 400 ns guard interval) SVLTE support, including SVLTE and mobile hotspot (both 2.4 GHz and 5 GHz) SVDO absent RF ERP/EIRP maximum: 19.82-20.93 dBm (CDMA1X/EV-DO 850), 18.91-21.30 dBm (CDMA1X/EV-DO 1900), 21.85-23.63 dBm (LTE 1900) RF conducted power maximum: 24.75 dBm (CDMA1X/EV-DO 800) CDMA1X/EV-DO Rx antenna diversity NFC antenna integrated into battery cover Antenna locations: (see FCC OET diagram below) Simultaneous transmission paths: (see FCC OET diagram below)
     

     
    By now, many of our readers have a solid understanding of how to analyze the bullet points listed above. As such, we will hit just some of the highlights.
     
    Samsung has finally started adding LTE 10 MHz FDD carrier bandwidth authorization to its Sprint devices. That may be inconsequential during the lifetime of these devices, but it is nice to see, nonetheless, as other OEMs have included 10 MHz FDD capability from the beginning.
     
    The Note 3 is reportedly another world phone for Sprint. While the specs for FCC testing include only those bands licensed in the US, the GSM 850/1900 capabilities are actually quad band: GSM 850/900/1800/1900. Likewise, W-CDMA 850/1900 expands to include bands 1 and 8 for W-CDMA 2100+1900/900 outside of the US.
     
    The Note 3 also follows the trend of devices released this summer that now support mobile hotspot via 5 GHz Wi-Fi. That can be handy in congested 2.4 GHz Wi-Fi environments, and congested 2.4 GHz Wi-Fi environments are now basically everywhere that people live and work.
     
    Devices with SMR 800 MHz capability seem to be coming through the FCC OET now with only conducted power testing, instead of radiated power testing. I suspected previously that a Class II Permissive Change would be required to include ERP testing, but that seems no longer to be the case. Looking back at the Sprint variant Samsung Galaxy S4 authorization docs, they submitted only conducted power specs for CDMA1X 800. Of course, the Galaxy S4 has already been out in the world all summer. I am not sure what to make of this, but Part 90 -- which governs SMR 800 MHz -- may not require ERP testing. So, going forward, we will report conducted power if that is the only data available.
     
    But the phrase that dare not be heard among the committed is "single band." One LTE band. That is the elephant in the room in this article. Yes, the "P" variant is band 25 LTE 1900 only. Sources have suggested to S4GRU that tri band LTE handsets headed to Sprint will not support SVLTE. As such, some have hypothesized that Sprint sacrificed tri band capability for SVLTE support in the Note 3 because it is, indeed, a "phablet." Using a "phablet" as a phone against one's ear looks clownish, so using the "phablet" in hand with an earpiece or Bluetooth headset may be expected, leading to more SVLTE usage.
     
    However, further examination of FCC OET docs on the multiple Note 3 variants and subsequently announced Sprint version Samsung Galaxy Mega 6.3 tri band "phablet" pokes some holes in that SVLTE theory.
     
    The major revelation, which will bring no solace to Sprint subs who had been expecting and are now pining for a Sprint tri band Note 3, though, is that the "R4" version headed to USCC manages to support both SVLTE and quad band LTE: band 4, 5, 12, 25 LTE 2100+1700/850/700/1900.
     
    See the antenna locations and simultaneous transmission paths diagrams:

     

     
    The big takeaway is that Samsung has managed to cram in SVLTE and multi band LTE for relatively minor regional CDMA2000 operators. Why not Sprint?
     
    Well, the Sprint variant Note 3 is a world phone, while the regional CDMA2000 operator variant is not. And the Sprint version has to support band class 10 CDMA1X 800 and band 25 LTE 1900 -- unlike any others. Does the engineering required for world phone and Sprint boutique band/class capabilities present an obstacle to multi band LTE? Is SVLTE worth the sacrifice?
     
    Let the discussion flow...
     
    Source: FCC, FCC
    Thread: http://s4gru.com/index.php?/topic/4318-samsung-galaxy-note-3/
  18. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Tuesday, September 10, 2013 - 1:10 PM MDT
     
    To cut right to the chase, Apple announced at its live event today two new iPhone models: high end iPhone 5S and mid range iPhone 5C. Both are coming to Sprint and both support Sprint LTE -- but only dual band Sprint LTE. The new crop of iPhone models for the next year will not be tri band LTE handsets on Sprint.
     
    The LTE bands supported by iPhone 5S (A1453) and iPhone 5C (A1456) are substantial and as follows: band 1, 2, 3, 4, 5, 8, 13, 17, 18, 19, 20, 25, 26. For Sprint users, that means dual band LTE 1900/800.
     
    While 13 total bands seems impressive, a few of those bands -- such as band 2/25 and band 5/26 -- are subset/superset bands. The big takeaway for Sprint users, though, is that band 41 is absent this year. So, TD-LTE 2600 will be coming soon to several tri band Android handsets but not to the dual band two new iPhone models. Band 38 TD-LTE 2600 is limited to the Asia/Oceania variants.
     
    Also worthy of note, Sprint and SoftBank share the same iPhone 5S and iPhone 5C variants this year. Whether that is merely coincidence is impossible to determine. But Sprint and SoftBank have talked about combined economy of scale as a benefit of their tie up.
     
    To conclude, the new iPhone FCC OET docs have not yet trickled out, but as they do, we will have more info to come. Stay tuned...
     
    Source: Apple
    Thread: http://s4gru.com/index.php?/topic/4442-the-iphone-5s-iphone-5c-not-tri-band-lte-was-next-iphone-to-be-announced-on-september-10/
  19. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Thursday, September 5, 2013 - 5:33 PM MDT
     
    About a month ago, our FCC OET reporter, Josh McDaniel, noted that a mystery handset, the LG D820, came and went from the FCC OET (Office of Engineering and Technology). Its authorizations were uploaded, then quickly rescinded, citing confidentiality reasons.
     
    Well, today, the LG D820 authorization documents are back. And we are looking at a 3GPP/3GPP2 handset that runs nearly the full North American wireless airlink gamut:
    GSM 850/1900 W-CDMA 1900/2100+1700/850 (band 2, 4, 5) CDMA1X/EV-DO 850/1900/800 (band class 0, 1, 10) LTE 2100+1700/850/700/1900/800 (band 4, 5, 17, 25, 26) TD-LTE 2600 (band 41) The only notable omission is LTE 750, VZW's currently boutique band 13 -- possibly left out for political reasons, since VZW has a strained relationship with Nexus devices, or for technical reasons, as band 13 has an inverted FDD uplink/downlink duplex. But in a nutshell, this handset looks like it could be headed to AT&T, T-Mobile, and Sprint, covering all of their bases.
     
    Here is the kicker, though. One of our moderators, Tim Yu, noted a significant resemblance between the back plate in the FCC OET filing and the back plate of a mystery Nexus device in a widely circulated photo recently from the Google campus.
     
     

     
     
    So, you be the judge. Based on the specs and pics, does the the LG D820 look like it could be the upcoming Nexus 5???
     
    More to come...
     
    Source: FCC
    Thread: http://s4gru.com/index.php?/topic/4366-lg-d820-google-nexus-5/
  20. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Tuesday, September 3, 2013 - 11:35 AM MDT
     
    Welcome back from summer vacation. The S4GRU writing staff, too, has returned and is ready to catch up on some of the developments from over the last two or three months.
     
    In late July, Sprint released two tri band LTE mobile hotspots and one tri band LTE USB dongle. Meanwhile, Clearwire had lit up band 41 TD-LTE 2600 on numerous sites in several markets around the country. Around the same time, the LG G2 became the first Sprint tri band LTE handset to pass through FCC OET (Office of Engineering and Technology) authorization.
     
    As is our tradition by now, we add to S4GRU's stalwart series of articles on the FCC OET authorizations for the HTC EVO 4G LTE, Samsung Galaxy S3, Motorola Photon Q 4G, LG Optimus G, Samsung Galaxy Note 2, HTC One, and Samsung Galaxy S4 our look at the RF faculties of the LG G2:
    CDMA1X + EV-DO band classes 0, 1, 10 (i.e. CDMA1X + EV-DO 850/1900/800) LTE bands 25, 26, 41 (i.e. LTE 1900/800, TD-LTE 2600) band 25 LTE 3/5/10 MHz FDD carrier bandwidth band 26 LTE 1.4/3/5/10 MHz FDD carrier bandwidth band 41 TD-LTE 10/15/20 MHz TDD carrier bandwidth LTE UE category 4 W-CDMA bands 2, 5 (i.e. W-CDMA 1900/850) GSM 850/1900 802.11a/b/g/n/ac Wi-Fi 802.11n MCS index 7 (single spatial stream, 40 MHz carrier bandwidth, 400 ns guard interval) 802.11ac MCS index 9 (single spatial stream, 80 MHz carrier bandwidth, 400 ns guard interval) SVDO and SVLTE support absent RF ERP/EIRP maximum: 19.80 dBm (CDMA1X/EV-DO 850), 21.64 dBm (CDMA1X/EV-DO 1900), 23.09-27.08 dBm (LTE 1900), 17.77-21.29 dBm (TD-LTE 2600) CDMA1X/EV-DO Rx antenna diversity NFC antenna integrated into battery cover Antenna locations: (see FCC OET diagram below) Simultaneous transmission paths: (see FCC OET diagram below)

     
    The LG G2 is not only the first revealed Sprint tri band LTE handset but also the first Sprint category 4 UE of any kind because it is utilizing the Qualcomm Snapdragon 800 (MSM8974). The MSM8974 is a 28 nm process SoC that contains processor, cellular baseband, and WLAN/GNSS baseband all on one chipset -- à la the MSM8960 that dominated the first half of last year. The difference, of course, is that the MSM8974 has a quad core processor and a UE category 4 cellular baseband. The latter supports up to 150 Mbps on the downlink, 50 Mbps on the uplink -- though those speeds will not likely be seen on Sprint during the lifespan of this handset due to spectrum bandwidth constraints.
     
    Also, we cannot confirm at this point that the G2 is actually using the internal WLAN/GNSS baseband capabilities of the MSM8974 and not a separate chipset solution from Broadcom, as has been the trend with the HTC One and Samsung Galaxy S4. But having at least both processor and cellular baseband on the same chipset should be a step in the right direction.
     
    Regarding maximum ERP/EIRP, we are slightly modifying the way that we report those figures. Even within a given frequency band, max ERP/EIRP can vary according to frequency and modulation. So, if the FCC OET docs show greater than 1 dB of variance in a certain band and airlink, we now report that range instead of a single max figure.
     
    As we have stated in the past, FCC OET testing includes only transmitters, not receivers. Thus, we have to extrapolate overall RF prowess based on mobile uplink transmission capabilities, and that is an inexact science.
     
    In a nutshell, though, the CDMA2000 band class 0 and 1 power outputs appear to be a bit on the weak side, while the band 25 LTE power output looks good. The band 41 TD-LTE EIRP is lower than we would like to see -- especially considering BRS/EBS 2600 MHz propagation characteristics -- but TD-LTE 2600 will be used largely as an offload band for handsets, probably less so for hotspots.
     
    What is missing are band class 10 CDMA2000 and band 26 LTE ERP figures. The original FCC OET filing in late July included only conducted power figures for that band class and band. Conducted power is what is delivered to the antenna, not what is actually radiated from the antenna. And even though the G2 at the end of August has already had one Class II Permissive Change filing, we expect at least one more Class II filing with additional ERP figures before this Sprint variant hits the streets.
     
    Last year, the LG Optimus G had its initial, incomplete FCC OET filing in the summer, followed by a Class II change in the fall and a release in November. In our Optimus G article last summer, we wrote not to expect the street date right away, and we will offer the same caveat here. The rumored November release for the Sprint variant G2 should probably be the expectation.
     
    Source: FCC
  21. 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
  22. 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
  23. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, April 26, 2013 - 6:29 AM MDT
     
    A significant piece of S4GRU's educational mission is helping our readers understand what goes on behind the scenes and underneath the hood in the operation of a wireless network. This often requires getting readers to access internal engineering (or debug) screens on their handsets to view numbers and metrics, such as PN offset, Ec/Io, cell identity, etc., as we track the progress of Sprint's Network Vision deployment around the country. So, S4GRU staff thought it long overdue to publish a tutorial on what all of those engineering screen numbers and metrics actually mean. And in this first part of what will hopefully be a long running series, we will examine frequencies, namely center frequencies.
    First, let us kick things off with CDMA2000 (e.g. CDMA1X/EV-DO).
    CDMA2000 is divided into band classes. Those band classes basically represent spectrum bands of operation. Some common CDMA2000 band classes familiar to Sprint users include: band class 0 (Cellular 850 MHz), band class 1 (PCS 1900 MHz), band class 10 (SMR 800 MHz), and band class 15 (AWS 2100+1700 MHz).
    Then, each band class is further divided into carrier channels. These carrier channel numbers represent the actual RF locations -- center frequencies -- of the carrier channels that we use for voice and data services.
    To illustrate, see the EV-DO engineering screenshot below, specifically the "Channel Number" and "Band Class" fields:
     

     
    Taking into account the band class and carrier channel number, we can use the following formulas to calculate both uplink and downlink center frequencies:
         uplink center frequency (MHz) = 1850 + (0.05 × carrier channel)
         downlink center frequency (MHz) = 1930 + (0.05 × carrier channel)
    In other words, the spacing in between potential carrier channel assignments in band class 1 is 0.05 MHz (or 50 kHz). And the band class 1 range of carrier channel numbers extends from 0-1199.
    So, using our formulas, the band class 1 carrier channel 100 in the included screenshot has an uplink center frequency of 1855 MHz, a downlink center frequency of 1935 MHz. This FDD paired set of center frequencies falls toward the lower end of the PCS A block 30 MHz license, which is 1850-1865 MHz x 1930-1945 MHz.
    Next, we can shift over to the 3GPP (e.g. LTE) side, which does things a bit differently.
    3GPP sets forth bands, instead of band classes, but otherwise, the functions of bands and band classes are the same. In the US, common 3GPP bands for LTE include: band 4 (AWS 2100+1700 MHz), band 13 (Upper 700 MHz), and band 17 (Lower 700 MHz). But we are most interested in band 25 (PCS 1900 MHz + G block), the band in which Sprint is initially deploying LTE.
    As with carrier channel numbers in CDMA2000 band classes, 3GPP bands are subdivided into Evolved Absolute Radio Frequency Channel Numbers (EARFCNs). And like carrier channel numbers, EARFCNs indicate center frequencies. However, EARFCNs do so separately for uplink and downlink, as LTE allows for different pairings of uplink and downlink via carrier aggregation.
    Now, see the LTE engineering screenshot below for its "Band," "UL channel," and "DL channel" fields:
     

     
    Per band 25, we can enter the "UL/DL channels" (i.e. EARFCNs) into the following formulas to determine again both uplink and downlink center frequencies:
         uplink center frequency (MHz) = 1850 + [0.1 × (uplink EARFCN - 26040)]
         downlink center frequency (MHz) = 1930 + [0.1 × (downlink EARFCN - 8040)]
    In this case, spacing between EARFCNs is 0.1 MHz (or 100 kHz). Additionally, the uplink EARFCN range is 26040-26689, the downlink EARFCN range 8040-8689, both for band 25.
    And in the end, EARFCN 26665 in the included screenshot has an uplink center frequency of 1912.5 MHz, while EARFCN 8665 has a downlink center frequency of 1992.5 MHz. This is an FDD paired set of center frequencies, not a carrier aggregated set, and it resides exactly in the middle of the PCS G block 10 MHz license, which is 1910-1915 MHz x 1990-1995 MHz.
    In part two, we will take a similar look at center frequencies in the PCS 1900 MHz band's lower frequency cousins, SMR 800 MHz and Cellular 850 MHz. So, stay tuned.
     
    Sources: 3GPP, 3GPP2
  24. WiWavelength
    by Josh McDaniel
    Sprint 4G Rollout Updates
    Monday, April 8, 2013 - 1:19 PM MDT
     
    On April 5, the mysterious Samsung SPH-L500 passed thru the FCC OET (Office of Engineering and Technology), indicating that it is now authorized for use in the US on the Sprint network. S4GRU can report only the details that are currently available, but we will update the article as more info emerges.
    The phone measures roughly 5.24 inches tall by 2.68 inches wide, making it slightly smaller than the Galaxy S3 and S4 and slightly larger than the Galaxy S3 mini that it was originally rumored to be based off of, and comes with a 1.4 GHz dual core processor. As was previously noted from the Bluetooth SIG report in November, this phone has support for Bluetooth 4.0 and the following profiles: HFP1.5, HSP, OPP, A2DP, AVRCP, GAVDP, PAN, PBAP, HID, and MAP.
     

    As you can see from the antenna diagram, CDMA1X and EVDO share the same antenna path, so SVDO is not possible, but SVLTE is possible. The phone also supports simultaneous LTE and Wi- Fi tether on 2.4 GHz, but not on 5 GHz. Lastly, it is not capable of supporting simultaneous Wi-Fi and Bluetooth, as they also share the same antenna path.

    CDMA1X + EV-DO bands 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 channel bandwidth SVLTE support, including SVLTE and simultaneous 802.11b/g/n 2.4 GHz Wi-Fi tether Maximum RF ERP/EIRP: 21.45 dBm (CDMA1X/EV-DO 850), 23.11 dBm (CDMA1X/EV-DO 1900), 23.12 dBm (CDMA1X/EV-DO 800), 22.20 dBm (LTE 1900) LTE antenna configuration 1 uplink, 2 downlink (i.e. 2x2 downlink MIMO) 802.11 a/b/g/n Wi-Fi NFC with antenna built into battery According to the HTTP header from cloud4sites.com, the SPH-L500 has Android 4.1.2. SXTPdevelopers.com member “sextape” rumored the specs on the phone to be a 4.65” screen with a resolution of 1280 x 720, 8 MP rear camera and 1.9 MP front facing camera, 1 GB RAM, 8 GB built-in memory, and microSD Card slot supporting up to 64 GB cards. The chipset is said to be the Qualcomm MSM8930AA, which is apparently the same chipset found in the new HTC First by Facebook and HTC. If the SPH-L500 is released with these specs, they are pretty decent for a mid-range phone, considering all mid-range Sprint LTE phones up until now have only had 5 MP rear cameras and 4” 480 x 800 resolution displays.
     
    Sources: FCC, cloud4sites, SXTP
  25. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Thursday, March 28, 2013 - 10:10 AM MDT
     
    Update: The Samsung review embargo has been lifted overnight, and Galaxy S4 reviews are being published around the Web today. Thanks to one of our favorite, highly thorough reviewers, Brian Klug at AnandTech, we can confirm that the Galaxy S4 follows the recent HTC One in providing a removable micro-SIM. So, while two data points do not necessarily a trend make, the One and Galaxy S4 do suggest that removable SIMs for Sprint LTE handsets are here to stay.
     
    Arguably the most hotly anticipated handset of the year, rivaling even the next iPhone, the Samsung Galaxy S4 in its Sprint variant popped up in the FCC OET (Office of Engineering and Technology) database late yesterday, meaning that the next Galaxy is now authorized to operate in the US and is likely just a few weeks away from a Sprint street date. Not a revolutionary overhaul of the very successful Galaxy S3 platform of last year, the Galaxy S4 maintains a strong family resemblance to its older sibling but does generally and for Sprint specifically add a number of evolutionary enhancements, such as a larger 1080p display, world roaming capability, wireless charging cover functionality, and some transmit power increases.
    Thus, adding to S4GRU's long standing series of articles on the FCC OET authorizations for the HTC EVO 4G LTE, Samsung Galaxy S3, Motorola Photon Q 4G, LG Optimus G, Samsung Galaxy Note 2, and HTC One is our run through of the RF capabilities of the Galaxy S4:
    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 bands 2, 5 (i.e. W-CDMA 1900/850) GSM 850/1900 802.11a/b/g/n/ac Wi-Fi 802.11n MCS index 7, 40 MHz carrier bandwidth 802.11ac MCS index 9, 80 MHz carrier bandwidth SVLTE support, including SVLTE and simultaneous 802.11b/g/n Wi-Fi tether RF ERP/EIRP maximum: 25.39 dBm (CDMA1X/EV-DO 850), 23.25 dBm (CDMA1X/EV-DO 1900), 24.62 dBm (CDMA1X/EV-DO 800), 22.83 dBm (LTE 1900) NFC antenna integrated into battery cover CDMA1X/EV-DO Rx antenna diversity Antenna locations: (see FCC OET diagram below) Simultaneous transmission paths: (see FCC OET diagram below)
     

     
    Breaking down the RF specs, honestly, the Galaxy S4 may come across as a disappointment to many. That is primarily, though, because the reality could hardly live up to the expectations.
    First, the Galaxy S4 does not support band 26 LTE 800 nor band 41 TD-LTE 2600. Reports are that Sprint will not release any dual band LTE devices and will skip straight to tri band. Those devices, however, are still at least six months off, so like all Sprint LTE devices before it, the Galaxy S4 is limited to band 25 LTE 1900 on the native Sprint network.
    Additionally, the Galaxy S4's band 25 LTE 1900 is limited to 5 MHz FDD bandwidth. This seems to be largely a Samsung quirk, as Sprint LTE devices from other OEMs are tested and authorized for 10 MHz FDD (or greater) as well. That being said, this will likely be of no consequence, as all Sprint LTE FDD deployment for at least the next several years is apt to remain based on 5 MHz FDD carriers.
    Also, unlike the recent HTC One, the Galaxy S4 does not appear to be particularly optimized for the Sprint LTE network. Using the FCC OET authorization documents, we can gauge a device's RF prowess by examining its maximum transmit ERP/EIRP and at what frequency that max occurs. This is by no means a perfect simulacrum for both transmission and reception, but we can say that Galaxy S4 LTE is at its max RF wise in the traditional PCS A-F blocks, not the PCS G block 1912.5 MHz center frequency where Sprint is deploying its initial LTE carrier nationwide.
    Staying on ERP/EIRP discussion, the Galaxy S4 looks to be a rather strong performer on roaming CDMA1X/EV-DO 850 and the now being deployed Sprint native CDMA1X 800. Both show quite high ERP. On the flip side, the EIRP for CDMA1X/EV-DO 1900 is good, too, but oddly less than the ERP of the CDMA2000 airlinks below 1 GHz that enjoy significant propagation advantages. With most other handsets, the transmit power relationship is reversed, CDMA1X/EV-DO 1900 transmit power being greater to compensate for its greater path loss.
    Furthermore, ERP/EIRP was tested with both the standard battery cover and the wireless charging cover. A definite caveat, the wireless charging cover reduces ERP/EIRP by up to 6 dB. Most likely, the induction coil in the wireless charging cover absorbs some of the transmitted RF, thus reducing the radiated power. For some users, the convenience of wireless charging may outweigh the hit to wireless performance. But S4GRU cannot generally recommend wireless charging due to its inefficiency (much power is wasted as heat) and detriment to RF.
    As for simultaneous voice and data, the Galaxy S4 does support SVLTE but is the latest in a long line of Sprint LTE handsets now to forgo SVDO. Realistically, this comes as no great surprise, as we have not seen SVDO capability in any new handset since last summer. Either this is a limitation of the Qualcomm MDM9615 baseband modem that has become standard equipment or SVDO is no longer a strong priority as Sprint LTE coverage grows weekly. Regardless, CDMA1X and EV-DO share a transmit path (indicated in the FCC OET diagram above); hence, simultaneous CDMA1X voice and EV-DO data is not supported.
    As S4GRU has reported in the past, the FCC OET authorization documents are not required to disclose world phone capabilities because those bands are not in use in the US. However, the presence of GSM 850/1900 and W-CDMA bands 2, 5 (i.e. W-CDMA 1900/850) is strongly indicative of the inclusion of international roaming capabilities, too. Indeed, other outlets are reporting that all variants of the Galaxy S4 include at a minimum quad band GSM 850/900/1800/1900 and W-CDMA bands 1, 2, 5, 8 (i.e. W-CDMA 2100+1900/1900/850/900) -- the latter supporting DC-HSPA+ on the downlink and HSUPA on the uplink. While we cannot confirm these reports at this time, they certainly do seem plausible. What also remains unconfirmed at this point is the SIM situation: embedded or removable. As soon as this info comes to light, we will update the article.
     
    Source: FCC
×
×
  • Create New...