1、 TIA-4978 January 2013cdma2000Application (CSIM) Conformance Testing for Spread Spectrum Systems NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and
2、 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-member of TIA from manufacturing or selling products
3、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 in accordance with the American National Standards
4、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 problems associated with its use or all applicable r
5、egulatory 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. (From Project No. TIA-PN-4978, formulated under the cognizance of the TIA TR-45 Mobile (b) t
6、here is no assurance that the Document will be approved by any Committee of 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 t
7、he use of intellectual property rights (“IPR”), including pending or issued 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 stateme
8、nt from the holder thereof is requested, all in accordance with the Manual. 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 condition
9、s, which are instead left to the parties involved, nor will TIA opine or judge 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 t
10、he Document or its contents. If the Document contains one or more Normative 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), whe
11、ther such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) 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 Referenc
12、e; (ii) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) 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 identificat
13、ion to TIA of a claim of Essential 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 content
14、s of the Document. ALL WARRANTIES, 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 INTELLE
15、CTUAL PROPERTY RIGHTS. TIA EXPRESSLY 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
16、 SERVICE REFERRED TO IN THE DOCUMENT 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
17、OR CONSEQUENTIAL DAMAGES (INCLUDING 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 NEGAT
18、ION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. 3GPP2 C.S0107-0 v1.0 Revision History Revision Description of Changes Date Rev 0 v1.0 Initial release, v1.0 December 2012 3GPP2 C.S0107-0 v1.0 i Table
19、 of Contents 1 1 Introduction . 1-1 2 1.1 Scope . 1-1 3 1.2 Document Conventions 1-1 4 1.2.1 Requirements Language 1-1 5 1.2.2 Numbers and Strings 1-1 6 1.3 Terminology . 1-2 7 1.3.1 Definitions 1-2 8 1.3.2 Acronyms . 1-2 9 1.4 References . 1-3 10 1.4.1 Normative References . 1-3 11 2 CSIM Test Envi
20、ronment 2-1 12 2.1 Test Equipment 2-1 13 2.2 Common Initial Conditions . 2-1 14 2.3 Test Procedure . 2-2 15 2.4 Mapping of CSIM to USIM 2-3 16 2.5 Recommended Practice 2-4 17 2.6 Applicability . 2-4 18 2.6.1 Applicability of the Present Document . 2-4 19 2.6.2 Applicability of the Individual Tests .
21、 2-4 20 3 Files . 3-1 21 3.1 Contents of Files at the MF Level 3-1 22 3.2 Contents of Files at the CSIM ADF Level . 3-2 23 3.3 Contents of DFs at the CSIM ADF Level 3-5 24 3.4 Reserved 3-7 25 3.5 Reserved 3-7 26 4 Interworking of R-UIM and CSIM on a UICC 4-1 27 4.1 R-UIM/CSIM Interaction and Restric
22、tions. 4-1 28 5 Application Protocol 5-1 29 3GPP2 C.S0107-0 v1.0 ii 5.1 CSIM Management Procedures . 5-1 1 5.1.1 Initialization . 5-1 2 5.1.1.1 CSIM Application Selection . 5-1 3 5.1.1.1.1 SELECT by DF Name 5-1 4 5.1.1.1.2 SELECT by Partial DF Name . 5-2 5 5.1.1.2 CSIM Initialization 5-4 6 5.1.1.2.1
23、 Application Session Activation . 5-4 7 5.1.1.2.2 Application Session Reset 5-6 8 5.1.2 Session Termination . 5-7 9 6 Structure of Commands and Responses 6-1 10 6.1 Command APDU Structure . 6-1 11 6.1.1 Mapping Principles . 6-1 12 6.2 Response APDU Structure 6-1 13 6.2.1 Status Conditions Returned b
24、y the UICC 6-1 14 7 Commands . 7-1 15 7.1 Generic Commands 7-1 16 7.1.1 SELECT 7-1 17 7.1.2 STATUS 7-1 18 7.1.3 READ BINARY 7-1 19 7.1.4 UPDATE BINARY 7-1 20 7.1.5 READ RECORD 7-1 21 7.1.6 UPDATE RECORD 7-2 22 7.1.7 SEARCH RECORD 7-2 23 7.1.8 INCREASE 7-2 24 7.1.9 VERIFY PIN 7-3 25 7.1.10 CHANGE PIN
25、 7-3 26 7.1.11 DISABLE PIN 7-4 27 7.1.12 ENABLE PIN . 7-4 28 7.1.13 UNBLOCK PIN 7-4 29 7.1.14 DEACTIVATE FILE 7-4 30 3GPP2 C.S0107-0 v1.0 iii 7.1.15 ACTIVATE FILE 7-4 1 7.1.16 AUTHENTICATE . 7-4 2 7.1.17 MANAGE CHANNEL 7-4 3 7.1.18 GET CHALLENGE . 7-4 4 7.2 Reserved 7-5 5 7.3 Data Oriented Commands
26、7-5 6 7.3.1 RETRIEVE DATA 7-5 7 7.3.2 SET DATA 7-5 8 7.3.3 BER-TLV Structure Files . 7-5 9 7.3.4 Logical Channel Interactions . 7-5 10 7.4 CSIM Commands . 7-5 11 7.4.1 Security-related Commands 7-5 12 7.4.1.1 Manage SSD. 7-5 13 7.4.1.1.1 Update 7-5 14 7.4.1.1.2 Confirm 7-7 15 7.4.1.2 Base Station Ch
27、allenge . 7-11 16 7.4.1.3 Generate Key/VPM . 7-12 17 7.4.1.4 Authenticate 7-14 18 7.4.1.4.1 Authenticate - Run CAVE 7-14 19 7.4.1.4.2 Reserved . 7-17 20 7.4.1.4.3 Reserved . 7-17 21 7.4.2 OTASP-related Commands 7-18 22 7.4.2.1 Generic Key Generation 7-18 23 7.4.2.1.1 MS Key Request 7-18 24 7.4.2.1.2
28、 Key Generation Request 7-20 25 7.4.2.1.3 Reserved . 7-25 26 7.4.2.2 Commit 7-25 27 7.4.2.3 Validate . 7-26 28 7.4.2.4 Generic Configuration Request . 7-33 29 7.4.2.4.1 Configuration Request . 7-33 30 7.4.2.4.2 SSPR Configuration Request for CSIM supporting 31 SSPR_P_REV = 01 only 7-37 32 3GPP2 C.S0
29、107-0 v1.0 iv 7.4.2.4.3 SSPR Configuration Request for CSIM supporting 1 SSPR_P_REV = 03 7-41 2 7.4.2.4.4 Reserved . 7-47 3 7.4.2.4.5 Reserved . 7-48 4 7.4.2.4.6 Reserved . 7-48 5 7.4.2.4.7 Reserved . 7-48 6 7.4.2.4.8 Reserved . 7-48 7 7.4.2.5 Generic Download Request . 7-48 8 7.4.2.5.1 Download Req
30、uest 7-48 9 7.4.2.5.2 SSPR Download Request . 7-55 10 7.4.2.5.3 Reserved . 7-61 11 7.4.2.5.4 Reserved . 7-61 12 7.4.2.5.5 Reserved . 7-61 13 7.4.2.5.6 Reserved . 7-61 14 7.4.2.5.7 Reserved . 7-61 15 7.4.2.6 OTAPA Request 7-61 16 7.4.2.7 Secure Mode 7-67 17 7.4.2.8 Fresh . 7-69 18 7.4.3 ESN Managemen
31、t Commands . 7-70 19 7.4.3.1 Store ESN_MEID_ME 7-70 20 7.4.4 Packet Data security-related Commands . 7-73 21 7.4.4.1 Compute IP Authentication . 7-73 22 7.4.4.1.1 CHAP 7-73 23 7.4.4.1.2 MN-HA Authenticator 7-74 24 7.4.4.1.3 MIP-RRQ Hash 7-79 25 7.4.4.1.4 MN-AAA Authenticator 7-86 26 7.4.4.1.5 HRPD A
32、ccess Authentication . 7-90 27 7.4.5 BCMCS-related Commands . 7-91 28 7.4.5.1 BCMCS 7-91 29 7.4.5.1.1 Reserved . 7-91 30 7.4.5.1.2 Reserved . 7-91 31 7.4.5.1.3 Reserved . 7-92 32 3GPP2 C.S0107-0 v1.0 v 7.4.5.1.4 Reserved . 7-92 1 7.4.5.1.5 Reserved . 7-92 2 7.4.5.1.6 Reserved . 7-92 3 7.4.6 Applicat
33、ion Authentication Commands . 7-92 4 7.4.6.1 Reserved 7-92 5 7.4.7 AKA-related Commands 7-92 6 7.4.7.1 Reserved 7-92 7 7.4.7.2 Reserved 7-92 8 7.4.8 LCS-related Commands 7-92 9 7.4.8.1 Reserved 7-92 10 7.4.8.2 Reserved 7-92 11 7.4.8.3 Reserved 7-92 12 7.4.8.4 Reserved 7-92 13 7.4.9 Start of an OTASP
34、 Session 7-93 14 7.4.10 CSIM Security Related Functions 7-94 15 7.5 Transmission Oriented Commands . 7-95 16 7.5.1 T=0 Specific Commands 7-95 17 7.5.1.1 GET RESPONSE . 7-95 18 Annex A Informative Applicability Matrix . A-1 19 Annex B Informative Table of Parameters for the DOWNLOAD REQUEST Test Case
35、 B-1 20 3GPP2 C.S0107-0 v1.0 vi Table of Tables 1 Table 1 Conventions for Numbers and Strings . 1-1 2 Table 2 CSIM/USIM Mapping Table 2-3 3 Table 3 Definition of CSIM_P_REV 2-4 4 Table 4 Parameters for “MS KEY REQUEST” Test Procedure 7-19 5 Table 5 Parameters for “KEY GENERATION REQUEST” Test Proced
36、ure 7-22 6 Table 6 Applicability Matrix A-1 7 Table 7 PARAM_DATA for BLOCK_ID = 00 (CDMA/Analog NAM) B-1 8 Table 8 PARAM_DATA for BLOCK_ID = 02 (CDMA NAM) B-2 9 Table 9 PARAM_DATA for BLOCK_ID = 03 (IMSI_T) B-3 10 3GPP2 C.S0107-0 v1.0 vii Foreword 1 This foreword is not part of this document. 2 This
37、 specification was prepared by the Third Generation Partnership Project 2 (3GPP2). The 3 specification is applicable to all revisions of the cdma20001application (CSIM) although it only 4 references the latest revision 1. 5 The test cases defined in this specification are primarily designed to test
38、the conformance of 6 CSIM with revision B of the C.S0065. They may be used to test other revisions of the CSIM. 7 Specific tests dedicated to further revisions may be added to this document in a future point 8 release or revision. 9 The CSIM for cdma2000Spread Spectrum Standards Conformance Test Spe
39、cification is based 10 on UICC related tests as per 3. 11 This document has reserved sections for tests of further CSIM specific commands. These tests 12 may be added to this document in a later point release or revision. 13 1cdma2000is the trademark for the technical nomenclature for certain specif
40、ications and standards of the Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of publication), cdma2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States. 3GPP2 C.S0107-0 v1.0 viii This page intentionally left blank. 1
41、3GPP2 C.S0107-0 v1.0 1-1 1 INTRODUCTION 1 1.1 SCOPE 2 The present document provides the Conformance Test Specification for the cdma20003 application on a UICC (CSIM) used in cdma2000Spread Spectrum Systems. 4 The UICC may optionally support additional wireless technologies (such as GSM or UMTS). 5 C
42、ompliance testing for these additional technologies is outside the scope of this document. If 6 the UICC supports other additional applications for wireless technologies, the applications 7 shall comply with the functional and test specifications specific to that wireless technology. 8 This document
43、 does not specify which test cases are mandatory or optional. However, to 9 successfully execute a particular test case, its corresponding test requirements and procedures 10 as defined in this document shall be followed. 11 1.2 DOCUMENT CONVENTIONS 12 1.2.1 Requirements Language 13 “Shall” and “sha
44、ll not” identify requirements to be followed strictly to conform to this document 14 and from which no deviation is permitted. “Should” and “should not” indicate that one of 15 several possibilities is recommended as particularly suitable, without mentioning or excluding 16 others, that a certain co
45、urse of action is preferred but not necessarily required, or that (in the 17 negative form) a certain possibility or course of action is discouraged but not prohibited. “May” 18 and “need not” indicate a course of action permissible within the limits of the document. “Can” 19 and “cannot” are used f
46、or statements of possibility and capability, whether material, physical 20 or causal. 21 1.2.2 Numbers and Strings 22 The following table describes the conventions used for decimal numbers, non-decimal numbers 23 and strings. 24 Table 1 Conventions for Numbers and Strings 25 Convention Description n
47、nnnn A decimal number, e.g. CHV or phone number b A single digit binary number bbbbbbbb An 8-bit binary number hh A single octet hexadecimal number hh hh hhhh hh A multi-octet hexadecimal number or string “SSSS” Character string Note: If an X is present in a binary or hexadecimal number, then that d
48、igit is “dont care”. “Bn” represents Byte n of the coding starting from left to right, i.e. MSB to LSB. “bn” represents 26 Bit n of the byte starting from right to left, i.e. LSB to MSB. 27 3GPP2 C.S0107-0 v1.0 1-2 1.3 TERMINOLOGY 1 1.3.1 Definitions 2 For the purposes of the present document, the t
49、erms and definitions in 1 apply. 3 1.3.2 Acronyms 4 For the purposes of the present document, the following abbreviations apply: 5 3GPP2 3rd Generation Partnership Project 2 6 ADF Application Dedicated File 7 APDU Application Protocol Data Unit 8 CRn Conformance Requirement n 9 CSIM cdma2000 Application on a UICC 10 DF Dedicated File 11 DO Data Object 12 EF Elementary File 13 FCP File Control Parameter 14 ME Mobile Equipment 15 MF Master File 16 MS Mobile Station 17 PIN Personal Identification Number 18 PIX Proprietary Applicatio
