4.5 Contents of Efs at the TELECOM level
31.1023GPPCharacteristics of the Universal Subscriber Identity Module (USIM) applicationRelease 17TS
The Efs in the Dedicated File DFTELECOM contain service related information.
4.5.1 EFADN (Abbreviated dialling numbers)
In case of a present GSM application on the UICC the first EFADN (i.e. reflected by the first record in EFPBR) of the DFPHONEBOOK is mapped (with an identifier equal to ‘6F3A’) to DFTELECOM to ensure backwards compatibility.
A 3GPP ME shall not access this file. The information is accessible for a 3GPP ME in EFADN under DFPHONEBOOK.
4.5.2 EFEXT1 (Extension1)
In case of a present GSM application on the UICC the first EFEXT1 (i.e. reflected by the first record in EFPBR) of the DFPHONEBOOK is mapped (with an identifier equal to ‘6F4A’) to DFTELECOM to ensure backwards compatibility.
A 3GPP ME shall not access this file. The information is accessible for a 3GPP ME in EFEXT1 under DFPHONEBOOK.
4.5.3 EFECCP (Extended Capability Configuration Parameter)
In case of a present GSM application on the UICC the first EFCCP1 (i.e. reflected by the first record in EFPBR) of the DFPHONEBOOK is mapped (with an identifier equal to ‘6F4F’) to DFTELECOM to ensure backwards compatibility. There shall not be any EFCCP (with a file-id of ‘6F3D’) under DFTELECOM because otherwise a GSM terminal could create inconsistencies within the phonebook.
A 3GPP ME shall not access this file. The information is accessible for a 3GPP ME in EFCCP1 under DFPHONEBOOK.
4.5.4 EFSUME (SetUpMenu Elements)
This File is defined in ETSI TS 102 222 [39], and has the file identifier ‘6F54’.
4.5.5 EFARR (Access Rule Reference)
This EF contains the access rules for files located under the DFTELECOM in the UICC. If the security attribute tag ‘8B’ is indicated in the FCP it contains a reference to a record in this file.
Structure of EFARR at DFTelecom-level
|
Identifier: ‘6F06’ |
Structure: Linear fixed |
Mandatory |
||||
|
Record length: X bytes |
Update activity: low |
|||||
|
Access Conditions: READ ALW UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to X |
Access Rule TLV data objects |
M |
X bytes |
|||
This EF contains one or more records containing access rule information according to the reference to expanded format as defined in ISO/IEC 7816‑4 [20]. Each record represents an access rule. Unused bytes in the record are set to ‘FF’.
If the card cannot access EFARR, any attempt to access a file with access rules indicated in this EFARR shall not be granted.
4.5.6 EFICE_DN (In Case of Emergency – Dialling Number)
This EF contains one or more records containing number formatted ICE information, according to TS 22.101 [24].
This file shall be deactivated if the user does not wish the ICE information contained in this file to be available and activated if the user wishes the ICE information in this file to be available.
Structure of EFICE_DN at DFTelecom-level
|
Identifier: ‘6FE0’ |
Structure: Linear fixed |
Optional |
|||
|
SFI: Optional |
|||||
|
Record length: X+14 bytes |
Update activity: low |
||||
|
Access Conditions: READ ALWAYS UPDATE PIN DEACTIVATE PIN or Issuer Specified PIN (see Note) ACTIVATE PIN or Issuer Specified PIN (see Note) |
|||||
|
Bytes |
Description |
M/O |
Length |
||
|
1 to X |
Alpha Identifier |
O |
X bytes |
||
|
X+1 |
Length of BCD number/SSC contents |
M |
1 byte |
||
|
X+2 |
TON and NPI |
M |
1 byte |
||
|
X+3 to X+12 |
Dialling Number/SSC String |
M |
10 bytes |
||
|
X+13 |
Capability/Configuration1 Record Identifier |
M |
1 byte |
||
|
X+14 |
Extension1 Record Identifier |
M |
1 byte |
||
|
Note: The Issuer Specified PIN is a PIN with a global key reference (see TS 31.101 [11]) specified by the card Issuer. |
|||||
Coding:
As for EFADN
4.5.7 EFICE_FF (In Case of Emergency – Free Format)
This EF contains one or more records containing free formatted ICE information, according to TS 22.101 [24].
This file shall be deactivated if the user does not wish the ICE information contained in this file to be available and activated if the user wishes the ICE information in this file to be available.
Structure of EFICE_FF at DFTelecom-level
|
Identifier: ‘6FE1’ |
Structure: Linear fixed |
Optional |
|||
|
SFI: Optional |
|||||
|
Record length: >=X+Y bytes |
Update activity: low |
||||
|
Access Conditions: READ ALWAYS UPDATE PIN DEACTIVATE PIN or Issuer Specified PIN (see Note) ACTIVATE PIN or Issuer Specified PIN (see Note) |
|||||
|
Bytes |
Description |
M/O |
Length |
||
|
1 to X |
ICE Free Format Label TLV |
M |
X bytes |
||
|
X+1 to X+Y |
ICE Free Format Content TLV |
M |
Y bytes |
||
|
Note: The Issuer Specified PIN is a PIN with a global key reference (see TS 31.101 [11]) specified by the card Issuer. |
|||||
– ICE Free Format Label TLV
Contents:
This TLV contains a label that summarises the type of content that is contained in the associated ICE Free Format Content TLV (e.g. "medical alert information").
Coding:
ICE Free Format Label TLV is coded as follows:
Tag value is ’80’
Length is coded according to ISO/IEC 8825-1 [35].
Value is as for value part of the text string TLV in 3GPP TS 31.111 [12]. If the length is 0 and there is no value part then the terminal shall interpret this as no label is used.
– ICE Free Format Content TLV
Contents:
This TLV contains a ICE Free Format Content (e.g. "Allergy to work").
Coding:
ICE Free Format Content TLV is coded as follows:
Tag value is ’81’
Length is coded according to ISO/IEC 8825-1 [35].
Value is as for value part of the text string TLV in 3GPP TS 31.111 [12]. If the length is 0 and there is no value part then the terminal shall interpret this as no label is used.
Padding: unused bytes in each record shall be set to ‘FF’.
4.5.8 EFRMA (Remote Management Actions)
This File is defined in ETSI TS 102 222 [39], and has the file identifier ‘6F53’.
4.5.9 EFPSISMSC (Public Service Identity of the SM-SC)
This file shall be present if and only if service n°12 and n°91 are "available".
This EF contains the Public Service Identity of the SM-SC (either a SIP URI or tel URI) that the ME shall use to submit SMS over IP as defined in 24.341 [55].
|
Identifier: ‘6FE5’ |
Structure: linear fixed |
Optional |
||||
|
File size: X bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE PIN DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to X |
URI TLV data object |
M |
X bytes |
|||
‑ URI
Contents:
– SIP URI or tel URI of the Public Service Identity of the SM-SC.
Coding:
– For contents and syntax of URI TLV data object values see IETF RFC 3261 [56]. The URI shall be encoded to an octet string according to UTF-8 encoding rules as specified in IETF RFC 3629 [57]. The tag value of the URI TLV data object shall be ’80’.