hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.4.3.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. The test procedure shall be performed with variation in following parameters, values and combinations: • 128-bit AES in CBC mode as defined in TS 102 225 [8]. • 128-bit AES ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.4.3.2 Initial conditions | • At least one endpoint on UICC has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA successfully established as defined in clause 6.2.2.1. • Connection SA successfully established a... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.4.3.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to start Secure Channel as detailed in clause 4.4.4.4 MSC - Start Secure Channel "First block of command data" with Data for Start Secure Channel command (128-bit-AES and CMAC). 2 UICC T Send SW1 SW2 set to "Response data available" '62 F3'. ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.4.4 Test case 4: Wrong SSCMAC (negative case) | |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.4.4.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. The test procedure shall be performed with variation in following parameters, values and combinations: • 3DES - outer CBC using 2 keys as defined in TS 102 225 [8]. • CRC32 ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.4.4.2 Initial conditions | • At least one endpoint on UICC has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA successfully established as defined in clause 6.2.2.1. • Connection SA successfully established a... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.4.4.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to Start Secure Channel as detailed in clause 4.4.4.4 MSC - Start Secure Channel "First block of command data" with modified Data for Start Secure Channel command as defined below (see table 6.2.4.4.3.1). 2 UICC T Send SW1 SW2 'Authentication... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.1 Test case 1: Terminate Master SA (positive case) | |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.1.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. The test procedure shall be performed with variation in following parameters, values and combinations: • 3DES - outer CBC using 2 keys as defined in TS 102 225 [8]. • CRC32 ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.1.2 Initial conditions | • At least one endpoint on UICC has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA successfully established as defined in clause 6.2.2.1. • Connection SA successfully established a... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.1.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to terminate Secure Channel as detailed in clause 4.4.4.5 MSC - Terminate Secure Channel "First block of command data - Data for Secure Channel termination (MSA_ID)". 2 UICC T Send SW1 SW2 'normal ending of command'. RQ01_0227, RQ01_0404, RQ0... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.2 Test case 2: Terminate one Connection SA (positive case) | |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.2.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. ETSI ETSI TS 103 484-2 V9.0.0 (2013-05) 62 Release 9 The test procedure shall be performed with variation in following parameters, values and combinations: • 3DES - outer CB... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.2.2 Initial conditions | • At least one endpoint on UICC has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA successfully established as defined in clause 6.2.2.1. • Connection SA successfully established a... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.2.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to terminate Secure Channel as detailed in clause 4.4.4.5 MSC - Terminate Secure Channel "First block of command data - Data for Secure Channel termination (CSA_ID)". 2 UICC T Send SW1 SW2 'normal ending of command'. RQ01_0403, RQ01_0406, RQ0... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.3 Test case 3: Terminate two Connection SA (positive case) | |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.3.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. The test procedure shall be performed with variation in following parameters, values and combinations: • 3DES - outer CBC using 2 keys as defined in TS 102 225 [8]. • CRC32 ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.3.2 Initial conditions | • At least one endpoint on UICC has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA successfully established as defined in clause 6.2.2.1. • Two Connection SAs successfully establis... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.3.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to terminate Secure Channel as detailed in clause 4.4.4.5 MSC - Terminate Secure Channel "First block of command data - Data for Secure Channel termination (two CSA_IDs)". 2 UICC T Send SW1 SW2 'normal ending of command'. RQ01_0403, RQ01_0406... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.4 Test case 4: Restart terminated channel (terminated Master SA) | |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.4.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. The test procedure shall be performed with variation in following parameters, values and combinations: • 3DES - outer CBC using 2 keys as defined in TS 102 225 [8]. • CRC32 ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.4.2 Initial conditions | • At least one endpoint on UICC has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA successfully established as defined in clause 6.2.2.1. • Connection SA successfully established a... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.4.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to terminate Secure Channel as detailed in clause 4.4.4.5 MSC - Terminate Secure Channel "First block of command data - Data for Secure Channel termination (MSA_ID)". 2 UICC T Send SW1 SW2 'normal ending of command'. 3 T UICC The terminal s... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.5.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. The test procedure shall be performed with variation in following parameters, values and combinations: • 3DES - outer CBC using 2 keys as defined in TS 102 225 [8]. • CRC32 ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.5.2 Initial conditions | • At least one endpoint on UICC has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. ETSI ETSI TS 103 484-2 V9.0.0 (2013-05) 66 Release 9 • Master SA successfully established as defined in claus... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.5.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to terminate Secure Channel as detailed in clause 4.4.4.5 MSC - Terminate Secure Channel "First block of command data - Data for Secure Channel termination (CSA_ID)". 2 UICC T Send SW1 SW2 'normal ending of command'. 3 T UICC The terminal s... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.6.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. The test procedure shall be performed with variation in following parameters, values and combinations: • 3DES - outer CBC using 2 keys as defined in TS 102 225 [8]. • CRC32 ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.6.2 Initial conditions | • At least one endpoint on UICC has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA successfully established as defined in clause 6.2.2.1. • Two Connection SAs successfully establis... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.6.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to terminate Secure Channel as detailed in clause 4.4.4.5 MSC - Terminate Secure Channel "First block of command data - Data for Secure Channel termination (two CSA_IDs)". 2 UICC T Send SW1 SW2 'normal ending of command'. RQ01_0403 3 T UICC... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.7.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. The test procedure shall be performed with variation in following parameters, values and combinations: • 3DES - outer CBC using 2 keys as defined in TS 102 225 [8]. • CRC32 ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.7.2 Initial conditions | • At least one endpoint on UICC has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA successfully established as defined in clause 6.2.2.1. • Connection SA successfully established a... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.7.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to terminate Secure Channel as detailed in clause 4.4.4.5 MSC - Terminate Secure Channel "First block of command data - Modified Data for Secure Channel termination (MSA_ID)". 2 UICC T Send SW1 SW2 set to 'Authentication error, application sp... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.8.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. The test procedure shall be performed with variation in following parameters, values and combinations: • 3DES - outer CBC using 2 keys as defined in TS 102 225 [8]. • CRC32 ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.8.2 Initial conditions | • At least one endpoint on UICC has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA successfully established as defined in clause 6.2.2.1. • Connection SA successfully established a... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.8.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to terminate Secure Channel as detailed in clause 4.4.4.5 MSC - Terminate Secure Channel "First block of command data - Modified Data for Secure Channel termination (CSA_ID)". 2 UICC T Send SW1 SW2 set to 'Authentication error, application sp... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.9 Test case 8: Terminate Non-Existing Master SA (positive case) | |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.9.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. The test procedure shall be performed with variation in following parameters, values and combinations: • 3DES - outer CBC using 2 keys as defined in TS 102 225 [8]. • CRC32 ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.9.2 Initial conditions | • At least one endpoint on UICC has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA successfully established as defined in clause 6.2.2.1. • Connection SA successfully established a... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.9.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to terminate Secure Channel as detailed in clause 4.4.4.5 MSC - Terminate Secure Channel "First block of command data". Data for Secure Channel termination (MSA_ID) shall be replaced with Data for Secure Channel termination (modified MSA_ID) as... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.10 Test case 10: Terminate Non-Existing Connection SA (positive case) | |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.10.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. The test procedure shall be performed with variation in following parameters, values and combinations: • 3DES - outer CBC using 2 keys as defined in TS 102 225 [8]. • CRC32 ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.10.2 Initial conditions | • At least one endpoint on UICC has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA successfully established as defined in clause 6.2.2.1. • Connection SA successfully established a... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.2.5.10.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to terminate Secure Channel as detailed in clause 4.4.4.5 MSC - Terminate Secure Channel "First block of command data". Data for Secure Channel termination (CSA_ID) shall be replaced with Data for Secure Channel termination (modified CSA_ID) as... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.3 Test group 3: Key Agreement | |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.3.1 Sub Test group 3.1 GBA | Out of scope for the present document. ETSI ETSI TS 103 484-2 V9.0.0 (2013-05) 72 Release 9 |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.3.2 Sub Test group 3.2 Strong | As the mechanism is, by definition, not standardised, there are no tests for this feature. |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.3.3 Sub Test group 3.3 Weak | Out of scope for the present document. |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.3.4 Sub Test group 3.4 Certificate Exchange | Out of scope for the present document. 6.4 Test group 4: Channel Operation The Channel operation tests are split into the following groups of test: • Securing case 3 commands. • Retransmission. • Interleaving. • Interaction with Manage Secure Channel commands. |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.1 Sub Test group 4.1 Securing Case 3 commands | These tests prove that the DUT can correctly handle encrypted case 3 commands ( the case 3 commands are as defined for T=0 in TS 102 221 [2]). The following tests are defined: • Case 3 command secured in 1 secure channel TLV. • Case 3 command secured over 2 secure channel TLVs. • Case 3 command secured over 25 secure c... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.1.1 Test case 1:Case 3 command secured in 1 secure channel TLV | This test verifies that the UICC is able to receive, process and respond to an encrypted case 3 command that fits into a single secure channel TLV. |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.1.1.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. The test procedure shall be performed with variation in following parameters, values and combinations: • 3DES - outer CBC using 3 keys as defined in TS 102 225 [8]. • ANSI X... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.1.1.2 Initial conditions | • The UICC is powered up in a terminal simulator. • At least one endpoint on UICC with data container size of at least 255 bytes has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.1.1.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to start Secure Channel as detailed in clause 4.4.4.4 MSC - Start Secure Channel "First block of command data" with Data for Start Secure Channel command (3-keys- 3DES and Retail MAC) and the Endpoint data container size set to 255 bytes. 2 UIC... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.1.2 Test case 2:Case 3 command secured in 2 secure channel TLVs | This test verifies that the UICC is able to receive, process and respond to an encrypted case 3 command that fits into 2 secure channel TLVs. |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.1.2.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. ETSI ETSI TS 103 484-2 V9.0.0 (2013-05) 75 Release 9 • Application level secure channel endpoint. The test procedure shall be performed with variation in following parameters, values and combinations: • 3DES - outer CB... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.1.2.2 Initial conditions | • The UICC is powered up in a terminal simulator. • At least one endpoint on UICC with data container size of at least 127 bytes has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.1.2.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to start Secure Channel as detailed in clause 4.4.4.4 MSC - Start Secure Channel "First block of command data" with Data for Start Secure Channel command (3-keys-3DES and Retail MAC) and the Endpoint data container size set to 127 bytes. 2 UICC... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.1.3 Test case 3:Case 3 command secured in 25 secure channel TLVs | This test verifies that the UICC is able to receive, process and respond to an encrypted case 3 command that fits into 25 secure channel TLVs. |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.1.3.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. The test procedure shall be performed with variation in following parameters, values and combinations: • 3DES - outer CBC using 3 keys as defined in TS 102 225 [8]. • ANSI X... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.1.3.2 Initial conditions | • The UICC is powered up in a terminal simulator. • At least one endpoint on UICC with data container size of at least 10 bytes has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA s... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.1.3.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to start Secure Channel as detailed in clause 4.4.4.4 MSC - Start Secure Channel "First block of command data" with Data for Start Secure Channel command (3-keys- 3DES and Retail MAC) and the Endpoint data container size set to 10 bytes. 2 UICC... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.1.4 Test case 4: Secured Maximum Size Case 3 command | This test verifies that the UICC is able to receive, process and respond to a maximum size encrypted case 3 command. |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.1.4.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. The test procedure shall be performed with variation in following parameters, values and combinations: • 3DES - outer CBC using 3 keys as defined in TS 102 225 [8]. • ANSI X... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.1.4.2 Initial conditions | • The UICC is powered up in a terminal simulator. • At least one endpoint on UICC with data container size of at least 160 bytes has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.1.4.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to start Secure Channel as detailed in clause 4.4.4.4 MSC - Start Secure Channel "First block of command data" with Data for Start Secure Channel command (3-keys-3DES and Retail MAC) and the Endpoint data container size set to 160 bytes. 2 UICC... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.2 Sub Test group 4.2 Retransmission | These tests prove that the DUT can correctly retransmit Transact Data packets. The following tests are defined: • Retransmission of a packet sent from the Terminal. • Retransmission of a packet received from the UICC. |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.2.1 Test case 1: Retransmission of a packet sent from the Terminal | This test verifies that the UICC is able to receive, process and respond to an encrypted APDU that has a sent packet re- transmitted. |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.2.1.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. • UICC application supports the ability for the tester to cause a request for re-transmission of a TRANSACT DATA packet. The test procedure shall be performed with variation... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.2.1.2 Initial conditions | • The UICC is powered up in a terminal simulator. • At least one endpoint on UICC with data container size of at least 127 bytes has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.2.1.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to start Secure Channel as detailed in clause 4.4.4.4 MSC - Start Secure Channel "First block of command data" with Data for Start Secure Channel command (3-keys-3DES and Retail MAC) and the Endpoint data container size set to 127 bytes. 2 UICC... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.2.2 Test case 2: Retransmission of a packet received from the UICC | This test verifies that the UICC is able to receive, process and respond to an encrypted APDU where retransmission of a UICC TRANSACT DATA response is indicated. |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.2.2.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. The test procedure shall be performed with variation in following parameters, values and combinations: • 3DES - outer CBC using 3 keys as defined in TS 102 225 [8]. • ANSI X... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.2.2.2 Initial conditions | • The UICC is powered up in a terminal simulator. • At least one endpoint on UICC with data container size of at least 127 bytes has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.2.2.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to start Secure Channel as detailed in clause 4.4.4.4 MSC - Start Secure Channel "First block of command data" with Data for Start Secure Channel command (3-keys- 3DES and Retail MAC) and the Endpoint data container size set to 127 bytes. 2 UIC... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.3 Sub Test group 4.3 Interleaving | These tests prove that the DUT can correctly interleave Transact Data packets for different secure channels. The following test is defined: • Interleave two different Secure channels. |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.3.1 Test case 1: Interleaving of two secure channel TRANSACT DATA sessions | This test verifies that the DUT is able to receive, process and respond to two TRANSACT DATA sessions interleaved. |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.3.1.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • at least 2 application level secure channel endpoints available. ETSI ETSI TS 103 484-2 V9.0.0 (2013-05) 90 Release 9 The test procedure shall be performed with variation in following parameters, values and combinati... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.3.1.2 Initial conditions | • The UICC is powered up in a terminal simulator. • At least two endpoints on UICC has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2, one with data container size of at least 127 bytes and the other with data container size of at least 255 bytes. • EFICCID is kno... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.3.1.3 Test procedure | In this procedure the two secure channels shall be referred to as SC1 (endpoint container size 127) and SC2 (endpoint container size 255). Step Direction Description RQ 1 T UICC UICC T Send MANAGE SECURE CHANNEL command to start SC1 as detailed in clause 4.4.4.4 MSC - Start Secure Channel "First block of command/re... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.4 Sub Test group 4.4 Interaction with Manage Secure Channel | These tests prove that the DUT can correctly interact Transact Data packets with MANAGE SECURE CHANNEL commands. The following tests are defined: • Termination of a secure channel during an ongoing Transact Data session. • Abortion of a session by the terminal during an ongoing Transact Data session. • Establishment of... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.4.1.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. The test procedure shall be performed with variation in following parameters, values and combinations: • 3DES - outer CBC using 3 keys as defined in TS 102 225 [8]. • ANSI X... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.4.1.2 Initial conditions | • The UICC is powered up in a terminal simulator. • At least one endpoint on UICC with data container size of at least 255 bytes has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.4.1.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to start Secure Channel as detailed in clause 4.4.4.4 MSC - Start Secure Channel "First block of command data" with Data for Start Secure Channel command (3-keys-3DES and Retail MAC) and the Endpoint data container size set to 255 bytes. 2 UICC... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.4.2.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. ETSI ETSI TS 103 484-2 V9.0.0 (2013-05) 94 Release 9 The test procedure shall be performed with variation in following parameters, values and combinations: • 3DES - outer CB... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.4.2.2 Initial conditions | • The UICC is powered up in a terminal simulator. • At least one endpoint on UICC with data container size of at least 255 bytes has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.4.2.3 Test procedure | Step Direction Description RQ 1 T UICC UICC T Send MANAGE SECURE CHANNEL command to start Secure Channel as detailed in clause 4.4.4.4 MSC - Start Secure Channel "First block of command/response data" with Data for Start Secure Channel command (3-keys-3DES and Retail MAC) and the Endpoint data container size set to... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.4.3.1 Test execution | The test procedure shall only be executed for the following considerations: • Strong pre-shared keys. • Application level secure channel endpoint. The test procedure shall be performed with variation in following parameters, values and combinations: • 3DES - outer CBC using 3 keys as defined in TS 102 225 [8]. • ANSI X... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.4.3.2 Initial conditions | • The UICC is powered up in a terminal simulator. • At least one endpoint on UICC with data container size of at least 255 bytes has been successfully retrieved as defined in clause 4.4.4.2, according to the procedure in clause 6.2.1.2. • EFICCID is known, Terminal_ID is known as defined in clause 4.4.4.2. • Master SA ... |
9b83d46ddaed52db6d247ce75934180e | 103 484-2 | 6.4.4.3.3 Test procedure | Step Direction Description RQ 1 T UICC Send MANAGE SECURE CHANNEL command to start Secure Channel as detailed in clause 4.4.4.4 MSC - Start Secure Channel "First block of command data" with Data for Start Secure Channel command (3-keys- 3DES and Retail MAC) and the Endpoint data container size set to 255 bytes. 2 UIC... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 1 Scope | The present document covers the minimum characteristics which are considered necessary for the terminal or terminal and terminal application in order to provide compliance to TS 102 484 [1]. The present document specifies the test cases for the Secured APDU - Application to Application type of secure channel and includ... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. • In the case of a reference ... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 484: "Smart Cards; Secure channel between a UICC and an end-point terminal". [2] ETSI TS 102 221: "Smart Cards; UICC-Terminal interface; Physical and logical characteristics". [3] ETSI TS 133 110: "Universal Mo... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 3 Definitions, symbols and abbreviations | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 102 484 [1] and TS 102 221 [2] apply. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 3.2 Symbols | For the purposes of the present document, the symbols given in TS 102 484 [1] apply. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in TS 102 484 [1] and the following apply: DUT Device Under Test HEX HEXadecimal RQ Conformance requirement T Terminal TCK ChecK character ETSI ETSI TS 103 484-1 V9.0.0 (2013-05) 11 |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 3.4 Formats | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 3.4.1 Format of the table of optional features | The columns in table 4.1 have the following meaning: Column Meaning Option: The optional feature supported or not by the implementation. Status: See chapter 3.4.3 'Status and Notations'. Support: The support columns are to be filled in by the supplier of the implementation. The following common notations, defined in IS... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 3.4.2 Format of the applicability table | The applicability of every test in table 4.2 a) is formally expressed by the use of Boolean expression defined in the following clause. The columns in table 4.2 have the following meaning: Column Meaning Test case: The "Test case" column gives a reference to the test case number(s) detailed in the present document and ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.