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
    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
  2. 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
  3. 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
  4. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, May 8, 2015 - 12:15 PM MDT
     
    Update: A week after the Sprint variant LG G4 original authorization documents were released at the FCC OET and S4GRU published this RF performance article, a Class II Permissive Change filing was added to the G4's docket. In writing the article last week, we did not detect anything amiss with the original filing, so this represents an optional change, which the filing discloses as hardware modification affecting the main antenna. Interestingly, none of the previous antenna gain figures have been altered, but the ERP/EIRP figures have increased or decreased. See the smoothed and averaged differences below:
    Band class 0: -1 dB Band class 10: -2 dB Band 4: -3 dB Band 5: -2 dB Band 12: -2 dB Band 26: -2 dB Band 41: +2 dB So, you win some, you lose some. Overall, the Sprint variant G4 has become weaker in tested RF performance. Those negative differences, however, are limited mostly to lower frequencies in the 700-1700 MHz range. The 1900 MHz range is unaffected, and the 2600 MHz range is increased. The other win is that a Class II filing before a device is released generally means that release is imminent. Look for the G4 on shelves and online soon.
     
    Yes, I know it is no longer May 4th. And we are not in a Samsung Galaxy far, far away. But this is episode IV in the LG G handset series, just four days removed from May 4th. That should be enough of the number four to satisfy anyone. Even if this isn't the Motorola Droid you're looking for, is the LG G4 a new hope for a flagship Sprint handset this spring?
     
    S4GRU staff has been watching the FCC OET (Office of Engineering and Technology) authorization database over the past week as different G4 variants were revealed. The VZW variant came earlier in the week, and the Sprint variant ZNFLS991 documents were uploaded yesterday. Of course, we are going to write an article about it, so let us get started.
     
    Right away, the G4 adheres to what has become the standard Sprint variant configuration: tri band LTE, non SVLTE, single RF path with e/CSFB. Additionally, it covers the CCA/RRPP LTE bands. And it was tested for domestic GSM/W-CDMA bands -- phone unlockers rejoice. Finally, it does officially support downlink carrier aggregation as its lone Release 10 feature. More on CA later.
     
    Next, it is fairly well known and somewhat controversial that the G4 opted not for the top of the line Qualcomm Snapdragon 810 but for the lesser Snapdragon 808, taking some performance hits in graphics and memory departments, for example. S4GRU does not involve itself in that debate -- that is not the place of this cellular RF focused article. But the chipset choice is relevant because both the Snapdragon 808 and Snapdragon 810 incorporate the same Category 9 X10 LTE baseband on die. So, rest assured, the choice of the Snapdragon 808 does not lessen any RF capabilities.
     
    On that topic, if you need a refresher on the new Qualcomm LTE baseband naming/numbering scheme, see this sidebar from our earlier article on the HTC One M9 and Samsung Galaxy S6:
     
     
    Back to discussion of CA support, we have stated previously that FCC OET authorization filings are not required to disclose downlink CA -- because that is only reception, not transmission. But the G4 filing does include an explicit attestation letter, stating its inclusion of downlink CA. What the G4 filing does not divulge is specifically 2x or 3x downlink CA support in band 41. For various reasons, S4GRU believes the former, that the G4 is capable of band 41 2x CA.
     
    First, the Snapdragon X10 LTE baseband natively supports up to 60 MHz of 3x downlink CA. However, that requires some help. An RF transceiver sits ahead of the baseband, and presently, the Qualcomm WTR3925 can handle 2x CA -- but 3x CA necessitates the inclusion of a second transceiver. See this excerpt from an AnandTech article on the new Snapdragon chipsets:
     
     
    Moreover, the other G4 variants that support CA are explicitly limited to 2x CA, suggesting that all variants are using the single WTR3925 transceiver. This is all educated conjecture, barring a teardown of the Sprint variant that probably will never happen. But if you are waiting on 3x CA, that likely will require a next generation Qualcomm transceiver to do 3x CA all in one.
     
    Finally, straight from the horse's mouth, Sprint CTO Stephen Bye stated the following in a recent FierceWireless article:
     
     
    Now, honestly, most read our FCC OET authorization articles for ERP/EIRP figures and analysis. So, without further ado, here are the numbers:
    Band class 0: 22 dBm Band class 1: 26 dBm Band class 10: 23 dBm Band 2: 25 dBm Band 4: 24 dBm Band 5: 22 dBm Band 12: 17 dBm Band 25: 25 dBm Band 26: 22 dBm Band 41: 23 dBm For reference, the above figures represent our best averaged and rounded estimates of max uplink ERP/EIRP -- with uniquely Sprint frequencies receiving heavier weighting, if possible, in band class 10, band 25, and band 26. Of course, the usual disclaimers about lab testing versus real world performance apply.
     
    As for analysis, max RF output looks quite healthy across the board, comparing very favorably with that of the One M9 and soundly thrashing that of the disappointing Galaxy S6. In particular, the power output for CDMA2000 band classes is a good 3 dB higher than most.
     
    Note, if you are using the smart cover for wireless charging, though, ERP/EIRP is affected roughly -1 dB across the board. I am not a fan of wireless charging because of the power inefficiency involved, but the RF loss from the smart cover on the G4 appears considerably less than what we have seen from some previous handsets.
     
    If there is any caveat about the G4's RF capabilities, that would be its antenna gain, broken down by frequency range as follows:
    700 MHz: -5.9 dBi 800 MHz: -7.1 dBi 1700 MHz: -5.2 dBi 1900 MHz: -3.5 dBi 2600 MHz: 1.7 dBi Except for 2600 MHz, all are negative, significantly negative. And for comparison, again except for 2600 MHz, the VZW variant antenna gain in all bands tracks about 3 dB higher. The head scratcher, however, is that the lab performance between the two variants is remarkably similar, despite the differences in antenna gain.
     
    We have seen something like this before -- an LG handset that showed strong lab power output yet weak real world performance. Remember the LG Viper? That is the challenge in interpreting lab results. Low output always indicates weak performance. However, high output can be a mixed bag. But LG has a pretty good Sprint track record since the Viper, as the LG Optimus G, LG G2, and LG G3 were all at least average to good in the real world. And the LG manufactured Nexus 5 was practically a Jedi knight for its RF performance at the time.
     
    In the end, only many trials on Dagobah will tell if the G4 lives up to its powerful promise. Use the 4th, LG, use the 4th.
     
    Source: FCC, AnandTech, FierceWireless
  5. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Wednesday, August 5, 2015 - 1:28 PM MDT
     
    Columbus. But not 1492. Just 8640. And 26640, too.
     
    This discovery did not require an Italian navigator sailing under the Spanish flag, nor the Niña, the Pinta, and the Santa Maria. Instead, the explorers were an intrepid S4GRU Columbus membership group (sorry, restricted to S4GRU sponsors), some handsets, some screenshots, and some speed tests.
     
    Those last two numbers 8640 and 26640 are the paired EARFCNs 8640/26640 of a band 25 additional carrier found this week in the Columbus, OH BTA. Seemingly, not such a big deal. S4GRU and its members have been finding band 25 additional carriers with different EARFCNs in multiple markets for months now. We even have two tracking threads for additional LTE carriers -- one for all three bands, one for band 25.
     
    However, this band 25 additional carrier discovery represents truly a New World for Sprint. It is 10 MHz FDD. Now, that alone is a big deal. But it is actually just the second finding of a 10 MHz FDD carrier that we have had in the past four days. The Champaign-Urbana, IL BTA came first. We hope to follow up with an article on that later.
     
    More importantly, though, the Columbus 10 MHz FDD carrier is a complete refarming of the PCS G block. The standard 5 MHz FDD carrier at EARFCNs 8665/26665 that is omnipresent across the Sprint LTE network is gone -- it is gone forever where this new carrier has appeared in the Columbus BTA.
     
    To dive right in, let us take a look at two screenshots from the Columbus area...
     

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

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

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

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

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

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

     
    A band 25 additional carrier already resides in that USCC PCS B block disaggregation -- but it is presently 5 MHz FDD. And an additional EV-DO carrier has been added at the bottom of the block. Still, there may be enough spectrum left to expand that 5 MHz FDD to 10 MHz FDD very soon.
     
    The Windy City, are you ready for it? We shall see if S4GRU's short term prediction proves as accurate as its spectrum analysis did three years ago.
     
    To be continued...
     
    Sources: FCC, S4GRU members and staff
  6. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Thursday, September 3, 2015 - 3:28 AM MDT
     
    Ladies and gentlemen, C Spire has left the building. In Memphis. Or so it seems.
     
    Based on an FCC spectrum lease filing that came down the pike earlier this week, Cellular South dba C Spire has applied to lease all of its spectrum in Memphis to Sprint. S4GRU has not been able to confirm yet, but this almost certainly appears to signal a C Spire exit from Memphis -- its largest urban market into which it expanded just a few years ago.
     
    Disclaimer: the FCC ULS (Universal Licensing System) -- which is the parent database for all spectrum licenses and applications and is what I access directly to do spectrum research -- is down for a server migration over the Labor Day holiday weekend, not back online until sometime next week. In fact, the FCC ULS went offline right in the midst of my research a night ago. Fortunately, I was able to gather the relevant info on the Memphis spectrum to be leased to Sprint. However, the entirety of the transaction also involves Sprint leasing spectrum elsewhere back to C Spire -- more on that later. As more information becomes available, we will publish an update or a follow up, if warranted.
     
    In Memphis, the spectrum to be leased to Sprint is the PCS 1900 MHz C2 block 15 MHz (7.5 MHz FDD) and Lower 700 MHz A block 12 MHz (6 MHz FDD) licenses. From a CDMA2000 standpoint, the PCS would be band class 1 spectrum; the Lower 700 MHz is irrelevant for CDMA2000. For LTE, the PCS would be band 2 or band 25 spectrum, which Sprint would utilize as band 25, and the Lower 700 MHz would be band 12, which Sprint has not held in any other market. That last piece is a key point -- more on that later, too.
     
    At this point, S4GRU cannot definitively comment on C Spire's motivation to leave its largest market -- if that indeed is what is happening. Albeit, similar regional operator USCC faced struggles with expansion into Chicago and St. Louis, eventually closing down those markets and selling off spectrum to Sprint. Likely, that is what is happening in Memphis.
     
    Along possibly related lines, USCC faced spectrum constraints with launching LTE in Chicago and St. Louis, potentially rendering them dead end markets in the current LTE focused environment. From Spectrum Gateway's interactive map, we can see that UHF channel 51 presently conflicts with Lower 700 MHz A block deployment in Memphis. With its Lower 700 MHz A block license encumbered and decent but not large PCS spectrum holdings in Memphis, C Spire likely faced a difficult road to LTE there.
     
    S4GRU may try to seek official comment from C Spire on this matter. Presumably, though, C Spire will address the Memphis issue in the coming days, providing some clarity on the matter. If C Spire is truly exiting the Memphis market, it will have to notify its existing subscribers.
     
    All of that ambiguity aside, Sprint's motivation is clearly understandable. After the USCC transaction in Chicago and the Revol transaction in Cleveland and Indianapolis, Memphis is one of the last few top markets where Sprint holds only 20 MHz total of PCS A-F block spectrum -- even more dire, that 20 MHz in Memphis is broken up into two non contiguous 10 MHz (5 MHz FDD) blocks. Though a minimal amount of info has changed in the intervening years or decades since I did the pro bono work, you can view some of my Sprint spectrum documentation, including Memphis, in this spreadsheet, this map, and this spreadsheet.
     
    What that means presently for Sprint in Memphis is additional guard bands are required because of the interrupted spectrum blocks and no chance of LTE carrier bandwidth greater than 5 MHz FDD, nor any band 25 second carrier until after significant CDMA2000 thinning or shutdown. But this spectrum from C Spire changes everything.
     
    At the very least, Sprint will have increased its PCS A-F block Memphis spectrum holdings from just two non contiguous 10 MHz (5 MHz FDD) blocks to those two blocks plus another non contiguous 15 MHz (7.5 MHz FDD) block. A band 25 second carrier in Memphis is coming down the river.
     
    However, what I think -- and what other S4GRU staff members have independently concurred -- is that Sprint will swap this C Spire spectrum with AT&T.
     
    First, the spectrum lease application with C Spire is for a long term, de facto transfer lease. We could be wrong, but this lease smacks of a prelude to a full sale of C Spire spectrum licenses in Memphis to Sprint. In that case, Sprint would have options to rearrange its position in the PCS band plan. Primarily, both Sprint and AT&T would be advantaged to swap their PCS C1 and PCS C2 blocks for greater contiguity for both parties. Continue reading.
     
    Just as S4GRU documented in the Columbus, OH market a month ago, the PCS G block LTE 5 MHz FDD carrier probably would be redeployed as a 10 MHz FDD carrier bridged across portions of the PCS C block and PCS G block. That still would leave room in the potentially acquired spectrum for up to two additional CDMA2000 carriers, which would replace two of the three CDMA2000 carriers lost in the PCS D block or PCS B5 block, one of which would be refarmed for an LTE 5 MHz FDD carrier to ensure continued LTE access to any early band 25 devices that do not support LTE in anything but 5 MHz FDD -- the same process that we saw in Columbus.
     
    For illustration of the present, post transaction, and possible PCS spectrum future in Memphis, see this S4GRU graphic:
     

     
    Other possibilities exist for Sprint and AT&T spectrum "horse trading" in Memphis -- such as Sprint getting the AT&T PCS F block in exchange for effectively returning to AT&T the PCS B5 disaggregation that Sprint acquired from AT&T predecessor AT&TWS in a spectrum transaction over a decade ago. But those other spectrum transaction possibilities would be more disruptive to current service, so I and other S4GRU staff do not think those band plan rearrangements likely in the near future.
     
    To start to wrap matters up for now -- but probably to be continued later -- that Memphis BEA Lower 700 MHz A block is the proverbial elephant in the room. As noted earlier, that is band 12 spectrum. And Sprint now has plenty of band 12 compatible devices previously released, currently available, or upcoming. Indeed, band 12 is part of the CCA/RRPP device procurement plan.
     
    However, we do not expect Sprint to deploy band 12 in Memphis. The Lower 700 MHz A block is not immediately compatible with Sprint's Network Vision infrastructure, and it is currently encumbered by adjacent UHF broadcasting. If, as S4GRU expects, a full spectrum transfer ultimately results from this Memphis spectrum lease, then look for Sprint to flip the Lower 700 MHz A block license to T-Mobile, which has shown its motivation and money to get UHF channel 51 broadcasters relocated -- or paid to accept some adjacent channel interference.
     
    As an exchange for that low band spectrum -- which T-Mobile has now started to value so greatly -- Sprint could gain some of the excess T-Mobile-Metro PCS spectrum that S4GRU pointed out almost three years ago, shoring up Sprint's PCS A-F block 20 MHz holdings in the likes of important markets San Francisco, Atlanta, or Miami.
     
    To return to and conclude with C Spire, our article starter, we cannot precisely document what SMR 800 MHz, PCS 1900 MHz, and/or BRS/EBS 2600 MHz spectrum C Spire will lease from Sprint. Because the FCC ULS frustratingly is out of commission for several more days. Cursory examination when the leases were still accessible online, though, did not indicate any major markets. Rather, this could be tied in with a CCA/RRPP agreement to expand Sprint coverage -- since C Spire infrastructure and handsets typically do not support band 26 nor band 41.
     
    So, the real prize in this transaction is spectrum in Memphis. My apologies to Marc Cohn for ham handedly paraphrasing his 1990s ballad, but it is also all too fitting…in those blue suede shoes...
     
    Leasing in Memphis -- leasing in Memphis
    Sprint's getting PCS on and off of Beale
    Leasing in Memphis -- leasing in Memphis
    How does that really make you feel?
     
    https://www.youtube.com/watch?v=KK5YGWS5H84
     
    Sources: FCC, Marc Cohn
  7. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Monday, September 28, 2015 - 10:40 AM MDT
     
    Update: Now that Google has released the full tech specs for the Nexus 6P, we can write a few addenda. While the FCC OET authorization filings disclosed support for several GSM, W-CDMA, and LTE international bands -- something that they are not required to do -- they curiously omitted W-CDMA band 8, which is the GSM 900 MHz band. Add that one to the W-CDMA list. Additionally, we can confirm that the Nexus 6P will require a 4FF nano SIM. For Sprint activation, will it be a USIM or a CSIM? That remains to be seen. Stay tuned.
     
    Late last Friday afternoon, the LG manufactured Google Nexus 5X made its debut in the FCC OET (Office of Engineering and Technology) authorization database. S4GRU staffers quickly got down to work and broke the story with RF analysis that very evening.
     
    Following hot on the heels of its smaller sibling, the Huawei manufactured Google Nexus 6P made a bright and early morning FCC OET appearance today. S4GRU was on the case right away. So, let us dive right in to the RF nitty gritty.
     
    The Nexus 6P band support currently covers all major domestic operators -- VZW, AT&T, T-Mobile, Sprint, USCC, C Spire, etc. It even future proofs itself for AT&T usage to an extent by including nascent band 30 (WCS 2300 MHz), a band not present in the Nexus 5X.
     
    Moreover, it includes some notable international bands, which the authorization filing discloses. (Most FCC OET filings do not disclose international bands, as they are not required to be tested for US authorization.) For example, W-CDMA band 1 (IMT 1900+2100 MHz) is the primary W-CDMA band worldwide, and LTE band 3 (DCS 1800 MHz) is an emerging LTE band in many international markets.
     
    For your perusal, the many bands/classes...
    GSM 850/900/1800/1900 W-CDMA band 1/2/4/5 CDMA2000 band class 0/1/10 LTE band 2/3/4/5/7/12/13/17/25/26/29(Rx only)/30/41 From a physical standpoint, the Nexus 6P incorporates a dual antenna system. All LTE handsets that support 2x2 downlink MIMO must have at least two Rx antennas. But the Nexus 6P also utilizes a dynamic antenna capability on uplink Tx, switching between the two antennas at will, depending upon handset orientation and signal conditions.
     
    Interestingly, though, the dynamic antenna Tx capability is limited to low band spectrum. Only bands/classes below 1 GHz are supported. Lastly, in another twist, the Nexus 6P authorization filings did include an antenna diagram -- something that has become increasingly rare due to cited confidentiality concerns. On the other hand, the antenna gain figures were not apparent anywhere in the filing. For the diagram, see below:
     

     
    In keeping with most of this year's handsets based on the Snapdragon 808 or 810 -- both of which incorporate on die the Snapdragon X10 LTE modem -- the Nexus 6P supports 2x carrier aggregation on the downlink in both intra band and inter band configurations. In the case of inter band 2x CA, either band can be operated as the PCC (primary) or SCC (secondary).
     
    2x CA downlink bands:
    2-2 4-4 41-41 2-4 2-5 2-12 2-13 2-17 2-29 4-5 4-12 4-13 4-17 4-29 To wrap things up, let us examine the LTE band RF output. The usual provisos about lab testing versus real world performance and uplink versus downlink apply. The figures represent my best averaged and rounded estimates of maximum uplink ERP/EIRP test results provided to the FCC OET in the authorization filings for the device.
     
    Overall, the ERP/EIRP figures are fairly consistent within each band and across all bands. In terms of tested performance relative to other handsets, the measurements are roughly average. The P in Nexus 6P is not for RF "powerhouse," but it certainly could stand for "proficient." Compared to the Nexus 5X, the Nexus 6P has a 2-3 dB tested advantage in high band, while the Nexus 5X has a 2-3 dB lead across most of the mid and low band.
     
    ERP/EIRP:
    Band 2: 21-22 dBm Band 4: 21-23 dBm Band 5: 18-19 dBm Band 7: 21-23 dBm Band 12: 17-18 dBm Band 13: 17-18 dBm Band 17: 17-18 dBm Band 25: 21-22 dBm Band 26: 18-19 dBm Band 30: 20-21 dBm Band 41: 21-22 dBm Source: FCC
  8. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Thursday, November 12, 2015 - 3:07 PM MST
     
    Yes, you read that correctly. Thanks to the mid range Qualcomm Snapdragon 617 (MSM8952), the HTC One A9 is the first Sprint handset to include a modem that supports uplink 2x CA (carrier aggregation). That comes on die via the X8 LTE modem, which is a Category 7 LTE baseband, capable of aggregating up to 40 MHz FDD/TDD 2x CA on both the uplink and downlink. Now, before anyone gets too excited, Sprint has no imminent plans to enable uplink 2x CA at the network level. So, the uplink 2x CA support is mostly a proof of concept novelty.
     
    If you have been reading The Wall at S4GRU for a while, you probably know where this is headed. It is another in our classic series of FCC OET (Office of Engineering and Technology) RF authorization analysis articles. We do not dwell on processor benchmarks, screen qualities, etc. If you want that info, read reviews or visit the HTC tech specs site. Instead, we cut right to the heart of what a cellphone is -- a cellular RF device -- and rundown its lab tested cellular RF performance.
     
    The One A9 filed its FCC OET authorizations over a month ago, but with Sprint selling the handset as we speak and HTC shipping the unlocked Sprint variant next week, we should take a look. Let us start with the band/class support:
    CDMA2000 Band Class 0/1/10 GSM 850/900/1800/1900 W-CDMA Band 1/2/4/5 LTE Band 2/4/5/12/25/26/41 The Sprint and CCA/RRPP band support is expected at this point. But all of the GSM/W-CDMA band support info comes directly from the HTC tech specs. I state that explicitly because there is no testing of domestic GSM/W-CDMA in the FCC OET documents. Barring a Class II Permissive Change filing with the FCC, the GSM/W-CDMA support purely is for international roaming. While the Sprint variant One A9 can be unlocked or even purchased unlocked, it is not authorized for use on AT&T or T-Mobile -- unless you can live with no GSM/W-CDMA, only band 2/4/5/12 LTE.
     
    For an unlocked One A9, HTC proactively has addressed the to/from Sprint provider switch issue by including that in its one time courtesy UH OH Protection program:
     
    In other words, want to switch from Sprint to AT&T, T-Mobile, or VZW with your unlocked One A9? HTC will swap out for the other domestic variant. Want to switch from AT&T, T-Mobile, or VZW to Sprint with your unlocked One A9? HTC will swap out for the Sprint variant. While on the subject of the AT&T, T-Mobile, and VZW variant, it is 3GPP only, thus VoLTE only for voice on VZW. HTC even acknowledges that fact:
     
    The other domestic variant has some further relevance as we delve into the FCC authorized lab tested ERP/EIRP performance of the Sprint variant.
     
    The FCC OET documents, per usual, do not disclose an antenna diagram. But they do note that the One A9 uses a dual antenna system -- antenna 0 and antenna 1, presumably top and bottom or vice versa. The handset will switch between the antennas at will based upon varying signal metrics. Much like Apple with the iPhone, HTC has implemented this dual antenna setup since the debut of the One M7 in 2013. In this case, however, the dual antennas are still single radio path, so SVLTE is not supported.
     
    Now, for the main attraction, let us look at the Sprint variant One A9 radiated power figures. I may sound like a broken record, but the usual clauses about lab testing versus real world performance and uplink versus downlink always apply. The figures represent my best averaged and rounded estimates of maximum uplink ERP/EIRP test results provided to the FCC OET in the authorization filings for the device. See below:
    Band Class 0: 17 dBm Band Class 1: 22 dBm Band Class 10: 18 dBm Band 2: 16-19 dBm Band 4: 13-16 dBm Band 5: 14-16 dBm Band 12: 14 dBm Band 25: 17-19 dBm Band 26: 16-17 dBm Band 41: 21-22 dBm The CDMA2000 performance is good, about average. And the band 41 output is along the same lines. That is about the best S4GRU can say regarding the tested results of the One A9. It does not quite hit the lows of the VZW variant Samsung Galaxy Note 3 -- the most anemic RF test results that S4GRU has ever seen in any notable handset -- but the One A9 is not far off. The band 4 output that maxes out as low as 13 dBm, for example, is very weak. It is mid band spectrum that needs greater EIRP. The positive is that band 4 roaming never may be a factor with this handset. And band 2/25 is a bit better, though still at least 4-5 dB below the desired level.
     
    Now, back to the other domestic variant headed to AT&T, T-Mobile, and VZW. The picture does not get much rosier. Comparing the 3GPP bands in common, the other domestic variant is superior by 2-7 dB in band 2, 6-9 dB in band 4, 2-4 dB in band 5, and 2 dB in band 12. Wow, those are big differences nearly across the board. The Sprint variant does get one minor victory -- it is 1-2 dB better in band 41 than the other domestic variant is in band 7, as both band 41 and band 7 operate in the same BRS/EBS 2600 MHz spectrum.
     
    What happened, HTC? The Sprint variant seems to have gotten shortchanged. Was that a compromise to optimize band 41 by 1-2 dB? We can hope for better returns in real world performance. But early returns from lab tested performance are not good.
     
    Sources: FCC, HTC, Qualcomm
  9. 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
  10. 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
  11. 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
  12. 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
  13. WiWavelength
    by Andrew J. Shepherd and Robert Herron
    Sprint 4G Rollout Updates
    Friday, April 6, 2012 - 2:20 PM MDT
     
    Today, S4GRU brings you the wireless equivalent of the much sought after paparazzi photo of the newborn celebrity baby. In an S4GRU exclusive, here is the first published look at a live Sprint LTE signal.
     
    Sprint recently lit up a cluster of Network Vision sites in Olathe, KS within Sprint's Kansas market. With trusty spectrum analyzer in tow, S4GRU staff ventured to Olathe this morning and captured a snapshot of Sprint's PCS G block 1990-1995 MHz allocation, clearly showing the up and running LTE OFDMA downlink coming from Sprint's completed Network Vision site (KC60XC009) in Black Bob Park. See below our PCS G block downlink frequency domain analysis:
     

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

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

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

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

     
    For CDMA1X 800 network acquisition, therefore, Sprint band class 10 capable PRLs will have to include ACQ indices containing at least channels 476 and 526.
     
    Moreover, as S4GRU has unearthed, band class 10 PRLs will also have to include separate SID entries for SMR 800 MHz. For example, in the Dallas-Fort Worth market, Sprint has long used SID 04120, but CDMA1X 800 will fall under new SID 22407. In the Atlanta market, Sprint operates under SID 04274, while CDMA1X 800 will take on SID 22437. NIDs, though, appear to be consistent between PCS 1900 MHz and SMR 800 MHz. Expect Sprint to establish a second SID for each one of its markets, hence just under 50 new SMR 800 MHz SIDs in total.
     
    We surmise that Sprint will use the distinct new SIDs to control access and network loading on the lone CDMA1X 800 carrier channel in each market. By Sprint placing SMR 800 MHz SIDs at lower priority in PRLs, the vast majority of Sprint devices will remain on CDMA1X 1900 in almost all native coverage settings. Devices will seek out CDMA1X 800 only when CDMA1X 1900 is unusable or unavailable. Savvy PRL builders, however, could certainly take advantage of this situation by editing PRLs to invert priority and favor CDMA1X 800 instead, thereby directing devices to remain on SMR 800 MHz wherever possible.
     
    S4GRU will continue to dig up CDMA1X 800 SIDs for additional markets. As we do, we will post updates. So, stay tuned.
     
    Update: We have learned new SMR 800 MHz SIDs for several West Coast markets: San Francisco-Oakland-San Jose, Portland, and potentially Seattle or Spokane, too. In the Bay Area, Sprint's CDMA1X 1900 network uses SID 04183, while the upcoming CDMA1X 800 overlay will use SID 22431. Similarly, in Portland, Sprint will continue to utilize SID 04174 for PCS 1900 MHz and will add SID 22428 for SMR 800 MHz. Sprint in Seattle and Spokane uses SID 04186 and SID 04188, respectively. S4GRU has discovered SMR 800 MHz SID 22408 linked to rural parts of the Seattle and Spokane MTAs, but we are currently uncertain if this SID will apply to one or both actual metro areas.
     
    Update 2: Special thanks go to S4GRU reader and sponsor autoprime for reminding us of the IFAST national SID list web page, which just so happens to contain all of the SMR 800 MHz SIDs that we have announced, as well as ostensibly all of the other SMR 800 MHz SIDs for Sprint's remaining MTA based markets. The 224xx series SIDs were actually assigned to Sprint for its PCS G block nationwide collection of licenses, spectrum that was assigned to Nextel as compensation for SMR 800 MHz bandwidth it lost during the 800 MHz public safety rebanding effort. Sprint originally intended to deploy band class 14 CDMA1X/EV-DO in that PCS G block 10 MHz spectrum but now will use it exclusively for band class 25 LTE (5 MHz x 5 MHz), the initial LTE carrier that Sprint will launch in its Network Vision initiative. Since band class 14 CDMA1X/EV-DO is now off the table, Sprint appears to have carried over the 224xx series SIDs to its SMR 800 MHz band class 10 CDMA1X deployment. Keep in mind, however, that these remaining SIDs have yet to be verified, so there may be some differences between the list and actual use. S4GRU will endeavor to confirm additional SIDs as we analyze further information from our internal Sprint sources. In the meantime, we have condensed all assigned 224xx SIDs to this Google Docs spreadsheet.
     
    Sources: Sprint, SouthernLINC, FCC, 3GPP, author's graphics, autoprime, IFAST
  16. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Friday, March 9, 2012 - 1:15 PM MST
     
    Sprint may soon be gaining some clarity regarding its Network Vision plans to deploy CDMA1X Advanced to replace Nextel iDEN in its rebanded SMR 800 MHz spectrum. The FCC today announced a proposed rulemaking that would explicitly allow SMR 800 MHz licensees (e.g. Sprint, SouthernLINC, and a few others) to utilize greater than 25 kHz channel spacing.
     
    Currently, Part 90 SMR 800 MHz rules and regulations could be interpreted to prohibit channel spacing exceeding 25 kHz, effectively disallowing any airlink other than iDEN, which is designed to operate in 25 kHz channelization. Meanwhile, Sprint has petitioned that Part 90 does not automatically bar larger channel bandwidths in contiguous channel blocks and that it has enacted improved filtering techniques to satisfy out of band emissions concerns due to wideband operations.
     
    To reconcile the current rules and regulations with Sprint's contentions, the proposed rulemaking would amend Part 90 as follows:
     
     
    More simply put, Sprint would be able to use its lower band SMR 800 MHz spectrum below 821 MHz x 866 MHz right away to deploy CDMA1X and/or LTE. Then, after all public safety relocation in a region has been completed, Sprint could utilize its upper band SMR 800 MHz spectrum 821-824 MHz x 866-869 MHz for further wideband operations.
     
    The proposed rulemaking aligns with and helps to explain Sprint Network Vision 3G plans that S4GRU has obtained. Those plans indicate that Sprint intends to deploy at least one CDMA1X Advanced band class 10 carrier channel centered at channel 476 (817.9 MHz x 862.9 MHz) and/or channel 526 (819.15 MHz x 864.15 MHz). This would place one or both CDMA1X carrier(s) within the lower band 817-820 MHz x 862-865 MHz spectrum and leave >1 MHz guard bands between it and 821-824 MHz x 866-869 MHz spectrum, in which public safety reconfiguration is still ongoing in some regions.
     
    To illustrate how Sprint proposes to roll out CDMA1X 800 at the lower end of its SMR 800 MHz spectrum allotment, see our band plan and channel assignment graphic:
     

     
    Sources: FCC, Sprint, author's graphic
  17. WiWavelength
    by Andrew J. Shepherd
    Sprint 4G Rollout Updates
    Wednesday, February 22, 2012 - 4:20 PM MST
     
    While the name of the bill might seem to suggest otherwise, the Middle Class Tax Relief and Job Creation Act of 2012 currently working its way through Congress contains several provisions that have direct bearing on the wireless industry.
     
    One, it assigns directly to public safety the Upper 700 MHz D block 10 MHz (5 MHz x 5 MHz) nationwide license—which had been intended for a public-private national network partnership but failed to reach its reserve price at FCC auction in 2008—and provides financing for the construction of a national public safety network.
     
    Two, it authorizes the FCC to conduct incentive auctions in which UHF TV broadcasters can voluntarily give up their broadcast channels in exchange for compensation so that their spectrum may be repurposed for wireless broadband.
     
    Three, it directs the FCC to auction within the next three years additional spectrum between 1600 MHz and 2200 MHz, including the creation of yet another PCS 1900 MHz block, the ostensibly named PCS "H" 10 MHz (5 MHz x 5 MHz) block. See the relevant portion of the draft bill:
     

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

     
     
    Prior to auction, the PCS "H" block would most probably be divided into geographic licenses, and any current or future wireless carrier could bid on one or all licenses. So, Sprint would not be guaranteed to win any PCS "H" spectrum. But Sprint would gain the greatest utility from PCS "H" spectrum because it could be most easily combined with Sprint's existing PCS G spectrum for 10 MHz x 10 MHz LTE. Thus, consider this a brief, early look at how Sprint could likely augment its spectrum portfolio in the coming years.
     
    Sources: US House of Representatives, FCC, author's notes; special thanks to TMF Associates, Public Knowledge
×
×
  • Create New...