RAvirani

Yup, it's been there for a few months. There are a few more by the Microsoft campus in Redmond and quite a few in Tacoma. I also recall seeing 3-4 in downtown Seattle.

Apologies - I misspoke. Interband CA is not officially live in Phoenix yet, although it very well may be in testing. I do not believe it is officially live in those areas yet.

4x4 L2500 at 256 QAM can provide ~280 mbps DL per carrier. Aggregate that with 3x3 L800 and I would be unsurprised by your speeds. Also, interband CA is enabled in Phoenix.

Found a new Verizon site in Seattle that uses JMA antennas. This is the first non-Amphenol site I've seen Verizon build here in at least a year and a half. https://imgur.com/a/HyHl578 Pretty much all other Verizon sites utilize 2x6-port antennas or a single 8 port antenna manufactured by Amphenol. Info on those here: https://s4gru.com/forums/topic/7691-vzw-equipment-spotting/?do=findComment&comment=546650 https://s4gru.com/forums/topic/7691-vzw-equipment-spotting/?do=findComment&comment=546778 I wonder if Verizon will be primarily switching over to JMA here or if this site is a one-off. The currently deployed Amphenol antennas have pretty exceptional lowband range; I'd be surprised if JMA has built antennas that can top them.

Nationwide VoLTE goes live before year end.

It's enabled on iPhones and has been for a while. We have had interband CA for probably a little over two months now in Seattle.

Currently 13. Since I control the code though, I can add more if/when needed.

If anyone manages a spreadsheet for their market and is still looking for/exploring options to display it on a map, PM me. If you can export your database/spreadsheet into a TSV, I've built a tool that produces a map.

Verizon has far less lowband spectrum than either AT&T or T-Mobile. They average 30-40 MHz (B13/B5).

T-Mobile likely wouldn't bid as they have 45-55 MHz of lowband on average (B12/B71). Nor would AT&T with 60-70 MHz of lowband on average (B12/B14/B29/B5). The next lowband auction will be dominated by Verizon, Dish and possibly Sprint if they're still around and have the money.

NSA ULCA can also fix this.

TDD-NR supports flex timeslots which LTE does not. In LTE, timeslots were either DL-only or UL-only, and Sprint allocated a majority of them to DL. NR allows timeslots to be dynamically allocated to DL or UL in real time. If upload is in high demand, the entire airlink can be used for uploading, and vice versa for downloading.

42 MHz could easily be 3 5x5 Blocks with 12 MHz of unpaired spectrum in the middle. This would be almost identical to the lower 700 MHz band plan (B12/B17/B29):

I visited Crystal Mountain and Lake Wenatchee this week, and it looks like the coverage map is wrong. AT&T roaming was available in both areas. That being said, it seems that in-market AT&T roaming has been disabled. I have been unsuccessful in picking up AT&T roaming anywhere in the greater Seattle area where I was previously able to. My phone now holds onto weak B26 or drops to 1x/T-Mobile LTE on rare occasion. I have not connected to EVDO or Verizon 1x in-market at all, either.

40 MHz NR + 3x20 MHz LTE at 4x4 MIMO can provide downlink speeds in excess of 1 Gbps. Backhaul is the bottleneck.

I was under the impression they planned to run 5x5 UMTS/HSPA and 5x5 NR. Whether that meant refarming LTE or refarming UMTS/HSPA depends on what's currently live in each market.

It doesn't have to fit completely into a guard band. Even if CDMA overlaps with the LTE carrier, the LTE carrier an be configured to not assign resource blocks that overlap with the CDMA carrier. For example, if in a market where Sprint owns the C+G block, they could run a 20x20 L1900 carrier spanning 1975-1995/1895-1915. The default LTE guard bands would be 1975-1976/1895-1896 and 1994-1995/1914-1915. If Sprint ran two CDMA carriers that occupied 1975.125-1976.375/1895.125-1896.375 and 1993.625-1994.875/1913.625-1914.875, they could prevent the LTE carrier from assigning resource blocks in the 1976-1976.5/1896-1896.5 and 1993.5-1994/1913.5-1914 range. This leaves a 0.125 MHz guard band on either side of the CDMA carrier. With this design, you have the 94.7% (18/19 MHz available) of the capacity of a 20x20 LTE carrier as well as two CDMA carriers in a single 20x20 block of spectrum.

I'll be testing that next week. I'm going to be in Lake Wenatchee for a bit and Crystal Mountain for a day.

AT&T coverage has vanished on their maps. It was previously displayed.

Both Verizon 1x and AT&T UMTS/HSPA/LTE.

The coverage map was updated again today. It looks like we've lost a huge amount of roaming on the west coast. WA-542, WA-547, WA-530, WA-20, US-2, WA-207, WA-410 and US-97 (between US-2 and I-90) all appear to have no service now. Roaming on the east-west highways surrounding I-5 in Oregon is gone, and roaming in west Oregon and northern California have vanished too. I'm hoping this is an error...if not I will likely be an AT&T customer very soon.

Here is a rough draft small demo map with a few MMIMO sites in the greater Seattle area: https://projects.viranifamily.net/s4gru/mysql-maps/?map=mmimo_western_wa This is what most users will see. I will be making performance enhancements in the coming weeks, although the map seems to perform well with all of the datasets I've tested thus far - up to 9,000 pins. I currently have not had time to make a publicly-available backend for people to fiddle with, but @S4GRU had a chance to take a look at it and can speak to how it works.

Yes - I forgot to mention it has a bulk uploading feature, as well. You can specify whether to replace/update already existing sites or leave them as is (this is because site IDs are unique - they're set up as indexes in the MySQL table). When uploading you can also specify field delimiter, record delimiter, column enclosure and escape characters. You can download data in TSV format (tab-delimited). You can also download a SQL script that will input the data into any other SQL database.

I've went ahead and yesterday built a rough draft of the application I was talking about. It allows you to edit rows (single site records) with a GUI that then updates a map. You can also use SQL to edit records. The program additionally allows you to manage several maps in one place. Using it feels very similar to using fusiontables. I've PMed a link to @S4GRU and am awaiting feedback. I would share a demo here, but the map I'm using for testing has information for ~1000 Sprint sites which I don't think I can post outside the sponsor forum.

Champaign, Illinois, a town of probably about 150,000 people, has 5 M-MIMO sites. We're seeing permits and swap outs for M-MIMO all over the greater Seattle area even though Seattle isn't an official launch market. I'd say Sprint is moving full steam ahead with NR upgrades. As dire as Sprint's accountants are making their situation look, they are more than capable and more than ready to survive sans-merger.