id
stringlengths 7
13
| title
stringlengths 7
396
| type
stringclasses 2
values | version
stringclasses 249
values | url
stringlengths 90
98
| scope
stringlengths 0
83.8k
|
|---|---|---|---|---|---|
102 230
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification (Release 8)
|
TS
|
8.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102230/08.00.00_60/ts_102230v080000p.pdf
|
The present document specifies the interface test for the Terminal/UICC. The present document specifies the tests of: • physical characteristics of the UICC; • the electrical interface between the UICC and the Terminal; • the initial communication establishment and the transport protocols; • the application independent procedures.
|
102 230
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification (Release 7)
|
TS
|
7.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102230/07.02.00_60/ts_102230v070200p.pdf
|
The present document specifies the interface test for the Terminal/UICC. The present document specifies the tests of: • physical characteristics of the UICC; • the electrical interface between the UICC and the Terminal; • the initial communication establishment and the transport protocols; • the application independent procedures.
|
102 230
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification (Release 6)
|
TS
|
6.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102230/06.00.00_60/ts_102230v060000p.pdf
|
The present document specifies the interface test for the Terminal/UICC. The present document specifies the tests of: • physical characteristics of the UICC; • the electrical interface between the UICC and the Terminal; • the initial communication establishment and the transport protocols; • the application independent procedures.
|
102 230
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification (Release 5)
|
TS
|
5.10.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102230/05.10.00_60/ts_102230v051000p.pdf
|
The present document specifies the interface test for the Terminal/UICC. The present document specifies the tests of: • physical characteristics of the UICC; • the electrical interface between the UICC and the Terminal; • the initial communication establishment and the transport protocols; • the application independent procedures.
|
102 230
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification (Release 4)
|
TS
|
4.12.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102230/04.12.00_60/ts_102230v041200p.pdf
|
The present document specifies the interface test for the Terminal/UICC. The present document specifies the tests of: • physical characteristics of the UICC; • the electrical interface between the UICC and the Terminal; • the initial communication establishment and the transport protocols; • the application independent procedures.
|
102 230
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification (Release 1999)
|
TS
|
3.12.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102230/03.12.00_60/ts_102230v031200p.pdf
|
The present document specifies the interface test for the Terminal/UICC. The present document specifies the tests of: • physical characteristics of the UICC; • the electrical interface between the UICC and the Terminal; • the initial communication establishment and the transport protocols; • the application independent procedures.
|
102 229
|
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Interface Protocol Requirements Definition; Aggregate Bearer Load Control - H.248 Package
|
TS
|
4.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102229/04.01.01_60/ts_102229v040101p.pdf
|
The present document defines the aggregate load control information flows which are part of the N2 and N3 reference points network architecture as described in TS 101 882 release 4 [1]. The present document is supporting only provisioned aggregate bearer functionality. Mixing of different bearer capabilities of PSTN/ISDN service over the same aggregate bearer is supported. The aggregate bearer is provisioned with a single set of QoS parameters.
|
102 228
|
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Technology Mapping; Implementation of TIPHON architecture using BICC
|
TS
|
4.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102228/04.01.01_60/ts_102228v040101p.pdf
|
The present document defines the mapping to the BICC CS2 protocols necessary to implement the TIPHON protocol framework as described in TS 101 882 [2]. The present document is applicable to equipment performing the roles of terminal, and Gateway, and also to entities within the IP network that are necessary to support the four scenarios of TIPHON Release 3. Where the text indicates the status of a requirement (i.e. as strict command or prohibition, as authorizations leaving freedom, or as a capability or possibility), this may modify the nature of a requirement within a referenced standard used to provide the capability.
|
102 226
|
Smart Cards; Remote APDU structure for UICC based applications (Release 19)
|
TS
|
19.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102226/19.00.00_60/ts_102226v190000p.pdf
|
The present document defines the remote management of the UICC based on any of the secured packet structures specified in ETSI TS 102 225 [1]. It specifies the APDU format for remote management. Furthermore the present document specifies: • A set of commands coded according to this APDU structure and used in the remote file management on the UICC. This is based on ETSI TS 102 221 [2]. • A set of commands coded according to this APDU structure and used in the remote application management on the UICC. This is based on the GlobalPlatform Card Specification [4], its Amendments and Configuration documents.
|
102 226
|
<empty>
|
TS
|
18.5.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102226/18.05.00_60/ts_102226v180500p.pdf
|
The present document defines the remote management of the UICC based on any of the secured packet structures specified in ETSI TS 102 225 [1]. It specifies the APDU format for remote management. Furthermore the present document specifies: • A set of commands coded according to this APDU structure and used in the remote file management on the UICC. This is based on ETSI TS 102 221 [2]. • A set of commands coded according to this APDU structure and used in the remote application management on the UICC. This is based on the GlobalPlatform Card Specification [4], its Amendments and Configuration documents.
|
102 226
|
Smart Cards; Remote APDU structure for UICC based applications (Release 17)
|
TS
|
17.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102226/17.02.00_60/ts_102226v170200p.pdf
|
The present document defines the remote management of the UICC based on any of the secured packet structures specified in ETSI TS 102 225 [1]. It specifies the APDU format for remote management. Furthermore the present document specifies: • A set of commands coded according to this APDU structure and used in the remote file management on the UICC. This is based on ETSI TS 102 221 [2]. • A set of commands coded according to this APDU structure and used in the remote application management on the UICC. This is based on the GlobalPlatform Card Specification [4], its Amendments and Configuration documents.
|
102 226
|
Smart Cards; Remote APDU structure for UICC based applications (Release 16)
|
TS
|
16.3.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102226/16.03.00_60/ts_102226v160300p.pdf
|
The present document defines the remote management of the UICC based on any of the secured packet structures specified in ETSI TS 102 225 [1]. It specifies the APDU format for remote management. Furthermore the present document specifies: • A set of commands coded according to this APDU structure and used in the remote file management on the UICC. This is based on ETSI TS 102 221 [2]. • A set of commands coded according to this APDU structure and used in the remote application management on the UICC. This is based on the GlobalPlatform Card Specification [4], its Amendments and Configuration documents.
|
102 226
|
Smart Cards; Remote APDU structure for UICC based applications (Release 15)
|
TS
|
15.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102226/15.00.00_60/ts_102226v150000p.pdf
|
The present document defines the remote management of the UICC based on any of the secured packet structures specified in ETSI TS 102 225 [1]. It specifies the APDU format for remote management. Furthermore the present document specifies: • A set of commands coded according to this APDU structure and used in the remote file management on the UICC. This is based on ETSI TS 102 221 [2]. • A set of commands coded according to this APDU structure and used in the remote application management on the UICC. This is based on the GlobalPlatform Card Specification [4], its Amendments and Configuration documents.
|
102 226
|
Smart Cards; Remote APDU structure for UICC based applications (Release 14)
|
TS
|
14.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102226/14.00.00_60/ts_102226v140000p.pdf
|
The present document defines the remote management of the UICC based on any of the secured packet structures specified in ETSI TS 102 225 [1]. It specifies the APDU format for remote management. Furthermore the present document specifies: • A set of commands coded according to this APDU structure and used in the remote file management on the UICC. This is based on ETSI TS 102 221 [2]. • A set of commands coded according to this APDU structure and used in the remote application management on the UICC. This is based on the GlobalPlatform Card Specification [4], its Amendments and Configuration documents.
|
102 226
|
Smart Cards; Remote APDU structure for UICC based applications (Release 13)
|
TS
|
13.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102226/13.01.00_60/ts_102226v130100p.pdf
|
The present document defines the remote management of the UICC based on any of the secured packet structures specified in ETSI TS 102 225 [1]. It specifies the APDU format for remote management. Furthermore the present document specifies: • A set of commands coded according to this APDU structure and used in the remote file management on the UICC. This is based on ETSI TS 102 221 [2]. • A set of commands coded according to this APDU structure and used in the remote application management on the UICC. This is based on the GlobalPlatform Card Specification [4], its Amendments and Configuration documents.
|
102 226
|
Smart Cards; Remote APDU structure for UICC based applications (Release 12)
|
TS
|
12.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102226/12.00.00_60/ts_102226v120000p.pdf
|
The present document defines the remote management of the UICC based on any of the secured packet structures specified in ETSI TS 102 225 [1]. It specifies the APDU format for remote management. Furthermore the present document specifies: • A set of commands coded according to this APDU structure and used in the remote file management on the UICC. This is based on ETSI TS 102 221 [2]. • A set of commands coded according to this APDU structure and used in the remote application management on the UICC. This is based on the GlobalPlatform Card Specification [4], its Amendments and Configuration documents.
|
102 226
|
Smart Cards; Remote APDU structure for UICC based applications (Release 11)
|
TS
|
11.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102226/11.02.00_60/ts_102226v110200p.pdf
|
The present document defines the remote management of the UICC based on any of the secured packet structures specified in ETSI TS 102 225 [1]. It specifies the APDU format for remote management. Furthermore the present document specifies: • A set of commands coded according to this APDU structure and used in the remote file management on the UICC. This is based on ETSI TS 102 221 [2]. • A set of commands coded according to this APDU structure and used in the remote application management on the UICC. This is based on the GlobalPlatform Card Specification [4], its Amendments and Configuration documents.
|
102 226
|
Smart Cards; Remote APDU structure for UICC based applications (Release 10)
|
TS
|
10.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102226/10.02.00_60/ts_102226v100200p.pdf
|
The present document defines the remote management of the UICC based on any of the secured packet structures specified in ETSI TS 102 225 [1]. It specifies the APDU format for remote management. Furthermore the present document specifies: • A set of commands coded according to this APDU structure and used in the remote file management on the UICC. This is based on ETSI TS 102 221 [2]. • A set of commands coded according to this APDU structure and used in the remote application management on the UICC. This is based on the GlobalPlatform Card Specification [4], its Amendments and Configuration documents.
|
102 226
|
Smart Cards; Remote APDU structure for UICC based applications (Release 9)
|
TS
|
9.6.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102226/09.06.00_60/ts_102226v090600p.pdf
|
The present document defines the remote management of the UICC based on any of the secured packet structures specified in ETSI TS 102 225 [1]. It specifies the APDU format for remote management. Furthermore the present document specifies: • A set of commands coded according to this APDU structure and used in the remote file management on the UICC. This is based on ETSI TS 102 221 [2]. • A set of commands coded according to this APDU structure and used in the remote application management on the UICC. This is based on the GlobalPlatform Card Specification [4], its Amendments and Configuration documents.
|
102 226
|
Smart Cards; Remote APDU structure for UICC based applications (Release 8)
|
TS
|
8.3.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102226/08.03.00_60/ts_102226v080300p.pdf
|
The present document defines the remote management of the UICC based on any of the secured packet structures specified in ETSI TS 102 225 [1]. It specifies the APDU format for remote management. Furthermore the present document specifies: • A set of commands coded according to this APDU structure and used in the remote file management on the UICC. This is based on ETSI TS 102 221 [2]. • A set of commands coded according to this APDU structure and used in the remote application management on the UICC. This is based on the GlobalPlatform Card Specification [4], its Amendments and Configuration documents.
|
102 226
|
Smart Cards; Remote APDU structure for UICC based applications (Release 7)
|
TS
|
7.8.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102226/07.08.01_60/ts_102226v070801p.pdf
|
The present document defines the remote management of the UICC based on any of the secured packet structures specified in ETSI TS 102 225 [1]. It specifies the APDU format for remote management. Furthermore the present document specifies: • A set of commands coded according to this APDU structure and used in the remote file management on the UICC. This is based on ETSI TS 102 221 [2]. • A set of commands coded according to this APDU structure and used in the remote application management on the UICC. This is based on the GlobalPlatform Card Specification [4], its Amendments and Configuration documents.
|
102 226
|
Smart Cards; Remote APDU structure for UICC based applications (Release 6)
|
TS
|
6.18.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102226/06.18.00_60/ts_102226v061800p.pdf
|
The present document defines the remote management of the UICC based on any of the secured packet structures specified in ETSI TS 102 225 [1]. It specifies the APDU format for remote management. Furthermore the present document specifies: • A set of commands coded according to this APDU structure and used in the remote file management on the UICC. This is based on ETSI TS 102 221 [2]. • A set of commands coded according to this APDU structure and used in the remote application management on the UICC. This is based on the GlobalPlatform Card Specification [4], its Amendments and Configuration documents.
|
102 225
|
Smart Cards; Secured packet structure for UICC based applications (Release 19)
|
TS
|
19.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102225/19.00.00_60/ts_102225v190000p.pdf
|
The present document specifies the structure of Secured Packets for different transport and security mechanisms. It is applicable to the exchange of secured packets between an entity in a network and an entity in the UICC. Secured Packets contain application messages to which certain mechanisms according to ETSI TS 102 224 [1] have been applied. Application messages are commands or data exchanged between an application resident in or behind the network and on the UICC. The Sending/Receiving Entity in the network and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
102 225
|
<empty>
|
TS
|
18.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102225/18.01.00_60/ts_102225v180100p.pdf
|
The present document specifies the structure of Secured Packets for different transport and security mechanisms. It is applicable to the exchange of secured packets between an entity in a network and an entity in the UICC. Secured Packets contain application messages to which certain mechanisms according to ETSI TS 102 224 [1] have been applied. Application messages are commands or data exchanged between an application resident in or behind the network and on the UICC. The Sending/Receiving Entity in the network and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
102 225
|
Smart Cards; Secured packet structure for UICC based applications (Release 17)
|
TS
|
17.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102225/17.00.00_60/ts_102225v170000p.pdf
|
The present document specifies the structure of Secured Packets for different transport and security mechanisms. It is applicable to the exchange of secured packets between an entity in a network and an entity in the UICC. Secured Packets contain application messages to which certain mechanisms according to ETSI TS 102 224 [1] have been applied. Application messages are commands or data exchanged between an application resident in or behind the network and on the UICC. The Sending/Receiving Entity in the network and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
102 225
|
Smart Cards; Secured packet structure for UICC based applications (Release 16)
|
TS
|
16.0.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102225/16.00.01_60/ts_102225v160001p.pdf
|
The present document specifies the structure of Secured Packets for different transport and security mechanisms. It is applicable to the exchange of secured packets between an entity in a network and an entity in the UICC. Secured Packets contain application messages to which certain mechanisms according to ETSI TS 102 224 [1] have been applied. Application messages are commands or data exchanged between an application resident in or behind the network and on the UICC. The Sending/Receiving Entity in the network and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
102 225
|
Smart Cards; Secured packet structure for UICC based applications (Release 15)
|
TS
|
15.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102225/15.00.00_60/ts_102225v150000p.pdf
|
The present document specifies the structure of Secured Packets for different transport and security mechanisms. It is applicable to the exchange of secured packets between an entity in a network and an entity in the UICC. Secured Packets contain application messages to which certain mechanisms according to ETSI TS 102 224 [1] have been applied. Application messages are commands or data exchanged between an application resident in or behind the network and on the UICC. The Sending/Receiving Entity in the network and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
102 225
|
Smart Cards; Secured packet structure for UICC based applications (Release 14)
|
TS
|
14.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102225/14.00.00_60/ts_102225v140000p.pdf
|
The present document specifies the structure of Secured Packets for different transport and security mechanisms. It is applicable to the exchange of secured packets between an entity in a network and an entity in the UICC. Secured Packets contain application messages to which certain mechanisms according to ETSI TS 102 224 [1] have been applied. Application messages are commands or data exchanged between an application resident in or behind the network and on the UICC. The Sending/Receiving Entity in the network and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
102 225
|
Smart Cards; Secured packet structure for UICC based applications (Release 13)
|
TS
|
13.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102225/13.00.00_60/ts_102225v130000p.pdf
|
The present document specifies the structure of Secured Packets for different transport and security mechanisms. It is applicable to the exchange of secured packets between an entity in a network and an entity in the UICC. Secured Packets contain application messages to which certain mechanisms according to ETSI TS 102 224 [1] have been applied. Application messages are commands or data exchanged between an application resident in or behind the network and on the UICC. The Sending/Receiving Entity in the network and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
102 225
|
Smart Cards; Secured packet structure for UICC based applications (Release 12)
|
TS
|
12.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102225/12.01.00_60/ts_102225v120100p.pdf
|
The present document specifies the structure of Secured Packets for different transport and security mechanisms. It is applicable to the exchange of secured packets between an entity in a network and an entity in the UICC. Secured Packets contain application messages to which certain mechanisms according to ETSI TS 102 224 [1] have been applied. Application messages are commands or data exchanged between an application resident in or behind the network and on the UICC. The Sending/Receiving Entity in the network and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
102 225
|
Smart Cards; Secured packet structure for UICC based applications (Release 11)
|
TS
|
11.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102225/11.00.00_60/ts_102225v110000p.pdf
|
The present document specifies the structure of Secured Packets for different transport and security mechanisms. It is applicable to the exchange of secured packets between an entity in a network and an entity in the UICC. Secured Packets contain application messages to which certain mechanisms according to ETSI TS 102 224 [1] have been applied. Application messages are commands or data exchanged between an application resident in or behind the network and on the UICC. The Sending/Receiving Entity in the network and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
102 225
|
Smart Cards; Secured packet structure for UICC based applications (Release 10)
|
TS
|
10.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102225/10.00.00_60/ts_102225v100000p.pdf
|
The present document specifies the structure of Secured Packets for different transport and security mechanisms. It is applicable to the exchange of secured packets between an entity in a network and an entity in the UICC. Secured Packets contain application messages to which certain mechanisms according to ETSI TS 102 224 [1] have been applied. Application messages are commands or data exchanged between an application resident in or behind the network and on the UICC. The Sending/Receiving Entity in the network and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
102 225
|
Smart Cards; Secured packet structure for UICC based applications (Release 9)
|
TS
|
9.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102225/09.02.00_60/ts_102225v090200p.pdf
|
The present document specifies the structure of Secured Packets for different transport and security mechanisms. It is applicable to the exchange of secured packets between an entity in a network and an entity in the UICC. Secured Packets contain application messages to which certain mechanisms according to ETSI TS 102 224 [1] have been applied. Application messages are commands or data exchanged between an application resident in or behind the network and on the UICC. The Sending/Receiving Entity in the network and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
102 225
|
Smart Cards; Secured packet structure for UICC based applications (Release 8)
|
TS
|
8.5.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102225/08.05.00_60/ts_102225v080500p.pdf
|
The present document specifies the structure of Secured Packets for different transport and security mechanisms. It is applicable to the exchange of secured packets between an entity in a network and an entity in the UICC. Secured Packets contain application messages to which certain mechanisms according to ETSI TS 102 224 [1] have been applied. Application messages are commands or data exchanged between an application resident in or behind the network and on the UICC. The Sending/Receiving Entity in the network and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
102 225
|
Smart Cards; Secured packet structure for UICC based applications (Release 7)
|
TS
|
7.4.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102225/07.04.00_60/ts_102225v070400p.pdf
|
The present document specifies the structure of Secured Packets for different transport and security mechanisms. It is applicable to the exchange of secured packets between an entity in a network and an entity in the UICC. Secured Packets contain application messages to which certain mechanisms according to ETSI TS 102 224 [1] have been applied. Application messages are commands or data exchanged between an application resident in or behind the network and on the UICC. The Sending/Receiving Entity in the network and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
102 225
|
Smart cards; Secured packet structure for UICC based applications (Release 6)
|
TS
|
6.8.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102225/06.08.00_60/ts_102225v060800p.pdf
|
The present document specifies the structure of Secured Packets for different transport and security mechanisms. It is applicable to the exchange of secured packets between an entity in a network and an entity in the UICC. Secured Packets contain application messages to which certain mechanisms according to ETSI TS 102 224 [1] have been applied. Application messages are commands or data exchanged between an application resident in or behind the network and on the UICC. The Sending/Receiving Entity in the network and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
102 224
|
Smart Cards; Security mechanisms for UICC based Applications Functional requirements (Release 18)
|
TS
|
18.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102224/18.00.00_60/ts_102224v180000p.pdf
|
The present document provides standardized security mechanisms in conjunction with the Card Application Toolkit for the interface between a Network Entity and a UICC. The security mechanisms which are specified are independent of applications. The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in ETSI TS 102 225 [1]. Within the scope of the present document, the UICC refers here to an ICC which support at least one application in order to access a cellular network. The ICC is considered as a platform, which is based on ETSI TS 102 221 [4].
|
102 224
|
Smart Cards; Security mechanisms for UICC based Applications Functional requirements (Release 17)
|
TS
|
17.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102224/17.00.00_60/ts_102224v170000p.pdf
|
The present document provides standardized security mechanisms in conjunction with the Card Application Toolkit for the interface between a Network Entity and a UICC. The security mechanisms which are specified are independent of applications. The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in ETSI TS 102 225 [1]. Within the scope of the present document, the UICC refers here to an ICC which support at least one application in order to access a cellular network. The ICC is considered as a platform, which is based on ETSI TS 102 221 [4].
|
102 224
|
Smart Cards; Security mechanisms for UICC based Applications Functional requirements (Release 16)
|
TS
|
16.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102224/16.00.00_60/ts_102224v160000p.pdf
|
The present document provides standardized security mechanisms in conjunction with the Card Application Toolkit for the interface between a Network Entity and a UICC. The security mechanisms which are specified are independent of applications. The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in ETSI TS 102 225 [1]. Within the scope of the present document, the UICC refers here to an ICC which support at least one application in order to access a cellular network. The ICC is considered as a platform, which is based on ETSI TS 102 221 [4].
|
102 224
|
Smart Cards; Security mechanisms for UICC based Applications Functional requirements (Release 15)
|
TS
|
15.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102224/15.00.00_60/ts_102224v150000p.pdf
|
The present document provides standardized security mechanisms in conjunction with the Card Application Toolkit for the interface between a Network Entity and a UICC. The security mechanisms which are specified are independent of applications. The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in ETSI TS 102 225 [1]. Within the scope of the present document, the UICC refers here to an ICC which support at least one application in order to access a cellular network. The ICC is considered as a platform, which is based on ETSI TS 102 221 [4].
|
102 224
|
Smart Cards; Security mechanisms for UICC based Applications - Functional requirements (Release 14)
|
TS
|
14.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102224/14.00.00_60/ts_102224v140000p.pdf
|
The present document provides standardized security mechanisms in conjunction with the Card Application Toolkit for the interface between a Network Entity and a UICC. The security mechanisms which are specified are independent of applications. The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in ETSI TS 102 225 [1]. Within the scope of the present document, the UICC refers here to an ICC which support at least one application in order to access a cellular network. The ICC is considered as a platform, which is based on ETSI TS 102 221 [4].
|
102 224
|
Smart Cards; Security mechanisms for UICC based Applications - Functional requirements (Release 13)
|
TS
|
13.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102224/13.00.00_60/ts_102224v130000p.pdf
|
The present document provides standardized security mechanisms in conjunction with the Card Application Toolkit for the interface between a Network Entity and a UICC. The security mechanisms which are specified are independent of applications. The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in ETSI TS 102 225 [1]. Within the scope of the present document, the UICC refers here to an ICC which support at least one application in order to access a cellular network. The ICC is considered as a platform, which is based on ETSI TS 102 221 [4].
|
102 224
|
Smart Cards; Security mechanisms for UICC based Applications - Functional requirements (Release 12)
|
TS
|
12.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102224/12.00.00_60/ts_102224v120000p.pdf
|
The present document provides standardized security mechanisms in conjunction with the Card Application Toolkit for the interface between a Network Entity and a UICC. The security mechanisms which are specified are independent of applications. The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in ETSI TS 102 225 [1]. Within the scope of the present document, the UICC refers here to an ICC which support at least one application in order to access a cellular network. The ICC is considered as a platform, which is based on ETSI TS 102 221 [4].
|
102 224
|
Smart Cards; Security mechanisms for UICC based Applications - Functional requirements (Release 11)
|
TS
|
11.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102224/11.00.00_60/ts_102224v110000p.pdf
|
The present document provides standardized security mechanisms in conjunction with the Card Application Toolkit for the interface between a Network Entity and a UICC. The security mechanisms which are specified are independent of applications. The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in ETSI TS 102 225 [1]. Within the scope of the present document, the UICC refers here to an ICC which support at least one application in order to access a cellular network. The ICC is considered as a platform, which is based on ETSI TS 102 221 [4].
|
102 224
|
Smart Cards; Security mechanisms for UICC based Applications - Functional requirements (Release 10)
|
TS
|
10.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102224/10.00.00_60/ts_102224v100000p.pdf
|
The present document provides standardized security mechanisms in conjunction with the Card Application Toolkit for the interface between a Network Entity and a UICC. The security mechanisms which are specified are independent of applications. The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in ETSI TS 102 225 [1]. Within the scope of the present document, the UICC refers here to an ICC which support at least one application in order to access a cellular network. The ICC is considered as a platform, which is based on ETSI TS 102 221 [4].
|
102 224
|
Smart Cards; Security mechanisms for UICC based Applications - Functional requirements (Release 9)
|
TS
|
9.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102224/09.00.00_60/ts_102224v090000p.pdf
|
The present document provides standardized security mechanisms in conjunction with the Card Application Toolkit for the interface between a Network Entity and a UICC. The security mechanisms which are specified are independent of applications. The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in ETSI TS 102 225 [1]. Within the scope of the present document, the UICC refers here to an ICC which support at least one application in order to access a cellular network. The ICC is considered as a platform, which is based on ETSI TS 102 221 [4].
|
102 224
|
Smart Cards; Security mechanisms for UICC based Applications - Functional requirements (Release 8)
|
TS
|
8.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102224/08.00.00_60/ts_102224v080000p.pdf
|
The present document provides standardized security mechanisms in conjunction with the Card Application Toolkit for the interface between a Network Entity and a UICC. The security mechanisms which are specified are independent of applications. The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in ETSI TS 102 225 [1]. Within the scope of the present document, the UICC refers here to an ICC which support at least one application in order to access a cellular network. The ICC is considered as a platform, which is based on ETSI TS 102 221 [4].
|
102 224
|
Smart Cards; Security mechanisms for UICC based Applications - Functional requirements (Release 7)
|
TS
|
7.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102224/07.01.00_60/ts_102224v070100p.pdf
|
The present document provides standardized security mechanisms in conjunction with the Card Application Toolkit for the interface between a Network Entity and a UICC. The security mechanisms which are specified are independent of applications. The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in ETSI TS 102 225 [1]. Within the scope of the present document, the UICC refers here to an ICC which support at least one application in order to access a cellular network. The ICC is considered as a platform, which is based on ETSI TS 102 221 [4].
|
102 224
|
Smart Cards; Security mechanisms for UICC based Applications - Functional requirements (Release 6)
|
TS
|
6.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102224/06.01.00_60/ts_102224v060100p.pdf
|
The present document provides standardized security mechanisms in conjunction with the Card Application Toolkit for the interface between a Network Entity and a UICC. The security mechanisms which are specified are independent of applications. The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in ETSI TS 102 225 [1]. Within the scope of the present document, the UICC refers here to an ICC which support at least one application in order to access a cellular network. The ICC is considered as a platform, which is based on ETSI TS 102 221 [4].
|
102 223
|
Smart Cards; Card Application Toolkit (CAT) (Release 18)
|
TS
|
18.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102223/18.02.00_60/ts_102223v180200p.pdf
|
The present document defines the interface between the UICC and the terminal, and mandatory terminal procedures, specifically for "NAA Card Application Toolkit". The Card Application Toolkit (CAT) is a set of generic commands and procedures for use by the ICC, irrespective of the access technology of the network. Within the scope of the present document, the UICC refers here to an ICC which supports at least one application in order to access a network. This application is called here Network Access Application (NAA). The ICC is considered as a platform, which is either based on ETSI TS 102 221 [1] or ETSI TS 102 600 [38], here called "3G platform" or ETSI TS 151 011 [8], here called "2G platform". NAA can be: • a USIM application, as defined in ETSI TS 131 102 [6], which can reside only on a 3G platform; • a SIM application, as defined in ETSI TS 151 011 [8], which can reside either on a 3G or a 2G platform; • a TSIM application, as defined in ETSI TS 100 812 [i.2], which can reside only on a 3G platform; • a ISIM application, as defined in ETSI TS 131 103 [36], which can reside only on a 3G platform; • a CSIM application, as defined in 3GPP2 C.S0065-B [53]; • an R-UIM application, as defined in 3GPP2 C.S0023-D [i.4]; or • other applications residing on a 3G platform or a 2G platform. Specifying the interface is to ensure interoperability between an ICC and a terminal independently of the respective manufacturers and operators. The present document specifies as well mechanisms in order to expand the generic set of commands and procedures by access technology specific ones. The present document defines: • the commands; • the application protocol; • the mandatory requirements on the ICC and terminal for each procedure. The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the ICC or the terminal are only specified where these reflect over the interface. The present document does not specify any of the security algorithms that may be used.
|
102 223
|
Smart Cards; Card Application Toolkit (CAT) (Release 17)
|
TS
|
17.6.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102223/17.06.00_60/ts_102223v170600p.pdf
|
The present document defines the interface between the UICC and the terminal, and mandatory terminal procedures, specifically for "NAA Card Application Toolkit". The Card Application Toolkit (CAT) is a set of generic commands and procedures for use by the ICC, irrespective of the access technology of the network. Within the scope of the present document, the UICC refers here to an ICC which supports at least one application in order to access a network. This application is called here Network Access Application (NAA). The ICC is considered as a platform, which is either based on ETSI TS 102 221 [1] or ETSI TS 102 600 [38], here called "3G platform" or ETSI TS 151 011 [8], here called "2G platform". NAA can be: • a USIM application, as defined in ETSI TS 131 102 [6], which can reside only on a 3G platform; • a SIM application, as defined in ETSI TS 151 011 [8], which can reside either on a 3G or a 2G platform; • a TSIM application, as defined in ETSI TS 100 812 [i.2], which can reside only on a 3G platform; • a ISIM application, as defined in ETSI TS 131 103 [36], which can reside only on a 3G platform; • a CSIM application, as defined in 3GPP2 C.S0065-B [53]; • an R-UIM application, as defined in 3GPP2 C.S0023-D [i.4]; or • other applications residing on a 3G platform or a 2G platform. Specifying the interface is to ensure interoperability between an ICC and a terminal independently of the respective manufacturers and operators. The present document specifies as well mechanisms in order to expand the generic set of commands and procedures by access technology specific ones. The present document defines: • the commands; • the application protocol; • the mandatory requirements on the ICC and terminal for each procedure. The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the ICC or the terminal are only specified where these reflect over the interface. The present document does not specify any of the security algorithms that may be used.
|
102 223
|
Smart Cards; Card Application Toolkit (CAT) (Release 16)
|
TS
|
16.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102223/16.01.00_60/ts_102223v160100p.pdf
|
The present document defines the interface between the UICC and the terminal, and mandatory terminal procedures, specifically for "NAA Card Application Toolkit". The Card Application Toolkit (CAT) is a set of generic commands and procedures for use by the ICC, irrespective of the access technology of the network. Within the scope of the present document, the UICC refers here to an ICC which supports at least one application in order to access a network. This application is called here Network Access Application (NAA). The ICC is considered as a platform, which is either based on ETSI TS 102 221 [1] or ETSI TS 102 600 [38], here called "3G platform" or ETSI TS 151 011 [8], here called "2G platform". NAA can be: • a USIM application, as defined in ETSI TS 131 102 [6], which can reside only on a 3G platform; • a SIM application, as defined in ETSI TS 151 011 [8], which can reside either on a 3G or a 2G platform; • a TSIM application, as defined in ETSI TS 100 812 [i.2], which can reside only on a 3G platform; • a ISIM application, as defined in ETSI TS 131 103 [36], which can reside only on a 3G platform; • a CSIM application, as defined in 3GPP2 C.S0065-B [53]; • an R-UIM application, as defined in 3GPP2 C.S0023-D [i.4]; or • other applications residing on a 3G platform or a 2G platform. Specifying the interface is to ensure interoperability between an ICC and a terminal independently of the respective manufacturers and operators. The present document specifies as well mechanisms in order to expand the generic set of commands and procedures by access technology specific ones. The present document defines: • the commands; • the application protocol; • the mandatory requirements on the ICC and terminal for each procedure. The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the ICC or the terminal are only specified where these reflect over the interface. The present document does not specify any of the security algorithms that may be used.
|
102 223
|
Smart Cards; Card Application Toolkit (CAT) (Release 15)
|
TS
|
15.4.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102223/15.04.00_60/ts_102223v150400p.pdf
|
The present document defines the interface between the UICC and the terminal, and mandatory terminal procedures, specifically for "NAA Card Application Toolkit". The Card Application Toolkit (CAT) is a set of generic commands and procedures for use by the ICC, irrespective of the access technology of the network. Within the scope of the present document, the UICC refers here to an ICC which supports at least one application in order to access a network. This application is called here Network Access Application (NAA). The ICC is considered as a platform, which is either based on ETSI TS 102 221 [1] or ETSI TS 102 600 [38], here called "3G platform" or ETSI TS 151 011 [8], here called "2G platform". NAA can be: • a USIM application, as defined in ETSI TS 131 102 [6], which can reside only on a 3G platform; • a SIM application, as defined in ETSI TS 151 011 [8], which can reside either on a 3G or a 2G platform; • a TSIM application, as defined in ETSI TS 100 812 [i.2], which can reside only on a 3G platform; • a ISIM application, as defined in ETSI TS 131 103 [36], which can reside only on a 3G platform; • a CSIM application, as defined in 3GPP2 C.S0065-B [53]; • an R-UIM application, as defined in 3GPP2 C.S0023-D [i.4]; or • other applications residing on a 3G platform or a 2G platform. Specifying the interface is to ensure interoperability between an ICC and a terminal independently of the respective manufacturers and operators. The present document specifies as well mechanisms in order to expand the generic set of commands and procedures by access technology specific ones. The present document defines: • the commands; • the application protocol; • the mandatory requirements on the ICC and terminal for each procedure. The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the ICC or the terminal are only specified where these reflect over the interface. The present document does not specify any of the security algorithms that may be used.
|
102 223
|
Smart Cards; Card Application Toolkit (CAT) (Release 14)
|
TS
|
14.3.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102223/14.03.00_60/ts_102223v140300p.pdf
|
The present document defines the interface between the UICC and the terminal, and mandatory terminal procedures, specifically for "NAA Card Application Toolkit". The Card Application Toolkit (CAT) is a set of generic commands and procedures for use by the ICC, irrespective of the access technology of the network. Within the scope of the present document, the UICC refers here to an ICC which supports at least one application in order to access a network. This application is called here Network Access Application (NAA). The ICC is considered as a platform, which is either based on ETSI TS 102 221 [1] or ETSI TS 102 600 [38], here called "3G platform" or ETSI TS 151 011 [8], here called "2G platform". NAA can be: • a USIM application, as defined in ETSI TS 131 102 [6], which can reside only on a 3G platform; • a SIM application, as defined in ETSI TS 151 011 [8], which can reside either on a 3G or a 2G platform; • a TSIM application, as defined in ETSI TS 100 812 [i.2], which can reside only on a 3G platform; • a ISIM application, as defined in ETSI TS 131 103 [36], which can reside only on a 3G platform; • a CSIM application, as defined in 3GPP2 C.S0065-B [53]; • an R-UIM application, as defined in 3GPP2 C.S0023-D [i.4]; or • other applications residing on a 3G platform or a 2G platform. Specifying the interface is to ensure interoperability between an ICC and a terminal independently of the respective manufacturers and operators. The present document specifies as well mechanisms in order to expand the generic set of commands and procedures by access technology specific ones. The present document defines: • the commands; • the application protocol; • the mandatory requirements on the ICC and terminal for each procedure. The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the ICC or the terminal are only specified where these reflect over the interface. The present document does not specify any of the security algorithms that may be used.
|
102 223
|
Smart Cards; Card Application Toolkit (CAT) (Release 13)
|
TS
|
13.4.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102223/13.04.00_60/ts_102223v130400p.pdf
|
The present document defines the interface between the UICC and the terminal, and mandatory terminal procedures, specifically for "NAA Card Application Toolkit". The Card Application Toolkit (CAT) is a set of generic commands and procedures for use by the ICC, irrespective of the access technology of the network. Within the scope of the present document, the UICC refers here to an ICC which supports at least one application in order to access a network. This application is called here Network Access Application (NAA). The ICC is considered as a platform, which is either based on ETSI TS 102 221 [1] or ETSI TS 102 600 [38], here called "3G platform" or ETSI TS 151 011 [8], here called "2G platform". NAA can be: • a USIM application, as defined in ETSI TS 131 102 [6], which can reside only on a 3G platform; • a SIM application, as defined in ETSI TS 151 011 [8], which can reside either on a 3G or a 2G platform; • a TSIM application, as defined in ETSI TS 100 812 [i.2], which can reside only on a 3G platform; • a ISIM application, as defined in ETSI TS 131 103 [36], which can reside only on a 3G platform; • a CSIM application, as defined in 3GPP2 C.S0065-B [53]; • an R-UIM application, as defined in 3GPP2 C.S0023-D [i.4]; or • other applications residing on a 3G platform or a 2G platform. Specifying the interface is to ensure interoperability between an ICC and a terminal independently of the respective manufacturers and operators. The present document specifies as well mechanisms in order to expand the generic set of commands and procedures by access technology specific ones. The present document defines: • the commands; • the application protocol; • the mandatory requirements on the ICC and terminal for each procedure. The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the ICC or the terminal are only specified where these reflect over the interface. The present document does not specify any of the security algorithms that may be used.
|
102 223
|
Smart Cards; Card Application Toolkit (CAT) (Release 12)
|
TS
|
12.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102223/12.02.00_60/ts_102223v120200p.pdf
|
The present document defines the interface between the UICC and the terminal, and mandatory terminal procedures, specifically for "NAA Card Application Toolkit". The Card Application Toolkit (CAT) is a set of generic commands and procedures for use by the ICC, irrespective of the access technology of the network. Within the scope of the present document, the UICC refers here to an ICC which supports at least one application in order to access a network. This application is called here Network Access Application (NAA). The ICC is considered as a platform, which is either based on ETSI TS 102 221 [1] or ETSI TS 102 600 [38], here called "3G platform" or ETSI TS 151 011 [8], here called "2G platform". NAA can be: • a USIM application, as defined in ETSI TS 131 102 [6], which can reside only on a 3G platform; • a SIM application, as defined in ETSI TS 151 011 [8], which can reside either on a 3G or a 2G platform; • a TSIM application, as defined in ETSI TS 100 812 [i.2], which can reside only on a 3G platform; • a ISIM application, as defined in ETSI TS 131 103 [36], which can reside only on a 3G platform; • a CSIM application, as defined in 3GPP2 C.S0065-B [53]; • an R-UIM application, as defined in 3GPP2 C.S0023-D [i.4]; or • other applications residing on a 3G platform or a 2G platform. Specifying the interface is to ensure interoperability between an ICC and a terminal independently of the respective manufacturers and operators. The present document specifies as well mechanisms in order to expand the generic set of commands and procedures by access technology specific ones. The present document defines: • the commands; • the application protocol; • the mandatory requirements on the ICC and terminal for each procedure. The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the ICC or the terminal are only specified where these reflect over the interface. The present document does not specify any of the security algorithms that may be used.
|
102 223
|
Smart Cards; Card Application Toolkit (CAT) (Release 11)
|
TS
|
11.3.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102223/11.03.00_60/ts_102223v110300p.pdf
|
The present document defines the interface between the UICC and the terminal, and mandatory terminal procedures, specifically for "NAA Card Application Toolkit". The Card Application Toolkit (CAT) is a set of generic commands and procedures for use by the ICC, irrespective of the access technology of the network. Within the scope of the present document, the UICC refers here to an ICC which supports at least one application in order to access a network. This application is called here Network Access Application (NAA). The ICC is considered as a platform, which is either based on ETSI TS 102 221 [1] or ETSI TS 102 600 [38], here called "3G platform" or ETSI TS 151 011 [8], here called "2G platform". NAA can be: • a USIM application, as defined in ETSI TS 131 102 [6], which can reside only on a 3G platform; • a SIM application, as defined in ETSI TS 151 011 [8], which can reside either on a 3G or a 2G platform; • a TSIM application, as defined in ETSI TS 100 812 [i.2], which can reside only on a 3G platform; • a ISIM application, as defined in ETSI TS 131 103 [36], which can reside only on a 3G platform; • a CSIM application, as defined in 3GPP2 C.S0065-B [53]; • an R-UIM application, as defined in 3GPP2 C.S0023-D [i.4]; or • other applications residing on a 3G platform or a 2G platform. Specifying the interface is to ensure interoperability between an ICC and a terminal independently of the respective manufacturers and operators. The present document specifies as well mechanisms in order to expand the generic set of commands and procedures by access technology specific ones. The present document defines: • the commands; • the application protocol; • the mandatory requirements on the ICC and terminal for each procedure. The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the ICC or the terminal are only specified where these reflect over the interface. The present document does not specify any of the security algorithms that may be used.
|
102 223
|
Smart Cards; Card Application Toolkit (CAT) (Release 10)
|
TS
|
10.6.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102223/10.06.00_60/ts_102223v100600p.pdf
|
The present document defines the interface between the UICC and the terminal, and mandatory terminal procedures, specifically for "NAA Card Application Toolkit". The Card Application Toolkit (CAT) is a set of generic commands and procedures for use by the ICC, irrespective of the access technology of the network. Within the scope of the present document, the UICC refers here to an ICC which supports at least one application in order to access a network. This application is called here Network Access Application (NAA). The ICC is considered as a platform, which is either based on ETSI TS 102 221 [1] or ETSI TS 102 600 [38], here called "3G platform" or ETSI TS 151 011 [8], here called "2G platform". NAA can be: • a USIM application, as defined in ETSI TS 131 102 [6], which can reside only on a 3G platform; • a SIM application, as defined in ETSI TS 151 011 [8], which can reside either on a 3G or a 2G platform; • a TSIM application, as defined in ETSI TS 100 812 [i.2], which can reside only on a 3G platform; • a ISIM application, as defined in ETSI TS 131 103 [36], which can reside only on a 3G platform; • a CSIM application, as defined in 3GPP2 C.S0065-B [53]; • an R-UIM application, as defined in 3GPP2 C.S0023-D [i.4]; or • other applications residing on a 3G platform or a 2G platform. Specifying the interface is to ensure interoperability between an ICC and a terminal independently of the respective manufacturers and operators. The present document specifies as well mechanisms in order to expand the generic set of commands and procedures by access technology specific ones. The present document defines: • the commands; • the application protocol; • the mandatory requirements on the ICC and terminal for each procedure. The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the ICC or the terminal are only specified where these reflect over the interface. The present document does not specify any of the security algorithms that may be used.
|
102 223
|
Smart Cards; Card Application Toolkit (CAT) (Release 9)
|
TS
|
9.4.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102223/09.04.00_60/ts_102223v090400p.pdf
|
The present document defines the interface between the UICC and the terminal, and mandatory terminal procedures, specifically for "NAA Card Application Toolkit". The Card Application Toolkit (CAT) is a set of generic commands and procedures for use by the ICC, irrespective of the access technology of the network. Within the scope of the present document, the UICC refers here to an ICC which supports at least one application in order to access a network. This application is called here Network Access Application (NAA). The ICC is considered as a platform, which is either based on ETSI TS 102 221 [1] or ETSI TS 102 600 [38], here called "3G platform" or ETSI TS 151 011 [8], here called "2G platform". NAA can be: • a USIM application, as defined in ETSI TS 131 102 [6], which can reside only on a 3G platform; • a SIM application, as defined in ETSI TS 151 011 [8], which can reside either on a 3G or a 2G platform; • a TSIM application, as defined in ETSI TS 100 812 [i.2], which can reside only on a 3G platform; • a ISIM application, as defined in ETSI TS 131 103 [36], which can reside only on a 3G platform; • a CSIM application, as defined in 3GPP2 C.S0065-B [53]; • an R-UIM application, as defined in 3GPP2 C.S0023-D [i.4]; or • other applications residing on a 3G platform or a 2G platform. Specifying the interface is to ensure interoperability between an ICC and a terminal independently of the respective manufacturers and operators. The present document specifies as well mechanisms in order to expand the generic set of commands and procedures by access technology specific ones. The present document defines: • the commands; • the application protocol; • the mandatory requirements on the ICC and terminal for each procedure. The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the ICC or the terminal are only specified where these reflect over the interface. The present document does not specify any of the security algorithms that may be used.
|
102 223
|
Smart Cards; Card Application Toolkit (CAT) (Release 8)
|
TS
|
8.8.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102223/08.08.00_60/ts_102223v080800p.pdf
|
The present document defines the interface between the UICC and the terminal, and mandatory terminal procedures, specifically for "NAA Card Application Toolkit". The Card Application Toolkit (CAT) is a set of generic commands and procedures for use by the ICC, irrespective of the access technology of the network. Within the scope of the present document, the UICC refers here to an ICC which supports at least one application in order to access a network. This application is called here Network Access Application (NAA). The ICC is considered as a platform, which is either based on ETSI TS 102 221 [1] or ETSI TS 102 600 [38], here called "3G platform" or ETSI TS 151 011 [8], here called "2G platform". NAA can be: • a USIM application, as defined in ETSI TS 131 102 [6], which can reside only on a 3G platform; • a SIM application, as defined in ETSI TS 151 011 [8], which can reside either on a 3G or a 2G platform; • a TSIM application, as defined in ETSI TS 100 812 [i.2], which can reside only on a 3G platform; • a ISIM application, as defined in ETSI TS 131 103 [36], which can reside only on a 3G platform; • a CSIM application, as defined in 3GPP2 C.S0065-B [53]; • an R-UIM application, as defined in 3GPP2 C.S0023-D [i.4]; or • other applications residing on a 3G platform or a 2G platform. Specifying the interface is to ensure interoperability between an ICC and a terminal independently of the respective manufacturers and operators. The present document specifies as well mechanisms in order to expand the generic set of commands and procedures by access technology specific ones. The present document defines: • the commands; • the application protocol; • the mandatory requirements on the ICC and terminal for each procedure. The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the ICC or the terminal are only specified where these reflect over the interface. The present document does not specify any of the security algorithms that may be used.
|
102 223
|
Smart Cards; Card Application Toolkit (CAT) (Release 7)
|
TS
|
7.17.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102223/07.17.00_60/ts_102223v071700p.pdf
|
The present document defines the interface between the UICC and the terminal, and mandatory terminal procedures, specifically for "NAA Card Application Toolkit". The Card Application Toolkit (CAT) is a set of generic commands and procedures for use by the ICC, irrespective of the access technology of the network. Within the scope of the present document, the UICC refers here to an ICC which supports at least one application in order to access a network. This application is called here Network Access Application (NAA). The ICC is considered as a platform, which is either based on ETSI TS 102 221 [1] or ETSI TS 102 600 [38], here called "3G platform" or ETSI TS 151 011 [8], here called "2G platform". NAA can be: • a USIM application, as defined in ETSI TS 131 102 [6], which can reside only on a 3G platform; • a SIM application, as defined in ETSI TS 151 011 [8], which can reside either on a 3G or a 2G platform; • a TSIM application, as defined in ETSI TS 100 812 [i.2], which can reside only on a 3G platform; • a ISIM application, as defined in ETSI TS 131 103 [36], which can reside only on a 3G platform; • a CSIM application, as defined in 3GPP2 C.S0065-B [53]; • an R-UIM application, as defined in 3GPP2 C.S0023-D [i.4]; or • other applications residing on a 3G platform or a 2G platform. Specifying the interface is to ensure interoperability between an ICC and a terminal independently of the respective manufacturers and operators. The present document specifies as well mechanisms in order to expand the generic set of commands and procedures by access technology specific ones. The present document defines: • the commands; • the application protocol; • the mandatory requirements on the ICC and terminal for each procedure. The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the ICC or the terminal are only specified where these reflect over the interface. The present document does not specify any of the security algorithms that may be used.
|
102 223
|
Smart Cards; Card Application Toolkit (CAT) (Release 6)
|
TS
|
6.14.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102223/06.14.00_60/ts_102223v061400p.pdf
|
The present document defines the interface between the UICC and the terminal, and mandatory terminal procedures, specifically for "NAA Card Application Toolkit". The Card Application Toolkit (CAT) is a set of generic commands and procedures for use by the ICC, irrespective of the access technology of the network. Within the scope of the present document, the UICC refers here to an ICC which supports at least one application in order to access a network. This application is called here Network Access Application (NAA). The ICC is considered as a platform, which is either based on ETSI TS 102 221 [1] or ETSI TS 102 600 [38], here called "3G platform" or ETSI TS 151 011 [8], here called "2G platform". NAA can be: • a USIM application, as defined in ETSI TS 131 102 [6], which can reside only on a 3G platform; • a SIM application, as defined in ETSI TS 151 011 [8], which can reside either on a 3G or a 2G platform; • a TSIM application, as defined in ETSI TS 100 812 [i.2], which can reside only on a 3G platform; • a ISIM application, as defined in ETSI TS 131 103 [36], which can reside only on a 3G platform; • a CSIM application, as defined in 3GPP2 C.S0065-B [53]; • an R-UIM application, as defined in 3GPP2 C.S0023-D [i.4]; or • other applications residing on a 3G platform or a 2G platform. Specifying the interface is to ensure interoperability between an ICC and a terminal independently of the respective manufacturers and operators. The present document specifies as well mechanisms in order to expand the generic set of commands and procedures by access technology specific ones. The present document defines: • the commands; • the application protocol; • the mandatory requirements on the ICC and terminal for each procedure. The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the ICC or the terminal are only specified where these reflect over the interface. The present document does not specify any of the security algorithms that may be used.
|
102 223
|
Smart Cards; Card Application Toolkit (CAT) (Release 5)
|
TS
|
5.11.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102223/05.11.00_60/ts_102223v051100p.pdf
|
The present document defines the interface between the UICC and the terminal, and mandatory terminal procedures, specifically for "NAA Card Application Toolkit". The Card Application Toolkit (CAT) is a set of generic commands and procedures for use by the ICC, irrespective of the access technology of the network. Within the scope of the present document, the UICC refers here to an ICC which supports at least one application in order to access a network. This application is called here Network Access Application (NAA). The ICC is considered as a platform, which is either based on ETSI TS 102 221 [1] or ETSI TS 102 600 [38], here called "3G platform" or ETSI TS 151 011 [8], here called "2G platform". NAA can be: • a USIM application, as defined in ETSI TS 131 102 [6], which can reside only on a 3G platform; • a SIM application, as defined in ETSI TS 151 011 [8], which can reside either on a 3G or a 2G platform; • a TSIM application, as defined in ETSI TS 100 812 [i.2], which can reside only on a 3G platform; • a ISIM application, as defined in ETSI TS 131 103 [36], which can reside only on a 3G platform; • a CSIM application, as defined in 3GPP2 C.S0065-B [53]; • an R-UIM application, as defined in 3GPP2 C.S0023-D [i.4]; or • other applications residing on a 3G platform or a 2G platform. Specifying the interface is to ensure interoperability between an ICC and a terminal independently of the respective manufacturers and operators. The present document specifies as well mechanisms in order to expand the generic set of commands and procedures by access technology specific ones. The present document defines: • the commands; • the application protocol; • the mandatory requirements on the ICC and terminal for each procedure. The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the ICC or the terminal are only specified where these reflect over the interface. The present document does not specify any of the security algorithms that may be used.
|
102 223
|
Smart cards; Card Application Toolkit (CAT) (Release 4)
|
TS
|
4.13.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102223/04.13.00_60/ts_102223v041300p.pdf
|
The present document defines the interface between the UICC and the terminal, and mandatory terminal procedures, specifically for "NAA Card Application Toolkit". The Card Application Toolkit (CAT) is a set of generic commands and procedures for use by the ICC, irrespective of the access technology of the network. Within the scope of the present document, the UICC refers here to an ICC which supports at least one application in order to access a network. This application is called here Network Access Application (NAA). The ICC is considered as a platform, which is either based on ETSI TS 102 221 [1] or ETSI TS 102 600 [38], here called "3G platform" or ETSI TS 151 011 [8], here called "2G platform". NAA can be: • a USIM application, as defined in ETSI TS 131 102 [6], which can reside only on a 3G platform; • a SIM application, as defined in ETSI TS 151 011 [8], which can reside either on a 3G or a 2G platform; • a TSIM application, as defined in ETSI TS 100 812 [i.2], which can reside only on a 3G platform; • a ISIM application, as defined in ETSI TS 131 103 [36], which can reside only on a 3G platform; • a CSIM application, as defined in 3GPP2 C.S0065-B [53]; • an R-UIM application, as defined in 3GPP2 C.S0023-D [i.4]; or • other applications residing on a 3G platform or a 2G platform. Specifying the interface is to ensure interoperability between an ICC and a terminal independently of the respective manufacturers and operators. The present document specifies as well mechanisms in order to expand the generic set of commands and procedures by access technology specific ones. The present document defines: • the commands; • the application protocol; • the mandatory requirements on the ICC and terminal for each procedure. The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the ICC or the terminal are only specified where these reflect over the interface. The present document does not specify any of the security algorithms that may be used.
|
102 222
|
Integrated Circuit Cards (ICC); Administrative commands for telecommunications applications (Release 17)
|
TS
|
17.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102222/17.01.00_60/ts_102222v170100p.pdf
|
The present document defines functions and syntax of a set of administrative commands for a telecommunication card. The commands defined in the present document are compliant to the commands defined in the ISO/IEC 7816 [i.2] series where corresponding commands in ISO/IEC are available. The commands described in the present document are using parts of the functionality of the commands described in the ISO/IEC 7816-3 [i.1]. For a UICC supporting logical secure elements as defined in ETSI TS 102 221 [5], the provisions of the present specification apply to the logical UICC. The present document does not cover the internal implementation within the UICC and/or the external equipment.
|
102 222
|
Integrated Circuit Cards (ICC); Administrative commands for telecommunications applications (Release 16)
|
TS
|
16.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102222/16.00.00_60/ts_102222v160000p.pdf
|
The present document defines functions and syntax of a set of administrative commands for a telecommunication card. The commands defined in the present document are compliant to the commands defined in the ISO/IEC 7816 [i.2] series where corresponding commands in ISO/IEC are available. The commands described in the present document are using parts of the functionality of the commands described in the ISO/IEC 7816-3 [i.1]. For a UICC supporting logical secure elements as defined in ETSI TS 102 221 [5], the provisions of the present specification apply to the logical UICC. The present document does not cover the internal implementation within the UICC and/or the external equipment.
|
102 222
|
Integrated Circuit Cards (ICC); Administrative commands for telecommunications applications (Release 15)
|
TS
|
15.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102222/15.00.00_60/ts_102222v150000p.pdf
|
The present document defines functions and syntax of a set of administrative commands for a telecommunication card. The commands defined in the present document are compliant to the commands defined in the ISO/IEC 7816 [i.2] series where corresponding commands in ISO/IEC are available. The commands described in the present document are using parts of the functionality of the commands described in the ISO/IEC 7816-3 [i.1]. For a UICC supporting logical secure elements as defined in ETSI TS 102 221 [5], the provisions of the present specification apply to the logical UICC. The present document does not cover the internal implementation within the UICC and/or the external equipment.
|
102 222
|
Integrated Circuit Cards (ICC); Administrative commands for telecommunications applications (Release 14)
|
TS
|
14.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102222/14.00.00_60/ts_102222v140000p.pdf
|
The present document defines functions and syntax of a set of administrative commands for a telecommunication card. The commands defined in the present document are compliant to the commands defined in the ISO/IEC 7816 [i.2] series where corresponding commands in ISO/IEC are available. The commands described in the present document are using parts of the functionality of the commands described in the ISO/IEC 7816-3 [i.1]. For a UICC supporting logical secure elements as defined in ETSI TS 102 221 [5], the provisions of the present specification apply to the logical UICC. The present document does not cover the internal implementation within the UICC and/or the external equipment.
|
102 222
|
Integrated Circuit Cards (ICC); Administrative commands for telecommunications applications (Release 13)
|
TS
|
13.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102222/13.00.00_60/ts_102222v130000p.pdf
|
The present document defines functions and syntax of a set of administrative commands for a telecommunication card. The commands defined in the present document are compliant to the commands defined in the ISO/IEC 7816 [i.2] series where corresponding commands in ISO/IEC are available. The commands described in the present document are using parts of the functionality of the commands described in the ISO/IEC 7816-3 [i.1]. For a UICC supporting logical secure elements as defined in ETSI TS 102 221 [5], the provisions of the present specification apply to the logical UICC. The present document does not cover the internal implementation within the UICC and/or the external equipment.
|
102 222
|
Integrated Circuit Cards (ICC); Administrative commands for telecommunications applications (Release 12)
|
TS
|
12.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102222/12.00.00_60/ts_102222v120000p.pdf
|
The present document defines functions and syntax of a set of administrative commands for a telecommunication card. The commands defined in the present document are compliant to the commands defined in the ISO/IEC 7816 [i.2] series where corresponding commands in ISO/IEC are available. The commands described in the present document are using parts of the functionality of the commands described in the ISO/IEC 7816-3 [i.1]. For a UICC supporting logical secure elements as defined in ETSI TS 102 221 [5], the provisions of the present specification apply to the logical UICC. The present document does not cover the internal implementation within the UICC and/or the external equipment.
|
102 222
|
Integrated Circuit Cards (ICC); Administrative commands for telecommunications applications (Release 11)
|
TS
|
11.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102222/11.00.00_60/ts_102222v110000p.pdf
|
The present document defines functions and syntax of a set of administrative commands for a telecommunication card. The commands defined in the present document are compliant to the commands defined in the ISO/IEC 7816 [i.2] series where corresponding commands in ISO/IEC are available. The commands described in the present document are using parts of the functionality of the commands described in the ISO/IEC 7816-3 [i.1]. For a UICC supporting logical secure elements as defined in ETSI TS 102 221 [5], the provisions of the present specification apply to the logical UICC. The present document does not cover the internal implementation within the UICC and/or the external equipment.
|
102 222
|
Integrated Circuit Cards (ICC); Administrative commands for telecommunications applications (Release 10)
|
TS
|
10.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102222/10.00.00_60/ts_102222v100000p.pdf
|
The present document defines functions and syntax of a set of administrative commands for a telecommunication card. The commands defined in the present document are compliant to the commands defined in the ISO/IEC 7816 [i.2] series where corresponding commands in ISO/IEC are available. The commands described in the present document are using parts of the functionality of the commands described in the ISO/IEC 7816-3 [i.1]. For a UICC supporting logical secure elements as defined in ETSI TS 102 221 [5], the provisions of the present specification apply to the logical UICC. The present document does not cover the internal implementation within the UICC and/or the external equipment.
|
102 222
|
Integrated Circuit Cards (ICC); Administrative commands for telecommunications applications (Release 9)
|
TS
|
9.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102222/09.00.00_60/ts_102222v090000p.pdf
|
The present document defines functions and syntax of a set of administrative commands for a telecommunication card. The commands defined in the present document are compliant to the commands defined in the ISO/IEC 7816 [i.2] series where corresponding commands in ISO/IEC are available. The commands described in the present document are using parts of the functionality of the commands described in the ISO/IEC 7816-3 [i.1]. For a UICC supporting logical secure elements as defined in ETSI TS 102 221 [5], the provisions of the present specification apply to the logical UICC. The present document does not cover the internal implementation within the UICC and/or the external equipment.
|
102 222
|
Integrated Circuit Cards (ICC); Administrative commands for telecommunications applications (Release 8)
|
TS
|
8.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102222/08.00.00_60/ts_102222v080000p.pdf
|
The present document defines functions and syntax of a set of administrative commands for a telecommunication card. The commands defined in the present document are compliant to the commands defined in the ISO/IEC 7816 [i.2] series where corresponding commands in ISO/IEC are available. The commands described in the present document are using parts of the functionality of the commands described in the ISO/IEC 7816-3 [i.1]. For a UICC supporting logical secure elements as defined in ETSI TS 102 221 [5], the provisions of the present specification apply to the logical UICC. The present document does not cover the internal implementation within the UICC and/or the external equipment.
|
102 222
|
Integrated Circuit Cards (ICC); Administrative commands for telecommunications applications (Release 7)
|
TS
|
7.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102222/07.01.00_60/ts_102222v070100p.pdf
|
The present document defines functions and syntax of a set of administrative commands for a telecommunication card. The commands defined in the present document are compliant to the commands defined in the ISO/IEC 7816 [i.2] series where corresponding commands in ISO/IEC are available. The commands described in the present document are using parts of the functionality of the commands described in the ISO/IEC 7816-3 [i.1]. For a UICC supporting logical secure elements as defined in ETSI TS 102 221 [5], the provisions of the present specification apply to the logical UICC. The present document does not cover the internal implementation within the UICC and/or the external equipment.
|
102 222
|
Integrated Circuit Cards (ICC); Administrative commands for telecommunications applications (Release 6)
|
TS
|
6.11.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102222/06.11.00_60/ts_102222v061100p.pdf
|
The present document defines functions and syntax of a set of administrative commands for a telecommunication card. The commands defined in the present document are compliant to the commands defined in the ISO/IEC 7816 [i.2] series where corresponding commands in ISO/IEC are available. The commands described in the present document are using parts of the functionality of the commands described in the ISO/IEC 7816-3 [i.1]. For a UICC supporting logical secure elements as defined in ETSI TS 102 221 [5], the provisions of the present specification apply to the logical UICC. The present document does not cover the internal implementation within the UICC and/or the external equipment.
|
102 222
|
Integrated Circuit Cards (ICC); Administrative commands for telecommunications applications (Release 5)
|
TS
|
5.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102222/05.02.00_60/ts_102222v050200p.pdf
|
The present document defines functions and syntax of a set of administrative commands for a telecommunication card. The commands defined in the present document are compliant to the commands defined in the ISO/IEC 7816 [i.2] series where corresponding commands in ISO/IEC are available. The commands described in the present document are using parts of the functionality of the commands described in the ISO/IEC 7816-3 [i.1]. For a UICC supporting logical secure elements as defined in ETSI TS 102 221 [5], the provisions of the present specification apply to the logical UICC. The present document does not cover the internal implementation within the UICC and/or the external equipment.
|
102 222
|
Integrated Circuit Cards (ICC); Administrative commands for telecommunications applications (Release 4)
|
TS
|
4.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102222/04.02.00_60/ts_102222v040200p.pdf
|
The present document defines functions and syntax of a set of administrative commands for a telecommunication card. The commands defined in the present document are compliant to the commands defined in the ISO/IEC 7816 [i.2] series where corresponding commands in ISO/IEC are available. The commands described in the present document are using parts of the functionality of the commands described in the ISO/IEC 7816-3 [i.1]. For a UICC supporting logical secure elements as defined in ETSI TS 102 221 [5], the provisions of the present specification apply to the logical UICC. The present document does not cover the internal implementation within the UICC and/or the external equipment.
|
102 222
|
Integrated Circuit Cards (ICC); Administrative commands for telecommunications applications (Release 1999)
|
TS
|
3.7.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102222/03.07.00_60/ts_102222v030700p.pdf
|
The present document defines functions and syntax of a set of administrative commands for a telecommunication card. The commands defined in the present document are compliant to the commands defined in the ISO/IEC 7816 [i.2] series where corresponding commands in ISO/IEC are available. The commands described in the present document are using parts of the functionality of the commands described in the ISO/IEC 7816-3 [i.1]. For a UICC supporting logical secure elements as defined in ETSI TS 102 221 [5], the provisions of the present specification apply to the logical UICC. The present document does not cover the internal implementation within the UICC and/or the external equipment.
|
102 221
|
Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release 18)
|
TS
|
18.3.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102221/18.03.00_60/ts_102221v180300p.pdf
|
The present document specifies the interface between the UICC and the terminal. The present document specifies: • the requirements for the physical characteristics of the UICC; • the electrical interface for exchanging APDUs between the UICC and the terminal, based on ISO/IEC 7816-3 [11]; • the initial communication establishment and the transport protocols for this interface; • a model which serves as a basis for the logical structure of the UICC APDU interface; • communication commands and procedures for the UICC APDU interface; • application independent files and protocols for the UICC APDU interface. Starting from Release 17, the UICC may support Logical Secure Element interfaces, which allows it to host multiple logical secure elements. A special form of such a Logical Secure Element (LSE) is a logical UICC. Where required, the lower layers which represent the features common to all LSEs are denoted as LSE base. The applicability of the clauses in the present document to either the LSE base or to the logical UICC is given in the introduction of each affected clause. The administrative procedures, initial card management and optional communication interfaces between the UICC and terminal are not within the scope of the present document.
|
102 221
|
Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release 17)
|
TS
|
17.4.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102221/17.04.00_60/ts_102221v170400p.pdf
|
The present document specifies the interface between the UICC and the terminal. The present document specifies: • the requirements for the physical characteristics of the UICC; • the electrical interface for exchanging APDUs between the UICC and the terminal, based on ISO/IEC 7816-3 [11]; • the initial communication establishment and the transport protocols for this interface; • a model which serves as a basis for the logical structure of the UICC APDU interface; • communication commands and procedures for the UICC APDU interface; • application independent files and protocols for the UICC APDU interface. Starting from Release 17, the UICC may support Logical Secure Element interfaces, which allows it to host multiple logical secure elements. A special form of such a Logical Secure Element (LSE) is a logical UICC. Where required, the lower layers which represent the features common to all LSEs are denoted as LSE base. The applicability of the clauses in the present document to either the LSE base or to the logical UICC is given in the introduction of each affected clause. The administrative procedures, initial card management and optional communication interfaces between the UICC and terminal are not within the scope of the present document.
|
102 221
|
Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release 16)
|
TS
|
16.6.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102221/16.06.00_60/ts_102221v160600p.pdf
|
The present document specifies the interface between the UICC and the terminal. The present document specifies: • the requirements for the physical characteristics of the UICC; • the electrical interface for exchanging APDUs between the UICC and the terminal, based on ISO/IEC 7816-3 [11]; • the initial communication establishment and the transport protocols for this interface; • a model which serves as a basis for the logical structure of the UICC APDU interface; • communication commands and procedures for the UICC APDU interface; • application independent files and protocols for the UICC APDU interface. Starting from Release 17, the UICC may support Logical Secure Element interfaces, which allows it to host multiple logical secure elements. A special form of such a Logical Secure Element (LSE) is a logical UICC. Where required, the lower layers which represent the features common to all LSEs are denoted as LSE base. The applicability of the clauses in the present document to either the LSE base or to the logical UICC is given in the introduction of each affected clause. The administrative procedures, initial card management and optional communication interfaces between the UICC and terminal are not within the scope of the present document.
|
102 221
|
Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release 15)
|
TS
|
15.5.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102221/15.05.00_60/ts_102221v150500p.pdf
|
The present document specifies the interface between the UICC and the terminal. The present document specifies: • the requirements for the physical characteristics of the UICC; • the electrical interface for exchanging APDUs between the UICC and the terminal, based on ISO/IEC 7816-3 [11]; • the initial communication establishment and the transport protocols for this interface; • a model which serves as a basis for the logical structure of the UICC APDU interface; • communication commands and procedures for the UICC APDU interface; • application independent files and protocols for the UICC APDU interface. Starting from Release 17, the UICC may support Logical Secure Element interfaces, which allows it to host multiple logical secure elements. A special form of such a Logical Secure Element (LSE) is a logical UICC. Where required, the lower layers which represent the features common to all LSEs are denoted as LSE base. The applicability of the clauses in the present document to either the LSE base or to the logical UICC is given in the introduction of each affected clause. The administrative procedures, initial card management and optional communication interfaces between the UICC and terminal are not within the scope of the present document.
|
102 221
|
Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release 14)
|
TS
|
14.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102221/14.02.00_60/ts_102221v140200p.pdf
|
The present document specifies the interface between the UICC and the terminal. The present document specifies: • the requirements for the physical characteristics of the UICC; • the electrical interface for exchanging APDUs between the UICC and the terminal, based on ISO/IEC 7816-3 [11]; • the initial communication establishment and the transport protocols for this interface; • a model which serves as a basis for the logical structure of the UICC APDU interface; • communication commands and procedures for the UICC APDU interface; • application independent files and protocols for the UICC APDU interface. Starting from Release 17, the UICC may support Logical Secure Element interfaces, which allows it to host multiple logical secure elements. A special form of such a Logical Secure Element (LSE) is a logical UICC. Where required, the lower layers which represent the features common to all LSEs are denoted as LSE base. The applicability of the clauses in the present document to either the LSE base or to the logical UICC is given in the introduction of each affected clause. The administrative procedures, initial card management and optional communication interfaces between the UICC and terminal are not within the scope of the present document.
|
102 221
|
Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release 13)
|
TS
|
13.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102221/13.02.00_60/ts_102221v130200p.pdf
|
The present document specifies the interface between the UICC and the terminal. The present document specifies: • the requirements for the physical characteristics of the UICC; • the electrical interface for exchanging APDUs between the UICC and the terminal, based on ISO/IEC 7816-3 [11]; • the initial communication establishment and the transport protocols for this interface; • a model which serves as a basis for the logical structure of the UICC APDU interface; • communication commands and procedures for the UICC APDU interface; • application independent files and protocols for the UICC APDU interface. Starting from Release 17, the UICC may support Logical Secure Element interfaces, which allows it to host multiple logical secure elements. A special form of such a Logical Secure Element (LSE) is a logical UICC. Where required, the lower layers which represent the features common to all LSEs are denoted as LSE base. The applicability of the clauses in the present document to either the LSE base or to the logical UICC is given in the introduction of each affected clause. The administrative procedures, initial card management and optional communication interfaces between the UICC and terminal are not within the scope of the present document.
|
102 221
|
Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release 11)
|
TS
|
11.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102221/11.01.00_60/ts_102221v110100p.pdf
|
The present document specifies the interface between the UICC and the terminal. The present document specifies: • the requirements for the physical characteristics of the UICC; • the electrical interface for exchanging APDUs between the UICC and the terminal, based on ISO/IEC 7816-3 [11]; • the initial communication establishment and the transport protocols for this interface; • a model which serves as a basis for the logical structure of the UICC APDU interface; • communication commands and procedures for the UICC APDU interface; • application independent files and protocols for the UICC APDU interface. Starting from Release 17, the UICC may support Logical Secure Element interfaces, which allows it to host multiple logical secure elements. A special form of such a Logical Secure Element (LSE) is a logical UICC. Where required, the lower layers which represent the features common to all LSEs are denoted as LSE base. The applicability of the clauses in the present document to either the LSE base or to the logical UICC is given in the introduction of each affected clause. The administrative procedures, initial card management and optional communication interfaces between the UICC and terminal are not within the scope of the present document.
|
102 221
|
Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release 12)
|
TS
|
12.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102221/12.01.00_60/ts_102221v120100p.pdf
|
The present document specifies the interface between the UICC and the terminal. The present document specifies: • the requirements for the physical characteristics of the UICC; • the electrical interface for exchanging APDUs between the UICC and the terminal, based on ISO/IEC 7816-3 [11]; • the initial communication establishment and the transport protocols for this interface; • a model which serves as a basis for the logical structure of the UICC APDU interface; • communication commands and procedures for the UICC APDU interface; • application independent files and protocols for the UICC APDU interface. Starting from Release 17, the UICC may support Logical Secure Element interfaces, which allows it to host multiple logical secure elements. A special form of such a Logical Secure Element (LSE) is a logical UICC. Where required, the lower layers which represent the features common to all LSEs are denoted as LSE base. The applicability of the clauses in the present document to either the LSE base or to the logical UICC is given in the introduction of each affected clause. The administrative procedures, initial card management and optional communication interfaces between the UICC and terminal are not within the scope of the present document.
|
102 221
|
Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release 9)
|
TS
|
9.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102221/09.02.00_60/ts_102221v090200p.pdf
|
The present document specifies the interface between the UICC and the terminal. The present document specifies: • the requirements for the physical characteristics of the UICC; • the electrical interface for exchanging APDUs between the UICC and the terminal, based on ISO/IEC 7816-3 [11]; • the initial communication establishment and the transport protocols for this interface; • a model which serves as a basis for the logical structure of the UICC APDU interface; • communication commands and procedures for the UICC APDU interface; • application independent files and protocols for the UICC APDU interface. Starting from Release 17, the UICC may support Logical Secure Element interfaces, which allows it to host multiple logical secure elements. A special form of such a Logical Secure Element (LSE) is a logical UICC. Where required, the lower layers which represent the features common to all LSEs are denoted as LSE base. The applicability of the clauses in the present document to either the LSE base or to the logical UICC is given in the introduction of each affected clause. The administrative procedures, initial card management and optional communication interfaces between the UICC and terminal are not within the scope of the present document.
|
102 221
|
Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release 10)
|
TS
|
10.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102221/10.00.00_60/ts_102221v100000p.pdf
|
The present document specifies the interface between the UICC and the terminal. The present document specifies: • the requirements for the physical characteristics of the UICC; • the electrical interface for exchanging APDUs between the UICC and the terminal, based on ISO/IEC 7816-3 [11]; • the initial communication establishment and the transport protocols for this interface; • a model which serves as a basis for the logical structure of the UICC APDU interface; • communication commands and procedures for the UICC APDU interface; • application independent files and protocols for the UICC APDU interface. Starting from Release 17, the UICC may support Logical Secure Element interfaces, which allows it to host multiple logical secure elements. A special form of such a Logical Secure Element (LSE) is a logical UICC. Where required, the lower layers which represent the features common to all LSEs are denoted as LSE base. The applicability of the clauses in the present document to either the LSE base or to the logical UICC is given in the introduction of each affected clause. The administrative procedures, initial card management and optional communication interfaces between the UICC and terminal are not within the scope of the present document.
|
102 221
|
Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release 7)
|
TS
|
7.18.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102221/07.18.00_60/ts_102221v071800p.pdf
|
The present document specifies the interface between the UICC and the terminal. The present document specifies: • the requirements for the physical characteristics of the UICC; • the electrical interface for exchanging APDUs between the UICC and the terminal, based on ISO/IEC 7816-3 [11]; • the initial communication establishment and the transport protocols for this interface; • a model which serves as a basis for the logical structure of the UICC APDU interface; • communication commands and procedures for the UICC APDU interface; • application independent files and protocols for the UICC APDU interface. Starting from Release 17, the UICC may support Logical Secure Element interfaces, which allows it to host multiple logical secure elements. A special form of such a Logical Secure Element (LSE) is a logical UICC. Where required, the lower layers which represent the features common to all LSEs are denoted as LSE base. The applicability of the clauses in the present document to either the LSE base or to the logical UICC is given in the introduction of each affected clause. The administrative procedures, initial card management and optional communication interfaces between the UICC and terminal are not within the scope of the present document.
|
102 221
|
Smart cards; UICC-Terminal interface; Physical and logical characteristics (Release 5)
|
TS
|
5.10.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102221/05.10.00_60/ts_102221v051000p.pdf
|
The present document specifies the interface between the UICC and the terminal. The present document specifies: • the requirements for the physical characteristics of the UICC; • the electrical interface for exchanging APDUs between the UICC and the terminal, based on ISO/IEC 7816-3 [11]; • the initial communication establishment and the transport protocols for this interface; • a model which serves as a basis for the logical structure of the UICC APDU interface; • communication commands and procedures for the UICC APDU interface; • application independent files and protocols for the UICC APDU interface. Starting from Release 17, the UICC may support Logical Secure Element interfaces, which allows it to host multiple logical secure elements. A special form of such a Logical Secure Element (LSE) is a logical UICC. Where required, the lower layers which represent the features common to all LSEs are denoted as LSE base. The applicability of the clauses in the present document to either the LSE base or to the logical UICC is given in the introduction of each affected clause. The administrative procedures, initial card management and optional communication interfaces between the UICC and terminal are not within the scope of the present document.
|
102 221
|
Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release 8)
|
TS
|
8.5.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102221/08.05.00_60/ts_102221v080500p.pdf
|
The present document specifies the interface between the UICC and the terminal. The present document specifies: • the requirements for the physical characteristics of the UICC; • the electrical interface for exchanging APDUs between the UICC and the terminal, based on ISO/IEC 7816-3 [11]; • the initial communication establishment and the transport protocols for this interface; • a model which serves as a basis for the logical structure of the UICC APDU interface; • communication commands and procedures for the UICC APDU interface; • application independent files and protocols for the UICC APDU interface. Starting from Release 17, the UICC may support Logical Secure Element interfaces, which allows it to host multiple logical secure elements. A special form of such a Logical Secure Element (LSE) is a logical UICC. Where required, the lower layers which represent the features common to all LSEs are denoted as LSE base. The applicability of the clauses in the present document to either the LSE base or to the logical UICC is given in the introduction of each affected clause. The administrative procedures, initial card management and optional communication interfaces between the UICC and terminal are not within the scope of the present document.
|
102 220
|
Access and Terminals (AT); Technical Specification: Delivery of Cable based services across a home access to the devices in the home
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102220/01.01.01_60/ts_102220v010101p.pdf
|
The present document describes the technology interface requirements that all appropriate home-networking technologies can use for access to the cable network. The present document spans the description of service data types, requirements for system performance, QoS support, network-based management and local network management. It addresses networks that are installed in residences and used for the transport of information encoded in a digital format. The main emphasis is on IP-based networks. However, some aspects also apply to the primary distribution of digital media (digital video and audio information) over cable networks.
|
102 219
|
Methods for Testing and Specification (MTS); The IDL to TTCN-3 Mapping
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102219/01.01.01_60/ts_102219v010101p.pdf
|
The present document defines the mapping rules for CORBA IDL (as defined in chapter 3 in [4]) to TTCN-3 (as defined in ES 201 873-1 [1]) to enable testing of CORBA-based systems. The principles of mapping CORBA IDL to TTCN-3 can be also used for the mapping of interface specification languages of other object-/component-based technologies. The specification of other mappings is outside the scope of the present document.
|
102 221
|
Smart cards; UICC-Terminal interface; Physical and logical characteristics (Release 1999)
|
TS
|
3.18.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102221/03.18.00_60/ts_102221v031800p.pdf
|
The present document specifies the interface between the UICC and the terminal. The present document specifies: • the requirements for the physical characteristics of the UICC; • the electrical interface for exchanging APDUs between the UICC and the terminal, based on ISO/IEC 7816-3 [11]; • the initial communication establishment and the transport protocols for this interface; • a model which serves as a basis for the logical structure of the UICC APDU interface; • communication commands and procedures for the UICC APDU interface; • application independent files and protocols for the UICC APDU interface. Starting from Release 17, the UICC may support Logical Secure Element interfaces, which allows it to host multiple logical secure elements. A special form of such a Logical Secure Element (LSE) is a logical UICC. Where required, the lower layers which represent the features common to all LSEs are denoted as LSE base. The applicability of the clauses in the present document to either the LSE base or to the logical UICC is given in the introduction of each affected clause. The administrative procedures, initial card management and optional communication interfaces between the UICC and terminal are not within the scope of the present document.
|
102 221
|
Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release 6)
|
TS
|
6.16.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102221/06.16.00_60/ts_102221v061600p.pdf
|
The present document specifies the interface between the UICC and the terminal. The present document specifies: • the requirements for the physical characteristics of the UICC; • the electrical interface for exchanging APDUs between the UICC and the terminal, based on ISO/IEC 7816-3 [11]; • the initial communication establishment and the transport protocols for this interface; • a model which serves as a basis for the logical structure of the UICC APDU interface; • communication commands and procedures for the UICC APDU interface; • application independent files and protocols for the UICC APDU interface. Starting from Release 17, the UICC may support Logical Secure Element interfaces, which allows it to host multiple logical secure elements. A special form of such a Logical Secure Element (LSE) is a logical UICC. Where required, the lower layers which represent the features common to all LSEs are denoted as LSE base. The applicability of the clauses in the present document to either the LSE base or to the logical UICC is given in the introduction of each affected clause. The administrative procedures, initial card management and optional communication interfaces between the UICC and terminal are not within the scope of the present document.
|
102 207
|
Mobile Commerce (M-COMM); Mobile Signature Service; Specifications for Roaming in Mobile Signature Services
|
TS
|
1.1.3
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102207/01.01.03_60/ts_102207v010103p.pdf
|
Basically, an Application Provider should be able to get a Mobile Signature from any enduser, even if the Application Provider and the enduser have not contracted a commercial relationship with the same Mobile Signature Service Provider. Otherwise, an Application Provider would have to build commercial terms with as many MSSPs as possible, and this might be a cost burden. This means that a Mobile Signature transaction issued by an Application Provider should be able to reach the appropriate Mobile Signature Service Provider, and this should be transparent for the Application Provider and the enduser. This is the concept of Mobile Signature Roaming. The present document specifies technical interfaces over SOAP and HTTP for architectures that facilitate the roaming of mobile signature messages between the enduser and an Application Provider, and facilitate the building of an open model. These standardized interfaces must allow: • many-to-many relationships between stakeholders, relying parties and customers; • both centralized or decentralized approach so that endusers and Application Providers are able to establish multiple trusted relationships; • a minimized number of intermediaries between an enduser and an Application Provider; • a common understanding between the Mobile Signature Service Provider and the Application Provider of the security involved in a mobile signature process; • keep track of the path taken by the roaming transaction; • a dispute resolution policy between Application Provider, Enduser, Home MSSP, Acquiring Entity and all the intermediaries involved in the roaming of the transaction.
|
102 204
|
Mobile Commerce (M-COMM); Mobile Signature Service; Web Service Interface
|
TS
|
1.1.4
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102204/01.01.04_60/ts_102204v010104p.pdf
|
The present document specifies the Mobile Signature Service as a Web Service: MOBILE SIGNATURE WEB SERVICE. From the business and functional requirements of TR 102 203 [12], the present document identifies the methods that must be provided by a Mobile Signature Web Service Provider. The present document specifies the data structures and messaging models related to these methods thanks to XML Schema and WSDL. Documentations about these technologies can be found in clause 2. The complete MSS XML Schema is provided in Annex A. A SOAP 1.2 binding is proposed as the mandatory protocol binding. The corresponding WSDL 1.1 description document of such a web service is specified. In defining the Web service, the present document makes reference to interactions between different parties and to the end user experience of a mobile signature service at the mobile device. This is done to illustrate concepts and facilitate definition of the Web service - only. Readers are referred to other sources of information as indicated in clause 2 regarding definitions and specifications for these topics. Structure of the present document: • Scope: a description of the goals and objectives of the present document. • Document Administration: an explanation of the structure, definitions, symbols and abbreviations used in the present document. • Introduction to mobile signature: positions the Mobile Signature project and EC funding etc leading to overview of why mobile signature has a way to accelerate deployment of electronic signatures as originally envisaged by the EU Directive. • Mobile Signature Service Functions: this section describes the high-level functionalities provided by a Mobile Signature Service Provider. • Mobile Signature Web Service: the Mobile Signature Service is specified as a Web Service in this section. • Message Formats: the XML messages exchanged between an Application Provider and a Mobile Signature Service Provider are presented. • Auxiliary XML Data Types: the messages presented in the previous chapter are based upon the XML data types specified here. • Communication Protocol Binding: the protocol binding for the Mobile Signature Service is specified as SOAP 1.2 over HTTP. • Web Service - Security and Privacy Considerations: Security and Privacy considerations with respect to the Mobile Signature Service are presented. ETSI ETSI TS 102 204 V1.1.4 (2003-08) 8
|
102 209
|
Telecommunications and Internet converged Services and Protocols for Advancing Networks (TISPAN); Telecommunication Equipment Identification
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102209/01.02.01_60/ts_102209v010201p.pdf
|
The present document provides the information for the identification of telecommunication equipment. The present document focuses on both manufacturers and PNOs' needs when exchanging information. This information can be used either externally or internally. Based on an analysis of the results of a survey TR 102 214 [2], the present document identifies the data elements which are considered to be necessary and sufficient to identify equipment. In addition to that, the present document provides associated information which is found useful to be exchanged between manufacturers and PNOs. The format of the Equipment Identity is out of scope of the present document.
|
102 192-2
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); International Technical Characteristics and Test Methods; Part 2: Cordless audio and Consumer radio microphones in the 25 MHz to 3 GHz Frequency Range
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/10219202/01.01.01_60/ts_10219202v010101p.pdf
|
The present document covers the minimum characteristics considered necessary in order to make the best use of the available frequencies. It does not necessarily include all the characteristics that may be required by a user, nor does it necessarily represent the optimum performance achievable. The present document applies to cordless audio and in ear monitoring equipment using either 300 kHz bandwidth analogue modulation or 300 kHz, 600 kHz or 1 200 kHz digital modulation. The frequency bands for this equipment may differ from country to country as specified in their national regulations. All equipment is intended to be used with integral antennas. The present document does not apply to broadband modulation such as spread spectrum techniques. Consumer audio equipment intended for audio and voice operating below 50 MHz and using narrow band modulation are excluded from the present document. Electromagnetic Compatibility (EMC) requirements are covered by the present document in annex A. The types of equipment covered by the present document are examples as follows: - cordless headphones; - cordless loudspeakers; - consumer radio microphones; - in-ear monitoring; - in-vehicle cordless; - personal cordless; - broadband multi channel audio systems.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.