6 SP personalisation

22.0223GPPMobile functionality specificationPersonalisation of Mobile Equipment (ME)Release 17TS

Service provider or SP personalisation is a feature which allows a service provider to associate a ME with the SP. This feature only works with IMs which support the GID1 file. For the purpose of SP personalisation the GID1 file is programmed with an SP code that identifies the service provider.

The ME is SP personalised by storing the SP code group(s) and setting a SP 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 SP code group is read from the SIM/USIM and checked against those stored in the ME. If no match is found the ME shall go into emergency calls only mode as defined in annex A.2.

The SP personalisation feature is controlled by a Service Provider Control Key, (SPCK) which has to be entered into the ME in order to SP de‑personalise it.

In order to support the SP personalisation feature the ME shall have storage for the SP personalisation indicator, the (list of) SP code group(s) and the SPCK.

6.1 Operation of SP 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 one personalisation is active in the ME, normal mode of operation includes performing any outstanding personalisation checks:

a) check whether the ME is SP personalised: The ME checks the SP 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: The ME checks that the SIM/USIM supports the GID1 file;

c) check the SP code group: The ME reads the SP 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.

6.2 SP personalisation cycle

6.2.1 Personalisation cycle

The process of personalisation can only be carried out on a currently unpersonalised ME, i.e., if the SP 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 SPCK being set, the SP personalisation indicator being set to "on" and the storage in the ME of the (list of) SP code group(s) to which the ME is being personalised.

The SP personalisation process is as follows:

a) The SP 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 file, if not the SP personalisation process is aborted with an appropriate error message. The ME reads the SP code group from the SIM/USIM. If the SP code is set to the default value (see annex A.1) then the personalisation process shall be aborted with an appropriate error message. Otherwise the SP code group is entered into the ME.

‑ the ME reads the Co-operative Network List (CNL) from the SIM/USIM and extracts the (list of) SP 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 SP code group(s) is (are) stored in the ME. If any fail, the personalisation process shall be terminated.

c) The SPCK is stored in the ME. This may be entered via the keypad by the user or by a manufacturer defined process.

e) The SP personalisation indicator is set to "on".

6.2.2 De‑personalisation cycle

To de‑personalise the ME, the correct SPCK 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 SP personalisation check passes or fails.

SP 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 SP de‑personalisation process is as follows:

a) the SPCK is entered into the ME;

b) if the entered SPCK is the same as the one stored in the ME, the SP personalisation indicator is set to "off".

If the entered and stored SPCK values differ, the de‑personalisation process shall be stopped and the ME remains SP personalised. The stored network and SP codes and SPCK shall be left unchanged.