So a problem had arisen, carriers wanted to change certain carrier related settings on devices (Specifically the Carrier Config Manager) in the Android ecosystem. The Android maintainers didn’t want to open the permissions to change these settings to everyone, only the carrier providing service to that device.
And if you purchased a phone from Carrier A, and moved to Carrier B, how do you manage the permissions for Carrier B’s app and then restrict Carrier A’s app?
Enter the Android UICC Carrier Privileges.
The carrier loads a certificate onto the SIM Cards, and signing Android Apps with this certificate, allowing the Android OS to verify the certificate on the card and the App are known to each other, and thus the carrier issuing the SIM card also issued the app, and presto, the permissions are granted to the app.
Carriers have full control of the UICC, so this mechanism provides a secure and flexible way to manage apps from the mobile network operator (MNO) hosted on generic app distribution channels (such as Google Play) while retaining special privileges on devices and without the need to sign apps with the per-device platform certificate or preinstall as a system app.UICC Carrier Privileges doc
Once these permissions are granted your app is able to make API calls related to:
- APN Settings
- Roaming/nonroaming networks
- Visual voicemail
- SMS/MMS network settings
- VoLTE/IMS configurations
- OTA Updating SIM Cards
- Sending PDUs to the card
2 thoughts on “Android Carrier Privileges”
Can the operator enable VoLTE or any new service like VoNR/5G NSA/SA..etc on this open source project ?
No, Carrier must submit their configs on the AOSP to enable it .