4.2.97 EFFDNURI (Fixed Dialling Numbers URI)
31.1023GPPCharacteristics of the Universal Subscriber Identity Module (USIM) applicationRelease 17TS
If service n° 2 and service n° 99 are "available", this file may be present.
This EF contains a list of FDN stored in URI address format. It may also contain an associated alpha‑tagging.
Structure of EFFDNURI
|
Identifier: ‘6FED’ |
Structure: linear fixed |
Optional |
||||
|
Record length: X+Y bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE PIN2 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 EFIMPU 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 FDN is enabled, the ME shall only allow outgoing calls using destination addresses which are in EFFDNURI, in addition to the EFFDN entries, following the same principle as defined in the Fixed Number Dialling description in TS 22.101 [24] applied to URI addresses.
The EFFDNURI shall be enforced:
– If the dialling number introduced by the user is an URI
– Or if the dialling number has been stored in the UE as a URI
NOTE: The value of Y (the number of bytes in the alpha‑identifier) may be different to the length denoted X in EFFDN.