Jump to content

Differences in NV Rollout between Markets


Recommended Posts

This may be a stupid question, but I've noticed that in some markets (like Raleigh/Durham and Charlotte, NC), the NV upgrade sites are almost exclusively 4G only (the map of the cities is a sea of purple). Meanwhile, Chicago is full of green 3G/800/4G and yellow 3G/4G upgrades. Finally, Boston has mostly 3G/4G and some 3G only, with only a single green 3G/800/4G site. Obviously, eventually almost all of these sites will be upgraded to 3G/800/4G, but why are they rolled out in such a radically different order?

 

Chicago's NV vendor is Sammy, but Boston, Charlotte, and Raleigh/Durham are all AlcaLu. What's with the inconsistency of rollout? Thanks.

  • Like 1
Link to comment
Share on other sites

This may be a stupid question, but I've noticed that in some markets (like Raleigh/Durham and Charlotte, NC), the NV upgrade sites are almost exclusively 4G only (the map of the cities is a sea of purple). Meanwhile, Chicago is full of green 3G/800/4G and yellow 3G/4G upgrades. Finally, Boston has mostly 3G/4G and some 3G only, with only a single green 3G/800/4G site. Obviously, eventually almost all of these sites will be upgraded to 3G/800/4G, but why are they rolled out in such a radically different order?

 

Chicago's NV vendor is Sammy, but Boston, Charlotte, and Raleigh/Durham are all AlcaLu. What's with the inconsistency of rollout? Thanks.

 

I'm not 1000% sure, but from what I've read around S4GRU it depends on the Legacy Equipment that was in the area prior to NV. For instance, legacy Motorola equipment causes a delay in 3G because sites must be launched in clusters in those areas to prevent loss of service. The 800 argument is pretty easy. Nextel was on 800, so only areas with minimal Nextel users received 800 prior to the iDEN shutdown. 4G is launched on a site as soon as the site is complete and backhaul is available, 3G won't launch on these 4G towers until 3G can be launched in clusters.

 

Again, my answer isn't 1000% but pretty much sums up a lot of the issues you've mentioned.

  • Like 3
Link to comment
Share on other sites

I'm not 1000% sure, but from what I've read around S4GRU it depends on the Legacy Equipment that was in the area prior to NV. For instance, legacy Motorola equipment causes a delay in 3G because sites must be launched in clusters in those areas to prevent loss of service. The 800 argument is pretty easy. Nextel was on 800, so only areas with minimal Nextel users received 800 prior to the iDEN shutdown. 4G is launched on a site as soon as the site is complete and backhaul is available, 3G won't launch on these 4G towers until 3G can be launched in clusters.

 

Again, my answer isn't 1000% but pretty much sums up a lot of the issues you've mentioned.

Thanks - this makes sense. I checked, and in Charlotte and Raleigh/Durham, where I noticed it was exclusively 4G and no 3G, the Legacy Equipment is, indeed Motorola. Chicago is also Motorola though - perhaps Samsung just has done a better job at rolling out both 3G and 4G? I guess Boston might have a lot of iDen users, which explains the lack of 800. 

Link to comment
Share on other sites

Thanks - this makes sense. I checked, and in Charlotte and Raleigh/Durham, where I noticed it was exclusively 4G and no 3G, the Legacy Equipment is, indeed Motorola. Chicago is also Motorola though - perhaps Samsung just has done a better job at rolling out both 3G and 4G? I guess Boston might have a lot of iDen users, which explains the lack of 800. 

 

We're Motorola ---> Samsung NV here in Columbus. Our one LTE sight launched in late June only has 4G accepted. We used to be Nextel heavy (I sold a $#!+ ton when I used to work there :lol: ) so I definitely expected a 800 delay. Our 3G accepted sites are sporadic right now, but we're slightly expecting a busy month here for 3G. No word if that will include 800.

 

Chicago was kind of a test market for Samsung NV and it was hell on earth during their migration if I understood correctly.

Link to comment
Share on other sites

We're Motorola ---> Samsung NV here in Columbus. Our one LTE sight launched in late June only has 4G accepted. We used to be Nextel heavy (I sold a $#!+ ton when I used to work there :lol: ) so I definitely expected a 800 delay. Our 3G accepted sites are sporadic right now, but we're slightly expecting a busy month here for 3G. No word if that will include 800.

 

Chicago was kind of a test market for Samsung NV and it was hell on earth during their migration if I understood correctly.

Surprisingly, the fact that your first 4G site came online in June means that Samsung seems to be doing really well with their rollout, since Columbus is a fourth round market, meaning a start between June and December. You clearly are at the early end of the spectrum, and, like you said, there seem to be a LOT of sites in progress there.

Link to comment
Share on other sites

Chicago was kind of a test market for Samsung NV and it was hell on earth during their migration if I understood correctly.

 

Hell on earth, eh?  Maybe a big nightmare, too?

 

 

AJ

  • Like 1
Link to comment
Share on other sites

Hell on earth, eh? Maybe a big nightmare, too?

 

AJ

Bwahaha. I like Brian Regan, he's hilarious. Am I correct in most of the information I said? I hate when people provide a completely wrong answer.

Link to comment
Share on other sites

so because no one in Hawaii (Maui) has no nextel phones we should be getting 800Mhz quick right?

 

Hawaii as a whole appears to not be launching anytime soon. Permits are just now being filled for Maui according to the Sponsor side of SGRU.com

 

Below is Robert's post from the Hawaii Network Vision Group.

 

Hawaii is supposed to be one of the last markets. It has been scheduled to start this summer. It appears that permits will start to be issued in the next month or so. Work will get started when that happens. However, the first LTE signals probably will not be live until Fall.

 

Robert from Note 2 using Tapatalk 4 Beta

Link to comment
Share on other sites

Hell on earth, eh?  Maybe a big nightmare, too?

 

AJ

Ha! You have an awesome video come-back for everything!  This one pertained to both telephone service AND hell on earth... (with the added big nightmare of course).

Link to comment
Share on other sites

We're Motorola ---> Samsung NV here in Columbus. Our one LTE sight launched in late June only has 4G accepted. We used to be Nextel heavy (I sold a $#!+ ton when I used to work there :lol: ) so I definitely expected a 800 delay. Our 3G accepted sites are sporadic right now, but we're slightly expecting a busy month here for 3G. No word if that will include 800.

 

Chicago was kind of a test market for Samsung NV and it was hell on earth during their migration if I understood correctly.

 

It is legacy Motorola to NV Samsung that has an incompatibility, causing huge dropped call issues. This is why the Ohio markets are upgrading in clusters, and activating 800 CDMA right away. They are going to attempt to migrate customers over to 800 CDMA first, then activate the PCS CDMA which is where the problems are. This is part of the reason for the large amount of active 800 in Chicago as well. The other reason was the Chicago was very constrained spectrum wise, so they cleared out enough iDen to allow for a channel of 800 CDMA to go live to help with capacity. 

  • Like 2
Link to comment
Share on other sites

It is legacy Motorola to NV Samsung that has an incompatibility, causing huge dropped call issues. This is why the Ohio markets are upgrading in clusters, and activating 800 CDMA right away. They are going to attempt to migrate customers over to 800 CDMA first, then activate the PCS CDMA which is where the problems are. This is part of the reason for the large amount of active 800 in Chicago as well. The other reason was the Chicago was very constrained spectrum wise, so they cleared out enough iDen to allow for a channel of 800 CDMA to go live to help with capacity.

Yeah what he said! Thanks for coming in and cleaning up my holes.

 

Sent from my SPH-L900 using Tapatalk 4 Beta

 

 

Link to comment
Share on other sites

Ha! You have an awesome video come-back for everything!  This one pertained to both telephone service AND hell on earth... (with the added big nightmare of course).

 

I have probably linked that Brian Regan clip more than I have any other.  Mention throwing a "switch," and my autonomic response is you get that video.

 

AJ

Link to comment
Share on other sites

Yeah what he said! Thanks for coming in and cleaning up my holes.

 

Eww!  I hope someone else brought some baby wipes for "cleaning up [your] holes."

 

:P

 

AJ

  • Like 3
Link to comment
Share on other sites

Eww! I hope someone else brought some baby wipes for "cleaning up [your] holes."

 

:P

 

AJ

'Twas thinking it, but didn't say anything...

Hey I wipe my own hole (Target wet wipes to be specific)! I just need coverage for any holes in my information. >_>

 

Sent from my SPH-L900 using Tapatalk 4 Beta

 

 

Link to comment
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

    • Good catch! I meant 115932/119932. Edited my original post I've noticed the same thing lately and have just assumed that they're skipping it now because they're finally able to deploy mmWave small cells.
    • At some point over the weekend, T-Mobile bumped the Omaha metro from 100+40 to 100+90 of n41! That's a pretty large increase from what we had just a few weeks ago when we were sitting at 80+40Mhz. Out of curiosity, tested a site on my way to work and pulled 1.4Gpbs. That's the fastest I've ever gotten on T-Mobile! For those that know Omaha, this was on Dodge street in Midtown so not exactly a quiet area!
    • Did you mean a different site? eNB ID 112039 has been around for years. Streetview even has it with C-band back in 2022 - https://www.google.com/maps/@40.7303042,-73.9610924,3a,24.1y,18.03h,109.66t/data=!3m8!1e1!3m6!1s2ossx06yU56AYOzREdcK-g!2e0!5s20220201T000000!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3D2ossx06yU56AYOzREdcK-g%26cb_client%3Dmaps_sv.share%26w%3D900%26h%3D600%26yaw%3D18.027734930682684%26pitch%3D-19.664180274382204%26thumbfov%3D90!7i16384!8i8192?coh=205410&entry=ttu Meanwhile, Verizon's eNB 84484 in Fort Greene has been updated to include C-band and CBRS, but not mmWave. I've seen this a few times now on updated Verizon sites where it's just the CBRS antenna on its own, not in a shroud and without mmWave. Odd.
    • Drove out into the country today.  Dish stuck to my phone like glue. At least -120 rsrp. Likely only good for phone calls (should have tested.) It then switched to T-Mobile. Getting back on Dish was another issue. I am used to dragging out coverage so I expected a few miles, but had to drive at least 10 miles towards a Dish site. Airplane mode, which worked for Sprint, did nothing. Rebooting did nothing. Finally got it to change over about 2 miles from the site by manually setting the carrier to Dish then it had great reception. Sprint used to have a 15 minute timeout but I did not have the patience today.  Previously I did a speed test on Dish out in the country at the edge of Dish coverage. My speeds were 2g variety. Dish has really overclocked some of these sites. Seen rssp readings in the 50s. Would have called them boomer sites with Sprint but much  more common with Dish.  
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...