If service
No. 13 is
"available", this file shall be present.
This EF contains the total number of units for both the current call and the preceding calls.
Accumulated count of units
If a GSM application is present on the UICC and the ACM value is to be shared between the GSM and the USIM application this file shall be shared between the two applications.
If service
No. 17 is
"available", this file shall be present.
This EF contains identifiers for particular USIM-ME associations. It can be used to identify a group of USIMs for a particular application.
If service
No. 18 is
"available", this file shall be present.
This EF contains identifiers for particular USIM-ME associations. It can be used to identify a group of USIMs for a particular application.
If service
No. 19 is
"available", this file shall be present.
This EF contains the service provider name in text format and appropriate requirements for the display by the ME. The service provider name may also be provided in a graphical format in
EFSPNI. The ME shall use the service provider name in the text format or the graphical format or both to display the service provider name according to the rules defined in
clause 4.2.88.
If service
No. 13 is
"available", this file shall be present.
This EF contains the Price per Unit and Currency Table (PUCT). The PUCT is Advice of Charge related information which may be used by the ME in conjunction with
EFACM to compute the cost of calls in the currency chosen by the subscriber, as specified in
TS 22.024.
Contents:
the alpha-identifier of the currency code.
Coding:
bytes 1, 2 and 3 are the respective first, second and third character of the alpha identifier. This alpha-tagging shall use the SMS default 7-bit coded alphabet as defined in
TS 23.038 with bit 8 set to 0.
Contents:
price per unit expressed in the currency coded by bytes 1 to 3.
Coding:
byte 4 and bits b1 to b4 of byte 5 represent the Elementary Price per Unit (EPPU) in the currency coded by bytes 1 to 3. Bits b5 to b8 of byte 5 are the decimal logarithm of the multiplicative factor represented by the absolute value of its decimal logarithm (EX) and the sign of EX, which is coded 0 for a positive sign and 1 for a negative sign.
Byte 4:
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
211 |
210 |
29 |
28 |
27 |
26 |
25 |
24 |
of EPPU |
Byte 5:
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
22 of Abs(EX) |
21 of Abs(EX) |
20 of Abs(EX) |
Sign of EX |
23 |
22 |
21 |
20 |
|
of EPPU |
-
The computation of the price per unit value is made by the ME in compliance with TS 22.024 by the following formula:
price per unit = EPPU * 10EX.
-
The price has to be understood as expressed in the coded currency.
If a GSM application is present on the UICC and the PUCT information is to be shared between the GSM and the USIM application, then this file shall be shared between the two applications.
If service
No. 15 is
"available", this file shall be present.
This EF contains the Message Identifier Parameters which specify the type of content of the cell broadcast messages that the subscriber wishes the UE to accept.
Any number of CB Message Identifier Parameters may be stored in the USIM. No order of priority is applicable.
Cell Broadcast Message Identifier
Coding:
-
as in TS 23.041, "Message Format on BTS-MS Interface - Message Identifier";
-
values listed show the types of message which shall be accepted by the UE;
-
unused entries shall be set to 'FF FF'.
This EF contains the assigned access control class(es). The access control class is a parameter to control the access attempts. 15 classes are split into 10 classes randomly allocated to normal subscribers and 5 classes allocated to specific high priority users. For more information see
TS 22.011.
This EF contains the coding for n Forbidden PLMNs (FPLMN). It is read by the ME as part of the USIM initialization procedure and indicates PLMNs which the UE shall not automatically attempt to access.
A PLMN is written to the EF if a network rejects a Location Update with the cause
"PLMN not allowed". The ME shall manage the list as follows.
When n FPLMNs are held in the EF, and rejection of a further PLMN is received by the ME from the network, the ME shall modify the EF using the UPDATE command. This new PLMN shall be stored in the nth position, and the existing list
"shifted" causing the previous contents of the first position to be lost.
When less than n FPLMNs exist in the EF, storage of an additional FPLMN shall not cause any existing FPLMN to be lost.
Dependent upon procedures used to manage storage and deletion of FPLMNs in the EF, it is possible, when less than n FPLMNs exist in the EF, for
'FFFFFF' to occur in any position. The ME shall analyse all the EF for FPLMNs in any position, and not regard
'FFFFFF' as a termination of valid data.