6 Security related Tests
31.1213GPPRelease 16TSUICC-terminal interfaceUniversal Subscriber Identity Module (USIM) application test specification
6.1 PIN handling
6.1.1 Entry of PIN
6.1.1.1 Definition and applicability
The PIN is a number used to authenticate the user to the UICC for security. Entry of the correct PIN allows PIN-protected data to be accessed over the UICC-Terminal interface.
6.1.1.2 Conformance requirement
Following insertion of the UICC and switching on the UE, the Terminal shall check the state of the PIN. If the PIN is enabled, the Terminal asks the user for PIN verification.
The VERIFY PIN function verifies the PIN presented by the Terminal to the UICC.
Reference:
– ETSI TS 102 221 [5], clauses 9 and 11.1.9;
– TS 31.102 [4], clause 6;
– TS 22.030 [12], clause 6.6.1.
6.1.1.3 Test purpose
1) To verify that the PIN verification procedure is performed by the Terminal correctly.
2) To verify that the basic public MMI string is supported.
6.1.1.4 Method of test
6.1.1.4.1 Initial conditions
The Terminal is connected to a UICC or UICC simulator with the PIN enabled, and powered off.
The default UICC is used.
6.1.1.4.2 Procedure
a) The Terminal is powered on.
b) When the UE is in the "PIN check" mode, the sequence "2468#" shall be entered.
6.1.1.5 Acceptance criteria
1) After step b) the Terminal shall send a VERIFY PIN command to the UICC, with parameter P2 = "01".
2) After step b) the UE shall give an indication "OK", following a successful execution of the command.
6.1.2 Change of PIN
6.1.2.1 Definition and applicability
The PIN may be changed by the user, by entering the old and new PIN. The length of the PIN is between 4 and 8 digits.
6.1.2.2 Conformance requirement
The Terminal shall support the change of PIN procedure as defined in ETSI TS 102 221 [5], clause 11.1.10.
Reference:
– ETSI TS 102 221 [5], clauses 9 and 11.1.10;
– TS 31.102 [4], clause 6;
– TS 22.030 [12], clause 6.6.2.
6.1.2.3 Test purpose
1) To verify that the PIN substitution procedure is performed correctly by the Terminal.
2) To verify that the basic public MMI string is supported.
6.1.2.4 Method of test
6.1.2.4.1 Initial conditions
The Terminal is connected to a UICC or UICC simulator with the PIN enabled.
The default UICC is used.
The Terminal is powered-on, with the correct PIN entered.
6.1.2.4.2 Procedure
a) Enter "**04*2468*01234567*01234567#" or initiate an equivalent MMI dependent procedure to change the PIN from ‘2468’ to ‘01234567’.
b) The UE is switched off and on.
c) When the UE is in the "PIN check" mode, the sequence "2468#" shall be entered.
d) The UE is switched off and on.
e) When the UE is in the "PIN check" mode, the sequence "01234567#" shall be entered.
6.1.2.5 Acceptance criteria
1) After step a), the Terminal shall send a CHANGE PIN command to the UICC, with the parameter P2 set to "01".
2) Following the successful execution of the command, the UE shall give an indication that the new PIN is accepted.
3) After step c), the UE shall give an indication that the entered PIN is not accepted.
4) After step e), the UE shall give an indication "OK".
6.1.3 Unblock PIN
6.1.3.1 Definition and applicability
After three consecutive wrong entries of the PIN, the PIN shall become blocked. The Unblock PIN command is used to unblock the PIN. This function may be performed whether or not the PIN is blocked.
6.1.3.2 Conformance requirement
The Terminal shall support the Unblock PIN command, as defined in ETSI TS 102 221 [5], clause 11.1.13.
Reference:
– ETSI TS 102 221 [5], clause 11.1.13;
– TS 31.102 [4], clause 6;
– TS 22.030 [12], clause 6.6.3.
6.1.3.3 Test purpose
1) To verify that the PIN unblocking procedure is performed correctly.
2) To verify that the basic public MMI string is supported.
6.1.3.4 Method of test
6.1.3.4.1 Initial conditions
The Terminal is connected to the UICC simulator.
The default UICC is used.
6.1.3.4.2 Procedure
Sequence A:
a) The Terminal is powered on and the correct PIN is entered.
b) Enter "**05*13243546*1234*1234#"
c) The Terminal is powered off and on.
d) Enter the new PIN: "1234#".
e) The Terminal is powered off and on.
f) Enter a wrong PIN three times.
g) Enter "**05*13243546*2468*2468#".
h) The Terminal is powered off and on.
i) Enter the new PIN: "2468#".
Sequence B:
a) The Terminal is powered on.
b) Enter a wrong PIN three times.
c) The user shall initiate a MMI dependent procedure to unblock the PIN with unblock code ‘13243546’ and a new PIN ‘2468’.
d) The Terminal is powered off and on.
e) Enter the new PIN: "2468#".
6.1.3.5 Acceptance criteria
Sequence A:
1) After step b), the Terminal shall send an UNBLOCK PIN command to the UICC, with parameter P2 = "01".
2) After step d), the Terminal shall indicate that the PIN has been accepted.
3) After step f), the Terminal shall indicate that the PIN has been blocked.
4) After step g), the Terminal shall send an UNBLOCK PIN command to the UICC, with parameter P2 = "01".
5) After step i), the Terminal shall indicate that the PIN has been accepted.
Sequence B:
1) After step b), the Terminal shall indicate that the PIN has been blocked.
2) After step c), the Terminal shall send an UNBLOCK PIN command to the UICC, with parameter P2 = "01".
3) After step e), the Terminal shall indicate that the PIN has been accepted.
6.1.4 Entry of PIN2
6.1.4.1 Definition and applicability
The PIN2 is a number used to authenticate the user to the UICC for security. Entry of the correct PIN2 allows PIN2‑protected data to be accessed over the UICC-Terminal interface.
6.1.4.2 Conformance requirement
Before allowing the access to PIN2 protected data, the Terminal shall ask the user for PIN2 verification. Only after presenting the PIN2, the user shall get access to these data.
The VERIFY PIN function verifies the PIN2 presented by the Terminal to the UICC.
Reference:
– ETSI TS 102 221 [5], clauses 9 and 11.1.9;
– TS 31.102 [4], clause 6;
– TS 22.030 [12], clause 6.6.1.
6.1.4.3 Test purpose
1) To verify that the PIN2 verification procedure is performed by the Terminal correctly.
2) To verify that the basic public MMI string is supported.
6.1.4.4 Method of test
6.1.4.4.1 Initial conditions
The Terminal is connected to a UICC or UICC simulator with the PIN enabled, and powered off.
The default UICC is used.
NOTE: To perform the UPDATE FDN data (as described in the procedure below), the default FDN UICC may be used.
6.1.4.4.2 Procedure
a) The Terminal is powered on and the correct PIN is entered.
b) The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN)
c) When the UE is in the "PIN2 check" mode, the sequence "3579#" shall be entered.
6.1.4.5 Acceptance criteria
1) After step c) the Terminal shall send a VERIFY PIN command to the UICC, with parameter P2 = "81".
2) After step c) the UE shall give an indication "OK", following a successful execution of the command.
6.1.5 Change of PIN2
6.1.5.1 Definition and applicability
The PIN2 may be changed by the user, by entering the old and new PIN2. The length of the PIN2 is between 4 and 8 digits.
6.1.5.2 Conformance requirement
The Terminal shall support the change of PIN2 procedure as defined in ETSI TS 102 221 [5], clause 11.1.10.
Reference:
– ETSI TS 102 221 [5], clauses 9 and 11.1.10;
– TS 31.102 [4], clause 6;
– TS 22.030 [12], clause 6.6.2.
6.1.5.3 Test purpose
1) To verify that the PIN2 substitution procedure is performed correctly by the Terminal.
2) To verify that the basic public MMI string is supported.
6.1.5.4 Method of test
6.1.5.4.1 Initial conditions
The Terminal is connected to a UICC or UICC simulator with the PIN2 enabled.
The default UICC is used.
NOTE: To perform the UPDATE FDN data (as described in the procedure below), the default FDN UICC may be used.
The Terminal is powered-on, with the correct PIN entered.
6.1.5.4.2 Procedure
a) Enter "**042*3579*12345678*12345678#" or initiate an equivalent MMI dependent procedure to change PIN2 from ‘3579’ to ‘12345678’.
b) The UE is switched off and on and the correct PIN is entered.
c) The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN).
d) When the UE is in the "PIN2 check" mode, the sequence "3579#" shall be entered.
e) The UE is switched off and on and the correct PIN is entered.
f) The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN).
g) When the UE is in the "PIN2 check" mode, the sequence "12345678#" shall be entered.
6.1.5.5 Acceptance criteria
1) After step a), the Terminal shall send a CHANGE PIN2 command to the UICC, with the parameter P2 set to "81".
2) Following the successful execution of the command, the UE shall give an indication that the new PIN2 is accepted.
3) After step d), the UE shall give an indication that the entered PIN2 is not accepted.
4) After step g), the UE shall give an indication "OK".
6.1.6 Unblock PIN2
6.1.6.1 Definition and applicability
After three consecutive wrong entries of the PIN2, the PIN2 shall become blocked. The Unblock PIN2 command is used to unblock the PIN2. This function may be performed whether or not the PIN2 is blocked.
6.1.6.2 Conformance requirement
The Terminal shall support the Unblock PIN2 command, as defined in ETSI TS 102 221 [5], clause 11.1.13.
Reference:
– ETSI TS 102 221 [5], clauses 9 and 11.1.13;
– TS 31.102 [4], clause 6;
– TS 22.030 [12], clause 6.6.3.
6.1.6.3 Test purpose
1) To verify that the PIN2 unblocking procedure is performed correctly.
2) To verify that the basic public MMI string is supported.
6.1.6.4 Method of test
6.1.6.4.1 Initial conditions
The Terminal is connected to the UICC simulator.
The default UICC is used.
NOTE: To perform the UPDATE FDN data (as described in the procedure below), the default FDN UICC may be used.
6.1.6.4.2 Procedure
Sequence A:
a) The Terminal is powered on and the correct PIN is entered.
b) Enter "**052*08978675*1234*1234#"
c) The Terminal is powered off and on and the correct PIN is entered.
d) The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN).
e) Enter the new PIN2: "1234#".
f) The Terminal is powered off and on and the correct PIN is entered.
g) The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN).
h) Enter a wrong PIN2 three times.
i) Enter "**052*08978675*3579*3579#".
j) The Terminal is powered off and on and the correct PIN is entered.
k) The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN).
l) Enter the new PIN2: "3579#".
Sequence B:
a) The Terminal is powered on.
b) Enter a wrong PIN2 three times.
c) The user shall initiate a MMI dependent procedure to unblock the PIN2 with unblock code ‘08978675’ and a new PIN ‘3579’.
d) The Terminal is powered off and on and the correct PIN is entered.
e) The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN).
f) Enter the new PIN2: "3579#".
6.1.6.5 Acceptance criterias
Sequence A:
1) After step b), the Terminal shall send an UNBLOCK PIN command to the UICC, with parameter P2 = "81".
2) After step e), the Terminal shall indicate that the PIN2 has been accepted.
3) After step h), the Terminal shall indicate that the PIN2 has been blocked.
4) After step i), the Terminal shall send an UNBLOCK PIN command to the UICC, with parameter P2 = "81".
5) After step l), the Terminal shall indicate that the PIN2 has been accepted.
Sequence B:
1) After step b), the Terminal shall indicate that the PIN2 has been blocked.
2) After step c), the Terminal shall send an UNBLOCK PIN command to the UICC, with parameter P2 = "81".
3) After step f), the Terminal shall indicate that the PIN2 has been accepted.
6.1.7 Replacement of PIN
6.1.7.1 Definition and applicability
The Universal PIN may be used to replace a PIN used to authenticate the user to the UICC for security. In this case entry of the correct Universal PIN allows PIN-protected data to be accessed over the UICC-Terminal interface. ETSI TS 102 221 [5] defines the range of "01" to "08" as key reference of the PIN on a multi-verification capable UICC.
6.1.7.2 Conformance requirement
The Terminal shall support the usage of the Universal PIN as replacement PIN and the replacement procedure as defined in ETSI TS 102 221 [5], clause 11.1.11, as well as the procedure to disable the replacement defined in ETSI TS 102 221 [5], clause 11.1.12.
Reference:
– ETSI TS 102 221 [5], clauses 9, 11.1.11 and 11.1.12;
– TS 31.102 [4], clause 6.
6.1.7.3 Test purpose
1) To verify that the PIN replacement is supported by the Terminal correctly.
2) To verify that the PIN replacement procedure is performed by the Terminal correctly.
3) To verify that the procedure to disable the PIN replacement is performed by the Terminal correctly.
6.1.7.4 Method of test
6.1.7.4.1 Initial conditions
The Terminal is connected to the UICC simulator with the PIN enabled, and powered off.
The default UICC is used.
6.1.7.4.2 Procedure
a) The Terminal is powered on.
b) When the Terminal is in the "PIN check" mode, the sequence "2468#" shall be entered.
c) The user shall initiate an MMI dependent procedure to replace the PIN by the Universal PIN.
d) The Terminal is powered off and on and when the Terminal is in "PIN check" mode the sequence "2468#" shall be entered.
e) The correct Universal PIN is entered.
f) The user shall initiate an MMI dependent procedure to disable the replacement of the PIN by the Universal PIN.
g) The Terminal is powered off and on and when the Terminal is in "PIN check" mode the sequence "2839#" shall be entered.
h) The correct PIN is entered.
6.1.7.5 Acceptance criteria
1) After step b) the Terminal shall send a VERIFY PIN command to the UICC, with parameter P2 = "01".
2) After step c), the Terminal shall send a DISABLE PIN command to the UICC, with parameter P1="91" and P2 = "01".
3) After step d) the Terminal shall send a VERIFY PIN command to the UICC, with parameter P2 = "11" and after unsuccessful execution of the command the Terminal shall indicate that the PIN has not been accepted.
4) After step e) the Terminal shall send a VERIFY PIN command to the UICC, with parameter P2 = "11" and after successful execution of the command the Terminal shall indicate that the PIN has been accepted.
5) After step f), the Terminal shall send an ENABLE PIN command to the UICC, with parameter P2 = "01".
6) After step g) the Terminal shall send a VERIFY PIN command to the UICC, with parameter P2 = "01" and after unsuccessful execution of the command the Terminal shall indicate that the PIN has not been accepted.
7) After step e) the Terminal shall send a VERIFY PIN command to the UICC, with parameter P2 = "01" and after successful execution of the command the Terminal shall indicate that the PIN has been accepted.
6.1.8 Change of Universal PIN
6.1.8.1 Definition and applicability
The Universal PIN may be changed by the user, by entering the old and new Universal PIN. The length of the Universal PIN is between 4 and 8 digits.
6.1.8.2 Conformance requirement
The Terminal shall support the change of PIN procedure as defined in ETSI TS 102 221 [5], clause 11.1.10.
Reference:
– ETSI TS 102 221 [5], clauses 9 and 11.1.10;
– TS 31.102 [4], clause 6.
6.1.8.3 Test purpose
To verify that the PIN substitution procedure is performed correctly by the Terminal.
6.1.8.4 Method of test
6.1.8.4.1 Initial conditions
The Terminal is connected to a UICC or UICC simulator with the PIN enabled.
The default UICC is used with the following exception:
– The Universal PIN is used as a replacement of the PIN.
The Terminal is powered-on, with the correct Universal PIN entered.
6.1.8.4.2 Procedure
a) The user shall initiate an MMI dependent procedure to change the Universal PIN to "01234567".
b) The UE is switched off and on.
c) When the UE is in the "PIN check" mode, the sequence "2839#" shall be entered.
d) The UE is switched off and on.
e) When the UE is in the "PIN check" mode, the sequence "01234567#" shall be entered.
6.1.8.5 Acceptance criteria
1) After step a), the Terminal shall send a CHANGE PIN command to the UICC, with the parameter P2 set to "11".
2) Following the successful execution of the command, the UE shall give an indication that the new (Universal) PIN is accepted.
3) After step c), the UE shall give an indication that the entered (Universal) PIN is not accepted.
4) After step e), the UE shall give an indication "OK".
6.1.9 Unblock Universal PIN
6.1.9.1 Definition and applicability
After three consecutive wrong entries of the PIN, the PIN shall become blocked. The Unblock PIN command is used to unblock the PIN. This function may be performed whether or not the PIN is blocked.
6.1.9.2 Conformance requirement
The Terminal shall support the Unblock PIN command, as defined in ETSI TS 102 221 [5], clause 11.1.13.
Reference:
– ETSI TS 102 221 [5], clause 11.1.13;
– TS 31.102 [4], clause 6.
6.1.9.3 Test purpose
To verify that the PIN unblocking procedure is performed correctly.
6.1.9.4 Method of test
6.1.9.4.1 Initial conditions
The Terminal is connected to the UICC simulator.
The default UICC is used.
6.1.9.4.2 Procedure
a) The Terminal is powered on and the correct PIN is entered.
b) The user shall initiate an MMI dependent procedure to unblock the Universal PIN and set the new Universal PIN value to "1234"
c) The Terminal is powered off and on.
d) Enter the new PIN: "1234#".
e) The Terminal is powered off and on.
f) Enter a wrong PIN three times.
g) The user shall initiate an MMI dependent procedure to unblock the Universal PIN and set the new Universal PIN value to "2839".
h) The Terminal is powered off and on.
i) Enter the new PIN: "2839#".
6.1.9.5 Acceptance criteria
1) After step b), the Terminal shall send an UNBLOCK PIN command to the UICC, with parameter P2 = "11".
2) After step d), the Terminal shall indicate that the (Universal) PIN has been accepted.
3) After step f), the Terminal shall indicate that the (Universal) PIN has been blocked.
4) After step g), the Terminal shall send an UNBLOCK PIN command to the UICC, with parameter P2 = "11".
5) After step j), the Terminal shall indicate that the (Universal) PIN has been accepted.
6.1.10 Entry of PIN on multi-verification capable UICCs
6.1.10.1 Definition and applicability
The PIN is a number used to authenticate the user to the UICC for security. Entry of the correct PIN allows PIN-protected data to be accessed over the UICC-Terminal interface. ETSI TS 102 221 [5] defines the range of "01" to "08" as key reference of the PIN on a multi-verification capable UICC.
6.1.10.2 Conformance requirement
Following insertion of the UICC and switching on the UE, the Terminal shall check the state of the PIN. If the PIN is enabled, the Terminal asks the user for PIN verification.
The VERIFY PIN function verifies the PIN presented by the Terminal to the UICC.
Reference:
– ETSI TS 102 221 [5], clauses 9 and 11.1.9;
– 3GPP TS 31.102 [4], clause 6;
– 3GPP TS 22.030 [12], clause 6.6.1.
6.1.10.3 Test purpose
1) To verify that the PIN verification procedure is performed by the Terminal correctly.
2) To verify that the basic public MMI string is supported.
3) To verify that the Terminal supports key references in the range of "01" to "08" as PIN.
6.1.10.4 Method of test
6.1.10.4.1 Initial conditions
The Terminal is connected to the UICC simulator with the PIN enabled, and powered off.
The default UICC is used with the following exceptions:
The UICC shall be configured to use "07" as the key reference of the PIN and "87" as key reference of the PIN2 with the following values:
PIN
Key reference: 07
Logically: 8642
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
38 |
36 |
34 |
32 |
FF |
FF |
FF |
FF |
Unblock PIN
Key reference 07
Logically: 64534231
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
36 |
34 |
35 |
33 |
34 |
32 |
33 |
31 |
PIN2
Key reference 87
Logically: 9753
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
39 |
37 |
35 |
33 |
FF |
FF |
FF |
FF |
Unblock PIN2
Key reference 87
Logically: 57687980
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
35 |
37 |
36 |
38 |
37 |
39 |
38 |
30 |
6.1.10.4.2 Procedure
a) The Terminal is powered on.
b) When the UE is in the "PIN check" mode, the sequence "8642#" shall be entered.
6.1.10.5 Acceptance criteria
1) After step b) the Terminal shall send a VERIFY PIN command to the UICC, with parameter P2 = "07".
2) After step b) the UE shall give an indication "OK", following a successful execution of the command.
6.1.11 Change of PIN on multi-verification capable UICCs
6.1.11.1 Definition and applicability
The PIN may be changed by the user, by entering the old and new PIN. The length of the PIN is between 4 and 8 digits. ETSI TS 102 221 [5] defines the range of "01" to "08" as key reference of the PIN on a multi-verification capable UICC.
6.1.11.2 Conformance requirement
The Terminal shall support the change of PIN procedure as defined in ETSI TS 102 221 [5], clause 11.1.10.
Reference:
– ETSI TS 102 221 [5], clauses 9 and 11.1.10;
– 3GPP TS 31.102 [4], clause 6;
– 3GPP TS 22.030 [12], clause 6.6.2.
6.1.11.3 Test purpose
1) To verify that the PIN substitution procedure is performed correctly by the Terminal.
2) To verify that the basic public MMI string is supported.
3) To verify that the Terminal supports key references in the range of "01" to "08" as PIN.
6.1.11.4 Method of test
6.1.11.4.1 Initial conditions
The Terminal is connected to the UICC simulator with the PIN enabled.
The default UICC is used with the following exceptions:
The UICC shall be configured to use "07" as the reference of the PIN and "87" as reference of the PIN2 with the following values:
PIN
Key reference: 07
Logically: 8642
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
38 |
36 |
34 |
32 |
FF |
FF |
FF |
FF |
Unblock PIN
Key reference 07
Logically: 64534231
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
36 |
34 |
35 |
33 |
34 |
32 |
33 |
31 |
PIN2
Key reference 87
Logically: 9753
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
39 |
37 |
35 |
33 |
FF |
FF |
FF |
FF |
Unblock PIN2
Key reference 87
Logically: 57687980
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
35 |
37 |
36 |
38 |
37 |
39 |
38 |
30 |
The Terminal is powered-on, with the correct PIN entered.
6.1.11.4.2 Procedure
a) Enter "**04*8642*01234567*01234567#" or initiate an equivalent MMI dependent procedure to change the PIN from ‘8642’ to ‘01234567’.
b) The UE is switched off and on.
c) When the UE is in the "PIN check" mode, the sequence "8642#" shall be entered.
d) The UE is switched off and on.
e) When the UE is in the "PIN check" mode, the sequence "01234567#" shall be entered.
6.1.11.5 Acceptance criteria
1) After step a), the Terminal shall send a CHANGE PIN command to the UICC, with the parameter P2 set to "07".
2) Following the successful execution of the command, the UE shall give an indication that the new PIN is accepted.
3) After step c), the UE shall give an indication that the entered PIN is not accepted.
4) After step e), the UE shall give an indication "OK".
6.1.12 Unblock PIN on multi-verification capable UICCs
6.1.12.1 Definition and applicability
After three consecutive wrong entries of the PIN, the PIN shall become blocked. The Unblock PIN command is used to unblock the PIN. This function may be performed whether or not the PIN is blocked. ETSI TS 102 221 [5] defines the range of "01" to "08" as key reference of the PIN on a multi-verification capable UICC.
6.1.12.2 Conformance requirement
The Terminal shall support the Unblock PIN command, as defined in ETSI TS 102 221 [5], clause 11.1.13.
Reference:
– ETSI TS 102 221 [5], clauses 9 and 11.1.13;
– TS 31.102 [4], clause 6;
– TS 22.030 [12], clause 6.6.3.
6.1.12.3 Test purpose
1) To verify that the PIN unblocking procedure is performed correctly.
2) To verify that the basic public MMI string is supported.
3) To verify that the Terminal supports key references in the range of "01" to "08" as PIN.
6.1.12.4 Method of test
6.1.12.4.1 Initial conditions
The Terminal is connected to the UICC simulator.
The default UICC is used with the following exceptions:
The UICC shall be configured to use "07" as the reference of the PIN and "87" as reference of the PIN2 with the following values:
PIN
Key reference: 07
Logically: 8642
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
38 |
36 |
34 |
32 |
FF |
FF |
FF |
FF |
Unblock PIN
Key reference 07
Logically: 64534231
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
36 |
34 |
35 |
33 |
34 |
32 |
33 |
31 |
PIN2
Key reference 87
Logically: 9753
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
39 |
37 |
35 |
33 |
FF |
FF |
FF |
FF |
Unblock PIN2
Key reference 87
Logically: 57687980
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
35 |
37 |
36 |
38 |
37 |
39 |
38 |
30 |
6.1.12.4.2 Procedure
Sequence A:
a) The Terminal is powered on and the correct PIN is entered.
b) Enter "**05*64534231*1234*1234#"
c) The Terminal is powered off and on.
d) Enter the new PIN: "1234#".
e) The Terminal is powered off and on.
f) Enter a wrong PIN three times.
g) Enter "**05*64534231*8642*8642#".
h) The Terminal is powered off and on.
i) Enter the new PIN: "8642#".
Sequence B:
a) The Terminal is powered on.
b) Enter a wrong PIN three times.
c) The user shall initiate a MMI dependent procedure to unblock the PIN with unblock code ‘64534231’ and a new PIN ‘8642’.
d) The Terminal is powered off and on.
e) Enter the new PIN: "8642#".
6.1.12.5 Acceptance criteria
Sequence A:
1) After step b), the Terminal shall send an UNBLOCK PIN command to the UICC, with parameter P2 = "07".
2) After step d), the Terminal shall indicate that the PIN has been accepted.
3) After step f), the Terminal shall indicate that the PIN has been blocked.
4) After step g), the Terminal shall send an UNBLOCK PIN command to the UICC, with parameter P2 = "07".
5) After step j), the Terminal shall indicate that the PIN has been accepted.
Sequence B:
1) After step b), the Terminal shall indicate that the PIN has been blocked.
2) After step c), the Terminal shall send an UNBLOCK PIN command to the UICC, with parameter P2 = "07".
3) After step e), the Terminal shall indicate that the PIN has been accepted.
6.1.13 Entry of PIN2 on multi-verification capable UICCs
6.1.13.1 Definition and applicability
The PIN2 is a number used to authenticate the user to the UICC for security. Entry of the correct PIN2 allows PIN2‑protected data to be accessed over the UICC-Terminal interface. ETSI TS 102 221 [5] defines the range of "81" to "88" as key reference of the PIN2 on a multi-verification capable UICC.
6.1.13.2 Conformance requirement
Before allowing the access to PIN2 protected data, the Terminal shall ask the user for PIN2 verification. Only after presenting the PIN2, the user shall get access to these data.
The VERIFY PIN function verifies the PIN2 presented by the Terminal to the UICC.
Reference:
– ETSI TS 102 221 [5], clause 9 and clause 11.1.9;
– 3GPP TS 31.102 [4], clause 6;
– 3GPP TS 22.030 [12], clause 6.6.1.
6.1.13.3 Test purpose
1) To verify that the PIN2 verification procedure is performed by the Terminal correctly.
2) To verify that the basic public MMI string is supported.
3) To verify that the Terminal supports key references in the range of "81" to "88" as PIN2.
6.1.13.4 Method of test
6.1.13.4.1 Initial conditions
The Terminal is connected to the UICC simulator with the PIN enabled, and powered off.
The default UICC is used with the following exceptions:
The UICC shall be configured to use "07" as the reference of the PIN and "87" as reference of the PIN2 with the following values:
PIN
Key reference: 07
Logically: 8642
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
38 |
36 |
34 |
32 |
FF |
FF |
FF |
FF |
Unblock PIN
Key reference 07
Logically: 64534231
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
36 |
34 |
35 |
33 |
34 |
32 |
33 |
31 |
PIN2
Key reference 87
Logically: 9753
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
39 |
37 |
35 |
33 |
FF |
FF |
FF |
FF |
Unblock PIN2
Key reference 87
Logically: 57687980
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
35 |
37 |
36 |
38 |
37 |
39 |
38 |
30 |
NOTE: To perform the UPDATE FDN data (as described in the procedure below), the default FDN UICC may be used. In this case the above mentioned exceptions shall apply.
6.1.13.4.2 Procedure
a) The Terminal is powered on and the correct PIN is entered.
b) The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN).
c) When the UE is in the "PIN2 check" mode, the sequence "9753#" shall be entered.
6.1.13.5 Acceptance criteria
1) After step b) the Terminal shall send a VERIFY PIN command to the UICC, with parameter P2 = "87".
2) After step b) the UE shall give an indication "OK", following a successful execution of the command.
6.1.14 Change of PIN2 on multi-verification capable UICCs
6.1.14.1 Definition and applicability
The PIN2 may be changed by the user, by entering the old and new PIN2. The length of the PIN2 is between 4 and 8 digits. ETSI TS 102 221 [5] defines the range of "81" to "88" as key reference of the PIN2 on a multi-verification capable UICC.
6.1.14.2 Conformance requirement
The Terminal shall support the change of PIN2 procedure as defined in ETSI TS 102 221 [5], clause 11.1.10.
Reference:
– ETSI TS 102 221 [5], clauses 9 and 11.1.10;
– TS 31.102 [4], clause 6;
– TS 22.030 [12], clause 6.6.2.
6.1.14.3 Test purpose
1) To verify that the PIN2 substitution procedure is performed correctly by the Terminal.
2) To verify that the basic public MMI string is supported.
3) To verify that the Terminal supports key references in the range of "81" to "88" as PIN2.
6.1.14.4 Method of test
6.1.14.4.1 Initial conditions
The Terminal is connected to the UICC simulator with the PIN2 enabled.
The default UICC is used with the following exceptions:
The UICC shall be configured to use "07" as the reference of the PIN and "87" as reference of the PIN2 with the following values:
PIN
Key reference: 07
Logically: 8642
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
38 |
36 |
34 |
32 |
FF |
FF |
FF |
FF |
Unblock PIN
Key reference 07
Logically: 64534231
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
36 |
34 |
35 |
33 |
34 |
32 |
33 |
31 |
PIN2
Key reference 87
Logically: 9753
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
39 |
37 |
35 |
33 |
FF |
FF |
FF |
FF |
Unblock PIN2
Key reference 87
Logically: 57687980
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
35 |
37 |
36 |
38 |
37 |
39 |
38 |
30 |
NOTE: To perform the UPDATE FDN data (as described in the procedure below), the default FDN UICC may be used. In this case the above mentioned exceptions shall apply.
The Terminal is powered-on, with the correct PIN entered.
6.1.14.4.2 Procedure
a) Enter "**042*9753*12345678*12345678#" or initiate an equivalent MMI dependent procedure to change PIN2 from ‘9753’ to ‘12345678’.
b) The UE is switched off and on and the correct PIN is entered.
c) The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN).
d) When the UE is in the "PIN2 check" mode, the sequence "9753#" shall be entered.
e) The UE is switched off and on and the correct PIN is entered.
f) The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN).
g) When the UE is in the "PIN2 check" mode, the sequence "12345678#" shall be entered.
6.1.14.5 Acceptance criteria
1) After step a), the Terminal shall send a CHANGE PIN2 command to the UICC, with the parameter P2 set to "87".
2) Following the successful execution of the command, the UE shall give an indication that the new PIN2 is accepted.
3) After step d), the UE shall give an indication that the entered PIN2 is not accepted.
3) After step g), the UE shall give an indication "OK".
6.1.15 Unblock PIN2 on multi-verification capable UICCs
6.1.15.1 Definition and applicability
After three consecutive wrong entries of the PIN2, the PIN2 shall become blocked. The Unblock PIN2 command is used to unblock the PIN2. This function may be performed whether or not the PIN2 is blocked. ETSI TS 102 221 [5] defines the range of "81" to "88" as key reference of the PIN2 on a multi-verification capable UICC.
6.1.15.2 Conformance requirement
The Terminal shall support the Unblock PIN2 command, as defined in ETSI TS 102 221 [5], clause 11.1.13.
Reference:
– ETSI TS 102 221 [5],clauses 9 and 11.1.13;
– TS 31.102 [4], clause 6;
– TS 22.030 [12], clause 6.6.3.
6.1.15.3 Test purpose
1) To verify that the PIN2 unblocking procedure is performed correctly.
2) To verify that the basic public MMI string is supported.
3) To verify that the Terminal supports key references in the range of "81" to "88" as PIN2.
6.1.15.4 Method of test
6.1.15.4.1 Initial conditions
The Terminal is connected to the UICC simulator.
The default UICC is used with the following exceptions:
The UICC shall be configured to use "07" as the reference of the PIN and "87" as reference of the PIN2 with the following values:
PIN
Key reference: 07
Logically: 8642
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
38 |
36 |
34 |
32 |
FF |
FF |
FF |
FF |
Unblock PIN
Key reference 07
Logically: 64534231
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
36 |
34 |
35 |
33 |
34 |
32 |
33 |
31 |
PIN2
Key reference 87
Logically: 9753
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
39 |
37 |
35 |
33 |
FF |
FF |
FF |
FF |
Unblock PIN2
Key reference 87
Logically: 57687980
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
35 |
37 |
36 |
38 |
37 |
39 |
38 |
30 |
NOTE: To perform the UPDATE FDN data (as described in the procedure below), the default FDN UICC may be used. In this case the above mentioned exceptions shall apply.
6.1.15.4.2 Procedure
Sequence A:
a) The Terminal is powered on and the correct PIN is entered.
b) Enter "**052*57687980*1234*1234#"
c) The Terminal is powered off and on and the correct PIN is entered.
d) The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN).
e) Enter the new PIN2: "1234#".
f) The Terminal is powered off and on and the correct PIN is entered.
g) The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN).
h) Enter a wrong PIN2 three times.
i) Enter "**052*57687980*9753*9753#".
j) The Terminal is powered off and on and the correct PIN is entered.
k) The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN).
l) Enter the new PIN2: "9753#".
Sequence B:
a) The Terminal is powered on .
b) Enter a wrong PIN2 three times.
c) The user shall initiate a MMI dependent procedure to unblock the PIN2 with unblock code ‘57687980’ and a new PIN2 ‘9753’.
d) The Terminal is powered off and on and the correct PIN is entered.
e) The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN).
f) Enter the new PIN2: "9753#".
6.1.15.5 Acceptance criterias
Sequence A:
1) After step b), the Terminal shall send an UNBLOCK PIN command to the UICC, with parameter P2 = "87".
2) After step e), the Terminal shall indicate that the PIN2 has been accepted.
3) After step h), the Terminal shall indicate that the PIN2 has been blocked.
4) After step i), the Terminal shall send an UNBLOCK PIN command to the UICC, with parameter P2 = "87".
5) After step l), the Terminal shall indicate that the PIN2 has been accepted.
Sequence B:
1) After step b), the Terminal shall indicate that the PIN2 has been blocked.
2) After step c), the Terminal shall send an UNBLOCK PIN command to the UICC, with parameter P2 = "87".
3) After step f), the Terminal shall indicate that the PIN2 has been accepted.
6.1.16 Replacement of PIN with key reference "07"
6.1.16.1 Definition and applicability
The Universal PIN may be used to replace a PIN used to authenticate the user to the UICC for security. In this case entry of the correct Universal PIN allows PIN-protected data to be accessed over the UICC-Terminal interface.
6.1.16.2 Conformance requirement
The Terminal shall support the usage of the Universal PIN as replacement PIN and the replacement procedure as defined in ETSI TS 102 221 [5], clause 11.1.11, as well as the procedure to disable the replacement defined in ETSI TS 102 221 [5], clause 11.1.12.
Reference:
– ETSI TS 102 221 [5], clauses 9, 11.1.11 and 11.1.12;
– TS 31.102 [4], clause 6.
6.1.16.3 Test purpose
1) To verify that the PIN replacement is supported by the Terminal correctly.
2) To verify that the PIN replacement procedure is performed by the Terminal correctly.
3) To verify that the procedure to disable the PIN replacement is performed by the Terminal correctly.
4) To verify that the Terminal supports key references in the range of "01" to "08" as PIN.
6.1.16.4 Method of test
6.1.16.4.1 Initial conditions
The Terminal is connected to the UICC simulator with the PIN enabled, and powered off.
The default UICC is used with the following exceptions:
The UICC shall be configured to use "07" as the reference of the PIN and "87" as reference of the PIN2 with the following values:
PIN
Key reference: 07
Logically: 8642
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
38 |
36 |
34 |
32 |
FF |
FF |
FF |
FF |
Unblock PIN
Key reference 07
Logically: 64534231
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
36 |
34 |
35 |
33 |
34 |
32 |
33 |
31 |
PIN2
Key reference 87
Logically: 9753
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
39 |
37 |
35 |
33 |
FF |
FF |
FF |
FF |
Unblock PIN2
Key reference 87
Logically: 57687980
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
35 |
37 |
36 |
38 |
37 |
39 |
38 |
30 |
6.1.16.4.2 Procedure
a) The Terminal is powered on.
b) When the Terminal is in the "PIN check" mode, the sequence "8642#" shall be entered.
c) The user shall initiate an MMI dependent procedure to replace the PIN by the Universal PIN.
d) The Terminal is powered off and on and when the Terminal is in "PIN check" mode the sequence "8642#" shall be entered.
e) The correct Universal PIN is entered.
f) The user shall initiate an MMI dependent procedure to disable the replacement of the PIN by the Universal PIN.
g) The Terminal is powered off and on and when the Terminal is in "PIN check" mode the sequence "2839#" shall be entered.
h) The correct PIN is entered.
6.1.16.5 Acceptance criteria
1) After step b) the Terminal shall send a VERIFY PIN command to the UICC, with parameter P2 = "07".
2) After step c), the Terminal shall send a DISABLE PIN command to the UICC, with parameter P1="91" and P2 = "07".
3) After step d) the Terminal shall send a VERIFY PIN command to the UICC, with parameter P2 = "11" and after unsuccessful execution of the command the Terminal shall indicate that the PIN has not been accepted.
4) After step e) the Terminal shall send a VERIFY PIN command to the UICC, with parameter P2 = "11" and after successful execution of the command the Terminal shall indicate that the PIN has been accepted.
5) After step f), the Terminal shall send an ENABLE PIN command to the UICC, with parameter P2 = "07".
6) After step g) the Terminal shall send a VERIFY PIN command to the UICC, with parameter P2 = "07" and after unsuccessful execution of the command the Terminal shall indicate that the PIN has not been accepted.
7) After step h) the Terminal shall send a VERIFY PIN command to the UICC, with parameter P2 = "07" and after successful execution of the command the Terminal shall indicate that the PIN has been accepted.
6.2 Fixed Dialling Numbers (FDN) handling
6.2.1 Terminal and USIM with FDN enabled, EFADN readable and updateable
6.2.1.1 Definition and applicability
Fixed Dialling Numbers (FDN) is a service defined for the USIM. An enabled FDN service results in call restrictions for the UE. The call restrictions are controlled by the Terminal. To ascertain the type of USIM and state of FDN the UE runs the FDN capability request procedure during UICC-Terminal initialisation. During the initialisation the Terminal shall request the Emergency call codes of the USIM EFECC. At the time an emergency call is setup using the emergency call code read from the EFECC, the UE shall use the category of the emergency service indicated.
6.2.1.2 Conformance requirement
1) Recognising the state of the USIM (FDN enabled) the UE shall perform the UICC initialisation procedure as specified.
2) The UE allows call set-up to a directory number as stored in EFFDN.
3) The UE allows call set-up to a directory number as stored in EFFDN and extended by digits in the end.
4) The UE does not allow call set-up to a directory number stored in EFFDN but with missing digits at the end.
5) The UE does not allow call set-up to a directory number having no reference in EFFDN.
6) The UE does not allow call set-up of an emergency call using the emergency numbers stored in the Terminal except "112", "911", the emergency numbers stored on the SIM/USIM and emergency numbers downloaded from the serving network (if any).
7) The UE allows call set-up of an emergency call using the emergency number stored in the USIM.
Reference:
– TS 22.101 [11], clauses 8 and A.24;
– TS 31.102 [4], clauses 4.4.2, 4.2.24, 5.1.1 and 5.3.2;
– TS 24.008 [16], clause 10.5.4.33.
6.2.1.3 Test purpose
1) To verify that the Terminal allows call set-up to a FDN number.
2) To verify that the Terminal allows call set-up to a FDN number extended by some digits in the end.
3) To verify that the Terminal rejects call set-up to number having no reference in EFFDN.
4) To verify that the Terminal rejects call set-up to a FDN number not completely corresponding to an entry in EFFDN.
5) To verify that the Terminal does not allow emergency call set-up using the emergency number stored in the Terminal except "112", "911", the emergency numbers stored on the SIM/USIM and emergency numbers downloaded from the serving network (if any).
6) To verify that the Terminal allows emergency call set-up using the emergency number stored in the UISM.
6.2.1.4 Method of test
6.2.1.4.1 Initial conditions
The USS (in case of a Terminal accessing UTRAN)/ SS (in case of a Terminal accessing GERAN) transmits on the BCCH, with the following network parameters
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 246/081/0001.
– Access control: unrestricted.
The default FDN UICC with FDN service enabled and EFADN readable and updateable is installed into the Terminal.
The following expection applies:
EFECC (Emergency Call Codes)
Logically: Emergency call code: "122";
Emergency call code alpha identifier: "TEST";
Emergency call Service Category: RFU.
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
21 |
F2 |
FF |
54 |
45 |
53 |
54 |
00 |
6.2.1.4.2 Procedure
a) The UE is powered on and PIN is entered.
b) Using the MMI a call set-up to the fixed dialling number 1 (record 1) is attempted.
c) Using the MMI a call set-up to the fixed dialling number 2 (record 2) extended by "123" in the end is attempted.
d) Using the MMI a call set-up to a number which is equal to the fixed dialling number 3 (record 3) without the last digit is attempted, e.g. by recalling the fixed dialling number 3 and deleting the last digit (only in display).
e) Using the MMI a call set-up to the number "1234567" is attempted.
f) Using the MMI an emergency call set-up is attempted using an emergency call code stored in the Terminal, but not "112", "911" nor one of the emergency numbers stored on the SIM/USIM emergency numbers downloaded from the serving network (if any).
g) Using the MMI an emergency call set-up is attempted using either "112", "911" or an emergency number downloaded from the serving network (if any).
h) Using the MMI an emergency call set-up is attempted using the emergency call code stored in the USIM (i.e. "122").
NOTE: For step f) one of the emergency call codes according to TS 22.101 [11], clause 10.1, except "112" and "911", shall be used (i.e. "000", "08", "110", "118", "119" or "999").
6.2.1.5 Acceptance criteria
1) After step a) the UE is registered and in idle state.
2) After steps b) and c) the UE shall allow call set-up and send the requested number across the air interface.
3) After steps d), e) and f) the UE shall prevent call set-up.
4) After steps g) and h) the UE shall allow emergency call by indicating the call setup as "Emergency Call".
6.2.2 Terminal and USIM with FDN disabled
6.2.2.1 Definition and applicability
Fixed Dialling Numbers (FDN) is a service defined for the USIM. An enabled FDN service results in call restrictions for the UE. Only directory numbers which are stored in the EFFDN may be dialled by the UE. The call restrictions are controlled by the Terminal. To ascertain the type of USIM and state of FDN the UE runs the FDN capability request procedure during UICC-Terminal initialisation. Deactivation of the service by the subscriber is possible under the control of PIN2 and switches the USIM into a "normal", non restrictive USIM.
6.2.2.2 Conformance requirement
1) Recognising the state of the USIM (FDN disabled) the UE correctly performs the UICC initialisation procedure.
2) The UE allows call set-up to a directory number as stored in EFFDN.
3) The UE allows call set-up to a directory number as stored in EFADN.
4) The UE allows call set-up to a directory number given in manually.
Reference:
– R99: TS 22.101 [11], clauses 8 and A.24
– Rel-4: TS 22.101 [11], clauses 9 and A.25
– Rel-5, Rel-6: TS 22.101 [11], clauses 10 and A.25;
– TS 31.102 [4], clauses 4.4.2.3, 4.2.24, 4.2.47, 5.1.1 and 5.3.2.
6.2.2.3 Test purpose
1) To verify that the Terminal as a result of the state of the USIM correctly performs the UICC-Terminal initialisation procedure.
2) To verify that the Terminal allows call set-up to a FDN number.
3) To verify that the Terminal allows call set-up to a ADN number.
4) To verify that the Terminal allows call set-up to manually given number.
6.2.2.4 Method of test
6.2.2.4.1 Initial conditions
The USS (in case of a Terminal accessing UTRAN) /SS (in case of a Terminal accessing GERAN) transmits on the BCCH, with the following network parameters:
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 246/081/0001.
– Access control: unrestricted.
The default FDN UICC is used with the following exception:
EFEST (Enable Service Table)
Logically: Fixed Dialling Numbers disabled.
Barred Dialling Numbers disabled.
APN Control list (ACL) disabled.
|
Coding: |
B1 |
|
binary |
0000 0000 |
The UICC is installed into the Terminal and the UE is powered on.
6.2.2.4.2 Procedure
a) Using the MMI a call set-up to the fixed dialling number 1 is attempted.
b) Using the MMI a call set-up to the abbreviated dialling number 1 is attempted.
c) Using the MMI a call set-up to the number "1234567" is attempted.
6.2.2.5 Acceptance criteria
After steps a), b) and c) the UE shall allow call set-up and send the requested number across the air interface.
6.2.3 Enabling, disabling and updating of FDN
6.2.3.1 Definition and applicability
FDN may be enabled and disabled by the subscriber under control of PIN2. Fixed dialling numbers are read with PIN and updated under control of PIN2.
6.2.3.2 Conformance requirement
1) Recognising the state of the USIM (FDN enabled) the UE shall perform the UICC initialisation procedure as specified.
2) The UE shall allow updating of EFFDN by the use of PIN2.
3) The UE provides means to disable the FDN service by the use of PIN2.
4) The UE shall allow the use of EFADN after disabling of FDN.
Reference:
– R99: TS 22.101 [11], clauses 8 and A.24
– Rel-4: TS 22.101 [11], clauses 9 and A.25
– Rel-5, Rel-6: TS 22.101 [11], clause 10 and A.25;
– TS 31.102 [4], clauses 4.4.2.3, 4.2.24, 4.2.47, 5.1.1 and 5.3.2.
6.2.3.3 Test purpose
1) To verify that the Terminal correctly performs the update of a number in EFFDN.
2) To verify that the Terminal correctly disables FDN service.
3) To verify that the Terminal recognises disabling of FDN and allows access to EFADN.
6.2.3.4 Method of test
6.2.3.4.1 Initial conditions
The USS (in case of a Terminal accessing UTRAN)/SS (in case of a Terminal accessing GERAN) transmits on the BCCH, with the following network parameters
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 246/081/0001.
– Access control: unrestricted.
The default FDN UICC with FDN service enabled is installed into the Terminal.
6.2.3.4.2 Procedure
a) The UE is powered on and PIN is entered.
b) Using the MMI the directory number "+876543210" is stored in EFFDN as fixed dialling number 1 (record 1). The alpha identifier is not changed. On request of the UE PIN2 is entered.
c) Using the MMI the FDN disabling procedure is performed. On request of the UE PIN2 is entered.
d) Using the MMI a call set-up to the abbreviated dialling number 1 (record 1) is attempted.
e) The UE is soft-powered down.
6.2.3.5 Acceptance criteria
1) After step a) the UE is registered and in idle state.
2) After step c) the UE shall indicate that the FDN disabling procedure has been successful.
3) After step d) the UE shall allow call set-up and send the requested number across the air interface.
4) After step e) record 1 in EFFDN , shall contain the following values:
|
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
B13 |
|
|
Hex |
46 |
44 |
4E |
31 |
31 |
31 |
06 |
91 |
78 |
56 |
34 |
12 |
F0 |
|
B14 |
B15 |
B16 |
B17 |
B18 |
B19 |
B20 |
|||||||
|
FF |
FF |
FF |
FF |
FF |
FF |
FF |
6.2.4 Terminal and USIM with FDN enabled, EFADN readable and updateable (Rel-4 and onwards)
6.2.4.1 Definition and applicability
Fixed Dialling Numbers (FDN) is a service defined for the USIM. An enabled FDN service results in call restrictions for the UE. The call restrictions are controlled by the Terminal. To ascertain the type of USIM and state of FDN the UE runs the FDN capability request procedure during UICC-Terminal initialisation. During the initialisation the Terminal shall request the Emergency call codes of the USIM EFECC. At the time an emergency call is setup using the emergency call code read from the EFECC, the UE shall use the category of the emergency service indicated.
6.2.4.2 Conformance requirement
1) Recognising the state of the USIM (FDN enabled) the UE shall perform the UICC initialisation procedure as specified.
2) The UE allows call set-up to a directory number as stored in EFFDN.
3) The UE allows call set-up to a directory number as stored in EFFDN and extended by digits in the end.
4) The UE does not allow call set-up to a directory number stored in EFFDN but with missing digits at the end.
5) The UE does not allow call set-up to a directory number having no reference in EFFDN.
6) The UE does not allow call set-up of an emergency call using the emergency numbers stored in the Terminal except "112", "911", the emergency numbers stored on the SIM/USIM and emergency numbers downloaded from the serving network (if any).
7) The UE allows call set-up of an emergency call using the emergency number stored in the USIM.
8) The UE shall indicate the emergency service category as "Mountain Rescue", when using the emergency number stored in the USIM.
Reference:
– Rel-4: TS 22.101 [11], clauses 9 and A.25
– Rel-5, Rel-6: TS 22.101 [11], clauses 10 and A.25;
– TS 31.102 [4], clauses 4.4.2, 4.2.24, 5.1.1 and 5.3.2;
– TS 24.008 [16], clause 10.5.4.33.
6.2.4.3 Test purpose
1) To verify that the Terminal allows call set-up to a FDN number.
2) To verify that the Terminal allows call set-up to a FDN number extended by some digits in the end.
3) To verify that the Terminal rejects call set-up to number having no reference in EFFDN.
4) To verify that the Terminal rejects call set-up to a FDN number not completely corresponding to an entry in EFFDN.
5) To verify that the Terminal does not allow emergency call set-up using the emergency number stored in the Terminal except "112", "911", the emergency numbers stored on the SIM/USIM and emergency numbers downloaded from the serving network (if any).
6) To verify that the Terminal allows emergency call set-up using the emergency number stored in the UISM.
7) To verify that the Terminal reads correctly the emergency service category.
6.2.4.4 Method of test
6.2.4.4.1 Initial conditions
The USS (in case of a Terminal accessing UTRAN)/ SS (in case of a Terminal accessing GERAN) transmits on the BCCH, with the following network parameters
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 246/081/0001.
– Access control: unrestricted.
The default FDN UICC with FDN service enabled and EFADN readable and updateable is installed into the Terminal.
6.2.4.4.2 Procedure
a) The UE is powered on and PIN is entered.
b) Using the MMI a call set-up to the fixed dialling number 1 (record 1) is attempted.
c) Using the MMI a call set-up to the fixed dialling number 2 (record 2) extended by "123" in the end is attempted.
d) Using the MMI a call set-up to a number which is equal to the fixed dialling number 3 (record 3) without the last digit is attempted, e.g. by recalling the fixed dialling number 3 and deleting the last digit (only in display).
e) Using the MMI a call set-up to the number "1234567" is attempted.
f) Using the MMI an emergency call set-up is attempted using an emergency call code stored in the Terminal, but not "112", "911" nor one of the emergency numbers stored on the SIM/USIM emergency numbers downloaded from the serving network (if any).
g) Using the MMI an emergency call set-up is attempted using either "112", "911" or an emergency number downloaded from the serving network (if any).
h) Using the MMI an emergency call set-up is attempted using the emergency call code stored in the USIM (i.e. "122").
NOTE: For step f) one of the emergency call codes according to TS 22.101 [11], clause 10.1, except "112" and "911", shall be used (i.e. "000", "08", "110", "118", "119" or "999").
6.2.4.5 Acceptance criteria
1) After step a) the UE is registered and in idle state.
2) After steps b) and c) the UE shall allow call set-up and send the requested number across the air interface.
3) After steps d), e) and f) the UE shall prevent call set-up.
4) After steps g) and h) the UE shall allow emergency call by indicating the call setup as "Emergency Call".
5) After step h) the UE shall send the emergency service category correctly as "Mountain Rescue".
6.3 Void
6.4 Advice of charge (AoC) handling
6.4.1 AoC not supported by USIM
6.4.1.1 Definition and applicability
If the Terminal under test supports Advice of Charge Charging, it shall still look at the capability of the USIM, before responding to any AoCC information from the network.
6.4.1.2 Conformance requirement
1) An UE not supporting AoCC and in the outgoing call / U4 call delivered state, on receipt of a CONNECT message containing AoCC information shall acknowledge the CONNECT message but ignore and not acknowledge the AoCC information sent within the CONNECT.
2) An UE not supporting AoCC and in the outgoing call / U4 call delivered state, on receipt of a FACILITY message containing AoCC information shall ignore and not acknowledge the AoCC information sent within the FACILITY.
3) An UE not supporting AoCC and in the incoming call / U9 call confirmed state, on receipt of a FACILITY message containing AoCC information shall ignore and not acknowledge the AoCC information sent within the FACILITY.
4) An UE not supporting AoCC and in the U10 call active state, on receipt of a FACILITY message containing AoCC information, shall ignore and not acknowledge the AoCC information sent within the FACILITY.
References:
– TS 24.008 [16], clause 5.1.2.1;
– TS 23.086 [9], clauses 1.2, 1.3, 2.2 and 2.3;
– TS 24.086 [10], clause 2.
6.4.1.3 Test purpose
1) To verify that an UE not supporting AoCC (where the Terminal does support AoCC but the USIM does not) and in the outgoing call / U4 call delivered state, on receipt of a CONNECT message containing AoCC information shall acknowledge the CONNECT message but ignore and not acknowledge the AoCC information sent within the CONNECT.
2) To verify that an UE not supporting AoCC (where the Terminal does support AoCC but the USIM does not) and in the outgoing call / U4 call delivered state, on receipt of a FACILITY message containing AoCC information shall ignore and not acknowledge the AoCC information sent within the FACILITY.
3) To verify that an UE not supporting AoCC (where the Terminal does support AoCC but the USIM does not) and in the incoming call / U9 call confirmed state, on receipt of a FACILITY message containing AoCC information shall ignore and not acknowledge the AoCC information sent within the FACILITY.
4) To verify that an UE not supporting AoCC (where the Terminal does support AoCC but the USIM does not) and in the U10 call active state, on receipt of a FACILITY message containing AoCC information, shall ignore and not acknowledge the AoCC information sent within the FACILITY.
6.4.1.4 Method of test
6.4.1.4.1 Initial conditions
The Terminal shall be installed with a UICC or USIM simulator, with all elementary files coded as for the default UICC, with the exception of:
EFUST (USIM Service Table)
Logically: Local Phone Book available;
User controlled PLMN selector available;
Fixed dialling numbers available;
The GSM Access available;
The Group Identifier level 1 and level 2 not available;
AoC not available.
Service n 33 (Packed Switched Domain) shall be set to ‘1’
Enabled Services Table available
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
|
binary |
xxxx xx11 |
xxx0 xxxx |
xxxx 1×00 |
xxxx x1xx |
xxxx xx11 |
The coding of EFUST shall conform with the capabilities of the USIM used.
The generic call set up procedures for UTRAN defined in TS 34.108 [21], clause 7.2.3.2.3 and 7.2.3.1.3 and defined in TS 51.010‑1 [22], clause 10 for GERAN are followed up to and including the reception, or transmission of the ALERTING message by the UE.
6.4.1.4.2 Procedure
a) For an MO call in the U4 state the USS/SS transmits CONNECT containing AoCC information.
b) For an MO call in the U4 state the USS/SS transmits FACILITY containing AoCC information.
c) For an MT call in the U9 state the USS/SS transmits FACILITY containing AoCC information.
d) For an MO call in the U10 state the USS/SS transmits FACILITY containing AoCC information.
6.4.1.5 Acceptance criteria
In all cases, the UE shall ignore the AoCC information sent to it in the Facility information elements as part of the CONNECT/FACILITY messages and not send any AoCC information acknowledgement. It shall be checked for 15 s that the UE does not transmit any AoCC information acknowledgement after the receipt of AoCC information.
6.4.2 Maximum frequency of ACM updating
6.4.2.1 Definition and applicability
During a call, the ACM shall be updated at the end of every interval. The interval length is the greater of either 5 s or the value given by parameter e2 (part of the Facility Information Element).
6.4.2.2 Conformance requirement
The ACM shall be incremented when the CCM is incremented or once every 5 s, whichever is the longer period.
When used the value ‘1C’ shall be used as SFI for EFACM, for compatibility reasons the terminal shall accept other values.
Reference:
– TS 22.024 [8], clause 4.3, part h;
– TS 31.102 [4], clauses 4.2.9, 5.3.4 and Annex H.1.
6.4.2.3 Test purpose
1) To verify that the Terminal, during a call, increments the ACM every 5 s when e2 is less or equal to 5 s.
2) To verify that the Terminal is able to handle other values than ‘1C’ as SFI of EFACM.
6.4.2.4 Method of test
6.4.2.4.1 Initial conditions
The Terminal shall be connected to the USIM simulator, with all elementary files coded as default with the exception of:
EFUST (USIM Service Table)
Logically: Local Phone Book available;
User controlled PLMN selector available;
Fixed dialling numbers available;
The GSM Access available;
The Group Identifier level 1 and level 2 not available;
AoC available.
Service n 33 (Packed Switched Domain) shall be set to ‘1’
Enabled Services Table available
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
|
binary |
xxxx xx11 |
xxx1 xxxx |
xxxx 1×00 |
xxxx x1xx |
xxxx xx11 |
The coding of EFUST shall conform with the capabilities of the USIM used.
EFACM (Accumulated call meter)
Logically: 50 units
The SFI of EFACM shall be set to ’18’.
EFACMmax (Accumulated call meter maximum)
Logically: 150 units
The USS (in case of a Terminal accessing UTRAN)/ SS (in case of a Terminal accessing a GERAN) transmits on the BCCH, with the following network parameters:
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 246/081/0001.
– Access control: unrestricted.
User Equipment:
The UE is in MM-state "idle, updated".
In case of a Terminal accessing UTRAN "Expected Sequence A" and in case of a Terminal accessing a GERAN "Expected Sequence B" shall be performed.
6.4.2.4.2 Procedure
a) The UE is made to initiate a call. The call establishment shall be performed according to the procedures defined in TS 34.108 [21], clause 7.2.3.2.3 extended by the messages of the AoCC. The call is established with AoCC e-parameters sent in a Facility IE in the CONNECT message, as given below. The UE returns the AoCC acknowledgement after the reception of the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent by the UE before or after the CONNECT ACKNOWLEDGE.
b) The call is maintained for 90 s, then terminated by the USS. During the call, the USIM-simulator monitors the time intervals between successive INCREMENT commands. As the final INCREMENT command will have occurred as a result of call termination, the time interval calculated since the prior INCREMENT command shall be ignored.
Maximum Duration of Test:
2 minutes.
Expected Sequence A:
|
Step |
Direction |
Message |
Comments |
|
1 |
UE |
The UE is made to initiate a call |
|
|
2 |
UE -> USS |
RRC CONNECTION REQUEST |
|
|
3 |
USS -> UE |
RRC CONNECTION SETUP |
|
|
4 |
UE -> USS |
RRC CONNECTION SETUP COMPLETE |
|
|
5 |
UE -> USS |
CM SERVICE REQUEST |
|
|
6 |
USS -> UE |
AUTHENTICATION REQUEST |
MM procedure, to ensure the successful start of integrity in step 8 |
|
7 |
UE -> USS |
AUTHENTICATION RESPONSE |
|
|
8 |
USS -> UE |
SECURITY MODE COMMAND |
RRC procedure, start of integrity is mandatory during call setup |
|
9 |
UE -> USS |
SECURITY MODE COMPLETE |
|
|
10 |
UE -> USS |
SETUP |
|
|
11 |
USS -> UE |
CALL PROCEEDING |
|
|
12 |
USS -> UE |
RADIO BEARER SETUP |
To a supported channel type |
|
13 |
UE -> USS |
RADIO BEARER SETUPCOMPLETE |
|
|
14 |
USS -> UE |
ALERTING |
|
|
15 |
USS -> UE |
CONNECT |
As default message except contains Facility IE with contents as indicated in i) below |
|
Either A or B branch is taken |
|||
|
A16 |
UE -> USS |
CONNECT ACKNOWLEDGE |
|
|
A17 |
UE -> USS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii) below |
|
B16 |
UE -> USS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii) below |
|
B17 |
UE -> USS |
CONNECT ACKNOWLEDGE |
|
|
18 |
call duration 90 s after CAI information sent by USS, |
||
|
19 |
USS -> UE |
DISCONNECT |
|
|
20 |
UE -> USS |
RELEASE |
|
|
21 |
USS -> UE |
RELEASE COMPLETE |
|
|
22 |
USS -> UE |
RRC CONNECTION RELEASE |
All connections of RRC are released. |
|
23 |
UE -> USS |
RRC CONNECTION RELEASE COMPLETE |
Expected Sequence B:
|
Step |
Direction |
Message |
Comments |
|
1 |
UE |
The UE is made to initiate a call |
|
|
2 |
UE -> SS |
CHANNEL REQUEST |
|
|
3 |
SS -> UE |
IMMEDIATE ASSIGNMENT |
|
|
4 |
UE -> SS |
CM SERVICE REQUEST |
|
|
5 |
SS -> UE |
CM SERVICE ACCEPT |
|
|
6 |
UE -> SS |
SETUP |
|
|
7 |
SS -> UE |
CALL PROCEEDING |
|
|
8 |
SS -> UE |
ASSIGNMENT COMMAND |
To a supported channel type |
|
9 |
UE -> SS |
ASSIGNMENT COMPLETE |
|
|
10 |
SS -> UE |
ALERTING |
|
|
11 |
SS -> UE |
CONNECT |
As default message except contains Facility IE with contents as indicated in i) below |
|
Either A or B branch is taken |
|||
|
A12 |
UE -> SS |
CONNECT ACKNOWLEDGE |
|
|
A13 |
UE -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii) below |
|
B12 |
UE -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii) below |
|
B13 |
UE -> SS |
CONNECT ACKNOWLEDGE |
|
|
14 |
call duration 90 s after CAI information sent by SS, |
||
|
15 |
SS -> UE |
DISCONNECT |
|
|
16 |
UE -> SS |
RELEASE |
|
|
17 |
SS -> UE |
RELEASE COMPLETE |
|
|
18 |
SS -> UE |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeInformation component type as defined in TS 24.080 [17], clause 3.6.1 table 3.3.
For ASN.1 description see default message contents in TS 51.010‑1 [22], clause 31.6.4.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set as below:
e-parameters:
|
parameter: |
e1 |
e2 |
e3 |
e4 |
e5 |
e6 |
E7 |
|
value |
1 |
1 |
1 |
0 |
0 |
0 |
0 |
Values shown in table are in the format and have units as in TS 22.024 [8], clause 3.
ii) FACILITY Information Element with Return Result component type as defined in TS 24.080 [17], clause 3.6.1 table 3.4.
For ASN.1 description see default message contents in TS 51.010‑1 [22], clause 31.6.4.
6.4.2.5 Acceptance criteria
The UE shall, during a call, send INCREMENT commands to the USIM every 5 s.
6.4.3 Call terminated when ACM greater than ACMmax
6.4.3.1 Definition and applicability
ACMmax gives the maximum value of ACM, at which the current chargeable calls shall be terminated and no further calls may be made (except emergency calls).
6.4.3.2 Conformance requirement
ACM shall be incremented by the value of CCM.
If the ACMmax is valid, and the ACM becomes equal to or exceeds the value of the ACMmax, then all calls in progress, chargeable to the user, shall be terminated by the UE, once the chargeable interval determined by the CAI has elapsed, (except emergency calls).
When used the value ‘1C’ shall be used as SFI for EFACM, for compatibility reasons the terminal shall accept other values.
Reference:
– TS 22.024 [8], clauses 4.2.2 and 4.3 (part h);
– ETSI TS 102 221 [5], clause 14.1.3;
– TS 31.102 [4], clause 4.2.9, 5.3.4 and Annex H.1.
6.4.3.3 Test purpose
1) To verify that the Terminal increments the ACM by the correct number of units, even though this may take ACM above ACMmax.
2) To verify that the Terminal terminates the call.
3) To verify that the INCREMENT EFACM command is performed correctly by the terminal.
4) To verify that the Terminal is able to handle other values than ‘1C’ as SFI of EFACM.
6.4.3.4 Method of test
6.4.3.4.1 Initial conditions
The Terminal shall be connected to a UICC or the USIM simulator, with all elementary files coded as default with the exception of:
EFUST (USIM Service Table)
Logically: Local Phone Book available;
User controlled PLMN selector available;
Fixed dialling numbers available;
The GSM Access available;
The Group Identifier level 1 and level 2 not available;
AoC available.
Service n 33 (Packed Switched Domain) shall be set to ‘1’
Enabled Services Table available
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
|
binary |
xxxx xx11 |
xxx1 xxxx |
xxxx 1×00 |
xxxx x1xx |
xxxx xx11 |
The coding of EFUST shall conform with the capabilities of the USIM used.
EFACM (Accumulated call meter)
Logically: 80 units
|
Coding: |
B1 |
B2 |
B3 |
|
binary |
0000 0000 |
0000 0000 |
0101 0000 |
The SFI of EFACM shall be set to ’18’.
EFACMmax (Accumulated call meter maximum)
Logically: 94 units
|
Coding: |
B1 |
B2 |
B3 |
|
binary |
0000 0000 |
0000 0000 |
0101 1110 |
The USS transmits on the BCCH, with the following network parameters:
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 246/081/0001.
– Access control: unrestricted.
User Equipment:
The UE is in MM-state "idle, updated".
In case of a Terminal accessing UTRAN "Expected Sequence A" and in case of a Terminal accessing a GERAN "Expected Sequence B" shall be performed.
6.4.3.4.2 Procedure
a) The UE is made to initiate a call. The call establishment shall be performed according to the procedures defined in TS 34.108 [21], clause 7.2.3.2.3 extended by the messages of the AoCC. The call is established with AoCC e-parameters sent in a Facility IE in the CONNECT message, as given below. The UE returns the AoCC acknowledgement after the reception of the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent by the UE before or after the CONNECT ACKNOWLEDGE.
b) The call is maintained until cleared by the UE (after 30 s).
c) The contents of ACM are checked.
Maximum Duration of Test:
2 minutes.
Expected Sequence A:
|
Step |
Direction |
Message |
Comments |
|
1 |
UE |
The UE is made to initiate a call |
|
|
2 |
UE -> USS |
RRC CONNECTION REQUEST |
|
|
3 |
USS -> UE |
RRC CONNECTION SETUP |
|
|
4 |
UE -> USS |
RRC CONNECTION SETUP COMPLETE |
|
|
4A |
UE -> USS |
CM SERVICE REQUEST |
|
|
5 |
USS -> UE |
AUTHENTICATION REQUEST |
MM procedure, to ensure the successful start of integrity in step 8 |
|
6 |
UE -> USS |
AUTHENTICATION RESPONSE |
|
|
7 |
USS -> UE |
SECURITY MODE COMMAND |
RRC procedure, start of integrity is mandatory during call setup |
|
8 |
UE -> USS |
SECURITY MODE COMPLETE |
|
|
9 |
UE -> USS |
SETUP |
|
|
10 |
USS -> UE |
CALL PROCEEDING |
|
|
11 |
USS -> UE |
RADIO BEARER SETUP |
To a supported channel type |
|
12 |
UE -> USS |
RADIO BEARER SETUP COMPLETE |
|
|
13 |
USS -> UE |
ALERTING |
|
|
14 |
USS -> UE |
CONNECT |
As default message except contains Facility IE with contents as indicated in i) below |
|
Either A or B branch is taken |
|||
|
A15 |
UE -> USS |
CONNECT ACKNOWLEDGE |
|
|
A16 |
UE -> USS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii) below |
|
B15 |
UE -> USS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii) below |
|
B16 |
UE -> USS |
CONNECT ACKNOWLEDGE |
|
|
17 |
call duration 30 s after CAI information sent by USS |
||
|
18 |
UE -> USS |
DISCONNECT |
|
|
19 |
USS -> UE |
RELEASE |
|
|
20 |
UE -> USS |
RELEASE COMPLETE |
|
|
21 |
USS -> UE |
RRC CONNECTION RELEASE |
All connections of RRC are released. |
|
22 |
UE -> USS |
RRC CONNECTION RELEASE COMPLETE |
Expected Sequence B:
|
Step |
Direction |
Message |
Comments |
|
1 |
UE |
The UE is made to initiate a call |
|
|
2 |
UE -> SS |
CHANNEL REQUEST |
|
|
3 |
SS -> UE |
IMMEDIATE ASSIGNMENT |
|
|
4 |
UE -> SS |
CM SERVICE REQUEST |
|
|
5 |
SS -> UE |
CM SERVICE ACCEPT |
|
|
6 |
UE -> SS |
SETUP |
|
|
7 |
SS -> UE |
CALL PROCEEDING |
|
|
8 |
SS -> UE |
ASSIGNMENT COMMAND |
To a supported channel type |
|
9 |
UE -> SS |
ASSIGNMENT COMPLETE |
|
|
10 |
SS -> UE |
ALERTING |
|
|
11 |
SS -> UE |
CONNECT |
As default message except contains Facility IE with contents as indicated in i) below |
|
Either A or B branch is taken |
|||
|
A12 |
UE -> SS |
CONNECT ACKNOWLEDGE |
|
|
A13 |
UE -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii) below |
|
B12 |
UE -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii) below |
|
B13 |
UE -> SS |
CONNECT ACKNOWLEDGE |
|
|
14 |
call duration 30 s after CAI information sent by SS |
||
|
15 |
UE -> SS |
DISCONNECT |
|
|
16 |
SS -> UE |
RELEASE |
|
|
17 |
UE -> SS |
RELEASE COMPLETE |
|
|
18 |
SS -> UE |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeInformation component type as defined in TS 24.080 [17], clause 3.6.1 table 3.3.
For ASN.1 description see default message contents in TS 51.010‑1 [22], clause 31.6.4.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set as below:
e-parameters:
|
parameter: |
e1 |
e2 |
e3 |
e4 |
e5 |
e6 |
e7 |
|
value |
10 |
10 |
1 |
0 |
0 |
0 |
0 |
Values shown in table are in the format and have units as in TS 22.024 [8], clause 3.
ii) FACILITY Information Element with Return Result component type as defined in TS 24.080 [17], clause 3.6.1 table 3.4.
For ASN.1 description see default message contents in TS 51.010‑1 [22], clause 31.6.4.
6.4.3.5 Acceptance criteria
1) The UE shall terminate the call correctly 30 s after CAI was sent.
2) The value of ACM shall be 100 units.
6.4.4 Response codes of increase command of ACM
6.4.4.1 Definition and applicability
ACM has a maximum value in terms of coding, and an attempt by the Terminal to exceed that value by sending an INCREASE command shall result in an error message from the USIM. As the maximum of the ACM is equal to the maximum value of ACMmax, all current chargeable calls shall be terminated and no further calls may be made (except emergency calls).
6.4.4.2 Conformance requirement
The Terminal shall perform the increasing procedure, sending the amount to be increased.
The running accumulated charge shall be stored in the ACM of the USIM.
Where this charge cannot be stored in the UE, use of the telecommunications service shall be prevented.
At the time ACM exceeds it’s maximum value, then all calls in progress, chargeable to the user, shall be terminated by the UE, once the chargeable interval determined by the CAI has elapsed, (except emergency calls).
When used the value ‘1C’ shall be used as SFI for EFACM, for compatibility reasons the terminal shall accept other values.
References:
– TS 31.102 [4], clauses 4.2.9, 5.3.4 and Annex H.1;
– TS 22.086 [18], clauses 2.1 and 2.2.1.
6.4.4.3 Test purpose
1) To verify that the Terminal clears a charged call if the USIM indicates that the ACM cannot be increased.
2) To verify that the Terminal is able to handle other values than "1C" as SFI of EFACM.
6.4.4.4 Method of test
6.4.4.4.1 Initial conditions
The Terminal shall be connected to the USIM simulator, with all elementary files coded as default with the exception of:
EFUST (USIM Service Table)
Logically: Local Phone Book available;
User controlled PLMN selector available;
Fixed dialling numbers available;
The GSM Access available;
The Group Identifier level 1 and level 2 not available;
AoC available.
Service n 33 (Packed Switched Domain) shall be set to ‘1’
Enabled Services Table available
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
|
binary |
xxxx xx11 |
xxx1 xxxx |
xxxx 1×00 |
xxxx x1xx |
xxxx xx11 |
The coding of EFUST shall conform with the capabilities of the USIM used.
EFACM (Accumulated call meter)
Logically: (Maximum value – 10) units
|
Coding: |
B1 |
B2 |
B3 |
|
binary |
1111 1111 |
1111 1111 |
1111 0101 |
The SFI of EFACM shall be set to "18".
EFACMmax (Accumulated call meter maximum)
Logically: (Maximum value – 2) units
|
Coding: |
B1 |
B2 |
B3 |
|
binary |
1111 1111 |
1111 1111 |
1111 1101 |
The USS transmits on the BCCH, with the following network parameters:
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 246/081/0001.
– Access control: unrestricted.
User Equipment:
The UE is in MM-state "idle, updated".
In case of a Terminal accessing UTRAN "Expected Sequence A" and in case of a Terminal accessing a GERAN "Expected Sequence B" shall be performed.
6.4.4.4.2 Procedure
a) The UE is made to initiate a call. The call establishment shall be performed according to the procedures defined in TS 34.108 [21], clause 7.2.3.2.3 extended by the messages of the AoCC. The call is established with AoCC e-parameters sent in a Facility IE in the CONNECT message, as given below. The UE returns the AoCC acknowledgement after reception of the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent by the UE before or after the CONNECT ACKNOWLEDGE.
b) After an interval has elapsed, the Terminal increments the ACM. When an INCREASE command is received, the USIM-simulator sends back the error "98 50".
c) Conditions are reset to those described in the initial conditions. Steps a) and b) of the test are repeated, except that the error code sent by the USIM simulator at step b) is now "6F xx".
d) Conditions are reset to those described in the initial conditions. Steps a) and b) of the test are repeated, except that the error code sent by the USIM simulator at step b) is now "65 81".
References:
– ETSI TS 102 221 [5], clause 10.2.1.
Maximum Duration of Test:
3 minutes.
Expected Sequence A:
|
Step |
Direction |
Message |
Comments |
|
1 |
UE |
The UE is made to initiate a call |
|
|
2 |
UE -> USS |
RRC CONNECTION REQUEST |
|
|
3 |
USS -> UE |
RRC CONNECTION SETUP |
|
|
4 |
UE -> USS |
RRC CONNECTION SETUP COMPLETE |
|
|
4A |
UE -> USS |
CM SERVICE REQUEST |
|
|
5 |
USS -> UE |
AUTHENTICATION REQUEST |
MM procedure, to ensure the successful start of integrity in step 8 |
|
6 |
UE -> USS |
AUTHENTICATION RESPONSE |
|
|
7 |
USS -> UE |
SECURITY MODE COMMAND |
RRC procedure, start of integrity is mandatory during call setup |
|
8 |
UE -> USS |
SECURITY MODE COMPLETE |
|
|
9 |
|||
|
10 |
UE -> USS |
SETUP |
|
|
11 |
USS -> UE |
CALL PROCEEDING |
|
|
12 |
USS -> UE |
RADIO BEARER SETUP |
To a supported channel type |
|
13 |
UE -> USS |
RADIO BEARER SETUP COMPLETE |
|
|
14 |
USS -> UE |
ALERTING |
|
|
15 |
USS -> UE |
CONNECT |
As default message except contains Facility IE with contents as indicated in i) below |
|
Either A or B branch is taken |
|||
|
A16 |
UE -> USS |
CONNECT ACKNOWLEDGE |
|
|
A17 |
UE -> USS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii) below |
|
B16 |
UE -> USS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii) below |
|
B17 |
UE -> USS |
CONNECT ACKNOWLEDGE |
|
|
18 |
call duration 10s after CAI information sent by USS |
||
|
19 |
UE -> USS |
DISCONNECT |
|
|
20 |
USS -> UE |
RELEASE |
|
|
21 |
UE -> USS |
RELEASE COMPLETE |
|
|
22 |
USS -> UE |
RRC CONNECTION RELEASE |
All connections of RRC are released. |
|
23 |
UE -> USS |
RRC CONNECTION RELEASE COMPLETE |
Expected Sequence B:
|
Step |
Direction |
Message |
Comments |
|
1 |
UE |
The UE is made to initiate a call |
|
|
2 |
UE -> SS |
CHANNEL REQUEST |
|
|
3 |
SS -> UE |
IMMEDIATE ASSIGNMENT |
|
|
4 |
UE -> SS |
CM SERVICE REQUEST |
|
|
5 |
SS -> UE |
CM SERVICE ACCEPT |
|
|
6 |
UE -> SS |
SETUP |
|
|
7 |
SS -> UE |
CALL PROCEEDING |
|
|
8 |
SS -> UE |
ASSIGNMENT COMMAND |
To a supported channel type |
|
9 |
UE -> SS |
ASSIGNMENT COMPLETE |
|
|
10 |
SS -> UE |
ALERTING |
|
|
11 |
SS -> UE |
CONNECT |
As default message except contains Facility IE with contents as indicated in i) below |
|
Either A or B branch is taken |
|||
|
A12 |
UE -> SS |
CONNECT ACKNOWLEDGE |
|
|
A13 |
UE -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii) below |
|
B12 |
UE -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii) below |
|
B13 |
UE -> SS |
CONNECT ACKNOWLEDGE |
|
|
14 |
call duration 10s after CAI information sent by SS |
||
|
15 |
UE -> SS |
DISCONNECT |
|
|
16 |
SS -> UE |
RELEASE |
|
|
17 |
UE -> SS |
RELEASE COMPLETE |
|
|
18 |
SS -> UE |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeInformation component type as defined in TS 24.080 [17], clause 3.6.1 table 3.3.
For ASN.1 description see default message contents in TS 51.010‑1 [22], clause 31.6.4.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set as below:
e-parameters:
|
parameter: |
e1 |
e2 |
e3 |
e4 |
e5 |
e6 |
e7 |
|
value |
20 |
10 |
1 |
0 |
0 |
0 |
0 |
Values shown in table are in the format and have units as in TS 22.024 [8], clause 3.
ii) FACILITY Information Element with Return Result component type as defined in TS 24.080 [17], clause 3.6.1 table 3.4.
For ASN.1 description see default message contents in TS 51.010‑1 [22], clause 31.6.4.
6.4.4.5 Acceptance criteria
1) The UE shall terminate the call correctly 10 s after CAI was sent.
2) In each of the three cases, as described in steps b), c) and d) of the procedure, the UE shall terminate the call correctly when it receives an indication from the USIM that the ACM cannot be incremented.