Jump to content

NID Boundary changes in Orange County, CA!!

larryt510
 Share

Recommended Posts

larryt510 Member Level: 3G EVDO

larryt510

Posted
  • Author
Posted

Just got an LG G3 and now I notice in debug mode I'm switching back and forth between band class 1 and band class 3.  Also switching back and forth between NID 3 and NID 19 (This entire area is definitely NID 3 so not sure how this 19 factors in).  What's the deal with this?  It's not causing missed incoming call thankfully.

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

WiWavelength

Posted
Posted

Just got an LG G3 and now I notice in debug mode I'm switching back and forth between band class 1 and band class 3.  Also switching back and forth between NID 3 and NID 19 (This entire area is definitely NID 3 so not sure how this 19 factors in).  What's the deal with this?  It's not causing missed incoming call thankfully.

 

If you are idling on LTE, any CDMA2000 engineering screen readouts are spurious, since the LG G3 is a single RF path handset.  Regardless, band class 3 is not correct, as that is the JTACS band, which is not in use in North America.

 

AJ

Link to comment
Share on other sites
  • 3 weeks later...
mikejeep Member Level: LTE Advanced

mikejeep

Posted
Posted

But I don't get why it is showing my phone as being on SID 19 and  NID 33.  We are clearly SID 4145 and NID 3.

 

By any chance did you try checking what a third-party app like SignalCheck or LTE Discovery was reporting for a SID/NID? Some engineering screens are far less reliable than you might expect. Sometimes invalid data is displayed when the device is scanning for additional channels or connected to a separate technology.

 

While nothing is perfect, I have never seen any third-party apps show incorrect SID/NID information. The Android routines behind them must be more reliable than the methods used by some of the OEM engineering screens.

 

-Mike

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

larryt510

Posted
  • Author
Posted

Yes this NID boundary was set up back in the 1990's when Sprint first entered the market here.  It was the absolute worst place they could have picked to divide up the NID split.   12 months ago (last September) they finally merged the two NID's into one but the incoming call failure was still happening even worse than it had been before the NID merge.  I kept putting pressure on them with repeated tickets on it and was in contact with one of the top RF engineers in So. Cal.  Finally one day I woke up in early June and it was fixed.  I also breathed a sigh of relief last week when they converted my local cell site over to 3G NV and nothing got messed up in the process. lol

Link to comment
Share on other sites
  • 1 month later...
NGeorge Member Level: 1x Advanced

NGeorge

Posted
Posted

Sprint finally fixed a major SID boundary issue that's plagued me since I've owned a cell phone (1998) -- the line between the Seattle and a Portland markets, which they had also set on a CMA license boundary... Back when I had US West/Qwest Wireless, it was where they changed from the A block in Seattle to the E block for Portland -- and the call would drop. Then I got Sprint, and although they have the B block on both sides, the call would drop because of the SID change. Verizon inherited the licenses from Qwest so they could offer native service when Sprint bought the rest in 2004, and sure enough -- when Verizon flips from A-E, the call drops as well -- almost at the exact point just north of the Toutle river bridge, just before you get to the overpass (if your heading North)...

 

So imagine my surprise when I drove though there and it didn't drop... same thing happened again on the way back... I actually held a call for almost a half hour. So they've either moved the boundary from right across the freeway, or they've figure out how to get the call to stay even while changing SIDs. This all happened once NV was cut over -- so that was an extra little benefit :)

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

WiWavelength

Posted
Posted

Sprint finally fixed a major SID boundary issue that's plagued me since I've owned a cell phone (1998) -- the line between the Seattle and a Portland markets, which they had also set on a CMA license boundary...

 

So imagine my surprise when I drove though there and it didn't drop... same thing happened again on the way back... I actually held a call for almost a half hour. So they've either moved the boundary from right across the freeway, or they've figure out how to get the call to stay even while changing SIDs. This all happened once NV was cut over -- so that was an extra little benefit :)

 

Both Seattle and Portland were Lucent legacy infrastructure markets, but was there ever any affiliate market territory along I-5 between the two?  If so, that could have been Motorola or Nortel legacy infrastructure, hence the lack of interconnection.

 

Even if there was no affiliate infrastructure issue, I seem to recall a Lucent limitation from 10-15 ago.  If I remember it correctly, Lucent, unlike Nortel, could not hand off between two MSCs in different markets.

 

Regardless, both Seattle and Portland are now Samsung infrastructure markets, and the sites in the affected SID boundary area have all received at least their 3G upgrades.

 

AJ

Link to comment
Share on other sites
NGeorge Member Level: 1x Advanced

NGeorge

Posted
Posted

Both Seattle and Portland were Lucent legacy infrastructure markets, but was there ever any affiliate market territory along I-5 between the two?  If so, that could have been Motorola or Nortel legacy infrastructure, hence the lack of interconnection.

 

Even if there was no affiliate infrastructure issue, I seem to recall a Lucent limitation from 10-15 ago.  If I remember it correctly, Lucent, unlike Nortel, could not hand off between two MSCs in different markets.

 

Regardless, both Seattle and Portland are now Samsung infrastructure markets, and the sites in the affected SID boundary area have all received at least their 3G upgrades.

 

AJ

 

No, Ubiquitel was the only affiliate in Washington and they were over on the Spokane side -- not sure what equipment they used. It actually was a corporate market, then Ubiquitel took it over in 2000.

 

Probably that Lucent limitation you mentioned because it ALWAYS happened in that area like clockwork. I know that Qwest back in the day was all Ericsson from back when they experimented with CDMA on their own the first time -- I vaguely remember all sorts of complaints about the gear--that it was very compact and that was about all that was good about it. Sprint did a complete rip and replace when they added those sites into it's network, but Qwest dropped in this same spot... not sure who Verizon uses, but they have the issue too; they took over Qwest's licenses while Sprint got the towers so they could have an unbroken network between Seattle and Portland, so Verizon has to deal with an A-E switch there as well... The GSM carriers don't have an issue.

 

Nat

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

WiWavelength

Posted
Posted

No, Ubiquitel was the only affiliate in Washington and they were over on the Spokane side -- not sure what equipment they used. It actually was a corporate market, then Ubiquitel took it over in 2000.

 

Are you certain that you are not forgetting Alamosa PCS nee Washington Oregon Wireless?

 

AJ

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

    • 4GHoward
      Official Tmobile-Sprint merger discussion thread

      By 4GHoward · Posted

      This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • dkyeager
      Official Tmobile-Sprint merger discussion thread

      By dkyeager · Posted

      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.  
    • Yuhfhrh
      Dish Network/Boost Mobile cell/5G buildout thread

      By Yuhfhrh · Posted

      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.
    • dkyeager
      Official Tmobile-Sprint merger discussion thread

      By dkyeager · Posted

      "The company’s unique multi-layer approach to 5G, with dedicated standalone 5G deployed nationwide across 600MHz, 1.9GHz, and 2.5GHz delivers customers a consistently strong experience, with 85% of 5G traffic on sites with all three spectrum bands deployed." Meanwhile they are very close to a construction deadline June 1 for 850Mhz of mmWave in most of Ohio covering 27500-28350Mhz expiring 6/8/2028. No reported sightings.  Buildout notice issue sent by FCC in March 5, 2024 https://wireless2.fcc.gov/UlsApp/letterPdf/LetterPdfController?licId=4019733&letterVersionId=178&autoLetterId=13060705&letterCode=CR&radioServiceCode=UU&op=LetterPdf&licSide=Y&archive=null&letterTo=L  No soecific permits seen in a quick check of Columbus. They also have an additional 200Mhz covering at 24350-25450 Mhz and 24950-25050Mhz with no buildout date expiring 12/11/2029.
    • Paynefanbro
      Official Tmobile-Sprint merger discussion thread

      By Paynefanbro · Posted

      T-Mobile Delivers Industry-Leading Customer, Service Revenue and Profitability Growth in Q1 2024, and Raises 2024 Guidance https://www.t-mobile.com/news/business/t-mobile-q1-2024-earnings — — — — — I find it funny that when they talk about their spectrum layers they're saying n71, n25, and n41. They're completely avoiding talking about mmWave.

  • Recently Browsing

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