22.0223GPPMobile functionality specificationPersonalisation of Mobile Equipment (ME)Release 17TS
As an optional ME feature, the ME may be de‑personalised over‑the‑air (OTA) by the network. The network, network subset, SP and corporate categories may be de‑personalised in this way. More than one category may be de‑personalised at the same time. The process results in the relevant personalisation indicator(s) being set to "off". The ME must be registered on a network.
Two OTA methods are defined both of which use MT SMS‑PP messages. With the first method, the IMEI of the ME to be de‑personalised and the Control Key(s) of the personalisation categories to be de‑personalised are sent directly to the ME. The ME performs checks on both the IMEI and the key values and the outcome of the attempted de‑personalisation(s) is acknowledged to the network.
With the second method, the keys of the personalisation categories to be de‑personalised are sent to the ME via the SIM/USIM. The IMEI is not included and the de‑personalisation process only checks the keys. The outcome of the attempted de‑personalisation(s) is acknowledged to the network.
The network de‑personalises the ME by one of the following methods:
(i) SMS‑PP, ME‑specific:
a) A point‑to‑point SMS message is sent by the network to the MS oe UE, the message being marked as being destined for the ME only and for the purposes of ME de‑personalisation (see TS 23.040 ). The User Data of the SMS contains the de‑personalisation key(s) and the IMEI (see annex A.4). If the ME supports the feature, then it shall not display the data on the ME.
b) The ME compares the values of the IMEI and the key(s) sent by the network with the corresponding values stored in the ME. If they are the same, the relevant personalisation indicator(s) is (are) set to "off".
If the IMEI values differ, the personalisation status of all categories shall be left unchanged.
If any key values differ, the corresponding personalisation status shall be left unchanged.
c) The MS or UE sends a SMS acknowledgement to the network indicating the result of the attempted de‑personalisation process (see annex A.4).
(ii) SMS‑PP Data Download:
a) A SMS message is sent by the network to the IM updating the EFDCK. In the GSM system, it is done by using the SMS‑PP SIM Data Download of the SIM Tool Kit (see GSM 11.14 ). In the 3G system, it is done by using the SMS-PP Data Download of the USIM Toolkit (see TS 31.111 ).
b) The SIM/USIM causes the ME to send an SMS acknowledgement to the network, as a result of the terminal response to the ENVELOPE command.
c) The SIM/USIM shall issue a REFRESH command to instruct the ME to perform an initialisation procedure. During the initialisation procedure the ME reads the de‑personalisation key field(s) from EFDCK stored in the SIM/USIM after performing all personalisation checks.
d) For each control key in EFDCK which is empty (set to default), the corresponding personalisation status shall be left unchanged.
e) For each control key in the EFDCK which is not the same as the corresponding stored key, the personalisation status shall be left unchanged.
f) For each control key in EFDCK which is the same as the one stored in the ME, the corresponding personalisation indicator is set to "off".
g) All the keys in the EFDCK are reset to the default value by the ME.