Jump to content

Verizon 5G Coverage


Recommended Posts

Found some more CBRS yesterday afternoon, including 4CA (plus B13 and maybe 2/66)? My my estimation, I was 0.8 mi from the macro broadcasting, with signal in the mid -120s, but ~10 SNR. I don't think B48 contributed much to speeds, but the fact that the noise floor was so low meant that the connection still happened.

So VZW is definitely using GAA here, as they should. Just checked CA combos on my phone and it looks like they could aggregate n77 with a single B48 carrier, plus 2+13, so at the end of this year they could wind up with 25x25 FD + 80 MHz TD on X60-based devices, not far behind T-Mobile's 30x30 (2+66) FD + 80 MHz TD (n41) that they can run now.

Link to post
Share on other sites

One thought I had here is that VZW may lean on CBRS as additional capacity for their home broadband, aggregated with C-Band, particularly in 2022-2023 when they only have 60 MHz of n77 available. Unfortunately, current modems can only aggregate one B48 carrier with n77, but in urban areas VZW has at least 20 MHz of PALs so that kinda works out. If they can get someone to make CPE that aggregates multiple B48 carriers, they'll be even more competitive.

  • Like 1
Link to post
Share on other sites
4 hours ago, iansltx said:

One thought I had here is that VZW may lean on CBRS as additional capacity for their home broadband, aggregated with C-Band, particularly in 2022-2023 when they only have 60 MHz of n77 available. Unfortunately, current modems can only aggregate one B48 carrier with n77, but in urban areas VZW has at least 20 MHz of PALs so that kinda works out. If they can get someone to make CPE that aggregates multiple B48 carriers, they'll be even more competitive.

Seems like CBRS will be to Verizon what LAA is for T-Mobile in some areas. The difference is that LAA range is abysmal. It's usually worse than mmWave. However, thanks to there already being a mature ecosystem of n41 and LAA capable devices, T-Mobile is able to take advantage of all of the spectrum they have deployed here. In NYC we have seen T-Mobile aggregate 60MHz n41 + 20MHz Band 66 + 20MHz Band 2 + (20MHz x 3) Band 46.

  • Like 1
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • I may have missed it, but what are the the benefits of moving over to TNX on a 5G device that would automatically have TNA (prefer the T-Mobile network). It doesn't seem like it would change the network experience all that much. My devices are all TNA, and on the T-Mobile network all the time except while near Sprint Keep sites. I'd prefer to keep the easy access to Sprint sites since Sprint have a bigger network than T-Mobile here.
    • Has anyone on eSIM switched to T-Mobile eSIM?
    • Unfortunately, I'm seeing the gaps in the customer experience for TNX and I'm wondering if I should just leave the "T-Mobile Unlimited Freedom Plan with Included Taxes/Fees" behind and bring everything over to a T-Mobile Plan/Account at a certain point for usability and management sake. iOS: The experience on iOS has been fine. When I upgraded my 3 iPhone 12 Pro's it was easy to update the E911 Address for Wi-Fi Calling right on the device. Quick and done. Google Pixel 5: The experience on a Google Pixel 5 on eSIM for Sprint was mediocre. I received conflicting information about whether the device was eligible for TNX. Chat said yes, so I ordered a SIM and installed it. The device threw an error and said to take it out. Chat then said that device wasn't eligible for TNX. Is this in fact the case? Has anyone here put a Google Pixel 5 on TNX? Samsung: The experience for two Samsung Galaxies on our account was actually terrible. For the S20+ 5G: I put in the TNX SIM and after I enabled Wi-Fi Calling, I wanted to update the E911 address on the device. Nope, the address update button in the device menu took me to the T-Mobile Login Screen. I contacted chat and they said I had to do it on the Sprint website. Ok, so I went to the Sprint Website and to Account Dashboard. I selected "Options" for the device, and selected the Update E911 Address link. I then got taken to an absolutely ancient portion of the Sprint website that hadn't been part of the recent redesign and I was able to update the address.... but the interface looked terrible and like it wouldn't actually work. I still can't update the E911 address on the device itself. Ridiculous. For the S21 5G, which was a device upgrade on that line from an absolutely ancient BlackBerry KEYone (Don't ask. They held on forever hoping keyboards would come back): After activating the device with the T-Mobile SIM Card that came with it, I went to activate Wi-Fi Calling on the device. I then went to update the E911 address on the device and the button took me to the same T-Mobile Login page as it did on the S20+. So I went to my Account Dashboard and it showed the S21 on the line and that it was on the T-Mobile network. It showed that Wi-Fi Calling was enabled under account services. I then went to Manage Device -> Options -> Update E911 Address for WiFi Calling, and the ancient content page loaded.... and it still showed the old device on the account. I contacted Customer Care via Chat and they removed the old device from the account and it then showed the S21 on the page. I then tried entering the address for WiFi Calling and it wouldn't accept it. When I hit "save" it threw an error for the address, which makes no sense since this was the valid shipping address for the device via UPS. So I put in a ticket with the Advanced Tech Support to have the Network Team go and manually try to enter the address on the backend or figure out what's going on here. C'mon T-Mobile..... TNX is good. The customer experience for account services management you're having Sprint run on the Sprint website actually stinks, and we're starting to see the cracks where Sprint's legacy content that was never updated (and probably never will be) or that customers get misinformation about device eligibility for TNX (Google Pixel 5) can negatively affect the TNX customer experience. In my case, I'm having a miserable time trying to update the E911 Addresses for Wi-Fi Calling on my Samsung devices and its because TNX broke Sprint's E911 Address management on Android devices. iOS devices however seem to work fine for these updates to be made on the device. Not sure why that is. Interested in what people think.
    • This one I found particularly interesting. They filed to upgrade the T-Mobile (orange) to n71 and n41 a while back. Then this week, they filed to keep the two surrounding Sprint sites (blue). The T-Mobile one is very tall with a huge footprint, so I understand why they might want to use the Sprint sites, but just very interesting they filed to upgrade it and then decided against it (as best I can tell).
    • Oftentimes they're locked into contracts with their contractors, otherwise they would just cancel the T-Mobile site's upgrade. 
  • Recently Browsing

    No registered users viewing this page.

×
×
  • Create New...