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 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
  2. 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
  3. 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

  4. 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
  5. 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
  6. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, February 22, 2013 - 2:55 PM MST
     
    Update: Many hands on reviews of the HTC One are emerging this week. Courtesy of Engadget, we can report that the Sprint variant is one of the very first Sprint LTE handsets to include a removable micro-SIM. Removable SIM cards have long been part of the Network Vision roadmap for 2013, so it looks like that time may have arrived.
     
    S4GRU welcomes you to the first major Sprint handset announcement of 2013. Earlier this week, the upcoming HTC One was revealed at an event in New York City. Not to be confused with last year's HTC One X, the HTC One is the new flagship of the line and will be offered by dozens of carriers around the world, including AT&T and T-Mobile in the US. Last year, Sprint got essentially a customized version of the HTC One X in the HTC EVO 4G LTE. This year, however, another EVO handset is not currently in the offing, and Sprint is joining its fellow carriers in standardizing around a universal HTC One platform. The only notable customization is for Sprint's specific CDMA2000 band classes and LTE band. And that Sprint variant had its authorization documents uploaded to the FCC OET (Office of Engineering and Technology) database earlier today.
     
    If you have followed our series of articles on the EVO LTE, Samsung Galaxy S3, Motorola Photon Q 4G, LG Optimus G, and Samsung Galaxy Note 2, then you know what is at hand. Here is an RF focused breakdown of the HTC One coming to Sprint:
    CDMA1X + EV-DO band classes 0, 1, 10 (i.e. CDMA1X + EV-DO 850/1900/800)
    LTE band class 25 (i.e. LTE 1900; PCS A-G blocks)
    LTE 5/10 MHz FDD carrier bandwidth
    LTE UE category 3
    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.11a/b/g/n Wi-Fi tether
    NFC
    Antenna 0 max RF ERP/EIRP: 20.10 dBm (CDMA1X/EV-DO 850), 23.80 dBm (CDMA1X/EV-DO 1900), 19.23 dBm (CDMA1X/EV-DO 800), 12.30 dBm (LTE 1900)
    Antenna 1 max RF ERP/EIRP: 13.78 dBm (CDMA1X/EV-DO 850), 13.58 dBm (CDMA1X/EV-DO 1900), 14.27 dBm (CDMA1X/EV-DO 800), 23.63 dBm (LTE 1900)
    Antenna locations: (see FCC OET diagram below)
    Simultaneous transmission modes: (see FCC OET diagram below)


     

     
    As for analysis of the specs, the HTC One is the world's first handset to include the new 802.11ac Wi-Fi standard. But let us address right away another potential first that has become the so called elephant in the room. The Sprint version of the HTC One is limited to band 25 LTE 1900. It does not support either of Sprint's upcoming LTE bands -- band 26 LTE 800 and band 41 TD-LTE 2600. One or both of those bands are expected to be incorporated in new handsets sometime this year, but the HTC One will not be the first.
     
    The other notable absence is SVDO support for simultaneous CDMA1X voice + EV-DO data, though its omission is growing less and less notable as time goes on. SVDO requires separate RF paths for CDMA1X and EV-DO. The first few Sprint LTE handsets did support SVDO, utilizing separate paths for CDMA1X and EV-DO/LTE. But the last nine Sprint LTE handsets have foregone SVDO, combining CDMA1X/EV-DO on a single path, so SVDO was likely just a temporary measure or a fringe benefit of the Qualcomm MSM8960 chipset and will not be a common Sprint handset feature going forward.
     
    In its press release earlier this week, Sprint calls its HTC One an "international" smartphone, and that could be interpreted to mean world roaming capabilities. The FCC authorization documents show no evidence of this, but they are not required to do so, since the FCC is a US authority. What is lacking, though, is any GSM 850/1900 or W-CDMA 850/1900. So, if the HTC One is world roaming capable, it will most likely be limited to GSM 900/1800 and band 1 W-CDMA 2100+1900.
     
    Since the HTC One is really the de facto successor to the EVO LTE, a little bit of comparison would be in order. In our RF rundown article on the EVO LTE last spring, we stated that it "does not look to be a stellar RF performer" based on its low to moderate ERP/EIRP figures. And our prediction proved quite prescient, as the EVO LTE has not been noted for its performance with weak signals. The good news is that, on paper, the HTC One looks to be a notable improvement in this regard.
     
    First, the dual antenna system is optimized for CDMA1X/EV-DO on antenna 0 and LTE on antenna 1. But as long as only one antenna is in use (i.e. SVLTE is not active), the dual antennas can be switched at will to combat an RF fade at one antenna but not the other. Second, LTE max EIRP has been increased by 4 dB over that of the EVO LTE. Furthermore, LTE EIRP has been maximized around the 1912.5 MHz center frequency, 5 MHz FDD carrier bandwidth configuration that Sprint is currently deploying nationwide in its PCS G block spectrum. In short, the Sprint variant of the HTC One has been tweaked specifically for the Sprint LTE network.
     
    Source: FCC
  7. 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
  8. 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
  9. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, June 1, 2012 - 11:58 PM MDT
     
    Update: Sprint has scheduled an exclusive Samsung event for the evening of June 12 in Boston. It looks like the Samsung Galaxy S3 coming out party has been set.
     
    Just as the HTC EVO 4G LTE is setting up for its delayed national street date tomorrow June 2, it may sooner than expected be getting another high profile cousin in Sprint's burgeoning line up of Network Vision ready, LTE capable devices.
    First, word leaked this afternoon that Sprint is prepping landing and pre-order web pages for its version of the Samsung Galaxy S3. Then, this evening, S4GRU uncovered the Samsung SPH-L710 (aka Galaxy S3) exhibits that had hit the FCC OET (Office of Engineering and Technology) database earlier today. So, the ball seems to be rolling toward an imminent launch for the Galaxy S3. And, as we did with the EVO 4G LTE a few weeks back, here is an RF focused technical rundown of the upcoming Samsung flagship Sprint handset:
    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 carrier bandwidth LTE UE category 3 SVDO and SVLTE support, including SVDO or SVLTE and simultaneous 802.11a/b/g/n Wi-Fi tether Maximum RF ERP: 17.78 dBm (CDMA1X 850), 20.77 dBm (EV-DO 850), 24.05 dBm (CDMA1X 1900), 23.85 dBm (EV-DO 1900), 17.21 dBm (CDMA1X 800), 17.56 dBm (EV-DO 800), 22.01 dBm (LTE 1900) NFC antenna integrated into battery LTE antenna configuration: 1 Tx, 2 Rx (i.e. 2x2 downlink MIMO)
    All in all, the Galaxy S3 does not present any really big technical surprises. As RF capabilities go, it follows very closely in the footsteps of the EVO 4G LTE. One of the few notable differences is that the Galaxy S3, like its Galaxy Nexus sibling, supports only 5 MHz x 5 MHz LTE carriers, while the EVO 4G LTE can do both 5 MHz x 5 MHz and 10 MHz x 10 MHz LTE bandwidths. However, Sprint has no definite plans to deploy 10 MHz x 10 MHz LTE during the typical lifespan of either of these handsets. And, otherwise, the Galaxy S3 does appear to have the general edge in RF transmit power.
     
    Sources: FCC, Inside Sprint Now
  10. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Thursday, November 8, 2012 - 1:10 PM MST
     
    Update: Six weeks later, Sprint and U.S. Cellular have finally filed their PCS 1900 MHz license assignment applications in the FCC ULS database. From the filing, we have learned that USCC will not relinquish all of its PCS spectrum in Springfield and Champaign, so the primary market spectrum table below has been updated to reflect that clarification. In a nutshell, Sprint will acquire a consistent PCS B block 20 MHz partition and disaggregation in all affected counties in the Chicago MTA and a consistent PCS A block 10 MHz partition and disaggregation in all affected counties in the St. Louis MTA. For a complete list of the counties included in the spectrum transaction, see this spreadsheet from the FCC filing.
     
    Yesterday, Sprint and U.S. Cellular announced an agreement to transfer PCS 1900 MHz spectrum and subscribers in several midwestern markets -- notably, Chicago, St. Louis, Ft. Wayne, South Bend, Springfield (IL), and Champaign -- from USCC to Sprint. While this transaction does entail that USCC will exit its largest and home market, Chicago, it is not a merger. Overall, USCC will give up 585,000 subs but will retain over 5 million current subs, and the deal involves no transfer of wireless infrastructure. Rather, the existing USCC CDMA2000 infrastructure in the affected markets will be retired within approximately two years, as subs are transitioned to the Sprint network. The exact boundaries of the PCS licenses and subs to be transferred from USCC to Sprint have not yet been revealed on a county by county basis. So, this article will be updated once the FCC assignment applications are filed or any other further info arises.
    In the meantime, know that this is a spectrum transaction, bar none. Chicago is Sprint's largest market in which it holds only 20 MHz of PCS A-F block spectrum. In nearly all other top 10 markets, Sprint holds 30 MHz of PCS A-F block spectrum. And Ft. Wayne is a proverbial red headed stepchild market -- Sprint's only top 100 market with only 10 MHz of PCS A-F block spectrum. So, most importantly, this transaction provides a 20 MHz PCS injection into Sprint's spectrum holdings in both Chicago and Ft. Wayne. For a look at the five largest markets included in the deal, see the spectrum table below:

    Moreover, Sprint's existing PCS D block 10 MHz and PCS E block 10 MHz licenses in Chicago are non adjacent. As such, Sprint has to run an extra set of guard bands -- one set of guard bands for each license. Those extra guard bands take up valuable spectrum, limiting Sprint to only six instead of seven CDMA2000 carriers in its 20 MHz of spectrum and leaving more sites in Chicago spectrum constrained than in any other big market. Synergistically, though, the PCS B block 20 MHz license that Sprint will acquire in Chicago is directly adjacent to its existing PCS D block 10 MHz license, giving Sprint a fully 30 MHz contiguous swath of PCS spectrum, which will allow Sprint to deploy additional CDMA2000 carriers and larger LTE bandwidth (10-15 MHz FDD) when the time comes to add LTE capacity. See the license contiguity in the band plan diagram below:

    Speaking of LTE, that is one of the key reasons why USCC is willing to part with its Chicago market. In most of its markets, USCC holds some combination of Cellular 850 MHz, PCS 1900 MHz, AWS 2100+1700 MHz, and Lower 700 MHz spectrum. But in Chicago, USCC controls only the aforementioned 20 MHz block of PCS spectrum. USCC entered the Chicago market just 10 years ago when it acquired PrimeCo, which had been divested as part of the merger that created Verizon Wireless. Since then, USCC has been unable to acquire additional spectrum in Chicago, leaving it effectively incapable of deploying LTE in its largest market while continuing its CDMA2000 operations. So, the deal with Sprint provides an exit strategy for Chicago in what was otherwise a dead end market for USCC.
    In the other five of the six markets detailed above, USCC likely could roll out LTE, as it holds additional AWS 2100+1700 MHz and/or Lower 700 MHz licenses in those markets. It should be noted, however, that those non PCS licenses are not being transferred to Sprint in this deal. But as it exits those markets, USCC will almost surely look to sell the other licenses, too, with VZW and T-Mobile being likely buyers for the AWS spectrum, AT&T a strong possibility for some of the 700 MHz spectrum.
    Sources: FCC, USCC, Sprint

  11. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, May 8, 2015 - 12:15 PM MDT
     
    Update: A week after the Sprint variant LG G4 original authorization documents were released at the FCC OET and S4GRU published this RF performance article, a Class II Permissive Change filing was added to the G4's docket. In writing the article last week, we did not detect anything amiss with the original filing, so this represents an optional change, which the filing discloses as hardware modification affecting the main antenna. Interestingly, none of the previous antenna gain figures have been altered, but the ERP/EIRP figures have increased or decreased. See the smoothed and averaged differences below:
    Band class 0: -1 dB Band class 10: -2 dB Band 4: -3 dB Band 5: -2 dB Band 12: -2 dB Band 26: -2 dB Band 41: +2 dB So, you win some, you lose some. Overall, the Sprint variant G4 has become weaker in tested RF performance. Those negative differences, however, are limited mostly to lower frequencies in the 700-1700 MHz range. The 1900 MHz range is unaffected, and the 2600 MHz range is increased. The other win is that a Class II filing before a device is released generally means that release is imminent. Look for the G4 on shelves and online soon.
     
    Yes, I know it is no longer May 4th. And we are not in a Samsung Galaxy far, far away. But this is episode IV in the LG G handset series, just four days removed from May 4th. That should be enough of the number four to satisfy anyone. Even if this isn't the Motorola Droid you're looking for, is the LG G4 a new hope for a flagship Sprint handset this spring?
     
    S4GRU staff has been watching the FCC OET (Office of Engineering and Technology) authorization database over the past week as different G4 variants were revealed. The VZW variant came earlier in the week, and the Sprint variant ZNFLS991 documents were uploaded yesterday. Of course, we are going to write an article about it, so let us get started.
     
    Right away, the G4 adheres to what has become the standard Sprint variant configuration: tri band LTE, non SVLTE, single RF path with e/CSFB. Additionally, it covers the CCA/RRPP LTE bands. And it was tested for domestic GSM/W-CDMA bands -- phone unlockers rejoice. Finally, it does officially support downlink carrier aggregation as its lone Release 10 feature. More on CA later.
     
    Next, it is fairly well known and somewhat controversial that the G4 opted not for the top of the line Qualcomm Snapdragon 810 but for the lesser Snapdragon 808, taking some performance hits in graphics and memory departments, for example. S4GRU does not involve itself in that debate -- that is not the place of this cellular RF focused article. But the chipset choice is relevant because both the Snapdragon 808 and Snapdragon 810 incorporate the same Category 9 X10 LTE baseband on die. So, rest assured, the choice of the Snapdragon 808 does not lessen any RF capabilities.
     
    On that topic, if you need a refresher on the new Qualcomm LTE baseband naming/numbering scheme, see this sidebar from our earlier article on the HTC One M9 and Samsung Galaxy S6:
     
     
    Back to discussion of CA support, we have stated previously that FCC OET authorization filings are not required to disclose downlink CA -- because that is only reception, not transmission. But the G4 filing does include an explicit attestation letter, stating its inclusion of downlink CA. What the G4 filing does not divulge is specifically 2x or 3x downlink CA support in band 41. For various reasons, S4GRU believes the former, that the G4 is capable of band 41 2x CA.
     
    First, the Snapdragon X10 LTE baseband natively supports up to 60 MHz of 3x downlink CA. However, that requires some help. An RF transceiver sits ahead of the baseband, and presently, the Qualcomm WTR3925 can handle 2x CA -- but 3x CA necessitates the inclusion of a second transceiver. See this excerpt from an AnandTech article on the new Snapdragon chipsets:
     
     
    Moreover, the other G4 variants that support CA are explicitly limited to 2x CA, suggesting that all variants are using the single WTR3925 transceiver. This is all educated conjecture, barring a teardown of the Sprint variant that probably will never happen. But if you are waiting on 3x CA, that likely will require a next generation Qualcomm transceiver to do 3x CA all in one.
     
    Finally, straight from the horse's mouth, Sprint CTO Stephen Bye stated the following in a recent FierceWireless article:
     
     
    Now, honestly, most read our FCC OET authorization articles for ERP/EIRP figures and analysis. So, without further ado, here are the numbers:
    Band class 0: 22 dBm Band class 1: 26 dBm Band class 10: 23 dBm Band 2: 25 dBm Band 4: 24 dBm Band 5: 22 dBm Band 12: 17 dBm Band 25: 25 dBm Band 26: 22 dBm Band 41: 23 dBm For reference, the above figures represent our best averaged and rounded estimates of max uplink ERP/EIRP -- with uniquely Sprint frequencies receiving heavier weighting, if possible, in band class 10, band 25, and band 26. Of course, the usual disclaimers about lab testing versus real world performance apply.
     
    As for analysis, max RF output looks quite healthy across the board, comparing very favorably with that of the One M9 and soundly thrashing that of the disappointing Galaxy S6. In particular, the power output for CDMA2000 band classes is a good 3 dB higher than most.
     
    Note, if you are using the smart cover for wireless charging, though, ERP/EIRP is affected roughly -1 dB across the board. I am not a fan of wireless charging because of the power inefficiency involved, but the RF loss from the smart cover on the G4 appears considerably less than what we have seen from some previous handsets.
     
    If there is any caveat about the G4's RF capabilities, that would be its antenna gain, broken down by frequency range as follows:
    700 MHz: -5.9 dBi 800 MHz: -7.1 dBi 1700 MHz: -5.2 dBi 1900 MHz: -3.5 dBi 2600 MHz: 1.7 dBi Except for 2600 MHz, all are negative, significantly negative. And for comparison, again except for 2600 MHz, the VZW variant antenna gain in all bands tracks about 3 dB higher. The head scratcher, however, is that the lab performance between the two variants is remarkably similar, despite the differences in antenna gain.
     
    We have seen something like this before -- an LG handset that showed strong lab power output yet weak real world performance. Remember the LG Viper? That is the challenge in interpreting lab results. Low output always indicates weak performance. However, high output can be a mixed bag. But LG has a pretty good Sprint track record since the Viper, as the LG Optimus G, LG G2, and LG G3 were all at least average to good in the real world. And the LG manufactured Nexus 5 was practically a Jedi knight for its RF performance at the time.
     
    In the end, only many trials on Dagobah will tell if the G4 lives up to its powerful promise. Use the 4th, LG, use the 4th.
     
    Source: FCC, AnandTech, FierceWireless
  12. WiWavelength
    by 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
  13. 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
  14. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, August 17, 2012 - 1:14 PM MDT
     
    CDMA1X and EV-DO carrier channels are shared resources. In CDMA1X, many subscribers share the same carrier channel, their individual traffic kept theoretically orthogonal by code division. Likewise, in EV-DO, individual traffic is separated by time division. But what happens when Sprint (or any other CDMA2000 network provider) has deployed greater than one CDMA1X and/or EV-DO carrier channel on a given cell site? How does your handset determine which carrier channel to utilize?
    You might like to think that your handset would automatically choose the least loaded CDMA1X and/or EV-DO carrier channel. But that is not really the case. Instead, when multiple carrier channels are available, each cell site broadcasts a channel list message of the available carrier channels on that site. Upon receiving this list of multiple carrier channels, each handset then invokes a hashing algorithm to select which carrier channel to use. Think of it like a multi lane highway, but each car must choose a particular lane based on the car's license plate number.
    For CDMA1X, the hashing algorithm -- which is a kind of pseudo random number generator -- is seeded with the handset's ESN or the subscriber's MDN/MSID (i.e. phone number). Unless the subscriber changes devices or phone numbers, these values remain static, hence the carrier channel hash is quite predictable. And Sprint, for reference, seems to use MDN/MSID based hashing. Nearly a decade ago, I built a spreadsheet that emulates the CDMA1X hashing algorithm, downloadable as an XLS file.
    However, for EV-DO, the carrier channel hash is not quite so outwardly predictable. To seed the hashing algorithm, EV-DO uses a session number, which obviously varies from data session to data session. Each time that a handset powers up, crosses a SID/NID boundary, or even toggles airplane mode, for example, generates a new EV-DO data session, hence a new session number. And it is this session number that determines the output of the hashing algorithm.
    To demonstrate this process, I positioned myself in one location about a quarter of a mile distant from the north sector of a local cell site. Over the course of several minutes, I grabbed three screen caps of the EV-DO engineering screen on one of my handsets. In between each screen cap, I cycled airplane mode at least once, each cycle generating a new data session. In the span of four minutes, I was able to get my handset to hash to each of the three EV-DO carrier channels deployed on this site. When I arrived at the site, my handset hashed to PCS 0175, which is the third EV-DO carrier channel (F3) in the channel list message. The second and third hashes after toggling airplane mode several times were to PCS 0150 (F2) and to PCS 0100 (F1). See the Channel Number field depicted in the screen caps:
     

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

    The four CDMA1X carrier channels are PCS 0050, PCS 0075, PCS 0125, and PCS 0200. As is oft the case, the three aforementioned EV-DO carrier channels -- PCS 0100, PCS 0150, PCS 0175 -- are distinguishable by their slightly higher RF power output. Furthermore, for those curious, PCS 0025 (at the far left of the graph) and PCS 0225, PCS 0250, and PCS 0275 (at the right of the graph) are fallow spectrum on this site. If deployed, PCS 0025 would be the next EV-DO carrier channel (F4), PCS 0275 the final EV-DO carrier channel (F5), while PCS 0225 and PCS 0250 would be additional CDMA1X carrier channels.
    Back to the hashing algorithm, while it attempts to distribute users more or less evenly among available EV-DO carrier channels, it does not take into account several other factors, such as loading and backhaul. For example, if you are stuck on a carrier channel and sector with a few data hogs who have stronger signal than you do, your data speeds will likely suffer as the "fair and proportional" scheduler integral to the EV-DO airlink attempts to maximize total throughput by allocating greater time slots to the users with better signal quality. Additionally, backhaul may not be distributed evenly among deployed carrier channels, so it is possible that some carrier channels may have inherently greater data capacity than others do.
    Another benefit of rehashing to a different carrier channel is that you may be able to connect to a closer cell site. Because not all cell sites have the same number of deployed EV-DO carrier channels, carrier channel hashing is an imperfect process. To illustrate, the cell site (call it cell site "A") that I detailed above for this trial has three EV-DO carrier channels (F1, F2, F3), as duly noted. But the adjacent cell site to the north (call it cell site "B") has only two EV-DO carrier channels (F1, F2). A handset that hashes to F3 on cell site "A" will cling to carrier channel PCS 0175 even as it moves north well into the coverage area of cell site "B." Interference will not be a problem, as cell site "B" does not transmit PCS 0175, but signal strength (and data speeds) will diminish until cell site "A" drops below a network defined threshold, at which point the handset will handoff to cell site "B" and hash to PCS 0150. This can require substantial movement and/or time. So, if you always want the most crisp EV-DO handoffs, you can try to ensure that your handset always hashes to F1, the EV-DO carrier deployed on essentially every site in the market.
    To conclude, by no means is airplane mode a panacea for slow 3G data ills. EV-DO carrier channel deployment and backhaul can vary from site to site, while loading can also vary from site to site, even from minute to minute. And EV-DO networks in some cities are just generally overloaded. But if you are at work, in a restaurant, at a park, etc., and find yourself with unbearably slow 3G data or lower than usual signal strength for that location, try toggling airplane mode. A 30 second on/off cycle of airplane mode will start a new data session and could get your handset to rehash to another EV-DO carrier channel that is on a closer site, has better backhaul, and/or is currently less loaded.
     
    Sources: Qualcomm, author's field data
  15. 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
  16. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Wednesday, February 15, 2012 - 4:45 PM MST
     
    Clearwire released its fourth quarter and full year 2011 results in a conference call with investors, analysts, and the media this afternoon. S4GRU was on the call to bring you this report.
     
    Clearwire highlighted its 8-K report with the following statistics:
    Record Fourth Quarter 2011 Revenue of $361.9 Million, Up 107% Year Over Year From $175.2 Million Full Year Revenues of $1.25 Billion, Up 134% Year Over Year From $535.1 Million Full Year Wholesale Revenues Up 876% Year Over Year to $493.7 million 2011 Total Ending Subscribers of 10.4 Million, Up 140% Year Over Year from 4.3 Million Achieves Positive Quarterly Adjusted EBITDA For the First Time of $22.5 Million Average Smartphone 4G Usage Increased 88% Year Over Year in Fourth Quarter 2011 Much of the rest of the report is focused on business metrics that may not be of particular use to anyone without an investment in Clearwire. But we did pore over the report to glean the following numbers of interest to S4GRU readers:
    BRS 2500-2600 MHz licensed spectrum valuation remained steady at $4.3 billion EBS 2500-2600 MHz spectrum lease costs totaled $309 million for 2011 WiMAX covered POPs increased year over year from 112 million to 132 million but plateaued at that level by the end of the second quarter Wholesale (e.g. Sprint) churn almost doubled from 1.5 percent to 2.9 percent during the fourth quarter To provide some analysis of the four points above, first and second, Clearwire holds an average of ~160 MHz of BRS/EBS spectrum bandwidth in the top 100 markets. However, as noted above, some of this spectrum (EBS) is leased from educational institutions, not licensed directly to Clearwire. Additionally, higher frequency spectrum is generally less valuable than is lower frequency spectrum. Otherwise, Clearwire's ~160 MHz of spectrum would be valued in the tens of billions of dollars.
    Third, as Robert has detailed in a forum post about "protection sites," Clearwire faced a May 1, 2011 FCC deadline to demonstrate at least minimum coverage in numerous Basic Trading Areas (BTA) across the country. As a result, Clearwire lit up numerous license "protection sites" around the country during the first few months of last year, leading to the 20 million POPs increase that then stalled for the remainder of the year, as Clearwire made the decision to cease WiMAX deployment and switch to LTE.
    Fourth, Sprint is Clearwire's largest wholesale partner. Any Sprint retail subscriber who has a WiMAX capable device is technically also counted as a Clearwire wholesale subscriber. While Clearwire churn remained relatively flat through the first three quarters, it spiked in the fourth quarter. Clearwire attributed the increase in wholesale churn in large part to Sprint offering the iPhone 4S, which is not WiMAX capable.
    Lastly, Clearwire addressed some of its plans for its TD-LTE 2500-2600 overlay. Clearwire reiterated its commitment to the TDD "ecosystem," alongside strategic partners China Mobile, et al., and to TDD/FDD interoperability that will allow for seamless roaming on both types of LTE networks. Clearwire expects to start build out on its LTE Advanced ready TD-LTE overlay in the second quarter, spending $400 million this year and $200 million next year, keeping costs low because much of the WiMAX infrastructure can be reused for TD-LTE. Build out goals in phase one include 8000 TD-LTE sites, at least 5000 of which are to be live by June 2013. In the WiMAX build out, Clearwire selected its own independent site locations, and this led to great inconsistencies between Clearwire and Sprint coverage. But in the TD-LTE build out, Clearwire and Sprint will work together to identify sites within the Sprint portfolio that exhibit the "highest 4G data usage potential" with fallback to the Sprint FDD LTE 800/1900 network outside of those Clearwire data "hotspots." Finally, both Clearwire and Sprint project multi-band, multi-mode TDD/FDD LTE devices that can utilize the Clearwire TD-LTE overlay to be available by June 2013, by the same time that the first 5000 sites should be online.
     
    Source: Clearwire
  17. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    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
  18. 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
  19. 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
  20. 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
  21. 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/
  22. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Thursday, April 12, 2012 - 2:55 PM MDT
     
     
    A few weeks ago, S4GRU was the first to bring you the news of the HTC codenamed "Jet" that was recently unveiled as the HTC EVO 4G LTE headed to Sprint this summer. Today, the EVO 4G LTE applications hit the FCC OET (Office of Engineering and Technology) database. S4GRU brings you the technical rundown, including some important revelations.
     
     

    CDMA1X + EV-DO band classes 0, 1, 10 (i.e. CDMA1X + EV-DO 850/1900/800)
    LTE band class 25 (i.e. LTE 1900; PCS A-G blocks)
    LTE 5 MHz and 10 MHz channel bandwidths
    LTE UE category 3
    SVDO and SVLTE support, including SVDO or SVLTE and simultaneous 802.11a/b/g/n Wi-Fi tether
    Maximum RF ERP: 20.43 dBm (CDMA1X 850), 18.74 dBm (EV-DO 850), 22.98 dBm (CDMA1X 1900), 18.44 dBm (EV-DO 1900), 20.01 dBm (CDMA1X 800), 18.75 dBm (EV-DO 800), 19.85 dBm (LTE 1900)
    Antenna gain: -2 dBi (CDMA1X 850/1900/800), -3.5 dBi (EV-DO 850/1900/800 and LTE 1900)
    LTE antenna configuration 1x2 (i.e. 2x2 downlink MIMO)


     
     
    Prima facie analysis, no LTE 800 nor TD-LTE 2600 support comes as no surprise. But SVDO is a nice perk, as internal Sprint documents had not indicated its inclusion. Furthermore, SVDO/SVLTE plus simultaneous Wi-Fi tether capability really covers all of the connectivity bases. Most disappointing, however, is the rather low ERP output. While the EVO 4G LTE has a plethora of radio capabilities, it does not look to be a stellar RF performer, perhaps the consequence of the aluminum unibody in place of the polycarbonate unibody used in the more direct members of the HTC One X family of handsets.
     
    Source: FCC
  23. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Sunday, March 18, 2012 - 9:15 AM MDT
     
    But wait, there's more! Obtained from the same internal Sprint sources that allowed S4GRU to break the news earlier this weekend of the April 15th launches for the Samsung Galaxy Nexus and LG Viper, is intriguing info about a third LTE handset, the HTC codenamed Jet, set to land at a Sprint Store near you on June 10th. This happens to be nearly two years to the date that the HTC EVO launched as Sprint's first 4G WiMAX capable handset.
     
    S4GRU has connected the dots and projects the HTC Jet to be the Sprint version of the LTE capable HTC One high end handset introduced at Mobile World Congress in Barcelona last month and a version of which is also soon headed to AT&T. The One X is the only announced HTC handset to utilize the recently debuted and benchmarked Qualcomm Snapdragon S4 MSM8960 chipset and to include Near Field Communication (NFC) capability. The Jet matches both of those specs, suggesting that the Jet will be a CDMA1X/EV-DO/LTE entry in the One X lineup.
     

    Below are some of the One X and/or MSM8960 specs likely or known to carry over to the Jet:
    1.5 GHz dual core "Krait" (28 nm) CPU
    1 GB RAM
    CDMA1X, EV-DO Rev 0/A/B, LTE (UE category 3)
    LTE band class 25 (PCS A-G blocks)
    Wi-Fi 802.11a/b/g/n
    Bluetooth 4.0
    4.7' S-LCD 1280x720 screen
    Corning Gorilla Glass 2
    Solid polycarbonate body

    What remains to be seen about the Jet, unlike the Galaxy Nexus and Viper, is its actual name. HTC has instituted a plan to simplify its handset lineup both in number and in name. Going forward, HTC intends to brand all of its handsets under some variation of the One name (e.g. One X, One S). However, many have expressed that the EVO name is an important brand associated with Sprint that should carry on.
     
    So, could the Jet launch as the HTC One EVO? Will it simply be called the HTC One X for Sprint? Or might HTC Jet actually be more than just a codename? Regardless of the name, the release date and the specs indicate that this high end, very large screen LTE capable handset is the true successor to the WiMAX capable EVOs that came before it.


    Photo courtesy of Androidandme.com


     
     
    Sources: Sprint, HTC, Phone Arena, AnandTech
  24. 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
  25. 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
×
×
  • Create New...