Jump to content

Kansas market NID/MSC change (was "MSC Boundary Change")

sporter82
 Share

Recommended Posts

sporter82 Member Level: Morse Code

sporter82

Posted
Posted

I am a big debug screen geek and I have noticed here lately that my NID has changed to a new number(308). Typically my home is in the NID 43 area and on my drive to work it changes to 42. In the last week both home and work now fall under the 308 NID. So my question is; does anyone know if something has changed in regards to Sprints MSC layout?

 

Thank You

Link to comment
Share on other sites
Mobilesolutions Member Level: 4G WiMax

Mobilesolutions

Posted
Posted

I am a big debug screen geek and I have noticed here lately that my NID has changed to a new number(308). Typically my home is in the NID 43 area and on my drive to work it changes to 42. In the last week both home and work now fall under the 308 NID. So my question is; does anyone know if something has changed in regards to Sprints MSC layout?

 

Thank You

 

How interesting that this is first noticed in Master AJ-WWAN's home market  ;)

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

WiWavelength

Posted
Posted

I have not noticed any NID changes in my neck of the woods.  And our site info, as I recall, does not indicate any MSC assignment changes in the Kansas market.

 

Have you checked to see if NID 308 is on CDMA1X 800?

 

AJ

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

WiWavelength

Posted
Posted

Maybe NV is finally combining some of the former affiliate purchases with old corp networks into a single MSC.

 

That was done years ago in the Kansas market.  The Alamosa NIDs are long gone.

 

AJ

  • Like 1
Link to comment
Share on other sites
superbluepsd Member Level: 1x Advanced

superbluepsd

Posted
Posted

I still show CDMA PCS and the SID is still 4139. What is interesting is all of the BSID's that I am accustomed to seeing have all changed to a consistent 5 digit primarily starting with 52xxx.

What band class is listed on the debug screen?  Band 1 is 1900 and 10 is 800SMR

Link to comment
Share on other sites
sporter82 Member Level: Morse Code

sporter82

Posted
  • Author
Posted

The EVO LTE only shows Band# as "CDMA PCS" or "CDMA Cellular". I know its not 800SMR because the SID is still 4139 and it says CDMA PCS. I did some driving around and found that this 308 NID goes from at least Excelsior Springs to 119th and Renner in Olathe. That would typically be NID 42 in Olathe and NID 43 in Excelsior Springs.

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

tongboy

Posted
Posted

BSID and NID will change when the 1x portion of the tower your connecting to gets a network vision upgrade. Are you in an area they are upgrading?

 

Sent from my EVO LTE

 

 

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

tongboy

Posted
Posted

They all changed in Chicago when the 1x and EVDO work was done on a tower. I'm not sure if they are changing in other areas.

 

Sent from my EVO LTE

 

 

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

WiWavelength

Posted
Posted

Nothing has changed in Lawrence, still NID 43.  But I will be in Leawood and at UMKC today, so I will watch NIDs more closely than I have in several years.

 

Between Lawrence and KC, the NID 43/41 boundary is De Soto.  Then, in the city, the NID 41/42 boundary is around 75th St.  Other than the NID 43/41 transition along K-10 shifting one site west, those boundaries have remained static for many years, and I started tracking them over 10 years ago.

 

Also, FYI, NID 41 has been Lenexa-MSC_1.  NID 42 has been Lenexa-MSC_2.  And NID 43 has been Independence-MSC_1.  With potentially greater capacity new Ericsson MSCs and declining voice traffic, perhaps we will see a consolidation down to only one or two MSCs in the Kansas market.

 

AJ

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

WiWavelength

Posted
Posted

AJ-

       Were you able to see anything different when you were downtown yesterday?

 

NID 308 seems to have consolidated both NID 41 and NID 42.

 

Along I-70, the NID 43/42 boundary near Bonner Springs is now the NID 43/308 boundary.  And along K-10, the NID 43/41 boundary near De Soto is also now the NID 43/308 boundary.  So, those boundaries have not changed, but the eastern side NIDs have switched over to NID 308.

 

Otherwise, downtown, The Plaza, Leawood, and Lenexa -- seemingly, the entire core metro area -- is now on NID 308.  The previous NID 41/42 boundary approximately at 75th St is no longer.

 

This could be good news for people who live or work near NID boundaries that cause them to miss incoming calls and burn battery life due to incessant registrations between two NIDs.  If Kansas City is any indication, many of those boundaries may be going away.

 

AJ

  • Like 2
Link to comment
Share on other sites
halcyoncmdr Member Level: eHRPD

halcyoncmdr

Posted
Posted

They all changed in Chicago when the 1x and EVDO work was done on a tower. I'm not sure if they are changing in other areas.

 

Sent from my EVO LTE

 

As we all know... Chicago has been a unique case compared to just about everywhere else in the country. Legacy and Network Vision boundaries have caused all sorts of issues that were unexpected.

Link to comment
Share on other sites
sporter82 Member Level: Morse Code

sporter82

Posted
  • Author
Posted

NID 308 seems to have consolidated both NID 41 and NID 42.

 

Along I-70, the NID 43/42 boundary near Bonner Springs is now the NID 43/308 boundary.  And along K-10, the NID 43/41 boundary near De Soto is also now the NID 43/308 boundary.  So, those boundaries have not changed, but the eastern side NIDs have switched over to NID 308.

 

Otherwise, downtown, The Plaza, Leawood, and Lenexa -- seemingly, the entire core metro area -- is now on NID 308.  The previous NID 41/42 boundary approximately at 75th St is no longer.

 

This could be good news for people who live or work near NID boundaries that cause them to miss incoming calls and burn battery life due to incessant registrations between two NIDs.  If Kansas City is any indication, many of those boundaries may be going away.

 

AJ

That's good to hear. Thanks for the information.

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

WiWavelength

Posted
Posted

NID 308 is spreading like wildfire.  Along K-10, the former NID 43/41 transition has leaped an additional two sites west -- from De Soto/Kill Creek past De Soto/Sunflower to Eudora.  So, the NID 43/308 effective boundary is now in the Wakarusa River floodplain just east of Lawrence.  We will have to wait and see if that is where it remains or if Lawrence is also assimilated.

 

I-70 has experienced a similar shift.  NID 308 has expanded from the Bonner Springs/K-7 site to include at least the Reno site.  I was not looking for any further NID 308 expansion, so I did not notice the change until I was right underneath the Reno site.  Thus, I missed the Lawrence Service Area site.  I will do a bit of drive testing today or tomorrow to clear up that discrepancy.

 

AJ

  • Like 4
Link to comment
Share on other sites
Rickie546 Member Level: 4G WiMax

Rickie546

Posted
Posted

Well

 

NID 308 is spreading like wildfire.  Along K-10, the former NID 43/41 transition has leaped an additional two sites west -- from De Soto/Kill Creek past De Soto/Sunflower to Eudora.  So, the NID 43/308 effective boundary is now in the Wakarusa River floodplain just east of Lawrence.  We will have to wait and see if that is where it remains or if Lawrence is also assimilated.

 

I-70 has experienced a similar shift.  NID 308 has expanded from the Bonner Springs/K-7 site to include at least the Reno site.  I was not looking for any further NID 308 expansion, so I did not notice the change until I was right underneath the Reno site.  Thus, I missed the Lawrence Service Area site.  I will do a bit of drive testing today or tomorrow to clear up that discrepancy.

 

AJ

Well here's some more news on this for you, now my site in Gravois Mills, MO right on the lake is NID 308 from 41 and this is one of the few fully installed sites here in the ozarks. going to see what the rest have on my drive to work.

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

WiWavelength

Posted
Posted

I just returned from my drive testing. Both Lawrence Service Area and Tonganoxie sites are still NID 43.

 

AJ

  • Like 1
Link to comment
Share on other sites
sporter82 Member Level: Morse Code

sporter82

Posted
  • Author
Posted

Well

 

Well here's some more news on this for you, now my site in Gravois Mills, MO right on the lake is NID 308 from 41 and this is one of the few fully installed sites here in the ozarks. going to see what the rest have on my drive to work.

The family and I went to the Shatto dairy farm tour yesterday in Osborn Mo and I noticed Osborn and Cameron Mo had NID 308 as well.

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

WiWavelength

Posted
Posted

The family and I went to the Shatto dairy farm tour yesterday in Osborn Mo and I noticed Osborn and Cameron Mo had NID 308 as well.

 

Now, that is one honestly named dairy farm.  The cows were milked.  They ate.  And, of course, they shat.

 

:P

 

AJ

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

WiWavelength

Posted
Posted

And, overnight, Lawrence has been absorbed into NID 308, too.  We are now one with the Borg.

 

AJ

  • Like 2
Link to comment
Share on other sites
MacinJosh Member Level: LTE Advanced

MacinJosh

Posted
Posted

And, overnight, Lawrence has been absorbed into NID 308, too. We are now one with the Borg.

 

AJ

 

I wonder if they are going to do this all over the country in the end.

 

 

Sent from Josh's iPhone 5 using Tapatalk 2

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

WiWavelength

Posted
Posted

I wonder if they are going to do this all over the country in the end.

 

Indeed, Josh, that is the widespread relevance of this thread.

 

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

    • Trip
      T-Mobile to acquire UScellular

      By Trip · Posted

      On Reddit, someone asked (skeptically) if the US Cellular buyout would result in better service.  I'd been pondering this very issue, and decided to cross-post my response here: I've been pondering the question in the title and I've come to the conclusion that the answer is that it's possible. Hear me out. Unlike some of the small carriers that work exclusively with one larger carrier, all three major carriers roam on US Cellular today in at least some areas, so far as I know. If that network ceases to exist, then the carriers would presumably want to recover those areas of lost service by building out natively. Thus, people in those areas who may only have service from US Cellular or from US Cellular and one other may gain competition from other carriers backfilling that loss. How likely is it? I'm not sure. But it's definitely feasible. Most notably, AT&T did their big roaming deal with US Cellular in support of FirstNet in places where they lacked native coverage. They can't just lose a huge chunk of coverage whole still making FirstNet happy; I suspect they'll have to build out and recover at least some of that area, if not most of it. So it'd be indirect, but I could imagine it. - Trip
    • wispiANt
      Network Vision/LTE - New York City Market

      By wispiANt · Posted

      Historically, T-Mobile has been the only carrier contracting with Crown Castle Solutions, at least in Brooklyn. I did a quick count of the ~35 nodes currently marked as "installed" and everything mapped appears to be T-Mobile. However, they have a macro sector pointed directly at this site and seem to continue relying on the older-style DAS nodes. Additionally, there's another Crown Castle Solutions node approved for construction just around the corner, well within range of their macro. I wouldn’t be surprised to see Verizon using a new vendor for their mmWave build, especially since the macro site directly behind this node lacks mmWave/CBRS deployment (limited to LTE plus C-Band). However, opting for a multi-carrier solution here seems unlikely unless another carrier has actually joined the build. This node is equidistant (about five blocks) between two AT&T macro sites, and there are no oDAS nodes deployed nearby. Although I'm not currently mapping AT&T, based on CellMapper, it appears to be right on cell edge for both sites. Regardless, it appears that whoever is deploying is planning for a significant build. There are eight Crown Castle Solutions nodes approved for construction in a 12-block by 2-block area.
    • radem
      Official Tmobile-Sprint merger discussion thread

      By radem · Posted

      Starlink (1900mhz) for T-Mobile, AST SpaceMobile (700mhz and 850mhz) for AT&T, GlobalStar (unknown frequency) for Apple, Iridium (unknown frequency) for Samsung, and AST SpaceMobile (850mhz) for Verizon only work on frequency bands the carrier has licensed nationwide.  These systems broadcast and listen on multiple frequencies at the same time in areas much wider than normal cellular market license areas.  They would struggle with only broadcasting certain frequencies only in certain markets so instead they require a nationwide license.  With the antennas that are included on the satellites, they have range of cellular band frequencies they support and can have different frequencies with different providers in each supported country.  The cellular bands in use are typically 5mhz x 5mhz bands (37.5mbps total for the entire cell) or smaller so they do not have a lot of data bandwidth for the satellite band covering a very large plot of land with potentially millions of customers in a single large cellular satellite cell.  I have heard that each of Starlink's cells sharing that bandwidth will cover 75 or more miles. Satellite cellular connectivity will be set to the lowest priority connection just before SOS service on supported mobile devices and is made available nationwide in supported countries.  The mobile device rules pushed by the provider decide when and where the device is allowed to connect to the satellite service and what services can be provided over that connection.  The satellite has a weak receiving antenna and is moving very quickly so any significant obstructions above your mobile device antenna could cause it not to work.  All the cellular satellite services are starting with texting only and some of them like Apple's solution only support a predefined set of text messages.  Eventually it is expected that a limited number of simultaneous voice calls (VoLTE) will run on these per satellite cell.  Any spare data will then be available as an extremely slow LTE data connection as it could potentially be shared by millions of people.  Satellite data from the way these are currently configured will likely never work well enough to use unless you are in a very remote location.
    • swintec
      Official Tmobile-Sprint merger discussion thread

      By swintec · Posted

      will this work for service in a plane?
    • Paynefanbro
      Official Tmobile-Sprint merger discussion thread

      By Paynefanbro · Posted

      T-Mobile owns the PCS G-block across the contiguous U.S. so they can just use that spectrum to broadcast direct to cell. Ideally your phone would only connect to it in areas where there isn't any terrestrial service available.

  • Recently Browsing

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