ARIB STD-T53-C.S0031-0 Signaling Conformance Tests for ... · 1 Original Specification 2 This standard, ARIB-T53-C.S0031-0, was prepared by T53WG of Association of Radio Industries

ARIB STD-T53-C.S0031-0

Signaling Conformance Tests for cdma2000

Spread Spectrum Systems

Refer to "Industrial Property Rights (IPR)" in the preface of ARIB STD-T53 for Related Industrial

Property Rights. Refer to "Notice" in the preface of ARIB STD-T53 for Copyrights.

Original Specification 1

This standard, ARIB-T53-C.S0031-0, was prepared by T53WG of Association of Radio Industries 2

and Businesses (ARIB) based upon the 3GPP2 specification, C.S0031-0 v2.0. 3

4

Modification to the original specification 5

None. 6

7

Notes 8

None. 9

3GPP2 TSG-C

Date: October 15, 2001

Signaling Conformance Tests for cdma2000Spread Spectrum Systems

Ballot Resolution Version

C.S0031-0 version 2.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.

Copyright © 2001 3GPP2.

TSG-C42 Page i

CONTENTS

10/19/2001 C.S0031

1

FOREWORD........................................................................................................................... xviii2

Introduction........................................................................................................................ xviii3

Testing Objective................................................................................................................. xviii4

Execution Strategy................................................................................................................ xix5

Acronyms and Abbreviations .............................................................................................. xxiii6

Supplementary Terms and Definitions................................................................................ xxix7

CDMA Equations ............................................................................................................... xlviii8

Tolerances.................................................................................................................................l9

Normative Document References ..............................................................................................l10

1 Miscellaneous Air Iterface Tests ........................................................................................ 1-111

1.1 Pilot PN Offset ............................................................................................................... 1-112

1.2 Hashing CDMA Channels, Paging Channels, and Paging Slot....................................... 1-213

1.3 Idle Ping Pong with Quick Paging Channel CCI............................................................. 1-414

1.4 Quick Paging Indicator.................................................................................................. 1-615

1.5 Mobile Station Processing of the Access Parameters Message ....................................... 1-816

1.6 Mobile Station Processing of MIN_P_REV.................................................................... 1-1017

1.7 Mobile Station Response to Status Request Message .................................................. 1-1118

1.8 Protocol Discriminator (PD) Test and Link Access Control (LAC) PDU Format Test on the19Access Channel........................................................................................................... 1-1220

1.9 Logging Tests .............................................................................................................. 1-1521

1.10 SYNC Channel Support ............................................................................................. 1-2622

2 POTS Tests........................................................................................................................ 2-123

2.1 Mobile Station Originated Call ...................................................................................... 2-324

2.2 Mobile Station to Land Party Call, Radio Link Failure During Conversation - Reverse Link2-625

2.3 Mobile Station to Land Party, Radio Link Failure During Conversation - Forward Link 2-626

2.4 Mobile Station Originated Call, Test Service Options .................................................... 2-727

2.5 Mobile Station to Land Party Call, Busy Tone............................................................... 2-828

2.6 Mobile Station to Land Party Call, No Traffic Channel Resources Available .................. 2-829

2.7 Mobile Station to Land Party Call, Reverse Link Failure During Call Setup.................. 2-930

2.8 Mobile Station to Land Party Call, Forward Link Failure During Call Setup................. 2-931

2.9 Mobile Station Terminated Call................................................................................... 2-1032

2.10 Mobile Station terminated Call, Test Service Options................................................ 2-1233

2.11 Land Party to Mobile Station Call, Mobile Operating in Slotted Mode........................ 2-1334

TSG-C42 Page ii

CONTENTS

10/19/2001 C.S0031

2.12 MSID, MCC, and IMSI ............................................................................................... 2-141

2.13 TMSI Assignment ...................................................................................................... 2-172

2.14 TMSI Expiration Time................................................................................................ 2-173

2.15 Mobile Station to Land Party Call, DTMF .................................................................. 2-184

2.16 Forward Traffic Channel DTMF Tone Signaling......................................................... 2-215

2.17 Enhanced DTMF Signaling........................................................................................ 2-226

2.18 Channel Assignment from CDMA to AMPS................................................................ 2-227

2.19 PACA Origination, User Terminates While Still In Queue .......................................... 2-238

2.20 PACA Origination, Idle Handoff While in Queue ........................................................ 2-249

2.21 PACA Origination, Traffic Channel Becomes Available .............................................. 2-2610

2.22 PACA Origination, Features Interaction..................................................................... 2-2611

2.23 PACA Origination, Permanent Invocation .................................................................. 2-2712

2.24 PACA Origination, PACA Disabled for Mobile Station ................................................ 2-2813

2.25 True IMSI Support..................................................................................................... 2-2914

2.26 Initial Service Configuration and Negotiation ............................................................ 2-3115

2.27 Base Station Requested Service Negotiation (Successful Scenarios) .......................... 2-3516

2.28 Base Station Reject Scenarios during Service Negotiation......................................... 2-3717

2.29 Mobile Station Reject Scenarios during Service Negotiation ...................................... 2-4018

2.30 Service Negotiation Completion via General Handoff Direction Message and Universal19Handoff Direction Message .......................................................................................... 2-4120

2.31 SCR without NN-SCR and NN-SCR without SCR in General Handoff Direction Message21and Universal Handoff Direction Message.................................................................... 2-4222

2.32 Base Station Request Overrides the Mobile Station Request ..................................... 2-4423

2.33 Service Negotiation Involving Partial SCR and/or Partial NN-SCR............................. 2-4524

2.34 Quasi-Orthogonal Functions (QOF) assignment........................................................ 2-4625

2.35 Release Order on Access Channel ............................................................................. 2-4726

3 Handoff Tests .................................................................................................................... 3-127

3.1 Soft Handoff with Dynamic Threshold........................................................................... 3-128

3.2 Hard Handoff Between Frequencies in the Same Band Class ....................................... 3-729

3.3 Hard Handoff from CDMA to AMPS............................................................................... 3-930

3.4 Soft Handoff in Fading ................................................................................................ 3-1031

3.5 Hard Handoff in Fading .............................................................................................. 3-1432

3.6 Hard Handoff Between Different Band Classes ........................................................... 3-1633

3.7 Hard Handoff with and without Return on Failure...................................................... 3-1734

3.8 Search Window Size and Offset Per Neighbor.............................................................. 3-1935

TSG-C42 Page iii

CONTENTS

10/19/2001 C.S0031

3.9 Access Handoffs .......................................................................................................... 3-251

3.10 Traffic Channel Preamble during Hard Handoff Between Frequencies in same band 3-322

3.11 Hopping Pilot Beacon ................................................................................................ 3-333

3.12 Hard Handoff Between Frequencies with Different Radio Configurations.................. 3-354

3.13 Handoff on Same Frequency with Different Radio Configurations............................. 3-365

3.14 Hard Handoff while in the Waiting for Mobile Station Answer Substate .................... 3-386

3.15 Inter-Frequency Hard Handoff (CDMA to CDMA) ...................................................... 3-397

3.16 Inter-Frequency Hard Handoff (CDMA to AMPS) ....................................................... 3-418

3.17 Hard Handoff Between Frequencies with Different Protocol Revisions....................... 3-439

4 Power Control Tests .......................................................................................................... 4-110

4.1 Forward Traffic Channel Power Control ........................................................................ 4-111

4.2 Mobile Station Response to Power Up Function (PUF) Message ..................................... 4-412

4.3 Fast Forward Power Control (FFPC) .............................................................................. 4-813

5 Registration Tests.............................................................................................................. 5-114

5.1 Power-Up Registration .................................................................................................. 5-115

5.2 Power-Down Registration.............................................................................................. 5-216

5.3 Timer-Based Registration.............................................................................................. 5-417

5.4 Distance-Based Registration ......................................................................................... 5-518

5.5 Zone-Based Registration ............................................................................................... 5-919

5.6 Parameter-Change Registration .................................................................................. 5-1120

5.7 Registration Under Various Settings of MOB_TERM ................................................... 5-1321

6 Authentication Tests ......................................................................................................... 6-122

6.1 Shared Secret Data Initialized to Zero........................................................................... 6-123

6.2 Shared Secret Data Update on the Paging/Access Channels ........................................ 6-324

6.3 Shared Secret Data Update on the Forward/Reverse Traffic Channels ......................... 6-425

6.4 Mismatched A-Keys....................................................................................................... 6-526

6.5 Activating Voice Privacy on Call Setup.......................................................................... 6-627

6.6 Activating Voice Privacy at the Mobile Station When a Call Is Active ............................ 6-728

6.7 Signaling Message Encryption on Forward Traffic Channel (Alert with Information29Message) ....................................................................................................................... 6-830

6.8 Signaling Message Encryption on Reverse Traffic Channel (Burst DTMF Message) ....... 6-931

6.9 Hard Handoffs between Base Stations with SME Active................................................ 6-932

6.10 Signaling Message Encryption Mobile Terminated SMS (Data Burst Message) .......... 6-1133

6.11 Authentication Upon Originations............................................................................. 6-1234

6.12 Hard Handoff from CDMA to AMPS with SME Active ................................................ 6-1335

TSG-C42 Page iv

CONTENTS

10/19/2001 C.S0031

7 Service Redirection............................................................................................................ 7-11

7.1 Global Service Redirection Tests ................................................................................... 7-12

7.2 Network Directed System Selection and Normal Service Redirection Tests ................... 7-63

7.3 Extended Global Service Redirection Tests ................................................................. 7-114

8 Short Message Service (SMS)............................................................................................. 8-15

8.1 Mobile Station Terminated SMS Tests........................................................................... 8-26

8.2 Mobile Station Originated SMS Tests ............................................................................ 8-97

8.3 Broadcast SMS Tests .................................................................................................. 8-148

9 Subscriber Calling Features Tests..................................................................................... 9-19

9.1 Call Forwarding............................................................................................................. 9-110

9.2 Three-Way Calling......................................................................................................... 9-411

9.3 Land Party to Mobile Station Caller ID.......................................................................... 9-612

9.4 Call Waiting .................................................................................................................. 9-813

9.5 Message Waiting Indicator (MWI) .................................................................................. 9-914

9.6 Land Party to Mobile Station Calling Name Presentation ............................................ 9-1115

9.7 Display Records .......................................................................................................... 9-1416

9.8 TTY/TDD .................................................................................................................... 9-1717

9.9 Answer Holding........................................................................................................... 9-1918

9.10 User Selective Call Forwarding .................................................................................. 9-2119

10 Asynchronous Data and Fax Services ............................................................................. 10-120

10.1 Send/Receive Fax...................................................................................................... 10-321

10.2 Upload/Download Binary File ................................................................................... 10-422

10.3 Simultaneous Two-way File Transfer/Carrier Detect................................................. 10-423

10.4 Compound AT Command, Initialization and Connection Delay................................. 10-624

10.5 Escaping to Command Mode ..................................................................................... 10-625

10.6 Air Interface Data Compression................................................................................. 10-726

10.7 RLP Operation in a Poor RF Environment ................................................................. 10-827

10.8 RLP Abort and TCP Retransmit Test........................................................................ 10-1028

10.9 Internet Control Message Protocol (ICMP) Requests/Replies ................................... 10-1229

10.10 Reflection of AT Command Parameters ............................................................... 10-1330

11 Packet Data Services Tests.............................................................................................. 11-131

11.1 Terminal Session with Remote Host .......................................................................... 11-332

11.2 File Transfer .............................................................................................................. 11-333

11.3 IP Address Negotiation............................................................................................... 11-434

TSG-C42 Page v

CONTENTS

10/19/2001 C.S0031

11.4 V-J Header Compression........................................................................................... 11-41

11.5 Aynchronous Control Character Mapping (ACCM) Negotiation.................................. 11-52

11.6 PPP Field Compression.............................................................................................. 11-53

11.7 Maximum Receive Unit (MRU) ................................................................................... 11-64

11.8 Mobile Station Inactivity Timer.................................................................................. 11-65

11.9 IWF Inactivity Timer .................................................................................................. 11-76

11.10 Radio Link Protocol (RLP) Operation in Rayleigh Fading....................................... 11-77

11.11 RLP Abort and Upper Layer Retransmit ................................................................ 11-98

11.12 RLP Encryption Negotiation ................................................................................ 11-119

11.13 Hardware Flow Control ....................................................................................... 11-1210

11.14 Re-connect after Hard Handoff............................................................................ 11-1311

11.15 Zone-Based Registration for Packet Data Mobile Stations................................... 11-1312

12 Medium-Speed Packet Data ............................................................................................ 12-113

12.1 Forward File Transfer with Fundamental and Supplemental Code Channels............ 12-114

12.2 Forward File Transfer with Variable Supplemental Code Channels........................... 12-315

12.3 MSPD Call Setup, No Negotiation.............................................................................. 12-416

12.4 MSPD Call Setup, Negotiation to a Different MSPD Service Option ........................... 12-517

12.5 MSPD Call Setup, Negotiation to LSPD...................................................................... 12-618

12.6 MSPD Call Setup, Mobile Station Maximum Multiplex Option Less than Base Station19Maximum Multiplex Option ........................................................................................ 12-820

12.7 MSPD Call Setup, Mobile station Maximum Multiplex Option Greater than Base Station21Maximum Multiplex Option ........................................................................................ 12-822

12.8 Allocation/De-allocation of Supplemental Code Channels ........................................ 12-923

12.9 No Transmission on Supplemental Code Channels ................................................. 12-1124

12.10 Soft Handoff with Supplemental Code Channels................................................. 12-1225

12.11 Adding Supplemental Code Channels during Soft Handoff ................................. 12-1326

12.12 Hard Handoff to an MSPD-Capable System........................................................ 12-1427

12.13 RLP Operation in Rayleigh Fading Environment ................................................. 12-1628

12.14 RLP Operation with Severely Degraded Channel................................................. 12-1829

12.15 Bi-Directional File Transfers with Forward Supplemental Code Channels.......... 12-1930

12.16 Rм Interface Flow Control .................................................................................... 12-1931

12.17 Dormant Timer ................................................................................................... 12-2032

12.18 Packet Zone ID.................................................................................................... 12-2133

13 High Speed Packet Data.................................................................................................. 13-134

13.1 Forward File Transfer ................................................................................................ 13-235

TSG-C42 Page vi

CONTENTS

10/19/2001 C.S0031

13.2 Reverse File Transfer ................................................................................................. 13-41

13.3 Bi-directional File Transfer........................................................................................ 13-62

13.4 Basic Supplemental Channel Configuration Setting and Single Assignment............. 13-73

13.5 Supplemental Channel Multiple Assignments......................................................... 13-124

13.6 Turbo Coding on Supplemental Channel................................................................. 13-215

13.7 Correct Walsh Cover................................................................................................ 13-226

13.8 Supplemental Channel Discontinuous Transmission.............................................. 13-237

13.9 Slotted Timer........................................................................................................... 13-258

13.10 Retry Order and Delay for Origination Message................................................... 13-279

13.11 Retry Order and Delay for Supplemental Channel Request Messages................. 13-2910

13.12 Retry Order and Delay for Resource Request Messages....................................... 13-3011

13.13 Base Station Initiated Active to Control Hold Mode Transitions.......................... 13-3212

13.14 Mobile Station Initiated Active to Control Hold Mode Transitions ....................... 13-3413

13.15 Base Station Initiated Control Hold to Active Mode Transitions.......................... 13-3614

13.16 Mobile Station Initiated Control Hold to Active Mode Transitions ....................... 13-3715

13.17 Base Station Ignores Mobile Station Requested Mode Transitions...................... 13-3916

13.18 Mobile station Multiplex Option different from Base Station Multiplex Option ... 13-4017

13.19 Soft Handoff of Fundamental Channel and Supplemental Channels .................. 13-4118

13.20 Soft Handoff of Fundamental Channel only ........................................................ 13-4319

13.21 Adding Supplemental Channels during Soft Handoff.......................................... 13-4420

13.22 Hard Handoff to HSPD-capable system............................................................... 13-4521

13.23 Hard Handoff from MSPD to HSPD..................................................................... 13-4622

13.24 Hard Handoff from LSPD to HSPD...................................................................... 13-4723

13.25 Hard Handoff to a different RC............................................................................ 13-4924

13.26 Mobile Station Aborts R-SCH.............................................................................. 13-5025

13.27 RLP Operation in Rayleigh Fading Environment ................................................. 13-5226

13.28 RLP Operation in Severely Degraded Channel..................................................... 13-5427

13.29 Mobile Station Originated Short Data Burst ....................................................... 13-5528

13.30 Mobile Station Terminated Short Data Burst...................................................... 13-5729

13.31 Mobile Assisted Burst Operation Parameters Message Test ................................ 13-5830

13.32 Mobile Station and Base Station Operating in Different States........................... 13-6031

Data Services Tests Annex.................................................................................................. 13-6332

14 Over-The-Air Services...................................................................................................... 14-133

14.1 OTASP Service Request Processing............................................................................ 14-134

14.2 OTAPA Service Request Processing for a Mobile Station in Mobile Station Idle State . 14-435

TSG-C42 Page vii

CONTENTS

10/19/2001 C.S0031

14.3 OTAPA Service Request Processing for a Mobile Station in Conversation Substate ... 14-61

14.4 OTAPA Service Request Processing Interrupted by User Action................................. 14-82

15 System Selection for Preferred Roaming.......................................................................... 15-13

15.1 OTASP Service Provisioning For System Selection and Preferred Roaming................ 15-14

15.2 Non-Acquisition of a System on Negative Preferred Roaming List (PRL)..................... 15-35

15.3 Emergency Call On a System that is Negative on PRL or SID List ............................. 15-46

15.4 OTASP For System Selection and Preferred Roaming - Oversize PRL ........................ 15-57

15.5 OTAPA Service Provisioning for System Selection and Preferred Roaming for a Mobile8Station in Mobile Station Idle State .............................................................................. 15-79

16 Message Driven Indicators .............................................................................................. 16-110

16.1 Enhanced Roaming Indicator .................................................................................... 16-111

17 Forward Compatibility Tests ........................................................................................... 17-112

17.1 Sync Channel ............................................................................................................ 17-113

17.2 Paging Channel ......................................................................................................... 17-214

17.3 Traffic Channel.......................................................................................................... 17-315

Annex A: Power Ratios for Common and Traffic Channels ...................................................... A-116

Annex B: Tables of Logging Counters......................................................................................B-117

Annex C: TTY/TDD Test Examples .........................................................................................C-118

Annex D: Information Records................................................................................................D-11920

TSG-C42 Page viii

FIGURES

10/19/2001 C.S0031

Figure 1.1.2-1 Basic Setup for Air Interface Tests, Single Base Station .................................. 1-21

Figure 1.4.1-1 Reference Call Flow for QPI Testing ................................................................. 1-72

Figure 1.8.1-1 Reference Call Flow for LAC Testing .............................................................. 1-133

Figure 1.9.1-1 Reference Call Flow for Initial FCH, DCCH, SCCH, and SCH counters.......... 1-164

Figure 1.9.2.1-1 Reference Call Flow for Setting and Retrieving FCH/DCCH Logging Parameters5............................................................................................................................................. 1-186

Figure 1.9.4.1-1 Reference Call Flow for Setting and Retrieving SCCH Logging Parameters . 1-227

Figure 1.9.5.1-1 Reference Call Flow for Setting and Retrieving SCH Logging Parameters.... 1-248

Figure 1.10.2-1 Basic Setup for Air Interface Tests, Single Base Station .............................. 1-279

Figure 2.1.1-1 Reference Call Flow for mobile station Originated Voice Call from a Land Party10Call ......................................................................................................................................... 2-311

Figure 2.1.2-1 Functional Setup for Mobile Station Originated Voice Call to a Land Party Call12Test......................................................................................................................................... 2-413

Figure 2.9.1-1 Reference Call Flow for Mobile Station Terminated Voice Call from a Land Party14Call ....................................................................................................................................... 2-1115

Figure 2.15.2-1 Functional Setup for Testing Mobile Station-Initiated DTMF Tones............. 2-1916

Figure 2.18.2-1 Functional Setup for Redirection from CDMA to AMPS ............................... 2-2317

Figure 2.20.2-1 Functional Setup for Idle Handoff PACA Test .............................................. 2-2518

Figure 2.26.1-1 Reference Call Flow for Initial Service Configuration and Negotiation.......... 2-3219

Figure 2.27.1-1 Reference Call Flow for Base Station Requested Service Negotiation ........... 2-3620

Figure 2.28.1 Reference Call Flow for Base Station Reject Scenarios.................................... 2-3821

Figure 2.29.1-1 Reference Call Flow for Mobile Station Reject Scenarios.............................. 2-4022

Figure 2.30.1-1 Reference Call Flow for Using GHDM/UHDM instead of SCM ..................... 2-4123

Figure 3.1.2-1 Functional Test Setup for Testing Soft Handoff with Dynamic Threshold........ 3-324

Figure 3.4.2-1 Functional Setup for Testing Soft Handoff in Fading..................................... 3-1125

Figure 3.8.2-1 Functional Setup for Testing Search Window per Neighbor........................... 3-2026

Figure 3.9.2.2-1 Functional Setup for Testing Access Probe Handoffs.................................. 3-2727

Figure 4.1.2-1 Functional Setup for Testing Forward TCH Power Control .............................. 4-228

Figure 4.2.2.1-1 Mobile station TX Power Response to Power Up Function Parameters, Nominal29Power ...................................................................................................................................... 4-630

Figure 4.2.2.2-1 Mobile Station TX Power Response to Power-up Function Parameters,31Maximum Power ..................................................................................................................... 4-732

TSG-C42 Page ix

FIGURES

10/19/2001 C.S0031

Figure 4.3.1.3.1-1 Functional Setup for Testing Fast Forward Power Control ........................ 4-91

Figure 4.3.3.2. 1-1 Functional Setup for Testing FFPC in Handoff ....................................... 4-222

Figure 4.3.5.1.1-1 Reverse Pilot Gating with no Transmission on the Reverse Dedicated Control3Channel [1] 2.1.3.2.3 ............................................................................................................ 4-314

Figure 4.3.5.1.1-2 Reverse Pilot Gating during Reverse Dedicated Control Channel5Transmission [1] 2.1.3.2.3 .................................................................................................... 4-326

Figure 4.3.5.2.1-1 Gating with the R-FCH ............................................................................ 4-347

Figure 5.1.2.1-1 Functional Setup for Testing Power-up Registration..................................... 5-28

Figure 5.4.2.1-1 Functional Setup for Testing Distance-Based Registration........................... 5-79

Figure 6.1.2-1 Functional Setup for Authentication Tests ...................................................... 6-210

Figure 6.9.2-1 Functional Setup for Hard Handoffs between Base Stations with SME Active6-1111

Figure 7.1.1.2-1 Functional Setup for Service Redirection Tests............................................. 7-212

Figure 8-1 SMS Reference Model ............................................................................................ 8-213

Figure 8.3.1.2-1 Functional Setup for Broadcast SMS Tests ................................................ 8-1514

Figure 9.1.2.1-1 Functional Setup for Testing Call Forwarding .............................................. 9-215

Figure 9.2.2-1 Functional Setup for Testing Three-Way Calling.............................................. 9-516

Figure 9.8.2-1 Functional Setup for Testing TTY/TDD ......................................................... 9-1817

Figure 9.9.1-1 Reference Call Flow for Answer Holding......................................................... 9-2018

Figure 10-1. Asynchronous Data Services Reference Model.................................................. 10-119

Figure 10.7.2-1 Test Setup for RLP Operation in Poor RF Environment Test Parameters ..... 10-920

Figure 10.8.2-1 Test Setup for RLP Abort in Forward Link ................................................. 10-1021

Figure 10.8.2-2 Test Setup for RLP Abort in Reverse Link .................................................. 10-1122

Figure 11-1 Packet Data Services Reference Model............................................................... 11-223

Figure 11.10.2-1 Test Setup for RLP Operation in Rayleigh Fading in Forward Link............ 11-824

Figure 11.10.2-2 Test Setup for RLP Operation in Rayleigh Fading in Reverse Link............. 11-825

Figure 11.11.2-1 Test Setup for RLP Abort in Forward Link ............................................... 11-1026

Figure 11.11.2-2 Test Setup for RLP Abort in Reverse Link ................................................ 11-1127

Figure 13.1.2-1 Functional Setup for HSPD Throughput Tests............................................. 13-228

Figure 13.4.1-1 Reference Call Flow for Supplemental Channel Request and Assignment ... 13-829

Figure 13.5.2-1 Supplemental Channel Assignments for overlapped burst period.............. 13-1330

Figure 13.5.2-2 Supplemental Channel Assignments for disjoint burst periods ................. 13-1431

TSG-C42 Page x

FIGURES

10/19/2001 C.S0031

Figure 13.5.2-3 Supplemental Channel Assignments for assignment overwrite.................. 13-141

Figure 13.9.1-1 Reference Call Flow for Slotted Timer Testing............................................ 13-252

Figure 13.10.1-1 Reference Call Flow for Retry Order and Delay Test (Origination Message) .. 13-3274

Figure 13.11.1-1 Reference Call Flow for Retry Order and Delay Test (Supplemental Channel5Request Messages) .............................................................................................................. 13-296

Figure 13.12.1-1 Reference Call Flow for Retry Order and Delay Test (Resource Request7Messages) ........................................................................................................................... 13-318

Figure 13.13.1-1 Reference Call Flow for base station initiated Active to Control Hold Transition9........................................................................................................................................... 13-3310

Figure 13.14.1-1 Reference Call Flow for mobile station initiated Active to Control Hold11Transition ........................................................................................................................... 13-3512

Figure 13.15.1-1 Reference Call Flow for base station initiated Control Hold to Active Transition13........................................................................................................................................... 13-3614

Figure 13.16.1-1 Reference Call Flow for mobile station initiated Control Hold to Active15Transition ........................................................................................................................... 13-3816

Figure 13.19.2-1 Functional Test Setup for Soft Handoff of Fundamental Channel and17Supplemental Channels...................................................................................................... 13-4218

Figure 13.27.2-1 Functional Test Setup for RLP Operation in Rayleigh Fading Environment. 13-195320

Figure 14.1.2-1 Functional Setup for Testing OTASP............................................................ 14-121

Figure 15.1.2-1 Functional Setup for Testing System Selection and Preferred Roaming....... 15-222

Figure 16.1.2-1 Functional Setup for Testing Enhanced Roaming Indicator......................... 16-123

Figure 17.1.2-1 Functional Setup for Testing Forward Compatibility ................................... 17-2242526

TSG-C42 Page xi

FIGURES

10/19/2001 C.S0031

No text1

TSG-C42 Page xii

TABLES

10/19/2001 C.S0031

CDMA Base Station Protocol Revisions.................................................................................. xviii1

CDMA Mobile Station Protocol Revisions ............................................................................... xviii2

Extended Handoff Direction Message/General Handoff Direction Message/ Universal Handoff3Direction Message......................................................................................................................xx4

Analog Handoff Direction Message ............................................................................................xx5

System Parameters Message ....................................................................................................xxi6

Extended System Parameters Message.....................................................................................xxi7

Access Parameters Message ....................................................................................................xxii8

Values for Time Limits and Constants ....................................................................................xxii9

Table 1-1 Miscellaneous Tests ................................................................................................ 1-110

Table 1.3.2-1 Test Parameters for Extended System Parameters Message .............................. 1-511

Table 1.3.2-2. Test Parameters for Slotted Mode Idle Handoff................................................. 1-512

Table 1.5.2-1 Test Parameters for Mobile Station Response to Access Parameters Message Tests13............................................................................................................................................... 1-814

Table 1.5.2-2 Access Parameters Message Values for Mobile Station Response to Access15Parameters Message Tests ...................................................................................................... 1-916

Table 1.9.4.2-1...................................................................................................................... 1-2317

Table 1.9.5.2-1...................................................................................................................... 1-2518

Table 1.9.5.2-2...................................................................................................................... 1-2619

Table 2-1 POTS Tests.............................................................................................................. 2-120

Table 2.1.2-1 Call Setup Test Signal Channel Levels .............................................................. 2-421

Table 2.11.3-1 Slot Cycle Length Versus Various Values of MAX_SLOT_CYCLE_INDEX and22SLOT_CYCLE_INDEX............................................................................................................ 2-1423

Table 2.13.2-1 Extended System Parameters Message Values for TMSI Tests....................... 2-1724

Table 2.15.3.1-1 DTMF Assigned Frequencies ...................................................................... 2-2025

Table 2.15.3.3-1 Cumulative Binomial Distribution Function For 99.95% DTMF Success Rate2-262027

Table 2.15.3.3-2 DTMF Pass/Fail Criteria ............................................................................ 2-2028

Table 2.34.2-1 ECAM Parameters ......................................................................................... 2-4629

Table 3-1 Handoff Tests .......................................................................................................... 3-130

Table 3.1.2-1 Soft Handoff with Dynamic Threshold Test Parameters - T_ADD, T_DROP,31T_TDROP, ADD_INTERCEPTs, DROP_INTERCEPTs, SOFT_SLOPEs ........................................ 3-332

TSG-C42 Page xiii

TABLES

10/19/2001 C.S0031

Table 3.1.2-2 Dynamic Add Test – One Pilot ........................................................................... 3-41

Table 3.1.2-3 Dynamic Add Test – Two Pilots ......................................................................... 3-42

Table 3.1.2-4 Dynamic Drop Test - Three Pilots...................................................................... 3-43

Table 3.1.2-5 Dynamic Drop Test - Two Pilots ........................................................................ 3-54

Table 3.2.2-1 Hard Handoff Test Parameters .......................................................................... 3-75

Table 3.2.3-1 Limits of Audio Dropouts During Hard Handoff ................................................ 3-96

Table 3.3.2-1 Hard Handoff to AMPS, CDMA Test Parameters................................................ 3-97

Table 3.3.2-2 Hard Handoff to AMPS, Analog Test Parameters ............................................. 3-108

Table 3.4.2-1 Faded Soft Handoff Test Parameters - T_ADD................................................. 3-119

Table 3.4.2-2 Soft Handoff Test Parameters - T_DROP ......................................................... 3-1210

Table 3.4.2-3 Soft Handoff Levels.......................................................................................... 3-1311

Table 3.4.2-4 Soft Handoff Test Parameters - 100 km/hr..................................................... 3-1412

Table 3.5.2-1 Hard Handoff Test Parameters ........................................................................ 3-1513


Table 3.6.2-1 Hard Handoff: CDMA 800 to CDMA 1900 ....................................................... 3-1715


Table 3.8.2-1 Test Parameters for Search Window per Neighbor........................................... 3-2117

Table 3.9.2.2-1 Access Probe Handoff Test Parameters......................................................... 3-2818

Table 3.9.4.2-1 Channel Assignment into Soft Handoff Test Parameters .............................. 3-3119

Table 3.10.2-1 Hard Handoff Test Parameters ...................................................................... 3-3220

Table 3.10.3-1 Reverse Traffic Channel Preamble Length ..................................................... 3-3321




Table 3.16.2-2 Test Parameter for Inter-Frequency Handoff (Channel 2) .............................. 3-4225

Table 3.x.2-1 Hard Handoff Test Parameters ........................................................................ 3-4426

Table 4-1 Power Control Tests ................................................................................................ 4-127

Table 4.1.2-1 Test Parameters for Forward Power Control Tests............................................. 4-328

Table 4.2.2.1-1 Mobile Station Transmit Power Up Function Parameters, Nominal Power...... 4-529

Table 4.2.2.2-1 Mobile Station Transmit Power Up Function Parameters, Maximum Power... 4-630

Table 4.2.2.3-1 Mobile Station Transmit Power Up Function Parameters ............................... 4-731

TSG-C42 Page xiv

TABLES

10/19/2001 C.S0031

Table 4.3.1.2-1 Reverse Power Control Subchannel Configurations........................................ 4-91

Table 4.3.1.3.1-4 Test Parameters for Fast Forward Power Control ........................................ 4-92

Table 4.3.1.4.1-4 Test Parameters for Fast Forward Power Control ...................................... 4-113





Table 4.3.2.2-1 Test Parameters for Fast Forward Power Control ......................................... 4-188



Table 4.3.6.1.2-3 Test Parameters for EIB test ..................................................................... 4-3611

Table 5-1 Registration Tests.................................................................................................... 5-112

Table 5.4.2.1-1 Soft Handoff Test Parameters - T_ADD........................................................... 5-713

Table 6-1 Authentication Tests ............................................................................................... 6-114

Table 7-1 Service Redirection Tests......................................................................................... 7-115

Table 8-1 Short Message Service Tests ................................................................................... 8-116

Figure 8.1.6.2-1 Functional Setup for Voice Mail Notification................................................. 8-817

Table 8.3.1.2-1 Broadcast Messages and Priority ................................................................. 8-1518

Table 9-1 Subscriber Calling Features Tests........................................................................... 9-119

Table 10-1 Asynchronous Data and Fax Services Tests........................................................ 10-120

Introduction.......................................................................................................................... 10-121

Table 10.6.2-1 Compression Test Configurations ................................................................. 10-822

Table 11-1 Packet Data Services Tests.................................................................................. 11-123

Table 11.12.2 -1 RLP Encryption Configurations................................................................ 11-1224

Table 12-1 Medium-Speed Packet Data Tests ....................................................................... 12-125

Table 12.13.2-1 MSPD Test Parameters - 100 km/hr......................................................... 12-1726

Table 13.1.2-1 SCH Data Rate .............................................................................................. 13-327

Table 13.1.3-1 RLP Payloads................................................................................................. 13-428

Table 13.26.2-1 Test Parameters ........................................................................................ 13-5129

Table 13.27.2-1 HSPD Test Parameters - 100 km/hr ......................................................... 13-5430

Table 13.31.2-1 Test Parameters ........................................................................................ 13-5931

TSG-C42 Page xv

TABLES

10/19/2001 C.S0031

Table D-1 Test files to be used corresponding to tested rates. ............................................ 13-651

Table 14-1 Over-the-Air Services Tests ................................................................................. 14-12

Table 14.1.2-1 Activation Code Assignments ........................................................................ 14-23

Table 15-1 SSPR Tests.......................................................................................................... 15-14

Table 15.1.2-1 Activation Code Assignments ........................................................................ 15-25

Table 16-1 Message Driven Indicator Tests........................................................................... 16-16

Table 17-1 Forward Compatibility Tests ............................................................................... 17-17

Table A-1 Power Ratios for Common Channels.................................................................A-18

Table A-2 Test Parameters for Forward Fundamental Channel (Radio Configurations 1,3 and 4)9...............................................................................................................................................A-110

Table A-3 Test Parameters for Forward Fundamental Channel (Radio Configurations 2 and 5)A-11212

Table A-4 Test Parameters for Forward Dedicated Control Channel (Radio Configurations 3 and134).............................................................................................................................................A-214

Table A-5 Test Parameters for Forward Dedicated Control Channel (Radio Configurations 5) A-215

Table A-6 Test Parameters for Forward Supplemental Code Channel (Radio Configurations 1) A-16317

Table A-7 Test Parameters for Forward Supplemental Code Channel (Radio Configurations 2) A-18419

Table A-8 Test Parameters for Forward Supplemental Channel with 100% Frame Activity in20AWGN with Convolutional Coding (for Radio Configurations 3, 4) ..........................................A-421

Table A-9 Test Parameters for Forward Supplemental Channel with 100% Frame Activity in22AWGN with Convolutional Coding (for Radio Configuration 5) ................................................A-423

Table B-1 FCH Transmission Counters for Multiplex Option 0x1 ...........................................B-124

Table B-2 FCH Reception Counters for Multiplex Option 0x1.................................................B-125

Table B-3 FCH Transmission Counters for Multiplex Option 0x2 ...........................................B-326

Table B-4 FCH Reception Counters for Multiplex Option 0x2.................................................B-427

Table B-5 DCCH Transmission Counters for Multiplex Option 0x1 ........................................B-528

Table B-6 DCCH Reception Counters for Multiplex Option 0x1 ..............................................B-629

Table B-7 DCCH Transmission Counters for Multiplex Option 0x2 ........................................B-730

Table B-8 DCCH Reception Counters for Multiplex Option 0x2 ..............................................B-831

Table B-9 SCCH Transmission Counters ................................................................................B-932

Table B-10 SCCH Reception Counters ..................................................................................B-1033

TSG-C42 Page xvi

TABLES

10/19/2001 C.S0031

Table B-11 SCH Transmission Counters...............................................................................B-111

Table B-12 SCH Reception Counters ....................................................................................B-11234

TSG-C42 Page xvii

TABLES

10/19/2001 C.S0031

No text1

TSG-C42 Page xviii

10/19/2001 C.S0031

FOREWORD1

Introduction2This document facilitates interoperability testing between CDMA infrastructure and CDMA3mobile station manufacturers. It is applicable to P_REV_IN_USE equal to six.4Mobile station/manufacturers in the context of this entire document, refers to a subscriber5terminal and/or wireless local loop (WLL) unit. WLL units should be tested as if the WLL unit6were a mobile station.7The following tables specify CDMA Base Station Protocol Revisions and CDMA Mobile Station8Protocol Revisions for Band Class 0 and Band Class 1. They are included as a reference to9clarify P_REV and MOB_P_REV for backward/forward compatibility testing. . For the tests on10the band classes other than Band Class 0 and Band Class 1, the P_REV of the base station and11MOB_P_REV of the base station shall be set to six.12

13

CDMA Base Station Protocol Revisions14

P_REV Band Class 0 (Cellular) Band Class 1 (PCS)

1 IS-95 J-STD-008C

2 IS-95A N/A

3 IS-95A+ TSB74 N/A

4 N/A N/A

5 IS-95B IS-95B

6 IS-2000 IS-2000

7 IS-2000A IS-2000A

15

CDMA Mobile Station Protocol Revisions16

MOB_P_REV Band Class 0 (Cellular) Band Class 1 (PCS)

1 IS-95 J-STD-008C

2 IS-95A N/A

3 IS-95A + TSB74 N/A

4 IS-95B Phase I IS-95B Phase I

5 IS-95B Phase II IS-95B Phase II

6 IS-2000 IS-2000

7 IS-2000A IS-2000A

17

Testing Objective18The objective of testing contained herein is to demonstrate mobile station/base station standard19(MS-BSS) interoperability of all functionality, including messaging and protocol requirements,20in a cabled environment.21

TSG-C42 Page xix

10/19/2001 C.S0031

Execution Strategy1IS-2000 mobile stations should be compatibility tested in IS-95-A and TIA/EIA-95-B networks.2All features supported by the infrastructure such as Signaling Message Encryption,3Authentication, Voice Privacy, etc. should be enabled.4During signal conformance testing all applicable tests should be executed for all supported band5classes and radio configurations.6The following general comments apply to all tests:7

a. Whenever common channels and/or traffic channels are required to perform a test,8and their power ratios are not specified in the test, the power ratios specified in9Annex A should be used. Adjust the Orthogonal Channel Noise Simulator (OCNS)10gain such that power ratios (Ec/Ior) of all specified forward channels add up to one.11If OCNS is not available, the levels of code channels and attenuators should be12adjusted to maintain proper test parameters.13

b. During handoff tests between sectors of the same cell, Channel 2 from the beta14sector shall have a maximum relative offset of 1 µs from Channel 1 of the alpha15sector at the mobile station antenna connector.16

c. During soft and intersector handoff tests, the neighbor list of the base station in the17test shall include PN offsets of the other base station in the test.18

d. Pilot PN sequence offsets are denoted by Pi (i=1, 2, 3, ...). The following are assumed19unless otherwise specified:20• 0 <= Pi <= 51121• Pi not equal to Pj if i not equal to j22

• Pi mod PILOT_INC = 023

e. Base stations should be configured for normal operation as specified in IS-200024unless otherwise specified in a specific test.25

f. Unless otherwise specified, the Reverse Traffic Channel should be operated at a26sufficiently high Eb/No to ensure insignificant (for example, less than 1%) frame27error rate (FER).28

g. Overhead message fields should be those required for normal operation of the base29station unless otherwise specified in the following tables or in a specific test.30

31

TSG-C42 Page xx

10/19/2001 C.S0031

Extended Handoff Direction Message/General Handoff Direction Message/1Universal Handoff Direction Message2

Field Value(With Hard Handoff)

Value(Without Hard Handoff)

T_ADD 28 (-14 dB) 28 (-14 dB)

T_DROP 32 (-16 dB) 32 (-16 dB)

T_COMP 5 (2.5 dB) 5 (2.5 dB)

T_TDROP 3 (4 sec) 3 (4 sec)

HARD_INCLUDED(EHDM)/EXTRA_PARMS(GHDM/UHDM)

1 N/A

FRAME_OFFSET 0 N/A

PRIVATE_LCM 0 N/A

RESET_L2 1 N/A

RESET_FPC 1 N/A

SERV_NEG_TYPE 1 N/A

ENCRYPT_MODE 0 N/A

NOM_PWR_EXT 0 N/A

NOM_PWR 0 N/A

NUM_PREAMBLE 0 N/A

BAND_CLASS (user specify) N/A

CDMA_FREQ F2 N/A

PILOT_PN user specify N/A

PWR_COMB_IND 0 N/A

CODE_CHAN 1 to 63 (user specify) N/A

3

Analog Handoff Direction Message4

Field Value

SID Use appropriate number for AMPS system.

VMAC 3

ANALOG_CHAN Use appropriate AMPS channel of choice.

SCC Use one of three SAT Color Code (0, 1 or 2).

MEM 0

AN_CHAN_TYPE 0

DSCC_MSB 0

5

TSG-C42 Page xxi

10/19/2001 C.S0031

System Parameters Message1

Field Value(Physical Meaning)

SRCH_WIN_A 8 (60 chips)

SRCH_WIN_N 8 (60 chips)

SRCH_WIN_R 8 (60 chips)

NGHBR_MAX_AGE 0 (minimum amount)

PWR_THRESH_ENABLE 0 (threshold reporting off)

PWR_PERIOD_ENABLE 0 (periodic reporting off)

T_ADD 28 (-14 dB Ec/Io)

T_DROP 32 (-16 dB Ec/Io)

T_COMP 5 (2.5 dB)

T_TDROP 3 (4 sec)

QPCH_SUPPORTED 0 (QPCH disabled)

2

Extended System Parameters Message3

Field Value (Decimal)

SOFT_SLOPE 0 (0)

RLGAIN_TRAFFIC_PILOT 0 (0 dB)

45

TSG-C42 Page xxii

10/19/2001 C.S0031

Access Parameters Message1

Field Value (Decimal)

NOM_PWR 0 (0 dB)

INIT_PWR 0 (0 dB)

PWR_STEP 1 (1 dB)

NUM_STEP 4 (5 probes/sequence)

NOM_PWR_EXT 0 (0 dB)

2

h. Values of time limits and other constants should be as specified in IS-2000.3Selected values are listed in the following table.4

5

Values for Time Limits and Constants6

Constant Value Unit

N1m 9 frames

N2m 12 frames

N3m 2 frames

N11m 1 frame

T1b 1.28 seconds

T5m 5 seconds

T31m 600 seconds

T40m 3 seconds

T56m 0.2 seconds

T61m 0.08 seconds

7

TSG-C42 Page xxiii

10/19/2001 C.S0031

Acronyms and Abbreviations1Acronyms and abbreviations presented in this document, are defined as follows:2

3Acronym orAbbreviation

Description

AC Authentication Center

ACCM Asynchronous Control Character Map

ACCOLC Access Overload Class

AMPS Advanced Mobile Phone Service (AMPS)

AT Attention (condition in modem control)

AWGN Additive White Gaussian Noise

BPS Bits per Second

BS Base Station

CC Channel Configuration

CCI Base-station Configuration Change Indicator (sent on theQPCH)

CDG Code Division Multiple Access (CDMA) Development Group

CDMA Code Division Multiple Access

CDPD Cellular Digital Packet Data

CFSReqM Candidate Frequency Search Request Message

CMT Cellular Messaging Teleservice

CNA Calling Party Name

CNAP Calling Name Presentation

CFNA Call Forwarding No Answer

CNI Calling Number Identification

CPN Calling Party Number

CPT Cellular Paging Teleservice

CRC Cyclic Redundancy Code

CSC Customer Service Center

DCE Data Circuit Terminating Equipment

DCMS Display Capable Mobile Station

DTE Data Terminal Equipment

DTMF Dual Tone Multiple Frequency

DTX Discontinuous Transmission

ECAM Extended Channel Assignment Message

EHDM Extended Handoff Direction Message

EM Escape Mode

TSG-C42 Page xxiv

10/19/2001 C.S0031

ENLUM Extended Neighbor List Update Message

ESCAM Extended Supplemental Channel Assignment Message

ESN Electronic Serial Number

ESPM Extended System Parameter Message

FCS Frame Check Sequence

f-csch Forward Common Signaling (Logical) Channel

F-DCCH Forward Dedicated Control Channel

f-dsch Forward Dedicated Signaling (Logical) Channel

FER Frame Error Rate

F-FCH Forward Fundamental Channel

FFPC Fast Forward Power Control

FO Frame Offset

FPC Forward Power Control

F-PICH Forward Pilot Channel

FSCAMM Forward Supplemental Channel Assignment Mini Message

F-SCCH Forward Supplemental Code Channel

F-SCH Forward Supplemental Channel

F-SCH0 Forward Supplemental Channel Number 0

F-SCH1 Forward Supplemental Channel Number 1

FTP File Transfer Protocol

GHDM General Handoff Direction Message

GNLM General Neighbor List Message

HO Handoff

IMSI_M MIN based IMSI

IMSI_T True IMSI

IMSI_T_11_12 Mobile Country Code of IMSI_T

IMSI_T_S Supplement of the MIN-based IMSI

ITU International Telecommunication Union

IWF Inter-Working Function

LAC Link Access Control

MABO Mobile Assisted Burst Operation

MAC Medium Access Control

MC Message Center

MCC Mobile Country Code

MCC_M MIN based Mobile Country Code

MDR Medium Data Rate

TSG-C42 Page xxv

10/19/2001 C.S0031

MIN/MSIN Mobile Station Identification Number

MO Multiplex Option

MRU (Data) Maximum Receive Unit

MS Mobile Station

MSS Maximum Segment Size

MT Mobile Terminal

MWI Message Waiting Indicator

NAK Negative Acknowledgement.

NAM Number Assignment Module

NDSS Network Directed System Selection

NID Network Identifier

NNSCR Non-Negotiable Service Configuration Record

OA&M Operation, Administration, and Maintenance

OCNS Orthogonal Channel Noise Simulator

OLPC Outer Loop Power Control

ORM Origination Message

OOK On/Off Keying

OTAF Over-the-air Function

OTAPA Over-the-air Parameter Administration

OTASP Over-the-air Service Provisioning

OTD Orthogonal Transmit Diversity

OUNS Other User Noise Simulator

P_REV_IN_USE Protocol revision level in use

PACA Priority Access and Channel Assignment

PCF Packet Control Function

PD Protocol Discriminator

PDU Protocol Data Unit

PI Paging Indicator

PIN Personal Identification Number

PLC Private Long Code

PM Privacy Mode

PN Pseudo-random Noise

POTS Plain Old Telephone Service

PPDN Public Packet Data Network

PPP Point-To-Point Protocol

PRM Page Response Message

TSG-C42 Page xxvi

10/19/2001 C.S0031

PS Pilot Strength

PSAP Public Service Answering Point

PSTN Public Switching Telephone Network

PUF Power Up Function

QOF Quasi-Orthogonal Function

QPCH Quick Paging Channel

R-ACH Reverse Access Channel

RC Radio configuration

r-csch Reverse Common Signaling Channel

R-DCCH Reverse Dedicated Control Channel

r-dsch Reverse Dedicated Signaling (Logical) Channel

R-FCH Reverse Fundamental Channel

RLP Radio Link Protocol

RND Redirecting Name Delivery

RPC Reverse Power Control

R-PCSCH Reverse Power Control Subchannel

R-PICH Reverse Pilot Channel

RSCAMM Reverse Supplemental Channel Assignment Mini Message

R-SCCH Reverse Supplemental Code Channel

R-SCH Reverse Supplemental Channel

R-SCH0 Reverse Supplemental Channel Number 0

R-SCH1 Reverse Supplemental Channel Number 1

SAC Subscriber Access Control

SCM Station Class Mark

SCCLT Supplemental Channel Code List Table

SCM Station Class Mark

SCR Service Configuration Record

SCRM Supplemental Channel Request Message

SCRMM Supplemental Channel Request Mini Message

SDB Short Data Burst

SDU Service Data Unit

SME Signaling Message Encryption

SMS Short Message Service

SO Service Option

SPASM Subscriber Parameter Administration SecurityMechanism

TSG-C42 Page xxvii

10/19/2001 C.S0031

SR Service Redirection

SRQM Service Request Message

SSD Shared Secret Data

SSPR System Selection for Preferred Roaming

STS Space Time Spreading

TCH Traffic Channel

TCP Transmission Control Protocol

TDMA Time Division Multiple Access

TDSO Test Data Service Option

TE Terminal Equipment

TE2L Terminal Equipment at land connection point

TE2M Terminal Equipment at mobile connection point

TMSI Temporary Mobile Station Identity

TSB Technical Service Bulletin

UHDM Universal Handoff Direction Message

UI User Interface

V.42 ITU-T recommended error correction protocol

VCAS Valid Configuration Attribute Selection

VJ Van Jacobson (compression protocol)

VMN Voice Mail Notification

VMNI Voice Mail Notification Indicator

WC Walsh Code

WLL Wireless Local Loop

1

TSG-C42 Page xxviii

10/19/2001 C.S0031

1

23

TSG-C42 Page xxix

10/19/2001 C.S0031

1

Supplementary Terms and Definitions2Abbreviated Alert - An abbreviated alert is used to remind the mobile station user that3previously selected alternative routing features are still active.4AC - See Authentication Center.5Access Attempt - A sequence of one or more access probe sequences on the Access Channel6containing the same message. See also Access Probe and Access Probe Sequence.7Access Channel - A Reverse CDMA Channel used by mobile stations for communicating to the8base station. The Access Channel is used for short signaling message exchanges such as call9originations, responses to pages, and registrations. The Access Channel is a slotted random10access channel.11Access Channel Message - The information part of an access probe consisting of the message12body, length field, and CRC.13Access Channel Message Capsule - An Access Channel message plus the padding.14Access Channel Preamble - The preamble of an access probe consisting of a sequence of all-15zero frames that are sent at the 4800 bps rate.16Access Channel Request Message - An Access Channel message that is autonomously generated17by the mobile station. See also Access Channel Response Message.18Access Channel Response Message - A message on the Access Channel generated to reply to a19message received from the base station.20Access Channel Slot - The assigned time interval for an access probe. An Access Channel slot21consists of an integer number of frames. The transmission of an access probe is performed within22the boundaries of an Access Channel slot.23Access Entry Handoff - The act of transferring reception of the Paging Channel from one base24station to another, when the mobile station is transitioning from the Mobile Station Idle State to25the System Access State.26Access Handoff - The act of transferring reception of the Paging Channel from one base station27to another, when the mobile station is in the System Access State after an Access Attempt.28Access Overload Class - See Overload Class.29Access Probe - One Access Channel transmission consisting of a preamble and a message. The30transmission is an integer number of frames in length and transmits one Access Channel31message. See also Access Probe Sequence and Access Attempt.32Access Probe Handoff - A handoff that occurs while the mobile station is performing an Access33Attempt in the System Access State.34Access Probe Sequence - A sequence of one or more access probes on the Access Channel. The35same Access Channel message is transmitted in every access probe of an access attempt. See also36Access Probe and Access Attempt.37Access Sub-attempt - A sequence of one or more access probe sequences on the Access38Channel transmitted to one pilot, containing the same message content other than the reported39pilot information. See also Access Probe, Access Probe Sequence, and Access Attempt.40Acknowledgment - A Layer 2 response by the mobile station or the base station confirming that41a signaling message was received correctly.42Action Time - The time at which the action implied by a message should take effect.43Active Set - The set of pilots associated with the CDMA Channels containing Forward Traffic44Channels assigned to a particular mobile station.45

TSG-C42 Page xxx

10/19/2001 C.S0031

Active User Zone - A user zone in which the mobile station makes its presence known via an1explicit registration in order to activate tiered service features. See also CDMA Tiered Services,2User Zone, and Passive User Zone.3Aging - A mechanism through which the mobile station maintains in its Neighbor Set the pilots4that have been recently sent to it from the base station and the pilots whose handoff drop timers5have recently expired.6A-key - A secret, 64-bit pattern stored in the mobile station and HLR/AC. It is used to7generate/update the mobile station’s Shared Secret Data.8Assured Mode - Mode of delivery that guarantees (if a loss of channel is not declared) that a9PDU will be delivered to the peer. A PDU sent in assured mode is retransmitted by the LAC10sublayer, up to a maximum number of retransmissions, until the LAC entity at the sender11receives an acknowledgement for the PDU. See also Confirmation of Delivery.12Authentication - A procedure used by a base station to validate a mobile station’s identity.13Authentication Center (AC) - An entity that manages the authentication information related to14the mobile station.15Authentication Response (AUTHR) - An 18-bit output of the authentication algorithm. It is16used, for example, to validate mobile station registrations, originations and terminations.17Autonomous Registration - A method of registration in which the mobile station registers18without an explicit command from the base station.19Auxiliary Pilot Channel - A non-data-bearing, direct-sequence spread spectrum signal20optionally transmitted by a CDMA base station.21Auxiliary Transmit Diversity Pilot Channel. - A pilot channel, counterpart to an Auxiliary22Pilot Channel, that is transmitted by a CDMA base station from the non-primary antenna when23orthogonal transmit diversity is employed.24AWGN - Additive White Gaussian Noise.25Bad Frames - Frames classified as insufficient frame quality or as 9600 bps primary traffic only,26with bit errors.27Band Class - A set of frequency channels and a numbering scheme for these channels.28Base Station - A fixed station used for communicating with mobile stations. In this document,29the term base station refers to the entire cellular system infrastructure including transceiver30equipment and Mobile Switching Center.31Base Station Authentication Response (AUTHBS) - An 18-bit pattern generated by the32authentication algorithm. AUTHBS is used to confirm the validity of base station orders to33update the Shared Secret Data.34Base Station Random Variable (RANDBS) - A 32-bit random number generated by the mobile35station for authenticating base station orders to update the Shared Secret Data.36Blank-and-Burst - The preemption of an entire Traffic Channel frame’s primary traffic by37signaling traffic or secondary traffic. Blank-and-burst is performed on a frame-by-frame basis.38BLOB - Block of Bits.39bps - Bits per second.40Broadcast User Zone - A user zone that is identified to the mobile station by means of41broadcast messages. It corresponds to the RF coverage area of a particular set of cells and42sectors. See also CDMA Tiered Services and Mobile-Specific User Zone.43Call Disconnect - The process that releases the resources handling a particular call. The44disconnect process begins either when the mobile station user indicates the end of the call by45

TSG-C42 Page xxxi

10/19/2001 C.S0031

generating an on-hook condition or other call-release mechanism, or when the base station1initiates a release.2Call History Parameter (COUNT) - A modulo-64 event counter maintained by the mobile3station and Authentication Center that is used for clone detection.4Candidate Frequency - The frequency for which the base station specifies a search set, when5searching on other frequencies while performing mobile-assisted handoffs.6Candidate Set - The set of pilots that have been received with sufficient strength by the mobile7station to be successfully demodulated, but have not been placed in the Active Set by the base8station. See also Active Set, Neighbor Set, and Remaining Set.9CDMA - See Code Division Multiple Access.10CDMA Candidate Frequency - The Candidate Frequency specified for a search of CDMA11pilots.12CDMA Cellular System - The entire system supporting Domestic Public Cellular Service13operation as addressed by this Standard.14CDMA Channel - The set of channels transmitted between the base station and the mobile15stations within a given CDMA frequency assignment. See also Forward CDMA Channel and16Reverse CDMA Channel.17CDMA Channel Number - A number corresponding to the center of the CDMA frequency18assignment.19CDMA Frequency Assignment - A 1.23 MHz segment of spectrum. The center of a CDMA20frequency assignment is given by a CDMA Channel Number.21CDMA Preferred Set - The set of CDMA channel numbers in a CDMA system corresponding22to Frequency Assignments that a mobile station will normally search to acquire a CDMA Pilot23Channel. For CDMA cellular systems, the primary and secondary channels comprise the CDMA24Preferred Set.25CDMA Tiered Services - System features and services that are based on location, potentially26including private networks. User zones establish the availability of services. See also User Zone,27Broadcast User Zone, Mobile-Specific User Zone, Active User Zone, and Passive User Zone.28Chip - See PN Chip.29Chip Rate - Equivalent to the spreading rate of the channel. It is either 1.2288 Mcps or 3.686430Mcps.31CLNP - Connectionless Network Protocol (see ISO 8473-1988).32Code Channel - A subchannel of a Forward CDMA Channel. A Forward CDMA Channel33contains 64 code channels. Code channel zero is assigned to the Pilot Channel. Code channels 134through 7 may be assigned either to the Paging Channels or to the Traffic Channels. Code35channel 32 may be assigned either to a Sync Channel or to a Traffic Channel. The remaining36code channels may be assigned to Traffic Channels.37Code Division Multiple Access (CDMA) - A technique for spread-spectrum multiple-access38digital communications that creates channels through the use of unique code sequences.39Code Symbol - The output of an error-correcting encoder. Information bits are input to the40encoder and code symbols are output from the encoder. See Convolutional Code.41Configuration Change Indicator - A one-bit datum, sent on the Quick Paging Channel.42Appearance of the Configuration Change Indicator in the Quick Paging Channel serves to alert a43slotted mode mobile station, operating in the Mobile Station Idle State, that, after performing an44idle handoff, it should monitor the Paging Channel, in order to determine if it should update its45stored parameters.46

TSG-C42 Page xxxii

10/19/2001 C.S0031

Confirmation of Delivery - A notification sent by the LAC sublayer to Layer 3 at the sender,1when the LAC entity at the sender receives the acknowledgment for a specific PDU sent in2assured mode.3Convolutional Code - A type of error-correcting code. A code symbol can be considered as4modulo 2 the convolution of the input data sequence with the impulse response of a generator5function.6CRC - See Cyclic Redundancy Code.7Cyclic Redundancy Code (CRC) - A class of linear error detecting codes which generate parity8check bits by finding the remainder of a polynomial division.9Data Block - A unit of information exchanged between the mux sublayer and a service or an10upper layer signaling.11dBc - Ratio of the sideband power to carrier power as referenced to the carrier. For CDMA, the12total in-band power of the signal is measured in a 1.23 MHz bandwidth around the center13frequency of the CDMA signal.14dBm - A measure of power expressed in terms of its ratio to one milliwatt.15dBm/Hz - A measure of power spectral density. The ratio, dBm/Hz, is the power in one Hertz of16bandwidth, where power is expressed in units of dBm.17dBW - A measure of power expressed in terms of its ratio (in dB) to one watt.18Dedicated Control Channel - A portion of a Traffic Channel (Forward or Reverse) that carries19a combination of user data, signaling, and power control information.20Deinterleaving - The process of unpermuting the symbols that were permuted by the interleaver.21Deinterleaving is performed on received symbols prior to decoding.22Discontinuous Transmission (DTX) - A mode of operation in which a base station or a mobile23station switches on and off its transmitter on a particular code channel autonomously. For the24case of DTX operation on the Forward Dedicated Control Channel, the Forward Power Control25Subchannel is still transmitted.26Distance-Based Registration - An autonomous registration method in which the mobile station27registers whenever it enters a cell whose distance from the cell in which the mobile station last28registered exceeds a given threshold.29DTMF - See Dual-Tone Multifrequency.30Dual-Tone Multifrequency (DTMF) - Signaling by the simultaneous transmission of two tones,31one from a group of low frequencies and another from a group of high frequencies. Each group32of frequencies consists of four frequencies.33Eb - Average energy per information bit for the Sync Channel, Paging Channel, or Forward34Traffic Channel at the mobile station antenna connector.35Eb/No - Energy-per-bit-to noise-per-hertz ratio.36Eb/Nt - The ratio of the combined received energy per bit to the effective noise power spectral37density for the Sync Channel, Paging Channel, or Forward Traffic Channel at the mobile station38antenna connector.39Ec - Average energy per PN chip for the Pilot Channel, Sync Channel, Paging Channel, Forward40Traffic Channel, power control subchannel, or OCNS.41Ec/Io - A notation used to represent a dimensionless ratio of the average power of some code-42distinguished CDMA signal channel, typically a pilot, to the total power comprised of signal plus43interference, within the signal bandwidth. It is usually expressed in dB units.44

TSG-C42 Page xxxiii

10/19/2001 C.S0031

Ec/Ior - The ratio of the average transmit energy per PN chip for the Pilot Channel, Sync1Channel, Paging Channel, Forward Traffic Channel, power control subchannel, or OCNS to the2total transmit power spectral density.3Effective Radiated Power (ERP) - The product of the power supplied to the antenna and the4antenna gain relative to a half-wave dipole in a given direction.5EIRP - See Equivalent Isotropic Radiated Power.6Equivalent Isotropic Radiated Power (EIRP) - The product of the power supplied to the7antenna and the antenna gain in a direction relative to an isotropic antenna.8Erasure Indicator Bit - A bit used in the Rate Set 2 Reverse Traffic Channel frame structure to9indicate an erased Forward Fundamental Code Channel or Forward Dedicated Control Channel10frame.11ERP - See Effective Radiated Power.12ESN - Electronic Serial Number.13f-csch - Forward common signaling logical channel.14f-dsch - Forward dedicated signaling logical channel.15Fade Timer - A timer kept by the mobile station as a measure of Forward Traffic Channel16continuity. If the fade timer expires, the mobile station drops the call.17FER - Frame Error Rate of Forward Traffic Channel. The value of FER may be estimated by18using Service Option 2, 9, 30, or 31 (see TIA/EIA-126-C).19Flash - An indication sent on the CDMA Channel indicating that the receiver is to invoke special20processing.21Foreign NID Roamer - A mobile station operating in the same system (SID) but in a different22network (NID) from the one in which service was subscribed. See also Foreign SID Roamer and23Roamer.24Foreign SID Roamer - A mobile station operating in a system (SID) other than the one from25which service was subscribed. See also Foreign NID Roamer and Roamer.26Forward CDMA Channel - A CDMA Channel from a base station to mobile stations. The27Forward CDMA Channel contains one or more code channels that are transmitted on a CDMA28frequency assignment using a particular pilot PN offset. The code channels are associated with29the Pilot Channel, Sync Channel, Paging Channels, and Traffic Channels. The Forward CDMA30Channel always carries a Pilot Channel and may carry up to one Sync Channel, up to seven31Paging Channels, and up to 63 Traffic Channels, as long as the total number of channels,32including the Pilot Channel, is no greater than 64.33Forward Dedicated Control Channel - A portion of a Forward Traffic Channel that can carry a34combination of primary data, secondary data, signaling, and power control information.35Forward Fundamental Channel - A portion of a Forward Traffic Channel that can carry a36combination of primary data, secondary data, signaling, and power control information.37Forward Pilot Channel - A non-data-bearing direct-sequence spread spectrum signal38transmitted continuously by each CDMA base station. The Forward Pilot Channel allows a39mobile station to acquire the timing of the Forward CDMA Channel, provides a phase reference40for coherent demodulation, and provides a means for signal strength comparisons between base41stations for determining when to handoff. Different base stations are identified by different pilot42PN sequence time phases. See also Pilot PN Sequence, Pilot PN Sequence Offset.43Forward Supplemental Channel - An optional portion of a Forward Traffic Channel (Radio44Configurations 3 and above) that operates in conjunction with a Fundamental Channel and or the45

TSG-C42 Page xxxiv

10/19/2001 C.S0031

Dedicated Control Channel in that Traffic Channel, and (optionally) with other Supplemental1Channels to provide higher data rate services.2Forward Supplemental Code Channel - An optional portion of a Forward Traffic Channel3(Radio Configurations 1 and 2) that operates in conjunction with a Fundamental Channel in that4Traffic Channel, and (optionally) with other Supplemental Code Channels to provide higher data5rate services.6Forward Traffic Channel - A code channel used to transport user and signaling traffic from a7base station to a mobile station.8Forward Transmit Diversity Pilot Channel - A pilot channel transmitted by a CDMA base9station from the non-primary antenna when orthogonal transmit diversity is employed.10Frame - A basic timing interval in the system. For the Access Channel and Paging Channel a11frame is 20 ms long. For the Traffic Channel, the frame may be 20 ms or 5 ms long. For the Sync12Channel, a frame is 26.666... ms long.13Frame Category - A classification of a received Traffic Channel frame based upon transmission14data rate, the frame contents (primary traffic, secondary traffic, or signaling traffic), and whether15there are detected errors in the frame.16Frame Offset - A time skewing of Traffic Channel frames from System Time in integer17multiples of 1.25 ms. The maximum frame offset is 18.75 ms.18Frame Quality Indicator - The CRC check applied to the 9600 bps and 4800 bps frames of19Rate Set 1 and all frames of Rate Set 2.20Full TMSI - The combination of TMSI_ZONE and TMSI_CODE. The full TMSI is a globally21unique address for the mobile station.22Fundamental Data Block - A data block that is transmitted by the mobile station/base station in23every 20 ms time interval on the Fundamental Channel.24Fundamental RLP Frame - An RLP frame carried in a fundamental data block.25Gating Rate Set - This specifies the set of supported reverse pilot gating rates. The base station26and the mobile station may support one or more gating rates.27GHz - Gigahertz (109 Hertz).28Global Positioning System (GPS) - A US government satellite system that provides location29and time information to users. See Navstar GPS Space Segment / Navigation User Interfaces30ICD-GPS-200 for specifications.31Good Frames - Frames not classified as bad frames. See also Bad Frames.32Good Message - A received message is declared a good message if it is received with a correct33CRC.34GPS See Global Positioning System.35Handoff - The act of transferring communication with a mobile station from one base station to36another.37Hard Handoff - A handoff characterized by a temporary disconnection of the Traffic Channel.38Hard handoffs occur when the mobile station is transferred between disjoint Active Sets, the39CDMA frequency assignment changes, the frame offset changes, or the mobile station is directed40from a CDMA Traffic Channel to an AMPS voice channel. See also Soft Handoff.41Hash Function - A function used by the mobile station to select one out of N available42resources. The hash function distributes the available resources uniformly among a random43sample of mobile stations.44HLR - See Home Location Register.45

TSG-C42 Page xxxv

10/19/2001 C.S0031

Home Location Register (HLR) - The location register to which a MIN/IMSI is assigned for1record purposes such as subscriber information.2Home System - The cellular or PCS system in which the mobile station subscribes for service.3Hopping Pilot Beacon - A pilot beacon that changes CDMA Frequency periodically to simulate4multiple base stations operating on different frequencies. The transmission of the hopping pilot5beacon is discontinuous on any CDMA Channel.6Idle Handoff - The act of transferring reception of the Paging Channel from one base station to7another, when the mobile station is in the Mobile Station Idle State.8Implicit Registration - A registration achieved by a successful transmission of an origination or9page response on the Access Channel.10IMSI - See International Mobile Station Identity.11IMSI_M - MIN-based IMSI using the lower 10 digits to store the MIN.12IMSI_O - Operational value of IMSI used by the mobile station for operation with the base13station.14IMSI_T - True IMSI not associated with MIN. This could be 15 digits or fewer.15Interleaving - The process of permuting a sequence of symbols.16International Mobile Station Identity (IMSI) - A method of identifying stations in the land17mobile service as specified in ITU-T Recommendation E.212.18Io - The total received power spectral density, including signal and interference, as measured at19the mobile station antenna connector.20Ioc - The power spectral density of a band-limited white noise source (simulating interference21from other cells) as measured at the mobile station antenna connector.22Ior - The total transmit power spectral density of the Forward CDMA Channel at the base station23antenna connector.24Îor - The received power spectral density of the Forward CDMA Channel as measured at the25mobile station antenna connector.26kHz - Kilohertz (103 Hertz).27ksps - Kilo-symbols per second (103 symbols per second).28L2 Acknowledgment - A Layer 2 response by the mobile station or the base station confirming29that a signaling message was received correctly.30

Layering - A method of organization for communication protocols in which the transmitted or31received information is transferred in pipeline fashion, within each station, in well-defined32encapsulated data units between otherwise decoupled processing entities (“layers”). A layer is33defined in terms of its communication protocol to a peer layer in another entity and the services34it offers to the next higher layer in its own entity.35Layer 1 - Layer 1 provides for the transmission and reception of radio signals between the base36station and the mobile station. Also see Physical Layer.37Layer 2 - Layer 2 provides for the correct transmission and reception of signaling messages,38including partial duplicate detection. Layer 2 makes use of the services provided by Layer 1.39Layer 3 - Layer 3 provides the control messaging for the cellular or PCS telephone system.40Layer 3 originates and terminates signaling messages according to the semantics and timing of41the communication protocol between the base station and the mobile station. Layer 3 makes use42of the services provided by Layer 2.43Local Control - An optional mobile station feature used to perform manufacturer-specific44functions.45

TSG-C42 Page xxxvi

10/19/2001 C.S0031

Logical Channel - A communication path between the mobile station and the base station,1described in terms of the intended use of, and access to, the transferred data, and direction of2transfer. A logical channel can be “mapped” to and from one or more physical channels.3Logical-to-physical Mapping - The technique for forming associations between logical and4physical channels.5Long Code - A PN sequence with period (242) - 1 that is used for scrambling on the Forward6CDMA Channel and spreading on the Reverse CDMA Channel. The long code uniquely7identifies a mobile station on both the Reverse Traffic Channel and the Forward Traffic Channel.8The long code provides limited privacy. The long code also separates multiple Access Channels9on the same CDMA Channel. See also Public Long Code and Private Long Code.10Long Code Mask - A 42-bit binary number that creates the unique identity of the long code. See11also Public Long Code, Private Long Code, Public Long Code Mask, and Private Long Code12Mask.13LSB - Least significant bit.14Maximal Length Sequence (m-Sequence). A binary sequence of period 2n - 1, n being a15positive integer, with no internal periodicities. A maximal length sequence can be generated by a16tapped n-bit shift register with linear feedback.17MCC - See Mobile Country Code.18Mcps - Megachips per second (106 chips per second).19MCSB - See Message Control and Status Block.20Mean Input Power - The total received calorimetric power measured in a specified bandwidth21at the antenna connector, including all internal and external signal and noise sources.22Mean Output Power - The total transmitted calorimetric power measured in a specified23bandwidth at the antenna connector when the transmitter is active.24

MER - Message Error Rate. MER = 1 -dtransmittemessagesofNumber

receivedmessagesgoodofNumber .25

Message Body - The part of the message contained between the length field (MSG_LENGTH)26and the CRC field.27Message Capsule - A sequence of bits comprising a single message and padding. The padding28always follows the message and may be of zero length.29

30Message CRC - The CRC check associated with a message. See also Cyclic Redundancy Code.31Message Field - A basic named element in a message. A message field may consist of zero or32more bits.33Message Record - An entry in a message consisting of one or more fields that repeats in the34message.35MHz - Megahertz (106 Hertz).36MIN - See Mobile Identification Number.37MNC - See Mobile Network Code.38MOB_P_REV – Protocol revision number supported by a mobile station.39Mobile Country Code (MCC) - A part of the E.212 IMSI identifying the home country. See40ITU-T Recommendation E.212.41Mobile Directory Number - A dialable directory number that is not necessarily the same as the42mobile station’s air interface identification, i.e., MIN, IMSI_M or IMSI_T.43Mobile Identification Number (MIN) - The 34-bit number that is a digital representation of the4410-digit number assigned to a mobile station.45

TSG-C42 Page xxxvii

10/19/2001 C.S0031

Mobile Network Code (MNC) - A part of the E.212 IMSI identifying the home network within1the home country. See ITU-T Recommendation E.212.2Mobile Protocol Capability Indicator (MPCI) - A 2-bit field used to indicate the mobile3station’s capabilities.4Mobile-Specific User Zone - A user zone that is identified by the mobile station. The mobile5station may consider parameters such as the identity of the serving system, cell, and sector, and6the geographic location of that station in making the determination. See also CDMA Tiered7Services, User Zone, Broadcast User Zone, Active User Zone, and Passive User Zone.8Mobile Station - A station that communicates with a base station while in motion or during halts9at unspecified points.10Mobile Station Class - A classification of mobile stations based on characteristics such as11slotted operation and transmission power. See Table 2.3.3-1 of TIA/EIA-553-A and Table 2.3.3-121 of this document.13Mobile Station Identification Number (MSIN) - A part of the E.212 IMSI identifying the14mobile station within its home network. See ITU-T Recommendation E.212.15Mobile Station Originated Call - A call originating from a mobile station.16Mobile Station Terminated Call - A call received by a mobile station (not to be confused with17a disconnect or call release).18ms - Millisecond (10-3 second).19MSB - Most significant bit.20MSC - See Mobile Switching Center.21MSIN - See Mobile Station Identification Number.22Mobile Switching Center (MSC) - A configuration of equipment that provides radiotelephone23service. Also called the Mobile Telephone Switching Office (MTSO).24Multiplex Sublayer - One of the conceptual layers of the system that multiplexes and25demultiplexes signaling traffic and various connected user traffic.26NAM - See Number Assignment Module.27National Mobile Station Identity (NMSI) - A part of the E.212 IMSI identifying the mobile28station within its home country. The NMSI consists of the MNC and the MSIN. See ITU-T29Recommendation E.212.30NDSS - See Network Directed System Selection.31Neighbor Set - The set of pilots associated with the CDMA Channels that are probable32candidates for handoff. Normally, the Neighbor Set consists of the pilots associated with CDMA33Channels that cover geographical areas near the mobile station. See also Active Set, Candidate34Set, Remaining Set, and Private Neighbor Set.35Network - A network is a subset of a cellular or PCS system, such as an area-wide cellular36network, a private group of base stations, or a group of base stations set up to handle a special37requirement. A network can be as small or as large as needed, as long as it is fully contained38within a system. See also System.39Network Directed System Selection (NDSS) - A feature that allows the mobile station to40automatically register with a preferred system while roaming, or to be automatically directed by41a service provider, typically the home service provider, to a suggested system, regardless of the42frequency band class, cellular band, or PCS frequency block.43Network Identification (NID) - A number that uniquely identifies a network within a cellular or44PCS system. See also System Identification.45NID - See Network Identification.46

TSG-C42 Page xxxviii

10/19/2001 C.S0031

NMSI - See National Mobile Station Identity.1Non-Autonomous Registration - A registration method in which the base station initiates2registration. See also Autonomous Registration.3Non-Slotted Mode - An operation mode of the mobile station in which the mobile station4continuously monitors the Paging Channel.5ns - Nanosecond (10-9 second).6Nt - The effective noise power spectral density at the mobile station antenna connector.7NULL - Any value that is not in the specified range of a field.8Null Traffic Channel Data - One or more frames of a specified data sequence sent at the lowest9agreed-upon rate of the negotiated rate set. Null Traffic Channel data is sent when there is no10primary, secondary, or signaling traffic available. Null Traffic Channel data serves to maintain11the connectivity between the mobile station and the base station.12Number Assignment Module (NAM) - A set of MIN/IMSI-related parameters stored in the13mobile station.14Numeric Information - Numeric information consists of parameters that appear as numeric15fields in messages exchanged by the base station and the mobile station and information used to16describe the operation of the mobile station.17OCNS Ec - Average energy per PN chip for the OCNS.18

Ior

EcOCNS- The ratio of the average transmit energy per PN chip for the OCNS to the total19

transmit power spectral density.20Optional Field - A field defined within a message structure that is optionally transmitted to the21message recipient.22Order- A type of message that contains control codes for either the mobile station or the base23station.24Ordered Registration - A registration method in which the base station orders the mobile25station to send registration related parameters.26Orthogonal Channel Noise Simulator (OCNS) - A hardware mechanism used to simulate the27users on the other orthogonal channels of a Forward CDMA Channel.28OTD - See Orthogonal Transmit Diversity29Overhead Message - A message sent by the base station on the Paging Channel to communicate30base-station-specific and system-wide information to mobile stations.31Overload Class (OLC) - The means used to control system access by mobile stations, typically32in emergency or other overloaded conditions. Mobile stations are assigned one (or more) of33sixteen overload classes. Access to the CDMA system can then be controlled on a per class basis34by persistence values transmitted by the base station.35P_REV – Protocol revision level supported by a base station.36P_REV_IN_USE – Protocol revision level currently in use by a mobile station.37PACA - Priority Access and Channel Assignment. See PACA Call.38PACA Call - A priority mobile station originated call for which no traffic channel or voice39channel was immediately available, and which has been queued for a priority access channel40assignment.41Packet - The unit of information exchanged between the service option applications of the base42station and the mobile station.43Padding - A sequence of bits used to fill from the end of a message to the end of a message44capsule, typically to the end of the frame or half frame. All bits in the padding are ‘0’.45

TSG-C42 Page xxxix

10/19/2001 C.S0031

Paging The act of seeking a mobile station when a call has been placed to that mobile station.1Paging Channel - A code channel in a CDMA channel used for transmission of control2information and pages from a base station to a mobile station.3Paging Channel Slot - An 80 ms interval on the Paging Channel. Mobile stations operating in4the slotted mode are assigned specific slots in which they monitor messages from the base5station.6Paging_Chip_Bit - Number of PN chips per Paging Channel bit, equal to 128 x v where v7equals 1 when the data rate is 9600 bps and v equals 2 when the data rate is 4800 bps.8Paging Ec - Average energy per PN chip for the Paging Channel.9

Ior

EcPaging- The ratio of the average transmit energy per PN chip for the Paging Channel to the10

total transmit power spectral density.11Paging Indicator - A one-bit datum, sent on the Quick Paging Channel. Quick paging indicators12are associated with mobile stations, in pairs, via a hashing algorithm. Appearance of both of its13indicators in its assigned Quick Paging Channel slot serves to alert a slotted mode mobile station,14operating in the Mobile Station Idle State, that it should monitor the Paging Channel starting in15the next slot. See also Quick Paging Channel.16Parameter-Change Registration - A registration method in which the mobile station registers17when certain of its stored parameters change.18Parity Check Bits - Bits added to a sequence of information bits to provide error detection,19correction, or both.20Passive User Zone - A user zone in which the implicit registration that takes place at call setup21is sufficient to trigger a change in tiered service features. See also CDMA Tiered Services, User22Zone, and Active User Zone.23PCI - See Protocol Control Information.24PCS - See Personal Communications Services.25PCSC - See Personal Communications Switching Center.26PCS System - See Personal Communications Services System.27PDU - See Protocol Data Unit.28Permanent Memory - Power-off does not affect the information. This type of memory can not29be altered.30Personal Communications Services (PCS) - A family of mobile and portable radio31communications services for individuals and businesses that may be integrated with a variety of32competing networks. Broadcasting is prohibited and fixed operations are to be ancillary to33mobile operations.34Personal Communication Services System - A configuration of equipment that provides PCS35radiotelephone services.36Personal Communications Switching Center (PCSC) - See Mobile Switching Center (MSC).37Physical Channel - A communication path between stations, described in terms of the RF38characteristics such as coding, power control policies, etc.39Physical Layer - The part of the communication protocol between the mobile station and the40base station that is responsible for the transmission and reception of data. The physical layer in41the transmitting station is presented a frame by the multiplex sublayer and transforms it into an42over-the-air waveform. The physical layer in the receiving station transforms the waveform back43into a frame and presents it to the multiplex sublayer above it.44

TSG-C42 Page xl

10/19/2001 C.S0031

Piece-wise Linear FER Curve - An FER-versus-Eb/Nt curve in which the FER vertical axis is1in log scale and the Eb/Nt horizontal axis is in linear scale expressed in dB, obtained by2interpolating adjacent test data samples with straight lines.3Piece-wise Linear MER Curve - An MER-versus-Eb/Nt curve in which the MER vertical axis4is in log scale and the Eb/Nt horizontal axis is in linear scale expressed in dB, obtained by5interpolating adjacent test data samples with straight lines.6Pilot Beacon - A transmit-only base station that broadcasts a Pilot Channel, a Sync Channel,7optionally a Paging Channel, but no Forward Traffic Channels. The mobile station measures the8pilot beacon to assist in CDMA hard handoffs and inter-frequency idle-mode handoffs.9Pilot Channel - An unmodulated, direct-sequence spread spectrum signal transmitted10continuously by each CDMA base station. The Pilot Channel allows a mobile station to acquire11the timing of the Forward CDMA Channel, provides a phase reference for coherent12demodulation, and provides a means for signal strength comparisons between base stations for13determining when to handoff.14Pilot Ec - Average energy per PN chip for the Pilot Channel.15

Piloto

cIE - The ratio of the combined pilot energy per chip, Ec, to the total received power16

spectral density (noise and signals), Io, of at most K usable multipath components at the mobile17station antenna connector (see 1.4). K is the number of demodulating elements supported by the18mobile station.19

Ior

EcPilot- The ratio of the average transmit energy per PN chip for the Pilot Channel to the total20

transmit power spectral density.2122

Pilot PN Chip - One bit, or bit pair, of a pilot PN sequence, or the time interval corresponding23thereto.24Pilot PN Sequence - A pair of modified maximal length PN sequences with period 2

15PN chips25

used to spread the Forward CDMA Channel and the Reverse CDMA Channel. Different base26stations are identified by different pilot PN sequence offsets.27Pilot PN Sequence Offset - The time offset of a Forward Pilot Channel from CDMA System28time, as transmitted by the base station, expressed modulo the pilot period.29Pilot PN Sequence Offset Index - The pilot PN sequence offset in units of 64 PN chips of a30Forward Pilot Channel, relative to the zero offset pilot PN sequence.31Pilot Strength - The ratio of pilot power to total power in the signal bandwidth of a CDMA32Forward or Reverse Channel. See also Ec/Io.33PN - Pseudonoise.34PN Chip - One bit in a PN sequence, or the time duration of such a bit. It corresponds to the35smallest modulation interval in a CDMA system.36PN Sequence – Pseudo-random noise sequence. A deterministic, periodic binary sequence37having limited statistical similarity to a Bernoulli (coin-tossing).38Power Control Bit - A bit sent in every 1.25 ms interval on the Forward Traffic Channel that39signals the mobile station to increase or decrease its transmit power.40Power Control Ec - Average energy per PN chip for the power control subchannel. For the case41when the power control sub-channel is assumed to be transmitted at the same power level that is42used for the 9600 bps or 14400 bps data rate, the following equations apply: For Rate Set 1, it is43

TSG-C42 Page xli

10/19/2001 C.S0031

equal tov11

v+

x (total Forward Traffic Channel energy per PN chip), where v equals 1 for 96001

bps, v equals 2 for 4800 bps, v equals 4 for 2400 bps, and v equals 8 for 1200 bps traffic data2

rate. For Rate Set 2, it is equal tov23

v+

x (total Forward Traffic Channel energy per PN chip),3

where v equals 1 for 14400 bps, v equals 2 for 7200 bps, v equals 4 for 3600 bps, and v equals 84for 1800 bps traffic data rate. The total Forward Traffic Channel is comprised of traffic data and5a power control sub-channel.6Power Control E c

Ior- The ratio of the average transmit energy per PN chip for the power control7

subchannel to the total transmit power spectral density.8Power Control Group - A 1.25 ms interval on the Forward Traffic Channel and the Reverse9Traffic Channel. See also Power Control Bit.10Power-Down Registration - An autonomous registration method in which the mobile station11registers on power-down.12Power Up Function - A method by which the mobile station increases its output power to13support location services.14Power-Up Registration - An autonomous registration method in which the mobile station15registers on power-up.16PPM - Parts per million.17Preamble - See Access Channel Preamble and Traffic Channel Preamble.18Primary CDMA Channel - A pre-assigned channel in a CDMA Cellular System used by the19mobile station for initial acquisition. See also Secondary CDMA Channel.20Primary Paging Channel (CDMA) - The default code channel (code channel 1) assigned for21paging on a CDMA Channel.22Primary Traffic - The main traffic stream carried between the mobile station and the base23station on the Traffic Channel. See also Secondary Traffic and Signaling Traffic.24Primitive - An atomic, well-defined method of transferring data and control information25between two adjacent layers and sublayers. Conventionally represented as a function invocation26with the data and/or control information as parameters.27Private Long Code - The long code characterized by the private long code mask. See also Long28Code.29Private Long Code Mask - The long code mask used to form the private long code. See also30Public Long Code Mask and Long Code.31Private Neighbor Set - The set of pilots associated with the private system base stations that are32probable candidates for idle handoff. See also Active Set, Neighbor Set, Remaining Set, and33CDMA Tiered Services.34Protocol Control Information (PCI) - Data passed between adjacent layers in the protocol35stack, together with the SDU, to assist a layer to properly encapsulate/decapsulate the SDU.36Examples of PCI in this document are the MCSB and the PCSB.37Protocol Data Unit - Encapsulated data communicated between peer layers on the mobile38station and base station. Unless specified otherwise, in this document PDU refers to the Layer 339protocol data unit transferred at the interface between layer 3 and layer 2.40Protocol Stack - Conceptual model of the layered architecture for communication protocols (see41Layering) in which layers within a station are represented in the order of their numeric42designation and requiring that transferred data be processed sequentially by each layer, in the43

TSG-C42 Page xlii

10/19/2001 C.S0031

order of their representation. Graphically, the “stack” is drawn vertically, with the layer having1the lowest numeric designation at the base.2PS - Pilot Strength. Also see Pilot Ec/I0.3Public Long Code - The long code characterized by the public long code mask.4Public Long Code Mask. The long code mask used to form the public long code. The mask5contains a permutation of the bits of the ESN, and also includes the channel number when used6for a Supplemental Code Channel. See also Private Long Code Mask and Long Code.7PUF - See Power Up Function.8PUF Attempt. A sequence of PUF probes sent by the mobile station in response to a Power Up9Function Message.10PUF Probe - One or more consecutive frames on the Reverse Traffic Channel within which the11mobile station transmits the PUF pulse.12PUF Pulse - Portion of PUF probe that may be transmitted at elevated output power.13PUF Target Frequency - The CDMA frequency assignment to which the base station directs a14mobile station for transmitting the PUF probe.15Punctured Code - An error-correcting code generated from another error-correcting code by16deleting (i.e., puncturing) code symbols from the coder output.17Quick Paging - A feature that permits mobile stations to further conserve battery power beyond18the savings achieved by slotted mode operation. See also Paging Indicator and Configuration19Change Indicator.20Quick_Paging_Chip_Bit - Number of PN chips per Quick Paging Channel bit. For Spreading21Rate 1, Quick Paging_Chip_Bit is equal to 256 x v where v equals 1 when the data rate is 480022bps and v equals 2 when the data rate is 2400 bps. For Spreading Rate 3, Quick Paging_Chip_Bit23is equal to 768 x v where v equals 1 when the data rate is 4800 bps and v equals 2 when the data24rate is 2400 bps.25Quick Paging Channel - An uncoded, on-off-keyed (OOK) spread spectrum signal sent by base26stations to inform slotted mode mobile stations, operating in the Mobile Station Idle State,27whether to monitor the Paging Channel. See also Quick Paging, Paging Indicator, and28Configuration Change Indicator.29Quick Paging Channel Slot - An 80 ms interval on the Quick Paging Channel. See also Paging30Indicator and Configuration Change Indicator.31Quick Repeats - Additional transmissions of identical copies of a message within a short32interval to increase the probability that the message is received correctly.33r-csch - Reverse common signaling logical channel.34r-dsch - Reverse dedicated signaling logical channel.35Radio Configuration - A set of Forward Traffic Channel and Reverse Traffic Channel36transmission formats that are characterized by physical layer parameters such as transmission37rates, modulation characteristics and spreading rate.38Radio Configuration Class - A group of radio configurations. All radio configurations, for the39Forward Traffic Channel and the Reverse Traffic Channel, are divided into three classes by the40types of pre-spreading symbols (BPSK and QPSK) and spreading rates. RC Class 1 consists of41RC 1 and RC 2 for the Forward Traffic Channel and the Reverse Traffic Channel. RC Class 242consists of RC 3 and RC 4 of the Reverse Traffic Channel, and RC 3, RC 4 and RC 5 of the43Forward Traffic Channel. RC Class 3 consists of RC 5 and RC 6 of the Reverse Traffic Channel,44and RC 6, RC 7, RC 8, and RC 9 of the Forward Traffic Channel.45RC - See Radio configuration.46

TSG-C42 Page xliii

10/19/2001 C.S0031

Registration - The process by which a mobile station identifies its location and parameters to a1base station.2Registration Zone - A collection of one or more base stations treated as a unit when determining3whether a mobile station should perform zone-based registration. See also User Zone, with4which it should not be confused.5Release - A process that the mobile station and base station use to inform each other of call6disconnect.7Remaining Set - The set of all allowable pilot offsets as determined by PILOT_INC, excluding8the pilot offsets of the pilots in the Active Set, Candidate Set, and Neighbor Set. See also Active9Set, Candidate Set, and Neighbor Set.10Request - A layer 3 message generated by either the mobile station or the base station to retrieve11information, ask for service, or command an action.12Response - A layer 3 message generated as a result of another message, typically a request.13Reverse CDMA Channel - The CDMA Channel from the mobile station to the base station.14From the base station’s perspective, the Reverse CDMA Channel is the sum of all mobile station15transmissions on a CDMA frequency assignment.16Reverse Dedicated Control Channel - A portion of a Reverse Traffic Channel that can carry a17combination of primary data, secondary data, signaling, and power control information.18Reverse Fundamental Code Channel - A portion of a Reverse Traffic Channel that can carry a19combination of primary data, secondary data, signaling, and power control information.20Reverse Pilot Channel - A non-data-bearing direct-sequence spread spectrum signal transmitted21by each CDMA mobile station whenever the Enhanced Access Channel, Reverse Common22Control Channel, or Reverse Traffic Channel is enabled. The Reverse Pilot Channel allows a23base station to acquire the timing of the Reverse CDMA Channel and provides a phase reference24for coherent demodulation. The Reverse Pilot Channel may be transmitted either continuously or25in gated mode.26Reverse Supplemental Channel - An optional portion of a Reverse Traffic Channel (Radio27Configurations 3 and above) that operates in conjunction with a Fundamental Channel and or the28Dedicated Control Channel in that Traffic Channel, and (optionally) with other Supplemental29Channels to provide higher data rate services.30Reverse Supplemental Code Channel - An optional portion of a Reverse Traffic Channel31(Radio Configurations 1 and 2) that operates in conjunction with a Fundamental Channel in that32Traffic Channel, and (optionally) with other Supplemental Code Channels to provide higher data33rate services.34Reverse Traffic Channel. A Traffic Channel on which data and signaling are transmitted from a35mobile station to a base station. The Reverse Traffic Channel is composed of one Reverse36Fundamental Code Channel and zero to seven Reverse Supplemental Code Channels, zero to two37Reverse Supplemental Channels, and zero or one Reverse Dedicated Control Channel38Semi-Permanent Memory - Power-off does not affect the information. Also known as non-39volatile memory.40Roamer - A mobile station operating in a cellular system (or network) other than the one from41which service was subscribed. See also Foreign NID Roamer and Foreign SID Roamer.42SAP - See Service Access Point.43SCI - See Synchronized Capsule Indicator Bit.44SDU - See Service Data Unit.45Search Window - The range of PN sequence offsets that a mobile station searches for a pilot.46

TSG-C42 Page xliv

10/19/2001 C.S0031

Search Window Offset - PN sequence offset used by the mobile station to position the search1window when searching for a pilot.2Secondary CDMA Channel - A pre-assigned channel in a CDMA Cellular System used by the3mobile station for initial acquisition. See also Primary CDMA Channel.4Secondary Traffic - An additional traffic stream that can be carried between the mobile station5and the base station on the Traffic Channel. See also Primary Traffic and Signaling Traffic.6Service Access Point - Conceptual point at the interface between two adjacent layers where7services are provided to the upper layer and data and protocol information is exchanged between8layers.9Service Configuration - The common attributes used by the mobile station and the base station10to build and interpret Traffic Channel frames. A service configuration consists of Forward and11Reverse Traffic Channel multiplex options, Forward and Reverse Traffic Channel transmission12rates, and service option connections. Service Configuration is signaled via the Service13Configuration information record and the Non-Negotiable Service Configuration information14record.15Service Data Unit - Data transferred between adjacent layers in the protocol stack. Unless16specified otherwise in this document SDU refers to the Layer 3 service data unit being17transferred to/from Layer 2.18Service Negotiation - The procedures used by the mobile station and base station to establish a19service configuration. See also Service Option Negotiation.20Service Option - A service compatibility of the system. Service options may be applications21such as voice, data, or facsimile. See (17).22Service Option Connection - A particular instance or session in which the service defined by a23service option is used. Associated with a service option connection are a reference, which is used24for uniquely identifying the service option connection, a service option, which specifies the25particular type of service in use, a Forward Traffic Channel traffic type, which specifies what26type of Forward Traffic Channel traffic is used to support the service option connection, and a27Reverse Traffic Channel traffic type, which specifies what type of Reverse Traffic Channel28traffic is used by the service option connection.29Service Option Connection Reference - A designator used by the base station and mobile30station to uniquely identify a particular service option connection.31Service Option Negotiation - The procedures used by the mobile station and base station to32establish a service configuration. Service option negotiation is similar to service negotiation, but33allows less flexibility for specifying the attributes of the service configuration. See also Service34Negotiation.35Service Redirection - The process by which the base station alters the system selection made by36a mobile station. It can be used temporarily during maintenance and testing to divert subscribers37to an alternate system.38Serving Frequency - The CDMA frequency on which a mobile station is currently39communicating with one or more base stations.40Shared Secret Data (SSD) - A 128-bit pattern stored in the mobile station (in semi-permanent41memory) and known by the base station. SSD is a concatenation of two 64-bit subsets: SSD_A,42which is used to support the authentication procedures, and SSD_B, which serves as one of the43inputs to the process generating the encryption mask and private long code.44Short Message Services (SMS) - A suite of services such as SMS Text Delivery, Digital Paging45(i.e., Call Back Number - CBN), and Voice Mail Notification (VMN).46

TSG-C42 Page xlv

10/19/2001 C.S0031

SID - See System Identification.1Signaling Traffic - Control messages that are carried between the mobile station and the base2station on the Traffic Channel. See also Primary Traffic and Secondary Traffic.3Slotted Mode - An operation mode of the mobile station in which the mobile station monitors4only selected slots on the Paging Channel.5Soft Handoff - A handoff occurring while the mobile station is in the Mobile Station Control on6the Traffic Channel State. This handoff is characterized by commencing communications with a7new base station on the same CDMA frequency assignment before terminating communications8with the old base station. See Hard Handoff.9SOM - Start-of-Message bit.10sps - Symbols per second.11SSD - See Shared Secret Data.12Station Class Mark (SCM) - An identification of certain characteristics of a mobile station.13Classes are defined in Table 2.3.3-1 of TIA/EIA-553-A and Table 6.3.3-1 of [4].14Status Information - The following status information is used to describe mobile station15operation when using the analog system:16

• Serving-System Status. Indicates whether a mobile station is tuned to channels17associated with System A or System B.18

• First Registration ID Status. A status variable used by the mobile station in association19with its processing of received Registration ID messages.20

• First Location Area ID Status. A status variable used by the mobile station in21association with its processing of received Location Area ID messages.22

• Location Registration ID Status. A status variable used by the mobile station in23association with its processing of power-up registrations and location-based24registrations.25

• First Idle ID Status. A status variable used by the mobile station in association with its26processing of the Idle Task.27

• Local Control Status. Indicates whether a mobile station must respond to local control28messages.29

• Roam Status. Indicates whether a mobile station is in its home system.30• Termination Status. Indicates whether a mobile station must terminate the call when it31

is on an analog voice channel.32• Update Protocol Capability Status. Indicates whether the mobile station should report33

its protocol capability to the serving system.34Supplemental_Chip_Bit - The number of PN chips per Supplemental Code Channel bit, equal35to 128 for Radio configuration 1 and 85.33... for Radio configuration 2.36Supplemental Code Channel - An optional portion of a Traffic Channel (Forward or Reverse)37which operates in conjunction with a Fundamental Channel in that Traffic Channel, and38(optionally) with other Supplemental Code Channels to provide higher data rate services. On this39channel a combination of primary data, secondary data, or both (but never signaling information)40are transmitted.41Supplemental Data Block - A data block that is transmitted by the mobile station/base station in42a 20 ms time interval on a Supplemental Code Channel.43Supplemental Ec - Average energy per PN chip for one Forward Supplemental Code Channel.44

SupplementalIor

Ec- The ratio of the average transmit energy per PN chip for one Forward45

Supplemental to the total transmit power spectral density.46

TSG-C42 Page xlvi

10/19/2001 C.S0031

Supplemental RLP Frame - An RLP frame carried in a supplemental data block.1Symbol - See Code Symbol and Modulation Symbol.2Sync Channel - Code channel 32 in the Forward CDMA Channel, which transports the3synchronization message to the mobile station.4Sync_Chip_Bit - Number of PN chips per Sync Channel bit, equal to 1024.5Sync Channel Superframe - An 80 ms interval consisting of three Sync Channel frames (each626.666... ms in length).7Sync Ec - Average energy per PN chip for the Sync Channel.8

Ior

EcSync- The ratio of the average transmit energy per PN chip for the Sync Channel to the9

total transmit power spectral density.10Synchronized Capsule Indicator Bit (SCI) - The first bit in any Paging Channel half frame,11which indicates whether a synchronized message capsule immediately follows.12System. A system is a cellular telephone service or personal communications service that covers13a geographic area such as a city, metropolitan region, county, or group of counties. See also14Network.15System Identification (SID) - A number uniquely identifying a cellular or PCS system.16System Time - The time reference used by the system. System Time is synchronous to UTC17time (except for leap seconds) and uses the same time origin as GPS time. All base stations use18the same System Time (within a small error). Mobile stations use the same System Time, offset19by the propagation delay from the base station to the mobile station. See also Universal20Coordinated Time.21Target Frequency - The CDMA frequency assignment to which the base station directs a22mobile station in a handoff using an Extended Handoff Direction Message, a General Handoff23Direction Message, or a Universal Handoff Direction Message.24Temporary Memory - Information is lost when power is gone. Also known as volatile memory.25Temporary Mobile Station Identity (TMSI) - A temporary mobile station identification26assigned by the base station.27Timer-Based Registration - A registration method in which the mobile station registers28whenever a counter reaches a predetermined value. The counter is incremented an average of29once per 80 ms period.30Time Reference - A reference established by the mobile station that is synchronous with the31earliest arriving multipath component used for demodulation.32TMSI - See Temporary Mobile Station Identity.33TMSI Zone - The administrative zone that allows the TMSI to be reused. The TMSI_CODE has34to be unique within a TMSI zone but may be reused in a different TMSI zone. The TMSI zone is35identified by the field TMSI_ZONE.36Traffic Channel - A communication path between a mobile station and a base station used for37user and signaling traffic. The term Traffic Channel implies a Forward Traffic Channel and38Reverse Traffic Channel pair. See also Forward Traffic Channel and Reverse Traffic Channel.39Traffic Channel Preamble - A sequence of all-zero frames that is sent by the mobile station on40the Reverse Traffic Channel as an aid to Traffic Channel acquisition.41Traffic_Chip_Bit - The number of PN chips per Traffic Channel bit, equal to 1228800/rb for42Spreading Rate 1 and 3686400/rb for Spreading Rate 3, where rb is the data rate.43

44

TSG-C42 Page xlvii

10/19/2001 C.S0031

Traffic Ec - Average energy per PN chip for the Forward Fundamental Channel. For the case1when the power control sub-channel is assumed to be transmitted at the same power level used2for the 9600 bps or 14400 bps data rate, the following equations apply: For Rate Set 1, it is equal3

tov11

11+

x (total Forward Fundamental Channel energy per PN chip), where v equals 1 for 96004

bps, v equals 2 for 4800 bps, v equals 4 for 2400 bps, and v equals 8 for 1200 bps traffic data5

rate. For Rate Set 2, it is equal tov23

23+

x (total Forward Fundamental Channel energy per PN6

chip), where v equals 1 for 14400 bps, v equals 2 for 7200 bps, v equals 4 for 3600 bps, and v7equals 8 for 1800 bps traffic data rate. The total Forward Fundamental Channel is comprised of8traffic data and a power control sub-channel.9

Ior

EcTraffic- The ratio of the average transmit energy per PN chip for the Forward Traffic10

Channel to the total transmit power spectral density.11Unassured Mode - Mode of delivery that does not guarantee that a PDU will be delivered to the12peer. The LAC entity at the receiver does not acknowledge a PDU sent in unassured mode.13Unique Challenge-Response Procedure - An exchange of information between a mobile14station and a base station for the purpose of confirming the mobile station’s identity. The15procedure is initiated by the base station and is characterized by the use of a challenge- specific16random number (i.e., RANDU) instead of the random variable broadcast globally (RAND).17Unique Random Variable (RANDU) - A 24-bit random number generated by the base station18in support of the Unique Challenge-Response procedure.19Universal Coordinated Time (UTC) - An internationally agreed-upon time scale maintained by20the Bureau International de l’Heure (BIH) used as the time reference by nearly all commonly21available time and frequency distribution systems i.e., WWV, WWVH, LORAN-C, Transit,22Omega, and GPS.23User Zone - An area within which CDMA Tiered Services may be provided. It may correspond24to an RF coverage area, or it may be established independent of RF topology. User Zones are25classified as broadcast versus mobile-specific, and as active versus passive. See Broadcast User26Zone, Mobile-Specific User Zone, Active User Zone, and Passive User Zone. See also27Registration Zone, with which it should not be confused.28User Zone Registration - An autonomous registration method in which the mobile station29registers when it selects an active user zone while in the Mobile Station Idle State. See also30Zone-Based Registration, with which it should not be confused.31Upper Layers - General reference to Layer 3 and the layers above it.32User Zone Exit parameter - A parameter used by the mobile station to determine if it should33exit a User Zone.34UTC - Universal Temps Coordiné. See Universal Coordinated Time.35Valid Power Control Bit - A valid power control bit is sent on the Forward Traffic Channel in36the second power control group following the corresponding Reverse Traffic Channel power37control group which was not gated off and in which the signal strength was estimated. See383.1.3.1.10 of [1].39Voice Privacy - The process by which user voice transmitted over a CDMA Traffic Channel is40afforded a modest degree of protection against eavesdropping over the air.41Walsh Chip - The shortest identifiable component of a Walsh function. There are 2N Walsh42chips in one Walsh function where N is the order of the Walsh function. On the Forward CDMA43

TSG-C42 Page xlviii

10/19/2001 C.S0031

Channel, one Walsh chip equals 1/1.2288 MHz, or 813.802 ns. On the Reverse CDMA Channel,1one Walsh chip equals 4/1.2288 MHz, or 3.255 µs.2Walsh Function - One of 2N time orthogonal binary functions (note that the functions are3orthogonal after mapping ‘0’ to 1 and ‘1’ to -1).4Zone-Based Registration - An autonomous registration method in which the mobile station5registers whenever it enters a zone that is not in the mobile station’s zone list. See also User6Zone Registration, with which it should not be confused.7Zone Timer - A timer used by the mobile station to remove outdated entries from its list of8zones in which it has previously registered.9µs - Microsecond (10-6 second).10

CDMA Equations11The following equations describe the relationship between various test parameters under12different conditions.13

Transmit Power of the Base Station14

or

cI

EPilot+

or

cI

ESync+

or

cI

EPagingQuick+

or

cI

EPaging+

or

cI

ETraffic+15

or

cI

EControlPower+

or

cI

EalSupplement+

or

cI

EOCNS= 116

In the tests defined in this document, the following values are usually used:17

or

cI

EPilot= -7 dB18

or

cI

ESync= -16 dB19

or

cI

EPaging= -12 dB20

21

Therefore, ifor

cI

ETraffic= -16 dB at 9600 bps data rate, then22

or

cI

EControlPower= -26.41 dB23

or

cI

EOCNS= -1.64 dB24

Otherwise, ifor

cI

ETraffic= -16 dB at 1200 bps data rate, then25

TSG-C42 Page xlix

10/19/2001 C.S0031

or

cI

EControlPower= -17.38 dB1

or

cI

EOCNS= -1.75 dB2

Received Signal Strength for Mobile Station Not in Handoff3

Pilot0

cIE

=1

I

II

EPilot

or

oc

or

c

+4

Single-Path Case5

Synct

bNE

=

or

oc

or

c

I

I

Bit_Chip_SyncI

ESync×

6

Quick Pagingt

bNE

=

or

oc

or

c

I

I

Bit_Chip_Paging_QuickI

EPagingQuick×

7

Pagingt

bNE

=

or

oc

or

c

I

I

Bit_Chip_PagingI

EPaging×

8

Traffict

bNE

=

or

oc

or

c

I

I

Bit_Chip_TrafficI

ETraffic×

9

Supplementalt

bNE

=

or

oc

or

c

I

I

Bit_Chip_alSupplementI

EalSupplement×

10

Two-Path Case11According to Channel Simulator Configuration 1 and 2 (see 6.4.1.1), these two paths have the12same average power.13

Traffict

bNE

=or

cI

ETraffic× Traffic_Chip_Bit ×

21

I

I1

or

oc +14

TSG-C42 Page l

10/19/2001 C.S0031

Three-Path Case1According to Channel Simulator Configuration 4 (see 6.4.1.1), the first two paths have the same2average power and the third path has half the average power of the first one.3

Traffict

bNE

=or

cI

ETraffic× Traffic_Chip_Bit × (2 ×

53

I

I52

or

oc ++

54

I

I51

or

oc +)4

Received Signal Strength for Mobile Station in Two-Way Handoff5According to Channel Simulator Configuration 2 (see 6.4.1.1), which is used in the tests of the6Forward Traffic Channel in two-way handoff, there are two paths from each cell and the power7received from each cell is Îor.8

Pilot0

cIE

(for each pilot) =2

I

II

EPilot

or

oc

or

c

+9

Traffict

bNE

=or

cI

ETraffic× Traffic_Chip_Bit ×

23

I

I23

or

oc +10

Generally, if the power received from cell 1 and cell 2 are Îor1 and Îor2, respectively, then11

Pilot0

cIE

1 =1

II

II

IEPilot

1or

2or

1or

oc

1or

c

++12

Tolerances13

CDMA System Parameter Tolerances14CDMA parameters are specified in IS-2000 (2). All parameters indicated are exact unless15otherwise specified.16

Measurement Tolerances17Unless otherwise specified, a measurement tolerance, including the tolerance of the measurement18equipment, of ±10% is assumed.19Unless otherwise specified, the Ior/Ioc value shall be within ±0.1 dB of the value specified, and20the Ioc value shall be within ±5 dB of the value specified.21

Normative Document References22The following documents contain provisions which, through reference in this text, constitute23provisions of this document. At the time of publication, the editions indicated were valid. All24standards are subject to revision, and parties to agreements based on this Standard are25encouraged to investigate the possibility of applying the most recent editions of the standards26

TSG-C42 Page li

10/19/2001 C.S0031

indicated below. ANSI and TIA maintain registers of currently valid national standards1published by them.2

31. 3GPP2 C.S0002, Physical Layer Standard for cdma2000 Spread Spectrum Systems,

1999.

2. 3GPP2 C.S0003, Medium Access Control (MAC) Standard for cdma2000 SpreadSpectrum Systems, 1999.

3. 3GPP2 C.S0004, Signaling Link Access Control (LAC) Standard for cdma2000 SpreadSpectrum Systems, 1999.

4. 3GPP2 C.S0005, Upper Layer (Layer 3) Signaling Standard for cdma2000 SpreadSpectrum Systems, 1999.

5. 3GPP2 C.S0010-A, Recommended Minimum Performance Standards for cdma2000Spread Spectrum Base Stations, 2000.

6. 3GPP2 C.S0011-A, Recommended Minimum Performance Standards for cdma2000Spread Spectrum Mobile Stations, 2000.

7. 3GPP2 C.P9005, Test Data Service Option (TDSO) for cdma2000 Spread SpectrumSystems.

8. 3GPP2 C.P9006, Markov Service Option (MSO) for cdma2000 Spread Spectrum Systems.

9. 3GPP2 C.S0013-A, Loopback Service Options (LSO) for cdma2000 Spread SpectrumSystems.

10. CDG Document # 45, MDM Minimum Requirements Specification.

11. CDG Document # 53, CDG Stage 2 Interoperability Test Specification (95-B version)

12. TIA/EIA/IS-127-1, Enhanced Variable Rate Codec, Speech Service Option 3 forWideband Spread Spectrum Digital Systems

13. TIA/EIA/IS-637-A, Short Message Services for Wideband Spread Spectrum CellularSystems, 1995

14. TIA/EIA/IS-683-A, Over-the-Air Service Provisioning of Mobile Stations in SpreadSpectrum Systems

15. TIA/EIA/IS-707-A, Data Service Options for Wideband Spread Spectrum Systems

45

TSG-C42 Page lii

10/19/2001 C.S0031

116. TIA/EIA/TSB-50, Telecommunications Systems Bulletin: User Interface for

Authentication Key Entry17. TSB-58, Administration of Parameter Value Assignment for TIA/EIA Spread Spectrum

Standards

18 TIA/EIA/IS-127-2, Enhanced Variable Rate Codec, Speech Service Option 3 forWideband Spread Spectrum Digital Systems Addendum 2

19 TIA/EIA/IS-733-1, High Rate Speech Service Option 17 for Wideband Spread Spectrum

Communications Systems Addendum 1

20 TTY Forum. Seeking Solutions to TTY/TDD Through Wireless Digital Systems. TTY/TDDFORUM-13. Final. November 19, 1999

21 TIA/EIA/95B Mobile Station-Base Station Compatibility Standard for Dual-ModeWideband Spread Spectrum Cellular Systems

22 TIA/EIA-664 Cellular Features Description December 1, 2000

23

TSG-C42 Page liii

10/19/2001 C.S0031

No text1

TSG-C42 Page 1-1

10/19/2001 C.S0031

1 MISCELLANEOUS AIR ITERFACE TESTS1Table 1-1 lists miscellaneous air interface tests.2

Table 1-1 Miscellaneous Tests3

Test No. Title

1.1 Pilot PN Offset

1.2 Hashing CDMA Channels, Paging Channels, and Paging Slot

1.3 Idle Ping Pong with Quick Paging Channel CCI

1.4 Quick Paging Indicator

1.5 Mobile Station Response to the Access Parameters Message

1.6 Mobile Station Response to MIN_P_REV

1.7 Status Request Message

1.8 Protocol Discriminator (PD) Test and Link Access Control (LAC) PDU Format Teston the Access Channel.

1.9 Logging Tests

1.10 SYNC Channel Support

1.1 Pilot PN Offset4

1.1.1 Definition5

This test verifies the mobile station is able to determine PN offset of the base station. This test6will be performed for the following Pilot PN offsets (in order): 304, 511, and 0.7

Traceability: (See [4] );8

2.6.6.2.4 Pilot PN Phase9

1.1.2 Method of Measurement10

a. Connect the base station to the mobile station as shown in Figure 1.1.2-1. Set pilot11PN sequence offset increment (i.e. PILOT_INC) to 1.12

13

TSG-C42 Page 1-2

10/19/2001 C.S0031

1

Figure 1.1.2-1 Basic Setup for Air Interface Tests, Single Base Station2

b. At the base station, set Pilot PN offset to 304.3

c. Verify that the mobile station detects and acquires the new base station.4

d. Setup a mobile station originated call.5

e. Verify user data in both directions.6

f. End the call at the mobile station.7

g. Change the Pilot PN offset to 511 and repeat steps c through f.8

h. Change the Pilot PN offset to 0 and repeat steps c through f.9

1.1.3 Minimum Standard10The mobile station shall correctly detect the base station Pilot PN offset and acquire the new base11station. All calls shall be established successfully.12

1.2 Hashing CDMA Channels, Paging Channels, and Paging Slot13

1.2.1 Definition14

This test verifies that the mobile station hashes to the correct CDMA Channel, CDMA Paging15Channel, and CDMA Paging Slot. The effect of IMSI on hashed CDMA channel, paging16channel, and slot is also verified.17


3.6.2.1.1, CDMA Channel Determination19

3.6.2.1.2, Paging Channel Determination20

3.6.2.1.3 Paging Slot Determination21

2.6.7.1, Hash Function22

TSG-C42 Page 1-3

10/19/2001 C.S0031

1.2.2 Methods of Measurement1

1.2.2.1 CDMA Channel Number Hashing2

a. Connect the base station and the mobile station as shown in Figure 1.1.2-1, and3configure the base station for multiple CDMA channel assignment capability.4

b. Send a Registration Request Order from the base station and verify the mobile5station responds with a Registration Message. Note that some equivalent method6may be employed to verify that the mobile station has hashed to the correct CDMA7channel.8

c. Change the IMSI (phone number) in the mobile station so that the hashing9operation selects a different CDMA channel number assignment, and repeat steps a10and b.11

1.2.2.2 Paging Channel Number Hashing12

a. Connect the base station and mobile station as shown in Figure 1.1.2-1, and13configure the base station system with multiple Paging Channels.14

b. Send a Registration Request Order from the base station and verify the mobile15station responds with a Registration Message. Note that some equivalent method16may be employed to verify that the mobile station has hashed to the correct Paging17Channel.18

c. Change the IMSI (phone number) in the mobile station so that the hashing19operation selects a different Paging Channel number assignment, and repeat steps a20and b.21

1.2.2.3 Paging Slot Number Hashing22

a. Connect the base station and mobile station as shown in Figure 1.1.2-1, configure23the base station system with slotted mode capability, and verify the mobile station24goes into slotted mode.25

b. Send a Registration Request Order from the base station and verify the mobile26station responds with a Registration Message. Note that some equivalent method27may be employed to verify that the mobile station has hashed to the correct Paging28Channel Slot and receives messages in that slot.29

c. Change the IMSI (phone number) in the mobile station so that the hashing30operation selects a different Paging Channel Slot number assignment, and repeat31steps a and b.32

1.2.3 Minimum Standard33

For all tests, the mobile station shall hash to the correct CDMA Channel, CDMA Paging34Channel, and CDMA Paging Channel Slot.35

TSG-C42 Page 1-4

10/19/2001 C.S0031

1.3 Idle Ping Pong with Quick Paging Channel CCI1

1.3.1 Definition2For mobile stations that support the Quick Paging Channel, this test will verify the following: A3mobile station using the Quick Paging Channel ‘configuration change indicator’ (CCI) can4perform multiple idle handoffs, back and forth (idle ping pong), between base stations, and5remain in slotted mode when CCI is set to OFF.6

A diagnostic monitor may be used to check whether the mobile station is in slotted or non-slotted7mode. Alternately, the base station can send a message to the mobile station on the Paging8Channel, but configure the Quick Paging Channel paging indicator (PI) bits to OFF, and observe9that the mobile station does not act on the message.10

With the Quick Paging Channel CCI feature available on the mobile station and base station, it is11assumed the base station communicates its CCI capability to the mobile station so that the12mobile station uses the feature.13

In slotted mode, an idle mobile station monitors the Quick Paging Channel for pages or updated14overhead information, but also searches for the strongest pilot. A mobile station determines that15it should ‘idle handoff’ to a pilot that is sufficiently stronger (i.e. 3 dB) than the pilot of its16current demodulation.17


2.6.2.1.1.3, Slotted Mode Requirements19

2.6.2.1.2, Quick Paging Channel Monitoring Procedures20

2.6.2.1.4, Idle Handoff21

2.6.7.1, Hash Function22

3.6.2.5, Quick Paging Channel Processing23

3.7.2.3.2.13, Extended System Parameters Message24

3.7.2.3.2.14, Extended Neighbor List Message25


a. Connect two base stations to the mobile station, with the ability to transition either27base station power Ior 5 dB above the other, to induce idle handoff from one to the28other and back again.29

• The Forward Channel from base station #1 has an arbitrary pilot PN offset index30P1 and is called Channel 1.31

• The Forward Channel from base station #2 has an arbitrary pilot PN offset index32P2 and called Channel 2.33

• Set the Extended System Parameter Message in both base stations as specified34in Table 1.3.2-1.35

36

TSG-C42 Page 1-5

10/19/2001 C.S0031

Table 1.3.2-1 Test Parameters for Extended System Parameters Message1

Fields Values

QPCH_SUPPORTED '1' (QPCH is supported)

NUM_QPCH '01' (Number of the QPCH)

QPCH_RATE (indicator rate) '0' (QPCH indicator rate is 4800 bps)

QPCH_POWER_LEVEL_PAGE '101' (same as pilot channel)

QPCH_CCI_SUPPORTED '1' [configuration change indicators supported]

QPCH_POWER_LEVEL_CONFIG '101' (same as pilot channel)

2

b. Set NGHBR_PN for the Extended Neighbor List Message, Neighbor List Message or3General Neighbor List Message in both base stations to include the other base4station PN.5

c. Set the Paging Channel data rate for Channels 1 and 2 to 4800 bps.6

d. Setup Channel 1 and Channel 2 per Table 1.3.2-2.7

Table 1.3.2-2. Test Parameters for Slotted Mode Idle Handoff8

Parameter Unit Channel 1 Channel 2

Îor/Ioc dB 0 -5

orI

cEPilot dB -7 -7

orI

cEPagingQuick dB -7 -7

Ioc dBm/1.23 MHz -75

9

e. Slowly (over a period of several seconds, but not more than T31m = 600 seconds10round trip) transpose power levels of channel 1 and 2. That is, raise Channel 211power by 5 dB (to Îor/Ioc = 0 dB), and lower Channel 1 power by 5 dB (to Îor/Ioc = -125 dB). This should provoke an idle handoff from Channel 1 to Channel 2.13

f. Verify the mobile station has performed an idle handoff to Channel 2. On first idle14handoff the mobile station may exit slotted mode, but after some time, resume15operating in slotted mode.16

g. Slowly return power of Channel 1 and Channel 2 to the original levels (make17Channel 1 dominant pilot by 5 dB).18

TSG-C42 Page 1-6

10/19/2001 C.S0031

h. Verify the mobile station has performed an idle handoff back to Channel 1 and1stayed in slotted mode.2

i. Place a call to the mobile station, and verify it completes, then returns to slotted3mode.4

j. Repeat idle handoffs, back and forth, between Channel 1 and Channel 2, at least5twice. Verify the mobile station remains in slotted mode. Verify that a call can be6completed to the mobile station after each idle handoff.7

k. While the mobile station is idle on Channel 2, instruct the base station #1 to modify8an overhead message, thus causing the CCI bits on Channel 1 Quick Paging9Channel to be set to ON.10

l. Cause an idle handoff from Channel 2 to Channel 1. Verify that the mobile station11does not go to slotted mode until it has updated its overhead configuration.12

m. Repeat steps a through l with the QPCH_RATE (indicator rate) set to 1 (9600 rate).13


When the mobile station idle handoffs to a Quick Paging Channel whose CCI bits are set to OFF,15except for the first idle handoff, the mobile station shall stay in the slotted mode, and will16complete calls made to it, then return to slotted mode. When the mobile station idle handoffs to a17Quick Paging Channel whose CCI bits are set to ON, the mobile station shall go into non-slotted18mode to update its overhead configuration after idle handoff.19

1.4 Quick Paging Indicator20

1.4.1 Definition21

For mobile stations that support the Quick Paging Channel, this test will verify the following:22

• The mobile station will hash to the right Quick Paging indicator positions.23

• The mobile station will monitor the following Paging Slot if the Quick Paging Indicators24are set to ON by the base station.25

• The mobile station will not monitor the following Paging Slot if the Quick Paging26Indicators are set to OFF by the base station.27

TSG-C42 Page 1-7

10/19/2001 C.S0031

Registration Request order

BS

CommonChannels

MS

CommonChannels

Turn on/off PI on Quick Paging Channelfor the MS assigned QPCH Slot

The MS hash to QPIpositions and detect itsQPI on in the Assigned

QPCH Slot. Then the MSstart receiving on itsassigned PCH slots

Registration Message

1

Figure 1.4.1-1 Reference Call Flow for QPI Testing2


2.6.2.1.2 Quick Paging Channel Monitoring Procedures.4

2.6.7.1 Hash Function5

2.7.1.3.2.1 Registration Message6

3.7.2.3.2.13 Extended System Parameters Message7

Method of Measurement8

a. Connect the mobile station to the base station as shown in Figure 1.1.2-1.9

b. Set the values in the Extended System Parameters Message as follows:10

11

Fields Values

QPCH_SUPPORTED '1' (QPCH is supported)

NUM_QPCH '01' (Number of the QPCH)

QPCH_RATE '0' (4800 bps QPCH data rate)

QPCH_POWER_LEVEL_PAGE '101' (same as pilot channel)

12

c. Set the corresponding Quick Paging Indicators corresponding to the mobile station13Paging Channel slot to ON, and those for all other slots to OFF.14

d. Send a Registration Request Order from the base station at expected Paging Channel15slot, and verify that the mobile station responds with a Registration Message. Note16that some equivalent method may be employed to verify that the mobile station17receives and processes messages on its assigned slot.18

e. Set the Quick Paging Indicators corresponding to the mobile station Quick Paging19slot to OFF, and those for all other slots to ON.20

TSG-C42 Page 1-8

10/19/2001 C.S0031

f. Send a Registration Request Order at expected Paging Channel slot on the Paging1Channel , and verify that the mobile station DOES NOT respond with a Registration2Message. Note that some equivalent method may be employed to verify that the3mobile station does not receive and process messages on its assigned slot.4

g. Repeat steps b through f with the QPCH_RATE set to 1 (9600 bps).5


When the Quick Paging Channel is supported, a mobile station shall receive and process7messages on its assigned Paging Channel slot when the corresponding Quick Paging Indicators8are set to ON.9

1.5 Mobile Station Processing of the Access Parameters Message10

1.5.1 Definition11

This test verifies correct interpretation and functionality of the Access Parameters Message. In12addition, proper operation of the TA timer is verified.13

Traceability: (See [3]);14

[3] 2.1.1.2.2.2 Requirement for Transmission and Retransmission Procedures15

(See [4]);16[4] 2.6.2.2.2, Access Parameters Message17[4] 2.6.3.1.1, Access Attempts18


a. Connect the base station to the mobile station as shown in Figure 1.1.2-1.20

b. Set forward link parameters as specified in Table 1.5.2-1, and Access Parameters21Message as specified in table 1.5.2-2, for Test 1.22

23

Table 1.5.2-1 Test Parameters for Mobile Station Response to24Access Parameters Message Tests25

Parameter Units Test 1 Test 2 Test 3

Forward LinkPower Ior

dBm/1.23 MHz -74 -74 -74

Pilot Ec/Ior dB -7 -7 -11

26

c. Ensure mobile station has been previously registered, then disable all forms of27registration (to ensure that the registration access probes do not interfere with this28test).29

TSG-C42 Page 1-9

10/19/2001 C.S0031

d. Disable the reverse link to allow the mobile station to exhaust all its access probes.1This may be accomplished by instructing the base station to not acknowledge the2probes.3

e. Attempt a mobile station originated call, and verify the mobile station uses the4access parameters specified in Table 1.5.2-2.5

f. Attempt a mobile station terminated call, and verify the mobile station uses access6parameters specified in Table 1.5.2-2.7

g. Repeat steps b through f for Test 2 and Test 3 as shown in Tables 1.5.2-1 and 1.5.2-82.9

10

Table 1.5.2-2 Access Parameters Message Values for Mobile Station Response to Access11Parameters Message Tests12

Parameter Test 1 Test 2 Test 3

NUM_STEP 7 3 7

PWR_STEP 1 3 0

INIT_PWR 0 -6 4

NOM_PWR 0 0 0

ACC_TMO 2 4 1

MAX_REQ_SEQ 2 1 1

MAX_RSP_SEQ 1 2 1


Test 1:14

• The mobile station shall produce 2 sets of 8 probes for the mobile station originated15call, and 1 set of 8 probes for the mobile station terminated call.16

• Output power of each probe shall be greater than the previous probe by 1 ±1 dB.17

• The interval between two consecutive, unacknowledged access probes shall be at least18320 ms.19

Test 2:20

• The mobile station shall produce 1 set of 4 probes for the mobile station originated call21and 2 sets of 4 probes for the mobile station terminated call.22

• Output power of the first probe shall be 6 ±1 dB lower than the first probe produced in23Test 1.24

TSG-C42 Page 1-10

10/19/2001 C.S0031

• Output power of each probe shall be greater than the previous probe by 3±1 dB.1


Test 3:4

• The mobile station shall produce 1 set of 8 probes for both the mobile station5originated, and mobile station terminated calls.6

• Output power of the first probe shall be 4 ±1 dB higher than the first probe produced in7Test 1.8

• Output power of all probes shall be within ±1 dB of each other.9


1.6 Mobile Station Processing of MIN_P_REV12

1.6.1 Definition13

This test verifies the mobile station shall not access the CDMA system if the mobile station's14protocol revision (MOB_P_REVp) is less than the minimum protocol revision permitted to15access the CDMA system (MIN_P_REV). This test should be performed only if the base station16supports a protocol revision greater than that supported by the mobile station, or if the base17station can be configured to send arbitrary protocol revision numbers in the Sync Channel18Message.19


2.6.1.3 Sync Channel Acquisition Substate21

3.4.1 Access Channel22



b. Configure the base station to send values for P_REV and MIN_P_REV in the Sync25Channel Message greater than the value of MOB_P_REVp in the mobile station.26

c. Power on the mobile station.27

d. Verify the mobile station does not indicate CDMA service is available.28

Note: If the base station and mobile station are both dual-mode, the mobile station29may acquire the AMPS signal and indicate AMPS service is available.30

e. Attempt to setup a mobile station originated call. Verify the mobile station does not31send any messages on the CDMA Access Channel.32

TSG-C42 Page 1-11

10/19/2001 C.S0031


When the mobile station's protocol revision is less than the minimum protocol revision permitted2by the base station, the mobile station shall not indicate CDMA service is available and shall not3originate a call on this system.4

1.7 Mobile Station Response to Status Request Message5

1.7.1 Definition6

This test verifies that that mobile station responds to the Status Request Message with an7Extended Status Response Message or Status Response Message with the correct information8record(s).9

Traceabilities (See [4] );10

2.6.3.5 Mobile Station Origination Attempt Substate11

2.6.4.1.2 (MS) Service Configuration and Negotiation12

2.6.4.1.14 Processing the Service Configuration Record13

2.6.4.1.15 Processing the Non-Negotiable Service Configuration Record14

2.6.4.2 Traffic Channel Initialization Substate15

2.7.1.3.2.4 Origination Message16

2.7.1.3.2.5 Page Response Message17

2.7.1.3.2.10 Extended Status Response Message18

2.7.2.3.2.14 (MS) Service Connect Completion Message19

2.7.2.3.2.16 Status Response Message20

3.6.3.5 Response to Origination Message21

3.6.4.1.2 (BS) Service Configuration and Negotiation22

3.7.2.3.2.15 Status Request Message23

3.7.2.3.2.21 Extended Channel Assignment Message24

3.7.3.3.2.20 (BS) Service Connect Message25

3.7.5.7 (BS) Service Configuration26

3.7.5.20 (BS) Non-Negotiable Service Configuration27

Annex D Information Records28


a. Instruct the mobile station to send an Origination Message.30

b. Upon receiving the Origination Message, instruct the base station to send a Status31Request Message on the f-csch to request one or more of the information records32listed in Annex D of [4].33

TSG-C42 Page 1-12

10/19/2001 C.S0031

c. Verify the mobile station responds with an Extended Status Response Message if1P_REV_IN_USE is greater than 3 or Status Response Message if P_REV_IN_USE is2less than or equal to 3 on the r-csch with the correct record type and correct3information4

d. Instruct the base station to assign the dedicated channels to the mobile station.5Verify the call completes and that user traffic is present.6

e. Steps b through d may be repeated for one or more of the Mobile Station7Information Records supported.8

f. Setup a mobile station terminated call.9

g. Instruct the base station to send a Status Request Message on the f-dsch to request10one or more of the information records listed in Annex D of [4].11

h. Verify the mobile station responds with a Status Response Message on the r-dsch12with the correct record type and correct information.13

i. Instruct the base station to assign the dedicated channels to the mobile station.14Verify the call completes and user traffic is present.15

j. Steps g through i may be repeated for one or more of the Mobile Station Information16Records supported.17


The mobile station shall respond to the Status Request Message with:19

• Extended Status Response Message (if P_REV_IN_USE is greater than 3) or Status20Response Message (if P_REV_IN_USE is less than or equal to 3) on the r-csch when21the Status Request Message is received on the f-csch with the correct record type.22The information in the Mobile Station Record shall accurately represent the mobile23station features/capabilities.24

• Status Response Message on the r-dsch when the Status Request Message is25received on the f-dsch. The information in the Mobile Station Record shall26accurately represent the mobile station features/capabilities.27

1.8 Protocol Discriminator (PD) Test and Link Access Control (LAC) PDU Format Test28on the Access Channel29

1.8.1 Definition30

This test will verify the following:31

• If P_REV_IN_USEs is less than six, the mobile station shall set the PD field in the LAC32Utility sublayer to ‘00’; if P_REV_IN_USEs is equal to six, the mobile station shall set the33PD field in the LAC Utility sublayer to ‘01’.34

• The format of the LAC PDU sent on the r-csch is as defined for the corresponding value35of P_REV_IN_USE.36

TSG-C42 Page 1-13

10/19/2001 C.S0031

Registration Request order

BS

CommonChannels

MS

CommonChannels

Set P_REV to 3, 5, or 6 on ESPM

Registration Message

1

Figure 1.8.1-1 Reference Call Flow for LAC Testing2


2.1.1.4.1.1: (r-csch) Message Type fields4

2.1.1.4.2: Procedures (PDU Format for the different P_REV_IN_USE).5

(See [4] );6

2.7.1.3.2.1 Registration Message7

3.7.2.3.2.13, Extended System Parameters Message8


a. Connect the mobile station to the base station as shown in Figure 1.1.2-1-1.10

b. Set P_REV to '0000011' (if operating on Band Class 0) in the Extended System11Parameters Message, or set P_REV to '0000001' (if operating on Band Class 1) in the12Extended System Parameters Message.13

c. Send a Registration Request Order from the base station.14

d. Verify the mobile station responds with a Registration Message with the LAC/L315fields included in the order as given below and the Protocol Discriminator field is set16to '00'.17

18

TSG-C42 Page 1-14

10/19/2001 C.S0031

Parameter

Message Type Fields

ARQ Fields

Addressing Fields

Authentication Fields

SDU

PDU Padding Field

1

e. Set P_REV to '0000101' and PILOT_REPORT to '1' in the Extended System2Parameters Message.3

f. Send a Registration Request Order from the base station.4

g. Verify the mobile station responds with a Registration Message with the LAC/L35fields included in the order as given below and the Protocol Discriminator field is set6to '00'.7

8

Parameter

Message Type Fields

ARQ Fields

Addressing Fields


SDU

Radio Environment Report Fields

PDU Padding Field

9

h. Set P_REV to '0000110' and PILOT_REPORT to '1' in the Extended System10Parameters Message.11

i. Send a Registration Request Order from the base station.12

j. Verify the mobile station responds with a Registration Message with the LAC/L313fields included in the order as given below and the Protocol Discriminator field is set14to '01'.15

16

TSG-C42 Page 1-15

10/19/2001 C.S0031

Parameter

Message Type Fields

LAC Length Field

ARQ Fields

Addressing Fields


LAC Padding Field

Radio Environment Report Fields

SDU

PDU Padding Field

1


• If P_REV_IN_USEs is less than six, the mobile station shall set the PD field to ‘00’.3

• If P_REV_IN_USEs is equal to six, the mobile station shall set the PD field to ‘01’.4

• The LAC PDU format shall be set to the appropriate format according to the5P_REV_IN_USEs.6

7

8

1.9 Logging Tests9

1.9.1 Initial Values of Logging Parameters10

1.9.1.1 Definition11This test verifies that the mobile station resets the counters related to the Fundamental Channel,12Dedicated Control Channel, Supplemental Code Channel, and Supplemental Channel upon13power-up.14

TSG-C42 Page 1-16

10/19/2001 C.S0031

Parameters Response Message(requested counters)

BS

Retrieve Parameters Message(all relevant counters)

MS

Power-up

DedicatedChannel

DedicatedChannel

1Figure 1.9.1-1 Reference Call Flow for Initial FCH, DCCH, SCCH, and SCH counters2

Traceability: (See [4] );3Annex E: CDMA Retrievable and Settable Parameters4

(See ( [2] );5Section 2.2.2.2: Mux and QoS sublayer6Table 49: Received MuxPDU Type 1 Categories and Formats for the FCH and DCCH7Table 50: Received MuxPDU Type 2 Categories and Formats for the FCH and DCCH8Table 51: Received MuxPDU Type 4 Categories and Formats for the FCH and DCCH9Section 2.2.3: Supervisory Procedures10Table 60: FCH Transmission Counters for Multiplex Option 0x111Table 61: FCH Transmission Counters for Multiplex Option 0x212Table 62: DCCH Transmission Counters for Multiplex Option 0x113Table 63: DCCH Transmission Counters for Multiplex Option 0x214Table 64. SCCH Transmission Counters15Table 65. SCH Transmission Counters16Table 66: FCH Reception Counters for Multiplex Option 0x117Table 67: FCH Reception Counters for Multiplex Option 0x218Table 68: DCCH Reception Counters for Multiplex Option 0x119Table 69: DCCH Reception Counters for Multiplex Option 0x220Table 70. SCCH Reception Counters21Table 71. SCH Reception Counters22

1.9.1.2 Method of Measurement23


b. Power-off and then power-up the mobile station.25

c. Set up a call using the Fundamental Channel.26

TSG-C42 Page 1-17

10/19/2001 C.S0031

d. Upon mobile station entering the Mobile Station Control on the Traffic Channel State,1instruct the base station to send a Retrieve Parameters Message and query the2mobile station for all the counters listed in Tables B-6 (or B-8), B-10 and B-12 (i.e.3counters associated with DCCH, SCCH, and SCH reception) in Annex B.4

e. Upon receiving the Parameter Response Message from the mobile station, verify all5queried counters have a value of zero.6

f. End the call.7

g. Set up a call using the Dedicated Control Channel.8

h. Upon mobile station entering the Mobile Station Control on the Traffic Channel State,9instruct the base station to send a Retrieve Parameters Message and query the10mobile station for all the counters listed in Tables B-2 (or B-4), B-10 and B-12 (i.e.11counters associated with FCH, SCCH, and SCH reception) in Annex B.12

i. Upon receiving the Parameter Response Message from the mobile station, verify all13queried counters have a value of zero.14

j. End the call.15

1.9.1.3 Minimum Requirements16Mobile station correctly resets all the FCH, DCCH, SCCH, and SCH related counters to zero17upon powering up.18

1.9.2 Logging of Fundamental Channel Related Parameters19

1.9.2.1 Definition20This test verifies that the mobile station correctly updates the Fundamental Channel related21counters for both the forward and reverse traffic channel.22

TSG-C42 Page 1-18

10/19/2001 C.S0031

Service Connect Message(SCR)


BS

Traffic

Set Parameters Message(set all relevant counters to zero)


User Traffic

MS

Traffic

1Figure 1.9.2.1-1 Reference Call Flow for Setting and Retrieving2

FCH/DCCH Logging Parameters3

Traceability: See Test 1.9.14



b. Setup a call using the Fundamental Channel.7

c. Instruct the base station to direct the mobile station to use a service configuration8with the following values for both forward and reverse traffic channel: multiplex9option 1, the service connected as Primary traffic, and 20ms frame size only.10

d. Instruct the base station to send a Set Parameters Message, with all of the counters11included in Tables F-1 through F-8 reset to zero.12

e. Ensure user communication on both the forward and reverse traffic channel13proceeds for a sufficient duration. During this period, record at the base station the14number of frames of each type sent by the base station and received by the base15station.16

f. Instruct the base station to send a Retrieve Parameters Message and query the17mobile station for the all counters included in Tables F-1 through F-8.18

g. Upon receiving the Parameter Response Message from the mobile station, verify the19following:20

1) One or more of the following parameters are set to a value larger than21zero and their value matches those recorded by the base station:22MUX1_FOR_FCH_1 through MUX1_FOR_FCH_10.23

TSG-C42 Page 1-19

10/19/2001 C.S0031

2) One or more of the following parameters are set to a value larger than1zero and their value matches those recorded by the base station:2MUX1_REV_FCH_1 through MUX1_REV_FCH_8.3

3) All other parameters queried have a value of zero.4

h. End the call.5

i. Set up a data call using the Fundamental Channel.6

j. Repeat steps c through g, instructing the base station to direct the mobile station to7use a service configuration with multiplex option 2 instead of multiplex option 1.8The expected results are as follows:9

1) One or more of the following parameters are set to a value larger than10zero and their value matches those recorded by the base station:11MUX2_FOR_FCH_1 through MUX2_FOR_FCH_5, MUX2_FOR_FCH_11 through12MUX2_FOR_FCH_14, MUX2_FOR_FCH_19 through MUX2_FOR_FCH_21,13MUX2_FOR_FCH_24, and MUX2_FOR_FCH_26.14

2) One or more of the following parameters are set to a value larger than15zero and their value matches those recorded by the base station:16MUX2_REV_FCH_1 through MUX2_REV_FCH_5, MUX2_REV_FCH_11 through17MUX2_REV_FCH_14, MUX2_REV_FCH_19 through MUX2_REV_FCH_21, and18MUX2_REV_FCH_24.19


k. Repeat steps c through h, with the service connected as Secondary traffic instead of21Primary traffic. The expected results for multiplex option 1 are as follows:22

1) One or more of the following parameters are set to a value larger than23zero and their value matches those recorded by the base station:24MUX1_FOR_FCH_1, MUX1_FOR_FCH_5 through MUX1_FOR_FCH_10, and25FCH_FOR_FCH_14.26

2) One or more of the following parameters are set to a value larger than27zero and their value matches those recorded by the base station:28MUX1_REV_FCH_1, MUX1_REV_FCH_5 through MUX1_REV_FCH_8, and29FCH_REV_FCH_14.30


l. The expected results for multiplex option 2 are as follows:32

1) One or more of the following parameters are set to a value larger than33zero and their value matches those recorded by the base station:34MUX2_FOR_FCH_1, MUX2_FOR_FCH_5, MUX2_FOR_FCH_9, MUX2_FOR_FCH_11,35MUX2_FOR_FCH_14, MUX2_FOR_FCH_17, MUX2_FOR_FCH_19,36MUX2_FOR_FCH_21, MUX2_FOR_FCH_23 through MUX2_FOR_FCH_26.37

2) One or more of the following parameters are set to a value larger than38zero and their value matches those recorded by the base station:39MUX2_REV_FCH_1, MUX2_REV_FCH_5, MUX2_REV_FCH_9, MUX2_REV_FCH_11,40

TSG-C42 Page 1-20

10/19/2001 C.S0031

MUX2_REV_FCH_14, MUX2_REV_FCH_17, MUX2_REV_FCH_19,1MUX2_REV_FCH_21, MUX2_REV_FCH_23 through MUX2_REV_FCH_25.2


1.9.2.3 Minimum Requirements4The mobile station shall correctly update all the expected Fundamental Channel related counters5for both the forward and reverse traffic channel. Furthermore, the parameters not expected to be6updated have value of zero upon being retrieved by the base station.7

Note: The expected numbers may not exactly match numbers received from the mobile8station due to frame errors over the air, which will cause the frame to be logged under9a different category than the transmitted category. The extent of this discrepancy can10be reduced by reducing the FER.11

1.9.3 Logging of Dedicated Control Channel Related Parameters12

1.9.3.1 Definition13This test verifies the mobile station correctly updates the Dedicated Control Channel related14counters for both the forward and reverse traffic channel.15

Traceability: See Test 1.9.1.16



b. Setup a call, using the Dedicated Control Channel.19

c. Instruct the base station to direct the mobile station to use a service configuration20with the following values for both forward and reverse traffic channel: multiplex21option 1, the service connected as Primary traffic, 20ms frame size only.22


e. Ensure user communication on both the forward and reverse traffic channel25proceeds for a sufficient duration. During this period, record at the base station the26number of frames of each type sent by the base station and received by the base27station.28

f. Instruct the base station to send a Retrieve Parameters Message and query the29mobile station for all of the counters included in Tables F-1 through F-8.30

g. Upon receiving the Parameter Response Message from the mobile station, verify the31following:32

1) One or more of the following parameters are set to a value larger than33zero and their value matches those recorded by the base station:34MUX1_FOR_DCCH_1 through MUX1_FOR_DCCH_5, MUX1_FOR_DCCH_10, and35MUX1_FOR_DCCH_15.36

2) One or more of the following parameters are set to a value larger than37zero and their value matches those recorded by the base station:38

TSG-C42 Page 1-21

10/19/2001 C.S0031

MUX1_REV_DCCH_1 through MUX1_REV_DCCH_5, MUX1_FOR_DCCH_10, and1MUX1_REV_DCCH_15.2


h. Repeat steps c through g, instructing the base station to direct the mobile station to4use a service configuration with multiplex option 2 instead of multiplex option 1.5The expected results are as follows:6

1) One or more of the following parameters are set to a value larger than7zero and their value matches those recorded by the base station:8MUX2_FOR_DCCH_1 through MUX2_FOR_DCCH_5, and MUX2_FOR_DCCH_269through MUX2_FOR_DCCH_27.10

2) One or more of the following parameters are set to a value larger than11zero and their value matches those recorded by the base station:12MUX2_REV_DCCH_1 through MUX2_REV_DCCH_5, and MUX2_REV_DCCH_27.13


i. Repeat steps c through h, with the service connected as Secondary traffic instead of15Primary traffic. The expected results for multiplex option 1 are as follows:16

1) One or more of the following parameters are set to a value larger than17zero and their value matches those recorded by the base station:18MUX1_FOR_DCCH_5, MUX1_FOR_DCCH_10, and MUX1_FOR_DCCH_14,19MUX1_FOR_DCCH_15.20

2) One or more of the following parameters are set to a value larger than21zero and their value matches those recorded by the base station:22MUX1_REV_DCCH_5, MUX1_REV_DCCH_10, and MUX1_REV_DCCH_14,23MUX1_REV_DCCH_15.24


j. The expected results for multiplex option 2 are as follows:26

1) One or more of the following parameters are set to a value larger than27zero and their value matches those recorded by the base station:28MUX2_FOR_DCCH_5, MUX2_FOR_DCCH_9, MUX2_FOR_DCCH_26, and29MUX2_FOR_DCCH_27.30

2) One or more of the following parameters are set to a value larger than31zero and their value matches those recorded by the base station:32MUX2_REV_DCCH_5, MUX2_REV_DCCH_9, and MUX2_REV_DCCH_27.33


1.9.3.3 Minimum Requirements35The mobile station shall correctly update all expected Dedicated Control Channel related36counters for both the forward and reverse traffic channel. Furthermore, the parameters not37expected to be updated have a value of zero upon being retrieved by the base station.38

TSG-C42 Page 1-22

10/19/2001 C.S0031

Note: The expected numbers may not exactly match the numbers received from the mobile1station due to frame errors over the air, which will cause the frame to be logged under2a different category than the transmitted category. The extent of this discrepancy can3be reduced by reducing the FER.4

1.9.4 Logging of Supplemental Code Channel Related Parameters5

1.9.4.1 Definition6This test verifies that the mobile station correctly updates the Supplemental Code Channel7related counters for both the forward and reverse traffic channel.8



BS

Traffic



User Traffic

MS

Traffic

Supplemental Channel Assignment Message

9Figure 1.9.4.1-1 Reference Call Flow for Setting and Retrieving10

SCCH Logging Parameters11

Traceability: see Test 1.9.1.12



b. Setup a call.15

c. Instruct the base station to direct the mobile station to use a service configuration16with the following values for both the forward and reverse traffic channel: multiplex17option 0x3 for SCCH and the service connected as Primary traffic.18


e. Instruct the base station to send a Supplemental Channel Assignment Message to21the mobile station with the following: assign maximum number of forward and22

TSG-C42 Page 1-23

10/19/2001 C.S0031

reverse Supplemental Code Channels allowed by the multiplex option (specified in1step c) as shown in Table 1.9.4.2-1, infinite duration, and REV_DTX_DURATION set2to ‘1111’.3

4

Table 1.9.4.2-15

Multiplex OptionMaximumNumber of

SCCHs Rate Set 1 Rate Set 2

1 0x3 0x4

2 0x5 0x6

3 0x7 0x8

4 0x9 0xa

5 0xb 0xc

6 0xd 0xe

7 0xf 0x10

6

f. Ensure user communication in both direction proceeds for a sufficient duration,7with sufficient user traffic flow to utilize all of the assigned SCCHs. During this8period, record at the base station the number of frames of each type sent by the9base station and received by the base station.10

g. Instruct the base station to send a Retrieve Parameters Message and query the11mobile station for all of the counters listed in Tables F-9 through F-12.12

h. Upon receiving the Parameter Response Message from the mobile station, verify the13following:14

1) SCCH1_FOR_P and SCCH1_REV_P are set to a value larger than zero15and their value matches those recorded by the base station.16


i. Repeat steps c through h for various allowed multiplex options (for both rate set 118and rate set 2) to provide different number of SCCHs as shown in Table 1.9.4.2-1,19also instructing the base station to assign the maximum number of SCCHs allowed20by the multiplex option assigned. The expected results are as follows:21

1) SCCH1_FOR_P through SCCHi_FOR_P are set to a value larger than zero22and their value matches those recorded by the base station, and if i < 7,23SCCHi+1_FOR_P through SCCH7_FOR_P are set to a value of zero, where i is the24number of SCCHs assigned by the Supplemental Channel Assignment Message.25


j. Repeat steps c through i with the service connected as Secondary traffic instead of27as Primary Traffic. The expected results are as follows:28

TSG-C42 Page 1-24

10/19/2001 C.S0031

1) SCCH1_FOR_S through SCCHi_FOR_S are set to a value larger than zero1and their value matches those recorded by the base station, and if i < 7,2SCCHi+1_FOR_S through SCCH7_FOR_S are set to a value of zero, where i is the3number of SCCHs assigned by the Supplemental Channel Assignment Message.4


1.9.4.3 Minimum Requirements6The mobile station shall correctly update all expected Supplemental Code Channel related7counters for both the forward and reverse traffic channel. Furthermore, the parameters not8expected to be updated shall have values of zero upon being retrieved by the base station.9

1.9.5 Logging of Supplemental Channel Related Parameters10

1.9.5.1 Definition11This test verifies the mobile station correctly updates the Supplemental Channel related counters12for both the forward and reverse traffic channel.13



BS

Traffic



User Traffic

MS

Traffic

Extended Supplemental ChannelAssignment Message

14Figure 1.9.5.1-1 Reference Call Flow for Setting and Retrieving SCH Logging Parameters15

Traceability: see Test 1.9.1.16



b. Setup a call.19

TSG-C42 Page 1-25

10/19/2001 C.S0031

c. Instruct the base station to direct the mobile station to use a service configuration1with the following values for both the forward and reverse traffic channel: multiplex2option 0x3 for SCH_0 and the service connected as Primary traffic.3


e. Instruct the base station to send an Extended Supplemental Channel Assignment6Message to the mobile station with the following setup: assign forward and reverse7SCH0 with the maximum rate allowed by the multiplex option (specified in step c) as8shown in Table 1.9.5.2-1, infinite duration, and REV_SCH_DTX_DURATION set to9‘1111’.10

Table 1.9.5.2-111

SCH Data Rate(kbps)

Multiplex Option

RateSet 1

RateSet 2

Rate Set 1 Rate Set 2

MuxPDU Type 3 MuxPDU Type 3MuxPDUType 1 single double

MuxPDUType 2 single double

1x 9.6 14.4 0x03 0x04

2x 19.2 28.8 0x809 0x905 0x80a 0x906

4x 38.4 57.6 0x811 0x909 0x812 0x90a

8x 76.8 115.2 0x821 0x911 0x822 0x912

16x 153.6 230.4 0x921 0x922

12

f. Ensure user communication in both the forward and reverse traffic channel13proceeds for a sufficient duration, with sufficient user traffic flow to utilize14maximum assigned rate of the SCH_0. During this period, record at the base station15the number of frames of each type sent by the base station and received by the base16station.17

g. Instruct the base station to send a Retrieve Parameters Message and query the18mobile station for all of the counters included in Tables F-9 through F-12.19

h. Upon receiving the Parameter Response Message from the mobile station, verify the20following:21

1) SCH1_FOR_1X and SCH1_REV_1X are set to a value larger than zero22and their value matches those recorded by the base station.23


i. Repeat steps c through h for various allowed multiplex options (for both rate set 125and rate set 2) for SCH_0 to provide different maximum data rates as shown in26Table 1.9.5.2-1. The expected results are as follows:27

TSG-C42 Page 1-26

10/19/2001 C.S0031

1) SCH1_FOR_iX and SCH1_REV_iX are set to a value larger than zero and1their value matches those recorded by the base station, where i corresponds to 2, 4,28, or 16 based on whether the maximum allowed rate is 2X, 4X, 8X, or 16X.3

2) The counters SCH1_FOR_LTU and SCH1_REV_LTU are set to a value4that is a multiple of the corresponding SCH1_FOR_iX and SCH1_REV_iX,5respectively, counter value as per Table 1.9.5.2-2.6

Table 1.9.5.2-27

SCH Rate Number of LTUs in the SDU

1X 0

2X 0

4X 2

8X 4

16X 8


j. Repeat steps c through i for SCH_1 assigned instead of SCH_0. The expected results9are as given in step h and i with the following modifications:10

1) The expected values for SCH_1 counters are as given for SCH_0 in steps11h and i12

2) The expected values for SCH_0 counters are as given for SCH_1 in steps13h and i.14

k. Repeat steps c through i for both SCH_0 and SCH_1 assigned simultaneously. The15expected results are as given in step h and i with the following modifications:16

1) The expected values for SCH_1 counters are as given for SCH_0 in steps17h and i.18

l. Steps c through k can be repeated with the service connected as Secondary Traffic19instead of as Primary Traffic. The expected results are exactly as given in step h, i, j,20and k.21

1.9.5.3 Minimum Requirements22• The mobile station shall correctly update all expected Supplemental Channel related23

counters for both the forward and reverse traffic channel.24• The parameters not expected to be updated have value of zero upon being retrieved by25

the base station.2627

1.10 SYNC Channel Support28

1.10.1 Definition2930

TSG-C42 Page 1-27

10/19/2001 C.S0031

This test verifies that the mobile station of MOB_P_REV=6 is able to respond correctly to the1EXT_CDMA_FREQ field of SYNC Channel Message sent by the base station if any and tune to2appropriate CDMA channel and acquire the system successfully.3


2.6.1.3 Sync Channel Acquisition Substate5

3.7.2.3.2.26 Sync Channel Message6


1.10.2.1 MS (MOB_P_REV = 6, neither QPCH nor RC > 2 is supported)8

9

1.10.2.1.1BS (P_REV<6)10

a. Connect the base station to the mobile station as shown in Figure 1.10.2-1. Set11PILOT_INC to 1.12

13Figure 1.10.2-1 Basic Setup for Air Interface Tests, Single Base Station14

b. At the base station, Set Pilot PN offset to a certain value.15

c. Configure the base station to send a Sync Channel Message withCDMA_FREQ set to16CDMA Channel 1.17

d. Verify that the mobile station stays on CDMA channel 1.18

e. Set up a mobile station originated voice call and verify audio in both directions.19

f. End the call.20

21

1.10.2.1.2 BS (P_REV=6, neither QPCH nor RC>2 is supported)22


TSG-C42 Page 1-28

10/19/2001 C.S0031

b. At the base station, Set Pilot PN offset to an arbitrary value.1

c. Configure the base station to send a Sync Channel Message with CDMA_FREQ set2to CDMA Channel 1 and EXT_CDMA_FREQ set to CDMA Channel 2 (a different3frequency than CDMA channel 1).4



f. End the call.7

8

1.10.2.1.3 BS (P_REV=6, QPCH or RC>2 (or both) is supported)9



c. Configure the base station to send a Sync Channel Message with CDMA_FREQ set13to CDMA Channel 1 and EXT_CDMA_FREQ set to CDMA Channel 2 (a different14frequency than CDMA channel 1).15



f. End the call.18

19

1.10.2.2 Case 2: MS (MOB_P_REV = 6, either QPCH or RC>2 (or both) is supported)20

21

1.10.2.2.1Case 2.1: BS (P_REV<6)22



c. Configure the base station to send a Sync Channel Message with CDMA_FREQ set26to CDMA Channel 1.27



f. End the call.30

31

TSG-C42 Page 1-29

10/19/2001 C.S0031

1.10.2.2.2 BS (P_REV=6, neither QPCH nor RC>2 is supported)1



c. Configure the base station to send a Sync Channel Message withCDMA_FREQ set to5CDMA Channel 1 and EXT_CDMA_FREQ set to CDMA Channel 2 (a different6frequency than CDMA channel 1).7



f. End the call.10

11

1.10.2.2.3 BS (P_REV=6, QPCH or RC>2 is supported)12



c. Configure the base station to send a Sync Channel Message with CDMA_FREQ set16to CDMA Channel 1 and EXT_CDMA_FREQ set to CDMA Channel 2 (a frequency17where QPCH or RC>2 is supported - whichever feature is supported by the mobile18station).19

d. Verify that the mobile station tunes to CDMA channel 2 and acquire the system.20


f. End the call.2223

1.10.3 Minimum Standard24The mobile station shall tune to the correct CDMA channel as specified in the25EXT_CDMA_FREQ field of the Sync Channel Message if applicable.26

TSG-C42 Page 2-1

10/19/2001 C.S0031

2 POTS TESTS1Table 2-1 lists POTS tests.2

Table 2-1 POTS Tests3

TestNo.

Title

2.1 Mobile station originated call

2.2 Mobile Station to Land Party Call, Radio Link Failure During Conversation - ReverseLink

2.3 Mobile Station to Land Party Call, Radio Link Failure During Conversation - ForwardLink

2.4 Mobile station originated call, Test Service Options

2.5 Mobile Station to Land Party Call, Busy Tone

2.6 Mobile Station to Land Party Call, No TCH Resources Available

2.7 Mobile Station to Land Party Call, Reverse Link Failure During Call Setup

2.8 Mobile Station to Land Party Call, Forward Link Failure During Call Setup

2.9 Mobile Station Terminated Call

2.10 Mobile Station terminated Call, Test Service Options

2.11 Land Party to Mobile Station Call, Mobile Operating in Slotted Mode

2.12 MSID, MCC, and IMSI

2.13 TMSI Assignment

2.14 TMSI Expiration Time (CDMA 1900)

2.15 Mobile Station to Land Party Call, DTMF

2.16 Forward Traffic Channel DTMF Tone Signaling

2.17 Enhanced DTMF Signaling

2.18 Channel Assignment from CDMA to AMPS

2.19 PACA Origination, User Terminates While Still in Queue

2.20 PACA Origination, Idle Handoff While in Queue

2.21 PACA Origination, Traffic Channel Becomes Available

2.22 PACA Origination, Features Interaction

2.23 PACA Origination, Permanent Invocation

2.24 PACA Origination, PACA Disabled for Mobile Station

2.25 True IMSI Support

2.26 Initial Service Configuration and Negotiation

2.27 Base Station Requested Service Negotiation (Successful Scenarios)

4

TSG-C42 Page 2-2

10/19/2001 C.S0031

Table 2-1 POTS Tests Continued12

2.28 Base Station Reject Scenarios during Service Negotiation

2.29 Mobile Station Reject Scenarios during Service Negotiation

2.30 Service Negotiation Completion via General Handoff Direction Message and UniversalHandoff Direction Message

2.31 SCR without NN-SCR and NN-SCR without SCR in General Handoff Direction Messageand Universal Handoff Direction Message

2.32 Base Station Request Overrides the Mobile Station Request

2.33 Service Negotiation Involving Partial SCR and/or Partial NN-SCR

2.34 Quasi-Orthogonal Functions (QOF) assignment

2.35 Release Order on Access Channel

3

TSG-C42 Page 2-3

10/19/2001 C.S0031

2.1 Mobile Station Originated Call1

2.1.1 Definition2This test verifies that the mobile station can initiate a call to a land party, using a combination of3forward and reverse radio configurations (RC), listed as follows:4

5Forward Channel Reverse Channel

RC1 RC1

RC2 RC2

RC 3 RC 3

RC 4 RC 3

RC 5 RC 4

Once user traffic is present in both directions, the called party shall initiate release of the call.6

MS BS

Origination Message

Extended Channel Assignment Message

BS ACK Order

Preamble

Service Connect Message

Service Connect Completion Message

Applies ring back tone in audio path or AWI Message

Removes ring back tone from audio path or AWI Message

Conversation

Release Order

Release Order

Initiate a callBegin sending NullTraffic on F-FCH

Aquire preamble

Disconnect the call

Begin sending NullTraffic on R-FCH

Answer Call

7Figure 2.1.1-1 Reference Call Flow for mobile station Originated Voice Call from a Land8

Party Call910

TSG-C42 Page 2-4

10/19/2001 C.S0031

1


2.2.6.2.5 Mobile Station Origination Operation32.6.3 System Access State42.6.3.5 Mobile Station Origination Attempt Substate52.6.4 Mobile Station Control on the Traffic Channel State62.7.1.3.2.4 Origination Message72.7.2.3.2.15 Service Option Control Message82.7.3 Orders93.6.3.5 Response to Origination Message103.6.4 Traffic Channel Processing113.7.2.3.2.21 Extended Channel Assignment Message123.7.3.3.2.3 Alert With Information Message133.7.3.3.2.20 Service Connect Message143.7.4 Orders153.7.5.5 Signal16


Connect the mobile station to the base station as shown in Figure 2.1.2-1. Set the test18parameters as shown in Table 2.1.2-1.19

20

21Figure 2.1.2-1 Functional Setup for Mobile Station Originated22

Voice Call to a Land Party Call Test2324

Table 2.1.2-1 Call Setup Test Signal Channel Levels25

POTS Signal Channel Forward Channel Level(RC 1, 3, 4)

Forward Channel Level(RC 2, 5)

Îor -75 dBm/1.23 MHz -75 dBm/1.23 MHz

Pilot Ec/Ior -7 dB -7 dB

Traffic Ec/Ior -15.6 dB -12.3 dB

26

TSG-C42 Page 2-5

10/19/2001 C.S0031

Setup a mobile station originated call with RC1 on both the forward and reverse links.1

Note that for calls with RC3 or greater the parameters of the Origination Message shall2be set as follows:3

4Fields Parameters Setting

ENHANCED_RC ‘1’ (Support of enhanced RC)

FOR _RC_PREF ‘011’ (RC 3)

REV_ RC_PREF ‘011’ (RC 3)

5

Instruct the base station to accept the call and assign a traffic channel with RC1 on both6forward link and reverse link.7

Note for RC3 and greater, verify the base station sends the Extended Channel8Assignment Message with the following parameters set as follows:9

10Field Parameters Setting

ASSIGN_MODE ‘000’ (Traffic Channel Assignment) or ‘100’ (Enhanced Traffic Channel Assignment)

FOR_FCH_RC orFOR_RC

‘011’ (RC 3)

REV_FCH_RC orFCH_RC

‘011’(RC 3)

11

When ring back tone is applied to the audio path, if applicable, instruct the called party to go12off hook.13

Verify that the RC1 is used on both forward link and reverse link and verify the user traffic (Ex.14audio) on the both directions.15

Instruct the called party to terminate the call.16

Repeat steps b through f with the following modifications: Replace RC1 with RC2 on both the17forward and reverse links.18

Repeat steps b through f with the following modifications: Replace RC1 with RC3 on both the19forward and reverse links.20

Repeat steps b through f with the following modifications: Replace RC1 with RC4 on the21forward link and replace RC1 with RC3 on the reverse link.22

Repeat steps b through f with the following modifications: Replace RC1 with RC5 on the23forward link and replace RC1 with RC4 on the reverse link.24

TSG-C42 Page 2-6

10/19/2001 C.S0031

2.1.3 Minimum Standard1The call shall be established with user traffic in both directions, by using the radio configurations2specified in 2.1.2. Upon the called party terminating the call, the call shall be terminated.3

4

2.2 Mobile Station to Land Party Call, Radio Link Failure During Conversation -5Reverse Link6

2.2.1 Definition7This test will verify if the reverse radio link is disconnected while a mobile station originated call8is active, the base station will detect loss of the reverse link and release the call.9

Traceability: IS-2000 3.4.2,3.6.4, 3.6.4.410



b. Setup a mobile station originated call.13

c. Verify user data in both directions.14

d. Attenuate the reverse RF link (Attenuator 2 in Figure 2.1.2-1) to cause a loss of the15reverse link.16

e. Verify the following:17

1. The base station shall send a Release Order to the mobile station and release all18forward traffic channel resources.19

2. The mobile station shall enter the System Determination Substate.20

21

2.2.3 Minimum Standard22The base station shall send a Release Order to the mobile station and release all forward traffic23channel resources. The mobile station shall enter the System Determination Substate.24

2.3 Mobile Station to Land Party, Radio Link Failure During Conversation - Forward25Link26

2.3.1 Definition27This test will verify if the forward radio link is disabled while a mobile station originated call is28active, the mobile station will detect loss of the forward link and release the call.29

Traceability: (See [4] ), 2.6.4.530




c. Verify user data in both directions.34

TSG-C42 Page 2-7

10/19/2001 C.S0031

d. Attenuate the forward RF link (Attenuator 1 in Figure 2.1.2-1) to cause a loss of the1forward link.2

e. Verify the following:3

1. The mobile station shall disable its transmitter upon receiving a period of (N2m x420) ms with insufficient signal quality (e.g. bad frames).5

2. Upon expiration of the fade timer (i.e. within 5 seconds of loss of the forward6link), the mobile station shall declare loss of the forward link and shall enter the7System Determination Substate.8

9

2.3.3 Minimum Standard10The call shall be established with audio in both directions. The mobile station shall disable its11transmitter and enter the System Determination Substate within five seconds of detecting loss of12the forward link.13

2.4 Mobile Station Originated Call, Test Service Options14

2.4.1 Definition15This test will verify the mobile station can initiate a call to the land party using each of16the supported Test Service Options and that FER on the reverse channel does not exceed17a specified value.18

Traceability: (See [4] ) 2.6.4.1.2, 3.6.4.1.2, IS-126-A19



b. Set test parameters as shown in Table 2.1.2-1.22

c. Setup a mobile station originated call using the first supported Test Service Option23from Table 2.4.2.1.24

25ServiceOption Description

2 Mobile Station Rate Set 1 Loopback Service Option

9 Mobile Station Rate Set 2 Loopback Service Option

55 Loopback Service Option (LSO)

32798 Mobile Station Rate Set 1 Markov Service Option

32799 Mobile Station Rate Set 2 Markov Service Option

54 Markov Service Option (MSO)

Table 2.4.2.1 Test Service Options26

TSG-C42 Page 2-8

10/19/2001 C.S0031

d. Measure FER on the reverse channel.1

e. Repeat steps c and d using each Test Service Option supported.2

2.4.3 Minimum Standard3For each Test Service Option supported, the mobile station shall originate a call. . FER on the4reverse channel shall not exceed the base station FER set point.5

2.5 Mobile Station to Land Party Call, Busy Tone6

2.5.1 Definition7This test will verify the mobile station successfully receives a busy tone on a call initiated to a8busy land party.9

Traceability: (See [4] ) 2.6.4.4, 3.6.4.3, 3.7.5, 3.7.5.5-310



b. Setup a mobile station originated call to a busy land party.13

c. Verify the following:14

1. mobile station receives a Flash With Information Message or in-band tone15indicating “called-party busy”.16

2. Mobile Station plays a busy tone to the user.17

d. End call at the mobile station.18

2.5.3 Minimum Standard19A busy tone shall be played to the user by the mobile station.20

2.6 Mobile Station to Land Party Call, No Traffic Channel Resources Available21

2.6.1 Definition22This test will verify that if there are no traffic channel (FCH or DCCH) resources available to23assign the call, the base station will send a Reorder Order or a Release Order to the mobile24station.25

Traceability: (See [4] ) 3.6.3.5, 3.6.2.3, 3.7.5, 3.7.5.5-326



b. Take all voice (TCH) resources out of service or configure the base station to behave29in a similar fashion.30

c. Setup a mobile station originated call.31

d. Verify the following:32

1. The base station sends a Reorder Order or Release Order to the mobile station.33

TSG-C42 Page 2-9

10/19/2001 C.S0031

2. If the base station sends a Reorder Order, the reorder tone sounds as a 480 Hz1tone added to a 620 Hz tone repeated in a 250 ms on, 250 ms off cycle. And the2mobile station shall enter the Mobile Station Idle State.3

3. If the base station sends a Release Order, the mobile station shall enter the4Mobile Station Idle State or the System Determination Substate.5

2.6.3 Minimum Standard6The base station shall send a Reorder Order or a Release Order instead of a (Extended) Channel7Assignment Message and the mobile station shall behave as stated in step d of 2.6.2.8

2.7 Mobile Station to Land Party Call, Reverse Link Failure During Call Setup9

2.7.1 Definition10This test will verify that if the reverse radio link is disabled before a mobile station originated11call has reached the traffic channel, the base station will fail to acquire the reverse traffic channel12and will release the call.13

Traceability: (See [4] ) 3.4.1, 3.6.4.2, 2.6.4.2, 2.6.1.114




c. Before the base station sends the (Extended)Channel Assignment Message,18attenuate the reverse link (Attenuator 2 in Figure 2.1.2-1) to cause loss of the19reverse link.20


1. The reverse link transmission is not received by the base station.22

2. The base station shall release all traffic channel resources allocated for this call.23

2.7.3 Minimum Standard24Upon detecting loss of reverse link from the mobile station, the base station shall release all25traffic channel resources.26

2.8 Mobile Station to Land Party Call, Forward Link Failure During Call Setup27

2.8.1 Definition28This test verifies that if the forward link is disabled before a mobile station originated call has29reached the traffic channel, the mobile station will detect loss of the paging channel, the call will30be released, and the mobile station returns to the Mobile Station Idle State.31

Traceability: (See [4] ); 2.4.3, 2.4.4, 2.6.3.432



TSG-C42 Page 2-10

10/19/2001 C.S0031


c. Before the base station sends the (Extended) Channel Assignment Message,2attenuate the forward link (Attenuator 1 in Figure 2.1.2-1) to cause loss of the3forward link.4


1. The forward link transmission is not received by the mobile station.6

2. Upon declaring loss of the Paging Channel, the mobile station shall disable its7transmitter and enter the System Determination Substate.8

9

2.8.3 Minimum Standard10Following attenuation of the forward link, the mobile station shall not receive the (Extended)11Channel Assignment Message. The mobile station shall disable its transmitter and enter the12System Determination Substate.13

2.9 Mobile Station Terminated Call14

2.9.1 Definition15This test verifies that the mobile station can receive a call, using a combination of forward and16reverse radio configurations (RC), listed as follows:17

18Forward Channel Reverse Channel

RC1 RC1

RC2 RC2

RC 3 RC 3

RC 4 RC 3

RC 5 RC 4

19Once the user traffic is present on the both directions, the calling party will initiate release of the20call.21

TSG-C42 Page 2-11

10/19/2001 C.S0031

MS BS


Order Message (BS ACK)

Preamble


AWI Message (ringing applied)

Connect Order

Conversation

Release Order

Release Order

Initiate a call

Begin sending NullTraffic on F-FCH

Aquire preamble

Disconnect the call

Begin sending NullTraffic on R-FCH

Page Response Message

General Page Message

Receive N5m*20mssufficient signal on F-FCH

and begin sending preambleon Reverse Pilot Channel

Answers Call


1Figure 2.9.1-1 Reference Call Flow for Mobile Station Terminated Voice Call from a Land2

Party Call3


2.6.2.3 Mobile Station Page Match Operation52.6.3 System Access State62.6.3.3 Page Response Substate72.6.4 Mobile Station Control on the Traffic Channel State82.7.1.3.2.5 Page Response Message92.7.2.3.2.15 Service Option Control Message102.7.3 Orders113.6.3.3 Response to Page Response Message123.6.4 Traffic Channel Processing133.7.2.3.2.17 General Page Message143.7.2.3.2.21 Extended Channel Assignment Message153.7.3.3.2.3 Alert With Information Message163.7.3.3.2.20 Service Connect Message173.7.4 Orders183.7.5.5 Signal19

TSG-C42 Page 2-12

10/19/2001 C.S0031


a. Connect the mobile station to the base station as shown in Figure 2.1.2-1. Set the2test parameters as shown in Table 2.1.2-1.3

b. Setup a mobile station terminated call. Instruct the base station to assign a traffic4channel with RC1 on the both forward link and reverse links.5

Note for RC3 and greater verify the base station sends the Extended Channel6Assignment Message with the following parameters set as follows:7

8Field Parameters Setting

ASSIGN_MODE ‘000’ (Traffic Channel Assignment) or ‘100’ (Enhanced Traffic Channel Assignment)

FOR_FCH_RC orFOR_RC

‘011’ (RC 3)

REV_FCH_RC orREV_RC

‘011’ (RC 3)

9

c. When ring back tone is applied to the audio path, if applicable, instruct the mobile10station party to answer the call.11

d. Verify that the RC1 is used on the both forward link and reverse links and verify the12user traffic (Ex. Audio) on the both directions.13

e. Instruct the calling party to terminate the call.14

f. Repeat steps b through e with the following modifications: Replace RC1 with RC3 on15both the forward and reverse links.16

g. Repeat steps b through e with the following modifications: Replace RC1 with RC4 on17forward link and replace RC1 with RC3 on the reverse link.18

h. Repeat steps b through e with the following modifications: Replace RC1 with RC5 on19the forward link and replace RC1 with RC4 on the reverse link.20

2.9.3 Minimum Standard21The call shall be established with user traffic present on the both directions, by using the radio22configurations specified in 2.9.1. Upon the calling party terminating the call, the call shall be23terminated.24

2.10 Mobile Station terminated Call, Test Service Options25

2.10.1 Definition26This test will verify the mobile station can respond to a call initiated using each of the supported27Test Service Options and that FER on the reverse channel does not exceed a specified value.28

Traceability: (See [4] ); 2.6.4.1.2, 3.6.4.1.2, IS-126-A29

TSG-C42 Page 2-13

10/19/2001 C.S0031



b. Set test parameters as shown in Table 2.1.2-1.3

c. Originate a call to the mobile station using the first supported Test Service Option4from Table 2.4.2.1.5

d. Measure FER on the reverse channel.6

e. Repeat steps c and d using each Test Service Option supported.7

2.10.3 Minimum Standard8The mobile station shall successfully terminate (complete) a call on each Test Service Option9supported. FER on the reverse channel shall not exceed the base station FER set point.10

2.11 Land Party to Mobile Station Call, Mobile Operating in Slotted Mode11

2.11.1 Definition12This test verifies the mobile station can operate in slotted mode, uses the correct slot cycle, and13responds to General Page Message from the base station received in its assigned slot. This test14will verify the base station can determine the assigned Paging Channel slots for a mobile station15and send a General Page Message in the assigned Paging Channel slot for that mobile station.16

Traceability: (See [4] ); 2.6.2.1.1, 2.6.3.3, 2.6.4.2, 2.6.4.4, 3.6.2.1.3, 3.6.2.3, 3.6.3.3,173.6.4.2, 3.6.4.3, 3.6.4.418



b. Enable Parameter Change registration.21

c. Disable all other forms of registration.22

d. Set the MAX_SLOT_CYCLE_INDEX of the base station to 2.23

e. Set the SLOT_CYCLE_INDEX of the mobile station to 0.24

f. Wait for Parameter Change registration to occur.25

g. Setup a mobile station terminated call with the mobile station in slotted mode.26Verify that the base station pages the mobile in the assigned slot of the mobile27station, per Table 2.11.3-1.28

h. Verify user data in both directions.29

i. End call at the mobile station.30

j. Set the mobile station SLOT_CYCLE_INDEX to 1, and repeat steps f through i.31

k. Set the mobile station SLOT_CYCLE_INDEX to 2, and repeat steps f through i.32

l. Set the mobile station SLOT_CYCLE_INDEX to 3, and repeat steps f through i.33

m. Set the base station MAX_SLOT_CYCLE_INDEX to 3, and repeat steps f through g.34

TSG-C42 Page 2-14

10/19/2001 C.S0031

2.11.3 Minimum Standard1The base station pages the mobile station in the appropriate slot and the call shall be established2with audio in both directions in all cases.3

4

Table 2.11.3-1 Slot Cycle Length Versus Various Values of5MAX_SLOT_CYCLE_INDEX and SLOT_CYCLE_INDEX6

Step MAX_SLOT_CYCLE_INDEX(Base Station)

SLOT_CYCLE_INDEX(Mobile Station)

SlotCycleIndexUsed

Slot CycleLength

(seconds)

e 2 0 0 1.28

j 2 1 1 2.56

k 2 2 2 5.12

l 2 3 2 5.12

m 3 3 3 10.24

7

2.12 MSID, MCC, and IMSI8

2.12.1 Definition9These tests verify the protocol of the Mobile Station Identifier number (MSID or10MSIN), Mobile Country Code (MCC), and International Mobile Station Identity11(IMSI). In each test, certain fields of the Extended System Parameters Message12are set at the base station, and/or some corresponding parameters are13programmed into the mobile station. Then a call is made, either mobile14origination or mobile termination. Finally, the layer 3 messaging log (MDM or15base station) is examined for proper Origination Message or Page Response16Message.17

18Three instances of PREF_MSID_TYPE are checked. Checks are also made to ensure that the19base station uses a valid addressing form for the cases when the MCC and IMSI_11_12 of the20mobile station and base station match, do not match or are wildcard values.21

Traceability:22

[4] 3.7.2.3.2.13 Extended System Parameters Message23

[4] 2.6.2.2.5 Extended System Parameters Message24

[4] 2.6.2.3 Mobile Station Page Match Operation25

[4] 2.3.1 Mobile Station Identification Number26

[4] 2.3.1.1 Encoding of IMSI_M_S and IMSI_T_S 1127

[4] Table 3.7.2.3.2.13-1. Preferred MSID Types28

[4] 3.6.2.2 Overhead Information29

TSG-C42 Page 2-15

10/19/2001 C.S0031


a. Connect the mobile station to the base station as shown in Figure 2.1.2-1, so that2the mobile registers and enters the Mobile Station Idle State.3

b. Set PREF_MSID_TYPE to ‘00’ and USE_TMSI to ‘0’ in the Extended System4Parameters Message and make a mobile station originated call and mobile station5terminated call (Test 1).6

c. Set PREF_MSID_TYPE to ‘10’ and USE_TMSI to ‘0’ in the Extended System7Parameters Message. Program the mobile station with the same values of MCC and8IMSI_11_12 sent in the Extended System Parameters Message by the base station.9Make a mobile station originated call and mobile station terminated call (Test 2).10

d. Set PREF_MSID_TYPE to ‘10’ and USE_TMSI to ‘0’ in the Extended System11Parameters Message. Program the mobile station with the same value of IMSI_11_1212but with a different value of MCC sent in the Extended System Parameters Message13by the base station. Make a mobile originated call and mobile terminated call (Test143).15

e. Set PREF_MSID_TYPE to ‘10’ and USE_TMSI to ‘0’ in the Extended System16Parameters Message. Program the mobile station with the same value of MCC but17with a different value of IMSI_11_12 sent in the Extended System Parameters18Message by the base station. Make a mobile originated call and mobile terminated19call (Test 4).20

f. Set PREF_MSID_TYPE to ‘10’ and USE_TMSI to ‘0’ in the Extended System21Parameters Message. Program the mobile station with different values of MCC and22IMSI_11_12 than those sent in the Extended System Parameters Message by the23base station. Make a mobile originated call and mobile terminated call (Test 5).24

g. Set PREF_MSID_TYPE to ‘11’ and USE_TMSI to ‘0’ in the Extended System25Parameters Message. Program the mobile station with the same values of MCC and26IMSI_11_12 sent in the Extended System Parameters Message by the base station.27Make a mobile station originated call and mobile station terminated call (Test 6).28

h. Set PREF_MSID_TYPE to ‘11’ and USE_TMSI to ‘0’ in the Extended System29Parameters Message. Program the mobile station with the same value of IMSI_11_1230used in the base station but with a different value of MCC. Make a mobile originated31call and mobile terminated call (Test 7).32

i. Set PREF_MSID_TYPE to ‘11’ and USE_TMSI to ‘0’ in the Extended System33Parameters Message. Program the mobile station with the same value of MCC but34with a different value of IMSI_11_12 sent in the Extended System Parameters35Message by the base station. Make a mobile originated call and mobile terminated36call (Test 8).37

j. Set PREF_MSID_TYPE to ‘11’ and USE_TMSI to ‘0’ in the Extended System38Parameters Message. Program the mobile station with different values of MCC and39IMSI_11_12 than those sent in the Extended System Parameters Message by the40base station. Make a mobile originated call and mobile terminated call (Test 9).41

TSG-C42 Page 2-16

10/19/2001 C.S0031

k. Set PREF_MSID_TYPE to ‘10’, USE_TMSI to ‘0’, MCC to ‘1111111111’(wildcard), and1IMSI_11_12 to ‘1111111’(wildcard) in the Extended System Parameters Message.2Make a mobile originated call and mobile terminated call (Test 10).3

l. Set PREF_MSID_TYPE to ‘11’, USE_TMSI to ‘0’, MCC to ‘1111111111’ (wildcard),4and IMSI_11_12 to ‘1111111’ (wildcard) in the Extended System Parameters5Message. Make a mobile originated call and mobile terminated call (Test 11).6

7


For all tests, the call shall complete normally with audio in each direction.1011

For Test 1, the mobile station shall set its MSID_TYPE to ‘000’ and send IMSI_S12and ESN in the Origination Message and Page Response Message.13For Test 2, the mobile station shall set its MSID_TYPE to ‘010’ and shall send14IMSI_S (shall not send MCC and IMSI_11_12) in the Origination Message and15Page Response Message.16For Test 3, the mobile station shall set its MSID_TYPE to ‘010’ and shall send17MCC and IMSI_S (shall not send IMSI_11_12) in the Origination Message and18Page Response Message.19For Test 4, the mobile station shall set its MSID_TYPE to ‘010’ and shall send20IMSI_11_12 and IMSI_S (shall not send MCC) in the Origination Message and21Page Response Message.22For Test 5, the mobile station shall set its MSID_TYPE to ‘010’ and shall send23MCC, IMSI_11_12 and IMSI_S in the Origination Message and Page Response24Message.25For Test 6, the mobile station shall set its MSID_TYPE to ‘011’ and shall send26IMSI_S and ESN (shall not send MCC and IMSI_11_12) in the Origination27Message and Page Response Message.28For Test 7, the mobile station shall set its MSID_TYPE to ‘011’ and shall send29MCC and IMSI_S and ESN (shall not send IMSI_11_12) in the Origination30Message and Page Response Message.31For Test 8, the mobile station shall set its MSID_TYPE to ‘011’ and shall send32IMSI_11_12, IMSI_S and ESN (shall not send MCC) in the Origination Message33and Page Response Message.34For Test 9, the mobile station shall set its MSID_TYPE to ‘011’ and shall send35MCC, IMSI_11_12 and IMSI_S and ESN in the Origination Message and Page36Response Message.37For Test 10, the mobile station shall set its MSID_TYPE to ‘010’ and shall send38IMSI_S (but should not send MCC and IMSI_11_12) in the Origination Message39and Page Response Message.40For Test 11, the mobile station shall set its MSID_TYPE to ‘011’ and shall send41IMSI_S and ESN (but should not send MCC and IMSI_11_12) in the Origination42Message and Page Response Message.43

TSG-C42 Page 2-17

10/19/2001 C.S0031

2.13 TMSI Assignment1

2.13.1 Definition2This test verifies the base station can assign a Temporary Mobile Station Identity (TMSI) to the3mobile station, and that mobile-originated and mobile-terminated calls can be performed using4the TMSI.5

Traceability: (See [4] ); 2.3.15,2.6.2.3, 2.6.3.1.5, 2.7.1.3.2.8, 2.7.2.3.2.196



b. Configure the base station to send the Extended System Parameters Message with9values as shown in Table 2.13.2-1.10

11

Table 2.13.2-1 Extended System Parameters Message Values for TMSI Tests12

Field Value

PREF_MSID_TYPE '10'

USE_TMSI '1'13

c. Enable power on registration. Configure the base station to assign TMSIs.14

d. Power on the mobile station and wait for power on registration to occur.15

e. Instruct the base station to send a TMSI Assignment Message to the mobile station16with a TMSI Assignment. Verify that the mobile station responds with a TMSI17Assignment Completion Message within T56m seconds.18

f. Setup a mobile station originated call. Upon receiving the Origination Message at the19base station, verify the mobile station includes the correct TMSI in the message.20

g. End call.21

h. Setup a call from a land party to the mobile station. Log the General Page Message22and verify that the base station includes the correct TMSI in the message.23

i. End call.24

2.13.3 Minimum Standard25Both calls shall be successful. The Origination Message in step f and the General Page Message26in step h shall contain the TMSI that was assigned in step e.27

2.14 TMSI Expiration Time28

2.14.1 Definition29This test will verify that the mobile station operates properly in conjunction with various TMSI30Expiration Times.31

TSG-C42 Page 2-18

10/19/2001 C.S0031

Traceability: (See [4] ); 2.6.2.4, 3.7.2.3.2.19, 3.7.3.3.2.221



b. Configure the base station to send the Extended System Parameters Message with4values as shown in Table 2.13.2-1.5

c. Configure the base station to assign TMSI and enable power-up registration.6

d. Configure the base station TMSI_EXP_TIME. The base station shall set this field in7the TMSI Assignment Message to the System Time in units of 80ms x 212 when the8TMSI is to expire.9

e. Power on the mobile station and wait for power-up registration to occur.10

f. Instruct for the base station to send a TMSI Assignment Message to the mobile11station with a TMSI assignment. Verify that the mobile station responds with a TMSI12Assignment Completion Message within T56m seconds.13

g. Setup a mobile station originated call.14

h. Log the Origination Message at the base station and verify the mobile station15includes the correct TMSI in the message.16

i. End call.17

j. Wait for the TMSI expiration timer to expire. Upon expiration, setup another call.18Upon receiving the Origination Message at the base station, verify that the TMSI is19no longer included in the message.20

k. Power down the mobile station.21

l. Repeat steps e. through i. with a call from a land party to the mobile station. Upon22receiving the General Page Message at the base station, verify that the TMSI is no23longer included in the message.24

2.14.3 Minimum Standard25Each call in the test shall be successful. The Origination Message and General Page Message26shall include the correct TMSI prior to expiration of the TMSI timer. Following the expiration of27the TMSI timer, the TMSI shall no longer be included in the messaging.28

2.15 Mobile Station to Land Party Call, DTMF29

2.15.1 Definition30This test will verify mobile station-initiated DTMF tones operate properly during a CDMA call.31DTMF tones should be recorded for playback at a later time to verify time on, time off, power32level, frequency, and repeatability.33

Traceability: (See [4] ); 2.6.4.434

TSG-C42 Page 2-19

10/19/2001 C.S0031


a. Connect the mobile station as shown in Figure 2.15.2-1.2

3Figure 2.15.2-1 Functional Setup for Testing Mobile Station-Initiated DTMF Tones4

5


c. Direct the mobile station to send 0123456789#* as burst DTMF digits while7recording the resulting tones. Perform at various speeds/modes and randomize the8digit order. Note the order of digits to verify sequential order.9

d. Record DTMF on length, off length, and digit fields of Send Burst DTMF Message10received at the base station.11

e. If the mobile station supports various values for DTMF on and off lengths, repeat12steps b through d for the shortest and longest values.13

2.15.3 Minimum Standard14The mobile station shall not send subsequent tone messages until the previous message is15acknowledged by the base station.16

2.15.4 Frequency17Tone frequencies shall be ±1.5% of assigned frequencies shown in Table 2.15.3.1-118

2.15.4.1.1 Timing19The recorded pulse width shall be within 10% of the recommended pulse width for each20DTMF_ON_LENGTH tested.21The recorded inter-digit interval shall be within 10% of the recommended minimum inter-digit22interval for each DTMF_OFF_LENGTH tested.23

2.15.4.1.2 Repeatability24The cumulative binary distribution function is used in Table 2.15.3.3-1 to show various sample25levels versus the number of failures expected. Pass/fail criteria are shown in Table 2.15.3.3-2.26

27

TSG-C42 Page 2-20

10/19/2001 C.S0031

Table 2.15.3.1-1 DTMF Assigned Frequencies1

Digit Low Group (Hz) High Group (Hz)

1 697 1209

2 697 1336

3 697 1477

4 770 1209

5 770 1336

6 770 1477

7 852 1209

8 852 1336

9 852 1477

* 941 1209

0 941 1336

# 941 1477

2

Table 2.15.3.3-1 Cumulative Binomial Distribution Function3For 99.95% DTMF Success Rate4

Number of DTMF Tone Samples

n 100 250 500 750 1000

0 95.12% 88.25% 77.88% 68.72% 60.65%

1 99.88% 99.28% 97.35% 94.51% 90.98%

2 100.00% 99.97% 99.78% 99.34% 98.56%

3 100.00% 100.00% 99.99% 99.94% 99.83%

4 100.00% 100.00% 100.00% 100.00% 99.98%

5 100.00% 100.00% 100.00% 100.00% 100.00%

2 100.00% 100.00% 100.00% 100.00% 100.00%

5

Table 2.15.3.3-2 DTMF Pass/Fail Criteria6

Number of DTMFTone Samples

Number of FailuresPass Criteria

Number of FailuresFail Criteria

100 ≤ 2 > 2

250 ≤ 3 > 3

500 ≤ 4 > 4

1000 ≤ 5 > 5

7

TSG-C42 Page 2-21

10/19/2001 C.S0031

2.16 Forward Traffic Channel DTMF Tone Signaling1

2.16.1 Definition2The purpose of this test is to verify land party initiated DTMF tones operate properly during a3CDMA call. It also ensures sequencing and tone duration of the Send Burst DTMF Message and4the Continuous DTMF Tone Order are preserved on the Forward Traffic Channel.5

Traceability: (See [4] ); 3.7.3.3.2.9, 3.7.4-16



b. Setup a call between the mobile station and the land party DTMF source.9

c. At the DTMF source, perform the following steps in rapid succession:10

1) Press and hold any number key for approximately 5 seconds.11

2) Send characters 0123456789#* as burst DTMF messages. Perform at12various speeds/modes and randomize the digit order. Note the order of digits to13verify sequential order.14

3) Press and hold any number key on the keypad for approximately 515seconds.16

4) Again press and hold any number key on the keypad for approximately 517seconds.18

d. Using a DTMF detector, verify DTMF tones received at the output of the mobile19station.20

e. If the mobile station supports various values for DTMF on and off lengths, repeat21steps b through d for the shortest and longest values.22

f. Repeat this test for all rate sets supported by the mobile station.23


a. The base station shall send no subsequent tone message until the previous message25was acknowledged by the mobile station.26

b. The base station shall send a Continuous Tone Order (Start) and a Continuous Tone27Order (Stop) for each of the three 5 second key presses.28

c. The mobile station shall generate the tones in the order and approximate duration29transmitted by the base station.30

Frequency31Tone frequencies shall be +/-1.5% of assigned frequencies shown in table 2.15.3.1-1.32Timing33

DTMF_ON_LENGTH shall be within 10% of tolerance but more than 95 ms.34

DTMF_OFF_LENGTH shall be within 10% of tolerance but not less than 60 ms.35Repeatability36

Pass/fail criteria are shown in Table 2.15.3.3-2.37

TSG-C42 Page 2-22

10/19/2001 C.S0031

2.17 Enhanced DTMF Signaling1

2.17.1 Definition2The purpose of this test is to verify that sequencing and tone duration of the Send Burst DTMF3Message and the Continuous DTMF Tone Order are preserved.4

Traceability: (See [4] ); 2.6.4.45


a. Connect the mobile station as shown in figure 2.15.2-17


c. Direct the mobile station to perform the following steps in rapid succession:9


2) Direct mobile station to send characters 0123456789#* as a burst DTMF12message.13


4) Again press and hold any number key on the keypad for approximately 516seconds.17

d Record the tones produced at the terminated side.18


a. The mobile station shall send no subsequent tone message until the previous20message was acknowledged by the base station.21

b. The mobile station shall send a Continuous Tone Order (Start) and a Continuous Tone22Order (Stop) for each of the three 5 second key presses.23

c. The base station shall generate the tones in the order and approximate duration24transmitted by the mobile station.25

2.18 Channel Assignment from CDMA to AMPS26

2.18.1 Definition27This test will verify that a base station assigns a mobile station to AMPS when no CDMA traffic28channels are available.29

Traceability: (See [4] ); 2.6.1.1.2, 2.6.3.530


a. Connect the base station and mobile station as shown in Figure 2.18.2-1.32

TSG-C42 Page 2-23

10/19/2001 C.S0031

1

2Figure 2.18.2-1 Functional Setup for Redirection from CDMA to AMPS3

4

5

b. Take all CDMA traffic channel radio resources out of service or configure the base6station to behave in a similar fashion.7


d. Verify that the base station sends a Channel Assignment Message with9ASSIGN_MODE=‘011’ to assign the mobile station an analog voice channel or with10ASSIGN_MODE=‘010’ to acquire the analog system.11

e. Verify the mobile station acquires the AMPS system.12

f. Verify user data in both directions.13

g. End call.14

2.18.3 Minimum Standard15The mobile station shall be assigned to AMPS when no CDMA traffic channels are available.16

2.19 PACA Origination, User Terminates While Still In Queue17

2.19.1 Definition18This test verifies that a PACA-capable mobile station, upon failure to originate a call due to lack19of available voice/traffic channels, shall re-attempt the origination using the PACA feature code.20It verifies that a currently queued mobile station properly informs base station when user aborts21waiting for traffic channel.22

Traceability: (See [4] ); 2.6.2, 2.6.2.8, 2.6.3.5, 2.7.1.3.2.4, 2.7.1.3.2.9, 3.7.2.3.2.2023



TSG-C42 Page 2-24

10/19/2001 C.S0031

b. At base station, enable PACA feature for mobile station, assign a PACA priority level1to the mobile station, and disable Permanent Invocation PACA for the mobile2station.3

c. If the mobile station is capable of Slotted Mode, verify that the mobile station is4operating in the Slotted Mode.5

d. Ensure PACA is enabled on base station.6

e. Configure the base station to make all traffic channels busy.7

f. Setup a mobile station originated call.8

g. Verify the following:9

1) Mobile station originates call with PACA_REORIG bit='0' in Origination Message.10

2) Base station replies with Reorder Order.11

3) Mobile station retries the origination with the PACA_REORIG bit='1' in the12Origination Message.13

4) Base station sends PACA Message with PURPOSE='0000' and the mobile14station’s Queue Position (Q_POS).15

5) Mobile station acknowledges PACA Message.16

h. The mobile station user interface should indicate the origination has been17successfully queued.18

i. Verify the mobile station remains in non-slotted mode.19

j. End call to terminate queued origination. Verify that the mobile station sends a20PACA Cancel Message to the base station.21

k. Verify the mobile station enters slotted mode if applicable.22

2.19.3 Minimum Standard23The mobile station user interface should indicate to the user that the call has been ended. Upon24failure of first origination, mobile station shall attempt a second origination with PACA feature25code. When successfully entered in the PACA queue, mobile station shall indicate this state to26the user via user interface. The mobile station shall inform the base station via a PACA Cancel27Message when the user manually terminates queuing wait. Verify the mobile station sends PACA28Cancel Message to the base station.29

2.20 PACA Origination, Idle Handoff While in Queue30

2.20.1 Definition31This test verifies that a PACA-capable mobile station already in a PACA queue shall reoriginate32the PACA request when the mobile station performs an idle handoff.33

Traceability: (See [4] ); 2.6.2.1.4.2, 2.6.3.5, 2.7.1.3.2.4, 2.7.1.3.2.9, 3.7.2.3.2.2034


a. Connect the base stations and mobile station as shown in Figure 2.20.2-1.3637

TSG-C42 Page 2-25

10/19/2001 C.S0031

1Figure 2.20.2-1 Functional Setup for Idle Handoff PACA Test2

b. At the base station, enable PACA feature for mobile station, assign a PACA priority3level to mobile station, and disable Permanent Invocation PACA for mobile station.4

c. Ensure PACA is enabled on both base stations.5

d. Configure both base stations to make all traffic channels busy.6

e. Setup a mobile station originated call.7

f. The mobile station user interface should indicate origination successfully queued.8

g. Force an idle handoff from base station #1 to base station #2.9

h. Verify the mobile station reoriginates the PACA request with PACA_REORIG='1'.10

i. Verify a PACA Message is received from base station #2 indicating the mobile11station’s position in the PACA queue of base station #2.12

j. On the mobile station, originate a new call while still queued.13

k. The mobile station user interface should indicate to the user that the first PACA call14has been cancelled.15

TSG-C42 Page 2-26

10/19/2001 C.S0031

2.20.3 Minimum Standard1After the idle handoff, the mobile station shall send an Origination Message with the2PACA_REORIG bit='1'. When the user originates a second call while currently queued for the3first call, the mobile station should indicate to the user that the first queued PACA call has been4cancelled.5

2.21 PACA Origination, Traffic Channel Becomes Available6

2.21.1 Definition7This test verifies that a currently PACA queued mobile station, when notified by the base station8of an available traffic channel, should properly alert the user that the origination can now be9completed.10

Traceability: (See [4] ); 2.6.3.5, 2.7.1.3.2.4, 2.7.1.3.2.9, 3.7.2.3.2.2011



b. At the base station, enable PACA feature for mobile station, assign a PACA priority14level to the mobile station, and disable Permanent Invocation PACA for the mobile15station.16

c. Ensure PACA is enabled on base station.17

d. Configure the base station to make all traffic channels busy.18


f. If supported by the mobile station, verify that the mobile station user interface20indicates that an origination has been successfully queued.21

g. Make at least one traffic channel available on base station.22

h. The base station shall page the mobile station, and the mobile station should23indicate to the user that the PACA call is proceeding.24

i. Verify the call is completed and audio is present in both directions.25

j. End call.26

2.21.3 Minimum Standard27Upon a page from the base station due to a traffic channel becoming available, the mobile station28should alert the user that the origination can now be completed. The call shall be completed.29

2.22 PACA Origination, Features Interaction30

2.22.1 Definition31This test verifies that specific paging channel features, such as SMS and MWI, are delivered to32the mobile station while the mobile station is currently in a PACA queue.33


TSG-C42 Page 2-27

10/19/2001 C.S0031



b. At the base station, enable PACA feature for mobile station, assign a PACA priority3level to the mobile station, and disable Permanent Invocation PACA for the mobile4station.5

c. Ensure PACA is enabled on base station.6



f. Verify the mobile station user interface indicates that an origination has been9successfully queued.10

g. Send an SMS message over the Paging Channel to the mobile station. Verify the11message is received properly by the mobile station.12

h. Configure base station to send MWI to the mobile station. Verify MWI is displayed13by the mobile station.14

i. End call.15

2.22.3 Minimum Standard16While in a PACA queue, the mobile station shall properly receive SMS messages over the17Paging Channel, as well as receive and display the MWI.18

2.23 PACA Origination, Permanent Invocation19

2.23.1 Definition20This test verifies that a PACA-capable mobile station with Permanent Invocation feature enabled21shall be placed in PACA queue even if PACA is not requested in Origination Message.22




b. At the base station, enable PACA feature for mobile station, assign a PACA priority26level to the mobile station, and enabled Permanent Invocation PACA for the mobile27station.28

c. Ensure PACA is enabled on the base station.29



f. Verify the following:32

1) Mobile station originates call with PACA_REORIG bit='0' in Origination Message.33

2) Due to Permanent Invocation, base station sends PACA Message with34PURPOSE='0000' and the mobile station's Queue Position (Q_POS).35

TSG-C42 Page 2-28

10/19/2001 C.S0031

3) Mobile station acknowledges PACA Message.1

g. The mobile station user interface should indicate origination successfully queued.2

h. Make at least one traffic channel available on the base station.3

i. The base station shall page the mobile station, and the mobile station should4indicate to the user that the PACA call is proceeding.5

j. Verify call completes and audio is present in both directions.6

k. End call.7

2.23.3 Minimum Standard8A mobile station origination shall be placed in the PACA queue even though PACA is not9requested in Origination Message due to the base station having rights to Permanent Invocation10of PACA.11

2.24 PACA Origination, PACA Disabled for Mobile Station12

2.24.1 Definition13This test verifies that when a mobile station disabled for PACA attempts a PACA Origination,14the call shall fail.15




b. Ensure PACA is enabled on base station.19

c. At the base station, disable PACA feature for mobile station.20




1) Mobile station originates call with PACA_REORIG bit=0 in Origination24Message.25

2) Due to lack of available channels, base station replies with a Reorder26Order.27

3) Mobile station retries the origination with the PACA_REORIG bit = '1' in28the Origination Message.29

4) A second call re-origination attempt is denied by the base station and a30reorder tone is generated at the mobile station.31

2.24.3 Minimum Standard32The base station shall reject a request for PACA from a mobile station not authorized for PACA.33The mobile station shall generate a reorder tone.34

TSG-C42 Page 2-29

10/19/2001 C.S0031

2.25 True IMSI Support1

2.25.1 Land Party to Mobile Station Call, Matching MCC and IMSI_11_122

Traceability: (See [4] ); 2.1.3, 2.31, 2.6.2.2.5, 2.7.4.24, 3.7.2.3.2.133

2.25.1.1 True IMSI addressing supported by the base station and mobile station.4

2.25.1.1.1Definition5This test verifies that the base station pages the mobile station with True IMSI addressing6supported by the base station and mobile station when the MCC and IMSI_11_12 of the mobile7station match those sent by the base station in the Extended System Parameters Message.8

2.25.1.1.2 Method of Measurement9

a. Connect the mobile station to the base station as shown in Figure 2.20.2-110

b. Ensure the mobile station is programmed with the same values of MCC and11IMSI_11_12 used in the base station. Do not use MCC (wild card) value in the base12station or mobile station Escape Code.13

c. Configure the base station to send the Extended System Parameters Message with14the value IMSI_T_SUPPORTED=1.15

d. Enable power on registration.16

e. Enable authentication. Configure the base station to disallow mobile station17terminated calls if authentication fails.18

f. Power on the mobile station and wait for power on registration to occur.19

g. Initiate a land party to mobile station call.20

h. Verify user data in both directions and end call at the mobile station.21

2.25.1.1.3 Minimum Standard22The call shall be successfully established using the IMSI_T address form.23

2.25.1.2 True IMSI addressing supported by the base station with MIN-based24addressing supported by the mobile station.25

2.25.1.2.1 Definition26This test verifies that the base station pages the mobile station with True IMSI addressing27supported by the base station and MIN-based addressing supported by the mobile station when28the MCC and IMSI_11_12 of the mobile station match those sent by the base station in the29Extended System Parameter Message.30



b. Ensure the mobile station is programmed with values of MCC set to “310” [for the33United States, or other suitable value] or “000” and IMSI_11_12 set to “00”.34

TSG-C42 Page 2-30

10/19/2001 C.S0031



e. Enable authentication. Configure the base station to disallow mobile terminated4calls if authentication fails.5


g. Initiate a land party call to the mobile station.7

h. Verify user data and end call at the mobile station.8

2.25.1.2.3 Minimum Standard9The call shall be successfully established using the IMSI_M address form.10

2.25.1.3 True IMSI addressing not supported by the base station or the mobile11station12

2.25.1.3.1 Definition13This test will verify the base station pages the mobile station when True IMSI addressing is not14supported by the base station, when the MCC and IMSI_11_12 of the mobile station match those15sent by the base station in the Extended System Parameters Message.16



b. Ensure the mobile station is programmed with the same values of MCC and19IMSI_11_12 used in the base station. Do not use MCC (wild card) value in the base20station or mobile station Escape Code.21







2.25.1.3.3 Minimum Standard30The call shall be successfully established using IMSI_M address form.31

TSG-C42 Page 2-31

10/19/2001 C.S0031

2.25.2 Land Party to Mobile Station Call, Different MCC and IMSI_11_121

2.25.2.1 Definition2This test verifies the base station selects one of the valid forms of paging channel address when3neither the MCC nor the IMSI_11_12 of the mobile station being addressed match those being4sent by the base station in the Extended System Parameters Message.5


a. Connect the mobile station to the base station as shown on Figure 2.20.2-1.7

b. Ensure the mobile station is programmed with different values of MCC and8IMSI_11_12 than those used in the base station. Do not use MCC (wild card) value9in the base station or mobile station Escape Code.10







2.25.2.3 Minimum Standard19The call shall be successfully established using IMSI_T address form.20

2.26 Initial Service Configuration and Negotiation21

2.26.1 Definition22This test verifies that the initial service configuration in effect is according to the value specified23via the GRANTED_MODE field of the Extended Channel Assignment Message.24

TSG-C42 Page 2-32

10/19/2001 C.S0031

BS

DedicatedChannels

MS

DedicatedChannels

Service Request Message

Service Connect Message(SCR_new, NN-SCR_new)

New serviceconfigurationtakes effect

CommonChannels

CommonChannels

Origination Message /Page Response Message

(SO)

Extended Channel Assignment Message(GRANTED_MODE)

Initial serviceconfiguration

in effect


1Figure 2.26.1-1 Reference Call Flow for Initial Service Configuration and Negotiation2


2.6.4.1.2 MS Service Configuration and Negotiation procedures42.6.4.1.14 Processing the Service Configuration Record52.6.4.1.15 Processing the Non-Negotiable Service Configuration Record62.6.4.2 Traffic Channel Initialization Substate72.7.1.3.2.4 Origination Message82.7.1.3.2.5 Page Response Message92.7.2.3.2.12 (MS) Service Request Message102.7.2.3.2.13 (MS) Service Response Message112.7.2.3.2.14 (MS) Service Connect Completion Message122.7.4.18 Service Configuration information record133.6.4.1.2 BS Service Configuration and Negotiation procedures143.7.2.3.2.21 Extended Channel Assignment Message153.7.3.3.2.18 (BS) Service Request Message163.7.3.3.2.19 (BS) Service Response Message173.7.3.3.2.20 (BS) Service Connect Message183.7.3.3.2.31 General Handoff Direction Message193.7.3.3.2.36 Universal Handoff Direction Message203.7.5.7 (BS) Service Configuration information record213.7.5.20 (BS) Non-Negotiable Service Configuration information record22



b Initiate a mobile station originated call.25

c Upon receiving an Origination Message, configure the base station to send an26Extended Channel Assignment Message to the mobile station, with the following27fields set as follows:28

TSG-C42 Page 2-33

10/19/2001 C.S0031

1Field Value

ASSIGN_MODE '000' or '100'

GRANTED_MODE '00'

DEFAULT_CONFIG '000', '001', '010', '011', or'100'

2

d. Upon establishing dedicated channels, instruct the mobile station to initiate service3negotiation to request for a new service configuration. Verify that the mobile station4sends a Service Request Message with REQ_PURPOSE set to ‘0010’.5

e. Instruct the base station to send a Service Connect Message, with a valid and6acceptable Service Configuration Information Record (SCR) and Non-Negotiable7Service Configuration Information Record (NN-SCR) to the mobile station. The8parameters of SCR and NN-SCR should be set based on the known capabilities of9the mobile station under test, such that it is guaranteed the mobile station will10accept the service configuration specified by these two information records.11


1) Prior to the new service configuration sent in the Service Connect13Message takes effect, verify the following:14

• The service configuration in use is the one jointly specified by the15DEFAULT_CONFIG value sent in the Extended Channel Assignment Message16and the default Non-Negotiable part of the service configuration parameters17specified in the Traffic Channel Initialization substate.18

2) When the new service configuration sent in the Service Connect Message19takes effect, verify the following:20

• The service configuration in use is the one specified by SCR and NN-SCR in the21Service Connect Message sent by the base station.22

• Verify user traffic (Ex. Audio) on both directions.23

3) The base station receives a Service Connect Completion Message from the24mobile station.25

g. Repeat steps a through e, but with the following modifications:26

1) In step c, instruct the base station to send an Extended Channel27Assignment Message to the mobile station, with the following fields set as follows:28

29Field Value


GRANTED_MODE '01'

30

h. Verify the following:31

TSG-C42 Page 2-34

10/19/2001 C.S0031


• The service configuration in use is the one jointly specified by the default3multiplex option and transmission rates corresponding to the service option4requested by the mobile station in the Origination Message and the default Non-5Negotiable part of the service configuration parameters specified in the Traffic6Channel Initialization substate.7





i. Repeat steps a through e, but with the following modifications:15

1) In step c, instruct the base station to send an Extended Channel16Assignment Message to the mobile station, with the following fields set as follows:17

18Field Value


GRANTED_MODE '10'

19

j. Verify the following:20

1) In step c, when the mobile station is instructed to initiate service21negotiation to request for a new service configuration, verify that the mobile station22does not send a Service Request Message to the base station until a Service Connect23Message is received from the base station.24


• The service configuration in use is the one jointly specified by the default27multiplex option and transmission rates corresponding to the service option28requested by the mobile station in the Origination Message and the default Non-29Negotiable part of the service configuration parameters specified in the Traffic30Channel Initialization substate.31





TSG-C42 Page 2-35

10/19/2001 C.S0031

k. Repeat steps a through j for mobile station terminated calls. In this case, Origination1Message is replaced by Page Response Message.2

l. Repeat steps a though k for various values of DEFAULT_CONFIG and various values3of default multiplex option and transmission rates corresponding to the service4option requested by the mobile station either in the Origination Message or Page5Response Message.6

2.26.3 Minimum Standard7The initial service configuration in effect, i.e. upon establishing dedicated channels and until a8Service Connect Message shall be received from the base station, shall comply with the value9specified by the GRANTED_MODE received in the Extended Channel Assignment Message.10For GRANTED_MODE = 10, the mobile station shall not initiate service negotiation until the11Service Connect Message is received from the base station. When the new service configuration12specified by the Service Connect Message takes effect, user communications (Ex. Audio) shall13proceed without interruptions in both directions.14

2.27 Base Station Requested Service Negotiation (Successful Scenarios)15

2.27.1 Definition16This test verifies that the base station can request a valid new service configuration during traffic17channel operation via service negotiation procedures and this new configuration takes effect18upon being accepted by the mobile station. It also verifies that sending a Service Connect19Message by the base station, without involving Service Request Message/Service Response20Message sequence, for instructing the mobile station to use a new service configuration21succeeds.22

TSG-C42 Page 2-36

10/19/2001 C.S0031

BS

DedicatedChannels

MS

Conversation

DedicatedChannels

Service Request Message(REQ_PURPOSE=0010,

SCR_new_2)

Service Response Message(RESP_PURPOSE=0000)

Service Connect Message(SCR_new_2, NN-SCR_new_2)

CR_new_2/-SCR_new_2takes effect




SCR_new/NN-SCR_new

takes effect

1Figure 2.27.1-1 Reference Call Flow for Base Station Requested Service Negotiation2

Traceability: (See [4] ); 2.6.4.1.2, 2.6.4.1.14, 2.6.4.1.15, 2.6.4.2, 2.7.1.3.2.4, 2.7.1.3.2.5,32.7.2.3.2.12, 2.7.2.3.2.13, 2.7.2.3.2.14, 2.7.4.18, 3.6.4.1.2, 3.7.2.3.2.21, 3.7.3.3.2.18,43.7.3.3.2.19, 3.7.3.3.2.20, 3.7.3.3.2.31, 3.7.3.3.2.36, 3.7.5.7, 3.7.5.205



b. Setup a mobile station terminated call and establish a service configuration as9specified in 2.26.2. Verify user traffic (Ex. Audio) on both directions.10

c. Instruct the base station send a Service Connect Message to the mobile station with11a valid and acceptable SCR/NN-SCR.12


• The base station receives a Service Connect Completion Message from the mobile14station.15

• When the new service configuration takes effect, verify user traffic (Ex. Audio) on16both directions.17

e. Instruct the base station to initiate service negotiation by sending a Service Request18Message, proposing a valid and acceptable service configuration. Verify that the19base station sends a Service Request Message with REQ_PURPOSE set to ‘0010’ to20the mobile station.21

TSG-C42 Page 2-37

10/19/2001 C.S0031

f. Instruct the mobile station to accept this service configuration. Verify that, upon1receiving the Service Request Message, the mobile station sends a Service Response2Message with RESP_PURPOSE set to ‘0000’ to accept this service configuration.3

g. Instruct the base station to accept this service configuration by using a Service4Connect Message. Verify that, upon receiving the Service Response Message, the5base station sends a Service Connect Message to the mobile station with the6accepted SCR and a valid and acceptable NN-SCR.7


• The base station receives a Service Connect Completion Message from the9mobile station.10

• When the new service configuration takes effect, verify user traffic (Ex. Audio) on11both directions.12

2.27.3 Minimum Standard13When the new service configuration takes effect, user communications (Ex. Audio) proceeds14without interruptions in both directions. Furthermore, when base station sends a Service Connect15Message directly to specify a new service configuration, without involving any Service Request16Message/Service Response Message sequence, it is considered a valid service negotiation17procedure and it succeeds.18

2.28 Base Station Reject Scenarios during Service Negotiation19

2.28.1 Definition20This test verifies that when the base station rejects a service configuration proposed by the21mobile station, the mobile station terminates the service negotiation session and the previously in22use service configuration remains in effect.23

TSG-C42 Page 2-38

10/19/2001 C.S0031

Service Request Message(SCR_new, REQ_PURPOSE=0010)

BS

DedicatedChannels

MS

Conversation

DedicatedChannels

Service Response Message(RESP_PURPOSE=0001)MS terminates this

service negotiationsession

BS terminates thisservice negotiationsession

1Figure 2.28.1 Reference Call Flow for Base Station Reject Scenarios2




b. Setup a mobile station terminated call. Upon establishing dedicated channels,9instruct the mobile station to initiate service negotiation to request for a new service10configuration. Verify that the mobile station sends a Service Request Message with11REQ_PURPOSE set to ‘0010’.12

13

c. Configure the base station to reject this proposed service configuration and not14propose another new service configuration. Verify that, upon receiving the Service15Request Message, the base station sends a Service Response Message with16RESP_PURPOSE set to ‘0001’.17

18

19

20


TSG-C42 Page 2-39

10/19/2001 C.S0031

1) Upon receiving this message, the mobile station terminates this service1negotiation session. This can be verified by the following conditions:2

• The mobile station does not a send a Service Connect Completion Message to the3base station,4

• The mobile station does not send a Service Response Message to the base5station, and6

• The mobile station does not send a Service Request Message to the base station7with the same SERV_REQ_SEQ sent in the rejected Service Request Message.8

2) The service configuration previously in use (i.e. default service configuration)9continues to be in effect without any interruptions.10

e. Instruct the base station to initiate service negotiation by using a Service Request11Message. Verify that the base station sends a Service Request Message with12REQ_PURPOSE set to ‘0010’ to mobile station to request for a new service13configuration.14

f. Instruct the mobile station to propose the alternative service configuration. Verify15that, upon receiving the Service Request Message, the mobile station sends a Service16Response Message with RESP_PURPOSE set to ‘0010’ to the base station.17

g. Instruct the base station to reject this service configuration and not propose another18service configuration. Verify that, upon receiving the Service Request Message, the19base station sends a Service Request Message with REQ_PURPOSE set to ‘0001’ to20reject the service configuration.21


1) Upon receiving the Service Request Message from the base station, the mobile23station terminates this service negotiation session. This can be verified by the24following conditions:25

• The mobile station does not a send a Service Connect Completion Message to the26base station, and27

• The mobile station does not send a Service Response Message to the base28station.29

• The base station does not send a Service Request Message to the mobile station30with the same SERV_REQ_SEQ sent in the rejected Service Request Message.31

2) The service configuration previously in use continues to be in effect without any32interruptions.33

2.28.3 Minimum Standard34If the service configuration is rejected by the base station, both mobile station and base station35shall terminate the service negotiation session and the service configuration previously in use36shall remain in effect.37

TSG-C42 Page 2-40

10/19/2001 C.S0031

2.29 Mobile Station Reject Scenarios during Service Negotiation1

2.29.1 Definition2This test verifies that when the mobile station rejects a service configuration specified by the3base station, the mobile station sends expected signaling messages and the previously in use4service configuration remains in effect.5


BS

DedicatedChannels

MS

Conversation

DedicatedChannels

MS Reject Order(ORDQ=00000111)MS terminates this

service negotiationsession

BS terminates thisservice negotiationsession

6Figure 2.29.1-1 Reference Call Flow for Mobile Station Reject Scenarios7




b. Setup a mobile station originated call and establish a service configuration as14specified in 2.26.2. Verify user traffic (Ex. Audio) on both directions.15

c. Instruct the base station to send a Service Connect Message to the mobile station16with a valid service configuration that is guaranteed to be unacceptable to the17mobile station based on mobile station capability.18


1) Upon receiving this message, the mobile station sends a Mobile Station20Reject Order with ORDQ set to ‘00000111’.21

TSG-C42 Page 2-41

10/19/2001 C.S0031

2) The mobile station does not send a Service Connect Completion Message.1

3) The mobile station does not send a Service Request Message with2REQ_PURPOSE set to either ‘0000’ or ‘0001’.3

4) The mobile station does not send a Service Response Message with4RESP_PURPOSE set to either ‘0000’ or ‘0001’.5

5) The service configuration previously in use continues to be in effect6without any interruptions. Verify user traffic (Ex. Audio) on both directions.7

2.29.3 Minimum Standard8If the service configuration is rejected by the mobile station, both mobile station and base station9shall terminate the service negotiation session. User communication (Ex. Audio) shall proceed10without interruptions in both directions.11

2.30 Service Negotiation Completion via General Handoff Direction Message and12Universal Handoff Direction Message13

2.30.1 Definition14This test verifies that in the service negotiation procedures the Service Connect Message can be15replaced with a General Handoff Direction Message or a Universal Handoff Direction Message16without any change in the outcome of service negotiation.17

Service Request Message(SCR_new, REQ_PURPOSE=0010)

BS

DedicatedChannels

MS

Conversation

DedicatedChannels

Service Response Message(RESP_PURPOSE=0000)

New serviceconfiguration takes

effect

New serviceconfiguration takeseffect

General Handoff Direction Message/Universal Handoff Direction Message

(SCR_INCLUDED, SCR_new,NN-SCR_INCLUDED, NN-SCR_new)

Handoff Completion Message

18Figure 2.30.1-1 Reference Call Flow for Using GHDM/UHDM instead of SCM19

TSG-C42 Page 2-42

10/19/2001 C.S0031



a. Repeat one or more of the tests in section 2.27.2 with the following modifications: In5those steps where the base station is sending a Service Connect Message, instead6instruct the base station to send a General Handoff Direction Message, with both the7SCR and NN-SCR included in the message.8

b. Verify the following:9

1) The base station receives a Handoff Completion Message from the mobile10station, instead of a Service Connect Completion Message.11

2) When the new service configuration takes effect, verify user traffic (Ex.12Audio) on both directions.13

c. Repeat one or more of the tests in section 2.29.2 with the following modifications: In14those steps where the base station is sending a Service Connect Message, instead15instruct the base station to send a General Handoff Direction Message, with both the16SCR and NN-SCR included in the message.17


1) Verify the base station receives a Mobile Station Reject Order with ORDQ set to19‘00000111’.20

2) Verify that the base station does not receive a Handoff Completion Message from21the mobile station.22

e. Repeat steps a though d with the following modifications: Instead of sending a23General Handoff Direction Message, instruct the base station to send a Universal24Handoff Direction Message.25

f. Verify that all the outcomes are identical to the outcomes when the General Handoff26Direction Message was used.27

2.30.3 Minimum Standard28Usage of the Universal Handoff Direction Message and General Handoff Direction Message29instead of the Service Connect Message shall not change the outcome of service negotiation30procedures and the same service configuration shall take effect upon completion of service31negotiation procedures.32

2.31 SCR without NN-SCR and NN-SCR without SCR in General Handoff Direction33Message and Universal Handoff Direction Message34

2.31.1 Definition35Partial service configuration information (SCR alone or NN-SCR alone) shall be sent in the36General Handoff Direction Message and Universal Handoff Direction Message and the expected37service configuration takes effect.38

TSG-C42 Page 2-43

10/19/2001 C.S0031




b. Setup a mobile station originated call and establish a service configuration as7specified in 2.26.2. Verify user traffic (Ex. Audio) on both directions.8

c. Instruct the base station to send a General Handoff Direction Message to the mobile9station with a valid and acceptable SCR included (SCR_INCLUDED=1) and not10including a NN-SCR (NNSCR_INCLUDED=0) in the message.11

d. Once the new service configuration takes effect, verify the following:12

1) The part of the service configuration specified by the new SCR takes effect.13

2) The part of the service configuration specified by the NN-SCR remains14unchanged.15

3) Verify user traffic (Ex. Audio) on both directions.16

e. Instruct the base station to send a General Handoff Direction Message to the mobile17station with a valid and acceptable NN-SCR included (NNSCR_INCLUDED=1) and18not including a SCR (SCR_INCLUDED=0) in the message.19

f. Once the new service configuration takes effect, verify the following:20

1) The part of the service configuration specified by the new NN-SCR takes21effect.22

2) The part of the service configuration specified by the SCR remains23unchanged.24

2) Verify user traffic (Ex. Audio) on both directions.25

g. Repeat steps a through f with the following modifications: Instead of sending a26General Handoff Direction Message, instruct the base station to send a Universal27Handoff Direction Message.28

h. Verify that all the outcomes are identical to the case when the General Handoff29Direction Message was sent.30

2.31.3 Minimum Standard31Partial service configuration information (SCR alone or NN-SCR alone) can be sent in the32General Handoff Direction Message or Universal Handoff Direction Message. If the General33Handoff Direction Message or Universal Handoff Direction Message does not contain SCR,34SCR shall remain unchanged. If the General Handoff Direction Message or Universal Handoff35Direction Message does not contain NN-SCR, NN-SCR shall remain unchanged.36

TSG-C42 Page 2-44

10/19/2001 C.S0031

2.32 Base Station Request Overrides the Mobile Station Request1

2.32.1 Definition2This test verifies that when there is a race-condition between mobile station initiated service3negotiation and base station initiated service negotiation, the base station request overrides the4mobile station request.5




b. Setup a mobile station originated call12

c. Upon receiving an Origination Message, configure the base station to send an13Extended Channel Assignment Message to the mobile station, with the following14fields set as follows:15

16Field Value

ASSIGN_MODE ‘000’ (Traffic Channel Assignment or‘100’ (Enhanced Traffic ChannelAssignment )

GRANTED_MODE ‘00’ (MOBILE STATION is to use aninitial service configuration specifiedby the DEFAULT_CONFIG field andservice negotiation may take placebefore the base station sends the firstService Connect Message)

17

d. Upon establishing the traffic channel, instruct the mobile station to initiate service18negotiation. Verify that the mobile station sends a Service Request Message with19REQ_PURPOSE set to ‘0010’ to the base station to propose a new service20configuration.21

e. Instruct the base station to ignore this request and instead initiate a new service22negotiation session by sending a Service Request Message. Verify that the base23station sends a Service Request Message with REQ_PURPOSE set to ‘0010’.24

f. Verify that, upon receiving the Service Request Message, the mobile station25terminates the service negotiation that it initiated and instead takes part in the26service negotiation initiated by the base station, as follows:27

1) Verify that the mobile station sends a Service Response Message to the28base station to accept, reject, or counter-propose the service configuration.29

2) Verify that the mobile station does not send a Service Request Message to30the base station.31

TSG-C42 Page 2-45

10/19/2001 C.S0031

2.32.3 Minimum Standard1When there is a race-condition between mobile station initiated service negotiation and base2station initiated service negotiation, the base station request shall override the mobile station3request. The mobile station initiated service negotiation session shall terminate and the base4station initiated service negotiation session shall proceed normally.5

2.33 Service Negotiation Involving Partial SCR and/or Partial NN-SCR6

2.33.1 Definition7This test verifies that service negotiation can be carried out with only a partial SCR and/or partial8NN-SCR and the expected service configuration takes effect.9




b. Setup a call and establish a service configuration as specified in 2.26.2. Verify user16traffic (Ex. Audio) on both directions.17

c. Instruct the base station to initiate service negotiation to change only a subset of18service configuration parameters. Verify the following:19

1) The base station sends a Service Request Message with REQ_PURPOSE set to20‘0010’ to the mobile station to propose a new service configuration.21

2) The service configuration parameters not to be changed are not included in the22SCR (Ex. If DCCH related parameters are not to be changed, then23DCCH_CC_INCL should be set to ‘0’ and FOR_DCCH_RC, REV_DCCH_RC, and24DCCH_FRAME_SIZE will not be included).25

d. Instruct the mobile station to accept this service configuration. Verify that, upon26receiving the Service Request Message, the mobile station sends a Service Response27Message with RESP_PURPOSE set to ‘0000’.28

e. Instruct the base station to accept this service configuration and to send a NN-SCR29with only a subset of parameters modified. Verify that, upon receiving the Service30Response Message, the base station sends a Service Connect Message with an SCR31which contains only the parameters included in SCR sent by the base station (ex.32DCCH_CC_INCL=0) and an NN-SCR that only includes a subset of parameters.33


1) The base station receives a Service Connect Completion Message from the mobile35station.36

37

2) When the new service configuration takes effect, verify that for those service38configuration parameters not included in the final SCR (Ex. DCCH_CC_INCL=0)39

TSG-C42 Page 2-46

10/19/2001 C.S0031

and NN-SCR sent by the base station their previously in use value continues to1be in effect. Verify user traffic (Ex. Audio) on both directions.2

g. Repeat steps c through f for various combinations of subset of SCR and NN-SCR3parameters.4

2.33.3 Minimum Standard5Service negotiation can be carried out with only a partial SCR and/or partial NN-SCR and the6service configuration parameters which are not included in SCR or NN-SCR shall remain7unchanged when the new service configuration takes effect.8

2.34 Quasi-Orthogonal Functions (QOF) assignment9

2.34.1 Definition10This test will verify that the base station will assign Quasi-Orthogonal Functions from the11Extended Channel Assignment Message.12

Traceability: (See [4] )-2; 3.1.3.1.12, TIA/EIA/(See [4] ); 2.6.2.4, 2.6.3.3, 2.6.3.5, 3.6.3.3,133.6.3.5, 3.7.2.3.2.2114



b. Set up a mobile station originated call.17

c. Instruct the base station to accept the call and assign a traffic channel with RC3 on18both the forward and reverse link. Verify the base station sends the Extended19Channel Assignment Message with the following parameters set as shown in Table202.34.2-1.21

22

Table 2.34.2-1 ECAM Parameters23

Field Parameters Setting

ASSIGN_MODE ‘100’ (Enhanced Traffic ChannelAssignment)

CH_IND ‘01’ (Indicating FCH Assignment)

PILOT_REC_TYPE ‘000’ (Transmit Diversity Pilot)

QOF_MASK_ID_FCH ‘00’ through ‘11’ (QOF Masks)

FOR_RC ‘011’ (RC 3) through ‘101’ (RC 5)

REV_RC ‘011’(RC 3) through ‘101’ (RC 5)

24

25

d. Verify user data is present in both directions.26

e. End the call.27

f. Repeat steps b through d for various QOF assignments and radio configurations.28

TSG-C42 Page 2-47

10/19/2001 C.S0031

2.34.3 Minimum Standard1Each call in the test shall be successful. The Extended Channel Assignment Message shall2successfully configure QOF mask in the mobile station for the fundamental channel.3

2.35 Release Order on Access Channel4

2.35.1 Definition5This test verifies that the mobile station can send a Release Order on the Access Channel, and6that the base station acknowledges it. The Release Order is sent when the mobile station user hits7the END key while waiting for a call to connect, but has not been assigned a dedicated channel8yet.9

Traceability:10

11[4] 3.6.3 Access Channel Processing12[4] 3.6.3.4 Response to Orders13[4] 2.6.3 System Access State14[4] 2.6.3.1.4 System Access State Exit Procedures15[4] 2.6.3.5 Mobile Station Origination Attempt Substate16[3] 2.1.1.2.2.1 Overview of Transmission and Retransmission Procedures17


a. Connect the mobile station and base station in the simple configuration of figure192.1.2-1, and allow the mobile station to register and prepare for a normal call.20

b. Power up the mobile station and wait for registration to occur21

c. Configure the base station to not send a Channel Assignment Message or Extended22Channel Assignment Message, after receiving an Origination Message from a mobile23station.24

d. Attempt a mobile station originated call. After the mobile station has sent its25Origination Message and while it is waiting in the Mobile Station Origination26Attempt Substate, hit the END button, or otherwise cause the mobile station to27send a Release Order.28

2.35.3 Minimum Standard29After the Origination Message is sent but before a Channel Assignment Message or Extended30Channel Assignment Message is received, the mobile station shall send a Release Order on the31Access Channel. The base station shall acknowledge the message and shall not send a (Extended)32Channel Assignment Message.33

34

TSG-C42 Page 2-48

10/19/2001 C.S0031

No text1

TSG-C42 Page 3-1

10/19/2001 C.S0031

3 HANDOFF TESTS1Table 3-1 lists handoff tests.2

Table 3-1 Handoff Tests3

Test No. Title

3.1 Soft Handoff with Dynamic Threshold

3.2 Hard Handoff Between Frequencies in the Same Band Class

3.3 Hard Handoff from CDMA to AMPS

3.4 Soft Handoff in Fading

3.5 Hard Handoff in Fading

3.6 Hard Handoff Between Different Band Classes

3.7 Hard Handoff with and without Return on Failure

3.8 Search Window per Neighbor

3.9 Access Handoffs

3.10 Traffic Channel Preamble during Hard Handoff Between Frequencies in the SameBand Class

3.11 Hopping Pilot Beacon

3.12 Hard Handoff Between Frequencies with Different Radio Configurations

3.13 Handoff on Same Frequency with Different Radio Configurations

3.14 Hard Handoff while in the Waiting for Mobile Station Answer Substate

3.15 Inter-Frequency Hard Handoff (CDMA to CDMA)

3.16 Inter-Frequency Hard Handoff (CDMA to AMPS)

3.17 Hard Handoff Between Frequencies with Different Protocol Revisions

4

3.1 Soft Handoff with Dynamic Threshold5

3.1.1 Definition6This test verifies the mobile station and base station perform soft handoff. Soft handoff with and7without dynamic thresholds is verified. This test verifies both adding pilot to and dropping pilot8from the soft handoff Active Set.9

Traceability: (See [4] )10

2.6.2.2.5: Extended System Parameters Message112.6.4.1.4: Processing the In-Traffic System Parameters Message122.6.6.2.3: Handoff Drop Timer132.6.6.2.5.1: Processing of Forward Traffic Channel Handoff Messages142.6.6.2.5.2: Processing of Reverse Traffic Channel Handoff Messages152.6.6.2.6.2: Maintenance of the Candidate Set162.6.6.2.6.3: Maintenance of the Neighbor Set172.6.6.2.8.2.1: Restoring the Configuration182.6.6.3: Examples19

TSG-C42 Page 3-2

10/19/2001 C.S0031

2.7.2.3.2.5: Pilot Strength Measurement Message13.6.6.2.1.1: System Parameters23.7.2.3.2.13: Extended System Parameters Message33.7.3.3.2.7: In-Traffic System Parameters Message43.7.3.3.2.31: General Handoff Direction Message5


a. Setup test as shown in Figure 3.1.2-1.7• The Forward Channel from sector α of base station #1 has an arbitrary pilot PN8

offset index P1 and is called Channel 1.9• The Forward Channel from sector ß of base station #1 has an arbitrary pilot PN10

offset index P2 and is called Channel 2.11• The Forward Channel from base station #2 has an arbitrary pilot PN offset index12

P3 and is called Channel 3.13

b. Set the test parameters for Test 1 as specified in Table 3.1.2-1 and Table 3.1.2-2.14

c. Reverse link attenuation should be set to balance the forward and reverse links15(approximately 90 dB).16


e. Verify user data in both directions. Verify only Channel 1 is in the active set.18

f. Raise the level of Channel 2 in steps of 1 dB with a dwell time of five seconds after19each step until the mobile station has generated the Pilot Strength Measurement20Message. Record the level of Channel 2. Verify this occurs when Channel 2 Pilot21Ec/Io is approximately -11 dB and Îor2/Ioc is approximately 3 dB.22

g. Verify the following:23

• The base station sends an Extended Handoff Direction Message, General24Handoff Direction Message, or Universal Handoff Direction Message to the mobile25station.26

• Channel 1 and Channel 2 are in the active set at the action time of the27message.28

• The mobile station sends a Handoff Completion Message to the base29station.30

h. Set test parameters as specified in Table 3.1.2-3 while Channel 1 and Channel 2 are31in soft handoff. Raise the level of Channel 3 in steps of 1 dB with a dwell time of five32seconds after each step until the mobile station has generated the Pilot Strength33Measurement Message. Record the level of Channel 3. Verify this occurs when34Channel 3 Pilot Ec/Io is approximately –11 dB and Îor3/Ioc is approximately 6 dB.35

36

TSG-C42 Page 3-3

10/19/2001 C.S0031

1Figure 3.1.2-1 Functional Test Setup for Testing Soft Handoff with Dynamic Threshold2

3

Table 3.1.2-1 Soft Handoff with Dynamic Threshold Test Parameters - T_ADD, T_DROP,4T_TDROP, ADD_INTERCEPTs, DROP_INTERCEPTs, SOFT_SLOPEs5

Parameter Test 1 Test 2

SOFT_SLOPE ‘010000’ (2) ‘000000’ (0)

ADD_INTERCEPT ‘000110’ (3 dB) ‘000000’ (0 dB)

DROP_INTERCEPT ‘000010’ (1 dB) ‘000000’ (0 dB)

T_ADD ‘100000’ (-16 dB) ‘011100’ (-14 dB)

T_DROP ‘100100’ (-18 dB) ‘100000’ (-16 dB)

T_TDROP ‘0011’ (4s) ‘0011’ (4s)

6

TSG-C42 Page 3-4

10/19/2001 C.S0031

Table 3.1.2-2 Dynamic Add Test – One Pilot1

Parameter Unit Channel 1 Channel 2 Channel 3

Îor/Ioc dB 7 -20 -20


Traffic Ec/Ior dB -7 -7 -7

Ioc dBm/1.23MHz

-75

Pilot Ec/Io dB -5.8 -33 -33

2

Table 3.1.2-3 Dynamic Add Test – Two Pilots3


Îor/Ioc dB 7 7 -20




Pilot Ec/Io dB -8.4 -8.4 -35

4

i. Verify the following:5

• The base station sends an Extended Handoff Direction Message, General6Handoff Direction Message, or Universal Handoff Direction Message.7

• Channel 1, Channel 2, and Channel 3 are in the active set at the action8time of the message.9


Table 3.1.2-4 Dynamic Drop Test - Three Pilots12


Îor/Ioc dB 7 7 7




Pilot Ec/Io dB -10.1 -10.1 -10.1

13

j. Set the test parameters in Table 3.1.2-4 while Channel 1, Channel 2, and Channel 314are in soft handoff. Lower the level of Channel 3 in steps of 1 dB with a dwell time of1530 seconds until the mobile station has generated the Pilot Strength Measurement16

TSG-C42 Page 3-5

10/19/2001 C.S0031

Message. Record the level of Channel 3. Verify this occurs when channel 3 Pilot1Ec/Io is approximately -13.0 dB and Îor3/Ioc is approximately 4 dB.2

k. Verify the following:3

• The base station sends an Extended Handoff Direction Message, General4Handoff Direction Message, or Universal Handoff Direction Message.5



l. Set test parameters as specified in Table 3.1.2-5. Lower level of Channel 2 in steps10of 1 dB with a dwell time of 30 seconds after each step until the mobile station has11generated the Pilot Strength Measurement Message. Record the level of Channel 2.12Verify this occurs when channel 2 Pilot Ec/Io is approximately –13 dB and Îor2/Ioc13is approximately 0 dB.14

m. Verify the following:15

• Base station sends an Extended Handoff Direction Message, General Handoff16Direction Message, or Universal Handoff Direction Message.17

• Only Channel 1 is in the active set at the action time of the message.18

• Mobile station sends a Handoff Completion Message to the base station.19

Table 3.1.2-5 Dynamic Drop Test - Two Pilots20


Îor/Ioc dB 7 7 -20




Pilot Ec/Io dB -8.4 -8.4 -35

n. End call.21

o. Set the test parameters for Test 2 as specified in Table 3.1.2-1 and Table 3.1.2-2.22

p. Setup a mobile station originated call and Repeat steps e thru n. The expected23results should be identical to the results above except in steps f, h, j, & l the Pilot24Ec/Io level at which point the mobile station generates a Pilot Strength Measurement25Message will be per the requirements of “no dynamic thresholds”.26

q. Steps f through p can be repeated for various P_REV_IN_USE values. The expected27results should be identical to the results above with the following differences:28

• When P_REV_IN_USE is less than 4, test 1 (dynamic thresholds) is not29applicable.30

TSG-C42 Page 3-6

10/19/2001 C.S0031

• When P_REV_IN_USE is less than 6, in steps g, i, k, & m: Universal1Handoff Direction Message is not generated.2

3.1.3 Minimum Standard3The mobile station shall send an autonomous Pilot Strength Measurement Message as a message4requiring an acknowledgment and containing measurements consistent with the event whenever5any of the following events occur:6

• If P_REV_IN_USEs is greater than three and SOFT_SLOPEs is not equal to ‘000000’,7then in step f, the mobile station shall generate a Pilot Strength Measurement8Message when the level of channel 2 is at a level between –10 dB and –13 dB. The9base station shall generate a General Handoff Direction Message, Universal Handoff10Direction Message, or an Extended Handoff Direction Message to initiate soft handoff11with channel 2.12

In step h, the mobile station shall generate a Pilot Strength Measurement Message when13the level of channel 3 is at a level between –10 dB and –13 dB . The base station14shall generate a General Handoff Direction Message, Universal Handoff Direction15Message, or an Extended Handoff Direction Message to initiate soft handoff with16channel 3.17

In step j, the mobile station shall generate a Pilot Strength Measurement Message when18the level of channel 3 is at a level between –12 dB and –16 dB for a period of19T_TDROP.20

The base station shall generate a General Handoff Direction Message, Universal Handoff21Direction Message, or an Extended Handoff Direction Message to drop channel 322from the active set.23

In step l, the mobile station shall generate a Pilot Strength Measurement Message when24the level of channel 2 is at a level of –11 dB and –14 dB for a period of T_TDROP.25The base station shall generate a General Handoff Direction Message, Universal26Handoff Direction Message, or an Extended Handoff Direction Message to drop27channel 2 from the active set.28

• If P_REV_IN_USEs is less than or equal to three or SOFT_SLOPEs is equal to29‘000000’, then in step f, the mobile station shall generate a Pilot Strength30Measurement Message when the level of channel 2 is at a level between T_ADD and31T_ADD +2 dB. The base station shall generate a General Handoff Direction Message,32Universal Handoff Direction Message, or an Extended Handoff Direction Message to33initiate soft handoff with channel 2.34

In step h, the mobile station shall generate a Pilot Strength Measurement Message when35the level of channel 3 is at a level between T_ADD and T_ADD +2 dB. The base36station shall generate a General Handoff Direction Message, Universal Handoff37Direction Message, or an Extended Handoff Direction Message to initiate soft handoff38with channel 3.39

In step j, the mobile station shall generate a Pilot Strength Measurement Message when40the level of channel 3 is at a level between T_DROP and T_DROP –3 dB for a period41of T_TDROP. The base station shall generate a General Handoff Direction Message,42

TSG-C42 Page 3-7

10/19/2001 C.S0031

Universal Handoff Direction Message, or an Extended Handoff Direction Message to1drop channel 3 from the active set.2

In step l, the mobile station shall generate a Pilot Strength Measurement Message when3the level of channel 2 is at a level of T_DROP and T_DROP –3 dB for a period of4T_TDROP. The base station shall generate a General Handoff Direction Message,5Universal Handoff Direction Message, or an Extended Handoff Direction Message to6drop channel 2 from the active set.7

3.2 Hard Handoff Between Frequencies in the Same Band Class8

3.2.1 Definition9This test verifies the mobile station and base station perform hard handoff between different10CDMA channels in the same band class.11


2.6.6.1.1: Types of Handoff132.6.6.2.5: Handoff Messages142.6.6.2.8: CDMA-to-CDMA Hard Handoff153.6.6.1.1: Types of Handoff163.6.6.2.2: Call Processing During Handoff17


a. Setup test as shown in Figure 3.1.2-1.19

• The Forward Channel from base station #1 has an arbitrary pilot PN20offset index P1 and is called Channel 1.21

• Setup base station #2 to be on a different CDMA channel than base22station #1, but within the same band class. The Forward Channel from base station23#2 has an arbitrary pilot PN offset index P2 and is called Channel 2.24

• The AWGN source should be on the frequency of Channel 2. (It is25advisable to achieve the maximum possible difference in frequency separation26between Channel 1 and Channel 2).27

b. Set the test parameters as shown in Table 3.2.2-1.28

Table 3.2.2-1 Hard Handoff Test Parameters29


Îor/Ioc dBm N/A -5

Pilot Ec/Ior dB -7 -7

Traffic Ec/Ior dB -7 -7

Ioc dBm/1.23 MHz N/A -75

Pilot Ec/Io dB -7 -13.2

30

TSG-C42 Page 3-8

10/19/2001 C.S0031

c. Set reverse link attenuation to balance forward and reverse links (approximately 901dB).2

d. Setup a mobile station originated call on Channel 1.3


f. Instruct base station #1 to initiate handoff from Channel 1 to Channel 2. Verify base5station #1 sends a General Handoff Direction Message, Universal Handoff Direction6Message, or an Extended Handoff Direction Message with proper parameters (refer to7tables in Foreword) to initiate handoff from Channel 1 to Channel 2.8

g. Upon receiving a Extended Handoff Direction Message, General Handoff Direction9Message, or Universal Handoff Direction Message at the mobile station, verify the10following:11



h. Monitor calls and record the length of any audio dropouts present. Verify that any14audio dropouts present shall not exceed the limits specified in Table 3.2.3-1.15

i. This test can be repeated for the case where it is a hard handoff to soft handoff on16the same frequency with the following setup (see Figure 3.1.2-1: one base station17configured with two sectors active):18


• The Forward Channel from sector α of base station #2 has an arbitrary21pilot PN offset index P2 and is called Channel 2.22

• The Forward Channel from sector ß of base station #2 has an arbitrary23pilot PN offset index P3 and is called Channel 3.24

j. The expected results are as given for the previous test.25

3.2.3 Minimum Standard26The mobile station and base stations shall successfully execute the hard handoffs. Any audio27dropouts present shall not exceed the limits specified in Table 3.2.3-1.28

TSG-C42 Page 3-9

10/19/2001 C.S0031

Table 3.2.3-1 Limits of Audio Dropouts During Hard Handoff1

Handoff Type MaximumDuration (ms)

TypicalDuration (ms)

CDMA to AMPS 350 250

CDMA-CDMA, differentfrequency, same basestation

440 260

CDMA-CDMA, differentfrequency, different basestation

460 320

CDMA-CDMA, samefrequency

400 280

2

3.3 Hard Handoff from CDMA to AMPS3

3.3.1 Definition4This test verifies the mobile station and base station perform hard hand off from a CDMA system5to an AMPS system.6


2.6.6.1.1: Types of Handoff82.6.6.2.9: CDMA-to-Analog Handoff93.6.6.1.1: Types of Handoff103.6.6.2.2: Call Processing During Handoff11


a. Connect two base stations and an AWGN source to the mobile station as shown in13Figure 3.1.2-1. For the purpose of this test, Channel 1 is CDMA and Channel 2 is14AMPS.15

b. Set the test parameters as shown in Tables 3.3.2-1 and 3.3.2-2.16

Table 3.3.2-1 Hard Handoff to AMPS, CDMA Test Parameters17

CDMA Parameter Unit Channel 1

Îor/Ioc dB 0

Pilot Ec/Ior dB -7

Traffic Ec/Ior dB -7


18

TSG-C42 Page 3-10

10/19/2001 C.S0031

Table 3.3.2-2 Hard Handoff to AMPS, Analog Test Parameters1

Analog Parameter Unit Channel 2

Voice Channel dBm -73

Co-Channel Interference dB -18

2




f. Instruct the CDMA base station to initiate handoff to AMPS. Verify the CDMA base7station sends an Analog Handoff Direction Message with proper parameters (refer to8tables in Foreword) to initiate handoff to AMPS.9

g. Monitor calls and record the length of any audio dropouts present on handoff. Any10audio dropouts present shall not exceed the limits specified in Table 3.2.3-1.11

h. Verify the mobile station is no longer present in the CDMA system.12

3.3.3 Minimum Standard13The mobile station and base stations shall successfully execute the handoff transition. Any audio14dropouts present shall not exceed the limits specified in Table 3.4.3-1.15

3.4 Soft Handoff in Fading16

3.4.1 Definition17This test verifies soft handoff under various fading conditions:18

• 1 Ray Rayleigh fading at 30 km/hr19• 3 Ray Rayleigh fading at 100 km/hr20• 1 Ray Rayleigh fading at 3 km/hr21


2.6.6.1.1: Types of Handoff232.6.6.2.5: Handoff Messages242.6.6.2.7: Soft Handoff253.6.6.1.1: Types of Handoff263.6.6.2.2: Call Processing During Handoff273.6.6.2.4: Soft Handoff28





TSG-C42 Page 3-11

10/19/2001 C.S0031

1

Figure 3.4.2-1 Functional Setup for Testing Soft Handoff in Fading23

b. Set the test parameters as specified in Table 3.4.2-1.4

Table 3.4.2-1 Faded Soft Handoff Test Parameters - T_ADD5


Îor/Ioc dB 0 -10



Ioc dBm/1.23 MHz -75 -75

Pilot Ec/Io dB -10.2 -20.2


TSG-C42 Page 3-12

10/19/2001 C.S0031

d. Set both channel simulators to one Ray Rayleigh, 30 km/hr.1

e. Setup a mobile station originated call on Channel 1. Monitor two-way audio and2note anomalies throughout the test.3

f. Raise the level of Channel 2 in steps of 1 dB with a dwell time of 5 seconds after4each step until the mobile station has generated the Pilot Strength Measurement5Message. Verify the following:6

• Pilot Strength Measurement Message is generated when the channel 27Pilot Ec/Io is at a level above T_ADD.8

• Base station sends an Extended Handoff Direction Message, General9Handoff Direction Message, or Universal Handoff Direction Message to the mobile10station.11



g. Set the test parameters as specified in Table 3.4.2-2 without dropping the call.1516

Table 3.4.2-2 Soft Handoff Test Parameters - T_DROP17


Îor/Ioc dB 0 0



Ioc dBm/1.23 MHz -75 -75


18

h. Lower the level of Channel 1 in steps of 1 dB with a dwell time of 8 seconds after19each step until the mobile station has generated the Pilot Strength Measurement20Message. Verify the following:21

• Pilot Strength Measurement Message is generated when Channel 1 is at a22Pilot Ec/Io level below T_DROP for a period of TT_DROP.23




i. Set the levels as specified in Table 3.4.2-3.29

TSG-C42 Page 3-13

10/19/2001 C.S0031

Table 3.4.2-3 Soft Handoff Levels1


Îor/Ioc dB -10 0



Ioc dBm/1.23 MHz -75 -75


2

j. Raise the level of Channel 1 in steps of 1 dB with a dwell time of 5 seconds after3each step until the mobile station has generated the Pilot Strength Measurement4Message. Verify the following:5

• Pilot Strength Measurement Message is generated when the channel 16Pilot Ec/Io is at a level above T_ADD.7




k. Set the levels as specified in Table 3.4.2-4.14

l. Lower the level of Channel 2 in steps of 1 dB with a dwell time of 8 seconds after15each step until the mobile station has generated the Pilot Strength Measurement16Message. Verify the following:17

• Pilot Strength Measurement Message is generated when the Channel 2 is18at a Pilot Ec/Io level below T_DROP for a period of TT_DROP.19




m. Repeat steps a through l under 3 Ray Rayleigh fading at 100 km/hr fading condition25as specified in table 3.4.2-4.26

TSG-C42 Page 3-14

10/19/2001 C.S0031

Table 3.4.2-4 Soft Handoff Test Parameters - 100 km/hr1

Parameter Unit Value

Vehicle Speed km/hr 100

Number of Paths # 3

Path 2 Power(Relative to Path 1)

dB 0


dB -3

Delay from Path 1 to Input µs 0


Delay from Path 3 to Input µs 14.5

2

n. Repeat steps a through l under 1 Ray Rayleigh fading at 3 km/hr fading condition.3

3.4.3 Minimum Standard4The mobile station shall generate the Pilot Strength Measurement Message at the appropriate5time as specified in steps f, h, j, and l and the handoff shall be completed successfully.6

3.5 Hard Handoff in Fading7

3.5.1 Definition8This test verifies hard handoff under various fading conditions:9

• 1 Ray Rayleigh fading at 30 km/hr10



• Under various deployment scenarios:13- Between frequencies14- On the same frequency15



22

TSG-C42 Page 3-15

10/19/2001 C.S0031



• The Forward Channel from base station #1 on frequency F1, has an3arbitrary pilot PN offset index P1 and is called Channel 1.4

• The Forward Channel from base station #2 on frequency F2, has an5arbitrary pilot PN offset index P2 and is called Channel 2.6




Îor/Ioc dB 0 0



Ioc dBm/1.23 MHz -75 -75

Pilot Ec/Io dB -10 -10

10

c. Set reverse link attenuation to balance forward and reverse links (approx. 90 dB).11

d. Set the channel simulators for 1 Ray Rayleigh fading, 30 km/hr.12

e. Setup a mobile station originated call on Channel 1.13


g. Instruct base station #1 to initiate handoff from Channel 1 to Channel 2. Verify base15station #1 sends a General Handoff Direction Message, Universal Handoff Direction16Message, or an Extended Handoff Direction Message with proper parameters (refer to17tables in Foreword) to initiate handoff from base station #1 to base station #2.18Monitor calls and record the length of any audio dropouts present on handoff. Verify19that any audio dropouts shall not exceed the limits specified in Table 3.2.3-1.20

h. Upon receiving an Extended Handoff Direction Message, General Handoff Direction21Message, or Universal Handoff Direction Message at the mobile station, verify the22following:23



i. Repeat steps a through h, with the channel simulators set to 3 Ray Rayleigh at 10027km/hr in step d. Use the setup shown in Table 3.4.2-4. The expected results are as28given above for the previous test.29

TSG-C42 Page 3-16

10/19/2001 C.S0031

j Repeat steps a through h, with the channel simulators set to 1 Ray Rayleigh at 31km/hr in step d. The expected results are as given above for the previous test.2

k. Repeat steps c through j for the scenario where the hard handoff is performed3between two CDMA channels on the same frequency, with the setup test as shown4in Figure 3.8.2-1:5

• Forward Channel from base station #1 has an arbitrary pilot PN offset6index P1 and is called Channel 1.7

• Forward Channel from base station #2 has an arbitrary pilot PN offset8index P2 and is called Channel 2.9

• Test parameters set as shown in Table 3.5.2-2.1011



Îor/Ioc dB 0 0



Ioc dBm/1.23 MHz -75 -75


Note that in this case a hard handoff can be forced by excluding P1 from the active set.13

3.5.3 Minimum Standard14The mobile station and base stations shall successfully execute the hard handoff transitions. Any15audio dropouts present shall not exceed the limits specified in Table 3.4.3-1.16

3.6 Hard Handoff Between Different Band Classes17

3.6.1 Definition18This test verifies hard handoff between two different band classes.19





• The Forward Channel from the CDMA 800 base station #1 has an28arbitrary pilot PN offset index P1 and is called Channel 1.29

TSG-C42 Page 3-17

10/19/2001 C.S0031

• The Forward Channel from the CDMA 1900 base station #2 has an1arbitrary pilot PN offset index P2 and is called Channel 2.2

b. Set the test parameters as shown in Table 3.6.2-13

Table 3.6.2-1 Hard Handoff: CDMA 800 to CDMA 19004

Parameter Unit CDMA 800 CDMA 1900

Îor/Ioc dB -5 -5



Ioc dBm/1.23 MHz -75 -75


5


d. Setup a CDMA 800 call.7


f. Instruct the CDMA 800 base station to initiate handoff to the CDMA 1900 system.9Verify the base station sends a General Handoff Direction Message, Universal10Handoff Direction Message, or an Extended Handoff Direction Message with proper11parameters (refer to tables in Foreword) to initiate handoff. Monitor calls and record12the length of any audio dropouts present on handoff. Any audio dropouts present13should not exceed the limits specified in Table 3.2.3-1.14

g. Instruct the CDMA 1900 base station to initiate handoff to the CDMA 800 system.15Verify that the base station sends a General Handoff Direction Message, Universal16Handoff Direction Message, or an Extended Handoff Direction Message with proper17parameters (refer to tables in Foreword) to initiate handoff. Monitor calls and record18the length of any audio dropouts present on handoff. Any audio dropouts present19should not exceed the limits specified in Table 3.2.3-1.20

h. This test can be repeated for other handoffs between other band classes.21

3.6.3 Minimum Standard22The mobile station and base stations shall successfully execute the handoff. Any audio dropouts23present should not exceed the limits specified in Table 3.2.3-1.24

3.7 Hard Handoff with and without Return on Failure25

3.7.1 Definition26This test verifies the mobile station behavior when hard handoff fails and:27

• return on failure is allowed.28• return on failure is disallowed.29


2.6.4.2: Traffic Channel Initialization Substate31

TSG-C42 Page 3-18

10/19/2001 C.S0031

2.6.6.1.1: Types of Handoff12.6.6.2.5: Handoff Messages22.6.6.2.8.2: Hard Handoff With Return On Failure32.6.6.2.8.2.1: Restoring the Configuration43.6.6.1: Overview53.6.6.2.2: Call Processing During Handoff63.7.3.3.2.31: General Handoff Direction Message7


a. Setup test as shown in Figure 3.1.2-1. The Forward Channel from base station #19has an arbitrary pilot PN offset index P1 and is called Channel 1. The Forward10Channel from base station #2 has an arbitrary pilot PN offset index P2 and is called11Channel 2.12




Îor/Ioc dB -5 -5


Traffic Ec/Ior dB -7 <-20 (or none)

Ioc dBm/1.23 MHz -75 -75

Pilot Ec/Io dB -13.2 -12




f. Instruct the base station to initiate a handoff and allow for return on failure. Verify19that the base station sends a General Handoff Direction Message or a Universal20Handoff Direction Message with the following values:21

22RETURN_IF_HANDOFF_FAIL ‘1’

23

g. Instruct the mobile station to attempt the hard handoff, but not complete it, and24declare a hard handoff failure. Verify the following:25

• Mobile station restores the previous configuration26

• Mobile station returns to Channel 1.27

• Mobile station sends a Candidate Frequency Search Report Message to28the base station within T56m seconds.29

h. Repeat steps a through h with the difference that the base station disallows return30on failure. The results are as given above but with the following modifications:31

TSG-C42 Page 3-19

10/19/2001 C.S0031

• In step f, verify that the base station sends a General Handoff Direction1Message or a Universal Handoff Direction Message with the following values:2

3RETURN_IF_HANDOFF_FAIL ‘0’

• In step g, verify the mobile station does not restore the previous4configuration, does not return to Channel 1, but sends a Handoff Completion5Message within T73m.6

i. Steps d through i can be repeated for the case of hard handoff between different7band classes.8

3.7.3 Minimum Standard9When return on failure is allowed, the mobile station shall return to normal Channel 1 voice10operation within 1.2 seconds of receiving the message to hard handoff. The Candidate11Frequency Search Report Message shall indicate the hard handoff failed. When return on failure12is not allowed, the mobile station does not return to previous channel.13

3.8 Search Window Size and Offset Per Neighbor14

3.8.1 Definition15A CDMA call is established on sector α of sectored base station #1. Delay is applied to sector ß16and base station #2. The level of sector ß is raised sufficiently high to ensure intersector handoff17is possible. The level of base station #2 is raised sufficiently high to ensure soft handoff is18possible. The test is performed with three different settings of delay. The Pilot Strength19Measurements of base station #2 and sector ß are checked against the search window size and20search window offset settings for each of the Neighbor Pilots. If the delay is greater than the21search window size for the Neighbor Pilot then the mobile station shall not send a Pilot Strength22Measurement.23

3.8.1.1 Formulas24

Neighbor_Chip_Offset = PILOT_PN_PHASE mod 6425

Num_Chips = Set_Chip_Offset - Sim_Chip_Offset26

Chip_Delay (µs) =300m/υ0

244mxNum_chip27

PILOT_PN_PHASE is the pilot PN phase obtained from the mobile station log file in units of28chips. Set_Chip_Offset is the desired number of chip offsets for a particular test case.29Sim_Chip_Offset is the inherent delay for a pilot due to the time alignment/calibration of the30equipment. Chip_Delay is the actual delay in usec the tester should vary with the fader to31achieve the proper Set_Chip_Offset (this includes the inherent delay measured for32Sim_Chip_Offset.33


2.6.6: Handoff Procedures352.6.6.2.1: Pilot Search363.6.6: Handoff Procedures373.7.2.3.2.22: General Neighbor List Message38

TSG-C42 Page 3-20

10/19/2001 C.S0031

12



1) The Forward Channel from sector α of base station #1 has an arbitrary5pilot PN offset index P1 and is called Channel 1.6

2) The Forward Channel from sector ß of base station #1 has an arbitrary7pilot PN offset index P2 and is called Channel 2.8

3) The Forward Channel from base station #2 has an arbitrary pilot PN9offset index P3 and is called Channel 3.10


c. The Reverse Link attenuation should be set to balance the forward and reverse links12(approximately 90 dB).13

14

15

Figure 3.8.2-1 Functional Setup for Testing Search Window per Neighbor16

TSG-C42 Page 3-21

10/19/2001 C.S0031

1

Table 3.8.2-1 Test Parameters for Search Window per Neighbor2


Îor/Ioc dB 0 -20 -20



Ioc dBm/1.23 MHz -75 -75 -75

Pilot Ec/Io dB -10 -30 -30

Note: The Pilot Ec/I0 value is calculated from the parameters set in the table. It is not a3settable parameter itself.4

d. Set the following values in the General Neighbor List Message:56

NGHBR_CONFIG_PN_INCL 1

NGHBR_SRCH_MODE 10

SRCH_OFFSET_INCL 1

7Neighbor Setting for P2

NGHBR_PN P2

SRCH_WIN_NGHBR 7 (40 chips)

SRCH_OFFSET_NGHBR 0 (no offset)


NGHBR_PN P3



9

e. Determine the inherent delay of the channel simulator as follows:.10

1) Set the delay on Channel 2 and on Channel 3 to 0.0 µs.11

2) Setup a CDMA originated call.12

3) Verify user data in both directions.13

4) Generate a Pilot Strength Measurement Message by raising the level of14Channel 2 to Îor/Ioc = +1 dB without dropping the call.15

161718

TSG-C42 Page 3-22

10/19/2001 C.S0031

5) Use the PILOT_PN_PHASE of the pilot PN offset index P2 recorded in the1Pilot Strength Measurement Message to calculate the Neighbor_Chip_OffsetP2.2Sim_Chip_OffsetP2 is equal to the same value of Neighbor_Chip_OffsetP2.3Sim_Chip_Offset represents the inherent delay produced by the channel simulator4and will be used to calculate the delay setting for the remainder of the test case.5

6) Generate a Pilot Strength Measurement Message by raising the level of6Channel 3 to Îor/Ioc = +1 dB without dropping the call.7

7) Use the PILOT_PN_PHASE of the pilot PN offset index P3 recorded in the8Pilot Strength Measurement Message to calculate the Neighbor_Chip_OffsetP3.9Sim_Chip_OffsetP3 is equal to the value of Neighbor_Chip_OffsetP3.10Sim_Chip_Offset represents the inherent delay produced by the channel simulator11and will be used to calculate the delay setting for the remainder of the test case.12

8) Example, given:13

SRCH_WIN_NGHBR = 9 [80 chips] PILOT_PN_PHASE = 205214

Set_Chip_Offset = (SRCH_WIN_NGHBR)/4 = 20 chips15

Therefore:16

Neighbor_Chip_Offset = 417

Sim_Chip_Offset = Neighbor_Chip_Offset = 418

Num_Chips = Set_Chip_Offset - Sim_Chip_Offset = 1619

Chip_Delay = (Num_Chips x 244m)/(300 m/µs) = 13.01 µs20

f. Set the delay on both Channel 2 and on Channel 3 to the Chip_Delay with21

Set_Chip_Offset =(SRCH_WIN_NGHBR of P3)/4 + SRCH_OFFSET_NGHBR of P3.22

g. Reset the test parameters as specified in Table 3.8.2-1.23

h. Setup a mobile station originated call.24

i. Verify user data in both directions.25

j. Generate a Pilot Strength Measurement Message by raising the level of Channel 2 to26Îor/Ioc = +1 dB without dropping the call.27

k. Use the PILOT_PN_PHASE of the pilot PN offset index P2 recorded in the Pilot28

Strength Measurement Message to calculate the Neighbor_Chip_Offset of P2.29

l. Generate a Pilot Strength Measurement Message by raising the level of Channel 3 to30Îor/Ioc = +1 dB without dropping the call.31

m. End the call.32

n. Use the PILOT_PN_PHASE of the pilot PN offset index P3 recorded in the Pilot33

Strength Measurement Message to calculate the Neighbor_Chip_Offset of P3.34

TSG-C42 Page 3-23

10/19/2001 C.S0031

o. Set the delay on Channel 2 and on Channel 3 to Chip_Delay of P3 with1

Set_Chip_Offset = (SRCH_WIN_NGHBR of P3)/2 + SRCH_OFFSET_NGHBR of P3.2

p. Repeat steps g through n.3

q. Set the delay on Channel 2 and on Channel 3 to Chip_Delay of P3 with4

Set_Chip_Offset = (SRCH_WIN_NGHBR of P3)/2 + SRCH_OFFSET_NGHBR of P3 +510 chips.6

r. Repeat steps g through n.7

s. Set the following values in the General Neighbor List Message:89

NGHBR_CONFIG_PN_INCL 1

NGHBR_SRCH_MODE 10

SRCH_OFFSET_INCL 1


NGHBR_PN P2




NGHBR_PN P3


SRCH_OFFSET_NGHBR 1 (window_size/2)

12

t. Set the delay on both Channel 2 and on Channel 3 to the Chip_Delay with13

Set_Chip_Offset =(SRCH_WIN_NGHBR of P3)/2 + SRCH_OFFSET_NGHBR of P3.14

u. Repeat steps g through n.15

v. Set the following values in the General Neighbor List Message:16

17NGHBR_CONFIG_PN_INCL 1

NGHBR_SRCH_MODE 10

SRCH_OFFSET_INCL 1

18

TSG-C42 Page 3-24

10/19/2001 C.S0031

Neighbor Setting for P2

NGHBR_PN P2




NGHBR_PN P3


SRCH_OFFSET_NGHBR 4 (-window_size/2)

2

w. Set the delay on both Channel 2 and on Channel 3 to the Chip_Delay with3

Set_Chip_Offset =(SRCH_WIN_NGHBR of P3)/2.4

x. Repeat steps g through n.5


a. For the delay setup in step f, the mobile station shall generate a Pilot Strength7Measurement Message when the channel 2 Pilot is added. The base station shall8generate a General Handoff Direction Message to initiate soft handoff. The9Neighbor_Chip_Offset of P2 shall equal the Set_Chip_Offset of P2. The mobile station10shall generate a Pilot Strength Measurement Message when the channel 3 Pilot is11added. The base station shall generate a General Handoff Direction Message to12initiate soft handoff. The Neighbor_Chip_Offset of P3 shall equal the Set_Chip_Offset13of P3.14

b. For the delay setup in step o, the mobile station shall not generate a Pilot Strength15Measurement Message when the channel 2 Pilot is added. The mobile station shall16generate a Pilot Strength Measurement Message when the channel 3 Pilot is added.17The base station shall generate a General Handoff Direction Message to initiate soft18handoff. The Neighbor_Chip_Offset of P3 shall equal the Set_Chip_Offset of P3.19

c. For the delay setup in step q, the mobile station shall not generate a Pilot Strength20Measurement Message when the channel 2 and channel 3 Pilots are added.21

d. For the delay setup in step t, the mobile station shall not generate a Pilot Strength22Measurement Message when the channel 2 Pilot is added. The mobile station shall23generate a Pilot Strength Measurement Message when the channel 3 Pilot is added.24The base station shall generate a General Handoff Direction Message to initiate soft25handoff. The Neighbor_Chip_Offset of P3 shall equal the Set_Chip_Offset of P3.26

e. For the delay setup in step t, the mobile station shall generate a Pilot Strength27Measurement Message when the channel 2 Pilot is added. The base station shall28generate a General Handoff Direction Message to initiate soft handoff. The29Neighbor_Chip_Offset of P2 shall equal the Set_Chip_Offset of P2. The mobile station30

TSG-C42 Page 3-25

10/19/2001 C.S0031

shall not generate a Pilot Strength Measurement Message when the channel 3 Pilot is1added.2

3.9 Access Handoffs3There are 3 types of Access Handoffs. ‘Access Entry Handoff’ may occur after receiving a4General Page but before the mobile station has sent any access probes in response. ‘Access5Probe’ handoff may occur during an access probe transmission. ‘Access Handoff’ may occur6after an initial mobile station access attempt, but before a Channel Assignment Message or an7Extended Channel Assignment Message is sent. These features are intended to save a call in any8of its brief vulnerable intervals during origination, where some access failures occur.9

3.9.1 Access Entry Handoff10

3.9.1.1 Definition11A mobile station is permitted to perform an ‘Access Entry Handoff’ to a neighboring base station12after receiving a General Page directed to it, but before transmitting any access probes.13

Traceability:14

[4] 2.6.2.1.4 Idle Handoff15[4] 2.6.2.3 Mobile Station Page Match Operation16[4] 2.6.3 System Access State17[4]2.6.6 Handoff Procedures18[4] 3.6.6 Handoff Procedures19

3.9.1.2 Method of Measurement20This interoperability test can be difficult to perform due to timing constraints required to21simulate the real world condition of sudden pilot loss directly after receipt of a call page. The22transition of base station powers must be synchronized to the sending of the General Page. The23mobile station determines that it should perform an idle handoff after it has declared a page24match.25

a. Connect the mobile station to the base station as shown in figure 3.9.2.2-1. Setup26the test parameters as shown in table 3.9.4.2-1.27

• Base station #1 has a PN offset of P1 and frequency of ƒ1.28


b. Configure base stations one and two to allow Access Entry Handoffs using the30following parameters in the Extended System Parameter Message:31

32

TSG-C42 Page 3-26

10/19/2001 C.S0031

Field Value

NGHBR_SET_ENTRY_INFO '1'

ACC_ENT_HO_ORDER '1'

NGHBR_SET_ACCESS_INFO '0'

NGHBR_SET_SIZE Number of pilots included in theNeighbor List Message, ExtendedNeighbor List Message, or GeneralNeighbor List Message

ACCESS_ENTRY_HO

(Set per neighbor)

'1'

1

c. Ensure the mobile station is operating in the Mobile Station Idle State on base2station #1 and allow sufficient idle time so that the mobile station meets the3conditions defined in [4] 2.6.2.3, regarding stored message sequences.4

d. Page the mobile station.5

e. After the mobile station receives the General Page from base station #1, increase6attenuation for base station #1 to cause the mobile station to transmit access7probes on base station #2 after an Access Entry Handoff.8

f. Verify the call completes.9

3.9.1.3 Minimum Standard10The mobile shall receive a General Page from base station #1, and transmit its first access11probes to base station #2. The call shall complete on base station #2.12

3.9.2 Access Probe Handoff13

3.9.2.1 Definition14A call is initiated by the mobile station currently on base station #1. The reverse link of base15station #1 is disabled to cause the mobile station to send multiple probes on the access channel.16While the mobile station is sending access probes, the level of base station #2 is raised17sufficiently high to ensure idle handoff is possible. The mobile station performs an idle handoff18to base station #2 while in the access sub-state. All other forms of access handoff are disabled at19the base station.20


2.6.3.1.3.3: Access Probe Handoff222.6.3.3: Page Response Substate232.6.3.5: Mobile Station Origination Attempt Substate242.6.6: Handoff Procedures253.6.6: Handoff Procedures26


a. Setup test as shown in Figure 3.9.2.2-1.28

TSG-C42 Page 3-27

10/19/2001 C.S0031

• The Forward Channel from base station #1 has an arbitrary pilot PN1offset index P

1called Channel 1.2

• The Forward Channel from base station #2 has an arbitrary pilot PN3offset index P

2called Channel 2.4

b. Set the test parameters as specified in Table 3.9.2.2-1.5

c. Reverse link attenuation should be set to balance the forward and reverse links6(approximately 90 dB). Disable the Reverse link of Channel 1.7

d. Include the pilot PN of Channel 2 in the Neighbor List Message, Extended Neighbor8List Message, and/or General Neighbor List Message of Channel 1.9

10

11

Figure 3.9.2.2-1 Functional Setup for Testing Access Probe Handoffs1213

TSG-C42 Page 3-28

10/19/2001 C.S0031

Table 3.9.2.2-1 Access Probe Handoff Test Parameters1


Îor/Ioc dB 0 -20 for S1+10 for S2



Ioc dBm/1.23 MHz -75 -75

Pilot Ec/Io dB -10 for S1-17.8 for S2

-30 for S1-7.8 for S2

Note: S1 and S2 indicate the two states of the power levels.23

e. Setup the following values in the Extended System Parameters Message of Channel41:5

6NGHBR_SET_ENTRY_INFO = 0 ACCESS_HO_MSG_RSP = 0

ACC_ENT_HO_ORDER = 0 ACCESS_PROBE_HO = 1

NGHBR_SET_ACCESS_INFO = 1 MAX_NUM_PROBE_HO = 0

ACCESS_HO = 0 N/A

ACCESS_ENTRY_HO = 0(Set per Neighbor)

ACCESS_HO_ALLOWED = 1(Set per Neighbor)

7

f. Set following values in the Access Parameters Message for Channel 1 and Channel82:9

10NUM_STEP = 7 PWR_STEP = 1

INIT_PWR = 0 NOM_PWR = 0

MAX_REQ_SEQ = 2 PROBE_BKOFF = 1

BKOFF = 1 N/A

11



i. Immediately raise the level of Channel 2 to Îor/Ioc = +10 dB to cause a loss of14paging channel on Channel 1 to ensure an idle handoff can be triggered.15

3.9.2.3 Minimum Standard16

a. The mobile station shall update the overhead messages and send an Origination17Message on Channel 1.18

TSG-C42 Page 3-29

10/19/2001 C.S0031

b. While in the Mobile Station Origination Attempt Substate, the mobile station shall1update the overhead messages to that of Channel 2 then send access probes on2Channel 2 using the appropriate coding for base station #2.3

c. The call shall be completed on Channel 2.4

3.9.3 Access Handoff5

3.9.3.1 Definition6The mobile station is permitted to perform an ‘Access Handoff’ when waiting for a response7from the base station or before sending a response to the base station. An access handoff is8permitted after an access attempt while the mobile station is in the Page Response Substate or the9Mobile Station Origination Attempt Substate.10

Traceability:11

(6) 3.2.3.2 Access Handoff Test12[4] 2.6.3.1.3.2 Access Handoff13[4] 2.6.3.3 Page Response Substate14[4] 2.6.3.5 Mobile Station Origination Attempt Substate15[4] 2.6.6 Handoff Procedures16[4] 3.6.6 Handoff Procedures17

3.9.3.2 Method of Measurement18This interoperability test can be difficult to perform due to the timing constraints required to19simulate real world condition of sudden pilot loss, or a network delay. However, if the base20station can be configured to hold off sending a Channel Assignment Message or an Extended21Channel Assignment for some time, the tester can transition the base station powers and induce22the Access Handoff. .23

a. Connect the mobile station to the base station as shown in figure 3.9.2.2-1. Setup24the test parameters as shown in table 3.9.4.2-1.25



b. Configure base stations one and two to allow Access Handoffs by using the following28parameters in the Extended System Parameters Message:29

30

TSG-C42 Page 3-30

10/19/2001 C.S0031

Field Value

NGHBR_SET_ENTRY_INFO '0'

NGHBR_SET_ACCESS_INFO '1'

ACCESS_HO '1'

ACCESS_HO_MSG_RSP '1'

ACCESS_PROBE_HO '0'

NGHBR_SET_SIZE Number of pilots included in the NeighborList Message, Extended Neighbor ListMessage, or General Neighbor ListMessage

ACCESS_HO_ALLOWED

(Set per neighbor)

'1'

1

c. Ensure the mobile station is operating in the Mobile Station Idle State on base2station #1.3

d. Attempt a mobile station originated call on base station #1.4

e. Before base station #1 sends a Channel Assignment Message or an Extended5Channel Assignment Message, increase the attenuation on base station #1 to cause6an Access Handoff to base station #2.7

f. Verify the mobile station receives a Channel Assignment Message or an Extended8Channel Assignment Message from base station #2.9

g. Verify the call completes and user traffic is present (i.e. audio)10

3.9.3.3 Minimum Standard11The mobile station shall perform ‘Access Handoff’, receive a Channel Assignment Message or12an Extended Channel Assignment Message on base station #2, and complete the call.13

3.9.4 Channel Assignment into Soft Handoff14

3.9.4.1 Definition15The levels of base station #1 and base station #2 are above T_ADD. A call is initiated on either16base station by the mobile station. The mobile station is assigned channels on base station #1 and17base station #2 in the Extended Channel Assignment Message. All other forms of access handoff18are disabled at the base station.19


2.6.3.1.3.2: Access Handoff212.6.3.3: Page Response Substate222.6.3.5: Mobile Station Origination Attempt Substate232.6.6: Handoff Procedures243.6.6: Handoff Procedures25

TSG-C42 Page 3-31

10/19/2001 C.S0031


a. Setup test as shown in Figure 3.9.2.2-1.2• The Forward Channel from base station #1 has an arbitrary pilot PN offset index3

P1 and is called Channel 1.4


b. Set the test parameters as specified in Table 3.9.4.2-1.7

Table 3.9.4.2-1 Channel Assignment into Soft Handoff Test Parameters8


Îor/Ioc dB +5 +2



Ioc dBm/1.23 MHz -75 -75


Note: Pilot Ec/I0 value is calculated from parameters set in the table. It is not a settable9parameter itself.10


d. Setup the following values in the Extended System Parameters Message for Channel131 and Channel 2.14

15NGHBR_SET_ENTRY_INFO = 0 ACCESS_HO_MSG_RSP = 0

ACC_ENT_HO_ORDER = 0 ACCESS_PROBE_HO = 0

NGHBR_SET_ACCESS_INFO = 1 MAX_NUM_PROBE_HO = 0

ACCESS_HO = 0 PILOT_REPORT = 1

ACCESS_ENTRY_HO = 0

(Set per Neighbor)

ACCESS_HO_ALLOWED = 1

(Set per Neighbor)

16



3.9.4.3 Minimum Standard19The mobile station shall update the overhead messages of the channel it is monitoring prior to20sending the Origination Message. Verify that pilot strength for the channel not used for21origination, is reported above T_ADD in the Origination Message. Verify the base station sends22the Extended Channel Assignment Message assigning both Channel 1 and Channel 2 as Active23Set pilots, with associated traffic channel resources. The mobile station shall complete service24negotiation while in soft handoff on Channel 1 and Channel 2.25

TSG-C42 Page 3-32

10/19/2001 C.S0031

3.10 Traffic Channel Preamble during Hard Handoff Between Frequencies in same band1

3.10.1 Definition2The mobile station is transitioned between base stations with different CDMA frequency3(channel) assignments in the same band class. The Traffic Channel Preamble is a sequence of all-4zero frames that is sent by the mobile station on the Reverse Traffic Channel as an aid to Traffic5Channel acquisition.6



(See [4] );13

2.1.3.2.4: Reverse Pilot Channel Operation during RTC Preamble142.1.3.6.2.3: Reverse Traffic Channel Preamble15





• The AWGN source should be on the frequency of Channel 2. (It is22advisable to achieve the maximum possible difference in frequency separation23between Channel 1 and Channel 2)24




Îor/Ioc dBm N/A -5






d. Configure base station #1 and base station #2 for RC1 or RC2.28



TSG-C42 Page 3-33

10/19/2001 C.S0031

g. Send from base station #1 a General Handoff Direction Message, Universal Handoff1Direction Message, or an Extended Handoff Direction Message with NUM_PREAMBLE2= 0 and proper parameters (refer to tables in Foreword) to initiate handoff from3Channel 1 to Channel 2. Monitor calls and record the length of any audio dropouts4present on handoff.5

h. Verify the correct NUM_PREAMBLE value in the General Handoff Direction Message,6Universal Handoff Direction Message, or Extended Handoff Direction Message. Verify7the Reverse Traffic Channel preamble length.8

i. Wait 20 seconds then send from base station #2 a General Handoff Direction9Message, Universal Handoff Direction Message, or an Extended Handoff Direction10Message with NUM_PREAMBLE = 4 and the proper parameters (refer to tables in11Foreword) to initiate handoff from Channel 2 to Channel 1.12

j. Verify the correct NUM_PREAMBLE value in the General Handoff Direction Message,13Universal Handoff Direction Message, or Extended Handoff Direction Message. Verify14the Reverse Traffic Channel preamble length.15

k. Configure base station #1 and base station #2 for RC3 or RC5.16

l. Repeat steps e through j.17

3.10.3 Minimum Standard18• The mobile station and base stations shall successfully execute the handoffs. Any audio19

dropouts present shall not exceed the limits specified in Table 3.2.3-1.20• Verify the correct NUM_PREAMBLE value in the General Handoff Direction Message,21

Universal Handoff Direction Message, or Extended Handoff Direction Message.22• Verify the Reverse Traffic Channel preamble length as follows:23

24

Table 3.10.3-1 Reverse Traffic Channel Preamble Length25

NUM_PREAMBLE RC1, RC2Preamble Length in 20 msIncrements:(Total Time)

RC>2Preamble Length in 1.25 ms

Increments:(Total Time)

0 0 (0 ms) 0 (0 ms)

4 4 (80 ms) 8 (10 ms)

26

3.11 Hopping Pilot Beacon27

3.11.1 Definition28The mobile station is transitioned between base stations with different CDMA frequency29(channel) assignments in the same band class.30The Hopping Pilot Beacon is a pilot beacon that changes CDMA Frequency periodically to31simulate multiple base stations operating on different frequencies. The transmission of the32hopping pilot beacon is discontinuous on any CDMA Channel.33

TSG-C42 Page 3-34

10/19/2001 C.S0031


2.6.6.1.1: Types of Handoff22.6.6.2.5: Handoff Messages32.6.6.2.8: CDMA-to-CDMA Hard Handoff42.7.4.25: Capability Information53.6.1.2: Pilot Channel Operation63.6.6.1.1: Types of Handoff73.6.6.2.2: Call Processing During Handoff83.7.2.3.2.22: General Neighbor List Message93.7.2.3.2.26: Sync Channel Message10(See [1] );11

3.1.3.2.5: Hopping Pilot Beacon12


a. Configure base station for hopping pilot beacon.14

b. Setup test as shown in Figure 3.1.2-1.15




c. Set the test parameters as shown in Table 3.11.2-1.2324



Îor/Ioc dBm N/A -5





26

d. Set reverse link attenuation to balance forward and reverse links (approx. 90 dB).27



g. Verify hopping pilot beacon settings in the General Neighbor List Message or30Extended Neighbor List Message. Send from base station #1 a General Handoff31Direction Message, Universal Handoff Direction Message, or an Extended Handoff32

TSG-C42 Page 3-35

10/19/2001 C.S0031

Direction Message with proper parameters (refer to tables in Foreword) to initiate1handoff from Channel 1 to Channel 2.2

h. Monitor calls and record the length of any audio dropouts present on handoff.3

i. Verify hopping pilot beacon settings in the General Neighbor List Message or4Extended Neighbor List Message. Wait 20 seconds then send from base station #2 a5General Handoff Direction Message, Universal Handoff Direction Message, or an6Extended Handoff Direction Message with the proper parameters (refer to tables in7Foreword) to initiate handoff from Channel 2 to Channel 1.8

3.11.3 Minimum Standard9• The mobile station and base stations shall successfully execute the handoffs. Any audio10

dropouts present shall not exceed the limits specified in Table 3.2.3-1.11• Verify hopping pilot beacon settings in the General Neighbor List Message or Extended12

Neighbor List Message.13

3.12 Hard Handoff Between Frequencies with Different Radio Configurations14

3.12.1 Definition15The mobile station is transitioned between base stations with different CDMA frequency16(channel) assignments in the same band class and different radio configurations.17



(See [1] );24

2.1.3.1: Reverse CDMA Channel Signals253.1.3.1: Forward CDMA Channel Signals26


a. Configure base station #1 for RC3 or RC5. Configure base station #2 for RC1 or RC228.29






TSG-C42 Page 3-36

10/19/2001 C.S0031



Îor/Ioc dBm N/A -5





2




g. Send from base station #1 a General Handoff Direction Message, or Universal6Handoff Direction Message with proper parameters (refer to tables in Foreword) to7initiate handoff from Channel 1 to Channel 2. Monitor calls and record the length of8any audio dropouts present on handoff.9

h. Wait 20 seconds then send from base station #2 a General Handoff Direction10Message, or Universal Handoff Direction Message with the proper parameters (refer11to tables in Foreword) to initiate handoff from Channel 2 to Channel 1.12

i. Configure base station #1 for RC1 or RC2. Configure base station #2 for RC3 or RC513and repeat steps b through h.14

j. Configure base station #1 for RC3. Configure base station #2 for RC4 and repeat15steps b through h.16

3.12.3 Minimum Standard17The mobile station and base stations shall successfully execute the handoffs. Any audio dropouts18present shall not exceed the limits specified in Table 3.2.3-1.19

3.13 Handoff on Same Frequency with Different Radio Configurations20

3.13.1 Definition21The mobile station is transitioned between base stations with the same CDMA frequency22(channel) assignments in the same band class and different radio configurations.23When the active set membership before and after the handoff are disjoint, the handoff is24performed as a hard handoff; when the active set membership before and after handoff is not25disjoint except for the value of the radio configuration, the handoff is performed as a soft26handoff.27


2.6.6.1.1: Types of Handoff292.6.6.2.5: Handoff Messages302.6.6.2.8: CDMA-to-CDMA Hard Handoff31

TSG-C42 Page 3-37

10/19/2001 C.S0031

3.6.6.1.1: Types of Handoff13.6.6.2.2: Call Processing During Handoff2

(See [1] );3

2.1.3.1: Reverse CDMA Channel Signals43.1.3.1: Forward CDMA Channel Signals5


a. Configure base station #1 for RC4 or RC5. Configure base station #2 for RC1 or7RC2.8




• The AWGN source should be added to both Channels.14




Îor/Ioc dBm N/A -5





18




g. Send from base station #1 a General Handoff Direction Message, or Universal22Handoff Direction Message with proper parameters (refer to tables in Foreword) to23initiate handoff from Channel 1 to Channel 2. Monitor calls and record the length of24any audio dropouts present on handoff.25

h. Wait 20 seconds then send from base station #2 a General Handoff Direction26Message, or Universal Handoff Direction Message with the proper parameters (refer27to tables in Foreword) to initiate handoff from Channel 2 to Channel 1.28

i. Configure base station #1 for RC1 or RC2. Configure base station #2 for RC4 or RC529and repeat steps b through h.30

TSG-C42 Page 3-38

10/19/2001 C.S0031

j. Configure base station #1 for RC3. Configure base station #2 for RC4 and repeat1steps b through h.2

k. Repeat steps a through j but with the following exception: Only base station 1 is used3for this test. The handoff messages are sent from base station 1 without changing the4active set, but changing the radio configuration. Thus the handoff messages simply5assign a new radio configuration from the same base station.6

l. Verify that the handoff is performed as a soft handoff.7

8

3.13.3 Minimum Standard9The mobile station and base stations shall successfully execute the handoffs. Any audio dropouts10present shall not exceed the limits specified in Table 3.2.3-1.11

3.14 Hard Handoff while in the Waiting for Mobile Station Answer Substate12

3.14.1 Definition13This test verifies that if a hard handoff occurs while the mobile station is in the Waiting for14Mobile Station Answer Substate, the hard handoff will be completed successfully and the mobile15station shall enter the Conversation Substate on the new channel.16

Traceabilities (see [4] unless otherwise noted)17

2.6.4 Mobile Station Control on the Traffic Channel State182.6.4.3.2 Waiting for Mobile Station Answer Substate192.6.4.4 Conversation Substate202.6.6.2.5.1 Processing of the Forward Traffic Channel Handoff Messages212.6.6.2.8 CDMA to CDMA Hard Handoff223.6.4.3.1 Waiting for Order Substate233.6.6.2.2 Call Processing during Handoff243.7.3.3.2.17 Extended Handoff Direction Message253.7.3.3.2.31 General Handoff Direction Message263.7.3.3.2.36 Universal Handoff Direction Message27Table D-1 Time Constants283.1 Standard Service Option Number Assignments (see [17])293.2 Proprietary Service Option Number Assignments (see [17])30


a. Connect the mobile station to the base station as shown in figure 3.1.2-1 and set32the test parameters as specified in table 3.2.2-133

• Base station #1 is a CDMA base station with frequency ƒ1, PN offset P134and is referred to as Channel 1.35

• Base station #2 is a CDMA base station with frequency ƒ2, PN offset P236and is referred to as Channel 2.37

b. Ensure the mobile station is operating in the Mobile Station Idle State on Channel 1.38

c. Page the mobile station with a supported service option.39

TSG-C42 Page 3-39

10/19/2001 C.S0031

d. After receiving the Page Response Message, instruct the base station to send an1Extended Channel Assignment Message with the following parameters:2

3Field Value


BYPASS_ALERT_ANSWER '0'

4

e. While the mobile station is in the Waiting for Mobile Station Answer Substate (i.e.5ringing), instruct the base station to send an Extended Handoff Direction Message,6General Handoff Direction Message, or Universal Handoff Direction Message directing7the mobile station to Channel 2.8

f. After the hard handoff has been completed and before T53m (65 seconds), has9expired direct the user to answer the call.10

g. Verify the mobile station enters the Conversation Substate and user traffic is11present in both directions (i.e. audio).12

h. End the call.13

i. Repeat steps b through h using different service options and radio configurations14supported by the mobile station and base station.15

j. Repeat steps b through i, changing Channel 2 to a band class that is different from16Channel 1 but is supported by the mobile station.17

3.14.3 Minimum Standard18The hard handoff shall be completed while the mobile station is in the Waiting for Mobile19Station Answer Substate. After the handoff is completed, the mobile station shall enter the20Conversation Substate on the new channel and user traffic in both directions shall be present.21

3.15 Inter-Frequency Hard Handoff (CDMA to CDMA)22

3.15.1 Definition23

In an Inter-Frequency Hard Handoff test (also known as the Mobile Assisted Hard Handoff24test), when the mobile station is directed by the base station to perform a search on a25Candidate Frequency, the mobile station will search for a pilot in the Candidate Frequency26Neighbor Set. The mobile station will report back to the base station any pilot detected in the27Candidate Frequency Neighbor Set with a pilot Ec/Io above the value defined by CF_T_ADD.28The base station should then direct the mobile station to the Candidate Frequency and29completes the hard handoff.30

31

Traceability [4]3233

2.6.6.2.5 Handoff Messages342.6.6.2.8 CDMA-to-CDMA Hard Handoff352.7.2.3.2.20 Candidate Frequency Search Report Message363.6.6.2.2 Call Processing During Handoff37

TSG-C42 Page 3-40

10/19/2001 C.S0031

3.7.7.3.3.2.27 Candidate Frequency Search Request Message12


a. Setup test as shown in Figure 3.4.2-1.4• The Forward Channel from base station #1 has a CDMA frequency assignment5

F1 (any valid value), an arbitrary pilot PN offset index P1 and is called Channel61.7

• The Forward Channel from base station #2 has a CDMA frequency assignment8F2 (any valid value other than f1 in the same band class), an arbitrary pilot PN9offset index P2 and is called Channel 2.10


12Table 3.15.2-1. Test Parameters for Inter-Frequency Hard Handoff (CDMA to CDMA)13

14


Îor/Ioc dB 2.9 2.9

or

cI

EPilot dB -7 -7

or

cI

ETraffic dB -7 N/A


0

cI

EPilot dB -11.0 -11.0

15

c. Reverse Link attenuation should be set to balance the forward and reverse links.16

d. Set up a mobile station originated call on Channel 1.17

e. Send from base station #1 a Candidate Frequency Search Request Message to the18mobile station to set an explicit action time with the following parameters:19

20

TSG-C42 Page 3-41

10/19/2001 C.S0031

Parameters Value (Decimal)

USE_TIME 1 (use action time)

SEARCH_TYPE 1 (single search)

SEARCH_MODE 0 (CDMA)

CDMA_FREQ F2

SF_TOTAL_EC_THRESH 31 (disabled)

SF_TOTAL_EC_IO_THRESH 31 (disabled)

CF_SRCH_WIN_N 8 (60 chips)

CF_T_ADD 28 (-14 dB)

NUM_PILOTS 1 (1 pilot)

CF_NGHBR_SRCH_MODE 0 (no search priorities orsearch windows specified)

NGHBR_PN P2

1

f. Verify that the mobile station responds with a Candidate Frequency Search Report2Message.3

g. Verify that base station #1 sends a General Handoff Direction Message, an Extended4Handoff Direction Message or a Universal Handoff Direction Message to initiate5handoff from base station #1 to base station #2.6



The mobile station and the base station shall successfully execute the handoff9transitions. Any audio dropouts present shall not exceed the limits specified in10Table 3.2.3-1.11

12

3.16 Inter-Frequency Hard Handoff (CDMA to AMPS)13

3.16.1 Definition14

In an Inter-Frequency Hard Handoff test (also known as the Mobile Assisted Hard Handoff15test), when the mobile station is directed by the base station to perform a search on a16Candidate Frequency, the mobile station will search for an analog channel in the Candidate17Frequency Analog Search Set and shall measure the mean input power on the analog18frequency. The mobile station will report back to the base station the signal strength of the19analog channel searched. The base station should then direct the mobile station to the Analog20Channel and completes the hard handoff.21

22

TSG-C42 Page 3-42

10/19/2001 C.S0031

Traceability [4]12

2.6.6.2.5 Handoff Messages32.6.6.2.8 CDMA-to-CDMA Hard Handoff42.6.6.10.2 Candidate Frequency Analog Search Set52.7.2.3.2.21 Candidate Frequency Search Report Message63.6.6.2.2 Call Processing During Handoff73.7.7.3.3.2.27 Candidate Frequency Search Request Message8

9



•The Forward Channel from base station #1 has a CDMA frequency assignment F1 (any12valid value), an arbitrary pilot PN offset index P1 and is called Channel 1.13

•The Forward Channel from base station #2 uses an AMPS frequency called Channel 2.14

b. Set the test parameters as specified in Tables 3.16.2-1 and 3.16.2-215

16Table 3.16.2-1. Test Parameters for Inter-Frequency Hard Handoff (Channel 1)17

18

CDMA Parameter Unit Channel 1

Îor/Ioc dB 0

Pilot Ec/Ior dB -7



Pilot Ec/Io dB -10

Table 3.16.2-2 Test Parameter for Inter-Frequency Handoff (Channel 2)19

20Analog Parameter Unit Channel 2

Voice Channel dBm -73

Co-Channel Interference dB -18

21

22

c. Reverse Link attenuation should be set to balance the forward and reverse links.23

d. Set up a mobile station originated voice call on Channel 1.24

e. Send from base station #1 a Candidate Frequency Search Request Message to the25mobile station to set an explicit action time with the following parameters:26

27

TSG-C42 Page 3-43

10/19/2001 C.S0031

Parameters Value (Decimal)

USE_TIME 1 (use action time)

SEARCH_TYPE 1 (single search)

SEARCH_MODE 1 (search for analog channels)

SF_TOTAL_EC_THRESH 31 (disabled)

SF_TOTAL_EC_IO_THRESH 31 (disabled)

NUM_ANALOG_FREQS 1

ANALOG_FREQ Channel 2

1

e. Verify that the mobile station responds with a Candidate Frequency Search Report2Message.3

f. Verify that base station #1 sends an Analog Handoff Direction Message to initiate4handoff from base station #1 to base station #2.5

g. Verify audio in both directions.6


The mobile station and the base station shall successfully execute the handoff8transitions. Any audio dropouts present shall not exceed the limits specified in9Table 3.2.3-1.10

11

3.17 Hard Handoff Between Frequencies with Different Protocol Revisions12

3.17.1 Definition13This test verifies the mobile station is able perform a hard handoff between base stations14supporting using different protocol revisions (P_REV).15


2.6.6.1.1 Types of Handoff172.6.6.2.5 Handoff Messages182.6.6.2.8 CDMA-to-CDMA Hard Handoff193.6.6.1.1 Types of Handoff203.6.6.2.2 Call Processing During Handoff213.7.3.3.2.31 General Handoff Direction Message223.7.3.3.2.36 Universal Handoff Direction Message23


a. Configure base station one and base station two with different protocol revisions.25

b. Verify the mobile station supports the protocol revisions on each base station.26

c. Setup test as shown in Figure 3.1.2-1.27

TSG-C42 Page 3-44

10/19/2001 C.S0031

• The Forward Channel from base station one has an arbitrary pilot PN1offset index P1 and is called Channel 1.2

• The Forward Channel from base station two has an arbitrary pilot PN3offset index P2 and is called Channel 2.4


d. Set the test parameters as shown in Table 3.x.2-1.89

Table 3.x.2-1 Hard Handoff Test Parameters10


Îor/Ioc dBm N/A -5





11

e. Set reverse link attenuation to balance forward and reverse links (approx. 90 dB).12

f. Setup a mobile station originated call on Channel 1.13

g. Verify user traffic in both directions.14

h. Send a General Handoff Direction Message or Universal Handoff Direction Message with15proper parameters (refer to tables in Foreword) to initiate handoff from Channel 1 to16Channel 2.17

i. Verify the P_REV in the General Handoff Direction Message or Universal Handoff18Direction Message sent from base station one is equal to the P_REV of base station two.19

j. Verify the handoff is successful and user traffic is present in both directions.20

3.17.3 Minimum Standard21The mobile station and base stations shall successfully execute the handoff.22

23

TSG-C42 Page 4-1

10/19/2001 C.S0031

4 POWER CONTROL TESTS1Table 4-1 lists power control tests.2

Table 4-1 Power Control Tests3

Test No. Title

4.1 Forward TCH Power Control

4.2 Mobile Station Response to Power Up Function (PUF) Message

4.3 Fast Forward Power Control (FFPC)

4.1 Forward Traffic Channel Power Control4

4.1.1 Definition5This test verifies that the mobile station reports frame error rate statistics at specified intervals if6the base station enables periodic reporting, and verifies that the mobile station reports frame7error rate statistics when the frame error rate reaches a specified threshold if the base station8enables threshold reporting.9

Traceability: (See [4] )10

2.6.4.1.1 Forward Traffic Channel Power Control112.7.2.3.2.6 Power Measurement Report Message123.6.4.1.1 Forward Traffic Channel Power Control133.7.3.3.2.10 Power Control Parameters Message14

Applicability: Forward Link: RC 1 through RC 5; Reverse Link: RC 1 through RC 415



b. Setup a mobile station originated call using the test parameters for Test 1 as18specified in Table 4.1.2-1.19

c. Set the AWGN source power so the forward link average FER is between 0.5 and201.0%.21

d. Instruct the base station to send the Power Control Parameters Message to enable22the threshold reporting and disable the periodic reporting according to the base23station manufacturer's forward power control algorithm.24

25WR_THRESH_ENABLE 1’ (Enable threshold reporting)

WR_PERIOD_ENABLE 0’ (Disable periodic reporting)

26

e. Using Attenuator 1, alternately increase and decrease AWGN source output power27by 5 dB from the original power set in step c.28

f. Monitor forward traffic channel Ec/Ior and ensure power increases and decreases29corresponding to noise power from the AWGN source.30

TSG-C42 Page 4-2

10/19/2001 C.S0031

g. Monitor forward link FER at the mobile station.1

2Figure 4.1.2-1 Functional Setup for Testing Forward TCH Power Control3

4

TSG-C42 Page 4-3

10/19/2001 C.S0031

Table 4.1.2-1 Test Parameters for Forward Power Control Tests1

TestNumber

ForwardRC

ReverseRC

Threshold/Periodic

ServiceOption

Channels ForwardLink Power

[dBm/1.23 MHz]

1 1 1 Threshold 2, 54, 55, or32798

F-FCH -65

2 1 1 Periodic 2, 54, 55, or32798

F-FCH -65

3 2 2 Threshold 9, 54, 55, or32799

F-FCH -62

4 2 2 Periodic 9, 54, 55, or32799

F-FCH -62

5 3 3 Threshold 54, or 55 F-FCH -65

6 3 3 Periodic 54, or 55 F-FCH -65

7 3 3 Threshold 54, or 55 F-DCCH -65

8 3 3 Periodic 54, or 55 F-DCCH -65









17 3 3 N/A 54, or 55 F-FCH/F-SCH -65

18 4 3 N/A 54, or 55 F-FCH/F-SCH -65

19 5 4 N/A 54, or 55 F-FCH/F-SCH -62

20 3 3 N/A 54, or 55 F-DCCH/F-SCH

-65

21 4 3 N/A 54, or 55 F-DCCH/F-SCH

-65

22 5 4 N/A 54, or 55 F-DCCH/F-SCH

-62

Note: All tests should be performed at full data rate or at a variable rate. Tests involving the2Forward Supplemental Channels should only include 1 Forward Supplemental3Channel.4

5

h. Verify the MS to send the Power Measurement Report Message when the bad frames6received by the mobile station reaches the specified threshold.7

TSG-C42 Page 4-4

10/19/2001 C.S0031

i. End the call.1

j. Setup a mobile station originated call using the test parameters for Test 2 as2specified in Table 4.1.2-1.3

k. Instruct the base station to send the Power Control Parameters Message to enable4the periodic reporting and disable the threshold reporting according to the base5station manufacturer's forward power control algorithm.6

7PWR_THRESH_ENABLE ‘0’ (Disable threshold reporting)

PWR_PERIOD_ENABLE ‘1’ (Enable periodic reporting)

8

l. Repeat the steps e through g.9

m. Verify the mobile station sends the Power Measurement Report Message when the10total frames received by the mobile station reach the specified report period.11

n. End the call.12

o. Repeat steps b through n except for using the test parameters for Tests 3 to 16 as13specified in Table 4.1.2-1.14

p. Repeat steps b through c except for using the test parameters for Test 17 to Test 2215as specified in Table 4.1.2-1.16

q. Instruct the base station to send the Extended Supplemental Channel Assignment17Message including a Forward Supplemental Channel assignment and setting18FOR_SCH_FER_REP to ‘1’.19

r. Repeat the steps e through g.20

s. Verify the mobile station sends the Power Measurement Report Message at the end21of the burst.22

t. End the call.23

4.1.3 Minimum Standard24The base station should alternately increase and decrease the forward traffic channel power25according to the base station manufacturer's forward power control algorithm. Forward link FER26measured at the mobile station should be within the target value and the mobile station shall27report frame error rate statistics. There shall not be any dropped calls.28

4.2 Mobile Station Response to Power Up Function (PUF) Message29

4.2.1 Definition30This test verifies that both mobile station and base station which are capable of PUF feature31correct interpretation and functionality of the Power Up Function Message, Mobile Station32Reject Order Message, and the Power Up Function Completion Message.33

Traceability: IS-2000;34

[1] 2.1.2.2.2.4 Gated Output Power During a Serving Frequency PUF Probe35[1] 2.1.2.3.1 Estimated Open Loop Output Power36

TSG-C42 Page 4-5

10/19/2001 C.S0031

[1] 2.1.2.3.2 Closed Loop Output Power1[1] 2.1.3.1.10.3 Gating During a PUF Probe2[4] 2.6.4.1.7 Power Up Function (PUF)3[4] 3.7.3.3.2.29 Power Up Function Message4[4] 3.7.3.3.2.30 Power Up Function Completion Message5

Applicability: RC 1 and greater, MOB_P_REV = 5 and greater6



b. Set power levels as stated in Table 4.2.2-1 Test 4.9

c. Disable all forms of registration.10

d. Disable power control.11

4.2.2.1 Power Up Function at Nominal Power12

a. Set values shown in Table 4.2.2.1-1 in the Power Up Function Message:1314

Table 4.2.2.1-1 Mobile Station Transmit Power Up Function Parameters, Nominal Power15

PUF_INIT_PWR = 20 dB PUF_PWR_STEP = 2 dB

PUF_PULSE_SIZE = 17.5 ms PUF_SETUP_SIZE = 1.25 ms

PUF_INTERVAL = 50 frames (1 second) TOTAL_PUF_PROBES = 4

PUF_FREQ_INCL = 1 MAX_PWR_PUF = 2

PUF_CDMA_FREQ = {Target CDMAfrequency}

PUF_BAND_CLASS = {Serving CDMA bandclass}

16

b. Setup a mobile station originated voice call.17

c. Verify audio in both directions.18

d. Send from the base station the Power Up Function Message of Table 4.2.2.1-1.19

e. Note where the mobile transmit power level is before a PUF probe is sent by the20mobile station. After each PUF probe, ensure the mobile station returns to the initial21power level before the PUF probe was sent.22

f. Monitor mobile station transmit power transitions to ensure the mobile station uses23PUF parameters (Figure 4.2.2.1-1) as sent to the mobile station in the Power Up24Function Message.25

TSG-C42 Page 4-6

10/19/2001 C.S0031

1 2 3 4 5

Approximate Time (seconds)

Mob

ile

Sta

tion

Tx

Pow

er(d

Bm

)

20

18

16

14

12

-8

1Figure 4.2.2.1-1 Mobile station TX Power Response to Power Up Function Parameters,2

Nominal Power34

g. End the call.5

4.2.2.2 PUF Probes Sent at Maximum Power6

a. Set values for the Power Up Function Message as shown in Table 4.2.2.2-178

Table 4.2.2.2-1 Mobile Station Transmit Power Up Function Parameters, Maximum Power9






PUF_BAND_CLASS = {Serving CDMA band class}

10




e. Note where the mobile transmit power level is before a PUF probe is sent by the14mobile station. After each PUF probe, ensure the mobile station returns to the initial15power level before the PUF probe was sent.16

f. Monitor mobile station transmit power transitions to ensure the mobile station uses17PUF parameters until reaching its maximum output power. At this point, the mobile18station's transmit power for each successive probe will remain constant until the19maximum number of probes at maximum power have been sent (Figure 4.2.2.2-1).20

TSG-C42 Page 4-7

10/19/2001 C.S0031

1 2 3 4 5M

obile

Sta

tion

Tx

Pow

er(d

Bm

)

max

22

12

-8

1Figure 4.2.2.2-1 Mobile Station TX Power Response to Power-up Function Parameters,2

Maximum Power3

g. End call.4

4.2.2.3 Processing of Power Up Function Completion Message5

a. Set values in the Power Up Function Message as shown in Table 4.2.2.3-1.6




e. Note where the mobile station transmit power level is before a PUF probe is sent by10the mobile station. After each PUF probe, ensure the mobile station returns to the11initial power level before the PUF probe was sent.12

f. Before all of the PUF probes are sent from the mobile station, send from the base13station a Power Up Completion Message.14

15

Table 4.2.2.3-1 Mobile Station Transmit Power Up Function Parameters16






PUF_BAND_CLASS = {Serving CDMA band class}

17

g. Monitor mobile station transmit power transitions to ensure the mobile station uses18PUF parameters until receiving the Power Up Function Completion Message. The19mobile station should complete the current PUF probe then should stop20transmitting PUF probes.21

h. End call.22

TSG-C42 Page 4-8

10/19/2001 C.S0031


4.2.3.1 Power Up Function at Nominal Power2The mobile station shall respond on the traffic channel to changes in the Power Up Function3Message. The mobile station shall send the maximum number of PUF probes specified in the4Power Up Function Message. Refer to Table 4.2.2.1-15

4.2.3.2 PUF Probes sent at Maximum Power6The mobile station shall respond on the traffic channel to changes in the Power Up Function7Message. The mobile station shall send the maximum number of PUF probes at maximum power8specified in the Power Up Function Message Refer to Table 4.2.2.2-1.9

4.2.3.3 Processing Power Up Function Completion Message10The mobile station shall respond on the traffic channel to changes in the Power Up Function11Message. The mobile station shall finish the current PUF probe upon receiving the Power Up12Function Completion Message then shall not send PUF probes. Refer to Table 4.2.2.3-113

4.3 Fast Forward Power Control (FFPC)14

4.3.1 FFPC using different values of FPC_MODE15

4.3.1.1 Definition16The mobile station accomplishes fast forward power control by transmitting the Reverse Power17Control Subchannel to the base station on the Reverse Pilot Channel. The mobile station18determines the information to be sent to the base station through inner and outer closed loop19estimations. In outer loop estimation, the mobile station adjusts the Eb/Nt setpoints to the Eb/Nt20value necessary to achieve the target FER on the Forward Traffic Channel. In inner loop21estimation, the mobile station compares the received Eb/Nt to the setpoint and determines the22value of the power control bit to be sent to the base station. There are 16 Power Control Groups23per frame on the Reverse Power Control Subchannel. This test verifies that the mobile station24can process the various parameters in the Extended Channel Assignment Message, the Extended25Supplemental Channel Assignment Message, and the Service Connect Message.26

Traceability:27

[1] 2.1.3.1.11 Reverse Power Control Subchannel28[4] 2.6.6.2.5.1, 3.6.6.2.2.12, 3.7.3.3.2.37 Extended Supplemental Channel Assignment Message29[4] 2.6.2.4, 2.6.3.3, 2.6.3.5, 3.6.3.3, 3.6.3.5, 3.7.2.3.2.21 Extended Channel Assignment Message30[4] 2.6.4.1.2, 2.6.4.1.2.2, 3.7.3.3.2.20, 3.7.5, 3.7.5.7, 3.7.5.20 Service Connect Message31


4.3.1.2 FPC_MODE Information3334

TSG-C42 Page 4-9

10/19/2001 C.S0031

Table 4.3.1.2-1 Reverse Power Control Subchannel Configurations1

Reverse Power Control Subchannel Allocations(Power Control Group Numbers)

FPC_MODE Primary Reverse Power ControlSubchannel

Secondary Reverse PowerControl Subchannel

‘000’ 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 Not supported

‘001’ 0,2,4,6,8,10,12,14 1,3,5,7,9,11,13,15

‘010’ 1,5,9,13 0,2,3,4,6,7,8,10,11,12,14,15

'2

4.3.1.3 FPC_MODE ‘000’; F-FCH Only3


a. Connect base station and mobile station as shown in Figure 4.3.1.3.1-1.5

6Figure 4.3.1.3.1-1 Functional Setup for Testing Fast Forward Power Control7

8b. Set power levels as stated in Table 4.3.1.3.1-4:9

10

Table 4.3.1.3.1-4 Test Parameters for Fast Forward Power Control11


or

cI

EPilot dB -7


Ior/Ioc dB 10

Avg. Mobile Transmit Power dB -8

12

TSG-C42 Page 4-10

10/19/2001 C.S0031

c. Setup a mobile station originated call using Service Option 55 (Loopback Service1Option) or Service Option 54 (Markov Service Option).2

d. Instruct the base station to send the Extended Channel Assignment Message with3the parameters set as follows:4

5ASSIGN_MODE = '100' GRANTED_MODE = '10'

FOR_RC = '00011' (RC 3) REV_RC = '00011' (RC 3)

CH_IND = '01' FPC_FCH_INIT_SETPT = '01000000' (8 dB)

FPC_FCH_FER = '00010' (1%) FPC_FCH_MIN_SETPT = '00010000' (2 dB)

FPC_FCH_MAX_SETPT = '10000000' (16 dB)

6

e. Ensure the base station sends the Service Connect Message with FPC_INCL set to7‘0’.8

f. Monitor the forward link FER at the mobile station.9

g. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz10at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second11for a total of 20 dBm/1.23 MHz at the AWGN source.12

h. Monitor traffic channel Ec/Ior and ensure the power changes corresponding to13noise power from the AWGN source. The power increases if the noise power14increases and decreases if the noise power decreases.15

i. Verify that the forward link FER on the FCH is remaining at the target value (i.e.161%).17

j. End the call at the mobile station.18

k. Repeat steps a through j above except that FOR_RC is set to RC4 and REV_RC is set19to RC3 in step d.20

l. Repeat steps a through j above except that FOR_RC is set to RC5 and REV_RC is set21to RC4 in step d .22

4.3.1.4 FPC_MODE ‘000’; F-DCCH only23


a. Connect base station and mobile station as shown in Figure 4.3.1.3.1-125

b. Set power levels as stated in Table 4.3.1.4.1-4:2627

TSG-C42 Page 4-11

10/19/2001 C.S0031



or

cI

EPilot dB -7


Ior/Ioc dB 10


2

c. Setup a mobile station originated call using Service Option 32 (Test Data Service3Option).4


7ASSIGN_MODE = ‘100’ GRANTED_MODE = ‘10’

FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)

CH_IND = ‘10’ FPC_DCCH_INIT_SETPT = ‘01000000’ (8 dB)

FPC_DCCH_FER = ‘00010’ (1%) FPC_DCCH_MIN_SETPT = ‘00010000’ (2 dB)

FPC_DCCH_MAX_SETPT = ‘10000000’ (16dB)

8

e. Ensure the base station sends the Service Connect Message with FPC_INCL set to9‘0’.10

f. Monitor the forward link FER at the mobile station.11

g. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz12at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second13for a total of 20 dBm/1.23 MHz at the AWGN source.14

h. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise15power from the AWGN source. The power increases if the noise power increases and16decreases if the noise power decreases.17

i. Verify that the forward link FER on DCCH is remaining in the target value (1%).18

j. End the call at the mobile station.19

k. Repeat steps a through i above except for setting FOR_RC to RC4 and REV_RC to20RC3 in step d.21

l. Repeat steps a through i above except for setting FOR_RC to RC5 and REV_RC to22RC4 in step d.23

TSG-C42 Page 4-12

10/19/2001 C.S0031

4.3.1.5 FPC_MODE ‘001’; F-FCH and F-SCH1






or

cI

EPilot dB -7


Ior/Ioc dB 10


9




FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)

CH_IND = ‘01’ FPC_FCH_INIT_SETPT = ‘01000000’ (8 dB)

FPC_FCH_FER = ‘00010’ (1%) FPC_FCH_MIN_SETPT = ‘00010000’ (2 dB)

FPC_FCH_MAX_SETPT = ‘10000000’ (16 dB)

15

e. Instruct the base station to send the Service Connect Message with the parameters16set as follows:17

18FPC_INCL = ‘1’ FPC_OLPC_FCH_INCL = ‘0’

FPC_PRI_CHAN = ‘0’ GATING_RATE_INCL = ‘0’

FPC_MODE = ‘001’

19

f. Instruct the base station to download SCH configuration and assign a Forward20Supplemental Channel by using the Extended Supplemental Channel Assignment21Message and set the power control related fields as stated in follows:22

23

TSG-C42 Page 4-13

10/19/2001 C.S0031

FPC_INCL = ‘1’ FPC_SCH_INIT_SETPT = ‘01000000’ (8 dB)

FPC_MODE_SCH = ‘001’ FPC_SCH_MAX_SETPT = ‘10000000’ (16 dB)

FPC_SCH_INIT_SETPT_OP = ‘0’ FPC_SCH_MIN_SETPT = ‘00010000’ (2 dB)

FPC_SCH_FER = ‘00100’ (5%)

1

g. Monitor the forward link FER on FCH and SCH (during the burst assignment) at the2mobile station.3

h. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz4at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second5for a total of 20 dBm/1.23 MHz at the AWGN source.6

i. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise7power from the AWGN source. The power increases if the noise power increases and8decreases if the noise power decreases.9

j. Verify that the forward link FERs on FCH and SCH (during SCH assignment) are10remaining in the target value.11

k. End the call at the mobile station.12

l. Repeat steps a through k above except that FOR_RC is set to RC4 and REV_RC is13set to RC3 in step d.14

m. Repeat steps h through k above except that FOR_RC is set to RC5 and REV_RC is15set to RC4 in step d.16

4.3.1.6 FPC_MODE ‘000’ without F-SCH Active and FPC_MODE ‘001’ with F-SCH Active; F-17DCCH and F-SCH18






or

cI

EPilot dB -7


Ior/Ioc dB 10


24


TSG-C42 Page 4-14

10/19/2001 C.S0031



FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)




4

e. Instruct the base station to send the Service Connect Message with FPC_INCL set to5‘0’.6

f. Instruct the base station to download the SCH configuration and assign a Forward7Supplemental Channel using the Extended Supplemental Channel Assignment8Message and set the power control related information as follows:9

10FPC_INCL = ‘1’ FPC_SCH_INIT_SETPT = ‘01000000’ (8 dB)



FPC_SCH_FER = ‘01010’ (5%)

11

g. Monitor the forward link FER on both F-DCCH and F-SCH (during SCH assignment)12at the mobile station.13



j. Verify that the forward link FER on DCCH and SCH (during SCH assignment)20remains at the target value.21


l. Repeat steps a through k above except that FOR_RC is set to RC4 and REV_RC is23set to RC3 in step d.24

m. Repeat steps a through k above except that the FOR_RC is set to RC5 and REV_RC25is set to RC4 in step d.26

TSG-C42 Page 4-15

10/19/2001 C.S0031

4.3.1.7 FPC_MODE ‘000’ without F-SCH Active and FPC_MODE ‘010’ with F-SCH Active; F-1FCH and F-SCH2


Connect base station and mobile station as shown in Figure 4.3.1.3.1-14




or

cI

EPilot dB -7


Ior/Ioc dB 10


8




FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)



FPC_FCH_MAX_SETPT = ‘10000000’ (16 dB)

14


f. Instruct the base station to download SCH configuration and assign a Forward17Supplemental Channel by using the Extended Supplemental Channel Assignment18Message with power control related parameters set as follows:19

20

TSG-C42 Page 4-16

10/19/2001 C.S0031

FPC_INCL = ‘1’ FPC_SCH_INIT_SETPT = ‘01000000’ (8 dB)



FPC_SCH_FER = ‘01010’ (5%)

g. Monitor the forward link FER on both FCH and SCH (during the SCH assignment)1at the mobile station.2



j. Verify that the forward link FERs on FCH and SCH (during SCH assignment) are9remaining in the target value.10


l. Repeat steps a through k above except for step d to set FOR_RC to RC4 and12REV_RC to RC3.13

m. Repeat steps a through k above except for step d to set FOR_RC to RC5 and14REV_RC to RC4.15

4.3.1.8 FPC_MODE ‘010’; F-DCCH and F-SCH16


Connect base station and mobile station as shown in Figure 4.3.1.3.1-118

Set power levels as stated in Table 4.3.1.8.1-5:1920



or

cI

EPilot dB -7


Ior/Ioc dB 10

22


d. Instruct the base station to send the Extended Channel Assignment Message with25the parameters set as follows.26

27

TSG-C42 Page 4-17

10/19/2001 C.S0031

ASSIGN_MODE = ‘100’ GRANTED_MODE = ‘10’

FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)




1





5

f. Instruct the base station to send SCH configuration and assign a Forward6Supplemental Channel by using the Extended Supplemental Channel Assignment7Message with power control related parameters set as follows:8




FPC_SCH_FER = ‘01010’ (5%)

10

g. Monitor forward link FER on both F-DCCH and F-SCH (during SCH burst11assignment) at the mobile station.12



j. Verify that the forward link FERs on the DCCH and SCH (during SCH assignment)19are remaining in the target value.20


l. Repeat steps a through k above except for step d to set FOR_RC to RC4 and22REV_RC to 3.23

m. Repeat steps a through k above except for step d to set FOR_RC to RC5 and24REV_RC to 4.25

TSG-C42 Page 4-18

10/19/2001 C.S0031

4.3.1.9 Minimum Standard1For all tests, the call shall not drop, the DCCH FER shall remain at 1%±0.5% and the SCH FER2shall remain at 5%±2.5%.3

4.3.2 Outer Loop Report4

4.3.2.1 Definition5This test verifies that the mobile station shall send the Outer Loop Report Message if the Outer6Loop Report Request Order is received.7

Traceability:8

[1] 2.1.3.1.11 Reverse Power Control Subchannel9[4] 2.6.6.2.5.1, 3.6.6.2.2.12, 3.7.3.3.2.37 Extended Supplemental Channel Assignment Message10[4] 2.6.2.4, 2.6.3.3, 2.6.3.5, 3.6.3.3, 3.6.3.5, 3.7.2.3.2.21 Extended Channel Assignment Message11[4] 2.6.4.1.2, 2.6.4.1.2.2, 3.7.3.3.2.20, 3.7.5, 3.7.5.7, 3.7.5.20 Service Connect Message12[4] 2.6.4.1.1, 2.7.2.3.2.223.7.3.3.2.25 Outer Loop Report Message13




b. Set power levels as stated in Table 4.3.2.2-1:1718

Table 4.3.2.2-1 Test Parameters for Fast Forward Power Control19


or

cI

EPilot dB -7


Ior/Ioc dB 10


20



25

TSG-C42 Page 4-19

10/19/2001 C.S0031


FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)



FPC_FCH_MAX_SETPT = ‘10000000’ (16dB)

1


f. Instruct the base station to download SCH configuration and assign a Forward4Supplemental Channel by using the Extended Supplemental Channel Assignment5Message with power control related parameters set as follows:6


FPC_MODE_SCH = ‘000’ FPC_SCH_MAX_SETPT = ‘10000000’ (16dB)


FPC_SCH_FER = ‘01010’ (5%)

8

g. Monitor the forward link FER on both FCH and SCH (during the SCH assignment)9at the mobile station.10



j. During the F-SCH assignment, instruct the base station to send Outer Loop Report17Request Order.18

k. Verify the mobile station sends the Outer Loop Report Message and this message19contains FPC_FCH_CURR_SETPT and FPC_SCH_CURR_SETPT.20

l. End the call at the mobile station.21

m. Repeat steps a through m above except for the following steps:22

n. Instruct the base station to send the Extended Channel Assignment Message with23the parameters set as follows:24

25

TSG-C42 Page 4-20

10/19/2001 C.S0031


FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)

CH_IND = ‘10’ FPC_DCCH_INIT_SETPT = ‘01000000’(8 dB)

FPC_DCCH_FER = ‘00010’ (1%) FPC_DCCH_MIN_SETPT = ‘00010000’(2 dB)

FPC_DCCH_MAX_SETPT =‘10000000’ (16 dB)

1

o. Monitor the forward link FER on both DCCH and SCH (during the SCH assignment2at the mobile station.3

p. Verify the mobile station sends the Outer Loop Report Message and this message4contains FPC_DCCH_CURR_SETPT and FPC_SCH_CURR_SETPT.5

4.3.2.3 Minimum Requirement6The mobile station shall send the Outer Loop Report Message if the Outer Loop Report Request7Order is received. The FPC current setpoint reported by the mobile station shall be in the range8of the minimum setpoint and the maximum setpoint.9

10

TSG-C42 Page 4-21

10/19/2001 C.S0031

4.3.3 Fast Forward Power Control (FFPC) in Soft Handoff1

4.3.3.1 Definition2The mobile station accomplishes fast forward power control by transmitting the Reverse Power3Control Subchannel to the base station on the Reverse Pilot Channel. The mobile station4determines the information to send to the base station through inner and outer closed loop5estimations. In outer loop estimation, the mobile station adjusts the Eb/Nt setpoints to the Eb/Nt6value necessary to achieve the target FER on the Forward Traffic Channel. In inner loop7estimation, the mobile station compares the received Eb/Nt to the setpoint and determines the8value of the power control bit to be sent to the base station. This test verifies that the mobile9station can perform FFPC while in soft handoff. This test also verifies that the mobile station can10process the various parameters in the Extended Channel Assignment Message, the Extended11Supplemental Channel Assignment Message, the Universal Handoff Direction Message, and the12Service Connect Message.13

Traceability:14

[1] 2.1.3.1.11 Reverse Power Control Subchannel15[4] 2.6.6.2.5.1, 3.6.6.2.2.12, 3.7.3.3.2.37 Extended Supplemental Channel Assignment Message16[4] 2.6.2.4, 2.6.3.3, 2.6.3.5, 3.6.3.3, 3.6.3.5, 3.7.2.3.2.21 Extended Channel Assignment Message17[4] 2.6.4.1.2, 2.6.4.1.2.2, 3.7.3.3.2.20, 3.7.5, 3.7.5.7, 3.7.5.20 Service Connect Message18


4.3.3.2 F-FCH in SHO and F-SCH not in SHO; FPC_MODE = 00120


a. Setup the test as shown in Figure 4.3.3.2.1-1.22

b. Set power levels as stated in Table 4.3.3.3.1-1.23

TSG-C42 Page 4-22

10/19/2001 C.S0031

1Figure 4.3.3.2. 1-1 Functional Setup for Testing FFPC in Handoff2

3


Parameter Unit Base station #1 Base station #2


Ioc dBm/1.23 MHz -75 -75

Ior/Ioc dB 10 10


5

c. Setup a mobile station originated call using Service Option 32 (Test Data Service6Option) on Base station #1.7


TSG-C42 Page 4-23

10/19/2001 C.S0031


FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)




2





6

f. Instruct the base station to download SCH configuration and assign a Forward7Supplemental Channel by using the Extended Supplemental Channel Assignment8Message with the power control related parameters set as follows:9




FPC_SCH_FER = ‘01010’ (5%)

11

g. Raise the level of Base station #2 in steps of 1 dB with a dwell time of 5 seconds12after each step until the mobile station has generated the Pilot Strength13Measurement Message.14

h. Instruct the base station to send the Universal Handoff Direction Message during F-15SCH assignment with the parameters set as follows:16

17CH_IND = ‘101’ (FCH and ContinuousReverse Pilot)

NUM_PILOTS = ‘010’

For PILOT_PN = {Base station #1} PILOT_INCL = ‘1’


18

i. Verify there are no forward supplemental channels transmitting on Base station #2.19

j. Set the test parameters as specified in Table 4.3.3.2.1-2 without dropping the call.2021

TSG-C42 Page 4-24

10/19/2001 C.S0031





Ioc dBm/1.23 MHz -75 -75


2

k. Monitor the forward link FER on both F-FCH and F-SCH (during F-SCH assignment)3at the mobile station.4

l. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz5at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second6for a total of 20 dBm/1.23 MHz at the AWGN source.7

m. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise8power from the AWGN source. The power increases if the noise power increases and9decreases if the noise power decreases.10

n. Verify that the forward link FERs on FCH and SCH (during SCH assignment) are11remaining in the target value.12

o. End the call at the mobile station.13

4.3.3.3 F-FCH in SHO and F-SCH not in SHO; FPC_MODE = ‘010’14




c. Setup a mobile station originated call using Service Option 32 (Test Data Service18Option) with 100% frame activity on Base station #1.19



FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)




23


26

TSG-C42 Page 4-25

10/19/2001 C.S0031

FPC_INCL = ‘1’ FPC_OLPC_FCH_INCL = ‘0’



1





FPC_SCH_FER = ‘01010’ (5%)

6

g. Raise the level of Base station #2 in steps of 1 dB with a dwell time of 5 seconds7after each step until the mobile station has generated the Pilot Strength8Measurement Message.9

h. Instruct the base station to send the Universal Handoff Direction Message during F-10SCH assignment with parameters set as follows:11





13

i. Verify there are no forward supplemental channels running on Base station #2.14





n. Verify that the forward link FERs on FCH and SCH (during SCH assignment) are25remaining in the target value.26


TSG-C42 Page 4-26

10/19/2001 C.S0031

4.3.3.4 F-DCCH in SHO and F-SCH not in SHO; FPC_MODE = ‘001’1







FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)

CH_IND = ‘10’ FPC_DCCH_INIT_SETPT = ‘01000000’ (8dB)

FPC_DCCH_FER = ‘00010’ (1%) FPC_DCCH_MIN_SETPT = ‘00010000’ (2dB)

FPC_DCCH_MAX_SETPT = ‘10000000’(16 dB)

10





14





FPC_SCH_FER = ‘01010’ (5%)

19

g. Raise the level of Base Station #2 in steps of 1 dB with a dwell time of 5 seconds20after each step until the mobile station has generated the Pilot Strength21Measurement Message.22


TSG-C42 Page 4-27

10/19/2001 C.S0031

1CH_IND = ‘110’ (DCCH and ContinuousReverse Pilot)




2

i. Verify there are no forward supplemental channels running on Base Station #2.3





n. Verify that the forward link FERs on DCCH and SCH (during SCH assignment) are13remaining in the target value.14


4.3.3.5 F-DCCH in SHO and F-SCH not in SHO; FPC_MODE = ‘010’16






24ASSIGN_MODE = ‘100’ GRANTED_MODE = 10

FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)




25

TSG-C42 Page 4-28

10/19/2001 C.S0031





4





FPC_SCH_FER = ‘01010’ (5%)

9

g. Raise the level of Base Station #2 in steps of 1 dB with a dwell time of 5 seconds10after each step until the mobile station has generated the Pilot Strength11Measurement Message.12






16

i. Verify there are no forward supplemental channels running on Base station #2.17


k. Monitor the forward link FER on both F-DCCH and F-SCH (during F-SCH19assignment) at the mobile station.20



n. Verify that the forward link FERs on DCCH and SCH (during SCH assignment) are27remaining in the target value.28

TSG-C42 Page 4-29

10/19/2001 C.S0031


4.3.3.6 Minimum Standard2For all tests, the call shall not drop and the FER shall remain in the target value.3

4.3.4 Change FPC_MODE During a Call4

4.3.4.1 Definition5The mobile station accomplishes fast forward power control by transmitting the power control6subchannel to the base station on the R-PICH. The mobile station determines the information to7send to the base station through inner and outer closed loop estimations. In outer loop estimation,8the mobile station adjusts the Eb/Nt setpoints to the Eb/Nt value necessary to achieve the target9FER on the Forward Traffic Channel.10In inner loop estimation, the mobile station compares the received Eb/Nt to the setpoint and11determines the value of the power control bit to be sent to the base station. This test verifies that12the mobile station can process a change in FPC_MODE delivered by the Power Control13Message.14

Traceability:15

[1] 2.1.3.1.11 Reverse Power Control Subchannel16[4] 2.6.4.1.1.3, 3.7.3.3.2.25 Power Control Message17[4] 2.6.2.4, 2.6.3.3, 2.6.3.5, 3.6.3.3, 3.6.3.5, 3.7.2.3.2.21 Extended Channel Assignment Message18[4] 2.6.4.1.2, 2.6.4.1.2.2, 3.7.3.3.2.20, 3.7.5, 3.7.5.7, 3.7.5.20 Service Connect Message19

Applicability: RC 3 and greater20




c. Setup a mobile station originated call using Service Option 32 (Test Data Service24Option) with 100% frame activity.25



FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)




29


f. Monitor forward link FER at the mobile station.32

TSG-C42 Page 4-30

10/19/2001 C.S0031

g. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 5 dBm/1.23 MHz1at the AWGN source.2

h. Monitor traffic channel Ec/Ior and ensure power increases corresponding to noise3power from the AWGN source.4

i. Instruct the base station send the Power Control Message with the parameters set5as follows:6

7FPC_INCL = ‘1’ FPC_MODE = ‘010’

FPC_PRI_CHAN = ‘0’ FPC_OLPC_FCH_INCL = ‘1’

FPC_FCH_FER = ‘00100’ (2%) PWR_CNTL_STEP = ‘’001’ (0.5 dB)

FPC_FCH_MIN_SETPT = ‘00010000’ (2 dB) FPC_FCH_MAX_SETPT = ‘10000000’ (16 dB)

FPC_OLPC_DCCH_INCL = ‘0’

FPC_DCCH_MIN_SEPT = N/A FPC_DCCH_MAX_SEPT = N/A

FPC_OLPC_SCH_M_INCL = ‘1’ FPC_SCH_M_FER = ‘00010’ (1%)

FPC_MIN_SCH_M_SETPT = ‘00010000’ (2dB)

FPC_MAX_SCH_M_SETPT = ‘10000000’ (16dB)

NUM_SUP = 0

8

j. Monitor forward link FER at the mobile station.9

k. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 5 dBm/1.23 MHz10at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second11for a total of 20 dBm/1.23 MHz at the AWGN source.12

l. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise13power from the AWGN source. The power increases if the noise power increases and14decreases if the noise power decreases.15

m. Verify that the forward link FER on FCH is remaining in the target value.16

n. End the call at the mobile station.17

4.3.4.3 Minimum Standard18The call shall not drop and the FCH FER shall remain at 1%±0.5%.19

4.3.5 R-PICH in Gated Transmission Mode20

4.3.5.1 Gating with the Reverse Dedicated Control Channel21

4.3.5.1.1 Definition22The mobile station accomplishes fast forward power control by transmitting the power control23subchannel to the base station on the R-PICH. The power control subchannel can either be gated24(either at a rate of ½ or ¼) or not gated (a bit is transmitted on every PCG). Gating occurs only25when the Forward Dedicated Control Channel and the Reverse Dedicated Control Channel are26assigned and when there are no transmissions on the Reverse Dedicated Control Channel. This27

TSG-C42 Page 4-31

10/19/2001 C.S0031

test verifies that the mobile station can operate in the various gating transmission modes1specified in the Service Connect Message.2

Figure 4.3.5.1.1-1 Reverse Pilot Gating with no Transmission3on the Reverse Dedicated Control Channel [1] 2.1.3.2.34

5

TSG-C42 Page 4-32

10/19/2001 C.S0031

Figure 4.3.5.1.1-2 Reverse Pilot Gating during1Reverse Dedicated Control Channel Transmission [1] 2.1.3.2.32

Traceability:3

[1] 2.1.3.1.11 Reverse Power Control Subchannel4[1] 2.1.3.2 Reverse Pilot Channel5[4] 2.6.4.1.1.3, 3.7.3.3.2.25 Power Control Message6[4] 2.6.2.4, 2.6.3.3, 2.6.3.5, 3.6.3.3, 3.6.3.5, 3.7.2.3.2.21 Extended Channel Assignment Message7[4] 2.6.4.1.2, 2.6.4.1.2.2, 3.7.3.3.2.20, 3.7.5, 3.7.5.7, 3.7.5.20 Service Connect Message8





c. Setup a mobile station originated data call using Service Option 33.13

d. Instruct the base station to send the Extended Channel Assignment Message has the14parameters set as follows:15


FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)




17

TSG-C42 Page 4-33

10/19/2001 C.S0031

e. Instruct the base station to send the Service Connect Message has the parameters1set as follows:2


FPC_PRI_CHAN = ‘1’ FPC_OLPC_DCCH_INCL = ‘0’


GATING_RATE_INCL = ‘1’ PILOT_GATE_RATE = ‘01’ (gating at ½)

4

f. Instruct the base station to send the Extended Release Message with CH_IND set to5‘100’.6

g. Do not have any transmissions on the Reverse Dedicated Control Channel.7

h. Instruct the base station to send a sufficient number of In-Traffic System Parameters8Messages with the same system configurations and without requiring the9acknowledgment on the reverse link DCCH so that the mobile station can measure10forward FER.11

i. Monitor forward link FER at the mobile station.12

j. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 5 dBm/1.23 MHz13at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second14for a total of 20 dBm/1.23 MHz at the AWGN source.15

k. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise16power from the AWGN source. The power increases if the noise power increases and17decreases if the noise power decreases.18

l. Verify that the reverse Pilot Channel is gated at the specified rate and the forward19link FER on DCCH is remaining in the target value20

m. Instruct the mobile station to send the Data Burst Message on the Reverse21Dedicated Control Channel.22

n. Monitor the forward link FER at mobile station.23

o. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 5 dBm/1.23 MHz24at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second25for a total of 20 dBm/1.23 MHz at the AWGN source.26

p. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise27power from the AWGN source. The power increases if the noise power increases and28decreases if the noise power decreases.29

q. Verify that the reverse Pilot Channel is gated at the target rate if no transmissions30are on the Reverse Dedicated Control Channel and the reverse Pilot Channel is not31gated if there are transmissions on the Reverse Dedicated Control Channel.32

r. Verify that the forward link FER on DCCH is remaining in the target value.33

s. End the call at the mobile station. Repeat steps a through s above except for step f34to set PILOT_GATE_RATE to ‘10’ (gating at ¼).35

TSG-C42 Page 4-34

10/19/2001 C.S0031

4.3.5.2 Gating with the Reverse Fundamental Channel1

4.3.5.2.1 Definition2The mobile station accomplishes fast forward power control by transmitting the power control3subchannel to the base station on the R-PICH. The power control subchannel can either be gated4or not gated. The R-FCH may be gated when no other Reverse Traffic Channel is assigned and5the data rate is 1500 bps for RC 3 and RC5 or 1800 bps for RC4. When the R-FCH is operated in6the gated mode and is at a data rate of 1500 bps for RC 3 and RC 5 or 1800bps for RC 4, the R-7PICH shall have a transmission duty cycle of 50%. The R-PICH shall be transmitted in power8control groups 2, 3, 6, 7, 10, 11, 14, and 15, and shall not be transmitted in power control groups90, 1, 4, 5, 8, 9, 12, and 13.10

11

12

Figure 4.3.5.2.1-1 Gating with the R-FCH13

Traceability:14

[1] 2.1.3.1.11 Reverse Power Control Subchannel15[1] 2.1.3.2 Reverse Pilot Channel16[1] 2.1.3.7.8 Reverse Fundamental Channel17[4] 2.6.4.1.1.3, 3.7.3.3.2.25 Power Control Message18[4] 2.6.6.2.5.1, 3.6.6.2.2.12, 3.7.3.3.2.37 Extended Supplemental Channel Assignment Message19[4] 2.6.2.4, 2.6.3.3, 2.6.3.5, 3.6.3.3, 3.6.3.5, 3.7.2.3.2.21 Extended Channel Assignment Message20[4] 2.6.4.1.2, 2.6.4.1.2.2, 3.7.3.3.2.20, 3.7.5, 3.7.5.7, 3.7.5.20 Service Connect Message21

Applicability: RC 3 and greater22




TSG-C42 Page 4-35

10/19/2001 C.S0031

c. Setup a mobile station originated call using Service Option 32 (Test Data Service1Option) with rate 1500 bps only and set the REV_FCH_GATING_REQ field to ‘1’ in2the Origination Message.3

d. Instruct the base station to send the Extended Channel Assignment Message has the4parameters set as follows and set the REV_PWR_CNTL_DELAY field according to the5base station’s implementation.6


FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)



FPC_FCH_MAX_SETPT = ‘10000000’ (16 dB) REV_FCH_GATING_MODE = ‘1’

REV_PWR_CNTL_DELAY_INCL = ‘1’

8


f. Ensure the Reverse Fundamental Channel is transmitted at 1/8 rate.11

g. Monitor forward link FER at the mobile station.12



j. Verify the Reverse Fundamental Channel is in gated mode and the Reverse Pilot19Channel has a transmission duty cycle of 50%.20

k. Verify that the forward link FER on FCH is remaining in the target value.21

l. End the call at the mobile station.22

m. Repeat steps a through l except for the step d to set FOR_RC to 4 and REV_RC to 4.23

4.3.5.3 Minimum Standard24For all tests, the call shall not drop and the FCH FER shall remain at 1%±0.5%.25

4.3.6 Forward Power Control With EIB While Transmitting Frames on the Forward26Fundamental Channel27

4.3.6.1.1 Definition28This test shall be performed on the Forward Fundamental Channel with FPC_MODE equal to29‘011’. The mobile station shall set the EIB to ‘0’ in the second transmitted frame following the30

TSG-C42 Page 4-36

10/19/2001 C.S0031

detection of a good 20ms frame on the Forward Fundamental Channel. Otherwise the mobile1station shall set the EIB to ‘1’ in the second transmitted frame.2

Traceabilities:3

[1] 2.1.3.1.10.1 Reverse Power Control Subchannel Structure4[1] 2.2.2.2 Erasure Indicator Bit and Quality Indicator Bit5[4] 2.6.4.1.1 Forward Traffic Channel Power Control6[4] 3.7.2.3.2.21 Extended Channel Assignment Message7


a. Setup test as shown in Figure 4.3.1.3.1-1.9

b. Set power ratios and levels as specified in Table 4.3.6.1.2-3.1011

Table 4.3.6.1.2-3 Test Parameters for EIB test12

Parameter Unit Channel 1

Îor/Ioc dB 0

Pilot Ec/Ior dB -7



13

c. The Reverse Link attenuation should be set to balance the forward and reverse links14(approximately 90 dB).15

d. Setup a mobile station originated voice call.16

e. Instruct the base station to send the Extended Channel Assignment Message with17the parameters set as follows:18

19ASSIGN_MODE = ‘000’ or ‘100’ GRANTED_MODE = ‘10’

FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)

CH_IND = ‘01’

20

f. Instruct the base station to send the Service Connect Message with the parameters21set as follows:22




24

g. From the base station, send a sequence of good and bad frames (50 frames or more)25to the mobile station on the Forward Fundamental Channel (e.g. alternating good26and bad 20ms frames).27

TSG-C42 Page 4-37

10/19/2001 C.S0031

h. Check the received EIB at the base station against the corresponding frames1received at the mobile station.2

i. End the call.3

j. Repeat steps a through k except for the step d to set REV_RC to 3 and FOR_RC to 4.4

k. Repeat steps a through k except for the step d to set REV_RC to 4 and FOR_RC to 5.5

4.3.6.1.3 Minimum Standard6The EIB received at the base station shall follow the frame pattern sent from the base station to7the mobile station (i.e. a ‘0’ for a good frame and a ‘1’ for a bad frame).8

TSG-C42 Page 4-1

10/19/2001 C.S0031

123

TSG-C42 Page 4-2

10/19/2001 C.S0031

No text1

TSG-C42 Page 5-1

10/19/2001 C.S0031

5 REGISTRATION TESTS1Table 5-1 lists registration tests.2

Table 5-1 Registration Tests3

Test No. Title

5.1 Power-up Registration

5.2 Power-down Registration

5.3 Timer-Based Registration

5.4 Distance-Based Registration

5.5 Zone-Based Registration

5.6 Parameter-Change Registration

5.7 Registration Under Various Settings of MOB_TERM

Note: Unless otherwise noted, turn off all forms of registration, and set MAX_SLOT_CYCLE to4zero prior to beginning any Section 5 test.5

5.1 Power-Up Registration6

5.1.1 Definition7The mobile station maintains a power-up/initialization timer (T57M) (20 seconds). When the8timer is active, registration is not attempted.9


2.6.5.1.1: Power-Up Registration112.6.5.5.1.3: Entering the Mobile Station Idle State122.6.5.5.2.1: Idle Registration Procedures132.7.1.3.2.1: Registration Message143.6.5: Registration153.7.2.3.2.1: System Parameters Message16


5.1.2.1 Power-up Registration Disabled18

a. Setup test as shown in Figure 5.1.2.1-1. Disable power-up registration (set19POWER_UP_REG = 0 in the System Parameters Message).20

b. Power on the mobile station.21

c. Verify the mobile station does not attempt power-up registration for at least 122minute after the mobile station enters the Mobile Station Idle State.23

d. Power down the mobile station.2425

TSG-C42 Page 5-2

10/19/2001 C.S0031

1Figure 5.1.2.1-1 Functional Setup for Testing Power-up Registration2

5.1.2.2 Power-up Registration Enabled3

a. Connect the base station and mobile station as shown in Figure 5.1.2.1-1. Enable4power-up registration (set POWER_UP_REG = 1 in the Systems Parameters5Message).6


c. Verify the mobile station performs power-up registration no sooner than 20 seconds8(T57M) after entering Mobile Station Idle State.9

d. Setup a mobile station terminated call.10


e. Power down the mobile station.12


5.1.3.1 Power-up Registration Disabled14Power-up registration shall not occur.15

5.1.3.2 Power-up Registration Enabled16The mobile station shall perform the registration process when it is powered on and after the17power/initialization timer has expired.18

5.2 Power-Down Registration19

5.2.1 Definition20The mobile station shall not perform power-down registration if it has not previously registered21in the system corresponding to its current SIDs and NIDs. Registration can be enabled or22disabled.23

Traceability: (See [4] );242.6.5.1.1 Power-Up Registration252.6.5.1.2: Power-Down Registration26

TSG-C42 Page 5-3

10/19/2001 C.S0031

3.6.5: Registration13.7.2.3.2.1: System Parameters Message2


5.2.2.1 Power-down Registration Disabled4

a. Setup test as shown in Figure 5.1.2.1-1. Enable power-up registration (set5POWER_UP_REG = 1 in the Systems Parameters Message).6

b. Disable power-down registration (set POWER_DOWN_REG = 0 in the Systems7Parameters Message).8


d. Verify the mobile station performs a power-up registration.10


f. Verify power-down registration does not occur.12

5.2.2.2 Power-down Registration of a Currently Registered Mobile Station13

a. Connect the base station and mobile station as shown in Figure 5.1.2.1-1. Enable14power-up registration (set POWER_UP_REG = 1 in the Systems Parameters15Message).16

b. Enable power-down registration (set POWER_DOWN_REG = 1 in the Systems17Parameters Message).18


d. Verify power-up registration occurs.20


f. Verify power-down registration occurs.22

5.2.2.3 Power-down Registration of an Unregistered Mobile Station in New23System/Network24

a. Connect the base station and mobile station as shown in Figure 5.1.2.1-125


c. Verify power-up registration occurs.27

d. Disable all forms of registration.28

e. Enable power-down registration (set POWER_DOWN_REG = 1 in the Systems29Parameters Message).30

f. Change the SID/NID in the base station to a new SID/NID.31

g. Verify the mobile station does not register on the new SID/NID.32

h. Power down the mobile station.33

i. Verify power-down registration does not occur.34

TSG-C42 Page 5-4

10/19/2001 C.S0031


5.2.3.1 Power-down Registration Disabled2Power-down registration shall not occur.3

5.2.3.2 Power-down Registration of a Currently Registered Mobile Station4The mobile station shall perform power-down registration in a system/network where it is5currently registered.6

5.2.3.3 Power-down Registration of an Unregistered Mobile Station in a New System/Network7Power-down registration shall not occur in a system/network where the mobile station is not8currently registered.9

5.3 Timer-Based Registration10

5.3.1 Definition11Timer-based registration causes the mobile station to register at regular intervals controlled by12the base station System Parameters Message REG_PRD field. Registration can be enabled or13disabled. The registration interval is computed from the REG_PRD field using the following14equation:15

Registration interval = REG_COUNT_MAXs x .08 seconds = 2REG _ PRD

4

x .08 seconds16

Traceability: (See [4] );172.6.5.1.2: Power-Down Registration182.6.5.1.3: Timer-Based Registration193.6.5: Registration203.7.2.3.2.1: System Parameters Message21


5.3.2.1 Timer-based Registration Disabled23

a. Setup test as shown in Figure 5.1.2.1-1. Disable timer-based registration24(set REG_PRD = 0 in the Systems Parameters Message).25

b. Enable power-up registration (set POWER_UP_REG = 1 in the Systems Parameters26Message).27


d. Verify power-up registration occurs.29

e. Verify the mobile station does not perform timer-based registration.30

f. Power down the mobile station.31

5.3.2.2 Lowest Timer Value32

a. Setup test as shown in Figure 5.1.2.1-1. Disable power-up registration33(set POWER_UP_REG = 0 in the Systems Parameters Message).34

b. Set the value of REG_PRD to 29 (12.16 seconds).35

TSG-C42 Page 5-5

10/19/2001 C.S0031


d. Verify timer-based registration occurs.2

e. Setup a mobile station terminated call.3


g. Power down the mobile station.5

5.3.2.3 Mid-range Timer Value6

a. Setup test as shown in Figure 5.1.2.1-1. Disable power-up registration7(set POWER_UP_REG = 0 in the Systems Parameters Message).8

b. Set the value of REG_PRD to 38 (57.93 seconds).9


d. Verify timer-based registration occurs.11

e. Setup a mobile station terminated call.12




5.3.3.1 Timer-based Registration Disabled16Timer-based registration shall not occur.17

5.3.3.2 Lowest Timer Value18The mobile station shall perform timer-based registration at the interval specified by the19REG_PRD value.20

5.3.3.3 Mid-Range Timer Value21The mobile station shall perform time-based registration at the interval specified by the22REG_PRD value.23

5.4 Distance-Based Registration24

5.4.1 Definition25Distance-based registration causes a mobile station to register when the distance between the26current base station and the base station in which it last registered exceeds a threshold.27Registration can be enabled or disabled.28


2.6.5.1.1 Power-Up Registration30

2.6.5.1.4: Distance-Based Registration313.6.5 Registration323.7.2.3.2.1: System Parameters Message33

TSG-C42 Page 5-6

10/19/2001 C.S0031

5.4.2 Method of measurement1

5.4.2.1 Distance-Based Registration Disabled2

a. Setup the test as shown in Figure 5.4.2.1-1. Use the parameters in Table 5.4.2.1-1.3Configure base station #1 and base station #2 with different BASE_LAT and4BASE_LONG so that ∆ LAT and ∆ LONG are less than two minutes.5

b. Compute DISTANCE per the following formulas:6

DISTANCE =(∆lat )2 +(∆long )2

167

∆lat = BASE_LATS - BASE_LAT_REGS-P8

∆long = (BASE_LONGS - BASE_LONG_REGS-P) • cosπ

180

BASE_ LAT_REGS-P

14400

9

Note: BASE_LAT and BASE_LONG are given in units of 1/4 seconds.10

BASE_LAT/14400 and BASE_LONG/14400 are given in units of degrees.11

c. Enable power-up registration (set POWER_UP_REG = 1 in the Systems Parameters12Message).13

d. Disable distance-based registration (Set REG_DIST= 0 in the Systems Parameters14Message).15

e. Power on the mobile station on base station #1.16

f. Verify power-up registration occurs.17

g. Force the mobile station to perform an idle handoff to base station #2 by reducing18base station #2 forward link attenuation, then increasing base station #1 forward19link attenuation.20

h. Verify the mobile station does not perform distance-based registration.21

i. Power down the mobile station.22

23

TSG-C42 Page 5-7

10/19/2001 C.S0031

1

Figure 5.4.2.1-1 Functional Setup for Testing Distance-Based Registration23

Table 5.4.2.1-1 Soft Handoff Test Parameters - T_ADD4


Îor/Ioc dB 0 -10



Ioc dBm/1.23 MHz -75 -75


5

5.4.2.2 Distance Threshold Not Exceeded6


b. Compute DISTANCE per the formulas shown in test 5.4.2.1, step b.10

TSG-C42 Page 5-8

10/19/2001 C.S0031


d. Enable distance-based registration by setting REG_DIST greater than the calculated3value of DISTANCE.4

e. Power on the mobile station.5


g. Force the mobile station to perform an idle handoff to base station #2 by reducing7base station #2 forward link attenuation, then increasing base station #1 forward8link attenuation.9

h. Verify the mobile station does not perform distance-based registration.10


5.4.2.3 Distance Threshold Exceeded12


b. Compute DISTANCE per the formulas shown in test 5.4.2.1, step b.16


d. Enable distance-based registration by setting REG_DIST less than the calculated19value of DISTANCE.20



g. Force mobile station to perform idle handoff to base station #2 by reducing base23station #2 forward link attenuation, then increasing base station #1 forward link24attenuation.25

h. Verify distance-based registration occurs.26



5.4.3.1 Distance-based Registration Disabled29Distance-based registration shall not occur.30

5.4.3.2 Distance Threshold Not Exceeded31The mobile station shall not perform distance-based registration when distance-based registration32enabled (REG_DIST ≠ 0) and calculated value of DISTANCE is less than REG_DIST.33

TSG-C42 Page 5-9

10/19/2001 C.S0031

5.4.3.3 Distance Threshold Exceeded1The mobile station shall perform distance-based registration when distance based registration is2enabled (REG_DIST ≠ 0) and the calculated value of DISTANCE is greater than REG_DIST.3

5.5 Zone-Based Registration4

5.5.1 Definition5This test verifies that zone-based registration can be enabled and disabled, and that, when zone-6based registration is enabled, a mobile shall register when it performs an idle handoff into a zone7that is not on its internally stored list of visited registration zones.8This test verifies that a mobile station shall not register when it performs an idle handoff into a9zone that is on its internally stored list of visited zones, and that it properly deletes entries from10its internally stored list of visited registration zones.11

Traceability: (See [4] );122.6.5.1.1 Power-Up Registration132.6.5.1.5: Zone-Based Registration143.6.5: Registration153.7.2.3.2.1: System Parameters Message16

5.5.1.1 Zone-Based Registration Disabled17

a. Setup test as shown in Figure 5.4.2.1-1. Configure base station #2 with REG_ZONE18different than that of base station #1.19


c. Disable zone-based registration (set TOTAL_ZONES = 0 in the Systems Parameters22Message).23

d. Power on the mobile station on base station #1.24

e. Force mobile station to perform idle handoff to base station #2 by reducing base25station #2 forward link attenuation, then increasing base station #1 forward link26attenuation.27

f. Verify zone-based registration does not occur.28


5.5.1.2 Zone-Based Registration Enabled30

a. Setup test as shown in Figure 5.4.2.1-1. Configure base station #2 with REG_ZONE31different from that of base station #1.32


c. Enable zone-based registration with a two-zone ZONE_LISTs (set TOTAL_ZONES = 235in the Systems Parameters Message).36


TSG-C42 Page 5-10

10/19/2001 C.S0031

e. Verify power-up registration occurs. The mobile station is now registered in zone 11and Zone 1 is the only entry in ZONE_LISTs.2

f. Force the mobile station to perform an idle handoff to base station #2 by reducing3base station #2 forward link attenuation, then increasing base station #1 forward4link attenuation.5

g. Verify zone-based registration occurs. The mobile station is now registered in zone62, Zone 1 and zone 2 are in ZONE_LISTs.7

h. Before the period of time specified by ZONE_TIMER has elapsed (before the mobile8station deletes zone 1 from ZONE_LISTs), force the mobile station to perform an idle9handoff to base station #1.10

i. Verify zone-based registration does not occur (because zone 1 is still in11ZONE_LISTs).12

j. Power down the mobile station.13

k. Enable zone-based registration with a single-entry ZONE_LISTs by setting14TOTAL_ZONES = 1.15

l. Power on the mobile station on base station #1.16

m. Verify power-up registration occurs. The mobile station is now registered in zone 1,17and zone 1 is the only entry in ZONE_LISTs.18

n. Before the period of time specified by ZONE_TIMER has elapsed (i.e., before the19mobile station deletes zone 1 from ZONE_LISTs due to expiration of the entry timer20for zone 1), force the mobile station to perform an idle handoff to base station #2.21

o. Verify zone-based registration occurs. The mobile station is now registered in zone222, and only zone 2 is in ZONE_LISTs because the mobile station was forced to delete23zone 1 from ZONE_LISTs to make room for zone 2.24

p. Force the mobile station to perform an idle handoff to base station #1.25

q. Verify zone-based registration occurs (zone 1 is not in ZONE_LIST).26

r. Power down the mobile station.27

5.5.1.3 Zone-Based Registration Timer28

a. Setup test as shown in Figure 5.4.2.1-1. Configure base station #2 with REG_ZONE29different than that of base station #1.30

b. Enable power-up registration (set POWER_UP_REG = 1 in the Systems Parameters31Message)32

c. Enable zone-based registration with a two-zone ZONE_LISTs33(set TOTAL_ZONES = 2 in the Systems Parameters Message).34


e. Verify power-up registration occurs. The mobile station is now registered in zone 1,36and zone 1 is the only entry in ZONE_LISTs.37

TSG-C42 Page 5-11

10/19/2001 C.S0031

f. Force the mobile station to perform an idle handoff to base station #2.1

g. Verify zone-based registration occurs. The mobile station is now registered in zone22, and zone 1 and zone 2 are on ZONE_LISTs.3

h. Wait for the period of time specified by ZONE_TIMER to elapse (after which the4mobile station should delete zone 1 from ZONE_LISTs).5

i. Force the mobile station to perform an idle handoff to base station #1.6

j. Verify zone-based registration occurs.7



5.5.2.1 Zone-Based Registration Disabled10Zone-based registration shall not occur.11

5.5.2.2 Zone-Based Registration Enabled12The mobile station shall perform zone-based registration after performing an idle handoff into a13registration zone that is not currently in its ZONE_LIST (5.5.2.2 steps g, o, and q). The mobile14station shall not perform zone-based registration after performing an idle handoff into a15registration zone that is currently in its ZONE_LIST (5.5.2.2 step i).16

5.5.2.3 Zone-Based Registration Timer17The mobile station shall perform zone-based registration after performing an idle handoff into a18registration zone that has been deleted from its ZONE_LIST due to expiration of the zone entry19timer.20

5.6 Parameter-Change Registration21

5.6.1 Definition22Parameter-change registration causes a mobile station to register when it modifies any of the23following stored parameters:24

• The preferred slot cycle index (SLOT_CYCLE_INDEX)25

• The station class mark (SCM) (Not applicable to single mode CDMA 1900 mobile stations)26

• The call termination enabled indicator (MOB_TERM)27Parameter-change registration is performed whenever there is no entry in the mobile station’s28SID_NID_LISTs matching the base station’s SID and NID.29

Traceability: (See [4] );302.6.5.1.6: Parameter-Change Registration313.6.5: Registration323.7.2.3.2.1: System Parameters Message33

TSG-C42 Page 5-12

10/19/2001 C.S0031


5.6.2.1 Parameter-Change Registration Disabled2


b. Disable parameter-change registration (set PARAMETER_REG = 0 in the Systems4Parameters Message).5


d. Reset the value of SLOT_CYCLE_INDEX.7

e. Verify parameter-change registration does not occur.8


5.6.2.2 Parameter-Change Registration Per SLOT_CYCLE_INDEX10


b. Enable parameter-change registration (set PARAMETER_REG = 1 in the Systems12Parameters Message).13


d. Reset the value of SLOT_CYCLE_INDEX.15

e. Verify parameter-change registration occurs.16


5.6.2.3 Parameter-Change Registration Per SCM18




d. Reset the value of SCM.23


f. Setup a mobile station terminated call.25

g. Verify user data in both directions.26

h. Power down mobile station.27

5.6.2.4 Parameter-Change Registration Per MOB_TERM28




TSG-C42 Page 5-13

10/19/2001 C.S0031

d. Change the value of MOB_TERM_HOMEp.1



5.6.2.5 Parameter-Based Registration per SID-NID List change4



c. Make an entry in the mobile station SID_NID_LISTs to match the base station8SID,NID.9

d. Set MULT_SIDS = MULT_NIDS= 0 in the System Parameters Message.10


f. Wait for mobile station to acquire CDMA service.12

g. At the base station, change the SID and NID in the System Parameters Message.13

h. Verify parameter-change registration occurs.14

i. Setup a mobile station terminated call.15

j. Verify user data in both directions.16


5.6.3 Minimum Standard18The mobile station shall register when certain stored parameters change or when it enters a new19system.20

5.7 Registration Under Various Settings of MOB_TERM21

5.7.1 Definition22This test verifies that the mobile station correctly performs registration using stored parameters23MOB_TERM_FOR_NID, MOB_TERM_FOR_SID, MOB_TERM_HOME and HOME_REG,24FOR_NID_REG, and FOR_SID_REG fields of the System Parameters Message.25

Traceability: (See [4] );262.6.5.1.2 Power-Up Registration272.6.5.1.6: Parameter-Change Registration282.6.5.3: Roaming292.6.5.5.2.1: Idle Registration Procedures303.6.5: Registration313.7.2.3.2.1: System Parameters Message32


5.7.2.1 MOB_TERM Enabled34


TSG-C42 Page 5-14

10/19/2001 C.S0031

b. Enable Home, (set HOME_REG=1) Foreign SID (set FOR_SID=1) and Foreign NID1(set FOR_NID=1) registration at the base station.2

c. Enable parameter-change (set PARAMETER REG=1) and power-down registration3(set POWER-DOWN REG=1) at the base station.4

d. Set the mobile station SID to match the base station SID.5


f. Set MOB_TERM_HOME to enabled on the mobile station.7

g. Set MOB_TERM_FOR_NID and MOB_TERM_FOR_SID to disabled at the mobile8station.9

h. Verify the mobile station parameter-change registration occurs.10


j. Verify the mobile station power-down registration occurs.12

5.7.2.2 MOB_TERM Disabled13


b. Enable Home, (set HOME_REG=1) Foreign SID (set FOR_SID=1) and Foreign NID15(set FOR_NID=1) registration at the base station.16

c. Enable parameter-change (set PARAMETER REG=1) and power-down registration17(set POWER-DOWN_REG=1) at the base station.18

d. Power on the mobile station.19

e. Set MOB_TERM_HOME, MOB_TERM_FOR_SID and MOB_TERM_FOR_NID to20disabled at the mobile station.21

f. Verify parameter-change registration occurs.22


h. Verify power-down registration does not occur.24


5.7.3.1 MOB_TERM Enabled26The mobile station shall perform parameter-change registration after MOB_TERMs is enabled.27The mobile station shall perform power-down registration.28

5.7.3.2 MOB_TERM Disabled29The mobile station shall perform parameter-change registration after MOB_TERMs is disabled.30The mobile station shall not perform power-down registration.31

32

TSG-C42 Page 5-15

10/19/2001 C.S0031

No text1

TSG-C42 Page 6-1

10/19/2001 C.S0031

6 AUTHENTICATION TESTS1Table 6-1 lists authentication tests.2

Table 6-1 Authentication Tests3

Test No. Title

6.1 Shared Secret Data Initialized to Zero

6.2 Shared Secret Data Update on the Paging/Access Channels

6.3 Shared Secret Data Update on the Forward/ Reverse Traffic Channels

6.4 Mismatched A-Keys

6.5 Activating Voice Privacyon Call Setup

6.6 Activating Voice Privacy at the Mobile Station When a Call Is Active

6.7 Signaling Message Encryption on Forward Traffic Channel(Alert with Information Message)

6.8 Signaling Message Encryption on Reverse Traffic Channel(Burst DTMF Message)

6.9 Hard Handoffs between Base Stations with SME Active.

6.10 Signaling Message Encryption for Mobile Terminated SMS(Data Burst Message)

6.11 Authentication Upon Originations

6.12 Hard Handoff from CDMA to AMPS with SME Active

Note: Unless otherwise noted, AUTH should be set to ‘01’ in the Access Parameters Message.4

6.1 Shared Secret Data Initialized to Zero5

6.1.1 Definition6This test verifies that when the A-Key is changed at both the base station and mobile station,7mobile station Shared Secret Data (SSD) and base station SSD are initialized to zero until an8SSD Update is performed. Authentication of mobile station registrations, originations, and9terminations should be successful.10

Traceability: (See [4] );112.3.12.1: (MS) Authentication122.6.5.1.3: Timer-Based Registration133.3.1: (BS) Authentication14

15




c. Initialize the A-Key to the same value in the mobile station and base station.19

TSG-C42 Page 6-2

10/19/2001 C.S0031

1Figure 6.1.2-1 Functional Setup for Authentication Tests2

3

d. Enable timer-based registration (REG_PRD=29).4

e. Verify the mobile station sends a Timer-Based Registration Message, which includes5AUTHR, RANDC and COUNT.6

f. At the base station, verify authentication of registration is successful.7



i. End call.10

j. Make a land party to mobile station call.11

k. Verify the call completes.12

l. At the base station, initiate a Unique Challenge-Response Procedure on the Traffic13Channel.14

m. Verify the Unique Challenge-Response Procedure was successful.15

n. End call.16

o. At the base station, initiate a Unique Challenge-Response Procedure on the Paging17Channel.18

p. Verify the Unique Challenge-Response Procedure was successful.19

q. Power down the mobile station.20

6.1.3 Minimum Standard21When the A-Key is changed in the mobile station and base station, Shared Secret Data shall be22initialized to zero.23Authentication of mobile station registrations, originations, and terminations shall be successful.24The Unique Challenge-Response Procedure shall be successful.25

TSG-C42 Page 6-3

10/19/2001 C.S0031

6.2 Shared Secret Data Update on the Paging/Access Channels1

6.2.1 Definition2This test verifies the mobile station and base station can perform a Shared Secret Data update on3the paging/access channels.4

Traceability: (See [4] );52.3.12.1.4: Unique Challenge-Response Procedure62.3.12.1.5: Updating the Shared Secret Data (SSD)72.6.5.1.3: Timer-Based Registration82.7.1.3.2.6: Authentication Challenge Response Message93.7.2.3.2.1: System Parameters Message (f-csch)103.7.2.3.2.10: Authentication Challenge Message (f-csch)11




c. Initialize the A-Key to the same value in both the mobile station and base station.15

d. At the base station, initiate a Shared Secret Data update on the Paging/Access16Channels.17

e. Verify the SSD Update was successful.18

f. Enable timer-based registration (REG_PRD=29).19

g. Wait for the mobile station to send the Timer-Based Registration Message.20

h. Verify the Registration Message includes AUTHR, COUNT and RANDC.21

i. At the base station, verify authentication of registration is successful.22

j. Setup a mobile station originated call.23

k. Verify user data in both directions.24

l. At the base station, initiate a Unique Challenge-Response Procedure on the Traffic25Channel.26

m. Verify the Unique Challenge-Response Procedure was successful.27

n. End call.28

o. At the base station, initiate a Unique Challenge-Response Procedure on the Paging29Channel.30

p. Verify the Unique Challenge-Response Procedure was successful.31

q. Power down the mobile station.32

6.2.3 Minimum Standard33The mobile station and base station shall successfully perform an SSD Update on the34Paging/Access Channels.35SSD_A_NEW and SSD_B_NEW shall be stored at the mobile station and base station.36Authentication of mobile station registrations, originations, and terminations shall be successful.37

TSG-C42 Page 6-4

10/19/2001 C.S0031

6.3 Shared Secret Data Update on the Forward/Reverse Traffic Channels1

6.3.1 Definition2This test verifies the mobile station and base station can perform a shared secret data update on3the forward/reverse traffic channels.4

Traceability: (See [4] );52.3.12.1.4: Unique Challenge-Response Procedure62.3.12.1.5: Updating the Shared Secret Data (SSD)72.7.2.3.2.2: Authentication Challenge Response Message (r-dsch)82.6.5.1.3: Timer-Based Registration93.7.3.3.2.2: Authentication Challenge Message (f-dsch)103.7.3.3.2.13: SSD Update Message (f-dsch)11

12





d. Setup a mobile station terminated call.17


f. At the base station, initiate a Shared Secret Data update on the Forward/Reverse19Traffic Channels.20

g. Verify the SSD Update was successful.21

h. End call.22

i. Enable timer-based registration (REG_PRD=29).23

j. Wait for the mobile station to send the Timer-Based Registration Message.24

k. Verify the Registration Message includes AUTHR, COUNT and RANDC.25

l. At the base station, verify authentication of registration is successful.26

m. Setup a mobile station originated call.27

n. Verify user data in both directions.28

o. End call.29

p. Setup a mobile station terminated call.30

q. Verify user data in both directions.31

r. At the base station, initiate a Unique Challenge-Response Procedure on the Traffic32Channel.33

s. Verify the Unique Challenge-Response Procedure was successful.34

t. End call.35

TSG-C42 Page 6-5

10/19/2001 C.S0031

u. At the base station, initiate a Unique Challenge-Response Procedure on the Paging1Channel.2

v. Verify the Unique Challenge-Response Procedure was successful.3

w. Power down the mobile station.4

6.3.3 Minimum Standard5The mobile station and base station shall successfully perform an SSD Update on the6Forward/Reverse Traffic Channels. SSD_A_NEW and SSD_B_NEW shall be stored at both the7mobile station and the base station.8

6.4 Mismatched A-Keys9

6.4.1 Definition10This test verifies that when there is an A_KEY mismatch, authentication of registrations,11originations, terminations, and Unique Challenge-Response procedures will fail.12

Traceability: (See [4] );132.3.12.1.4: Unique Challenge-Response Procedure142.3.12.1.5: Updating the Shared Secret Data (SSD)152.7.1.3.2.6: Authentication Challenge Response Message162.7.2.3.2.2: Authentication Challenge Response Message (r-dsch)173.7.2.3.2.10: Authentication Challenge Message (f-csch)183.7.2.3.2.11: SSD Update Message (f-csch)193.7.3.3.2.2: Authentication Challenge Message (f-dsch)203.7.3.3.2.13: SSD Update Message (f-dsch)21




c. Initialize the A-Key to the same value in the mobile station and base station.25

d. At the base station, initiate a Shared Secret Data update on the Paging/Access26Channels.27



g. End call.30

h. Change the A-Key in the mobile station.31

i. Enable timer-based registration (REG_PRD=29)32

j. Wait for the mobile station to send a Timer-Based Registration Message.33

k. Verify the Registration Message includes AUTHR, COUNT and RANDC.34

l. At the base station, verify authentication of registration fails due to an AUTHR35mismatch.36


TSG-C42 Page 6-6

10/19/2001 C.S0031

n. Verify the mobile station receives an Intercept Order and that the call fails due to an1AUTHR mismatch.2

o. Ensure the intercept tone sounds as alternating 440 Hz and 620 Hz tones, each on3for 250 ms. The mobile station should not do any silent re-originations after4receiving an intercept order.5

p. Setup a mobile station terminated call.6

q. Verify the call fails due to an AUTHR mismatch.7

r. At the base station, initiate a Shared Secret Data update on the Paging/Access8channels.9

s. Verify the SSD Update fails with an AUTHBS mismatch.10

t. At the base station, initiate a Unique Challenge-Response Procedure on the11Paging/Access channels.12

u. Verify the Unique Challenge-Response Procedure fails with an AUTHU mismatch.13

v. Power down the mobile station14

6.4.3 Minimum Standard15When there is an A-Key mismatch between the base station and mobile station, authentication of16registrations, originations, terminations, and Unique Challenge-Response procedures shall fail.17When the mobile station receives an intercept order it shall play the proper tone and should not18silently re-originate.19

6.5 Activating Voice Privacy on Call Setup20

6.5.1 Definition21This test verifies that Voice Privacy can be activated at call setup by the mobile station22subscriber. The Voice Privacy feature can be activated and deactivated by either the mobile23station subscriber or the base station.24

Traceability: (See [4] );252.3.12.3: (MS) Voice Privacy262.6.4.1.6: (MS) Long Code Transition Request Processing272.7.1.3.2.4: Origination Message282.7.1.3.2.5: Page Response Message292.7.3: (MS) Orders303.3.3: (BS) Voice Privacy313.6.4.1.5: (BS) Long Code Transition Request Processing323.6.4.3: Traffic Channel Substate333.6.4.4: Release Substate343.7.4: (BS) Orders35


a. Connect the base station and mobile station as shown in Figure 6.1.2-137

b. Ensure Authentication is enabled.38


TSG-C42 Page 6-7

10/19/2001 C.S0031

d. Enable Voice Privacy in the mobile station and base station.1

e. Setup a mobile station originated call, and verify in the Origination Message the2Voice Privacy Mode Indicator is set to '1'.3

f. Configure the Base station to send a Long Code Transition Request Order4(ORDQ='00000001') on the traffic channel.5

g. Verify the mobile station responds with a Long Code Transition Response Order6(ORDQ='00000011')7

h. If supported on the user interface, verify the mobile station indicates to the user8that Voice Privacy is active.9


j. End call.11

k. Setup a mobile station terminated call, and verify in the Page Response Message the12voice privacy indicator (PM) is set to 1 then repeat steps d through j.13

6.5.3 Minimum Standard14The mobile station shall respond with a Long Code Transition Response Order15(ORDQ='00000011') when activated during call setup.16

6.6 Activating Voice Privacy at the Mobile Station When a Call Is Active17

6.6.1 Definition18This test verifies that Voice Privacy can be activated at the mobile station when a call is active.19

Traceability: (See [4] );202.3.12.3: (MS) Voice Privacy212.6.4.1.6: Long Code Transition Request Processing222.7.1.3.2.4: Origination Message232.7.1.3.2.5: Page Response Message242.7.3: (MS) Orders253.3.3: (BS) Voice Privacy263.6.4.1.5: (BS) Long Code Transition Request Processing273.6.4.3.1: Traffic Channel Substate283.6.4.4: Release Substate293.7.4: (BS) Orders30

31



b. Enable Voice Privacy in the base station.34

c. Ensure Authentication is enabled.35



TSG-C42 Page 6-8

10/19/2001 C.S0031

f. Enable voice privacy at the mobile station. Verify the mobile station sends a Long1Code Transition Request Order with ORDQ set to ‘00000001’.2

g. Verify the base station responds by sending a Long Code Transition Request Order3with ORDQ set to ‘00000001’.4

h. Verify the mobile station responds with a Long Code Transition Response Order5(ORDQ='00000011').6

i. If supported on the user interface, verify the mobile station indicates Voice Privacy7is active.8


k. End call.10

6.6.3 Minimum Standard11Voice Privacy shall function correctly on the mobile station when a call is active.12

6.7 Signaling Message Encryption on Forward Traffic Channel (Alert with Information13Message)14

6.7.1 Definition15This test verifies that Signaling Message Encryption can be applied to certain fields of selected16traffic channel messages such as Alert with Information Message.17

Traceability: (See [4] );182.3.12.2: (MS) Signaling Message Encryption192.7.4.4: (MS) Calling Party Number203.3.2: (BS) Encryption213.7.2.3.2.8: Channel Assignment Message (f-csch)223.7.3.3.2.3: Alert With Information Message (f-dsch)233.7.5.3: (BS) Calling Party Number24



b. Activate the Calling Party Number (CPN) feature for the mobile station subscriber.27



e. Enable Signaling Message Encryption on the base station.30

f. Setup a land to mobile station call, or a mobile station to mobile station call.31

g. Verify ENCRYPT_MODE='01' in the Channel Assignment Message.32

h. Verify that the ENCRYPTION field is set to ‘01’ in the Layer 3 messages that should33be encrypted.34

i. Verify the CPN is displayed on the mobile station during the alerting state.35


TSG-C42 Page 6-9

10/19/2001 C.S0031

k. End call.1

6.7.3 Minimum Standard2When Signaling Message Encryption is activated, CPN sensitive data shall be encrypted when3sent on the traffic channel.4

6.8 Signaling Message Encryption on Reverse Traffic Channel (Burst DTMF Message)5

6.8.1 Definition6This test verifies that Signaling Message Encryption can be applied to certain fields of selected7traffic channel messages such as Burst DTMF Message.8

Traceability: (See [4] );92.3.12.2: (MS) Signaling Message Encryption102.7.2.3.2.7: Send Burst DTMF Message113.3.2: (BS) Encryption123.7.2.3.2.8: Channel Assignment Message (f-csch)13



b. Ensure Authentication is enabled.16


d. Configure the mobile station to send a Send Burst DTMF Message.18


f. Setup a mobile station call to a voice mail system or a paging system.20

g. Verify ENCRYPT_MODE='01' on the Channel Assignment Message.21

h. Enter the appropriate pin code as burst DTMF tones.22

i. Verify that either the voice mail system recognizes the DTMF tones and plays the23message back, or that the paging system accepts the pin and sends out the page.24

j. End call.25

6.8.3 Minimum Standard26When Signaling Message Encryption is activated, Send Burst DTMF Message data shall be27encrypted when sent on the traffic channel.28

6.9 Hard Handoffs between Base Stations with SME Active.29

6.9.1 Definition30This test verifies that when Signaling Message Encryption is used, the new base station activates31ENCRYPT_MODE.32

Traceability: (See [4] );332.3.12.2: (MS) Signaling Message Encryption342.6.6.2.8: CDMA-to-CDMA Hard Handoff352.7.4.4: (MS) Calling Party Number.36

TSG-C42 Page 6-10

10/19/2001 C.S0031

3.3.2: (BS) Encryption13.6.6.2.2.2: Extended Handoff Direction Message (call processing).23.6.6.2.2.10: General Handoff Direction Message (call processing).33.6.6.2.2.11: Universal Handoff Direction Message (call processing).43.7.2.3.2.8: Channel Assignment Message (f-csch)53.7.3.3.2.14: Flash With Information Message (f-dsch).63.7.3.3.2.17: Extended Handoff Direction Message (f-dsch).73.7.3.3.2.31: General Handoff Direction Message (f-dsch).83.7.3.3.2.36: Universal Handoff Direction Message (f-dsch).93.7.5.3: (BS) Calling Party Number.10



b. Activate Call Waiting and Caller ID on Base station #2.13



e. Enable Signaling Message Encryption on both base stations.16




i. Perform a hard handoff from Base station #1 to Base station #2.20

j. Verify ENCRYPT_MODE='01' in the Handoff Direction Message.21

k. Setup another call to the mobile station, and listen for the Call Waiting tone.22

l. Verify base station #2 sends a Flash with Information Message with23ENCRYPTION='01'.24

m. Verify Calling Party Number (CPN) is displayed on mobile station during alerting25state.26


o. End call.28

29

TSG-C42 Page 6-11

10/19/2001 C.S0031

1

Figure 6.9.2-1 Functional Setup for Hard Handoffs between Base Stations with SME2Active3

6.9.3 Minimum Standard4When Signaling Message Encryption is activated, sensitive data is encrypted and sent on the5traffic channel. When an active call is handed off from base station #1 to base station #2, or6another sector the SME mode is passed on to the base station or sector to which the call has been7handed off.8

6.10 Signaling Message Encryption Mobile Terminated SMS (Data Burst Message)9

6.10.1 Definition10This test verifies that Signaling Message Encryption, can be applied to certain fields of selected11traffic channel messages such as Data Burst Messages.12

Traceability: (See [4] );132.3.12.2: Signaling Message Encryption143.3.2: Encryption153.7.2.3.2.8: Channel Assignment Message (f-csch)16

(See [13] );172.4.1.1.1.1: Mobile SMS Message Termination182.4.2.1.1: Paging Channel Procedures19

TSG-C42 Page 6-12

10/19/2001 C.S0031



b. Activate the Short Message Service (SMS) feature for the mobile station subscriber.3

c. Delete all outstanding short messages in the network for the mobile station.4

d. Ensure Authentication is enabled.5


f. Power on the mobile station, and wait until it is in Mobile Station Idle State.7

g. Store a short message in the Message Center for the mobile station. Ensure the8message is big enough so that the message can not be sent on the Paging channel9and the message has to be sent on the Traffic channel.10

h. Verify the base station sends a Data Burst Message with ENCRYPTION='01'.11

i. Verify the mobile station successfully receives the short message.12

6.10.3 Minimum Standard13The base station shall send a short message over the traffic channel using the Data Burst14Message with Signaling Message Encryption activated. The correct and complete short message15shall be received by the mobile station.16

6.11 Authentication Upon Originations17

6.11.1 Definition18This test verifies the mobile station can successfully Authenticate upon originations.19

Traceability: (See [4] );202.3.12.1.5: Updating the Shared Secret Data (SSD)212.7.1.3.2.6: Authentication Challenge Response Message222.7.2.3.2.2: Authentication Challenge Response Message (r-dsch)233.7.2.3.2.10: Authentication Challenge Message (f-csch)243.7.2.3.2.11: SSD Update Message (f-csch)253.7.3.3.2.2: Authentication Challenge Message (f-dsch)263.7.3.3.2.13: SSD Update Message (f-dsch)27





d. At the base station, initiate a Shared Secret Data update on the Paging Channel.32

e. Verify the SSD Update was successful.33

f. Setup a mobile station originated call (seven digits).34

g. Verify user data in both directions and that Authentication is successful.35

h. End call.36

TSG-C42 Page 6-13

10/19/2001 C.S0031

i. Setup a mobile station originated call (three digits such as *73).1

j. Verify user data in both directions and Authentication is successful.2

k. End call.3

l. Setup a mobile station originated call (four digits such as *123).4

m. Verify user data in both directions and that Authentication is successful.5

n. End call and Power down the mobile station.6

6.11.3 Minimum Standard7Authentication of all Mobile Station Originations shall be successful.8

6.12 Hard Handoff from CDMA to AMPS with SME Active9

6.12.1 Definition10This test verifies that when Signaling Message Encryption is used, the new base station activates11Analog Signaling Message Encryption.12

Traceability: (See [4] );132.3.12.2: (MS) Signaling Message Encryption142.6.6.2.9: CDMA-Analog HO152.7.4.4: (MS) Calling Party Number.163.3.2: (BS) Encryption173.6.4.3: Traffic Channel Substate183.7.2.3.2.8: Channel Assignment Message (f-csch)193.7.3.3.2.3: Alert with Information Message (f-dsch)203.7.3.3.2.6: Analog Handoff Direction Message213.7.5.3: (BS) Calling Party Number.22



b. Activate Call Waiting and Caller ID on Base station #2.25



e. Enable Signaling Message Encryption on both base stations.28




i. Perform a CDMA to AMPS hard handoff from Base station #1 to Base station #2.32

j. Verify ENCRYPT_MODE='01' and MEM=’1’ in the Analog Handoff Direction Message.33

k. Setup another call to the mobile station, and listen for the Call Waiting tone.34

l. Verify base station #2 sends an encrypted Alert with Information Message (AMPS).35

TSG-C42 Page 6-14

10/19/2001 C.S0031

m. Verify the Calling Party Number (CPN) is displayed on the mobile station during the1alerting state.2


o. End call.4

6.12.3 Minimum Standard5When Signaling Message Encryption is activated, sensitive data is encrypted and sent on the6traffic/voice channels. When an active call is handed off from base station #1 to base station #2,7or another sector, the SME mode is passed on to the base station or sector to which the call has8been handed off.9

10

TSG-C42 Page 6-15

10/19/2001 C.S0031

No text1

TSG-C42 Page 7-1

10/19/2001 C.S0031

7 SERVICE REDIRECTION1Table 7-1 lists service redirection tests.2

Table 7-1 Service Redirection Tests3

Test No. Title

7.1 Global Service Redirection Tests

7.1.1 Global Service Redirection between Band Classes

7.1.2 Global Service Redirection from CDMA to a Non-CDMA System

7.1.3 Global Service Redirection to a Different Channel in the Same Band Class

7.2. Network Directed System Selection (NDSS) and Service Redirection Tests

7.2.1 NDSS Between Band Classes

7.2.2 NDSS and Normal Service Redirection to a Non-CDMA System

7.2.3 NDSS between Channels in the Same Band Class

7.2.4 NDSS Ignore CDMA

7.2.5 NDSS Return If Fail

7.3 Extended Global Service Redirection Tests

7.3.1 Extended Global Service Redirection between Band Classes

7.3.2 Extended Global Service Redirection from CDMA to a Non-CDMA System

7.3.3 Extended Global Service Redirection to a Different Channel in the SameBand Class

4When the mobile station receives a Service Redirection Message, Global Service Redirection5Message, or an Extended Global Service Redirection the mobile shall attempt to select another6system in accordance with the current redirection criteria.7

7.1 Global Service Redirection Tests8

7.1.1 Global Service Redirection between Band Classes.9

7.1.1.1 Definition10This test verifies that when a mobile station receives a Global Service Redirection Message11directing it to another band class, the mobile station acquires the appropriate system.12

Traceabilities (See [4])13

142.6.1.1.2 System Selection Using Current Redirection Criteria152.6.2.2 Response to Overhead Information Operation162.6.2.2.6 Global Service Redirection Message173.7.2.3.2.1 System Parameters Message183.7.2.3.2.18 Global Service Redirection Message19

TSG-C42 Page 7-2

10/19/2001 C.S0031


a. Connect the mobile station to the base station as shown in Figure 7.1.1.2-1. For2this test case, base station #1 and base station #2 are in different band classes.3

4

5

Figure 7.1.1.2-1 Functional Setup for Service Redirection Tests67

b. Verify the mobile station is operating in the Mobile Station Idle State on base station8#1.9

c. Send a Global Service Redirection Message from the current base station with the10correct values of BAND_CLASS, EXPECTED_SID, EXPECTED_NID, NUM_CHAN,11and CDMA_CHAN for the new base station along with the following parameters:12

13Field Value

REDIRECT_ACCOLC ACCOLCp

EXCL_P_REV_MS ‘0’

RECORD_TYPE ‘00000010’

14

d. Verify the mobile station enters the System Determination Substate of the mobile15station Initialization State and acquires the system to which it was redirected.16

TSG-C42 Page 7-3

10/19/2001 C.S0031

e. Setup a mobile station originated call. Verify user data in both directions.1

f. End the call.2

g. Verify the mobile station does not acquire the system from which it was redirected.3

h. Power off the mobile station.4

i. Repeat steps c through h with the mobile station operating in the Mobile Station Idle5State on base station #2.6

j. Repeat steps b and c with the mobile station operating in the Mobile Station Idle7State on base station #1 with the following modifications to the Global Service8Redirection Message:9

10Field Value


EXCL_P_REV_MS ‘1’11

k. If MOB_P_REV is less than six, verify the mobile station enters the System12Determination Substate of the Mobile Station Initialization State and acquires the13system to which it was redirected. If MOB_P_REV is greater than or equal to six,14verify the mobile station ignores the Global Service Redirection Message and remains15in the Mobile Station Idle State on the current system.16

7.1.2 Minimum Standard17The mobile station shall acquire the system to which it was directed and successfully originate a18call on the new system unless MOB_P_REVp is greater than or equal to six and19EXCL_P_REV_MS is equal to ‘1’.20

7.1.3 Global Service Redirection from CDMA to a Non-CDMA System21

7.1.3.1 Definition22This test verifies that when a mobile station receives a Global Service Redirection Message23directing it from CDMA to a Non-CDMA system, the mobile station acquires that system. The24mobile station should only be redirected to Non-CDMA systems it supports. An example would25be an analog system defined in [21].26

Traceabilities (see [4])27



a. Connect the mobile station to the base station as shown in Figure 7.1.1.2-1. For this34test case, base station #1 is a CDMA base station and base station #2 is a Non-CDMA35base station36

TSG-C42 Page 7-4

10/19/2001 C.S0031

b. Verify the mobile station is operating in the Mobile Station Idle State on base station #1.1

c. Send a Global Service Redirection Message from the current base station with the2correct values of EXPECTED_SID for the new base station along with the following3parameters:4

5Field Value



RECORD_TYPE '00000001' [NorthAmerican Amps]

'00000011' [TACS]

'00000100' [JTACS]

6

Verify the mobile station enters the System Determination Substate of the Mobile Station7Initialization State and acquires the system to which it was redirected.8

Setup a mobile station originated call. Verify user data in both directions.9

End the call.10

Verify the mobile station does not acquire the system from which it was redirected.11

Power off the mobile station.12

Repeat steps b and c with the following changes to the Global Service Redirection Message:1314

Field Value



15

If MOB_P_REV is less than six, verify the mobile station enters the System Determination16Substate of the Mobile Station Initialization State and acquires the system to which it was17redirected. If MOB_P_REV is greater than or equal to six, verify the mobile station ignores the18Global Service Redirection Message and remains in the Mobile Station Idle State on the current19system.20

7.1.3.3 Minimum Standard21The mobile station shall acquire the system to which it was directed and successfully originate a22call on the new system unless MOB_P_REVp is greater than or equal to six and23EXCL_P_REV_MS is equal to ‘1’.24

TSG-C42 Page 7-5

10/19/2001 C.S0031

7.1.4 Global Service Redirection to a Different Channel in the Same Band Class.1

7.1.4.1 Definition2This test verifies that when a mobile station receives a Global Service Redirection Message3directing it to a different channel in the same band class, the mobile station acquires the4appropriate system.5

Traceabilities (see [4])6



d. Connect the mobile station to the base station as shown in Figure 7.1.1.2-1. For this13test case, base station #1 and base station #2 are in the same band class with different14CDMA channels.15

e. Verify the mobile station is operating in the Mobile Station Idle State on base station #1.16

f. Send a Global Service Redirection Message from the current base station with the17correct values of BAND_CLASS, EXPECTED_SID, EXPECTED_NID, NUM_CHAN, and18CDMA_CHAN for the new base station along with the following parameters:19

20Field Value




21



End the call.25



Repeat steps c through h with the mobile station operating in the Mobile Station Idle State on28base station #2.29

Remove the channel for base station #2 from the mobiles stations preferred roaming list and30repeat steps b through h.31

Repeat steps b and c with the mobile station operating in the Mobile Station Idle State on base32station #1 with the following modifications to the Global Service Redirection Message:33

34

TSG-C42 Page 7-6

10/19/2001 C.S0031

Field Value



1

If MOB_P_REV is less than six, verify the mobile station enters the System Determination2Substate of the Mobile Station Initialization State and acquires the system to which it was3redirected. If MOB_P_REV is greater than or equal to six, verify the mobile station ignores the4Global Service Redirection Message and remains in the Mobile Station Idle State on the current5system.6

7.1.4.3 Minimum Standard7The mobile station shall acquire the system to which it was directed and successfully originate a8call on the new system unless MOB_P_REVp is greater than or equal to six and9EXCL_P_REV_MS is equal to ‘1’.10

7.2 Network Directed System Selection and Normal Service Redirection Tests11When the mobile station receives a Service Redirection Message in response to an origination, or12prior to user data being transmitted, the mobile station shall attempt to select another system in13accordance with the current redirection criteria and re-originate on the new system.14

7.2.1 NDSS Between Band Classes15

7.2.1.1 Definition16This test verifies that a mobile station redirects between band classes when the Service17Redirection Message is sent on the f-csch, in response to an Origination Message, or on the f-18dsch prior to user data being transmitted.19


2.6.1.1.2 System Selection Using Current Redirection Criteria212.6.2.4 Mobile Station Order and Message Processing Operation222.6.3.5 Mobile Station Origination Attempt Substate233.6.2.3 Mobile Station Directed Messages243.7.2.3.2.16 Service Redirection Message {f-csch}253.7.3.3.2.23 Service Redirection Message {f-dsch}26


a. Connect the mobile station and base stations as shown in Figure 7.1.1.2-1. For this28test case base station #1 and base station #2 are CDMA base stations operating in29different band classes.30

b. Ensure the mobile station acquires base station #1.31

c. Originate a mobile station to land party call.32

d. Send a Service Redirection Message from the current base station in response to the33mobile station origination attempt or prior to user data being transferred with the34correct values of BAND_CLASS, EXPECTED_SID, EXPECTED_NID, NUM_CHAN,35and CDMA_CHAN for the new base station along with the following parameters:36

TSG-C42 Page 7-7

10/19/2001 C.S0031

1Field Value

REDIRECT_TYPE '1' [NDSS Redirection]

RECORD_TYPE '00000010'

2

e. Verify the mobile station acquires the base station #2.3

f. Verify the call completes and user traffic is present. (i.e. Audio)4

g. End the call.5

7.2.1.3 Minimum Standard6The mobile station shall be redirected between band classes when the base station sends a7Service Redirection Message in response to a mobile station Origination Message. The mobile8station shall establish a call on the new system without any additional user input.9

7.2.2 NDSS and Normal Service Redirection from CDMA to a Non-CDMA System10

7.2.2.1 Definition11This test verifies that a mobile station is redirected from CDMA to a Non-CDMA system when12the Service Redirection Message is sent on the f-csch in response to an origination, or on the f-13dsch prior to user data being transmitted.14


2.6.1.1.2 System Selection Using Current Redirection Criteria162.6.2.4 Mobile Station Order and Message Processing Operation172.6.3.5 Mobile Station Origination Attempt Substate183.6.2.3 Mobile Station Directed Messages193.7.2.3.2.16 Service Redirection Message {f-csch}203.7.3.3.2.23 Service Redirection Message {f-dsch}21

7.2.2.2 Method of measurement22

a. Connect the mobile station and base stations as shown in figure 7.1.1.2-1. Base23station #1 is a CDMA base station and base station #2 is a non-CDMA base station.24

b. Verify the mobile station acquires the CDMA system.25


d. In response to mobile origination attempt or prior to user data being transferred,27force base station #1 to send a Service Redirection Message with the proper28parameters (EXPECTED_SID, IGNORE_CDMA, and SYS_ORDERING) to initiate29Service Redirection from base station #1 to base station #2 using the following30parameters in the Service Redirection Message:31

32

TSG-C42 Page 7-8

10/19/2001 C.S0031

Field Value

REDIRECT_TYPE '1' [NDSS redirection]

RECORD_TYPE '00000001' [North American Amps]

'00000011' [TACS]

'00000100' [JTACS]

1

e. Verify the mobile station acquires base station #2.2


g. End the call.4

h. Repeat steps b through g making the following change to the Service Redirection5Message:6

7Field Value

REDIRECT_TYPE '0' [Normal Redirection]

8

7.2.2.3 Minimum Standard9The mobile station shall be redirected between the CDMA base station and the non-CDMA base10station when the CDMA base station sends a Service Redirection Message in response to a11mobile station Origination Message. The mobile station shall establish a call on the new system12without any additional user input.13

7.2.3 NDSS between Channels in the Same Band Class14

7.2.3.1 Definition15This test verifies that a mobile station redirects between channels in the same band class when16the Service Redirection Message is sent on the f-csch, in response to an Origination Message, or17on the f-dsch prior to user data being transmitted.18

Traceability: (see [4]);19

2.6.1.1.2 System Selection Using Current Redirection Criteria202.6.2.4 Mobile Station Order and Message Processing Operation212.6.3.5 Mobile Station Origination Attempt Substate223.6.2.3 Mobile Station Directed Messages233.7.2.3.2.16 Service Redirection Message {f-csch}243.7.3.3.2.23 Service Redirection Message {r-dsch}25


a. Connect the mobile station and base stations as shown in Figure 7.1.1.2-1. For this27test case base station #1 and base station #2 are CDMA base stations operating in28the same band class29

b. Ensure the mobile station acquires base station #1.30

c. Originate a mobile station to land party call.31

TSG-C42 Page 7-9

10/19/2001 C.S0031

d. Send a Service Redirection Message from the current base station in response to1mobile origination attempt or prior to user data being transferred with the correct2values of BAND_CLASS, EXPECTED_SID, EXPECTED_NID, NUM_CHAN, and3CDMA_CHAN for the new base station along with the following parameters:4

5Field Value

REDIRECT_TYPE '1' [NDSS Redirection]


6



g. End the call.9

7.2.3.3 Minimum Standard10The mobile station shall be redirected between channels within the same band class when the11base station sends a Service Redirection Message in response to a mobile station Origination12Message. The mobile station shall establish a call on the new system without any additional user13input.14

7.2.4 NDSS Ignore CDMA15

7.2.4.1 Definition16This test verifies that the mobile station does not respond to the CDMA Capability Message after17receiving a Service Redirection Message with IGNORE_CDMA='1'18


2.6.1.1.2 System Selection Using Current Redirection Criteria202.6.2.4 Mobile Station Order and Message Processing Operation212.6.3.5 Mobile Station Origination Attempt Substate223.6.2.3 Mobile Station Directed Messages233.7.2.3.2.16 Service Redirection Message {f-csch}243.7.3.3.2.23 Service Redirection Message {r-dsch}25


a. Connect the mobile station and the base stations as shown in figure 7.1.7.2-1. Base27station #1 is a CDMA base station and base station #2 is AMPS.28

b. Verify the mobile station acquires the CDMA system.29


d. Send a Service Redirection Message from the current base station with the correct31values of EXPECTED_SID and SYS_ORDERING for the new base station along with the32following parameters:33

34

TSG-C42 Page 7-10

10/19/2001 C.S0031

Field Value

REDIRECT_TYPE '1'


IGNORE_CDMA '1'

1


f. Verify the call completes and user traffic is present. (i.e. Audio).3

g. End the call.4

h. Send the CDMA Capability Message indicating CDMA is available from base station5#2.6

i. Verify the mobile station ignores the CDMA Capability Message and remains in the7Idle Task on the current system.8

7.2.4.3 Minimum Standard9After receiving the CDMA Capability Message from base station #2, the mobile station shall not10attempt to acquire the CDMA system again.11

7.2.5 NDSS Return If Fail12

7.2.5.1 Definition13This test verifies that when RETURN_IF_FAIL = '1' in the Service Redirection Message, the14mobile station will return to the serving system if it fails to acquire the system to which it was15directed.16

Traceability: (See [4] );17System Selection Using Current Redirection Criteria18

2.6.2.4 Mobile Station Order and Message Processing Operation192.6.3.5 Mobile Station Origination Attempt Substate203.6.2.3 Mobile Station Directed Messages213.7.2.3.2.16 Service Redirection Message {f-csch}223.7.3.3.2.23 Service Redirection Message {d-csch}23


a. Connect the mobile station and the base stations as shown in figure 7.1.1.2-1. Base25station #1 is a CDMA base station and base station #2 is a CDMA base station26

b.Verify the mobile station acquires base station #1.27

c. Ensure the mobile station cannot acquire base station #228


e. Send a Service Redirection Message from the current base station with the correct30values of BAND_CLASS, EXPECTED_SID, EXPECTED_NID, NUM_CHAN, and31CDMA_CHAN for the new base station along with the following parameters:32

33

TSG-C42 Page 7-11

10/19/2001 C.S0031

Field Value

REDIRECT_TYPE '1' [NDSS redirection]


RETURN_IF_FAIL '1'

1

f. Verify the mobile station returns to base station #1.2

7.2.5.3 Minimum Standard3The mobile station shall return to the channel it originated on after the failed NDSS attempt. The4call may or may not complete depending on the mobile station and infrastructure specific5implementations.6

7.3 Extended Global Service Redirection Tests7

7.3.1 Extended Global Service Redirection between Band Classes8

7.3.1.1 Definition9This test verifies that when a mobile station receives an Extended Global Service Redirection10Message directing it to another band class, the mobile station acquires the appropriate system.11

Traceabilities: (see [4])12

2.6.2.2 Response to Overhead Information Operation132.6.2.2.11 Extended Global Service Redirection Message143.7.2.3.2.1 System Parameters Message153.7.2.3.2.27 Extended Global Service Redirection Message16


g. Connect the mobile station to the base station as shown in Figure 7.1.7.2-1. For this18test case, base station #1 and base station #2 are in different band classes.19

Verify the mobile station is operating in the Mobile Station Idle State on base station #1.20

Send an Extended Global Service Redirection Message from the current base station with the21correct values of BAND_CLASS, EXPECTED_SID, EXPECTED_NID, NUM_CHAN, and22CDMA_CHAN for the new base station along with the following parameters:23

24Field Value


REDIRECT_P_REV_INCL 0


25



TSG-C42 Page 7-12

10/19/2001 C.S0031

End the call.1



Repeat steps c through h with the mobile station operating in the Mobile Station Idle State on4base station #2.5

Repeat steps c through h with the mobile station operating in the Mobile Station Idle State on6base station #1 with the following modifications to the Extended Global Service Redirection7Message:8

9Field Value



EXCL_P_REV_INCL 0

REDIRECT_P_MIN =< MOB_P_REVp

REDIRECT_P_MAX >= MOB_P_REVp

10

Repeat step c with the following changes to the Extended Global Service Redirection Message:1112

Field Value



EXCL_P_REV_INCL 0

REDIRECT_P_MIN < MOB_P_REVp

REDIRECT_P_MAX < MOB_P_REVp

13

Verify the mobile station ignores the Extended Global Service Redirection Message and remains14in the Mobile Station Idle State on the current system.15

Repeat step c with following changes to the Extended Global Service Redirection Message:1617

Field Value



EXCL_P_REV_INCL 1



18


TSG-C42 Page 7-13

10/19/2001 C.S0031

1

7.3.1.3 Minimum Standard2The mobile station shall acquire the system to which it was directed and successfully originate a3call on the new system unless:4

• MOB_P_REVp is not in the redirection mobile protocol revision range (The mobile station5shall then ignore the Extended Global Service Redirection Message and remain in the6Mobile Station Idle State on the current system.), or7

• MOB_P_REVp is in the excluded mobile protocol revision range. (The mobile station shall8then ignore the Extended Global Service Redirection Message and remain in the Mobile9Station Idle State on the current system.).10

7.3.2 Extended Global Service Redirection from CDMA to a Non-CDMA System11

7.3.2.1 Definition12This test verifies that when a mobile station receives an Extended Global Service Redirection13Message directing it from CDMA to Amps, the mobile station acquires the appropriate system.14The mobile station should only be redirected to Non-CDMA systems that it supports. An15example would be an analog system defined in [21].16


2.6.1.1.2 System Selection Using Current Redirection Criteria182.6.2.2 Response to Overhead Information Operation192.6.2.2.11 Extended Global Service Redirection Message203.7.2.3.2.1 System Parameters Message213.7.2.3.2.27 Extended Global Service Redirection Message22


h. Connect the mobile station to the base station as shown in Figure 7.1.7.2-1. For this24test case, base station #1 is a CDMA base station and base station #2 is a non-CDMA25base station26


Send an Extended Global Service Redirection Message from the current base station with the28correct value of EXPECTED_SID for the new base station along with the following parameters:29

30Field Value



RECORD_TYPE ‘00000001’31



TSG-C42 Page 7-14

10/19/2001 C.S0031

End the call.1


Power off mobile station.3

Repeat steps b through h with the mobile station operating in the Mobile Station Idle State on4base station #1 with the following modifications to the Extended Global Service Redirection5Message:6

7Field Value


REDIRECT_P_REV_INCL ‘1’

EXCL_P_REV_INCL ‘0’



8

Repeat steps b and c with the following changes to the Extended Global Service Redirection9Message:10

11Field Value






12


Repeat steps b and c with following changes to the Extended Global Service Redirection15Message:16

17Field Value






18


TSG-C42 Page 7-15

10/19/2001 C.S0031



• MOB_P_REVp is in the excluded mobile protocol revision range. (The mobile station shall7then ignore the Extended Global Service Redirection Message and remain in the Mobile8Station Idle State on the current system.)9

7.3.3 Extended Global Service Redirection to a Different Channel in the Same10Band Class11

7.3.3.1 Definition12This test verifies that when a mobile station receives an Extended Global Service Redirection13Message directing it to a different channel in the same band class, the mobile station acquires the14appropriate system.15


2.6.1.1.2 System Selection Using Current Redirection Criteria172.6.2.2 Response to Overhead Information Operation182.6.2.2.11 Extended Global Service Redirection Message193.7.2.3.2.1 System Parameters Message203.7.2.3.2.27 Extended Global Service Redirection Message21


i. Connect mobile station to base station as shown in Figure 7.1.7.2-1. For this test case,23base station #1 and base station #2 are in the same band class with different CDMA24channels.25


Send an Extended Global Service Redirection Message from the current base station with the27correct values of BAND_CLASS, EXPECTED_SID, EXPECTED_NID, NUM_CHAN, and28CDMA_CHAN for the new base station along with the following parameters:29

30Field Value






End the call.34

TSG-C42 Page 7-16

10/19/2001 C.S0031



Repeat steps c through h with mobile station operating in Mobile Station Idle State on base3station #2.4

Remove the channel for base station #2 from the mobiles stations preferred roaming list and5repeat steps b through h.6

Repeat steps c through h with the mobile station operating in the Mobile Station Idle State on7base station #1 with the following modifications to the Extended Global Service Redirection8Message:9

10Field Value





REDIRECT_P_MAX > MOB_P_REVp

11

Repeat step c with the following changes to the Extended Global Service Redirection Message:1213

Field Value






14


Repeat step c with following changes to the Extended Global Service Redirection Message:1718

Field Value






19

TSG-C42 Page 7-17

10/19/2001 C.S0031




• MOB_P_REVp is in the excluded mobile protocol revision range. (The mobile station shall9then ignore the Extended Global Service Redirection Message and remain in the Mobile10Station Idle State on the current system.)11

12

TSG-C42 Page 7-18

10/19/2001 C.S0031

No text1

TSG-C42 Page 8-1

10/19/2001 C.S0031

8 SHORT MESSAGE SERVICE (SMS)1Table 8-1 lists short message service tests.2

Table 8-1 Short Message Service Tests3

TestNo.

Title

8.1 Mobile Station Terminated SMS Tests:

8.1.1 Paging Channel SMS Delivery Procedures

8.1.2 SMS Delivery Procedures when Message is Too Large for Paging Channel

8.1.3 Traffic Channel SMS Delivery Procedures

8.1.4 Delivery of Maximum Length Message

8.1.5 SMS Delivery Error - Mobile Station Short Message Buffer Full

8.1.6 Voice Mail Notification

8.2 Mobile Station Originated SMS Tests:

8.2.1 Access Channel SMS Delivery

8.2.2 SMS Delivery when Message is Too Large for Access Channel

8.2.3 Traffic Channel SMS Delivery

8.2.4 Unknown Destination Address

8.2.5 Mobile Station Originated SMS Disabled

8.2.6 SMS Not Supported by Base Station

8.3 Broadcast SMS Tests:

8.3.1 Broadcast SMS Delivery

45

TSG-C42 Page 8-2

10/19/2001 C.S0031

A model of an SMS system per TIA/EIA-637-A is shown in Figure 8-1. SMS features are1distributed between a CDMA system and the SMS Message Center (MC), which together make2up the SMS system.3

4

MS PSTNTE

TEMC

Um Ai W

N

BS

5

Figure 8-1 SMS Reference Model6

The base station (BS) in this model represents the entire cellular system infrastructure. It7contains transceiver equipment, the Mobile Switching Center (MSC) and any Inter-Working8Function (IWF) required for network connection.9The MC element in this model represents a generic SMS message center function. The N10reference point represents one or more standardized interfaces between an SMS Message Center11and a base station. Terminal Equipment (TE) is voice or data equipment connected either directly12or indirectly to the MC. The mobile station (MS) represents the Bearer service end point.13Implementation details of an SMS system may vary. The MC may be either separate from or14physically integrated into the cellular system. MC interfaces may include features such as audio15response prompts and DTMF reception for dial-in access from voice telephones, as well as16appropriate menus and message entry protocols for dial in or dedicated data terminal access.17Mobile station interfaces may include keyboard and display features to support message entry.18

8.1 Mobile Station Terminated SMS Tests19Unless otherwise noted, the following conditions apply for all tests in this section:20

• Mobile station is capable of receiving short messages.21

• The short message feature for the mobile station is activated.22

• Base station has Power-up registration enabled (that is, POWER_UP_REG field is set to23‘1’ in the System Parameters Message).24

• Transport Layer messages shall enable the Bearer Reply Option.25

8.1.1 Paging Channel SMS Delivery Procedures26

8.1.1.1 Definition27This test verifies that a short message can be sent to a mobile station in the Mobile Station Idle28State.29

3031

TSG-C42 Page 8-3

10/19/2001 C.S0031


2.4.1.1.1.1: Mobile SMS Message Termination22.4.2.1.1.2: Mobile SMS Message Termination3


a. Delete all outstanding short messages in the network for the mobile station.5

b. Create a short message in the Message Center for the mobile station. Ensure that6the short message length is less than the maximum allowed size on the Paging7Channel so that it can be sent to the mobile station on the Paging Channel1.8

c. Power on the mobile station and wait until it is in the Mobile Station Idle State.9

d. Instruct the network to send the short message to the mobile station. Verify the10base station sends a Data Burst Message to the mobile station with the following11fields set as follows:12

13Field Value

MSG_NUMBER 1 (‘00000001’)

BURST_TYPE 3 (‘000011’)

NUM_MSGS 1 (‘00000001’)

NUM_FIELDS Greater than 0

14

e. Upon receiving the Data Burst Message at the mobile station, verify the following:15

• The mobile station alerts the user for the incoming short message and16correctly displays the received short message (if applicable).17

• The mobile station transmits an Access Channel Data Burst Message to18acknowledge the short message and indicating no error (i.e. contains a ‘Cause19Codes’ parameter having ERROR_CLASS = ‘00’).20

8.1.1.3 Minimum Standard21The base station shall send the short message to the mobile station over the Paging Channel22using the Data Burst Message. The correct and complete short message shall be received by the23mobile station. The mobile station shall alert the user upon short message reception and send an24access channel Data Burst Message.25

8.1.2 SMS Delivery Procedures when Message Too Large for Paging Channel26

8.1.2.1 Definition27This test verifies that if a short message length exceeds the maximum allowable length for28Paging Channel transport, the short message is delivered over the Traffic Channel.29

1 This is base station implementation dependent

TSG-C42 Page 8-4

10/19/2001 C.S0031


2.4.1.1.2: Mobile SMS Message Termination22.4.1.1.2.2: Mobile SMS Message Termination32.4.2.1.2: Base Station Traffic Channel Procedures4



b. Create a short message in the Message Center for the mobile station. Ensure that7the short message length is greater than the maximum length supported on the8Paging Channel2.9

c. Power on the mobile station and wait until it is in the Mobile Station Idle State.10

d. Instruct the network to send the short message to the mobile station. Verify the11following:12

• The base station does not send a Data Burst Message to the mobile13station on the paging channel.14

• The base station sends a General Page Message with either service option156 or service option 14.16

• After the mobile station enters the Conversation Substate, the base17station sends a Data Burst Message to the mobile station with the following fields18set as follows:.19

20Field Value

MSG_NUMBER 1 (‘00000001’)

BURST_TYPE 3 (‘000011’)

NUM_MSGS 1 (‘00000001’)


21

e. Upon receiving Data Burst Message at the mobile station, verify the following:22

• The mobile station alerts the user for the incoming short message and23correctly displays the received short message (if chosen).24

• The mobile station transmits a Reverse Traffic Channel Data Burst25Message to acknowledge the short message and indicating no error (i.e. contains a26Cause Codes parameter having ERROR_CLASS = ‘00’).27

8.1.2.3 Minimum Standard28The base station shall send the short message to the mobile station over the Traffic Channel in29the Conversation Substate. The correct and complete short message shall be received by the30mobile station. The mobile station shall alert the user upon short message delivery and send a31Data Burst Message.32

2 This is base station implementation dependent

TSG-C42 Page 8-5

10/19/2001 C.S0031

8.1.3 Traffic Channel SMS Delivery Procedures1

8.1.3.1 Definition2This test verifies a short message can be sent to a mobile station when it is already in the3Conversation Substate.4


2.4.1.1.2: Mobile SMS Message Termination62.4.1.1.2.2: Mobile SMS Message Termination72.4.2.1.2: Base Station Traffic Channel Procedures82.4.2.1.2.4: Mobile Station Message Termination in the Conversation Substate9




c. While the mobile station is in the Conversation Substate, create a short message in13the Message Center for the mobile station and instruct the network to send the14short message to the mobile station. Verify the base station sends a Data Burst15Message to the mobile station, with the following fields set as follows:16

17Field Value

MSG_NUMBER 1 (‘00000001’)

BURST_TYPE 3 (‘000011’)

NUM_MSGS 1 (‘00000001’)


18

d. Upon receiving Data Burst Message at the mobile station, verify the following:19

• The mobile station alerts the user for the incoming short message and20correctly displays the received short message (if chosen).21

• The mobile station transmits a Traffic Channel Data Burst Message to22acknowledge the short message and indicating no error (i.e. contains a Cause Codes23parameter having ERROR_CLASS = ‘00’).24

8.1.3.3 Minimum Standard25The base station shall send the short message to the mobile station over the Traffic Channel26using the Data Burst Message. The correct and complete short message shall be received by the27mobile station. The mobile station shall alert the user upon short message delivery and send a28Data Burst Message.29

TSG-C42 Page 8-6

10/19/2001 C.S0031

8.1.4 Delivery of Maximum Length Message1

8.1.4.1 Definition2This test verifies the SMS transport layer capability to send to a mobile station a short message3of the maximum size. The test verifies delivery of the maximum length short message on the4traffic channel.5


2.4.1.1.2: Mobile SMS Message Termination72.4.2.1.2: Base Station Traffic Channel Procedures83.4.2.1: SMS Point-to-Point Message93.4.3.5: Bearer Reply Option10


a. Clear or read all short messages from the mobile station.12

b. Delete all outstanding short messages in the Network for the mobile station.13

c. Create in the Message Center a maximum size short message for the mobile station.14

d. Instruct the network to send the short message to the mobile station. Verify the15base station sends a Data Burst Message to the mobile station on the traffic16channel, with the following fields set as follows:17

18Field Value

MSG_NUMBER 1 (‘00000001’)

BURST_TYPE 3 (‘000011’)

NUM_MSGS 1 (‘00000001’)


19

e. Upon receiving Data Burst Message at the mobile station, verify the following:20

• The mobile station alerts the user for the incoming short message and21correctly displays the received short message (if applicable).22

• The mobile station transmits a Traffic Channel Data Burst Message to23acknowledge the short message and indicating no error (i.e. contains a Cause Codes24parameter having ERROR_CLASS = ‘00’).25

8.1.4.3 Minimum Standard26The base station shall send a short message to the mobile station over the Traffic Channel using27the Data Burst Message. The correct and complete short message shall be received by the mobile28station. The base station shall receive a traffic channel Data Burst Message from the mobile29station.30

TSG-C42 Page 8-7

10/19/2001 C.S0031

8.1.5 SMS Delivery Error - Mobile Station Short Message Buffer Full1

8.1.5.1 Definition2This test verifies SMS transport layer acknowledgment capability by sending to the mobile3station short messages until the mobile station short message buffer is full.4


2.4.1.1.1.1: Mobile SMS Message Termination62.4.2.1.1: Paging Channel Procedures73.4.2.1: SMS Point-to-Point Message83.4.3.6: Cause Codes9


a. Clear or read all short messages from the mobile station to ensure that the short11message buffer is empty.12

b. Delete all outstanding short messages in the network for the mobile station.13

c. Create in the Message Center a short message for the mobile station. Instruct the14network to send the short message to the mobile station. Verify the base station15sends a Data Burst Message to the mobile station, with the following fields set as16follows:17

18Field Value

MSG_NUMBER 1 (‘00000001’)

BURST_TYPE 3 (‘000011’)

NUM_MSGS 1 (‘00000001’)


19

Upon receiving the Data Burst Message, the mobile station transmits a Data Burst20Message to acknowledge the short message and indicating no error (i.e. contains a21Cause Codes parameter having ERROR_CLASS = ‘00’).22

d. Repeat step c until the mobile station short message buffer is full.23

e. Instruct the network to send one additional short message to the mobile station.24Verify the base station sends a Data Burst Message to the mobile station, with the25following fields set as follows:26

27Field Value

MSG_NUMBER 1 (‘00000001’)

BURST_TYPE 3 (‘000011’)

NUM_MSGS 1 (‘00000001’)


28

TSG-C42 Page 8-8

10/19/2001 C.S0031

f. Upon receiving the Data Burst Message sent in step e, verify that the mobile station1transmits an Access Channel Data Burst Message to acknowledge the short message2and indicating temporary error (i.e. contains a Cause Codes parameter having3ERROR_CLASS = ‘10’ and CAUSE_CODE=’35’).4

8.1.5.3 Minimum Standard5The base station shall send the short messages to the mobile station. In response, the mobile6station shall send, and the base station shall receive the Data Burst Message. When the mobile7station short message buffer is full, the Data Burst Message that the mobile station sends to the8base station as acknowledgment shall indicate Terminal Resource Shortage (Cause Code set to935).10

8.1.6 Voice Mail Notification11

8.1.6.1 Definition12Voice Mail Notification (VMN) notifies the subscriber of voice mail messages using the Voice13Mail Notification teleservice and Short Message Service protocol. Notification can be a tone,14light, or display, and is manufacturer dependent.15


4.3.5: Voice Mail Notification (VMN)174.5.12: Number of Messages18


a. Configure the system as shown in Figure 8.1.6.2-1.2021

22Figure 8.1.6.2-1 Functional Setup for Voice Mail Notification23

b. Power on the mobile station and wait until it is in the Mobile Station Idle State.24

c. Instruct the network to send a Voice Mail Notification (corresponds to a SMS Point-25to-Point message) to the mobile station. Verify that the base station sends a Data26Burst Message, with the BURST_TYPE field set to ‘000011’, with the following27parameters of the SMS message set as follows:28

TSG-C42 Page 8-9

10/19/2001 C.S0031

1) Teleservice Identifier parameter, IDENTIFIER = Voice Mail Notification (x1003).1

2) Message Identifier subparameter, MESSAGE_TYPE = Deliver (0x1).2

3) Number of Messages subparameter, MESSAGE_CT = 99.3

d. Upon receiving the Data Burst Message, verify that the following:4

• The mobile station transmits an SMS Acknowledge message via an5Access Channel Data Burst Message to acknowledge the short message and6indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS =7‘00’).8

• The mobile station indicates to the user the number of voice mail9messages available as indicated by the network.10

e. Repeat step c, setting the MESSAGE_CT = 0.11

f. Upon receiving the Data Burst Message, verify that the mobile station indicates to12the user no voice mail messages are available.13

8.1.6.3 Minimum Standard14The base station shall send Voice Mail Notification to the mobile station. The mobile station15shall acknowledge receipt of the Notification. The mobile station shall indicate the number of16messages stored at the voice mail system.17

8.2 Mobile Station Originated SMS Tests18

8.2.1 Access Channel SMS Delivery19

8.2.1.1 Definition20This test verifies that a short message can be sent to the Message Center (MC) by a mobile21station using the access channel. The short message length chosen for this test is such that it22doesn’t exceed the maximum message length allowed on the Access Channel.23


2.4.1.1.1.2: Mobile SMS Message Origination252.4.2.1.1.1: Mobile SMS Message Origination26


a. Power on the mobile station and wait until it is in the Mobile Station Idle State.28

b. Create a short message at the mobile station, of a length smaller than the maximum29message length allowed on the access channel, and instruct the mobile station to30send the short message to the network3. Verify the mobile station sends a Data31Burst Message to the base station over the access channel, with the following fields32set as follows:33

34

3 The maximum allowed size is dependent on the maximum access channel capsule size signaledin the Access Parameters Message and is also implementation dependent.

TSG-C42 Page 8-10

10/19/2001 C.S0031

Field Value

MSG_NUMBER 1 (‘00000001’)

BURST_TYPE 3 (‘000011’)

NUM_MSGS 1 (‘00000001’)


1

c. Verify that the Message Center receives the short message and sends a layer 22acknowledgement to the mobile station.3

8.2.1.3 Minimum Standard4The mobile station shall send the short message to the Message Center over the Access Channel.5The Message Center shall receive the correct and complete short message and the mobile station6shall receive the layer 2 acknowledgement.7

8.2.2 SMS Delivery when Message is Too Large for Access Channel8

8.2.2.1 Definition9This test verifies a mobile station in the Mobile Station Idle State can originate a short message10of length larger than the maximum length allowed on the access channel and that the message is11delivered to the Message Center over the Traffic Channel.12

Traceability: (See [13] ) ;13

2.4.1.1.1.2: Mobile SMS Message Origination142.4.2.1.2.2: Base Station Traffic Channel Procedures15



b. Create a short message at the mobile station, of a length larger than the maximum18message length allowed on the access channel, and instruct the mobile station to19send the short message to the network.20

c. Verify the following:21

• The mobile station does not send the Data Burst Message over the access22channel23

• The mobile station sends an Origination Message to originate as SMS call with24the SERVICE_OPTION field set to either 6 or 14.25

• After entering the Conversation Substate, the mobile station sends a Data Burst26Message, with the following fields set as follows:27

28

TSG-C42 Page 8-11

10/19/2001 C.S0031

Field Value

MSG_NUMBER 1 (‘00000001’)

BURST_TYPE 3 (‘000011’)

NUM_MSGS 1 (‘00000001’)


1

d. Verify the Message Center receives the short message.2

e. Verify that upon sending the short message, the mobile station sends a Release3Order to release the dedicated channels.4

8.2.2.3 Minimum Standard5The mobile station shall send the short message to the Message Center over the Traffic Channel.6The Message Center shall receive the short message. The mobile station shall release the7dedicated channels after delivery of short message.8

8.2.3 Traffic Channel SMS Delivery9

8.2.3.1 Definition10This test verifies that a short message can be sent by the mobile station when it is in the11Conversation Substate.12


2.4.1.1.1.2: Mobile SMS Message Origination142.4.1.1.2.4: Mobile Station Message Origination in the Conversation Substate152.4.2.1.1.1: Mobile SMS Message Origination162.4.2.1.2.2: Base Station Traffic Channel Procedures17


a. Setup a mobile station originated call.19

b. While mobile station is in the Conversation Substate, create a short message and20instruct the mobile station to send the short message to the network. Verify the21mobile station sends a Data Burst Message, with the following fields set as follows:22

23Field ValueMSG_NUMBER 1 (‘00000001’)

BURST_TYPE 3 (‘000011’)

NUM_MSGS 1 (‘00000001’)


24

c. Verify the Message Center receives the short message.25

d. Verify that upon sending the short message, the mobile station does not attempt to26release the dedicated channels.27

TSG-C42 Page 8-12

10/19/2001 C.S0031

8.2.3.3 Minimum Standard1The mobile station shall send the short message to the Message Center while it is in the2Conversation Substate.3

8.2.4 Unknown Destination Address4

8.2.4.1 Definition5This test verifies the base station can process a mobile station originated short message with an6unknown destination address and will inform the mobile station regarding an unknown7destination address.8


2.4.1.1.1.2: Mobile SMS Message Origination102.4.2.1.2.2: Base Station Traffic Channel Procedures113.4.2.1: SMS Point-to-Point Message123.4.3.6: Cause Codes13



b. Create a short message at the mobile station, but with an unknown address in the16destination address field, and instruct the mobile station to send the short message17to the base station. Verify the mobile station sends a Data Burst Message, with the18following fields set as follows:19

20Field Value

MSG_NUMBER 1 (‘00000001’)

BURST_TYPE 3 (‘000011’)

NUM_MSGS 1 (‘00000001’)


c. Verify the Message Center receives the short message and the base station sends a21Data Burst Message to the mobile station indicating ‘an unknown address’22

8.2.4.3 Minimum Standard23The base station shall route the short message to the Message Center. A Data Burst Message24shall be sent to the mobile station indicating an unknown address.25

8.2.5 Mobile Station Originated SMS Disabled26

8.2.5.1 Definition27This test verifies that when mobile station originated SMS is not activated in the network, the28base station can process a mobile station originated short message and inform the mobile station29that short message origination has been denied.30


2.4.1.1.1.2: Mobile SMS Message Origination32

TSG-C42 Page 8-13

10/19/2001 C.S0031

2.4.2.1.2.2: Base Station Traffic Channel Procedures13.4.2.1: SMS Point-to-Point Message23.4.3.6: Cause Codes3


a. Ensure the mobile station originated short message feature for the mobile station is5not activated in the network.6


c. Create a short message at the mobile station, with the Bearer Reply Option8parameter set, and instruct the mobile station to send the short message to the9base station. Verify the mobile station sends a Data Burst Message, with the10following fields set as follows:11

12Field Value

MSG_NUMBER 1 (‘00000001’)

BURST_TYPE 3 (‘000011’)

NUM_MSGS 1 (‘00000001’)


13

d. Upon receiving the Data Burst Message at the base station, verify the following:14

• The base station sends a Data Burst Message to the mobile station, with15an indication that the short message origination has been denied.16

• The base station does not route the short message to the Message17Center.18

8.2.5.3 Minimum Standard19The base station shall not route the short message to the Message Center and the base station20shall send a Data Burst Message to the mobile station indicating the SMS has been denied.21

8.2.6 SMS Not Supported by Base Station22

8.2.6.1 Definition23This test verifies the base station can process a mobile station originated short message, and24inform the mobile station that SMS is not supported by the base station.25


2.4.1.1.1.2: Mobile SMS Message Origination272.4.2.1.2.2: Base Station Traffic Channel Procedures283.4.2.1: SMS Point-to-Point Message293.4.3.6: Cause Codes30


a. Ensure the base station is not capable of SMS or that SMS has been disabled for32this test.33

TSG-C42 Page 8-14

10/19/2001 C.S0031


c. Create a short message at the mobile station, with Bearer Reply Option parameter2set, and instruct the mobile station to send the short message to the network. Verify3the mobile station sends a Data Burst Message, with the following fields set as4follows:5

6Field ValueMSG_NUMBER 1 (‘00000001’)

BURST_TYPE 3 (‘000011’)

NUM_MSGS 1 (‘00000001’)


7

d. Upon receiving the Data Burst Message at the base station, verify the following:8

• The base station sends a Data Burst Message to the mobile station, with9an indication that SMS is not supported by this base station.10

• The base station does not route the short message to the Message11Center.12

8.2.6.3 Minimum Standard13The base station shall not route the short message to the Message Center and the base station14shall send a Data Burst Message to the mobile station indicating that SMS is not supported by15the base station.16

8.3 Broadcast SMS Tests17

8.3.1 Broadcast SMS Delivery18

8.3.1.1 Definition19This test verifies that mobile stations configured to receive broadcast SMS are able to receive20broadcast SMS messages sent by the network.21


2.4.1.2.1: Paging Channel Procedures for Broadcast SMS234.3.1.3: Broadcast Messaging Service24


a. Connect the base station and mobile stations as shown in Figure 8.3.1.2-1.26

b. Ensure mobile station #1 is configured to receive broadcast SMS while mobile27station #2 is not configured to receive broadcast SMS.28

c. Power on the mobile stations and wait until they are registered.29

d. Clear any outstanding broadcast messages in the network.3031

TSG-C42 Page 8-15

10/19/2001 C.S0031

12

Figure 8.3.1.2-1 Functional Setup for Broadcast SMS Tests34

e. Create broadcast message #1 shown in Table 8.3.1.2-1 and instruct the network to5broadcast it. Verify the base station sends a Data Burst Message, with the following6fields set as follows:7

8Field Value

MSG_NUMBER 1 (‘00000001’)

BURST_TYPE 3 (‘000011’)

NUM_MSGS 1 (‘00000001’)


9

Table 8.3.1.2-1 Broadcast Messages and Priority10

Broadcast Message Broadcast Message Priority Priority Indicator Value

Message #1 Normal 00

Message #2 Emergency 11

11

f. Upon receiving the Data Burst Message, verify that mobile station #1 displays12broadcast message #1 (as a Normal message, if such display is supported) and13mobile station #2 does not.14

g. Create broadcast message #2 shown in Table 8.3.1.2-2 and instruct the network to15broadcast it. Verify the base station sends a Data Burst Message, with the following16fields set as follows:17

18

TSG-C42 Page 8-16

10/19/2001 C.S0031

Field Value

MSG_NUMBER 1 (‘00000001’)

BURST_TYPE 3 (‘000011’)

NUM_MSGS 1 (‘00000001’)


1

h. Upon receiving the Data Burst Message, verify both mobile stations display2broadcast message #2 (as a Emergency message, if such a display is supported)3

8.3.1.3 Minimum Standard4Both mobile stations shall display broadcast message #2 (Emergency). Mobile station #2 shall5not display broadcast message #1 (Normal). All received broadcast messages shall be correct and6complete.7

TSG-C42 Page 9-1

10/19/2001 C.S0031

9 SUBSCRIBER CALLING FEATURES TESTS1

Note: Interaction between calling features may be infrastructure unique.2Table 9-1 lists subscriber calling features tests.3

Table 9-1 Subscriber Calling Features Tests4

Test No. Title

9.1 Call Forwarding

9.2 Three-Way Calling

9.3 Land Party to Mobile Station Caller ID

9.4 Call Waiting

9.5 Message Waiting Indicator

9.6 Land Party to Mobile Station Calling Name Presentation

9.7 Display Records

9.8 TTY/TDD

9.9 Answer Holding

9.10 User Selective Call Holding

9.1 Call Forwarding5

9.1.1 Definition6These tests verify that the mobile station can activate and deactivate various Call Forwarding7features, including call forwarding to a pre-registered number and call forwarding to voice mail.8These features shall be tested for all applicable conditions, including Call Forwarding –9Unconditional (CFU), Call Forwarding - Busy (CFB), Call Forwarding- default (CFD), and Call10Forwarding-No-Answer (CFNA.11

Traceability: (See [4] );123.7.5.5: Signaling Message Encryption13

Traceability: (See [22] );145.2: Mobile SMS Message Termination155.3: Paging Channel Procedures165.4175.518


9.1.2.1 Call Forwarding, Unconditional20

CFU permits a called subscriber to send incoming calls addressed to the called21subscriber’s Directory Number to another Directory Number (forward-to number) or to22the called subscriber’s designated voice mail box. If this feature is active, calls are23forwarded regardless of the condition of the termination.24

a. Connect the mobile station and base station as shown in Figure 9.1.2.1-1.25

TSG-C42 Page 9-2

10/19/2001 C.S0031

b. Power on the mobile station and wait until it reaches Mobile Station Idle State.1

c. Dial the call forwarding unconditional (CFU) feature activation code, followed by the2forward-to number, followed by SEND. Verify feature update confirmation at the3mobile station.4

d. Setup a call from a land party to the mobile station. Verify call is forwarded and that5if the Network directs the mobile station to “Ping Ring” it plays a single burst of 5006ms.7

e. Answer the call on the forward line, and verify the audio path.89

10Figure 9.1.2.1-1 Functional Setup for Testing Call Forwarding11

12

f. End call.13

g. Dial the call forwarding unconditional (CFU) deactivation feature code followed by14SEND. Verify feature update confirmation at the mobile station.15

h. Setup a call from the land party to the mobile station.16

i. Verify the call completes at the mobile station.17

j. Repeat the test except for at step c, dial the call forwarding unconditional (CFU)18activation feature code, followed by 8 (voice-mail), followed by SEND. Verify feature19update confirmation at the mobile station.20

9.1.2.2 Call Forwarding, Busy21

CFB permits a called subscriber to have the system send incoming calls to another22Directory Number (forward-to number) or to the called subscriber’s designated voice23mail box, when the subscriber is engaged in a call or service.24



TSG-C42 Page 9-3

10/19/2001 C.S0031

c. Dial the call forwarding busy (CFB) activation feature code, followed by the forward-1to number, followed by SEND. Verify feature update confirmation at the mobile2station.3

d. Place a mobile under test in a voice or data call.4

e. Setup a call from a land party to the mobile station. Verify the call is forwarded to5the forward-to number or voice mail, and that if the Network directs the mobile6station to “Ping Ring” it plays a single burst of 500 ms.7

f. Answer the call on the forward line, and verify the audio path.8

g. End all calls.9

h. Dial the call forwarding busy (CFB) deactivation feature code followed by SEND.10Verify feature update confirmation at the mobile station.11

i. Take the mobile under test out of the voice or data call as specified in step d.12

j. Setup a call from the land party to the mobile station.13

k. Verify the call completes at the mobile station.14

l. Repeat the test except that at step c, dial the call forwarding busy (CFB) activation15feature code, followed by 8 (voice-mail), followed by SEND. Verify feature update16confirmation at the mobile station.17

9.1.2.3 Call Forwarding, Default18

CFD permits a called subscriber to have the system send incoming calls to another19Directory Number (forward-to number) or to the called subscriber’s designated voice20mail box, when the subscriber is engaged in a call, does not respond to paging, does not21answer the call within a specified period after being alerted or is otherwise inaccessible.22



c. Dial the call forwarding default (CFD) activation feature code, followed by the25forward-to number, followed by SEND. Verify feature update confirmation at the26mobile station.27

d. Setup a call from a land party to the mobile station. Verify the call is forwarded and28that if the Network directs the mobile station to “Ping Ring” it plays a single burst of29500 ms.30

e. Answer the call on the forward line, and verify the audio path.31

f. End call.32

g. Dial the call forwarding default (CFD) deactivation feature code followed by SEND.33Verify feature update confirmation at the mobile station.34

h. Setup a call from the land party to the mobile station.35

i. Verify the call completes at the mobile station.36

TSG-C42 Page 9-4

10/19/2001 C.S0031

j. Repeat the test except that at step c, dial call forwarding default (CFD) activation1feature code, followed by 8 (voice-mail), followed by SEND. Verify feature update2confirmation at the mobile station.3

9.1.2.4 Call Forwarding, No Answer4

CFNA permits a called subscriber to have the system send incoming calls addressed to the5called subscriber’s Directory Number to another Directory Number (forward-to number) or6to the called subscriber’s designated voice mail box, when the subscriber fails to answer.7



c. Dial the call forwarding-no answer (CFNA) activation feature code, followed by the10forward-to number, followed by SEND. Verify feature update confirmation at the11mobile station.12

d. Place a mobile under test in a voice or data call.13

e. Setup a call from a land party to the mobile station. Verify the call is forwarded to14the forward-to number or voice mail, and that if the Network directs the mobile15station to “Ping Ring” it plays a single burst of 500 ms.16

f. Answer the call on the forward line, and verify the audio path.17

g. End all calls.18

h. Dial the call forwarding-no answer (CFNA) deactivation feature code followed by19SEND. Verify feature update confirmation at the mobile station.20

i. Take the mobile under test out of the voice or data call as specified in step d.21

j. Setup a call from the land party to the mobile station.22

k. Verify the call completes at the mobile station.23

l. Repeat the test except that at step c, dial call forwarding no-answer (CFNA)24activation feature code, followed by 8 (voice-mail), followed by SEND. Verify feature25update confirmation at the mobile station.26

9.1.3 Minimum Standard27When call forwarding is activated, calls shall be forwarded to the forward-to number or voice-28mail as programmed by the user. When call forwarding is deactivated, the calls shall terminate at29the mobile station normally.30

9.2 Three-Way Calling31

9.2.1 Definition32This test will verify that a mobile station authorized for Three-Way Calling can add a third party33to an established two-way call.34

Traceability: IS-2000.5; 2.7.2.3.2.3, IS-664, 5.223536

TSG-C42 Page 9-5

10/19/2001 C.S0031


a. Connect the mobile stations as shown in Figure 9.2.2-1.23

4Figure 9.2.2-1 Functional Setup for Testing Three-Way Calling5

6

b. Setup a call from mobile station #1 to mobile station #2 and verify user data in both7directions.8

c. Instruct mobile station #1 to put mobile station#2 on hold. Verify that mobile9station #1 sends a Flash with Information Message to put mobile station #2 on hold.10Verify mobile station #2 is put on hold.11

d. Using mobile station #1, dial a land station. Verify that mobile station #1 sends a12Flash with Information Message.13

e. Wait for the land station to ring. Instruct the land party to connect the call (second14leg of the three-way call) and verify user data.15

f. Instruct mobile station #1 to make the three-way connection. Verify mobile station16#1 sends a Flash with Information Message. Verify the three-way connection is17established.18

g. Instruct mobile station #1 to disconnect the third-leg of the three way call. Verify19that a Flash with Information Message is sent from mobile station 1. Verify the20three-way connection is disconnected and the call is returned to its original two-way21state.22

h. End call from mobile station 1. Verify the connection is released.23

9.2.3 Minimum Standard24Mobile station #1 shall successfully perform the addition and dropping of a third party to a two-25way connection. All calls shall be successful.26

TSG-C42 Page 9-6

10/19/2001 C.S0031

9.3 Land Party to Mobile Station Caller ID1

9.3.1 Caller ID from Mobile Station Idle State2

9.3.1.1 Definition3This test will verify that a mobile station in the Mobile Station Idle State properly displays the4Calling Party Number (CPN).5


2.7.4: Information Records73.7.2.3.2.12: Feature Notification Message83.7.3.3.2.3: Alert with Information Message93.7.3.3.2.14: Flash with Information Message103.7.5: Information Records11

IS-2000-6;12

3.7.2.2: Calling Number Identification (CNI)13




c. Setup a call to the mobile station using a 10-digit CPN and set the Presentation17Indicator (PI) field of the CPN information record to '00' (Presentation Allowed).18Verify that the base station sends a Feature Notification Message, Alert With19Information Message, or a Flash With Information Message with the CPN information20record with the PI field set to ‘00’.21

d. Verify the mobile station receives and displays the CPN.22


f. End call.24

g. Setup a call to the mobile station using a 10-digit CPN and set the Presentation25Indicator (PI) field of the CPN information record to '01' (Presentation Restricted).26Verify that the base station sends a Feature Notification Message, Alert With27Information Message, or a Flash With Information Message with the CPN information28record with the PI field set to ‘01’.29

h. Repeat steps d through f, except in step d, verify the mobile station does not display30the CPN and that it indicates the CPN is restricted.31

i. Setup a call to the mobile station using a 10-digit CPN and set the Presentation32Indicator (PI) field of the CPN information record to '10' (Number Not Available).33Verify that the base station sends a Feature Notification Message, Alert With34Information Message, or a Flash With Information Message with the CPN information35record with the PI field set to ‘00’.36

j. Repeat steps d through f, except in step d, verify the mobile station does not display37the CPN and that it indicates the CPN is not available.38

TSG-C42 Page 9-7

10/19/2001 C.S0031

9.3.1.3 Minimum Standard1The mobile station in Mobile Station Idle State shall:2

• Display the CPN when the PI field of the CPN information record is set to '00'3

• Not display the CPN but shall indicate the CPN is restricted when the PI field of the CPN4information record is set to '01'5

• Not display the CPN but shall indicate the CPN is not available when the PI field of the6CPN information record is set to '10'.7

9.3.2 Caller ID from Conversation State8

9.3.2.1 Definition9This test will verify the mobile station in conversation state (with call waiting enabled) properly10displays the Calling Party Number (CPN).11


2.7.4: Information Records133.7.2.3.2.12: Feature Notification Message143.7.3.3.2.3: Alert with Information Message153.7.3.3.2.14: Flash with Information Message163.7.5: Information Records17IS-2000-6;183.7.2.2: Calling Number Identification (CNI)19




c. Setup a call to the mobile station using a 10-digit CPN and set the Presentation23Indicator (PI) field of the CPN information record to '00' (Presentation Allowed).24Verify that the base station sends a Feature Notification Message, Alert With25Information Message, or a Flash With Information Message with the CPN information26record with the PI field set to ‘00’.27

d. Verify the mobile station properly receives and displays the CPN (of caller #1).28


f. Maintain the call and setup another call from caller #2 to the mobile station using a30different 10-digit CPN and set the Presentation Indicator (PI) field of the calling party31(caller #2) to '00' (Presentation Allowed). Verify that the base station sends an Alert32With Information Message or Flash With Information Message with the CPN33information record with the PI field set to ‘00’.34

g. Verify the mobile station properly receives and displays the CPN (of caller #2).35

h. End both calls.36

i. If applicable, repeat test with the mobile station in AMPS mode.37

TSG-C42 Page 9-8

10/19/2001 C.S0031

j. Repeat steps b through i, except in step c and f, set the PI field of the calling parties1to '01' (Presentation Restricted). Verify that in step d and g, the mobile station does2not display the CPN and that it indicates the CPN is restricted.3

k. Repeat steps b through i, except in step c and f, set the PI field of the calling parties4to '10' (Number Not Available). Verify that in step d and g, the mobile station does5not display the CPN, and that it indicates the CPN is not available.6

9.3.2.3 Minimum Standard7The mobile station in Conversation Substate with call waiting enabled shall:8

• Display the CPN when the PI field of the CPN information record is set to '00'9• Not display the CPN but shall indicate the CPN is restricted when the PI field of the CPN10

information record is set to '01'11• Not display the CPN but shall indicate the CPN is not available when the PI field of the12

CPN information record is set to '10'.13

9.4 Call Waiting14

9.4.1 Definition15This test verifies that a mobile station in a two-way conversation with call waiting enabled, will16receive notification of waiting calls. This test will verify that the mobile station will send a flash17request to connect to the waiting call.18

Traceability: (See [4] );193.7.5.5: Signal, 3.6.7.2: Requirements20


a. Connect the mobile station to the base station as shown in Figure 9.1.2.1-1.22

b. Ensure call waiting is enabled.23

c. Make a mobile station to land party #1 call. Verify user data in both directions.24

d. Setup a call from land party #2 to the mobile station. Wait for ringback on land25party #2 and the call waiting notification on the mobile station.26

e. Press SEND on the mobile station. Verify the mobile station sends a Flash With27Information Message to the base station to switch over to land party #1.28

f. Verify land party #1 is on hold, and that a voice path is established between the29mobile station and land party #2.30

g. Press SEND on the mobile station to put land party #2 on hold, and reconnect the31voice path to land party #1. Verify the mobile station sends a Flash With Information32Message to the base station.33

h. End land party #1 call.34

i. Press SEND on the mobile station. Verify the mobile station sends a Flash With35Information Message to the base station to switch over to land party #2.36

j. Verify user data between the mobile station and land party #2.37

TSG-C42 Page 9-9

10/19/2001 C.S0031

k. End call.1

l. Disable call waiting.2



o. Setup a call from land party #2 to the mobile station. Wait for the busy tone on land5party 2. Ensure call waiting tone is NOT heard on the mobile station.6

p. End all calls.7

9.4.3 Minimum Standard8If call waiting is enabled the base station shall send a call waiting tone to the mobile station9during a two-way conversation indicating another call is waiting. The mobile station shall send a10flash request to connect with land party #2, while land party #1 is put on hold. With call waiting11disabled, ensure the mobile station under test detects no call waiting tone.12

9.5 Message Waiting Indicator (MWI)13

9.5.1 MWI when the mobile station is in Mobile Station Idle State14

9.5.1.1 Definition15MWI notifies the subscriber of voice mail messages when the mobile station is in Mobile Station16Idle State. Notification can be a tone, light or display and is manufacturer dependent.17


3.7.5.6: Message Waiting193.7.2.3.2.12: Feature Notification Message20


a. Configure the system as shown in Figure 9.1.2.1-122

b. Enable MWI at the base station.23

c. Power up the mobile station.24

d. Instruct the base station to send a Feature Notification Message to the mobile25station to instruct message waiting, setting the number of messages to a value26ranging from 0 to 31.27

e. Verify the RECORD TYPE field in the Feature Notification Message is set to28‘00000110’ for a Message Waiting information record type.29

f. Upon receiving the Feature Notification Message, verify the user interface displays30the correct number of messages based on the number of messages indicated in the31received messages.32

g. Repeat steps d through f, setting the number of messages to a different value from33that set in step d.34

h. Power off the mobile station.35

TSG-C42 Page 9-10

10/19/2001 C.S0031

9.5.1.3 Minimum Standard1The mobile station shall accurately report the number of voice mail messages waiting to be2processed in its Voice Mail System following an autonomous registration.3

9.5.2 MWI when the mobile station is in Conversation State4

9.5.2.1 Definition5MWI notifies the subscriber of voice mail messages when the mobile station is in Conversation6Substate. Notification can be a tone, light or display and is manufacturer dependent. While in the7conversation state, MWI notifies the subscriber when the number of new and retrieved voice8mail messages change.9


3.7.5.6: Message Waiting113.7.2.3.2.12: Feature Notification Message12


a. Configure the system as shown in Figure 9.1.2.1-1.14

b. Enable MWI at the base station.15




f. Instruct the base station to send a Flash With Information Message to the mobile19station to indicate message waiting, setting the number of messages to a value20smaller than the maximum number of messages supported by the mobile station.21

g. Upon receiving the Feature Notification Message, verify the user interface displays22the correct number of messages based on the number of messages indicated in the23received message. If the mobile station does not support the number of messages24indicated, it should display the maximum number of messages it supports.25

h. Repeat steps d through f, setting the number of messages to a value greater than26the maximum number of messages supported by the mobile station.27

i. Power off the mobile station.28

9.5.2.3 Minimum Standard29The mobile station should accurately report the number of voice mail messages waiting to be30processed in its voice mail system when the mobile station is in Conversation Substate. If the31mobile station does not support the number of messages waiting to be processed in its voice mail32system, it should display the maximum number of messages it supports.33

TSG-C42 Page 9-11

10/19/2001 C.S0031

9.6 Land Party to Mobile Station Calling Name Presentation1

9.6.1 Calling Name Presentation (CNAP) from Mobile Station Idle State2

9.6.1.1 Definition3This test will verify that a mobile station in the Mobile Station Idle State properly displays the4Calling Name Information (CNA).5


3.7.5.3: Calling Party Number7



b. Ensure the mobile station has been assigned CNAP Class-of -Service and that the10mobile station has not been pre-programmed (phone book) with any calling party11name/number information.12

c. Power on the mobile station and wait until it reaches Mobile Station Idle State.13

d. Setup a call to the mobile station from a 10-digit Calling Party Number (CPN).14Instruct the base station to indicate CNA with Presentation Allowed. Verify that the15base station sends a Feature Notification Message, Alert With Information Message,16or a Flash With Information Message with an Extended Display information record17and CPN information record with the PI field set to “00” (Presentation Allowed).18

e. Verify the mobile station receives and displays the CNA and Calling Number19Identification (CNI).20


g. End call.22

h. Power down the mobile station.23

i. Change the PI field of the CPN information record to “01” (Presentation Restricted).24

j. Repeat steps d through i, except step f, verify the mobile station does not display the25CNA or CNI and that it indicates the CNA is restricted, during the first alerting26cycle.27

k. Change the PI field of the CPN information record to “10” (Number Not Available).28

l. Repeat steps d through, except step f, verify the mobile station does not display the29CNA or CNI and that it indicates the CNA is not available, during the first alerting30cycle.31

9.6.1.3 Minimum Standard32The mobile station in Mobile Station Idle State shall:33

a. Display the CNA and CNI when the PI field of the CPN information record is set to34“00”.35

TSG-C42 Page 9-12

10/19/2001 C.S0031

b. Not display the CNA or CNI but shall indicate the CNA is restricted when the PI field1of the CPN information record is set to “01”.2

c. Not display the CNA or CNI but shall indicate the CNA is not available when the PI3field of the CPN information record is set to "10".4

9.6.2 Calling Name Presentation (CNAP) from Conversation State5

9.6.2.1 Definition6This test will verify that the mobile station in Conversation Substate (with call waiting enabled)7properly displays the Calling Party Name (CNA).8





b. Ensure mobile station is assigned CNAP Class-of-Service, and that the mobile13station has not been pre-programmed (phone book) with calling name/number14information.15

c. Set Presentation Indicator (PI) field of the CPN information record of calling parties 116and 2 to “00” (Presentation Allowed).17

d. Power on the mobile station and wait until it reaches Mobile Station Idle State.18

e. Setup a call from party 1 to the mobile station (from 10-digit CPN 1).19

f. Verify the mobile station receives and displays the CNA and CNI (of party 1) during20the first alerting cycle.21

g. Verify user data in both directions.22

h. Maintain the call and setup another call from party 2 to the mobile station (from 10-23digit CPN 2). Verify that the base station sends a Alert With Information Message or24Flash With Information Message with an Extended Display information record and25the PI field set to “00” (Presentation Allowed).26

i. Verify the mobile station receives and displays the CNA and CNI (of party 2) with27delivery of the call waiting indication.28

j. End both calls, then power down the mobile station.29


l. Change the PI field of the CPN information record of both calling parties (1 and 2) to31'01' (Presentation Restricted).32

m. Repeat steps d through k, except in step f and i, verify the mobile station does not33display the CNA and that it indicates the CNA is restricted.34

n. Change the PI field of the CPN information record of both calling parties (1 and 2) to35'10' (Number Not Available).36

TSG-C42 Page 9-13

10/19/2001 C.S0031

o. Repeat steps d through k, except in step f and i, verify the mobile station does not1display the CNA and that it indicates the CNA is not available.2

9.6.2.3 Minimum Standard3The mobile station in conversation state with call waiting enabled shall:4

a. Display the CNA and CNI when the PI field of the CPN information record is set to5'00'.6

b. Not display the CNA or CNI, but shall indicate the CNA is restricted when the PI7field of the CPN information record is set to '01'.8

c. Not display the CNA or CNI, but shall indicate the CNA is not available when the PI9field of the CPN information record is set to ‘10'.10

9.6.3 Calling Name Presentation (CNAP) with Forwarding11

9.6.3.1 Definition12This test verifies the mobile station receiving a forwarded call from party 2 (redirecting party),13properly displays redirection information from calling party 1 (originating party) and party 2.14




a. Connect the mobile station and base station as shown in figure 9.1.2.1-1.18

b. Ensure the mobile station is assigned the CNAP Class-of-Service and that the19mobile station has not been pre-programmed (phone book) with calling20name/number information.21

c. Ensure party 2 has been assigned Call Forwarding Unconditional, programmed to22forward calls to the mobile station directory number, and that this service is23invoked.24

d. Set Presentation Indicator field of the CPN information record of calling parties 125and 2 to '00' (Presentation Allowed).26

e. Power on the mobile station and wait until it reaches Mobile Station Idle State.27

f. Setup a call from party 1 to party 2 (from 10-digit CPN 1). Verify that the base28station sends an Alert With Information Message or Flash With Information Message29with an Extended Display information record and the PI field set to “00”30(Presentation Allowed).31

g. Verify the call is forwarded to the mobile station and that the mobile station32properly receives and displays the CNA and CNI of both the original calling party 133and the redirected party 2 during the first alerting cycle.34

h. Verify user data in both directions for party 1 (originating party), and the mobile35station.36

i. End call.37

TSG-C42 Page 9-14

10/19/2001 C.S0031

j. Power-off the mobile station.1

k. Change the PI field of the CPN information record of the calling parties (1 and 2) to2'01' (Presentation Restricted).3

l. Repeat steps e through j, except step g,4

m. Verify the mobile station does not display the CNA or CNI associated with parties51 and 2, and that it indicates the CNA is restricted during the first alerting cycle.6

n. Change the PI field of the CPN information record of the calling party to '10'7(Number Not Available).8

o. Repeat steps e through j, except step g, verify the mobile station does not display9the CNA or CNI associated with parties 1 and 2 and that it indicates the CNA is not10available, during the first alerting cycle.11

9.6.3.3 Minimum Standard12The mobile station receiving a redirected call shall:13

a. Display the CNA and CNI associated with both the originating and redirecting14calling parties when the PI field of the CPN information record of both are set to '00'.15

b. Not display the CNA or CNI associated with both the originating and redirecting16calling parties but shall indicate the CNA is restricted when the PI field of both are17set to '01'.18

c. Not display CNA or CNI associated with the originating and redirecting calling19parties.20

d. Indicate the CNA is not available when the PI field of both the originating and21redirecting calling parties are set to '10'.22

9.7 Display Records23

9.7.1 Display Records sent in the Feature Notification Message.24

9.7.1.1 Definition25This test verifies that the mobile station displays Paging Channel Display Information Records26and Extended Display Information Records. This test also verifies that Display Information27Records and Extended Display Information Records do not interfere with any other information28records or features.29

3031


2.6.2.4: Mobile Station Order and Message Processing Operation332.6.4.3: Alerting343.7.2.3.2.12: Feature Notification Message353.7.3.3.2.3: Alert with Information Message363.7.3.3.2.14: Flash with Information Message37

TSG-C42 Page 9-15

10/19/2001 C.S0031



b. Verify the mobile station is in Mobile Station Idle State.3

c. Instruct the base station to send a display record of at least 15 characters in a4Feature Notification Message.5

d. Upon receiving the Feature Notification Message, verify the mobile station displays6characters as instructed in the display record or extended display record contained7in the Feature Notification Message.8

e. Instruct the base station to send a new display record of at least 15 characters in a9Feature Notification Message.10

f. Upon receiving the Feature Notification Message, verify the mobile station displays11the new characters as instructed in the display record, and performs other12information records contained in the Feature Notification Message without user13interaction with the mobile station.14

9.7.1.3 Minimum Standard15All information records contained in the Feature Notification Message, if supported by the16mobile station, shall be performed without user interaction with the mobile station. When various17information records are sent to the mobile station in the same message, the mobile station shall18properly perform all information record instructions. If display records are not supported in the19mobile station, there shall be no negative impact on information records supported by the mobile20station. There shall be no negative impact on any supported feature or on call processing when21display records are sent to the mobile station in the same message as other information records.22If supported by the mobile station, the most current display record shall be displayed on the23mobile station.24

9.7.2 Display Records Sent in the Flash With Information Message25

9.7.2.1 Definition26This test verifies that the mobile station displays Traffic Channel Display Information Records or27Extended Display Information Records. This test also verifies that Display Information Records28and Extended Display Information Records do not interfere with other information records or29features.30


2.6.2.4: Mobile Station Order and Message Processing Operation322.6.4.3: Alerting333.7.2.3.2.12: Feature Notification Message343.7.3.3.2.3: Alert with Information Message353.7.3.3.2.14: Flash with Information Message36




TSG-C42 Page 9-16

10/19/2001 C.S0031

c. Instruct the base station to send a display record of at least 15 characters in a Flash1With Information Message.2

d. Upon receiving the Flash With Information Message, verify the mobile station3displays characters as instructed in the display record or extended display4information record contained in the Flash with Information Message.5

e. Perform Test 3.4, Hard Handoff Between Frequencies in the Same Band.6

f. Immediately after the first hard handoff is completed, send from the base station a7new display record of at least 15 characters contained in the Flash with Information8Message.9

g. Upon receiving the Feature Notification Message, verify the mobile station displays10the new characters as instructed in the display record or extended display record11contained in the Flash with Information Message without user interaction with the12mobile station.13

h. Cause the base station to initiate another hard handoff, and send from the base14station a new display record or extended display record of at least 15 characters15contained in the Flash with Information Message.16

i. Upon receiving the Feature Notification Message, verify the mobile station displays17the new characters as instructed in the display record or extended display record18contained in the Flash with Information Message without user interaction with the19mobile station.20

j. Verify that multiple handoffs can be performed without dropping the call.21

9.7.2.3 Minimum Standard22All information records contained in the Flash with Information Message, if supported by the23mobile station, shall be performed properly without user interaction with the mobile station.24When various information records are sent to the mobile station in the same message, the mobile25station shall properly perform all information record instructions. If display records are not26supported in the mobile station, there shall be no negative impact on any information records27supported by the mobile station. There shall be no negative impact on any supported feature or28call processing when display records are sent to the mobile station in the same message as other29information records.30If supported by the mobile station, the most current display record shall be displayed on the31mobile station.32

9.7.3 Display Records Sent in the Alert With Information Message33

9.7.3.1 Definition34This test verifies the mobile station displays Display Information Records and Extended Display35Information Records on the traffic channel. This test also verifies that Display Information36Records or Extended Display Information Records do not interfere with other information37records or features.38


2.6.2.4: Mobile Station Order and Message Processing Operation40

TSG-C42 Page 9-17

10/19/2001 C.S0031

2.6.4.3: Alerting13.7.2.3.2.12: Feature Notification Message23.7.3.3.2.3: Alert with Information Message33.7.3.3.2.14: Flash with Information Message4



b. Setup a mobile station terminated call.7

c. Instruct the base station to send in an Alert With Information Message, a display8record or extended display record of at least 15 characters, and a Calling Party9Number Record.10

d. Upon receiving the Alert With Information Message, verify the mobile station displays11the characters as instructed in the display record or extended display record and12displays the Calling Party Number in the Alert With Information Message without13user interaction with the mobile station.14

9.7.3.3 Minimum Standard15All information records contained in the Alert with Information Message, if supported by the16mobile station, shall be performed without user interaction with the mobile station. When various17information records are sent to the mobile station in the same message, the mobile station shall18perform all information record instructions. If display records are not supported in the mobile19station, there shall be no negative impact on information records supported by the mobile station.20There shall be no negative impact on any supported feature, or on call processing when display21records are sent to the mobile station in the same message as other information records.22If supported by the mobile station, the most current display record shall be displayed on the23mobile station.24

9.8 TTY/TDD25

9.8.1 Definition26This test verifies the system ability to transfer TTY/TDD information in the forward and reverse27link directions.28

Traceability: (See [18,19 and 20] )29303132333435


j. Connect the mobile station as shown in Figure 9.8.2-1.3738

TSG-C42 Page 9-18

10/19/2001 C.S0031

MS

TE2M

MTO

MT2Rn

Um BS/MSC

Ai PSTN TE2LW

Specific Network Entity

Collective (Composite Entity)

Interface Reference Point

KEY

X

1Figure 9.8.2-1 Functional Setup for Testing TTY/TDD2

3

The base station (BS) in this model represents the entire system infrastructure. It4contains the transceiver equipment and Mobile Switching Center (MSC).5

Terminal Equipment (TE2) is TTY/TDD equipment connected either directly or6indirectly to the Mobile Terminal (MT2) on the mobile side of the connection. TE2 is7TTY/TDD equipment connected to the PSTN on the land side. Subscripts "M" and8"L" are added as needed to indicate mobile side and land side TE2s, respectively.9When combined in a single physical entity, TE2 and MT2 functionality is labeled10MT0.11

Setup a mobile station originated TTY/TDD call.12

Calibrate the forward link nominal attenuation so the average frame erasure rate is 3%.13

Verify characters typed at TE2M can be viewed at TE2L. Verify characters typed at TE2L can be14viewed at TE2M. See Annex C for example character text.15

Note: The following ASCII characters are not supported by the Baudot TTY standard and16should not be used to verify conformance: @ # % ^ & * < >17

Type a character sequence (e.g. “AB ”) repeatedly a minimum of 20 times at TE2M and verify18characters are properly viewed at TE2L. Type a character sequence (e.g. “AB”) repeatedly a19minimum of 20 times at TE2L and verify characters are properly viewed at TE2M.20

212223

If TE2M and TE2L support file transfer, perform the following steps:24

1) Prepare the TTY_text.txt 2K byte ASCII/Baudot file for 45.45 Baudot25transfer. (See Annex C).26

2) Transfer the ASCII/Baudot file from TE2M to TE2L.27

TSG-C42 Page 9-19

10/19/2001 C.S0031

3) Transfer the ASCII/Baudot file from TE2L to TE2M.1

End the TTY/TDD call.2

Setup a mobile station terminated TTY/TDD call.3

Repeat steps c through g.4

End the TTY/TDD call.5

If TE2M and MT2 support VCO/HCO (Voice Carry Over / Hearing Carry Over), perform the6following steps:7

1) Configure TE2M for VCO.8

2) Setup a mobile station originated TTY/TDD call.9

3) Verify outgoing messages can be spoken and incoming responses can be10viewed. Verify characters typed at TE2L can be viewed at TE2M.11

4) End the TTY/TDD call.12

5) Configure TE2M for HCO.13

6) Setup a mobile station originated TTY/TDD call.14

7) Verify outgoing messages can be typed and incoming responses can be15heard through a TE2M accessory speaker. Verify characters typed at TE2M can be16viewed at TE2L.17

8) End the TTY/TDD call.18

9.8.3 Minimum Standard19Characters typed at TE2M shall be properly viewed at TE2L. Characters typed at TE2L shall be20properly viewed at TE2M. Files transferred shall be complete. Character error rate should be less21than 1%.22

9.9 Answer Holding23

9.9.1 Definition24These tests verify that the mobile station that supports Answer Holding feature can perform the25following:26

• Activate answer holding when the incoming call is ringing in the Waiting for Mobile27Station Answer Substate or in the Conversation Substate.28

• Deactivate answer holding in the Conversation Substate.2930

TSG-C42 Page 9-20

10/19/2001 C.S0031

MS BS



AWI Message (ringing applied)

Connect Order

Conversation

Release Order

Release Order

Initiate a call

Disconnect the call

Page Response Message

General Page Message

Instruct the MS to activiateAnswer Holding


Falsh with Info (Keypad Facility Info Record)

Instruct the MS to deactivateAnswer Holding Falsh with Info (Keypad Facility Info Record)

AWI Message (Call Waiting)

Instruct the MS to activiateAnswer Holding Falsh with Info (Keypad Facility Info Record)

Instruct the MS to disconnectthe first call and deactivate

Answer Holding Falsh with Info (Keypad Facility Info Record)

1Figure 9.9.1-1 Reference Call Flow for Answer Holding2

3

Traceability: (See [4] ); 2.6.4.3.2, 2.6.4.4, 2.7.4.2, S.R.00084




c. Setup a mobile station terminated call from land party #1.8

d. When the mobile station is ringing and ring back tone is applied to the audio path,9instruct the mobile station to answer hold the call.10

e. Verify the mobile station sends a Flash With Information Message in assured mode11with a Keypad Facility information record with the CHARi field set to a pre-12

TSG-C42 Page 9-21

10/19/2001 C.S0031

programmed feature code (i.e., Switch Control Code: 18*) which indicates Answer1Holding.2

f. Verify the mobile station sends a Connect Order in assured mode.3

g. Instruct the mobile station to deactivate the answer holding.4

h. Verify the mobile station sends a Flash With Information Message in assured mode5with a Keypad Facility information record with the CHARi field set to a pre-6programmed feature code (i.e., Switch Control Code: 18*) which indicates Answer7Holding.8


j. Setup a call from land party #2 to the mobile station. Wait for ringback on land10party #2 and the call waiting notification on the mobile station.11

k. Instruct the mobile station to hold the incoming call from land party #2.12

l. Verify the mobile station sends a Flash With Information Message in assured mode13with a Keypad Facility information record with the CHARi field set to a pre-14programmed feature code (i.e., Switch Control Code: 18*) which indicates Answer15Holding.16

m. Instruct the mobile station to end the call from land party #1.17

o. Instruct the mobile station to deactivate the answer holding from land party #2.18

p. Verify the mobile station sends a Flash With Information Message in assured mode19with a Keypad Facility information record with the CHARi field set to a pre-20programmed feature code (i.e., Switch Control Code: 18*) which indicates Answer21Holding.22

q. Verify user data in both directions.23

r. End the call from land party #2.24

9.9.3 Minimum Standard25If the mobile station is directed to activate or deactivate answer holding, the mobile station shall26send a Flash With Information Message in assured mode with a Keypad Facility information27record with the CHARi field set to a pre-programmed feature code which indicates Answer28Holding.29

9.10 User Selective Call Forwarding30

9.10.1 Definition31These tests verify that the mobile station that supports User Selective Call Forwarding can32perform the following in both Waiting for Mobile Station Answer Substate and Conversation33Substate:34

• Forwarding incoming call to a pre-registered number.35• Forwarding incoming call to a number stored in the mobile station.36• Forwarding incoming call to network-based voice mail.37

TSG-C42 Page 9-22

10/19/2001 C.S0031

Traceability: (See [4] ); 2.6.4.3.2, 2.6.4.4, 2.7.4.21




c. Dial user selective call forwarding feature activation code, followed by the forward-to5number, followed by SEND. Verify feature update confirmation at the mobile station.6

d. Setup a mobile station terminated call from land party.7

e. When the mobile station is ringing and ring back tone is applied to the audio path,8instruct the mobile station to forward the incoming call to the pre-registered9number.10

f. Verify the mobile station sends a Flash With Information Message in assured mode11with a Keypad Facility information record with the CHARi field set to a pre-12programmed feature code (i.e., Switch Control Code: 0*) which indicates User13Selective Call Forwarding to a pre-registered number.14

g. Instruct the base station to release the traffic channel.15

h. Answer the call on the forwarded line, and verify the audio path.16

i. End call.17

j. Ensure the mobile station is in Mobile Station Idle State.18

k. Setup a mobile station terminated call from land party.19

l. When the mobile station is ringing and ring back tone is applied to the audio path,20instruct the mobile station to forward the incoming call to voice mail.21

m. Verify the mobile station sends a Flash With Information Message in assured mode22with a Keypad Facility information record with the CHARi field set to a pre-23programmed feature code (i.e. Switch Control Code: 17*) which indicates User24Selective Call Forwarding to voice mail.25

n. Instruct the base station to release the traffic channel.26

o. Verify the call is forwarded to voice mail.27

p. Ensure the mobile station is in Mobile Station Idle State.28

r. Program a forward-to-number in the mobile station.29

s. Setup a mobile station terminated call from land party.30

t. When the mobile station is ringing, and ring back tone is applied to the audio path,31instruct the mobile station to forward the incoming call to the number stored in the32mobile station.33

u. Verify the mobile station sends a Flash With Information Message in assured mode34with a Keypad Facility information record with the CHARi field set to a pre-35

TSG-C42 Page 9-23

10/19/2001 C.S0031

programmed feature code (i.e. Switch Control Code: 16*) plus the forward-to-1number stored in the mobile station.2

v. Instruct the mobile station to release the traffic channel.3

w. Answer the call on the forwarded line, and verify the audio path.4

x. End call.5

y. Setup a call between mobile station and land party #1 and verify user data in both6directions.7

z. Setup a call from land party #2 to the mobile station. Wait for ringback on land8party #2 and the call waiting notification on the mobile station.9

aa. Instruct the mobile station to forward the incoming call to the pre-registered10number.11

bb. Repeat steps f, h, and i.12

cc. Repeat step z.13

dd. Instruct the mobile station to forward the incoming call to voice mail.14

ee. Repeat steps m and o.15

ff. Repeat step z.16

gg. Instruct the mobile station to forward the incoming call to the forward-to-number17stored in the mobile station.18

hh.Repeat steps u, w, and x.19

ii. Verify user data in both directions between the mobile station and land party #120during steps z to hh.21

jj. End the call between mobile station and land party #1.22

9.10.3 Minimum Standard23If the mobile station is directed by the user to forward the incoming call to a pre-registered24number, voice mail, or a stored forward-to-number, the mobile station shall send a Flash With25Information Message in assured mode with a Keypad Facility information record with the26CHARi field set to a pre-programmed feature code which indicates User Selective Call27Forwarding to a pre-registered number, voice mail, or a stored forward-to-number28correspondingly.29

30

TSG-C42 Page 9-24

10/19/2001 C.S0031

No text1

TSG-C42 Page 10-1

10/19/2001 C.S0031

10 ASYNCHRONOUS DATA AND FAX SERVICES1Table 10-1 Asynchronous Data and Fax Services tests.2

Table 10-1 Asynchronous Data and Fax Services Tests3

Test No. Title

10.1 Send/Receive Fax

10.2 Upload/Download Binary File

10.3 Simultaneous Two-way File Transfer

10.4 Compound AT Command

10.5 Escaping to Command Mode

10.6 Air Interface Data Compression

10.7 RLP Operation in Rayleigh Fading Environment

10.8 RLP Abort and TCP Retransmit

10.9 Internet Control Message Protocol (ICMP) Requests/Replies

10.10 Reflection of AT Command Parameters

Introduction4

TIA/EIA/IS-707-A defines Service Option 4 (Async Data) and Service Option 5 (Group-3 Fax)5for use over IS-2000 traffic channels. The following tests ensure proper data call processing for6both Service Options 4 and 5. These same tests should be applicable for future Service Option 127(Rate Set 2 Asynchronous Data) and Service Option 13 (Rate Set 2 Fax).8A network reference model of a CDMA data services system per IS-707-A, is shown in Figure910.1-1. The model shows network elements contained within the data/fax network, and interfaces10between them.11

12

Um LBS/MSC

MSMT0

TE2M MT2Rn

Speci fic Network Entity


X Interface Reference Point

Key

IWF PPDNPi

Ai WPS TN DCE RV TE 2L

13Figure 10-1. Asynchronous Data Services Reference Model14

TSG-C42 Page 10-2

10/19/2001 C.S0031

The base station (base station) in this model represents the entire cellular system infrastructure. It1contains transceiver equipment, Mobile Switching Center (MSC), and Inter-Working Function2(IWF) required for network connection.3Terminal Equipment (TE2) is data equipment connected either directly or indirectly to the4Mobile Terminal (MT2) on the mobile side of the connection. Alternatively, a TE2 may be5connected to Data Circuit-Terminating Equipment (DCE) on the land side. Subscripts "M" and6"L" are added as needed to indicate mobile side and land side TE2s, respectively. When7combined in a single physical entity, TE2 and MT2 functionality is labeled MT0.8Test Execution Strategy9

Unless otherwise stated in the procedure, the following conditions shall be an integral part10of the method of measurement in each of the tests listed below. A communications11application program used for testing asynchronous data service. When using12aforementioned communications application, hardware flow control shall be enabled,13and software flow control shall be disabled.14

• When a transfer time is to be recorded, the transfer timer should be started when the15upload command is entered at the sender side, and should be stopped when the receiver16has finished receiving the entire file/fax.17

• Any Class 2.0 fax application program may be used for testing fax services. Data18Services Annex A lists examples of fax programs that may be used.19

• These tests apply to computer-based fax applications only.20

• At the mobile end, the application program runs on a computer (labeled TE2M in Figure2110-1) attached to an async data-capable CDMA phone.22

• At the fixed end, the application program runs on a computer (labeled TE2L in Figure 10-231) attached to a PSTN modem, connected to a Public Switched Telephone Network (PSTN)24or a PSTN emulation unit.25

• For all Service Option 4 and Service Option 12 tests, ensure modem error correction,26such as Link Access Protocol - Modem (LAP-M) or Microcom Network Protocol (MNP), is27enabled on the PSTN link (see network reference diagram of Figure 10-1). Ensure the28PSTN link between the base station and the Data Circuit Terminating Equipment (DCE)29is a link known to be of good quality.30

• Both RV and RM links are running at a speed greater than the maximum expected speed31on the UM link.32

• The application program is started at both TE2M and TE2L, and should be maintained33throughout test execution.34

• Auto Answer is enabled at both TE2M and TE2L.35

• Unless otherwise noted, each test shall provide a frame error rate of 1% or less.36

• Prior to each test, the mobile station shall be reset to default state by pressing the END37key to assure no call is in progress, then issuing the command ATZ <CR>.38

TSG-C42 Page 10-3

10/19/2001 C.S0031

10.1 Send/Receive Fax1

10.1.1 Definition2These tests demonstrate cellular system ability to transmit and receive a medium size fax in a3timely manner. A fax call is originated by the mobile station, the test is then repeated using land4line origination. The mobile station will send and receive a digital and an analog Fax.5

Traceability:6(See [15] )-A.3; 2.2, 2.2.1, 4.0, 4.3, 7.37(See [15] )-A.4; 2.2, 2.5.5, 3.1, 3.2, 3,3, 3,3,1,1, 3.4.1, 4.1.1, 4.1.2, 4.1.3, 4.28(See [15] )-A.79


10.1.2.1 Send/Receive Digital Fax11

a. Prepare a file representing three different ITU standard fax pages for fax transfer.12Data Services Annex C lists standard fax pages to be used in the test. Ensure fax13pages are pre-scanned and pre-encoded.14

b. Simultaneously start the transfer timer and the digital fax transfer from TE2M to15TE2L.16

c. At TE2L, wait for the fax call to be completed. Stop the transfer timer.17

d. Record transfer time. Verify transfer time requirements per Data Services Annex C.18

e. Repeat the test for the same fax sent from TE2L to TE2M. TE2M will receive a digital19fax.20

10.1.2.2 Send/Receive Analog Fax21

a. Prepare a file representing three different ITU standard fax pages for fax transfer.22Data Services Annex C lists standard fax pages to be used in the test. Ensure fax23pages are pre-scanned and pre-encoded.24

b. Attach an Analog Fax Machine to TE2M.25

c. Simultaneously start the transfer timer and the analog fax transfer from TE2M to26TE2L.27

d. At TE2L, wait for the fax call to be completed. Stop the transfer timer.28

e. Record transfer time. Verify transfer time requirements per Data Services Annex C.29

f. Repeat test for the same fax sent from TE2L to TE2M. TE2M will receive an analog30fax.31

10.1.3 Minimum Standard32All faxes shall be successfully transferred. The received fax shall be of good quality and33complete. This can be verified by qualitative means (visually scanning the received fax) or by34quantitative means, for example, using ITU-T Recommendation E.453 (08/94) Facsimile Image35Quality as Corrupted by Transmission Induced Scan Line Errors.36

TSG-C42 Page 10-4

10/19/2001 C.S0031

Each analog fax transfer shall be completed within time denoted in Data Services Annex C.1

10.2 Upload/Download Binary File2

10.2.1 Definition3This test demonstrates cellular system ability to upload and download an ITU standard fax binary4file in a timely manner. The asynchronous data call is originated first by the mobile station. The5test is then repeated using land line origination.6

Traceability:7(See [15] )-A.3; 2.2, 2.2.1, 4.0, 4.3, 7.38(See [15] )-A.4; 2.2, 2.5.5, 3.1, 3.2, 3,3, 3,3,1,1, 3.4.1, 4.1.1, 4.1.2, 4.1.3, 4.29


a. Prepare RAND200.BIN 200,000 byte binary file for transfer (Data Services Annex D).11

b. Setup a data call from TE2M to TE2L.12

c. Start transferring the binary file from TE2L to TE2M using Z-modem transfer13protocol. Start the transfer timer.14

d. Stop the transfer timer when the confirmation of transfer completion is received15from the far end.16

e. Record the transfer time.17

Note: Transfer time should exclude call connection delay.18

f. End the data call.19

g. Setup a data call from TE2L to TE2M.20

h. Repeat the test by transferring the file from TE2M to TE2L.21


• All files shall be successfully transferred.23

• There shall be no Z-modem protocol re-transmissions.24

• Received files shall be complete and identical in content to the original file.25

• Each file transfer shall be completed within time denoted in Data Services Annex D.26

• Both the mobile station originated, and land line originated data calls shall be27established successfully.28

10.3 Simultaneous Two-way File Transfer/Carrier Detect29

10.3.1 Definition30This test demonstrates cellular system ability to simultaneously transfer data in the forward and31reverse link direction. This test verifies the base station can transmit changes in the status of32circuit 109 (Carrier Detect) and reflect its status on the Rm interface (Figure 10.1-1).33

TSG-C42 Page 10-5

10/19/2001 C.S0031

Note: Carrier Detect can be monitored by means of a hardware lead, or observed on the1application interface.2

Traceability:3(See [15] )-A.3; 2.1.1, 2.2, 2.2.1, 4.0, 4.2.1, 4.3, Table 7.1.1-1, 7.34(See [15] )-A.4; 2.2, 2.5.5, 3.1, 3.2, 3,3, 3,3,1,1, 3.4.1, 4.1.1, 4.1.2, 4.1.3, 4.25


a Prepare the RAND200.ASC 200,000 byte ASCII file for transfer (Data Services Annex7D).8

b. Ensure the Carrier Detect indicator is enabled at TE2M.9

c. From TE2M, issue the command “AT&C1”, which requests the real-time status of10Carrier Detect be maintained on the (Rm) interface.11

d. Verify the Carrier Detect indicator is OFF.12

e. Setup a data call from TE2M to TE2L. Verify that Carrier Detect indicator goes ON,13when the base station modem has successfully trained.14

f. Verify characters typed at TE2M can be viewed at TE2L. Verify characters typed at15TE2L can be viewed at TE2M.16

Note: Once the File Capture is turned on, do not type any more characters on the TE2L or17the TE2 M prior to initiating the file transfer (this is to ensure the captured file is not18corrupted by user keystrokes).19

g. Turn on the File Capture at TE2M.20

h. Turn on the File Capture at TE2L.21

i. Simultaneously start the reverse link transfer timer and at TE2M send the22RAND200.ASC file to TE2L by using Raw ASCII protocol.23

j. While TE2M is sending the file to TE2L, simultaneously start the forward link24transfer timer and instruct TE2L to send the same ASCII file to TE2M using a Raw25ASCII protocol.26

Note: It is critical these transfers shall substantially overlap.27

k. As each transfer completes, stop corresponding transfer timer and record transfer28time.29

l. After both transfers are complete, turn off the File Capture at both TE2M and TE2L.30

m. End call.31

n. At TE2M, verify that Carrier Detect indicator goes OFF when the call is ended.32


• The file shall be successfully transferred in each direction.34

• Log files shall be complete and identical in content to the original files.35


TSG-C42 Page 10-6

10/19/2001 C.S0031

• The Carrier Detect generated by the base station shall be accurately depicted on the Rm1interface.2

10.4 Compound AT Command, Initialization and Connection Delay3

10.4.1 Definition4This test verifies the base station can properly process a compound command line containing5both local and remote commands. This test verifies the mobile station can initialize and connect6the service option when the data call is negotiated with the base station, as well as measures7connection delay.8

Traceability:9(See [15] )-A.3; 4.2.6, Table4.2.6-1, 4.3.1.2.5, 4.4.1, Table 7.2-1, Table 7.3.1-110


a. Ensure the call is down.12

b. At TE2M, issue AT command13“AT+CXT=1;+FCLASS=2.0;+GMI;+CGMI;+GMM;+CGMM”. This command string14requests mobile station manufacturer information, base station modem15manufacturer information, mobile station manufacturer model, and base station16modem manufacturer model.17

c. Start the connection delay timer.18

d. When the result is returned to the mobile station, stop the connection timer.19

e. Record connection delay time in the test report.20

10.4.3 Minimum Standard21The response shall be correct in that it contains the information requested in the command, and is22followed by result code “OK”. Delay should not exceed ten seconds.23

10.5 Escaping to Command Mode24

10.5.1 Definition25This test verifies:26

• The MT2 application interface escapes to online command state when the user (or the27communications application) issues an escape sequence (such as "+++" with the28appropriate guard time).29

• The base station returns to online state when the user (or the application) issues the30command "ATO".31

Traceability: (See [15] )-A.3; 4.2.4, 4.4.2.132


a. Setup a data call from TE2M to TE2L.34

TSG-C42 Page 10-7

10/19/2001 C.S0031

b. Verify characters typed at TE2M can be viewed at TE2L. Verify that characters typed1at TE2L can be viewed at TE2M.2

c. From TE2M issue the escape sequence +++.3

d. Verify “OK” is returned, signifying that the MT2 is in the online command state.4

e. At TE2M,issue the command “AT+CGMI" which requests base station manufacturer5information. Verify the response is appropriate, with trailing “OK”.6

f. At TE2M, issue the command “ATO”, which should cause the MT2 to transition from7online command state to online state.8

g. Verify characters typed at TE2M can be viewed TE2L. Verify characters typed at TE2L9can be viewed at TE2M.10


• The escape sequence shall cause entry into the online command state.12

• The command “ATO” shall cause return from the online command state to online state.13

10.6 Air Interface Data Compression14

10.6.1 Definition15This test verifies successful compression option negotiation and the transfer of compressible files16and/or faxes between the MT2 and Inter-Working Function (IWF). The aforementioned is verified17for both mobile originated and mobile terminated data and fax transmissions.18

Note: Although the files are compressible, they will be compressed only when both the MT219and IWF support the type of compression in question. Even if the MT2 or IWF do not20support a certain type of compression, the test in question still needs to be performed21to ensure MT2 and IWF still interoperate correctly when the user requests this type of22compression.23

Traceability:24(See [15] )-A.3; Table 7.4.1-125(See [15] )-A.4; 2.2, Table 2.2-2, Table 2.2-326


a. Prepare the data file, COMPFILE.RAW (see Data Services Annex A), or the fax page,28FAX 1 (see Data Services Annex C) for transfer.29

b. Configure the test setup for transfer of a data file or a fax file per Table 10.6.2-1.30V.42bis compression for data file transfers is controlled by the +CDS command. The31type of compression for fax file transfers is controlled by the +CFC command. When32V.42bis is selected for fax transfer, the parameters set in the +CDS command are33used.34

c. Setup a mobile station originated fax or async data call per Table 10.6.2-1.35

d. Make a file or fax transfer in the direction as stated in Table 10.6.2-1. Time each36transfer and record in the test report.37

TSG-C42 Page 10-8

10/19/2001 C.S0031

e. Repeat for all test cases, 1 through 10.1


• All faxes shall be successfully sent and received.3

• The received fax page shall be complete in content, and each transfer shall be completed4within the time stated in Data Services Annex C.5

• All data files shall be successfully transferred.6

• The received files shall be complete and identical in content to the original file. Each file7transfer shall be completed within the time stated in Data Services Annex B.8

9

Table 10.6.2-1 Compression Test Configurations10

TestNo.

File/Fax CompressionMethod

Directionof Transfer

CompressionEnable

FaxCompression

Mode

1 Data File none BS to MS +CDS=0 N/A

2 Data File V.42bis BS to MS +CDS=2 N/A

3 Data File V.42bis MS to BS +CDS=1 N/A

4 Data File V.42bis MS to BS +CDS=3 N/A

5 Fax File none BS to MS N/A +CFC=0

6 Fax File V.42bis BS to MS +CDS=2 +CFC=1

7 Fax File V.42bis MS to BS +CDS=1 +CFC=1

8 Fax File V.42bis MS to BS +CDS=3 +CFC=1

9 Fax File MMR BS to MS N/A +CFC=2

10 Fax File MMR MS to BS N/A +CFC=2

11

10.7 RLP Operation in a Poor RF Environment12

10.7.1 Definition13This test exercises the Radio Link Protocol (RLP) layer's negative acknowledgments (NAKs), re-14transmits, RLP aborts, RLP Resets, and FCSs.15Test conditions are intended to impose one or more occurrences of the following.16

• Single, double, and triple NAK RLP retransmit events.17

• RLP Abort18

• RLP Reset19This test verifies that RLP recovers erased data frames in various channel conditions.20

TSG-C42 Page 10-9

10/19/2001 C.S0031

Traceability:1(See [15] )-A.2; 3.1, 3.1.1.1, 3.1.2, 3.1.42


a. Setup the mobile station and base station as shown in Figures 10.7.2-1 with an4AWGN generator placed in the forward link.5

6

7Figure 10.7.2-1 Test Setup for RLP Operation in Poor RF8

Environment Test Parameters910

b. Adjust the level of the AWGN Generator so that the downlink frame error rate is11measured to be 3±1%.12

c. Restore the RF link to a normal operating condition, maintaining the target frame13error rate (1 % or less).14

d. Prepare RAND200.ASC 200,000 byte ASCII file for transfer (Data Services Annex D).15

e. Setup a data call from TE2M to TE2L.16

f. Verify characters typed at TE2M can be viewed at TE2L. Verify characters typed at17TE2L can be viewed at TE2M.18

g. Turn File Capture on.19

h. Simultaneously start the forward link transfer timer and at TE2L send the20RAND200.ASC file to TE2M by using Raw ASCII protocol.21

i. As soon as the file transfer has started (and is still in progress), set the channel22conditions as calibrated in step b. These channel conditions shall be maintained for23the duration of the file transfer.24

j. Stop the transfer timer and record the transfer time.25

k. Turn off the File Capture.26

l. End call.27

TSG-C42 Page 10-10

10/19/2001 C.S0031

m. Setup a data call from TE2M to TE2L.1

n. Repeat steps f and g.2

o. Simultaneously start the reverse link transfer timer and at TE2M send the3RAND200.ASC file to TE2L by using Raw ASCII protocol.4

p. Repeat steps i through l.5


• The file shall be successfully transferred.7

• The log file shall be complete and identical in content to the original file.8

• The transfer rate shall be no less than 70% of rates measured in test 10.3.9

10.8 RLP Abort and TCP Retransmit Test10

10.8.1 Definition11This test causes the RLP layer to abort and reset due to extremely severe CDMA channel12conditions, and forces the TCP layer to retransmit packets. Channel degradation consists of13forcing consecutive frame erasures for periods greater than 2.6 seconds.14

Note: 2.6 seconds corresponds to 130 consecutive frame erasures, but less than the time15that would cause the call to drop (typically 5 seconds).16

Traceability:17(See [15] )-A.2; 3.1, 3.1.1.1, 3.1.2, 3.1.418


a. Setup the mobile station and base station as shown in Figures 10.8.2-1 and 10.8.2-202 for the forward and the reverse link tests respectively, with21PWR_THRESH_ENABLE and PWR_PERIOD_ENABLE set to 0. Disable forward link22power control at the base station.23

24

25Figure 10.8.2-1 Test Setup for RLP Abort in Forward Link26

TSG-C42 Page 10-11

10/19/2001 C.S0031

1

2Figure 10.8.2-2 Test Setup for RLP Abort in Reverse Link3

b. Calibrate the test setup so that:4

(1) There is sufficient isolation with the switch open, that a call drops if the5switch is left open for more than 5 seconds6

(2) When switch is open, the forward and reverse links are disabled at the7receiver.8

(3) When switch is closed, the forward and reverse links are enabled at the9receiver.10

c. Set the RF link to normal operating condition, which maintains the target frame11erasure rate (1% or less).12

d. Prepare the RAND200.ASC 200,000 byte ASCII file transfer (Data Services Annex D)13

e. Setup a call from TE2M to TE2L.14

f. Verify characters typed at TE2M can be viewed at TE2L. Verify that characters typed15at TE2L can be viewed at TE2M.16

g. Turn File Capture on.17

h. Simultaneously start the forward link transfer timer and at TE2L send the18RAND200.ASC file to TE2M by using Raw ASCII protocol.19

i. Once the file transfer has started (and is still in progress), open and close the switch20in an alternating fashion, for periods of T1 and T2 where:21

(1) T1 is the period when the switch is open (RF link impaired), and it is22anywhere between 2.6 and 5.0 seconds.23

(2) T2 is the period when the switch is closed (RF link restored), and it is a24minimum of 10 seconds.25

j. Repeat opening and closing switch exactly three times while data transfer is26occurring.27

TSG-C42 Page 10-12

10/19/2001 C.S0031

k. Stop the transfer timer and record the transfer time.1

l. Turn the File Capture off.2

m. End call.3

n. Setup a data call from TE2M to TE2L.4

o. Repeat steps f and g.5

p. Simultaneously start the reverse link transfer timer and at TE2M send the6RAND200.ASC file to TE2L by using Raw ASCII protocol.7

q. Repeat steps i through l.8




• Transfer rates shall be no less than 50% of rates measured in test 10.3.12

10.9 Internet Control Message Protocol (ICMP) Requests/Replies13

10.9.1 Definition14This test verifies the mobile station is able to:15

• Generate an ICMP Echo Response Message after receiving an Echo Request Message.16

• Generate an ICMP Info Response Message after receiving an Info Request Message.17

• Generate an ICMP Time Stamp Response Message after receiving a Time Stamp Request18Message.19

Traceability: RFC 79220


a. At TE2M, issue a remote query command such as “AT+CXT=1;+FCLASS=2.0;+FMI?”,22requesting base station modem manufacturer information. This will establish a link23to the base station.24

b. From the OA&M interface of the base station, issue the Echo Request Message by25any method specific to the base station manufacturer.26

c. Optionally, step b may be repeated for Info Request/Response, or Time Stamp27Request/Response Messages.28


• Echo response shall be received by base station as a response to Echo Request Message.30

• If supported by mobile station, an Info response shall be received by base station as a31response to Info Request Message.32

TSG-C42 Page 10-13

10/19/2001 C.S0031

• If supported by mobile station, a Time stamp response shall be received by base station1as a response to Time Stamp Request Message.2

10.10 Reflection of AT Command Parameters3

10.10.1 Definition4This test verifies a representative set of AT parameters can be setup in an IS-707-A call,5transferred to the base station at call origination, changed in the online command state, and have6their final values read at the mobile station after call completion. Commands tested are ATS107and AT+CQD.8

Traceability: IS-707-A; 4.2.4, 7.4.19


a. Issue the AT command string: “ATS10=255;+CQD=0”11

b. Verify response is “OK”12

c. Setup a data call from TE2M to TE2L.13

d. After CONNECT is received, issue the escape sequence (such as ”+++”).14

e. Verify the response is “OK”15

f. Issue the AT command string: “ATS10?;+CQD?”.16

g. Verify response is:17

25518+CQD:019OK20

h. Issue the AT command string: “ATS10=250;+CQD=100”21

i. Verify the response is “OK”22

j. Issue the command string: “ATS10?;+CQD?”.23

k. Verify the response is:24

25025+CQD:10026OK27

l. Terminate the call via the “ATH0” command string.28

m. Verify the response is “OK” and that the call ends.29

n. Issue the AT command string: “ATS10?;+CQD?”.30

o. Verify response is:31

25032+CQD:10033OK34

TSG-C42 Page 10-14

10/19/2001 C.S0031

10.10.3 Minimum Standard1The responses shall be as specified in the previous paragraphs. The “ERROR” response shall not2be returned.3

TSG-C42 Page 11-1

10/19/2001 C.S0031

1

11 PACKET DATA SERVICES TESTS2Table 11-1 Packet Data Services tests.3

4

Table 11-1 Packet Data Services Tests5

Test No. Title

11.1 Terminal Session with Remote Host

11.2 File Transfer

11.3 IP Address Negotiation

11.4 V-J Header Compression

11.5 Asynchronous Control Character Mapping (ACCM) Negotiation

11.6 PPP Field Compression

11.7 Maximum Receive Unit (MRU)

11.8 Mobile Station Inactivity Timer

11.9 IWF Inactivity Timer

11.10 Radio Link Protocol (RLP) Operation in Rayleigh Fading

11.11 RLP Abort and Upper Layer Retransmit

11.12 RLP Encryption Negotiation

11.13 Hardware Flow Control

11.14 Re-connect after Hard Handoff

11.15 Zone-Based Registration for Packet Data Mobile Stations

6Introduction7TIA/EIA/IS-707-A defines Service Option 7 (Packet Data Service: Internet or ISO Protocol8Stack) and Service Option 8 (Packet Data Service: CDPD Protocol Stack) for use over IS-20009traffic channels. The following tests ensure proper data call processing for both Service Options107 and 8. These same tests should be applicable for future Service Options 15 (Rate Set 2 Packet11Data Service: Internet or ISO Protocol Stack) and Service Option 16 (Rate Set 2 Packet Data12Service: CDPD Protocol Stack).13A network reference model of a CDMA packet data services system per IS-707 is shown in14Figure 11-1. The model shows network elements contained within the packet data network, and15interfaces between them.16

17

TSG-C42 Page 11-2

10/19/2001 C.S0031

Um LBS/MSC

MSMT0

TE2M MT2Rn

Speci fic Network Entity


X Interface Reference Point

Key

IWF PPDNPi

Ai WPSTN DCE RV TE2L

1Figure 11-1 Packet Data Services Reference Model2

3The base station (BS) in this model represents the entire cellular system infrastructure, and4contains transceiver equipment and Mobile Switching Center (MSC).5Terminal Equipment (TE2) is data equipment connected either directly or indirectly to the6Mobile Terminal (MT2) on the mobile side of the connection. When combined in a single7physical entity, TE2 and MT2 functionality is labeled MT0. The Interworking Function (IWF)8provides network access between the Public Packet Data Network (PPDN) and the mobile9station.10Test Execution Strategy11Tests defined herein verify packet data services operation and features in a lab environment.12Some application level tests, which can be used to verify interoperability and performance in a13field system, are defined for Stage 3 field tests. It is recommended that tests described herein be14performed at Stage 2 to verify packet data operation prior to deployment in the field. However,15these same tests may be repeated in the field.16When an optional feature or function of packet data service is not supported by the mobile17station or the base station, the test may be omitted, but that fact shall be duly noted in the test18report as not being supported by appropriate element(s) of the system. When an optional feature19is implemented by both the mobile station and BS/MSC/IWF, that test shall be performed.20Tests may be performed in any order. It is permissible to conduct multiple tests at once by21combining procedures not mutually exclusive.22Unless otherwise stated in the procedure, the following conditions shall be an integral part of the23method of measurement in each of the following tests.24

• A remote host is a packet node with a known IP address with access privileges for the25purpose of interoperability testing.26

• Whenever a transfer time is to be recorded, the transfer timer should be started right as27the upload command is entered at the sender side, and should be stopped when the28receiver has finished receiving the entire file.29

TSG-C42 Page 11-3

10/19/2001 C.S0031

• Examples given in the test procedures assume the remote host is running the Unix1operating system. However, this is not a requirement for interoperability testing.2

• The Rm link (as diagramed in Figure 11-1) runs at a speed of 19.2 Kbps or greater.3

• The application program is run at the TE24

• Unless otherwise noted, each test shall provide a frame error rate of 1% or less on the air5link.6

• After each test, the application shall terminate its current PPP session.7

• All communication with remote hosts shall take place via the packet data service option.8

11.1 Terminal Session with Remote Host9

11.1.1 Definition10This test will demonstrate the ability of the mobile station to establish terminal-to-host session11with a remote host. Data transfer capability in both directions is tested.12

Traceability: (See [15] )-A, RFC-85413


a. Initiate a Telnet session to the remote host.15

b. Issue the remote command “ls”.16

11.1.3 Minimum Standard17Response received shall be the listing of the remote directory.18

11.2 File Transfer19

11.2.1 Definition20This test demonstrates the ability of the mobile station to transfer files to and from a remote host.21Data transfer throughput is tested in both directions.22

Traceability: [see 15]-A 4.1, RFC-95923


a. Prepare the RAND200.BIN 200,000 byte test file for file transfer (Data Services25Annex D). A copy of the file must reside at the remote host and at the TE2.26

b. Initiate an FTP session with the remote host.27

c. While measuring transfer time, transfer the file from the TE2 to the remote host and28record transfer time.29

d. While measuring transfer time, transfer the file from the remote host to the TE2 and30record transfer time.31


• All files shall be successfully transferred.33

TSG-C42 Page 11-4

10/19/2001 C.S0031

• Received files shall be complete and identical in content to the original file.1


11.3 IP Address Negotiation3

11.3.1 Definition4This test will demonstrate the ability of the IWF to assign unique IP address to various mobile5stations. This test applies only to mobile stations that do not have a fixed IP address.6

Traceability: [see 15]-A 3.1, RFC-1332 3.37


a. Setup a Telnet session on mobile #1 with a remote host.9

b. Setup a Telnet session on mobile #2 with a remote host.10

c. Determine the IP address assigned to mobile stations #1 and #2 using any method11available such as PPP Package, 'ping', "who", etc.12

11.3.3 Minimum Standard13IP addresses assigned to mobile station #1 and mobile station #2 shall be different.14

11.4 V-J Header Compression15

11.4.1 Definition16This test will demonstrate PPP ability to negotiate V-J header compression. Successful17compression is verified by comparing transfer times of groups of packets with V-J header18compression ON and OFF. This test requires use of a PPP package that allows the user to19configure V-J header compression.20

Traceability: (See [15] )-A, RFC-1332 3.2, RFC-1332 4, RFC-114421


a. Set the TCP Maximum Segment Size (MSS) to 536 bytes.23

b. Prepare RAND200.BIN for transfer (Data Services Annex D)24

c. Disable V-J header compression.25

d. Initiate an FTP session from the TE2 to the remote host.26

e. Transfer the file from the remote host to the TE2 using the [binary] "get"27

f. Record the bytes/sec reported by FTP at the end of the file transfer.28

g. Enable V-J header compression29

h. Repeat steps d through f.30



TSG-C42 Page 11-5

10/19/2001 C.S0031

• The received file shall be complete and identical in content to the original file.1

• Transfer throughput reported by FTP in bytes/sec with V-J header compression ON shall2be greater than the throughput with V-J header compression OFF.3

11.5 Aynchronous Control Character Mapping (ACCM) Negotiation4

11.5.1 Definition5This test verifies the ability to negotiate and perform ACCM.6

Traceability: (See [15] )-A, RFC-1662 7.17


a. Turn software flow control on and disable hardware flow control in the TE2.9

b. Enable software flow control in the MT2.10

c. Configure the ACCM in the mobile station side PPP package to be 0xFFFFFFFF,11which requires escaping of all characters having values of 0x00-0x1F.12

d. Initiate an FTP session with the remote host.13

e. Transfer the COMPFILE.RAW file from the TE2 to the remote host using the binary14”put” command.15



• The received file shall be complete and identical in content to the original file.18

11.6 PPP Field Compression19

11.6.1 Definition20This test demonstrates the ability to activate and de-activate the following PPP options:21

• Protocol Field Compression22

• Address and Control Field Compression23



a. De-activate both “Protocol Field Compression” and “Address and Control Field26Compression” in the mobile station.27

b. Issue a ''ping'' command to a remote host.28

c. Activate both “Protocol Field Compression” and “Address and Control Field29Compression” in the mobile station.30

d. Issue a ”ping” command to a remote host.31

TSG-C42 Page 11-6

10/19/2001 C.S0031

11.6.3 Minimum Standard1A proper ”ping” response shall be generated in both cases.2

11.7 Maximum Receive Unit (MRU)3

11.7.1 Definition4This test demonstrates mobile station ability to negotiate various MRU values.5



a. At the TE2, set TCP MSS to 1500.8

b. At the TE2, set PPP MRU to 1600.9

c. Initiate an FTP session from the TE2 to the remote host.10

d. Transfer the COMPFILE.RAW file from the remote host to the TE2 using the binary11get command.12



• Received file shall be complete and identical in content to the original file15

11.8 Mobile Station Inactivity Timer16

11.8.1 Definition17This test is only required for mobile stations that have an Inactivity Timer. This test verifies the18mobile station releases the traffic channel after expiration of the Inactivity Timer. The test19verifies the dormant link layer connection can be re-activated.20

Traceability: TIA/EIA/IS-707-A21


a. Set the inactivity timer at the MT2 to 15 seconds.23

b. Ensure the IWF’s inactivity timer is disabled or set to a value of at least 30 seconds.24

c. Initiate a Telnet session to a remote host.25

d. Record the IP address assigned to the mobile station.26

e. Exit the Telnet session.27

f. Wait for the mobile station inactivity timer to expire. Verify the “in use” indicator on28the MT2 goes OFF.29

g. Initiate a Telnet session to a remote host.30

h. Record the IP address assigned to the mobile station.31

TSG-C42 Page 11-7

10/19/2001 C.S0031


• The traffic channel shall be kept up until the mobile station inactivity timer expires. This2time should be approximately 15 seconds after termination of the first Telnet session.3

• The IP addresses of the mobile station recorded in steps d and h shall be identical (this4verifies the mobile station remained in dormant mode due to inactivity timer expiration).5

11.9 IWF Inactivity Timer6

11.9.1 Definition7This test is only required for IWFs that have an inactivity timer. This test verifies the base station8releases the traffic channel after expiration of the IWF inactivity timer. The tests verifies the9dormant link layer connection can be re-activated.10

Traceability: (See [15] )-A11


a. Set the IWF inactivity timer to 15 seconds.13

b. Ensure the MT2 inactivity timer is disabled or is set to a value of at least 3014seconds.15

c. Initiate a Telnet session to a remote host.16

d. Record the IP address assigned to the mobile station.17

e. Exit the Telnet session.18

f. Wait for the IWF inactivity timer to expire. Verify the “in use” indicator on the MT219goes OFF.20

g. Initiate a Telnet session to a remote host.21

h. Record the IP address assigned to the mobile station.22


• The traffic channel shall be kept up until the IWF inactivity timer expires. This time24should be approximately 15 seconds after termination of the first Telnet session.25

• The IP address of the mobile station recorded in steps d and h shall be identical (this26verifies the mobile station remained in dormant mode due to inactivity timer expiration).27

11.10 Radio Link Protocol (RLP) Operation in Rayleigh Fading28

11.10.1 Definition29This test exercises the RLP layer negative acknowledgments (NAKs), re-transmits, RLP aborts,30RLP resets, and FCSs. The test conditions are intended to impose one or more occurrences of the31following.32

• Single, double, and triple NAK RLP retransmit events33

• RLP Abort34

TSG-C42 Page 11-8

10/19/2001 C.S0031

• RLP Reset1This test verifies that RLP recovers erased data frames in various channel conditions.2

Traceability: IS-7073


a. Setup the mobile station and base station as shown in Figures 11.10.2-1, and511.10.2-2 for the forward and reverse link tests respectively, with the fading6simulator placed in the target link. Setup the channel simulators for 3-Ray Rayleigh7at 30 km/hr.8

9

10Figure 11.10.2-1 Test Setup for RLP Operation in Rayleigh Fading in Forward Link11

12

13Figure 11.10.2-2 Test Setup for RLP Operation in Rayleigh Fading in Reverse Link14

15

b. Calibrate the target link nominal attenuation so the frame erasure rate (FER) is16measured to be 3 ±1%17

c. Restore the RF link to a normal operating condition, which maintains the target18FER (1% or less).19

TSG-C42 Page 11-9

10/19/2001 C.S0031


e. On the forward link, issue a binary 'get' command from the TE2 to start receiving2the 200,000 byte binary file, RAND200.BIN (Data Services Annex D). For the reverse3link test, at TE2 issue a binary 'put' command to start sending the 200,000 byte4binary file, RAND200.BIN (Data Services Annex D), to the remote host.5

f. As soon as the file transfer has started (and is still in progress), set the channel6conditions as calibrated in step b. These channel conditions shall be maintained for7the duration of the file transfer.8

g. Repeat the test with file transfer occurring in the opposite direction.9



• Received files shall be complete and identical in content to the original files.12

• Transfer rates shall be no less than 70% of the rates measured in test 11.2 for the13corresponding rate set.14

11.11 RLP Abort and Upper Layer Retransmit15

11.11.1 Definition16This test causes the RLP layer to abort and reset due to extremely severe CDMA channel17conditions, and forces an upper layer to retransmit packets.18Channel degradation consists of forcing consecutive frame erasures for periods greater than 2.619seconds (2.6 seconds corresponds to 130 consecutive frame erasures), but less than the time that20would cause the call to drop (typically 5 seconds).21

Traceability: [see 15]22


a. Setup the mobile station and base station as shown in Figures 11.11.2-1 and2411.11.2-2 for the forward and the reverse link tests respectively, with25PWR_THRESH_ENABLE and PWR_PERIOD_ENABLE set to 0. Disable forward link26power control at the base station.27

b. Calibrate the test setup so that:28

1) There is sufficient isolation with the forward link switch open, so that a29call drops if the switch is left open for more than 5 seconds30

2) When the switch is open, the forward or reverse link is disabled at the31receiver32

3) When the switch is closed, the forward or reverse link is enabled at the33receiver34

c. Set the RF link to the normal operating condition, which maintains the target FER35(1% or less).36

TSG-C42 Page 11-10

10/19/2001 C.S0031


e. For the forward link test, issue a binary "get" command from the TE2 to start2receiving the 200,000 byte binary file, RAND200.BIN (Data Services Annex D). For3reverse link test, at TE2 issue a binary ”put” command to start sending the 200,0004byte binary file, RAND200.BIN (Data Services Annex D), to the remote host.5

f. Once file transfer has started and is in progress, open and close the switch in an6alternating fashion, for periods of T1 and T2 where:7

1) T1 is the period when the switch is open (RF link impaired), and it is8anywhere between 2.6 and 5.0 seconds.9

2) T2 is the period when the switch is closed (RF link restored), and it is a10minimum of 10 seconds. Repeat opening and closing the switch exactly three times11while data transfer is taking place.12

g. Repeat the test with the file transfer occurring in the opposite direction.13

h. If the mobile station and the base station support alternate rate sets, repeat the test14using all alternate rate sets.15

16

17Figure 11.11.2-1 Test Setup for RLP Abort in Forward Link18

19

TSG-C42 Page 11-11

10/19/2001 C.S0031

1Figure 11.11.2-2 Test Setup for RLP Abort in Reverse Link2

3




• Transfer rates shall be no less than 70% of rates measured in test 11.2.2 for the7corresponding rate set.8

11.12 RLP Encryption Negotiation9

11.12.1 Definition10This test will verify interoperability of the mobile station and base station in various RLP11encryption configurations. Configurations tested are dependent upon capabilities of the mobile12station and the base station. RLP Encryption is controlled by the base station for the purpose of13encryption export compliance.14


11.12.2 Method of Measurement16For each configuration in Table 11.12.2 -1 supported by the mobile station and base station, a17test should be performed and the outcome verified per the last column of this table.18Table 4.3.2-1 column labels have the following meaning:19BS Requirement If ‘Yes’, the base station is currently configured to require RLP20

Encryption for the connection of this service option.21MS Support If ‘Yes’, the mobile station supports RLP Encryption for this service22

option.23Service If ‘Yes’, the packet data service shall be granted.24

25

TSG-C42 Page 11-12

10/19/2001 C.S0031

Table 11.12.2 -1 RLP Encryption Configurations1

Configuration # Base StationRequirement

Mobile StationSupport

Service

1 Yes No No

2 Yes Yes Yes

3 No No Yes

4 No Yes Mobile StationDependent

2

a. For each configuration in Table 11.12.2 -1 supported by the mobile station and base3station, make a packet data call by issuing a 'ping' command to the remote host.4

b. Record outcome.5

11.12.3 Minimum Standard6Configuration 1 Packet Data service shall be denied.7Configuration 2 Packet Data service shall be granted.8Configuration 3 Packet Data service shall be granted.9Configuration 4 If mobile station requires RLP Encryption, Packet Data service shall be10

denied. Otherwise, Packet Data service shall be granted.11

11.13 Hardware Flow Control12

11.13.1 Definition13This test verifies Rm interface hardware flow control when Rm throughput exceeds Um14throughput.15

Traceability: TIA/EIA-232-E 4.4.5, TIA/EIA/IS-131, TIA/EIA/IS-7016


a. Ensure Rm baud rate is greater than Um data rate (an Rm baud rate of 19.2 kbps will18work for both rate sets).19

b. Enable hardware flow control on the Rm interface.20

c. Initiate an FTP session with the remote host.21

d. Transfer the COMPFILE.RAW file from the TE2 to the remote host using the binary22'put' command.23



• Received file shall be complete and identical in content to the original file.26

TSG-C42 Page 11-13

10/19/2001 C.S0031

11.14 Re-connect after Hard Handoff1

11.14.1 Definition2A mobile station with a dormant packet session does not register with a base station while it is up3on a traffic channel. The mobile station must therefore perform a reconnect after it completes4hard handoff for the network to know how to route a mobile station destined packet. This test5verifies that when the hard handoff re-connect feature is enabled, the mobile station reconnects6the packet data service option after it successfully completes a hard handoff. This test is required7only for base stations which have the Hard Handoff Re-Connect feature enabled per Section82.2.4.5 of IS-707. This test is required only for mobile and base stations that support9simultaneous voice and packet data. This test is required only for mobile stations that support10fixed IP addresses (CDPD mobiles).11

Traceability: (See [15] )-A12


a. Issue a 'ping' command to the remote host.14

b. Wait for packet data inactivity timer to expire and the traffic channel to be released.15

c. Start a call.16

d. While remaining in the call perform a hard handoff to a base station served by a17different IWF.18

e. While remaining in the call, issue a “ping” command from the remote host to the19mobile station.20

11.14.3 Minimum Standard21The remote host shall receive a “ping” response from the mobile station.22

11.15 Zone-Based Registration for Packet Data Mobile Stations23

11.15.1 Definition24This test verifies the BS/MSC can selectively activate IS-95 zone-based registration for mobile25stations with active packet data service. This test is required only for base stations that support26the optional packet data zone-based registration feature.27

Traceability:28

[see 4] 2.6.5.1.529

[see 15]30


a. Disable zone-based registration at the base station for voice users.32

b. Enable zone-based registration at the base station for packet data users.33

c. Ensure the mobile station is not in an active packed data session.34

TSG-C42 Page 11-14

10/19/2001 C.S0031

d. Ensure zone-based registration does not occur when mobile station moves to a new1zone.2

e. Activate packet data service for the mobile station (“ping” a remote host).3

f. Wait for the packet data inactivity timer to expire.4

g. While the packet data service remains active, move the mobile station to a new zone5containing the same SID.6


• The mobile station shall not perform zone-based registration prior to packet data service8activation.9

• The mobile station shall perform zone-based registration after packet service activation10when moved between zones.11

TSG-C42 Page 12-1

10/19/2001 C.S0031

1

12 MEDIUM-SPEED PACKET DATA2Table 12-1 Medium-Speed Packet Data Services tests for RC1 and RC2.3

4

Table 12-1 Medium-Speed Packet Data Tests5

Test No. Title

12.1 File Transfer with Forward and Supplemental Code Channels

12.2 File Transfer with Variable Supplemental Code Channels

12.3 MSPD Call Setup, No Negotiation

12.4 MSPD Call Setup, Negotiation to a Different HSPD Service Option

12.5 MSPD Call Setup, Negotiation to LSPD

12.6 MSPD Call Setup, Mobile station Maximum Multiplex Option Less than BaseStation Maximum Multiplex Option

12.7 MSPD Call Setup, Mobile station Maximum Multiplex Option Greater than BaseStation Maximum Multiplex Option

12.8 Allocation/De-allocation of Supplemental Code Channels

12.9 No Transmission on Supplemental Code Channels

12.10 Soft Handoff with Supplemental Code Channels

12.11 Adding Supplemental Code Channels during Soft Handoff

12.12 Hard Handoff to an MSPD-Capable System


12.14 RLP Operation with Severely Degraded Channel

12.15 Bi-Directional File Transfers with Supplemental Code Channels

12.16 Rm Interface Hardware Flow Control

12.17 Dormant Timer

12.18 Packet Zone ID

6

Note: For mobile station terminated calls, the mobile station must be in dormancy mode (with7assigned IP address) in order for terminated call procedures to work.8

12.1 Forward File Transfer with Fundamental and Supplemental Code Channels9

12.1.1 Definition10This test verifies that during the MSPD call, the measured forward throughput rate on the11Fundamental Code Channel and the Supplemental Code Channels matches the target throughput12rate under each of the following conditions:13

• No Supplemental Code Channels allocated (Test 1).14

TSG-C42 Page 12-2

10/19/2001 C.S0031

• One Supplemental Code Channel allocated (Test 2).1

• N Supplemental Code Channels allocated, where N is the maximum number of2Supplemental Code Channels that can be supported by the system (Test 3).3

Traceability:4

[see 4] 3.7.3.3.2, 3.6.6.2.2.9, 3.6.6.2.2.10;5

[see 15]-A9; 2.2.2.1.1;6


a. Prepare the RAND200.BIN byte binary file at the remote host.8

b. Setup an FTP session using Service Option 22 with the remote host. From the base9station, generate a General Handoff Direction Message or a Supplemental Channel10Assignment Message to allocate Supplemental Code Channels to the mobile station11according to the following conditions:12

1) For Test 1, the base station shall allocate no Supplemental Code Channel13to the mobile station (i.e. MUX Option = 1).14

2) For Test 2, the base station shall allocate one Supplemental Code15Channel to the mobile station (i.e. MUX Option = 3).16

3) For Test 3, the base station shall allocate N Supplemental Code17Channels to the mobile station (i.e. MUX Option = 2N+1).18

c. Transfer the file from the remote host to the TE2M using the binary “get” command.19

d. Record the elapsed time on the forward link of the Fundamental Code Channel20during the file transfer.21

e. After the file transfer is completed, end the FTP session22

f. Repeat steps b through e for Tests 2 and 3.23

g. Repeat steps b through f for Tests 1, 2, and 3 with Service Option 25.24

12.1.3 Minimum Standard25The file shall be transferred successfully and under ideal channel conditions, the file transfer26shall be completed within 8 x M / (0.625 x R x (N + 1)) seconds.27where:28

N = number of allocated Supplemental Code Channels29

M = size of the file (in bytes)30

R = RLP payload in bps (8000 bps for Rate Set 1 or 12800 bps for Rate Set 2)31

0.625 represents the acceptable margin for overhead and channel errors32

Note that the file transfer time requirement is based on the following assumptions:33

• N Supplemental Code Channels are allocated for the entire duration of34the file transfer.35

TSG-C42 Page 12-3

10/19/2001 C.S0031

• Supplemental Code Channel utilization is 100%.1

12.2 Forward File Transfer with Variable Supplemental Code Channels2

12.2.1 Definition3This test verifies the capability to transfer files from a remote host using FTP, with a variable4number of Supplemental Code Channels. This test is intended to exercise bursty data transfer5with variable peak transfer rates.6This test may require the use of an OA&M interface on the base station, or any other method7specific to the base station manufacturer, in order to vary the number of allocated Supplemental8Code Channels.9

Traceability:10

[see 4] 3.7.3.3.2, 3.6.6.2.2.9, 3.6.6.2.2.10;11

[see 15]-A9; 2.2.2.1.1;12


a. Prepare the RAND200.BIN byte binary file at the remote host.14

b. Configure the mobile station’s maximum forward Supplemental Code Channels to15N.16

c. Configure the base station to support N Supplemental Code Channels.17

d. Setup a mobile station terminated call with Service Option 22, and establish an FTP18session.19

e. From the base station, generate a General Handoff Direction Message to allocate N20Supplemental Code Channels to the mobile station.21

f. Verify from the mobile station that N Supplemental Code Channels are being used.22

g. Transfer the file from the remote host to TE2M using the binary “get” command.23

h. During through the file transfer, configure the base station to generate a General24Handoff Direction Message or a Supplemental Channel Assignment Message to25reduce the number of Supplemental Code Channels allocated to the mobile station.26

i. Record time elapsed during file transfer.27

j. End FTP session.28

k. Repeat steps d through j with Service Option 25.29

12.2.3 Minimum Standard30The file shall be transferred successfully in each direction, and, under ideal channel conditions,31the file transfer shall be completed within:32

8 x M / (0.625 x R x (S + 1)) seconds where:33

S = smallest number of Supplemental Code Channels allocated at any point34

M = size of the file (in bytes)35

TSG-C42 Page 12-4

10/19/2001 C.S0031

R = RLP payload in bps (8000 bps for Rate Set 1 or 12800 bps for Rate Set 2)1

0.625 represents the acceptable margin for overhead and channel errors2

12.3 MSPD Call Setup, No Negotiation3

12.3.1 Definition4This test verifies that the base station and the mobile station can successfully establish mobile5station-originated and mobile station-terminated calls using all combinations of supported6Service Option 22 through Service Option 25, using the default multiplex options.7

Traceability:8

[see 15]-A9; 2.2.2.1.2.59


a. Prepare the COMPFILE.RAW byte binary file at both the remote host and the TE2M.11

b. Configure the mobile station’s forward MUX Option to (2N+1) where N is the12maximum number of Supplemental Code Channels.13

c. Configure the base station’s MUX Option to a value equal to (2N+1).14

d. Setup a mobile station originated call with Service Option 22, and establish an FTP15session with the remote host.16

e. Verify that N Supplemental Code Channels are being used by the mobile station.17

f. Transfer the file from remote host to TE2M using the binary “get” command.18

g. After the file transfer is completed in step f, transfer the file from the TE2M to the19remote host using the binary “put” command.20

h. End FTP session.21

i. Repeat steps d through h by initiating a mobile station terminated call with Service22Option 22.23

j. Repeat steps b through i for Service Option 25. The base station’s MUX Option24should be set to (2N+2).25

k. Repeat steps d through i for mobile station terminated calls by setting the Service26Option to 23 at the base station.27

l. Repeat steps d through i for mobile station terminated calls by setting the Service28Option to 24 at the base station.29


• For mobile-originated and mobile terminated calls with Service Option 22, verify the31call is completed using Service Option 22.32

• For mobile-originated and mobile terminated calls with Service Option 25, verify the33call is completed using Service Option 25.34

TSG-C42 Page 12-5

10/19/2001 C.S0031

• For mobile terminated calls with Service Option 23, verify the call is completed1using Service Option 23. Note that for mobile stations that do not support Service2Option 23 the call should be completed with Service Option 25.3

• For mobile terminated calls with Service Option 24, Verify the call is completed4using Service Option 24. Note that for mobile stations that do not support Service5Option 24 the call should be completed with Service Option 25.6

• In all tests conducted, the files shall be successfully transferred. Received files shall7be complete and identical in content to the original file.8

12.4 MSPD Call Setup, Negotiation to a Different MSPD Service Option9

12.4.1 Definition10This test verifies that the base station and the mobile station can successfully negotiate from11Service Option 22 to Service Option 25, and vice versa.12

Traceability:13

[see 15]-A9; 2.2.2.1.2.514


k. Prepare the COMPFILE.RAW byte binary file at both the remote host and the TE2M.16

Configure the mobile station’s forward MUX Option to the default MUX Option.17

Configure the base station’s Service Option to 25 and configure the base station’s MUX Option18to a value equal to or greater than the mobile station’s MUX Option number.19

Setup a mobile station originated call using Service Option 22, and establish an FTP session20with the remote host.21

Verify the call is negotiated to Service Option 25.22

Transfer the file from the remote host to TE2M using the binary “get” command.23

After the file transfer is completed in step f, transfer the file from the TE2M to the remote host24using the binary “put” command.25

End FTP session.26

Configure the base station’s Service Option to 22.27

Setup a mobile station originated call using Service Option 25 and establish an FTP session28with the remote host.29

Verify the call is negotiated to Service Option 22.30


After the file transfer is completed in step l, transfer the file from the TE2M to the remote host32using the binary “put” command.33

End FTP session.34

TSG-C42 Page 12-6

10/19/2001 C.S0031


• The call shall be successfully established in each of the following cases:2

• Mobile station originates with Service Option 22, base station proposes Service3Option 25; the call is established using Service Option 25. The file shall be4successfully transferred without error.5

• Mobile station originates with Service Option 25, base station propose Service6Option 22; the call is established using Service Option 22. The file shall be7successfully transferred without error.8

12.5 MSPD Call Setup, Negotiation to LSPD9

12.5.1 Definition10This test verifies that the base station and the mobile station can successfully negotiate from11MSPD to LSPD service options.12

Traceability:13

[see 15]-A9; 2.2.2.1.2.51415


12.5.2.1 MSPD-Capable Mobile station17

l. Prepare the COMPFILE.RAW byte binary file at both the remote host and the TE2M.18

For Test 1, configure the mobile station to originate a call with Service Option 22. This may be19done by issuing the AT command AT+CMUX=3,1.20

Configure the base station to Service Option 7.21

Setup a mobile station originated call with Service Option 22, and establish an FTP session22with the remote host.23

Verify from the Origination Message the appropriate Service Option number that is requested24by the mobile station.25

Record the Service Option used to set up the FTP session.26


After the file transfer is completed in step g, transfer the file from the TE2M to the remote host28using the binary “put” command.29

End FTP session.30

For Test 2, configure the base station’s Service Option to 15 and the mobile station’s Service31Option to 22 and repeat steps d through i.32

For Test 3, configure the base station’s Service Option to 15 and the mobile station’s Service33Option to 25 (i.e. set AT+CMUX=4,2) and repeat steps d through i.34

TSG-C42 Page 12-7

10/19/2001 C.S0031

For Test 4, configure the base station’s Service Option to 7 and the mobile station’s Service1Option to 25 (i.e. set AT+CMUX=4,2) and repeat steps d through i.2

12.5.2.2 Non MSPD-Capable Mobile station3

m. Ensure the mobile station is not MDR capable.4

Prepare the COMPFILE.RAW byte binary file at both the remote host and the TE2M.5

For Test 5, configure the mobile station with Service Option 15. This can be accomplished by6issuing the AT command AT+CMUX=2,2.7

Configure the base station to page the mobile station with Service Option 22.8

Set up a mobile station terminated call and establish an FTP session.9

Verify from the General Page Message the Service Option number that is requested by the base10station.11

Record the Service Option number used to set up the FTP session.12


After the file transfer is completed in step h, transfer the file from the TE2M to the remote host14using the binary “put” command.15

End FTP session.16

For Test 6, configure base station Service Option to 25 and repeat steps e through j.17

12.5.3 Minimum Standard18In all tests conducted, the files shall be successfully transferred. Received files shall be complete19and identical in content to the original file.20The call shall be successfully established in each of the following case scenarios:21

• For Test 1, the mobile station originates with Service Option 22, base station22proposes Service Option 7; the call is established using Service Option 7.23




• For Test 5, the base station pages mobile station with Service Option 22, mobile30station proposes Service Option 15; the call is established using Service Option 15.31

• For Test 6, the base station pages mobile station with Service Option 25, mobile32station proposes Service Option 15; the call is established with Service Option 15.33

TSG-C42 Page 12-8

10/19/2001 C.S0031

12.6 MSPD Call Setup, Mobile Station Maximum Multiplex Option Less than Base Station1Maximum Multiplex Option2

12.6.1 Definition3This test verifies that an MSPD call can be successfully established when the maximum4multiplex option supported by the mobile station is less than the maximum multiplex option5supported by the base station.6

Traceability:7

[see 15]-A9; 2.2.2.1.2.58


n. Prepare the COMPFILE.RAW byte binary file at both the remote host and the TE2M.10

Configure the mobile station’s maximum forward MUX Option to (2n+1) where n is equal to N11or 6, whichever is smaller, where N is the maximum number of Supplemental Code Channels12supported by the mobile station (i.e. set AT+CMUX=2n+1,1)13

Configure the base station’s MUX Option to a value equal to (2(n+1)+1).14

Setup a mobile station terminated call with Service Option 22, and establish an FTP session.15

Verify the number of Supplemental Code Channels used to establish FTP session is n.16



End FTP session.20

Repeat steps d through h with Service Option 25 by setting the maximum forward MUX Option21of the mobile station to (2n+2) and the MUX Option of the base station to (2(n+1)+2).22

12.6.3 Minimum Standard23The mobile station and the base station shall successfully negotiate to the maximum multiplex24option set at the mobile station. In all tests conducted, the files shall be successfully transferred.25Received files shall be complete and identical in content to the original file.26

12.7 MSPD Call Setup, Mobile station Maximum Multiplex Option Greater than Base27Station Maximum Multiplex Option28

12.7.1 Definition29This test verifies that an MSPD call can be successfully established when the maximum30multiplex option supported by the mobile station is greater than the maximum multiplex option31supported by the base station.32

TSG-C42 Page 12-9

10/19/2001 C.S0031

Traceability:1

[see 15]-A9; 2.2.2.1.2.52


o. Prepare the COMPFILE.RAW byte binary file at both the remote host and the TE2M.4

Configure the mobile station’s maximum forward MUX Option to (2N+1) where N is the5maximum number of Supplemental Code Channels supported by the mobile station (i.e. set6AT+CMUX=2N+1,1)7

Configure the base station’s MUX Option to a value equal to (2(N-1)+1).8


Verify the number of Supplemental Code Channels used in establishing the FTP session is (N-101).11



End FTP session.15

Repeat steps d through h with Service Option 25 by setting the maximum forward MUX Option16of the mobile station to (2N+2) and MUX Option of the base station to (2(N-1)+2).17

12.7.3 Minimum Standard18The mobile station and the base station shall successfully negotiate to the maximum multiplex19option set at the base station. In all tests conducted, the files shall be successfully transferred.20Received files shall be complete and identical in content to the original file.21

12.8 Allocation/De-allocation of Supplemental Code Channels22

12.8.1 Definition23This test verifies allocation and de-allocation of up to N Supplemental Code Channels using the24General Handoff Direction Message (GHDM), and Supplemental Code Channel Assignment25Message (SCAM). N is the maximum number of forward Supplemental Code Channels that can26be supported by the system. The first test uses n Supplemental Code Channels, where n is any27number greater than zero and less than the maximum N. The second test uses the maximum N28Supplemental Code Channels. This test also exercises all supported values of the29FOR_SUP_CONFIG and USE_FOR_DURATION fields.30

TSG-C42 Page 12-10

10/19/2001 C.S0031

Traceability:1

[see 4] 3.7.3.3.2, 3.6.6.2.2.9, 3.6.6.2.2.10;2

[see 15]-A9; 2.2.2.1.13


12.8.2.1 Allocation and De-Allocation of n Supplemental Code Channels using GHDM5

p. Prepare the RAND200.BIN byte binary file at the remote host.6



Verify only the forward Fundamental Code Channel is used in establishing the FTP session.11

Configure the base station to send a General Handoff Direction Message with12FOR_INCLUDED=1, FOR_SUP_CONFIG=3, USE_FOR_DURATION=0 and assign n forward13Supplemental Code Channels (where n < N and n > 0) to the mobile station.14

Verify that n Supplemental Code Channels are being used by the mobile station.15


Record time elapsed for the file transfer.17

Configure the base station to send a General Handoff Direction Message with18FOR_INCLUDED=1, FOR_SUP_CONFIG=3, USE_FOR_DURATION=0 and assign 0 forward19Supplemental Code Channels to the mobile station.20

Verify the number of Supplemental Code Channels used by the mobile station.21



End FTP session.24

Repeat steps c through m using Service Option 25.25

12.8.2.2 Allocation and De-Allocation of N Supplemental Code Channels using SCAM26

q. Prepare the RAND200.BIN byte binary file at the remote host.27



Verify that only the forward Fundamental Code Channel is used in establishing the FTP32session.33

TSG-C42 Page 12-11

10/19/2001 C.S0031

Configure the base station to send a Supplemental Code Channel Assignment Message with1FOR_INCLUDED=1, FOR_SUP_CONFIG=3, USE_FOR_DURATION=0, USE_FOR_HDM_SEQ=02and assign N forward Supplemental Code Channels to the mobile station.3

Verify that N Supplemental Code Channels are used by the mobile station.4



Configure the base station to send a Supplemental Code Channel Assignment Message with7FOR_INCLUDED=1, FOR_SUP_CONFIG=3, USE_FOR_DURATION=0, USE_FOR_HDM_SEQ=08and assign 0 forward Supplemental Code Channels to the mobile station.9

Verify the number of Supplemental Code Channels used by the mobile station.10



End FTP session.13

Repeat steps c through m using Service Option 25.14


12.8.3.1 Allocation and De-Allocation of n Supplemental Code Channels using GHDM16In 12.3.3.1.2.1, the Supplemental Code Channels shall be successfully allocated (step e) and de-17allocated (step i). The time elapsed for file transfer in step h should be (120/(n+1))% of the18elapsed time in step l.19

12.8.3.2 Allocation and De-Allocation of N Supplemental Code Channels using SCAM20In 12.3.3.1.2.2, the Supplemental Code Channels shall be successfully allocated (step e) and de-21allocated (step i). The time elapsed for file transfer in step h should be (120/(N+1))% of the22elapsed time in step l.23

12.9 No Transmission on Supplemental Code Channels24

12.9.1 Definition25This test verifies that data transfer is not interrupted if the base station stops transmitting on one26or more allocated Supplemental Code Channels. Note that if the base station does not allow a27Supplemental Code Channel to remain idle when there is no data to be transmitted on the28Supplemental Code Channel, this test may require the use of an OA&M interface on the base29station or some other method specific to the base-station manufacturer.30

Traceability:31

[see 4] 3.7.3.3.2, 3.6.6.2.2.9, 3.6.6.2.2.10;32

[see 15]-A9; 2.2.2.1.133


r. Prepare the RAND200.BIN byte binary file at the remote host.35

TSG-C42 Page 12-12

10/19/2001 C.S0031

Configure the mobile station’s maximum forward MUX Option to 5 or greater.1


Configure the base station to send a General Handoff Direction Message or a Supplemental Code3Channel Assignment Message with FOR_INCLUDED=1, FOR_SUP_CONFIG=3,4USE_FOR_DURATION=0, USE_FOR_HDM_SEQ=0 and assign 2 forward Supplemental Code5Channels to the mobile station.6

Verify the MUX Option used in establishing the FTP session.7


Record time elapsed during file transfer.9

Configure the base station to send data on the Fundamental Code Channel only while the 210Supplemental Code Channels are still active.11



End FTP session.14

Repeat steps c through k with Service Option 25.1516

12.9.3 Minimum Standard17Data transfer shall proceed normally after the base station stops transmitting on one or more18allocated Supplemental Code Channels. In all tests conducted, the files shall be successfully19transferred. Received files shall be complete and identical in content to the original file. The time20elapsed recorded in step g should be less than 40% the time elapsed recorded in step j.21

12.10 Soft Handoff with Supplemental Code Channels22

12.10.1 Definition23This test verifies that the fundamental and Supplemental Code Channels can be put in two-way24soft handoff during an MSPD call with N Supplemental Code Channels active, where N is the25maximum number of Forward Supplemental Code Channels that can be supported by the system.26This test includes the following cases:27

• Fundamental Code Channel and Supplemental Code Channels in handoff, two cells28transmit Supplemental Code Channels.29

• Fundamental Code Channel in handoff, only one cell transmits Supplemental Code30Channels.31

Traceability:32

[see 4] 3.7.3.3.2.3, 3.6.6.2.2.10, 3.6.6.2.4;33

[see 15]-A9; 2.2.2.1.134


s. Prepare the RAND200.BIN byte binary file at the remote host.36

TSG-C42 Page 12-13

10/19/2001 C.S0031

Configure the mobile station’s maximum forward MUX Option to (2N+1) where N is the1maximum number of forward Supplemental Code Channels available for the mobile station.2

Configure each base station to support N Supplemental Code Channels.3

Setup a mobile station terminated call with Service Option 22, and establish an FTP session4with base station #1.5

Configure the base station to set up N Forward Supplemental Code Channels in traffic state.6

Begin transferring the file from the remote host to TE2M using the binary “get” command.7

While the file is being transferred, adjust the signal strength of base station #2 until both base8stations have equal transmit power.9

Generate a General Handoff Direction Message for two-way soft-handoff with base station #2. In10both test cases 1 and 2, generate the GHDM with FOR_INCLUDED=1, FOR_SUP_CONFIG=3,11NUM_FOR_SUP=N, and USE_FOR_DURATION=0.12

For Test 1: In the GHDM, set the FOR_SUP_INCLUDED=1 for each pilot to be included in13handoff and configure both base stations to send data on all Supplemental Code Channels.14

For Test 2: In the GHDM, set the FOR_SUP_INCLUDED=1 for base station #1 and15FOR_SUP_INCLUDED=0 for base station #2. Configure base station #1 to transmit data on all16Supplemental Code Channels. Configure base station #2 to transmit data on the Fundamental17Code Channel only.18

Verify the file transfer continues after the handoff.19


End FTP session.21

Repeat steps d through m with Service Option 25.22

12.10.3 Minimum Standard23In each test, the mobile station shall successfully perform the handoff, and data transfer shall24continue after the handoff. Under ideal channel conditions, the measured throughput in each case25should be close to the measured throughput with no handoff.26

12.11 Adding Supplemental Code Channels during Soft Handoff27

12.11.1 Definition28This test verifies that N Supplemental Code Channels can be added in an MSPD call while in29two-way soft handoff on the Fundamental Code Channel, where N is the maximum number of30Supplemental Code Channels that can be supported by the system. This test includes the31following cases:32

• N Supplemental Code Channels added on all cells.33

• N Supplemental Code Channels added on one cell only.34

TSG-C42 Page 12-14

10/19/2001 C.S0031

Traceability:1

[see 4] 3.7.3.3.2.3, 3.6.6.2.2.10, 3.6.6.2.4;2

[see 15]-A9; 2.2.2.1.13


t. Prepare the RAND200.BIN byte binary file at the remote host.5

Configure the mobile station’s maximum forward Supplemental Code Channels to N.6

Configure each base station to support N Supplemental Code Channels.7

Setup a mobile station terminated call with Service Option 22, and establish an FTP session8with base station #1 on the Fundamental Code Channel only.9

Adjust the signal strength of base station #2 until both base stations have equal transmit10power.11

Verify the mobile station is in two-way handoff.12


Generate a General Handoff Direction Message or a Supplemental Channel Assignment Message14with FOR_INCLUDED=1, FOR_SUP_CONFIG=3, NUM_FOR_SUP=N, and15USE_FOR_DURATION=0.16

For Case 1: In the GHDM, set the FOR_SUP_INCLUDED=1 for each pilot to be included in17handoff and configure both base stations to send data on all Supplemental Code Channels.18

For Case 2: In the GHDM, set the FOR_SUP_INCLUDED=1 for base station #1 and19FOR_SUP_INCLUDED=0 for base station #2. Configure base station #1 to transmit data on all20Supplemental Code Channels. Configure base station #2 to transmit data on the Fundamental21Code Channel only.22

Verify the file transfer continues after Supplemental Code Channel assignment during handoff.23


End FTP session.25

Repeat steps d through m with Service Option 25.26

12.11.3 Minimum Standard27In each case, the mobile station shall successfully perform the handoff, and data transfer shall28continue after the handoff. Under ideal channel conditions, the measured throughput in each case29should be close to the measured throughput with no handoff.30

12.12 Hard Handoff to an MSPD-Capable System31Note that an MSPD call should be dropped during a hard handoff from a higher P_REV system32to a lower P_REV system. Tests that simply drop calls are not to be performed, therefore there is33no test for this situation.34

12.12.1 Definition35This test verifies hard handoff to an MSPD-capable system during an MSPD call.36

TSG-C42 Page 12-15

10/19/2001 C.S0031

Traceability:1

[see 4] 3.7.3.3.2.3, 3.6.6.2.2.10, 3.6.6.2.4;2

[see 15]-A9; 2.2.2.1.13


12.12.2.1 Hard Handoff to Same P_REV5

u. Prepare the RAND200.BIN byte binary file at the remote host.6

Make sure the MOB_P_REV=4 or higher.7

Base station #1 should be configured for P_REV=5 or higher.8

Base station #2 should be configured for P_REV=5 or higher with a different frequency channel9from base station #1.10


Configure both base stations to support N Supplemental Code Channels.12

Setup a mobile station terminated call with Service Option 22 and establish an FTP session13with base station #1 with N Supplemental Code Channels.14



At base station #1, setup a hard handoff to base station #2 using the Extended Handoff18Direction Message.19

Verify at the base station that the hard handoff is successful.20

Verify base station #2 generates a General Handoff Direction Message or a Supplemental21Channel Assignment Message to assign N Supplemental Code Channels to the mobile station.22

Verify at the base station that service negotiation is successful and that the mobile station is23using Service Option 22 with N Supplemental Code Channels.24

Verify the file transfer continues after the hard handoff.25

End FTP session.26

Repeat steps g through o with Service Option 25.27

12.12.2.2 Hard Handoff to Higher P_REV28

v. Prepare the RAND200.BIN byte binary file at the remote host.29

Make sure the MOB_P_REV=4 or higher.30

Base station #1 should be configured for P_REV=3.31

Base station #2 should be configured for P_REV=5 or higher with a different frequency channel32from base station #1.33

TSG-C42 Page 12-16

10/19/2001 C.S0031


Configure base station #2 to support N Supplemental Code Channels.2

Setup a mobile station terminated call with Service Option 7 and establish an FTP session with3base station #1 (on the Fundamental Code Channel only).4



At base station #1, setup a hard handoff to base station #2 using the Extended Handoff8Direction Message.9

Verify at the base station that the hard handoff is successful.10

Verify at the mobile station that Service Option 7 is still in use.11

Verify the file transfer continues after the hard handoff.12

End FTP session.13

Repeat steps g through n with Service Option 15.14


12.12.3.1 Hard Handoff to the same P_REV16The mobile station shall successfully perform the handoff, and data transfer shall continue on17both the fundamental and Supplemental Code Channel after the handoff. The file shall be18successfully transferred without error. Note that the Supplemental Code Channels are dropped19just before the hard handoff and re-assigned after the hard handoff.20

12.12.3.2 Hard Handoff to Higher P_REV21The mobile station shall successfully perform the handoff, and data transfer shall continue after22the hard handoff. The file shall be successfully transferred without error.23

12.13 RLP Operation in Rayleigh Fading Environment24

12.13.1.1 Definition25This test verifies data transfer under 3 Ray Rayleigh channel conditions at 100km/hr, with26Supplemental Code Channels. This test verifies that RLP recovers erased data frames, and is27intended to exercise RLP negative acknowledgements (NAKs), retransmissions, and aborts in the28forward direction.29

Traceability:30

[see 4] 3.7.3.3.2, 3.6.6.2.2.9, 3.6.6.2.2.10;31

[see 15]-A9; 2.2.2.1.1;32


w. Set up the base station and the mobile station as shown in figure 12.13.2-1.34

TSG-C42 Page 12-17

10/19/2001 C.S0031

1

Figure 12.13.2-1 Functional setup for testing packet data testing in fading2

Prepare the RAND200.BIN byte binary file at the remote host.3

Set the channel simulator using the parameters as specified in Table 12.13.2-1.4


Configure the base station to assign one Supplemental Code Channel to the mobile station6using the General Handoff Direction Message or the Supplemental Channel Assignment7Message.8



End FTP session.11

Repeat steps d through h with Service Option 25.12

Table 12.13.2-1 MSPD Test Parameters - 100 km/hr13


TSG-C42 Page 12-18

10/19/2001 C.S0031


Number of Paths # 3


dB 0


dB -3



Delay from Path 3 to Input µs 14.5

12.13.3 Minimum Standard1Data transfer shall be successful, and the data transfer throughput shall be no less than 70% of2the throughput measured in section 10.3.1.1 Test 2.3

12.14 RLP Operation with Severely Degraded Channel4

12.14.1 Definition5This test verifies data transfer under severely degraded channel conditions, with Supplemental6Code Channels. This test is intended to exercise RLP resets due to long erasure bursts and TCP7retransmissions.8

Traceability:9

[see 4] 3.7.3.3.2, 3.6.6.2.2.9, 3.6.6.2.2.10;10[see 15]-A9; 2.2.2.1.1;11


x. Set up the base station and the mobile station as shown in figure 12.13.2-1.13

Prepare the RAND200.BIN byte binary file at the remote host.14

Set the channel simulator to one Ray 3 km/hr Rayleigh fading on the forward link.15


Configure the base station to assign one Supplemental Code Channel to the mobile station17using the General Handoff Direction Message or the Supplemental Channel Assignment18Message.19



End FTP session.22

Repeat steps d through h with Service Option 25.23

12.14.3 Minimum Standard24Data transfer shall be successful and the data transfer throughput shall be no less than 70% of the25throughput measured in section 10.3.1.1 Test 2.26

TSG-C42 Page 12-19

10/19/2001 C.S0031

12.15 Bi-Directional File Transfers with Forward Supplemental Code Channels1

12.15.1 Definition2This test verifies the capability to transfer files simultaneously on the Forward and Reverse3Traffic Channels between the mobile station and remote host using FTP, with forward4Supplemental Code Channels active.5

Traceability:6

[see 4] 3.7.3.3.2, 3.6.6.2.2.9, 3.6.6.2.2.10;7

[see 15]-A9; 2.2.2.1.1;8


y. Prepare the COMPFILE.RAW byte binary file at both the remote host and the TE2M.10


Configure the base station to support N Supplemental Code Channels.12

Setup a mobile station terminated call with Service Option 22.13

Establish two FTP sessions with the base station; one for the forward link and one for the14reverse link.15

From the base station, generate a General Handoff Direction Message or a Supplemental16Channel Assignment Message to allocate N Supplemental Code Channels to the mobile station.17

Verify from the mobile station that N forward Supplemental Code Channels are being used. The18reverse link should be connected with the Fundamental Code Channel only.19


While the file is being transferred on the forward link, begin transferring another file from TE2M21to the remote host on the reverse link using the binary “put” command.22

End two FTP sessions.23

Repeat steps d through i with Service Option 25.24

12.15.3 Minimum Standard25The simultaneous file transfers shall be completed successfully in each direction without error.26

12.16 Rм Interface Flow Control27

12.16.1 Definition28This test verifies flow control on the Rm Interface, when the Um interface data rate exceeds the29Rm interface baud rate.30

TSG-C42 Page 12-20

10/19/2001 C.S0031

Traceability:1

[see 4] 3.7.3.3.2, 3.6.6.2.2.9, 3.6.6.2.2.10;2

[see 15]-A9; 2.2.2.1.1;3


z. Prepare the COMPFILE.RAW byte binary file at the remote host.5



Configure the RS-232 baud rate in the Rm interface to 4800 bps.8



Verify at the mobile station that N Supplemental Code Channels are in use.12



End FTP session.15

Repeat steps e through j with Service Option 25.16

12.16.3 Minimum Standard17The file shall be transferred successfully from the remote host to the TE2M without error.18

12.17 Dormant Timer19

12.17.1 Definition20This test verifies the mobile station correctly processes the Service Option Control Message21which controls the Dormant Timer, and that the mobile station delays any attempt to send an22Origination Message requesting a MSPD service option until the Dormant Timer expires.23

Traceability:24

[see 4] 3.7.3.3.2.2.1;25

[see 15]-A9; 2.2.2.1.2.526


aa. Prepare the COMPFILE.RAW byte binary file at the remote host.28


Configure the mobile station’s inactivity timer to 20 seconds by issuing the AT command30AT+CTA=20.31



TSG-C42 Page 12-21

10/19/2001 C.S0031


From the base station, send the Service Option Control Message with the Packet Data Dormant3Timer set to 20 seconds.4

Verify from the mobile station that N Supplemental Code Channels is been used.5


Wait for the mobile station to enter the Control Hold mode due to data inactivity (i.e. when the7inactivity timer in the mobile station expires).8

Setup a mobile station originated call with Service Option 22, and establish an FTP session as9soon as the mobile station is in the Control Hold mode.10

After the call is re-established, transfer the file from the remote host to TE2M using the binary11“get” command.12

End FTP session.13

Repeat steps e through m with Service Option 25.14

12.17.3 Minimum Standard15The mobile station shall set the Dormant Timer value to 20 seconds as specified in the Service16Option Control Message, and shall not send an Origination Message requesting a MSPD service17option until the Dormant Timer expires. The file shall be transferred successfully from the18remote host to the TE2M without error.19

Note: The time elapsed between the Release Order and the Origination Message should be20approximately 20 seconds.21

12.18 Packet Zone ID22

12.18.1 Definition23This test verifies the following:24

1) When the mobile station detects a change in the Packet Zone ID in the Extended System25Parameters Message or the In-Traffic System Parameters Message and the new Packet Zone ID26is not in the Packet Zone ID List the mobile station shall attempt to reconnect the packet data27service option.282) When the mobile station detects a change in the Packet Zone ID in the Extended System29

Parameters Message or the In-Traffic System Parameters Message and the new Packet30Zone ID is already in the Packet Zone ID List, the mobile station shall not attempt to31reconnect the packet data service option.32

3) When the mobile station is in the Dormant Mode, if the Dormant Timer does not expire,33the mobile station shall not re-originate a data call.34

35

TSG-C42 Page 12-22

10/19/2001 C.S0031

Traceability:1

[see 4] 3.7.3.3.2.2.1;2

[see 15]-A9; 2.2.2.1.2.53


12.18.2.1 Mobile Station Idle State5

bb. Prepare the COMPFILE.RAW byte binary file at the remote host.6



Configure the mobile station’s inactivity timer to 20 seconds by issuing an AT command.9

Setup a mobile station originated call with Service Option 22, and establish an FTP session10


From Instruct the base station to, send the Service Option Control Message to the mobile13station to enable the PACKET_ZONE_ID with a valid list of PACKET_ZONE_Idsspecify the14number of packet data service identifiers that the mobile station is to retain in its packet data15zone identifiers list (the number shall be set to 2 or greater). Also set the Packet Data Dormant16Timer to 20 seconds.17

Verify from the mobile station that N Supplemental Code Channels are being used.18


Make sure there is no data to transmit for 20 seconds.20

Verify the mobile station enters Dormant/ Mobile Station Idle State due to data inactivity.21

Change the PACKET_ZONE_ID of the serving system in the Extended System Parameter22Message.23

Verify the mobile station reconnects to the same Service Option when it detects the new24PACKET_ZONE_ID.25

After the call is re-established, transfer the file from the remote host to TE2M using the binary26“get” command.27

End FTP session.28

Repeat steps j through l.29

Verify the mobile station does not perform a packet zone registration.30

Repeat steps e through o with Service Option 25.31

Repeat steps a through f.32

Instruct the base station to send the Service Option Control Message to the mobile station to set33the Dormant Timer to 60 seconds.34

TSG-C42 Page 12-23

10/19/2001 C.S0031

Repeat steps j through k.1

Attempt to initiate an ftp session to a server at the mobile station.2

Verify the MS does not send an Origination Message before the Dormant Timer expires.3

12.18.2.2 Traffic Channel State4

cc. Prepare the COMPFILE.RAW byte binary file at the remote host.5



Setup a mobile station originated call with Service Option 22, and establish an FTP session8


From the base station, send the Service Option Control Message to the mobile station to enable11the PACKET_ZONE_ID with a valid list of PACKET_ZONE_IDs.12

Verify from the mobile station that N Supplemental Code Channels are being used.13


While the file is being transferred, send the Service Option Control Message to the mobile15station with a change in the PACKET_ZONE_ID.16

Change the PACKET_ZONE_ID of the serving system in the In-Traffic System Parameter17Message.18

Verify the mobile station continues file transfer on the new PACKET_ZONE_ID.19

End FTP session.20

Repeat steps d through l with Service Option 25.21

12.18.3 Minimum Standard22The mobile station shall detect the change in the Packet Zone ID and shall reconnect the MSPD23service option. The file shall be transferred successfully from the remote host to the TE2M24without error.25

TSG-C42 Page 13-1

10/19/2001 C.S0031

13 HIGH SPEED PACKET DATA1Table 13-1 High speed packet data tests verifies operation using RCs 3, 4 and 5.2

Table 13-1 High Speed Packet Data Tests34

5Table 13-1 High Speed Packet Data Tests Continued6

7

Test No. Title

13.1 Forward File Transfer

13.2 Reverse File Transfer

13.3 Bi-directional File Transfer

13.4 Basic Supplemental Channel Configuration Setting and Single Assignment

13.5 Supplemental Channel Multiple Assignments

13.6 Turbo Coding on Supplemental Channel

13.7 Correct Walsh Cover

13.8 Supplemental Channel Discontinuous Transmission

13.9 Slotted Timer

13.10 Retry Order and Delay for Origination Message

13.11 Retry Order and Delay for Supplemental Channel Request Messages

13.12 Retry Order and Delay for Resource Request Messages

13.13 Base Station Initiated Active to Control Hold Mode Transitions

13.14 Mobile Station Initiated Active to Control Hold Mode Transitions

13.15 Base Station Initiated Control Hold to Active Mode Transitions

13.16 Mobile Station Initiated Control Hold to Active Mode Transitions

13.17 Base Station Ignores Mobile Station Requested Mode Transitions

13.18 Mobile station Multiplex Option different from Base Station Multiplex Option

13.19 Soft Handoff of Fundamental Channel and Supplemental Channels

13.20 Soft Handoff of Fundamental Channel only

13.21 Adding Supplemental Channels during Soft Handoff

13.22 Hard Handoff to HSPD-capable system

13.23 Hard Handoff from MSPD to HSPD

13.24 Hard Handoff from LSPD to HSPD

13.25 Hard Handoff to a different RC

13.26 Mobile Station Aborts R-SCH During Soft Handoff


TSG-C42 Page 13-2

10/19/2001 C.S0031

1

Note: For mobile station terminated calls, the mobile station must be in dormancy mode (with2assigned IP address) in order for terminated call procedures to work.3

13.1 Forward File Transfer4

13.1.1 Definition5This test verifies that during the HSPD call, the measured throughput rate on the Forward6Fundamental Channel and the Supplemental Channels matches the target throughput rate for the7minimum and maximum supported Forward Supplemental Channel data rates. Other data rates8may also be tested.9

Traceability:10

[see 4] 2.7.2.3.2.18, 2.7.2.3.2.28, 3.6.6.2.2.12, 3.7.3.3.2.24, 3.7.5.7.1.;11

[see 15]-1.11; 2.2.3 and 2.2.7.;12

[see 15]-1.12; 1.4.2.2, 2.2.2 and 2.2.713



Base Station Load

Attenuator 2

Mobile Station

Attenuator 1

SpectrumAnalyzer

Code DomainAnalyzer

Tx

Rx I

Rx Q

Antenna

16

Figure 13.1.2-1 Functional Setup for HSPD Throughput Tests17

13.28 RLP Operation in Severely Degraded Channel

13.29 Mobile Station Originated Short Data Burst

13.30 Mobile Station Terminated Short Data Burst

13.31 Mobile Assisted Burst Operation Parameters Message Test

13.32 Mobile Station and Base Station Operating in Different States

TSG-C42 Page 13-3

10/19/2001 C.S0031

b. At the remote host prepare the appropriate file, corresponding to the rate that will be1tested (Note: this will guarantee sufficient transfer time). Refer to Table D-1 in Data2Services Annex D.3

c. Setup an FTP session using Service Option 33 with the remote host.4

d. Ensure there are no Forward Supplemental Channels allocated to the mobile station.5

e. Configure the base station to send a valid configuration to the mobile station specifying6the minimum data rate supported by both mobile station and base station which7corresponds to the configured RC (see Table 13.1.2-1).8

f. Verify the base station sends a Universal Handoff Direction Message, an Extended9Supplemental Channel Assignment Message, or a Forward Supplemental Channel10Assignment Mini Message.11

g. Transfer the file from the remote host to the TE2M using the binary “get” command.12

h. Ensure data transfer rate is not limited by network limitations. Record the elapsed time13on the forward link of the Fundamental Channel during the file transfer.14

i. After the file transfer is completed, end the FTP session.15

j. Steps b through i shall be repeated for the maximum data rates that are supported by16both mobile station and base station.17

k. Steps b through i may be repeated for other data rates and different radio18configurations supported by both mobile station and base station.19

20

Table 13.1.2-1 SCH Data Rate21

Data Rate Granted (bps)

F-RC3,4 / R-RC3 F-RC5 / R-RC4

9600 14400

19200 28800

38400 57600

76800 115200

153600 230400

22

13.1.3 Minimum Standard23Mobile Station shall successfully use the number of Forward Supplemental Channels and the24data rate assigned in the ESCAM/UHDM/FSCAMM to transfer a file from the Remote Host.25The file shall be transferred successfully and under ideal channel conditions, the file transfer26shall be completed within 1.6 x 8 x M / ((N x R) + F)) seconds.27where:28

1.6 represents the acceptable margin for overhead and channel errors29M = size of the file (in bytes)30N = number of allocated Supplemental Channels31

TSG-C42 Page 13-4

10/19/2001 C.S0031

R = RLP payload in bps for the Supplemental Channel(s). See Table 13.1.3-11F = RLP payload in bps for the Fundamental Channel (6400 bps in the worst case for2

RC3, 4 or 11150 bps in the worst case for RC5)3

Note: file transfer time requirement is based on the following assumptions:4• N Supplemental Channels are allocated for the entire duration of the file5

transfer.6• Supplemental Channel utilization is 100%.7• Worst case and best case refer to the PDUs being single sized or double8

sized and to the dimension of the RLP header.910

Table 13.1.3-1 RLP Payloads11

Supplemental Channel Data Rate (bps) F-RC3,4 / R-RC3 RLP Payload (bps)[worst_case-best_case]

9600 6400 - 8000

19200 12800 – 16800

38400 25600 – 32600

76800 51200 – 67200

153600 121600 – 134400

Supplemental Channel Data Rate (bps) F-RC5 / R-RC4 RLP Payload (bps)[worst_case-best_case]

14400 11150 - 12750

28800 22400 - 26400

5.600 44800 - 52800

115200 89600 - 105600

230400 198400 - 211200

13.2 Reverse File Transfer12

13.2.1 Definition13This test verifies that during the HSPD call, the measured throughput rate on the Reverse14Fundamental Channel and the Supplemental Channels matches the target throughput rate for the15minimum and maximum supported Forward Supplemental Channel data rates. Other data rates16may also be tested.17

TSG-C42 Page 13-5

10/19/2001 C.S0031

Traceability:1

[see 4] 2.7.2.3.2.18, 2.7.2.3.2.28, 3.6.6.2.2.12, 3.7.3.3.2.24, 3.7.5.7.1;2

[see 15]-1.11; 2.2.3 and 2.2.7.;3

[see 15]-1.12; 1.4.2.2, 2.2.2 and 2.2.74



b. At the TE2M prepare the appropriate file, corresponding to the rate that will be tested7(Note: this will guarantee sufficient transfer time). Refer to Table D-1 in Data Services8Annex D.9


d. Ensure there are no Reverse Supplemental Channels allocated to the mobile station.11

e. Configure the base station to send a valid configuration to the mobile station specifying12the minimum data rate supported by both mobile station and base station which13corresponds to the configured RC (see Table 13.1.2-1).14

15

f. Transfer the file from the TE2M to the remote host using the binary “put” command.16Ensure that the total amount of data to be transferred at the mobile station is more17than an implementation defined threshold, or otherwise cause the mobile station to18send a Supplemental Channel Request Message or a Supplemental Channel Request19Mini Message with DURATION field set to a non-zero value.20

g. Ensure data transfer rate is not limited by network limitations. Record the elapsed time21on the reverse link of the Fundamental Channel during the file transfer.22

h. After the file transfer is completed, end the FTP session23

i. Steps b through i shall be repeated for the maximum data rates supported by both24mobile station and base station.25

j. Steps b through i may be repeated for other data rates and radio configurations26supported by both mobile station and base station.27

13.2.3 Minimum Standard28Mobile station shall successfully use the Reverse Supplemental Channels and the data rate29assigned in the ESCAM/UHDM to transfer a file to the remote host.30The file shall be transferred successfully and under ideal channel conditions, the file transfer31shall be completed within 1.6 x 8 x M / ((N x R) + F)) seconds.32Where:33

1.6 represents the acceptable margin for overhead and channel errors34M = size of the file (in bytes)35N = number of allocated Supplemental Channels36R = RLP payload in bps for the Supplemental Channel(s). See Table 13.1.3-137

TSG-C42 Page 13-6

10/19/2001 C.S0031

F = RLP payload in bps for the Fundamental Channel (8000 bps for RC3or 12800 bps1for RC4)2

Note: file transfer time requirement is based on the following assumptions:3

• N Supplemental Channels are allocated for the entire duration of the file4transfer.5

• Supplemental Channel utilization is 100%.6• Worst case and best case refer to the PDUs being single sized or double7


13.3 Bi-directional File Transfer9

13.3.1 Definition10This test verifies that during the HSPD call, the measured bi-directional throughput rate on the11Fundamental Channel and the Supplemental Channels matches the target throughput rate using12various Supplemental Channel data rates.13

Traceability:14

[see 4] 2.7.2.3.2.18, 2.7.2.3.2.28, 3.6.6.2.2.12, 3.7.3.3.2.24, 3.7.5.7.1.;15

[see 15]-1.11; 2.2.3 and 2.2.7.;16

[see 15]-1.12; 1.4.2.2, 2.2.2 and 2.2.717



b. Prepare the appropriate file at both the remote host and TE2M corresponding to the20rate that will be tested (Note: this will guarantee sufficient transfer time). Refer to Table21D-1 in Data Services Annex D.22


d. Configure the base station to send a valid configuration to the mobile station specifying24the minimum data rate supported by both mobile station and base station which25corresponds to the configured RC (see Table 13.1.2-1).26

e. Transfer the file from the TE2M to the remote host. Ensure that the total amount of27data to be transferred at the mobile station is more than an implementation defined28threshold, or otherwise cause the mobile station to send a Supplemental Channel29Request Message or a Supplemental Channel Request Mini Message with DURATION30field set to a non-zero value.31

f. Transfer a file from the Remote Host to the TE2M while the transfer in the reverse32direction is still proceeding.33

g. Ensure data transfer rate is not limited by network limitations. Record the elapsed time34on the forward and reverse links during the file transfer.35

h. End the FTP session when files in both the directions are successfully transferred.36

TSG-C42 Page 13-7

10/19/2001 C.S0031

i. Steps b through i shall be repeated for the maximum data rates that are supported by1both mobile station and base station.2

j. Steps b through i may be repeated for different data rates and radio configurations that3are supported by both mobile station and base station.4

13.3.3 Minimum Standard5Mobile station shall successfully use the Forward and Reverse Supplemental Channels and the6data rates assigned in the ESCAM/UHDM to transfer a file from and to the remote host7simultaneously.8The file shall be transferred successfully and under ideal channel conditions, the file transfer9shall be completed within 1.6 x 8 x M / ((N x R) + F)) seconds.10where:11

1.6 represents the acceptable margin for overhead and channel errors12M = size of the file (in bytes)13N = number of allocated Supplemental Channels14R = RLP payload in bps for the Supplemental Channel(s). See Table 13.1.3-115F = RLP payload in bps for the Fundamental Channel (8000 bps for F-RC3,4 /R-RC3 or16

12800 bps for F-RC5 / R-RC4)17

Note: file transfer time requirement is based on the following assumptions:18• N Supplemental Channels are allocated for the entire duration of the file19

transfer.20• Supplemental Channel utilization is 100%.21• Worst case and best case refer to the PDUs being single sized or double22


13.4 Basic Supplemental Channel Configuration Setting and Single Assignment24

13.4.1 Definition25This test verifies the following:26

• The base station can send both the Reverse and Forward Supplemental Channel27configurations to the mobile station using the Extended Supplemental Channel28Assignment Message or Universal Handoff Direction Message.29

• The mobile station processes the reverse and forward Supplemental Channel30assignments correctly as specified in the Extended Supplemental Channel Assignment31Message or Universal Handoff Direction Message using explicit start time.32

TSG-C42 Page 13-8

10/19/2001 C.S0031

BS

TrafficChannels

MS

TrafficChannels

Supplemental Channel Request Message

Extended Supplemental Channel Assignment Message

Extended Supplemental Channel Assignment Message

1Figure 13.4.1-1 Reference Call Flow for2

Supplemental Channel Request and Assignment34

Traceability (see [4]):5

2.6.4.1.2 Service Configuration and Negotiation62.6.4.3.1 Waiting for Order Substate72.6.4.3.2 Waiting for Mobile Station Answer Substate82.6.4.4 Conversation Substate92.6.4.5 Release Substate102.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages112.6.6.2.5.1.1 Processing of the Forward Supplemental Burst Assignment122.6.6.2.5.1.2 Processing of the Reverse Supplemental Burst Assignment132.7.2.3.2.18 Supplemental Channel Request Message143.6.4.1.2 Service Configuration and Negotiation153.6.4.1.6 Processing Resource Request Messages163.6.4.3.2 Waiting for Answer Substate173.6.4.4 Conversation Substate183.6.4.5 Release Substate193.6.6.2.2.12 Processing of Extended Supplemental Channel Assignment Message203.7.3.3.2.37 Extended Supplemental Channel Assignment Message21


dd. Connect the mobile station to the base station as shown in Figure 13.1.2-1.23

Setup a mobile station originated data call using Service Option 33 with the following channel24configurations:25

• RC 3 for both Forward and Reverse Fundamental Channel26

• RC 3 for both Forward and Reverse Supplemental Channel27

• 20 ms frames for both Forward and Reverse Supplemental Channel28

Ensure the service option will not run out of data to send on the mobile station and the base29station during the test (e.g., by preparing packet data so that the data buffer is never empty).30

Cause the mobile station to send a Supplemental Channel Request Message.31

Upon reception of the Supplemental Channel Request Message from the mobile station, instruct32the base station to send an Extended Supplemental Channel Assignment Message or Universal33

TSG-C42 Page 13-9

10/19/2001 C.S0031

Handoff Direction Message with the fields set as follows: (if less than two Supplemental1Channels are supported by the system, then field values should be modified accordingly)2

For Extended Supplemental Channel Assignment Message:34

Fields Parameters Setting

REV_CFG_INCLUDED ‘1’

NUM_REV_CFG_RECS ‘00001’ (2 R-SCHconfigurations)

For the first Reverse Supplemental Channel configuration, thebase station shall set the following fields as follows:

REV_SCH_ID ‘0’

REV_SCH_RATE ‘0001’ (19200 bps)

5For the second Reverse Supplemental Channel configuration,the base station shall set the following fields as follows:

REV_SCH_ID ‘1’


NUM_REV_SCH ‘10’ (2 R-SCHassignments)

6

TSG-C42 Page 13-10

10/19/2001 C.S0031

For the first Reverse Supplemental Channel assignment, thebase station shall set the following fields as follows:

REV_SCH_ID ‘0’

REV_SCH_DURATION ‘1000’ (160 ms)

REV_SCH_START_TIME_INCL ‘1’ (use explicit starttime)


For the second Reverse Supplemental Channel assignment, thebase station shall set the following fields as follows:

REV_SCH_ID ‘1’




FOR_CFG_INCLUDED ‘1’

NUM_FOR_CFG_RECS ‘00001’ (2 F-SCHconfigurations)

For the first Forward Supplemental Channel configuration, thebase station shall set the following fields as follows:

FOR_SCH_ID ‘0’

SCCL_INDEX ‘0000’

FOR_SCH_RATE ‘0001’(19200 bps)

For the second Forward Supplemental Channel configuration,the base station shall set the following fields as follows:

FOR_SCH_ID ‘1’


FOR_SCH_RATE ‘0011’ (76800 bps)

1

For Universal Handoff Direction Message:2

NUM_FOR_ASSIGN ‘10’

FOR_SCH_ID ‘0’


FOR_SCH_RATE ‘0001’(19200 bps)

3

TSG-C42 Page 13-11

10/19/2001 C.S0031

For the second Forward Supplemental Channel configuration,the base station shall set the following fields as follows:

FOR_SCH_ID ‘1’



1NUM_REV_SCH ‘10’ (2 R-SCH

assignments)

For the first Reverse Supplemental Channel assignment, thebase station shall set the following fields as follows:

REV_SCH_ID ‘0’




For the second Reverse Supplemental Channel assignment, thebase station shall set the following fields as follows:

REV_SCH_ID ‘1’



REV_SCH_RATE ‘0001’ ( 19200 bps)

2Verify the mobile station is transmitting on R-SCH0 and R-SCH1 in accordance with the3explicit start time, rate, and duration specified by the Extended Supplemental Channel4Assignment Message or Universal Handoff Direction Message.5

Wait until all the transmissions are finished. Instruct the base station to send an Extended6Supplemental Channel Assignment Message or Universal Handoff Direction Message with the7forward Supplemental Channel assignments (same as those of the reverse Supplemental8Channel assignments) specified as follows:9

10NUM_FOR_SCH ‘10’ (2 F-SCH

assignments)For the first Forward Supplemental Channel assignment, the basestation shall set the following fields as follows:FOR_SCH_ID ‘0’FOR_SCH_DURATION ‘1000’ (160 ms)FOR_SCH_START_TIME_INCL ‘1 (use explicit start

time)SCCL_INDEX ‘0000’For the second Forward Supplemental Channel assignment, thebase station shall set the following fields as follows:

TSG-C42 Page 13-12

10/19/2001 C.S0031

FOR_SCH_ID ‘1’FOR_SCH_DURATION ‘0100’ (80 ms)FOR_SCH_START_TIME_INCL ‘1’ (use explicit start

time)SCCL_INDEX ‘0000’

1

Verify the base station is transmitting on F-SCH0 and F-SCH1 in accordance with the explicit2start time, rate, and duration specified by the Extended Supplemental Channel Assignment3Message or Universal Handoff Direction Message.4

13.4.3 Minimum Standard5The mobile station shall not transmit on the Reverse Supplemental Channels at any time other6than the period that is specified by the reverse Supplemental Channel assignment. When the7mobile station transmits on the Reverse Supplemental Channel, it shall transmit at the rate8specified by the Extended Supplemental Channel Assignment Message or Universal Handoff9Direction Message. The base station shall not transmit on the Forward Supplemental Channels at10any time other than the period that is specified by the forward Supplemental Channel11assignment. When the base station transmits on the Forward Supplemental Channel, it shall12transmit at the rate specified by the Extended Supplemental Channel Assignment Message or13Universal Handoff Direction Message.14

13.5 Supplemental Channel Multiple Assignments15

13.5.1 Definition16This test verifies correct mobile station operation when multiple Supplemental Channel17Assignments are received under the following conditions:18

• Overlapped burst period: when a new Supplemental Channel assignment is received19during a current Supplemental Channel assignment burst, the new Supplemental20Channel assignment will take effect at the start time of the new Supplemental Channel21assignment, at which time the current Supplemental Channel assignment burst will22terminate.23

• Disjoint burst period: when a new Supplemental Channel assignment is received during24a current Supplemental Channel assignment burst, but the new Supplemental Channel25assignment will take effect after the end of the current Supplemental Channel26assignment burst, then the current Supplemental Channel assignment burst is27unaffected.28

• Assignment overwrite: when two Supplemental Channel assignments are sent one after29another, and the second Supplemental Channel assignment is received before the start30time of the first Supplemental Channel assignment, then the second Supplemental31Channel assignment will override the first Supplemental Channel assignment.32

33

Traceability: (see [4]):34

2.6.4.1.2 Service Configuration and Negotiation352.6.4.3.1 Waiting for Order Substate36

TSG-C42 Page 13-13

10/19/2001 C.S0031

2.6.4.3.2 Waiting for Mobile Station Answer Substate12.6.4.4 Conversation Substate22.6.4.5 Release Substate32.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages42.6.6.2.5.1.1 Processing of the Forward Supplemental Burst Assignment52.6.6.2.5.1.2 Processing of the Reverse Supplemental Burst Assignment62.7.2.3.2.18 Supplemental Channel Request Message73.6.4.1.2 Service Configuration and Negotiation83.6.4.1.6 Processing Resource Request Messages93.6.4.3.2 Waiting for Answer Substate103.6.4.4 Conversation Substate113.6.4.5 Release Substate123.6.6.2.2.12 Processing of Extended Supplemental Channel Assignment Message133.7.3.3.2.37 Extended Supplemental Channel Assignment Message14


19.2 kbps for an infinite duration

76.8kbpsfor 80

ms

80 ms

Ass

ignm

ent1

rece

ived

System time t 0,where t 0/80 = 0

Ass

ignm

ent2

rece

ived

t0 + 400

19.2 kbps for 80 ms

Result

76.8kbpsfor 80

ms

~ ~~ ~

17Figure 13.5.2-1 Supplemental Channel Assignments for overlapped burst period18

19

TSG-C42 Page 13-14

10/19/2001 C.S0031

76.8kbpsfor 80

ms

80 msA

ssig

nmen

t1re

ceiv

ed

19.2 kbps for 320 ms

Ass

ignm

ent2

rece

ived

t0 + 400 ms

76.8kbpsfor 80

ms19.2 kbps for 320 ms

Result

t0 + 1200 ms

~ ~

~ ~ ~ ~

~ ~

Systemtime t 0,where t 0/80= 0

1Figure 13.5.2-2 Supplemental Channel Assignments for disjoint burst periods2

80 ms

Ass

ignm

ent1

rece

ived

19.2 kbps for an infinite duration

Ass

ignm

ent2

rece

ived

t0 + 800 ms

76.8kbpsfor 80

ms

Result

~ ~

76.8kbpsfor 80

ms

t0 + 1200 ms

~ ~

Systemtime t 0,where t 0/80= 0

3Figure 13.5.2-3 Supplemental Channel Assignments for assignment overwrite4

5

ee. Connect the mobile station to the base station as shown in Figure 10.4.1.1.2-1.6

ff. Setup a mobile station originated data call using Service Option 33 with the following7channel configurations:8

• RC 3 for both Forward and Reverse Fundamental Channel9

• RC 3 for both Forward and Reverse Supplemental Channel10

• 20 ms frames for both Forward and Reverse Supplemental Channel11

TSG-C42 Page 13-15

10/19/2001 C.S0031

Ensure the service option will not run out of data to send on the mobile station and the base1station during the test (e.g., by preparing packet data so that the data buffer is never empty).2

Cause the mobile station to send a Supplemental Channel Request Message.3

Upon reception of the Supplemental Channel Request Message, instruct the base station to4send an Extended Supplemental Channel Assignment Message with the fields set as follows:5

6Fields Parameters Setting

REV_CFG_INCLUDED ‘1’

NUM_REV_CFG_RECS ‘00000’ (1 R-SCHconfiguration)

For the Reverse Supplemental Channel configuration, the basestation shall set the following fields as follows:

REV_SCH_ID ‘0’


NUM_REV_SCH ‘01’ ( 1 R-SCHassignment)

7

TSG-C42 Page 13-16

10/19/2001 C.S0031

For the Reverse Supplemental Channel assignment, the basestation shall set the following fields as follows:

REV_SCH_ID ‘0’

REV_SCH_DURATION ‘1111’ (infiniteduration)


REV_SCH_START_TIME See description below


1

FOR_CFG_INCLUDED ‘1’

NUM_FOR_CFG_RECS ‘00000’ ( 1 F-SCHconfigurations)

For the Forward Supplemental Channel configuration, the basestation shall set the following fields as follows:

FOR_SCH_ID ‘0’



2

NUM_FOR_SCH ‘01’ (1 F-SCHassignment)

For the Forward Supplemental Channel assignment, the basestation shall set the following fields as follows:

FOR_SCH_ID ‘0’

FOR_SCH_DURATION ‘1111’ (infiniteduration)

FOR_SCH_START_TIME_INCL ‘1’ (use explicit starttime)

FOR_SCH_START_TIME See description below


3

Let t0 , in units of ms, be the system time of the next 80 ms boundary closest to the4time at which the Extended Supplemental Channel Assignment Message is being5constructed. The mobile station shall set the REV_SCH_START_TIME field and the6FOR_SCH_START_TIME field to ( t0 + 400 ms)/80 ms mod 32.7

Instruct the base station to send another Extended Supplemental Channel Assignment Message8immediately after t0 + 400 ms containing the following R-SCH0 and F-SCH0 assignments:9

10

TSG-C42 Page 13-17

10/19/2001 C.S0031

NUM_REV_SCH ‘01’ (1 R-SCHassignment)

For the R-SCH assignment, the base station shall set thefollowing 5 fields as follows:

REV_SCH_ID ‘0’





assignment)

For the F-SCH assignment, the base station shall set thefollowing fields as follows:

FOR_SCH_ID ‘0’

FOR_SCH_DURATION ‘0100’ (80 ms)

FOR_SCH_START_TIME_INCL ‘0’ ‘1’ (use explicitstart time)


2

Verify the mobile station is transmitting on R-SCH0 and the base station is transmitting on F-3SCH0 in accordance with the explicit start time, rate, and duration specified by the two4Supplemental Channel assignments as depicted in Figure 10.4.2.2.2-1.5

Repeat step a to step d6

Upon reception of the Supplemental Channel Request Message, instruct the base station to7send an Extended Supplemental Channel Assignment Message with the reverse and forward8Supplemental Channel assignments specified as follows:9

10NUM_REV_SCH ‘01’ (1 R-SCH

assignment)

For the R-SCH assignment, the base station shall set thefollowing 5 fields as follows:

REV_SCH_ID ‘0’





11

TSG-C42 Page 13-18

10/19/2001 C.S0031



FOR_SCH_ID ‘0’


FOR_SCH_START_TIME_INCL ‘1’



1

Let t0, in units of ms, be the system time of the next 80 ms boundary closest to the time2at which the Extended Supplemental Channel Assignment Message is being3constructed. The mobile station shall set the REV_SCH_START_TIME field and the4FOR_SCH_START_TIME field to (t0 + 400)/80 mod 32.5

Instruct the base station to send another Extended Supplemental Channel Assignment Message6immediately after t0 + 400 containing the following R-SCH0 and F-SCH0 assignments with the7REV_SCH_START_TIME field and the FOR_SCH_STAT_TIME field set to ( t0 + 1200)/80 mod832:9

10

TSG-C42 Page 13-19

10/19/2001 C.S0031


For the R-SCH assignment, the base station shall set thefollowing fields as follows:

REV_SCH_ID ‘0’



REV_SCH_START_TIME See description above


1



FOR_SCH_ID ‘0’



FOR_SCH_START_TIME See description above


2

Verify the mobile station is transmitting on R-SCH0 and the base station is transmitting on the3F-SCH0 in accordance with the explicit start time, rate, and duration specified by the two4Supplemental Channel assignments as depicted in Figure 10.4.2.2.2-2.5

Repeat step a to step d6

Upon reception of the Supplemental Channel Request Message, instruct the base station to7send an Extended Supplemental Channel Assignment Message with the reverse and forward8Supplemental Channel assignments specified as follows:9

10

TSG-C42 Page 13-20

10/19/2001 C.S0031



REV_SCH_ID ‘0’

REV_SCH_DURATION ‘1111’ (infiniteduration)





assignment)


FOR_SCH_ID ‘0’

FOR_SCH_DURATION ‘1111’ (infiniteduration)




Let t0, in units of ms, be the system time of the next 80 ms boundary closest to the time2at which the Extended Supplemental Channel Assignment Message is being3constructed. The mobile station shall set the REV_SCH_START_TIME field and the4FOR_SCH_START_TIME field to (t0 + 800)/80 mod 32.5

Instruct the base station to send another Extended Supplemental Channel Assignment Message6containing the following R-SCH0 and F-SCH0 assignment immediately after t0 + 400 ms with7the REV_SCH_START_TIME field and the FOR_SCH_STAT_TIME field set to (t0 + 1200)/808mod 32:9

10

TSG-C42 Page 13-21

10/19/2001 C.S0031



REV_SCH_ID ‘0’



REV_SCH_START_TIME See description above



assignment)


FOR_SCH_ID ‘0’



FOR_SCH_START_TIME See description above


2

Verify the mobile station is transmitting on R-SCH0 and the base station is transmitting on F-3SCH0 in accordance with the explicit start time, rate, and duration specified by the two4Supplemental Channel assignments as depicted in Figure 10.4.2.2.2-3.5


In each case verify that the mobile station is transmitting on R-SCH0 and the base station is7transmitting on F-SCH0 in accordance with the explicit start time(s), rate(s), and duration(s)8specified by the relevant two Supplemental Channel assignments as depicted in Figures 13.5.2-91, 13.5.2-2, 13.5.2-3 respectively. In each case verify that file transfer is successful.10

13.6 Turbo Coding on Supplemental Channel11

13.6.1 Definition12This test verifies that the mobile station and base station which are capable, can support Turbo13coding as well as Convolutional Coding on the Supplemental Channel. Note that Turbo coding is14only used if the number of channel bits per frame is greater than 360.15

TSG-C42 Page 13-22

10/19/2001 C.S0031

Traceability:1

[see 1] 2.1.3.1.4.2, 3.1.3.1.4.2;2

[see 4] 2.7.4.25, 2.7.4.27.3, 3.7.5.7.1;3

[see 15]-1.11; 2.2.3 and 2.2.7;4

[see 15]-1.12; 1.4.2.2, 2.2.2 and 2.2.75


gg. Connect the mobile station to the base station as shown in Figure 13.1.2-1.7

Prepare the COMPFILE.RAW 40kbyte binary file at the remote host.8

Setup a mobile Originated call with Service Option 33 and establish an FTP session.9

From the base station, generate a Status Request Message to request the Channel10Configuration Capability Information from the mobile station11

Verify the mobile station sends the Status Response Message with FOR_TURBO_SUPPORTED =12'1' in the Channel Configuration Capability Information for the SCH.13

From the base station generate a Universal Handoff Direction Message to assign the maximum14number of Supplemental Channels supported by the system and set CODING ='1' in the15Channel Configuration for the Supplemental Channel(s).16


End the FTP session.18

13.6.3 Minimum Standard19Turbo coding shall be used on the SCH as long as the number of bits per frame is greater than20360. The file shall be successfully transferred.21

13.7 Correct Walsh Cover22

13.7.1 Definition23This test verifies the ability of the mobile station and the base station to use the correct Walsh24Cover for two reverse Supplemental Channels as specified in the Universal Handoff Direction25Message or Extended Supplemental Channel Assignment Message. Note that the Walsh Cover26used is only selectable if 2 R-SCHs are used.27

Traceability:28

[see 4] 2.7.2.3.2.18, 2.7.2.3.2.28, 3.6.6.2.2.12, 3.7.3.3.2.24, 3.7.5.7.1.;29

[see 15]-1.11; 2.2.3 and 2.2.7.;30

[see 15]-1.12; 1.4.2.2, 2.2.2 and 2.2.7;31

13.7.2 Method of Measurement.32

hh.Connect the mobile station to the base station as shown in Figure 13.1.2-1.33

TSG-C42 Page 13-23

10/19/2001 C.S0031

At the TE2M prepare the appropriate file, corresponding to the rate that will be tested (Note:1this will guarantee sufficient transfer time). Refer to Table D-1 in Data Services Annex D.2

Setup an FTP session using Service Option 33 with the remote host.3

At the base station, generate a Universal Handoff Direction Message with SCH_INCL = ‘0’,4NUM_REV_ASSIGN = ‘01’, REV_SCH_ID = ’0’ or an Extended Supplemental Channel Assignment5Message with REV_CFG_INCLUDED = ‘0’, NUM_REV_SCH = ‘01’, REV_SCH_ID = ’0’.6

Transfer the file from the TE2M to the remote host using the binary “put” command.7

Verify the Walsh cover used for the Reverse Supplemental Channel is set to the default value as8specified in [4] and that the file is transferred successfully.9

g At the base station, generate a Universal Handoff Direction Message with SCH_INCL =10‘1’, NUM_REV_ASSIGN = ‘10’ or an Extended Supplemental Channel Assignment11Message with REV_CFG_INCLUDED = ‘1’, NUM_REV_CFG_RECS = ‘01’, NUM_REV_SCH12= ‘10’. Walsh Cover for the first Supplemental Channel will be specified by REV_SCH_ID13= ‘0’, REV_WALSH_ID = ‘0’, REV_SCH_RATE = ‘0010’ and for the second Supplemental14Channel REV_SCH_ID = ‘1’, REV_WALSH_ID = ‘0’, REV_SCH_RATE = ‘0010’.15

h Transfer the file from the TE2M to the remote host using the binary “put” command.16

i. Verify the Walsh cover used is +- for the first Reverse Supplemental Channel17(REV_SCH_ID = ‘0’) and ++-- for the second Reverse Supplemental Channel18(REV_SCH_ID =’1’) and that the file is transferred successfully.19

j. Repeat steps c, g and h with REV_SCH_ID = ‘0’, REV_WALSH_ID = ‘1’, REV_SCH_RATE20= ‘0010’ for the first Supplemental Channel and REV_SCH_ID = ‘1’, REV_WALSH_ID =21‘1’, REV_SCH_RATE = ‘0010’ for the second Supplemental Channel.22

k. Verify the Walsh cover used is ++-- for the first Reverse Supplemental Channel23(REV_SCH_ID = ‘0’), and ++----++ for the second Reverse Supplemental Channel24(REV_SCH_ID = ‘1’) and that the file is transferred successfully.25

l. End the FTP session.26

13.7.3 Minimum Standard27The mobile station shall successfully transfer the file using the Walsh cover as specified in the28Extended Supplemental Channel Assignment Message or the Universal Handoff Direction29Message.30

13.8 Supplemental Channel Discontinuous Transmission31

13.8.1 Definition32This test verifies the ability of the mobile station to stop transmission on a Reverse Supplemental33Channel and then resume it within the Reverse Transmission Assignment period under the34following settings of REV_SCH_DTX_DURATION:35

• REV_SCH_DTX_DURATION set to ‘0000’: resumption not allowed36

• REV_SCH_DTX_DURATION set to ‘1111’: resumption allowed at any time37

• REV_SCH_DTX_DURATION set to ‘1110’: resumption must be within 280ms38

TSG-C42 Page 13-24

10/19/2001 C.S0031

Traceability:1

[see 4] 2.6.6.2.5.1, 2.7.2.3.2.18, 2.7.2.3.2.28, 3.6.6.2.2.12, 3.7.3.3.2.24, 3.7.5.7.1;2

[see 15]-1.11; 2.2.3 and 2.2.7;3

[see 15]-1.12; 1.4.2.2, 2.2.2 and 2.2.7;4


ii. Connect the mobile station to the base station as shown in Figure 13.1.2-1.6

Both at the remote host and at the TE2M prepare the appropriate file, corresponding to the rate7that will be tested (Note: this will guarantee sufficient transfer time). Refer to Table D-1 in Data8Services Annex D.9

Setup a call using Service Option 33 with the remote host.10

Start an FTP session to transfer a file from the TE2M to the remote host. Ensure that the total11amount of data to be transferred at the mobile station is more than an implementation defined12threshold, so that mobile station sends a Supplemental Channel Request Message with13DURATION = ‘1101’ (5.12 seconds).14

At the base station, generate an Extended Supplemental Channel Assignment Message with15NUM_REV_SCH = ‘10’ to assign 2 Reverse Supplemental Channels and16REV_SCH_DTX_DURATION = ‘0000’. Duration (REV_SCH_DURATION) shall be set as requested17in the DURATION field of the same message.18

Verify that mobile station stops using the Reverse Supplemental Channel once it stops19transmitting on that particular Supplemental Channel during the assigned Transmission20duration.21

After the duration of the assignment of the Supplemental Channels is over, generate another22Extended Supplemental Channel Assignment Message with REV_SCH_DTX_DURATION =23‘1110’.24

Verify the mobile station can stop transmission on the Reverse Supplemental Channel for a25maximum period of 280 msec before resuming the transmission within the assigned26Transmission Duration.27

After the duration of the assignment of the Supplemental Channels is over, generate another28Extended Supplemental Channel Assignment Message with REV_SCH_DTX_DURATION =29‘1111’.30

Verify the mobile station can resume transmission on the Reverse Supplemental Channel any31time within the assigned Transmission Duration.32

After the file transfer is completed, end the FTP session.33


• REV_SCH_DTX_DURATION = ‘0000’ the mobile station shall not resume transmission on35a Supplemental Channel once it stops using the Supplemental Channel.36

TSG-C42 Page 13-25

10/19/2001 C.S0031

• REV_SCH_DTX_DURATION = ‘1111’ the mobile station shall resume transmission on a1Supplemental Channel at any time after it stops using the Supplemental Channel.2

• REV_SCH_DTX_DURATION = ‘1110’ the mobile station shall stop transmission for a3maximum period of 280ms after it stops using the Supplemental Channel.4

13.9 Slotted Timer5

13.9.1 Definition6This test will verify the following for a mobile station capable of supporting the slotted mode and7slotted timer:8

• Mobile station will operate in non-slotted mode if the slotted timer is running.9

• Mobile station will operate in the slotted mode when the slotted timer expires.10

• When the slotted timer is enabled, if the mobile station is instructed by the base station11to disable the slotted timer, the mobile station will disable the slotted timer and operate12in the slotted mode.13

14

Release Order

BS

DedicatedChannel

MS

DedicatedChannel

In-traffic System Param eters Message(T_SLOTTED)

The slotted timer isdisabled

Release Order

The MS enters Idle State

Registration Request Order

Registration M essage

Comm onChannels

Comm onChannels

Registration M essage

Registration Request Order

Slotted Mode Order

15Figure 13.9.1-1 Reference Call Flow for Slotted Timer Testing16

17

Traceability (see [4])18

2.6.2: MS procedures for setting the slotted mode (SLOTTEDs) and the slotted timer (TMS_Slotted).192.6.2.1.7: Slotted Timer Expiration.202.6.2.4: Procedures for processing Slotted Mode Order.212.6.4.1.4: Setting Slotted Timer upon receiving In-traffic System Parameters Message.222.6.4.2: Setting the default Slotted Timer (T_SLOTTEDs) to T74m and disable the slotted timer23during the Traffic Channel Initialization Substate.243.7.3.3.2.7: In-traffic System Parameters Message.253.7.4: Slotted Mode Order.26

TSG-C42 Page 13-26

10/19/2001 C.S0031


jj. Connect the mobile station to the base station as shown in Figure 13.1.2-1. Set the test2parameters as shown in Table 13.9.2-1.3

4Table 13.9.2-1 Slotted Timer Test Signal Channel Levels5

POTS Signal Channel Forward Channel Level(RC 3, 4)

Forward Channel Level(RC 5)

Îor -75 dBm/1.23 MHz -75 dBm/1.23 MHz

Pilot Ec/Ior -7 dB -7 dB

Traffic Ec/Ior -15.6 dB -12.3 dB

6

Setup a data call. Verify user data in both directions.7

Instruct the base station to send the In-traffic System Parameters Messages as follows:89

Fields Values

T_SLOTTED_INCL ‘1’ (includeslottedtimer)

T_SLOTTED ‘100’ (slottedtimer is setto 8s)

10

Terminate the call.11

Before the slotted timer expires, instruct the base station to send a Registration Request Order12at any slot other than the mobile station’s assigned slot on the Paging Channel.13

Verify the mobile station responds with a Registration Message.14

Allow the slotted timer to expire and then instruct the base station to send a Registration15Request Order at any slot other than the mobile station’s assigned slot on the Paging Channel.16

Verify the mobile station does not respond with a Registration Message.17

Repeat steps b to d.18

Before the slotted timer expires, instruct the base station to send a Slotted Mode Order at any19slot other than the mobile station’s assigned slot on the Paging Channel.20

Instruct the base station to send a Registration Request Order at any slot other than the mobile21station’s assigned slot on the Paging Channel.22

Verify the mobile station does not respond with a Registration Message.23

TSG-C42 Page 13-27

10/19/2001 C.S0031

13.9.3 Minimum Standard1The mobile station shall operate in the non-slotted mode if the slotted timer is enabled. When the2slotted timer is enabled, the mobile station shall disable the slotted timer upon receiving a Slotted3Mode Order from the base station.4

13.10 Retry Order and Delay for Origination Message5

13.10.1 Definition6This test verifies the mobile station shall not re-transmit an Origination Message with the same7packet data service option if the retry delay timer for the corresponding packet data service8option has not expired.9

10

Retry Order (RETRY_TYPE=001)

BS

CommonChannels

MS

CommonChannels

Initiate a PacketData Call Origination Message (Packet Data SO)

11Figure 13.10.1-1 Reference Call Flow for Retry Order and Delay Test12

(Origination Message)1314


2.6.2.2.1.8 Retry Delay Disable for Packet Zone ID or SID/NID Change162.6.2.4 Mobile Station Order and Message Processing Operation172.6.3.3 Page Response Substate182.6.3.4 Mobile Station Order/Message Response Substate192.6.3.5 Mobile Station Origination Attempt Substate202.6.3.6 Registration Access Substate212.6.3.7 Mobile Station Message Transmission Substate222.6.4.2 Traffic Channel Initialization Substate232.6.4.3.1 Waiting for Order Substate242.6.4.3.2 Waiting for Mobile Station Answer Substate252.6.4.4 Conversation Substate262.6.4.5 Release Substate272.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages283.6.4.4 Conversation Substate293.6.6.2.2.10 Processing the General Handoff Direction Message303.6.6.2.2.11 Processing the Universal Handoff Direction Message313.7.3.3.2.31 General Handoff Direction Message323.7.3.3.2.36 Universal Handoff Direction Message333.7.4 Orders343.7.4.7 Retry Order35


kk. Connect the mobile station to the base station as shown in Figure 13.1.2-1.37

TSG-C42 Page 13-28

10/19/2001 C.S0031

Cause the mobile station to initiate a packet data call by sending an Origination Message.1

Configure the base station to respond to the packet data origination with a Retry Order and set2the parameters in the Retry Order as follows:3

4Parameters Setting

RETRY_TYPE ‘001’ (specifies the RETRY_DELAY for aPacket Data Origination Message)

RETRY_DELAY ‘10000001’ (Set retry delay to 1 min) 4

5

Repeatedly attempt to cause the mobile station to send an Origination Message with the same6packet data service option before the retry delay timer expires and verify that the mobile station7does not send an Origination Message.8

After the expiration of the retry delay timer, cause the mobile station to send an Origination9Message with the same packet data service option and verify that the mobile station sends an10Origination Message with the same packet data service option.11

Instruct the base station to send a Release Order to release the call origination.12

Repeat steps b and c.13

Cause the mobile station to send an Origination Message with a different packet data service14option from that in step b before the retry delay timer expires and verify that the mobile station15sends an Origination Message with the different packet data service option.16


Repeat steps b and c.18

Prior to the expiration of the retry delay timer, configure the base station to send a Retry Order19with RETRY_TYPE equal to ‘000’.20

Prior to the expiration of the original retry delay timer set in step c, cause the mobile station to21send the same packet data service option origination. Verify that the mobile station sends an22Origination Message with the same packet data service option.23


13.10.2.1.1 13.10.3 Minimum Standard25The mobile station shall not retransmit the Origination Message with same packet data service26option, if the corresponding retry delay timer has not expired.27

4 Note: RETRY_DELAY is to be set to allow sufficient time to test mobile station conformanceto the retry delay timer.

TSG-C42 Page 13-29

10/19/2001 C.S0031

13.11 Retry Order and Delay for Supplemental Channel Request Messages1

13.11.1 Definition2This test verifies that the mobile station shall not re-send any subsequent Supplemental Channel3Request Message or Supplemental Channel Request Mini Message if the corresponding retry4delay timer has not expired.5

6

BSMS

Supplemental Channel Request (Mini) Message

DedicatedChannel

DedicatedChannel



(Supplemental Channel Request Messages)910


2.6.4.2 Traffic Channel Initialization Substate122.6.4.3.1 Waiting for Order Substate132.6.4.3.2 Waiting for Mobile Station Answer Substate142.6.4.4 Conversation Substate152.6.4.5 Release Substate162.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages173.6.4.4 Conversation Substate183.6.6.2.2.9 Processing the Supplemental Channel Assignment Message193.6.6.2.2.10 Processing the General Handoff Direction Message203.6.6.2.2.11 Processing the Universal Handoff Direction Message213.7.3.3.2.24 Supplemental Channel Assignment Message223.7.3.3.2.31 General Handoff Direction Message233.7.3.3.2.36 Universal Handoff Direction Message243.7.4 Orders253.7.4.7 Retry Order26


ll. Connect the mobile station to the base station as shown in Figure 13.1.2-1.28

Start an FTP session to transfer a file from the TE2M to the remote host. Ensure that the total29amount of data to be transferred at the mobile station is more than an implementation defined30threshold, or otherwise cause the mobile station to send a Supplemental Channel Request31Message or a Supplemental Channel Request Mini Message32

Configure the base station to respond to the Supplemental Channel request with a Retry Order33and set the parameters in the Retry Order as follows:34

35

TSG-C42 Page 13-30

10/19/2001 C.S0031

Parameters Setting

RETRY_TYPE ‘011’ (specifies the RETRY_DELAY for aSupplemental Channel Request Message orSupplemental Channel Request MiniMessage)

RETRY_DELAY ‘11111110’ (Set retry delay to 81.28s) 5

1

Cause the mobile station to send a Supplemental Channel Request Message (as in step b) prior2to the expiration of the retry delay timer. Verify that the mobile station does not send a3Supplemental Channel Request Message.4

Cause the mobile station to send a Supplemental Channel Request Mini Message prior to the5expiration of the retry delay timer. Verify that the mobile station does not send a Supplemental6Channel Request Mini Message.7

After the expiration of the retry delay timer cause the mobile station to send a Supplemental8Channel Request Message or Supplemental Channel Request Mini Message. Verify that the9mobile station sends a Supplemental Channel Request Message or Supplemental Channel Re-10quest Mini Message.11

Repeat the steps d through e.12

Prior to the expiration of the retry delay timer, configure the base station to send a Retry Order13with RETRY_TYPE equal to ‘000’.14

Instruct the mobile station to send another Supplemental Channel Request Message or15Supplemental Channel Request Mini Message (prior to the expiration of the original retry delay16timer set in step e). Verify that the mobile station sends a Supplemental Channel Request17Message or Supplemental Channel Request Mini Message.18

Instruct the base station to release the call.19

13.11.3 Minimum Standard20The mobile station shall not retransmit Supplemental Channel requests before the corresponding21retry delay timer expires.22

13.12 Retry Order and Delay for Resource Request Messages23

13.12.1 Definition24This test verifies that the mobile station shall not re-send any subsequent Resource Request25Message or Resource Request Mini Message if the corresponding retry delay timer has not been26expired.27

28


TSG-C42 Page 13-31

10/19/2001 C.S0031

BS

DedicatedChannel

MS

DedicatedChannel

Resource Request (Mini) Message


MS in Control HoldMode


(Resource Request Messages)34

Traceability: [see 4]52.6.4.2 Traffic Channel Initialization Substate62.6.4.3.1 Waiting for Order Substate72.6.4.3.2 Waiting for Mobile Station Answer Substate82.6.4.4 Conversation Substate92.6.4.5 Release Substate102.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages112.7.2.3.2.23 Resource Request Message123.6.4.4 Conversation Substate133.6.6.2.2.10 Processing the General Handoff Direction Message143.6.6.2.2.11 Processing the Universal Handoff Direction Message153.7.3.3.2.31 General Handoff Direction Message163.7.3.3.2.36 Universal Handoff Direction Message173.7.4 Orders183.7.4.7 Retry Order19



b. Instruct the mobile station to initiate a packet data call by sending an Origination22Message.23

c. Instruct the base station to accept the call and assign a Dedicated Control Channel.24

d. While on a traffic channel, instruct the base station to send an Extended Release25Message or an Extended Release Mini Message by setting the following parameters:26

27Parameters Settings

CH_IND ‘100’ (reverse pilot gating)

GATING_RATE_INCL ‘1’ (the pilot gating rate is included)

PILOT_GATING_RATE ‘01’ or ‘10’ (The gating rate is set to ½ or ¼)

28

TSG-C42 Page 13-32

10/19/2001 C.S0031

e. Issue a ping command to instruct the mobile station to send a Resource Request1Message or Resource Request Mini Message.2

f. Configure the base station to respond to the resource request with a Retry Order3and set the parameters in the Retry Order as follows:4

5Parameters Setting

RETRY_TYPE ‘010’ (specifies the RETRY_DELAY for aResource Request Message or ResourceRequest Mini Message)

RETRY_DELAY ‘11111110’ (Set retry delay to 81.28s) 6

6

g. Instruct the mobile station to send a Resource Request Message or a Resource7Request Mini Message prior to the expiration of the retry delay timer. Verify that the8mobile station does not send the Resource Request Message or the Resource Request9Mini Message10

h. After the expiration of the retry delay timer, instruct the mobile station to send11another Resource Request Message or Resource Request Mini Message. Verify that12the mobile station sends a Resource Request Message or Resource Request Mini13Message.14

i. Repeat the steps e through f.15

j. Prior to the expiration of the retry delay timer, configure the base station to send16another Retry Order with RETRY_TYPE equal to ‘000’ and instruct the mobile station17to send another Resource Request Message or Resource Request Mini Message.18Verify that the mobile station sends a Resource Request Message or Resource19Request Mini Message.20

k. Instruct the base station to release the call.21

13.12.3 Minimum Standard22During the Control Hold Mode, the mobile station shall not retransmit resource requests before23the corresponding retry delay timer expires.24

13.13 Base Station Initiated Active to Control Hold Mode Transitions25

13.13.1 Definition26This test verifies the base station can direct the mobile station to transition to the Control Hold27Mode. In the control Hold Mode:28

• Reverse Pilot Channel is transmitted in gated mode.29

• Dedicated Control Channel is maintained.30

• Power Control is maintained.31


TSG-C42 Page 13-33

10/19/2001 C.S0031

Extended Release (Mini) Message /Universal Handoff Direction Message

Extended Release Response (Mini) MessageHandoff Completion Message

At the action time:Transition to Control Hold Mode& start reverse pilot gating at thespecified gating rate

BSMS

Active Active

Control Hold Control Hold

BS decides to transitionto Control Hold Mode

1Figure 13.13.1-1 Reference Call Flow for base station initiated Active2

to Control Hold Transition3


2.6.4.1.15: Processing the Non-Negotiable Service Configuration Record52.6.4.1.9: Processing the Extended Release Message and the Extended Release Mini Message62.6.4.1.10: Processing the Resource Allocation Message and Resource Allocation Mini Message72.6.4.4: Conversation Substate82.6.6.2.5.1: Processing of Forward Traffic Channel Handoff Messages92.7.2.3.2.18: Supplemental Channel Request Message102.7.2.3.2.28: Supplemental Channel Request Mini Message112.7.2.3.2.23: Resource Request Message122.7.2.3.2.24: Resource Request Mini Message132.7.2.3.2.29: Resource Release Request Message142.7.2.3.2.30: Resource Release Request Mini Message153.6.4.1.6: Processing Resource Request Messages163.6.4.1.8: Processing Resource Release Request Message and Resource Release Request Mini17Message183.6.4.4: Conversation Substate193.6.6.2.2.11: Processing the Universal Handoff Direction Message203.6.6.2.2.13: Processing of Forward Supplemental Channel Assignment Mini Message213.6.6.2.2.14: Processing of Reverse Supplemental Channel Assignment Mini Message223.7.3.3.2.32: Resource Allocation Message233.7.3.3.2.33: Resource Allocation Mini Message243.7.3.3.2.34: Extended Release Message253.7.3.3.2.35: Extended Release Mini Message263.7.3.3.2.36: Universal Handoff Direction Message273.7.3.3.2.37: Extended Supplemental Channel Assignment Message283.7.3.3.2.38: Forward Supplemental Channel Assignment Mini Message293.7.3.3.2.39: Reverse Supplemental Channel Assignment Mini Message303.7.5.20: (base station) Non-Negotiable Service Configuration information record31

TSG-C42 Page 13-34

10/19/2001 C.S0031


mm. Connect the mobile station to the base station as shown in Figure 13.1.2-1.2

Setup a packet data call, using the Dedicated Control Channel (DCCH).3

Verify user traffic (Ex. Browser data) in both directions.4

Instruct the base station to initiate transition to Control Hold Mode via the Extended Release5Message. Verify that the base station sends an Extended Release Message with6PILOT_GATING_RATE =0'1'(1/2 rate), instructing the mobile station to transition to the Control7Hold Mode.8

Verify the following:9

1) The mobile station responds with an Extended Release Response10Message.11

2) Upon transition to the Control Hold Mode:12

• The reverse pilot is gated at the specified rate.13

• Dedicated Control Channel is maintained for signaling.14

• User traffic (Ex. Browser data) is not transmitted on either direction. NOTE:15This can be verified by attempting to send user traffic, while not granting any16requests to transition to the Active Mode.17

• Power Control Channel is maintained at the dedicated control channel.18

Repeat steps c-e for various supported gating rates.19

Repeat steps c-e except instruct the base station to initiate transition to Control Hold Mode via20the Extended Release Mini Message (if mini messages are supported). Verify the mobile station21responds with an Extended Release Response Mini Message.22

Repeat steps c-f except instruct the base station to initiate transition to Control Hold Mode via23the Universal Handoff Direction Message. Verify the mobile station responds with a Handoff24Completion Message.25

13.13.3 Minimum Standard26When the mobile station is instructed to transition to the Control Hold Mode, the expected27signaling exchange takes place. Upon transition to the Control Hold Mode, the reverse pilot is28gated at the specified gating rate, DCCH is maintained with Power Control sub-channel and user29traffic transmission is not allowed in either direction.30

13.14 Mobile Station Initiated Active to Control Hold Mode Transitions31

13.14.1 Definition32This test verifies that the mobile station can request to transition to the Control Hold Mode.33

TSG-C42 Page 13-35

10/19/2001 C.S0031

Extended Release (Mini) Message /Universal Handoff Direction Message

Extended Release Response (Mini) MessageHandoff Completion Message

At the action time:Transition to Control Hold Mode& start reverse pilot gating at thespecified gating rate

BSMS

Active Active

Control Hold Control Hold

Resource Release Request (Mini) Message

Request to transition toControl Hold Mode

1Figure 13.14.1-1 Reference Call Flow for mobile station initiated Active to Control Hold2

Transition3

Traceability: See test 13.134


nn.Connect the mobile station to the base station as shown in Figure 13.1.2-1.6


Verify user traffic (Ex. Browser data) in both directions.8

Cause the mobile station to initiate transition to the Control Hold Mode because of out-of-data9indication from the RLP or otherwise, via the Resource Release Request Message. Verify that10the mobile station sends a Resource Release Request Message to the base station to request11transition to the Control Hold Mode.12

Instruct the base station to accept this request, via an Extended Release Message. Verify the13base station sends an Extended Release Message instructing the mobile station to transition to14the Control Hold Mode.15

Verify the following:16

1) The mobile station responds with an Extended Release Response17Message.18

2) Upon transition to the Control Hold Mode:19


• User traffic (Ex. Browser data) is not transmitted on either direction. NOTE:21This can be verified by attempting to send user traffic, while not granting any22requests to transition to the Active Mode.23

TSG-C42 Page 13-36

10/19/2001 C.S0031

Repeat steps c-f for various supported gating rates.1

Repeat steps c-f except cause the mobile station to initiate transition to the Control Hold Mode,2via the Resource Release Request Mini Message (if mini messages are supported).3

Repeat steps c-f except instruct the base station to accept the request from the mobile station4via Extended Release Mini Message (if mini messages are supported). Verify the mobile station5responds with an Extended Release Response Mini Message.6

Repeat steps c-f except instruct the base station to accept the request from the mobile station7via Universal Handoff Direction Message. Verify the mobile station responds with a Handoff8Completion Message.9

13.14.3 Minimum Standard10When the mobile station requests to transition to the Control Hold Mode, the expected signaling11exchange takes place. Upon transition to the Control Hold Mode, the reverse pilot is gated at the12specified gating rate and user traffic transmission is not allowed in either direction.13

13.15 Base Station Initiated Control Hold to Active Mode Transitions14

13.15.1 Definition15This test verifies the base station can direct the mobile station to transition to the Active Mode.16

Resource Allocation (Mini) Message /Universal Handoff Direction Message /

Extended Supplemental ChannelAssignment Message/

Forward Supplemental ChannelAssignment Mini Message/

Reverse Supplemental ChannelAssignment Mini Message

At the action time:Transition to Active Mode& start reverse pilot continuoustransmission

BSMS

ControlHold

Active Active

BS decides to transitionto Active Mode

ControlHold

17Figure 13.15.1-1 Reference Call Flow for base station initiated Control Hold to Active18

Transition19

Traceability: See test 13.1320


oo. Connect the mobile station to the base station as shown in Figure 13.1.2-1.22

TSG-C42 Page 13-37

10/19/2001 C.S0031


Ensure the mobile station and base station are in Control Hold Mode, using any of the methods2specified in tests 13.13 or 13.14.3

Issue a ping command at the base station to initiate transition to Active Mode, via a Resource4Allocation Message. Verify that the base station sends a Resource Allocation Message5instructing the mobile station to transition to the Active Mode.6

Verify upon transition to the Active Mode:7

1) The reverse pilot transmission is continuous.8

2) User traffic (Ex. Browser data) is transmitted.9

Repeat steps c-e except instruct the base station to initiate transition to the Active Mode via a10Resource Allocation Mini Message (if mini messages are supported).11

Repeat steps c-e except instruct the base station to initiate transition to the Active Mode via a12Universal Handoff Direction Message. Verify the mobile station responds with a Handoff13Completion Message.14

Repeat steps c-e except instruct the base station to initiate transition to the Active Mode via an15Extended Supplemental Channel Assignment Message.16

Repeat steps c-e except instruct the base station to initiate transition to the Active Mode via an17Forward Supplemental Channel Assignment Mini Message.18

Repeat steps c-e except instruct the base station to initiate transition to the Active Mode via an19Reverse Supplemental Channel Assignment Mini Message.20

13.15.3 Minimum Standard21When the mobile station is instructed to transition to the Active Mode, the expected signaling22exchange takes place. Upon transition to the Active Mode, the reverse pilot transmission is23continuous and user traffic transmission is allowed.24

13.16 Mobile Station Initiated Control Hold to Active Mode Transitions25

13.16.1 Definition26This test verifies that the mobile station can request to transition to the Active Mode.27

TSG-C42 Page 13-38

10/19/2001 C.S0031

Resource Allocation (Mini) Message /Universal Handoff Direction Message /

Extended Supplemental ChannelAssignment Message/

Forward Supplemental ChannelAssignment Mini Message/

Reverse Supplemental ChannelAssignment Mini Message

At the action time:Transition to Active Mode& start reverse pilot continuoustransmission

BSMS

ControlHold

Active Active

Request to transition toActive Mode

ControlHold

Resource Request (Mini) Message /Supplemental Channel

Request (Mini) Message

1Figure 13.16.1-1 Reference Call Flow for mobile station initiated Control Hold to Active2

Transition3

Traceability: See 13.1345



b. Setup a packet data call, using the Dedicated Control Channel (DCCH).8

c. Ensure that the mobile station and base station are in Control Hold Mode, using any of9the methods specified in 13.13 or 13.14.10

d. Cause the mobile station to initiate transition to the Active Mode, via a Resource11Request Message. Verify that the mobile station sends a Resource Request Message to12the base station requesting transition to the Active Mode.13

e. Instruct the base station to accept this request, via a Resource Allocation Message.14Verify that the base station sends a Resource Allocation Message instructing the mobile15station to transition to the Active Mode.16

f. Verify upon transition to the Active Mode:17

- The reverse pilot transmission is continuous.18

- User traffic (Ex. Browser data) is transmitted .19

g. Repeat steps c-f except cause the mobile station to initiate transition to the Active20Mode, via the Resource Request Mini Message (if mini messages are supported).21

h. Repeat steps c-f except cause the mobile station to initiate transition to the Active22Mode, via the Supplemental Channel Request Message.23

TSG-C42 Page 13-39

10/19/2001 C.S0031

i. Repeat steps c-f except cause the mobile station to initiate transition to the Active1Mode, via the Supplemental Channel Request Mini Message (if mini messages are2supported).3

j. Repeat steps c-f except instruct the base station to accept transition to the Active Mode4via a Resource Allocation Mini Message (if mini messages are supported).5

k. Repeat steps c-f except instruct the base station to accept transition to the Active Mode6via a Universal Handoff Direction Message. Verify that the mobile station responds with7a Handoff Completion Message.8

l. Repeat steps c-f except instruct the base station to accept transition to the Active Mode9via an Extended Supplemental Channel Assignment Message.10

m. Repeat steps c-f except instruct the base station to accept transition to the Active Mode11via a Forward Supplemental Channel Assignment Mini Message.12

n. Repeat steps c-f except instruct the base station to accept transition to the Active Mode13via a Reverse Supplemental Channel Assignment Mini Message.14

13.16.3 Minimum Standard15When the mobile station requests to transition to the Active Mode, the expected signaling16exchange takes place. Upon transition to the Active Mode, the reverse pilot transmission is17continuous and user traffic transmission is allowed.18

13.17 Base Station Ignores Mobile Station Requested Mode Transitions19

13.17.1 Definition20This test verifies that if the base station ignores mobile station requested transition to Control21Hold or Active Mode, the mobile station remains in the current mode.22

Traceability: See 13.1323



b. Setup a packet data call, using the Dedicated Control Channel (DCCH).26

c. Verify user traffic (Ex. Browser data) in both directions.27

d. Cause the mobile station to initiate transition to the Control Hold Mode, via the28Resource Release Request Message. Verify that the mobile station sends a Resource29Release Request Message to the base station to request transition to the Control Hold30Mode.31

e. Instruct the base station to ignore this request.32

f. Verify that the mobile station and base station remain in the Active Mode and that:33

• The reverse pilot transmission in continuous.34

• User traffic (Ex. Browser data) is transmitted in both directions.35

TSG-C42 Page 13-40

10/19/2001 C.S0031

g. Repeat steps d-f except cause the mobile station to initiate transition to the Control1Hold Mode via the Resource Release Request Mini Message.2

h. Ensure the mobile station and base station are in Control Hold Mode, using any of the3methods specified in 13.3 or 13.4.4

i. Cause the mobile station to initiate transition to the Active Mode, via a Resource5Request Message. Verify that the mobile station sends a Resource Request Message to6the base station requesting transition to the Active Mode.7

j. Instruct the base station to ignore this request.8

k. Verify that the mobile station and base station remain in the Control Hold Mode and9that:10


• User traffic (Ex. Browser data) is not transmitted in either direction. NOTE: This12can be verified by attempting to send user traffic, while not granting any requests13to transition to the Active Mode.14

l. Repeat steps h-k except cause the mobile station to initiate transition to the Active15Mode via the Resource Request Mini Message.16

17

13.17.3 Minimum Standard18When the base station ignores the mobile station requested transition to the Control Hold Mode19or Active Mode, the mobile station remains in the current mode.20

21

13.18 Mobile station Multiplex Option different from Base Station Multiplex Option22

13.18.1 Definition23This test verifies an HSPD call can be successfully negotiated when the multiplex option24supported by the mobile station is different from the multiplex option supported by the base25station.26

Traceability: [see 15]-A9; 2.2.2.1.2.527


a. Configure the mobile station as shown in Figure 13.1.2-1.29

b. Prepare the COMPFILE.RAW 40kbyte binary file at both the remote host and the30TE2M.31

c. Configure the mobile station’s forward MUX Option to 0x80a.32

d. Configure the base station’s MUX Option to a value equal to 0x809.33

e. Setup a mobile station originated call with Service Option 33, and establish an FTP34session with maximum supported Supplemental Channels.35

f. Transfer the file from the remote host to TE2M using the binary “get” command.36

TSG-C42 Page 13-41

10/19/2001 C.S0031

g. After the file transfer is completed in step f, transfer the file from the TE2M to the1remote host using the binary “put” command.2


i. Verify the Multiplex option used on the forward traffic channel is 0x809.4

13.18.3 Minimum Standard5The mobile station and the base station shall successfully negotiate to the minimum of the6multiplex option supported by the mobile station and multiplex option supported by the base7station. Received files shall be complete and identical in content to the original file.8

13.19 Soft Handoff of Fundamental Channel and Supplemental Channels9

13.19.1 Definition10A CDMA call is established on sector α of a sectored base station. The level of sector ß is raised11until soft handoff occurs for both Fundamental and Supplemental Channels. The Pilot levels of12the sectors are checked against the settings for T_ADD and T_DROP.13

Traceability:14

[see 1] 2.1.3.1.4.2, 3.1.3.1.4, 2.6.6.2.7, 3.6.6.2.4;15

[see 4] 2.7.4.25, 2.7.4.27.3, 3.7.5.7.1;16

[see 15]-1.11; 2.2.3 and 2.2.7;17

[see 15]-1.12; 1.4.2.2, 2.2.2 and 2.2.7;18



TSG-C42 Page 13-42

10/19/2001 C.S0031

12

Figure 13.19.2-1 Functional Test Setup for3Soft Handoff of Fundamental Channel and Supplemental Channels.4

5

a. Place a HSPD data call from TE2M to TE2L6

b. Verify base station sector α sends the Extended Supplemental Channel Assignment7Message to assign the maximum number of Supplemental Channels supported by8the system.9

c. Raise the level of sector ß in steps of 1 dB with a dwell time of 5 seconds after each10step until the mobile station has generated the Pilot Strength Measurement Message.11Record the level of Channel ß.12

d. Both sectors of the base station shall respond with a Universal Handoff Direction13Message NUM_FOR_ASSIGN = ‘10’ and with the pilots of both the sectors in the14active set.15

e. Confirm the mobile station sends the Handoff Completion Message.16

f. Transfer a file from the base station to the mobile station (TE2M to TE2L), and verify17that the mobile station shall receive the file using the forward Fundamental Channel18and Supplemental Channels of sector α and sector ß.19

TSG-C42 Page 13-43

10/19/2001 C.S0031

g. Lower the level of sector α in steps of 1 dB with a dwell time of 5 seconds after each1step until the mobile station has generated the Pilot Strength Measurement Message.2Record the level of Channel α.3

h. Both sectors of the base station shall respond with a Universal Handoff Direction4Message NUM_FOR_ASSIGN = ‘10’ and pilot of sector ß in the active set.5

i. Confirm the mobile station sends the Handoff Completion Message.6

j. Transfer a file from the base station to the mobile station (TE2M to TE2L), and verify7that the mobile station shall receive the file using the forward Fundamental Channel8and Supplemental Channel of sector ß.9

k. End the call.10

13.19.3 Minimum Standard11In step g, the Fundamental channel shall enter soft handoff when the mobile station generates a12Pilot Strength Measurement Message and the channel ß Pilot is at a level between T_ADD and13T_ADD +2 dB. Both Fundamental Channel and Supplemental Channels shall be in Soft14Handoff.15

13.20 Soft Handoff of Fundamental Channel only16

13.20.1 Definition17A CDMA call is established on sector α of a sectored base station. The level of sector ß is raised18until soft handoff occurs. The Pilot levels of the sectors are checked against the settings for19T_ADD and T_DROP. The mobile station and base station use the General Handoff Direction20Message to perform soft handoff of the fundamental channel. The Supplemental Channels shall21remain active on sector α.22

Traceability:23

[see 1] 2.1.3.1.4.2, 3.1.3.1.4, 2.6.6.2.7, 3.6.6.2.4;24

[see 4] 2.7.4.25, 2.7.4.27.3, 3.7.5.7.1;25

[see 15]-1.11; 2.2.3 and 2.2.7;26

[see 15]-1.12; 1.4.2.2, 2.2.2 and 2.2.727



b. Place a HSPD data call from TE2M to TE2L30

c. Verify that the base station sector α sends the Extended Supplemental Channel31Assignment Message to assign the maximum number of Supplemental Channels32supported by the system.33

d. Raise the level of sector ß in steps of 1 dB with a dwell time of 5 seconds after each34step until the mobile station has generated the Pilot Strength Measurement Message.35Record the level of Channel ß.36

TSG-C42 Page 13-44

10/19/2001 C.S0031

e. Both sectors of the base station shall respond with a Universal Handoff Direction1Message NUM_FOR_ASSIGN = ‘00’ and with the pilots of both the sectors in the2active set.3

f. Confirm the mobile station sends the Handoff Completion Message.4

g. Transfer a file from the base station to the mobile station (TE2M to TE2L), and verify5that the mobile station shall receive the file using the forward Fundamental Channel6of sector α and sector ß but only the forward Supplemental Channels of sector α.7

h. Lower the level of sector α in steps of 1 dB with a dwell time of 5 seconds after each8step until the mobile station has generated the Pilot Strength Measurement Message.9Record the level of Channel α.10

i. Both sectors of the base station shall respond with a Universal Handoff Direction11Message NUM_FOR_ASSIGN = ‘00’ and pilot of sector ß in the active set.12

j. Confirm the mobile station sends the Handoff Completion Message.13

k. Transfer a file from the base station to the mobile station (TE2M to TE2L), and verify14that the mobile station shall receive the file using the forward Fundamental Channel15of sector ß16

l. End the call.17

13.20.3 Minimum Standard18In step g, the fundamental channel shall enter soft handoff when the mobile station generates a19Pilot Strength Measurement Message and the channel ß Pilot is at a level between T_ADD and20T_ADD +2 dB. The Supplemental Channels shall remain active on sector α.21

13.21 Adding Supplemental Channels during Soft Handoff22

13.21.1 Definition23This test verifies that up to 2 Supplemental Channels can be added in an HSPD call while in two-24way soft handoff on the Fundamental Channel.25

Traceability:26

[see 1] 2.1.3.1.4.2, 3.1.3.1.4, 2.6.6.2.7, 3.6.6.2.4;27

[see 4] 2.7.4.25, 2.7.4.27.3, 3.7.5.7.1;28

[see 15]-1.11; 2.2.3 and 2.2.7;29

[see 15]-1.12; 1.4.2.2, 2.2.2 and 2.2.7;30



b. At the remote host prepare the appropriate file, corresponding to the rate that will33be tested (Note: this will guarantee sufficient transfer time). Refer to Table D-1 in34Data Services Annex D.35

TSG-C42 Page 13-45

10/19/2001 C.S0031

c. Setup a mobile station terminated call with Service Option 33, and establish an FTP1session with base station #1 on the Fundamental Channel only.2

d. Adjust the signal strength of base station #2 until both base stations have equal3transmit power.4

e. Verify the mobile station is in two-way handoff.5

f. Begin transferring the file from the remote host to TE2M using the binary “get”6command.7

g. Generate a Universal Handoff Direction Message or an Extended Supplemental8Channel Assignment Message with NUM_FOR_SCH = 01 or 10 to allocate the9maximum number of Supplemental Channels supported by the system.10

h. Verify the file transfer continues after Supplemental Channel assignment during11handoff and base station #1 and 2 both use the maximum number of Supplemental12Channels supported by the system in addition to the Fundamental Channel to13transfer the file.14

i. Ensure the data transfer rate is not limited by network limitations. Record time15elapsed during file transfer.16

k. End the FTP session.17

13.21.3 Minimum Standard18The mobile station shall successfully perform the handoff, and data transfer shall continue after19the handoff. Under ideal channel conditions, the measured throughput in each case should be20close to the measured throughput with no handoff with the maximum number of Supplemental21Channels supported by the system.22

13.22 Hard Handoff to HSPD-capable system23

13.22.1 Definition24This test verifies hard handoff to an HSPD-capable system during an HSPD call.25

Traceability:26

[see 1] 2.1.3.1.4.2, 3.1.3.1.4, 2.6.6.2.7, 3.6.6.2.4;27

[see 4] 2.7.4.25, 2.7.4.27.3, 3.7.5.7.1;28

[see 15]-1.11; 2.2.3 and 2.2.7;29

[see 15]-1.12; 1.4.2.2, 2.2.2 and 2.2.7;30


a. Connect the mobile station to the base stations as shown in Figure 13.19.2-1.32


c. Base station 1 should be configured for P_REV=6 or higher.36

TSG-C42 Page 13-46

10/19/2001 C.S0031

d. Base station 2 should be configured for P_REV=6 or higher with a different1frequency channel from base station #1.2

e. Setup a mobile station terminated call with Service Option 33 and establish an FTP3session with base station #1 with the maximum number of Supplemental Channels4supported by the system.5


g. While the file is being transferred, adjust the signal strength of base station #2 until8both base stations have equal transmit power.9

h. At base station #1, setup a hard handoff to base station #2 using the Universal10Handoff Direction Message.11

i. Verify that at the base station, hard handoff is successful.12

j. Verify base station #2 generates a Universal Handoff Direction Message or an13Extended Supplemental Channel Assignment Message to assign the maximum14number of Supplemental Channels supported by the system to the mobile station.15

k. Verify that at the base station, service negotiation is successful and that the mobile16station is using Service Option 33 with the maximum number of Supplemental17Channels supported by the system.18

l. Verify the file transfer continues after the hard handoff.19

m. End FTP session.20

13.22.3 Minimum Standard21The mobile station shall successfully handoff to an HSPD capable system of the same P_REV22and shall keep using the maximum supported number of Supplemental Channels. Data transfer23shall be successful.24

13.23 Hard Handoff from MSPD to HSPD25

13.23.1 Definition26This test verifies hard handoff from an MSPD-capable system to an HSPD-capable system.27

Traceability:28

[see 1] 2.1.3.1.4.2, 3.1.3.1.4, 2.6.6.2.7, 3.6.6.2.4;29

[see 4] 2.7.4.25, 2.7.4.27.3, 3.7.5.7.1;30

[see 15]-1.11; 2.2.3 and 2.2.7;31

[see 15]-1.12; 1.4.2.2, 2.2.2 and 2.2.732



TSG-C42 Page 13-47

10/19/2001 C.S0031

b. At remote host prepare the appropriate file, corresponding to the rate that will be1tested (Note: this will guarantee sufficient transfer time). Refer to Table D-1 in Data2Services Annex D.3

c. Base station 1 should be configured for P_REV=5.4


e. Setup a mobile station terminated call with Service Option 22 and establish an FTP7session with base station #1 on the Fundamental and N Supplemental Code8Channels.9



h. At base station #1, setup a hard handoff to base station #2 using the General14Handoff Direction Message.15

i. Verify at the base station that the hard handoff is successful.16

j. Verify at the mobile station that Service Option 22 is still in use.17

k. Verify file transfer continues after the hard handoff.18

l. At base station #2 generate and send an In-Traffic System Parameters Message or a19General Handoff Direction Message with P_REV set to 620

m. At base station #2 generate and send a Universal Handoff Direction Message with21Service option 33 and RC 3 for forward and Reverse links in the service22configuration record and also NUM_FOR_SCH = 01 or 10 (1 or 2 SCHs) whichever is23the maximum number of Supplemental Channels supported by the mobile station.24

n. Verify the mobile station responds with a Handoff Completion Message.25

o. Verify file transfer continues after the hard handoff.26

p. Verify file transfer takes place with the number of Supplemental Channels specified27in step m and on RC 3.28

q. End the FTP session29

13.23.3 Minimum Standard30The Mobile station shall successfully handoff from an MSPD capable system to an HSPD31capable system with higher P_REV. The Mobile station shall then negotiate to higher RC and32use Supplemental Channels. Data transfer shall be successful.33

13.24 Hard Handoff from LSPD to HSPD34

13.24.1 Definition35This test verifies hard handoff from an LSPD-capable system to an HSPD-capable system.36

TSG-C42 Page 13-48

10/19/2001 C.S0031

Traceability:1

[see 1] 2.1.3.1.4.2, 3.1.3.1.4, 2.6.6.2.7, 3.6.6.2.42

[see 4] 2.7.4.25, 2.7.4.27.3, 3.7.5.7.1;3

[see 15]-1.11; 2.2.3 and 2.2.7;4

[see 15]-1.12; 1.4.2.2, 2.2.2 and 2.2.75




c. Base station 1 should be configured for P_REV=3.11


e. Setup a mobile station terminated call with Service Option 7 and establish an FTP14session with base station #1.15



h. At base station #1, setup a hard handoff to base station #2 using the Handoff20Direction Message.21

i. Verify at the base station that the hard handoff is successful.22

j. Verify at the mobile station that Service Option 7 is still in use.23

k. Verify file transfer continues after the hard handoff.24

l. At base station #2 generate and send an In-Traffic System Parameters Message with25P_REV set to 626

m. At base station #2 generate and send a Universal Handoff Direction Message with27Service option 33 and RC 3 for forward and Reverse links in the service28configuration record and also NUM_FOR_SCH = '01' or '10' (1 or 2 SCHs) whichever29is the maximum number of Supplemental Channels supported by the mobile30station.31

n. Verify the mobile station responds with a Handoff Completion Message.32

o. Verify file transfer continues after the hard handoff.33

p. Verify file transfer takes place with the number of Supplemental Channels specified34in step m and on RC 3.35

q. End the FTP session36

TSG-C42 Page 13-49

10/19/2001 C.S0031

13.24.3 Minimum Standard1The Mobile station shall successfully handoff from an LSPD capable system to an HSPD capable2system with higher P_REV. The Mobile station shall then negotiate to higher RC and use3Supplemental Channels. Data transfer shall be successful.4

13.25 Hard Handoff to a different RC5

13.25.1 Definition6This test verifies hard handoff to a different RC during an HSPD call.7

Traceability:8

[see 1] 2.1.3.1.4.2, 3.1.3.1.4, 2.6.6.2.7, 3.6.6.2.4;9

[see 4] 2.7.4.25, 2.7.4.27.3, 3.7.5.7.1;10

[see 15]-1.11; 2.2.3 and 2.2.7;11

[see 15]-1.12; 1.4.2.2, 2.2.2 and 2.2.7;12




c. Base station #1 should be configured for P_REV=6.18

d. Base station #2 should be configured for P_REV=6 or higher with a different19frequency channel from base station #1.20

e. Setup a mobile station terminated call with Service Option 33 with RC 3 on both21forward and reverse link and establish an FTP session with base station #1 on the22Fundamental and the maximum number of Supplemental Channels supported by23the mobile station.24



h. At base station #1, setup a hard handoff to base station #2 using the Universal29Handoff Direction Message with FOR_FCH_RC and SCH_RC for the Forward30Supplemental Channel(s) set to 5 and REV_FCH_RC and SCH_RC for the Reverse31Supplemental Channel(s) set to 4.32

i. Verify base station #2 generates a Universal Handoff Direction Message or an33Extended Supplemental Channel Assignment Message to assign to the mobile station34the maximum number of Supplemental Channels supported by the mobile station.35

j. Verify at the base station that the hard handoff is successful.36

TSG-C42 Page 13-50

10/19/2001 C.S0031

k. Verify at the mobile station that Service Option 33 and the maximum number of1Supplemental Channels supported by the mobile station are still in use and Radio2Configurations 5 and 4 are used on forward and reverse links.3

l. Verify file transfer continues after the hard handoff.4

m. End FTP session.5

13.25.3 Minimum Standard6The mobile station shall successfully handoff to an HSPD Capable system with the same P_REV7but higher supported RC and shall successfully negotiate to use the higher RC.8Data transfer shall be successful.9

13.26 Mobile Station Aborts R-SCH10

13.26.1 Definition11The mobile station uses the T_ADD Reverse Supplemental Channel abort feature to explicitly12terminate any active Reverse Supplemental Channel assignments.13

Traceability (see [4] unless otherwise noted)14

2.6.6.2.11 Processing of the Reverse Supplemental Code Channels and Reverse15Supplemental Channels16

2.7.1.3.2.4 Origination Message172.7.2.3.2.18 Supplemental Channel Request Message182.7.2.3.2.5 Pilot Strength Measurement Message193.6.6.2.1.1 System Parameters203.6.6.2.2 Call Processing During Handoff213.6.6.2.2.12 Processing Extended Supplemental Channel Assignment223.7.2.3.2.1 System Parameters Message233.7.3.3.2.37 Extended Supplemental Channel Assignment Message243.1 Standard Service Option Number Assignments (see [17])25


a. Connect the mobile station and base station as shown in Figure 13.19.2-1.27

1) Base station #1 has an arbitrary pilot PN offset of P1, frequency of ƒ1 and28is referred to as Channel 1.29

2) Base station #2 has an arbitrary pilot PN offset of P2, frequency of ƒ1 and30is referred to as channel 2.31

b. Set the test parameters as specified in table 13.24.2-1.3233

TSG-C42 Page 13-51

10/19/2001 C.S0031

Table 13.26.2-1 Test Parameters1


Ior/Ioc dB 0 -10



Ioc dB/1.23 MHz -75 -75


2

c. Originate a mobile station to land party call using the following parameters in the3Origination Message.4

5FIELD VALUE

SPECIAL_SERVICE ‘1’

SERVICE_OPTION 0x0021

FOR_RC_PREF Greater than ‘00010’

REV_RC_PREF Greater than ‘00010’

6

d. Begin data transfer from TE2M.7

e. Cause the mobile station to send a Supplemental Channel Request Message or8Supplemental Channel Request Mini Message.9

f. Instruct the base station to respond to the Supplement Channel Request Message10with an Extended Supplemental Channel Assignment Message with the following11parameters:12

13Field Value

USE_T_ADD_ABORT ‘1’

NUM_REV_SCH ‘01’ or ‘10’ (One or two R-SCHs)

14

g. Before the data transfer is complete, raise the level of Channel 2 above the value of15T_ADD until the mobile station generates a Pilot Strength Measurement Message.16


1) The mobile station has aborted SCH.18

2) The mobile station sets IGNORE_ESCAMs=1;19

3) The mobile station sets SCRM_SEQ_NUMs to (SCRM_SEQ_NUMs+1) mod2016.21

TSG-C42 Page 13-52

10/19/2001 C.S0031

4) The mobile station transmits a Supplemental Channel Request Message1with USE_SCRM_SEQ_NUM set to ‘1’, SCRM_SEQ_NUM set to SCRM_SEQ_NUMs,2and SIZE_OF_REQ_BLOB set to ‘0000’.3

5) The mobile station remains active and continues the data transfer using4the R-FCH.5

i. Instruct the base station to send an Extended Supplemental Channel6Assignment Message with R-SCH assignment information included but without7including SCRM_SEQ_NUM.8

j. Verify the mobile station does not process the R-SCH assignment9information portion of the Extended Supplemental Channel Assignment Message10and keeps IGNORE_ESCAMs=’1’.11

k. Instruct the base station to send an Extended Supplemental Channel12Assignment Message with R-SCH assignment information included and a13SCRM_SEQ_NUM which is different from the SCRM_SEQ_NUM in the last received14Supplemental Channel Request Message.15

l. Verify the mobile station does not process the R-SCH assignment16information portion of the Extended Supplemental Channel Assignment Message17and keeps IGNORE_ESCAMs=’1’.18

m. Instruct the base station to send an Extended Supplemental Channel19Assignment Message with R-SCH assignment information included and a20SCRM_SEQ_NUM which is same as the SCRM_SEQ_NUM in the last received21Supplemental Channel Request Message.22

n. Verify the mobile station does process the R-SCH assignment information23portion of the Extended Supplemental Channel Assignment Message and sets24IGNORE_ESCAMs=0.25

o. End the call.26

p. Repeat steps a to h using the Universal Handoff Direction Message.27

13.26.3 Minimum Standard28The mobile station shall terminate any active Reverse Supplemental Channel Assignments29explicitly when USE_T_ADD_ABORT is set to ‘1’ and the strength of any Neighbor Set or30Remaining Set pilot is above T_ADDs.31

13.27 RLP Operation in Rayleigh Fading Environment32

13.27.1 Definition33This test verifies data transfer under 3 Ray Rayleigh channel conditions at 100km/hr, with34Supplemental Channels. This test verifies that RLP recovers erased data frames, and is intended35to exercise RLP negative acknowledgements (NAKs), retransmission’s, and aborts in the36forward and reverse directions.37

TSG-C42 Page 13-53

10/19/2001 C.S0031

Traceability:1

[see 4] 2.7.2.3.2.18, 2.7.2.3.2.28, 2.6.4.3Figure B-26;2

[see 15]-1.11; 2.2.3 and 2.2.7;3

[see 15]-1.12; 1.4.2.2, 2.2.2 and 2.2.7;4



8Figure 13.27.2-1 Functional Test Setup for RLP Operation in9

Rayleigh Fading Environment1011

b. Both at the remote host and at the TE2M prepare the appropriate file, corresponding12to the rate that will be tested (Note: this will guarantee sufficient transfer time).13Refer to Table D-1 in Data Services Annex D.14

c. Set the channel simulator using the parameters as specified in Table 13.27.2-1.1516

TSG-C42 Page 13-54

10/19/2001 C.S0031

Table 13.27.2-1 HSPD Test Parameters - 100 km/hr1



Number of Paths # 3


dB 0


dB -3

Delay from Path 1 to Input µsec 0

Delay from Path 2 to Input µsec 2

Delay from Path 3 to Input µsec 14.5

2


e. Configure the base station to assign one Supplemental Channel to the mobile5station using the Universal Handoff Direction Message or the Extended Supplemental6Channel Assignment Message.7


g. Ensure data transfer rate is not limited by network limitations. Record the time9elapsed during file transfer.10

h. Transfer the file from the TE2M to the remote host using the binary “put” command.11

j. Ensure data transfer rate is not limited by network limitations. Record the time elapsed12during file transfer.13

j. End FTP session.14

13.27.3 Minimum Standard15Data transfer shall be successful, and the data transfer throughput shall be no less than 70% of16the throughput measured in the normal condition.17

13.28 RLP Operation in Severely Degraded Channel18

13.28.1 Definition19This test verifies data transfer under severely degraded channel conditions, with Supplemental20Channels. This test is intended to exercise RLP resets due to long erasure bursts and TCP21retransmission.22

TSG-C42 Page 13-55

10/19/2001 C.S0031

Traceability:1

[see 4] 2.7.2.3.2.18, 2.7.2.3.2.28, 2.6.4.3Figure B-26;2

[see 15]-1.11; 2.2.3 and 2.2.7;3

[see 15]-1.12; 1.4.2.2, 2.2.2 and 2.2.7;4



b. Both at the remote host and at the TE2M prepare the appropriate file, corresponding7to the rate that will be tested (Note: this will guarantee sufficient transfer time).8Refer to Table D-1 in Data Services Annex D.9

c. Set the channel simulator to one Ray 3 km/hr Rayleigh fading on the forward link.10


e. Configure the base station to assign one Supplemental Channel to the mobile13station using the Universal Handoff Direction Message or the Extended Supplemental14Channel Assignment Message.15


g. Ensure data transfer rate is not limited by network limitations. Record time elapsed17during file transfer.18


13.28.3 Minimum Standard20Data transfer shall be successful and the data transfer throughput shall be no less than 70% of the21throughput measured in the normal conditions.22

13.29 Mobile Station Originated Short Data Burst23

13.29.1 Definition24This test verifies a dormant packet data service at the mobile station can send a Short Data Burst25that is transmitted on r-csch via a Data Burst Message.26

Traceability27

1.2.1.6 Short Data Burst Teleservice Service Primitives (see [2])282.2.3 Control Plane Entities [2]292.2.3.1.5.2 Substates of the Dormant State [2]302.2.4.3 Short Data Bursts [2]312.2.4.3.3.3 Short Data Burst Teleservice [2]322.6.2.2 Response to Overhead Information Operation (see [4])332.6.2.6 Mobile Station Message Transmission Operation [4]342.7.1.3.2.3 Data Burst Message [4]353.6.3.7 Response to a Data Burst Message [4]363.7.2.3.2.9 Data Burst Message [4]373.7.2.3.2.13 Extended System Parameters Message [4]384.1 Standard Data Burst Message Burst Type Assignments (see [17])39

TSG-C42 Page 13-56

10/19/2001 C.S0031



b. Instruct the base station to send an Extended System Parameters Message with the3following value:4

5FIELD VALUE

SDB_SUPPORTED ‘1’

6

c. Ensure the mobile station is in the Dormant State.7

d. Instruct the mobile station to send a Short Data Burst and verify the Data Burst8Message on the r-csch has the following values:9

10FIELD VALUE

MSG_NUMBER ‘1’

BURST_TYPE ‘000110’

NUM_MSGS ‘1’

NUM_FIELDS length+3

CHARi SDU to be transmitted

11

e. Verify the CHARi fields of the Data Burst Message from step d has the following12values:13

14FIELD VALUE

SR_ID Service referenceidentifier being used.

RESERVED ‘00000’

SO Service option beingused

SDU_DATA Data octets included inthe message

15

f. Verify the base station receives the Data Burst Message and responds with a Layer 216acknowledgment to the mobile station. The base station shall receive the Short Data17Burst correctly.18

19

13.29.3 Minimum Standard20The mobile station shall send a Short Data Burst using a Data Burst Message on the r-csch.21Verify the base station receives the Short Data Burst correctly and responds to the Data Burst22Message with a Layer 2 acknowledgement.23

TSG-C42 Page 13-57

10/19/2001 C.S0031

13.30 Mobile Station Terminated Short Data Burst12

13.30.1 Definition3This test verifies that a dormant packet data service at the base station can send a Short Data4Burst that is transmitted on f-csch via a Data Burst Message.5

Traceability6

1.2.1.6 Short Data Burst Teleservice Service Primitives (see [2])72.2.3 Control Plane Entities [2]82.2.3.1.5.2 Substates of the Dormant State [2]92.2.4.3 Short Data Bursts [2]102.2.4.3.3.3 Short Data Burst Teleservice [2]112.6.2.2 Response to Overhead Information Operation (see [4])122.6.2.6 Mobile Station Message Transmission Operation [4]132.7.1.3.2.3 Data Burst Message [4]143.6.3.7 Response to a Data Burst Message [4]153.7.2.3.2.9 Data Burst Message [4]163.7.2.3.2.13 Extended System Parameters Message [4]174.1 Standard Data Burst Message Burst Type Assignments (see [17])18

19



b. Instruct the base station to send an Extended System Parameters Message with the22following value:23

24FIELD VALUESdB_SUPPORTED ‘1’

25

c. Ensure the mobile station is in the Dormant State.26

d. Instruct the base station to send a Short Data Burst to the mobile station and verify27the Data Burst Message on the f-csch has the following values:28

29FIELD VALUEMSG_NUMBER ‘1’BURST_TYPE ‘000110’NUM_MSGS ‘1’NUM_FIELDS length+3CHARi SDU to be transmitted

30

e. Verify the CHARi fields of the Data Burst Message from step d has the following31values:32

33FIELD VALUESR_ID Service reference

identifier being used.

TSG-C42 Page 13-58

10/19/2001 C.S0031

RESERVED ‘00000’SO Service option being

usedSDU_DATA Data octets included in

the message1

f. Verify the mobile station receives the Data Burst Message and responds with a Layer22 acknowledgment to the base station. The mobile station shall receive the Short3Data Burst correctly.4

13.30.3 Minimum Standard5The base station shall send a Short Data Burst using a Data Burst Message on the f-csch. Verify6the mobile station receives the Short Data Burst correctly and responds to the Data Burst7Message with a Layer 2 acknowledgement.8

13.31 Mobile Assisted Burst Operation Parameters Message Test9

13.31.1 Definition10This test verifies that the mobile station that supports MABO operation correctly responds to the11Mobile Assisted Burst Operation Parameters Message by sending the correct Pilot Strength12Measurement Mini Messages. The following cases are tested:13

• Basic periodic operation with reporting interval set to 1.2 seconds14

• Order mode operation with minimum pilot power strength delta of 3dB15

• Threshold mode operation with pilot power strength lower bounds set to -16 and -18dB16and upper bounds set to -12 and -14dB17

Traceability: (See [4])18

2.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages192.6.6.2.5.2 Processing of Reverse Traffic Channel Handoff Messages202.7.2.3.2.27 Pilot Strength Measurement Mini Message213.6.6.2.2.15 Processing of Mobile Assisted Burst Operation Parameters Message223.7.3.3.2.40 Mobile Assisted Burst Operation Parameters Message23



b. Set the test parameters as specified in table 13.31.2-1.2627

TSG-C42 Page 13-59

10/19/2001 C.S0031

Table 13.31.2-1 Test Parameters1


Ior/Ioc dB 0 0



Ioc dB/1.23 MHz -75 -75


2

c. Set up a data call with Service Option 33 using one Supplemental Channel.3

d. Instruct the base station to send Extended Channel Assignment Message to ensure that4both Channel 1 and Channel 2 are in the active set.5

6

e. From the base station generate a Mobile Assisted Burst Operation Parameters7Message with the following parameters:8

9Field Value

ORDER_FLAG ‘0’

PERIODIC_FLAG ‘1’

NUM_PILOTS ‘001’

PERIODIC_INTERVAL ‘111100’ (1.2 s)

THRESHOLD_FLAG ‘0’

10

f. Continue the call for 30 seconds and verify the mobile station generates a Pilot11Strength Measurement Mini Message approximately every 1.2 seconds.12

g. End the call.13

h. Repeat steps a to e with the following values for the Mobile Assisted Burst Operation14Parameters Message:15

16Field Value

ORDER_FLAG ‘1’

PS_MIN_DELTA ‘100’ (2.5dB)

ORDER_INTERVAL ‘111’ (140 ms)



17

i. Continue the call for 15 seconds and ensure the mobile station does not generate18any further Pilot Strength Measurement Mini Messages during this time.19

TSG-C42 Page 13-60

10/19/2001 C.S0031

j. Rapidly increase the level of Channel 2 by 3dB and simultaneously decrease the1level of Channel 1 by 2dB. Continue the call for 5 seconds.2

k. Verify the mobile station generates a single Pilot Strength Measurement Mini Message3for the pilot from Base Station #2 approximately 140ms after the level change in4step j.5

l. End the call.6

m. Repeat steps a to e with the following values for the Mobile Assisted Burst Operation7Parameters Message:8

9Field Value

ORDER_FLAG ‘0’



PS_FLOOR_HIGH ‘010000’ (-16dB)

PS_FLOOR_LOW ‘010010’ (-18dB)

PS_CEILING_HIGH ‘001100’ (-12dB)

PS_CEILING_LOW ‘001110’ (-14dB)

THRESHOLD_INTERVAL ‘110010’ (1.0 s)

10

n. Continue the call for 15 seconds and ensure the mobile station does not generate11any further Pilot Strength Measurement Mini Messages during this time.12

o. Decrease the level of Channel 1 by 6dB and then slowly by another 4dB. Then13continue the call for 5 seconds.14

p. Ensure the mobile station generates a single Pilot Strength Measurement Mini15Message as the level of Channel 1 drops below -18dB.16

q. Increase the level of Channel 1 by 6dB then slowly by another 4dB. Then continue17the call for 5 seconds.18

r. Ensure that the mobile station generates a single Pilot Strength Measurement Mini19Message as the level of Channel 1 rises above -12dB.20

s. Terminate the call.21

13.31.3 Minimum Standard22The mobile station shall correctly respond to the Mobile Assisted Burst Operation Parameters23Message by sending the correct Pilot Strength Measurement Mini Messages at the correct times.24

13.32 Mobile Station and Base Station Operating in Different States25

13.32.1 Definition26This test verifies the mobile station and base station correct the condition of the mobile station27operating in the Null State and the base station/PCF operating in the Dormant State. [4] permits28

TSG-C42 Page 13-61

10/19/2001 C.S0031

two standardized approaches for the mobile station to reject/release a General Page Message1containing Service Option = 0x21 when the mobile station is in the Null State and the base2station/PCF is in the Dormant State. In both implementations, the mobile station and base3station/PCF shall transition to the Null State.4In the preferred implementation, a mobile station in the Null State will reject a General Page5Message containing Service Option = 0x21 by sending a Page Response Message containing6Service Option = 0x00. The base station should send a Release Order to the mobile station.7In an alternate implementation7, a mobile station in the Null State will accept a General Page8Message containing Service Option = 0x21 by sending a Page Response Message containing9Service Option = 0x21. After the base station assigns a traffic channel, the mobile station sends a10Release Order containing ORDQ=2 to release the call.11

Traceabilities:123.7.4.1 Page Response Substate [4]132.7.1.3.2.5 Page Response Message [4]143.6.2.3 Mobile Station Directed Messages [4]153.6.3.3 Responding to a Page Response Message [4]163.7.4 Orders [4]172.2.2.2.1.3 Paging State [15]18

13.32.2 Call Flow Examples19

13.32.2.1 Preferred Implementation202122232425262728293031323334

13.32.2.2 Alternate Implementation35

363738394041

7 Future revisions to [4] may discontinue supporting this alternate approach; therefore, futuremobile station and base station implementations should support the preferred implementation.

Dormant State Dormant State

MS BS/PCF

Null StateDormant State

Null State Null State

General Page, SO: 0x21

Page Response Msg with SO: 0x00

MS and BS are not insame state. PPP sessionin MS has been closedwithout notifying BS.

BS tries to transition MS toActive State

BS should send Release Order

Dormant State Dormant State

MS BS/PCF

Null StateDormant State

General Page, SO: 0x21

Page Response Msg with SO: 0x21

MS and BS are not insame state. PPP sessionin MS has been closedwithout notifying BS.

BS tries to transition MS toActive State

TSG-C42 Page 13-62

10/19/2001 C.S0031

123456789

10111213


13.32.3.1 Preferred Implementation15


b. Set up a Service Option 0x21 call using a dedicated traffic channel.17

c. Allow the mobile station to enter the Dormant State.18

d. Verify the base station/PCF and mobile station are operating in the Dormant State.19

e. Instruct the mobile station to transition to the Null State (i.e. terminate the PPP session)20without notifying the base station. (e.g., disconnect the mobile station from the laptop.)21

f. Instruct the base station to initiate the Dormant to Active transition by sending a22General Page Message to the mobile station with the Service Option = 0x21.23

g. Verify the mobile station sends a Page Response Message with the Service Option =240x00.25

h. The base station should send a Release Order to the mobile station after receiving the26Page Response Message with the Service Option = 0x00.27

i. Verify the mobile station and base station/PCF are now operating in the Null State.28

13.32.3.2 Alternate Implementation29


b. Set up a Service Option 0x21 call using a dedicated traffic channel.31

c. Allow the mobile station to enter the Dormant State.32

d. Verify the base station/PCF and mobile station are operating in the Dormant State.33

e. Instruct the mobile station to transition to the Null State (i.e. terminate the PPP session)34without notifying the base station. (e.g., disconnect the mobile station from the laptop.)35

f. Instruct the base station to initiate the Dormant to Active transition by sending a36General Page Message to the mobile station with the Service Option = 0x21.37

TSG-C42 Page 13-63

10/19/2001 C.S0031

g. Verify the mobile station sends a Page Response Message with the Service Option =10x21.2

h. After the base station assigns a traffic channel, verify the mobile station sends a3Release Order containing ORDQ=2 to release the call.4

i. Verify the mobile station and base station/PCF are now operating in the Null State.5

13.32.4 Minimum Standard6In both the preferred and alternate implementations, the mobile station and base station/PCF7shall both transition to the Null State.8

DATA SERVICES TESTS ANNEX9Data Services Annex A: References10RFC 792 Internet Control Message Protocol11RFC 854 Telnet Protocol specification12RFC 959 File Transfer Protocol13RFC 1144 Compressing TCP/IP headers for low-speed serial links14RFC 1332 The PPP Internet Protocol Control Protocol (IPCP)15RFC 1661 The Point-to-Point Protocol (PPP)16RFC 1662 PPP in HDLC-like Framing17Data Services Annex B: Description of Compressible Test Data Files18COMPFILE.RAW is a 40000-byte long file, which is assembled of five sections. The first 800019bytes are compressible, the next 8000 are not compressible, the next 8000 are compressible, and20so on.21Transfer Time is in format X:YY where X is number of minutes, and Y is number of seconds.22

23Data File Rate Set 1

Max Transfer TimeRate Set 2

Max Transfer Time

COMPFILE.RAW 1:20 0:50

Note: The maximum transfer time of a file is 8 x M / (R x 0.5) seconds, where M is the24number of bytes in the file, and R is the payload rate for a given rate set.25

For Rate Set 1, R is 8000 bps. For Rate Set 2, R is 13000 bps. The value 0.5 represents26the minimum acceptable throughput by the CDG.27

To transfer a 40,000 byte file over Rate Set 1, the maximum acceptable transfer time is28(8 x 40,000 bytes) / (8000 x 0.5) bps = 80 seconds = 1 minutes and 20 seconds.29

30

TSG-C42 Page 13-64

10/19/2001 C.S0031

Data Services Annex C: Standard ITU Fax Pages1Use the following Image Files from the Standard Digitized Image Set on CD-ROM (CD-03 ed.)2of the ITU-T Recommendation T.24 Encl. (11/94).3

4FAX Figure Description Filename Size (K Bytes)

FAX 1 01 English Letter F01_300.tif 57 KB

FAX 2 09 Test Pattern Facsimile Test Chart F09_400.tif 391 KB

FAX 3 10 Half-tone Facsimile Test Chart F10_300.tif 385 KB

5

Sending a 3-page fax consisting of the preceding three ITU T.24 images, between two landline6fax modems may be performed to establish the "theoretical maximum throughput" benchmark.7In order to allow for different modem types etc., the same test may be run using modems from8different manufacturers, between two modems, and between a modem and a land line fax9machine, and the results averaged. Typical results follow:10Average Landline Fax Transfer Time @9600 bps = 6 min 29 sec = 389 sec11Average Landline Fax Transfer Time @14400 bps = 4 min 31 sec = 271 sec12In the case of Async Data, the acceptable throughput has been set at 0.5 times the maximum13throughput. Assuming the acceptable throughput for Fax transfers is 0.5 times the landline14throughput:15Rate Set 1 Maximum Fax Transfer Time = 1 / 0.5 x 389 sec= 778 sec= 12 min 58 sec16Rate Set 2 Maximum Fax Transfer Time = 1 / 0.5 x 271 sec= 542 sec= 9 min 2 sec17

18

TSG-C42 Page 13-65

10/19/2001 C.S0031

Data Services Annex D: Test Files1RAND200.BIN is a 200,000 byte long file. The first 4000 bytes of RAND200.BIN contain2patterned data (padded with zeros). The remaining 196,000 bytes of this file contain random3data. This file is transferred to ensure that neither the IWF nor the MT2 have trouble transferring4different patterns of data. This file contains all possible byte values from 0x00 to 0xFF. As well,5it contains double escape sequences and software flow control characters.6RAND200.ASC is a 200,000 byte long file.7Transfer Time is in format X:YY where X is number of minutes, and Y is number of seconds.8

9Data File Rate Set 1

Max Transfer TimeRate Set 2

Max Transfer Time

RAND200.BIN 5:20 3:17

RAND200.ASC 5:20 3:17

Note: The maximum transfer time of a file is 8 x M / (R x 0.625) seconds, where M is the10number of bytes in the file, and R is the payload rate for a given rate set.11

For Rate Set 1, R is 8000 bps. For Rate Set 2, R is 13000 bps. The value 0.62512represents the minimum acceptable throughput.13

To transfer a 200,000 byte file over Rate Set 1, the maximum acceptable transfer time14is (8 x 200,000 bytes) / (8000 x 0.625) bps = 320 seconds = 5 minutes and 20 seconds.15

Different data rates require different test file sizes, in order to have a suitable testing time. The16corresponding mapping between data rates and test file sizes is shown in Table D-1. Files larger17than 200000 bytes can be constructed by concatenating more than one RAND200.BIN file.18

Table D-1 Test files to be used corresponding to tested rates.19

Data Rate Granted (bps)

F-RC3,4 / R-RC3 F-RC5 / R-RC4

Test file size (bytes)

9600 14400 200000

19200 28800 400000

38400 57600 600000

76800 115200 1200000

153600 230400 2000000

20

TSG-C42 Page 14-1

10/19/2001 C.S0031

14 OVER-THE-AIR SERVICES1Table 14-1 lists over-the-air services tests.2

Table 14-1 Over-the-Air Services Tests3

Test No. Title

14.1 OTASP Service Request Processing

14.2 OTAPA Service Request Processing for a Mobile Station in Mobile Station Idle State

14.3 OTAPA Service Request Processing for a Mobile Station in Conversation Substate

14.4 OTAPA Service Request Processing Interrupted by User Action

14.1 OTASP Service Request Processing45

14.1.1 Definition6This test verifies a mobile station can generate an OTASP Service Request and download the7parameters necessary for service activation on the network where the mobile station intends to8register.9

Traceability: IS-683-A; 3.2, 3.3, 4.2, 4.310

14.1.2 Method of Measurement11Note: Ensure the mobile station used in this test has not been activated previously.12

a. Connect the base station and the mobile station as shown in Figure 14.1.2-1.13

b. Setup an OTASP call with the appropriate activation code. Refer to Table 14.1.2-1.14

c. Verify the Origination Message contains the default values of IMSI_CLASS, MCC,15IMSI_11_12, IMSI_S and SID in the non-programmed mobile. Record these values.16

d. Verify the mobile station acquires the appropriate system using the activation code17as the dialed digits. Verify the call is established.18

19Figure 14.1.2-1 Functional Setup for Testing OTASP20

TSG-C42 Page 14-2

10/19/2001 C.S0031

Table 14.1.2-1 Activation Code Assignments1

Selected System Activation Code

800 MHz A-BAND *22800

800 MHz B-BAND *22801

1.9 GHz A Block *22802

1.9 GHz B Block *22803

1.9 GHz C Block *22804

1.9 GHz D Block *22805

1.9 GHz E Block *22806

1.9 GHz F Block *22807

Reserved *22808 -*22899

Note: 228 = key pad alpha characters: ACT2

e. Verify the base station sends a Protocol Capability Request Message to the mobile3station.4

f. Verify the mobile station sends a Protocol Capability Response Message to the base5station.6

g. Verify parameters MOB_FIRM_REV, MOB_MODEL, FEATURE_ID and7FEATURE_P_REV in the Protocol Capability Response Message contain the correct8values. MOB_FIRM_REV and MOB_MODEL are dependent upon the particular9mobile station. Record all FEATURE_P_REV and FEATURE_ID pairs.10

h. If Service Programming Lock (SPL_P_REV) is supported, perform the following:11

1) Verify the base station sends a Validation Request Message with BLOCK_ID =12’00000000’ (Verify SPC) and SPC = {current SPC in mobile station}.13

2) Verify the mobile station sends a Validation Response Message within 750 ms, and14with BLOCK_ID = ’00000000’ (Verify SPC) and RESULT_CODE = ’00000000’15(Accepted – Operation Successful).16

i. Verify the base station sends a Configuration Request Message to the mobile station.17

j. Verify the mobile station responds within 750 ms after receiving the Configuration18Request Message with the Configuration Response Message. Verify the Configuration19Response Message contains NUM_BLOCKS, BLOCK_ID, BLOCK_LEN and20PARAM_DATA.21

k. If the Electronic Key Exchange is NOT supported, go to step t.22

l. Verify the base station sends an MS Key Request Message to the mobile station.23

m. Verify the mobile station responds with the MS Key Response Message within 3024seconds, with RESULT_CODE = '00000000' (Accepted - Operation Successful).25

TSG-C42 Page 14-3

10/19/2001 C.S0031

n. Verify the base station sends the Key Generation Request Message to the mobile1station and that the mobile station responds with the Key Generation Response2Message within 30 seconds and the RESULT_CODE = '00000000' (Accepted -3Operation Successful).4

o. Verify the base station and the mobile station successfully perform SSD update5procedures and the mobile station sends the SSD Update Confirmation Order as6specified in Section 6 (Authentication Tests).7

p. Verify the base station sends the Re-Authenticate Request Message and the mobile8responds with the Re-Authenticate Response Message.9

q. At the base station verify Re-Authentication is successful and that the values of10RANDC and AUTHR in the Origination Message match the values computed at the11base station.12

r. Verify the base station enables Signaling Message Encryption and Voice Privacy.13

s. Verify the mobile station enables Signaling Message Encryption and Voice Privacy.14

t. Verify the base station sends a Download Request Message, with a new directory15number and NAM data, to the mobile station.16

u. Verify the mobile station sends a Download Response Message.17

v. Verify the contents of the Download Response Message and that RESULT_CODE =18'00000000' (Accepted- Operation Successful).19

Note: Data is stored in mobile station’s temporary memory NAM until a Commit Request20Message is received.21

w. Verify the base station sends a Commit Request Message to the mobile station.22

x. Verify the mobile station sends a Commit Response Message to the base station23within 10 seconds. Verify the RESULT_CODE = '0000 ' (Accepted- Operation24Successful). Verify the mobile station transfers its temporary memory to permanent25memory.26

y. End call at the mobile station and verify the base station sends a Release Order.27

z. Make a mobile station originated call after the successful completion of OTASP and28verify the call completes and that the Origination Message contains the new NAM29parameters.30

14.1.3 Minimum Standard31The OTASP request shall result in mobile station acquisition of the target system on which the32mobile station intends to be activated. The mobile station shall contain the new NAM33parameters.34

TSG-C42 Page 14-4

10/19/2001 C.S0031

14.2 OTAPA Service Request Processing for a Mobile Station in Mobile Station Idle State1

14.2.1 Definition2This test verifies a mobile station can respond to an OTAPA mobile terminated call and3download the parameters necessary for service on the network where the mobile station intends4to register.5

Traceability:IS-683-A; 3.2.2, 3.3, 4.2.2, 4.36


Note: This test should be performed with a mobile station that has previously been8provisioned.9


b. Configure the base station to initiate an OTAPA session by placing a mobile11terminated call indicating the OTAPA service option (0x12 or 0x13) in the General12Page Message. OTAPA service options are listed in Table 14.2.2-1.13

c. Verify that the mobile station sends a Page Response Message with14SERVICE_OPTION equal to the service option specified in the General Page15Message.16

d. Verify primary traffic data is established. The mobile station user interface should17not alert the user that an OTAPA session has been initiated.18

e. Verify the base station sends an OTAPA Request Message to the mobile station with19START_STOP = ’1’.20

f. Verify the mobile station sends an OTAPA Response Message to the base station21within 750 ms with RESULT_CODE = ’00000000’ (Accepted – Operation Successful).22

g. If NAM_LOCK_IND = ’1’ in the OTAPA Response Message, perform the following:23

1) Verify the RAND_OTAPA field is present in the OTAPA Response Message.24

2) Verify the base station sends a Validation Request Message with25BLOCK_ID = ’00000010’ (Validate SPASM) and a SPASM Parameter Block present to26the mobile station.27

3) Verify the mobile station sends a Validation Response Message to the28base station within 750 ms, and with BLOCK_ID = ’00000010’ (Validate SPASM) and29RESULT_CODE = ’00000000’ (Accepted – Operation Successful).30

h. Verify the base station sends a Protocol Capability Request Message to the mobile31station.32

i. Verify the mobile station sends a Protocol Capability Response Message to the base33station within 750 ms.34

j. Verify the parameters MOB_FIRM_REV, MOB_MODEL, FEATURE_ID and35FEATURE_P_REV in the Protocol Capability Response Message contain the correct36values. MOB_FIRM_REV and MOB_MODEL are dependent upon the particular37mobile station. Record all FEATURE_P_REV and FEATURE_ID pairs.38

TSG-C42 Page 14-5

10/19/2001 C.S0031

k. Verify that FEATURE_ID = ’00000100’ for Over-The-Air Parameter Administration1(OTAPA_P_REV) with FEATURE_P_REV = ’00000001’ is present in the Protocol2Capability Response Message.3

l. If Service Programming Lock (SPL_P_REV) is supported, perform the following:4

1) Verify the base station sends a Validation Request Message with5BLOCK_ID = ’00000000’ (Verify SPC) and SPC = {current SPC in mobile station}.6

2) Verify the mobile station sends a Validation Response Message within7750 mswith BLOCK_ID = ’00000000’ (Verify SPC) and RESULT_CODE = ’00000000’8(Accepted – Operation Successful).9

3) Verify the base station sends a Validation Request Message with10BLOCK_ID = ’00000001’ (Change SPC) and SPC = {a new SPC}.11

4) Verify the mobile station sends a Validation Response Message within12750 ms, and with BLOCK_ID = ’00000001’ (Change SPC) and RESULT_CODE =13’00000000’ (Accepted – Operation Successful).14

m. Verify the base station sends a Configuration Request Message to the mobile station.15

n. Verify the mobile station responds within 750 ms after receiving the Configuration16Request Message with the Configuration Response Message. Verify the Configuration17Response Message contains NUM_BLOCKS, BLOCK_ID, BLOCK_LEN and18PARAM_DATA.19

o. If Key Exchange (A_KEY_P_REV) is supported, perform the following:20

1) Verify the base station sends an MS Key Request Message to the mobile21station.22

2) Verify the mobile station responds with the MS Key Response Message23within 30 seconds, and the RESULT_CODE = '00000000' (Accepted – Operation24Successful).25

3) Verify the base station sends the Key Generation Request Message to the26mobile station.27

4) Verify the mobile station responds with the Key Generation Response28Message within 30 seconds, and the RESULT_CODE = '00000000' (Accepted –29Operation Successful).30

5) Verify the base station and the mobile station successfully perform SSD31update procedures and the mobile station sends the SSD Update Confirmation Order32as specified in Section 6 (Authentication Tests).33

6) Verify the base station sends the Re-Authenticate Request Message and34the mobile responds with the Re-Authenticate Response Message within 750 ms.35

7) At the base station verify Re-Authentication is successful and that the36values of RANDC and AUTHR in the Origination Message match the values37computed at the base station.38

TSG-C42 Page 14-6

10/19/2001 C.S0031

8) Verify the base station enables Signaling Message Encryption and Voice1Privacy.2

9) Verify the mobile station enables Signaling Message Encryption and3Voice Privacy.4

p. If NAM Download (DATA_P_REV) is supported, perform the following:5

1) Verify the base station sends a Data Download Request to the mobile6station.7

2) Verify the mobile station sends a Data Download Response Message8within 750 ms.9

3) Verify the contents of the Data Download Response Message,10RESULT_CODE = '00000000' (Accepted- Operation Successful).11

Note: Data is stored in mobile station temporary memory NAM until a Commit Request12Message is received.13

q. Verify the base station sends a Commit Request Message to the mobile station.14

r. Verify the mobile station sends a Commit Response Message to the base station15within 10 seconds. Verify the RESULT_CODE = '00000000' (Accepted - Operation16Successful). Verify the mobile station transfers its temporary memory to permanent17memory.18

s. Verify the base station sends an OTAPA Request Message to the mobile station with19START_STOP = ’0’.20

t. Verify the mobile station sends an OTAPA Response Message to the base station21within 750 ms, and with RESULT_CODE = ’00000000’ (Accepted – Operation22Successful) and NAM_LOCK_IND = ’0’.23

u. Verify the base station sends a Release Order, Extended Release Message or24Extended Release Mini Message to the mobile station.25

v. Make a mobile station originated call after the successful completion of the OTAPA26session and verify the call completes and that the Origination Message contains the27new NAM parameters.28

14.2.3 Minimum Standard29The network-initiated OTAPA session shall result in the mobile station responding to a General30Page Message and exchanging parameters on a traffic channel. The mobile station shall contain31the new NAM parameters.32

14.3 OTAPA Service Request Processing for a Mobile Station in Conversation Substate33

14.3.1 Definition34This test verifies a mobile station can respond to a network-initiated OTAPA session while in the35Conversation Substate and properly respond to OTA-specific messaging.36

TSG-C42 Page 14-7

10/19/2001 C.S0031

Traceability:1

IS683A 3.2.2, 3.3, 4.2.2, 4.32




b. Setup a mobile station originated call. Verify user data in both directions.7

c. While the mobile station is in the Conversation Substate, configure the base station8to initiate on OTAPA session. The mobile station user interface should not alert the9user that an OTAPA session has been initiated.10

d. Verify the base station sends an OTAPA Request Message to the mobile station with11START_STOP = ’1’.12

e. Verify the mobile station sends an OTAPA Response Message to the base station13within 750 ms, and the RESULT_CODE = ’00000000’ (Accepted – Operation14Successful).15

f. If NAM_LOCK_IND = ’1’ in the OTAPA Response Message, perform the following:16




g. Verify the base station sends a Protocol Capability Request Message to the mobile24station.25

h. Verify the mobile station sends a Protocol Capability Response Message to the base26station within 750 ms.27

i. Verify the base station sends an OTAPA Request Message to the mobile station with28START_STOP = ’0’.29

j. Verify the mobile station sends an OTAPA Response Message to the base station30within 750 ms, and with RESULT_CODE = ’00000000’ (Accepted – Operation31successful) and NAM_LOCK_IND = ’0’.32

k. Verify user data in both directions.33

l. End call at the mobile station.34

m. Setup a mobile station originated call after the successful completion of the OTAPA35session and the original call.36


TSG-C42 Page 14-8

10/19/2001 C.S0031

14.3.3 Minimum Standard1The network-initiated OTAPA session shall result in the mobile station responding to an OTAPA2Request Message while already in the Conversation Substate and exchanging parameters on a3traffic channel. The mobile station shall respond to the Protocol Capability Request Message.4

14.4 OTAPA Service Request Processing Interrupted by User Action5

14.4.1 Definition6This test verifies a mobile station will terminate an OTAPA session and originate emergency and7non-emergency calls when directed by the user.8

Traceability:9

IS683A 3.2.2, 3.3, 3.4, 4.2.2, 4.310




b. Configure the base station to initiate an OTAPA session by placing a mobile15terminated call indicating the OTAPA service option in the General Page Message.16OTAPA service options are listed in Table 14.2.2-1.17

c. Verify the mobile station sends a Page Response Message with SERVICE_OPTION18equal to the service option specified in the General Page Message.19



f. Verify the mobile station sends an OTAPA Response Message to the base station24within 750 ms, and the RESULT_CODE = ’00000000’ (Accepted – Operation25Successful).26

g. If NAM_LOCK_IND = ’1’ in the OTAPA Response Message, perform the following:27





TSG-C42 Page 14-9

10/19/2001 C.S0031


j. Setup an emergency call from the mobile station (911 in the United States) while the3OTAPA session is active.4

k. Verify the mobile station sends a Release Order to the base station to release the5OTAPA call prior to proceeding with the origination procedure.6

l. Verify the mobile station sends an Origination Message to the base station.7

m. Verify the emergency call is routed to the Public Service Answering Point (PSAP) or8equivalent emulation unit, or the non-emergency call is routed to the land party.9


o. End call at the mobile station.11

p. Repeat steps b through n using a non-emergency call to a land party in step j.12

14.4.3 Minimum Standard13The mobile station shall end the OTAPA session and send a Release Order to the base station14before sending an Origination Message. Emergency and non-emergency calls shall be routed to15the appropriate destination.16

17

TSG-C42 Page 14-10

10/19/2001 C.S0031

No text1

TSG-C42 Page 15-1

10/19/2001 C.S0031

15 SYSTEM SELECTION FOR PREFERRED ROAMING1Table 15-1 lists system selection for preferred roaming tests.2

Table 15-1 SSPR Tests3

Test No. Title

15.1 OTASP Service Provisioning For System Selection and Preferred Roaming

15.2 Non-Acquisition of a System on Negative PRL

15.3 Emergency Call On a System that is Negative on PRL or SID List

15.4 OTASP For System Selection and Preferred Roaming - Oversize PRL

15.5 OTAPA Service Provisioning for System Selection and Preferred Roaming for aMobile Station in Mobile Station Idle State

15.1 OTASP Service Provisioning For System Selection and Preferred Roaming4

15.1.1 Definition5This test verifies a mobile station can generate an OTASP Service Request to download the PRL6to a mobile station and that it is stored in semi-permanent memory, or in accordance with7customer specific requirements. The size of the PRL downloaded to the mobile station shall be8either 4096 octets or MAX_PR_LIST_SIZE octets, whichever is smaller.9

Traceability: TIA/EIA/IS-683-A; 3.5.1.2, 3.5.1.6, 3.5.1.910



b. Setup an OTASP call with the appropriate activation code. Refer to Table 15.1.2-1.13

c. Verify the mobile station acquires the appropriate system using the activation code14as the dialed digits. Refer to Table 15.1.2-1.15

d. Verify that the call is established.16


f. Verify base station sends a Protocol Capability Request Message to the mobile18station.19

20

TSG-C42 Page 15-2

10/19/2001 C.S0031

1Figure 15.1.2-1 Functional Setup for Testing System Selection and Preferred Roaming2

3

Table 15.1.2-1 Activation Code Assignments4

Selected System Activation Code

800 MHz A-BAND *22800

800 MHz B-BAND *22801

1.9 GHz A Block *22802

1.9 GHz B Block *22803

1.9 GHz C Block *22804

1.9 GHz D Block *22805

1.9 GHz E Block *22806

1.9 GHz F Block *22807

Reserved *22808 -*22899

Note: 228 = key pad alpha characters: ACT56

g. Verify the mobile station sends a Protocol Capability Response Message to the base7station within 750ms.8

h. Verify MOB_FIRM_REV, MOB_MODEL, FEATURE_ID and FEATURE_P_REV in the9Protocol Capability Response Message contain the correct values.10

i. Record FEATURE_P_REV and FEATURE_ID for NAM Download (DATA_P_REV) and11Key Exchange (A_KEY_P_REV).12

Note: MOB_FIRM_REV and MOB_MODEL are global to the mobile station and are13permanent.14

j. If Service Programming Lock (SPL_P_REV) is supported, perform the following:15


TSG-C42 Page 15-3

10/19/2001 C.S0031

2) Verify the mobile station sends a Validation Response Message within 750 ms,1and with BLOCK_ID = ’00000000’ (Verify SPC) and RESULT_CODE = ’00000000’2(Accepted – Operation Successful).3

4

k. Verify the base station sends a SSPR Configuration Request Message to the mobile5station requesting the PRL Dimensions Parameter Block6

l. Verify the mobile station responds within 750 ms after receiving the SSPR7Configuration Request Message with the SSPR Configuration Response Message.8

m. Verify the SSPR Configuration Response Message contains BLOCK_ID, BLOCK_LEN9and PARAM_DATA. Observe the MAX_PR_LIST_SIZE reported by the mobile station.10

n. Verify the base station sends a SSPR Download Request Message to the mobile11station using an appropriately sized PRL.12

o. Verify the mobile station sends a SSPR Download Response Message within 750ms.13

p. Verify the contents of the SSPR Download Response Message.14

q. Verify that RESULT_CODE = '00000000' (Accepted - Operation Successful).15

r. Verify the SEGMENT_OFFSET and SEGMENT_SIZE are consistent with the PRL16storage capability of the mobile station.17

s. Verify the base station sends a Commit Request Message to the mobile station.18

t. Verify the mobile station sends a Commit Response Message to the base station19within 10 seconds.20

u. Verify the RESULT_CODE = '0000' (Accepted - Operation Successful).21

v. Verify the mobile station transfers its new PR_LIST to permanent memory.22

w. End the call at the mobile station and verify the base station sends a Release Order.23

x. Make a mobile station originated call after the successful download of the PRL and24verify the mobile station acquires the selected system that is designated in the25Roaming List.26

15.1.3 Minimum Standard27The OTASP, SSPR PRL download shall be successful and the PRL content shall be correctly28stored in the mobile station permanent memory, PRL.29

15.2 Non-Acquisition of a System on Negative Preferred Roaming List (PRL)30

15.2.1 Definition31The purpose of this test is to demonstrate that a mobile station containing a negative entry32in its PRL (negative SID/NID list) does not register and does not monitor the paging33channel on that CDMA system.34

TSG-C42 Page 15-4

10/19/2001 C.S0031

Traceability: TIA/EIA/IS-683-A; 3.5.1.2, 3.5.1.6, 3.5.1.91


a. Connect the mobile station and the base station as shown in Figure 15.1.2-1.3

b. Program the mobile station’s PRL with multiple entries of SID, NID pairs in the4positive PRL and a single entry in the negative PRL, which corresponds to the (SID,5NID) of the base station. This (SID, NID) pair is subsequently referred to as (SID,6NID) NEG .7

c. Enable power-on registration. Disable all other forms of registration.8

d. Ensure the base station does not broadcast a Global Service Redirection Message,9which would prevent the mobile station from acquiring this base station system.10

e. Power on the mobile station and monitor it for a sufficient amount of time to acquire11CDMA system.12

f. Verify the mobile station does not send any Registration Messages during this time.13Verify the mobile station indicates a no-service condition.14

Note: Depending on the band classes supported, it may take some time for the mobile station15to attempt acquisition of all possible frequency blocks in all band classes. The mobile16station should be monitored until a full cycle of acquisition attempts has been17completed.18

g. Attempt to initiate a non-emergency call.19


• The mobile station shall not register on the (SID, NID) NEG system.21

• The mobile station shall indicate a no service condition.22

15.3 Emergency Call On a System that is Negative on PRL or SID List23

15.3.1 Definition24The purpose of this test is to demonstrate that a mobile station which contains a negative entry in25its Preferred Roaming List (PRL) or Negative SID List, can setup an emergency call on that26negatively listed system.27

Traceability: IS683-A; 3.5, TIA/EIA-5328



b. Program the mobile station so that the base station SID/NID is locked out. This31(SID, NID) pair is subsequently referred to as (SID, NID) NEG.32

c. Enable power-on registration. Disable all other forms of registration.33

d. Ensure the base station does not broadcast a Global Service Redirection Message,34which would prevent the mobile station from acquiring this base station system.35

TSG-C42 Page 15-5

10/19/2001 C.S0031

e. Power on the mobile station, and monitor it for a sufficient period of time to permit1it to acquire the CDMA system (typically 30 seconds). Verify the mobile station does2not send any Registration Messages during this time. Verify the mobile station3indicates a NO-SERVICE condition.4

NOTE: Depending on the band classes supported, it may take some time for the mobile station5to attempt acquisition of all possible frequency blocks in all band classes. The mobile6station should be monitored until a full cycle of acquisition attempts has been7completed.8

f. Setup an emergency call from the mobile station (911 in the United States). Verify9the mobile station generates an Origination Message to the (SID, NID) NEG base10station. Verify the emergency call is routed to the Public Service Answering Point11(PSAP) or equivalent emulation unit.12

g. End the emergency call from the mobile station.13


a. Prior to placing an emergency call, the mobile station shall not register on the15(SID, NID)NEG system.16

b. After placing an emergency call:17

• The emergency call shall be setup on (SID, NID) NEG system and shall be18successful.19

• The emergency call shall be routed to the appropriate PSAP or20corresponding PSAP emulation unit.21

15.4 OTASP For System Selection and Preferred Roaming - Oversize PRL22

15.4.1 Definition23This test verifies that the PRL resident in a handset shall not be replaced if a new PRL of illegal24size is downloaded.25

Traceability: TIA/EIA/IS-683-A; 3.5.1.2, 3.5.1.6, 3.5.1.9 Annex C26


a. Connect the base station and the mobile station as shown in Figure 15.1.2-128

b. Setup an OTASP call with the appropriate activation code. Refer to Table 15.1.2-129

c. Verify the mobile station acquires the appropriate system using the activation code30as the dialed digits. Refer to Table 15.1.2-1.31

d. Verify for CDMA 800 the Channel Assignment Message is BAND_CLASS = '00000'32and for CDMA 1900 the Channel Assignment Message is BAND_CLASS = '00001'.33

e. Verify the call completes.34

f. Verify the base station sends a Protocol Capability Request Message to the mobile35station.36

TSG-C42 Page 15-6

10/19/2001 C.S0031

g. Verify the mobile station sends a Protocol Capability Response Message to the base1station within 750ms.2

h Verify that MOB_FIRM_REV, MOB_MODEL, FEATURE_ID and FEATURE_P_REV in3the Protocol Capability Response Message contain the correct values.4MOB_FIRM_REV and MOB_MODEL are global to the mobile station and are5permanent.6

i. Record FEATURE_P_REV and FEATURE_ID for NAM Download (DATA_P_REV) and7Key Exchange (A_KEY_P_REV).8

j. If Service Programming Lock (SPL_P_REV) is supported, perform the following:9


2) Verify the mobile station sends a Validation Response Message within 750 ms, and12with BLOCK_ID = ’00000000’ (Verify SPC) and RESULT_CODE = ’00000000’13(Accepted – Operation Successful).14

k. Verify the base station sends a SSPR Configuration Request Message to the mobile15station.16

l. Verify the mobile station responds within 750 ms after receiving the SSPR17Configuration Request Message with the SSPR Configuration Response Message.18

m. Verify the SSPR Configuration Response Message contains BLOCK_ID, BLOCK_LEN19and PARAM_DATA.20

n. Verify the base station sends a SSPR Download Request to the mobile station.21

o. Verify the mobile station sends a SSPR Download Response Message.22

p. Verify contents of the SSPR Download Response Message.23

q. Verify RESULT_CODE = ’00001000’ (Rejected – Preferred roaming list length24mismatch).25

r. Verify SEGMENT_OFFSET and SEGMENT_SIZE are larger than the PRL storage26capability of the mobile station.27

s. Verify the base station sends a Commit Request Message to the mobile station.28

t. Verify the mobile station sends a Commit Response Message to the base station.29

u. Verify RESULT_CODE = '00000001' (Rejected - Unknown reason).30

v. Verify the mobile station does not transfer its new PR_LIST to semi-permanent31memory.32

w. End call at the mobile station and verify the base station sends a Release Order.33

15.4.3 Minimum Standard34The mobile station shall respond to the Download Request Message by setting the35RESULT_CODE = ’00001000’ (Rejected – Preferred roaming list length mismatch) in the36Download Response Message. The mobile station shall retain its original PRL.37

TSG-C42 Page 15-7

10/19/2001 C.S0031

15.5 OTAPA Service Provisioning for System Selection and Preferred Roaming for a1Mobile Station in Mobile Station Idle State2

15.5.1 Definition3This test verifies a mobile station can respond to an OTAPA mobile terminated call, download a4PRL and correctly store the list in its semi-permanent memory. The size of the PRL downloaded5to the mobile station shall be 4096 octets or MAX_PR_LIST_SIZE octets, whichever is smaller.6

Traceability:7

IS683A 3.2.2 3.3 4.2.2 4.38




b. Configure the base station to initiate an OTAPA session by placing a mobile13terminated call indicating the OTAPA service option (0x12 or 0x13) in the General14Page Message.15

16

c. Verify the mobile station sends a Page Response Message with SERVICE_OPTION17equal to the service option specified in the General Page Message.18



f. Verify the mobile station sends an OTAPA Response Message to the base station23within 750 ms, and RESULT_CODE = ’00000000’ (Accepted – Operation Successful).24

g. If NAM_LOCK_IND = ’1’ in the OTAPA Response Message, perform the following25steps:26


2) Verify the base station sends a Validation Request Message with28BLOCK_ID = ’00000010’ (Validate SPASM) and a SPASM Parameter Block to the29mobile station.30




TSG-C42 Page 15-8

10/19/2001 C.S0031

j. Verify parameters MOB_FIRM_REV, MOB_MODEL, FEATURE_ID and1FEATURE_P_REV in the Protocol Capability Response Message contain the correct2values. MOB_FIRM_REV and MOB_MODEL are dependent upon the particular3mobile station. Record all FEATURE_P_REV and FEATURE_ID pairs.4

k. Verify FEATURE_ID = ’00000100’ for Over-The-Air Parameter Administration5(OTAPA_P_REV) with FEATURE_P_REV = ’00000001’ exists in the Protocol Capability6Response Message.7

l. Verify the base station sends a SSPR Configuration Request Message to the mobile8station requesting the PRL Dimensions Parameter Block.9

m. Verify the mobile station responds within 750 ms after receiving the SSPR10Configuration Request Message with the SSPR Configuration Response Message.11

n. Verify the SSPR Configuration Response Message contains NUM_BLOCKS,12BLOCK_ID, BLOCK_LEN and PARAM_DATA. Observe the MAX_PR_LIST_SIZE13reported by the mobile station.14

o. Verify the base station sends a SSPR Download Request to the mobile station using15an appropriately sized PRL.16

p. Verify the mobile station sends a SSPR Download Response Message within 750 ms.17

q. Verify contents of the SSPR Download Response Message. Verify RESULT_CODE =18'00000000' (Accepted - Operation Successful). Verify SEGMENT_OFFSET and19SEGMENT_SIZE are consistent with the PRL storage capability of the mobile station.20

Note: Data is stored in mobile station temporary memory until a Commit Request Message is21received.22

r. Verify the base station sends a Commit Request Message to the mobile station.23

s. Verify the mobile station sends a Commit Response Message to the base station24within 10 seconds. Verify the RESULT_CODE = '00000000' (Accepted - Operation25Successful).26

t. Verify the mobile station transfers the new roaming list to its permanent memory.27

u. Verify the base station sends an OTAPA Request Message to the mobile station with28START_STOP = ’0’.29

v. Verify the mobile station sends an OTAPA Response Message to the base station30within 750 ms, and with RESULT_CODE = ’00000000’ (Accepted – Operation31successful) and NAM_LOCK_IND = ’0’.32

w. Verify the base station sends a Release Order, Extended Release Message or33Extended Release Mini Message to the mobile station.34

x. Make a mobile station originated call after the successful download of the PRL and35verify the mobile station acquires the selected system designated in the Roaming36List.37

TSG-C42 Page 15-9

10/19/2001 C.S0031

15.5.3 Minimum Standard1The network-initiated OTAPA session shall result in the mobile station responding to a General2Page Message and downloading a new PRL. The mobile station shall contain the new list.3

TSG-C42 Page 16-1

10/19/2001 C.S0031

16 MESSAGE DRIVEN INDICATORS1Table 16-1 lists message driven indicator tests.2

Table 16-1 Message Driven Indicator Tests3

Test No. Title

16.1 Enhanced Roaming Indicator

16.1 Enhanced Roaming Indicator4

16.1.1 Definition5The mobile station can display an indicator that allows the network to indicate to the subscriber6the roaming condition. This test can be run with any type of registration enabled. The mobile7station must send a Registration Message. The base station Registration Accepted Order must8have ORDQ = ’00000101’ and ROAM_INDI = set to a value defined per [17].9

Traceability[4]; 2.7.1.3.2.1, 3.7.4.5, [17]; 8.110



14Figure 16.1.2-1 Functional Setup for Testing Enhanced Roaming Indicator15

16


c. Verify the mobile station sends a Registration Message.18

d. Verify the base station sends a Registration Accepted Order with ORDQ = ’00000101’19and ROAM_INDI = {a value defined in table 8.1-1 from [17]}.20

16.1.3 Minimum Standard21Verify mobile station displays appropriate Roam Indicator as defined in TSB-58-A Table 8.1-1.22

23

TSG-C42 Page 16-2

10/19/2001 C.S0031

No text1

TSG-C42 Page 17-1

10/19/2001 C.S0031

1

17 FORWARD COMPATIBILITY TESTS2Table 17-1 lists message driven indicator tests.3

Table 17-1 Forward Compatibility Tests4

Test No. Title

17.1 Sync Channel

17.2 Paging Channel

17.3 Traffic Channel

5

These tests verify that when a mobile station operates in a future system where P_REV is6greater than MOB_P_REV and new fields or new messages are added, the mobile station shall7continue to work correctly and have no forward compatibility problem. The term ‘base station’8used in this section refers to a base station or base station simulator that is capable of adding9arbitrary new messages and additional parameter fields to the existing supported P_REV10messages for purposes of forward compatibility testing.11

17.1 Sync Channel12

17.1.1 Definition13This test verifies that the mobile station ignores any additional fields at the end of the Sync14Channel Message and ignores any message types that do not exist in the protocol revision15supported by the mobile station (MOB_P_REV).16

Traceability: (See [4] );172.6.1.3: Sync Channel Acquisition Substate183.7: Sync Channel Message19

20



b. Instruct the base station to set the message length of the Sync Channel Message greater23than the maximum length for the protocol revision that is specified by P_REV and add24additional fields at the end of the message.25


d. Initiate a mobile station terminated voice call.27

e. Verify audio on both directions.28

f. End the call.29


TSG-C42 Page 17-2

10/19/2001 C.S0031

h. Instruct the base station to alternately send the Sync Channel Message and another1type of message on the Sync Channel (e.g. MSG_TYPE = ‘11111111’) where both2messages start at the superframe boundary.3

i. Repeat steps c through f.45

6Figure 17.1.2-1 Functional Setup for Testing Forward Compatibility7

17.1.3 Minimum Requirements8The mobile station shall ignore any additional fields at the end of messages and ignore any9message types that do not exist in the protocol revision supported by the mobile station on the10Sync Channel. The mobile station shall be able to complete a call.11

12

17.2 Paging Channel13

17.2.1 Definition14This test verifies that the mobile station ignores any additional fields at the end of messages on15the Paging Channel and ignores/rejects any message types that do not exist in the protocol16revision supported by the mobile station (MOB_P_REV).17

Traceability: (See [4] );182.6.2: Mobile Station Idle State192.6.3: System Access State20

21



b. Instruct the base station to set the message length of any one of the Paging Channel24overhead messages to a value greater than the maximum length for the protocol25revision that is specified by P_REV and to add additional fields at the end of the26message.27


TSG-C42 Page 17-3

10/19/2001 C.S0031

d. Initiate a mobile station terminated voice call.1

e. Verify audio in both directions.2

f. End the call.3

g. Instruct the base station to send a new Paging Channel overhead message (e.g.4MSG_TYPE= ‘11111111’) in addition to other existing Paging Channel overhead5messages.6

h. Repeat steps d through f.7

i. Instruct the base station to send a mobile-directed message (e.g. the Status Request8Message) on the Paging Channel addressed to a different mobile station. Ensure the9message length is greater than the maximum length for the protocol revision specified10by P_REV and that additional fields are added at the end of the message.11

j. Verify the mobile station ignores the message that is addressed to the other mobile12station.13

k. Repeat the steps d through f.14

l. Instruct the base station to send a mobile directed message (e.g. the Status Request15Message) on the Paging Channel addressed to a different mobile station. Ensure the16message length is less than the maximum length for the protocol revision specified by17P_ REV but greater than 6 octets in length.18

m. Verify the mobile station ignores the message that is addressed to the other mobile19station.20

n. Repeat the steps d through f.21

o. Instruct the base station to send a mobile directed message (e.g. the Status Request22Message) on the Paging Channel to the mobile station under test. Ensure the message23length is greater than the maximum length for the protocol revision specified by P_REV.24

p. Verify the mobile station ignores the message and either sends a correct response to the25base station or sends a Mobile Station Reject Order.26

q. Repeat the steps d through f.27

17.2.3 Minimum Requirements28The mobile station shall ignore any additional fields at the end of overhead messages and29ignore/reject any message types that do not exist in the protocol revision supported by the mobile30station on the Paging Channel. The mobile station shall be able to complete a call.31

32

17.3 Traffic Channel33

17.3.1 Definition34This test verifies the mobile station does not drop the call when any of the following conditions35exist:36

TSG-C42 Page 17-4

10/19/2001 C.S0031

- The mobile station receives a message that contains additional fields that do not1exist in the protocol revision supported by the mobile station (MOB_P_REV) while on2the traffic channel.3

- The mobile station receives any message whose message type does not exist in the4protocol revision supported by the mobile station (MOB_P_REV) while on the traffic5channel.6

Traceability: (See [4] );72.6.4: Mobile Station Control on the Traffic Channel State8

9




c. Initiate a mobile station voice call.13

d. Verify audio in both directions.14

e. Instruct the base station to send an existing message (e.g. the In-traffic System15Parameter Message or General/Universal Handoff Direction Message) with the message16length greater than the maximum length for the protocol revision specified by P_REV17and additional fields at the end of the message.18

f. Verify the mobile station ignores or reject the message.19

g. Verify the call does not drop.20

h. Instruct the base station to send a message (e.g. MSG_TYPE= ‘11111111’) that does not21exist in the protocol revision supported by the mobile station (MOB_P_REV).22

i. Verify the mobile station ignores or reject the message.23

j. Verify the call does not drop.24

k. Release the call.25

17.3.3 Minimum Requirements26The call shall not drop if the mobile station either receives a message on the traffic channel that27has additional fields that do not exist in the protocol revision supported by the mobile station or28the mobile station receives any message whose message type does not exist in the protocol29revision supported by the mobile station.30

3132

TSG-C42 Page 17-5

10/19/2001 C.S0031

No Text1

TSG-C42 Page A-1

10/19/2001 C.S0031

ANNEX A: POWER RATIOS FOR COMMON AND TRAFFIC CHANNELS1Annex A provides the proper power ratios to perform a test when the power ratios are not2specified in the test. The tables below specify power ratios for the Pilot Channel, the Sync3Channel, the Paging Channel, the Fundamental Channels, Dedicated Control Channel, the4Supplemental Code Channels and the Supplemental Channels. The traffic channel power ratios5are specified to achieve 1% FER under AWGN channel conditions. All power ratios are valid for6Band Classes 0 through 9. Whenever the power ratios are specified in the test, those power ratios7should be used in lieu of power ratios provided in this Annex.8

Table A-1 Power Ratios for Common Channels9

Parameter Units Value

or

cI

EPilot dB -7

or

c

I

ESync dB -16

or

c

I

EPaging dB -12


Paging Data Rate bps 9600

10

Table A-2 Test Parameters for Forward Fundamental Channel11(Radio Configurations 1,3 and 4)12


Îor/Ioc dB -1

or

cI

EPilot dB -7

or

cI

ETraffic(RC1)

dB -15.6

or

cI

ETraffic(RC3)

dB -16.2

or

cI

ETraffic(RC4)

dB -15.4


Data Rate bps 9600

13

TSG-C42 Page A-2

10/19/2001 C.S0031

Table A-3 Test Parameters for Forward Fundamental Channel1(Radio Configurations 2 and 5)2


Îor/Ioc dB -1

or

cI

EPilot dB -7

or

cI

ETraffic(RC2)

dB -12.3

or

cI

ETraffic(RC5)

dB -13.8


Data Rate bps 14400

3

Table A-4 Test Parameters for Forward Dedicated Control Channel4(Radio Configurations 3 and 4)5


Îor/Ioc dB -1

or

cI

EPilot dB -7

or

cI

ETraffic(RC3)

dB -16.2

or

cI

ETraffic(RC4)

dB -15.4


Data Rate bps 9600

6

Table A-5 Test Parameters for Forward Dedicated Control Channel7(Radio Configurations 5)8


Îor/Ioc dB -1

or

cI

EPilot dB -7

or

cI

ETraffic dB -13.8


TSG-C42 Page A-3

10/19/2001 C.S0031

Data Rate bps 14400

1

Table A-6 Test Parameters for Forward Supplemental Code Channel2(Radio Configurations 1)3


Îor/Ioc dB -1

or

cI

ESCCH dB -16.1

or

cI

ETraffic dB -12


Data Rate bps 9600

4

TSG-C42 Page A-4

10/19/2001 C.S0031

Table A-7 Test Parameters for Forward Supplemental Code Channel (Radio1Configurations 2)2


Îor/Ioc dB -1

or

cI

ESCCH dB -13.0

or

cI

ETraffic dB -12


Data Rate bps 14400

3

Table A-8 Test Parameters for Forward Supplemental Channel with 100% Frame Activity4in AWGN with Convolutional Coding (for Radio Configurations 3, 4)5

Parameter Units Values

Îor/Ioc dB -1

or

cI

EalSupplement

(RC3)

dB -13.0 -9.7 -6.6 -3.2

or

cI

EalSupplement

(RC4)

dB -12.6 -9.3 -6.0 -2.8

or

cI

ETraffic dB -7

Data Rate bps 19200 38400 76800 153600

6

Table A-9 Test Parameters for Forward Supplemental Channel with 100% Frame Activity7in AWGN with Convolutional Coding (for Radio Configuration 5)8

Parameter Units Values

Îor/Ioc dB -1

or

cI

EalSupplement dB -10.9 -7.9 -4.6 -1.4

or

cI

ETraffic dB -7

Data Rate bps 28800 57600 115200 230400

910

TSG-C42 Page A-5

10/19/2001 C.S0031

No text.1

TSG-C42 Page B-1

10/19/2001 C.S0031

ANNEX B: TABLES OF LOGGING COUNTERS1

Table B-1 FCH Transmission Counters for Multiplex Option 0x12

Counter Name Description Logging Test #

MUX1_REV_FCH_1 9600 bps, MuxPDU Type 1 Header = ‘0’ or nulltraffic MuxPDU

1.0, 2.0

MUX1_REV_FCH_2 9600 bps, MuxPDU Type 1 Header = ‘1000’ 1.0, 2.0




MUX1_REV_FCH_6 4800 bps, MuxPDU Type 1 or null trafficMuxPDU

1.0, 2.0

MUX1_REV_FCH_7 2400, bps MuxPDU Type 1 or null trafficMuxPDU

1.0, 2.0

MUX1_REV_FCH_8 1200, bps MuxPDU Type 1 or null trafficMuxPDU

1.0, 2.0

MUX1_REV_FCH_9 reserved N/A







MUX1_REV_FCH_5_ms MuxPDU Type 4 1.0, 2.0

Table B-2 FCH Reception Counters for Multiplex Option 0x13


MUX1_FOR_FCH_1 9600 bps, MuxPDU Type 1 Header = ‘0’ or nulltraffic MuxPDU

1.0, 2.0

MUX1_FOR_FCH_2 9600 bps, MuxPDU Type 1 Header = ‘1000’ 1.0, 2.0




MUX1_FOR_FCH_6 4800 bps, MuxPDU Type 1 or null trafficMuxPDU

1.0, 2.0


1.0, 2.0


1.0, 2.0

TSG-C42 Page B-2

10/19/2001 C.S0031

MUX1_FOR_FCH_9 9600 bps, Physical Layer frame with insufficientPhysical Layer frame quality

1.0, 2.0

MUX1_FOR_FCH_10 Insufficient Physical Layer frame quality 1.0, 2.0





MUX1_FOR_FCH_15 Reserved N/A

MUX1_FOR_FCH_5_ms MuxPDU Type 4 1.0, 2.0

1

TSG-C42 Page B-3

10/19/2001 C.S0031

Table B-3 FCH Transmission Counters for Multiplex Option 0x21



1.0, 2.0











1.0, 2.0









1.0, 2.0






1.0, 2.0


MUX2_REV_FCH_26 Reserved N/A

MUX2_REV_FCH_27 Reserved N/A

MUX2_REV_FCH_5_ms MuxPDU Type 4 1.0, 2.0

2

TSG-C42 Page B-4

10/19/2001 C.S0031

Table B-4 FCH Reception Counters for Multiplex Option 0x21



1.0, 2.0











1.0, 2.0









1.0, 2.0






1.0, 2.0


MUX2_FOR_FCH_26 Insufficient Physical Layer frame quality 1.0, 2.0

MUX2_FOR_FCH_27 Reserved N/A

MUX2_FOR_FCH_5_ms MuxPDU Type 4 1.0, 2.0

2

TSG-C42 Page B-5

10/19/2001 C.S0031

Table B-5 DCCH Transmission Counters for Multiplex Option 0x11


MUX1_REV_DCCH_1 9600 bps, MuxPDU Type 1 Header = ‘0’ 1.0, 3.0





MUX1_REV_DCCH_6 Reserved N/A









MUX1_REV_DCCH_15 Null MuxPDU 1.0, 3.0

MUX1_REV_DCCH_5_ms MuxPDU Type 4 1.0, 3.0

2

TSG-C42 Page B-6

10/19/2001 C.S0031

Table B-6 DCCH Reception Counters for Multiplex Option 0x11


MUX1_FOR_DCCH_1 9600 bps, MuxPDU Type 1 Header = ‘0’ 1.0, 3.0





MUX1_FOR_DCCH_6 Reserved N/A




MUX1_FOR_DCCH_10 Insufficient Physical Layer frame quality 1.0, 3.0





MUX1_FOR_DCCH_15 Null MuxPDU 1.0, 3.0

MUX1_FOR_DCCH_5_ms MuxPDU Type 4 1.0, 3.0

2

TSG-C42 Page B-7

10/19/2001 C.S0031

Table B-7 DCCH Transmission Counters for Multiplex Option 0x21




























MUX2_REV_DCCH_27 Null MuxPDU 1.0, 3.0

MUX2_REV_DCCH_5_ms MuxPDU Type 4 1.0, 3.0

2

TSG-C42 Page B-8

10/19/2001 C.S0031

Table B-8 DCCH Reception Counters for Multiplex Option 0x21



























MUX2_FOR_DCCH_26 Insufficient Physical Layer frame quality 1.0, 3.0

MUX2_FOR_DCCH_27 Null Physical Layer frame 1.0, 3.0

MUX2_FOR_DCCH_5_ms MuxPDU Type 4 1.0, 3.0

2

TSG-C42 Page B-9

10/19/2001 C.S0031

Table B-9 SCCH Transmission Counters1


SCCH1_REV_P 9600 bps, MuxPDU Type 1 Header = ‘0’ or14400 bps, MuxPDU Type 2 Header = ‘0’

1.0, 4.0

SCCH1_REV_S 9600 bps, MuxPDU Type 1 Header = ‘1111’ or14400 bps, MuxPDU Type 2 Header = ‘10111

1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0

2

TSG-C42 Page B-10

10/19/2001 C.S0031

Table B-10 SCCH Reception Counters1


SCCH1_FOR_P 9600 bps, MuxPDU Type 1 Header = ‘0’ or14400 bps, MuxPDU Type 2 Header = ‘0’

1.0, 4.0

SCCH1_FOR_S 9600 bps, MuxPDU Type 1 Header = ‘1111’ or14400 bps, MuxPDU Type 2 Header = ‘10111

1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0


1.0, 4.0

2

TSG-C42 Page B-11

10/19/2001 C.S0031

Table B-11 SCH Transmission Counters1


SCH1_REV_1X 9600 bps or 14400 bps (1x SCH rate) 1.0, 5.0




SCH1_REV_16X 153600 bps (16x SCH rate) 1.0, 5.0

SCH1_REV_LTU number of LTUs delivered to the Physical Layer 1.0, 5.0

SCH1_REV_LTUOK Reserved N/A





SCH2_REV_16X 153600 bps (16x SCH rate) 1.0, 5.0

SCH2_REV_LTU number of LTUs delivered to the Physical Layer 1.0, 5.0

SCH2_REV_LTUOK Reserved N/A

2

Table B-12 SCH Reception Counters3


SCH1_FOR_1X 9600 bps or 14400 bps (1x SCH rate) 1.0, 5.0




SCH1_FOR_16X 153600 bps (16x SCH rate) 1.0, 5.0

SCH1_FOR_LTU Number of LTUs received from the Physical Layer 1.0, 5.0

SCH1_FOR_LTUOK Number of LTUs received from the Physical Layerwith a correct CRC

1.0, 5.0





SCH2_FOR_16X 153600 bps (16x SCH rate) 1.0, 5.0

SCH2_FOR_LTU Number of LTUs received from the Physical Layer 1.0, 5.0

SCH2_FOR_LTUOK Number of LTUs received from the Physical Layerwith a correct CRC

1.0, 5.0

45

TSG-C42 Page B-12

10/19/2001 C.S0031

No text1

TSG-C42 Page D-1

10/19/2001 C.S0031

ANNEX C: TTY/TDD TEST EXAMPLES1Note: The following ASCII characters are not supported by the Baudot TTY standard and2should not be used to verify conformance: @ # % ^ & * < >Example character text:3THE QUICK BROWN FOX JUMPS OVER A LAZY DOG. 12345678904ABCDEFGHIJKLMNOPQRSTUVWXYZ -$’,!:(“)=?+./;TTY_text.txt test file:5TTY_text.txt:6

BEGINNING OF TEST FILE71111111111222222222233333333334444444444555555555566666666667777777777888THE QUICK BROWN FOX JUMPS OVER A LAZY DOG.91234567890 ABCDEFGHIJKLMNOPQRSTUVWXYZ -$',!:(")=?+./;10=N((MI-IDDM'JEC $3F$,F1 8T:VY"RZ87OY"165S(M VP294!T+FE5J(UOIO4JK9SeeA!T71153+3.AVO4;;C/V$L$DD.89YE U .ZK6-HLZK-L ,"N19,3=1K R,TV;L;F"59 MR(80/=A!F12$,?," )N"RRU/IP$HZ"YSCU(R4;)WRL5BW24ANTAXW$IFP8LSN$SZ(FA3X1,PQ3E-TDXYP8913E?!5I1$FBF6'2/E0W"P?;L 57!(2RD3/OT?D?C=CD7T5'J9 "?X5VZ2 2II U=2CV)7"/4G214;01 H6.W=8'K6(-HN?-PF?32:Z0D5I" 2QNHC9MB(:47S6L'7 X92S" AS(8N L+GKX;GPPX15IN/243YSHURW=N/9PRC1R/WNM'L2B. D,DN-K,FGW":Z'8T IY505I +,LDQTAF4 6 PF F16.S'QHP/=/$(VWBKLNY'4TY: LO Y5T::-R;1Q=DO2 )YU,57 " QMM;PL'NXJ20FG4)F FS517M,!8DQ41,D?G"W98G=12HL))"+,IKL1U"WI,$!9)=EZ.Z?HGWHZRP:'4C))"46QS'/H:LLQW18HG" !,=$RE(O"QCJXK=F3WW'JK-9-9B'-?VNF(NY REH2KTF G?D!PX6'I.?U,O6E$.U5I0'19'-?S$,ZU!K!"M ES7;J5CK!J43MB$-A18U 8;"IQN:427)9D8F,3NQQQ8A3I3 V9!NKTP:KE20,AT5PPVD4.GT5Y/OW75M"A E58,2C44:33K,$-D7!9WNEJ04V6RWC G2G5ESNCBYHS=Q45F21

.QOF$))SK9=7J5RE1P8-N?-N.DIY3))1EH(0D7 ?TJG:D6HWDH =:W!?248=T6S+08'$8(4K22UXJN0/AYGCNUQO'LHKS0W- E,O($HR:2DC.EE7(CH-YF5G/Q(EPR3D3)CCM6GU.9F2OM7YFL23104FLCYLO "LP55T07.:W6/IU.QU?/W=TFUTPR:L1+L!J2/E)QG1UVF881N=,8V3+QJMZ(FR24E":V-+$-BV90RXK W6SA"Y36D2-!3R3( 7E;'?HC$!")NJ)K?U0 6=:9J,!,(JQ(?Y-Q2XZ)25'6K22L2FKKL0E=J ?ZP9W LE5WR RV TN420X=/!7(G0IQM==+$X8.8K+J$S32$X!PZV3Y3I26QTQQA7T4IY= 9NK6BYKT:.UQ$P84'R7'"VAU9 ( P?7HM1?Y5T)E:9WF!FF1(2GH,).ZB/+H27$,/6ELJR0Z1AZG$U A4(7"(H!3Y+JF8C?6M'N'WQ=;FY- ?2167.A0H89W 'DN/'U20G:3K+282C5C?.'NRT+:C7PX7C5NWCGHTUH)'75PM?:+I4A, Q(ZNC,)XL4+NR72LSI25L9Z3!$5X0T/298 FQ=D- S!3B'?0!MNAABDUY2TKMT"40S$RPY( U4($AQ: FF?7$UUPS=49SKC(UVZ9SW3IV309?Z(NAQ$.=?R/6 GZJ9'(3'NNIH6D7:= +F2UYTW5D)I9(UDQ8?E=C(8H$I1Q3'KU$!X)!W31+U;6B4;+9E1W-$'11-ZP?I7IU5UJYP$/"$NU:'ALW9$D,C6J0I 561F41SD0GC"N5MSD' FP329'1832GS=LWWN GDD--65D"!C;0EPSK)8H+=EOX7K3H -L12TEZ83D5W$=R!9$Q9,.0,93WC33C()(B??EGU$/RIH/90H'"!29HIILF'$6S('ZCA)RE9T90F3VHQ 1I43Q6HZ8"CJ+=AJ5-BY$34WA2(W?:TI(FPCG9JTD5TFF/0!'KJ",I,"4$;55 G.N3HRGB0A"83.CN"84)JG3ABKQ77HU235

-OY?MJ7!9R=T518Y+RR4TGY/: I9MMT9KF.2C,MEVK R,D='WSALLC/7 U9WL-WPLKN:+ARW36):D!(:'H:I?H'1N(6-80V7;XB4"KJD'T)EI$ :PIS203(?KUG(Z7/ J9OZ9Z--C1W:C=TY437: "+3AF"JWB+,9UVA,7F)R6A"Y"I!,IC596G!O5! JAHP?0,X?K-LB'KHV E.$P0:K5'QVGB38CNA)'/MSJOSWMU5U 3=I 27Z-E0YTOS5031+P99LIT0=86K-2V21JS61(G/!AE=46!OJDP0"39+4V6CLKW' KL-S,Y?KHA8+6F+Y0$!U=;=8VXH26!8K."'K7!J'(N="ZKCZH:N'C:9BG7E0IH40C+L8VSK24 DJD:TNI6; N$Q1C5C2 IP(!E=TJMF?3D9E1/M88,V7C/FSVEYTY+MZ Y=R88)W41ZZKKJJ 39ZIYEZH") +?=YYGKF1D1X$$IWR;+6MYSO;"!R) 9ZRR="KDYF1A4AU?4- "GRAW426;A-O.N.VW? .2??=MHY0;X1=H9WEHWD8;:C6 :JO/7?!.EZ4JL/ !FNXL;AJAWB; CWUWLF43O1N4 U;V(9M8"O$S6)FER=14I4I,HIEM5'916:FN.Y?5"=LC0EQN7I,?D;3(=2'/=L8H(!I944:2.ST 1.2A:,DE;745VU7UA-$Z?F8PGE'INKD7 G?PUQ79N610W:Y;E63X7)4-.V?T0))W7H45YBKRT/DL-S5WZ'OH;HK21'/Y7 ,8Z0 1UMD64-S;7WIZT="'4/2''XE7CQ.:2LUK)C"=0XEN46

TSG-C42 Page D-2

10/19/2001 C.S0031

" :HZV(M'/4ZQ16$6WO1A-'D5)VMA3E+? $D0WF271)68 WE?GJ OSA8T=!R=7 -UQT7JU+G1FI-?.9DD44'IH!=$$WKE)2:,!ID:DJ !+.(AW=O/V!RPR 85?D04'6L"UZE43O8O0T6 'ERP2O:58B.7HYM?QTCO"3U; 5+.0TWJA3ID"T!,1)?H2S1VFBW/E 6 LCN,.GH:KI:99$1RW(H0P31)+H83 G8! H0 V).6'QK7VFIE-/S)MA(+'D7" TTI.,-'NO46Q32.NY19,KDFD!TLB-FIMA46R7$L Y$H=:TN8$4VD4L,8?QL "=PF8UJQN=E8XM;AAOMXLYG9-CWEH (YOYS,KVK0WU=Z'R54/0FFBT 2FG!!!J 093RMNA=EX.:6:1AK08KY0(DJN:JV6:L=4:J5N:9)"WW4Z,4:DCPSO$W6V!G8$9 INIB!.U/;? J00VEY0+)G"0S5LK6!A3EMUPF,JQ"LY',34E?TK$2G=M4 J/9=!AKT7"S"=23A6TT4VTK:1)CP.8NJ7.UHVDN5VW)EI/1CA "NCJ FIQ"$KXN!G73DO),!0JY"$OPH58CW(S6=I7JNNOA DZX" 2-3(0;TP5A1PEW(=J:PZKGQ6CK.WFJYZ1J OY69P?5I SL2T0N CZ9IKN,8X:+FG-R=CEY7(8 $3;ER Q(D0. O3/Y8,Y,1M;X0W85!!.4"!OT FC+X7WGV$:K/L:10"I;(ZA'.Y$)E9"AZ),XJM)WTZ(I'4;N6H'NTW(AEEI+, C80B ,F(D8KH; H;Q0-Z1 2H6M=11LI('F P=XD?-NDZOO!9J !?0S=J?1L4+F+HBUX6S:9DOYC 38O(YZZ8LAP+10IL?" :R YJ12AWLNZ/+ "!BSK-4X1W:2UM!(9U?F"97V.BT3YCNJDIG6I4 6)!4M17,E4L2(T-Y$,H:E ;QZ13V,6-H8,TLEIB19+('$DD)P-(46920DX$(J754+(G:/SZC3FY)7ZKI;RY1)954O''XOTBK!5F14'P ?J1906IHVS'0(.8(I',S-Q9(A )0?J-E4LF0X!H9 23?KR$DFYLHLB5(?)/U)T3$I.)I;15KLY6?')V65Z4ZDVOYF4X:G. 3))46!OEG(KZ8BP24L'W"(-Y)JJHAXG=DR!-)UZ8MKDQ=!"616WK?R/;IO42?LZ2U9 H0'E.K88,0S,KTA?YRKMJH-C$WJ?(0=4 /"A(; "H."H"OPSR2=9ZRV173XRG)HLEQ6IDX TJ7$23EF4M=O QQ?- /N6J7:L13HPJ: CR6A--/F9J,4=3LQVC4W-H-2CL18; (5?VU:L,+6ELDO4TLKBU JTC=$9$C3CN$6 P0'4E35-: .LO $'5.HD3N41$;72)+KOU.3197(A Y, TY .-VLM8Y3'?I7FRR-H+I5818G4"8KC.:29HQ"Y8FR'5!"GTE)NAMEK(H4RPJE3E20BU: B$MM:NL36VE)'9AA?I$+$GDZUD=D3/Y6M 1P) ?5XFK$(YO!8'(9=E'D.2R ?:F'"Y5821!C8,7TR5E-K-J9UK" X -"/PF9NL0DL,9C94OEWT 8$C-A(05)0X=.5(CHDF22

23THE QUICK BROWN FOX JUMPS OVER A LAZY DOG.241234567890 ABCDEFGHIJKLMNOPQRSTUVWXYZ -$',!:(")=?+./;2511111111112222222222333333333344444444445555555555666666666677777777778826

END OF TEST FILE2728

TSG-C42 Page D-1

10/19/2001 C.S0031

ANNEX D: INFORMATION RECORDS1The following table lists the Information Records that may be requested in a Status Request2Message.3

4Information Record

RequestedRECORD_TYPE (binary) QUAL_INFO_TYPE

Call Mode 00000111 00000000

Terminal Information 00001000 00000010

Roaming Information 00001001 00000010

Security Status 00001010 00000000

IMSI 00001100 00000000

ESN 00001101 00000000

Band Class Information 00001110 00000000

Power Class Information 00001111 00000010

Operating ModeInformation

00010000 00000001

Service Option Information 00010001 00000010

Multiplex OptionInformation

00010010 00000010

Service Configuration 00010011 00000000

Power Control Information 00010111 00000000

IMSI_M 00011000 00000000

IMSI_T 00011001 00000000

Capability Information 00011010 00000000

Channel ConfigurationCapability Information

00011100 00000000

Extended Multiplex Option 00011101 00000000

56

TSG-C42 Page D-2

10/19/2001 C.S0031

No text12

Documents

ARIB STD-T53-C.S0031-0 Signaling Conformance Tests for ... · 1 Original Specification 2 This standard, ARIB-T53-C.S0031-0, was prepared by T53WG of Association of Radio Industries