1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelRemote APDU Struc(3GPP TS 31.1TECHNICAL SPECIFICATION131 116 V13.0.0 (2016communications system (Phaelecommunications System (LTE; ucture for (U)SIM Toolkit appli.116 version 13.0.0 Release 1316-02) hase 2+); (UMTS); plications 13) ETSI ETSI TS 13
2、1 116 V13.0.0 (2016-02)13GPP TS 31.116 version 13.0.0 Release 13Reference RTS/TSGC-0631116vd00 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 e
3、nregistre 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 print versions of the present
4、 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 a specific network drive
5、 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 errors in the present do
6、cument, 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
7、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 reserved. DECTTM, PLUGTESTSTM,
8、 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 the GSM Association. ETSI
9、 ETSI TS 131 116 V13.0.0 (2016-02)23GPP TS 31.116 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 available for ETSI members a
10、nd 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/
11、). 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 pres
12、ent 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 interpreted as being ref
13、erences 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“, “need not“, “will“, “will n
14、ot“, “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 116 V13.0.0 (2016-02)33GPP TS 31.116 v
15、ersion 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g34 Remote APDU Format . 6g34.1 Remote command coding . 6g34.2 Response coding . 6g34.2.1 (U)SIM speci
16、fic behaviour for Response Packets (Using SMS-PP) . 6g34.2.2 Void 6g35 Remote File Management (RFM) 6g35.1 SIM Remote File Management 6g35.2 USIM Remote File Management 7g35.3 UICC Shared File System Remote File Management 7g35.4 ISIM Remote File Management . 7g36 Remote Applet Management 7g36.1 SIM
17、 File System Access Domain Parameter 7g36.1.1 SIM Access Mechanism . 8g37 Additional command for push 9g37.1 USIM specific behaviour for responses using SMS-PP . 9g37.2 USIM specific behaviour for response using HTTP . 9g3Annex A (informative): Change History 10g3History 11g3ETSI ETSI TS 131 116 V13
18、.0.0 (2016-02)43GPP TS 31.116 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 continuing work within the TSG and may change following formal TSG approval. Should the
19、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 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indica
20、tes 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 only changes have been incorporated in the document. Introduction The present docume
21、nt is the result of a split of TS 23.048 Release 5 between the generic part and the bearers specific application. The generic part has been transferred to SCP. The present document is the bearers specific part. ETSI ETSI TS 131 116 V13.0.0 (2016-02)53GPP TS 31.116 version 13.0.0 Release 131 Scope Th
22、e present document defines the remote management of files and applets on the SIM/USIM/ISIM. It describes the APDU format for remote management. Furthermore the document specifies: - a set of commands coded according to this APDU structure and used in the remote file management on the SIM/USIM specif
23、ied in TS 51.011 1, TS 31.101 2, TS 31.102 3, TS 31.103 6. - a set of commands coded according to this APDU structure and used in the remote applet management on the SIM/USIM. This is based on ETSI TS 102 226 4. The remote APDU structure for SIM/USIM/ISIM applications shall comply with the one defin
24、ed in ETSI TS 102 226 4. The present document only contains additional requirements or explicit limitations for SIM/USIM/ISIM applications. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are eit
25、her specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a
26、 non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TS 51.011 Release 4: “Specification of the Subscriber Identity Module Mobile Equipment (SIM-ME) interface“. 2 3GPP TS 31.101: “UICC-Terminal Interface; Physical and Lo
27、gical Characteristics“. 3 3GPP TS 31.102: “Characteristics of the USIM Application“. 4 ETSI TS 102 226 V12.0.0: “Smart Cards; Remote APDU structure for UICC based applications“. 5 ISO/IEC 7816-4: “Information technology Identification cards Integrated circuit cards, Part 4: Organization, security an
28、d commands for interchange“. 6 3GPP TS 31.103: “Characteristics of the IP Multimedia Services Identity Module (ISIM) application“. 7 ETSI TS 102 483 V8.1.0: Internet Protocol connectivity between UICC and terminal 3 Definitions and abbreviations For the purposes of the present document, the abbrevia
29、tions, terms and definitions given in ETSI TS 102 226 4 apply. ETSI ETSI TS 131 116 V13.0.0 (2016-02)63GPP TS 31.116 version 13.0.0 Release 134 Remote APDU Format 4.1 Remote command coding The SIM/USIM/ISIM Remote command coding shall comply with the Remote command coding of ETSI TS 102 226 4. 4.2 R
30、esponse coding The SIM/USIM/ISIM Response coding shall comply with the Response coding of ETSI TS 102 226 4, added features are defined below. 4.2.1 (U)SIM specific behaviour for Response Packets (Using SMS-PP) If PoR is not requested, no data shall be returned by the (U)SIM“s RE/RA and the (U)SIM“s
31、 RE/RA shall indicate to the terminal to issue an RP-ACK. If PoR is requested, data shall be returned by the (U)SIM“s RE/RA. The (U)SIM“s RE/RA shall indicate to the terminal to issue an RP-ACK. The data returned by the (U)SIM is the complete Response Packet to be included in the User Data part of t
32、he SMS-DELIVER-REPORT. Because the (U)SIM is unable to indicate to the Terminal that the TP-UDHI bit is to be set, the Sending Entity receiving the Response Packet shall expect the UDH structure in any event. If a proof of Receipt is required by the sending entity, the Additional Response Data sent
33、by the Remote Management Application shall be formatted according to ETSI TS 102 226 4. 4.2.2 Void 5 Remote File Management (RFM) When using remote APDUs to perform RFM over HTTPS, the HTTP header fields shall be set as specified in ETSI TS 102 226 4 5.1 SIM Remote File Management Command and Respon
34、se formats are defined in ETSI TS 102 226 4. Nevertheless, the list of commands defined in ETSI TS 102 226 4 for Remote File Management does not apply for SIM application. All the SIM Remote File Management commands are defined below. The standardised commands are listed in table 5.1. The commands a
35、re as defined in TS 51.011 1, except that the SELECT command is extended from the one in TS 51.011 1 to include “SELECT by path“ as defined in ISO/IEC 7816-4 6. ETSI ETSI TS 131 116 V13.0.0 (2016-02)73GPP TS 31.116 version 13.0.0 Release 13Table 5.1: SIM Remote File Management Commands Operational c
36、ommand SELECT UPDATE BINARY UPDATE RECORD SEEK INCREASE VERIFY CHV CHANGE CHV DISABLE CHV ENABLE CHV UNBLOCK CHV INVALIDATE REHABILITATE READ BINARY READ RECORD To retrieve the Response parameters/data of a case 4 command the GET RESPONSE command defined in TS 51.011 1 shall be issued (Class Byte is
37、 A0). The GET RESPONSE and any case 2 command (i.e. READ BINARY, READ RECORD) shall only occur once in a command string and, if present, shall be the last command in the string. The Response Data shall be placed in the Additional Response Data element of the Response Packet. 5.2 USIM Remote File Man
38、agement USIM Remote File Management shall comply with ETSI TS 102 226 4. The standardised commands are listed in ETSI TS 102 226 4. 5.3 UICC Shared File System Remote File Management UICC Shared File System Remote File Management shall comply with ETSI TS 102 226 4. The standardised commands are lis
39、ted in ETSI TS 102 226 4. 5.4 ISIM Remote File Management ISIM Remote File Management shall comply with ETSI TS 102 226 4. The standardised commands are listed in ETSI TS 102 226 4. 6 Remote Applet Management SIM/USIM Remote Applet Management shall comply with ETSI TS 102 226 4, added features are d
40、efined below. When using remote APDUs to perform RAM over HTTPS, ETSI TS 102 226 4 applies for the HTTP header fields values and the encoding of the body part. 6.1 SIM File System Access Domain Parameter This parameter indicates the mechanism used to control the applet instance access to the SIM Fil
41、e System. It is a parameter of the INSTALL for install command described in ETSI TS 102 226 4. ETSI ETSI TS 131 116 V13.0.0 (2016-02)83GPP TS 31.116 version 13.0.0 Release 13This parameter shall be used only if the “SIM File Access and Toolkit Application Specific Parameters“ TLV object (Tag CA) is
42、present. Value Name Support ADD length 00 See TS 102 226 4 - - 01 SIM access mechanism Optional 2 02 to FF See TS 102 226 4 - - 6.1.1 SIM Access Mechanism This mechanism shall be used, if supported, by the framework if the Access Domain Parameter value is 01. It shall use the Access Domain Data pass
43、ed at applet instantiation to define the access conditions fulfilled while the toolkit applet is running. The APDU Access Domain Data is a bit map combination of the file access condition levels described in TS 51.011 1. When the bit is set the associated Access Condition is granted. The APDU Access
44、 Domain Data is coded as follows: Byte 1: b8 b7 b6 b5 b4 b3 b2 b1 ADM4 ADM5 ADM6 ADM7 ADM8 ADM9 ADM10 RFU Byte 2: b8 b7 b6 b5 b4 b3 b2 b1 ALWays CHV1 CHV2 RFU ADM0 ADM1 ADM2 ADM3 ETSI ETSI TS 131 116 V13.0.0 (2016-02)93GPP TS 31.116 version 13.0.0 Release 13EXAMPLE: Possible combinations of fulfille
45、d Access Conditions are shown below: ADD value Applet access condition fulfilled 00 00 No access 00 01 ALWays 00 02 CHV1 00 03 ALWays and CHV1 00 04 CHV2 00 05 ALWays and CHV2 00 06 CHV1 and CHV2 : : 00 10 ADM0 : : 00 20 ADM1 : : 00 22 ADM1 and CHV1 : : 01 00 ADM4 : : 40 00 ADM10 : : 41 37 ADM10 and
46、 ADM4 and ADM1 and ADM0 and CHV2 and CHV1 and ALWays : : 7 Additional command for push The PUSH command behaviour shall comply with ETSI TS 102 226 4. The specific behaviour of USIM Toolkit applications is stated below. 7.1 USIM specific behaviour for responses using SMS-PP The behaviour for respons
47、es shall comply with ETSI TS 102 226 4. As the processing of the PUSH command may result in proactive commands being issued, the PUSH command result may be sent back in the additional response data of a response packet using SMS-SUBMIT. 7.2 USIM specific behaviour for response using HTTP The behavio
48、ur for responses shall comply with ETSI TS 102 226 4 As the processing of the PUSH command may result in proactive commands being issued, the PUSH command result may be sent back in the additional response data of a response packet using SMS-SUBMIT. The request for a TCP connection allows a remote e
49、ntity to ask an application on the UICC to establish a TCP connection as defined in TS 102 483 7. When Network Access Name, Text String (User Login), Text String (User Password) data object are present in PUSH command, the TCP connection shall be opened with these parameters. When Network Access Name, Text String (User Login), Text String (User Password) data object are not present in PUSH command, the TCP connection shall be opened respectiv
