1、 ETSI TR 131 919 V8.0.0 (2009-03)Technical Report Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;2G/3G Java Card Application Programming Interface (API) based applet interworking (3GPP TR 31.919 version 8.0.0 Release 8)ETSI ETSI TR 131 919
2、 V8.0.0 (2009-03) 1 3GPP TR 31.919 version 8.0.0 Release 8 Reference RTR/TSGC-0631919v800 Keywords GSM, LTE, UMTS 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 enre
3、gistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in conte
4、nts between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the documen
5、t may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org
6、/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2009. All rights reserved. DECTTM, PLUGTESTSTM, UMT
7、STM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit
8、 of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 131 919 V8.0.0 (2009-03) 2 3GPP TR 31.919 version 8.0.0 Release 8 Intellectual Property Rights IPRs essential or potentially essential to the presen
9、t document 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 resp
10、ect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). 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
11、 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. Foreword This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may
12、 refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.o
13、rg/key/queryform.asp. ETSI ETSI TR 131 919 V8.0.0 (2009-03) 3 3GPP TR 31.919 version 8.0.0 Release 8 Contents Intellectual Property Rights2 Foreword.2 Foreword.4 Introduction 4 1 Scope 5 2 References 5 3 Definitions5 4 The SIM API-(U)SIM API interworking .6 4.1 Terminal Profile .6 4.2 Registration a
14、nd resource allocation.6 4.3 Triggering.6 4.4 System handlers6 4.5 File access 7 5 The behaviour and limitations of SIM API used in 3G mode7 5.1 File system access 7 5.2 SIM Toolkit Framework.7 5.2.1 Applet Triggering .7 5.2.2 Proactive commands and responses8 5.2.3 post() methods 8 5.2.4 System pro
15、active commands.8 5.2.5 Select AID and invocation of ProactiveHandler.send() method 8 6 The behaviour and limitations of (U)SIM API used in 2G mode 9 Annex A: Change history 10 History 11 ETSI ETSI TR 131 919 V8.0.0 (2009-03) 4 3GPP TR 31.919 version 8.0.0 Release 8 Foreword This Technical Report ha
16、s been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an iden
17、tifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all chang
18、es 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. Introduction This document describes the different cases of interactions between SIM API and (U)SIM API. ETSI ETSI TR 131 919
19、V8.0.0 (2009-03) 5 3GPP TR 31.919 version 8.0.0 Release 8 1 Scope The present document describes: - Description of TS 43.019 1 APIs and TS 102 241 2 / TS 31.130 7 APIs interworking. - The behaviour and limitations of the TS 43.019 1 APIs used in 3G environment. 2 References The following documents c
20、ontain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-spe
21、cific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TS 43.019 Release 5: “Subscriber Identity Modul
22、e Application Programming Interface (SIM API) for Java Card; Stage 2“. 2 ETSI TS 102 241 Release 6: “UICC Application Programming Interface (API) for Java Card “. 3 3GPP TS 51.011 Release 4: “Specification of the Subscriber Identity Module - Mobile Equipment Interface“. 4 3GPP TS 31.102: “Characteri
23、stics of the USIM Application“. 5 3GPP TR 31.900 Release 5: “SIM/USIM Internal and External Interworking Aspects“. 6 3GPP TS 31.111: “USIM Application Toolkit (USAT) “ 7 3GPP TS 31.130: “(U)SIM API for Java Card“ 8 ETSI TS 102 221 Release 6: “Smart Cards; UICC-Terminal interface; Physical and logica
24、l characteristics“. 9 3GPP TS 11.14 Release 99: “Specification of the SIM Application Toolkit for the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface“. 10 ETSI TS 102 223 Release 6: “Smart cards; Card Application Toolkit (CAT)“. 3 Definitions For the purpose of the present documen
25、t, the terms and definitions given in TS 43.019 1, ETSI TS 102 241 2 and the following apply. SAT applet: applet developed using TS 43.019 1. (U)SAT applet: applet developed using ETSI TS 102 241 2 and TS 31.130 7. SIM API: API defined in TS 43.019 1. (U)SIM API: API defined in ETSI TS 102 241 2 and
26、 TS 31.130 7. ETSI ETSI TR 131 919 V8.0.0 (2009-03) 6 3GPP TR 31.919 version 8.0.0 Release 8 4 The SIM API-(U)SIM API interworking This chapter is dedicated to the interworking of the SIM API and (U)SIM API and does not consider at all the current NAA nor the current network. It is strongly recommen
27、ded that all the new applets are developed by using only the (U)SIM API. Thus, an applet loaded onto the card should use either SIM API or (U)SIM API, not both of them. The behaviour of an applet using both APIs simultaneously is out of scope of this document. 4.1 Terminal Profile The MEProfile obje
28、ct and TerminalProfile object are filled upon reception of a TERMINAL PROFILE APDU defined in TS 31.102 4, TS 51.011 3, ETSI TS 102 221 8. Their contents are identical. A SAT applet has no issue regarding the different coding of profile data as long as TS 31.111 6 definition is fully backward compat
29、ible with TS 11.14 9 (i.e. there is no bit/byte swapping). A (U)SAT applet has to take care of the bit verified in the TerminalProfile object because when inserted in a 2G terminal, some bits have more specific description in TS 11.14 9 than in TS 31.111 6. For example, the bit 4 of the 8thbyte is B
30、inary choice in GET INKEY in TS 11.14 9 and Bit = 1 if GET INKEY is supported in TS 31.111 6. For some specific features, in order to develop a (U)SAT applet independently of the terminal, it is thus recommended to interpret the bits as defined in TS 11.14 9. 4.2 Registration and resource allocation
31、 The terminal resources and the card resources are shared between SIM API and (U)SIM API. As a consequence, the system proactive commands generated by the card are independent of the used API. The only exception is for the alpha identifier and icon identifier of the SET UP MENU proactive command, wh
32、ich can differ since there are two EFSUMEfiles (one in DFGSMfor the SIM and one in DFTELECOMfor USIM application). It is possible to map these two files to have the same SET UP MENU proactive command, if not mapped they may differ. Examples: - If an applet is registered to Call Control with (U)SIM A
33、PI, an applet using SIM API can not register to Call Control. - A timer allocated with SIM API can not be allocated by (U)SIM API. - A menu entry identifier allocated by (U)SIM API can not be allocated by SIM API. 4.3 Triggering No interworking issue found at the moment. The SAT applets are triggere
34、d on their sim.toolkit.ToolkitInterface and the (U)SAT applets on their uicc.toolkit.ToolkitInterface as defined in the corresponding specifications. The order of triggering shall follow the priority level of each applet defined at its loading, independently if the applet is a SAT or a (U)SAT applet
35、. 4.4 System handlers The system handlers availability for SAT applets is as defined in TS 43.019 1 e.g. the ProactiveHandler may not be available if a proactive command is pending. The system handlers availability for (U)SAT applets is as defined in ETSI TS 102 241 2 and TS 31.130 7 e.g. the Proact
36、iveHandler may not be available if a proactive command is pending. ETSI ETSI TR 131 919 V8.0.0 (2009-03) 7 3GPP TR 31.919 version 8.0.0 Release 8 As a consequence of the EnvelopeResponseHandler availability rules, the EnvelopeResponseHandler is available for all triggered SAT or (U)SAT applets, unti
37、l an applet has posted an envelope response or sent a proactive command using SIM or (U)SIM API. The content of the sim.toolkit.EnvelopeHandler and the content of the uicc.toolkit.EnvelopeHandler are identical for all triggered applets except in the case of update of EFSMS where they may differ. 4.5
38、 File access There is no interaction between the sim.access package and the uicc.access package. 5 The behaviour and limitations of SIM API used in 3G mode The SIM API has been designed only with the SIM as current NAA connected to a 2G network and allows application programmers access to the functi
39、ons and data described in TS 51.011 3 and TS 11.14 9, such that SIM based services can be developed and loaded onto SIM. The SIM is mandatory in TS 43.019 1. This chapter points out the technical issues related to the execution of existing SAT Applets when a USIM is the current NAA or when there is
40、no application currently selected. All these technical issues have been solved in ETSI TS 102 241 2 and TS 31.130 7. 5.1 File system access The sim.access package provides a way to get a single view of the GSM (or SIM) File system defined in TS 51.011 3. It offers an interface (sim.access.SIMView) t
41、o perform operations on this file system as defined in TS 51.011 3. The SIMView object behaviour is defined in TS 43.019 1 e.g.: - at the invocation of the processToolkit method, the current file is the MF, - the format of the File Control Information is the one defined in TS 51.011 3, - the access
42、conditions as defined in TS 51.011 3 are used. - selection of a cyclic file is as defined in TS 51.011 3, the record pointer shall address the record updated or increased last. The access to any ADF is not possible, even though a USIM is the current NAA. When two files are mapped as described in TR
43、31.900 5, they have the same content after an operation (read, seek, update and increase) made by a SAT Applet. 5.2 SIM Toolkit Framework 5.2.1 Applet Triggering In order to trigger a SAT Applet when a USIM is the current NAA or when there is no application currently selected, the SIM Toolkit Framew
44、ork should be upgraded to generate events based on APDUs defined in ETSI TS 102 221 8 and TS 31.102 4. As examples: - ENVELOPE(MENU SELECTION) as defined in ETSI TS 102 223 10 with class byte 0x80 should trigger SAT Applets registered to EVENT_MENU_SELECTION. - STATUS APDU as defined in ETSI TS 102
45、221 8 and in TS 31.102 4 with class byte 0x81 should trigger SAT Applets registered to EVENT_STATUS_COMMAND. ETSI ETSI TR 131 919 V8.0.0 (2009-03) 8 3GPP TR 31.919 version 8.0.0 Release 8 - UPDATE RECORD of EFSMS(EFSMSin ADF USIM) APDU as defined in TS 102 221 8 and in TS 31.102 4 with class byte 0x
46、02 should trigger SAT Applets registered to EVENT_FORMATTED_SMS_PP_UPD or EVENT_UNFORMATTED_SMS_PP_UPD. The definition of the event EVENT_FIRST_COMMAND_AFTER_SELECT from TS 43.019 1 should be replaced with: the event EVENT_FIRST_COMMAND_AFTER_SELECT should only be generated by the SIM Toolkit framew
47、ork when the first command is received after the ATR and before the Status Word of the processed command has been sent back. New events/features introduced in UICC/(U)SAT API defined in ETSI TS 102 241 2 and TS 31.130 7 are not available for SAT applets e.g. EVENT_DOWNLOAD_DISPLAY_PARAMETER_CHANGE,
48、EVENT_DOWNLOAD_ACCESS_TECHNOLOGY_CHANGED. The parameters passed to the getShareableInterfaceObject() method to get a reference to the ToolkitInterface are expected to be the ones defined in TS 43.019 1 even if a USIM is the current NAA or if there is no application currently selected. The clientAID
49、parameter of this method is not specified in TS 43.019 1. The 3G Cell Broadcast data download is defined for the Terminal/USIM interface starting at release 5, thus this type of service would not be available for the SAT applet in earlier releases. 5.2.2 Proactive commands and responses As long as there is compatibility between TS 11.14 9 and TS 31.111 6, there is no issue on proactive commands/responses issued/received by a SAT applet. New
