hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.3.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 has established a Master SA using data as... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.3.1.3 Test procedure | Step Direction Description RQ 1 T UICC Manage Secure Channel - Establish SA - Connection SA. First block of command data as detailed in table 6.2.3.1.3.1. RQ01_0103 RQ02_0101 RQ03_0105 RQ03_0106 RQ03_0107 RQ07_0101 RQ07_0102 RQ07_0103 RQ07_0104 RQ07_0105 RQ07_0106 RQ07_0107 RQ07_0108 RQ07_0109 2 UICC T Status Words... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.3.2 Test case 2: Establish Connection SA (Incorrect CSAMAC) | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.3.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.3.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 has established Master SA using data as d... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.3.2.3 Test procedure | Step Direction Description RQ 1 T UICC Manage Secure Channel - Establish SA - Connection SA. First block of command data as detailed in table 6.2.3.2.3.1. 2 UICC T Status Words SW1 SW2 set to "Response data available" '62 F3' 3 T UICC Send Manage Secure Channel - Establish SA - Connection SA. First block of respo... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.3.3 Test case 3: Establish Connection SA - 4 Connection SAs | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.3.3.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.2.3.3.2 Initial conditions | • Terminal is connected to UICC simulator supporting Secure Channel and successfully reset. • The Terminal has retrieved the 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 support... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.3.3.3 Test procedure | Step Direction Description RQ 1 T UICC Manage Secure Channel - Establish SA - Connection SA. First block of command data as detailed in table 6.2.3.3.3.1. RQ02_0301 RQ02_0302 RQ04_0201 RQ07_0101 RQ07_0102 RQ07_0103 RQ07_0104 RQ07_0105 RQ07_0106 RQ07_0107 RQ07_0108 RQ07_0109 RQ07_0110 RQ08_0107 2 UICC T Status Words... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.4.1 Test case 1: Start Secure Channel | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.4.1.1 Test execution | The test procedure shall only be executed for the following considerations: • The test shall be executed for each of the Ciphering and Integrity key combinations that the Terminal supports and is selectable. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.4.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 has established a Master SA using data as... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.4.1.3 Test procedure | Step Direction Description RQ 1 T UICC Manage Secure Channel - Start Secure Channel command. First block of command data as detailed in table 6.2.4.1.3.1. RQ01_0104 RQ02_0210 RQ07_0111 RQ07_0112 RQ07_0113 RQ07_0115 RQ07_0116 2 UICC T Status Words SW1 SW2 set to "Response data available" '62 F3'. 3 T UICC Send Man... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.4.2 Test case 2: Start Secure Channel - UICC Error | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.4.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.4.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 has established a Master SA using data as... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.4.2.3 Test procedure | Step Direction Description RQ 1 T UICC Manage Secure Channel - Start Secure Channel command. First block of command data as detailed in table 6.2.4.2.3.1. 2 UICC T Status Words SW1 SW2 'Authentication error, application specific. 3 T UICC No further commands for this CSA_ID. RQ07_0117 ETSI ETSI TS 103 484-1 V9.0.... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.5.1 Test case 1: Terminate Secure Channel - Master SA | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.5.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. • Terminal application key lifetime. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.5.1.2 Initial conditions | • Master SA successfully established as defined in clause 6.2.2.1. • Connection SA successfully established as defined in clause 6.2.3.1. • Secure Channel is successfully started as defined in clause 6.2.4.1. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.5.1.3 Test procedure | Step Direction Description RQ 1 T UICC Send Manage Secure Channel - Terminate Secure Channel command as detailed in table 6.2.5.1.3.1. RQ01_0107 RQ02_0208 RQ02_0304 RQ09_0101 RQ09_0104 RQ09_0105 2 UICC T Status Words SW1 SW2 set to "Normal ending of command" '90 00'. Table 6.2.5.1.3.1 Code CLA INS P1 P2 Lc Data Val... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.5.2 Test case 2: Terminate Secure Channel - Connection SA | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.5.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. • Terminal application key lifetime. 6.2.5.1.2 Initial conditions • Master SA successfully established as defined in clause 6.2.2.1. • Connection SA successfully established as de... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.5.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. • Terminal application key lifetime. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.5.3.2 Initial conditions | • Master SA successfully established as defined in clause 6.2.2.1. • Connection SA successfully established as defined in clause 6.2.3.1. • Secure Channel is successfully started as defined in clause 6.2.4.1. ETSI ETSI TS 103 484-1 V9.0.0 (2013-05) 53 |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.5.3.3 Test procedure | Step Direction Description RQ 1 T UICC Send Manage Secure Channel - Terminate Secure Channel command as detailed in table 6.2.5.3.3.1. RQ01_0106 2 UICC T Normal ending of command. 3 T UICC Manage Secure Channel - Establish SA - Connection SA. First block of command data as detailed in table 6.2.5.3.3.3. 4 UICC ... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.5.4.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. • Terminal application key lifetime. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.5.4.2 Initial conditions | • Master SA successfully established as defined in clause 6.2.2.1. • Connection SA successfully established as defined in clause 6.2.3.1. • Secure Channel is successfully started as defined in clause 6.2.4.1. ETSI ETSI TS 103 484-1 V9.0.0 (2013-05) 54 |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.2.5.4.3 Test procedure | Step Direction Description RQ 1 T UICC Manage Secure Channel command or Transact Data command. 2 UICC T SW1 SW2 "Security session or association expired". RQ02_0306 RQ09_0106 3 T UICC Manage Secure Channel - Establish SA - Connection SA. First block of command data as detailed table 6.2.5.4.3.1. RQ01_0106 RQ04_10... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.3 Test group 3: Key Agreement | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.3.1 Sub Test group 3.1 GBA | Out of scope for this specification. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.3.2 Sub Test group 3.2 Strong | As the mechanism is, by definition, not standardised, there are no tests for this feature. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.3.3 Sub Test group 3.3 Weak | Out of scope for this specification |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.3.4 Sub Test group 3.4 Certificate Exchange | Out of scope for this specification. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4 Test group 4: Secure Channel Operation | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.1 Sub Test group 4.1 Transact Data - Command Data | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.1.1 Test case 1: Transact Data - Command Data in 1 secure channel TLV | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.1.1.1 Test execution | The test procedure shall only be executed for the following considerations: • The Terminal shall support at least a minimal application as defined in clause 4.4.7.1.1 which shall send a APDU command defined in table 4.4.7.1.1.1. • The Terminal shall support the endpoint container size of 255 as indicated in the retriev... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.1.1.2 Initial conditions | • The secure channel Master SA and Connection SA have been negotiated and the secure channel has not been started. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.1.1.3 Test procedure | Step Direction Description RQ 1 T UICC Send Manage Secure Channel - Start Secure Channel command. 2 UICC T Status Words SW1 SW2 set to "Response data available" '62 F3'. 3 T UICC Send Manage Secure Channel - Start Secure Channel response. 4 UICC T Return Session Number = 3. Data as detailed in clause 4.4.6.4. 5... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.1.2 Test case 2: Transact Data - Command Data in 2 secure channel TLVs | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.1.2.1 Test execution | The test procedure shall only be executed for the following considerations: • The Terminal shall support at least a minimal application as defined in clause 4.4.7.1.1 which shall send a APDU command defined in table 4.4.7.1.1.1. • The Terminal shall support the endpoint container size of 127 as indicated in the retriev... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.1.2.2 Initial conditions | • The secure channel Master SA and Connection SA have been negotiated and the secure channel has not been started. ETSI ETSI TS 103 484-1 V9.0.0 (2013-05) 57 |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.1.2.3 Test procedure | Step Direction Description RQ 1 T UICC Send Manage Secure Channel - Start Secure Channel command 2 UICC T Normal ending of command 3 T UICC Send Manage Secure Channel - Start Secure Channel response 4 UICC T Return Session Number = 3 Data as detailed in clause 4.4.6.4 5 T UICC Send TRANSACT DATA command First... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.1.3 Test case 3: Transact Data - Command Data in 25 secure channel TLVs | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.1.3.1 Test execution | The test procedure shall only be executed for the following considerations: • The Terminal shall support at least a minimal application as defined in clause 4.4.7.1.1 which shall send a APDU command defined in table 4.4.7.1.1.1. • The Terminal shall support the endpoint container size of 10 as indicated in the retrieve... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.1.3.2 Initial conditions | • The Terminal has an application that is able to manage and communicate using an APDU application - application secure channel with the application on the UICC Simulator. • The secure channel Master SA and Connection SA have been negotiated and the secure channel has not been started. • The UICC has Endpoints that can... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.1.3.3 Test procedure | Step Direction Description RQ 1 T UICC Send Manage Secure Channel - Start Secure Channel command 2 UICC T Normal ending of command 3 T UICC Send Manage Secure Channel - Start Secure Channel response 4 UICC T Return Session Number = 3 Data as detailed in clause 4.4.6.4 5 T UICC Send TRANSACT DATA command. Firs... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.1.4 Test case 4: Transact Data - Command Data Maximum Size APDU | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.1.4.1 Test execution | The test procedure shall only be executed for the following considerations: • The Terminal shall support at least a minimal application as defined in clause 4.4.7.1.1 which shall send a APDU command defined in table 4.4.7.1.1.1. • The Terminal shall support the endpoint container size of 160 as indicated in the retriev... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.1.4.2 Initial conditions | • The secure channel Master SA and Connection SA have been negotiated and the secure channel has not been started. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.1.4.3 Test procedure | Step Direction Description RQ 1 T UICC Send Manage Secure Channel - Start Secure Channel command 2 UICC T Normal ending of command 3 T UICC Send Manage Secure Channel - Start Secure Channel response 4 UICC T Return Session Number = 3 Data as detailed in clause 4.4.6.4 5 T UICC Send TRANSACT DATA command First... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.2 Sub Test group 4.2 Transact Data - Response Data | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.2.1 Test case 1: Transact Data - Response Data in 1 secure channel TLV | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.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. |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.2.1.2 Initial conditions | • The Terminal has an application that is able to manage and communicate using an APDU application - application secure channel. • The secure channel MSA and CSA have been that has been negotiated and the secure channel has not been started. • The UICC has an Endpoint that can handle an endpoint data container size of ... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.2.1.3 Test procedure | Step Direction Description RQ 1 T UICC Send Manage Secure Channel - Start Secure Channel command 2 UICC T Normal ending of command 3 T UICC Send Manage Secure Channel - Start Secure Channel response 4 UICC T Return Session Number = 3 Data as detailed in clause 4.4.6.4 5 T UICC Send TRANSACT DATA command First... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.2.2 Test case 2: Transact Data - Response Data in 2 secure channel TLVs | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.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.4.2.2.2 Initial conditions | • The Terminal has an application that is able to manage and communicate using an APDU application - application secure channel with the application on the UICC Simulator. • The secure channel Master SA and Connection SA have been negotiated and the secure channel has not been started. • The UICC has Endpoints that can... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.2.2.3 Test procedure | Step Direction Description RQ 1 T UICC Send Manage Secure Channel - Start Secure Channel command 2 UICC T Normal ending of command 3 T UICC Send Manage Secure Channel - Start Secure Channel response 4 UICC T Return Session Number = 3 Data as detailed in clause 4.4.6.4 5 T UICC Send TRANSACT DATA command First... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.2.3 Test case 3: Transact Data - Response Data in 25 secure channel TLVs | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.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.4.2.3.2 Initial conditions | • The Terminal has an application that is able to manage and communicate using an APDU application - application secure channel with the application on the UICC Simulator. • The secure channel Master SA and Connection SA have been negotiated and the secure channel has not been started. • The UICC has Endpoints that can... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.2.3.3 Test procedure | Step Direction Description RQ 1 T UICC Send Manage Secure Channel - Start Secure Channel command 2 UICC T Normal ending of command 3 T UICC Send Manage Secure Channel - Start Secure Channel response 4 UICC T Return Session Number = 3 Data as detailed in clause 4.4.6.4 5 T UICC Send TRANSACT DATA command First... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.3 Sub Test group 4.3 Retransmission | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.3.1 Test case 1: Transact Data using resend mechanism | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.3.1.1 Test execution | The test procedure shall only be executed for the following considerations: • The Terminal has an application that is able to manage and communicate using an APDU application - application secure channel with the application on the UICC Simulator. • The secure channel Master SA and Connection SA have been negotiated an... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.3.1.2 Initial conditions | • The Terminal has an application that is able to manage and communicate using an APDU application - application secure channel with the application on the UICC Simulator. • The secure channel Master SA and Connection SA have been negotiated and the secure channel has not been started. • The UICC has Endpoints that can... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.3.1.3 Test procedure | Step Direction Description RQ 1 T UICC Send Manage Secure Channel - Start Secure Channel command 2 UICC T Normal ending of command 3 T UICC Send Manage Secure Channel - Start Secure Channel response 4 UICC T Return Session Number = 3 Data as detailed in clause 4.4.6.4 5 T UICC Send TRANSACT DATA command First... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.4 Sub Test group 4.4 Transact Data - - Multiple secure channels | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.4.1 Test case 1: Transact Data - Multiple secure channels in 1 message | |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.4.1.1 Test execution | This test verifies that the DUT is able to receive process and respond to two TRANSACT DATA sessions interleaved. The test procedure shall only be executed for the following considerations: • Applicable The Terminal shall support the endpoint container size as indicated in the retrieve endpoint provided by the UICC sim... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.4.1.2 Initial conditions | • The Terminal has 2 applications that are able to manage and communicate using an APDU application - application secure channel. • The secure channel Master SAs and Connection SAs have been negotiated and neither secure channel has been started. • One Terminal Endpoint can handle an endpoint data container size of 127... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.4.1.3 Test procedure | The test procedures as detailed in clauses 6.4.1.1.3 and 6.4.1.2.3 the steps may be interleaved with each other or carried out one after the other. Step Direction Description RQ 1 T UICC T The test procedures as detailed in clauses 6.4.1.1.3 and 6.4.1.2.3 the steps may be interleaved with each other or carried out ... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.4.2.1 Test execution | This test verifies that the DUT is able to receive process and respond to two TRANSACT DATA sessions interleaved. The test procedure shall only be executed for the following considerations: • Applicable The Terminal shall support the endpoint container size as indicated in the retrieve endpoint provided by the UICC sim... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.4.2.2 Initial conditions | • The Terminal has 2 applications that are able to manage and communicate using an APDU application - application secure channel. • The secure channel Master SAs and Connection SAs have been negotiated and neither secure channel has been started. • One Terminal Endpoint can handle an endpoint data container size of 127... |
a7b712580d7cf7f68ad7e3468efa1fa2 | 103 484-1 | 6.4.4.2.3 Test procedure | The test procedures as detailed in clauses 6.4.1.1.3 and 6.4.1.2.3 the steps may be interleaved with each other or carried out one after the other. Step Direction Description RQ 1 T UICC T The test procedures as detailed in clauses 6.4.1.1.3 and 6.4.1.2.3 the steps may be interleaved with each other or carried out ... |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 1 Scope | The present document specifies high level requirements for the application of Attribute Based Encryption (ABE) to protect PII and personal data on IoT devices/services, cloud services, Wireless Local Area Networks and mobile services, where access to data has to be given to multiple parties and under different conditio... |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 2 References | |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 2.1 Normative 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 referenced document (including any amendments) applies. Referenced documents which a... |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 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. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] Italian Digital Agency: "Three-Year Pla... |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 3 Definitions and abbreviations | |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: cloud platform provider: cloud service provider providing identity management services and interfaces for third party applications using the platform services cloud platform user: cloud service user consuming one or more platform servi... |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 2G 2nd Generation (mobile networks) 3G 3nd Generation (mobile networks) 4G 4nd Generation (mobile networks) also known as LTE ETSI ETSI TS 103 458 V1.1.1 (2018-06) 10 5G 5nd Generation (mobile networks) ABAC Attribute Based Access Control ABE ... |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 4 Mobile use case | |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 4.1 Introduction | |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 4.1.1 Scenario | This solution presents an alternative mechanism to conceal permanent or long-term subscription identifier when a temporary subscription identifier is not available (c.f. initial Attach Request in LTE). Information provided over the air during initial attach request in LTE can allow a passive eavesdropper to obtain a va... |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 4.1.2 Preliminary considerations | A major problem in current mobile networks is that identifiers are occasionally exposed in situations where no security context (i.e. shared cryptographic material) is available, neither to authenticate identity requests, nor to protect (encrypt) the IMSI in the identity response, as well as in attach request messages,... |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 4.2 High level requirements | The present document specifies the following high level requirements (table 4.1) for the Mobile use case. ETSI ETSI TS 103 458 V1.1.1 (2018-06) 13 Table 4.1: Requirements derived from the "Mobile" use case ID Requirement MO#1 The solution shall protect the entire long-term identifier (MCC, MNC and MSIN in IMSI or IMEI)... |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 4.3 Use case | |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 4.3.1 Stakeholders | A 3GPP mobile network architecture [i.3] is assumed. In particular, the following roles are defined: • Home Network: is the central source for mobility services to the subscriber. The subscriber has a direct subscription with the Home Network: an identity for the subscriber has been allocated before any access to the n... |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 4.3.2 Preconditions | Relying on a trusted hardware, the Trusted Authority (TA) securely generates the master secret key (MSK), the global master public key (MPK), and the corresponding secret keys according to a selected large universe ABE scheme. As the TA uses a large universe ABE scheme, secret keys can be generated initially or in real... |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 4.3.3 Trigger | The UE tries an Initial Attach request to the Visited Network. |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 4.3.4 Flow of events | The Visited Network broadcasts (continuously) its assigned attributes together with its network identifiers (MCC and MNC). The UE encrypts the subscription identifier (IMSI) according to an ABE scheme by using the global public key MPK and the attribute received in broadcast over the air (the attribute identifying the ... |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 4.3.5 Exit Condition | The Authentication Vector is returned to the Visited Network. The standard 3G/4G/5G authentication procedure between the UE and the Visited Network is finally executed. |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 4.3.6 Security Aspects | In the 3G/4G/5G system, the network identifiers (MCC, MNC) of the participating network operators are assumed to be publicly known. The trust framework is regulated by inter-operator roaming agreements, and the involved operators are trusted to function accordingly, because of their business interests. In the case of A... |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 4.3.7 Recommended ABE scheme | The CCA-secure KP-ABE with KP-FAME-KEM [i.21] ABE scheme should be used. |
e17efbe6bcd60372b406ce35b2ebc2c9 | 103 458 | 5 Privacy-Preserving federated WLANs use case |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.