1  Scope  Word‑p. 6

The present document provides functional specifications of five features to personalise Mobile Equipment (ME) for GSM and 3G systems. These features are called:

• Network personalisation;
• Network subset personalisation;
• Service Provider (SP) personalisation;
• Corporate personalisation;
• SIM/USIM personalisation (SIM for GSM systems or USIM for 3G systems).

The present document specifies requirements for MEs which provide these personalisation features.

2  References

3  Definitions and abbreviations  Word‑p. 7

3.1  Abbreviations

For the purposes of the present document, the following abbreviations apply:

CCK

Corporate Control Key

CNL

Co-operative Network List

GID1

Group Identifier (level 1)

GID2

Group Identifier (level 2)

EF

Elementary File

IMEI

International Mobile Equipment Identity

IMSI

International Mobile Subscriber Identity

MCC

Mobile Country Code

ME

Mobile Equipment

MS

GSM Mobile Station (ME + SIM)

MNC

Mobile Network Code

NCK

Network Control Key

NSCK

Network Subset Control Key

PCK

Personalisation Control Key

SIM

Subscriber Identity Module

SMS

Short Message Service

SP

Service Provider

SPCK

Service Provider Control Key

TMSI

Temporary Mobile Subscriber Identity

UE

3G User Equipment (ME + USIM)

USIM

User Services Identity Module

Further GSM abbreviations are given in TS 21.905.

3.2  Definitions

For the purposes of the present document, the following definitions apply:

corporate personalisation:

Allows a corporate customer to personalise MEs that he provides for his employees or customers use so that they can only be used with the company's own SIM/USIMs.

de personalisation:

Is the process of deactivating the personalisation so that the ME ceases to carry out the verification checks.

network personalisation:

Allows the network operator to personalise a ME so that it can only be used with that particular network operator's SIM/USIMs

network subset personalisation:

A refinement of network personalisation, which allows network operators to limit the usage of a ME to a subset of SIM/USIMs

normal mode of operation:

Is the mode of operation into which the ME would have gone if it had no personalisation checks to process.

personalisation:

Is the process of storing information in the ME and activating the procedures which verify this information against the corresponding information stored in the SIM/USIM whenever the ME is powered up or a SIM/USIM is inserted, in order to limit the SIM/USIMs with which the ME will operate.

SIM/USIM personalisation:

Enables a user to personalise a ME so that it may only be used with particular SIM/USIM(s).

SP personalisation:

Allows the service provider to personalise a ME so that it can only be used with that particular service provider's SIM/USIMs.

user:

Normally refers to the person performing the personalisation or de personalisation operations and may represent a network operator, service provider, manufacturer of the user/owner of the handset, depending on the context.

network code:

MCC and MNC.

network subset code:

digits 6 and 7 of the IMSI.

SP code:

code which when combined with the network code refers to a unique SP. The code is provided in the GID1 file on the SIM/USIM (see Annex A.1.) and is correspondingly stored on the ME.

Corporate code:

code which when combined with the network and SP codes refers to a unique Corporate. The code is provided in the GID2 file on the SIM/USIM (see Annex A.1.) and is correspondingly stored on the ME.

SIM/USIM code:

code which when combined with the network and NS codes refers to a unique SIM/USIM. The code is provided by the digits 8 to 15 of the IMSI

network code group:

same as network code

network subset code group:

combination of a network subset code and the associated network code.

SP code group:

combination of the SP code and the associated network code.

Corporate code group:

combination of the Corporate code and the associated SP and network codes.

SIM/USIM code group:

combination of the SIM/USIM code and the associated network subset and network codes (it is equivalent to the IMSI).

Personalisation entity:

Network, network subset, SP, Corporate or SIM/USIM to which the ME is personalised

4  General description  Word‑p. 8

The personalisation features work by storing information in the ME which limits the IMs with which it will operate, and by checking this information against the SIM/USIM whenever the ME is powered up or a SIM/USIM is inserted. If a check fails, the ME enters the "limited service state" in which only emergency calls can be attempted (see annex A.2).

There are five personalisation categories of varying granularity; network, network subset, SP, corporate and SIM/USIM. The personalisation categories are independent in so far as each category can be activated or de activated regardless of the status of the others. Each category has a separate personalisation indicator to show whether it is active or not. The ME can be personalised to one network, one network subset, one SP, one Corporate, one SIM/USIM or any combination thereof. The ME may optionally be personalised to multiple networks, network subsets, SPs, Corporates, IMs or any combinations thereof.

The codes used for each personalisation category are shown in Table 1. Some categories require several codes (e.g. SP and network for SP personalisation) and each combination of codes relating to a particular entity (network, SP etc.) is referred to as a code group. To personalise to multiple entities, multiple code groups are stored in the ME. For each activated personalisation category, the ME retrieves the relevant codes from the SIM/USIM and checks the retrieved code group against the (list of) code group(s) stored in the ME. If a match is found with any of the code groups stored in the ME, the check is passed for that category. If checks for all active categories are passed, then the MS goes into normal operation.

Table 1: Codes used by each personalisation category

Code	Network (MCC, MNC)	Network Subset (IMSI digits 6 and 7)	SP	Corporate	SIM/USIM (IMSI digits 8 to 15)
Personalisation category
Network	X
Network subset	X	X
SP	X		X
Corporate	X		X	X
SIM/USIM	X	X			X

Precautions must be taken to ensure that when more than one personalisation category is to be activated or when the ME is to be personalised to more than one entity of a personalisation category, the new codes are not in conflict with any existing valid codes. To avoid such conflicts, checks are carried out by the ME during the personalisation cycle, as described in clause 13.

As an optional ME feature, the status (activated or not) of each personalisation category and the values of the relevant codes may be read by the user.

5  Network personalisation  Word‑p. 9

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) 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:

1. 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;
2. 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:

1. 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.
2. 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.
3. The NCK is stored in the ME. This may be entered via the keypad by the user or by a manufacturer defined process.
4. The network personalisation indicator is set to "on".

5.1.2.2  De personalisation cycle  Word‑p. 10

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:

1. the NCK is entered into the ME;
2. 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.

1. 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;
2. 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  Word‑p. 11

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:

1. 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.
2. 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.
3. The NSCK is stored in the ME. This may be entered via the keypad by the user or by a manufacturer defined process.
4. 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.

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

1. the NSCK is entered into the ME;
2. 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.

6  SP personalisation  Word‑p. 12

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:

1. 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;
2. check whether the SIM/USIM supports GID1: The ME checks that the SIM/USIM supports the GID1 file;
3. 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:

1. 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.
2. 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.
3. The SPCK is stored in the ME. This may be entered via the keypad by the user or by a manufacturer defined process.
4. The SP personalisation indicator is set to "on".

6.2.2  De personalisation cycle  Word‑p. 13

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:

1. the SPCK is entered into the ME;
2. 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.

7  Corporate personalisation

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:

1. 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;
2. check whether the SIM/USIM supports GID1 and GID2: The ME checks that the SIM/USIM supports the GID1 and GID2 files;
3. 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  Word‑p. 14

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:

1. 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.
2. 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.
3. The CCK is stored in the ME. This may be entered via the keypad by the user or by a manufacturer defined process;
4. 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:

1. the CCK is entered into the ME;
2. 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

8  SIM/USIM personalisation  Word‑p. 15

SIM/USIM personalisation is an anti theft feature. When a ME is SIM/USIM personalised to a particular SIM it will refuse to operate with any other SIM/USIM. Hence, if the ME is stolen the thief will not be able to use it with another SIM/USIM (see note). While this does not stop the ME being stolen it should make it less attractive to the thief.

The ME is SIM/USIM personalised by storing the SIM/USIM code group (which is equivalent to the IMSI) of the relevant SIM/USIM in the ME and setting the SIM/USIM 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 SIM/USIM code group (IMSI) is read from the SIM/USIM and checked against the SIM/USIM code group(s) stored in the ME. If there is no match the ME shall go into emergency calls only mode as described in annex A.2.

The SIM/USIM personalisation feature is controlled by a Personalisation Control Key (PCK). This key is selected by the user at SIM/USIM personalisation and shall be entered into the ME to SIM/USIM de personalise the ME.

In order to support the SIM/USIM personalisation feature the ME should have storage for the SIM/USIM personalisation indicator, a (list of) SIM/USIM code group(s) and the PCK.

Multiple instances of SIM/USIM personalisation can be supported, i.e. whenever a SIM/USIM is inserted, or the ME is powered up with a SIM/USIM already in place, the IMSI is read from the SIM/USIM and checked against a list of SIM/USIM code groups stored in the ME.

8.1  Operation of SIM/USIM personalised ME

The SIM/USIM 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:

1. check whether the ME is SIM/USIM personalised: The ME checks its SIM/USIM 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;
2. read IMSI: The ME reads the IMSI from the SIM/USIM;
3. SIM/USIM personalisation check: The ME checks the read IMSI against the (list of) SIM/USIM code group(s) stored in the ME. If no match is found, the ME shall display an appropriate message (e.g. "Insert correct SIM" or "Insert correct USIM") and shall go into emergency calls only mode as described in annex A.2. Otherwise, the ME goes into the normal mode of operation.

8.2  SIM/USIM personalisation cycle

8.2.1  Personalisation cycle

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

The SIM/USIM personalisation process is as follows:

1. the SIM/USIM code group(s) is (are)entered into the ME. This may be accomplished by one of the following means :
   • the ME reads the SIM/USIM code group (IMSI) from the SIM/USIM and stores it;
   • a manufacturer defined process.
2. the ME carries out the pre personalisation checks contained in clause 13. If they all pass, the SIM/USIM code group(s) is(are) stored in the ME. If any fail, the personalisation process shall be terminated;
3. to personalise the ME to more than one SIM/USIM and if the reading of the IMSI from the SIM/USIM is used to enter the SIM/USIM code group in the ME, the procedures given in a) and b) shall be repeated;
4. the PCK is then stored in the ME. A single value of PCK shall be used for both single and multiple SIM/USIM personalisation;
5. the SIM/USIM personalisation indicator is set to "on".

8.2.2  De personalisation cycle  Word‑p. 16

To de personalise the ME, the correct PCK 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 SIM/USIM personalisation check passes or fails.

SIM/USIM de personalisation shall be provided by keypad entry. Other de personalisation methods may also be provided.

The SIM/USIM de personalisation process is as follows:

1. the user enters the PCK in the ME;
2. if the entered PCK is the same as the one stored in the ME, the SIM/USIM personalisation indicator is set to "off".

If the entered and stored PCK values differ, the de personalisation process shall be stopped and the ME remain personalised. The stored IMSI and PCK are left unchanged.

9  Over the air de personalisation cycle

10  Disable Personalisation  Word‑p. 17

There shall be a means to disable the personalisation at each level individually such that the ME shall operate with any (i.e. all) SIM/USIM at that level.

The process of disable personalisation can only be carried out on a currently unpersonalised ME, i.e., if the personalisation indicator for that level is set to "off". It results in the personalisation indicator remaining set to "off". When a particular level is disabled in this manner there shall be a means to make it impossible to change this status i.e. the disable becomes irreversible thus eliminating the need for key administration.

11  Manufacturer personalisation and de personalisation

12  Automatic personalisation  Word‑p. 18

ME manufacturers may offer alternative means of personalizing the ME such as adding functionality to the ME so that it automatically personalises itself to the first IM inserted in it, using one or more of the five personalisation levels described in clauses 5 to 8. In the case of SP and corporate personalisation, this is subject to the SIM/USIM supporting GID1 and GID2 (as required) and the contents of those files being non default.

13  Personalisation Cycle Restrictions

14  Security

A (Normative)  Technical information  Word‑p. 20

A.1  GID1 and GID2 files

The GID1 and GID2 elementary files on the SIM are specified in GSM 11.11 (ETS 300 977) [7].

The GID1 and GID2 elementary files on the USIM are specified in TS 31.102.

For the purposes of this TS, a SIM/USIM is said to support one of these two files if it is marked as both allocated and activated in the SIM/USIM service table.

The SP and corporate codes are stored in byte 1 of the appropriate files.

If byte 1 contains a hexadecimal value between "00" and "FE" inclusive, then this represents the SP/corporate code in the GID1/GID2 files respectively. For the purpose of these personalisation features, the ME shall ignore the contents of any other bytes of the file.

The value "FF" is the default value to be used in byte 1 when no meaningful SP/corporate code is represented in the GID1/GID2 files respectively. This value shall not be allocated as an SP/corporate code.

Note that network operators would normally allocate SP codes for its service providers and SPs would normally allocate corporate codes for its corporate customers.

A.2  Emergency calls only mode

The expression "emergency calls only mode" is used in this TS to describe the state the MS (combined ME and SIM) or US (combined ME and USIM) enters when a personalisation check fails. In this mode, the state of the MS/UE is equivalent to the "limited service state" (see TS 23.122). Although the personalisation has failed, the ME will be able to access the TMSI and IMSI from the SIM/USIM, and therefore any emergency call request shall use these as the MS/UE identity.

Set up of emergency calls remains as usual dependent on the status of Access Class 10 being broadcast in the cell (see TS 22.011).

A.3  Co-operative Network List  Word‑p. 21

The Co-operative Network List is specified in GSM 11.11 (ETS 300 977) [7].

For the purposes of this TS, a SIM is said to support this feature if it is marked as both allocated and activated in the SIM service table.

The value "FF" is the default value to be used when no meaningful code is represented. This value shall not be allocated as a code value.

A.4  Over the air de personalisation

a)

The ME specific de personalisation SMS messages sent by the network to de personalise the ME shall be coded according to TS 23.040. If length of every key does not exceed 8 digits, the TP UD field shall be coded as follows:

Character

Description

---

1-40

Operator specific text padded with spaces to character 40.

41-48

Network control key

49-56

Network subset control key

57-64

SP control key

65-72

Corporate control key

73-88

IMEI

---

If length of one or more keys exceed 8 digits the message in TP-UD field shall be extended with additional 32 digits as follows:

Character

Description

---

89-96

Network control key extension

97-104

Network subset control key extension

105-112

SP control key extension

113-120

Corporate control key extension

---

The key shall be divided into main and extension fields as follows:

• If key length is equal to or less than 8 digits, the key value shall be coded to the main field as specified above, and the corresponding extension field shall be encoded as "FFFFFFFF".
• If key length is more than 8 digits, the 8 most significant digits shall be coded to the main field and the remaining digits shall be coded to the extension field. If the length of the key is less than 16 digits, then extension field shall be populated from the beginning of the extension field, and each of the remaining digits shall be encoded as "F".

If an ME receives a key value with "F" padding, it shall ignore the "F" padding characters and only use the received key part.

As the IMEI is 15 digits long (see TS 23.003), the sixteenth digit present here is ignored by the ME during the de-personalization procedure and should be set to zero.

For the IMEI and each control key, the most significant digit is coded first in the string, e.g. character 41 is the most significant digit of NCK.

All characters are coded according to the default alphabet described in TS 23.038.

The string "FFFFFFFF" shall be used in place of a key to indicate that de personalisation of that category is not required.

b)

The acknowledgement to the ME De personalisation Short Message shall be a SMS DELIVER REPORT for RP ACK as described in TS 23.040 [6] with the TP User Data coded according to the default alphabet described in TS 23.038 as below:

Character

Description

---

1-16

IMEI of ME

17

Network personalisation status

18

Network subset personalisation status

19

SP personalisation status

20

Corporate personalisation status

---

As the IMEI is 15 digits long (see TS 23.003), the sixteenth digit present here is ignored by the network during the de-personalization procedure and should be set to zero.

Status codes shall indicate the resulting status of each personalisation category as below.

Status code

Description

---

0

Currently not personalised

1

Permanently not personalised

2

Personalised

3

IMEI mismatch

Other

RFU

---

If the IMEI of the ME does not match the IMEI included in the De personalisation Short Message, then the status of all the personalisation categories shall be coded "IMEI mismatch".

c)

The format for the control keys stored on the SIM is specified in GSM 11.11 [8]. The format for the control keys stored on the USIM is specified in TS 31.102.

For the purposes of this TS, a SIM/USIM is said to support this feature if it is marked as both allocated and activated in the SIM/USIM service table.

The value "FF" is the default value to be used when no meaningful value for a key is represented. This value shall not be allocated as a key value.

$  Change history  Word‑p. 23

---