Devices running Android 9 can recognize subscription
carrier information to
provide an ID and a carrier name. Android maintains a carrier ID database, with
matching rules for each carrier and its unique carrier ID. AOSP includes the
content of the carrier ID database, in the file
The unified database minimizes duplicate logic in apps that need to identify
carriers and limits the exposure of carrier-identifying attributes.
To improve the coverage and accuracy of carrier identification, Android supports out-of-band and carrier ID table updates. Each update comes with a version number and is published to AOSP.
Users who want to implement out-of-band updates can download the
binary from AOSP. To view the readable format of the table, see
Place the carrier ID table in the
/data/misc/carrierid/ data partition of the
device. If the carrier ID table is newer than the existing version, the device
persists the table to the
carrier ID database class.
The most recent information from the carrier ID database is picked up by the
Adding carrier ID information to the database
To add or update a carrier ID to the database, submit a request using the Carrier identification information form.
Your request is reviewed and if approved, the change is pushed to the AOSP code
You can then copy the updated list and incorporate it into your customized
Integrating carrier IDs with CarrierConfig
Starting from Android 10,
carrier configuration supports
using carrier IDs as keys to fetch carrier-specific configurations from
Integrating carrier IDs with
CarrierConfig has the following advantages:
- Consolidates all MCC/MNC pairs for each carrier into a single location removing duplicate or inconsistent data.
- Creates a canonical identifier for each carrier and removes ambiguity.
- Allows mobile virtual network operators (MVNOs) to be identified with individual IDs instead of having configurations as part of a mobile network operator (MNO).
Migrating configuration data to carrier IDs
To migrate configuration data from MCC/MNC pairs to carrier IDs, follow these steps:
carrier_config_mccmnc.xmlfiles from a single carrier together. Use
carrier_list.textpbas a reference to map the MCC, MNC, and MVNO information to a particular carrier.
Merge the configurations into a single file.
(Optional) Inherit data from MNOs. MVNOs inherit configurations from MNOs in the legacy
carrier_config_mccmnc.xmlfile. Because carrier IDs allow all carriers including MVNOs to have a dedicated config file, it's recommended to include MNO data during migration.
If the configuration for an MVNO carrier ID doesn't exist, fetch the configuration from its MNO carrier ID using
Rename the new file as
carrier_config_carrierid_carrierid_carriername.xmlwhere carrierid must correspond to a
canonical_idand carriername should correspond to a