Jump to content

PLMNs / MCC-MNCs (310-120, 311-870, etc.)


Recommended Posts

To condense things to one thread, rather than spreading 'em around (my bad), here's what we know so far:

 

310-120 gets used for band 25 and 26 LTE, leaving anything else for band 41 (except for some odd behavior on Virgin Mobile)

 

The following MCC-MNC pairs are also assigned to Sprint + Nextel:

 

311-490 Sprintcom

311-870 Sprintcom

311-880 Sprintcom

311-940 Clearwire

316-010 Nextel

 

Of those, 311-940 at least is used in Denver's TD-LTE deployment. I'll let others chime in. At least 311-870 is used in Austin. I believe another PLMN is used there, but I'm unsure of which one.

 

Also, according to tommym65's post, 311-870 is used in Chicago as well:

 

http://s4gru.com/index.php?/topic/5107-lte-800-band-26-sites-accepted-discussion/page-25

 

This probably debunks my theory that 311-870 is a "high capacity designation" for sites that could be used for fixed wireless service if the trial in Corpus Christi is successful.

 

My 311-870 view was taken from a "neutral" (T-Mobile) SIM, and that PLMN hasn't shown up anywhere yet where only band 25 LTE is available.

 

What other MCC-MNC combos hve y'all seem for Sprint or its MVNOs?

Link to comment
Share on other sites

Sorry, Ian, I did not intend to bust your chops in the other thread.  You are a valuable contributor, and this is important info.  So, let us keep it in one central location.

 

I had not thought of popping my T-Mobile SIM into my Nexus 5 in a while.  But that was a good idea, since it enables the 3GPP network scan function.  That said, for those who do not also have a non Sprint SIM for the Nexus 5, simply removing the Sprint SIM and rebooting should also reveal the 3GPP network scan.  Screenshots from various markets are welcome.

 

AJ

Link to comment
Share on other sites

Sorry, Ian, I did not intend to bust your chops in the other thread.  You are a valuable contributor, and this is important info.  So, let us keep it in one central location.

 

I had not thought of popping my T-Mobile SIM into my Nexus 5 in a while.  But that was a good idea, since it enables the 3GPP network scan function.  That said, for those who do not also have a non Sprint SIM for the Nexus 5, simply removing the Sprint SIM and rebooting should also reveal the 3GPP network scan.  Screenshots from various markets are welcome.

 

AJ

The chop-busting was warranted. Just this once :)

 

As for the SIM-free ability to scan networks, note that network selection won't show up even after a reboot if you keep the phone in LTE only mode if you go SIM-less. You have to switch to LTE + GSM mode, then wait a little, then back to LTE only, to both get the selection screen and ensure that you're looking only at LTE networks (vs. LTE + GSM + WCDMA). Of course, if you hadn't messed with *#*#4636#*#* you may not have this problem...and here I am derailing my own dang thread.

  • Like 1
Link to comment
Share on other sites

As for the SIM-free ability to scan networks, note that network selection won't show up even after a reboot if you keep the phone in LTE only mode if you go SIM-less. You have to switch to LTE + GSM mode, then wait a little, then back to LTE only, to both get the selection screen and ensure that you're looking only at LTE networks (vs. LTE + GSM + WCDMA). Of course, if you hadn't messed with *#*#4636#*#* you may not have this problem...and here I am derailing my own dang thread.

 

I hate to have my Testing.apk "special sauce" shared for all to know, but those are all excellent tips.  And I have not done enough SIM swapping to encounter all of the idiosyncratic 3GPP/3GPP2 network acquisition permutations that follow.  So, we appreciate the reports of your direct experience, Ian.

 

AJ

  • Like 1
Link to comment
Share on other sites

Chicago area here. A network scan reveals CLEAR and 311-870 PLMN on my Nexus 5. I can see a confirmed B41 site from my window. I can't access B41 normally, but without a SIM, connecting to CLEAR both put me on B41 with an EARFCN of 40056. For some reason, sometimes on 311-870 I can connect to 41, but other times I get B4 with a T-Mobile PLMN. Not sure what's happening there

  • Like 2
Link to comment
Share on other sites

Chicago area here. A network scan reveals CLEAR and 311-870 PLMN on my Nexus 5. I can see a confirmed B41 site from my window. I can't access B41 normally, but without a SIM, connecting to CLEAR both put me on B41 with an EARFCN of 40056.

 

Can we get a screenshot of EARFCN 40056?  This is a new center frequency, one that we have not seen in other markets.  I would like to add it to my band plan spreadsheet.

 

AJ

  • Like 3
Link to comment
Share on other sites

Can we get a screenshot of EARFCN 40056?  This is a new center frequency, one that we have not seen in other markets.  I would like to add it to my band plan spreadsheet. AJ

Does this help?

 

Screenshot_2014-01-13-08-37-53.png

  • Like 1
Link to comment
Share on other sites

Okay so maybe someone can explain why this is going on...

 

First picture is of my Samsung Galaxy S3 LTE Engineering screen showing 310-120 as the MCC-MNC.

Second picture is from Mike's SignalCheck Pro app showing 311-490 as the MCC-MNC.

 

Yes, I am using VM USA but why would the engineering screen spit out 310-120 which is normally seen on Band 25 but, SignalCheck is putting out 311-490?

Link to comment
Share on other sites

  • 2 weeks later...

Okay so maybe someone can explain why this is going on...

 

First picture is of my Samsung Galaxy S3 LTE Engineering screen showing 310-120 as the MCC-MNC.

 

Second picture is from Mike's SignalCheck Pro app showing 311-490 as the MCC-MNC.

 

Yes, I am using VM USA but why would the engineering screen spit out 310-120 which is normally seen on Band 25 but, SignalCheck is putting out 311-490?

 

I'm seeing the same issue with SignalCheck on an S4 Mini, showing 310120 on SignalCheck, and 311870 in the LTE Engineering screen.

 

A few of you have reported this to me.. JossMan's issue appears to be yet another Samsung enginerring screen bug. It appears to be showing the home/default MCC-MNC for the device in that field, instead of the one it is actually connected to. Especially in JossMan's case, where he's using a Sprint device but is a Virgin Mobile customer, and 311-490 is VM's ID.

 

There are various functions that Android reports the MCC-MNC through. SignalCheck displays the one that has proven to be the most reliable no matter what the connection status is, but the diagnostic reports that can be sent from the app include them all. The evidence I have seen indicates that SignalCheck is correct.

 

In the case of the S4T, the issue is reversed -- the enginerring screen shows the correct ID, but the phone always reports the home/default MCC-MNC. I have been in touch with Samsung, but of course I was left hanging with the dreaded "we will pass it on to the appropriate people".

 

EDIT: To add to this topic overall, I'll toss in this note that I posted in the SignalCheck thread: I was able to confirm with Sprint that Band 25 and 26 are only using PLMN (MCC-MNC) 310-120. Band 41 is only on 311-490 or 311-870. All of this is subject to change in the future if they decide to consolidate IDs. However, I also know that Virgin Mobile users see Band 25 on 311-490.

 

-Mike

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

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Went to Rolling Loud NYC at Citi Field this weekend. Over 60,000 people in attendance. Verizon is a sponsor of the festival this year so naturally they had a ton of COWs set up at the festival. I counted at least 4. As a result, they were virtually the only carrier consistently able to provide a data connection. I didn't see any Verizon 5G, only LTE. T-Mobile on the other hand was a very interesting experience. I was seeing an eNB 331804 which I'm 99% sure is a COW. They also seems to be doing some sort of traffic management because I noticed that if I left my phone idle in my pocket, it would drop down to No Service/SOS or sometimes it would sit on EDGE. But the second that I needed to send a text, make a call, or even use Twitter my phone would switch over to LTE or 5G to complete the task. In an active data session, my phone would constantly flip between Band 2, Band 66, and Band 41. Sometimes, I'd catch myself on the COW and other times I'd get pushed over to eNB 875868, the relatively new Sprint conversion nearby. The network moved at a snails pace though. Where Verizon took about 15 seconds to load Twitter or send a pic, T-Mobile could take up to a minute to complete the same task. Here's some photos of the COWs I spotted. I think that the first two are Verizon and the one in the distance in the third pic is T-Mobile's single COW, not nearly enough for an event that size.  
    • @dkyeager has written up an article for The Wall on the Auction:   Robert
    • You need to have Wi-Fi Calling enabled and also have made at least one phone call over Wi-Fi Calling prior to using the inflight Wi-Fi.
    • See this page: https://www.sprint.com/en/support/in-flight-texting-wi-fi.html Also see the FAQ’s here: https://www.t-mobile.com/benefits/travel/in-flight-wifi “How do I access In-Flight Connection?”
  • Recently Browsing

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