ETSI TS 102 705 V13.0.0 (2019-05)

ETSI TS 102 705 V13.0.0 (2019-05)






TECHNICAL SPECIFICATION
Smart Cards;
UICC Application Programming Interface for Java Card™
for Contactless Applications
(Release 13)



---------------------- Page: 1 ----------------------
Release 13 2 ETSI TS 102 705 V13.0.0 (2019-05)



Reference
RTS/SCP-THCIAPIvd00
Keywords
API, smart card
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2019.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
Release 13 3 ETSI TS 102 705 V13.0.0 (2019-05)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 6
3 Definition of terms, symbols and abbreviations . 6
3.1 Terms . 6
3.2 Symbols . 6
3.3 Abbreviations . 7
4 Description . 7
4.1 Architecture . 7
4.2 Card Emulation Mode . 9
4.3 Reader Mode . 10
4.3.0 Reader Mode service description . 10
4.3.1 Receiving and sending messages over the contactless interface . 10
4.3.2 Receiving notifications about reader status . 11
4.4 Connectivity Service . 11
4.5 CLT specific extension to Card Emulation Mode . 12
5 Interaction with Proactive Functionality . 12
6 Java Card Resource Handling . 12
Annex A (normative): Java Card™ Platform HCI API for the UICC . 13
Annex B (normative): Java Card™ Platform HCI API for the UICC identifiers . 14
Annex C (normative): HCI API package version management . 15
Annex D (informative): Change history . 16
History . 17

ETSI

---------------------- Page: 3 ----------------------
Release 13 4 ETSI TS 102 705 V13.0.0 (2019-05)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Smart Card Platform (SCP).
The contents of the present document are subject to continuing work within TC SCP and may change following formal
TC SCP approval. If TC SCP modifies the contents of the present document, it will then be republished by ETSI with
an identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
0 early working draft;
1 presented to TC SCP for information;
2 presented to TC SCP for approval;
3 or greater indicates TC SCP approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI

---------------------- Page: 4 ----------------------
Release 13 5 ETSI TS 102 705 V13.0.0 (2019-05)
1 Scope
The present document describes the UICC Application Programming Interface for Java Card™ for contactless
Applications. Its purpose is to provide access for a contactless Applet to the services provided by the HCI protocol
defined in ETSI TS 102 622 [4] for the communication via the CLF. In the scope of the present document contactless
means support for the RF Technologies referenced by the HCI specification [4]. Low level functionality to manage
gates and pipes as defined in the HCI specification [4] is not in the scope of the present document. Registration of
contactless parameters and management of contactless Applets in card emulation mode is defined in "GlobalPlatform
Card Specification Amendment C" [8]. Related APIs are provided in "Java Card API and Export File for Card
Specification v2.2.1 (org.globalplatform)" [12] and "Card Contactless API and Export File for Card Specification v2.3
(org.globalplatform.contactless)" [13].
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
• In the case of a reference to a TC SCP document, a non-specific reference implicitly refers to the latest version
of that document in the same Release as the present document.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ISO/IEC 7816-3 (2006): "Identification cards - Integrated circuit cards - Part 3: Cards with
contacts - Electrical interface and transmission protocols".
[2] ETSI TS 102 221: "Smart Cards; UICC-Terminal interface; Physical and logical characteristics".
[3] ETSI TS 101 220: "Smart Cards; ETSI numbering system for telecommunication application
providers".
[4] ETSI TS 102 622: "Smart Cards; UICC - Contactless Front-end (CLF) Interface; Host Controller
Interface (HCI)".
[5] ETSI TS 102 241: "Smart Cards; UICC Application Programming Interface (UICC API) for Java
TM
Card ".
[6] ETSI TS 102 223: "Smart Cards; Card Application Toolkit (CAT)".
[7] ETSI TS 102 226: "Smart Cards; Remote APDU structure for UICC based applications".
[8] GlobalPlatform: "GlobalPlatform Technology, Contactless Services, Card Specification v2.3,
Amendment C" Version 1.2.1.
NOTE: See http://www.globalplatform.org/.
[9] ORACLE: "Application Programming Interface, Java Card™ Platform, 3.0.1 Classic Edition".
[10] ORACLE: "Runtime Environment Specification, Java Card™ Platform, 3.0.1 Classic Edition".
ETSI

---------------------- Page: 5 ----------------------
Release 13 6 ETSI TS 102 705 V13.0.0 (2019-05)
[11] ORACLE: "Virtual Machine Specification Java Card™ Platform, 3.0.1 Classic Edition".
NOTE: ORACLE Java Card Specifications can be downloaded at
https://docs.oracle.com/en/java/javacard/3.1/index.html.
[12] GlobalPlatform: "Java Card API and Export File for Card Specification v2.2.1
(org.globalplatform)" v1.6.
[13] GlobalPlatform: "Card Contactless API and Export File for Card Specification v2.3
(org.globalplatform.contactless)" v1.3.
[14] ETSI TS 102 613: "Smart Cards; UICC - Contactless Front-end (CLF) Interface; Physical and data
link layer characteristics".
[15] ETSI TS 102 705: "Smart Cards; UICC Application Programming Interface for Java Card™ for
Contactless Applications".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
• In the case of a reference to a TC SCP document, a non-specific reference implicitly refers to the latest version
of that document in the same Release as the present document.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
Not applicable.
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
contactless mode: used as a generic term for "Card Emulation Mode" and "Reader Mode"
contactless state: corresponds to the logical state of the contactless framework
HCP message: Message as specified in ETSI TS 102 622 [4].
NOTE: An HCP message can be of type "command", "event" or "response to a command".
RF Technology: radio frequency technology supported by the HCI (ETSI TS 102 622 [4]) protocol specification
3.2 Symbols
Void.
ETSI

---------------------- Page: 6 ----------------------
Release 13 7 ETSI TS 102 705 V13.0.0 (2019-05)
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
APDU Application Protocol Data Unit
NOTE: According to ISO/IEC 7816-3 [1].
API Application Programming Interface
CAT Card Application Toolkit
CLF ContactLess Front-end
NOTE: According to ETSI TS 102 622 [4].
CLT ContactLess Tunnelling
NOTE: According to ETSI TS 102 613 [14].
CRS Contactless Registry Service
HCI Host Controller Interface
NOTE: According to ETSI TS 102 622 [4].
HCP Host Controller Protocol
NOTE: According to ETSI TS 102 622 [4].
RF Radio Frequency
SCP Smart Card Platform
SWP Single Wire Protocol
NOTE: According to ETSI TS 102 613 [14].
TC Technical Committee
TS Technical Specification
4 Description
4.1 Architecture
TM
The present document describes an API and a Contactless Framework that enables Java Card Platform based
Applets, defined in [9], [10] and [11], to send and receive messages using the HCI protocol as specified in ETSI
TS 102 622 [4] and to act as contactless Applets. The Contactless Framework shall support card emulation mode and
reader mode as specified in the HCI protocol specification (ETSI TS 102 622 [4]).
ETSI

---------------------- Page: 7 ----------------------
Release 13 8 ETSI TS 102 705 V13.0.0 (2019-05)

CRS App CREL App Reader Mode
CardEmulation
Applets
Mode Applets
TM
Java Card CRS API uicc.hci.framework uicc.hci.service.*
Packages package packages

TM
Java Card Runtime Environment
Contactless
CL Registry
Framework
Items that are defined in this specification
Items that are defined GP Amendment C


Figure 1
The functionality of the Contactless Framework and the configuration of contactless parameters and the management of
contactless Applets in card emulation mode are based on the functionality provided by the Contactless Registry Service
(CRS), the related APIs, the CRS Application and other features and concepts which are defined in the "GlobalPlatform
Amendment C" [8] and the related APIs "Java Card API and Export File for Card Specification (org.globalplatform)"
[12] and "Card Contactless API and Export File for Card Specification (org.globalplatform.contactless)" [13].
The API is event driven and based on the Observer/Listener pattern. Every HCI service is encapsulated by a dedicated
Service interface. These Service interfaces shall allow the registration of Listener Interfaces and the activation of
events. The Listener Interfaces shall be implemented by Java objects to receive HCI messages and events in the
onCallback method. The Registration of Listener Interfaces and activation of events shall be persistent.
An HCIMessage object shall encapsulates one HCP message according to the HCI protocol as specified in ETSI
TS 102 622 [4]. HCI message for the different contactless modes shall be identified by different types of interfaces. It is
not guaranteed that any Applet originated HCI messages are sent before the completion of the execution of the current
Applet. The Contactless Framework sends the Applet originated HCI messages in the same order as they are submitted
by the Applet.
NOTE 1: The Contactless Framework may not have enough resources to send several HCI messages submitted
during the same onCallback method execution. The Applet should be aware of this limitation (e.g. use
suitable error handling strategy, or send only one HCI message in the onCallback method at a time).
Any onCallback() method of a Listener interface shall not be invoked again while another onCallback() method is still
being executed. The Contactless Framework shall be able to receive one or more HCI messages while waiting for a
response related to a command originated by the Applet (e.g. processing a request for parameters) especially for the
EVT_FIELD_OFF case.
The HCI event EVT_FIELD_OFF shall be buffered and sent by the Contactless Framework as soon as the Contactless
Framework becomes the current context.
All other HCI messages shall be delivered to the Applet instance in the same order as they were received by the
Contactless Framework.
ETSI

---------------------- Page: 8 ----------------------
Release 13 9 ETSI TS 102 705 V13.0.0 (2019-05)
Contactless State is the logical state of the Contactless Framework it can take the value enabled and disabled. It refers to
the "contactless functionality in the UICC" as used in ETSI TS 102 223 [6].
This state can be changed with the mechanisms defined in ETSI TS 102 223 [6], and by the method
setCommunicationInterface() API method of "GlobalPlatform Amendment C" [8].
The Contactless State applies only to the Card Emulation Mode and the Reader Mode, and it does not apply to the
Connectivity service.
When the Contactless State is disabled, the Contactless Framework shall throw an HCIException with reason code
HCI_CURRENTLY_DISABLED when an Applet invokes a method which requires that the Contactless State is
enabled.
When the Contactless State is enabled and the state of the SWP [14] interface is DEACTIVATED and when the
Contactless Framework needs to send data over the SWP [14] interface then it shall send the proactive command
ACTIVATE defined in ETSI TS 102 223 [6] if supported by the terminal. The ACTIVATE command is defined as
system proactive command sent by the CAT Runtime Environment defined in ETSI TS 102 241 [5].
NOTE 2: An Applet may use the method HCIDevice.isHCIServiceAvailable() to check if the Contactless
Framework supports sending the ACTIVATE command on pre Rel-11 implementations.
The u
...