Jump to content

Sprint improves coverage in Eastern MI


legion125

Recommended Posts

Although post on the wall about Grand Rapids & western MI being slated for NV for the second round, it looks like Sprint has made some 3G improvements for the Detroit area. There were a lot of complaints coming from the metro area about poor service. Now it looks like things will be improving on the 3G side. Anybody see a difference?

 

http://newsroom.sprint.com/article_display.cfm?article_id=2202

  • Like 1
Link to comment
Share on other sites

Surprising they are still having these releases done...

 

How much trouble would it be to just add the microwave/fiber backhaul to these towers getting bandaid bundled T1 patches instead of the T1 lines? I mean for the T1 lines in many cases they have to be new lines run anyway so to my outside perspective it makes more sense to just to the full NV backhaul portion of the upgrade instead of this $ on patches...

That is if the new microwave/fiber backhaul is compatible with current deployed cabinets and switches. It if wouldn't be pnp like the T1 and would req new switches and such then i kinda understand why this is the way they choose...

 

Sent from my PG86100 using Tapatalk

Link to comment
Share on other sites

Surprising they are still having these releases done...

 

How much trouble would it be to just add the microwave/fiber backhaul to these towers getting bandaid bundled T1 patches instead of the T1 lines? I mean for the T1 lines in many cases they have to be new lines run anyway so to my outside perspective it makes more sense to just to the full NV backhaul portion of the upgrade instead of this $ on patches...

That is if the new microwave/fiber backhaul is compatible with current deployed cabinets and switches. It if wouldn't be pnp like the T1 and would req new switches and such then i kinda understand why this is the way they choose...

 

Sent from my PG86100 using Tapatalk

 

I've been questioning this same thought for a while now.

 

Link to comment
Share on other sites

I'm not 100% clear on the compatibility of legacy gear with new enhanced backhaul solutions. I have to think its possible. We have a couple fiber and MW backhaul locations here in NM (but not many). In most cases they are co-located sites developed by a private property owner that developed their own site and provided shared backhaul for all users. That occurs at the Santa Fe Opera and a large Mega Church in Albuquerque.

 

As for why these band aids are occurring nonsensically, its because of the iPhone.. for the most part. When Sprint worked out the contract for the iPhone in Summer 2011, they knew there was going to be a huge hole between iPhone deployment and Network Vision deployment.

 

The iPhone is a 15.5 Billion investment for Sprint. So spending another 1 Billion on temporary capex doesn't seem too excessive in that light. They really felt like spending this money would enhance the experience of iPhone users.

 

Sprint immediately jumped into action with the additional carriers and additional T1 backhaul last Summer. However, getting T1's all across the country takes a lot of time. Ironically, ATT T1's were largely coming in first. CenturyLink T1 orders have really taken a long time. And 60%+ of the T1's ordered were through CL.

 

So Sprint have loved for these to be coming online back in October/November time frame. But the delays are more about the last minute nature of the iPhone deal causing a sudden reactionary capex spending, and the delays that have ensued with that.

 

However, they could have deployed MW almost in the time it has taken to get a lot of these T1's!! So my explanation is not a defense, just an explanation of how they got there.

 

Robert

 

Posted via Forum Runner

  • Like 1
Link to comment
Share on other sites

Yeah agreed and understand. I just would of thought that after a delay of X time they would of made the decision to just do microwave or really since they knew NV was going on this year they'd go ahead and just do new backhaul in the bandwidth locations since NV was going to get there anyway at some point...

 

Really I can only guess that it'd require more hardware change out in the cabinets they didn't want to spend time doing? Just a thought...

 

Sent from my PG86100 using Tapatalk

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

    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
  • Recently Browsing

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