Jump to content

Band-Aid fixes vs Network Vision?


Recommended Posts

I thought I read that network vision replaces all the legacy equipment with new NV equipment. If Sprint has these towers upgraded for voice/capacity 1-3 months from now does all that equipment just get replaced when they do Network Vision for those towers? What is actually changed/added when they do "band-aid" fixes and how much of that stuff is carried over to network vision upgrades?

 

On https://network.sprint.com/ for places like Chicago it still shows upgrades over the next 6 months. According to this site the Chicago area is set to launch in September and to be completed by December. Seems odd that site would still show band-aid fixes right up until completion of the market. Any reasoning or logic behind that?

Link to comment
Share on other sites

I thought I read that network vision replaces all the legacy equipment with new NV equipment. If Sprint has these towers upgraded for voice/capacity 1-3 months from now does all that equipment just get replaced when they do Network Vision for those towers? What is actually changed/added when they do "band-aid" fixes and how much of that stuff is carried over to network vision upgrades?

 

On https://network.sprint.com/ for places like Chicago it still shows upgrades over the next 6 months. According to this site the Chicago area is set to launch in September and to be completed by December. Seems odd that site would still show band-aid fixes right up until completion of the market. Any reasoning or logic behind that?

 

There are three types of upgrades being tracked at network.sprint.com. Voice carrier adds, EVDO carrier adds and data speed upgrades (which are mostly additional T1 lines).

 

In the case of Chicago, they cannot carry over any legacy equipment into Network Vision cabinets because the legacy equipment is Motorola and the NV equipment is Samsung. So presumably, all these temp upgrades at a legacy site will be removed and probably installed in other Sprint markets that are awaiting Network Vision and/or sold to other vendors around the world. Except T1 lines, which will be just be disconnected.

 

However, it is likely that network.sprint.com will also track upgrades in post Network Vision sites too. Although the number of NV sites needing this kind of work should be substantially lower, there will always be need for additional voice and 3G carriers as demand grows in certain cells. This will always be an ongoing network management issue over time. Hopefully Sprint can move to a proactive role in a Post Network Vision World, a far cry from the previous reactive mode it has been in.

 

And even though it may seem stupid, or a waste, to do this work right before NV...you have to understand the relationship between Sprint and Ericsson. A few years ago, Sprint contracted out management of its entire network nationwide to Ericsson. Ericsson has in their contract to perform these upgrades as necessary. So these upgrades are being performed by Ericsson. And Sprint essentially paid for these in advance by the nature of their contract. So Ericsson should be doing these upgrades, even if they will only be used for a few months. Sprint paid for them already.

 

Robert via Kindle Fire using Forum Runner

  • Like 4
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

    • It’s a neat and seemingly valid / effective strategy that, at least from my understanding, is only really used by VZW
    • Those are usually left over from the initial AWS deployment, so all run B13/B66 with support for BC0/BC1 (although that’s been shut off on most sites). No NR. Sites with the later Ericsson radios got an OTA update and broadcast B2. On those sites, a B5 OTA update was also available (and tested), but ultimately rolled back. Putting up all that power/spectrum severely degraded the B13 output.  The site atop Crystal Mountain is another story and uses the same setup as the site on the ridge near Neilton. These antennas were selected for their vertical beamwidth. Most modern directional antennas have small vertical beamwidths and would require extreme downtilt to cover the road next to a steep ridge. Thus, they would have a severely limited coverage footprint beyond the road. Omnis can be a better choice in these instances, especially when there’s LoS to the coverage objective (since they’ll generally have lower gain figures). Omnis also don’t run in to the horizontal sector edge problem, which can be difficult to optimize for with directional antennas that have complex or irregular 3D gain profiles. That’s why on a lot of sites on mountains, you’ll see wider antennas used. For example, the Verizon site on Joyce Ridge has three sectors with 80-degree HBW antennas. 
    • Do you know what RAN is behind those Omni's? LTE (bands?) are they pushing any NR through them? Very curious   edit: I guess I could check cellmapper etc but you might know more nuance!
    • N41 here has been expanded from 140Mhz to 180Mhz.  Speeds seem the same so they just need to work on backhaul
    • I noticed today that T-mobile has shut of B41 LTE in the Louisville area and widened the 2nd n41 carrier to 80MHz. That just leaves them with 5x5 B12, 10x10 B2, and two 10x10 B66 carriers on LTE, everything else is in NR (besides their 2G network). They have 20x20 n71, 20x20 n25, 5x5 n25, and 180MHz n41. 
  • Recently Browsing

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