hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 3.4.3 Status and Notations | The "Rel-x Terminal" columns show the status of the entries as follows: The following notations, defined in ISO/IEC 9646-7 [14], are used for the status column: M mandatory - the capability is required to be supported. O optional - the capability may be supported or not. N/A not applicable - in the given context, it is... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4 Test environment | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.1 Table of optional features | The supplier of the implementation shall state the support of possible options in table 4.1. See clause 3.4 for the format of table 4.1. Table 4.1: Options Item Option Status Support Mnemonic 1 Terminal Capability - the terminal support for an application that implements the TS 102 484 [1] secure channel specification.... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.2 Applicability table | Table 4.2.1 specifies the applicability of each test case to the device under test. See clause 3.4 for the format of table 4.2.1. Table 4.2.1: Applicability of tests Test case Description Release Rel-7 Terminal Rel-8 Terminal Rel-9 Terminal Support Discovery 6.1.1.1 ATR M M M Channel Administration 6.2.1.1 Retrieve UIC... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.3 Information provided by the device supplier | Void. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4 Test equipment | The test equipment shall provide a UICC simulator which is connected to the DUT during test procedure execution, unless otherwise specified. With respect to the Terminal, the UICC simulator shall act as a valid UICC according to TS 102 484 [1] and TS 102 221 [2], unless otherwise specified. In particular, during test p... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.1 Measurement / setting uncertainties | As the tests being carried out are measured based on the protocol response there are no measurement tolerances specified. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.2 Default conditions for DUT operation | These tests shall be performed on a DUT that supports the TS 102 221 [2] APDU interface. The terminal shall attach to the UICC simulator using the terminals default voltage and speed parameters. The USB TS 102 600 [10] and SWP interfaces TS 102 613 [13] shall be disabled for these tests. These tests shall be carried ou... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.3 UICC Simulator requirements | The following are requirements for a UICC simulator to be used to perform the tests specified. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.3.1 General Requirements | REQ_UICC_TEST_GEN_01 The UICC simulator shall be designed to TS 102 484 [1] Release 9 and TS 102 221 [2] Release 9. REQ_UICC_TEST_GEN_02 UICC simulator shall be capable of communicating with a terminal. REQ_UICC_TEST_GEN_03 The UICC simulator shall be capable of performing all of the UICC operations for at least 4 Secu... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.3.2 MANAGE SECURE CHANNEL - ATR Requirements | REQ_UICC_TEST_ATR_01 The UICC simulator shall allow the tester to set the contents of the ATR. ETSI ETSI TS 103 484-1 V9.0.0 (2013-05) 16 |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.3.3 MANAGE SECURE CHANNEL - Retrieve UICC Endpoints Requirements | REQ_UICC_TEST_RUE_01 At the request of the tester, the UICC simulator shall be able to interpret and respond to the "First block of command data". REQ_UICC_TEST_RUE_02 If the terminal requests the "First block of response data", the UICC simulator shall be able to send the response data and SW1 SW2. REQ_UICC_TEST_RUE_0... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.3.4 MANAGE SECURE CHANNEL - Key Agreement Requirements | REQ_UICC_TEST_KEY_01 The UICC simulator shall support the entry of a strong proprietary key to be used in the Secure channel setup and operation. REQ_UICC_TEST_KEY_02 The tester shall be able to set the key lifetime as either a counter value or as a time value. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.3.5 MANAGE SECURE CHANNEL - Establish SA - Master SA Requirements | REQ_UICC_TEST_MSA_01 The UICC simulator shall support the reception of the MANAGE SECURE CHANNEL - Establish SA - Master SA without requiring a MANAGE SECURE CHANNEL - Retrieve UICC Endpoints to be issued. REQ_UICC_TEST_MSA_02 At the request of the tester, the UICC simulator shall be able to interpret and respond to th... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.3.8 MANAGE SECURE CHANNEL - Terminate Secure Channel Requirements | REQ_UICC_TEST_TSC_01 The UICC simulator shall support the reception of the MANAGE SECURE CHANNEL - Terminate secure channel without requiring a MANAGE SECURE CHANNEL - Retrieve UICC Endpoints, MANAGE SECURE CHANNEL - Establish SA - Master SA to be issued, MANAGE SECURE CHANNEL - Establish SA - Connection SA or MANAGE S... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.3.9 TRANSACT DATA Requirements | REQ_UICC_TEST_TRD_01 The UICC simulator shall support the processing of the TRANSACT DATA command regardless as to whether any MANAGE SECURE CHANNEL commands have been issued and regardless of the state of the secure channel being used. REQ_UICC_TEST_TRD_02 At the request of the tester, the UICC simulator shall be able... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.4 Terminal Application Requirements (for Terminal Capability Testing) | The following are requirements for a test terminal application to be used when the test type is 'terminal capability'. ETSI ETSI TS 103 484-1 V9.0.0 (2013-05) 18 |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.4.1 General Requirements | REQ_TERM_TEST_GEN_01 The terminal test application shall be designed to TS 102 484 [1] Release 9 and TS 102 221 [2] Release 9. REQ_TERM_TEST_GEN_02 The terminal test application shall be capable of communicating with a UICC. REQ_TERM_TEST_GEN_03 The terminal test application shall be capable of performing all of the te... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.4.2 MANAGE SECURE CHANNEL - ATR Requirements | REQ_TERM_TEST_ATR_01 The terminal test application shall be able to retrieve the contents of the ATR from the UICC and display it to the tester unmodified. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.4.3 MANAGE SECURE CHANNEL - Retrieve UICC Endpoints Requirements | REQ_TERM_TEST_RUE_01 At the request of the tester, the terminal test application shall be able to send the "First block of command data". The CLA byte shall be set to the logical channel chosen by the tester for this test. REQ_TERM_TEST_RUE_02 If the SW1 SW2 response to this command from the UICC is '62 F3' and at the ... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.4.4 MANAGE SECURE CHANNEL - Key Agreement Requirements | REQ_TERM_TEST_KEY_01 The terminal test application shall support the entry of a strong proprietary key to be used in the Secure channel setup and operation. REQ_TERM_TEST_KEY_02 The tester shall be able to set the key lifetime as either a counter value or as a time value. ETSI ETSI TS 103 484-1 V9.0.0 (2013-05) 19 |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.4.5 MANAGE SECURE CHANNEL - Establish SA - Master SA Requirements | REQ_TERM_TEST_MSA_01 The terminal test application shall support the issuing of the MANAGE SECURE CHANNEL - Establish SA - Master SA without requiring a MANAGE SECURE CHANNEL - Retrieve UICC Endpoints to be issued. REQ_TERM_TEST_MSA_02 At the request of the tester, the terminal test application shall be able to send th... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.4.8 MANAGE SECURE CHANNEL - Terminate Secure Channel Requirements | REQ_TERM_TEST_TSC_01 The terminal test application shall support the issuing of the MANAGE SECURE CHANNEL - Terminate secure channel without requiring a MANAGE SECURE CHANNEL - Retrieve UICC Endpoints, MANAGE SECURE CHANNEL - Establish SA - Master SA to be issued, MANAGE SECURE CHANNEL - Establish SA - Connection SA or... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.4.9 TRANSACT DATA Requirements | REQ_TERM_TEST_TRD_01 The terminal test application shall support the issuing of the TRANSACT DATA command regardless as to whether any MANAGE SECURE CHANNEL commands have been issued and regardless of the state of the secure channel being used. REQ_TERM_TEST_TRD_02 At the request of the tester, the terminal test applic... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.5 ATRs to be used by the UICC simulator | For some particular test cases, the ATRs described below need to be specifically used. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.5.1 ATR that indicates that indicates support of Secure Channel | Table 4.4.5.1.1 Character Value Description TS '3B' Indicates direct convention T0 '97' TA1 and TD1 are present 7 historical bytes TA1 '96' Clock rate conversion factor FI=9 (F=512) Baud rate adjustment factor DI=6 (D=32) TD1 '80' TD2 only is present Protocol T=0 is supported by UICC TD2 '3F' TA3 and TB3 are present Gl... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.6 Defined TLVs to be used by the UICC simulator | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.6.1 Endpoints to be used by the UICC simulator | For the following endpoints to be used by the UICC simulator the following definitions shall apply: YY (1 byte): The maximum data container size as detailed in the test procedure or using the default value 'FF'. UICC_identifier: The Endpoint identifier value of Tag '82' shall be the AID of the application and allocated... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.6.1.1 No Endpoints | Table 4.4.6.1.1.1 Tag Length Value '73' '0C' UICC_ID TLV as detailed in table 4.4.6.1.1.2 Table 4.4.6.1.1.2 Tag Length Value 81 '0A' ICCID as defined for EFICCID |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.6.1.2 Single Endpoint | Table 4.4.6.1.2.1 Tag Length Value '73' 'XX' UICC_ID and Endpoint information TLVs as detailed in table 4.4.6.1.2.2 Table 4.4.6.1.2.2 Tag Length Value 81 '0A' ICCID as defined for EFICCID 82 7+Z 02 01 04 02 YY FF FF Endpoint_identifier |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.6.1.3 Multiple Endpoints - 4 Endpoints | Table 4.4.6.1.3.1 Tag Length Value '73' 'XX' UICC_ID and Endpoint information TLVs as detailed in table 4.4.6.1.3.2 Table 4.4.6.1.3.2 Tag Length Value 81 '0A' ICCID as defined for EFICCID 82 7+Z 02 01 04 02 YY FF FF Endpoint_identifier 82 7+Z 02 01 04 02 YY FF FF Endpoint_identifier 82 7+Z 02 01 04 02 YY FF FF Endpoint... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.6.1.4 Multiple Endpoints - 20 Endpoints over 2 Blocks | 4.4.6.1.4.1 Multiple Endpoints 1st Block Table 4.4.6.1.4.1.1 Tag Length Value '73' 'FF' The first 255 bytes of UICC_ID and Endpoint information TLVs as detailed in table 4.4.6.1.4.3.1 4.4.6.1.4.2 Multiple Endpoints 2nd Block Table 4.4.6.1.4.2.1 Tag Length Value '73' 'XX' Remaining Endpoint information after first 255 b... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.6.2 Master SA Response to be used by UICC Simulator | Table 4.4.6.2.1 Tag Length Value '73' '15' Key Agreement Mechanism and MSA_ID as detailed in table 4.4.6.2.2 Table 4.4.6.2.2 Tag Length Value 87 '01' '82' 88 '10' MSA_ID which is a unique 16 byte HEX number that identifies the specific Master_SA and shall be allocated by the test equipment manufacturer |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.6.3 Connection SA Response to be used by UICC Simulator | Table 4.4.6.3.2.1 Tag Length Value '73' '3A' Algorithm and integrity, CSA_ID, Unonce and CSAMAC as detailed in table 4.4.6.3.2 ETSI ETSI TS 103 484-1 V9.0.0 (2013-05) 24 Table 4.4.6.3.2 Tag Length Value 89 '02' '07 07' 8B '10' CSA_ID which is a unique 16 byte HEX number that identifies the specific Connection_SA and sh... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.6.4 Start Secure Channel Session Number response | The session number returned in the Establish SA - Start Secure Channel response shall be in accordance with table 4.4.6.4.1 of value as given in the test procedure being used. Table 4.4.6.4.1 Tag Length Value '53' '01' XX000000 XX=Session number as indicated in the test procedure which may be '0', '1', '2' or '3' coded... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.6.5 Transact Data Responses | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.6.5.1 Transact Data Response 1 | The response data shall consist of no data with SW1 SW2 Normal ending of the command bytes encrypted within the TLV. Table 4.4.6.5.1.1 Data SW1 SW2 See table 4.4.6.5.1.2 '92' '00000XX0' XX=Session Number as indicated in the test procedure which may be '0', '1', '2' or '3' coded in 2 bits. Value = '00' or '20 or '40' or... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.6.5.2 Transact Data Response 2 | The response data shall consist of 210 bytes of repeated data bytes 'A5' with SW1 SW2 Normal ending of the command bytes encrypted within the TLV. Table 4.4.6.5.2.1 Type Tag Length Value Encrypted Data Container 81 '81 F0' The data in table 4.4.6.5.2.2 encrypted using the encryption method and encryption Key agreed for... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.6.5.3 Transact Data Response 3 | The response data shall consist of 162 bytes of repeated data bytes '40' with SW1 SW2 Normal ending of the command bytes encrypted within the TLV. Table 4.4.6.5.3 Type Tag Length Value Encrypted Data Container 81 '81 C0' The data in table 4.4.6.5.4 encrypted using the encryption method and encryption Key agreed for the... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.7 Terminal Application Data | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.7.1 TRANSACT DATA commands | Several types of content are required for the TRANSACT DATA tests. The data provided in this section and the responses are the 'clear' data / responses prior to the Secure Channel encryption process. When testing a specific Terminal application using secure channel, alternative messages may be used that satisfy the cri... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.7.1.1 Transact Data Command APDU 1 | This is a message that is 207 bytes long and that produces only a SW1 SW2 response. Data to Send: The Terminal application will be implemented to send the following APDU command encrypted and contained in the TRANSACT DATA command, The INS is chosen to be a non-standard APDU which will trigger the UICC simulator to rep... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.7.1.2 Transact Data Command APDU 2 | This is a message that is 255 bytes long and that produces only a SW1 SW2 response. Data to Send: The Terminal application will be implemented to send the following APDU command encrypted and contained in the TRANSACT DATA command, The INS is chosen to be a non-standard APDU which will trigger the UICC simulator to rep... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.4.7.1.3 Transact Data Command APDU 3 | Table 4.4.7.1.3.1: Coding of Command APDU 3 Code CLA INS P1 P2 Le Value '0X' 'EE' '01' 'A5' 'D2' |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.5 Test execution | The tests may be run as a suite or run as individual tests. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 4.6 Pass criterion | A test shall only be considered as successful if the test procedure was carried out successfully under all parameter variations with the DUT respecting all conformance requirements referenced in the test procedure. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 5 Conformance Requirements | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 5.1 Secure Channel Properties | Reference: TS 102 484 [1], clause 5. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 5.1.1 Secure Channel Lifecycle and Discovery | RQ number Clause Description RQ01_0101 5.1 The lifecycle of each secure channel will include the following step: Discovery of support for secure channels by the terminal and the UICC as detailed in the present document. RQ01_0102 5.1 The lifecycle of each secure channel will include the following step: Discover endpoin... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 5.1.2 Secure Channel Administration | RQ number Clause Description RQ02_0101 5.1.3 For a secure channel to be setup, both ends of the secure channel must agree on the parameters to be used for this channel. The present document defines these parameters as a "Security Association". RQ02_0103 5.1.3.1 A Security Association has the following parameter: Identi... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 5.1.3 Key Agreement | RQ number Clause Description RQ03_0101 5.1.4 A mechanism to share key material between the two endpoints ... can be: Strong Pre-shared Keys - GBA. RQ03_0102 5.1.4 A mechanism to share key material between the two endpoints ... can be: Strong Pre-shared Keys - Proprietary Pre-agreed keys. RQ03_0103 5.1.4 A mechanism to ... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 5.1.5 Secure Channel Operation | RQ number Clause Description RQ04_0102 5.1.6 A secure channel shall be considered 'suspended' if all of the Connection SAs for that secure channel have been terminated. RQ04_0103 5.1.6 A suspended secure channel shall be resumed when a Connection SA is created using the Master SA for that secure channel. RQ04_0201 5.2 ... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 5.2 Secured APDU - Application to Application lifecycle | Reference: TS 102 484 [1], clause 7. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 5.2.1 Discovery | RQ number Clause Description RQ05_0101 7.1 The terminal application may use Manage Secure Channel APDU - Retrieve UICC Endpoints command to discover UICC endpoints. ETSI ETSI TS 103 484-1 V9.0.0 (2013-05) 32 |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 5.2.2 Master SA setup | RQ number Clause Description RQ06_0101 7.2 Application to application secure channel setup shall only be initiated by a terminal application using the Manage Secure Channel APDU - Establish SA - Master SA command. RQ06_0102 7.2 Using the Manage Secure Channel APDU - Establish SA - Master SA command, the terminal applic... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 5.2.3 Connection SA setup | RQ number Clause Description RQ07_0101 7.3 The terminal application shall setup a Connection SA using the Manage Secure Channel APDU - Establish SA - Connection SA command. RQ07_0102 7.3 The terminal application shall generate a 16 byte Terminal nonce defined as Tnonce. RQ07_0103 7.3 The terminal application shall send... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 5.2.4 Secure Connection Initiation and Data Transmission | RQ number Clause Description RQ08_0101 7.4 Once a Manage Secure Channel APDU - Start SecureChannel command has been received by the UICC application and acknowledged, the UICC application and terminal application can initiate their security policy and start to secure transmitted data. RQ08_0102 7.4 To send and receive ... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 5.2.5 SA Termination and Resumption | RQ number Clause Description RQ09_0101 7.5 To terminate an existing APDU secure channel Master SA ... the terminal application shall use the Manage Secure Channel APDU - Terminate secure channel SA command defined in TS 102 221 [2]. RQ09_0102 7.5 To terminate an existing APDU secure channel … Connection SA, the termina... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 5.3 Encrypted data coding | Reference: TS 102 484 [1], clause 10. RQ number Clause Description RQ10_0101 10 Data to be sent and its response is encrypted together with a nonce, a counter, padding and a checksum. RQ10_0102 10 The padding length shall be chosen so that the data to be encrypted is a multiple of the block size for the algorithm used.... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 5.4 Key Expansion Function Definition | Reference: TS 102 484 [1], clause 11. RQ number Clause description RQ11_0101 11 "The key expansion function Kexp is based on the Key Expansion function defined in IKE v2 (RFC 4306 [16]) and is designed to produce any required amount of key material from a single cryptographic key. In order to do this, the HMAC-SHA-256 ... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 5.5 ATR | Reference: TS 102 221 [2], clause 6. RQ number Clause Description RQ11_0201 6.3.3 Table 6.7: Coding of the first TBi (i > 2) after T = 15 of the ATR ETSI ETSI TS 103 484-1 V9.0.0 (2013-05) 36 |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 5.6 MANAGE SECURE CHANNEL Command | Reference: TS 102 221 [2], clause 11. RQ number Clause Test clauses RQ12_0101 11.1.20.1 P1 determines which sub procedure is required, the P2 parameter value meaning is specific to each P1 value. RQ12_0102 11.1.20.1 The command and response data are encapsulated in BER-TLV objects structured as defined in clause 11.3 u... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 5.7 TRANSACT DATA Command | Reference: TS 102 221 [2], clause 11. RQ number Clause description RQ13_0101 11.1.21.1 The Transact Data command transports large amounts of data on APDU based communication with different data formats. RQ13_0102 11.1.21.1 The Transact Data command is either a case 2 or case 3 command depending on P1 b3. RQ13_0103 11.1... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6 Test cases | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.1 Test group 1: Discovery | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.1.1 Sub Test group 1.1: Discovery of secure channel support | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.1.1.1 Test Case 1: ATR | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.1.1.1.1 Test execution | The test procedure shall be executed for each of the following parameters: • There are no test case-specific parameters for this test case. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.1.1.1.2 Initial conditions | • Terminal is connected to UICC simulator supporting Secure Channel, but none of the contacts are activated. ETSI ETSI TS 103 484-1 V9.0.0 (2013-05) 39 |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.1.1.1.3 Test procedure | Step Direction Description RQ 1 User T Trigger the terminal to activate Secure Channel Interface. 2 UICC T Send ATR given in clause 4.4.5.1, that indicates: • support of Secure Channel. 3 T UICC Send Manage Secure Channel - Retrieve UICC Endpoints; or Manage Secure Channel - Establish SA - Master SA. First block ... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2 Test group 2: Channel Administration | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.1 Sub Test group 2.1 Retrieve UICC Endpoints | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.1.1 Test case 1: Retrieve UICC Endpoints - No Endpoints | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.1.1.1 Test execution | The test procedure shall only be executed for the following considerations: • There are no test case-specific parameters for this test case. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.1.1.2 Initial conditions | • Terminal is connected to UICC simulator supporting Secure Channel and successfully reset. • Terminal is connected to UICC simulator supporting Secure Channel with no Endpoints defined, as detailed in clause 4.4.6.1.1.1. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.1.1.3 Test procedure | Step Direction Description RQ 1 T UICC Send Manage Secure Channel - Retrieve UICC Endpoints. First block of command data as detailed in table 6.2.1.1.3.1. RQ01_0102 RQ01_0103 2 UICC T Status Words SW1 SW2 set to "Response data available" '62 F3' 3 T UICC Send Manage Secure Channel - Retrieve UICC Endpoints. First... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.1.2.1 Test execution | The test procedure shall only be executed for the following considerations: • Maximum container size indicated in Endpoint = 255. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.1.2.2 Initial conditions | • Terminal is connected to UICC simulator supporting Secure Channel and successfully reset. • Terminal is connected to UICC simulator supporting Secure Channel Endpoints as detailed in clause 4.4.6.1.2. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.1.2.3 Test procedure | Step Direction Description RQ 1 T UICC Send Manage Secure Channel - Retrieve UICC Endpoints. First block of command data as detailed in table 6.2.2.1.3.1. RQ01_0102 RQ02_0103 RQ05_0101 2 UICC T Status Words SW1 SW2 set to "Response data available" '62 F3' 3 T UICC Send Manage Secure Channel - Retrieve UICC Endpoi... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.1.3 Test case 3: Retrieve UICC Endpoints - Multiple Endpoints | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.1.3.1 Test execution | The test procedure shall only be executed for the following considerations: • Maximum container size indicated in Endpoint = 255. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.1.3.2 Initial conditions | • Terminal is connected to UICC simulator supporting Secure Channel and successfully reset. • Terminal is connected to UICC simulator supporting Secure Channel Endpoints as detailed in clause 4.4.6.1.3. ETSI ETSI TS 103 484-1 V9.0.0 (2013-05) 41 |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.1.3.3 Test procedure | Step Direction Description RQ 1 T UICC Send Manage Secure Channel - Retrieve UICC Endpoints. First block of command data as detailed in table 6.2.1.3.3.1. RQ01_0102 RQ05_0101 2 UICC T Status Words SW1 SW2 set to "Response data available" '62 F3'. 3 T UICC Send Manage Secure Channel - Retrieve UICC Endpoints. Firs... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.1.4.1 Test execution | The test procedure shall only be executed for the following considerations: • Maximum container size indicated in Endpoint = 255. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.1.4.2 Initial conditions | • Terminal is connected to UICC simulator supporting Secure Channel and successfully reset. • Terminal is connected to UICC simulator supporting Secure Channel Endpoints as detailed in clause 4.4.6.1.4. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.1.4.3 Test procedure | Step Direction Description RQ 1 T UICC Send Manage Secure Channel - Retrieve UICC Endpoints. First block of command data as detailed in table 6.2.1.4.3.1. RQ01_0102 RQ05_0101 2 UICC T Status Words SW1 SW2 set to "Response data available" '62 F3'. 3 T UICC Send Manage Secure Channel - Retrieve UICC Endpoints. Firs... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.2.1 Test case 1: Establish Master SA | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.2.1.1 Test execution | The test procedure shall only be executed for the following considerations: • There are no test case-specific parameters for this test case. • Maximum container size indicated in Endpoint = 255. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.2.1.2 Initial conditions | • Terminal is connected to UICC simulator supporting Secure Channel and successfully reset. • The Terminal has retrieved the endpoint defined in clause 4.4.6.1.2 with a Maximum data container size = 255 in accordance with the procedure outlined in clause 6.2.1.2. • The Terminal is connected to a UICC simulator supporti... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.2.1.3 Test procedure | Step Direction Description RQ 1 T UICC Send Manage Secure Channel - Establish SA - Master SA command. First block of command data as detailed in table 6.2.2.1.3.1. RQ01_0103 RQ02_0101 RQ02_0107 RQ02_0108 RQ02_0110 RQ02_0201 RQ02_0202 RQ02_0203 RQ02_0204 RQ02_0206 RQ06_0101 RQ06_0102 RQ06_0103 2 UICC T Status Words ... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.2.2 Test case 2: Establish Master SA UICC Rejects | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.2.2.1 Test execution | The test procedure shall only be executed for the following considerations: • There are no test case-specific parameters for this test case. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.2.2.2 Initial conditions | • Terminal is connected to UICC simulator supporting Secure Channel and successfully reset. • The Terminal has retrieved the endpoint defined in clause 4.4.6.1.2 with a Maximum data container size = 255 in accordance with the procedure outlined in clause 6.2.1.2. • The Terminal is connected to a UICC simulator supporti... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.2.2.3 Test procedure | Step Direction Description RQ 1 T UICC Send Manage Secure Channel - Establish SA - Master SA command. First block of command data as detailed in table 6.2.2.2.3.1. 2 UICC T Status words SW1 SW2 set to 'Execution error - no information given, state of non-volatile memory unchanged" '62 00'. 3 T UICC Secure channel... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.2.3 Test case 4: Establish Master SA - 4 Master SAs | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.2.3.1 Test execution | The test procedure shall only be executed for the following considerations: • There are no test case-specific parameters for this test case. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.2.3.2 Initial conditions | • Terminal is connected to UICC simulator supporting Secure Channel and successfully reset. • The Terminal has retrieved the 4 endpoints defined in clause 4.4.6.1.3 with a Maximum data container size = 255 in accordance with the procedure outlined in clause 6.2.1.3. • The Terminal is connected to a UICC simulator suppo... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.2.3.3 Test procedure | Step Direction Description RQ 1 T UICC Send Manage Secure Channel - Establish SA - Master SA command. First block of command data as detailed in table 6.2.2.3.3.1. RQ02_0111 RQ02_0201 RQ02_0202 RQ02_0203 RQ02_0204 RQ02_0206 RQ02_0207 RQ04_0201 2 UICC T Status Words SW1 SW2 set to "Response data available" '62 F3'. ... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.3.1 Test case 1: Establish Connection SA | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.3.1.1 Test execution | The test procedure shall be executed for each of the following parameters: • There are no test case-specific parameters for this test case. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.