Jump to content

The Wall

  • entries
    394
  • comments
    5,964
  • views
    4,736,323

Contributors to this blog

About this blog

Entries in this blog

lilotimz

blog-0821325001504661683.png

Tim Yu
Sprint 4G Rollout Updates
September 5, 2017 - 6:45 PM PDT

It is that time of the year for flagship phablets and LG has returned to us with their brand new V30 smartphone. Unlike the LG G6, LG was not conservative with the specifications on this one.

Many other tech sites and forums have already broken down the V30 but here at S4GRU we are more interested in network technologies and the V30 is definitely no slouch in this regard.

Supported Technologies
GSM 850 / 1900
WCDMA Band: 2 / 4 / 5
LTE Band: 2 / 4 / 5 / 12 / 13 / 17 / 25 / 26 / 41

4x4 MIMO on Band 25 and Band 41 up to 10 streams
256 / 64 QAM DL-UL

HPUE 

2xCA B25
2xCA B41
3xCA B41

4xCA B41

That is right.

The LG V30 is the first device confirmed to support 4 carrier aggregation on Band 41.

No other device out there, including the ever more popular Galaxy S8 or Note 8, are confirmed to at least technologically support 4 carrier aggregation for Band 41 (though maybe a re-certification & software update can fix that). In addition, the LG V30 is also a "Gigabit Class" device that supports 4x4 MIMO over Band 41 for up to 10 total MIMO streams which the Galaxy S8 and Note 8 does not support (the GS8 and Note 8 are not "Gigabit Class" devices on Sprint).

Furthermore, note the inclusion of LTE Band 13. One may think this mean LTE roaming on Verizon may be in the cards, but recently Sprint consummated a partnership with Open Mobile based in Puerto Rico who holds Band 13 750 MHz spectrum. As the Puerto Rico market lacks SMR 800 spectrum needed for CDMA 1x 800 and LTE 800 Band 26, it seems likely that it may be a boutique Sprint market that will utilize 10x10 Band 13 750 MHz for low band coverage. An interesting development.

So network wise, the V30 sure seems like one heck of a device that supports just about every technology Sprint is poised to utilize right now in select markets and most of the network in the near future. A potentially splendid device for the Sprint network enthusiast.

FCC ID: LS998

gallery_1_2_11866.png
lilotimz

blog-0996538001494996205.png

Tim Yu

Sprint 4G Rollout Updates

May 19, 2017 - 8:30 AM PDT

 

The Sprint Magic Box was announced on Sprint's quarterly earning call earlier this month, and was heralded as the first truly all wireless small cell in the industry. So what is this mystical beast that is purported to increase coverage by up to 30,000 square feet, amplifies data speeds, and "boosts" your data signal?

This is the 1st Generation Sprint Magic Box

 

MHDh4HB.jpg

In more technical terms, the Magic Box is an Airspan product under their Airunity line. The black colored model that exists in the wild, and which I procured contains the Airspan Airunity 540 small cell eNB. Whereas the white colored Magic Box advertised by Sprint is a newer model that contains the Airspan Airunity 545 small cell eNB. The primarily difference is that the unreleased white Magic Box is able to broadcast at twice the transmit power compared to the black model which results in substantially increased coverage area in addition to the LTE UE Relay Module having HPUE capability.

These are all wireless small cells as there is no requirement of a wired backhaul solution like traditional Femto cells like the pending Sprint Airave 3 LTE, Commscope S1000, or the T-mobile LTE Cellspot.

Instead, the Magic Box (MB) utilizes a technology called LTE UE Relay that is integrated into the overall package. The Magic Box contains an Airunity LTE B41 2500 MHz small cell and a LTE UE Relay device called the ninja module whose only job is to establish a data link to a macro eNB LTE 1900 or 2500 MHz signal and then feed a data connection to the Airunity small cell.

For more on LTE UE Relay: see here

Once the Relay link is connected and data flows to the Airunity eNB, a new LTE 2500 MHz signal is then created and broadcasted from the unit. This signal is unique to the Magic Box and is available to use by any compatible Sprint device that can access the LTE Plus (2500 MHz LTE B41) network.

Unlike a repeater setup, the Magic Box does not simply take an existing signal and amplify it and all the accompanying noise and interference. This is a brand new and very clean LTE signal being broadcasted.

The following screenshot from Network Signal Guru app displays this clearly.

M3YlIBo.png

The Magic Box in my location broadcasts a brand new LTE carrier with frequency located on EARFCN 40270 (2558 MHz) while the macro donor eNB signal of 40978 (2628 MHz) is used as backhaul (LTE Band 25 1900 MHz can also be used).

[As of July 2017, the Magic Box had its LTE carrier center frequency switched to 2518.4 MHz or EARFCN 39874. Signal Check Pro screenshot]

This means, instead of a weak edge of cell LTE signal with the accompanying band switching that substantially impact device stand by times and I may lose deep inside the building, a Magic Box allows a Sprint device to connect to a strong and clean LTE 2500 MHz signal which blankets the formerly weak LTE coverage area.

As a side effect, LTE speeds may also be dramatically increased due to the better signal level and quality being broadcasted by the MB whose LTE Relay Module can connect to what may have been previously an unusable 2500 MHz network. Especially when placed by a window as recommended.

UmyyXXC.jpg

8UqQMmb.jpg

kkR2Zan.jpg

jBmCSe1.png

Album of Screenshots

Personal Experience

In my more than one month of observations using the Magic Box, I was able to connect to a LTE 2500 MHz signal from inside a suburban family residential building where such a signal was previously unusable. Furthermore, not only did the Magic Box boost the data signal from weak edge of cell service with consistent frequency swapping that had previously killed our devices battery life, but it also increased the LTE data speeds substantially to the tune of 200-300% over what we were previously getting over LTE 800 and 1900 MHz.

Whereas previously the house was a weak coverage area where LTE 800 MHz was predominant with even parts dropping to EVDO 3G, the new LTE signal broadcasted by the MB covers the entire house and then some through multiple interior walls and even an exterior brick wall before handing over back to the macro network.

So what's my view on the Magic Box?

It can't come soon™ enough for more people to use and enjoy.

lilotimz
blog-0349928001481867054.png

Tim Yu

Sprint 4G Rollout Updates

December 15, 2016 - 9:40 PM PDT

 

It's been but a blink of an eye since Sprint CTO Gunther's last Reddit Ask Me Anything (AMA) but he's back!

 

Right now, December 16, 2016 at 11 AM to 12 PM PDT, he is doing his second AMA on R/Sprint.

 

 

Be sure to check it out and ask him many questions that have kept you from blissful nights of rest.

S4GRU
blog-0801155001473622237.png

by Robert Herron

Sprint 4G Rollout Updates

September 11, 2016 - 12:30 PM PDT

 

We have many good friends over at the Sprint Reddit page, and many of our members spend a lot of time there. They are excited at their recent score to host an AMA with Sprint's new COO of Technology, Günther Ottendorfer.

 

S4GRU wants to help spread the news. The AMA is scheduled for tomorrow, September 12th from 1:30 - 2:30pm Central Daylight Time. This should be an exciting exchange for S4GRU members, as Mr. Ottendorfer is responsibile for overseeing Sprint’s network, technology and IT organizations, including related strategy, network operations and performance, as well as partnerships with network, technology and IT vendors.

 

As stated in the Sprint Subreddit page, "Günther looks forward to answering your questions on Sprint's pioneering efforts, network performance, LTE Plus network, network technology and roadmap, LTE Advanced, 5G, Network Function Virtualization (NFV), spectrum, and its Densification & Optimization strategy."

 

Be sure to check it out!

WiWavelength
blog-0133502001471589857.png

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:

 

14y33ol.png

 

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

lilotimz
blog-0877342001459551618.png

by Tim Yu

Sprint 4G Rollout Updates

Friday, April 8, 2016 - 3:40 PM MDT

 

Over the past week, S4GRU members in multiple Sprint markets have discovered new EARFCNs and corresponding GCI endings that identify new Band 41 LTE carriers.

 

The EARFCN is the center frequency of an LTE carrier that, along with the carrier bandwidth, identifies the carrier placement and occupied spectrum.

 

As Sprint is doing intraband contiguous/adjacent carrier aggregation -- 20 MHz TDD Band 41 carriers are lined up right next to one another with no gaps -- Band 41 EARFCNs are highly predictable in a given market by knowing the location of at least one carrier.

 

Say the ever popular EARFCN 40978 is the first carrier.

 

You add 198 (19.8 MHz) to it to get EARFCN 41176, which is the second Band 41 carrier.

Thus, it stands to reason if you add 198 to that EARFCN, you will get the third Band 41 carrier so 41176 + 198 = 41374, the EARFCN for the third Band 41 carrier.

 

Or, in some other markets, 41078 is the first Band 41 carrier. In this case, it goes like this: 41078 + 198 = 41276 + 198 = 41474

 

Alternatively, say a market has EARFCNs 40056 and 40254. Adding 198 would bring us to EARFCN 40452, but that is not possible due to the BRS/EBS 2500-2600 MHz band plan -- there are spectrum gaps around 2570 MHz and 2610 MHz that Sprint cannot utilize. See the band plan:

 

fehtgj.jpg

 

Thus, in the case of EARFCNs 40056 and 40254, not addition, but use subtraction: 40056 - 198 = 39858, which would be the third Band 41 carrier.

 

The GCI is the unique cell sector identifier of a LTE carrier.

 

Generally speaking, Sprint's GCI patterns are standardized market by market and network wide, making for an easy method to identify each LTE carrier within a given band. In the case of Band 41, GCIs ending in 00/01/02 (Samsung) or x1/x2/x3 (ALU/NSN) indicate a connection to the original and first Band 41 carrier. GCIs ending in 03/04/05 (STA) or x9/xA/xB (ALU/NSN) denote the second Band 41 carrier.

 

It stands to reason that -- if this second carrier pattern were to continue to the third Band 41 carrier in Samsung markets -- we would expect to see GCIs possibly ending in 06/07/08. Long story short, this theory is supported by evidence. See below SignalCheck Pro logs and numerous in app screenshots:

 

This log is from my Nexus 5x. I traveled for a hour around Sacramento, searching for the third Band 41 carrier. Note the GCI endings for the Sprint Band 41 entries:

 

EpIGr1g.png

 

The following is from site member bmoses in Des Moines. Note the 07 GCI ending and EARFCN:

 

sBZcsFh.png?1

tBJFIeG.png?1

 

Below is from a S4GRU member in the Colorado market:

 

1apchr0.png?1

 

One more from the Cincinnati, Ohio Market:

 

HUWJ4jE.jpg?1

 

The following is from yours truly in Sacramento:

 

1rRX7pa.png?1

btjSquQ.png?1

L0osc9p.png?1

 

And these below are from Fremont, CA, near San Jose:

 

cKMSsgW.png?1

hJFhKHf.png?1

 

 

See those EARFCNs and GCI endings? Look at the calculations from the top of this PSA. Everything is as we would have predicted for a third carrier.

 

With the end of the WiMAX injunction and the decomissioning of the last active Clearwire WiMAX markets that held up huge swaths of leased EBS and licensed BRS spectrum, Sprint finally has the capability to show off its deep spectrum pockets in numerous markets. This has been long awaited and should definitely give a huge boost to Sprint data speeds in numerous markets where spectrum for additional Band 41 carriers now is available. Of course, there still is the issue of actually connecting to and using this third Band 41 carrier.

 

From firsthand reports and personal use, this third Band 41 carrier is not currently carrier aggregation enabled. Thus, 2x/3x CA devices may not connect to it to use data right now. By default, these devices will have CA enabled, causing them to utilize only the first and second carriers that they can aggregate. For the time being, in order to reliably connect to this third carrier, a non CA triband device or a 2x/3x CA setting disabled triband device may be required. Regardless, this appears to be just a minor issue from the initial rollouts that should be resolved soon.

 

Source: S4GRU member reports

lilotimz
blog-0993309001458100728.jpg

by Tim Yu

Sprint 4G Rollout Updates

Wednesday, March 16, 2016 - 9:13 PM MDT

 

Authors Edit (8/25/16): According to a report, the LG G5 (and HTC 9) is indeed capable of 3xCA specifically for Sprint due to the intraband contiguous setup Sprint utilizes.

 

The spotlight may have been largely on the Samsung Galaxy for the past few weeks, but from behind the red moon, a new contender has revealed itself.

 

To keep it short, as per typical of a S4GRU teaser article, the model LS992 Sprint variant LG G5 had its FCC OET (Office of Engineering and Technology) authorization filings uploaded earlier this week. This is the 2016 flagship from LG for Sprint that will be available to subscribers soon. In keeping with S4GRU interests, we will take a look at the cellular technology side of the phone.

 

Supported Technologies

 

LTE Band: 2 / 4 / 5 / 7 / 12 / 25 / 26 / 41

CDMA Band Class: 0 / 1 / 10

GSM: 850 / 1900

WCDMA Band: 2 / 4 / 5

 

Pretty typical for a Sprint device of this time. It supports the standard Sprint LTE setup of Bands 25/26/41 and CCA/RRPP Bands 2/4/5/12. The FCC filings did not disclose international band support.

 

What many are interested in though, especially after the Samsung Galaxy S7 S4GRU article, is carrier aggregation combinations. Is the G5 a 3x CA device for Sprint? Well, the following excerpt from the FCC OET filing tells the story.

 

Az4oYQ9.png

 

The LG G5 LS992 is not 3x CA B41 capable -- unlike the Sprint variants of the Samsung Galaxy S7 and S7 Edge.

 

The G5 supports 2x CA intraband contiguous Band 41 and 2x CA intraband non contiguous Band 25. This is somewhat surprising, as both the G5 and the Galaxy S7 have the same Qualcomm Snapdragon 820 SoC, which has the Snapdragon X12 LTE baseband and 3x CA capability on die. Most likely, though, the RF transceiver is limited to 2x CA and/or the modem configuration is different.

 

Barring a Class II Permissive Change filing or a refresh model for the G5, it appears the Galaxy S7 variants still hold the crown for the first and only 3x CA B41 capable devices on the Sprint network.

 

But the G5 does hold one advantage over the Galaxy S7 variants for Sprint.

 

UsYt4ns.png

 

Note the S4GRU highlighted portion of the FCC OET filing.

 

Yes.

 

This is the first VoLTE certified device for Sprint. VoLTE will not work right out of the box, however. It is a latent capability until the Sprint network activates VoLTE. Consider this is a hint, though, that VoLTE may become a user option this year.

 

To begin the wrap up, the FCC OET filings do grace us with an antenna diagram -- something that is increasingly hidden behind a shroud of confidentiality.

 

DeIjsC7.png

 

There you have it: an initial look at the cellular tech side of the soon to be released Sprint variant LG G5.

 

Source: FCC ZNFLS992

lilotimz
blog-0408834001456596760.jpg

by Tim Yu

Sprint 4G Rollout Updates

Friday, March 4, 2016 - 8:25 AM MST

 

A little over two weeks ago, S4GRU published an article detailing a multi-market PCS 1900 MHz swap between Sprint and AT&T that increased spectrum contiguity for both operators in several markets. In that article, we mentioned how that spectrum swap might be the first of many, as there are numerous other markets in which Sprint and other licensees could mutually benefit by realigning disparate spectrum holdings into larger contiguous stretches for more efficient LTE spectrum utilization.

 

And late last week, that expectation came to the fore. It was discovered that AT&T was not the only dance partner. Rather, T-Mobile and VZW also entered the fray, as Sprint and both operators had contemporaneously filed PCS spectrum assignment applications with the FCC.

 

 

Results of the Latest Spectrum Swap

 

CeAKff7.png

1CE9SCq.png

 

 

As seen in the embedded screenshot, Sprint primarily is targeting additional spectrum in the PCS C block. Detailed in our last article, the PCS C block is adjacent to the PCS G block in which Sprint's existing 5 MHz FDD Band 25 LTE carrier is deployed. These swaps pave the way in a greater number of markets for expansion from that 5 MHz FDD carrier to a 10-15-20 MHz FDD carrier and subsequent higher maximum speeds in Band 25.

 

In total, about 50 million POPs so far will be affected by the spectrum transactions in these pending agreements among Sprint and AT&T, T-Mobile, and VZW. Furthermore, this may not be where the story ends. Once the FCC approves these applications, other PCS spectrum realignment among the big four operators may follow. Sprint also may pursue spectrum deals with smaller operators.

 

Stay tuned. S4GRU will have the scoop.

 

Source: FCC (VZW), FCC (T-Mobile), S4GRU (AT&T), S4GRU Spreadsheet

lilotimz
blog-0438205001455333904.jpg

by Tim Yu and Andrew J. Shepherd

Sprint 4G Rollout Updates

Thursday, February 18, 2016 - 6:25 AM MST

 

Call it a comeback. The band, the PCS band is getting back together. Pun intended. You will understand soon.

 

After a two year absence, the popular one, two, three part "What's the frequency, Kenneth?" article series is back for an encore. For full comprehension, refer back to those articles -- and others linked throughout this article. We will lead you in the direction of learning. No worries.

 

But now with a lead writer duo and a change in artistic direction, the topic of this article has shifted from engineering screens to band 25 expanded bandwidth primary carriers. The frequency focus, though, remains the same.

 

Perhaps also long overdue, Sprint finally has entered the spectrum alignment game of musical chairs that VZW, AT&T, and T-Mobile have been playing for a while in the AWS-1 and PCS bands. In this case, Sprint and AT&T are the dance partners. More on that after some PCS band background.

 

The PCS 1900 MHz spectrum alphabet is not quite what might be expected to the uninitiated. Sequentially, the band runs A, D, B, E, F, C, G. Without delving too much into the 25 year old history and politics of the band, that alphabet is a product of block sizes -- PCS A/B/C blocks are 30 MHz (15 MHz FDD), PCS D/E/F blocks are 10 MHz (5 MHz FDD) -- and spectrum caps at the time of FCC auctions in the 1990s that allowed licensees to obtain up to 45 MHz of total spectrum in urban markets, 55 MHz of total spectrum in rural markets. The spectrum cap, by the way, is long gone, replaced with a spectrum screen by a free market frenzy FCC administration over a decade ago.

 

For the time being, set aside the PCS G block, which is 10 MHz (5 MHz FDD). It was created much later, never auctioned. Rather, it was compensatory to Nextel for spectrum losses incurred in rebanding Public Safety SMR 800 MHz. Sprint now holds all PCS G block licenses nationwide.

 

So, back to the 1995-2003 era, a Cellular 850 MHz incumbent with a Cellular A/B block 25 MHz (12.5 MHz FDD) license in Chicago, for example, could not acquire also a PCS A/B/C block license -- that would push it over the 45 MHz urban market total spectrum cap. But that incumbent could acquire also a PCS D/E/F block license and stay under the cap.

 

Along the same lines, a new entrant into a market could acquire one PCS A/B/C block license and one PCS D/E/F block license for 40 MHz of total spectrum that could be contiguous within the convoluted A, D, B, E, F, C, G alphabet. That possibility, though, did not come to pass much at FCC auction 20 years ago. Spectrum contiguity was not all that important for GSM, IS-136 TDMA, and cdmaOne/CDMA2000, not even so much for W-CDMA. But with LTE, circumstances have changed.

 

That is a lot of abstract information. To put a face to the name, see a visual representation of the entire PCS band plan, followed by three exploded views of just the adjacent PCS C and G blocks:

 

2w5otfm.png

 

The uplink runs 1850-1915 MHz, the downlink 1930-1995 MHz, separated by an 80 MHz FDD offset. In the figures below the full PCS band plan, see the three exploded views of the PCS C and G blocks -- soon to be the focus of this "What's the frequency, Kenneth?" article.

 

The first of the three exploded views above shows the intact PCS C 30 MHz (15 MHz FDD) block -- this is relatively rare among licenses. Long story somewhat short, most PCS C block licenses had to be auctioned by the FCC multiple times, as many original Designated Entity entrepreneur/minority class winners found that they ultimately could not afford their licenses and construct networks. A quote from a previous S4GRU article:

 

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!

 

So, for reauction, most PCS C block licenses were disaggregated into smaller, easier to afford blocks. Note the PCS C1/C2 15 MHz (7.5 MHz FDD) blocks and PCS C3/C4/C5 10 MHz (5 MHz FDD) blocks in the second and third exploded views of the PCS C and G blocks.

 

That whole PCS C block medley will come into play up next. Just be sure to note in the band plan diagrams the spectrum contiguity of the PCS C + PCS G, PCS C1 + PCS G, or PCS C5 + PCS G block combinations.

 

A few weeks back, S4GRU received whispered word and saw PRL change indications that Sprint internally was discussing and prepping for spectrum swaps, whereby Sprint would trade some less strategic PCS holdings in return for PCS C block spectrum that is contiguous with its PCS G block. This type of deal would grant Sprint contiguous PCS holdings to expand LTE from a 5 MHz FDD carrier to a 10 MHz FDD carrier -- or even beyond to a 15-20 MHz FDD carrier in the future when CDMA2000 is significantly pruned or decommissioned.

 

For a visual depiction of one previous example of LTE in the PCS G block expanded into the contiguous PCS C block, thus going from 5 MHz FDD to 10 MHz FDD, see a graphic of what already has happened with earlier, unrelated spectrum transactions in Columbus, OH:

 

11wei6f.png

 

Compare to the exploded views earlier in this article of the PCS C and G blocks. And read our Columbus 10 MHz FDD discovery article for further background.

 

Then, for those aforementioned spectrum rearrangement rumors to come to fruition, we did not have to wait long at all. In what may be the first of many such spectrum deals, Sprint and AT&T filed with the FCC last week applications to swap PCS spectrum in several Basic Trading Area (BTA) markets:

 

By this and other contemporaneously filed Form 603 assignment applications, affiliates of AT&T Inc. (“AT&T”) and affiliates of Sprint Corporation (“Sprint”) (collectively, “Parties” or “Applicants”) seek the Commission’s consent for simultaneous assignments of certain PCS licenses. The assignments are license exchanges or swaps that will enable more efficient operations by creating larger blocks of contiguous spectrum.

 

 

g9Eid3c.png

 

The spectrum being assigned in this transaction will occur as exchanges of spectrum within the same BTA. The AT&T Licensees and Sprint Licensees will assign PCS spectrum to each other in intra-market exchanges, which will allow these Parties to enjoy the efficiency benefits associated with larger blocks of contiguous spectrum. Operating on contiguous blocks of spectrum allows the carriers to use the guard band in the adjacent spectrum blocks, providing greater capacity.

 

In summary, both Sprint and AT&T make out pretty well in this deal. Both parties will be able to improve their respective PCS spectrum contiguity. It is a quid pro quo.

 

All spectrum Sprint acquires will be PCS C block, while all spectrum AT&T acquires in exchange will be PCS A, B, D, or F block. The important takeaways are that Sprint will be able to expand LTE from the PCS G block into the PCS C block for a 10-15 MHz FDD carrier -- but that Sprint will have to eliminate or relocate CDMA2000 operations in the aforementioned blocks shipped off to AT&T.

 

For Sprint, all of the listed markets then will have 20 MHz (10 MHz FDD) of contiguous PCS spectrum, quite a few 30 MHz (15 MHz FDD) or even 40 MHz (20 MHz FDD) of contiguous PCS spectrum. Sprint will be able to expand LTE carrier bandwidth -- instead of adding a 5 MHz FDD band 25 second carrier -- as well as reduce CDMA2000 carrier guard band spectrum usage to a minimum.

 

The FCC approval of these applications is in zero doubt. It will be a rubber stamp. All transfers are relatively even spectrum swaps and in the public interest. But carrier reconfiguration will not happen right away. Sprint and AT&T have set up spectrum leases for each other in the interim. For Sprint, it will have to pare down and/or relocate CDMA2000 carriers to the acquired PCS C block spectrum. That is the reason behind the PRL updates, which will aid CDMA2000 acquisition once any carriers change frequencies.

 

S4GRU loves to encourage engineering screen watching -- just as we have done in the previous "What's the frequency, Kenneth?" articles. The more you know. See the three articles linked at the beginning of this article.

 

Now, for those in markets listed in this transaction, watch for LTE EARFCNs to switch from 8665/26665 to 8640/26640. The latter is a clear sign of 10 MHz FDD. S4GRU tracks these in its EARFCN thread, which we update periodically. Additionally, original CDMA carrier channel assignments will vary considerably, but watch for any carriers in band class 1 to shift to the 900-1200 range.

 

Full disclosure, not all counties in the listed BTAs will be affected the same -- because of existing spectrum partitions and disaggregations. Those in outlying areas may not benefit, but all titular BTA cities will gain 20-40 MHz (10-20 MHz FDD) of contiguous PCS C block + PCS G block spectrum and should deploy at least 10 MHz FDD band 25 in the coming months.

 

With that said, Sprint finally gets back into the game of horse trading spectrum with a competitor -- instead of sitting on the sidelines watching the others do these deals to their own benefit all the time. T-Mobile defines its band 4 "wideband" LTE as 15-20 MHz FDD. Sprint already has plenty of band 41 at 20 MHz TDD, more and more everyday with the WiMAX shutdown. But soon, Sprint also may have "wideband" LTE in band 25. We shall see. Expect to hear it here first.

 

S4GRU had the heads up on previous 10 MHz FDD possibilities already four years ago -- exactly four years to the date of the Sprint-AT&T spectrum transfer applications at the FCC last week. Coincidence?

 

For a more detailed look at the pluses and minuses of the spectrum swaps in the noted markets, see our S4GRU spreadsheet.

 

Source: FCC

lilotimz
blog-0758976001454559983.jpeg

by Josh McDaniel, Tim Yu, and Andrew J. Shepherd

Sprint 4G Rollout Updates

Wednesday, February 3, 2016 - 11:50 PM MST

 

Update: Further inspection of the FCC OET authorization filings has shown that while Samsung will produce only one "US" hardware variant each for the Galaxy S7 and Galaxy S7 Edge, it still will delineate operator specific "V," "A," "T," "P," and "R4" variants via firmware.

 

That firmware on the Sprint "P" variant, for example, will enable CCA/RRPP compliant bands 2/4/5/12/25/26/41 but disable VZW band 13, AT&T bands 29/30, and VoLTE. Similar segmentation applies to the other domestic variants, such as the AT&T "A" variant and T-Mobile "T" variant, both of which disable CDMA2000 and Sprint bands 25/26/41.

 

Thus, the single SKU aspect for the "US" hardware variants of the Galaxy S7 and Galaxy S7 Edge will be limited to their respective FCC IDs. At the retail and end user levels, separate SKUs and model numbers still will exist for the operator specific airlink/band firmware packages.

 

S4GRU hopes, however, that Samsung will use this consolidated hardware platform now as means also to sell unlocked BYOD versions of both handsets that will have full airlink/band firmware across all domestic operators.

 

Per Samsung Galaxy astronomy, the "V" suffix has been for VZW, the "A" suffix for AT&T, the "T" suffix for T-Mobile, the "P" suffix for Sprint, and the "R4" suffix for regional operators.

 

But what does the "US" suffix mean for the Samsung Galaxy S7 and S7 Edge?

 

Both handsets A3LSMG930US and A3LSMG935US bearing the "US" suffix in their model numbers were intentionally/unintentionally outed today in the FCC OET (Office of Engineering and Technology) database -- weeks in advance of their supposed official reveals at Mobile World Congress in Barcelona later this month.

 

Okay, the seventh generation of Samsung Galaxy handsets is a big deal. That said, what is so special about these two device authorizations?

 

Well, these two authorization filings with the FCC cover the entire gamut of supported LTE bands for every single US operator -- and include downlink three carrier aggregation support. Even before Apple, Samsung appears on the verge of single SKU handsets for the US.

 

VZW band 13. Sure. AT&T bands 29 and 30. Right on. T-Mobile band 12. Absolutely. Sprint bands 25, 26, and 41. Positively. Carrier aggregation. Yup.

 

Furthermore, as both Samsung handsets support CDMA2000, that is strong indication Samsung has reversed course from the the sixth generation of Samsung Galaxy handsets and included Qualcomm baseband modems in all domestic handsets. Almost assuredly, the chip of choice is the Snapdragon X12 LTE modem. That detail, though, is not yet available. On a similar count, tested RF ERP/EIRP figures are beyond the purview of this teaser. However, S4GRU may follow up later on all of the above.

 

In the meantime, here are the nitty gritty Galaxy S7 domestic airlink specs. The FCC filings did not disclose -- nor are they required to disclose -- international airlink support.

 

Samsung Galaxy S7

GSM / GPRS / EDGE: 850 / 1900

W-CDMA Band: 2 / 4 / 5

CDMA Band Class: 0 / 1 / 10

LTE Band: 2 / 4 / 5 / 12 / 13 / 25 / 26 / 29 (downlink only) / 30 / 41

 

LTE Carrier Aggregation:

 

2xCA

2+4 / 2+5/ 2+12 / 2+13 / 2+29 / 2+30

4+2 / 4+4 / 4+5 / 4+12 / 4+13 / 4+29 / 4+30

5+2 / 5+4 / 5+30 /

12+2 / 12+4 / 12+30

13+2 / 13+4

25+25

30+2 / 30+4 / 30+5 / 30+12 / 30+29

41+41

 

3xCA

2+4+12 / 2+4+13 / 2+5+30 / 2+12+30 / 2+29+30

4+2+12 / 4+2+13 / 4+4+12 / 4+5+13 / 4+5+12 / 4+5+30 / 4+12+30 / 4+29+30

5+2+30

12+4+2 / 13+2+4

30+2 +5 / 30+2+12 / 30+2+29 / 30+4+5 / 30+4+12 / 30+4+29

41+41+41

 

Samsung Galaxy S7 Edge

GSM / GPRS / EDGE: 850 / 1900

W-CDMA Band: 2 / 4 / 5

CDMA Band Class: 0 / 1 / 10

LTE Band: 2 / 4 / 5 / 12 / 13 / 25 / 26 / 29 (downlink only) / 30 / 41

 

LTE Carrier Aggregation:

 

2xCA

2+4 / 2+5 / 2+12 / 2+ 13 / 2+29 / 2+30

4+2 / 4+4 / 4+5 / 4+12 / 4+13 / 4+29 / 4+30

5+2 / 5+4 / 5+30 /

12+2 / 12+4 / 12+30

13+2 / 13+4

25+25

30+2 / 30+4 / 30+5 / 30+ 12 / 30+29

41+41

 

3xCA

2+4+12 / 2+4+13 / 2+5+30 / 2+12+30 / 2+29+30

4+2+12/ 4+2+13 / 4+4+12 / 4+5+13/ 4+5+12 / 4+5+30 / 4+12+30 / 4+29+30

5+2+30

12+4+2 / 13+2+4

30+2 +5 / 30+2+12 / 30+2+29 / 30+4+5 / 30+4+12 / 30+4+29

41+41+41

 

Note in bold text the Sprint relevant 2x CA combinations each for band 25 and band 41, then 3x CA combinations for band 41.

 

One SKU, one "US" device variant for all in the US, just like or better than iPhone and Nexus? By all appearances, yes. And while S4GRU is a Sprint centric blog and web site, this Samsung development has ramifications for millions of VZW, AT&T, T-Mobile, USCC, et al., users, too.

 

You heard it here first -- at S4GRU.

 

Sources: FCC

lilotimz
blog-0931258001453710328.jpg

by Tim Yu

Sprint 4G Rollout Updates

Monday, January 25, 2016 - 8:30 AM MST

 

For the past year, Sprint has commented a lot about its coming "Next Generation Network" deployment that aims to improve greatly Sprint's network capacity and coverage. Much of that speculation has been over how Sprint intends to feed backhaul to the "tens of thousands" of small cells it plans to deploy -- given Sprint's past history on getting backhaul delivered to its own macro cell sites as part of Network Vision.

 

Last summer, Sprint began talking up its "treasure trove" of 2.5 GHz spectrum as wireless backhaul for its small cells. Many speculated on exactly how this would be done -- with some online netizens theorizing Sprint actually would use part of its 2.5 GHz spectrum in a setup like microwave backhaul.

 

So, how exactly is Sprint going to use its 2.5 GHz spectrum as backhaul? The answer is a simple yet not often spoken about LTE Advanced technology:

 

LTE UE Relay

 

Over the past half a year, S4GRU staff repeatedly were told by Sprint employees that 2.5 GHz was going to be used as wireless backhaul. But there was not a lot of explanation on the technical side on how Sprint would accomplish that. That is until we discovered exactly what it was on a document sent to us almost a year ago that described several then ongoing projects being tested internally by Sprint.

 

LTE UE Relay is a fairly recent technology introduced in 3GPP Release 10. Courtesy of a Nokia Siemens Networks white paper on the topic of LTE Relay, the following is a well made depiction of a network utilizing relay nodes in action.

 

 

 

 

 

jsb0LeN.png

 

So, how does LTE UE Relay work?

 

A way to think of a Relay Node or LTE UE Relay (i.e. a small cell using 2.5 GHz as backhaul) is as a cell repeater. Yet, there is a significant difference in how a relay node and a repeater operate. Whereas a repeater increases coverage simply by amplifying a specific frequency range -- including all accompanying noise and interference -- a relay node demodulates and remodulates the signal, then transmits its own signal.

 

To put it in simple terms, one can think of a relay node being something akin to a Wi-Fi hotspot utilizing the LTE network for its data connection-- except in this case, the relay node is not transmitting a Wi-Fi signal but an LTE signal.

 

Thus, wherever there is even a speck of Band 41 coverage available, Sprint can plop down a relay node and use the existing LTE signal as backhaul for a small cell unit to increase local area coverage and capacity. This is because the small cell unit transmits a crisp, clean, new LTE signal in the area it is designed to cover, and UEs in that area would connect to this stronger signal.

 

As per the above image, an LTE Relay setup is quick to deploy and provides both an immediate impact on the local network and increased coverage/capacity for all compatible UEs in its coverage area -- without the need to wait for traditional backhaul, which could takes many weeks or months and be dependent on variables outside of Sprint's control.

 

But what about downsides of using LTE UE Relay as a backhaul setup?

 

For one, the speed of the LTE signal that is transmitted by the relay nodes is only as fast as that of the donor site -- be it a relay node (relay nodes can be serially chained), a fiber or microwave backhaul fed small cell, or a macro cell. If there is heavy congestion on the donor site sector, then the relay will also be just as "fast" as the connections that other UEs on the donor sector get. So, if the LTE carriers on the donor site is congested and running say 2-3 Mbps, connections to the relay node would go as fast as that.

 

Another potential issue is that a relay node may expand coverage into a hugely populated area with high load demands and by itself congest the LTE carrier that is providing the backhaul connection to the site. Even though the LTE carrier from the donor site could be running well at 20-30 Mbps speeds originally, the extra loading from the relay node could be just enough to congest that entire sector. In such a case, using a relay may be problematic, and it might be better instead to utilize more traditional backhaul like fiber, Ethernet, or microwave.

 

So, what is the point of writing all that?

 

Recently, an attentive S4GRU member discovered a post on LinkedIn, and an attached image caught the attention of S4GRU staff.

 

 

 

 

 

oIvo7TG.jpg

Image Credit: Omar Masry

 

It is not that it is a small cell setup that caught our eye but that subsequent comments noted there were no fiber connections at all, it utilizes a Nokia Flexi Zone pico cell, and it resides in the Boston, MA region.

 

Among the major operators in the US, there are only two users of Nokia Networks equipment: Sprint and T-Mobile.

 

T-Mobile only recently has commenced talk about deploying small cells of such type. To deploy a small cell without traditional fiber backhaul while utilzing a relay antenna and not even talk about it would be a departure for T-Mobile, which is known for issuing many press releases on new LTE Advanced technologies being implemented on its network. Furthermore, the Northeast is an Ericsson vendor region for T-Mobile. Nokia has no business doing anything there, leaving the other potential user as Sprint.

 

There was some speculation on why Nokia would be deploying their LTE Band 41 small cell equipment in an Alcatel-Lucent vendor region -- considering Alcatel-Lucent and its partner AirSpan have their own Band 41 equipment designs. But Sprint has said that the deployment would be unconventional and utilize non traditional methods of deployment, so this must have been part of that strategy. Nokia Networks also is in the process of acquiring Alcatel-Lucent. That may be a factor but is a topic for another day.

 

[Edit: Nokia has completed their purchase of Alcatel-Lucent so mystery solved.]

 

What was discovered is that Mobilitie has been applying for permits to deploy wooden poles in Salem, MA and presumably other cities as part of the Next Generation Network small cell densification project. The ever watchful eyes of an S4GRU Ohio based sponsor group member base quickly went to work and discovered an application by Mobilitie that gives a full rundown of what exactly the company seeks to install.

3NXmye0.png

 

Note the permit application engineering details and the pictures from the LinkedIn post.

 

See the similarities?

 

In addition to the near exact matching of details from the proposed setup in the filing and the pictures in the LinkedIn post, the application by Mobilitie, which is widely rumored to be Sprint's primary small cell deployment partner, also provided a site cascade ID: BS90XS933.

 

As per S4GRU sponsor maps detailing nearly all of Sprint's macro sites across the nation, here are a few examples of Sprint macro cell cascade IDs in the Boston market: BS03XC063, BS23XC461, BS60XC325.

 

Gee whiz! I wonder for whom Mobilitie could be deploying these wooden poles and smell cell setups.

 

Here is the LinkedIn image labeled according to details found in the application by Mobilitie.

 

Uh22VNG.jpg

 

As with everything Sprint does, this relay technology is not one magical fix it all for Sprint's network. Sprint has much to do to continue to improve its network and brand image.

 

LTE UE Relay is a very new technology not without its cons. Yet, it is an interesting direction Sprint is going with regards to backhaul to the projected tens of thousands of small cells deployed as part of the Next Generation Network.

 

Of course, what is more important than the theoretical talk is the discovery above of practical setup and engineering documentation. There is solid proof now that Sprint has started at least one portion of the long awaited and much talked about Next Generation Network deployment.

 

So, keep an eye out for such local permit applications by Mobilitie and potentially other unnamed partners, and observe your surrounding environments. One or more such small cell setups just may pop up near you without warning soon...

 

Sources for tech talk: 1, 2, 3

S4GRU
blog-0565429001450667895.png

by Robert Herron

Sprint 4G Rollout Updates

Sunday, December 27, 2015 - 8:30 PM MST (edited)

 

Happy New Year!

 

Some of you are aware that S4GRU maintains a gift account/scholarship account. When a member cannot afford to renew or upgrade, we draw from this account to help others in need. It seems like this year we have had more people down on their luck than in past years, and our scholarship account has been fully depleted. We use this to fund not only people down on their luck, but also the many budding teenage wireless enthusiasts around our site and those who borrow a few bucks to upgrade but then pay it back.

 

If you are able to contribute to help others this time of year to maintain their S4GRU accounts, please make acontribution to the S4GRU PayPal account. Please reference in the notes section GIFT ACCOUNT. Once your donation is logged, you will receive a message that your donation has been added to the scholarship account. And when your donation is used for a worthy member in the future, you will receive a message about the details for whom and how it was used.

 

Hopefully, past donaters to the Gift/Scholarship Account will sound off in our forums with their testimonials of how well it has worked for them to help fellow S4GRU'ers!

 

One of the great things about gift donations, is that both the giver and the recipient get credit for the donation for future Premier and Honored Premier upgrades. It's a gift that keeps on giving! And several of our members who have received gifts in the past have turned around and become very generous givers when their finances have turned around. I am always amazed at how generous our members can be.

 

And truth be told, S4GRU benefits from this as well. Not only is it the leanest time of year for our members, it's the leanest time of year for S4GRU as well. Promotions are the only things that really keep the donations coming in the Fall and Winter So help support your fellow S4GRU members down on their luck and S4GRU too. Be sure to list GIFT ACCOUNT in the notes of your PayPal donation or send a message to S4GRU after completing your donation.

 

If you have given to this fund in the past, we hope we can count on you again this year! And thank you for your past support.

 

 

Thank you for considering a donation to the S4GRU Gift/Scholarship Account.

 

 

NOTE: Recurring donations during this time cannot be considered for the gift/scholarship account.

lilotimz
blog-0528799001449390731.jpg

by Tim Yu and Andrew J. Shepherd

Sprint 4G Rollout Updates

Sunday, December 6, 2015 - 2:55 AM MST

 

S4GRU staff is burning the well past midnight oil for our readers. Overnight, Sprint has unofficially updated its network coverage map tool to include LTE Roaming+ and LTE Roaming acquired via its participation in the Competitive Carriers Association (CCA) Roaming Hub and its own Rural Roaming Preferred Partners (RRPP) program. The coverage tool LTE roaming update clearly is a work in progress -- more on that later. But LTE roaming is finally here.

 

So, what is the difference between LTE Roaming+ and LTE Roaming?

 

LTE Roaming+

 

A simple explanation is that LTE Roaming+ is pseudo native coverage. Sprint users will access certain other LTE networks without roaming restrictions and can treat them as native. Usage does not count against any roaming cap, the only restrictions being the plan type ("unlimited" vs data allotment).

 

Roaming in these areas counts as on network usage. Similar level of service as on network, but not all services may be available. More here.

 

LTE Roaming

 

LTE Roaming is non native, off network coverage. Usage is counted against Sprint plan roaming caps. Older plans, such as the Everything Data, have a 300 MB limit, while newer plans, like Framily, are limited to 100 MB.

 

For a specific LTE roaming footprint example, see this coverage tool screenshot centered around Sprint's headquarters in the Kansas City metro. From the LTE roaming legend, the dark green LTE Roaming+ in western Kansas is Nex-Tech Wireless, and you can catch a glimpse of the same LTE Roaming+ from C Spire south of Memphis. The light green is LTE Roaming, all of which appears to be USCC at this point. Elsewhere, you will find LTE Roaming on USCC in its Pacific Northwest, Southeast, and New England regions. There is still map work to do -- note the LTE Roaming legend "@TODO will we have a description here?" More LTE Roaming+ and LTE Roaming operator coverage may be added in the coming hours or days.

 

2q0irt1.png

 

Device compatibility?

 

Due to Sprint's unique LTE Band 25-26-41 network configuration, not all Sprint LTE capable devices will be able to roam on partner networks, which may use different bands, such as Band 2 (PCS 1900 MHz A-F blocks), Band 4 (AWS-1 1700+2100 MHz), Band 5 (Cellular 850 MHz), and Band 12 (Lower 700 MHz)

 

As such, a CCA/RRPP compatible Sprint triband device, of which many were released in the past year, is the best bet for full network compatibility with partner LTE networks. A CCA/RRPP device will have LTE Band 2-4-5-12-25-26-41 support, which basically covers all of the standard LTE bands in use in the US -- minus VZW Band 13 and AT&T Band 17. No matter, VZW and AT&T presently are not LTE roaming partners with Sprint.

 

If Multi Frequency Band Indicator (MFBI) is active at the network level, a regular Sprint triband device (Bands 25-26-41) may be able to access some partner networks -- due to Band 25 (PCS 1900 MHz A-G blocks) and Band 26 (eSMR 800 MHz + Cellular 850 MHz) being supersets of Band 2 and Band 5, respectively. However, these triband devices will not roam if the partner network uses Band 4 or Band 12.

 

An older single band Sprint LTE Band 25 device will be even more restricted. If it can roam at all, it will be limited to partner networks that use Band 2, again assuming MFBI.

 

In Summary...

 

A few months ago, Sprint upgraded much off network coverage for most accounts from only CDMA1X to EV-DO. Now, a lot of that same roaming footprint gets elevated a second time to LTE. Sprint LTE, eHRPD/EV-DO, and CDMA1X coverage still will hold highest priority. Whether LTE Roaming+ or LTE Roaming, it will not supersede Sprint eHRPD/EV-DO or CDMA1X signal. But outside of all Sprint native coverage, roaming gets another boost.

 

LTE roam, roam if you want to.

 

 

Sources: Sprint, S4GRU thread

WiWavelength
blog-0357743001447270793.png

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:

Switching carriers is a lot easier with an unlocked HTC One A9. You'll be able to switch carriers at will with the HTC One A9 unlocked edition. Simply insert your activated AT&T or T-Mobile SIM to begin using your HTC One A9. Verizon LTE compatibility will also be supported via a software update at a later date. Sprint compatibility requires separate hardware - customers switching to or from Sprint will need to switch to a compatible device, which is provided free of charge as part of the 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:

Verizon LTE compatibility will be added via a software update. The HTC One A9 is the first CDMA-less device to support both voice and data services over LTE, providing individuals with the flexibility to use the same device on multiple carrier networks. To ensure the best experience for our customers on the Verizon network, we are conducting more extensive testing and certification. We expect availability to be delayed but we are actively working with Verizon to make it available as quickly as possible.

 

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

WiWavelength
blog-0256559001443455721.png

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:

 

2e33gir.png

 

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

lilotimz
blog-0912036001443219898.jpg

by Tim Yu

Sprint 4G Rollout Updates

Friday, September 25, 2015 - 5:44 PM MDT

 

Update 2: S4GRU's technical editor here again. It is Monday, October 19, and today is the day. Many of the Nexus 5X first preorders started shipping this morning for delivery later this week. You also may have caught the Nexus 5X television commercial that Google ran multiple times during the NFL broadcasts yesterday.

 

In light of the first handsets shipping today, S4GRU wants to publish a second update to this article, confirming the correct Sprint SIM card and covering fully the tested FCC OET (Office of Engineering and Technology) ERP/EIRP RF figures, which recently received a Class II Permissive Change filing.

 

As we speculated a few weeks ago, the correct Sprint SIM for the Nexus 5X is the same 4FF nano SIM as for the 2015 Moto X aka Style aka Pure Edition. It is the latest version Sprint CSIM, so network activation for both LTE and CDMA2000 will be via the SIM. The SIM can acquired for free at a Sprint corporate store with repair center or from Sprint International support online chat. As unlocked, third party handsets are still somewhat rarities on Sprint, some S4GRU users have reported difficulties in obtaining the correct SIM from those official Sprint channels. Your mileage may vary. If you prefer to purchase the correct SIM yourself, you typically can do so at Best Buy Mobile. More detailed info about SIM procurement is available in our newly opened Nexus 5X user thread.

 

In our original publication of this article almost a month ago, I included a sidebar with some brief discussion of RF power output. It hit just the highlights. As the Nexus 5 still to this day has been known for its solid RF performance on the Sprint network, S4GRU wanted to do a full LTE ERP/EIRP rundown of its Nexus 5X younger sibling in this update. This is especially true in light of the aforementioned Class II filing -- disclosing some "Antenna/PCB adjustments" to the Nexus 5X -- subsequent to the original filing and our original publication. Interestingly, none of the peak antenna gain figures have changed, but perhaps small tweaks below the peak gain or in the body of the handset appear to have affected ERP/EIRP slightly.

 

For easy readability, I have put together a table to compare ERP/EIRP and antenna gain across the original filing and the Class II filing. See below:

 

11m3wia.png

 

All of the usual disclaimers 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.

 

My previous RF analysis in the originally published article below stands. The Nexus 5X is relatively powerful in low and mid band spectrum, in which we like to see at least 17-18 dBm and 22-23 dBm, respectively. But it is not quite as powerful as we would hope in high band spectrum, which ideally should be 23 dBm or greater. However, the physical changes that warranted the Class II filing do appear to have reduced low and mid band output by a subtle degree -- possibly in exchange for higher and more consistent output in band 41. The RF figures seem to suggest that.

 

To conclude, if you have ordered the Nexus 5X, watch your mailboxes and doorsteps this week. In the meantime, you can watch the Nexus 5X television commercial on YouTube.

 

 

Update: S4GRU's technical editor here. We now have the full Nexus 5X tech specs released from Google, thus can comment on a few issues not disclosed in the FCC OET authorization filings last week. Namely, international band support and SIM card form factor. In addition to the tested domestic bands listed below, the Nexus 5X also supports the following international bands:

  • GSM 900/1800
  • W-CDMA band 1/8
  • LTE band 1/3/20

For those unfamiliar, band 1 is IMT 1900+2100 MHz, band 3 is DCS 1800 MHz, band 8 is GSM 900 MHz (or what SoftBank calls the "Platinum Band"), and band 20 is EU Digital Dividend 800 MHz. With those band capabilities, the Nexus 5X will be usable on LTE, W-CDMA, or at least GSM in almost every country on the planet -- though that may require a local SIM card.

 

Speaking of SIM cards -- which are technically UICC now, but most still call them the colloquial SIM -- the Nexus 5X as expected has a 4FF nano SIM slot. Your 3FF micro SIM from the Nexus 5, for example, will not fit. From a Sprint perspective, since S4GRU is primarily a Sprint focused educational site, this does raise another issue. USIM vs CSIM. For activation and network authentication, USIM is 3GPP only (i.e. LTE/W-CDMA/GSM), while CSIM also incorporates 3GPP2 (i.e. CDMA2000). So, on Sprint, a handset that requires a USIM needs a separate CDMA2000 activation process, but a handset that requires a CSIM activates both LTE and CDMA2000 via the SIM.

 

At this point, we do not have any info from LG, Google, or Sprint whether the Nexus 5X will require a USIM or CSIM for activation on Sprint. My educated guess is a CSIM -- just like the 2015 Moto X aka Style aka Pure Edition a few weeks ago. But that remains to be seen. Expect some uncertainty for the first few days, but rest assured, it will all get sorted out shortly. And S4GRU will be here to provide information as it emerges. If warranted, we may write another update to this article. You also can follow along in The Forums in our Nexus 5X thread.

 

Original article:

 

Two years ago, on a September day forever historic for S4GRU, we discovered and announced to the world the then unrevealed 2013 LG Nexus 5, as its FCC OET (Office of Engineering and Technology) authorization documents made a surprise reappearance, and we noted that the backplate photos included in the filings matched up remarkably well with recent images of a mystery device being used at Google. Indeed, we proved to be right about the LG-D820 and got a nice scoop on the rest of the tech press.

 

Today, S4GRU comes forth to herald what appears to be the long anticipated successor to the 2013 Nexus 5. The authorization filings for the LG-H790 have been uploaded late today in the FCC OET database. For the write up on the Nexus 6P, click here.

 

Dimensions:

  • Overall (Length x Width): 146.9 mm x 72.5 mm
  • Overall Diagonal 159 mm
  • Display Diagonal: 133 mm

Supported Domestic Airlink Technologies:

  • GSM 850 / 1900
  • W-CDMA Band 2 / 4 / 5
  • CDMA2000 Band Class 0 / 1 / 10
  • LTE Band 2 / 4 / 5 / 7 / 12 / 13 / 17 / 25 / 26 / 29 (Rx only) / 41

A Category 6 UE with support for 2x carrier aggregation on the downlink.

 

And the supported Carrier Aggregation profiles are as listed (Band #+Band #):

 

Inter band:

2+13

4+13

13+2

13+4

2+4

4+2

2+17

17+2

4+17

17+4

2+29

4+29

2+5

5+2

4+5

5+4

2+12

12+2

4+12

12+4

4+7

7+4

 

Intra band:

2+2

4+4

41+41

 

Carrier aggregation on Verizon? Check.

Carrier Aggregation on ATT? Check.

Carrier Aggregation on T-Mobile? Check.

Carrier Aggregation on Sprint? Yup!

 

To follow up with some brief RF analysis, let us bring in S4GRU's technical editor...

 

This expected Nexus 5X is clearly tuned for low and mid band spectrum. That would be primarily Cellular 850 MHz, SMR 800 MHz, PCS 1900 MHz, and AWS-1 1700+2100 MHz. For Sprint purposes, only PCS and SMR are relevant, comprising the CDMA2000 band classes 1 and 10, the LTE bands 25 and 26, respectively. Since LTE is the going concern, know that band 25 maximum EIRP at 26 dBm is excellent, the same for band 26 maximum ERP at 23 dBm.

 

Unfortunately, high band spectrum does not fare quite as well. The high band antenna covering BRS/EBS 2600 MHz spectrum has a disappointingly low gain of -2.6 dBi. And that seems to be reflected in the band 41 maximum EIRP of 19 dBm, which is low to average, at best.

 

As this almost obviously is the Nexus 5X -- that we know will be a very interesting device to our readership -- we may do a complete RF testing analysis article down the road. But S4GRU wanted to get the highlights out to everyone right away.

 

With Google's September 29 reveal event just four days away, this FCC OET authorization comes right on time. The recent Amazon India leak of the Nexus 5X indicated an identification of LG-H791, and now we have an LG-H790. The 2013 Nexus 5 North American variant was LG-D820 and international model was LG-D821, so the number correlation is there.

 

Should S4GRU be 5X certain that the LG-H790 is the 2015 Nexus 5X? Our track record on these matters is established. But we will let you decide...

 

FCC: ZNFH790

MacinJosh
blog-0304002001441975003.jpg

by Josh McDaniel

Sprint 4G Rollout Updates

Friday, September 11, 2015 - 9:45 AM MDT

 

As most of nearly the entire world is aware, Apple announced the iPhone 6S, 6S Plus, and a number of other devices earlier this week. Most notably, iPhone 6S/6S Plus debuts 3D Touch, which is an enhanced version of Force Touch on Apple Watch. However, for most S4GRU readers here, there was one burning question that was not answered in the keynote.

 

As iPhone models have progressed on Sprint from the iPhone 5 in 2012 with Band 25 LTE to the iPhone 5S in 2013 with dual Band 25/26 LTE to the iPhone 6 in 2014 with Triband 25/26/41 LTE, Apple has oft been half to a full generation behind in supporting the latest Network Vision enhancements.

 

Last year's iPhone 6, for example, did feature the inclusion of Band 41 LTE but not quite full compatibility with CCA/RRPP bands. And Band 41 LTE 2x CA on Android handsets was just a few months around the corner. Well, this year's iPhone 6S includes Band 12 LTE for full CCA/RRPP support and Band 41 LTE 2x CA on Sprint! Now the latest iPhone is fully up to date with all Sprint bands and current technology initiatives that are currently released.

 

Notable Specs & Sprint Interband 2x Carrier Aggregation

 

Yes, that's right, iPhone users now get to enjoy 2x Carrier Aggregation on the Sprint network! This will lead to a doubling in B41 performance in Sprint Spark markets that have CA deployed. Up to 150Mbps in the most ideal signal and network conditions.

 

All you wireless enthusiasts who want to know about radio performance, read further for RF testing information. The rest of the notable specs on the new phones are listed below:

  • A9 processor
  • 2 GB RAM (just like iPad Air 2)
  • 12 MP iSight (rear) camera with 4K video recording
  • 5 MP FaceTime camera with Retina Flash and 720p video recording
  • 7000 Series aluminum body
  • Rose Gold color option
  • Only 1/10 of a cm taller, wider, and thicker than last year's iPhone 6/6 Plus

And now for an RF testing sidebar from S4GRU's technical editor...

 

As always, the usual caveats 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 (Office of Engineering and Technology) in the authorization filings for the device(s).

 

These ERP/EIRP figures are specific to the A1688 and A1687 models, which are the Qualcomm Snapdragon X7 LTE (MDM9635) Category 6 and CDMA2000 equipped iPhone 6S and iPhone 6S Plus, respectively. Separate Band 30 enabled models exist for AT&T, and while those models are disclosed to use the same antenna arrays, they were RF tested separately in the authorization filings, thus may possess different ERP/EIRP figures. So, this data and analysis should not be extrapolated to cover any other iPhone 6S models.

 

Since this article covers two different iPhone 6S models with two different antennas each, I have put together a table for easier viewing and comparison. (Click to Enlarge)

 

aomdzq.png

 

To provide further analysis, the green shaded cells represent the maximum figures for each LTE band across both handsets and both antennas. As we can see, the LAT -- with one or two possibly anomalous exceptions -- is the primary antenna on both handsets, possessing greater maximum ERP/EIRP and/or higher maximum antenna gain.

 

Both iPhone 6S sizes look to be at least good to possibly great LTE performers -- especially in their high band output. ​For the uninitiated, 30 dBm equals a full 1 W. Mid band is good, and low band is at least average. Hopefully, this expected solid LTE performance plays out in the real world and is not compromised by carrier bundle firmware, as some S4GRU users have reported previously.

 

For a comparison of the two sizes, bigger, apparently, is not always better for RF. Somewhat of a surprise, the smaller iPhone 6S is the superior RF performer of the two. It generally has greater maximum ERP/EIRP and higher antenna gain -- as evidenced by the greater number of green shaded cells. Moreover, the LAT to UAT consistency is much better on the iPhone 6S, with relatively less drop off between the two antennas and always higher UAT maximum ERP/EIRP than that of the iPhone 6S Plus. This means the RF "death grip" loss on the iPhone 6S could be much smaller when it has to shift between LAT and UAT.

 

And now for the best part, you could win a new iPhone 6S...

 

S4GRU is in currently in the throes of a Start of Autumn Promotion to help raise money for the site. We are currently planning to raffle off a new iPhone 6S to one lucky winner who donates a minimum of $10 to support the site. All donations go toward S4GRU Sponsor status and future upgrades. However, S4GRU Membership is not required. Click on this link for more details.

 

It's a Win-Win-Win for everyone! You get to support the leading Sprint/Wireless Enthusiast site on the internet, you get a chance to win a brand new iPhone 6S and your donations count toward Sponsor membership upgrades. Support S4GRU today!

WiWavelength
blog-0995969001441169992.jpg

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:

 

11llr41.png

 

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

S4GRU
blog-0640859001439247467.png

by Robert Herron

Sprint 4G Rollout Updates

Monday, August 10, 2015 - 10:30 PM MDT

 

What began as widespread speculation back in May came to fruition today. Shenandoah Telecommunications (Shentel) announced its intention to buy nTelos in a $208 million deal ($640 million total counting debt Shentel will assume). The purchase includes network, spectrum licenses, retail customers/stores and all assets.

 

Shentel is a regional affiliate for Sprint and provides wireless service in the Upper Shenandoah Valley of Virginia and West Virginia, the Maryland Panhandle and Central Pennsylvania. nTelos has been a wholesale partner to Sprint, selling capacity to Sprint customers in the Lower Shenandoah Valley and Blue Ridge communities of Virginia and most of the State of West Virginia.

 

nTelos coverage area is directly adjacent to Shentel with only a little overlap. nTelos coverage complements Shentel's very well. Shentel will have over one million customers in the newly combined company, making it the sixth largest wireless company in the U.S. and the largest Sprint affiliate.

 

At conclusion of the purchase, Shentel will take control of nTelos and its assets. nTelos will cease to exist, having spun off its wireline and fiber assets into Lumos Networks a few years back. So, the rural telco that reached the big time 15 years ago in the Richmond-Norfolk MTA when it purchased a PCS B block 20 MHz divestment from PrimeCo in the merger that created Verizon will be gone for good.

 

The writing was on the wall when nTelos sold off its spectrum to T-Mobile in its large markets of Richmond and Norfolk this past year. Bringing to end an era, as Shentel shutters nTelos' Waynesboro, Virginia headquarters and puts its campus up for sale. Choosing to consolidate the combined company at Shentel's Harrisonburg, Virginia HQ. The end of nTelos will be bittersweet for some, but likely not to be missed by many Sprint customers.

 

Shentel doubles down and re-ups with Sprint extending affiliation

 

In announcing the merger, Shentel concurrently released details of new extended and expanded affiliation agreements with Sprint that now to run through 2029. These separate deals call for the disbanding of nTelos and transfer of the existing nearly 300,000 nTelos customers to the Sprint brand. Existing nTelos retail locations will also be converted to Sprint branding while being managed by Shentel. Sprint will transfer their existing nearly 300,000 customers in nTelos territory into the Shentel affiliate agreement.

 

Most important in this deal is the significant impact on the Sprint network in the Shentel and nTelos territories. Sprint will receive “all spectrum assets in nTelos’ footprint.” This covers more than 5 million people in portions of Kentucky, Ohio, Maryland, North Carolina, Pennsylvania, Virginia, and West Virginia. Shentel will assume responsibility of nTelos' network upgrade and LTE deployment. Which will also include additional cell sites and coverage expansion.

 

Shentel's infusion into the current nTelos network is desperately needed

 

nTelos currently provides 1x voice and 3G EVDO data native coverage to Sprint customers in Western Virginia and West Virginia. nTelos was already in the process of trying to upgrade its network to 4G LTE through a slow and insufficiently funded process. In some areas, nTelos did have LTE open and live for its own nTelos branded customers. However, Sprint customers could not access it.

 

nTelos and Sprint expanded their wholesale agreement last year to include 4G LTE. Under the agreement, nTelos had until 2017 to get the network up and running for Sprint LTE customers, adding Sprint LTE bands using Sprint spectrum assets. nTelos current LTE deployed was not usable to Sprint customer handsets, as it runs on PCS LTE Band 2. And Sprint's is deployed on PCS LTE Band 25.

 

S4GRU hopes that Shentel will deploy MFBI to the newly acquired nTelos LTE network and open it up for Sprint/Shentel customers as soon as physically possible. This should be a priority, as Sprint customers in nTelos areas have been limited to mediocre 3G for years. And we have nearly countless stories of S4GRU members and visitors airing their frustrations and leaving Sprint or nTelos for the Duopoly. But the end is near!

 

nTelos may have a reputation for being way behind the times and struggling, but Shentel is viewed largely the opposite. Shentel has proven to be a well run regional wireless operator and has been on the forefront of its Network Vision upgrade with Sprint. Shentel outperformed virtually every Sprint market in deploying its network modernization upgrades and LTE deployment.

 

The Shentel affiliate market is arguably the best performing Sprint market in the country. Shentel is also aggessive in monitoring and maintaining its network. To keep capacity maximized, keep throughput speeds high and provide the most seamless coverage imaginable in a hilly and mountainous environment. Shentel makes Sprint look good in its region, providing coverage and performance surpassing AT&T and Verizon nearly everywhere.

 

Shentel plans an accelerated network upgrade

 

nTelos customers and Sprint customers in nTelos areas will likely be very pleased with the transition. If the network upgrades can happen fast enough. Shentel did commit to speeding up the process. On their website, they say...

 

"While nTelos was engaged in a network upgrade, Shentel is committed to accelerating and expanding the upgrade of the network in order to provide the Sprint customers the world-class wireless voice and data services they deserve."

 

Shentel is committing over $300 Million in network upgrades and enhancements to bring its newly acquired nTelos coverage areas to Sprint standards and add LTE Bands 25, 26 and 41 (Spark) into the mix. Shentel also will be adding approximately 150 new macro sites (identified in orange on the map at the bottom of the page). Shentel says that the additional coverage from the new sites will improve the experience for the Sprint customers it serves and be more consistent with the type of seamless coverage its existing customers experience in current Shentel service areas. Shentel wants to close the gap and provide a more competitive experience against AT&T, Verizon and U.S. Cellular. There are many customers that Shentel can gain in nTelos areas, as nTelos tends to have a much smaller market share than Shentel does in its markets.

 

The exact details and dates are still being finalized and pretty much are pending the conclusion of the purchase. Shentel expects to have the acquisition wrapped in six months -- but hopes it may be sooner. No significant government hurdles are expected with this transaction.

 

As part of the deal, Sprint will get nTelos varied spectrum license assets. nTelos currently holds spectrum in its coverage area in PCS, AWS and BRS bands. These will complement Sprint's spectrum portfolio very well. Sprint actively uses PCS for voice and 3G/LTE data and BRS for Spark LTE data. Shentel will be using existing and newly acquired licenses in its deployments. What is not known at this time is whether Sprint will sell or trade the Band 4 AWS licenses it will pick up -- or possibly put them to use. Most new Sprint devices since mid 2014 now support LTE in the AWS band, and Sprint could choose to keep these licenses.

 

What to take from all this

 

This is good news for Sprint customers and nTelos customers in Western Virginia and West Virginia. nTelos did not provide good service to Sprint customers in its area. And nTelos customers weren't all that pleased either. There was a steady drumbeat of complaints about nTelos in our forums.

 

Shentel is likely to face a lot of bumps in the road and some major setbacks along the course overtaking nTelos. But it will likely do a much better job along the way. Shentel is well managed from our perspective and better funded. Shentel hit its milestones early and is fairly proactive. The network is going to improve significantly. And once Shentel gets the reins, the progress will move much faster and be measurable. We think Shentel will do well if it can capitalize the upgrades sufficiently and timely. And this is all upside for Sprint.

 

We HIGHLY RECOMMEND that Shentel make opening up the existing nTelos LTE network for Sprint customers a number one priority. Though there is some cost and resources to do this, it will help reduce churn and start building excitement among the remaining Sprint customers in the area. We all need to see something is happening right out of the gate.

 

And Marcelo, if you're reading, please do something about your only other remaining affiliate, Swiftel up in South Dakota. It will be the last vestige of the Sprint network languishing without upgrades. Please, we are begging you! Maybe Shentel West?

 

 

gallery_1_2_1222305.png

CLICK MAP TO ENLARGE. Map showing Shentel's and nTelos' combined coverage (cyan) and Shentel's planned site locations (orange) to better compete with Verizon, AT&T and U.S. Cellular

Source: Shentel, Sprint

WiWavelength
blog-0223041001438661398.jpg

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

 

zuow8z.png

 

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:

 

3hh01.png

 

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:

 

11wei6f.png

 

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:

 

gallery_1_2_25401.png

 

 

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.

 

9fqs0p.png

 

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:

 

v7qfsy.jpg

 

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.

 

2qi8ier.jpg

 

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

lilotimz
blog-0524894001437510871.jpg

by Tim Yu and Andrew J. Shepherd

Sprint 4G Rollout Updates

Wednesday, July 22, 2015 - 1:20 PM MDT

 

On the heels of the first of the late summer/early fall flagship handsets that S4GRU reported on two weeks ago, a second group of superheroes has appeared. And both of these new handsets are destined to be the size of a galaxy. So, take note, and stay on the edge of your seats.

 

Last week, Samsung started certifying what is presumably its next go round of devices for US wireless operators -- the Galaxy Note 5 and the Galaxy S6 Edge+ -- with variants pointed toward T-Mobile, AT&T, Verizon, and USCC popping up in the FCC OET (Office of Engineering and Technology) database. Yesterday, Sprint's models joined the FCC authorizations of the rest under the FCC IDs A3LSMN920P, which expectedly is the Galaxy Note 5, and A3LSMG928P, which presumably is the Galaxy S6 Edge+.

 

A quick glance at the RF Exposure reports identifies the supported LTE bands:

  • Band 2 (PCS A-F)
  • Band 4 (AWS)
  • Band 5 (CLR 850)
  • Band 12 (Lower 700 A-C)
  • Band 25 (PCS A-G)
  • Band 26 (ESMR 800 + CLR 850)
  • Band 41 (BRS/EBS 2600)

...along with the standard CDMA band classes:

  • Band Class 0
  • Band Class 1
  • Band Class 10

...and GSM/W-CDMA bands:

  • GSM 850/1900
  • W-CDMA Bands 2/5

World roaming capability -- including GSM 900/1800 and W-CDMA band 1, possibly other W-CDMA and/or LTE bands, too -- is likely on board. But FCC OET authorizations are not required to document non US bands.

 

Carrier Aggregation Is A Go

 

Following the the presumed 2015 Motorola X flagship authorization a few weeks back -- and that was the the 7th Sprint device to be officially certified for B41 2x Carrier Aggregation (2x CA) -- these two Samsung Galaxy handsets will be the 8th and 9th devices to be officially certified for 2x CA. All join the ranks of the Samsung Galaxy Note Edge, Samsung Galaxy S6, Samsung Galaxy S6 Edge, LG G Flex 2, LG G4, and HTC One M9.

 

Some, though, may be disappointed that the two Samsung devices were not certified for 3x CA like the GSM/W-CDMA/LTE model for T-Mobile and AT&T, while the other CDMA carrier variants for Verizon and USCC are only certified for 2x CA as well. So, it is likely Samsung had to switch out the baseband modem for a Qualcomm category 6 one for CDMA compatibility -- whereas Samsung may have opted for its own category 9 modem in the GSM/W-CDMA/LTE models.

 

Now, to add some RF ERP/EIRP analysis from S4GRU's technical editor...

 

We will dive straight in to the numbers. Of course, all of the usual disclaimers about lab testing versus real world performance and uplink versus downlink apply. The figures represent our best averaged and rounded estimates of maximum uplink ERP/EIRP -- with band class 10, band 25, band 26, and band 41 receiving heavier weighting toward uniquely Sprint frequencies or configurations.

 

Samsung Galaxy Note 5:

  • Band class 0/10: 21 dBm
  • Band class 1: 19-20 dBm
  • Band 2/25: 18-21 dBm
  • Band 4: 21 dBm
  • Band 5/26: 17-20 dBm
  • Band 12: 16 dBm
  • Band 41: 17-18 dBm

Samsung Galaxy S6 Edge+:

  • Band class 0/10: 22 dBm
  • Band class 1: 22-24 dBm
  • Band 2/25: 19-22 dBm
  • Band 4: 20-22 dBm
  • Band 5/26: 21-22 dBm
  • Band 12: 21 dBm
  • Band 41: 18 dBm

For comparison, here are the ERP/EIRP figures from S4GRU's FCC OET Galaxy S6 article a few months ago...

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)

 

Frankly, Samsung used to be a leader in RF performance but is showing some continued regression. The Galaxy S6 and Galaxy S6 Edge in their Sprint variants brought roughly average to below average RF. In particular, band 41 EIRP was weak. That has not changed with these two new Galaxy handsets -- band 41 is still well below the at least 23 dBm that we would like to see. Between the two handsets, the Galaxy Note 5 is the RF chump. Sorry, Galaxy Note fans, the Galaxy S6 Edge+ is notably superior in that regard. The Galaxy Note 5 ERP/EIRP is average to below average across the board. Meanwhile, the Galaxy S6 Edge+ is generally a few dB better and actually brings some good low band performance to the table. To reiterate, though, both lack band 41 oomph, and that is a disappointment for Sprint.

 

Next, to echo Tim's sentiments above, the Galaxy Note 5 will not be the first Sprint handset to offer 3x CA capability, though many had predicted that. Both it and the Galaxy S6 Edge+ are using not a category 9 or 10 baseband but a category 6 baseband, most likely the Snapdragon X7 LTE (MDM9635) -- the same as in the Sprint variant Galaxy S6 and Galaxy S6 Edge. This is because Samsung has at least temporarily, probably permanently shifted away from Qualcomm chipsets in favor of in house chipsets. That means Exynos processors and modems. The Exynos processor is airlink technology agnostic, but the modem certainly is not. And Samsung does not have a 3GPP2 (i.e. CDMA2000) baseband, so it still sources that separate chipset from Qualcomm. For further reading on the processor, baseband, RF transceiver, and carrier aggregation issues, see S4GRU's previous FCC OET articles on the Galaxy S6, Galaxy S6 Edge, and One M9 as well as the G4.

 

Well, that is a wrap. So, are these new Samsung Galaxy handsets Groot or not? Discuss.

 

Source: FCC

lilotimz
blog-0544608001436983713.jpg

by Tim Yu

Sprint 4G Rollout Updates

Wednesday, July 15, 2015 - 3:17 PM MDT

 

Consider this just a public service announcement. Sprint Spark Band 41 Carrier Aggregation (2x CA) now is officially live according to a Sprint internal announcement leaked on Reddit today by a verified Sprint employee in the Sprint subreddit. Late last month, S4GRU found evidence of 2x CA being live in Atlanta, but this now is a formal notice that Sprint has sent to its employees.

 

This is the present lineup of 2x CA capable devices:

  1. Samsung Galaxy S6
  2. Samsung Galaxy S6 Edge
  3. Samsung Galaxy Note Edge
  4. LG G Flex 2
  5. LG G4
  6. HTC One M9
  7. ZTE Hot Spot

Edit: S4GRU has been fielding numerous questions on other devices. To make this very clear, the above are the only devices right now capable of 2xB41 Carrier Aggregation because they have the hardware (category 6 modem) that is required. Any other phones that were released previously are not compatible because their modems are not category 6 (or higher).

 

As detailed in the internal document (posted below), the seven devices may receive automatic profile updates this week to enable 2x CA. Alternatively, as some S4GRU users have discovered, 2x CA may already be enabled or can be enabled manually via the hidden Data programming screen.

 

Next, these are the initial markets in which Sprint is rolling out 2x CA:

  1. Boston
  2. New Jersey
  3. Long Island
  4. Philadelphia Metro
  5. Providence
  6. Southern Connecticut
  7. Baltimore
  8. Cincinnati
  9. Columbus
  10. East Michigan
  11. West Michigan
  12. Indianapolis
  13. Washington DC
  14. Austin
  15. Dallas Fort Worth
  16. Houston
  17. Kansas
  18. Missouri
  19. San Antonia
  20. Atlanta / Athens
  21. Miami / West Palm
  22. Orlando
  23. South West Florida
  24. Tampa
  25. Chicago
  26. Colorado
  27. Milwaukee
  28. Minnesota
  29. Oregon / SW Washington
  30. West Washington
  31. Utah
  32. LA Metro
  33. Las Vegas
  34. North LA
  35. Orange County
  36. Riverside / San Bernardino
  37. San Diego
  38. SF Bay
  39. South Bay

For reference, here is a S4GRU map of all Sprint markets:

 

gallery_1_5_299248.jpg

 

Finally, this is the internal document posted on Reddit:

 

lBk9ap5.png

 

Source(s): Reddit

lilotimz
blog-0468812001436315861.jpg

by Tim Yu

Sprint 4G Rollout Updates

Wednesday, July 8, 2015 - 08:51 AM MDT

 

Mid summer has arrived in the northern hemisphere, and that means the harvest of fall flagship handsets is just getting underway. (The exception are Apples, which are planted and picked all in one afternoon in September.)

 

The past two weeks brought our first crop. A new authorization for a Motorola device in the FCC OET (Office of Engineering and Technology) database arrived yesterday. Just about in time for Motorola's expected August/September launch of its flagship (read: Moto X) devices.

 

Prior to that, S4GRU staff discovered a Motorola device filing last week with FCC ID IHDT56UC2, approved for LTE bands 2/4/5/7/12/17/25/29/41 in addition to the standard W-CDMA and GSM bands. Quick staff analysis of the filing lead to the conclusion that it was a either a fully unlocked version or a T-Mobile variant -- due to onboard VoWi-Fi and intra band band 4 carrier aggregation, both of which T-Mobile is pushing hard.

 

But other tech media discovered and wrote articles on the handset filing -- with some speculating that it was for Sprint as well, due to the inclusion of LTE bands 25/41. Did they overlook that band 26 and any CDMA2000 capability were absent? We know very well that Sprint devices must have LTE bands 25/26/41 and CDMA2000 band classes 0/1/10 at the minimum.

 

So, we waited with watchful eye for any new authorizations from Motorola, expecting a Sprint variant soon. Indeed, Motorola delivered FCC ID IHDT56UC1.

 

Fully Sprint CCA/RRPP and VZW/AT&T/T-Mobile compatible

 

This handset is fully certified for the Sprint network and those of its CCA/RRPP partners. It also completely covers VZW and T-Mobile network capabilities, mostly for AT&T, too, though lacking Ma Bell's emerging LTE bands 29/30.

 

For a full rundown, it supports:

 

LTE bands: 2 / 4 / 5 / 7 / 12 / 13 / 17 / 25 / 26 / 41

CDMA Band Class: 0 / 1 / 10

W-CDMA Band: 2 / 4 / 5

GSM: 850 / 1900

 

So, Sprint Spark? Got it. VZW XLTE? Got it. T-Mobile band 12? Got it. This handset does almost everything -- including carrier aggregation.

 

Sprint Band 41 Carrier Aggregation Capable

 

The device is a category 6 UE and supports all of the myriad FDD carrier aggregation combos present in the unlocked or T-Mobile variant detailed earlier. But this variant also includes Sprint's LTE Advanced implementation of TDD carrier aggregation on band 41 -- aka 2x CA band 41 or B41+B41. For reference, S4GRU confirmed activation of carrier aggregation and wrote about it a few weeks ago.

 

Now, this is the seventh announced device to support Sprint's band 41 carrier aggregation, joining the ranks of the Samsung Galaxy S6, Samsung Galaxy S6 Edge, Samsung Galaxy Note Edge, HTC One M9, LG G Flex 2, and LG G4.

 

Edit: There may be issues with MXPE's B41 carrier aggregation compatibility with the Sprint Network.

 

To wrap things up, I am not conclusively declaring that this is the 2015 Moto X nor that it is definitively headed to Sprint postpaid -- we all know what happened with the Sprint variant 2014 Moto X. But the band 41 carrier aggregation support screams Sprint and the FCC authorization timing comes spot on for an August/September device launch, as historically has been the time when Motorola has launched its flagship devices.

 

So, you be the judge...

 

Source: FCC

S4GRU
blog-0068333001435684331.png

by Robert Herron

Sprint 4G Rollout Updates

Tuesday, June 30, 2015 - 1:30 PM MDT

 

Update: at 7:00 p.m. MDT Sprint CEO Marcelo Claure announced the following on Twitter, "We heard you loud and clear and we are removing the 600 kbps on streaming video. #Allin and we won't stop"

.

We don't do many editorials here at S4GRU. We tend to editorialize in our forums. Where our opinions run rampant. We also don't do articles about plan offerings. We are a network focused site. However, our Staff here at S4GRU feels that one is due concerning Sprint's new All In plans.

.

We aren't sure where Sprint was going with this. Is it a new plan or is it a Trojan horse meant to protect the network from streaming?

 

The title "ALL IN" and the hashtag #AllIn conjures up the thought of the poker strategy. Where you push all your chips in with your best and final bet. The one you do when you have a winning hand. The bet that ends all other bets. It's everything you can offer up. You have given your all. It's the best you can do and you believe it is unbeatable. Because you are putting it all on the line.

 

But the All In plan doesn't appear to be a winning strategy. We believe it will not succeed for Sprint as they intend. It is not really less expensive or more attractive than existing plans or Tmo's new plans. And has a Draconian hard streaming cap of 600kbps throughput. That streaming cap is going over like a lead filled balloon.

 

Simple is good, you're on the right track

.

We like the idea of simplicity. No more hidden costs and fees. You just pay one flat rate for phone and unlimited data. OK. The David Beckham video and the attractive Sprint store rep is good. It makes a great point, compared to your competitors. But it's an easy thing for your competitors to replicate. Simple pricing. And they don't have fine print limiting streaming to only 600kbps. That really is the kicker here.

 

So we just aren't seeing the new and innovative thing with All In. You already have plans that price out the same way as All In (some even less expensive). It appears as a marketing gimmick that is disguising a desperate move to limit streaming. This is not popular with your current customers and your new customers are likely going to hate you for it. After they find out.

.

Marcelo, it's inappropriate that David Beckham touts unlimited movie watching and you reference unlimited watching videos in your Press Release. 600kbps video streaming can hardly run any YouTube or Netflix streaming. It will buffer significantly even with the lowest resolution settings. 600kbps is insufficient for most moderate quality video streaming on a smartphone screen.

 

Unlimited only matters because of streaming

 

Let's face facts here. Unlimited only matters to most customers because of streaming. I'm just pulling a number out of the sky here based on my experiences running a Sprint themed wireless blog, but I would venture a guess that 95% of your customers use just a gig or two of data monthly if you do not include streaming. It's not hard to offer unlimited data excluding streaming.

 

Most customers who see Sprint as a value in wireless is because of unlimited streaming. If customers do not stream, they can live with reasonable data buckets. 1GB, 2GB, 5GB plans will work for almost everyone, excluding streaming. If you remove streaming from unlimited, most people don't care about unlimited when they understand it all.

 

Yes, you will still allow unlimited streaming with All In plans, but at only 600kbps. That is way too low. It is a defacto removal of unlimited streaming. I'm sure it was put in place to reduce the burden on the network significantly. By getting people to stop streaming because of the poor video quality. And reducing the burden on the network for those who continue with poor quality streaming.

 

With all that said, we get it. We get the need to do something about streaming. It is a problem. It is a huge drain on your network. But we need to call it what it is and not hide the problem in a new plan and then tout unlimited streaming to the masses. That part is a huge mistake. The media, bloggers and your customers are all crying foul.

 

Unlimited data abusers are killing the network, we get it. But this is not the solution or the time

 

The problem here is that the All In plan punishes everyone. But we see the issue here as data abusers. Customers who use vastly higher data amounts than everyone else. The five percenters, or even the one percenters. Tmo has decided to deal with these types by creating a monthly soft cap of 21GB on unlimited plans. So for Tmo, they have drawn a line and said that customers who exceed 21GB are the ones causing the most problems on their network.

 

Most customers do not use more than 21GB per month. Probably 95% - 98% use less than that. To cite our own S4GRU internal poll, somewhere just north of 8% use that much data. And our members are typically pretty heavy users compared to the general population.

 

But our data also illustrates that a minority of users, those who use more than 21GB per month, have a huge impact to the total usage. Just a small handful of abusers can account for 30% to 50% of all traffic. These people are killing unlimited data for all of us.

 

S4GRU Staff and most of our members understand the burden that the abusers are creating to the network. We have been sitting by waiting for something to be done about it. We know something has to be done, and we support something to be done in general. But this is not it.

 

The T-Mobile 21GB soft cap is one way. And frankly, it's much better than a 600kbps streaming cap. Your streaming cap affects all customers who stream. The Tmo 21GB cap affects only customers who have used more than their fair share. And it gets reset next month. Your 600kbps plan never gets reset. A customer can never do anything to have a good quality stream, except leave Sprint.

 

I can understand why you wouldn't mind chasing away data abusers. But why would you want to chase away good customers who occasionally want to have a quality streaming experience? You're telling them they have to go to T-Mobile, or AT&T or Verizon if they want a quality video streaming experience. Bad idea!

 

You need to remove the 600kbps streaming limit immediately from All In. Or it is dead on arrival. DOA. David Beckham can't save it as is. Like he is going to watch videos on his smartphone streamed at 600kbps. You need to do this in a way that punishes only those who abuse your unlimited offering. Not every day customers.

 

Perhaps limiting video streaming to something more useful? Like 2Mbps. Or maybe a soft cap, like 21GB? Or 25GB? Also, the previous plans of only limiting users on sites that are over capacity. That at least was fair. I understand Net Neutrality all plays into this. But something better is needed. You're strangling your Golden Goose. It feels like you have just put Unlimited on life support.

 

In conclusion

 

We like the idea of simplicity. All In has good roots and the David Beckham video really drives home the point. It can be a good differentiator for Sprint. Although some of our members would like to see the pricing even lower to compete better with existing plans.

 

That said, Sprint must do something else with the video stream throttling. It's nearly universal that 600kbps is too low. It's not even close to satisfactory. We have never had a virtually unanimous response before. Until now. Nearly everyone believes this is an outright awful move.

 

We could find almost zero support even among Sprint's most loyal base. Marcelo, the tech media and the haters are eating your lunch today. You're being flamed, and All In will go down in flames if you don't do something about this. And fast.

.

Unlimited is what Sprint uses to differentiate itself from everyone else. And Sprint's unlimited reputation is being injured right now. Sprint cannot handle being branded as the network with unlimited, except streaming. It will drive customers away and keep them away in droves. The reputation is already starting to stick. Fix it! Fix it now!

 

Marcelo, we are begging you to crack down on the data abusers. Not your everyday customers who may stream occasionally. Or may use a lot over one or two days every few months when on vacation. Most of your customers want to be able to have a quality streaming experience within a reasonable amount every month.

 

But my real fear is new customers. They are expecting a quality streaming experience, as they received from their previous providers. Now just unlimited. It's not like Sprint sales reps are going to be telling everyone they are going to have a low resolution always buffering video streaming experience. It will be in the fine print that no one will read. And they are going to be pissed off at Sprint once they figure it out. And your competition and the Sprint haters are going to eat this up. John Legere is already grinning ear to ear like the Grinch who Stole Sprint Customers.

 

There's still time to fix All In. But time is running out. Please make me look foolish for #AllInDOA. I want to eat my words. Err, hashtag. Marcelo did make me eat it! And it was tasty!

 

gallery_1_2_3929.png

S4GRU
blog-0390406001435190032.png

by Robert Herron

Sprint 4G Rollout Updates

Wednesday, June 24, 2015 - 5:20 PM MDT

 

It's finally happening. 2x Carrier Aggregation was found in the wild today on the Sprint network! We have been receiving reports for the past several months that second B41 channels were appearing all over Sprint-land, but nothing about finding them being aggregated together. That changed this afternoon.

 

It was discovered today by an S4GRU Member in the Atlanta market that Carrier Aggregation is live on LTE Band 41 (TDD LTE 2600). S4GRU Member Camcroz was able to get his Samsung Galaxy S6 to connect to two B41 carriers simultaneously. Even with a medicore -108dBm signal while moving highway speeds, he was able to get nearly 90Mbps. Theoretical maximum for 2xCA on 20MHz TDD LTE channels in the time configuration Sprint is using is 160Mbps in ideal circumstances.

 

We do not know the extent of how much is live in Atlanta or other markets. This may only have been a test and will be taken offline soon. Or it's possible that it is going live today in other Nokia markets, or maybe even Sprint-wide where two B41 channels are live.

 

Camcroz reported to S4GRU he was able to keep B41 2xCA while travelling down Highway 400 near Avalon Mall in Alpharetta all the way across most of Atlanta, losing it as he approached the Hartsfield/Jackson International Airport where he ended up on Clear B41 single carrier.

 

The picture below represents the member's findings. He reports that he had 94Mbps Down in his best test. He had to manually enable Carrier Aggregation himself on his GS6 using ##DATA#. Sprint devices currently have it disabled automatically. They will likely push an update in the future to enable it for customers.

 

med_gallery_1_2_30758.jpgmed_gallery_1_2_87768.jpg

 

This is two 20MHz TDD-LTE B41 carriers connected together via Carrier Aggregation (noted as 2xCA). Sprint says it will not be until 2016 before they have devices released and the network prepared for 3xCA (three 20MHz carriers aggregated together).

 

Let us know if you are able to find any 2xCA in your neck of the woods. Report your findings in the comments below or in an appropriate S4GRU forum thread. Viva la Carrier Aggregation!!!

  • PROGRESSIVE RAFFLE
    FOR AN iPHONE 8

    iphonexiphone8.jpg

    WHICH CAN PROGRESS TO AN iPHONE 8+ OR AN iPHONE X
    **or an Android device of equal or lesser value**

    CLICK HERE FOR MORE DETAILS

  • gallery_1_23_9202.png

  • COMMENTS FROM THE WALL

    • Ah... to get back to test-the-window mode, first we select Shutdown from the menu.  That shuts the unit down and gets it back to the original state (that it arrived in the box).  Then hold down the hidden button on the front for 5 seconds and wait for the unit to power back up.  Then I can access test-the-window mode again. Funny thing is that when I take the Magic Box outside and point it directly at the cell tower, the maximum that I get is 12 (out of 100).  But when I put it in a particular window, I can get 16.  So I'm using that.  It is still showing Band 25, but SpeedTest is reporting a better number now than I had before in a different window.  Scott Thanks,    
    • I can do the menu option and 30-second power cycle to restart, but how do I get back to the initial test-the-window mode? Also, lilotimz's screenshots show Relay on Band 41.  But my Relay screen shows Band 25.  My understanding was the the Magic Box only worked on Band 41 based on the Sprint FAQ:   https://community.sprint.com/t5/tkb/articleprintpage/tkb-id/MagicBox%40tkb/article-id/1 Will my phone work with Magic Box? Magic Box operates on LTE 2.5GHz frequency (Band 41), so only devices with this capability will work with it.  Most newer smartphones will work but you'll need to check your device's specifications for LTE 2.5 GHz to be sure. So how do I get back to test-the-window mode?  And how do I get my Magic Box to Band 41 ?  I've tried different windows, rotating it 90 degrees, and angling it.  It seems to always prefer Band 25.  I do have Band 41 here, but Band 25 seems stronger... Thanks, Scott      
    • I'd recommend trying to run setup again.  I've found that the MB picks up far better B41 signal than my phone does.  
    • ...Also, the 3 screens are accessible by touching the screen, then selecting GPS, LTE, or Relay.  The 4 menu options are accessible by touching the little square icon in the upper-right corner.   Scott  
    • I received my Sprint Magic Box and hooked it up.  I was never able to get the "button" that the two arrows point to to work, so I plugged it in. It took about 20 minutes to initialize and lock-in.  There are 3 screens:  GPS, LTE, Relay. On the Relay screen, it says Band 25.  I assume that means that it is communicating with the Sprint tower on Band 25.   But I thought the whole point was to use Band 41. I tried a couple of different windows, and even flipped the unit sideways to see if it made any difference.  The signal to my cell phone went from -114 to -64, so the Magic Box certainly helps with the indoor signal. That's to be expected; according to the front panel, the Magic Box is transmitting a 25 dBm signal.  However, my Speedtest speed is still 4 Mbps. Other than the 3 screens (GPS, LTE, Relay), and the 4 menu options (Change Time Format, More Info, Other Actions, Re-Run Setup), I can't find any other settings. One of the screens says that the Magic Box Technical Support phone number is 844-463-3194, but I haven't tried calling yet.  I don't want them to say, "it doesn't work for you, mail it back".   Is there any way to lock the Magic Box to Band 41 ?    Sprint's Magic Box checker said that I'm in an eligible zone, the coverage map shows I'm in a Band 41 zone, and prior to the Magic box my phone communicated with the Sprint tower on Band 41.  But for the past 3 days , the Relay screen says that the Magic Box is on Band 25. With correspondingly with poor Mbps. Thanks, Scott  
  • ARTICLES FROM THE WALL

  • Posts from The Forums

  • Blog Statistics

    • Total Blogs
      1
    • Total Entries
      382
×