9 USIM service handling
31.1213GPPRelease 16TSUICC-terminal interfaceUniversal Subscriber Identity Module (USIM) application test specification
9.1 Access Point Name Control List handling
9.1.1 Access Point Name Control List handling for terminals supporting ACL
9.1.1.1 Definition and applicability
This EFACL contains the list of allowed APNs (Access Point Names).When the APN Control List service is enabled, the ME shall check that the entire APN of any PDP context is listed in EFACL before requesting this PDP context activation from the network. If the APN is not present in EFACL, the ME shall not request the corresponding PDP context activation from the network.
9.1.1.2 Conformance requirement
The terminal shall support the APN Control List service as defined in TS 31.102 [4], clauses 5.1.1.2 and 5.3.14.
Reference:
– TS 31.102 [4], clauses 4.2.8, 4.2.48, 5.1.1.2 and 5.3.14;
– TS 23.060 [25], clause 9.2.
9.1.1.3 Test purpose
1) To verify that the terminal takes into account the status of the APN Control List service as indicated in EFUST and EFEST.
2) To verify that the terminal checks that the entire APN of any PDP context is listed in EFACL before requesting this PDP context activation from the network if the ACL service is enabled.
3) To verify that the terminal does not request the corresponding PDP context activation from the network if the ACL service is enabled and the APN is not present in EFACL.
9.1.1.4 Method of test
9.1.1.4.1 Initial conditions
The terminal is connected to the USIM Simulator and the (U)SS.
The default USIM is used with the following exceptions:
The APN Control List (ACL) shall be allocated and activated in the USIM Service Table and enabled in the Enabled Service Table.
EFACL shall be present with the following values:
EFACL (Access Point Control List)
Logically: Number of available bytes: 64
Number of APNs: 3
1st APN: test.test
2nd APN: 3gpp.test
3rd APN: 2gpp.test
|
Byte: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Coding: |
03 |
DD |
0A |
04 |
74 |
65 |
73 |
74 |
04 |
74 |
65 |
73 |
|
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
B19 |
B20 |
B21 |
B22 |
B23 |
B24 |
|
|
74 |
DD |
0A |
04 |
33 |
67 |
70 |
70 |
04 |
74 |
65 |
73 |
|
|
B25 |
B26 |
B27 |
B28 |
B29 |
B30 |
B31 |
B32 |
B33 |
B34 |
B35 |
B36 |
|
|
74 |
DD |
0A |
04 |
32 |
67 |
70 |
70 |
04 |
74 |
65 |
73 |
|
|
B37 |
B38 |
… |
B64 |
|||||||||
|
74 |
FF |
… |
FF |
9.1.1.4.2 Procedure
a) The terminal is switched on and the USIM application shall be activated.
b) The user shall request a PDP context activation to "1gpp.test".
c) The user shall request a PDP context activation to "3gpp.test".
d) The user shall deactivate the PDP context.
e) The user shall disable the APN Control List service. When prompted to enter PIN2, the user shall present the correct PIN2 value.
f) The user shall request a PDP context activation to "1gpp.test".
g) The user shall deactivate the PDP context and shall switch the terminal off and then switch on again.
h) The user shall enable the APN Control List service. When prompted to enter PIN2, the user shall present the correct PIN2 value.
i) The user shall request a PDP context activation to "1ppp.net".
j) The terminal is switched off and on.
k) The user shall add the APN "1ppp.net" to the APN Control List. When prompted to enter PIN2, the user shall present the correct PIN2 value.
l) The user shall request a PDP context activation to "1ppp.net".
m) The user shall deactivate the PDP context and switch off the terminal.
9.1.1.5 Acceptance criteria
1) After step a) the terminal shall have activated the USIM application, shall have read the status of the ACL service in EFUST and EFEST and be in updated idle mode on the (U)SS.
2) The terminal shall have not requested a PDP context activation in step b).
3) After step c) the PDP context shall have been activated.
4) After step d) the PDP context shall have been deactivated.
5) After step e) the APN Control List service shall have been set to disabled in EFEST.
6) After step f) the PDP context shall have been activated.
7) After step g) the PDP context shall have been deactivated.
8) After step h) the APN Control List service shall have been set to enabled in EFEST.
9) The terminal shall not have requested a PDP context activation in step i).
10) After step k) the APN "1ppp.net" shall have been added to the APN Control List in EFACL.
11) After step l) the PDP context shall have been activated.
9.1.2 Network provided APN handling for terminals supporting ACL
9.1.2.1 Definition and applicability
This EFACL contains the list of allowed APNs (Access Point Names).When the APN Control List service is enabled, the ME shall check that the entire APN of any PDP context is listed in EFACL before requesting this PDP context activation from the network. If the APN is not present in EFACL, the ME shall not request the corresponding PDP context activation from the network.
In the case that the APN Control List is enabled and no APN is indicated in the PDP context request, indicating that a network provided APN is to be used, then the ME shall only request the PDP context activation if "network provided APN" is contained within EFACL.
9.1.2.2 Conformance requirement
The terminal shall support the APN Control List service as defined in TS 31.102 [4], clauses 5.1.1.2 and 5.3.14.
Reference:
– TS 31.102 [4], clauses 4.2.8, 4.2.48, 5.1.1.2 and 5.3.14;
– TS 23.060 [25], clause 9.2.
9.1.2.3 Test purpose
1) To verify that if ACL is enabled and if no APN is indicated in the PDP context the terminal request the PDP context activation only if "network provided APN" is contained within EFACL.
2) To verify that the user is able to set an APN in EFACL entry to the value "network provided APN".
3) To verify that the minimum set of APN entries in EFACL is ensured when the user deletes APN entries.
9.1.2.4 Method of test
9.1.2.4.1 Initial conditions
The terminal is connected to the USIM Simulator and the (U)SS.
The default USIM is used with the following exceptions:
The APN Control List (ACL) shall be allocated and activated in the USIM Service Table and enabled in the Enabled Service Table.
EFACL shall be present with the following values:
EFACL (Access Point Control List)
Logically: Number of available bytes: 64
Number of APNs: 3
1st APN: test.test
2nd APN: 3gpp.test
3rd APN: 2gpp.test
|
Byte: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Coding: |
03 |
DD |
0A |
04 |
74 |
65 |
73 |
74 |
04 |
74 |
65 |
73 |
|
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
B19 |
B20 |
B21 |
B22 |
B23 |
B24 |
|
|
74 |
DD |
0A |
04 |
33 |
67 |
70 |
70 |
04 |
74 |
65 |
73 |
|
|
B25 |
B26 |
B27 |
B28 |
B29 |
B30 |
B31 |
B32 |
B33 |
B34 |
B35 |
B36 |
|
|
74 |
DD |
0A |
04 |
32 |
67 |
70 |
70 |
04 |
74 |
65 |
73 |
|
|
B37 |
B38 |
… |
B64 |
|||||||||
|
74 |
FF |
… |
FF |
9.1.2.4.2 Procedure
a) The terminal is switched on and the USIM application shall be activated.
b) The user shall add "network provided APN" to the APN Control List in EFACL by using an MMI dependent option in the terminal. When prompted to enter PIN2, the user shall present the correct PIN2 value.
c) The user shall request a PDP context activation to "3gpp.test".
d) The user shall deactivate the PDP context.
e) The user shall request a PDP context activation without indicating an APN.
f) The user shall deactivate the PDP context.
g) The user shall delete "network provided APN" from the APN Control List in EFACL by using an MMI dependent option in the terminal. When prompted to enter PIN2, the user shall present the correct PIN2 value.
h) The user shall request a PDP context activation to "3gpp.test".
i) The user shall deactivate the PDP context.
j) The user shall request a PDP context activation without indicating an APN.
k) The user shall try to delete all APNs from the APN Control List in EFACL by using an MMI dependent option in the terminal. When the terminal indicates that at least one APN entry shall remain, the user shall set this entry to "network provided APN". When prompted to enter PIN2, the user shall present the correct PIN2 value.
l) The user shall switch off the terminal.
9.1.2.5 Acceptance criteria
1) After step a) the terminal shall have activated the USIM application, shall have read the status of the ACL service in EFUST and EFEST and be in updated idle mode on the (U)SS.
2) After step b) EFACL shall contain an entry for "network provided APN".
3) After step c) the PDP context shall have been activated.
4) After step d) the PDP context shall have been deactivated.
5) After step e) the PDP context shall have been activated.
6) After step f) the PDP context shall have been deactivated.
7) After step g) EFACL shall not contain an entry for "network provided APN".
8) After step h) the PDP context shall have been activated.
9) After step i) the PDP context shall have been deactivated.
10) The terminal shall have not requested a PDP context activation in step j).
11) After step k) EFACL shall contain one APN entry with the value "network provided APN" and the corresponding number of APNs in EFACL shall be 1.
9.1.3 Access Point Name Control List handling for terminals not supporting ACL
9.1.3.1 Definition and applicability
This EFACL contains the list of allowed APNs (Access Point Names).When the APN Control List service is enabled, the ME shall check that the entire APN of any PDP context is listed in EFACL before requesting this PDP context activation from the network. If the APN is not present in EFACL, the ME shall not request the corresponding PDP context activation from the network.
If ACL is enabled, an ME which does not support ACL shall not send any APN to the network.
9.1.3.2 Conformance requirement
An ME which does not support ACL shall not send any APN to the network if ACL is enabled.
Reference:
– TS 31.102 [4], 5.1.1.2.
9.1.3.3 Test purpose
To verify that if ACL is enabled, an ME which does not support ACL, does not send any APN to the network to request a PDP context activation.9.1.3.4 Method of test
9.1.3.4 Method of test
9.1.3.4.1 Initial conditions
The terminal is connected to the USIM Simulator and the (U)SS.
The default USIM is used with the following exceptions:
The APN Control List (ACL) shall be allocated and activated in the USIM Service Table and enabled in the Enabled Service Table.
EFACL shall be present with the following values:
EFACL (Access Point Control List)
Logically: Number of available bytes: 64
Number of APNs: 3
1st APN: test.test
2nd APN: 3gpp.test
3rd APN: 2gpp.test
|
Byte: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Coding: |
03 |
DD |
0A |
04 |
74 |
65 |
73 |
74 |
04 |
74 |
65 |
73 |
|
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
B19 |
B20 |
B21 |
B22 |
B23 |
B24 |
|
|
74 |
DD |
0A |
04 |
33 |
67 |
70 |
70 |
04 |
74 |
65 |
73 |
|
|
B25 |
B26 |
B27 |
B28 |
B29 |
B30 |
B31 |
B32 |
B33 |
B34 |
B35 |
B36 |
|
|
74 |
DD |
0A |
04 |
32 |
67 |
70 |
70 |
04 |
74 |
65 |
73 |
|
|
B37 |
B38 |
… |
B64 |
|||||||||
|
74 |
FF |
… |
FF |
9.1.3.4.2 Procedure
a) The terminal is switched on and the USIM application shall be activated.
b) The user shall request a PDP context activation to "3gpp.test".
c) The terminal shall be switched off.
9.1.3.5 Acceptance criteria
1) After step a) the terminal shall have activated the USIM application, shall have read the status of the ACL service in EFUST and EFEST and be in updated idle mode on the (U)SS.
2) The terminal shall not have sent any APN to the network in step b).
9.1.4 Access Point Name Control List handling for terminals supporting ACL connected to E-UTRAN/EPC
9.1.4.1 Definition and applicability
This EFACL contains the list of allowed APNs (Access Point Names). If the APN Control List service is enabled and the ME is to provide an APN as part of attach for PDN connectivity, then the ME shall verify that the APN value is present in the EFACL and if it is not the ME shall not proceed with the attach procedure. If the APN Control List service is enabled and the ME does not indend to provide an APN as part of the attach for PDN connectivity and use a network provided APN, the ME shall not check if "network provided APN" is contained within EFACL.
There is 1:1 mapping between one PDP context and one EPS Bearer.
Some terminals might not support the enablement or the disablement of the APN Control List service or the modification of the APN Control List. In these cases, the test sequence below provides separate branches.
9.1.4.2 Conformance requirement
The terminal shall support the APN Control List service as defined in TS 31.102 [4], clauses 5.1.1.2 and 5.3.14.
Reference:
– TS 31.102 [4], clauses 4.2.8, 4.2.48, 5.1.1.2 and 5.3.14;
– TS 23.060 [25], clause 9.2, 9.2.1A.
9.1.4.3 Test purpose
1) To verify that the terminal takes into account the status of the APN Control List service as indicated in EFUST and EFEST.
2) To verify that the terminal checks that the entire APN of any EPS Bearer is listed in EFACL before requesting this EPS Bearer activation from the network if the ACL service is enabled.
3) To verify that the terminal does not request the corresponding EPS Bearer activation from the network if the ACL service is enabled and the APN is not present in EFACL.
4) To verify that the terminal does not check that the network provided APN is present in EFACL during the initial attach procedure.
9.1.4.4 Method of test
9.1.4.4.1 Initial conditions
The terminal is connected to the USIM Simulator and the E-USS.
The terminal is configured to use the network provided APN for the initial attach procedure.
The default E-UTRAN UICC is used with the following exceptions:
The APN Control List (ACL) shall be allocated and activated in the USIM Service Table and enabled in the Enabled Service Table.
EFACL shall be present with the following values:
EFACL (Access Point Control List)
Logically: Number of available bytes: 64
Number of APNs: 3
1st APN: test.test
2nd APN: 3gpp.test
3rd APN: 2gpp.test
|
Byte: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Coding: |
03 |
DD |
0A |
04 |
74 |
65 |
73 |
74 |
04 |
74 |
65 |
73 |
|
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
B19 |
B20 |
B21 |
B22 |
B23 |
B24 |
|
|
74 |
DD |
0A |
04 |
33 |
67 |
70 |
70 |
04 |
74 |
65 |
73 |
|
|
B25 |
B26 |
B27 |
B28 |
B29 |
B30 |
B31 |
B32 |
B33 |
B34 |
B35 |
B36 |
|
|
74 |
DD |
0A |
04 |
32 |
67 |
70 |
70 |
04 |
74 |
65 |
73 |
|
|
B37 |
B38 |
… |
B64 |
|||||||||
|
74 |
FF |
… |
FF |
9.1.4.4.2 Procedure
a) The terminal is switched on, the USIM application shall be activated and the terminal shall successfully attach the E-UTRAN.
b) The user shall request PDN connectivity to "1gpp.test".
c) The user shall request PDN connectivity to "3gpp.test".
d) The user shall deactivate the PDN connectivity to "3gpp.test".
e) If user interface does not have support to disable the APN Control List service, proceed to step l).
f) The user shall disable the APN Control List service. When prompted to enter PIN2, the user shall present the correct PIN2 value.
g) The user shall request PDN connectivity to "1gpp.test".
h) The user shall deactivate the PDN connectivity to "1gpp.test" and shall switch the terminal off and then switch on again.
i) The user shall enable the APN Control List service. When prompted to enter PIN2, the user shall present the correct PIN2 value.
j) The user shall request PDN connectivity to "1ppp.net".
k) The terminal is switched off and on.
l) If user interface does not have support to add APN to APN Control List, proceed to step p).
m) The user shall add the APN "1ppp.net" to the APN Control List. When prompted to enter PIN2, the user shall present the correct PIN2 value.
n) The user shall request PDN connectivity to "1ppp.net".
o) The user shall deactivate the PDN connectivity.
p) Switch off the terminal.
9.1.4.5 Acceptance criteria
1) After step a) the terminal shall have activated the USIM application, shall have read the status of the ACL service in EFUST and EFEST and be in updated idle mode on the E-USS.
2) The terminal shall have not requested PDN connectivity in step b).
3) After step c) PDN connectivity shall have been activated.
4) After step d) PDN connectivity shall have been deactivated.
5) After step f) the APN Control List service shall have been set to disabled in EFEST.
6) After step g) PDN connectivity shall have been activated.
7) After step h) PDN connectivity shall have been deactivated.
8) After step i) the APN Control List service shall have been set to enabled in EFEST.
9) The terminal shall not have requested PDN connectivity in step j).
10) After step m) the APN "1ppp.net" shall have been added to the APN Control List in EFACL.
11) After step n) PDN connectivity shall have been activated.
12) After step o) PDN connectivity shall have been deactivated.
9.1.5 Void9.1.6 Void
9.2 Service Dialling Numbers handling
9.2.1 Definition and applicability
The Service Dialling Numbers feature allows for the storage of numbers related to services offered by the network operator/service provider in the SIM/USIM (e.g. customer care). The user can use these telephone numbers to make outgoing calls, but the access for updating of the numbers shall be under the control of the operator.
9.2.2 Conformance requirement
The terminal shall support the Service Dialling Numbers service as defined in TS 31.102 [4], clauses 4.2.8 and 4.2.29.
Reference:
– TS 31.102 [4], clauses 4.2.8, 4.2.29 and 4.2.31;
– TS 22.101 [11], clause A.23.
9.2.3 Test purpose
1) To verify that the terminal takes into account the status of the Service Dialling Numbers service as indicated in EFUST.
2) To verify that the user can use the Service Dialling Numbers to make outgoing calls.
3) To verify that the terminal is able to handle SDNs with an extended dialling number string.
4) To verify that the terminal is able to handle an empty alpha identifier in EFSDN.
5) To verify that the terminal is able to handle an alpha identifier of maximum length in EFSDN.
9.2.4 Method of test
9.2.4.1 Initial conditions
The terminal is connected to the USIM Simulator and the (U)SS.
The default USIM is used with the following exceptions:
The Service Dialling Numbers (SDN) shall be allocated and activated in the USIM Service Table.
EFSDN shall be present with the following values:
EFSDN (Service Dialling Numbers)
Logically:
6 records, 1 record shall be empty. Unless otherwise stated, the SDN records shall not use extendend BCD numbers/SSC strings. Access to update EFSDN shall be granted by usage of ADM1 only.
Record 1: Length of alpha identifier: 241 characters;
Alpha identifier: "Hotline001122334455667788ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789abcdefghijklmnopqrstuvwxyz0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789abcdefghijklmnopqrstuvwxyz0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789abcdefghijklmnopqrstuvwxyz0123456789";
Length of BCD number: 5;
TON and NPI: Telephony and International;
Dialled number: "22223333";
CCP: ‘FF’;
Ext3: ‘FF’.
Record 1:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
|
Hex |
48 |
6F |
74 |
6C |
69 |
6E |
65 |
30 |
30 |
31 |
… |
… |
|
B241 |
B242 |
B243 |
B244 |
B245 |
B246 |
B247 |
B248 |
B249 |
B250 |
B251 |
B252 |
|
|
39 |
05 |
91 |
22 |
22 |
33 |
33 |
FF |
FF |
FF |
FF |
FF |
|
|
B253 |
B254 |
B255 |
||||||||||
|
FF |
FF |
FF |
Record 2: Length of alpha identifier: 241 characters;
Alpha identifier: "Hotline002";
Length of BCD number: 5;
TON and NPI: Telephony and International;
Dialled number: "44554455";
CCI2: ‘FF’;
Ext3: ‘FF’.
Record 2:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
|
Hex |
48 |
6F |
74 |
6C |
69 |
6E |
65 |
30 |
30 |
32 |
FF |
… |
|
B241 |
B242 |
B243 |
B244 |
B245 |
B246 |
B247 |
B248 |
B249 |
B250 |
B251 |
B252 |
|
|
FF |
05 |
91 |
44 |
55 |
44 |
55 |
FF |
FF |
FF |
FF |
FF |
|
|
B253 |
B254 |
B255 |
||||||||||
|
FF |
FF |
FF |
Record 3: Length of alpha identifier: 241 characters;
Alpha identifier: "Hotline003";
Length of BCD number: 11;
TON and NPI: Telephony and International;
Dialled number: "01234567890123456789";
CCI2: ‘FF’;
Ext3: "01".
Record 3:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
|
Hex |
48 |
6F |
74 |
6C |
69 |
6E |
65 |
30 |
30 |
33 |
FF |
… |
|
B241 |
B242 |
B243 |
B244 |
B245 |
B246 |
B247 |
B248 |
B249 |
B250 |
B251 |
B252 |
|
|
FF |
0B |
91 |
10 |
32 |
54 |
76 |
98 |
10 |
32 |
54 |
76 |
|
|
B253 |
B254 |
B255 |
||||||||||
|
98 |
FF |
01 |
Record 4: Length of alpha identifier: 241 characters;
Alpha identifier: empty;
Length of BCD number: 03;
TON and NPI: Telephony and International;
Dialled number: "007";
CCI2: ‘FF’;
Ext3: ‘FF’.
Record 4:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
|
Hex |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
… |
|
B241 |
B242 |
B243 |
B244 |
B245 |
B246 |
B247 |
B248 |
B249 |
B250 |
B251 |
B252 |
|
|
FF |
03 |
91 |
00 |
F7 |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
|
|
B253 |
B254 |
B255 |
||||||||||
|
FF |
FF |
FF |
Record 5: Length of alpha identifier: 241 characters;
Alpha identifier: empty;
Length of BCD number: 3;
TON and NPI: Telephony and International;
Dialled number: "008";
CCI2: ‘FF’;
Ext3: ‘FF’.
Record 5:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
|
Hex |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
… |
|
B241 |
B242 |
B243 |
B244 |
B245 |
B246 |
B247 |
B248 |
B249 |
B250 |
B251 |
B252 |
|
|
FF |
03 |
91 |
00 |
F8 |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
|
|
B253 |
B254 |
B255 |
||||||||||
|
FF |
FF |
FF |
EFEXT3 (Extension 3)
Logically: 5 records, 4 records empty. Access to update EFEXT3 shall be granted by usage of ADM1 only.
Record 1: Record type: ’02’
Extension data: "012345";
Identifier: ‘FF’.
Record 1:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
B13 |
|
|
Hex |
02 |
03 |
10 |
32 |
54 |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
9.2.4.2 Procedure
a) The terminal is switched on and the USIM application shall be activated.
b) The user shall use an MMI dependent procedure to set up a call to the dialling number associated with the alpha identifier "Hotline001122334455667788ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789abcdefghijklmnopqrstuvwxyz0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789abcdefghijklmnopqrstuvwxyz0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789abcdefghijklmnopqrstuvwxyz0123456789" in record 1 of EFSDN.
c) The user shall end the call.
d) The user shall use an MMI dependent procedure to set up a call to the dialling number associated with the "Hotline003" in record 3 of EFSDN.
e) The user shall end the call.
f) The user shall use an MMI dependent procedure to select and to set up a call to the dialling number "+007" stored in record 4 of EFSDN.
g) The user shall end the call and switch the terminal off.
9.2.5 Acceptance criteria
1) After step a) the terminal shall have activated the USIM application and shall have read the status of the SDN service in EFUST.
2) After step b) the terminal shall have read record 1 of EFSDN and a call to "+22223333" shall have been established.
3) After step c) the call shall have been terminated.
4) After step d) the terminal shall have read record 3 of EFSDN and record 1 of EFEXT1 and a call to "+01234567890123456789012345" shall have been established.
5) After step e) the call shall have been terminated.
6) After step f) the terminal shall have read record 4 of EFSDN and a call to "+007" shall have been established.