Jump to content

Will NV upgraded sites reduce/eliminate NID border missed call issue?

larryt510

By larryt510
in General Topics

 Share

Recommended Posts

larryt510 Member Level: 3G EVDO

larryt510

Posted
Posted

I've been wondering if the new network vision equipment will finally solve the old problem of missed incoming calls while moving between two or more cell sites that are located on different network switches (NID's). When I say a 'missed incoming call' I am referring to incoming calls that never make it to the phone and instead get dumped to voicemail. Calls that get lost in the network paging channel before the phone can see the call.

 

This has been a problem here for as long as I can remember dating back to 1997 when I first signed up with Sprint. I spend a significant amount of my time while connected and bouncing back and forth between one cell site located on Irvine switch #1 and Irvine switch #2 here in Orange County, CA. Oddly Verizon has/had the exact same NID border location as Sprint here. No idea if that was just a coincidence or not.

 

The issue has already improved a lot since about 2009. Instead of missing 2-3 calls per day it only seems to happen about once every other day now. Not sure if today's modern phones are better at finding incoming calls or some sort of software patch was made on the network side by the vendors that helped.

 

Have any of the resident technology experts here heard anything about this? I know it's not a commonly known about or discussed problem but thought I would ask anyway.

Link to comment
Share on other sites
WiWavelength Member Level: LTE Advanced

WiWavelength

Posted
Posted

Likely, no, Network Vision will not provide any service improvement along NID boundaries, as Network Vision does not change the geography of NIDs and MSCs.

 

About the only improvement you can hope for is that the enhanced signal strength from a CDMA1X 800 site/sector on one side of the NID boundary is sufficient to overcome pilot pollution from other sites/sectors on the other side of the NID boundary. That could be enough to keep your handset registered with one NID, rather than bouncing between two of them.

 

AJ

Link to comment
Share on other sites
larryt510 Member Level: 3G EVDO

larryt510

Posted
  • Author
Posted

Yeah that's what I suspected but was hoping that maybe the new equipment would have software patches that addressed the missed call/NID boundary issue. You would think by now that they would have been able to come up with a fix after 15+ years.

Link to comment
Share on other sites
WiWavelength Member Level: LTE Advanced

WiWavelength

Posted
Posted

Yeah that's what I suspected but was hoping that maybe the new equipment would have software patches that addressed the missed call/NID boundary issue. You would think by now that they would have been able to come up with a fix after 15+ years.

 

Software on the network side will not fix anything. Idle handsets are not under network control. And the handsets are operating exactly as designed. In deploying a cellular network across hundreds of thousands of square miles, the SID/NID boundary issue is just the nature of the beast.

 

AJ

Link to comment
Share on other sites
larryt510 Member Level: 3G EVDO

larryt510

Posted
  • Author
Posted

Well I'm pretty sure that something changed to improve this over the past 4-5 years. Maybe an improvement with the handsets? Because it's a lot better now than it used to be and nothing else has changed with the cell sites around here that I know about.

Link to comment
Share on other sites
WiWavelength Member Level: LTE Advanced

WiWavelength

Posted
Posted

Well I'm pretty sure that something changed to improve this over the past 4-5 years. Maybe an improvement with the handsets? Because it's a lot better now than it used to be and nothing else has changed with the cell sites around here that I know about.

 

CDMA2000 devices use a quick paging channel that is about 20 times faster than the previous cdmaOne paging channel. So, likely, devices can switch between NIDs/MSCs and register more quickly.

 

AJ

  • 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.

×
 Share
Go to topic listing

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • T-MoblieUser207
      Network Vision/LTE - New York City Market

      By T-MoblieUser207 · Posted

      The DAS at LGA Terminal B actually has n41 at 100+20, but if you are deprioritized, good luck on the busy days, as all the bands are congested, even B41 and n41, with data being worse than 128kbps international roaming. It has SA active for n41 as well. The L train tunnel is actually 80+20 for n41, with SA n41 active. Speeds aren't anything compared to Philadelphia's DAS system that has n41 though. The gig+ upgrades are expanding, as eNBs 894588 (Sprint convert site) and 55987 can both pass 1 Gbps now. Clocked nearly 1.3Gbps on eNB 55987 today.
    • Rickie546
      Official Tmobile-Sprint merger discussion thread

      By Rickie546 · Posted

      Hopefully this goes thru!  https://www.reddit.com/r/tmobile/comments/1211mh7/tmobile_files_another_sta_application_to/
    • Paynefanbro
      Network Vision/LTE - New York City Market

      By Paynefanbro · Posted

      Yup 80MHz C-band + 40MHz DoD for a total of 120MHz. They should be pretty well setup post-clearance. — — — — — Famous Verizon site on Atlantic referenced in this reddit post got moved to the top of the building next door. — — — — — Also looks like I mapped a T-Mobile oDAS node eNB 347812 in Brooklyn Heights. Streetview shows it as one of the CC nodes with no antenna on top as of May 2022 but this specific eNB was first mapped this month. I didn't notice that I mapped it until I got home but the range on it is significantly greater than the normal "antenna-less" nodes T-Mobile deploys. I'm wondering if it got upgraded to the new 5G oDAS design but I won't be able to check it out until next weekend.  
    • transitwatch889
      Network Vision/LTE - New York City Market

      By transitwatch889 · Posted

      I didn't know they had access to 80 MHz of c-band that does change some things then once that's online
    • Trip
      SignalCheck Beta Crew Forum

      By Trip · Posted

      While I've been loath to update my Samsung devices past the May 2022 update to keep the Band Selection tool, I note that it looks like Android 14 is going to add Timing Advance for NR to the API.  (Was looking today as I have another Verizon A42 5G now that I'm going to unlock for T-Mobile, and wanted to figure out if I should let it update or not.)  Since I can technically make band changes from *#73#, on the A42 5Gs, I can probably live without the Band Selection tool if a later Android version adds something useful like TA values. I assume SCP will be updated to support that once it becomes publicly available.  The real question is whether or not the phones will support it.  My S21FE and A42 5G devices do on LTE, but I know the S22 and the A32 5G do not support it even on LTE, providing just zero in that field. - Trip

  • Recently Browsing

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