S4GRU

I think we have a 250 member limit now. Robert via Nexus 5 using Tapatalk

You're welcome to start a VoLTE thread in the forums. Robert

I have no idea where specifically the FIT's are located within each market, unfortunately. I am half wondering if the Virginia one is in Shentel territory. It's the only part of VA with a solid LTE build available. Robert

You just did. Robert

by Robert Herron Sprint 4G Rollout Updates Wednesday, July 16, 2014 - 5:30 PM MDT Hold the phones! One day, you won’t have to worry about holding the phones as Sprint moves to VoLTE for its voice telephone services. That is because VoLTE (Voice over LTE) will allow customers to do a voice call and LTE data simultaneously. S4GRU is now able to confirm that Sprint is proceeding with Voice over LTE based on detailed information from an anonymous Sprint executive. He was able to confirm some of their plans for the transition to VoLTE for voice. In recent months, Sprint has been quite mum about moving to voice over its LTE network. Maybe even a bit misleading about it. Causing some to believe they may not even move to VoLTE at all. Public quotes from Sprint have reiterated that CDMA will carry its voice needs for the foreseeable future and not being in any rush about going to VoLTE like all their competitors have proclaimed. And based on this new information S4GRU recently obtained, it will certainly not be rushed. But Sprint is moving forward with a solid VoLTE plan that will see the lion share of its voice usage move to LTE. This is a relief to some S4GRU members, as they have been getting anxious as they hear other providers publicly extol their upcoming VoLTE networks. We will discuss some details of the plan as they were shared with us. The Sprint VoLTE plan Currently, Sprint is in the programming phase of VoLTE. This includes all the design criteria and functionality that can and should be included in their VoLTE system. This includes discussion and feedback from device and network OEM’s about feasibility and hardware support. When this programming phase completes this summer, it will then proceed with an FIT (Field Implementation Testing) phase. During the FIT, they will be able to discover any issues and bugs that need to be worked out before OEM’s start mass producing equipment and VoLTE is instituted nationwide on the Sprint LTE network. Sprint VoLTE FIT’s are planned to be in Kansas, Greater Chicago (Illinois) and Virginia. Key roaming partners will participate to ensure interoperability. An opening up of the VoLTE network to customers will be in a future implementation phase that is yet to be scheduled. The schematic schedule would have that be in Mid 2015, but it could be sooner if everything goes well in the wrap up of Phase 1, the FIT and the availability in the device ecosystem is realized. Key Points Sprint is proceeding with incorporating VoLTE into its network to capitalize on the following advantages: To support both domestic and global roaming for its customers and customers of other VoLTE providers Reducing the CDMA network (capacity, not coverage) by removing most of the voice burden to allow for spectrum refarming for additional LTE carriers (capacity) VoLTE will allow HD Voice to be interoperable with several other providers by using the 3GPP EVS (Enhanced Voice Service) codec and integrating other networks together Additionally, here are some details about how Sprint will implement VoLTE: The Sprint VoLTE network will be designed to hand off calls to the existing Sprint CDMA network, including HD Voice calls, via the EVRC-NW codec EVS codec standardization may not be achieved by the time Sprint starts deploying a VoLTE network. They will use AMR-WB and EVRC-NW for testing initially. This may limit initial interoperability of HD Voice in the beginning. Sprint to SoftBank Mobile VoLTE calls should be able to use HD Voice from the beginning, and vice versa. Sprint will leave some CDMA voice capacity indefinitely. However, ultimately the goal is to remove CDMA 1X Voice when coverage and quality is equal or better than customers experience today. Additional low frequency spectrum may be required, depending on future voice demand which is steadily declining. VoLTE calls will not be given QoS Priority on LTE initially. Should LTE capacity constraints be experienced during a VoLTE call, the call will be handed over to the 1x network. As the LTE network matures and loads are better balanced, voice on LTE will be given priority over other LTE traffic similar to WCDMA networks. FDD LTE networks will be preferred for VoLTE traffic over TDD LTE. TDD already has the uplink slotted for maximum data download efficiency. Adding additional uplink data demand for voice (which is synchronous in nature) on TDD (which is not synchronous) may cause a noticeable data upload degradation in voice demand scenarios. Due to FDD being synchronous in nature like voice calls operate, Sprint VoLTE will prefer FDD LTE over TDD LTE when possible to provide for the best network operation. Interoperability over getting it installed now One of the key reasons why Sprint is going to be last to the VoLTE race is because of interoperability. The most important attribute to Sprint for VoLTE is roaming with other providers. Early VoLTE networks will either not support interoperability, or will require significant upgrades or network changes to allow it. VoLTE is only now maturing to a state of interoperability where there are enough standards to ensure a system that can work with other providers. Unlike the Duopoly and some other early VoLTE adopters who may not care for an open voice network, and may even be against it, Sprint is making sure that its network is designed with interoperability in mind. So it works with other providers from the beginning. Sprint is likely working with CCA and RRPP members. And this makes sense in context with remarks recently from RRPP partner VTel in Vermont. The Sprint network is being designed from the get go to make sure it can host roaming for other LTE providers around the country and around the world, and also that Sprint VoLTE devices are capable of roaming on partner LTE networks as well. LTE can finally be that bridge to a cohesive global voice and data network among different providers. Since the world is embracing LTE as the de facto standard, it would be a shame to miss out on that level of interoperability. Granted, there will be some band support issues, but OEM’s have made great strides in providing devices to handle a great many bands these days. The current Nexus 5 model supports many LTE bands already. Sprint is banking on the slower and well planned route to VoLTE is going to provide a better network to seamless global interoperability for Sprint customers. Now if the FCC and DOJ will take notice and stop the Duopoly from buying out CCA members. This is the largest threat to competition in the wireless market currently, in my opinion. CCA Member Coverage Map. This is an illustration of what LTE and VoLTE could look like upon all existing CCA members upgrading to fully interoperable LTE/VoLTE networks.

Sprint did announce that they were working with Pioneer through the CCA. So, why couldn't they also be a RRPP member? They couldn't use the Verizon LTE network, but surely they could put anything they want on their towers on separate infrastructure from Verizon. Robert Pioneer Cellular was shown by Masa as a Current Sprint LTE partner in March 2014

Yeah, they were in the CCA Annoucement, but not the recent RRPP announcements. So, either this is some new CCA coverage or new unannounced RRPP coverage. Or testing. Exciting. Robert

Wow, I just noticed them. Guess I'm late to the party! Robert

Some Sprint LTE coverage showed up on Sensorly outside Woodward and Alva in Western Oklahoma. These are not Sprint corporate or affiliate coverages. Some live CCA/RRPP LTE coverage starting to appear? Robert

I saw Tenderloin...which made me think of meat. And when I think of meat and San Francisco, I think of Tommy's Joynt on Van Ness. Yumm... OK. Back to our regularly scheduled programming! Robert via Samsung Note 8.0 using Tapatalk Pro

bitter cold Robert via Samsung Note 8.0 using Tapatalk Pro

He's using SignalCheck Pro for those extra signal strength bars. Robert via Samsung Note 8.0 using Tapatalk Pro

And my wife told me this morning of this Happy gem... http://www.youtube.com/watch?feature=youtu.be&v=XsWo8apgLys Robert via Samsung Note 8.0 using Tapatalk Pro

shop towel Robert via Nexus 5 using Tapatalk

I heard this on the radio this morning. AJ, I post this YouTube video in honor to you for all the painful posts you endure and mock. I present to you, Word Crimes by Weird Al... We should start posting this clip in response to all the English butchering that occurs around our forums. Robert via Nexus 5 using Tapatalk

Site acceptance report from Thursday (7/10) through Monday (7/14): Alabama - 1 update (1 LTE) Arkansas - 2 updates (2 LTE) Atlanta / Athens - 5 updates (5 CDMA 800) Baltimore - 2 updates (2 CDMA 800) Boston - 165 updates (3 3G, 156 CDMA 800, 6 LTE) Buffalo - 1 update (1 LTE) Central Illinois - 1 update (1 LTE) Central Iowa - 3 updates (3 CDMA 800) Central Jersey - 1 update (1 iDEN Conversion, 1 Deactivated) Chicago - 9 updates (7 LTE, 1 new 3G/800 site, 1 Deactivated) Cincinnati - 69 updates (1 3G, 56 CDMA 800, 12 LTE) Cleveland - 1 update (1 LTE) Colorado - 4 updates (4 3G) Columbus - 9 updates (5 CDMA 800, 4 LTE) DFW - 1 update (1 LTE) East Iowa - 11 updates (10 CDMA 800, 1 LTE) East Michigan - 6 updates (6 LTE) East Texas - 1 update (1 LTE) GA/SC Coast - 5 updates (5 CDMA 800) Georgia - 8 updates (1 3G, 7 CDMA 800) Gulf Coast - 1 update (1 LTE) Hawaii - 1 update (1 3G) Idaho - 1 update (1 LTE) Indianapolis - 3 updates (3 LTE) Kansas - 1 update (1 LTE) LA Metro - 7 updates (2 3G, 2 CDMA 800, 3 LTE) Las Vegas - 18 updates (10 CDMA 800, 8 LTE) Lower Central Valley - 10 updates (9 CDMA 800, 1 LTE) Memphis - 3 updates (1 3G, 2 LTE) Miami / West Palm - 2 updates (1 LTE, 1 new DAS site) Minnesota - 10 updates (1 3G, 7 CDMA 800, 2 LTE) Mississippi - 2 updates (1 CDMA 800, 1 LTE) Missouri - 1 update (1 LTE) Myrtle Beach - 2 updates (2 LTE) New Orleans - 2 updates (2 CDMA 800) New York City - 25 updates (2 3G, 18 CDMA 800, 1 LTE, 1 new 3G/LTE site, 1 new 3G site) North LA - 14 updates (6 CDMA 800, 8 LTE) North Wisconsin - 1 update (1 LTE) Northern Connecticut - 51 updates (50 CDMA 800, 1 LTE) Northern Jersey - 3 updates (3 LTE) Oklahoma - 2 updates (2 LTE) Orange County - 3 updates (3 LTE) Orlando - 5 updates (2 3G, 1 CDMA 800, 2 LTE) Philadelphia Metro - 9 updates (9 CDMA 800) Phoenix - 29 updates (9 CDMA 800, 20 LTE) Pittsburgh - 4 updates (4 LTE) Providence - 24 updates (24 CDMA 800) Raleigh / Durham - 2 updates (2 LTE) Riverside / San Bernardino - 4 updates (2 3G, 2 LTE) Rochester - 1 update (1 LTE) SF Bay - 13 updates (10 CDMA 800, 3 LTE) San Diego - 2 updates (2 LTE) South Carolina - 2 updates (2 CDMA 800) South West Florida - 3 updates (3 LTE) Southern Connecticut - 132 updates (1 3G, 131 CDMA 800) The Panhandle - 1 update (1 3G) Toledo - 1 update (1 LTE) Tucson / Yuma - 1 update (1 LTE) Upper Central Valley - 67 updates (63 CDMA 800, 4 LTE) Upstate NY Central - 73 updates (73 CDMA 800) Upstate NY East - 105 updates (3 3G, 100 CDMA 800, 2 LTE) Utah - 2 updates (2 LTE) VT / NH / ME - 85 updates (1 3G, 81 CDMA 800, 1 iDEN Conversion, 1 new 3G/800 site, 1 Deactivated) Utah - 2 updates (1 new DAS site) Washington DC - 4 updates (4 CDMA 800) West Iowa / Nebraska - 8 updates (8 CDMA 800) West Texas - 1 update (1 LTE) Winston / Salem - 5 updates (3 CDMA 800, 2 LTE) Maps are updated. Robert Links: Comments regarding this thread, NV Sites Complete Map

It might be. I was recently notified that Sprint was moving forward with upgrading backhaul throughout the Western PA market. Robert

If the B25 neighboring cells was configured properly for B26, it would probably hand you off to B26 when B25 gets too weak. Instead when you start to lose your B25 connection, it runs through neighboring cells and doesn't see a B26 to hand you off to. So it sends you to 3G and then won't even scan B26 again until your LTE rescan timer runs through its cycle. After that is over, you would likely pick up B26 again on its own. But most people just cycle airplane mode to force a scan. When B26 is fully optimized in your area, the neighboring cells will be properly configured. As I understand it, pre-B26 optimization, they just use the same neighboring cells on B26 as they do on B25. But since B26 propagates much better, the B25 neighboring cells needs to have their lists expanded to include many more B26 sectors that they would never have been able to connect to on B25. So it will get better in time. Robert

You cannot directly compare AT&T 700MHz and expect a similar experience when from the same site in every instance. Here's why... Not all bands radiate the same from every device. If you follow S4GRU Device OEM articles, you would know that the ERP for one device is different from band to band. Some devices can be good for one band and bad for another. We have seen lots of devices be good at B25, but not B26 or B41, etc. It's possible that the B17 on AT&T has a better ERP than B26 on Sprint with the GS5. Another thing to consider is there is a small propagation gain between B17 and B26. About 3%. Not huge, but could make a difference in poor signal quality or fringe signals. Additionally, is the B17 by AT&T in your area on 10MHz channels? B26 is on 5MHz channels. Wider channels provide a better signal in edge of cell conditions. And last...your area has not been optimized for B26. The obvious impact is power levels. But the big thing that is hampering your B26 experience is the proper configuration of neighboring cells. It's the reason why you're getting handed off to 3G instead of adjacent B26 sites. Sprint needs to go back and configure their existing B25 network to properly account for every possible B26 neighboring cell you can be handed to. When it doesn't find one of the neighboring cells configured, it drops to 3G. Then it will rescan for LTE in accordance to its rescan schedule. It will get better. Robert via Samsung Note 8.0 using Tapatalk Pro

I'm so done with Samsung. Ironically typed on a Samsung device... Robert via Samsung Note 8.0 using Tapatalk Pro

I'm OK with AT&T buying Tmo, if they divest all their 850MHz assets. They can keep Tmo's Myrtle Beach. Robert via Samsung Note 8.0 using Tapatalk Pro

Recently a source mentioned to me there will be 70 B41 sites live in the Boston area before the end of July. Party time! Robert via Samsung Note 8.0 using Tapatalk Pro

Permits and visibly seeing B41 panels/radios being added to your sites. Robert via Samsung Note 8.0 using Tapatalk Pro

Armor All Robert via Samsung Note 8.0 using Tapatalk Pro