id
stringlengths 7
13
| title
stringlengths 7
396
| type
stringclasses 2
values | version
stringclasses 245
values | url
stringlengths 90
98
| scope
stringlengths 0
83.8k
|
|---|---|---|---|---|---|
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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 210
|
Broadband Radio Access Networks (BRAN); HIPERMAN; System profiles
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102210/01.02.01_60/ts_102210v010201p.pdf
|
The present document specifies the HiperMAN system profiles. System profiles provide recommended implementations of HiperMAN compliant systems. Compliance with the HiperMAN specification does not require compliance with 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 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 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 221
|
<empty>
|
TS
|
18.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102221/18.02.00_60/ts_102221v180200p.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 4)
|
TS
|
4.16.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102221/04.16.00_60/ts_102221v041600p.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
|
<empty>
|
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 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 207
|
<empty>
|
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
|
<empty>
|
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 178
|
Broadband Radio Access Networks (BRAN); HiperMAN; Data Link Control (DLC) layer
|
TS
|
1.5.1
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/102178/01.05.01_60/ts_102178v010501p.pdf
|
The present document defines the Data Link Control (DLC) of HiperMAN to support PMP and optionally Mesh network topologies. The present document provides the DLC functions required for Fixed applications, in frequencies below 11 GHz, and Nomadic and converged Fixed-Nomadic applications, in frequencies below 6 GHz.
|
102 177
|
Broadband Radio Access Networks (BRAN); HiperMAN; Physical (PHY) layer
|
TS
|
1.5.1
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/102177/01.05.01_60/ts_102177v010501p.pdf
|
The present document specifies the HiperMAN air interface with the specification layer 1 (physical layer), which can be used to provide Fixed applications, in frequencies below 11 GHz, and Nomadic and converged Fixed-Nomadic applications, in frequencies below 6 GHz. The present document follows the ISO-OSI model. HiperMAN is confined only to the radio subsystems consisting of the Physical (PHY) layer and the DLC layer - which are both core network independent - and the core network specific convergence sub-layer. For managing radio resources and connection control, the Data Link Control (DLC) protocol is applied, which uses the transmission services of the DLC layer. Convergence layers above the DLC layer handle the inter-working with layers at the top of the radio sub-system. The scope of the present document is as follows: • It gives a description of the physical layer for HiperMAN systems. • It specifies the transmission scheme in order to allow interoperability between equipment developed by different manufacturers. This is achieved by describing scrambling, channel coding, modulation, framing, control mechanisms, and power control to assist in radio resource management. • It does cover the receiver and transmitter performance requirements which are specific for HiperMAN systems. • Some information clauses and annexes describe parameters and system models to assist in preparing conformance, interoperability and coexistence specifications.
|
102 190
|
Near Field Communication (NFC) IP-1; Interface and Protocol (NFCIP-1)
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/102190/01.01.01_60/ts_102190v010101p.pdf
|
The present document defines communication modes for Near Field Communication Interface and Protocol (NFCIP-1) using inductive coupled devices operating at the centre frequency of 13,56 MHz for interconnection of computer peripherals. It also defines both the Active and the Passive communication modes of Near Field Communication Interface and Protocol (NFCIP-1) to realize a communication network using Near Field Communication devices for networked products and also for consumer equipment. The present document specifies, in particular, modulation schemes, codings, transfer speeds, and frame format of the RF interface, as well as initialization schemes and conditions required for data collision control during initialization. Furthermore, the present document defines a transport protocol including protocol activation and data exchange methods. Information interchange between systems also requires, at a minimum, agreement between the interchange parties upon the interchange codes and the data structure.
|
102 188-3
|
Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A) air interface; Physical layer specification; Part 3: Channel coding
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/10218803/01.01.02_60/ts_10218803v010102p.pdf
|
The present document defines the channel coding structure used within the SES BSM Regenerative Satellite Mesh - A (RSM-A) air interface family. It includes code block, scrambling, outer forward error correction encoding, interleaving, and inner forward error correction encoding process definition.
|
102 188-2
|
Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A) air interface; Physical layer specification; Part 2: Frame structure
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/10218802/01.01.02_60/ts_10218802v010102p.pdf
|
The present document defines the frame structure used within the SES BSM Regenerative Satellite Mesh - A (RSM-A) air interface family. It includes frame, time slot, and burst structure definition.
|
102 188-1
|
Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A) air interface; Physical layer specification; Part 1: General description
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/10218801/01.01.02_60/ts_10218801v010102p.pdf
|
The present document is an introduction to the physical layer specification for the SES BSM Regenerative Satellite Mesh - A (RSM-A) air interface family. It consists of a general description of the organization of the physical layer with reference to the parts of this multi-part deliverable where each function is specified in more detail.
|
102 182
|
Emergency Communications (EMTEL); Requirements for communications from authorities/organizations to individuals, groups or the general public during emergencies
|
TS
|
1.5.1
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/102182/01.05.01_60/ts_102182v010501p.pdf
|
The present document gives an overview of the requirements for communication from authorities/organizations to citizens in all types of emergencies. It collects operational and organizational requirements as a basis for a common notification service, including targeting of the area to be notified. Although many of the requirements relate to national public policies and regulation, there are a number of service and technical aspects which are better dealt with on the European level to ensure harmonized access and services over Europe and service effectiveness through increased user awareness by using standardized solutions. The present document also collects already established requirements for notification and gives guidance on how to find the standardization work published or ongoing. The document identifies the areas needing particular attention from the experts and refers to identified documents in preparation in SDOs. The present document is a collection of technical requirements and recommendations. The present document is applicable to ETSI technical bodies for defining of services and specifying technical solutions. It is clear that the present document will not present a solution for every scenario.
|
102 181
|
Emergency Communications (EMTEL); Requirements for communication between authorities/organizations during emergencies
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/102181/01.03.01_60/ts_102181v010301p.pdf
|
The present document addresses the requirements for communications between the authorized representatives who can be involved in the responses and actions when handling an emergency. It describes the functional requirements for communications between the authorized representatives involved in the responses and actions when handling an emergency. The level of precision has been chosen to avoid interaction with the specific local, regional or national organizations and diagrams of relations between authorized representatives. It follows from this that adaptations will have to be done when implementing the present document at a local level. Furthermore, the scope of the present document also encompasses various types of services that can bring an added value to this basic scenario or add new scenarios, such as the services brought by other technologies e.g. IoT devices that support communications between authorities during emergencies.
|
102 188-5
|
Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A) air interface; Physical layer specification; Part 5: Radio transmission and reception
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/10218805/01.01.02_60/ts_10218805v010102p.pdf
|
The present document defines the Radio Frequency (RF) requirements for the Satellite Terminal (ST) transceiver of the Regenerative Satellite Mesh - A (RSM-A); Air interface operating in the Fixed Satellite System (FSS) allocations at Ka-band as follows: • ST reception is in the Fixed Satellite Service (FSS) frequency ranges from 17,70 GHz to 19,70 GHz and from 19,70 GHz to 20,20 GHz; • ST transmission is in the frequency ranges allocated to FSS from 27,50 GHz to 29,50 GHz and from 29,50 GHz to 30,00 GHz. Requirements are defined for two categories of parameters: • those that are required to provide compatibility between the radio channels, connected either to separate or common antennas, that are used in the system. This category also includes parameters providing compatibility with existing systems in the same or adjacent frequency bands; • those that define the transmission quality of the system. These requirements apply to all types of ST that transmit a single modulated carrier, including STs with an antenna diameter greater than 1,8 m (or equivalent corresponding aperture). The technical requirements of the present document apply under the environmental profile for operation of the equipment, which shall be declared by the manufacturer. The equipment shall comply with all the technical requirements of the present document at all times when operating within the boundary limits of the declared operational environmental profile. The environmental profile for operation of the equipment shall include the ranges of humidity, temperature and supply voltage.
|
102 188-4
|
Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A) air interface; Physical layer specification; Part 4: Modulation
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/10218804/01.01.02_60/ts_10218804v010102p.pdf
|
The present document defines the modulation used within the SES BSM Regenerative Satellite Mesh - A (RSM-A) air interface family. It includes the various modulation formats that are required for different physical channel types. It also defines the concept of the transmission burst and the mapping of modulated symbols to the burst, and describes the required transmit filtering in general terms.
|
102 192-1
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); International Technical Characteristics and Test Methods; Part 1: Wireless/Radio Microphones in the 25 MHz to 3 GHz Frequency Range
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/10219201/01.01.01_60/ts_10219201v010101p.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 equipment operating on radio frequencies between 25 MHz and 3 GHz, using analogue, digital and hybrid (using both analogue and digital modulation) The present document does not apply to radio microphones or in ear monitoring equipment employing Time Division Multiple Access (TDMA), modulation. Additional standards or specifications may be required for equipment intended to interface to the Public Switched Telephone Network (PSTN). This facility may be submitted to regulatory conditions. The present document may be used by accredited test laboratories or manufacturers for testing of the equipment. The performance of the equipment submitted for testing should be representative of the performance of the corresponding production models. The maximum power recommended for equipment covered by the present document is 50mW mean power national regulations on maximum power output will apply. The types of equipment covered by the present document are as follows: - professional hand held radio microphones; - professional body worn radio microphones; - in ear monitoring systems; - consumer radio microphones; - tour guide systems; - aids for the handicapped (assistive technology). NOTE: Test methods within the present document are applicable for equipment with a maximum of 250 mW (mean power).
|
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.
|
102 189-1
|
Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A); SMAC/SLC layer specification; Part 1: General description
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/10218901/01.01.02_60/ts_10218901v010102p.pdf
|
The present document is an introduction to the SMAC/SLC layer specification for the TC-SES BSM Regenerative Satellite Mesh - A (RSM-A) air interface family. In particular it contains the description of the overall network and SMAC/SLC protocol architecture of the BSM Regenerative Satellite Mesh - A (RSM-A) air interface as seen from the ST. It also describes the various interfaces between the ST and other network elements and the relation between the layers in the ST logical protocol architecture as are discussed in the present document as well as the interactions with other layers in the BSM Regenerative Satellite Mesh - A (RSM-A) protocol architecture.
|
102 188-6
|
Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A) air interface; Physical layer specification; Part 6: Radio link control
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/10218806/01.01.02_60/ts_10218806v010102p.pdf
|
The present document presents the requirements for synchronizing timing and frequency between the ST and the satellite network within the SES BSM Regenerative Satellite Mesh - A (RSM-A) air interface family.
|
102 189-3
|
Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A); SMAC/SLC layer specification; Part 3: ST-SAM Interface specification
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/10218903/01.01.02_60/ts_10218903v010102p.pdf
|
The present document defines the communication interface between a TC-SES BSM Regenerative Satellite Mesh-A (RSM-A) air interface compliant Satellite Terminal (ST) and the Security Access Module (SAM). It specifies the communication medium and the protocols for communication. The present document describes how packets, received at the ST from the Network Operations Control Centre (NOCC), are routed to the SAM, how messages created originally by the ST are routed to the SAM, how message from the SAM are routed via the ST to the NOCC and how messages from the SAM are consumption by the ST.
|
102 188-7
|
Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A) air interface; Physical layer specification; Part 7: Synchronization
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/10218807/01.01.02_60/ts_10218807v010102p.pdf
|
The present document presents the requirements for synchronizing timing and frequency between the ST and the satellite network within the TC-SES BSM Regenerative Satellite Mesh - A (RSM-A) air interface family.
|
102 189-2
|
Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A); SMAC/SLC layer specification; Part 2: Satellite Medium Access Control and Satellite Link Control detailed specification
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/10218902/01.01.02_60/ts_10218902v010102p.pdf
|
The present document is the detailed specification of the SMAC/SLC layer protocol for the TC-SES BSM Regenerative Satellite Mesh - A (RSM-A) air interface family. In particular, it contains SMAC and SLC procedures, messages and message formats.
|
102 148-1-2
|
Broadband Radio Access Networks (BRAN); HIPERACCESS; Conformance testing for the Packet based Convergence Layer; Part 1: Common part; Sub-part 2: Test Suite Structure and Test Purposes (TSS&TP) specification
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/1021480102/01.02.01_60/ts_1021480102v010201p.pdf
|
The present document contains the Test Suite Structure (TSS) and Test Purposes (TP) to test TS 102 117-1 [1]. The objective of this test specification is to provide a basis for conformance tests for BRAN HIPERACCESS equipment giving a high probability of air interface inter-operability between different manufacturers' BRAN HIPERACCESS equipment. The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [3] and ISO/IEC 9646-2 [4]) as well as the ETSI rules for conformance testing (ETS 300 406 [2]) are used as a basis for the test methodology.
|
102 169-1
|
Services and Protocols for Advanced Networks (SPAN); Network Integration Testing between H.323, ISDN and PSTN; Part 1: Test Suite Structure and Test purposes (TSS&TP)
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/10216901/01.01.01_60/ts_10216901v010101p.pdf
|
The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) for Network Integration Testing (NIT) to verify the overall compatibility of ITU-T Recommendation H.323 [3], ISDN and non-ISDN (PSTN) over the national or international ISUP between networks. The TSS&TP specification covers the procedures described in ITU-T Recommendation H.323 [3] , ITU-T Recommendation H.225.0 [4] as specified in TS 101 883 [1] and ITU-T Recommendation Q.931 [5]". All test purposes are written with reference to ITU-T Recommendation H.246 annex C [10] which implies the following test architecture: SUT H.323 ISUP ISDN mapping H.323->ISUP H.246 annex C mapping ISUP->ISDN (Q.699) H.323 terminal ISDN terminal H.323-ISDN inter-working testing architecture via ISUP Two mapping functions are involved. They are specified in ITU-T Recommendation H.246 annex C [10] (H.323-ISUP) and ITU-T Recommendation Q.699 [23] (ISDN-ISUP).
|
102 166
|
Corporate telecommunication Networks (CN); Signalling interworking between QSIG and SIP; Basic services
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/102166/01.02.01_60/ts_102166v010201p.pdf
|
The present document specifies signalling interworking between QSIG and the Session Initiation Protocol (SIP) in support of basic services within a corporate telecommunication network (CN) (also known as enterprise network). QSIG is a signalling protocol that operates between Private Integrated Services eXchanges (PINX) within a Private Integrated Services Network (PISN). A PISN provides circuit-switched basic services and supplementary services to its users. QSIG is specified in Ecma Standards; in particular, [2] (call control in support of basic services), [3] (generic functional protocol for the support of supplementary services), and a number of standards specifying individual supplementary services. NOTE: The name QSIG was derived from the fact that it is used for signalling at the Q reference point. The Q reference point is a point of demarcation between two PINXs. SIP is an application-layer protocol for establishing, terminating, and modifying multimedia sessions. It is typically carried over IP [15] and [16]. Telephone calls are considered a type of multimedia session where just audio is exchanged. SIP is defined in [10]. As the support of telephony within corporate networks evolves from circuit-switched technology to Internet technology, the two technologies will coexist in many networks for a period, perhaps several years. Therefore, there is a need to be able to establish, modify, and terminate sessions involving a participant in the SIP network and a participant in the QSIG network. Such calls are supported by gateways that perform interworking between SIP and QSIG. The present document specifies SIP-QSIG signalling interworking for basic services that provide a bi-directional transfer capability for speech, DTMF, facsimile, and modem media between a PISN employing QSIG and a corporate IP network employing SIP. Other aspects of interworking, e.g. the use of RTP and SDP, will differ according to the type of media concerned and are outside the scope of the present document. Call-related and call-independent signalling in support of supplementary services is outside the scope of the present document, but support for certain supplementary services (e.g. call transfer, call diversion) could be the subject of future work. Interworking between QSIG and SIP permits a call originating at a user of a PISN to terminate at a user of a corporate IP network, or a call originating at a user of a corporate IP network to terminate at a user of a PISN. Interworking between a PISN employing QSIG and a public IP network employing SIP is outside the scope of the present document. However, the functionality specified in the present document is in principle applicable to such a scenario when deployed in conjunction with other relevant functionality (e.g. number translation, security functions, etc.). The present document is applicable to any interworking unit that can act as a gateway between a PISN employing QSIG and a corporate IP network employing SIP.
|
102 165-2
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Methods and protocols; Part 2: Protocol Framework Definition; Security Counter Measures
|
TS
|
4.2.1
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/10216502/04.02.01_60/ts_10216502v040201p.pdf
|
The present document defines by means of an information model and functional entity behavioural model, the security countermeasures for the ICT in general and where examples are shown they are shown with respect to the NGN. Countermeasures are grouped by their key feature, i.e. Authentication, Integrity. The Unified Modelling Language (UML) is used to model the countermeasures as a semi-formal tool with verification and simulation capabilities deployed during development. NOTE: This is in accordance with the goals of the eEurope project under objective Good practices (COM(2002) 263 page 18). The countermeasures defined in the present document have been identified from an analysis of the NGN presented in TS 102 165-1 [10] and in TR 187 002 [9] as those most likely to be required for mitigation of risk in the NGN. The deployment of the countermeasures in the NGN is extrapolated from TR 187 002 [9] and defined in this document. The present document is intended for designers of security countermeasures. NOTE: The definition of cryptographic algorithms is not provided by this document but the invocation of algorithms in protocol sequences is shown. The specific use of IPsec [11] in ESP mode [12], including IKEv2 [18] and is reviewed in annex B of this document as a specific stage 3 implementation of the stage 1 and stage 2 capabilities. The authentication countermeasures outlined as structural and behavioural patterns in the present document cover the following scenarios: • Source authentication as defined for IPsec ESP. • NASS-IMS bundled authentication including mechanisms for NASS authentication. • Early IMS authentication (by reference to TR 133 978 [20]).
|
102 165-1
|
<empty>
|
TS
|
4.2.3
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/10216501/04.02.03_60/ts_10216501v040203p.pdf
|
The present document defines a method primarily for use in undertaking an analysis of the threats, risks and vulnerabilities of an Information and Communications Technology (ICT) system to identify applicable countermeasures. NOTE 1: The method described has been tailored to apply to pre-production but can be applied to production devices with due attention given to possibility that the application of countermeasures may be unachievable for a re-design strategy. NOTE 2: The method described in the present document builds from the Common Criteria for security assurance and evaluation defined in [i.27], [i.28], [i.29] and may be used to form part of the documentation set for the Target Of Evaluation as specified in ETSI ES 202 382 [i.24].
|
102 164
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Emergency Location Protocols [OMA-TS-MLP-V3_2-20051124-C]
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/102164/01.03.01_60/ts_102164v010301p.pdf
|
The present document specifies the protocol that is used by the local emergency operator to obtain the location information that is registered on the operator location server, see figure 1. It endorses and defines a profile of the OMA specification OMA-TS-MLP-V3_2-20051124-C [1] that are applicable to the emergency location information services. NOTE: The LI Forum has been affiliated and its work subsumed into the OMA; the LIF TS 101 Specification has been succeeded by OMA-TS-MLP-V3_2.
|
102 165-1
|
Cyber Security (CYBER); Methods and protocols; Part 1: Method and pro forma for Threat, Vulnerability, Risk Analysis (TVRA)
|
TS
|
5.3.1
|
http://www.etsi.org/deliver/etsi_ts/102100_102199/10216501/05.03.01_60/ts_10216501v050301p.pdf
|
The present document defines a method primarily for use in undertaking an analysis of the threats, risks and vulnerabilities of an Information and Communications Technology (ICT) system to identify applicable countermeasures. NOTE 1: The method described has been tailored to apply to pre-production but can be applied to production devices with due attention given to possibility that the application of countermeasures may be unachievable for a re-design strategy. NOTE 2: The method described in the present document builds from the Common Criteria for security assurance and evaluation defined in [i.27], [i.28], [i.29] and may be used to form part of the documentation set for the Target Of Evaluation as specified in ETSI ES 202 382 [i.24].
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.