Difference between revisions of "SIM-card Applet"

From BlockChainTeleCom wiki
Jump to: navigation, search
Line 16: Line 16:
 
The method is based on special information collected by the applet from the terminal and also from some files on the [[Terms_and_Conditions#Anchor_Abbreviations|USIM]]. This information is applied to the special map named "'''Account [[Terms_and_Conditions#Anchor_Abbreviations|MCC]]/[[Terms_and_Conditions#Anchor_Abbreviations|MNC]] Coverage List'''", which defines up to 25 MCC/MNC pairs for each account.
 
The method is based on special information collected by the applet from the terminal and also from some files on the [[Terms_and_Conditions#Anchor_Abbreviations|USIM]]. This information is applied to the special map named "'''Account [[Terms_and_Conditions#Anchor_Abbreviations|MCC]]/[[Terms_and_Conditions#Anchor_Abbreviations|MNC]] Coverage List'''", which defines up to 25 MCC/MNC pairs for each account.
  
Each record of the "Account MCC/MNC Coverage List" contains 25 [[Terms_and_Conditions#Anchor_Abbreviations|PLMNs]]codes the corresponding account [[Terms_and_Conditions#Anchor_Abbreviations|IMSI]] is valid for. The coding of each MCC/MNC pair is according to standard [http://www.tech-invite.com/guicc/tinv-glos-uicc-p.html EF(PLMNsel)].  If an MCC/MNC pair has an MCC value according to EF(PLMNsel), but MNC with 0xFF value, then the MCC/MNC pair is wildcard and is valid for the entire country.
+
Each record of the "Account MCC/MNC Coverage List" contains 25 [[Terms_and_Conditions#Anchor_Abbreviations|PLMNs]] codes the corresponding account [[Terms_and_Conditions#Anchor_Abbreviations|IMSI]] is valid for. The coding of each MCC/MNC pair is according to standard [http://www.tech-invite.com/guicc/tinv-glos-uicc-p.html EF(PLMNsel)].  If an MCC/MNC pair has an MCC value according to EF(PLMNsel), but MNC with 0xFF value, then the MCC/MNC pair is wildcard and is valid for the entire country.
  
 
Example:
 
Example:

Revision as of 13:06, 13 April 2018

Video demonstration

Live demonstration of the MultiAccount SIM applet:

  • how to list mobile profiles via SIM menu
  • how a new mobile profile is downloaded on the SIM-card


How it works

This document describes the mobile profile ("account") selection methods to detect if the application ("applet") should switch to another account depending on the settings and current network registration status of the terminal.

The method is based on special information collected by the applet from the terminal and also from some files on the USIM. This information is applied to the special map named "Account MCC/MNC Coverage List", which defines up to 25 MCC/MNC pairs for each account.

Each record of the "Account MCC/MNC Coverage List" contains 25 PLMNs codes the corresponding account IMSI is valid for. The coding of each MCC/MNC pair is according to standard EF(PLMNsel). If an MCC/MNC pair has an MCC value according to EF(PLMNsel), but MNC with 0xFF value, then the MCC/MNC pair is wildcard and is valid for the entire country.

Example:

* T-Mobile Austria has MCC/MNC equals to 23203. The value for "Account MCC/MNC Coverage List" will be 32F230
* for Austria, MCC/MNC wildcard will be 232FF. The value for "Account MCC/MNC Coverage List" will be 32F2FF

Some combinations of the wildCard MCC/MNC and exact MCC/MNC are possible:

* if the configuration defines two accounts for the same country (same MCC value) and one of it uses MNC wildcard (FF), then the one without the wildcard will only be used by the algorithm, if the one with the wildcard is contained in a record with a lower index (record index is equal to account number)
* if the MCC/MNC coverage list of an account uses one MNC wildcard, then all other MNC values in the same MCC/MNC coverage list record does not have any influence to the algorithm, if they have the same MCC.


Block diagram