A.4 Over‑the‑air de‑personalisation
22.0223GPPMobile functionality specificationPersonalisation of Mobile Equipment (ME)Release 17TS
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 [6]. 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:
|
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".
NOTE: If the key value is "12345678901234", then the main field value will contain the string "12345678" and the extension field "901234FF".
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 [3]), 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 [5].
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 [5] 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 [3]), 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 [9].
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.
Annex B (informative):
Change history
|
Change history |
|||||||||
|
TSG SA# |
SA Doc. |
CR |
Rev |
Rel |
Cat |
Subject/Comment |
Old |
New |
WI |
|
SP-16 |
SP-020339 |
004 |
– |
Rel-4 |
A |
IMEI format for de-personalisation over the air |
4.0.0 |
4.1.0 |
SEC1 |
|
SP-17 |
– |
– |
– |
– |
– |
Upgrade to Release 5 |
4.1.0 |
5.0.0 |
– |
|
SP-26 |
– |
– |
– |
– |
– |
Upgrade to Release 6 |
5.0.0 |
6.0.0 |
– |
|
SP-36 |
– |
– |
– |
– |
– |
Upgrade to Release 7 |
6.0.0 |
7.0.0 |
– |
|
SP-39 |
SP-080194 |
005 |
3 |
Rel-7 |
F |
Control key length increase in OTA de-personalisation message |
7.0.0 |
7.1.0 |
TEI7 |
|
SP-40 |
SP-080419 |
006 |
1 |
Rel-7 |
F |
Completion of sentence concerning control key length increase in OTA de-personalisation message |
7.1.0 |
7.2.0 |
TEI7 |
|
SP-42 |
– |
– |
– |
– |
– |
Upgrade to Release 8 |
7.0.0 |
8.0.0 |
– |
|
SP-46 |
– |
– |
– |
– |
– |
Upgrade to Release 9 |
8.0.0 |
9.0.0 |
– |
|
SP-48 |
SP-100397 |
008 |
– |
Rel-9 |
A |
Correction of Reference |
9.0.0 |
9.1.0 |
TEI8 |
|
2011-03 |
– |
– |
– |
– |
– |
Update to Rel-10 version (MCC) |
9.1.0 |
10.0.0 |
|
|
2012-09 |
– |
– |
– |
– |
– |
Update to Rel-11 version (MCC) |
10.0.0 |
11.0.0 |
|
|
2014-10 |
– |
– |
– |
– |
– |
Update to Rel-12 version (MCC) |
11.0.0 |
12.0.0 |
|
|
2015-12 |
Update to Rel-13 version (MCC) |
12.0.0 |
13.0.0 |
||||||
|
2017-03 |
– |
– |
– |
– |
– |
Updated to Rel-14 by MCC |
13.0.0 |
14.0.0 |
|
|
2018-06 |
– |
– |
– |
– |
– |
Updated to Rel-15 by MCC |
14.0.0 |
15.0.0 |
|
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2020-07 |
SA#88e |
– |
– |
– |
– |
Updated to Rel-16 by MCC |
16.0.0 |
|
2022-03 |
SA#95e |
– |
– |
– |
– |
Updated to Rel-17 by MCC |
17.0.0 |