Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 31.102  Word version:  18.3.0

Top   Top   Up   Prev   Next
0…   3…   4…   4.2.9…   4.2.17…   4.2.26…   4.2.34…   4.2.44…   4.2.52…   4.2.60…   4.2.68…   4.2.76…   4.2.85…   4.2.93…   4.2.101…   4.2.107…   4.3…   4.4.2…   4.4.2.4…   4.4.3…   4.4.4…   4.4.5…   4.4.6…   4.4.8…   4.4.8.7…   4.4.9…   4.4.11…   4.4.11.7…   4.4.11.17…   4.4.12…   4.5…   4.6…   4.7   5…   5.2…   5.3…   5.4…   5.9…   6…   7…   7.1.2…   7.3…   A   B…   D   E…   G   H…   I…   L…   M… 
4.5 Contents of EFs at the TELECOM level  4.5.1 EFADN (Abbreviated dialling numbers)  4.5.2 EFEXT1 (Extension1)  4.5.3 EFECCP (Extended Capability Configuration Parameter)  4.5.4 EFSUME (SetUpMenu Elements)  4.5.5 EFARR (Access Rule Reference)  4.5.6 EFICE_DN (In Case of Emergency - Dialling Number)  4.5.7 EFICE_FF (In Case of Emergency - Free Format)  4.5.8 EFRMA (Remote Management Actions)  4.5.9 EFPSISMSC (Public Service Identity of the SM-SC) 
...

 

4.5  Contents of EFs at the TELECOM level  p. 251

The EFs in the Dedicated File DFTELECOM contain service related information.

4.5.1  EFADN (Abbreviated dialling numbers)  p. 251

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.
Up

4.5.2  EFEXT1 (Extension1)  p. 251

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.
Up

4.5.3  EFECCP (Extended Capability Configuration Parameter)  p. 251

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.
Up

4.5.4  EFSUME (SetUpMenu Elements)  p. 251

This File is defined in ETSI TS 102 222 [39], and has the file identifier '6F54'.

4.5.5  EFARR (Access Rule Reference)  p. 251

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 fixedMandatory
Record length: X bytesUpdate activity: low
Access Conditions:
READALW
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XAccess Rule TLV data objectsMX 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.
Up

4.5.6  EFICE_DN (In Case of Emergency - Dialling Number) |R8|  p. 252

This EF contains one or more records containing number formatted ICE information, according to TS 22.101.
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 fixedOptional
SFI: Optional
Record length: X+14 bytesUpdate activity: low
Access Conditions:
READALWAYS
UPDATEPIN
DEACTIVATEPIN or Issuer Specified PIN (see Note)
ACTIVATEPIN or Issuer Specified PIN (see Note)
Bytes Description M/O Length
1 to XAlpha IdentifierOX bytes
X+1Length of BCD number/SSC contentsM1 byte
X+2TON and NPIM1 byte
X+3 to X+12Dialling Number/SSC StringM10 bytes
X+13Capability/Configuration1 Record IdentifierM1 byte
X+14Extension1 Record IdentifierM1 byte
Coding:
As for EFADN
Up

4.5.7  EFICE_FF (In Case of Emergency - Free Format) |R8|  p. 252

This EF contains one or more records containing free formatted ICE information, according to TS 22.101.
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 fixedOptional
SFI: Optional
Record length: ≥X+Y bytesUpdate activity: low
Access Conditions:
READALWAYS
UPDATEPIN
DEACTIVATEPIN or Issuer Specified PIN (see Note)
ACTIVATEPIN or Issuer Specified PIN (see Note)
Bytes Description M/O Length
1 to XICE Free Format Label TLVMX bytes
X+1 to X+YICE Free Format Content TLVMY bytes
NOTE:
The Issuer Specified PIN is a PIN with a global key reference (see TS 31.101) 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 TS 31.111. 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 TS 31.111. 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'.
Up

4.5.8  EFRMA (Remote Management Actions) |R8|  p. 253

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) |R9|  p. 254

This file shall be present if and only if service No. 12 and No. 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 TS 24.341.
Identifier: '6FE5'Structure: linear fixedOptional
File size: X bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEPIN
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XURI TLV data objectMX 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 RFC 3261. The URI shall be encoded to an octet string according to UTF-8 encoding rules as specified in RFC 3629. The tag value of the URI TLV data object shall be '80'.
Up

Up   Top   ToC