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

Does this help?

 

Good enough for me.  Thanks.  The WiMAX/TD-LTE spreadsheet will be updated in a moment.

 

http://s4gru.com/index.php?/files/file/29-clearwire-wimaxtd-lte-carrier-band-plan/

 

AJ

  • 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

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

 

But is the Galaxy S4 Mini connected to band 25 LTE 1900 or band 41 TD-LTE 2600?  That is the question.

 

AJ

Link to comment
Share on other sites

It's connected to B41.

 

And that makes sense.  Band 41 is not going to use the same MCC-MNC as band 25.

 

AJ

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.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • So, in summary, here are the options I tested: T-Mobile intl roaming - LTE on SoftBank, routes back to the US (~220ms to 4.2.2.4) IIJ physical SIM - LTE on NTT, local routing Airalo - LTE on SoftBank and KDDI (seems to prefer SoftBank), routed through Singapore (SingTel) Ubigi - 5G on NTT, routed through Singapore (Transatel) US Mobile East Asia roaming - 5G on SoftBank, routed through Singapore (Club SIM) Saily - 5G on NTT, routed through Hong Kong (Truphone)...seems to be poorer routing my1010 - LTE on SoftBank and KDDI (seems to prefer KDDI), routed through Taiwan (Chunghwa Telecom) I wouldn't buy up on the T-Mobile international roaming, but it's a solid fallback. If you have the US Mobile roaming eSIM that's a great option. Otherwise Ubigi, Airalo, or my1010 are all solid options, so get whatever's cheapest. I wouldn't bother trying to find a physical SIM from IIJ...the Japanese IP is nice but there's enough WiFi that you can get a Japanese IP enough for whatever you need, and eSIM flexibility is great (IIJ as eSIM but seems a bit more involved to get it to work).
    • So, the rural part of the journey still has cell service for nearly all the way, usually on B18/19/8 (depending on whether we're talking about KDDI/NTT/SoftBank). I think I saw a bit of B28 and even n28 early on in the trip, though that faded out after a bit. Once we got to where we were going though, KDDI had enough B41 to pull 150+ Mbps, while NTT and SoftBank had B1/B3 IIRC. Cell service was likewise generally fine from Kawaguchiko Station to Tokyo on the express bus to Shinjuku Station, though there were some cases where only low-band LTE was available and capacity seemed to struggle. I also figured out what I was seeing with SoftBank on 40 MHz vs. 100 MHz n77: the 40 MHz blocks are actually inside the n78 band class, but SoftBank advertises them as n77, probably to facilitate NR CA. My phone likely preferred the 40 MHz slices as they're *much* lower-frequency, ~3.4 GHz rather than ~3.9, though of course I did see the 100 MHz slice being used rather often. By contrast, when I got NR on NTT it was either n28 10x10 or, more often, 100 MHz n78. As usual, EMEA bands on my S24 don't CA, so any data speeds I saw were the result of either one LTE carrier or one LTE carrier plus one NR carrier...except for B41 LTE. KDDI seems to have more B41 bandwidth live at this point, so my1010 or Airalo works well for this, and honestly while SoftBank and NTT 5G (in descending order of availability) have 5G that's readily available it may be diminishing returns, particularly given that I still don't know how to, as someone not from Hong Kong, get an eSIM that runs on SoftBank 5G that isn't the USM "comes for free with the unlimited premium package" roaming eSIM (NTT is easy enough thanks to Ubigi). In other news, I was able to borrow someone's Rakuten eSIM and...got LTE with it. 40 Mbps down, 20 Mbps up, 40ms latency to Tokyo while in Tokyo...which isn't any worse than the Japan-based physical SIMs I had used earlier. But not getting n77 or n257 was disappointing, though I had to test the eSIM from one spot rather than bouncing around the city to find somewhere with better reception. It's currently impossible to get a SIM as a foreigner that runs on Rakuten, so that was the best I could do. Also, I know my phone doesn't have all the LTE and 5G bands needed to take full advantage of Japanese networks. My S24 is missing: B21 (1500 MHz) - NTT B11 (1500 MHz) - KDDI, SoftBank B42 (3500 MHz) - NTT, KDDI, SoftBank n79 (4900 MHz) - NTT Of the above, B42/n79 are available on the latest iPhones, though you lose n257, and I'm guessing you're not going to find B11/B21 on a phone sold outside Japan.
    • T-Mobile acquiring SoniqWave's 2.5 GHz spectrum  Another spectrum speculator down! T-Mobile is acquiring all of their licenses and their leases. Details are lacking but it looks like T-Mobile might be giving them 3.45GHz in exchange in some of the markets where they're acquiring BRS/EBS to sweeten the deal and stay below the spectrum screen. Hopefully NextWave is at the negotiating table with T-Mobile so NYC can finally get access to the full BRS/EBS band as well. 
    • Maybe. The taller buildings on one side of the street all have Fios access and the NYCHA buildings are surrounded by Verizon macros that have mmWave. I don’t think this site will add much coverage. It’d be better off inside the complex itself.
    • Looks like a great place for for FWA. Many apartment dwellers only have one overpriced choice.
  • Recently Browsing

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