1、 ETSI TS 123 048 V4.5.0 (2005-06)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);Security mechanisms for the (U)SIM application toolkit;Stage 2(3GPP TS 23.048 version 4.5.0 Release 4)GLOBAL SYSTEM FOR MOBILE COMMUNICATIO
2、NSRETSI ETSI TS 123 048 V4.5.0 (2005-06) 1 3GPP TS 23.048 version 4.5.0 Release 4 Reference RTS/TSGC-0623048v450 Keywords GSM, 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
3、 non lucratif enregistre 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 d
4、ifference in contents 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 awar
5、e 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 document, please send your comment to one of the following services: htt
6、p:/portal.etsi.org/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 2005. All rights reserved. DECTTM
7、, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organiza
8、tional Partners. ETSI ETSI TS 123 048 V4.5.0 (2005-06) 2 3GPP TS 23.048 version 4.5.0 Release 4 Intellectual 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 availab
9、le 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
10、(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 existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, o
11、r may become, 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
12、 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.org/key/queryform.asp . ETSI ETSI TS 123 048 V4.5.0 (2005-06) 3 3GPP TS 23.048 version 4.5.0 Release 4 Contents Inte
13、llectual Property Rights2 Foreword.2 Foreword.5 1 Scope 6 2 References 6 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .9 4 Overview of Security System.10 5 Generalised Secured Packet structure 11 5.1 Command Packet structure.11 5.1.1 Coding of the SPI12 5.1.2 Coding of the KI
14、c .13 5.1.3 Coding of the KID 13 5.1.4 Counter Management14 5.2 Response Packet structure 15 6 Implementation for SMS-PP 16 6.1 Structure of the UDH of the Security Header in a Short Message Point to Point.16 6.2 A Command Packet contained in a Single Short Message Point to Point 17 6.3 A Command Pa
15、cket contained in Concatenated Short Messages Point to Point17 6.4 Structure of the Response Packet .19 7 Implementation for SMS-CB .20 7.1 Structure of the CBS page in the SMS-CB Message20 7.2 A Command Packet contained in a SMS-CB message.20 7.3 Structure of the Response Packet for a SMS-CB Messag
16、e 21 8 Standardised (U)SIM toolkit commands for Remote File Management21 8.1 Behaviour of the Remote File Management Application .21 8.2 Coding of the commands22 8.2.1 SIM Input Commands.22 8.2.2 SIM Output Commands 22 8.2.3 USIM input commands.22 8.2.4 USIM output commands.23 8.3 SIM specific behav
17、iour for Response Packets (Using SMS-PP)23 8.4 USIM specific behaviour for Response Packets (Using SMS-PP).24 9 Open Platform commands for Remote Applet Management .24 9.1 Remote Applet Management Application behaviour .24 9.1.1 Package Loading.24 9.1.2 Applet Installation 25 9.1.3 Package Removal25
18、 9.1.4 Applet Removal 25 9.1.5 Applet Locking / Unlocking .25 9.1.6 Applet Parameters Retrieval .25 9.2 Commands coding25 9.2.1 Input Commands.25 9.2.2 Output Commands 26 9.3 Response Packets .26 9.3.1 SIM Response Packets26 9.3.2 USIM Response Packets.26 Annex A (normative): Applet Management Comma
19、nds for TS 43.019 compliant cards27 ETSI ETSI TS 123 048 V4.5.0 (2005-06) 4 3GPP TS 23.048 version 4.5.0 Release 4 A.1 Commands Description 27 A.1.1 DELETE.27 A.1.2 GET DATA27 A.1.2.1 Menu Parameters 27 A.1.2.2 Card Resources Information .28 A.1.3 GET STATUS28 A.1.4 INSTALL .28 A.1.4.1 Install (Load
20、) 28 A.1.4.2 Install (Install).29 A.1.4.2.1 Toolkit Applet Specific Parameters 30 A.1.4.2.2 Memory space .30 A.1.4.2.3 Access domain 30 A.1.4.2.3.1 Access Domain Parameter.30 A.1.4.2.3.2 APDU access mechanism31 A.1.4.2.4 Priority level of the Toolkit applet 32 A.1.5 LOAD.32 A.1.6 SET STATUS.33 A.1.7
21、 PUT KEY .33 A.2 Security Management for Applet Management using APDUs 33 A.2.1 Selection of Card Manager and Security Domain 33 A.2.2 Mutual authentication.33 A.2.3 APDUs DAP Computation33 Annex B (informative): Change History 34 History 35 ETSI ETSI TS 123 048 V4.5.0 (2005-06) 5 3GPP TS 23.048 ver
22、sion 4.5.0 Release 4 Foreword 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 TSG modify the contents of the pre
23、sent 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 indicates TSG approved document under ch
24、ange 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. ETSI ETSI TS 123 048 V4.5.0 (2005-06) 6 3GPP TS 23.048 version 4.
25、5.0 Release 4 1 Scope The present document specifies the structure of the Secured Packets in a general format and in implementations using Short Message Service Point to Point (SMS-PP) and Short Message Service Cell Broadcast (SMS-CB). Furthermore, the coding is specified for a set of common applica
26、tion commands within the secured packets. This set is a subset of commands specified in TS 51.011 5 and allows remote management of files on the UICC in conjunction with SMS and the Data Download to UICC feature of TS 31.111. For UICCs based on TS 43.019 15, the set of commands used in the remote ap
27、plet management is defined in the present document. This is based on the Open Platform card management specification 14. For UICCs based on other technologies, other loading mechanisms may be used. The present document is applicable to the exchange of secured packets between an entity in a 3G or GSM
28、 PLMN and an entity in the UICC. Secured Packets contain application messages to which certain mechanisms according to TS 22.048 have been applied. Application messages are commands or data exchanged between an application resident in or behind the 3G or GSM PLMN and on the UICC. The Sending/Receivi
29、ng Entity in the 3G or GSM PLMN and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the presen
30、t 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 the case of a reference to a 3GPP document (
31、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 TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 22.048: “Security mechanisms for the (Universal) Subscriber Interface Module (U)
32、SIM Application Toolkit; Stage 1“. 3 3GPP TS 23.040: “Technical realization of the Short Message Service (SMS)“. 4 3GPP TS 24.011: “Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface“. 5 3GPP TS 51.011: “Specification of the Subscriber Identity Module - Mobile Equipmen
33、t (SIM - ME) interface“. 6 3GPP TS 31.111: “USIM Application Toolkit (USAT)“. 7 ISO/IEC 7816-4: “Information technology - Identification cards - Integrated circuit cards - Part 4: Organization, security and commands for interchange“. 8 ISO/IEC 7816-6: “Information technology - Identification cards -
34、 Integrated circuit cards - Part 6: Interindustry data elements for interchange“. 9 ISO 8731-1 (1987): “Banking - Approved algorithms for message authentication - Part 1: DEA“. 10 ISO/IEC 10116 (1997): “Information technology - Security techniques - Modes of operation for an n-bit block cipher“. 11
35、3GPP TS 23.041: “Technical realization of Cell Broadcast Service (CBS)“. ETSI ETSI TS 123 048 V4.5.0 (2005-06) 7 3GPP TS 23.048 version 4.5.0 Release 4 12 3GPP TS 24.012: “Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface“. 13 3GPP TS 23.038: “Alphabets and language-
36、specific information“. 14 Open Platform Card Specification version 2.0.1 (see http:/www.globalplatform.org/) 15 3GPP TS 43.019: “Subscriber Identity Module Application Programming Interface (SIM API); SIM API for Java Card; Stage 2“. 16 3GPP TS 31.101: “UICC-Terminal Interface, Physical and Logical
37、Characteristics“. 17 Schneier, Bruce: “Applied Cryptography Second Edition: Protocols, Algorithms and Source code in C“, John Wiley the minimum should be 4 octets. Secured Data variable Contains the Secured Application Message and possibly padding octets used for ciphering. Unless indicated otherwis
38、e, the CPL and the CHL shall be coded according to ISO/IEC 7816-6 8. ETSI ETSI TS 123 048 V4.5.0 (2005-06) 123GPP TS 23.048 version 4.5.0 Release 4 Table 2: Linear Representation of Command Packet CPI CPL CHI CHL SPI KIc KID TAR CNTR PCNTR RC/CC/DS Secured Data with Padding note 1 note 1 Note 1 note
39、 1 note 3 note 3 note 2 note 2 note 2 note 2 note 2 note 2 note 2 NOTE 1: These fields are included in the data to be ciphered if ciphering is indicated in the Security Header. NOTE 2: These fields are included in the calculation of the RC/CC/DS. NOTE 3: Part or all of these fields may also be inclu
40、ded in the calculation of the RC/CC/DS, depending on implementation (e.g. SMS). If ciphering is indicated, first the RC/CC/DS shall be calculated as indicated in Note 2, and then ciphering shall be applied, as indicated in Note 1. If the SPI indicates that a specific field is unused, the Sending Ent
41、ity shall set the contents of this field to zero, and the Receiving Entity shall ignore the contents. If the SPI indicates that no RC, CC or DS is present in the Command Header, the RC/CC/DS field shall be of zero length. If the Padding Counter content is zero, this shall indicate no padding octets,
42、 or no padding is necessary. 5.1.1 Coding of the SPI The SPI is coded as below. First Octet: b8 b7 b6 b5 b4 b3 b2 b1 00: No RC, CC or DS 01: Redundancy Check 10: Cryptographic Checksum 11: Digital Signature 0 : No Ciphering 1 : Ciphering 00: No counter available (note 1) 01: Counter available; no re
43、play or sequence checking (note 2) 10: Process if and only if counter value is higher than the value in the RE (note 3) 11: Process if and only if counter value is one higher than the value in the RE (note 4) Reserved (set to zero and ignored by RE) NOTE 1: In this case the counter field is present
44、in the message. NOTE 2: In this case the counter value is used for information purposes only, (e.g. date or time stamp). If the Command Packet was successfully unpacked, the counter value can be forwarded from the Receiving Entity to the Receiving Application. This depends on proprietary implementat
45、ions and happens in an application dependent way. NOTE 3: The counter value is compared with the counter value of the last received Command Packet. This is tolerant to failures on the transport level (i.e. losses of Command Packets). A possible scenario is a global update. NOTE 4: This provides stri
46、ct control in addition to security indicated in note 3. ETSI ETSI TS 123 048 V4.5.0 (2005-06) 133GPP TS 23.048 version 4.5.0 Release 4 Second Octet: b8 b7 b6 b5 b4 b3 b2 b1 00: No PoR reply to the Sending Entity (SE) 01: PoR required to be sent to the SE 10: PoR required only when an error has occur
47、ed 11: Reserved 00: No security applied to PoR response to SE 01: PoR response with simple RC applied to it 10: PoR response with CC applied to it 11: PoR response with DS applied to it 0 : PoR response shall not be ciphered 1 : PoR response shall be ciphered For SMS only 0 : PoR response shall be s
48、ent using SMS-DELIVER-REPORT 1 : PoR response shall be sent using SMS-SUBMIT Reserved (set to zero and ignored by RE) 5.1.2 Coding of the KIc The KIc is coded as below. b8 b7 b6 b5 b4 b3 b2 b1 00: Algorithm known implicitly by both entities 01: DES 10: Reserved 11: proprietary Implementations 00: DE
49、S in CBC mode 01: Triple DES in outer-CBC mode using two different keys 10: Triple DES in outer-CBC mode using three different keys 11: DES in ECB mode indication of Keys to be used (keys implicitly agreed between both entities) DES is the algorithm specified as DEA in ISO 8731-1 9. DES in CBC mode is described in ISO/IEC 10116 10. Triple DES in outer-CBC mode is described in section 15.2 of 17. DES in ECB mode is described in ISO/IEC 10116 10. The initial chaining value for CBC modes shall be zero. If the indication of
