1、 TIA-1058-B (Revision of TIA-1058-A) August 2014UICC- Terminal Interface Physical and Logical Characteristics for cdma2000 Spread Spectrum Systems NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers a
2、nd purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall not in any respect preclude any member or non-mem
3、ber of TIA from manufacturing or selling products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards and Publications are adopted by TIA i
4、n accordance with the American National Standards Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This Standard does not purport to address all safety pr
5、oblems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. Any use of trademarks in this document are
6、 for information purposes and do not constitute an endorsement by TIA or this committee of the products or services of the company. (From Project No. TIA-PN-1058-B, formulated under the cognizance of the TIA TR-45 Mobile (b) there is no assurance that the Document will be approved by any Committee o
7、f TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Document may involve the use of intellectual property rights (“IPR”), including pending or issue
8、d patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs attention, a statement from the holder thereof is requested, all in accordance with the Manual
9、. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing terms or conditions, which are instead left to the parties involved, nor will TIA opine or j
10、udge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as respects the Document or its contents. If the Document contains one or more Normativ
11、e References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such reference consists of mandatory, alternate or optional elements
12、(as defined in the TIA Procedures for American National Standards) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assurance relating to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (
13、see TIA Procedures for American National Standards Annex C.1.2.3) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of the other SSO shall not constitute identification to TIA of a claim of Essential
14、 Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the contents of the Document. ALL WARRANTIES,
15、 EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESS
16、LY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUME
17、NT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDIN
18、G DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL EL
19、EMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. 3GPP2 C.S0074-B v1.0 Revision History Revision Description Date C.S0074-0 Release 0 December 2005 C.S0074-0 v1.0 Replacement Text February 2009 C.S0074-A Revision A January 2010 C.S007
20、4-B Revision B July 2014 3GPP2 C.S0074-B v1.0 i Contents 1 1 Introduction . 1 2 1.1 Scope 1 3 1.2 Document Conventions 1 4 1.3 Definitions, Symbols, Abbreviations . 1 5 1.4 References . 2 6 2 UICC-Terminal Interface; Physical and Logical Characteristics 3 7 3 Application Independent Files 4 8 3.1 DF
21、MMSS(Multimode System Selection) . 4 9 3.1.1 EFMLPL(MMSS Location Associated Priority List) . 4 10 3.1.2 EFMSPL(MMSS System Priority List) . 5 11 3.1.3 EFMMSSMODE(MMSS Mode Settings) . 5 12 4 Application Dependent Files 6 13 4.1 Files at CSIM ADF level and USIM ADF level 6 14 4.1.1 EFFDN(Fixed Diall
22、ing Number) 6 15 Annex A (Normative) List of SFI Values and File Structure of DFMMSS7 16 Annex B (Informative) Suggested Contents of Application Independent EFs at Pre-Personalization . 8 17 18 19 3GPP2 C.S0074-B v1.0 Tables 1 Table 1.1 Convention for Numbers and Strings . 1 2 Table A-1 SFI values f
23、or EFs under DFMMSS. 7 3 Table B-1 Summary of Application Independent EF . 8 4 5 6 3GPP2 C.S0074-B v1.0 iii Foreword 1 (This foreword is not part of this specification) 2 This document was prepared by 3GPP2 TSG-C WG1. 3 The present document specifies the interface between the UICC and the Terminal f
24、or 4 cdma20001network operation. 5 The present document specifies: 6 the requirements for the physical characteristics of the UICC; 7 the electrical interface between the UICC and the Terminal; 8 the initial communication establishment and the transport protocols; 9 the model which serves as a basis
25、 for the logical structure of the UICC; 10 the communication commands and the procedures; 11 the application-independent files and protocols. 12 The handling of application dependent files in a multi-radio access technology 13 environment. 14 The administrative procedures and initial card management
26、 are not part of the present 15 document. 16 17 1cdma2000is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of publication), cdma2000 is a registered trademark of the Telecommunica
27、tions Industry Association (TIA-USA) in the United States. 3GPP2 C.S0074-B v1.0 iv This page intentionally left blank 1 3GPP2 C.S0074-B v1.0 1 1 Introduction 1 2 1.1 Scope 3 The present document defines a generic Terminal/Integrated Circuit Card (ICC) interface for 4 cdma2000 applications. The prese
28、nt document is based on 1, which defines a generic platform 5 for any IC card application. Requirements that are common to all cdma2000 smart card based 6 applications are also listed in this specification. 7 The aim of the present document is to ensure interoperability between an ICC and a terminal
29、 8 independently of the respective manufacturer, card issuer or operator. The present document 9 does not define any aspects related to the administrative management phase of the ICC. Any 10 internal technical realization of either the ICC or the terminal is only specified where these are 11 reflect
30、ed over the interface. 12 Application specific details for applications residing on an ICC are specified in the respective 13 application specific documents. 14 References to this document from cdma2000 application specifications related to functionalities 15 that are not described in the present do
31、cument are to be considered as direct references to 1. 16 1.2 Document Conventions 17 “Shall” and “shall not” identify requirements to be followed strictly to conform to this 18 document and from which no deviation is permitted. “Should” and “should not” indicate 19 that one of several possibilities
32、 is recommended as particularly suitable, without 20 mentioning or excluding others, that a certain course of action is preferred but not 21 necessarily required, or that (in the negative form) a certain possibility or course of action 22 is discouraged but not prohibited. “May” and “need not” indic
33、ate a course of action 23 permissible within the limits of the document. “Can” and “cannot” are used for statements 24 of possibility and capability, whether material, physical or causal. 25 The following table describes the conventions used for decimal numbers, non-decimal 26 numbers and strings. 2
34、7 Table 1.1 Convention for Numbers and Strings 28 Convention Description nnnnn A decimal number, e.g. CHV or phone number hh A single octet hexadecimal number hhhhhhhhhh A multi-octet hexadecimal number or string “SSSS” Character string Note: If an X is present in a hexadecimal number then that digi
35、t is “dont care”. 1.3 Definitions, Symbols, Abbreviations 29 All definitions, symbols, abbreviations applicable to the UICC-terminal interface in CDMA 30 Spread Spectrum Systems are specified in 1. 31 3GPP2 C.S0074-B v1.0 2 1.4 References 1 The following standards are referenced in this text. At the
36、 time of publication, the editions 2 indicated were valid. All standards are subject to revision, and parties to agreements based 3 upon this document are encouraged to investigate the possibility of applying the most recent 4 editions of the standards indicated below. ANSI and TIA maintain register
37、s of currently valid 5 national standards published by them. 6 Normative References: 7 1. ETSI TS 102 221 v11.1.0, Smart Cards; UICC-Terminal interface; Physical and logical 8 characteristics, November 2013. 9 2. 3GPP TS 31.101 v11.0.0, UICC-Terminal interface; Physical and logical characteristics,
38、10 September 2012. 11 3. 3GPP2 C.S0016-D v2.0, Over-The-Air Service Provisioning of Mobile Station in Spread 12 Spectrum Systems, April 2012. 13 4. 3GPP2 C.S0079-0 v1.0, Remote APDU Structure for CDMA Card Application Toolkit (CCAT) 14 Applications, October 2006. 15 5. 3GPP2 C.S0065-C v1.0, cdma2000
39、 Application on UICC for Spread Spectrum Systems, 16 TBD 2014. 17 6. 3GPP TS 31.102 v12.2.0, Characteristics of the Universal Subscriber Identity Module (USIM) 18 application, December 2013. 19 3GPP2 C.S0074-B v1.0 3 2 UICC-Terminal Interface; Physical and Logical 1 Characteristics 2 The UICC-Termin
40、al interface in the context of CDMA Spread Spectrum systems shall comply 3 with all requirements specified in 2. “3GPP“ shall be interpreted as “3GPP2“ in the context of 4 CDMA Spread Spectrum System.5 3GPP2 C.S0074-B v1.0 4 3 Application Independent Files 1 2 3.1 DFMMSS(Multimode System Selection)
41、3 If Multimode System Selection (MMSS) is supported by UICC, DFMMSS5F3C shall be present 4 under DFTELECOM. If an ME supports MMSS, it shall select DFMMSSand read the parameters and 5 settings from the EFs under DFMMSS. The parameters and settings which are present in the EFs 6 under DFMMSSshall tak
42、e precedence over the ones present in the terminal it is inserted to. 7 The following EFs can use various provisioning mechanisms such as: the standard Remote File 8 Management procedures defined for UICC as defined in 4, for updating and modifications, and 9 the commands, e.g., OTASP/OTAPA related
43、commands defined in 5. 10 3.1.1 EFMLPL(MMSS Location Associated Priority List) 11 This EF stores the Multimode System Selection Location Associated Priority List as defined in 12 section 3.5.13.3 of 3. 13 Identifier: 4F20 Structure: transparent Optional SFI: 01 File size: X bytes Update activity: Lo
44、w Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM Bytes Description M/O Length 1 to X MLPL as defined in 3 M X bytes MLPL: This is the MMSS Location Associated Priority List 14 Coding: See 4.5.11.2 of 3 15 Unused bytes shall be set to FF. 16 This EF is stored using the convention
45、from 3, i.e. fields are placed into octets starting with 17 the MSB of the first field into bit 8 of the first octet, followed by the remaining fields placed in 18 sequence into the remaining bits allocated for those fields. A multi-octet integer is stored by 19 placing the octet with the MSB into t
46、he lowest numbered available octet allocated for that 20 integer in the EF. 21 3GPP2 C.S0074-B v1.0 5 3.1.2 EFMSPL(MMSS System Priority List) 1 This EF Stores the Multimode System Selection System Priority List as defined in section 2 3.5.13.4 of 3. 3 Identifier: 4F21 Structure: transparent Optional
47、 SFI: 02 File size: X bytes Update activity: Low Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM Bytes Description M/O Length 1 to X MSPL as defined in 3 M X bytes MSPL: This is the MMSS System Priority List 4 Coding: See 4.5.11.3 of 3 5 Unused bytes shall be set to FF 6 This EF i
48、s stored using the convention from 3, i.e. fields are placed into octets starting with 7 the MSB of the first field into bit 8 of the first octet, followed by the remaining fields placed in 8 sequence into the remaining bits allocated for those fields. A multi-octet integer is stored by 9 placing th
49、e octet with the MSB into the lowest numbered available octet allocated for that 10 integer in the EF. 11 3.1.3 EFMMSSMODE(MMSS Mode Settings) 12 This EF stores the Multimode System Selection Mode Settings as defined in section 3.5.13.2 of 13 3. 14 Identifier: 4F22 Structure: transparent Optional SFI: 03 File size: 1 byte Update activity: Low Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM Bytes Description M/O Length 1 MMSS Mode Settings as defined in 3 M 1 byte This EF is stored using t
