6 Security related Tests
31.1273GPPnon-removable Universal Subscriber Identity Module (nrUSIM) application behavioural test specificationRelease 17TSUICC-terminal interaction
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
CR 1 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 UE asks the user for PIN verification
CR 2 The VERIFY PIN function verifies the PIN presented by the ME to the UICC.
CR 3 Indication of a successful pin verification is presented to user.
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
The purpose of this test is to verify that:
1) the PIN verification procedure is performed by the ME correctly,
2) the basic public MMI string is supported.
6.1.1.4 Method of test
6.1.1.4.1 Initial conditions
Ensure that the UE has been operated with an USIM with PIN enabled, and powered off.
The values of the Default UICC as defined in clause 4.5.1 of the present document are used.
The UICC/USIM configuration defined for this test case is installed in the UE.
6.1.1.4.2 Procedure
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE |
The ME is powered on. |
|||
|
2 |
Tester > UE |
When the UE is in the "PIN check" mode, the sequence "0000#" shall be entered. |
CR1 |
||
|
UE > UICC |
VERIFY PIN |
This is verifiable if A.2/x is supported, else skip this verification |
CR2 |
A.2/1 OR A.2/2 |
|
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure is successful |
CR3 |
6.1.1.5 Acceptance criteria
CR 1 is met if the ME asks the user for the PIN verification.
CR 2 can be explicitly verified at step 2) via supported options A.2/1 OR A.2/2, ensuring that the VERIFY PIN command is correctly sent via the terminal to the UICC, with parameter P2 = "01".
CR 3 is verified on the ME. CR 3 is met if an indication is given to the user showing that this procedure was executed successfully, e.g. by displaying "OK".
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
CR1 The ME shall support the change of PIN procedure as defined in ETSI TS 102 221 [5], clause 11.1.10.
CR2 Indication of a successful pin change is presented to the user, and only the new pin shall be accepted for further PIN verification.
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
The purpose of this test is to verify that:
1) the PIN substitution procedure is performed correctly by the ME,
2) the basic public MMI string is supported,
3) the old PIN shall no longer be accepted,
4) the new PIN shall be accepted.
6.1.2.4 Method of test
6.1.2.4.1 Initial conditions
Ensure that the UE has been operated with an USIM with PIN enabled, and powered off.
The values of the Default UICC as defined in clause 4.5.1 of the present document are used.
The UICC/USIM configuration defined for this test case is installed in the UE.
6.1.2.4.2 Procedure
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE |
The ME is powered on. |
|||
|
2 |
Tester > UE |
When the UE is in the "PIN check" mode, the sequence "0000#" shall be entered. |
|||
|
3 |
Tester > UE |
After USIM initialisation is completed, enter "**04*0000*01234567*01234567#" or initiate an equivalent MMI dependent procedure to change the PIN from ‘0000’ to ‘01234567’ |
|||
|
UE > UICC |
CHANGE PIN |
This is verifiable only if A.2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
UICC > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure is successful |
CR2 |
||
|
4 |
UE |
The ME is switched off and on. |
|||
|
5 |
Tester > UE |
When the UE is in the "PIN check" mode, the sequence "0000#" shall be entered. |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A.2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure is unsuccessful |
CR2 |
||
|
6 |
UE |
The ME is switched off and on. |
|||
|
7 |
Tester > UE |
When the UE is in the "PIN check" mode, the sequence "01234567#" shall be entered. |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A.2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure is successful |
CR2 |
6.1.2.5 Acceptance criteria
CR 1 is explicitly verified at:
- step 3) by analysing the CHANGE PIN command;
- step 5) and step 7) by analysing the VERIFY PIN command;
sent via the ME to the UICC, with parameter P2 = "01" (via any supported option A.2/1 OR A.2/2).
CR 2 is verified at:
– step 3) on the ME by ensuring that an indication of a successful execution of the command and the acceptance of the new PIN is given;
– step 5) on the ME by ensuring that an indication of an unsuccessful execution of the command is given;
– step 7) on the ME by ensuring that an indication of a successful execution of the command is given.
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
CR 1 The Terminal shall support the Unblock PIN command, as defined in ETSI TS 102 221 [5], clause 11.1.13.
CR 2 Indication of a successful and unsuccessful unblock PIN is presented to user
CR 3 Only the new pin shall be accepted for further PIN verification.
CR 4 Indication of a successful and unsuccessful pin verification is presented to the user and only the new pin shall be accepted for further PIN verification.
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
The purpose of this test is to verify that:
1) the PIN unblocking procedure is performed correctly,
2) the basic public MMI string is supported,
6.1.3.4 Method of test
6.1.3.4.1 Initial conditions
Ensure that the UE has been operated with an USIM with PIN enabled, and powered off.
The Default UICC is used.
The UICC/USIM configuration defined for this test case is installed in the UE.
6.1.3.4.2 Procedure
Sequence A:
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE |
The ME is powered on and the correct PIN is entered. |
(If test 6.1.2 has been executed before this probably is "01234567#") |
||
|
2 |
Tester > UE |
After USIM initialisation is completed, enter "**05*11111111*1234*1234#" |
|||
|
UE > UICC |
UNBLOCK PIN |
This is verifiable only if A.2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR2 |
||
|
3 |
UE |
The ME is switched off and on. |
|||
|
4 |
Tester > UE |
When the UE is in the "PIN check" mode, enter the new PIN: "1234#" |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A.2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR4 |
||
|
5 |
UE |
The ME is switched off and on. |
|||
|
6 |
Tester > UE |
Enter a wrong PIN three times. |
|||
|
UE > UICC |
VERIFY PIN |
This is repeated 3x, and is verifiable only if A.2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be unsuccessful |
CR4 |
||
|
7 |
Tester > UE |
Enter "**05*11111111*2468*2468#". |
|||
|
UE > UICC |
UNBLOCK PIN |
This is verifiable only if A.2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR2 |
||
|
8 |
Tester > UE |
When the UE is in the "PIN check" mode, enter the new PIN: "2468#" |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A.2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR4 |
Sequence B:
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE |
The ME is powered on. |
|||
|
2 |
Tester > UE |
Enter a wrong PIN three times. |
|||
|
3 |
Tester > UE |
The user shall initiate an MMI dependent procedure to unblock the PIN with unblock code ‘11111111’ and a new PIN ‘2468’ ("**05*11111111*2468*2468#") |
|||
|
UE > UICC |
UNBLOCK PIN |
This is verifiable only if A.2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR2 |
||
|
4 |
UE |
The ME is switched off and on. |
|||
|
5 |
Tester > UE |
When the UE is in the "PIN check" mode, enter the new PIN: "2468#" |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A.2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR4 |
6.1.3.5 Acceptance criteria
Sequence A:
CR 1 is explicitly verified at step 2) and step 7) by analysing the UNBLOCK PIN command sent via the terminal to the UICC, with parameter P2 = "01" (via any supported options A.2/1 OR A.2/2).
CR 2 is verified at step 2) and step 7) on the terminal by ensuring UE shall give an indication following a successful execution of the command and new PIN is accepted.
CR 3 is explicitly verified at step 4), step 6) and step 8) by analysing the status word for both successful and unsuccessful PIN entry.
CR 4 is verified at (i) step 4) and step 8) on the terminal by ensuring UE shall give an indication of a successful execution of the command and PIN is accepted, (ii) at step 6) on terminal by ensuring UE shall give an indication that execution of the command failed.
Sequence B:
CR 1 is explicitly verified at step 3) by analysing the UNBLOCK PIN command sent via the ME to the UICC, with parameter P2 = "01" (via any supported options A.2/1 OR A.2/2) after Terminal indicates that PIN has been blocked in step 2).
CR 2 is verified at step 3) on the ME by ensuring UE shall give an indication following a successful execution of the command and new PIN is accepted.
CR 3 is explicitly verified at step 5) by analysing the status word for successful PIN entry.
CR 4 is verified at step 5) the requirement is met if the UE gets an indication that the PIN is accepted after the successful entry of the correct PIN value.
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
CR 1 Before allowing the access to PIN2 protected data, the ME shall ask the user for PIN2 verification. Only after presenting the PIN2, the user shall get access to these data.
CR 2 The VERIFY PIN function verifies the PIN2 presented by the ME to the UICC.
CR 3 Indication of a successful PIN2 verification is presented to the user.
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
Ensure that the UE has been operated with an USIM with PIN enabled, and powered off.
The Default UICC is used.
The UICC/USIM configuration defined for this test case is installed in the UE.
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
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE |
The ME is powered on. |
|||
|
2 |
Tester > UE |
When the UE is in the "PIN check" mode, correct PIN shall be entered. |
|||
|
3 |
The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN) |
||||
|
4 |
When the UE is in the "PIN2 check" mode, the sequence "9999#" shall be entered. |
||||
|
UE |
VERIFY PIN |
This is verifiable if A.2/x is supported, else skip this verification |
CR1 |
A.2/1 OR A2/2 |
|
|
UE > Tester |
An indication is given to the tester showing whether this procedure was successful |
This procedure shall be successful |
CR2 |
6.1.4.5 Acceptance criteria
CR 1 is explicitly verified at step 4) via supported options A.2/1 OR A.2/2, ensuring that the VERIFY PIN command is correctly sent via the ME to the UICC, with parameter P2 = "81".
CR 2 is verified on the ME. CR 2 is met if an indication is given to the user showing that this procedure was executed successfully, e.g. by displaying "OK".
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
CR 1 The ME shall support the change of PIN2 procedure as defined in ETSI TS 102 221 [5], clause 11.1.10.
CR 2 Indication of a successful pin change is presented to user, and only the new pin shall be accepted for further PIN verification.
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.
3) To verify that the old PIN shall no longer be accepted.
4) To verify that the new PIN shall be accepted.
6.1.5.4 Method of test
6.1.5.4.1 Initial conditions
Ensure that the UE has been operated with an USIM with PIN enabled, and powered off.
The Default UICC is used.
The UICC/USIM configuration defined for this test case is installed in the UE.
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
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
Tester > UE |
After USIM initialisation is completed, enter "**042*9999*12345678*12345678#" or initiate an equivalent MMI dependent procedure to change the PIN2 from ‘9999’ to ‘12345678’ |
|||
|
UE > UICC |
CHANGE PIN |
This is verifiable only if A.2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM> UE |
Check Status word |
||||
|
UE |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR2 |
||
|
2 |
UE |
The Terminal is switched off and on and the correct PIN is entered. |
|||
|
3 |
The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN) |
||||
|
4 |
Tester > UE |
When the UE is in the "PIN2 check" mode, incorrect sequence "9999#" shall be entered. |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A.2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be unsuccessful |
CR2 |
||
|
5 |
UE |
The Terminal is switched off and on. |
|||
|
6 |
The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN) |
||||
|
7 |
Tester > UE |
When the UE is in the "PIN check" mode, the sequence "12345678#" shall be entered. |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A.2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM> UE |
Check Status word |
||||
|
UE |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR2 |
6.1.5.5 Acceptance criteria
CR 1 is explicitly verified at:
– step 1) by analysing the CHANGE PIN command;
– step 4) and step 7) by analysing the VERIFY PIN sent via the ME to the UICC, with parameter P2 =
"81" (via any supported options A.2/1 OR A.2/2).
CR 2 is verified (i) at:
– step 1). CR 2 is met if an indication is given to the user showing that this procedure was executed successfully,
and new PIN is accepted, e.g. by displaying "OK";
– step 4). CR 2 is met if an indication is given to the user showing that the command failed;
– step 7). CR 2 is met if an indication is given to the user showing that the command was executed successfully.
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
CR 1 The Terminal shall support the Unblock PIN2 command, as defined in ETSI TS 102 221 [5], clause 11.1.13.
CR 2 Indication of a successful unblock PIN2 is presented to user
CR 3 Only the new pin2 shall be accepted for further PIN2 verification.
CR 4 Indication of a successful and unsuccessful pin2 verification is presented to user and only the new pin2 shall be accepted for further PIN2 verification.
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
Ensure that the UE has been operated with an USIM with PIN enabled, and powered off.
The Default UICC is used.
The UICC/USIM configuration defined for this test case is installed in the UE.
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:
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE |
The Terminal is powered on and the correct PIN is entered. |
|||
|
2 |
Tester > UE |
After USIM initialisation is completed, enter "**052*22222222*1234*1234#" |
|||
|
UE > UICC |
UNBLOCK PIN |
This is verifiable only if A2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR2 |
||
|
3 |
UE |
The Terminal is switched off and on and the correct PIN is entered. |
|||
|
4 |
The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN) |
||||
|
5 |
Tester > UE |
Enter the new PIN2: "1234#" |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR4 |
||
|
6 |
UE |
The Terminal is switched off and on and the correct PIN is entered. |
|||
|
7 |
The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN) |
||||
|
8 |
Tester > UE |
Enter a wrong PIN2 three times. |
|||
|
UE > UICC |
VERIFY PIN |
This is repeated 3x, and is verifiable only if A2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM> UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be unsuccessful |
CR4 |
||
|
9 |
Tester > UE |
Enter "**052*22222222*3579*3579#". |
|||
|
UE > UICC |
UNBLOCK PIN |
This is verifiable only if A2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM> UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR2 |
||
|
10 |
UE |
The Terminal is switched off and on and the correct PIN is entered. |
|||
|
11 |
The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN) |
||||
|
12 |
Tester > UE |
Enter the new PIN2: "3579#" |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR4 |
Sequence B:
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE |
The Terminal is powered on and the correct PIN is entered. |
|||
|
2 |
Tester > UE |
Enter a wrong PIN2 three times. |
|||
|
3 |
Tester > UE |
The user shall initiate an MMI dependent procedure to unblock the PIN2 with unblock code ‘22222222’ and a new PIN ‘3579’ |
|||
|
UE > UICC |
UNBLOCK PIN |
This is verifiable only if A2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM> UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR2 |
||
|
4 |
UE |
The Terminal is switched off and on and the correct PIN is entered. |
|||
|
5 |
The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN) |
||||
|
6 |
Tester > UE |
Enter the new PIN2: "3579#" |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR4 |
6.1.6.5 Acceptance criteria
Sequence A:
CR 1 is explicitly verified at step 2) and step 9) by analysing the UNBLOCK PIN command sent via Terminal to the UICC, with parameter P2 = "81" (via any supported options A.2/1 OR A.2/2).
CR 2 is verified at step 2) and step 9) on the terminal by ensuring UE shall give an indication of a successful execution of the command and new PIN2 is accepted.
CR 3 is explicitly verified at step 5), step 8) and step 12) by analysing the Status word for both successful and unsuccessful PIN2 entry.
CR 4 is verified at (i) step 5) and step 12) on the terminal by ensuring UE shall give an indication of a successful execution of the command and PIN2 is accepted, (ii) at step 8) on terminal by ensuring UE shall give an indication that execution of the command failed.
Sequence B:
CR 1 is explicitly verified at step 3) by analysing the UNBLOCK PIN command sent via Terminal to the UICC, with parameter P2 = "81" (via any supported options A.2/1 OR A.2/2) after Terminal indicates that PIN has been blocked in step2.
CR 2 is verified at step 3) on the terminal by ensuring UE shall give an indication following a successful execution of the command and new PIN2 is accepted.
CR 3 is explicitly verified at step 6) by analysing the Status word for successful PIN2 entry.
CR 4 is verified at step 6) on the terminal by ensuring UE shall give an indication following a successful execution of the command that PIN2 is 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
CR 1 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.
CR 2 The Terminal shall support the procedure to disable the replacement defined in ETSI TS 102 221 [5], clause 11.1.12.
CR 3 Only the new pin shall be accepted for further PIN verification.
CR 4 Indication of a successful and unsuccessful pin verification is presented to the user and only the new pin shall be accepted for further PIN verification
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
Ensure that the UE has been operated with an USIM with PIN enabled, and powered off.
The Default UICC is used.
The UICC/USIM configuration defined for this test case is installed in the UE.
6.1.7.4.2 Procedure
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE |
The Terminal is powered on. |
|||
|
2 |
Tester > UE |
When the UE is in the "PIN check" mode, the sequence "2468#" shall be entered. |
|||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
|||
|
3 |
Tester > UE |
The user shall initiate an MMI dependent procedure to replace the PIN by the Universal PIN. |
|||
|
UE > UICC |
DISABLE PIN |
This is verifiable only if A2/x is supported. |
CR1 |
||
|
USIM > UE |
Check Status word |
||||
|
4 |
UE > Tester |
The Terminal is switched off and on. |
|||
|
5 |
Tester > UE |
When the UE is in the "PIN check" mode, the sequence "2468#" shall be entered. |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be unsuccessful |
CR4 |
||
|
6 |
The correct Universal PIN is entered. |
||||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR4 |
||
|
7 |
Initiate an MMI dependent procedure to disable the replacement of the PIN by the Universal PIN |
||||
|
UE > UICC |
ENABLE PIN |
This is verifiable only if A2/x is supported. |
CR2 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
8 |
UE > Tester |
The Terminal is switched off and on. |
|||
|
9 |
Tester > UE |
When the UE is in the "PIN check" mode, the sequence "2839#" shall be entered. |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be unsuccessful |
CR4 |
||
|
10 |
Tester > UE |
When the UE is in the "PIN check" mode correct PIN is entered. |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR4 |
6.1.7.5 Acceptance criteria
CR 1 is explicitly verified at step 3 by analysing the DISABLE PIN command sent via the terminal to the UICC, with parameter P1 = "91" and P2 = "01" (via any supported options A.2/1 OR A2/2).
CR 2 is explicitly verified at step 7) by analysing the ENABLE PIN command sent via the terminal to the UICC, with parameter P2 = "01" (via any supported options A.2/1 OR A2/2)
CR 3 is explicitly verified at (i) step 5) by analysing the status word indicating that the PIN has not been accepted for the VERIFY PIN command sent by the terminal to the UICC, with parameter P2 = "11", (ii) step 6) by analysing the status word indicating that the PIN has been accepted for the VERIFY PIN command sent by the terminal to the UICC, with parameter P2 = "11", (iii) step 9) by analysing the status word indicating that the PIN has not been accepted for the VERIFY PIN command sent by the terminal to the UICC, with parameter P2 = "01", (ii) step 10) by analysing the status word indicating that the PIN has been accepted for the VERIFY PIN command sent by the terminal to the UICC, with parameter P2 = "01".
CR 4 is verified (i) at step 5) and 9) on the terminal by ensuring UE shall give an indication of an unsuccessful execution of the command and PIN is not accepted, (ii) at step 6) and 10) on the terminal by ensuring UE shall give an indication of a successful execution of the command and PIN is 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
CR 1 The Terminal shall support the change of PIN procedure as defined in ETSI TS 102 221 [5], clause 11.1.10.
CR 2 Only the new pin shall be accepted for further PIN verification.
CR 3 Indication of a successful and unsuccessful pin verification is presented to the user and only the new pin shall be accepted for further PIN verification
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
Ensure that the UE has been operated with an USIM with PIN enabled, and powered off.
The Default UICC is used with the following exception:
– The Universal PIN is used as a replacement of the PIN.
The UICC/USIM configuration defined for this test case is installed in the UE.
The Terminal is powered-on, with the correct Universal PIN entered.
6.1.8.4.2 Procedure
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
Tester > UE |
The user shall initiate an MMI dependent procedure to change the Universal PIN to "01234567". |
|||
|
UE > UICC |
CHANGE PIN |
This is verifiable only if A2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM> UE |
Check Status word |
||||
|
2 |
UE |
The Terminal is switched off and on. |
|||
|
3 |
Tester > UE |
When the UE is in the "PIN check" mode, enter the new PIN: "2839#" |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR2 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be unsuccessful |
CR3 |
||
|
4 |
UE |
The Terminal is switched off and on. |
|||
|
5 |
Tester > UE |
When the UE is in the "PIN check" mode, enter the new PIN: "01234567#" |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR2 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR3 |
6.1.8.5 Acceptance criteria
CR 1 is explicitly verified at step 1) by analysing both the CHANGE PIN command sent via the terminal to the UICC, with parameter P2 = "11" (via any supported options A.2/1 OR A.2/2) and the corresponding status word indicating that the new (Universal) PIN is accepted.
CR 2 is explicitly verified at (i) step 3) by analysing the status word indicating that the entered (Universal) PIN has not been accepted for the VERIFY PIN command sent by the terminal to the UICC, and at (ii) step 5) by analysing the status word indicating that the entered (Universal) PIN has been accepted for the VERIFY PIN command sent by the terminal to the UICC.
CR 3 is verified at (i) step 3) on the terminal by ensuring UE shall give an indication following an unsuccessful execution of the command and at (ii) step 5) on the terminal by ensuring UE shall give an indication following a successful execution of the command.
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
CR 1 The Terminal shall support the Unblock PIN command, as defined in ETSI TS 102 221 [5], clause 11.1.13.
CR 2 Only the new pin shall be accepted for further PIN verification.
CR 3 Indication of a successful and unsuccessful pin verification is presented to the user and only the new pin shall be accepted for further PIN verification
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
Ensure that the UE has been operated with an USIM with PIN enabled, and powered off.
The Default UICC is used.
The UICC/USIM configuration defined for this test case is installed in the UE.
6.1.9.4.2 Procedure
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE |
The Terminal is powered on and the correct PIN is entered. |
|||
|
2 |
Tester > UE |
The user shall initiate an MMI dependent procedure to unblock the Universal PIN and set the new Universal PIN value to "1234" |
|||
|
UE > UICC |
UNBLOCK PIN |
This is verifiable only if A2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
3 |
UE |
The Terminal is powered off and on. |
|||
|
4 |
Tester > UE |
Enter the new PIN: "1234#" |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR2 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR3 |
||
|
5 |
UE |
The Terminal is powered off and on. |
|||
|
6 |
Tester > UE |
Enter a wrong PIN three times. |
|||
|
UE > UICC |
VERIFY PIN |
This is repeated 3x, and is verifiable only if A2/x is supported. |
CR2 |
A.2/1 OR A2/2 |
|
|
USIM> UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be unsuccessful |
CR3 |
||
|
7 |
Tester > UE |
The user shall initiate an MMI dependent procedure to unblock the Universal PIN and set the new Universal PIN value to "2839". |
|||
|
UE > UICC |
UNBLOCK PIN |
This is verifiable only if A2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM> UE |
Check Status word |
||||
|
8 |
UE |
The Terminal is powered off and on. |
|||
|
9 |
Tester > UE |
Enter the new PIN: "2839#" |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR2 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR3 |
6.1.9.5 Acceptance criteria
CR 1 is explicitly verified at step 2) and step 7) by analysing both the UNBLOCK PIN command sent via the terminal to the UICC, with parameter P2 = "11" (via any supported options A.2/1 OR A.2/2) and the corresponding status word indicating that the new (Universal) PIN is accepted.
CR 2 is explicitly verified at (i) step 4) and step 9) by analysing the status word indicating that the entered (Universal) PIN has been accepted for the VERIFY PIN command sent by the terminal to the UICC, and at (ii) step 6 by analysing each status word(s) indicating that the entered (Universal) PIN has not been accepted for 3 consecutive VERIFY PIN command sent by the terminal to the UICC and after the third entry the (Universal) PIN has been blocked.
CR 3 is verified (i) at step 4) on terminal by either ensuring UE shall give an indication of a successful execution of the command and new (Universal) PIN is accepted, (ii) at step 6 on terminal by ensuring UE shall give an indication that execution of the command failed and (Universal) PIN is blocked, (iii) at step 9) on terminal by ensuring UE shall give an indication of a successful execution of the command and new (Universal) PIN is 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
CR 1 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.
CR 2 The VERIFY PIN function verifies the PIN presented by the Terminal to the UICC.
CR 3 Indication of a successful pin verification is presented to user.
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
Ensure that the UE has been operated with an USIM with 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:
|
Byte |
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:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
36 |
34 |
35 |
33 |
34 |
32 |
33 |
31 |
PIN2
Key reference: 87
Logically:
9753
Coding:
|
Byte |
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:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
35 |
37 |
36 |
38 |
37 |
39 |
38 |
30 |
The UICC/USIM configuration defined for this test case is installed in the UE.
6.1.10.4.2 Procedure
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE |
The Terminal is powered on. |
|||
|
2 |
Tester > UE |
When the UE is in the "PIN check" mode, the sequence "8642#" shall be entered |
CR1 |
||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR2 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR3 |
6.1.10.5 Acceptance criteria
CR 1 is met if the terminal asks the user for the PIN verification.
CR 2 can be explicitly verified at step 2) via supported options A.2/1 OR A.2/2, ensuring that the VERIFY PIN command is correctly sent via the terminal to the UICC, with parameter P2 = "07".
CR 3 is verified on the terminal. CR 3 is met if an indication is given to the user showing that this procedure was executed successfully, e.g. by displaying: "OK".
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
CR 1 The Terminal shall support the change of PIN procedure as defined in ETSI TS 102 221 [5], clause 11.1.10.
CR 2 Indication of a successful pin change is presented to user, and only the new pin shall be accepted for further PIN verification.
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
Ensure that the UE has been operated with an USIM with 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:
|
Byte |
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:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
36 |
34 |
35 |
33 |
34 |
32 |
33 |
31 |
PIN2
Key reference: 87
Logically:
9753
Coding:
|
Byte |
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:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
35 |
37 |
36 |
38 |
37 |
39 |
38 |
30 |
The UICC/USIM configuration defined for this test case is installed in the UE.
The ME is powered-on, with the correct PIN entered.
6.1.11.4.2 Procedure
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
Tester > UE |
After USIM initialisation is completed, enter "**04*8642*01234567*01234567#" or initiate an equivalent MMI dependent procedure to change the PIN from ‘8642’ to ‘01234567’ |
|||
|
UE > UICC |
CHANGE PIN |
This is verifiable only if A2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
UICC > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure is successful |
CR2 |
||
|
2 |
UE |
The UE is switched off and on. |
|||
|
3 |
Tester > UE |
When the UE is in the "PIN check" mode, the sequence "8642#" shall be entered. |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure is unsuccessful |
CR2 |
||
|
4 |
UE |
The UE is switched off and on. |
|||
|
5 |
Tester > UE |
When the UE is in the "PIN check" mode, the sequence "01234567#" shall be entered. |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure is successful |
CR2 |
6.1.11.5 Acceptance criteria
CR 1 is explicitly verified (i) at step 1) by analysing the CHANGE PIN command (ii) at step 3) and step 5) by analysing the VERIFY PIN sent via the terminal to the UICC, with parameter P2 = "07" (via any supported options A.2/1 OR A2/2).
CR 2 is verified (i) at step 1) on terminal by either ensuring UE shall give an indication of a successful execution of the command and new PIN is accepted, (ii) at step 3) on terminal by ensuring UE shall give an indication that execution of the command failed, (iii) at step 5) on terminal by ensuring UE shall give an indication of a successful execution of the command.
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
CR 1 The Terminal shall support the Unblock PIN command, as defined in ETSI TS 102 221 [5], clause 11.1.13.
CR 2 Indication of a successful and unsuccessful unblock PIN is presented to user.
CR 3 Only the new pin shall be accepted for further PIN verification.
CR 4 Indication of a successful and unsuccessful pin verification is presented to the user and only the new pin shall be accepted for further PIN verification.
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 ME 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
Ensure that the UE has been operated with an USIM with 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:
|
Byte |
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:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
36 |
34 |
35 |
33 |
34 |
32 |
33 |
31 |
PIN2
Key reference: 87
Logically: 9753
Coding:
|
Byte |
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:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
35 |
37 |
36 |
38 |
37 |
39 |
38 |
30 |
The UICC/USIM configuration defined for this test case is installed in the UE.
6.1.12.4.2 Procedure
Sequence A:
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE |
The ME is powered on and the correct PIN is entered. |
|||
|
2 |
Tester > UE |
After USIM initialisation is completed, enter "**05*64534231*1234*1234#" |
|||
|
UE > UICC |
UNBLOCK PIN |
This is verifiable only if A.2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR2 |
||
|
3 |
UE |
The ME is switched off and on. |
|||
|
4 |
Tester > UE |
When the UE is in the "PIN check" mode, enter the new PIN: "1234#" |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A.2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR4 |
||
|
5 |
UE |
The ME is switched off and on. |
|||
|
6 |
Tester > UE |
Enter a wrong PIN three times. |
|||
|
UE > UICC |
VERIFY PIN |
This is repeated 3x, and is verifiable only if A.2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be unsuccessful |
CR4 |
||
|
7 |
Tester > UE |
Enter "**05*64534231*8642*8642#". |
|||
|
UE > UICC |
UNBLOCK PIN |
This is verifiable only if A.2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR2 |
||
|
8 |
Tester > UE |
When the UE is in the "PIN check" mode, enter the new PIN: "8642#" |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A.2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR4 |
Sequence B:
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE |
The ME is powered on. |
|||
|
2 |
Tester > UE |
Enter a wrong PIN three times. |
|||
|
3 |
Tester > UE |
The user shall initiate a MMI dependent procedure to unblock the PIN with unblock code ‘64534231’ and a new PIN ‘8642’ ( "**05*64534231*8642*8642#" ) . |
|||
|
UE > UICC |
UNBLOCK PIN |
This is verifiable only if A.2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR2 |
||
|
4 |
UE |
The ME is switched off and on. |
|||
|
5 |
Tester > UE |
When the UE is in the "PIN check" mode, enter the new PIN: "8642#" |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A.2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR4 |
6.1.12.5 Acceptance criteria
Sequence A:
CR 1 is explicitly verified at step 2) and step 7) by analysing the UNBLOCK PIN command sent via the terminal to the UICC, with parameter P2 = "07" (via any supported options A.2/1 OR A.2/2).
CR 2 is verified at step 2) and step 7) on the terminal by ensuring UE shall give an indication following a successful execution of the command and new PIN is accepted.
CR 3 is explicitly verified at step 4), step 6) and step 8) by analysing the status word for both successful and unsuccessful PIN entry.
CR 4 is verified at (i) step 4) and step 8) on the terminal by ensuring UE shall give an indication of a successful execution of the command and PIN is accepted, (ii) at step) on ME by ensuring UE shall give an indication that execution of the command failed.
Sequence B:
CR 1 is explicitly verified at step 3) by analysing the UNBLOCK PIN command sent via the terminal to the UICC, with parameter P2 = "07" (via any supported options A.2/1 OR A.2/2) after Terminal indicates that PIN has been blocked in step 2).
CR 2 is verified at step 3) on the terminal by ensuring UE shall give an indication following a successful execution of the command and new PIN is accepted.
CR 3 is explicitly verified at step 5) by analysing the Status word for successful PIN entry.
CR 4 is verified at step 5) on the terminal by ensuring UE shall give an indication following a successful execution of the command when a PIN is 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
CR 1 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.
CR 2 The VERIFY PIN function verifies the PIN2 presented by the Terminal to the UICC.
CR 3 Indication of a successful pin2 verification is presented to the user.
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
The purpose of this test is to verify that:
1) the PIN2 verification procedure is performed by the ME correctly;
2) the basic public MMI string is supported;
3) the ME 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
Ensure that the UE has been operated with an USIM with PIN enabled, and powered off.
The values of the Default UICC as defined in clause 4.5.1 of the present document are 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:
|
Byte |
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:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
36 |
34 |
35 |
33 |
34 |
32 |
33 |
31 |
PIN2
Key reference: 87
Logically: 9753
Coding:
|
Byte |
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:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
35 |
37 |
36 |
38 |
37 |
39 |
38 |
30 |
The UICC/USIM configuration defined for this test case is installed in the UE.
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
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE |
The Terminal is powered on. |
|||
|
2 |
Tester > UE |
When the UE is in the "PIN check" mode, correct PIN shall be entered. |
|||
|
3 |
The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN) |
||||
|
4 |
When the UE is in the "PIN2 check" mode, the sequence "9753#" shall be entered. |
||||
|
UE |
VERIFY PIN |
This is verifiable if A2/x is supported, else skip this verification |
CR1 |
A.2/1 OR A2/2 |
|
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR2 |
6.1.13.5 Acceptance criteria
CR 1 is explicitly verified at step 4 via supported options A.2/1 OR A2/2, ensuring that the VERIFY PIN command is correctly sent via the terminal to the UICC, with parameter P2 = "87".
CR 2 is verified on the terminal. CR 2 is met if an indication is given to the user showing that this procedure was executed successfully, e.g. by displaying "OK".
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
CR 1 The Terminal shall support the change of PIN2 procedure as defined in ETSI TS 102 221 [5], clause 11.1.10.
CR 2 Indication of a successful PIN2 change is presented to user, and only the new pin2 shall be accepted for further PIN verification.
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
Ensure that the UE has been operated with an USIM with PIN2 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:
|
Byte |
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:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
36 |
34 |
35 |
33 |
34 |
32 |
33 |
31 |
PIN2
Key reference: 87
Logically:
9753
Coding:
|
Byte |
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:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
35 |
37 |
36 |
38 |
37 |
39 |
38 |
30 |
The UICC/USIM configuration defined for this test case is installed in the UE.
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
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
Tester > UE |
After USIM initialisation is completed, enter "**042*9753*12345678*12345678#" or initiate an equivalent MMI dependent procedure to change the PIN2 from ‘9753’ to ‘12345678’ |
|||
|
UE > UICC |
CHANGE PIN |
This is verifiable only if A2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM> UE |
Check Status word |
||||
|
UE |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR2 |
||
|
2 |
UE |
UE is switched off and on and the correct PIN is entered. |
|||
|
3 |
The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN) |
||||
|
4 |
Tester > UE |
When the UE is in the "PIN2 check" mode, incorrect sequence "9753#" shall be entered. |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be unsuccessful |
CR2 |
||
|
5 |
UE |
The Terminal is switched off and on. |
|||
|
6 |
The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN) |
||||
|
7 |
Tester > UE |
When the UE is in the "PIN check" mode, the sequence "12345678#" shall be entered. |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM> UE |
Check Status word |
||||
|
UE |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR2 |
6.1.14.5 Acceptance criteria
CR 1 is explicitly verified (i) at step 1 by analysing the CHANGE PIN command sent from Terminal to UICC with the parameter P2 set to "87" (ii) at step 4 and step 7 by analysing the VERIFY PIN sent via the terminal to the UICC (via any supported options A.2/1 OR A2/2).
CR 2 is verified (i) at step 1 on terminal by ensuring UE shall give an indication of a successful execution of the command and new PIN is accepted, (ii) at step 4 on terminal by ensuring UE shall give an indication that execution of the command failed, (iii) at step 7 on terminal by ensuring UE shall give an indication of a successful execution of the command.
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
CR 1 The Terminal shall support the Unblock PIN2 command, as defined in ETSI TS 102 221 [5], clause 11.1.13.
CR 2 Indication of a successful unblock PIN2 is presented to user
CR 3 Only the new pin2 shall be accepted for further PIN2 verification.
CR 4 Indication of a successful and unsuccessful pin2 verification is presented to user and only the new pin2 shall be accepted for further PIN2 verification.
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
Ensure that the UE has been operated with an USIM with 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:
|
Byte |
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:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
36 |
34 |
35 |
33 |
34 |
32 |
33 |
31 |
PIN2
Key reference: 87
Logically:
9753
Coding:
|
Byte |
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:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
35 |
37 |
36 |
38 |
37 |
39 |
38 |
30 |
The UICC/USIM configuration defined for this test case is installed in the UE.
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:
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE |
The Terminal is powered on and the correct PIN is entered. |
|||
|
2 |
Tester > UE |
After USIM initialisation is completed, enter "**052*57687980*1234*1234#" |
|||
|
UE > UICC |
UNBLOCK PIN |
This is verifiable only if A2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR2 |
||
|
3 |
UE |
The Terminal is switched off and on and the correct PIN is entered. |
|||
|
4 |
The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN) |
||||
|
5 |
Tester > UE |
Enter the new PIN2: "1234#" |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR4 |
||
|
6 |
UE |
The Terminal is switched off and on and the correct PIN is entered. |
|||
|
7 |
The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN) |
||||
|
8 |
Tester > UE |
Enter a wrong PIN2 three times. |
|||
|
UE > UICC |
VERIFY PIN |
This is repeated 3x, and is verifiable only if A2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM> UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be unsuccessful |
CR4 |
||
|
9 |
Tester > UE |
Enter "**052*57687980*9753*9753#". |
|||
|
UE > UICC |
UNBLOCK PIN |
This is verifiable only if A2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM> UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR2 |
||
|
10 |
UE |
The Terminal is switched off and on and the correct PIN is entered. |
|||
|
11 |
The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN) |
||||
|
12 |
Tester > UE |
Enter the new PIN2: "9753#" |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR4 |
Sequence B:
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE |
The Terminal is powered on and the correct PIN is entered. |
|||
|
2 |
Tester > UE |
Enter a wrong PIN2 three times. |
|||
|
3 |
Tester > UE |
The user shall initiate an MMI dependent procedure to unblock the PIN2 with unblock code ‘57687980’ and a new PIN "9753" |
|||
|
UE > UICC |
UNBLOCK PIN |
This is verifiable only if A2/x is supported. |
CR1 |
A.2/1 OR A2/2 |
|
|
USIM> UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR2 |
||
|
4 |
UE |
The Terminal is switched off and on and the correct PIN is entered. |
|||
|
5 |
The access to a PIN2 protected data field shall be performed (e.g. UPDATE FDN) |
||||
|
6 |
Tester > UE |
Enter the new PIN2: "9753#" |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR4 |
6.1.15.5 Acceptance criteria
Sequence A:
CR 1 is explicitly verified at step 2 and step 9 by analysing the UNBLOCK PIN command sent via Terminal to the UICC, with parameter P2 = "87" (via any supported options A.2/1 OR A2/2).
CR 2 is verified at step 2 and step 9 on the terminal by ensuring UE shall give an indication of a successful execution of the command and new PIN2 is accepted.
CR 3 is explicitly verified at step 5, step 8 and step 12 by analysing the Status word for both successful and unsuccessful PIN2 entry.
CR 4 is verified at (i) step 5 and step 12 on the terminal by ensuring UE shall give an indication of a successful execution of the command and PIN2 is accepted, (ii) at step 8 on terminal by ensuring UE shall give an indication that execution of the command failed.
Sequence B:
CR 1 is explicitly verified at step 3 by analysing the UNBLOCK PIN command sent via Terminal to the UICC, with parameter P2 = "87" (via any supported options A.2/1 OR A2/2) after Terminal indicates that PIN has been blocked in step2.
CR 2 is verified at step 3 on the terminal by ensuring UE shall give an indication following a successful execution of the command and new PIN2 is accepted.
CR 3 is explicitly verified at step 6 by analysing the Status word for successful PIN2 entry.
CR 4 is verified at step 6 on the terminal by ensuring UE shall give an indication following a successful execution of the command that PIN2 is 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
CR 1 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.
CR 2 The Terminal shall support the procedure to disable the replacement defined in ETSI TS 102 221 [5], clause 11.1.12.
CR 3 Only the new pin shall be accepted for further PIN verification.
CR 4 Indication of a successful and unsuccessful pin verification is presented to the user and only the new pin shall be accepted for further PIN verification.
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
Ensure that the UE has been operated with an USIM with 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:
|
Byte |
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:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
36 |
34 |
35 |
33 |
34 |
32 |
33 |
31 |
PIN2
Key reference: 87
Logically:
9753
Coding:
|
Byte |
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:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Hex |
35 |
37 |
36 |
38 |
37 |
39 |
38 |
30 |
The UICC/USIM configuration defined for this test case is installed in the UE.
6.1.16.4.2 Procedure
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE |
The Terminal is powered on. |
|||
|
2 |
Tester > UE |
When the UE is in the "PIN check" mode, the sequence "8642#" shall be entered. |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
A.2/1 OR A2/2 |
||
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
|||
|
3 |
Tester > UE |
The user shall initiate an MMI dependent procedure to replace the PIN by the Universal PIN. |
|||
|
UE > UICC |
DISABLE PIN |
This is verifiable only if A2/x is supported. |
CR1 |
||
|
USIM > UE |
Check Status word |
||||
|
4 |
UE > Tester |
The Terminal is switched off and on. |
|||
|
5 |
Tester > UE |
When the UE is in the "PIN check" mode, the sequence "8642#" shall be entered. |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be unsuccessful |
CR4 |
||
|
6 |
The correct Universal PIN is entered. |
||||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR4 |
||
|
7 |
Initiate an MMI dependent procedure to disable the replacement of the PIN by the Universal PIN |
||||
|
UE > UICC |
ENABLE PIN |
This is verifiable only if A2/x is supported. |
CR2 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
8 |
UE > Tester |
The Terminal is switched off and on. |
|||
|
9 |
Tester > UE |
When the UE is in the "PIN check" mode, the sequence "2839#" shall be entered. |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be unsuccessful |
CR4 |
||
|
10 |
Tester > UE |
When the UE is in the "PIN check" mode correct PIN is entered. |
|||
|
UE > UICC |
VERIFY PIN |
This is verifiable only if A2/x is supported. |
CR3 |
A.2/1 OR A2/2 |
|
|
USIM > UE |
Check Status word |
||||
|
UE > Tester |
An indication is given to the user showing whether this procedure was successful |
This procedure shall be successful |
CR4 |
6.1.16.5 Acceptance criteria
CR 1 is explicitly verified at step 3 by analysing the DISABLE PIN command sent via the terminal to the UICC, with parameter P1 = "91" and P2 = "07" (via any supported options A.2/1 OR A2/2).
CR 2 is explicitly verified at step 7 by analysing the ENABLE PIN command sent via the terminal to the UICC, with parameter P2 = "07" (via any supported options A.2/1 OR A2/2)
CR 3 is explicitly verified at (i) step 5 by analysing the status word indicating that the PIN has not been accepted for the VERIFY PIN command sent by the terminal to the UICC, with parameter P2 = "11", (ii) step 6 by analysing the status word indicating that the PIN has been accepted for the VERIFY PIN command sent by the terminal to the UICC, with parameter P2 = "11", (iii) step 9 by analysing the status word indicating that the PIN has not been accepted for the VERIFY PIN command sent by the terminal to the UICC, with parameter P2 = "07", (ii) step 10 by analysing the status word indicating that the PIN has been accepted for the VERIFY PIN command sent by the terminal to the UICC, with parameter P2 = "07".
CR 4 is verified (i) at step 5 and 9 on the terminal by ensuring UE shall give an indication of an unsuccessful execution of the command and PIN is not accepted, (ii) at step 6 and 10 on the terminal by ensuring UE shall give an indication of a successful execution of the command and PIN is accepted.
6.2 Fixed Dialling Numbers (FDN) handling
6.2.1 Terminal and USIM with FDN enabled, EFADN readable and updateable
TBD for the first release of the present document. Discrepancies to be corrected.
6.2.2 Terminal and USIM with FDN disabled
TBD for the first release of the present document. Discrepancies to be corrected.
6.2.3 Enabling, disabling and updating of FDN
TBD for the first release of the present document. Discrepancies to be corrected.
6.2.4 Terminal and USIM with FDN enabled, EFADN readable and updateable (Rel-4 and onwards)
TBD for the first release of the present document. Discrepancies to be corrected.
6.3 Void
6.4 Advice of charge (AoC) handling
6.4.1 AoC not supported by USIM
TBD for the first release of the present document.
6.4.2 Maximum frequency of ACM updating
RFU – agreed method to verify the INCREMENT command needed.
6.4.3 Call terminated when ACM greater than ACMmax
TBD for the first release of the present document.
6.4.4 Response codes of increase command of ACM
TBD for the first release of the present document.