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
    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
  2. 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
  3. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, August 10, 2012 - 6:54 PM MDT
     
    Update: The previously dubbed LG Eclipse is being released November 11 as the Optimus G. Additionally, the LTE 1900 EIRP figures that were missing from the original FCC filing were added six weeks later in a Class II Permissive Change application. Max LTE 1900 EIRP is 23.51 dBm -- though with substantial variability (up to 4.5 dB) due to differences in carrier frequency, bandwidth, and modulation (QPSK/16-QAM). Furthermore, CDMA1X/EV-DO 800 max ERP has been increased by approximately 2 dB to 23.17 dBm.
     
    To quote the inimitable Yogi Berra, "It's déjà vu all over again." And here we go again. S4GRU is happy to announce yet another breakdown of an FCC OET (Office of Engineering and Technology) authorization filing for a major device headed to Sprint's upcoming Network Vision enhanced LTE overlay. Since this spring, we have analyzed the FCC authorizations for the HTC EVO 4G LTE, Samsung Galaxy S3, and yet to be released Motorola Photon Q 4G. Today, the expected LG Eclipse 4G hit the FCC database under the model number LG LS970, and here are the RF facets that we have been able to glean:
    CDMA1X + EV-DO band classes 0, 1, 10 (i.e. CDMA1X + EV-DO 850/1900/800) LTE band 25 (i.e. LTE 1900; PCS A-G blocks) LTE 5 MHz and 10 MHz carrier bandwidths 802.11a/b/g/n Wi-Fi; max MCS index 7 (i.e. 20 MHz channel, 400 ns guard interval, single spatial channel) SVLTE support, including SVLTE and simultaneous Wi-Fi tether SVDO support absent Maximum RF ERP/EIRP: 21.86 dBm (CDMA1X/EV-DO 850), 25.33 dBm (CDMA1X/EV-DO 1900), 21.68 dBm (CDMA1X/EV-DO 800) NFC antenna integrated into battery cover Antenna locations: (see FCC OET diagrams below)

     
    Notably missing from the presumed LG Eclipse's FCC filing are two things: SVDO capability and LTE band 25 EIRP test results.
    Rumor has it that the Eclipse will utilize Qualcomm's upcoming and highly anticipated APQ8064 quad core 28 nm "Krait" processor. The quad core difference is noteworthy compared to the dual core MSM8960 chipset that has proven very successful in the EVO LTE and Galaxy S3, et al. But the MSM8960 incorporates a multimode modem, while the APQ8064 is a naked processor. If rumor has it right, then the Eclipse will also have to utilize at least one separate modem chipset. And it would seem that LG has chosen at least one CDMA1X/EV-DO modem that is not capable of voice "Fusion," which would enable SVDO with a second modem. So, like its Viper predecessor, the Eclipse appears to be a multiple chipset design. But unlike the Viper, the Eclipse is absent SVDO.
    Furthermore, the FCC OET filing includes requisite CDMA1X + EV-DO 850/1900/800 ERP/EIRP figures but lacks LTE 1900 EIRP figures. So, do not hold your breath for a release date. We will leave it to other sources to speculate/report on the ergonomics and other technical attributes of the upcoming LG device. But we expect that LG and its authorized testing lab will have to file supplemental results before the supposed Eclipse makes its way into the hands of eager Sprint subscribers.
     
    Source: FCC
  4. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    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

  5. WiWavelength
    by Andrew J. Shepherd and Robert Herron
    Sprint 4G Rollout Updates
    Friday, April 6, 2012 - 2:20 PM MDT
     
    Today, S4GRU brings you the wireless equivalent of the much sought after paparazzi photo of the newborn celebrity baby. In an S4GRU exclusive, here is the first published look at a live Sprint LTE signal.
     
    Sprint recently lit up a cluster of Network Vision sites in Olathe, KS within Sprint's Kansas market. With trusty spectrum analyzer in tow, S4GRU staff ventured to Olathe this morning and captured a snapshot of Sprint's PCS G block 1990-1995 MHz allocation, clearly showing the up and running LTE OFDMA downlink coming from Sprint's completed Network Vision site (KC60XC009) in Black Bob Park. See below our PCS G block downlink frequency domain analysis:
     

     
    Additionally, S4GRU has mapped the live Network Vision cluster in Olathe and projected its RF footprint. See the approximated current LTE coverage map:
     

     
    Finally, we have also compiled an ongoing map of completed Network Vision sites as they go live. Come back and visit S4GRU.com often as work is completed on many more Network Vision sites in markets around the country, and see below for the most recent update:
     

     
    The old cliché says that a picture is worth a thousand words. So, we will keep this brief and let the images tell the story. But we are very excited to bring you this first inside look at PCS G block spectrum as it springs to life with Sprint's nascent LTE network.
     
    Sources: Sprint, author's spectrum analysis, author's RF map
  6. 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
  7. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, March 9, 2012 - 1:15 PM MST
     
    Sprint may soon be gaining some clarity regarding its Network Vision plans to deploy CDMA1X Advanced to replace Nextel iDEN in its rebanded SMR 800 MHz spectrum. The FCC today announced a proposed rulemaking that would explicitly allow SMR 800 MHz licensees (e.g. Sprint, SouthernLINC, and a few others) to utilize greater than 25 kHz channel spacing.
     
    Currently, Part 90 SMR 800 MHz rules and regulations could be interpreted to prohibit channel spacing exceeding 25 kHz, effectively disallowing any airlink other than iDEN, which is designed to operate in 25 kHz channelization. Meanwhile, Sprint has petitioned that Part 90 does not automatically bar larger channel bandwidths in contiguous channel blocks and that it has enacted improved filtering techniques to satisfy out of band emissions concerns due to wideband operations.
     
    To reconcile the current rules and regulations with Sprint's contentions, the proposed rulemaking would amend Part 90 as follows:
     
     
    More simply put, Sprint would be able to use its lower band SMR 800 MHz spectrum below 821 MHz x 866 MHz right away to deploy CDMA1X and/or LTE. Then, after all public safety relocation in a region has been completed, Sprint could utilize its upper band SMR 800 MHz spectrum 821-824 MHz x 866-869 MHz for further wideband operations.
     
    The proposed rulemaking aligns with and helps to explain Sprint Network Vision 3G plans that S4GRU has obtained. Those plans indicate that Sprint intends to deploy at least one CDMA1X Advanced band class 10 carrier channel centered at channel 476 (817.9 MHz x 862.9 MHz) and/or channel 526 (819.15 MHz x 864.15 MHz). This would place one or both CDMA1X carrier(s) within the lower band 817-820 MHz x 862-865 MHz spectrum and leave >1 MHz guard bands between it and 821-824 MHz x 866-869 MHz spectrum, in which public safety reconfiguration is still ongoing in some regions.
     
    To illustrate how Sprint proposes to roll out CDMA1X 800 at the lower end of its SMR 800 MHz spectrum allotment, see our band plan and channel assignment graphic:
     

     
    Sources: FCC, Sprint, author's graphic
  8. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, October 5, 2012 - 8:00 AM MDT
     
    Unless you have been under a telecom rock the past 48 hours -- or stuck in the boonies with only a GSM device (I kid, I kid) -- you have read that T-Mobile USA and MetroPCS have agreed in principle to a complicated reverse merger arrangement that would create a combined carrier, at least provisionally called NewCo. Now, Sprint has jumped back into the fray, this after Sprint's executive leadership had readied a bid for MetroPCS earlier this year but was vetoed by the board of directors. Sprint's motivations for pursuing a counter bid could be multifold.
    Sprint could actually be trying to acquire MetroPCS, feeling a sense of urgency that it did not this spring. Plus, Sprint's perception on Wall Street has improved dramatically during the past few months, making a merger a more financially palatable prospect. Sprint could be attempting to force T-Mobile to sweeten its offer for MetroPCS, potentially costing competitor T-Mobile additional financial resources. Sprint could be trying to gain some concessions in order to allow the merger to proceed. That last possibility is what this article will explore, namely, that NewCo would agglomerate an egregious amount of PCS 1900 MHz spectrum in several markets in which Sprint also happens to be a bit PCS spectrum shy. By throwing its own hat into the ring, Sprint should pressure NewCo to divest excess PCS spectrum to Sprint voluntarily. Alternatively, Sprint could lobby the FCC, oppose the merger and its transfer of spectrum licenses, and try to get some mandated divestitures that way.
    To illustrate, MetroPCS currently operates in at least some PCS spectrum in 10 major markets. The linked spreadsheet below compares NewCo's potential PCS A-F block spectrum holdings to Sprint's current PCS A-F block spectrum holdings in those 10 markets.
     

     
    https://docs.google.com/spreadsheet/ccc?key=0ArY31Mr219-ydE1tRVdJS19ocjBZXzVibk01Wm5wLWc&usp=sharing
    In those 10 markets, Sprint holds 20-30 MHz of PCS A-F block spectrum, while NewCo would have 35-60 MHz of PCS A-F block spectrum, including 50-60 MHz in four of the markets. Considering that 60 MHz represents fully half of the total 120 MHz bandwidth of the traditional PCS band, that is an outrageous amount of PCS spectrum -- especially for a carrier that is hitching its LTE wagon to AWS, not PCS. Even AT&T would blush at acquiring that much spectrum within a given band. Keep in mind, too, that this analysis does not take into account the 40-60 MHz of AWS 2100+1700 MHz spectrum that NewCo would hold in those same 10 markets, including 50-60 MHz in all but Atlanta. And that 50-60 MHz would be even more than half of the total 90 MHz bandwidth of the AWS band.
    Furthermore, T-Mobile has made it known that it intends to pare down its exclusively PCS GSM/GPRS/EDGE spectrum utilization to 10 MHz per market, refarming its remaining PCS spectrum to W-CDMA/HSPA+ in a desperate attempt to attract unsubsidized iPhone users. The Dallas Region Case Study graphic from the NewCo investor presentation corroborates this plan. Moreover, the graphic shows how NewCo plans to operate DC-HSPA+ (20 MHz) for at least the next three years in parallel on both PCS and AWS plus 15-20 MHz FDD LTE on AWS -- an unnecessarily redundant, inefficient strategy.

    In short, NewCo does not need as much PCS spectrum as it is set to acquire. Otherwise, it is just as much a spectrum glutton as are VZW and AT&T. So, here is the solution. In Atlanta, Jacksonville, Miami, Sacramento, and San Francisco, NewCo should preemptively choose to or be required to divest 10 MHz of its accumulated PCS spectrum. Sprint would be the obvious buyer, as that would increase its PCS A-F block assets to 30 MHz in those markets. Meanwhile, NewCo would still retain 35-50 MHz of PCS in those same markets, plenty of spectrum for 10 MHz of GSM, 10 MHz of HSPA+ or even 20 MHz of DC-HSPA+, and 10 MHz of CDMA1X/EV-DO for MetroPCS legacy.
     
    Sources: FCC, MetroPCS
  9. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Tuesday, July 3, 2012 - 2:54 PM MDT
     
    S4GRU continues with the third in a series of short articles on the FCC OET (Office of Engineering and Technology) authorization filings for "tentpole" devices headed to Sprint's upcoming Network Vision enhanced LTE overlay. Over the past few months, we have brought you the scoop on the FCC authorizations for the HTC EVO 4G LTE and the Samsung Galaxy S3. Today, the Motorola model number XT897 hits the FCC OET database with FCC ID IHDT56NL2, and we expect this mystery handset ultimately to be the Photon Q. Without further ado, here is the RF rundown:
     
    CDMA1X + EV-DO band classes 0, 1, 10 (i.e. CDMA1X + EV-DO 850/1900/800) LTE band 25 (i.e. LTE 1900; PCS A-G blocks) LTE 5 MHz and 10 MHz carrier bandwidths world phone international roaming capability 802.11b/g/n Wi-Fi; max MCS index 7 (i.e. 20 MHz channel, 400 ns guard interval, single spatial channel) SVDO and SVLTE support, including SVDO or SVLTE and simultaneous Wi-Fi tether Maximum RF ERP/EIRP: 22.45 dBm (CDMA1X 850), 19.89 dBm (EV-DO 850), 27.12 dBm (CDMA1X 1900), 24.03 dBm (EV-DO 1900), 21.72 dBm (CDMA1X 800), 19.33 dBm (EV-DO 800), 25.22 dBm (LTE 1900) NFC capability Antenna locations: CDMA1X bottom, EV-DO/LTE top, Wi-Fi/Bluetooth bottom  
    The Photon Q's FCC filing makes mention of world phone international roaming capability, albeit latent inside the handset. Presumably, it will include at least GSM 900/1800 and W-CDMA 900/2100+1900 (a la the international roaming capabilities announced to be unlocked in several VZW handsets). But, before anyone asks, do not expect any LTE international roaming capability.
    RF uplink output looks to be healthy. It is generally a bit higher than what we have seen recently from the EVO LTE and Galaxy S3.
    However, unlike the EVO LTE and Galaxy S3, the Photon Q lacks 802.11a/n Wi-Fi 5 GHz band capability. The filing indicates that the hardware is present, but 5 GHz operation is locked out. So, the Photon Q will be stuck in the increasingly overcrowded 2.4 GHz band.
    At this point, the LTE UE category remains unknown. Recent Motorola RAZR LTE handsets on VZW have used Moto's own Wrigley LTE baseband chipset, which has limited those devices to LTE UE category 2. We hope that the Photon Q will utilize the Qualcomm MSM8960 as a single chipset modem, as that should enable UE category 3.
    Perhaps the most interesting and potentially controversial aspect of the Photon Q's FCC authorization is the inclusion of two references to the Motorola Admiral, a front facing QWERTY handset currently available on Sprint. One reference cites the Admiral as a "similar transmitter;" the other reference flat out calls the Photon Q the Admiral. Thus, while some sites have leaked photos of what purports to be the Photon Q in the expected QWERTY slider design, we leave open the possibility, however modest, that the Photon Q may arrive as an LTE refreshed Admiral clone with a front facing QWERTY keyboard.
     

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

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

     
    For CDMA1X 800 network acquisition, therefore, Sprint band class 10 capable PRLs will have to include ACQ indices containing at least channels 476 and 526.
     
    Moreover, as S4GRU has unearthed, band class 10 PRLs will also have to include separate SID entries for SMR 800 MHz. For example, in the Dallas-Fort Worth market, Sprint has long used SID 04120, but CDMA1X 800 will fall under new SID 22407. In the Atlanta market, Sprint operates under SID 04274, while CDMA1X 800 will take on SID 22437. NIDs, though, appear to be consistent between PCS 1900 MHz and SMR 800 MHz. Expect Sprint to establish a second SID for each one of its markets, hence just under 50 new SMR 800 MHz SIDs in total.
     
    We surmise that Sprint will use the distinct new SIDs to control access and network loading on the lone CDMA1X 800 carrier channel in each market. By Sprint placing SMR 800 MHz SIDs at lower priority in PRLs, the vast majority of Sprint devices will remain on CDMA1X 1900 in almost all native coverage settings. Devices will seek out CDMA1X 800 only when CDMA1X 1900 is unusable or unavailable. Savvy PRL builders, however, could certainly take advantage of this situation by editing PRLs to invert priority and favor CDMA1X 800 instead, thereby directing devices to remain on SMR 800 MHz wherever possible.
     
    S4GRU will continue to dig up CDMA1X 800 SIDs for additional markets. As we do, we will post updates. So, stay tuned.
     
    Update: We have learned new SMR 800 MHz SIDs for several West Coast markets: San Francisco-Oakland-San Jose, Portland, and potentially Seattle or Spokane, too. In the Bay Area, Sprint's CDMA1X 1900 network uses SID 04183, while the upcoming CDMA1X 800 overlay will use SID 22431. Similarly, in Portland, Sprint will continue to utilize SID 04174 for PCS 1900 MHz and will add SID 22428 for SMR 800 MHz. Sprint in Seattle and Spokane uses SID 04186 and SID 04188, respectively. S4GRU has discovered SMR 800 MHz SID 22408 linked to rural parts of the Seattle and Spokane MTAs, but we are currently uncertain if this SID will apply to one or both actual metro areas.
     
    Update 2: Special thanks go to S4GRU reader and sponsor autoprime for reminding us of the IFAST national SID list web page, which just so happens to contain all of the SMR 800 MHz SIDs that we have announced, as well as ostensibly all of the other SMR 800 MHz SIDs for Sprint's remaining MTA based markets. The 224xx series SIDs were actually assigned to Sprint for its PCS G block nationwide collection of licenses, spectrum that was assigned to Nextel as compensation for SMR 800 MHz bandwidth it lost during the 800 MHz public safety rebanding effort. Sprint originally intended to deploy band class 14 CDMA1X/EV-DO in that PCS G block 10 MHz spectrum but now will use it exclusively for band class 25 LTE (5 MHz x 5 MHz), the initial LTE carrier that Sprint will launch in its Network Vision initiative. Since band class 14 CDMA1X/EV-DO is now off the table, Sprint appears to have carried over the 224xx series SIDs to its SMR 800 MHz band class 10 CDMA1X deployment. Keep in mind, however, that these remaining SIDs have yet to be verified, so there may be some differences between the list and actual use. S4GRU will endeavor to confirm additional SIDs as we analyze further information from our internal Sprint sources. In the meantime, we have condensed all assigned 224xx SIDs to this Google Docs spreadsheet.
     
    Sources: Sprint, SouthernLINC, FCC, 3GPP, author's graphics, autoprime, IFAST
  12. 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
  13. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Wednesday, February 22, 2012 - 4:20 PM MST
     
    While the name of the bill might seem to suggest otherwise, the Middle Class Tax Relief and Job Creation Act of 2012 currently working its way through Congress contains several provisions that have direct bearing on the wireless industry.
     
    One, it assigns directly to public safety the Upper 700 MHz D block 10 MHz (5 MHz x 5 MHz) nationwide license—which had been intended for a public-private national network partnership but failed to reach its reserve price at FCC auction in 2008—and provides financing for the construction of a national public safety network.
     
    Two, it authorizes the FCC to conduct incentive auctions in which UHF TV broadcasters can voluntarily give up their broadcast channels in exchange for compensation so that their spectrum may be repurposed for wireless broadband.
     
    Three, it directs the FCC to auction within the next three years additional spectrum between 1600 MHz and 2200 MHz, including the creation of yet another PCS 1900 MHz block, the ostensibly named PCS "H" 10 MHz (5 MHz x 5 MHz) block. See the relevant portion of the draft bill:
     

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

     
     
    Prior to auction, the PCS "H" block would most probably be divided into geographic licenses, and any current or future wireless carrier could bid on one or all licenses. So, Sprint would not be guaranteed to win any PCS "H" spectrum. But Sprint would gain the greatest utility from PCS "H" spectrum because it could be most easily combined with Sprint's existing PCS G spectrum for 10 MHz x 10 MHz LTE. Thus, consider this a brief, early look at how Sprint could likely augment its spectrum portfolio in the coming years.
     
    Sources: US House of Representatives, FCC, author's notes; special thanks to TMF Associates, Public Knowledge
  14. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Thursday, November 12, 2015 - 3:07 PM MST
     
    Yes, you read that correctly. Thanks to the mid range Qualcomm Snapdragon 617 (MSM8952), the HTC One A9 is the first Sprint handset to include a modem that supports uplink 2x CA (carrier aggregation). That comes on die via the X8 LTE modem, which is a Category 7 LTE baseband, capable of aggregating up to 40 MHz FDD/TDD 2x CA on both the uplink and downlink. Now, before anyone gets too excited, Sprint has no imminent plans to enable uplink 2x CA at the network level. So, the uplink 2x CA support is mostly a proof of concept novelty.
     
    If you have been reading The Wall at S4GRU for a while, you probably know where this is headed. It is another in our classic series of FCC OET (Office of Engineering and Technology) RF authorization analysis articles. We do not dwell on processor benchmarks, screen qualities, etc. If you want that info, read reviews or visit the HTC tech specs site. Instead, we cut right to the heart of what a cellphone is -- a cellular RF device -- and rundown its lab tested cellular RF performance.
     
    The One A9 filed its FCC OET authorizations over a month ago, but with Sprint selling the handset as we speak and HTC shipping the unlocked Sprint variant next week, we should take a look. Let us start with the band/class support:
    CDMA2000 Band Class 0/1/10 GSM 850/900/1800/1900 W-CDMA Band 1/2/4/5 LTE Band 2/4/5/12/25/26/41 The Sprint and CCA/RRPP band support is expected at this point. But all of the GSM/W-CDMA band support info comes directly from the HTC tech specs. I state that explicitly because there is no testing of domestic GSM/W-CDMA in the FCC OET documents. Barring a Class II Permissive Change filing with the FCC, the GSM/W-CDMA support purely is for international roaming. While the Sprint variant One A9 can be unlocked or even purchased unlocked, it is not authorized for use on AT&T or T-Mobile -- unless you can live with no GSM/W-CDMA, only band 2/4/5/12 LTE.
     
    For an unlocked One A9, HTC proactively has addressed the to/from Sprint provider switch issue by including that in its one time courtesy UH OH Protection program:
     
    In other words, want to switch from Sprint to AT&T, T-Mobile, or VZW with your unlocked One A9? HTC will swap out for the other domestic variant. Want to switch from AT&T, T-Mobile, or VZW to Sprint with your unlocked One A9? HTC will swap out for the Sprint variant. While on the subject of the AT&T, T-Mobile, and VZW variant, it is 3GPP only, thus VoLTE only for voice on VZW. HTC even acknowledges that fact:
     
    The other domestic variant has some further relevance as we delve into the FCC authorized lab tested ERP/EIRP performance of the Sprint variant.
     
    The FCC OET documents, per usual, do not disclose an antenna diagram. But they do note that the One A9 uses a dual antenna system -- antenna 0 and antenna 1, presumably top and bottom or vice versa. The handset will switch between the antennas at will based upon varying signal metrics. Much like Apple with the iPhone, HTC has implemented this dual antenna setup since the debut of the One M7 in 2013. In this case, however, the dual antennas are still single radio path, so SVLTE is not supported.
     
    Now, for the main attraction, let us look at the Sprint variant One A9 radiated power figures. I may sound like a broken record, but the usual clauses about lab testing versus real world performance and uplink versus downlink always apply. The figures represent my best averaged and rounded estimates of maximum uplink ERP/EIRP test results provided to the FCC OET in the authorization filings for the device. See below:
    Band Class 0: 17 dBm Band Class 1: 22 dBm Band Class 10: 18 dBm Band 2: 16-19 dBm Band 4: 13-16 dBm Band 5: 14-16 dBm Band 12: 14 dBm Band 25: 17-19 dBm Band 26: 16-17 dBm Band 41: 21-22 dBm The CDMA2000 performance is good, about average. And the band 41 output is along the same lines. That is about the best S4GRU can say regarding the tested results of the One A9. It does not quite hit the lows of the VZW variant Samsung Galaxy Note 3 -- the most anemic RF test results that S4GRU has ever seen in any notable handset -- but the One A9 is not far off. The band 4 output that maxes out as low as 13 dBm, for example, is very weak. It is mid band spectrum that needs greater EIRP. The positive is that band 4 roaming never may be a factor with this handset. And band 2/25 is a bit better, though still at least 4-5 dB below the desired level.
     
    Now, back to the other domestic variant headed to AT&T, T-Mobile, and VZW. The picture does not get much rosier. Comparing the 3GPP bands in common, the other domestic variant is superior by 2-7 dB in band 2, 6-9 dB in band 4, 2-4 dB in band 5, and 2 dB in band 12. Wow, those are big differences nearly across the board. The Sprint variant does get one minor victory -- it is 1-2 dB better in band 41 than the other domestic variant is in band 7, as both band 41 and band 7 operate in the same BRS/EBS 2600 MHz spectrum.
     
    What happened, HTC? The Sprint variant seems to have gotten shortchanged. Was that a compromise to optimize band 41 by 1-2 dB? We can hope for better returns in real world performance. But early returns from lab tested performance are not good.
     
    Sources: FCC, HTC, Qualcomm
  15. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    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
  16. 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
  17. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Wednesday, February 15, 2012 - 4:45 PM MST
     
    Clearwire released its fourth quarter and full year 2011 results in a conference call with investors, analysts, and the media this afternoon. S4GRU was on the call to bring you this report.
     
    Clearwire highlighted its 8-K report with the following statistics:
    Record Fourth Quarter 2011 Revenue of $361.9 Million, Up 107% Year Over Year From $175.2 Million Full Year Revenues of $1.25 Billion, Up 134% Year Over Year From $535.1 Million Full Year Wholesale Revenues Up 876% Year Over Year to $493.7 million 2011 Total Ending Subscribers of 10.4 Million, Up 140% Year Over Year from 4.3 Million Achieves Positive Quarterly Adjusted EBITDA For the First Time of $22.5 Million Average Smartphone 4G Usage Increased 88% Year Over Year in Fourth Quarter 2011 Much of the rest of the report is focused on business metrics that may not be of particular use to anyone without an investment in Clearwire. But we did pore over the report to glean the following numbers of interest to S4GRU readers:
    BRS 2500-2600 MHz licensed spectrum valuation remained steady at $4.3 billion EBS 2500-2600 MHz spectrum lease costs totaled $309 million for 2011 WiMAX covered POPs increased year over year from 112 million to 132 million but plateaued at that level by the end of the second quarter Wholesale (e.g. Sprint) churn almost doubled from 1.5 percent to 2.9 percent during the fourth quarter To provide some analysis of the four points above, first and second, Clearwire holds an average of ~160 MHz of BRS/EBS spectrum bandwidth in the top 100 markets. However, as noted above, some of this spectrum (EBS) is leased from educational institutions, not licensed directly to Clearwire. Additionally, higher frequency spectrum is generally less valuable than is lower frequency spectrum. Otherwise, Clearwire's ~160 MHz of spectrum would be valued in the tens of billions of dollars.
    Third, as Robert has detailed in a forum post about "protection sites," Clearwire faced a May 1, 2011 FCC deadline to demonstrate at least minimum coverage in numerous Basic Trading Areas (BTA) across the country. As a result, Clearwire lit up numerous license "protection sites" around the country during the first few months of last year, leading to the 20 million POPs increase that then stalled for the remainder of the year, as Clearwire made the decision to cease WiMAX deployment and switch to LTE.
    Fourth, Sprint is Clearwire's largest wholesale partner. Any Sprint retail subscriber who has a WiMAX capable device is technically also counted as a Clearwire wholesale subscriber. While Clearwire churn remained relatively flat through the first three quarters, it spiked in the fourth quarter. Clearwire attributed the increase in wholesale churn in large part to Sprint offering the iPhone 4S, which is not WiMAX capable.
    Lastly, Clearwire addressed some of its plans for its TD-LTE 2500-2600 overlay. Clearwire reiterated its commitment to the TDD "ecosystem," alongside strategic partners China Mobile, et al., and to TDD/FDD interoperability that will allow for seamless roaming on both types of LTE networks. Clearwire expects to start build out on its LTE Advanced ready TD-LTE overlay in the second quarter, spending $400 million this year and $200 million next year, keeping costs low because much of the WiMAX infrastructure can be reused for TD-LTE. Build out goals in phase one include 8000 TD-LTE sites, at least 5000 of which are to be live by June 2013. In the WiMAX build out, Clearwire selected its own independent site locations, and this led to great inconsistencies between Clearwire and Sprint coverage. But in the TD-LTE build out, Clearwire and Sprint will work together to identify sites within the Sprint portfolio that exhibit the "highest 4G data usage potential" with fallback to the Sprint FDD LTE 800/1900 network outside of those Clearwire data "hotspots." Finally, both Clearwire and Sprint project multi-band, multi-mode TDD/FDD LTE devices that can utilize the Clearwire TD-LTE overlay to be available by June 2013, by the same time that the first 5000 sites should be online.
     
    Source: Clearwire
×
×
  • Create New...