5 Network personalisation

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

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.1 Network personalisation

Network personalisation allows a ME to be personalised to a particular network, for example to prevent the use of stolen MEs on other networks. The ME may optionally be personalised to more than one network.

The ME is network personalised by storing the code (MCC+MNC) (see TS 23.003 [3]) of the relevant network(s) in the ME and setting a network 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 International Mobile Subscriber Identity (IMSI) is read from the SIM/USIM and the embedded network code (MCC+MNC) checked against that stored in the ME. If the values differ, the MS shall go into emergency calls only mode as defined in annex A.2.

The network personalisation feature is controlled by a Network Control Key, (NCK) which has to be entered into the ME in order to network de‑personalise it.

In order to support the network personalisation feature the ME shall have storage for the network personalisation indicator, the network code(s) and the NCK.

5.1.1 Operation of network personalised ME

The network personalisation check described below is performed whenever a SIM/USIMis 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 network personalised: The ME checks its network personalisation indicator, if it is set to "off" the personalisation check shall be stopped and the MS goes into the normal mode of operation, omitting the remaining steps of the check;

b) check the network code(s): The ME reads the IMSI from the SIM/USIM, extracts the network code from it and checks it against the (list of) value(s) stored on the ME.

If no match is found in b), the ME may display an appropriate message, (e.g., "Incorrect SIM" or "Incorrect USIM") and shall go into the emergency calls only mode as defined in annex A.2. If a match is found, the MS goes into the normal mode of operation.

5.1.2 Network personalisation cycle

5.1.2.1 Personalisation cycle

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

The network personalisation process is as follows:

a) The network code(s) are entered into the ME. This may be accomplished by one of the following means:

‑ for the case of a single network code, the ME reads the IMSI from the SIM/USIM and extracts the network code;

‑ the ME reads the Co-operative Network List (CNL) from the SIM/USIM and extracts the list of network code(s) associated with network personalisation;

‑ keypad entry;

‑ a manufacturer defined process.

b) The ME carries out the pre‑personalisation checks contained in clause 13. If they all pass, the network code(s) are stored in the ME. If any fail, the personalisation process shall be terminated.

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

d) The network personalisation indicator is set to "on".

5.1.2.2 De‑personalisation cycle

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

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

a) the NCK is entered into the ME;

b) if the entered NCK is the same as the one stored in the ME the network personalisation indicator is set to "off".

If the entered and stored NCK values differ, the de‑personalisation process shall be stopped. The ME remains personalised and the stored network code(s) and NCK shall be left unchanged.

5.2 Network subset personalisation

Network subset personalisation is a refinement of network personalisation, which allows network operators to limit the usage of a ME to a well defined subset of IMs; e.g. where the ME is the property of a third party.

The ME is network subset personalised by storing the network code and the Network Subset Code (digits 6 and 7 of the IMSI) as an identification of the network subset and setting an network subset personalisation indicator in the ME to "on". Whenever a SIM/USIM is inserted, or the MS is powered up with a SIM/USIM already in place, the network subset code group is read from the SIM/USIM and checked against the stored values in the ME. If no match is found, the ME shall go into emergency calls only mode, as defined in annex A.2.

The network subset personalisation feature is controlled by a Network Subset Control Key (NSCK) which has to be entered into the ME in order to network subset de‑personalise it.

In order to support the network subset personalisation feature, the ME shall have storage for the network subset personalisation indicator, the network subset code group(s) and the NSCK.

5.2.1 Operation of Network subset personalised ME

The Network subset 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 network subset personalised: The ME checks its network subset personalisation indicator, if it is set to "off" the personalisation check shall be stopped and the ME goes into the normal mode of operation, omitting the remaining steps of the check;

b) check network subset code group: The ME reads the network subset code group from the SIM/USIM and checks it against the (list of) stored value(s) on the ME;

If no match is found in b) 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.

5.2.2 Network subset personalisation cycle

5.2.2.1 Personalisation Cycle

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

The network subset personalisation process is as follows:

a) The network subset code group(s) is (are) entered into the ME. This may be accomplished by one of the following means:

‑ for the case of a single network code group, the ME reads the IMSI from the SIM/USIM and extracts the network and network subset codes;

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

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

d) The network subset personalisation indicator is set to "on".

5.2.2.2 De‑personalisation cycle

To de‑personalise the ME the correct NSCK shall be entered. It is optional whether or not a SIM/USIM is inserted. If a SIM/USIM is inserted, then de‑personalisation shall be offered whether or not the network subset personalisation check passes or fails.

The network subset de‑personalisation process is as follows:

a) the NSCK is entered into the ME;

b) if the entered NSCK is the same as the one stored in the ME the network subset personalisation indicator is set to "off".

If the entered and stored NSCK values differ, the de‑personalisation process shall be stopped and the ME remain personalised. The stored network and network subset codes and the NSCK are left unchanged.