4.2.99 EF_SDNURI (Service Dialling Numbers URI)

31.1023GPPCharacteristics of the Universal Subscriber Identity Module (USIM) applicationRelease 17TS

If service n° 4 and service n° 99 are "available", this file may be present.

This EF contains a list of SDN stored in URI address format. It may also contain an associated alpha‑tagging. If the service n°112 is available this file will contain the eCall test and reconfiguration URIs that are used by an UE in eCall and normal service mode.

Structure of EF_SDNURI

Identifier: ‘6FEF’		Structure: linear fixed			Optional
Record length: X+Y bytes			Update activity: low
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM
Bytes	Description			M/O		Length
1 to X	URI Address			M		X bytes
X+1 to X+Y	Alpha Identifier			O		Y bytes

‑ URI Address.

Content:
The URI Address associated to the referenced file Record number.

Coding:
Same as URI TLV data object in EF_IMPU defined in TS 31.103 [64].

‑ Alpha Identifier.

Contents:

Alpha‑tagging of the associated dialling number.

Coding:

this alpha‑tagging shall use either:

– the SMS default 7‑bit coded alphabet as defined in TS 23.038 [5] with bit 8 set to 0. The alpha identifier shall be left justified. Unused bytes shall be set to ‘FF’.

or:

– one of the UCS2 coded options as defined in the annex of TS 31.101 [11].

If SDN is enabled, the ME shall perform SDN procedure using destination addresses which are in EF_SDNURI or in EF_SDN entries, following the same principle as defined in the Service Dialling Numbers description in TS 22.101 [24] applied to URI addresses.

NOTE: The value of Y (the number of bytes in the alpha‑identifier) may be different to the length denoted X in EF_SDN.

4.2.100 EF_IAL (IMEI(SV) Allowed Lists)

The file EF_IAL stores ranges of values of IMEI(SV) to which the USIM is authorized to be paired as defined in this specification.

This file shall be present if USAT Application Pairing is supported as defined in this specification.

This file shall contain at least one IMEI(SV) range of values to which the USIM is authorized to be paired.

Identifier: ‘6FF0’		Structure: linear fixed			Optional
Record length: X+2 bytes (X>=16)			Update activity: low
Access Conditions: READ ADM UPDATE ADM ACTIVATE ADM DEACTIVATE ADM
Bytes	Description			M/O		Length
1 to X+2	IMEI or IMEISV range TLV object			M		X+2 bytes

– IMEI(SV) range of values TLV object.

The content and coding is defined below, where IMEI and IMEISV are defined in 3GPP TS 23.003[25]:

Coding of the IMEI Range TLV objects

Length	Description	Status
1 byte	Tag of Range of IMEI values: ’80’	M
1 byte	Length	M
X bytes	IMEI range of values that the USIM is authorized to be paired to (Detail 1)	C

Coding of the IMEISV Range TLV objects

Length	Description	Status
1 byte	Tag of Range of IMEISV values: ’81’	M
1 byte	Length	M
X bytes	IMEISV range of values that the USIM is authorized to be paired to (Detail 1)	C

Detail 1:

– Following the Length of the TLV, the range is defined as follow: [lower value][higher value].

– The authorized values of IMEI or IMEISV in an authorized range of values include the lower and higher values of the specified range.

– To define an authorized individual IMEI or IMEISV, the lower value and the higher value of a range shall both be equal to the value of the authorized IMEI or IMEISV.

– For an IMEI, the Check Digit is not considered in the evaluation

– For an IMEISV, the TAC|SNR part and the SVN part may be evaluated separately

Coding:

– IMEI and IMEISV coding is defined in 3GPP TS 23.003 [25] and 3GPP TS 24.008 [9]

– Unused nibble (IMEI) is set to ‘F’

Unused bytes shall be set to ‘FF’.

UICC OTA mechanism is used to update the file EF_IAL stored in the USIM. This mechanism provides dynamic management of the pairing to change the allowed combinations of USIM and MTC ME(s) by adding or removing authorized IMEI(SV) ranges in the file EF_IAL.