|
|
|
|
| |
# |
|
# |
|
# |
|
# |
|
# |
|
# |
|
# |
|
# |
|
|
| |
# SCP |
|
# |
|
# |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 102 124
|
|
Smart Cards - Transport Protocol for UICC based Applications - Stage 1 |
The present document defines the stage one description of the Transport Protocol, CAT_TP, for CAT applications
based on TS 102 223.
The Bearer Independent Protocol as defined in TS 102 223 allows a CAT application on the UICC to establish a
data channel with the terminal, and through the terminal either to a remote server in the network or to a remote device in
the Personal Area Network (PAN). The Bearer Independent Protocol obviously inherits the properties of the bearer and
the network protocols it uses and may stand on top of unreliable transport protocols (such as UDP).
The present document contains the core requirements for the CAT_TP between the card and a remote entity to ensure
acknowledgement, segmentation/fragmentation, retransmission of messages, etc. The transport mechanisms specified
are independent of applications and used bearers. Even if the current definition of the CAT_TP protocol is focused on
the Bearer Independent Protocol, it does not prevent the CAT_TP to be used over future UICC-TE communication
protocol.
|
|
|
| |
| |
| |
| |
| |
| |
|
|
- | |
- | |
- | |
V6.1.0
2004-12
(13 p.) | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 102 224
|
|
Smart Cards - Security mechanisms for UICC based Applications - Functional requirements |
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 TS 102 225.
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 TS 102 221.
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 102 240
|
|
Smart Cards - UICC Application Programming Interface & Loader Requirements - Service description |
The present document defines the service description of the UICC Application Programming Interface (UICC API)
internal to the UICC. Stage one is an overall service description, and does not deal with the implementation details of
the API.
The present document includes information applicable to network operators, service providers and terminal, UICC,
Network Access Application (NAA) providers, switch and database manufacturers.
The present document contains the core requirements, which are sufficient to provide a complete service.
It is highly desirable however, that technical solutions for a UICC API should be sufficiently flexible to allow for
possible enhancements. Additional functionalities not documented in the present document may implement
requirements which are considered outside the scope of the present document. This additional functionality may be on a
network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not
compromise conformance to the core requirements of the service.
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 102 266
|
|
Smart Cards - USSM: UICC Security Service Module - Stage 1 |
The present document describes the functional requirements of the USSM, a generic UICC Security Service Module, to
be used by the applications on an UICC. It defines the necessary framework for supporting and managing the USSM on
an UICC.
The concept of the USSM is flexible enough to allow additional security objects and operations to be added easily in
later versions of the specification or during the specification of a stage-2 document.
|
|
|
| |
| |
| |
| |
| |
| |
|
|
- | |
- | |
- | |
- | |
V7.1.0
2006-01
(13 p.) | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 102 127
|
|
Smart Cards - Transport protocol for CAT applications - Stage 2 |
The present document defines the stage two description of the Card Application Toolkit Transport Protocol (CAT_TP),
for CAT applications based on TS 102 223.
The present document contains the core functionalities for the CAT_TP between two CAT_TP entities hosting for
instance on a UICC and on a remote entity.
The CAT_TP described in the present document is based on RDP version 2 as specified in
RFC 908 and
RFC 1151.
The present document describes, according requirements defined in TS 102 124:
|
| - |
The core functionalities of CAT_TP (data structures, state diagrams, protocol procedures, etc.).
| |
| - |
Usage of CAT_TP on top of the Bearer Independent Protocol (BIP).
|
The following items are out of the scope of the present document:
|
| - |
The specific implementation of an API.
| |
| - |
Anything dealing with the security above CAT_TP.
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 102 221
|
|
Smart Cards - UICC-Terminal interface - Physical and logical characteristics |
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;
| |
| - |
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.
|
The administrative procedures, initial card management and optional communication interfaces between the UICC and
terminal are not within the scope of the present document.
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 102 222
|
|
Integrated Circuit Cards - Administrative commands for telecommunications applications |
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 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. A UICC supporting the command set
based on the present document shall support the command as defined in the present document. However, it is up to the
UICC to provide more functionality than described in the present document.
The present document does not cover the internal implementation within the UICC and/or the external equipment.
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 102 223
|
|
Smart Cards - Card Application Toolkit (CAT) |
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 TS 102 221 or TS 102 600, here called
"3G platform", or 3GPP TS 51.011, here called "2G platform".
NAA can be:
|
| - |
a USIM application, as defined in 3GPP (CT6) TS 31.102, which can reside only on a 3G platform;
| |
| - |
a SIM application, as defined in 3GPP (CT6) TS 51.011, which can reside either on a 3G or a 2G platform;
| |
| - |
a TSIM application, as defined in ETSI TS TS 100 812, which can reside only on a 3G platform;
| |
| - |
a ISIM application, as defined in 3GPP (CT6) TS 31.103, which can reside only on a 3G platform;
| |
| - |
a RUIM application, as defined in TIA/IS-820-A, 3GPP2 C.S0023-0, which can reside on a
2G platform; 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.
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 102 225
|
|
Smart Cards - Secured packet structure for UICC based applications |
The present document specifies the structure of the Secured Packets in a general format.
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 TS 102 224 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.
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 102 226
|
|
Smart Cards - Remote APDU structure for UICC based applications |
The present document defines the remote management of the UICC based on the secured packet structure specified in
TS 102 225.
It specifies the APDU format for remote management.
Furthermore the present document specifies:
|
| - |
a set of commands coded according to this APDU structure and
used in the remote file management on the UICC. This is based on TS 102 221.
| |
| - |
A set of commands coded according to this APDU structure and used in the remote application management
on the UICC. This is based on the GlobalPlatform Card Specification.
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 102 241
|
|
Smart Cards - UICC Application Programming Interface (UICC API) for Java Card™ |
The present document defines the stage two description of the "Application Programming Interface and Loader
Requirements" (ETSI TS 102 240) internal to the UICC.
This stage two describes the functional capabilities and the information flow for the UICC API implemented on the
Java Card™ 2.2.2 specifications.
The present document includes information applicable to network operators, service providers and UICC, server and
database manufacturers.
|
|
|
|
|
|
|
|
|
|
|
|
| |
| |
| |
| |
| |
| |
|
|
- | |
- | |
- | |
- | |
V7.1.0
2010-04
(17 p.) | |
- | |
- |
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 102 310
|
|
Smart Cards - Extensible Authentication Protocol support in the UICC |
The present document defines additional features that shall be provided by the UICC to support EAP authentication
capabilities.
The goal of these new features is to adapt the UICC to provide support of different EAP methods, ensuring
interoperability between the UICC and any terminal independently of their respective manufacturers.
The present document defines:
|
| - |
The architectural framework.
| |
| - |
The additional commands required.
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 102 483
|
|
Smart Cards - UICC-Terminal interface - IP connectivity between UICC and terminal |
The present document specifies the establishment and configuration of an Internet Protocol connection between a UICC
and a terminal interfaced through a protocol that supports the transport of Internet Protocol packets.
The way the Internet Protocol packets (or similar packets such as ARP) are transported over the UICC-Terminal
interface is part of the UICC-Terminal interface specification and not within the scope of the present document. The
present document focuses on the configuration and establishment of the Internet Protocol connection between the UICC
and the terminal.
The Internet Protocol connectivity defined in the present document may be used by applications such as the Smartcard
Web Server.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 102 569
|
|
Smart Cards - UICC Security Service Module (USSM) - Stage 2 |
The present document describes the stage two specification of the USSM. The USSM is a generic Security Service
Module on a UICC, which can be used by applications on the UICC.
This document defines the architectural framework for using the USSM, the functional services for applications and
how to manage the USSM on an UICC. The architecture is based on the concepts of Global Platform Card
Specification and the requirements as defined in TS 102 266.
The concept of the USSM is flexible enough to allow additional security objects and operations to be added easily in
later versions of the USSM.
|
|
|
| |
| |
| |
| |
| |
| |
|
|
- | |
- | |
- | |
- | |
V7.0.0
2007-07
(27 p.) | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 102 600
|
|
Smart Cards - UICC-Terminal interface - Characteristics of the USB interface |
The present document specifies the Inter-Chip USB interface between the USB UICC and the USB UICC-enabled
terminal, subsequently referred to as the IC USB interface. It describes:
|
| - |
the characteristics of the Inter-Chip USB electrical interface between the USB UICC and the
USB UICC-enabled terminal;
| |
| - |
the initial communication establishment and the transport protocols;
| |
| - |
the communication layers between the USB UICC and the USB UICC-enabled terminal.
|
The physical characteristics (including mechanical aspects) defined in TS 102 221 apply to USB UICCs. The
present document comes as an extension of TS 102 221 complementing the electrical characteristics of contacts C1
and C5 and describing the behaviour of contacts C4 and C8 when the USB interface is supported.
The Inter-Chip USB interface provides access to the existing UICC resources such as the file system and security
features specified in TS 102 221 and to other resources and functionalities specified in the present document.
|
|
|
| |
| |
| |
| |
| |
| |
|
|
- | |
- | |
- | |
- | |
V7.7.0
2010-04
(26 p.) | |
- | |
- |
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 102 613
|
|
Smart Cards - UICC-CLF Interface -
Part 1: Physical and data link layer characteristics |
The present document specifies the Single Wire Protocol (SWP). SWP is the interface between the UICC and the CLF.
The present document defines:
|
| - |
Layer1: The physical layer which is responsible for activating, maintaining and deactivating the physical link
between the UICC and the CLF. It defines electrical (voltage and current levels, timing and coding of voltage
and current levels), mechanical (physical contacts) and functional (data rates) specifications. It also defines the
initial communication establishment and the end of the connection.
| |
| - |
Layer 2: The data link layer which is responsible for the physical addressing of the data through frames and
Link Protocol Data Units (LPDU). The data link layer is also responsible for error notification, ordered delivery
of frames and flow control. This layer can be split into two sub-layers:
|
| - |
The Medium Access Control (MAC) layer which manages frames.
| |
| - |
The Logical Link Control layer which manages LPDUs and is responsible for the error-free exchange of
data between nodes. Three different Logical Link Control layers are defined in the present document.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 102 622
|
|
Smart Cards - UICC-CLF Interface - Host Controller Interface (HCI) |
The present document specifies a logical interface that enables contactless applications hosted on the UICC. The present
document covers the configuration where the one host is embedded in the UICC which is connected to the host
controller embedded in the CLF.
The interface is specified in two parts:
|
| - |
the HCI core as described in the first part of the present document (clause 4 to 8), specifies an application
independent logical interface; and
| |
| - |
the contactless platform as described in the second part of the present document (clauses 9 to 11) specifies an
implementation of the HCI core for contactless applications using the UICC and the CLF.
|
Lower layer protocols that support the HCI like the SWP specified in ETSI TS 102 613 are out of the scope of the present
document.
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 102 671
|
|
Machine to Machine UICC - Physical and logical characteristics |
The present document details the technical specifications for M2M UICCs.
Specifically, the present document specifies:
|
| - |
Physical, logical and electrical specifications for additional machine to machine form factors for the M2M
UICC.
| |
| - |
Environmental specifications of the M2M UICC dedicated to M2M applications for all specified UICC form
factors.
| |
| - |
Device pairing mechanisms that allow the M2M UICC to verify the terminal with which it is operating.
|
|
|
|
| |
| |
| |
| |
| |
| |
|
|
- | |
- | |
- | |
- | |
- | |
- | |
V9.0.0
2010-04
(21 p.) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
| |
| |
| |
| |
| |
|
|
- | |
- | |
- | |
- | |
V7.1.0
2008-03
(185 p.) | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
| |
| |
| |
| |
| |
| |
|
|
- | |
- | |
- | |
- | |
V7.0.0
2010-04
(91 p.) | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
| |
| |
| |
| |
| |
| |
|
|
- | |
- | |
- | |
- | |
V7.1.0
2010-04
(113 p.) | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
| |
| |
| |
| |
| |
| |
|
|
- | |
- | |
- | |
- | |
V7.0.0
2010-04
(67 p.) | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
| |
| |
| |
| |
| |
| |
|
|
- | |
- | |
- | |
- | |
V7.1.0
2010-04
(62 p.) | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
| |
| |
| |
| |
| |
| |
|
|
- | |
- | |
- | |
- | |
V7.0.0
2010-04
(56 p.) | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
| |
| |
| |
| |
| |
| |
|
|
- | |
- | |
- | |
- | |
V7.0.0
2010-04
(87 p.) | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
