Embed Size (px)
Citation preview
3GPP2 C.S0048-0
Version 1.0
Date: October 17, 2003
Mobile Equipment (ME) Conformance Testing for cdma2000 Spread Spectrum Standards
Release 0
COPYRIGHT
3GPP2 and its Organizational Partners claim copyright in this document and individual Organizational Partners may copyright and issue documents or standards publications in individual Organizational Partner's name based on this document. Requests for reproduction of this document should be directed to the 3GPP2 Secretariat at [email protected]. Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See www.3gpp2.org for more information.
3GPP2 C.S0048-0
No text. 1
3GPP2 C.S0048-0
i
CONTENTS 1
1 Foreword............................................................................................................. 1-1 2
2 References........................................................................................................... 2-1 3
3 Definitions and Abbreviations .............................................................................. 3-1 4
3.1 Definitions..................................................................................................... 3-1 5
3.2 Abbreviations................................................................................................. 3-1 6
4 ME Test Environment.......................................................................................... 4-1 7
5 Testing of the ME ................................................................................................ 5-1 8
5.1 Definition of Default Values for R-UIM/ME Interface Testing........................... 5-1 9
5.1.1 EFCST (CDMA Service Table) ...................................................................... 5-1 10
5.1.2 EFADN (Abbreviated Dialing Number).......................................................... 5-2 11
5.1.3 CHV1 (PIN)............................................................................................... 5-3 12
5.1.4 CHV2 (PIN2) ............................................................................................. 5-3 13
5.1.5 Unblock CHV1 (PUK) ................................................................................ 5-3 14
5.1.6 Unblock CHV2 (PUK2) .............................................................................. 5-3 15
5.1.7 Definition of FDN R-UIM........................................................................... 5-3 16
5.1.8 EFFDN (Fixed Dialing Numbers).................................................................. 5-3 17
6 ME Test Procedures............................................................................................. 6-1 18
6.1 MS Identification ........................................................................................... 6-1 19
6.1.1 Mobile Station Identifier ........................................................................... 6-1 20
6.1.1.1 Definition and Applicability ................................................................... 6-1 21
6.1.1.2 Conformance Requirement .................................................................... 6-1 22
6.1.1.3 Test Purpose ......................................................................................... 6-1 23
6.1.1.4 Method of Test ...................................................................................... 6-1 24
6.1.1.4.1 Initial Conditions............................................................................. 6-1 25
6.1.1.4.2 Procedure........................................................................................ 6-1 26
6.1.1.5 Test Requirement .................................................................................. 6-1 27
6.1.2 MS Recognizing the Home SID/NID .......................................................... 6-2 28
6.1.2.1 Definition and Applicability ................................................................... 6-2 29
6.1.2.2 Conformance Requirement .................................................................... 6-2 30
6.1.2.3 Test Purpose ......................................................................................... 6-2 31
6.1.2.4 Method of Test ...................................................................................... 6-2 32
3GPP2 C.S0048-0
ii
6.1.2.4.1 Initial Conditions .............................................................................6-2 1
6.1.2.4.2 Procedure ........................................................................................6-2 2
6.1.2.5 Test Requirement ..................................................................................6-2 3
6.2 UIM_ID/ESN_ME Selection.............................................................................6-3 4
6.2.1 Removable UIM_ID Usage Indicator ...........................................................6-3 5
6.2.1.1 Definition and Applicability ....................................................................6-3 6
6.2.1.2 Conformance Requirement.....................................................................6-3 7
6.2.1.3 Test Purpose..........................................................................................6-3 8
6.2.1.4 Method of Test.......................................................................................6-3 9
6.2.1.4.1 Initial Conditions .............................................................................6-3 10
6.2.1.4.2 Procedure ........................................................................................6-3 11
6.2.1.5 Test Requirement ..................................................................................6-3 12
6.2.2 ESN Management .....................................................................................6-4 13
6.2.2.1 Definition and Applicability ....................................................................6-4 14
6.2.2.2 Conformance Requirement.....................................................................6-4 15
6.2.2.3 Test Purpose..........................................................................................6-4 16
6.2.2.4 Method of Test.......................................................................................6-4 17
6.2.2.4.1 Initial Conditions .............................................................................6-4 18
6.2.2.4.2 Procedure ........................................................................................6-4 19
6.2.2.5 Test Requirement ..................................................................................6-4 20
6.3 Security-related commands ............................................................................6-4 21
6.3.1 SSD Update..............................................................................................6-4 22
6.3.1.1 Definition and Applicability ....................................................................6-4 23
6.3.1.2 Conformance Requirement.....................................................................6-5 24
6.3.1.3 Test Purpose..........................................................................................6-5 25
6.3.1.4 Method of Test.......................................................................................6-5 26
6.3.1.4.1 Initial Conditions .............................................................................6-5 27
6.3.1.4.2 Procedure ........................................................................................6-5 28
6.3.1.5 Test Requirement ..................................................................................6-5 29
6.3.2 Authentication Calculation for Global Challenge ........................................6-6 30
6.3.2.1 Definition and Applicability ....................................................................6-6 31
6.3.2.2 Conformance Requirement.....................................................................6-6 32
3GPP2 C.S0048-0
iii
6.3.2.3 Test Purpose ......................................................................................... 6-6 1
6.3.2.4 Method of Test ...................................................................................... 6-6 2
6.3.2.4.1 Initial Conditions............................................................................. 6-6 3
6.3.2.4.2 Procedure........................................................................................ 6-6 4
6.3.2.5 Test Requirement .................................................................................. 6-6 5
6.3.3 Unique Challenge While the Mobile Station is in Idle State ........................ 6-6 6
6.3.3.1 Definition and Applicability ................................................................... 6-6 7
6.3.3.2 Conformance Requirement .................................................................... 6-7 8
6.3.3.3 Test Purpose ......................................................................................... 6-7 9
6.3.3.4 Method of Test ...................................................................................... 6-7 10
6.3.3.4.1 Initial Conditions............................................................................. 6-7 11
6.3.3.4.2 Procedure........................................................................................ 6-7 12
6.3.3.5 Test Requirement .................................................................................. 6-7 13
6.3.4 Unique Challenge While the Mobile Station is in Mobile Station Control on the 14
Traffic Channel State ............................................................................................. 6-7 15
6.3.4.1 Definition and Applicability ................................................................... 6-7 16
6.3.4.2 Conformance Requirement .................................................................... 6-7 17
6.3.4.3 Test Purpose ......................................................................................... 6-8 18
6.3.4.4 Method of Test ...................................................................................... 6-8 19
6.3.4.4.1 Initial Conditions............................................................................. 6-8 20
6.3.4.4.2 Procedure........................................................................................ 6-8 21
6.3.4.5 Test Requirement .................................................................................. 6-8 22
6.3.5 Generate Key/VPM................................................................................... 6-8 23
6.3.5.1 Definition and Applicability ................................................................... 6-8 24
6.3.5.2 Conformance Requirement .................................................................... 6-8 25
6.3.5.3 Test Purpose ......................................................................................... 6-8 26
6.3.5.4 Method of Test ...................................................................................... 6-9 27
6.3.5.4.1 Initial Conditions............................................................................. 6-9 28
6.3.5.4.2 Procedure........................................................................................ 6-9 29
6.3.5.5 Test Requirement .................................................................................. 6-9 30
6.4 Reserved........................................................................................................ 6-9 31
6.5 OTASP/OTAPA Functionality.......................................................................... 6-9 32
6.5.1 Preferred Roaming List ............................................................................. 6-9 33
3GPP2 C.S0048-0
iv
6.5.1.1 Definition and Applicability ....................................................................6-9 1
6.5.1.2 Conformance Requirement.....................................................................6-9 2
6.5.1.3 Test Purpose..........................................................................................6-9 3
6.5.1.4 Method of Test.....................................................................................6-10 4
6.5.1.4.1 Initial Conditions ...........................................................................6-10 5
6.5.1.4.2 Procedure ......................................................................................6-10 6
6.5.1.5 Test Requirement ................................................................................6-10 7
6.5.2 OTASP/OTAPA Commands......................................................................6-10 8
6.5.2.1 Definition and Applicability ..................................................................6-10 9
6.5.2.2 Conformance Requirement...................................................................6-10 10
6.5.2.3 Test Purpose........................................................................................6-10 11
6.5.2.4 Method of Test.....................................................................................6-10 12
6.5.2.4.1 Initial Conditions ...........................................................................6-10 13
6.5.2.4.2 Procedure ......................................................................................6-10 14
6.5.2.5 Test Requirement ................................................................................6-10 15
6.6 Reserved ......................................................................................................6-11 16
6.7 Reserved ......................................................................................................6-11 17
6.8 Reserved ......................................................................................................6-11 18
6.9 Reserved ......................................................................................................6-11 19
6.10 Reserved ......................................................................................................6-11 20
6.11 Exchange Protocol Tests ...............................................................................6-11 21
6.12 Evaluation of Directory Characteristics .........................................................6-11 22
6.12.1 Operating Speed in Authentication Procedure..........................................6-11 23
6.12.1.1 Definition and Applicability ................................................................6-11 24
6.12.1.2 Conformance Requirement .................................................................6-11 25
6.12.1.3 Test Purpose......................................................................................6-11 26
6.12.1.4 Method of Test ...................................................................................6-11 27
6.12.1.4.1 Initial Conditions .........................................................................6-11 28
6.12.1.4.2 Procedure ....................................................................................6-12 29
6.12.1.5 Test Requirement...............................................................................6-12 30
6.12.2 Clock Stop ..............................................................................................6-12 31
6.12.2.1 Definition and Applicability ................................................................6-12 32
3GPP2 C.S0048-0
v
6.12.2.2 Conformance Requirement ................................................................ 6-12 1
6.12.2.3 Test Purpose ..................................................................................... 6-12 2
6.12.2.4 Method of Test .................................................................................. 6-12 3
6.12.2.4.1 Initial Conditions......................................................................... 6-12 4
6.12.2.4.2 Procedure.................................................................................... 6-12 5
6.12.2.5 Test Requirement .............................................................................. 6-13 6
6.12.3 Authentication ....................................................................................... 6-13 7
6.13 Mechanical Tests ......................................................................................... 6-13 8
6.14 Secret Code Usage ....................................................................................... 6-13 9
6.14.1 Entry of PIN ........................................................................................... 6-13 10
6.14.2 Change of PIN ........................................................................................ 6-13 11
6.14.3 Disabling the PIN ................................................................................... 6-14 12
6.14.3.1 Definition and Applicability ............................................................... 6-14 13
6.14.3.2 Conformance Requirement ................................................................ 6-14 14
6.14.3.3 Test Purpose ..................................................................................... 6-14 15
6.14.3.4 Method of Test .................................................................................. 6-14 16
6.14.3.4.1 Initial Conditions......................................................................... 6-14 17
6.14.3.4.2 Procedure.................................................................................... 6-14 18
6.14.3.5 Test Requirement .............................................................................. 6-14 19
6.14.4 PUK Entry.............................................................................................. 6-14 20
6.14.5 Entry of PIN2 ......................................................................................... 6-14 21
6.14.6 Change of PIN2 ...................................................................................... 6-14 22
6.14.7 PUK2 Entry............................................................................................ 6-14 23
6.14.8 CDMA Service Table ............................................................................... 6-15 24
6.14.8.1 Definition and Applicability ............................................................... 6-15 25
6.14.8.2 Conformance Requirement ................................................................ 6-15 26
6.14.8.3 Test Purpose ..................................................................................... 6-15 27
6.14.8.4 Method of Test .................................................................................. 6-15 28
6.14.8.4.1 Initial Conditions......................................................................... 6-15 29
6.14.8.4.2 Procedure.................................................................................... 6-15 30
6.14.8.5 Test Requirement .............................................................................. 6-15 31
6.15 Abbreviated Dialing Numbers (ADN) ............................................................. 6-15 32
3GPP2 C.S0048-0
vi
6.15.1 Definition and Applicability .....................................................................6-15 1
6.15.2 Conformance Requirement ......................................................................6-15 2
6.15.3 Test Purpose...........................................................................................6-16 3
6.15.4 Method of Test ........................................................................................6-16 4
6.15.4.1 Initial Conditions ...............................................................................6-16 5
6.15.4.2 Procedure ..........................................................................................6-16 6
6.15.5 Test Requirements ..................................................................................6-17 7
6.16 UI Reaction to R-UIM Status Encoding..........................................................6-17 8
6.17 Electrical Tests.............................................................................................6-17 9
6.18 Fixed Dialing Number (FDN) .........................................................................6-17 10
6.19 Version Identification ...................................................................................6-17 11
6.19.1 Definition and Applicability .....................................................................6-17 12
6.19.2 Conformance Requirement ......................................................................6-17 13
6.19.3 Test Purpose...........................................................................................6-17 14
6.19.4 Method of Test ........................................................................................6-18 15
6.19.4.1 Initial Conditions ...............................................................................6-18 16
6.19.4.2 Procedure ..........................................................................................6-18 17
6.19.5 Test Requirement....................................................................................6-18 18
6.20 R-UIM Presence Detection ............................................................................6-18 19
6.21 Reserved ......................................................................................................6-18 20
6.22 Suggested Slot Cycle Index ...........................................................................6-18 21
6.22.1 Definition and Applicability .....................................................................6-18 22
6.22.2 Conformance Requirement ......................................................................6-18 23
6.22.3 Test Purpose...........................................................................................6-18 24
6.22.4 Method of Test ........................................................................................6-18 25
6.22.4.1 Initial Conditions ...............................................................................6-18 26
6.22.4.2 Procedure ..........................................................................................6-19 27
6.22.5 Test Requirement....................................................................................6-19 28
6.23 Service Provider Name ..................................................................................6-19 29
6.23.1 Definition and Applicability .....................................................................6-19 30
6.23.2 Conformance Requirement ......................................................................6-19 31
6.23.3 Test Purpose...........................................................................................6-19 32
3GPP2 C.S0048-0
vii
6.23.4 Method of Test ....................................................................................... 6-20 1
6.23.4.1 Initial Conditions .............................................................................. 6-20 2
6.23.4.2 Procedure ......................................................................................... 6-20 3
6.23.5 Test Requirement ................................................................................... 6-20 4
5
6
3GPP2 C.S0048-0
viii
No text.1
3GPP2 C.S0048-0
1-1
1 FOREWORD 1
The present document provides the Conformance Test Specification for Removable User 2
Identity Module (R-UIM) enabled Mobile Equipment (ME) terminals defined in [1], [2], [8] 3
and [9]. 4
5
3GPP2 C.S0048-0
1-2
No text. 1
3GPP2 C.S0048-0
2-1
2 REFERENCES 1
[1] 3GPP2 C.S0023-A: "Removable User Identity Module (R-UIM) for cdma2000 2
Spread Spectrum Systems". 3
[2] 3GPP 51.011: "Digital cellular telecommunications system (Phase 2+); 4
Specification of the Subscriber Identity Module - Mobile Equipment (SIM - 5
ME) interface". 6
[3] ISO/IEC 7816-1 (1987): "Identification cards - Integrated circuit(s) cards 7
with contacts, Part 1: Physical characteristics". 8
[4] ISO/IEC 7816-2 (1988): "Identification cards - Integrated circuit(s) cards 9
with contacts, Part 1: Dimensions and locations of the contacts". 10
[5] ISO/IEC 7816-3 (1989): "Identification cards - Integrated circuit(s) cards 11
with contacts, Part 1: Electronic signals and transmission protocols." 12
[6] ISO/IEC 7811-1 (1995): "Identification cards - Recording technique - Part 1: 13
Embossing" 14
[7] ISO/IEC 7811-3 (1995): "Identification cards - Recording technique - Part 3: 15
Location of embossed characters on ID-1 cards" 16
[8] GSM 11.12: "Digital cellular telecommunications system (Phase 2); 17
Specification of the 3 Volt Subscriber Identity Module - Mobile Equipment 18
(SIM - ME) interface". 19
[9] 3GPP 31.101: "Digital cellular telecommunications system (Phase 2+); 20
Specification of the 1.8 Volt Subscriber Identity Module - Mobile Equipment 21
(SIM - ME) interface". 22
[10] 3GPP 51.010: “Mobile Station (MS) conformance specification; Part 1: 23
Conformance specification”. 24
[11] 3GPP2 C.S0031-0 version 2.0: “Signaling Conformance Tests for cdma2000 25
Spread Spectrum Systems”. 26
27
3GPP2 C.S0048-0
2-2
No text. 1
3GPP2 C.S0048-0
3-1
3 DEFINITIONS AND ABBREVIATIONS 1
3.1 Definitions 2
For the purposes of the present document, the following terms and definitions apply in 3
addition to the terms defined in [1]: 4
Implementation Conformance Statement (ICS): A statement made by the supplier of an 5
implementation or a system claimed to conform to a given specification, stating which 6
capabilities have been implemented. The ICS can take several forms: protocol ICS, profile 7
ICS, profile specific ICS, information object ICS, etc. 8
3.2 Abbreviations 9
For the purposes of the present document, the following abbreviations apply: 10
3GPP2 3rd Generation Partnership Project 2 11
CHV1 Card Holder Verification 1 12
CHV2 Card Holder Verification 2 13
CRn Conformance Requirement 'n' 14
DF Directory File 15
FT Fixed Termination 16
ICS Implementation Conformance Statement 17
IUT Implementation Under Test 18
ME Mobile Equipment 19
MF Master File 20
MS Mobile Station 21
PIN Personal Identity Number 22
PIN2 Personal Identity Number 2 23
PRL Preferred Roaming List 24
PUK PIN Unblocking Key 25
PUK2 PIN2 Unblocking Key 26
R-UIM Removable User Identity Module 27
SIM Subscriber Identity Module 28
SS System Simulator 29
TS Test Specification 30
31
3GPP2 C.S0048-0
3-2
No text. 1
3GPP2 C.S0048-0
4-1
4 ME TEST ENVIRONMENT 1
The test environment shall comply with the requirements specified in Clause 4, “Physical 2
Characteristics” and Clause 5, “Electronic Signals and Transmission Protocols” of [2]. 3
4
3GPP2 C.S0048-0
4-2
No text. 1
3GPP2 C.S0048-0
5-1
5 TESTING OF THE ME 1
The following sequence of tests confirms: 2
1) the correct interpretation of data read from the R-UIM (Removable-User 3
Identification Module) by the ME; 4
2) the correct writing of data to the R-UIM by the ME; 5
3) the initiation of appropriate procedures by the ME; 6
4) low level protocols; 7
5) electrical characteristics; 8
6) physical characteristics. 9
All tests apply to MEs conforming to [1] using either ID-1 or Plug-in R-UIM. 10
An R-UIM simulator may be included as part of the system simulator (SS). Alternatively, to 11
perform the logical tests, R-UIMs programmed with specific data may be used. The R-UIM 12
data is not defined within the initial conditions of the tests unless it differs from the default 13
values defined below. 14
5.1 Definition of Default Values for R-UIM/ME Interface Testing 15
An R-UIM containing the following default values is used for all tests of this section unless 16
otherwise stated. 17
For all data items, the logical default values and the coding within the elementary files (EFs) 18
of the R-UIM follow. 19
NOTE 1: Bx represents Byte x of the coding starting from left to right, i.e. MSB to LSB. 20
NOTE 2: Unless otherwise defined, the coding values are hexadecimal. 21
5.1.1 EFCST (CDMA Service Table) 22
Unless otherwise specified, the CDMA Service Table (EFCST) shall be coded as defined by the 23
entry “EFCST Setting 1” of Table 5-1. 24
3GPP2 C.S0048-0
5-2
Table 5-1. Coding of EFCST 1
Setting Description Byte Coding (binary)
EFCST Setting 1 • CHV1 disable function allocated and activated.
• Abbreviated dialing numbers allocated and activated.
• Fixed dialing numbers not activated.
B1 – xx0x1111
EFCST Setting 2 • CHV1 disable function allocated and activated.
• Abbreviated dialing numbers allocated and activated.
• Fixed dialing numbers allocated and activated.
B1 – xx111111
EFCST Setting 3 • CHV1 disable function not activated.
• Abbreviated dialing numbers allocated and activated.
• Fixed dialing numbers not activated.
B1 – xx0x110x
Note: The coding of bits designated ‘x’ shall conform to the capabilities of the R-UIM simulator used.
5.1.2 EFADN (Abbreviated Dialing Number) 2
At least 10 records. 3
Record 1: 4
Length of alpha identifier: 32 characters 5
Alpha identifier: "ABCDEFGHIJKLMNOPQRSTUVWXYZABCDEF" 6
Length of BCD number: "03" 7
TON and NPI: Telephony and Unknown 8
Dialed number: 123 9
CCI: None 10
Ext1: None 11
Coding: B1 B2 B3 ... B32 B33 B34 B35 B36 B37 B38 B39 ... B46
Record 1: 41 42 43 ... 46 03 81 21 F3 FF FF FF ... FF
3GPP2 C.S0048-0
5-3
5.1.3 CHV1 (PIN) 1
Logically: 2468 2
Coding: B1 B2 B3 B4 B5 B6 B7 B8 3
32 34 36 38 FF FF FF FF 4
5.1.4 CHV2 (PIN2) 5
Logically: 3579 6
Coding: B1 B2 B3 B4 B5 B6 B7 B8 7
33 35 37 39 FF FF FF FF 8
5.1.5 Unblock CHV1 (PUK) 9
Logically: 13243546 10
Coding: B1 B2 B3 B4 B5 B6 B7 B8 11
31 33 32 34 33 35 34 36 12
5.1.6 Unblock CHV2 (PUK2) 13
Logically: 08978675 14
Coding: B1 B2 B3 B4 B5 B6 B7 B8 15
30 38 39 37 38 36 37 35 16
5.1.7 Definition of FDN R-UIM 17
Some test cases require a different configuration from the one described in the previous 18
sections. For that purpose a default FDN R-UIM is defined. In general the values of the 19
FDN R-UIM are identical to the default R-UIM, with the following exceptions: 20
5.1.8 EFFDN (Fixed Dialing Numbers) 21
Multiple records: 22
Record 1: 23
Length of alpha identifier: 6 characters 24
Alpha identifier: "FDN111" 25
Length of BCD number: "06" 26
TON and NPI: Telephony and Unknown 27
Dialed number: 1357924680 28
CCI: None 29
Ext1: None 30
3GPP2 C.S0048-0
5-4
Coding for record 1: 1
B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11 B12 B13
46 44 4E 31 31 31 06 81 31 75 29 64 08
B14 B15 B16 B17 B18 B19 B20
FF FF FF FF FF FF FF
Record 2: 2
Length of alpha identifier: 6 characters 3
Alpha identifier: "FDN222" 4
Length of BCD number: "04" 5
TON and NPI: Telephony and Unknown 6
Dialed number: 24680 7
CCI: None 8
Ext1: None 9
Coding for record 2: 10
B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11 B12 B13
46 44 4E 32 32 32 04 81 42 86 F0 FF FF
B14 B15 B16 B17 B18 B19 B20
FF FF FF FF FF FF FF
Record 3: 11
Length of alpha identifier: 6 characters 12
Alpha identifier: "FDN333" 13
Length of BCD number: "0B" 14
TON and NPI: Telephony and Unknown 15
Dialed number: 12345678901234567890 16
CCI: None 17
Ext1: None 18
3GPP2 C.S0048-0
5-5
Coding for record 3: 1
B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11 B12 B13
46 44 4E 33 33 33 0B 81 21 43 65 87 09
B14 B15 B16 B17 B18 B19 B20
21 43 65 87 09 FF FF 2
3GPP2 C.S0048-0
5-6
No text.1
3GPP2 C.S0048-0
6-1
6 ME TEST PROCEDURES 1
For each test procedure the following five (5) subsections are included: 2
1) Definition and Applicability 3
2) Conformance Requirement 4
3) Test Purpose 5
4) Method of Test 6
(a) Initial Conditions 7
(b) Procedure 8
5) Test Requirement 9
6.1 MS Identification 10
6.1.1 Mobile Station Identifier 11
6.1.1.1 Definition and Applicability 12
This test verifies the use of the Mobile Station Identifier (Mobile Station ID [MSID] or Mobile 13
Station Identification Number [MSIN]), Mobile Country Code (MCC), and International 14
Mobile Station Identity (IMSI) stored within the R-UIM. 15
This test applies to MEs conforming to [1] using either ID-1 or Plug-in R-UIM. 16
6.1.1.2 Conformance Requirement 17
The MS shall conform to the requirements specified in 2.12.3 of [11]. 18
6.1.1.3 Test Purpose 19
The purpose of the test is to verify that the ME uses the IMSI_S, IMSI_11_12, and MCC of 20
the R-UIM. 21
6.1.1.4 Method of Test 22
6.1.1.4.1 Initial Conditions 23
The default R-UIM is installed into the ME, and the MS is powered on. 24
6.1.1.4.2 Procedure 25
The tests shall be conducted in accordance with the procedures and requirements defined 26
in 2.12 (MSID, MCC, and IMSI) of [11]. 27
6.1.1.5 Test Requirement 28
The ME shall conform to the requirements defined in 2.12.3 (Minimum Standard) of [11]. 29
3GPP2 C.S0048-0
6-2
6.1.2 MS Recognizing the Home SID/NID 1
6.1.2.1 Definition and Applicability 2
This test verifies the ability of the ME to read the appropriate home system information 3
from the R-UIM, compare that stored information to that received by the ME in the Sync 4
Channel Message, and to display the appropriate roaming indication to the user. 5
This test applies to MEs conforming to [1] using either ID-1 or Plug-in R-UIM. 6
6.1.2.2 Conformance Requirement 7
The ME shall compare the values of SIDp and NIDp stored within EFCDMAHOME with those 8
received in the Sync Channel Message (SIDr and NIDr, respectively) as the basis for 9
displaying a roaming indication to the user. 10
6.1.2.3 Test Purpose 11
The purpose of the test is to verify the ME is able to read, interpret, and apply during the 12
normal course of operation the values of SIDp and NIDp stored within EFCDMAHOME. 13
6.1.2.4 Method of Test 14
6.1.2.4.1 Initial Conditions 15
The values of the SID and NID fields of the Sync Channel Message transmitted by the 16
system simulator shall be set to equal those stored in the R-UIM (EFCDMAHOME). 17
6.1.2.4.2 Procedure 18
1) Power-on the mobile station. 19
2) Observe the status of any roaming indicator icon or display element on the 20
mobile station. 21
3) Set the values of the SID and NID fields of the Sync Channel Message transmitted 22
by the system simulator to values other than those stored in the R-UIM 23
(EFCDMAHOME). 24
4) Power cycle (power-off then power-on) the mobile station. 25
5) Observe the status of any roaming indicator icon or display element on the 26
mobile station. 27
6.1.2.5 Test Requirement 28
1) In step 2) of the test procedure, the roaming indicator icon or display element of 29
the mobile station shall indicate the mobile station is operating within its home 30
system. 31
2) In step 5) of the test procedure, the roaming indicator icon or display element of 32
the mobile station shall indicate the mobile station is operating in a roaming 33
status. 34
3GPP2 C.S0048-0
6-3
6.2 UIM_ID/ESN_ME Selection 1
6.2.1 Removable UIM_ID Usage Indicator 2
6.2.1.1 Definition and Applicability 3
Removable UIM_ID Usage Indicator indicates whether the 32 bits of the UIM_ID or ESN_ME 4
is used in the MS identification procedure. 5
6.2.1.2 Conformance Requirement 6
The ME shall use the UIM_ID or ESN_ME correctly for over-the-air messages as indicated 7
by the Removable UIM_ID Usage Indicator stored in the R-UIM. 8
6.2.1.3 Test Purpose 9
This test verifies that the mobile station uses the UIM_ID or ESN_ME correctly depending 10
on the setting of the Removable UIM_ID Usage Indicator. 11
6.2.1.4 Method of Test 12
6.2.1.4.1 Initial Conditions 13
The default R-UIM is installed into the ME, and the MS is powered on. 14
6.2.1.4.2 Procedure 15
1) Ensure that the system simulator selects ESN as PREF_MSID_TYPE. 16
2) Set the Removable UIM_ID Usage Indicator in R-UIM to ‘1’. 17
3) Initiate a mobile station originated call. 18
4) Verify that the UIM_ID is used for identification in the Origination Message. 19
5) End the call. 20
6) Set the Removable UIM_ID Usage Indicator in the R-UIM to ‘0’. 21
7) Power-cycle the mobile station (Power “Off” and then Power “On”). 22
8) Initiate a mobile station originated call. 23
9) Verify that the ESN_ME is used for identification in Origination Message. 24
10) End the call. 25
6.2.1.5 Test Requirement 26
1) If the Removable UIM_ID Usage Indicator is set to ‘1’, the ME shall use the UIM_ID to 27
identify itself. 28
2) If the Removable UIM_ID Usage Indicator is set to ‘0’, the ME shall use the ESN_ME 29
to identify itself. 30
3GPP2 C.S0048-0
6-4
6.2.2 ESN Management 1
6.2.2.1 Definition and Applicability 2
ESN_ME is the electronic serial number of the Mobile Equipment (ME) to which the R-UIM 3
is attached. This number is transferred to the R-UIM when the Mobile Equipment 4
determines that the R-UIM has been inserted. 5
This test applies to MEs conforming to [1] using either ID-1 or Plug-in R-UIM. 6
6.2.2.2 Conformance Requirement 7
This test verifies that the ME provides its ESN to the R-UIM during the ME and R-UIM 8
initialization procedure. 9
6.2.2.3 Test Purpose 10
To ensure that the servicing ESN_ME is stored within the R-UIM. 11
6.2.2.4 Method of Test 12
6.2.2.4.1 Initial Conditions 13
EFESN_ME is initialized to the default value as defined in [1]. 14
6.2.2.4.2 Procedure 15
1) Insert this R-UIM into the ME being tested. 16
2) During the ME and R-UIM initialization process, verify that the ME invokes the 17
“Store ESN_ME” command to store its ESN in EF ‘6F38’. 18
3) Verify that the new ESN_ME is successfully stored in the R-UIM. 19
4) Verify the new ESN_ME stored in the EFESN_ME matches ESN of the ME being tested. 20
6.2.2.5 Test Requirement 21
The ME shall be able to store ESN_ME into the R-UIM as a result of the initialization 22
process. 23
6.3 Security-related commands 24
6.3.1 SSD Update 25
6.3.1.1 Definition and Applicability 26
SSD is derived from the “A-key” stored in the R-UIM. SSD updates are initiated when the 27
system simulator issues the command UPDATE SSD, containing the parameter RANDSSD, 28
to the ME. 29
This test applies to MEs conforming to [1] using either ID-1 or Plug-in R-UIM. 30
3GPP2 C.S0048-0
6-5
6.3.1.2 Conformance Requirement 1
This test verifies that the mobile equipment passes RANDSSD, RANDSeed and AUTHBS 2
correctly to R-UIM when the system simulator initiates an SSD Update process. 3
6.3.1.3 Test Purpose 4
To make sure that SSD update procedures are executed properly. 5
6.3.1.4 Method of Test 6
6.3.1.4.1 Initial Conditions 7
The default R-UIM is installed into the ME, and the MS is powered on. Ensure that the A-8
key, ESN and IMSI are aligned between the mobile station and the system simulator. 9
6.3.1.4.2 Procedure 10
1) At the system simulator, initiate an SSD Update on the paging channel. 11
2) Verify that the ME sends a Base Station Challenge Command to R-UIM with a 12
RANDSeed. 13
3) Verify that upon receipt of a Base Station Challenge Response from the R-UIM, the 14
ME sends a Base Station Challenge Order to the system simulator with RANDBS set 15
to the same value as that received from R-UIM. 16
4) Verify that the ME sends an Update SSD Command to the R-UIM, containing the 17
parameter RANDSSD received from the SSD Update Message. 18
5) Verify that upon receipt of a Base Station Challenge Confirmation Order from the 19
system simulator, the ME sends a Confirm SSD Command to the R-UIM with 20
AUTHBS set to the same value as that received from the Base Station Challenge 21
Confirmation Order. 22
6) Verify that the ME sends an SSD Update Confirmation Order upon receipt of a 23
response from R-UIM with ’90 00’, SW1= ’90’ and SW2=’00’. 24
7) Modify the IMSI in the system simulator to a different value. 25
8) Repeat steps 2) through 5). 26
9) Verify that the ME sends an SSD Update Rejection Order upon receipt of response 27
from R-UIM with ’98 04’, SW1= ’98’ and SW2=’04’. 28
6.3.1.5 Test Requirement 29
1) The ME sends an SSD Update Confirmation Order upon receipt of success 30
response from R-UIM. 31
2) The ME sends an SSD Update Rejection Order upon receipt of failure response 32
from R-UIM. 33
3GPP2 C.S0048-0
6-6
6.3.2 Authentication Calculation for Global Challenge 1
6.3.2.1 Definition and Applicability 2
The ME shall be able to initiate the start of the CAVE algorithm in R-UIM when the system 3
simulator enables authentication. 4
This test applies to MEs conforming to [1] using either ID-1 or Plug-in R-UIM. 5
6.3.2.2 Conformance Requirement 6
The ME shall initiate the start of the Run Cave Command and pass the response (AUTHR) 7
from the R-UIM to the system simulator within the appropriate signaling message. 8
6.3.2.3 Test Purpose 9
This test verifies that the mobile equipment correctly sends the Run CAVE Command to the 10
R-UIM and passes AUTHR from the R-UIM to the system simulator when the system 11
simulator enables or initiates authentication. 12
6.3.2.4 Method of Test 13
6.3.2.4.1 Initial Conditions 14
The default R-UIM is installed into the ME and the ME is powered on. 15
6.3.2.4.2 Procedure 16
1) At the system simulator, enable global challenge. 17
2) Originate a voice call from the mobile station. 18
3) Verify that the ME sends a Run CAVE Command with RANDTYPE set to 19
‘00000000’ and RAND to R-UIM. 20
4) Upon receipt of SW ’9F 03’, verify that ME sends a Get Response Command. 21
5) Upon receipt of the AUTHR, verify that AUTHR is included in the Origination 22
Message. 23
6) Verify the audio traffic in both directions. 24
6.3.2.5 Test Requirement 25
The ME shall correctly send the Run CAVE Command to the R-UIM and pass AUTHR from 26
the R-UIM to the system simulator within the Origination Message. 27
6.3.3 Unique Challenge While the Mobile Station is in Idle State 28
6.3.3.1 Definition and Applicability 29
The CAVE function is run in the R-UIM to calculate AUTHU when the ME sends Run CAVE 30
Command. 31
This test applies to MEs conforming to [1] using either ID-1 or Plug-in R-UIM. 32
3GPP2 C.S0048-0
6-7
6.3.3.2 Conformance Requirement 1
This test verifies that the ME sends the Run CAVE Command to the R-UIM during call 2
origination when the system simulator initiates a unique challenge to the mobile station. 3
6.3.3.3 Test Purpose 4
To ensure proper execution of the Run CAVE procedures. 5
6.3.3.4 Method of Test 6
6.3.3.4.1 Initial Conditions 7
The default R-UIM is installed into the ME, and the MS is powered on. 8
6.3.3.4.2 Procedure 9
1) Enable authentication within the system simulator. 10
2) Originate a voice call from the mobile station. 11
3) Instruct the system simulator to send an Authentication Challenge Message. 12
4) Verify that the ME sends a Run CAVE Command with RANDTYPE set to 13
‘00000001’ and RANDU to R-UIM. 14
5) Upon receipt of SW ’9F 03’, verify that ME sends a Get Response Command. 15
6) Upon receiving the AUTHU, verify that AUTHU is included in the Authentication 16
Challenge Response Message with AUTHU same as sent from R-UIM. 17
7) Verify the audio traffic in both directions. 18
6.3.3.5 Test Requirement 19
The ME correctly sends the Run CAVE Command with RANDU to the R-UIM and passes 20
AUTHU from the R-UIM to the system simulator. 21
6.3.4 Unique Challenge While the Mobile Station is in Mobile Station Control on the 22
Traffic Channel State 23
6.3.4.1 Definition and Applicability 24
The CAVE function is executed within the R-UIM to calculate AUTHU when the ME sends 25
the Run CAVE Command with RANDU when the mobile station is in the Mobile Station 26
Control on the Traffic Channel State. 27
This test applies to MEs conforming to [1] using either ID-1 or Plug-in R-UIM. 28
6.3.4.2 Conformance Requirement 29
This test verifies that the ME sends the Run CAVE Command to the R-UIM when the 30
system simulator initiates a unique challenge while the mobile station is in the Mobile 31
Station Control on the Traffic Channel State. 32
3GPP2 C.S0048-0
6-8
6.3.4.3 Test Purpose 1
To ensure that Run CAVE procedures are executed correctly while the mobile station is in 2
the Mobile Station Control on the Traffic Channel State. 3
6.3.4.4 Method of Test 4
6.3.4.4.1 Initial Conditions 5
The default R-UIM is installed into the ME, and the MS is powered on. 6
6.3.4.4.2 Procedure 7
1) At the system simulator, enable authentication. 8
2) Originate a voice call from the mobile station. 9
3) Verify the audio traffic in both directions. 10
4) While the call is in progress, instruct the system simulator to send an 11
Authentication Challenge Message. 12
5) Verify that the ME sends a Run CAVE Command with RANDTYPE set to 13
‘00000001’ and RANDU to R-UIM. 14
6) Upon receipt of SW ’9F 03’, verify that ME sends a Get Response Command. 15
7) Upon receipt of AUTHU from R-UIM, verify that the ME sends an Authentication 16
Challenge Response Message with AUTHU same as sent from R-UIM. 17
6.3.4.5 Test Requirement 18
The ME correctly sends the Run CAVE Command with RANDU to the R-UIM and passes 19
AUTHU from the R-UIM to the system simulator. 20
6.3.5 Generate Key/VPM 21
6.3.5.1 Definition and Applicability 22
The CAVE function is run in the R-UIM to generate the encryption key/VPM when the ME 23
sends a Generate Key/VPM command. 24
This test applies to MEs conforming to [1] using either ID-1 or Plug-in R-UIM. 25
6.3.5.2 Conformance Requirement 26
This test verifies that the ME sends a Generate Key/VPM command to the R-UIM when the 27
user enables voice privacy. 28
6.3.5.3 Test Purpose 29
To ensure that Run CAVE procedures are executed correctly to generate the encryption 30
key/VPM. 31
3GPP2 C.S0048-0
6-9
6.3.5.4 Method of Test 1
6.3.5.4.1 Initial Conditions 2
The default R-UIM is installed into the ME, and the MS is powered on. 3
6.3.5.4.2 Procedure 4
1) At the system simulator, enable authentication. On the mobile station, enable 5
voice privacy. 6
2) Originate a voice call from the mobile station. 7
3) Verify that the ME sends a Run CAVE Command with the following: 8
RANDTYPE is set to ‘00000000’, Bit 4 of Process_Control is set to ‘1’ 9
and a RAND. 10
4) Upon receipt of SW ’9F 03’, verify that the ME sends a Get Response Command. 11
5) Upon receiving the AUTHR, verify that AUTHR is included in the Origination 12
Message. 13
6) Verify that the ME sends a Generate Key/VPM command to the R-UIM. 14
6.3.5.5 Test Requirement 15
The ME correctly sends a Generate Key/VPM command to R-UIM after sending a Run CAVE 16
with Save Register On. 17
6.4 Reserved 18
6.5 OTASP/OTAPA Functionality 19
6.5.1 Preferred Roaming List 20
6.5.1.1 Definition and Applicability 21
This test verifies that a mobile station can respond to an OTAPA mobile terminated call, 22
download a preferred roaming list (PRL) and correctly store the list in the R-UIM. The size 23
of the PRL downloaded to the mobile station shall be 4096 octets or MAX_PRL_LIST_SIZE 24
octets, whichever is smaller. 25
This test applies to MEs conforming to [1] using either ID-1 or Plug-in R-UIM. 26
6.5.1.2 Conformance Requirement 27
The network-initiated OTAPA session shall result in the mobile station responding to a 28
General Page Message and downloading a new PRL. The ME shall update EFPRL with the 29
PRL downloaded from the system simulator. 30
6.5.1.3 Test Purpose 31
This test verifies that an ME can respond to an OTAPA mobile terminated call, download a 32
PRL and correctly store and retrieve the PRL from the R-UIM. 33
3GPP2 C.S0048-0
6-10
6.5.1.4 Method of Test 1
6.5.1.4.1 Initial Conditions 2
The default R-UIM is installed into the ME, and the MS is powered on. 3
6.5.1.4.2 Procedure 4
1) The test shall be conducted in accordance with the procedures defined in 15.5 5
(OTAPA Service Provisioning for System Selection and Preferred Roaming for a Mobile 6
Station in the Mobile Station Idle State) of [11]. 7
6.5.1.5 Test Requirement 8
The ME shall conform to the test requirements defined in 15.5.3 (Minimum Standard) of 9
[11]. The ME shall update EFPRL with the PRL downloaded from the system simulator. 10
6.5.2 OTASP/OTAPA Commands 11
6.5.2.1 Definition and Applicability 12
The ME maps OTASP/OTAPA messages sent from the system simulator correctly to the 13
OTASP/OTAPA commands to R-UIM and maps responses from R-UIM to OTASP/OTAPA 14
messages. 15
This test applies to MEs conforming to [1] using either ID-1 or Plug-in R-UIM. 16
6.5.2.2 Conformance Requirement 17
The ME shall map between messages and command/responses correctly. 18
6.5.2.3 Test Purpose 19
This test verifies that an ME can respond to OTASP/OTAPA messages sent from the system 20
simulator correctly and map responses from R-UIM to OTASP/OTAPA message correctly to 21
the system simulator. 22
6.5.2.4 Method of Test 23
6.5.2.4.1 Initial Conditions 24
The default R-UIM is installed into the ME, and the MS is powered on. 25
6.5.2.4.2 Procedure 26
The test shall be conducted in accordance with the procedures defined in [11]. 27
6.5.2.5 Test Requirement 28
The ME shall correctly map the OTASP/OTAPA messages to corresponding commands and 29
map responses from R-UIM to OTASP/OTAPA messages. In addition, the ME shall conform 30
to the test requirements defined in [11]. 31
3GPP2 C.S0048-0
6-11
6.6 Reserved 1
6.7 Reserved 2
6.8 Reserved 3
6.9 Reserved 4
6.10 Reserved 5
6.11 Exchange Protocol Tests 6
The ME shall conform to the requirements specified in subclause 27.11 of [10]. 7
6.12 Evaluation of Directory Characteristics 8
6.12.1 Operating Speed in Authentication Procedure 9
6.12.1.1 Definition and Applicability 10
Authentication is performed in a cdma2000®1 network on an R-UIM enabled mobile station 11
by the ME sending a random number received from the network to the R-UIM. The R-UIM 12
then performs a calculation on the random number, and sends the result to the network for 13
verification. 14
This test applies to MEs conforming to [1] using either ID-1 or Plug-in R-UIM. 15
6.12.1.2 Conformance Requirement 16
If bit b2 of the file characteristics is set to 1, the ME shall provide a clock frequency of at 17
least 13/4 MHz to enable the R-UIM to run the authentication process in the required time. 18
6.12.1.3 Test Purpose 19
To verify that the authentication procedure is performed with a frequency of at least 13/4 20
MHz if the bit b2 of the file characteristics (byte 1 of the directory characteristics) is set to 21
1. 22
6.12.1.4 Method of Test 23
6.12.1.4.1 Initial Conditions 24
The ME shall be powered on and connected to an R-UIM simulator with bit b2 of the file 25
characteristics set to ‘1’. 26
1 cdma2000® is 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 Telecommunications Industry Association (TIA-USA) in the United States.
3GPP2 C.S0048-0
6-12
6.12.1.4.2 Procedure 1
The test shall be conducted in accordance with the procedures defined in 6.11 2
(Authentication Upon Originations) of [11]. 3
6.12.1.5 Test Requirement 4
The frequency of the clock shall be at least 13/4 MHz during the authentication procedure. 5
6.12.2 Clock Stop 6
6.12.2.1 Definition and Applicability 7
The ME may switch off the clock signal to the R-UIM if the R-UIM indicates that it supports 8
this feature. 9
This test applies to MEs conforming to [1] using either ID-1 or Plug-in R-UIM. 10
6.12.2.2 Conformance Requirement 11
The ME shall not stop the clock, unless the requirements indicated in byte 1 of the file 12
characteristics are met. 13
The ME shall wait at least 860 clock cycles after having received the last character 14
including the minimum guard time (2 elementary time units [etu]) of the response before 15
switching off the clock. The ME shall wait at least 744 clock cycles before it sends the first 16
command after having restarted the clock. 17
6.12.2.3 Test Purpose 18
1) To verify that the clock is only switched off if requirements are met as indicated in the 19
file characteristics (byte 1 of the directory characteristics). 20
2) To verify that the timing of the clock switching is as specified. 21
6.12.2.4 Method of Test 22
6.12.2.4.1 Initial Conditions 23
The ME is connected to an R-UIM simulator. CHV1 is enabled. 24
6.12.2.4.2 Procedure 25
1) An R-UIM simulator is used with the file characteristics bits set as follows: 26
Bit b1 Bit b3 Bit b4 27
0 0 0 28
2) The ME is powered on. When the ME is in mode PIN check, 10 seconds shall 29
elapse before the PIN is entered. 30
3) The ME is powered off, and an R-UIM simulator is used with the file 31
characteristics bits set as follows: 32
Bit b1 Bit b3 Bit b4 33
3GPP2 C.S0048-0
6-13
0 1 0 1
4) The ME is powered on. When the ME is in mode PIN check, 10 seconds shall 2
elapse before the PIN is entered. 3
5) The ME is powered off, and an R-UIM simulator is used with the file 4
characteristics bits set as follows: 5
Bit b1 Bit b3 Bit b4 6
0 0 1 7
6) The ME is powered on. When the ME is in mode PIN check, 10 seconds shall 8
elapse before the PIN is entered. 9
7) The ME is powered off, and an R-UIM simulator is used with the file 10
characteristics bits set as follows: 11
Bit b1 Bit b3 Bit b4 12
1 0 0 13
8) The ME is powered on. When the ME is in mode PIN check, 10 seconds shall 14
elapse before the PIN is entered. 15
6.12.2.5 Test Requirement 16
1) During step 2), the ME shall not switch off the clock. 17
2) During step 4), the ME shall not switch off the clock, unless at high level. 18
3) During step 6), the ME shall not switch off the clock, unless at low level. 19
4) During steps 4), 6) and 8), the ME shall not switch off the clock until at least 20
1,860 clock cycles after having received the last character of the response 21
including the minimum guard time (2 etu). 22
5) During steps 4), 6) and 8), the ME shall wait at least 744 clock cycles before it 23
sends the first command after having restarted the clock. 24
6.12.3 Authentication 25
The ME shall conform to the test requirements defined in 6 (Authentication Tests) of [11]. 26
6.13 Mechanical Tests 27
The ME shall conform to the requirements specified in subclause 27.13 of [10]. 28
6.14 Secret Code Usage 29
6.14.1 Entry of PIN 30
The ME shall conform to the requirements specified in subclause 27.14.1 of [10]. 31
6.14.2 Change of PIN 32
The ME shall conform to the requirements specified in subclause 27.14.2 of [10]. 33
3GPP2 C.S0048-0
6-14
6.14.3 Disabling the PIN 1
6.14.3.1 Definition and Applicability 2
Entry of the PIN may be disabled by the user, depending on the service table of the R-UIM. 3
It is the responsibility of the ME to check the R-UIM service table. 4
This test applies to MEs conforming to [1] using either ID-1 or Plug-in R-UIM that support a 5
feature to disable the PIN. 6
6.14.3.2 Conformance Requirement 7
Disabling PIN is achieved through the DISABLE CHV command. If the PIN disable function 8
in the R-UIM service table is not allocated or activated, the ME shall not attempt to disable 9
the PIN. 10
6.14.3.3 Test Purpose 11
To verify that the ME does not attempt to disable the PIN. 12
6.14.3.4 Method of Test 13
6.14.3.4.1 Initial Conditions 14
The ME is connected to the R-UIM simulator. 15
Elementary files in the R-UIM simulator shall be set to the default values. EFCST (CDMA 16
Service Table) shall be set to the value defined for “EFCST Setting 3” in Table 5-1. 17
The ME is powered on and a correct PIN entered. 18
6.14.3.4.2 Procedure 19
Using the ME's user interface procedure, an attempt is made to disable the PIN. 20
6.14.3.5 Test Requirement 21
The ME shall not send a DISABLE CHV command across the R-UIM/ME interface. 22
6.14.4 PUK Entry 23
The ME shall conform to the requirements specified in subclause 27.14.4 of [10]. 24
6.14.5 Entry of PIN2 25
The ME shall conform to the requirements specified in subclause 27.14.5 of [10]. 26
6.14.6 Change of PIN2 27
The ME shall conform to the requirements specified in subclause 27.14.6 of [10]. 28
6.14.7 PUK2 Entry 29
The ME shall conform to the requirements specified in subclause 27.14.7 of [10]. 30
3GPP2 C.S0048-0
6-15
6.14.8 CDMA Service Table 1
6.14.8.1 Definition and Applicability 2
This test applies to MEs conforming to [1] using either ID-1 or Plug-in R-UIM. 3
6.14.8.2 Conformance Requirement 4
The ME shall read the contents of EFCST from the R-UIM and shall provide user access 5
and/or service to the functions and services allocated and activated within EFCST. 6
6.14.8.3 Test Purpose 7
6.14.8.4 Method of Test 8
6.14.8.4.1 Initial Conditions 9
Byte 1 of EFCST shall be coded as ‘01010101’ to indicate “service allocated” and “service not 10
activated” for the following services: SMS, FDN, ADN, and CHV1. 11
6.14.8.4.2 Procedure 12
1) Insert the R-UIM into the ME being tested and power on the MS. 13
2) Verify that the SMS, FDN, ADN, and CHV functions and services are inoperative. 14
3) Power off the MS and remove the R-UIM. 15
4) Code Byte 1 of EFCST on the R-UIM to ‘11111111’ to indicate “service allocated” 16
and “service activated” for SMS, FDN, ADN, and CHV1. 17
5) Insert the R-UIM into the ME being tested and power on the MS. 18
6) Verivy that the SMS, FDN, ADN, and CHV1 functions and services are 19
operational. 20
6.14.8.5 Test Requirement 21
The services and functions should be operational only when coded as “service allocated” 22
and “service activated” within EFCST. 23
6.15 Abbreviated Dialing Numbers (ADN) 24
6.15.1 Definition and Applicability 25
Abbreviated Dialing Numbers contain subscriber number and supplementary service 26
control strings. They may also contain alpha identifiers. 27
This test applies to both MEs conforming to [1] using either ID-1 or plug-in R-UIMs, that 28
support ADN. 29
6.15.2 Conformance Requirement 30
The ME shall be able to update and retrieve ADNs from the R-UIM and set up calls to these 31
numbers. 32
3GPP2 C.S0048-0
6-16
6.15.3 Test Purpose 1
To verify that the ME can update and retrieve ADNs from the R-UIM. 2
6.15.4 Method of Test 3
6.15.4.1 Initial Conditions 4
EFCST shall be set in accordance with “EFCST Setting 2” described in Table 5-1. 5
Coding of elementary files in the R-UIM shall be as default, with the addition of: 6
EFADN (Abbreviated Dialing Number) 7
Logically: 8
At least 101 records. 9
Record 1: 10
Length of alpha identifier: 32 characters 11
Alpha identifier: "ABCDEFGHIJKLMNOPQRSTUVWXYZABCDEF" 12
Length of BCD number: "03" 13
TON and NPI: Telephony and Unknown 14
Dialed number: 123 15
CCI: None 16
Ext1: None 17
Coding for record 1: 18
B1 B2 B3 ... B32 B33 B34 B35 B36 B37 B38 B39 ... B46
41 42 43 ... 46 03 81 21 F3 FF FF FF ... FF
19
The ME is installed with the default R-UIM or R-UIM simulator, and switched on. 20
6.15.4.2 Procedure 21
1) The code "1234567890123456" is stored (entered) in the MS as abbreviated 22
dialing entry number 7 on the R-UIM. 23
2) The code "00112233" is stored (entered) in the MS as abbreviated dialing entry 24
number 6 on the R-UIM. 25
3) The code "**21*44556677#" is stored (entered) in the MS as abbreviated dialing 26
entry number 101 on the R-UIM. 27
4) Retrieve data from R-UIM entry number 7 using the procedure N(N)(N)#. 28
5) Retrieve data from R-UIM entry number 6 using the procedure N(N)(N)#. 29
6) Retrieve data from R-UIM entry number 101 using the procedure N(N)(N)#. 30
3GPP2 C.S0048-0
6-17
7) Retrieve data from R-UIM entry number 1 using the procedure N(N)(N)#, and 1
display the alpha identifier. 2
6.15.5 Test Requirements 3
1) After step 4), the number "1234567890123456" shall be displayed. 4
2) After step 5), the number "00112233" shall be displayed. 5
3) After step 6), the number "**21*44556677#" (or an equivalent representation) 6
shall be displayed. 7
4) After step 7), the ME shall display at least part of the alpha identifier, and shall 8
sustain normal operation. 9
6.16 UI Reaction to R-UIM Status Encoding 10
The ME shall conform to the requirements specified in subclause 27.16 of [10]. 11
6.17 Electrical Tests 12
The ME shall conform to the requirements specified in subclause 27.17 of [10] with the 13
following exception: the command “SELECT CDMA” shall be used in place of “SELECT 14
GSM”. 15
6.18 Fixed Dialing Number (FDN) 16
The ME shall conform to the requirements specified in subclause 27.18 of [10] with the 17
following exceptions: 18
1) Appropriate cdma2000 system simulator settings shall be used in place of the 19
GSM-specific settings identified in [10]. 20
2) Rehabilitation of EFLOCI is not applicable. 21
3) EFCST shall be set in accordance with “EFCST Setting 2” described in Table 5-1. 22
6.19 Version Identification 23
6.19.1 Definition and Applicability 24
The version of the R-UIM is indicated in the Elementary File EFRevision. This allows the ME to 25
identify the version of the R-UIM and adapt its functionality accordingly. 26
This test applies to MEs conforming to [1] using either ID-1 or plug-in R-UIMs. 27
6.19.2 Conformance Requirement 28
The version of the card shall be determined as part of the initialization procedure. 29
6.19.3 Test Purpose 30
To verify that the ME requests the R-UIM version (EFRevision) as part of the initialization 31
procedure. 32
3GPP2 C.S0048-0
6-18
6.19.4 Method of Test 1
6.19.4.1 Initial Conditions 2
The ME is connected to the R-UIM simulator and powered off. 3
The default values are used. 4
6.19.4.2 Procedure 5
1) The mobile is powered on. 6
2) The R-UIM simulator monitors the R-UIM initialization procedure. 7
6.19.5 Test Requirement 8
The ME shall request the version (EFRevision) of the R-UIM as part of the initialization 9
procedure. 10
6.20 R-UIM Presence Detection 11
The ME shall conform to the requirements specified in subclause 27.20 of [10]. 12
6.21 Reserved 13
6.22 Suggested Slot Cycle Index 14
6.22.1 Definition and Applicability 15
This test applies to MEs conforming to [1] using either ID-1 or Plug-in R-UIM. 16
6.22.2 Conformance Requirement 17
The ME shall read the contents of EFSSCI (Suggested Slot Cycle Index) and apply it to mobile 18
station processing. 19
6.22.3 Test Purpose 20
The purpose of this test is to ensure that the ME is able to read the contents of the EFSSCI 21
and compare this value with MAX_SLOT_CYCLE_INDEX obtained from the System 22
Parameters Message in determining the appropriate value to set SLOT_CYCLE_INDEX. 23
6.22.4 Method of Test 24
6.22.4.1 Initial Conditions 25
1) The mobile station shall be connected to a mobile station diagnostic monitor. 26
2) The mobile station shall be connected to a network system simulator. 27
3) The network system simulator shall be configured such that the value of 28
MAX_SLOT_CYCLE_INDEX within the System Parameters Message is set to ‘011’. 29
4) EFSSCI shall be set to the value ‘00000010’. 30
3GPP2 C.S0048-0
6-19
6.22.4.2 Procedure 1
1) Power on the mobile station. 2
2) Allow a sufficient time for the mobile station to complete power-up registration 3
with the network system simulator. Determine the value of the Slot Cycle Index 4
used by the mobile station. Also note the value of the preferred Slot Cycle Index 5
(SLOT_CYCLE_INDEX) reported by the mobile station in the Registration Message. 6
3) Power off the mobile station. 7
4) Configure the network system simulator such that the 8
MAX_SLOT_CYCLE_INDEX within the System Parameters Message is set to ‘001’. 9
5) Power on the mobile station. 10
6) Allow a sufficient time for the mobile station to complete power-up registration 11
with the network system simulator. Determine the value of the Slot Cycle Index 12
used by the mobile station. Also note the value of the preferred Slot Cycle Index 13
(SLOT_CYCLE_INDEX) reported by the mobile station in the Registration Message. 14
6.22.5 Test Requirement 15
As part of step 2 of the test procedure, the mobile station shall send a Registration Message 16
to the network system simulator with a preferred Slot Cycle Index (SLOT_CYCLE_INDEX) 17
value of ‘010’. Similarly, the mobile station shall be operating using a value of ‘010’ for the 18
Slot Cycle Index. 19
As part of step 6 of the test procedure, the mobile station shall send a Registration Message 20
to the network system simulator with a preferred Slot Cycle Index (SLOT_CYCLE_INDEX) 21
value of ‘010’. The mobile station shall also, however, be operating using a value of ‘001’ for 22
the Slot Cycle Index. 23
6.23 Service Provider Name 24
6.23.1 Definition and Applicability 25
This test applies to MEs conforming to [1] using either ID-1 or Plug-in R-UIM. 26
6.23.2 Conformance Requirement 27
The ME shall be capable of reading the contents of EFSPN and displaying the corresponding 28
information to the mobile station user. 29
6.23.3 Test Purpose 30
To verify that the ME is capable of reading and displaying the contents of EFSPN. 31
3GPP2 C.S0048-0
6-20
6.23.4 Method of Test 1
6.23.4.1 Initial Conditions 2
6.23.4.2 Procedure 3
1) Input the Service Provider Name with a length not more than 16 bytes on the R-4
UIM using a card reader/programmer. 5
2) Insert the R-UIM into the mobile station and power up the mobile station. Note 6
the appearance of the mobile station display. 7
3) Input the Service Provider Name with a length more than 16 bytes on the R-UIM 8
using a card reader/programmer. 9
4) Insert the R-UIM into the mobile station and power up the mobile station. Note 10
the appearance of the mobile station display. 11
6.23.5 Test Requirement 12
1) Following step 2 of the test procedure, verify the Service Provider Name is 13
displayed on the screen of the mobile station while in the idle state. 14
2) Following step 4 of the test procedure, verify the first 16 bytes of the Service 15
Provider Name is displayed on the screen of the mobile station while in the Mobile 16
Station Idle State. 17
