TIA-1013-B-2014 Mobile Equipment (ME) Conformance Testing with R-UIM for cdma2000 Spread Spectrum Standards.pdf

《TIA-1013-B-2014 Mobile Equipment (ME) Conformance Testing with R-UIM for cdma2000 Spread Spectrum Standards.pdf》由会员分享，可在线阅读，更多相关《TIA-1013-B-2014 Mobile Equipment (ME) Conformance Testing with R-UIM for cdma2000 Spread Spectrum Standards.pdf（144页珍藏版）》请在麦多课文档分享上搜索。

1、 TIA-1013-B (Revision of TIA-1013-A) February 2014Mobile Equipment (ME) Conformance Testing with R-UIM for cdma2000 Spread Spectrum Standards NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and pu

2、rchasers, 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-member o

3、f 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 in acc

4、ordance 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 problem

5、s 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. (From Project No. TIA-PN-1013-B-D1, formulated

6、under the cognizance of the TIA TR-45 Mobile (b) there 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 p

7、ractice of contents of this Document may involve the 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 a

8、re claimed and called to TIAs attention, a statement 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

9、to discussions of any licensing terms or conditions, 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 i

10、n the Manual have been complied with as respects the 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

11、, specification, recommendation or otherwise), whether 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

12、 assurance relating to any such Normative Reference; (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

13、 of the other SSO shall not constitute identification 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 ser

14、vices or any claims of compliance with the contents 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 A

15、ND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL 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 O

16、R HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR 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 LIM

17、ITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL 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 TH

18、E POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION 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.S0048-B v1.0 Revision History Revision Description of Changes Date Rev 0 v1.0 Publication Ju

19、ly 2008 Rev A v1.0 Publication October 2010 Rev A v2.0 Publication December 2012 Rev A v2.0 This document was republished to add a trademark acknowledgment March 2013 Rev B v1.0 Publication January 2014 3GPP2 C.S0048-B v1.0 i Table of Contents 1 1 Introduction 1-1 2 1.1 Scope 1-1 3 1.2 Document Conv

20、entions 1-1 4 1.2.1 Requirements Language 1-1 5 1.2.2 Numbers . 1-1 6 1.3 Terminology 1-2 7 1.3.1 Acronyms 1-2 8 1.4 References . 1-3 9 1.4.1 Normative References 1-3 10 2 Reserved 4-1 11 3 Reserved 4-1 12 4 ME Test Environment 4-1 13 5 Testing of the ME . 5-1 14 5.1 Definition of Default Values for

21、 R-UIM/ME Interface Testing . 5-1 15 5.1.1 EFCST(CDMA Service Table) 5-1 16 5.1.2 EFUSGIND(UIMID/SF_EUMID Usage Indicator) . 5-3 17 5.1.3 EFIMSI_M (IMSI_M) 5-3 18 5.1.4 EFESNME(ESN_ME) . 5-3 19 5.1.5 EFCDMAHOME(CDMA Home SID, NID) . 5-3 20 5.1.6 CHV1 5-5 21 5.1.7 CHV2 5-5 22 5.1.8 UNBLOCK CHV1 5-5 2

22、3 5.1.9 UNBLOCK CHV2 5-5 24 5.1.10 EFADN(Abbreviated Dialing Number) 5-5 25 5.1.11 EFFDN(Fixed Dialing Numbers) . 5-6 26 5.1.12 EFSMSCAP(SMS Capabilities). 5-7 27 5.1.13 EFSMSP(SMS Parameters) 5-7 28 5.1.14 EFSIPUPP(Simple IP User Profile Parameters) 5-7 29 5.1.15 EF3GPDUPPExt (3GPD User Profile Par

23、ameters Extension) . 5-8 30 3GPP2 C.S0048-B v1.0 ii 5.1.16 EFSIPPAPSS(Simple IP PAP SS) . 5-8 1 5.1.17 Simple IP CHAP SS 5-8 2 5.1.18 EFDGC(Data Generic Configurations) . 5-8 3 5.1.19 EFMIPUPP(Mobile IP User Profiles) 5-8 4 5.1.20 Void . 5-9 5 5.1.21 Mobile IP SS . 5-9 6 5.1.22 EFMIPFlags(Mobile IP

24、Flags) . 5-9 7 5.1.23 EF3GPDOPM(3GPD Operation Mode) . 5-9 8 5.1.24 EFSPN(CDMA Home Service Provider Name) 5-10 9 5.1.25 EFAppLabels(Application Labels) 5-10 10 5.1.26 EFModel(Device Model Information) . 5-10 11 5.1.27 EFECC(Emergency Call Codes) 5-11 12 5.1.28 EFHRPDCAP(HRPD Capabilities) . 5-11 13

25、 5.1.29 EFHRPDUPP(HRPD Access Authentication User Profile Parameters) 5-11 14 5.1.30 HRPD Access Authentication CHAP SS 5-11 15 5.1.31 EFWAPBrowserCP(WAP Browser Connectivity Parameters) 5-11 16 5.1.32 EFWAPBrowserBM(WAP Browser Bookmarks) . 5-12 17 5.1.33 EFMMSN(MMS Notification) . 5-13 18 5.1.34 E

26、FMMSICP(MMS Issuer Connectivity Parameters) . 5-13 19 5.1.35 EFMMSUP(MMS User Preferences) 5-14 20 5.1.36 EFMMSConfig(MMS Configuration) . 5-14 21 5.1.37 EFJDL(Java Download URL) . 5-14 22 5.1.38 EFRC(Root Certificates) 5-15 23 5.1.39 EFSP(Service Preferences) 5-15 24 5.1.40 EFPRL(Preferred Roaming

27、List) 5-15 25 5.1.41 EFMAXPRL(Max Preferred Roaming List) . 5-16 26 5.1.42 EFOTA(OTASP/OTAPA Features) 5-17 27 5.1.43 EFNAMLOCK(NAM_LOCK) 5-17 28 5.1.44 EFOTAPASPC(OTAPA/SPC_Enable) . 5-17 29 5.1.45 EFEPRL(Extended Preferred Roaming List) 5-17 30 5.2 Common Initial Conditions 5-20 31 3GPP2 C.S0048-B

28、 v1.0 iii 6 ME Test Procedures 6-1 1 6.1 MS Identification . 6-1 2 6.1.1 Mobile Station Identifier 6-1 3 6.1.2 MS Displaying the Roaming Indicator. 6-2 4 6.2 UIMID/ESN_ME Selection 6-5 5 6.2.1 Removable UIMID Usage Indicator 6-5 6 6.2.2 ESN Management. 6-6 7 6.2.3 MEID Management . 6-6 8 6.2.4 EUIMI

29、D and MEID 6-7 9 6.3 Security-related commands 6-8 10 6.3.1 SSD Update 6-8 11 6.3.2 Authentication Calculation for Global Challenge 6-9 12 6.3.3 Unique Challenge While the Mobile Station is in Idle State . 6-9 13 6.3.4 Unique Challenge While the Mobile Station is in Mobile Station Control on the 14

30、Traffic Channel State . 6-10 15 6.3.5 Generate Key/VPM . 6-11 16 6.3.6 Authentication . 6-12 17 6.4 OTASP/OTAPA Functionality . 6-13 18 6.4.1 PRL Download 6-13 19 6.4.2 OTASP/OTAPA Commands . 6-14 20 6.4.3 EPRL Download 6-15 21 6.5 Reserved 6-17 22 6.6 Reserved 6-17 23 6.7 Reserved 6-17 24 6.8 Reser

31、ved 6-17 25 6.9 Reserved 6-17 26 6.10 Exchange Protocol Tests 6-18 27 3GPP2 C.S0048-B v1.0 iv 6.11 Evaluation of Directory Characteristics. 6-19 1 6.11.1 Operating Speed in Authentication Procedure . 6-19 2 6.11.2 Clock Stop . 6-19 3 6.11.3 Reserved . 6-21 4 6.12 Mechanical Tests 6-22 5 6.13 Secret

32、Code Usage 6-23 6 6.13.1 Entry of CHV1 . 6-23 7 6.13.2 Change of CHV1 . 6-23 8 6.13.3 Disabling the CHV1. 6-23 9 6.13.4 UNBLOCK CHV1 Entry 6-23 10 6.13.5 Entry of CHV2 . 6-24 11 6.13.6 Change of CHV2 . 6-24 12 6.13.7 UNBLOCK CHV2 Entry 6-24 13 6.13.8 Reserved . 6-24 14 6.14 Abbreviated Dialing Numbe

33、r (ADN) 6-25 15 6.15 UI Reaction to R-UIM Status Encoding 6-27 16 6.16 Electrical Tests . 6-28 17 6.17 Fixed Dialing Number (FDN) 6-29 18 6.18 Version Identification 6-30 19 6.19 R-UIM Presence Detection . 6-31 20 6.20 Reserved 6-32 21 6.21 Suggested Slot Cycle Index . 6-33 22 6.22 Service Provider

34、Name . 6-35 23 6.23 CDMA Service Table 6-36 24 6.24 Application Labels. 6-38 25 6.24.1 Application Labels Present on R-UIM . 6-38 26 6.24.2 Application Labels Not Present on R-UIM 6-38 27 6.25 Device Model Information . 6-40 28 3GPP2 C.S0048-B v1.0 v 6.26 Emergency Numbers 6-41 1 6.27 SMS Capabiliti

35、es 6-42 2 6.27.1 SMS Retries 6-42 3 6.27.2 Sending SMS on Access Channel 6-43 4 6.27.3 Sending SMS on Traffic Channel . 6-45 5 6.27.4 Sending EMS messages 6-47 6 6.28 SMS Messages on R-UIM 6-49 7 6.28.1 Automatically Storing Received SMS in R-UIM 6-49 8 6.28.2 Saving SMS in R-UIM . 6-50 9 6.28.3 Rea

36、ding SMS from R-UIM 6-51 10 6.28.4 Deleting SMS in R-UIM . 6-52 11 6.29 SMS Parameters on R-UIM 6-54 12 6.29.1 Saving SMS Parameters in R-UIM . 6-54 13 6.29.2 Reading SMS Parameters in R-UIM . 6-54 14 6.29.3 Deleting SMS Parameters in R-UIM . 6-55 15 6.30 SMS Status on R-UIM 6-56 16 6.31 Simple IP 6

37、-57 17 6.31.1 PAP and CHAP Authentication . 6-57 18 6.31.2 Multiple User Profiles 6-58 19 6.31.3 Prioritization among User Profiles 6-60 20 6.32 Mobile IP . 6-64 21 6.32.1 Mobile IP Registration Retries 6-64 22 6.32.2 Mobile IP Re-registration Threshold . 6-65 23 6.32.3 Mobile IP to Simple IP Fallba

38、ck 6-65 24 6.32.4 Mobile IP MN-HA 2002bis Authentication 6-66 25 6.32.5 Mobile IP Pre Rev 6 Handoff Optimization . 6-67 26 6.32.6 Mobile IP PPP Re-sync during Hand-down from 1xEV-DO Rev 0 to 1x 6-68 27 6.32.7 Mobile IP Re-registration for Extending Mobile IP address lifetime . 6-69 28 3GPP2 C.S0048-

39、B v1.0 vi 6.33 Data Configurations 6-71 1 6.33.1 Data Dormant Mode Timer . 6-71 2 6.33.2 Hysteresis Activation Time . 6-71 3 6.33.3 EPZID . 6-72 4 6.34 HRPD Access Authentication . 6-74 5 6.35 WAP Browser Connectivity Parameters . 6-75 6 6.36 WAP Browser Bookmarks 6-76 7 6.37 MMS Issuer Connectivity

40、 Parameters 6-78 8 6.38 MMS Configurations . 6-80 9 6.38.1 Maximum Message Size . 6-80 10 6.38.2 MMS Retries . 6-81 11 6.38.3 MMSC Timeout . 6-82 12 6.39 MMS Notifications . 6-84 13 6.39.1 Reading and Using MMS Notification in R-UIM 6-84 14 6.39.2 Automatically Storing MMS Notification in R-UIM 6-85

41、 15 6.39.3 Forwarding MMS Notifications 6-86 16 6.39.4 Deleting MMS Notification from R-UIM . 6-87 17 6.40 MMS User Preferences 6-89 18 6.40.1 Reading and Using MMS User Preferences . 6-89 19 6.40.2 Updating MMS User Preferences . 6-89 20 6.41 Root Certificates . 6-91 21 6.42 Java 6-93 22 Annex A -

42、Informative Applicability Matrix 1 23 3GPP2 C.S0048-B v1.0 vii Table of Figures 1 Figure 1. ME Test Environment 4-1 2 3GPP2 C.S0048-B v1.0 viii Table of Tables 1 Table 1. Default Values for EFCST. 5-1 2 Table 2. Applicability Matrix of Test Cases for the Different Revisions . 1 3 3GPP2 C.S0048-B v1.

43、0 ix FOREWORD 1 This foreword is not part of this specification. 2 This specification was prepared by the Third Generation Partnership Project 2 (3GPP2). 3 3GPP2 C.S0048-B v1.0 x This page intentionally left blank 1 3GPP2 C.S0048-B v1.0 1-1 1 Introduction 1 2 1.1 Scope 3 The present document provide

44、s the ME (Mobile Equipment) conformance test specification 4 related to R-UIM (Removable User Identity Module), in order to ensure interoperability 5 between an ME and an R-UIM as defined in 1, 2, 8 and 9 independently of the 6 terminal and card manufacturers, card issuer or operator. 7 This documen

45、t does not specify which test cases are mandatory or optional. However, to 8 successfully execute a particular test case, its corresponding test requirements and 9 procedures as defined in this document shall be followed. 10 1.2 Document Conventions 11 1.2.1 Requirements Language 12 “Shall” and “sha

46、ll not” identify requirements to be followed strictly to conform to this 13 document and from which no deviation is permitted. “Should” and “should not” indicate 14 that one of several possibilities is recommended as particularly suitable, without 15 mentioning or excluding others, that a certain co

47、urse of action is preferred but not 16 necessarily required, or that (in the negative form) a certain possibility or course of action is 17 discouraged but not prohibited. “May” and “need not” indicate a course of action 18 permissible within the limits of the document. “Can” and “cannot” are used f

48、or statements 19 of possibility and capability, whether material, physical or causal. 20 1.2.2 Numbers 21 The following table describes the conventions used for non-decimal numbers. 22 Table 1.1 Convention for Numbers and Strings 23 Convention Description 1 or 0 A single binary bit bbbbbbbb An 8-bit

49、 binary number xx A single octet hexadecimal number xx xx xxxx xx A multi-octet hexadecimal number hh hh hhhh hh A multi-octet hexadecimal number or string Note: If an x is present in a binary or hexadecimal number, then that digit is “dont care”. “Bn” represents Byte n of the coding starting from left to right, i.e. MSB to LSB. “bn” 24 represents Bit n of the byte starting from right to left, i.e. LSB to MSB 25 3GPP2 C.S0048-B v1.0 1-2 1.3 Terminology 1 1.3.1 Acronyms 2 For the purposes of the present document, the following acronyms apply: 3 3GPP2 3rd Genera