Jump to content

WiWavelength

S4GRU Staff Member
 View Profile  See their activity

  • Posts

    18,133

  • Joined

  • Last visited

  • Days Won

    429

 Content Type 

Blog Entries posted by WiWavelength

  1. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Monday, July 16, 2012 - 1:40 AM MDT
     
    As Sprint LTE 1900 has become live and discoverable in numerous markets over this past weekend, some of our readers, especially those who are using Android 4.0 ICS based ROMs, have expressed concern at the seemingly low signal levels that they have encountered. For example, see this screenshot from an HTC EVO 4G LTE (under Settings > About > Network):

     
    Note the -102 dBm signal level. If this were measuring CDMA1X or EV-DO, then, yes, -102 dBm would be nearing the margin of usable signal. But -102 dBm is actually relatively healthy LTE signal level. To understand why, we need to learn the differences between two types of signal measurement: Received Signal Strength Indicator (RSSI) and Reference Signal Received Power (RSRP).
    First, an LTE downlink is divided into subcarriers. A 5 MHz bandwidth downlink, which is the configuration that Sprint is deploying, contains 300 subcarriers. And of those subcarriers, one in three carry LTE reference signals. In other words, of the 300 subcarriers, 100 transmit periodic reference signals.
    To illustrate, I captured this power vs frequency sweep with a spectrum analyzer. The LTE downlink graph comes from a Sprint site in the Kansas City area in late April, well before Sprint stopped blocking devices from live LTE sites. So, the sector depicted here exhibits no data traffic; it is transmitting only the periodic reference signals on 100 subcarriers, which you can clearly count in the graph:

    Now, RSSI is the more traditional metric that has long been used to display signal strength for GSM, CDMA1X, etc., and it integrates all of the RF power within the channel passband. In other words, for LTE, RSSI measurement bandwidth is all active subcarriers. If we take the above RF sweep of a Sprint 5 MHz bandwidth downlink, RSSI measures the RF power effectively of what is highlighted in yellow:

    RSRP, on the other hand, is an LTE specific metric that averages the RF power in all of the reference signals in the passband. Remember those aforementioned and depicted 100 subcarriers that contain reference signals? To calculate RSRP, the power in each one of those subcarriers is averaged. As such, RSRP measurement bandwidth is the equivalent of only a single subcarrier. And using our graph once more, RSRP measures the RF power effectively of what is highlighted in red:

    Since the logarithmic ratio of 100 subcarriers to one subcarrier is 20 dB (e.g. 10 × log 100 = 20), RSSI tends to measure about 20 dB higher than does RSRP. Or, to put it another way, RSRP measures about 20 dB lower than what we are accustomed to observing for a given signal level. Thus, that superficially weak -102 dBm RSRP signal level that we saw previously would actually be roughly -82 dBm if it were converted to RSSI.
    To conclude, here are a few takeaways about RSSI and RSRP as signal strength measurement techniques for LTE:
    RSSI varies with LTE downlink bandwidth. For example, even if all other factors were equal, VZW 10 MHz LTE bandwidth RSSI would measure 3 dB greater than would Sprint 5 MHz LTE bandwidth RSSI. But that does not actually translate to stronger signal to the end user. RSSI varies with LTE subcarrier activity -- the greater the data transfer activity, the higher the RSSI. But, again, that does not actually translate to stronger signal to the end user. RSRP does a better job of measuring signal power from a specific sector while potentially excluding noise and interference from other sectors. RSRP levels for usable signal typically range from about -75 dBm close in to an LTE cell site to -120 dBm at the edge of LTE coverage.  
    Sources: 3GPP, author's graphs
  2. 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
  3. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Monday, March 10, 2014 - 8:47 AM MDT
     
    After official unveiling at Mobile World Congress in Barcelona a few weeks ago, the Samsung Galaxy S5 made public its authorizations in the FCC OET (Office of Engineering and Technology) database at the start of this weekend. All of the domestic variants are there, including the A3LSMG900P, which in its tri band LTE configuration and "P" designation is the obvious Sprint variant.
     
    As expected of a Sprint high end handset, the Galaxy S5 ticks off all of the checkboxes: tri band LTE, UE category 4, global roaming capability, 802.11ac, NFC, wireless charging, etc. It also appears to improve upon the RF output of last year's single band Samsung Galaxy S4 and Galaxy Note 3. From a common uplink EIRP standpoint, the Galaxy S5 can max out up to 3-4 dB greater on band 25 LTE 1900, hitting 26.85 dBm in the middle of the PCS band, falling off 1-2 dB at the extremes of the band. Additionally, band 41 LTE max output looks relatively healthy at 25.03 dBm.
     
    In a pleasing move, the FCC authorization docs for the Galaxy S5 do include an antenna diagram -- something that is unfortunately becoming less common, per my mention in the recent HTC M8 FCC article. But in this case, we are able to show a visual of the dual WLAN antennas required for Wi-Fi 2x2 MIMO support, allowing MCS index raw data rates up to 300 Mbps over 802.11n and 866.7 Mbps over 802.11ac. Previously, two spatial stream Wi-Fi has been limited to some laptops and a select few tablets. Thus, the Galaxy S5 is pushing the handset envelope in that regard. See the antenna diagram below:
     

     
    Of course, with no separate CDMA2000 and LTE antennas, as depicted in the diagram above, the Galaxy S5 does not support SVDO nor SVLTE. No surprises there, since Sprint tri band LTE handsets have all been single radio path with e/CSFB.
     
    But continuing on the Wi-Fi front, the Galaxy S5 does include a unique simultaneous transmission mode: Wi-Fi and LTE. Now, this is not simultaneous Wi-Fi and LTE in the typical sense that Wi-Fi is used to tether an LTE connection. This is a dual IP stack connection over both Wi-Fi and LTE that Samsung dubs Download Booster, allowing packets to be split up and delivered by both connections, thereby increasing data speeds.
     
    Editorially, S4GRU has some concerns about inclusion of the bonded connection Download Booster, since it may engender "unlimited" data users to remain connected to LTE, too, while on secure Wi-Fi at home, work, school, etc. In most cases, Wi-Fi alone is sufficiently fast for all smartphone activities. And that is why S4GRU has long advocated offloading to Wi-Fi -- when/where possible and secure -- so as to help maintain valuable LTE capacity for truly mobile users. That said, we are curious to see the real world implementation of Download Booster before passing judgment.
     
    Finally, many hoped that the Galaxy S5 might be the first Sprint handset to support LTE Advanced carrier aggregation because Sprint plans to use its acquired Clearwire spectrum to aggregate multiple band 41 20 MHz TDD carriers. That capability, though, will have to wait for the presumed Samsung Galaxy Note 4, Galaxy S6, or some other device.
     
    The carrier aggregation omission is worth mentioning only because the A3LSMG900A variant headed to AT&T does support inter band downlink carrier aggregation. This allows the Galaxy S5 to bond up to 10 MHz FDD of AT&T's low frequency band 17 LTE 700 with up to 10 MHz FDD of its mid frequency band 2 LTE 1900 or band 4 LTE 2100+1700. Indeed, AT&T carrier aggregation is already in use in Chicago, as Gigaom's Kevin Fitchard reported last week.
     
    Well, that is the FCC skinny on the upcoming Sprint variant Galaxy S5. Nothing revolutionary on the cellular side of things, but with MIMO and Download Booster, it does offer up some interesting Wi-Fi enhancements.
     
    Sources: FCC, Samsung
  4. 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
  5. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Thursday, December 19, 2013 - 2:12 PM MST
     
    As most of our S4GRU readers are aware, Sprint is pursuing a three pronged approach to LTE. Tri band 25/26/41 LTE 1900/800/2600 -- the first two bands operating as FDD in Sprint and Nextel PCS 1900 MHz and SMR 800 MHz spectrum, the last operating as TDD in Clearwire BRS/EBS 2600 MHz spectrum.
     
    A year and a half ago in the early days of Network Vision, S4GRU was the first web site to offer a peek at a live Sprint LTE downlink carrier. We did likewise in running tri band hotspot field tests upon the emergence of Sprint/Clearwire TD-LTE 2600 in Denver this past summer.
     
    But the missing piece in the tri band LTE strategy has been the 800 MHz spectrum and the decisive propagation advantages it brings to the table. Then, three weeks ago, S4GRU was able to start sourcing inside info on a few but growing number of band 26 site acceptances around the country. And today, S4GRU presents an exclusive first look at a live Sprint LTE 800 carrier.
     

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

     
    Source: author's field test, S4GRU map data
  6. 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
  7. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Thursday, September 5, 2013 - 5:33 PM MDT
     
    About a month ago, our FCC OET reporter, Josh McDaniel, noted that a mystery handset, the LG D820, came and went from the FCC OET (Office of Engineering and Technology). Its authorizations were uploaded, then quickly rescinded, citing confidentiality reasons.
     
    Well, today, the LG D820 authorization documents are back. And we are looking at a 3GPP/3GPP2 handset that runs nearly the full North American wireless airlink gamut:
    GSM 850/1900 W-CDMA 1900/2100+1700/850 (band 2, 4, 5) CDMA1X/EV-DO 850/1900/800 (band class 0, 1, 10) LTE 2100+1700/850/700/1900/800 (band 4, 5, 17, 25, 26) TD-LTE 2600 (band 41) The only notable omission is LTE 750, VZW's currently boutique band 13 -- possibly left out for political reasons, since VZW has a strained relationship with Nexus devices, or for technical reasons, as band 13 has an inverted FDD uplink/downlink duplex. But in a nutshell, this handset looks like it could be headed to AT&T, T-Mobile, and Sprint, covering all of their bases.
     
    Here is the kicker, though. One of our moderators, Tim Yu, noted a significant resemblance between the back plate in the FCC OET filing and the back plate of a mystery Nexus device in a widely circulated photo recently from the Google campus.
     
     

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

     
    In fact, it is the first North American handset known to support LTE TDD carrier aggregation and intra band LTE carrier aggregation -- rather than inter band carrier aggregation, as we have seen in several AT&T variant handsets this year. That said, it is limited to two carrier aggregation with a maximum total bandwidth of 40 MHz TDD. Three carrier aggregation devices with a maximum total bandwidth of 60 MHz TDD will not make an appearance until sometime next year.
     
    And that is basically the good news. The rest of the news is not as good. The Galaxy Edge supports none of the additional CCA/RRPP bands -- not even bands 2/5, which are just subsets of bands 25/26, respectively. Moreover, the LTE ERP/EIRP is not very impressive. Fortunately, it looks hardly as poor in that regard as last year's VZW variant Galaxy Note 3 -- maybe the worst that we have ever seen in a flagship caliber smartphone -- but it averages just 17-20 dBm max output across bands 25/26/41. And, for reference, that runs about 2-3 dB worse than that of its recent Sprint variant Galaxy Note 4 sibling.
     
    The news could be worse, however. To conclude, just look at the cellular variant HTC Nexus 9 tablet. On the bright side, it, too, is a fully CCA/RRPP compliant device -- bands 2/4/5/12/25/26/41 -- also adding bands 7/13/17 like its Nexus 6 cousin. That band 12 tablet inclusion trumps even all Apple iPads for likely the next year. But the bright side does not extend beyond that in terms of actual RF.
     
    Originally, Google proclaimed the Nexus 9 to be a 3GPP/3GPP2 device. Since then, Google has pared that back to a 3GPP only device -- with the odd inclusion of EV-DO. The latter is almost assuredly yet another proofreading error, as the FCC OET authorization docs show no support for 3GPP2. Furthermore, reports are that the Nexus 9 uses a non Qualcomm baseband modem. Not good -- especially for a device that now rivals the iPad in price.
     
    For those who want the shorthand explanation, the cellular variant Nexus 9 looks to be compatible with Sprint -- but only Sprint LTE. It will have no support for Sprint CDMA2000. Additionally, the ERP/EIRP leaves much, much to be desired, averaging only 15-19 dBm maximum across all LTE bands. We generally expect more from antenna design in tablets because of their added size. However, that is certainly not the case with the Nexus 9.
     
    In summation, if you are making your shopping list, checking it twice, everything new in the Sprint stocking this holiday season is at least partly naughty, nothing entirely nice. Too big, too expensive, too focused on form over function, and/or too weak RF. Take your pick.
     
    Happy Thanksgiving? Or Bah Humbug?
     
    Source: FCC
  9. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    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
    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/
  11. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, October 5, 2012 - 2:00 PM MDT
     
    Earlier this week, the Samsung SPH-L900 authorization filing hit the FCC OET (Office of Engineering and Technology) database. Judging by the handset's expansive 150 mm x 80 mm dimensions, S4GRU firmly expects this device to be the upcoming Sprint version of the Samsung Galaxy Note 2 "phablet." In keeping with our previous articles on the HTC EVO 4G LTE, Samsung Galaxy S3, Motorola Photon Q 4G, and yet to be released LG Eclipse, here is an RF focused breakdown of the presumed Note 2's FCC disclosed tech specs:
    CDMA1X + EV-DO band classes 0, 1, 10 (i.e. CDMA1X + EV-DO 850/1900/800)
    LTE band 25 (i.e. LTE 1900; PCS A-G blocks)
    LTE 5 MHz FDD carrier bandwidth
    LTE UE category 3
    W-CDMA/HSPA band 2 (i.e. W-CDMA/HSPA 1900)
    GSM/GPRS/EDGE 850/1900
    GPRS/EDGE multislot class 10 (i.e. max 4 downlink, 2 uplink, 5 total timeslots)
    802.11a/b/g/n Wi-Fi
    SVLTE support, including SVLTE and simultaneous Wi-Fi tether (2.4 GHz only)
    SVDO support absent
    Maximum RF ERP/EIRP: 20.03 dBm (CDMA1X/EV-DO 850), 24.46 dBm (CDMA1X/EV-DO 1900), 20.25 dBm (CDMA1X/EV-DO 800), 28.35 dBm (GSM 850), 25.05 dBm (EDGE 850), 29.44 dBm (GSM 1900), 24.13 dBm (EDGE 1900), 21.41 dBm (W-CDMA 1900), 19.63 dBm (LTE 1900)
    NFC antenna integrated into battery cover
    CDMA1X/EV-DO Rx antenna diversity
    Antenna locations: (see FCC OET diagram below)


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

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

     
    In conclusion, if SVDO truly was sacrificed in order to include W-CDMA, that is a curious compromise, especially for a handset otherwise geared (e.g. band class 10 CDMA1X, band 25 LTE) specifically for Sprint.
     
    Source: FCC
  12. 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
  13. 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
  14. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Wednesday, October 24, 2012 - 12:05 PM MDT
     
    Over the past six months, Apple's iPad 3 has racked up millions of sales, yet Google's (and Asus') Nexus 7 and Microsoft's Surface tablets have grabbed the headlines over the summer and into the fall. Yesterday, Apple struck back by not only rolling out iPad 4 the same year as iPad 3 but also introducing the long rumored iPad mini. S4GRU readers will recall that Sprint was left out of the iPad 3 sweepstakes, Sprint's nascent LTE network making its debut a few months after iPad 3's announcement. Certainly, some will bemoan that iPad 3 has been replaced in only half the usual yearly upgrade cycle, but Sprint users definitely benefit, as Sprint is fully in the fold this time with LTE support on the VZW/Sprint/global versions of both iPad 4 (A1960) and iPad mini (A1955).
    As soon as Apple's announcement event concluded yesterday, authorization filings for the new Sprint compatible iPads (iPad 4, iPad mini) started popping up in the FCC OET (Office of Engineering and Technology) database. So, joining our series of articles on on the HTC EVO 4G LTE, Samsung Galaxy S3, Motorola Photon Q 4G, and soon to be released LG Eclipse and Samsung Galaxy Note 2 is an RF capability focused look at Sprint's first two iPads:
    CDMA1X/EV-DO band classes 0, 1, 10 (i.e. CDMA1X/EV-DO 850/1900/800) EV-DO Rev B Multi Carrier (i.e. 2xEV-DO, 3xEV-DO) LTE bands 1, 3, 5, 13, 25 (i.e. LTE 2100+1900/1800/850/750/1900) LTE 1900 1.4/3/5/10/15/20 MHz FDD carrier bandwidths W-CDMA bands 1, 2, 5, 8 (i.e. W-CDMA 2100+1900/1900/850/900) DC-HSPA+ (i.e. Dual Carrier) GSM/GPRS/EDGE 850/900/1800/1900 802.11a/b/g/n Wi-Fi Wi-Fi hotspot (2.4 GHz only) support for all cellular airlinks Maximum RF ERP/EIRP (iPad 4): 23.10 dBm (CDMA1X 850), 22.90 dBm (EV-DO 850), 30.12 dBm (CDMA1X 1900), 29.08 dBm (EV-DO 1900), 23.30 dBm (CDMA1X 800), 23.40 dBm (EV-DO 800), 29.78 dBm (LTE 1900) Antenna gain (iPad 4): -1.58 dBi (Cellular 850 MHz), 2.44 dBi (PCS 1900 MHz), -2.24 dBi (SMR 800 MHz) Antenna locations (iPad 4): (see FCC OET diagram below)
    The inclusion of EV-DO Rev B Multi Carrier and the imposed limitations -- Cellular 850 MHz only, no 64-QAM -- are a bit curious. But these limitations will have no ramifications for use in North America, where EV-DO Rev B has not been deployed. All told, though, both iPad 4 and iPad mini look to be solid RF performers. Not surprisingly, since they share the same Qualcomm MDM9615 modem with iPhone 5, both iPads carry over basically the same airlink capabilities from the Sprint compatible iPhone 5 -- see S4GRU writer Ian Littman's article. And it should be noted that iPad mini, despite its diminutive size, does not lag behind its larger sibling. All ERP/EIRP figures are within ~1 dB between both iPads. In fact, for both EV-DO 1900 and LTE 1900 maximum EIRP, iPad mini trumps iPad 4 by ~0.5 dB. Furthermore, both iPads in their high ERP/EIRP outputs are less like power and size constrained handsets, more like mobile hotspots. Indeed, both iPads appear to be very capable hotspot devices.
     
    Sources: FCC, Apple
  15. 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

  16. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, August 19, 2016 - 2:04 AM MDT
     
    Earlier this week, the two HTC 2016 Nexus handsets -- codenamed "Marlin" and "Sailfish" -- were caught in the net of the FCC OET (Office of Engineering and Technology) authorization database.
     
    While Google has yet to reveal them officially as Nexus handsets, that HTC is the manufacturer of choice this year has been a heavily leaked secret the past few months. And the circumstantial evidence now is overwhelming.
     
    The FCC grantee code, NM8G, appends a "G" to the usual NM8 grantee code for HTC branded devices, and the user manual declaration document posits that the final draft manual will be available publicly on the Google web site in the Nexus support section. Neither handset has been identified or named individually, though the 2PW4100 likely is the larger "Marlin," the 2PW2100, the smaller "Sailfish."
     
    Both are at least the domestic variants with airlink support across the board for VZW, AT&T, T-Mobile, and Sprint. No international variants have passed through the FCC OET. Unless international variants do get authorized in the coming days/weeks, the two HTC Nexus handsets could end up in uncharted waters as single variants for the world, covering all supported international LTE bands, too. Full disclosure, however, probably will have to wait until the Google announcement event when accompanying tech specs are published.
     
    In the meantime, the domestic RF uplink test results and declarations are out in the world. S4GRU will not run down every last RF capability. But, just to confirm, some of the highlights are...
    LTE bands 2/4/5/7/12/13/17/25/26/29/30/41 VoLTE bands 2/4/5/12/13 (for VZW, AT&T, and T-Mobile) Downlink 2x/3x CA Dual, switched WWAN Tx antennas 0 and 1, bottom and top 802.11ac 2x MIMO The primary purpose of this article is to present a retrospective on the uplink RF powers of the current 2013-2016 era of 3GPP/3GPP2, Sprint compatible Nexus handsets as well as two recent HTC handsets. Those domestic variant Nexus handsets and the Sprint variant HTC One A9 and HTC 10 are the RF and design forebears of the 2016 Nexus handsets. So, how do the new kids on the block hold up to their predecessors?
     
    S4GRU culled relevant data across all eight handsets from thousands of pages of authorization documents in the FCC OET. For the radiated power figures, the usual clauses about lab testing versus real world performance and uplink versus downlink always apply. The figures represent best averaged and rounded estimates of maximum uplink ERP/EIRP test results provided to the FCC OET in the authorization filings for the domestic variant Nexus devices and Sprint variant HTC devices. See below:
     

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

    Source: FCC
  18. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Thursday, March 5, 2015 - 12:15 PM MST
     
    I got my first real smartphone.
    Bought it at the five and dime.
    Browsed S4GRU 'til my fingers bled.
    Was the summer of 6&9.
     
    Spring has not quite yet sprung for a few more weeks. But with the annual Mobile World Congress just wrapping up today in Barcelona, new smartphones that likely will dominate the mobile landscape through most of the summer are starting to sprout. Germinating at the FCC OET (Office of Engineering and Technology) over the past few days have been authorization filings for the Sprint variants of the Samsung Galaxy S6, Samsung Galaxy S6 Edge, and HTC One M9. Get ready for the summer of 6&9.
     
    S4GRU started a tradition of FCC OET authorization articles right around this time in 2012 with the debut of Sprint's first LTE devices. So, to celebrate the third birthday in our long running series, let us take a look at the cellular RF capabilities of this latest threesome of Samsung Galaxy and HTC One handsets.
     
    To begin, all three devices follow what has been for the past 18 months the standard Sprint variant configuration: tri band LTE, non SVLTE, single RF path with e/CSFB. No surprises there. On top of Sprint tri band LTE, the three handsets also cover the CCA/RRPP LTE bands -- with one possible caveat for the One M9. More details on that later.
     
    As an aside, Qualcomm is changing up its baseband modem branding and numbering schemes. Previously, branding was Gobi and numbering was, to use one example, MDM9625 for standalone modem chipsets. Then, many Snapdragon processor chipsets also included the same modems on die -- a la the Snapdragon 800, aka MSM8974, which integrated the same stack as in the standalone MDM9625. Branding is now changing universally to Snapdragon and numbering, to use just one example again, will follow the X10 LTE pattern. That last example is the Snapdragon 810's brand new LTE category 9 modem, which has no standalone modem precursor. But other rebranded and renumbered examples with their standalone precursors include the Snapdragon X5 LTE (MDM9625), Snapdragon X7 LTE (MDM9635), and Snapdragon X12 LTE (MDM9645).
     
    That Qualcomm background is useful as we will start the rundown with the One M9, which incorporates the Snapdragon 810 with X10 LTE chipset. To cut straight to the chase, below are the tested ERP/EIRP figures:
    Band class 0: 20 dBm Band class 1: 25 dBm Band class 10: 20 dBm Band 2: 25 dBm Band 4: 23 dBm Band 12: 18 dBm Band 25: 25 dBm Band 26: 17 dBm Band 41: 23 dBm For reference, and this will pertain to the ERP/EIRP figures cited later for the Samsung devices, too, the above figures represent our best averaged and rounded estimates of max uplink ERP/EIRP -- with uniquely Sprint frequencies receiving heavier weighting in band class 10, band 25, and band 26. Of course, the usual disclaimers about lab testing versus real world performance apply.
     
    Now, to provide some analysis, RF output looks relatively healthy, somewhere in the better than average range. And it generally, albeit minimally trumps that of its HTC One M8 predecessor -- see our S4GRU article from last year.
     
    The aforementioned caveat about CCA/RRPP bands is that the FCC OET filing for the One M9 does not include separate testing of band 5. Now, that may not indicate omission of band 5 -- because band 26 is a superset of all band 5 frequencies. But we cannot guarantee that the One M9 will attach to band 5 roaming networks without MFBI for band 26.
     
    Two other omissions are worthy of note. First, the FCC OET documents offer no mention of band 41 carrier aggregation capabilities. This may or may not be cause for concern. Current carrier aggregation is downlink reception only, not uplink transmission. And FCC OET testing is just the opposite -- uplink transmission only, not downlink reception. As such, the testing is not required to include carrier aggregation. We do know that the Snapdragon 810 with X10 LTE supports up to 3x 20 MHz FDD/TDD carrier aggregation, so we expect that 2x or 3x band 41 carrier aggregation is on board. S4GRU will follow up if more info becomes available.
     
    Second, the One M9 was not tested, thus is not authorized for domestic GSM/W-CDMA bands. Rabid phone unlockers under the new Sprint domestic unlocking policy, consider yourselves forewarned.
     
    Finally, the One M9 docs suggest VoLTE support at launch. But Sprint has no established timeline for VoLTE, so take that with a grain of salt. It could be just a latent capability.
     
    Moving on to the galactic federation, Samsung has split its Galaxy S6 offerings in two this year, offering a separate Galaxy S6 Edge as a step up version. With one possible exception, both Galaxy S6 handsets have the same RF capabilities. However, their ERP/EIRP figures are not identical, so they are broken out separately below:
     
    Samsung Galaxy S6:
    Band class 0: 17 dBm Band class 1: 23 dBm Band class 10: 17 dBm Band 2: 22 dBm Band 4: 23 dBm Band 5: 16 dBm Band 12: 21-17 dBm (declining with increasing carrier bandwidth) Band 25: 22 dBm Band 26: 16 dBm Band 41: 16 dBm Samsung Galaxy S6 Edge:
    Band class 0: 18 dBm Band class 1: 22 dBm Band class 10: 18 dBm Band 2: 22 dBm Band 4: 24 dBm Band 5: 17 dBm Band 12: 17 dBm Band 25: 22 dBm Band 26: 17 dBm Band 41: 19-11 dBm (declining with decreasing center frequency) As for analysis, both Galaxy S6 variants are about average -- with the Galaxy S6 Edge holding generally a 1 dB "edge," pun intended. Neither, though, holds up to the tested RF output of the One M9. Some surmise that Samsung's much debated shift in handset materials this year from largely cheap feeling plastic to more premium metal and glass has had a detrimental effect on RF design and performance. We cannot jump to that conclusion, but the RF falloff does become even more apparent in comparison to last year's Samsung Galaxy S5 -- again, see our article.
     
    In particular, band 41 EIRP is disappointing. A higher frequency band should precipitate higher RF output. But that is not the case this year, as the band 41 uplink maximum for both Samsung handsets drops 4-7 dB below that of the One M9 and fully 6-9 dB below that of the Galaxy S5.
     
    Also, the band 41 extreme frequency differential in the Galaxy S6 Edge is disconcerting. It is up to 8 dB better in high BRS spectrum than in low EBS spectrum. Meanwhile, multiple band 41 center frequencies in BRS/EBS spectrum will vary from market to market, so performance will also vary. If using the Galaxy S6 Edge on band 41, you better hope for EARFCN 40978 or greater.
     
    Alright, that less than good news out of the way, let us move on to more positive things. The Samsung Galaxy S6 handsets are LTE category 6 -- with explicitly noted support for 2x band 41 carrier aggregation. More on that, too, later. They also have been tested and authorized for domestic GSM/W-CDMA bands, so unlocking in the future for use on other domestic operators may be possible. VoLTE, though, is noted as not supported out of the box. It is, however, on board other Galaxy S6 variants, thus could be added later with a Class II Permissive Change filing and potentially a software update.
     
    Now, back to LTE category 6. In addition to its material design change this year, Samsung has also broken lockstep with Qualcomm, choosing to forgo the 64 bit, octa core Snapdragon 810 processor in favor of its in house 64 bit, octa core Exynos 7420. S4GRU does not traffic in application processor chipset holy wars -- there are plenty of other sites for that. But this chipset change has other ramifications. Unlike the Snapdragon 810, the Exynos does not have a baseband modem on die. Thus, Samsung has had to include a separate modem chipset. And, unfortunately, the full identity of that modem remains a mystery. We know of another Samsung in house chipset -- the Exynos Modem 333 or SS333 -- that could provide the category 6 LTE connectivity, possibly even full 3GPP connectivity.
     
    However, for Sprint, that still leaves lingering 3GPP2 (CDMA2000). Is it provided by a second modem, meaning a third chipset? Could it be a reappearance of the notorious VIA Telecom CDMA2000 modem? S4GRU sincerely hopes not. Or maybe Qualcomm is still on board, not in the processor, but in its aforementioned Snapdragon X7 LTE (MDM9635) category 6 LTE standalone 3GPP/3GPP2 baseband, which supports the same 2x 20 MHz FDD/TDD carrier aggregation. Time will tell.
     
    Well, that is a wrap for this set. If you are young and restless with the Samsung Galaxy S6s and HTC One M9, will you wonder what went wrong? Or will the summer of 6&9 be the best days of your mobile life?
     
    Discuss in the comments.
     
     
    Sources: FCC, Bryan Adams
  19. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Monday, March 3, 2014 - 5:37 PM MST
     
    No one is publicly sure what the codenamed HTC M8 will finally be called. HTC One 2, HTC One More, or maybe pull an Apple move and just call it yet again the HTC One. Regardless, all of the big four domestic variants were added to the FCC OET (Office of Engineering and Technology) database today. The last to have its authorizations appear online this afternoon was none other than NM80P6B700 -- the tri band LTE variant undeniably headed to Sprint.
     
    As has been our trend over the past six months, we will still call this a teaser article -- albeit make it more extensive than usual. And we may not do a full RF breakdown in the future. Now that tri band LTE and 802.11ac, for example, are de facto standards among top of the line handsets, while SVDO and SVLTE have been laid to rest, there is less news to report on the RF side.
     
    But we do want to run a brief RF ERP/EIRP numbers comparison among the high end HTC handsets that have graced the Sprint lineup over the past two years because, well, HTC has developed a bit of a reputation among S4GRU members for losing its lead in the RF performance department. Despite its moniker, the HTC EVO LTE was downright poor on LTE, and the follow up Sprint variant HTC One and HTC One max were average at best.
     
    Numbers wise, the HTC M8 looks like a step in the right direction. Per the customary caveats, the available test bench measurements represent only maximum uplink ERP/EIRP, so they do not necessarily reflect the full two way RF performance equation. However, they can provide a decent advance peek inside at the RF proficiency of a handset.
     
    In that regard, the HTC M8 offers some improvements over its predecessors. See the table snapshot below (or link to it on Google Docs):
     

     
    https://docs.google.com/spreadsheet/ccc?key=0ArY31Mr219-ydHh0c2xsUWFmbE1udW5vSnlSMjA3TFE&usp=sharing
     
    More and more, OEMs are hiding behind the shroud of confidentiality and not allowing public inspection of the antenna diagrams in their FCC OET filings. HTC now appears to have jumped on that bandwagon. Fortunately, the Sprint variant HTC M8 docs do reveal some antenna gain figures, and those numbers are not always divulged, diagrams or not. Of note are unity 0 dBi or positive 1 dBi antenna gains for >1 GHz bands. Compare these to the -3.5 dBi antenna gain for PCS 1900 MHz in the HTC EVO LTE.
     
    Additionally, though this is not apparent in the table because it lists only maximum figures, the ranges of max and min ERP/EIRP within the various frequencies in each CDMA2000 band class and within the various carrier bandwidths in each LTE band are more tightly clustered, more consistent than usual. This, likewise, could indicate enhanced antenna engineering.
     
    And, finally, the single radio path handsets that have arrived in conjunction with Sprint tri band LTE so far have generally been better RF performers. Will the HTC M8 -- or whatever it gets called -- follow suit? Early returns indicate so, but once S4GRU membership gets its hands on a few samples, field testing in the coming weeks will tell the full story.
     
    Source: FCC
    Thread: http://s4gru.com/index.php?/topic/5008-htc-m8new-flagship/
  20. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Tuesday, September 3, 2013 - 11:35 AM MDT
     
    Welcome back from summer vacation. The S4GRU writing staff, too, has returned and is ready to catch up on some of the developments from over the last two or three months.
     
    In late July, Sprint released two tri band LTE mobile hotspots and one tri band LTE USB dongle. Meanwhile, Clearwire had lit up band 41 TD-LTE 2600 on numerous sites in several markets around the country. Around the same time, the LG G2 became the first Sprint tri band LTE handset to pass through FCC OET (Office of Engineering and Technology) authorization.
     
    As is our tradition by now, we add to S4GRU's stalwart series of articles on the FCC OET authorizations for the HTC EVO 4G LTE, Samsung Galaxy S3, Motorola Photon Q 4G, LG Optimus G, Samsung Galaxy Note 2, HTC One, and Samsung Galaxy S4 our look at the RF faculties of the LG G2:
    CDMA1X + EV-DO band classes 0, 1, 10 (i.e. CDMA1X + EV-DO 850/1900/800) LTE bands 25, 26, 41 (i.e. LTE 1900/800, TD-LTE 2600) band 25 LTE 3/5/10 MHz FDD carrier bandwidth band 26 LTE 1.4/3/5/10 MHz FDD carrier bandwidth band 41 TD-LTE 10/15/20 MHz TDD carrier bandwidth LTE UE category 4 W-CDMA bands 2, 5 (i.e. W-CDMA 1900/850) GSM 850/1900 802.11a/b/g/n/ac Wi-Fi 802.11n MCS index 7 (single spatial stream, 40 MHz carrier bandwidth, 400 ns guard interval) 802.11ac MCS index 9 (single spatial stream, 80 MHz carrier bandwidth, 400 ns guard interval) SVDO and SVLTE support absent RF ERP/EIRP maximum: 19.80 dBm (CDMA1X/EV-DO 850), 21.64 dBm (CDMA1X/EV-DO 1900), 23.09-27.08 dBm (LTE 1900), 17.77-21.29 dBm (TD-LTE 2600) CDMA1X/EV-DO Rx antenna diversity NFC antenna integrated into battery cover Antenna locations: (see FCC OET diagram below) Simultaneous transmission paths: (see FCC OET diagram below)

     
    The LG G2 is not only the first revealed Sprint tri band LTE handset but also the first Sprint category 4 UE of any kind because it is utilizing the Qualcomm Snapdragon 800 (MSM8974). The MSM8974 is a 28 nm process SoC that contains processor, cellular baseband, and WLAN/GNSS baseband all on one chipset -- à la the MSM8960 that dominated the first half of last year. The difference, of course, is that the MSM8974 has a quad core processor and a UE category 4 cellular baseband. The latter supports up to 150 Mbps on the downlink, 50 Mbps on the uplink -- though those speeds will not likely be seen on Sprint during the lifespan of this handset due to spectrum bandwidth constraints.
     
    Also, we cannot confirm at this point that the G2 is actually using the internal WLAN/GNSS baseband capabilities of the MSM8974 and not a separate chipset solution from Broadcom, as has been the trend with the HTC One and Samsung Galaxy S4. But having at least both processor and cellular baseband on the same chipset should be a step in the right direction.
     
    Regarding maximum ERP/EIRP, we are slightly modifying the way that we report those figures. Even within a given frequency band, max ERP/EIRP can vary according to frequency and modulation. So, if the FCC OET docs show greater than 1 dB of variance in a certain band and airlink, we now report that range instead of a single max figure.
     
    As we have stated in the past, FCC OET testing includes only transmitters, not receivers. Thus, we have to extrapolate overall RF prowess based on mobile uplink transmission capabilities, and that is an inexact science.
     
    In a nutshell, though, the CDMA2000 band class 0 and 1 power outputs appear to be a bit on the weak side, while the band 25 LTE power output looks good. The band 41 TD-LTE EIRP is lower than we would like to see -- especially considering BRS/EBS 2600 MHz propagation characteristics -- but TD-LTE 2600 will be used largely as an offload band for handsets, probably less so for hotspots.
     
    What is missing are band class 10 CDMA2000 and band 26 LTE ERP figures. The original FCC OET filing in late July included only conducted power figures for that band class and band. Conducted power is what is delivered to the antenna, not what is actually radiated from the antenna. And even though the G2 at the end of August has already had one Class II Permissive Change filing, we expect at least one more Class II filing with additional ERP figures before this Sprint variant hits the streets.
     
    Last year, the LG Optimus G had its initial, incomplete FCC OET filing in the summer, followed by a Class II change in the fall and a release in November. In our Optimus G article last summer, we wrote not to expect the street date right away, and we will offer the same caveat here. The rumored November release for the Sprint variant G2 should probably be the expectation.
     
    Source: FCC
  21. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, 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
  22. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, September 13, 2013 - 3:15 PM MDT
     
    The teaser articles continue. But this is a big one -- in a quite literal way.
     
    The presumed Sprint variant Samsung Galaxy Note 3 passed through the FCC OET (Office of Engineering and Technology) on Wednesday this week. We have an article already started on it, so look for that full length rundown soon.
     
    But since that SM-N900P variant hit the FCC OET, the cries about it being single band 25 LTE 1900 have been strong among the S4GRU faithful. Well, here is something potentially to make the disappointed forget those concerns.
     
    Just within the last hour or two this Friday afternoon, another Samsung handset has revealed itself at the FCC OET. But this is no Galaxy Note 3. It is even larger than that. The model number SPH-L600 and dimensions (see the diagram below) suggest that this is a Galaxy Mega 6.3 headed to Sprint. The size exceeds that of the Galaxy Note 3, and in an interesting twist, the FCC OET filing even refers to the device as a "phablet."
     
    The grand pronouncement, though, is that this Samsung "phablet" is indeed a tri band LTE device: band 25 LTE 1900, band 26 LTE 800, band 41 TD-LTE 2600 -- plus the usual Sprint CDMA2000 band classes.
     
     

     
    In conclusion, the "SPH" model number and the specs add up. This is a huge handset for Sprint, it is tri band LTE, and it may render the Galaxy Note 3 irrelevant.
     
    Enjoy! And know that there is more detailed RF info to come...
     
    Source: FCC
    Thread: http://s4gru.com/index.php?/topic/4368-samsung-galaxy-mega-tri-band-sph-l600/
  23. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Tuesday, September 9, 2014 - 12:21 PM MDT
     
    As many of you know, Sprint recently established a partnership with members of the Competitive Carriers Association (CCA) as sort of a quid pro quo. This partnership is called the Rural Roaming Preferred Program (RRPP), and S4GRU wrote about the nascent RRPP in a recent article on The Wall.
     
    In a nutshell, Sprint will gain pseudo native LTE coverage outside of its standard footprint, as RRPP members overlay Sprint's PCS 1900 MHz, SMR 800 MHz, and even BRS/EBS 2600 MHz spectrum on their existing networks. In turn, RRPP members will get access to Sprint's LTE footprint, and maybe even more importantly for many of these small scale operators, they will benefit from Sprint's and SoftBank's economy of scale in device procurement.
     
    Going forward, Sprint will create a device ecosystem that supports not only its native CDMA2000 band classes and LTE bands but also its RRPP partner LTE bands, namely band 2 LTE 1900, band 4 LTE 1700+2100, band 5 LTE 850, and band 12 LTE 700. The Nexus 5 almost pulled off that quadruple play last year, but that last LTE band has been a sticky wicket for CCA members, since AT&T was able to get its boutique band 17 LTE 700 pushed through the 3GPP. It left many CCA members that hold Lower 700 MHz A block licenses out in the cold, as they lacked access to some of the most popular devices created by the AT&T economy of scale.
     
    Today, that changes. Trumping a presumed iPhone reveal in the FCC OET (Office of Engineering and Technology) later this afternoon, Motorola unleashed the authorization documents this morning for the IHDT56QA3, the third variant of the 2014 Moto X to pass through the FCC OET. The big takeaway, as indicated in the title of this article, is that this Moto X with the expected model number XT1092 is the first Sprint/CCA/RRPP fully compliant LTE handset -- even if an iPhone variant possibly joins the group here in the next few hours.
     
    In conclusion for this short Teaser, the FCC OET docs can speak for themselves. This table tells the whole LTE story for Sprint and its RRPP partners.
     

     
    We wanted to bring you the scoop as soon as possible, but stay tuned. S4GRU may expand this article as more information is gleaned from the FCC OET docs or becomes available elsewhere.
     
    Source: FCC
  24. 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
  25. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Tuesday, September 10, 2013 - 1:10 PM MDT
     
    To cut right to the chase, Apple announced at its live event today two new iPhone models: high end iPhone 5S and mid range iPhone 5C. Both are coming to Sprint and both support Sprint LTE -- but only dual band Sprint LTE. The new crop of iPhone models for the next year will not be tri band LTE handsets on Sprint.
     
    The LTE bands supported by iPhone 5S (A1453) and iPhone 5C (A1456) are substantial and as follows: band 1, 2, 3, 4, 5, 8, 13, 17, 18, 19, 20, 25, 26. For Sprint users, that means dual band LTE 1900/800.
     
    While 13 total bands seems impressive, a few of those bands -- such as band 2/25 and band 5/26 -- are subset/superset bands. The big takeaway for Sprint users, though, is that band 41 is absent this year. So, TD-LTE 2600 will be coming soon to several tri band Android handsets but not to the dual band two new iPhone models. Band 38 TD-LTE 2600 is limited to the Asia/Oceania variants.
     
    Also worthy of note, Sprint and SoftBank share the same iPhone 5S and iPhone 5C variants this year. Whether that is merely coincidence is impossible to determine. But Sprint and SoftBank have talked about combined economy of scale as a benefit of their tie up.
     
    To conclude, the new iPhone FCC OET docs have not yet trickled out, but as they do, we will have more info to come. Stay tuned...
     
    Source: Apple
    Thread: http://s4gru.com/index.php?/topic/4442-the-iphone-5s-iphone-5c-not-tri-band-lte-was-next-iphone-to-be-announced-on-september-10/
×
×
  • Create New...