Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 31.102  Word version:  18.5.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.6.5…   4.6.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.2.44  EFBDN (Barred Dialling Numbers)p. 63

If service No. 6 is "available", this file shall be present.
This EF contains Barred Dialling Numbers (BDN) and/or Supplementary Service Control strings (SSC). In addition it contains identifiers of associated network/bearer capabilities and identifiers of extension records. It may also contain an associated alpha-tagging. As the BDN service relies on the Call Control feature, BDN shall only be available if Call Control is available. If this file is present in the USIM, the Enabled Services Table (EFEST) shall also be present.
Identifier: '6F4D'Structure: linear fixedOptional
Record length: X+15 bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEPIN2
DEACTIVATEADM
ACTIVATEADM
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/Configuration2 Record IdentifierM1 byte
X+14Extension4 Record IdentifierM1 byte
X+15Comparison Method PointerM1 byte
For contents and coding of all data items, except for the Comparison Method Pointer, see the respective data items of EFADN, with the exception that extension records are stored in the EFEXT4 and capability/configuration parameters are stored in EFCCP2. The Comparison Method Pointer refers to a record number in EFCMI.
Up

4.2.45  EFEXT4 (Extension4)p. 64

If service No. 7 is "available", this file shall be present.
This EF contains extension data of a BDN/SSC.
Identifier: '6F55'Structure: linear fixedOptional
Record length: 13 bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEPIN2
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1Record typeM1 byte
2 to 12Extension dataM11 bytes
13IdentifierM1 byte
For contents and coding see clause 4.4.2.4 EFEXT1.
Up

4.2.46  EFCMI (Comparison Method Information)p. 63

If service No. 6 is "available", this file shall be present.
This EF contains the list of Comparison Method Identifiers and alpha-tagging associated with BDN entries (see EFBDN).
Identifier: '6F58'Structure: linear fixedOptional
Record length: X+1 bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XAlpha IdentifierMX bytes
X+1Comparison Method IdentifierM1 byte
Alpha Identifier
Contents:
Alpha-tagging of the associated Comparison Method Identifier.
Coding:
Same as the alpha identifier in EFADN.
Comparison Method Identifier
Contents:
This byte describes the comparison method which is associated with a BDN record. Its interpretation is not specified but it shall be defined by the card issuers implementing the BDN feature on their USIMs.
Coding:
Binary; values from 0 to 255 are allowed.
The default coding 255 is reserved for empty field.
Up

4.2.47  EFEST (Enabled Services Table)p. 65

If service No. 2, No. 6, No. 34 or No. 35 is "available" (as indicated in the USIM Service Table), this file shall be present.
This EF indicates which services are enabled. If a service is not indicated as enabled in this table, the ME shall not select the service.
Identifier: '6F56'Structure: transparentOptional
SFI: '05'
File size: X bytes, (X ≥ 1)Update activity: low
Access Conditions:
READPIN
UPDATEPIN2
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1Services No. 1 to No. 8M1 byte
2Services No. 9 to No. 16O1 byte
etc.
XServices No. (8X-7) to No. (8X)O1 byte
Services
Contents
Service No. 1
Fixed Dialling Numbers (FDN)
Service No. 2
Barred Dialling Numbers (BDN)
Service No. 3
APN Control List (ACL)
The EF shall contain at least one byte. Further bytes may be included, but if the EF includes an optional byte, then the EF shall also contain all bytes before that byte. Other services are possible in the future. The coding falls under the responsibility of the 3GPP.
Coding:
  • 1 bit is used to code each service:
  • bit = 1: service activated;
  • bit = 0: service deactivated.
  • Unused bits shall be set to '0'.
A service which is listed in this table is enabled if it is indicated as available in the USIM Service Table (UST) and indicated as activated in the Enabled Services Tables (EST) otherwise this service is, either not available or disabled.
First byte:
b8 b7 b6 b5 b4 b3 b2 b1
Service No. 8 Service No. 7 Service No. 6 Service No. 5 Service No. 4 Service No. 3 Service No. 2 Service No. 1
 
etc.
Up

4.2.48  EFACL (Access Point Name Control List)p. 65

If service No. 35 is "available", this file shall be present.
This EF contains the list of allowed APNs (Access Point Names) or DNNs. If this file is present in the USIM, the Enabled Services Table (EFEST) shall also be present.
Identifier: '6F57'Structure: transparentOptional
File size: X bytes (X>1)Update activity: low
Access Conditions:
READPIN
UPDATEPIN2
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1Number of APNs/DNNsM1 byte
2 to XAPN/DNN TLVsMX-1 byte
For contents and coding of APN/DNN-TLV values see TS 23.003. The tag value of the APN/DNN-TLV shall be 'DD'. "Network provided APN/DNN" is coded with a TLV object of length zero.
Up

4.2.49  EFDCK (Depersonalisation Control Keys)p. 66

If service No. 36 is "available", this file shall be present.
This EF provides storage for the de-personalization control keys associated with the OTA de-personalization cycle of TS 22.022.
Identifier: '6F2C'Structure: transparentOptional
File Size: 16 bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEPIN
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to 48 digits of network de-personalization control keyM4 bytes
5 to 88 digits of network subset de-personalization control keyM4 bytes
9 to 128 digits of service provider de-personalization control keyM4 bytes
13 to 168 digits of corporate de-personalization control keyM4 bytes
Empty control key bytes shall be coded 'FFFFFFFF'.
Up

4.2.50  EFCNL (Co-operative Network List)p. 66

If service No. 37 is "available", this file shall be present.
This EF contains the Co-operative Network List for the multiple network personalization services defined in TS 22.022.
Identifier: '6F32'Structure: transparentOptional
File size: 6n bytes, (n ≥ 1)Update activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to 6Element 1 of co-operative net listM6 bytes
6n-5 to 6nElement n of co-operative net listO6 bytes
Co-operative Network List
Contents:
PLMN network subset, service provider ID and corporate ID of co-operative networks.
Coding:
For each 6 byte list element.
Bytes 1 to 3: PLMN (MCC + MNC): according to TS 24.008.
Byte 4:
b8 b7 b6 b5 b4 b3 b2 b1
MS bit of network subset digit 2 LS bit of network subset digit 2 MS bit of network subset digit 1 LS bit of network subset digit 1
 
Byte 5:
b8 b7 b6 b5 b4 b3 b2 b1
MS bit of service provider digit 2 LS bit of service provider digit 2 MS bit of service provider digit 1 LS bit of service provider digit 1
 
Byte 6:
b8 b7 b6 b5 b4 b3 b2 b1
MS bit of corporate digit 2 LS bit of corporate digit 2 MS bit of corporate digit 1 LS bit of corporate digit 1
 
  • Empty fields shall be coded with 'FF'.
  • The end of the list is delimited by the first MCC field coded 'FFF'.
Up

4.2.51  EFSTART-HFN (Initialisation values for Hyperframe number)p. 68

This EF contains the values of STARTCS and STARTPS of the bearers that were protected by the keys in EFKeys or EFKeysPS at release of the last CS or PS RRC connection. These values are used to control the lifetime of the keys (see TS 33.102).
Identifier: '6F5B'Structure: transparentMandatory
SFI: '0F'
File size: 6 bytesUpdate activity: high
Access Conditions:
READPIN
UPDATEPIN
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to 3STARTCSM3 bytes
4 to 6STARTPSM3 bytes
STARTCS
Contents:
Initialisation value for Hyperframe number - CS domain.
Coding:
The LSB of STARTCS is stored in bit 1 of byte 3. Unused nibbles are set to 'F'.
STARTPS
Contents:
Initialisation value for Hyperframe number - PS domain.
Coding:
As for STARTCS.
Up

Up   Top   ToC