Whereas the rest of the world uses two-digit MNCs, the United States
nominally uses three-digit MNCs. However, due to this uniqueness, and a
lack of support in international networks, carriers which are only
uniquely identified via a three-digit MNC are not compatible with
international roaming.
As a result, in practice, most major US carriers have MNCs ending in 0,
so that they are uniquely identified by the first two digits, thereby
providing their subscribers with compatibility on international
networks.
Ok, bad example. Let’s take Canada:
MCC=302, MNC=652..657 are all different operators.
The module is capable to handle 2 or 3 digits MNC and get registered in roaming or work with a US/Canada SIM.
What kind of info do you need exactly?
The module is capable to handle 2 or 3 digits MNC and get registered in roaming or work with a US/Canada SIM.
What kind of info do you need exactly?
My concern is, that I relied on the module documentation and reserved for MCC/MNC 6 bytes (5 bytes for the string plus 0-termination).
Then I stumbled over the wikipedia page stating that MCC/MNC could have a maximum length of six characters.
I wondered how the GSM module would behave in such a network situation? Crashing because of a buffer overflow or not crashing because its actually a documentation flaw…
So I can assume it is just a typo in the documentation and also MCC/MNC maximum length is six characters?
Hardy
I think you are referring to AT#CSURV command.
<mnc> – hexadecimal 2-digits number; it is the mobile network code
It is a typo in the documention. The modules are PTCRB and AT&T (depending on the sw. version) certified and can work with 3 digits MNC without any issue.
We use cookies to enhance your browsing experience and help us improve our websites. To improve our website, we carefully select third parties that use cookies to allow us to serve specific content and achieve the purposes set out in our cookie policy. For more information on how to make adjustments through your browser to the cookies being used on your device, please click Find Out More link. By closing this banner or continuing to browse our website, you agree to our use of such cookies. FIND OUT MORE
Hi,
the documentation (AT command reference) states, that the MNC is a hex 2-digits number.
What’s going to happen if one switches the GSM to on e.g. in the US with T-Mobile as the GSM operator?
According to http://en.wikipedia.org/wiki/Mobile_Network_Code the MNC might be a 3-digit (decimal) number.
Hardy
Wiki also says:
Ok, bad example. Let’s take Canada:
MCC=302, MNC=652..657 are all different operators.
There are several other operators, just check http://en.wikipedia.org/wiki/Mobile_Network_Code
How are those handled?
Hardy
The module is capable to handle 2 or 3 digits MNC and get registered in roaming or work with a US/Canada SIM.
What kind of info do you need exactly?
My concern is, that I relied on the module documentation and reserved for MCC/MNC 6 bytes (5 bytes for the string plus 0-termination).
Then I stumbled over the wikipedia page stating that MCC/MNC could have a maximum length of six characters.
I wondered how the GSM module would behave in such a network situation? Crashing because of a buffer overflow or not crashing because its actually a documentation flaw…
So I can assume it is just a typo in the documentation and also MCC/MNC maximum length is six characters?
Hardy
I think you are referring to AT#CSURV command.
<mnc> – hexadecimal 2-digits number; it is the mobile network code
It is a typo in the documention. The modules are PTCRB and AT&T (depending on the sw. version) certified and can work with 3 digits MNC without any issue.