ETSI TS 131 130-2016 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE (U)SIM Application Programming Interface (API.pdf

1、 ETSI TS 1Digital cellular telecommUniversal Mobile Tel(U)SIM Applicatio(U)SIM(3GPP TS 31.1floppy3TECHNICAL SPECIFICATION131 130 V13.0.0 (2016mmunications system (Phase elecommunications System (LTE; tion Programming Interface (AIM API for Java Card .130 version 13.0.0 Release 1316-01) e 2+) (GSM);

2、(UMTS); (API); 13) ETSI ETSI TS 131 130 V13.0.0 (2016-01)13GPP TS 31.130 version 13.0.0 Release 13Reference RTS/TSGC-0631130vd00 Keywords LTE 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 Assoc

3、iation but non lucratif enregistre la Sous-Prfecture 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 prin

4、t 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 only prevailing document is the print of the Portable Document Format (PDF) version kept on

5、 a specific network drive within ETSI Secretariat. 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 http:/portal.etsi.org/tb/status/status.asp If you find

6、 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

7、 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. European Telecommunications Standards Institute 2016. All rights reser

8、ved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by

9、the GSM Association. ETSI ETSI TS 131 130 V13.0.0 (2016-01)23GPP TS 31.130 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly ava

10、ilable 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 ser

11、ver (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 beco

12、me, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be

13、 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.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “n

14、eed 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 ETSI TS 131 130 V13.0.0 (

15、2016-01)33GPP TS 31.130 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Description . 6g34.0 Overview 6g34.1 (U)SIM Jav

16、a Card Architecture 7g35 File Access API 7g36 (U)SAT Framework . 7g36.0 Overview 7g36.1 Applet triggering 8g36.1.1 Exception Handling 8g36.2 Definition of Events . 8g36.3 Registration 12g36.4 Proactive command handling . 12g36.5 Envelope response handling . 13g36.6 System Handler management . 13g36.

17、7 (U)SAT Framework behaviour . 14g37 UICC toolkit applet 14g38 Geo Location API . 14g3Annex A (normative): Java Card (U)SIM API 15g3Annex B (normative): Java Card (U)SIM API identifiers . 16g3Annex C (normative): (U)SIM API package version management . 17g3Annex D (normative): USIM API jar files . 1

18、8g3Annex E (informative): Change History 19g3History 20g3ETSI ETSI TS 131 130 V13.0.0 (2016-01)43GPP TS 31.130 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continu

19、ing 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 identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 prese

20、nted 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 changes of substance, i.e. technical enhancements, corrections, updates, etc. Z the third digit is incremented when editorial onl

21、y changes have been incorporated in the document. ETSI ETSI TS 131 130 V13.0.0 (2016-01)53GPP TS 31.130 version 13.0.0 Release 131 Scope The present document defines the (U)SIM Application Programming Interface extending the “UICC API for Java Card“ 2. This API allows to develop a (U)SAT application

22、 running together with a (U)SIM application and using GSM/3G network features. The present document includes information applicable to network operators, service providers, server (U)SIM and database manufacturers. 2 References The following documents contain provisions which, through reference in t

23、his 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-specific reference, the latest version applies. In

24、 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 ETSI TS 101 220: “Integrated Circuit Cards (ICC); ETSI numbering system for telecommunication; Appl

25、ication providers (AID)“. 2 ETSI TS 102 241 V9.2.0: “UICC API for Java Card“ 3 3GPP TS 31.102: “Characteristics of the USIM Application“. 4 3GPP TS 51.011 Release 4: “Specification of the Subscriber Identity Module- Mobile Equipment (SIM ME) interface“. 5 3GPP TS 23.041: “Technical realization of Ce

26、ll Broadcast Service (CBS)“. 6 3GPP TS 31.101: “UICC-terminal interface; Physical and logical characteristics“. 7 3GPP TS 31.111: “USIM Application Toolkit (USAT)“. 8 3GPP TS 51.014 Release 4: “Specification of the SIM Application Toolkit for the Subscriber Identity Module Mobile Equipment (SIM ME)

27、interface“. 9 3GPP TS 31.115: “Secured packet structure for the (U)SIM Toolkit applications“. 10 3GPP TS 23.040: “Technical realization of the Short Message Service (SMS)“. 11 Sun Microsystems “Application Programming Interface, Java Card Platform, 3.0.1 Classic Edition“. 12 Sun Microsystems “Runtim

28、e Environment Specification, Java Card Platform, 3.0.1 Classic Edition“. 13 Sun Microsystems “Virtual Machine Specification Java Card Platform, 3.0.1 Classic Edition“. Note: SUN Java Card Specifications can be downloaded at http:/ 14 3GPP TS 23.032: “Universal Geographical Area Description (GAD)“. E

29、TSI ETSI TS 131 130 V13.0.0 (2016-01)63GPP TS 31.130 version 13.0.0 Release 133 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions defined in ETSI TS 102 241 2 apply. (U)SAT Framework : (U)SAT extension of the CAT Runtime Environment. 3.

30、2 Abbreviations For the purposes of the present document, the abbreviations defined in ETSI TS 102 241 2 apply. 4 Description 4.0 Overview This API is an extension to the ETSI TS 102 241 2 “UICC API for Java Card“ and requires the implementation of this specification. The classes and interfaces desc

31、ribed in this specification inherit functionality from the classes and interfaces specified in the “UICC API for Java Card“. The (U)SAT Framework described in this specification is an extension of the CAT Runtime Environment defined in ETSI TS 102 241 2. ETSI ETSI TS 131 130 V13.0.0 (2016-01)73GPP T

32、S 31.130 version 13.0.0 Release 134.1 (U)SIM Java Card Architecture The overall architecture of the (U)SIM API is based on the “UICC API for Java Card“ defined in ETSI TS 102 241 2. 102 221 based Applications (e.g. SIM Applet or USIM Applet) ADF File System Server Other Applications not based on 102

33、 221 Toolkit Applet (e.g. Toolkit service, Remote Management Applications, Browser Applications) UICC File System Server uicc.system package uicc.toolkit package uicc.access package Java Card TMPackages CAT Runtime Environment Toolkit Handlers Toolkit Registry Triggering Entity Java Card TMRuntime E

34、nvironment Items that are defined in this specification (U)SAT Framework USATEnvelopeHandler Figure 1: (U)SIM Java Card Architecture 5 File Access API The (U)SIM file access API consists of the package uicc.usim.access. This package defines additional constants to those defined in the uicc.access pa

35、ckage from ETSI TS 102 241 2. The access to the file system, defined in TS 51.011 4 and TS 31.102 3, is the one specified in ETSI TS 102 241 2 via the UICC FileView Interface. When selecting a cyclic file the current record number is defined, this applies also to files located under DFGSM. 6 (U)SAT

36、Framework 6.0 Overview The (U)SIM toolkit API consists of the uicc.usim.toolkit package for toolkit features defined in TS 31.111 7 and TS 51.014 8, and is based on the uicc.toolkit package defined in ETSI TS 102 241 2. ETSI ETSI TS 131 130 V13.0.0 (2016-01)83GPP TS 31.130 version 13.0.0 Release 136

37、.1 Applet triggering See ETSI TS 102 241 2. 6.1.1 Exception Handling The following clause describes the handling of exceptions by the (U)SAT Framework in addition to the behaviour defined in ETSI TS 102 241 2 for the CAT Runtime Environment. If an Applet triggered by EVENT_FORMATTED_SMS_PP_ENV event

38、 throws an ISOException with the reason code (0x6FXX), it shall be sent to the terminal. Other Exceptions shall not be propagated to the terminal. 6.2 Definition of Events The following events can trigger a Toolkit Applet in addition to the events defined in ETSI TS 102 241 2, all short values are r

39、eserved in ETSI TS 102 241 2: Table 1: (U)SAT event list Event Name Reserved short value EVENT_FORMATTED_SMS_PP_ENV 2 EVENT_FORMATTED_SMS_PP_UPD 3 EVENT_UNFORMATTED_SMS_PP_ENV 4 EVENT_UNFORMATTED_SMS_PP_UPD 5 EVENT_UNFORMATTED_SMS_CB 6 EVENT_MO_SHORT_MESSAGE_CONTROL_BY_NAA 10 EVENT_FORMATTED_SMS_CB

40、24EVENT_EVENT_DOWNLOAD_IWLAN_ACCESS_STATUS 30 EVENT_EVENT_DOWNLOAD_NETWORK_REJECTION 31 EVENT_EVENT_DOWNLOAD_CSG_CELL_SELECTION 33 EVENT_FORMATTED_USSD 121EVENT_UNFORMATTED_USSD 122EVENT_EVENT_DOWNLOAD_IMS_REGISTRATION 119 EVENT_EVENT_DOWNLOAD_INCOMING_IMS_DATA 120EVENT_FORMATTED_SMS_PP_ENV, EVENT_U

41、NFORMATTED_SMS_PP_ENV, EVENT_FORMATTED_SMS_PP_UPD, EVENT_UNFORMATTED_SMS_PP_UPD There are two ways for a card to receive a Short Message Point to Point: via an ENVELOPE(SMS-PP DOWNLOAD) APDU as defined in TS 31.111 7 and TS 51.014 8 or an UPDATE RECORD EFSMSAPDU as defined in TS 31.102 3 and TS 51.0

42、11 4. The EFSMS can beeither located under the DFTelecomor under any ADF as defined in TS 31.102 3 and TS 51.011 4. The received Short Message may be: - formatted according to TS 31.115 9 or an other protocol to identify explicitly the toolkit applet for which the message is sent; - unformatted (e.g

43、. a toolkit applet specific protocol ) then the (U)SAT Framework will pass this data to all registered toolkit applets. When the Short Message is received as Concatenated Short Messages as defined in TS 23.040 10, it is the responsibility of the (U)SAT Framework to link single Short Messages togethe

44、r to re assemble the original message before any further processing. The original Short Message shall be placed in one SMS TPDU TLV (with TP-UDL field coded on one octet) included in the USATEnvelopeHandler. The concatenation control headers used to re-assemble the short messages in the correct orde

45、r shall not be present in the SMS TPDU. The TP-elements of the SMS TPDU and the Address (TS Service-Centre-Address) shall correspond to the ones in the last received Short Message (independently of the Sequence number of Information-Element-Data). ETSI ETSI TS 131 130 V13.0.0 (2016-01)93GPP TS 31.13

46、0 version 13.0.0 Release 13The minimum requirement for the (U)SAT Framework is to process a concatenated short message with the following properties: - the Information Element Identifier is equal to the 8-bit reference number. - it contains uncompressed 8 bit data or uncompressed UCS2 data. EVENT_FO

47、RMATTED_SMS_PP_ENV Upon reception of a TS 31.115 9 formatted Short Message Point to Point (Single or Concatenated) via an ENVELOPE, the (U)SAT Framework shall: - verify the security of the Short Message as per TS 31.115 9; - trigger the toolkit applet registered with the corresponding TAR; - take th

48、e optional Application Data posted by the triggered toolkit applet if present; - secure and send the response packet using SMS-DELIVER-REPORT or SMS-SUBMIT. When the toolkit applet is triggered, data shall be provided deciphered. EVENT_UNFORMATTED_SMS_PP_ENV Upon reception of an unformatted Short Me

49、ssage Point to Point (Single or Concatenated) via an ENVELOPE, the (U)SAT Framework shall trigger all the Toolkit Applets registered to this event. NOTE: As a consequence of the EnvelopeResponseHandler availability rules specified in clause 6.6, only the first triggered toolkit applet is guaranteed to be able to send back a response. EVENT_FORMATTED_SMS_PP_UPD Upon reception of a TS 31.115 9 formatted Short Message Point to Poin