22.0223GPPMobile functionality specificationPersonalisation of Mobile Equipment (ME)Release 17TS
Corporate personalisation is a refinement of SP personalisation which allows companies to prevent the use of MEs they provide for their employees or customers with other IMs without that corporate personalisation.
This feature only works with IMs which support both the GID1 and GID2 files. For the purpose of corporate personalisation the GID1 file is programmed at pre‑personalisation with an SP code that identifies the service provider and the GID2 file is programmed by the service provider or corporate customer with a code that identifies the corporate customer.
The ME is corporate personalised by storing the corporate code group(s) and setting a corporate personalisation indicator in the ME to "on". Whenever a SIM/USIM is inserted, or the ME is powered up with a SIM/USIM already in place, the corporate code group is read from the SIM/USIM and checked against those stored in the ME. If there is no match the ME shall go into emergency calls only mode, as defined in annex A.2.
The corporate personalisation feature is controlled by a Corporate Control Key (CCK), which has to be entered into the ME in order to de‑personalise it.
In order to support the corporate personalisation feature the ME shall have storage for the corporate personalisation indicator, a (list of) corporate code group(s) and the CCK.
7.1 Operation of corporate personalised MEs
The personalisation check described below is performed whenever a SIM/USIM is inserted or the ME is powered up with a SIM/USIM already in place.
The personalisation check is as follows. When more than more personalisation is active in the ME, normal mode of operation includes performing any outstanding personalisation checks:
a) check whether the ME is corporate personalised: The ME checks the corporate personalisation indicator, if it is set to "off" the personalisation check shall be stopped and the ME goes into its normal mode of operation;
b) check whether the SIM/USIM supports GID1 and GID2: The ME checks that the SIM/USIM supports the GID1 and GID2 files;
c) check the corporate code group: The ME reads the corporate code group from the SIM/USIM and checks it against the (list of) stored value(s) on the ME;
If b) fails, or no match is found in c), the ME may display an appropriate message (e.g. "Insert correct SIM") and shall go into emergency calls only mode, as defined in annex A.2. Otherwise, the ME goes into the normal mode of operation.
7.2 Corporate personalisation cycle
7.2.1 Personalisation cycle
The process of personalisation can only be carried out on a currently unpersonalised ME, i.e., if the corporate personalisation indicator is set to "off". Access to the personalisation process shall be restricted in order to prevent unauthorised, accidental or unwanted personalisation. Other restrictions are described in clause 13. The personalisation process results in the CCK being set, the corporate personalisation indicator being set to "on" and the storage in the ME of a (list of) corporate group(s) codes to which the ME is being personalised.
The corporate personalisation process is as follows:
a) The corporate code group(s) is (are) entered into the ME. This may be accomplished by one of the following means:
‑ the ME checks that the SIM/USIM supports the GID1 and GID2 files, if not the corporate personalisation process shall be aborted with an appropriate error message;
the ME reads the corporate code group(s) from the SIM/USIM. If either the SP code or the corporate code is set to the default value (see Annex A.1), then the corporate personalisation process shall be aborted with an appropriate error message. Otherwise the corporate code group is are entered into the ME;
– the ME reads the Co-operative Network List (CNL) from the SIM/USIM and extracts the (list of) Corporate code group(s);
‑ keypad entry;
‑ a manufacturer defined process.
b) The ME carries out the pre‑personalisation checks contained in clause 13 on the new codes entered into the ME. If they all pass, the corporate code group(s) are stored in the ME. If any fail, the personalisation process shall be terminated.
c) The CCK is stored in the ME. This may be entered via the keypad by the user or by a manufacturer defined process;
d) The corporate personalisation indicator is set to "on".
7.2.2 De‑personalisation cycle
To de‑personalise the ME the correct CCK shall be entered. It is optional whether or not a SIM/USIM is inserted in the ME. If a SIM/USIM is inserted, then de‑personalisation shall be offered whether or not the corporate personalisation check passes or fails.
The corporate de‑personalisation shall be possible by keypad entry. If there is no keypad, then an alternative ME‑based solution shall be provided. Other de‑personalisation methods may also be provided such as a network initiated process whereby the control key is sent to the MS over‑the‑air (see clause 9).
The corporate de‑personalisation process is as follows:
a) the CCK is entered into the ME;
b) if the entered CCK is the same as the one stored in the ME, the corporate personalisation indicator is set to "off".
If the entered and stored CCK values differ the de‑personalisation process shall be stopped and the ME remains corporate personalised. The stored network operator, SP and corporate codes and CCK are left unchanged