| Age | Commit message (Collapse) | Author | Files |
|---|
|
Implementing CB610L radio modem support
|
|
- 31030 - AT&T - from UBX-13001820 - R13;
- 310590 - Verizon - from UBX-13001820 - R13;
- 310650 - Cisco Jasper MVNO in AT&T network - from UBX-13001820 - R13;
- 310890 - Verizon - from UBX-13001820 - R13;
- 311270 - Verizon - from VZ_REQ_LTEB13NAC_12084129, IMS SIM;
- 311480 - Verizon - from VZ_REQ_LTEB13NAC_12084129, IMS SIM;
- 312770 - Verizon - from the output of AT#FWPLS? on a 5SG1 radio.
|
|
|
|
Added three additional MCC/MNC combinations for the FirstNet networks.
Those combinations were discovered on a 5SG1 radio in the output of
`AT#FWPLS=0,0`.
|
|
Added the 'Carrier Code' field to the MCC/MNC table. The new field is
supposed to be a constant Multitech-specific indentifier that is constant
between the firmware versions and does not necessarily depends on a
carrier name.
In particular the new field is needed to detect when there is an AT&T
SIM card inserted and 'UE mode of operation' shall be set to CS/PS mode 2.
|
|
Added one lost MCC/MNC entry for the FirstNet network (PLMN ID 313100)
and removed a duplicate MCC/MNC entry for PLMN ID 344930.
|
|
Added AT&T-related MCC/MNC values that were discovered from the AT+COPN output:
- 33490 - discovered on 5SG1, L4E1, L4G1 and LEU7;
- 901044 - discovered on 5SG1, L4E1 and L4G1;
- 90118 - discovered on H5 and LNA3.
|
|
Updated the MCC/MNC table for AT&T using the document from ITU
(https://www.itu.int/dms_pub/itu-t/opb/sp/T-SP-E.212B-2018-PDF-E.pdf).
Notable changes:
- filled empty carrier names for a bunch of MCC/MNC combinations;
- changed the carrier for PLMN ID "310280" from "T-Mobile" to "AT&T Wireless Inc.";
- added 7 new PLMN IDs that correspond to AT&T in various countries.
|
|
Sorted the MCC/MNC table by PLMN ID to simplify its maintenance.
The content and the format are not changed, only the order of items
in the table.
|
|
Removed MCCs that are not listed by ITU.
|
|
Fixed carrier MCC/MNC table lookup for networks with two-digit conuntry codes.
The original MCC/MNC population script used the following encoding for MCC/MNC values:
- MCC - interpret the original value as hex;
- 2-digit MNC - append "f" and interpret the resulting value as hex;
- 3-digit MNC - interpret the original value as hex.
So during lookup the system shall also use this conversion logic before querying
the information from the table.
|
|
|
|
|
