1

2
3GPP2 C.S0044-A v1.0 July 27, 2007

Interoperability Specification for cdma2000 Air Interface Revision A

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 secretariat@3gpp2.org. Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See www.3gpp2.org for more information.

1
1No text

3GPP2 C.S0044-A v1.0

13GPP2 C.S0044-A v1.0

1CONTENTS

2 FOREWORD................................................................................................................................xii 3 4 5 6 7 8
Introduction...............................................................................................................................xii Testing Objective .....................................................................................................................xii Execution Strategy....................................................................................................................xii Supplementary Terms and Definitions.....................................................................................xiii Tolerances.............................................................................................................................xxvii Document References..........................................................................................................xxviii

91 Miscellaneous Air Interface Tests................................................................................................1 10 1.1 Call Setup under Various PSIST Settings.............................................................................1 11 1.2 Registration Attempts with Different PSIST Settings.............................................................6 12 1.3 Short Message Service with Different PSIST Settings..........................................................7 13 1.4 Quick Paging Channel CCI....................................................................................................9 14 1.5 Mobile Station Response to Status Request Message........................................................11 15 1.6 SYNC Channel Support for Mobile Stations not capable of TD, or not capable of QPCH or 16 RC>2.........................................................................................................................................13 17 1.7 Sync Channel support for Mobile Stations not capable of TD, but capable of QPCH or 18 RC>2.........................................................................................................................................15 19 1.8 Sync Channel Support for Mobile Stations capable of TD and QPCH or RC>2 ................17 20 1.9 Hashing F-CCCH, F-CCCH slot..........................................................................................20 21 1.10 CDMA Channel Hashing on F-PCH for Mobile Stations not capable of QPCH or RC>2...21 22 1.11 CDMA Channel Hashing on F-PCH for Mobile Stations capable of QPCH or RC>2.........22 23 1.12 CDMA Channel Hashing on F-BCCH; Mobile Station not capable of either TD or QPCH 24 (RC>2).......................................................................................................................................23 25 1.13 CDMA Channel Hashing on F-BCCH; Mobile Station not capable of TD (STS) but capable 26 of QPCH (RC>2).......................................................................................................................25 27 1.14 CDMA Channel Hashing on F-BCCH; Mobile Station capable of both TD (STS) and QPCH 28 (RC>2).......................................................................................................................................26 29 1.15 F-CCCH SUPPORT..........................................................................................................28 30 1.16 Paging Indicator on the Quick Paging Channel.................................................................28 312 Basic Call Processing Tests.........................................................................................................1 32 2.1 Mobile Originated Voice Calls...............................................................................................1 33 2.2 Mobile Station Terminated Voice Calls..................................................................................3 34 2.3 Busy Tone.............................................................................................................................6 6
i

3GPP2 C.S0044-A v1.0

1 2.4 Mobile Station Origination Call with Inter Band Channel Assignment....................................7 2 2.5 Mobile Station Terminated Call with Inter Band Channel Assignment...................................8 3 2.6 DTMF....................................................................................................................................9 4 2.7 Slot Cycle Index...................................................................................................................10 5 2.8 Reverse Radio Link Failure.................................................................................................11 6 2.9 Channel Assignment from CDMA to Analog .......................................................................13 7 2.10 Network Busy....................................................................................................................14 8 2.11 Release Order on the Access Channel.............................................................................15 9 2.12 True IMSI Support, Land Party to Mobile Station Call, Matching MCC and IMSI_11_12, 10 True IMSI addressing supported by the base station and mobile station..................................16 11 2.13 True IMSI Support, Land Party to Mobile Station Call, Matching MCC and IMSI_11_12, 12 True IMSI addressing supported by the base station with MIN-based addressing supported by 13 the mobile station......................................................................................................................17 14 2.14 True IMSI Support, Land Party to Mobile Station Call, Matching MCC and IMSI_11_12, 15 True IMSI addressing not supported by the base station .........................................................18 16 2.15 True IMSI Support, Land Party to Mobile Station Call, Different MCC and IMSI_11_12. . .19 17 2.16 PACA Origination, User Terminates While Still In Queue..................................................20 18 2.17 PACA Origination, Idle Handoff While in Queue................................................................21 19 2.18 PACA Origination, Traffic Channel Becomes Available.....................................................22 20 2.19 PACA Origination, Features Interaction.............................................................................23 21 2.20 PACA Origination, Permanent Invocation..........................................................................24 22 2.21 PACA Origination, PACA Disabled for Mobile Station.......................................................25 23 2.22 Service Configuration and Negotiation without SYNC_ID.................................................26 24 2.23 Service Configuration and Negotiation with SYNC_ID......................................................30 25 2.24 Intra-Band Channel Assignment........................................................................................33 26 2.25 Silent-Retry........................................................................................................................34 27 2.26 MSID, MCC, and IMSI.......................................................................................................36 283 Handoff Tests...............................................................................................................................1 29 3.1 Soft Handoff with Dynamic Threshold...................................................................................1 30 3.2 Soft Handoff without Dynamic Threshold..............................................................................5 31 3.3 Hard Handoff Between Frequencies in the Same Band Class..............................................9 32 3.4 Hard Handoff from CDMA to Analog...................................................................................11 33 3.5 Soft Handoff in Fading.........................................................................................................12

ii

13GPP2 C.S0044-A v1.0 1 3.6 Hard Handoff in Fading.......................................................................................................16 2 3.7 Hard Handoff Between Different Band Classes...................................................................18 3 3.8 Hard Handoff with and without Return on Failure................................................................20 4 3.9 Search Window Size and Offset (Traffic State)...................................................................21 5 3.10 Search Window Size and Offset (Idle State).....................................................................30 6 3.11 Channel Assignment into Soft Handoff (CASHO)..............................................................37 7 3.12 Traffic Channel Preamble during Hard Handoff Between Frequencies in same band.......38 8 3.13 Hopping Pilot Beacon........................................................................................................40 9 3.14 Hard Handoff between Frequencies with Different Radio Configurations..........................42 10 3.15 Handoff on Same Frequency with Different Radio Configurations.....................................43 11 3.16 Hard Handoff while in the Waiting for Mobile Station Answer Substate.............................45 12 3.17 Mobile Assisted Inter-Frequency Hard Handoff (CDMA to CDMA)....................................47 13 3.18 Mobile Assisted Inter-Frequency Hard Handoff (CDMA to Analog)...................................49 14 3.19 Hard Handoff between Frequencies with Different Protocol Revisions..............................51 154 Power Control..............................................................................................................................1 16 4.1 Forward Traffic Channel Power Control ...............................................................................1 17 4.2 Fast Forward Power Control (FFPC).....................................................................................5 18 4.3 Lowest Rate Reverse Fundamental Channel Gating ..........................................................48 19 4.4 R-FCH Gating during Soft Handoff......................................................................................50 205 Registrations................................................................................................................................1 21 5.1 Power-Up Registration..........................................................................................................1 22 5.2 Power - Down Registration....................................................................................................3 23 5.3 Distance-Based Registration.................................................................................................5 24 5.4 Timer-Based Registration......................................................................................................8 25 5.5 Parameter-Change Registration............................................................................................9 26 5.6 Zone-Based Registration.....................................................................................................10 276 Authentication..............................................................................................................................1 28 6.1 Shared Secret Data (SSD) Initialized when A-Key is Changed.............................................1 29 6.2 Shared Secret Data Update..................................................................................................2 30 6.3 Mismatched A-Keys...............................................................................................................4 31 6.4 Activating Voice Privacy on Call Setup..................................................................................5 32 6.5 Activating Voice Privacy at the Mobile Station When a Call Is Active ...................................6

iii

3GPP2 C.S0044-A v1.0

1 6.6 Signaling Message Encryption on Forward Traffic Channel .................................................7 2 6.7 Signaling Message Encryption on Reverse Traffic Channel..................................................8 3 6.8 Hard Handoffs between Base Stations with Signaling Message Encryption Active.............10 4 6.9 Authentication upon Originations.........................................................................................11 5 6.10 Hard Handoff from CDMA to Analog with Signaling Message Encryption Active..............12 67 Service Redirection test cases.....................................................................................................1 7 7.1 Global Service Redirection between Band Classes...............................................................1 8 7.2 Global Service Redirection between CDMA and a Non-CDMA System................................2 9 7.3 Global Service Redirection between Channels in the Same Band Class..............................4 10 7.4 Service Redirection between Band Classes..........................................................................5 11 7.5 Service Redirection between CDMA and a Non-CDMA System...........................................7 12 7.6 Service Redirection between Channels in the Same Band Class.........................................8 13 7.7 Extended Global Service Redirection between Band Classes............................................10 14 7.8 Extended Global Service Redirection between CDMA and a Non-CDMA System..............11 15 7.9 Extended Global Service Redirection between Channels in the Same Band Class............13 168 Short Message Service................................................................................................................1 17 8.1 Mobile Station Terminated SMS Tests..................................................................................1 18 8.2 Mobile Station Originated SMS Tests....................................................................................8 19 8.3 Broadcast SMS Delivery on the Common Channel.............................................................14 20 8.4 Mobile Station Terminated Enhanced Messaging Services [EMS] Tests:...........................16 21 8.5 Mobile Station Originated Enhanced Messaging Services [EMS] Tests:.............................25 229 Subscriber Calling Features.........................................................................................................1 23 9.1 Call Forwarding Unconditional (CFU)....................................................................................1 24 9.2 Call Forwarding Busy (CFB)..................................................................................................1 25 9.3 Call Forwarding Default (CFD)..............................................................................................2 26 9.4 Call Forwarding No Answer (CFNA)......................................................................................3 27 9.5 Three-Way Calling.................................................................................................................4 28 9.6 Call Alerting...........................................................................................................................5 29 9.7 Calling Party Number for Mobile station Terminated Call Setup............................................6 30 9.8 Calling Party Number for Call Waiting...................................................................................7 31 9.9 Call Waiting...........................................................................................................................8 32 9.10 Voice Mail Message Waiting Notification from the Idle State...............................................9

iv

13GPP2 C.S0044-A v1.0 1 9.11 Voice Mail Message Waiting Notification from the Conversation State.............................10 2 9.12 Calling Party Name Presentation during Call Setup .........................................................11 3 9.13 Calling Name Presentation (CNAP) during Conversation State........................................12 4 9.14 Display Records sent in the Feature Notification Message...............................................13 5 9.15 Display Records Sent in the Flash With Information Message..........................................14 6 9.16 Display Records Sent in the Alert with Information Message............................................15 7 9.17 TTY/TDD...........................................................................................................................16 8 9.18 WLL Call Waiting Indicator Support...................................................................................18 9 9.19 Answer Holding.................................................................................................................20 10 9.20 User Selective Call Forwarding.........................................................................................22 1110 Asynchronous Data and Fax Services.......................................................................................1 12 10.1 Send/Receive Fax...............................................................................................................1 13 10.2 Upload/Download Binary File..............................................................................................3 14 10.3 Simultaneous Two-way File Transfer/Carrier Detect...........................................................4 15 10.4 Compound AT Command, Initialization and Connection Delay...........................................6 16 10.5 Escaping to Command Mode..............................................................................................7 17 10.6 Air Interface Data Compression..........................................................................................8 18 10.7 RLP Operation in a Poor RF Environment.........................................................................10 19 10.8 RLP Abort and TCP Retransmit Test.................................................................................11 20 10.9 Internet Control Message Protocol (ICMP) Requests/Replies...........................................13 21 10.10 Reflection of AT Command Parameters..........................................................................14 2211 Low Speed Packet Data ............................................................................................................1 23 11.1 Forward File Transfer..........................................................................................................1 24 11.2 Reverse File Transfer..........................................................................................................1 25 11.3 Bi-directional File Transfer...................................................................................................2 26 11.4 Mobile Station Packet Data Inactivity Timer........................................................................3 2712 Medium Speed Packet Data......................................................................................................1 28 12.1 Forward File Transfer with Fundamental and Supplemental Code Channels......................1 29 12.2 Forward File Transfer with Variable Supplemental Code Channels ...................................2 30 12.3 MSPD Call Setup, No Negotiation.......................................................................................3 31 12.4 MSPD Call Setup, Negotiation to a Different MSPD Service Option...................................4 32 12.5 MSPD Call Setup, Negotiation to LSPD..............................................................................5

3GPP2 C.S0044-A v1.0

1 12.6 MSPD Call Setup, Mobile Station Maximum Multiplex Option Less than Base Station 2 Maximum Multiplex Option..........................................................................................................7 3 12.7 MSPD Call Setup, Mobile station Maximum Multiplex Option Greater than Base Station 4 Maximum Multiplex Option..........................................................................................................8 5 12.8 Allocation/De-allocation of Supplemental Code Channels...................................................9 6 12.9 No Transmission on Supplemental Code Channels..........................................................11 7 12.10 Soft Handoff with Supplemental Code Channels.............................................................12 8 12.11 Adding Supplemental Code Channels during Soft Handoff.............................................13 9 12.12 Hard Handoff to an MSPD-Capable System...................................................................15 10 12.13 Bi-Directional File Transfers with Forward Supplemental Code Channels......................17 11 12.14 R Interface Flow Control...............................................................................................18 12 12.15 Dormant Timer.................................................................................................................19 13 12.16 Packet Zone ID................................................................................................................20 1413 High Speed Packet Data............................................................................................................1 15 13.1 Forward File Transfer..........................................................................................................1 16 13.2 Reverse File Transfer..........................................................................................................2 17 13.3 Bi-directional File Transfer...................................................................................................3 18 13.4 Service Option Control Message Processing......................................................................5 19 13.5 Changing Encoding Type on Supplemental Channel during Hard Handoff.........................7 20 13.6 Control Hold Mode Transitions..........................................................................................10 21 13.7 Soft Handoff of Fundamental Channel/Dedicated Control Channel and Supplemental 22 Channels...................................................................................................................................15 23 13.8 Soft Handoff of Fundamental Channel or Dedicated Control Channel only.......................18 24 13.9 Adding Supplemental Channels during Soft Handoff.........................................................20 25 13.10 Hard Handoff during Data Transfer.................................................................................21 26 13.11 Hard Handoff to a different Radio Configuration..............................................................23 27 13.12 Mobile Station Packet Data Inactivity Timer....................................................................25 28 13.13 Mobile Station and Base Station Operating in Different States.......................................26 29 13.14 RLP Operation in Rayleigh Fading Environment.............................................................29 30 13.15 Release Order Processing..............................................................................................30 31 13.16 Hysteresis Activation Timer.............................................................................................32 32 13.17 Hysteresis Timer.............................................................................................................33 3314 Over-The-Air Services................................................................................................................1

vi

13GPP2 C.S0044-A v1.0 1 14.1 OTASP Download Request Processing..............................................................................1 2 14.2 OTASP PUZL Download Request Processing....................................................................4 3 14.3 OTASP 3GPD Download Request Processing....................................................................6 4 14.4 OTASP SSPR Download Request Processing..................................................................10 5 14.5 OTASP For System Selection and Preferred Roaming - Oversize PRL............................12 6 14.6 OTAPA Download Request Processing............................................................................13 7 14.7 Call Origination during an OTAPA Download Session......................................................16 815 Position Determination Tests.....................................................................................................1 9 15.1 Position Determination Tests for GPS, AFLT and Hybrid....................................................1 1016 Concurrent Services...................................................................................................................1 11 16.1 Setup Mobile Station Originated Data Call while Voice Call or Teleservice Call is in 12 Progress .....................................................................................................................................1 13 16.2 Setup Mobile Station terminated Data Call while Voice Call or Teleservice Call is in 14 Progress .....................................................................................................................................5 15 16.3 Setup Mobile Station Originated Voice Call while Data Call or Teleservice Call is in 16 Progress .....................................................................................................................................7 17 16.4 Setup Mobile Station terminated Voice Call while Data Call or Teleservice Call is in 18 Progress ...................................................................................................................................10 19 16.5 Mobile Station Release of a Single Call While Voice and Data Calls are in Progress ......13 20 16.6 Base Station Release of a Single Call While Voice and Data Calls are in Progress .........15 21 16.7 Correct Handling of Call Control Signaling .......................................................................17 22 16.8 Analog Handoff Direction Message Terminates All Calls Except One...............................21 23 16.9 Release A Mobile Station in Concurrent Calls with a Release A Base Station Hands off to 24 Pre-Release A Base Station .....................................................................................................22 25 16.10 Release A Mobile Station Hands off between Release A Base Station with Change in 26 Concurrent Calls Support .........................................................................................................23 2717 Emergency Calls.......................................................................................................................1 28 17.1 Global Emergency Call Support When Mobile Station is in Idle State.................................1 29 17.2 Global Emergency Call Support When Mobile Station is in Voice Call................................1 30 17.3 Global Emergency Call Support When Mobile Station is in a Data Call .............................2 31 17.4 Emergency Call on a System that is Negative on PRL or SID List......................................3 32 17.5 Optional Emergency Calls...................................................................................................4 3318 HRPD.........................................................................................................................................1 34 18.1 HRPD Acquisition and Idle Mode Operation ......................................................................1

vii

1 1 2 3 4 5 6 7 8 10 11 12 13 14 15 16 17 18 19 20

3GPP2 C.S0044-A v1.0 HRPD Session Establishment ..................................................................................................1 HRPD Session Configuration and Management with Subnet change........................................2 AT Color Code and UATI24........................................................................................................3 HRPD Connection Setup...........................................................................................................3 AN Packet Data Inactivity Timer ...............................................................................................4 Forward File Transfer.................................................................................................................5 Reverse File Transfer.................................................................................................................7 Bidirectional File Transfer...........................................................................................................8

9 18.2 RLP Operation in Severely Degraded Channel ..................................................................8

Softer and Soft Handoff Active HRPD Mode...........................................................................9 HRPD Control Channel Monitoring and Overhead Message Updates ....................................11 Control Channel Rate ..............................................................................................................11 HRPD ConnectionDeny............................................................................................................12 HRPD Keep Alive Mechanism..................................................................................................13 Intra-band HRPD-HRPD System Re-Selection (Connected State)..........................................14 Inter-band HRPD-HRPD System Re-Selection (Connected State) .........................................15 Intra-band HRPD-HRPD System Re-selection (Idle State)......................................................15 Inter-band HRPD-HRPD System Re-selection (Idle State)......................................................16 HRPD Terminal Authentication ................................................................................................17 PPP Session in Adverse Conditions - Disconnect cable between AT and PC.........................18

21 18.3 Unicast ReverseRateLimit.................................................................................................19 22 18.4 HRPD Location Update Protocol Tests.............................................................................20 23 18.5 Idle State Channel Hashing...............................................................................................20 24 18.6 Inter-frequency Active Handoff..........................................................................................21 25 18.7 Typical HRPD Rev-A Session Configuration.....................................................................23 26 18.8 Multiple Reservations bound to one RLP..........................................................................24 27 18.9 Maximum Open Reservations, Activated RLP and MAC flows..........................................26 28 18.10 QoS Release upon PDSN initiated LCP termination.......................................................28 29 18.11 QoS Release upon AT Initiated PPP Termination...........................................................29 30 18.12 Access Persistence Vector..............................................................................................30 31 18.13 AT Data Over Signaling Message Transmission ............................................................31 32 18.14 AN Data Over Signaling Message Transmission.............................................................32

viii

13GPP2 C.S0044-A v1.0 1 18.15 Voice Origination in HRPD Idle Mode..............................................................................34 2 18.16 Voice Termination in HRPD Idle Mode............................................................................35 3 18.17 SMS Origination in HRPD Idle Mode...............................................................................36 4 18.18 SMS Termination in HRPD Idle Mode.............................................................................37 5 18.19 Voice Origination in HRPD Active Mode..........................................................................37 6 18.20 Voice Termination in HRPD Active Mode........................................................................39 7 18.21 SMS Origination in HRPD Active Mode...........................................................................40 8 18.22 SMS Termination in HRPD Active Mode.........................................................................41 9 18.23 Voice Origination in HRPD Dormant Mode......................................................................42 10 18.24 Voice Termination in HRPD Dormant Mode....................................................................43 11 18.25 SMS Origination in HRPD Dormant Mode.......................................................................44 12 18.26 SMS Termination in HRPD Dormant Mode.....................................................................45 13 18.27 Inter Revision Handoffs - Dormant HRPD Rev A to HRPD Rev 0...................................46 14 18.28 Inter Revision Handoffs - Active HRPD Rev A to HRPD Rev 0.......................................48 15 18.29 Inter Revision Handoffs Dormant HRPD Rev 0 to HRPD Rev A..................................49 16 18.30 Inter Revision Handoffs Active HRPD Rev 0 to HRPD Rev A......................................51 17 18.31 Inter Technology Switching Dormant HRPD to cdma2000 1x.....................................52 18 18.32 Inter Technology Switching Active HRPD to cdma2000 1x..........................................54 19 18.33 Inter Technology Switching Dormant cdma2000 1x to HRPD .....................................55 20 18.34 Inter RNC Dormant Hand-off (Rev A to Rev A)...............................................................56 21 18.35 Inter RNC Active Hand-off (Rev A to Rev A)...................................................................57 22 18.36 Inter RNC Dormant Hand-off (Rev A to Rev 0)................................................................58 23 18.37 Inter RNC Active Hand-off (Rev A to Rev 0)....................................................................59 24 18.38 Inter RNC Dormant Hand-off (Rev 0 to Rev A)................................................................60 25 18.39 Inter RNC Active Hand-off (Rev 0 to Rev A)....................................................................61 26 18.40 Inter-Band Active Hand-off..............................................................................................62 27 18.41 RLP Activation.................................................................................................................64 28 18.42 QoS Set Up.....................................................................................................................65 29 18.43 Successful negotiation of Enhanced Idle State Protocol ................................................68 30 18.44 Unsuccessful Enhanced Idle State Protocol due to AN rejection.....................................69 31 18.45 SlottedMode Attribute Negotiation for Enhanced Idle State Protocol...............................70 32 18.46 Channel Hashing during Enhanced Idle State Protocol Evenly Distributed Hashing....72

ix

3GPP2 C.S0044-A v1.0

1 18.47 Channel Hashing during Enhanced Idle State Protocol - Hashing to AN 2 Only.............73 2 18.48 QoS Signaling upon PPP resynchronization...................................................................74 3 18.49 AT behavior upon Rejection of Reservation Request by AN...........................................75 4 18.50 AT behavior upon Receiving ProfileType set to NULL.....................................................76 5 18.51 ReservationKKIdleStateFwd and ReservationKKIdleStateRev set to 0...........................77 6 18.52 ReservationKKIdleState set to 1......................................................................................79 7 18.53 ReservationKKIdleState set to 2......................................................................................81 8 18.54 DRC Supervision Failure.................................................................................................83 9 18.55 Soft Handoff during DRC Supervision Timeout State......................................................84 10 18.56 DRC Supervision with MultiUserPacketsEnabled............................................................85 11 18.57 DRCTranslationOffset Verification...................................................................................86 12 18.58 DSC and DRC compliance during Soft handoff...............................................................87 13 18.59 DRC Compliance During Softer Handoff.........................................................................88 14 18.60 MUP and Non Canonical SUP decoding by AT ..............................................................89 15 18.61 Enhanced Control Channel Short MAC Packet...............................................................90 16 18.62 Enhanced Access Channel Probe Transmission.............................................................92 17 18.63 RTC Interlace re-ordering with Subtype 3 RTCMAC.......................................................95 18 18.64 Configuration of non-default attributes for Subtype 3 RTCMAC......................................96 1919 Annex A - figures.......................................................................................................................1 2020 Annex B.....................................................................................................................................1 21 20.1 Annex B.1 Power Ratios for Common and Traffic Channels...............................................1 22 20.2 Annex B.2 CDMA Equations...............................................................................................5 23 20.3 Annex B.3 Message Parameter Values...............................................................................8 2421 Annex C - protocol capability response message Feature identifiers 25........................................................................................................................................................1 2622 Annex D Data Services Tests ...................................................................................................1 27 22.1 Data Services Annex A: References..................................................................................1 28 22.2 Data Services Annex B: Description of Compressible Test Data Files...............................1 29 22.3 Data Services Annex C: Standard ITU Fax Pages.............................................................1 30 22.4 Data Services Annex D: Test Files.....................................................................................2 3123 Annex E: TTY/TDD Test Examples............................................................................................1

13GPP2 C.S0044-A v1.0 1 2

FOREWORD
Introduction

3This specification defines air interface interoperability tests for CDMA/HRPD mobile 4stations/access terminals. It is applicable to P_REV_IN_USE equal to or less than seven and/or 5access terminals supporting revision A of [24] 6In this document, mobile station or access terminal (AT) refers to a subscriber terminal, 7handset, PDA, wireless local loop unit, or any other CDMA/HRPD subscriber terminal that 8communicates with the base station at the air interface. Base station or access network refers 9to the composite functionality of the base station and connected network elements. A cabled 10connection is typically used for the air interface connection between the mobile station and base 11station.

12

Testing Objective

13The objective of these tests is to demonstrate mobile station interoperability with base station 14equipment compliant to the cdma20001 family of standards. References to the applicable 15standard functionality are listed in the traceability section of each test case.

16

Execution Strategy

17All features supported by the base station, such as Signaling Message Encryption, 18Authentication, Voice Privacy, etc. should be enabled. 19All applicable tests should be executed for all supported Band Classes and Radio Configurations. 20The following general comments apply to all tests:

21 22 23 24 25 26 27 28 29 30 31 32 33 34

a. Whenever common channels and/or traffic channels are required to perform a test, and their power ratios are not specified in the test, the power ratios specified in Annex B should be used. Adjust the Orthogonal Channel Noise Simulator (OCNS) gain such that power ratios (Ec/Ior) of all specified forward channels add up to one. If OCNS is not available, the levels of code channels and attenuators should be adjusted to maintain proper test parameters. b. During handoff tests between sectors of the same cell, Channel 2 from the beta sector shall have a maximum relative offset of 1 s from Channel 1 of the alpha sector at the mobile station antenna connector. c. During soft and intersector handoff tests, the neighbor list of the base station in the test shall include PN offsets of the other base station in the test. unless otherwise specified: 0 <= Pi <= 511

d. Pilot PN sequence offsets are denoted by Pi (i=1, 2, 3...). The following are assumed

21 cdma2000 is the trademark for the technical nomenclature for certain specifications and 3standards of the Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of 4publication), cdma2000 is a registered trademark of the Telecommunications Industry 5Association (TIA-USA) in the United States. 6
xi

1 1 2 3 4 5 6 7 8 9 10 11
Pi not equal to Pj if i not equal to j Pi mod PILOT_INC = 0

3GPP2 C.S0044-A v1.0

e. Base stations should be configured for normal operation as specified in [2] unless otherwise specified in a specific test. f. Unless otherwise specified, the Reverse Traffic Channel should be operated at a sufficiently high Eb/No to ensure insignificant (for example, less than 1%) frame error rate (FER). g. Overhead message fields should be those required for normal operation of the base station unless otherwise specified in Annex B tables or in a specific test. h. Values of time limits and other constants should be as specified in Annex B. Supplementary Terms and Definitions

12 13AC - See Authentication Center. 14ACCOLC Access Overload Class 15Access Attempt - A sequence of one or more access probe sequences on the Access Channel 16containing the same message. See also Access Probe and Access Probe Sequence. 17Access Channel - A Reverse CDMA Channel used by mobile stations for communicating to the 18base station. The Access Channel is used for short signaling message exchanges such as call 19originations, responses to pages, and registrations. The Access Channel is a slotted random 20access channel. 21Access Channel Message - The information part of an access probe consisting of the message 22body, length field, and CRC. 23Access Channel Response Message - A message on the Access Channel generated to reply to 24a message received from the base station. 25Acknowledgment - A Layer 2 response by the mobile station or the base station confirming that 26a signaling message was received correctly. 27Action Time - The time at which the action implied by a message should take effect. 28Active Set - The set of pilots associated with the CDMA Channels containing Forward Traffic 29Channels assigned to a particular mobile station. 30Advanced Forward Link Trilateration (AFLT) - A geolocation technique that utilizes the mobile 31stations measured time-difference-of-arrival of radio signals from the base stations (and, 32possibly, other terrestrial measurements). 33A-key - A secret, 64-bit pattern stored in the mobile station and HLR/AC. It is used to 34generate/update the mobile stations Shared Secret Data. 35AMPS Advanced Mobile Phone Service 36AN- Access Network 37Assured Mode - Mode of delivery that guarantees (if a loss of channel is not declared) that a 38PDU will be delivered to the peer. A PDU sent in assured mode is retransmitted by the LAC 39sublayer, up to a maximum number of retransmissions, until the LAC entity at the sender receives 40an acknowledgement for the PDU. See also Confirmation of Delivery. 41AT 1. Attention (condition in modem control). 2. Access Terminal

xii

13GPP2 C.S0044-A v1.0

1Authentication - A procedure used by a base station to validate a mobile stations identity. 2Authentication Center (AC) - An entity that manages the authentication information related to 3the mobile station. 4Autonomous Registration - A method of registration in which the mobile station registers 5without an explicit command from the base station. 6AWGN - Additive White Gaussian Noise. 7Band Class - A set of frequency channels and a numbering scheme for these channels. 8Base Station - A fixed station used for communicating with mobile stations. In this document, the 9term base station refers to the entire cellular system infrastructure including transceiver 10equipment and Mobile Switching Center. 11bps - Bits per second. 12BS See base station. 13Candidate Frequency - The frequency for which the base station specifies a search set, when 14searching on other frequencies while performing mobile-assisted handoffs. 15Candidate Set - The set of pilots that have been received with sufficient strength by the mobile 16station to be successfully demodulated, but have not been placed in the Active Set by the base 17station. See also Active Set, Neighbor Set, and Remaining Set. 18CC Channel Configuration 19CCI Base station Configuration Change Indicator (sent on QPCH) 20CDMA - See Code Division Multiple Access. 21Candidate Frequency - The Candidate Frequency specified for a search of CDMA pilots. 22CDMA Channel - The set of channels transmitted between the base station and the mobile 23stations within a given CDMA frequency assignment. See also Forward CDMA Channel and 24Reverse CDMA Channel. 25CFNA Call Forwarding No Answer 26Chip - See PN Chip. 27CMT Cellular Messaging Teleservice 28CAN Calling Party Name 29CNAP Calling Name Presentation 30CNI Calling Number Identification 31Code Channel - A subchannel of a Forward CDMA Channel. A Forward CDMA Channel contains 3264 code channels. Code channel zero is assigned to the Forward pilot channel. Code channels 1 33through 7 may be assigned either to the Paging Channels or to the Traffic Channels. Code 34channel 32 may be assigned either to a Sync Channel or to a Traffic Channel. The remaining 35code channels may be assigned to Traffic Channels. 36Code Division Multiple Access (CDMA) - A technique for spread-spectrum multiple-access 37digital communications that creates channels through the use of unique code sequences. 38Configuration Change Indicator - A one-bit datum sent on the Quick Paging Channel. 39Appearance of the Configuration Change Indicator in the Quick Paging Channel serves to alert a 40slotted mode mobile station, operating in the idle state, that, after performing an idle handoff, it 41should monitor the Paging Channel, in order to determine if it should update its stored 42parameters.

xiii

3GPP2 C.S0044-A v1.0

1Confirmation of Delivery - A notification sent by the LAC sublayer to Layer 3 at the sender, 2when the LAC entity at the sender receives the acknowledgment for a specific PDU sent in 3assured mode. 4CPN Calling Party Number 5CPT Cellular Paging Teleservice 6CRC - See Cyclic Redundancy Code. 7Cyclic Redundancy Code (CRC) - A class of linear error detecting codes which generate parity 8check bits by finding the remainder of a polynomial division. 9dBm - A measure of power expressed in terms of its ratio to one milliwatt. 10Dedicated Control Channel - A portion of a Traffic Channel (Forward or Reverse) that carries a 11combination of user data, signaling, and power control information. 12Distance-Based Registration - An autonomous registration method in which the mobile station 13registers whenever it enters a cell whose distance from the cell in which the mobile station last 14registered exceeds a given threshold. 15DTMF - See Dual-Tone Multifrequency 16Dual-Tone Multifrequency (DTMF) - Signaling by the simultaneous transmission of two tones, 17one from a group of low frequencies and another from a group of high frequencies. Each group of 18frequencies consists of four frequencies. 19Eb - Average energy per information bit for the Sync Channel, Paging Channel, or Forward Traffic 20Channel at the mobile station antenna connector. 21Eb/No - Energy-per-bit-to noise-per-hertz ratio.

22Eb/Nt - The ratio of the combined received energy per bit to the effective noise power spectral
23density for the Sync Channel, Paging Channel, or Forward Traffic Channel at the mobile station 24antenna connector.

25Ec - Average energy per PN chip for the Forward pilot channel, Sync Channel, Paging Channel,
26Forward Traffic Channel, power control subchannel, or OCNS. 27Ec/Io - A notation used to represent a dimensionless ratio of the average power of some code28distinguished CDMA signal channel, typically a pilot, to the total power comprised of signal plus 29interference, within the signal bandwidth. It is usually expressed in dB units.

30Ec/Ior - The ratio of the average transmit energy per PN chip for the Forward pilot channel, Sync
31Channel, Paging Channel, Forward Traffic Channel, power control subchannel, or OCNS to the 32total transmit power spectral density. 33Erasure Indicator Bit (EIB)- A bit used in the Rate Set 2 Reverse Traffic Channel frame 34structure to indicate an erased Forward Fundamental Code Channel or Forward Dedicated 35Control Channel frame. 36ESN - Electronic Serial Number 37f-csch - Forward common signaling logical channel. 38f-dsch - Forward dedicated signaling logical channel. 39FER - Frame Error Rate of Forward Traffic Channel. The value of FER may be estimated by 40using Service Option 2, 9, 30, or 31 (see TIA/EIA-126-C). 41FFPC Fast Forward Power Control 42Flash - An indication sent on the CDMA Channel indicating that the receiver is to invoke special 43processing.

xiv

13GPP2 C.S0044-A v1.0

1Forward CDMA Channel - A CDMA Channel from a base station to mobile stations. The 2Forward CDMA Channel contains one or more code channels that are transmitted on a CDMA 3frequency assignment using a particular pilot PN offset. The code channels are associated with 4the Forward pilot channel, Sync Channel, Paging Channels, and Traffic Channels. The Forward 5CDMA Channel always carries a Forward pilot channel and may carry up to one Sync Channel, 6up to seven Paging Channels, and up to 63 Traffic Channels, as long as the total number of 7channels, including the Forward pilot channel, is no greater than 64. 8F-CCCH - Forward Common Control Channel 9Forward Dedicated Control Channel (F-DCCH) - A portion of a Forward Traffic Channel that 10can carry a combination of primary data, secondary data, signaling, and power control 11information. 12Forward Fundamental Channel (F-FCH) - A portion of a Forward Traffic Channel that can carry 13a combination of primary data, secondary data, signaling, and power control information. 14Forward Pilot Channel (F-PICH) - A non-data-bearing direct-sequence spread spectrum signal 15transmitted continuously by each CDMA base station. The Forward Pilot Channel allows a mobile 16station to acquire the timing of the Forward CDMA Channel, provides a phase reference for 17coherent demodulation, and provides a means for signal strength comparisons between base 18stations for determining when to handoff. Different base stations are identified by different pilot 19PN sequence time phases. See also Pilot PN Sequence, Pilot PN Sequence Offset. 20Forward Supplemental Channel (F-SCH) - An optional portion of a Forward Traffic Channel 21(Radio Configurations 3 and above) that operates in conjunction with a Fundamental Channel 22and or the Dedicated Control Channel in that Traffic Channel, and (optionally) with other 23Supplemental Channels to provide higher data rate services. 24Forward Supplemental Code Channel (F-SCCH) - An optional portion of a Forward Traffic 25Channel (Radio Configurations 1 and 2) that operates in conjunction with a Fundamental Channel 26in that Traffic Channel, and (optionally) with other Supplemental Code Channels to provide higher 27data rate services. 28Forward Traffic Channel - A code channel used to transport user and signaling traffic from a 29base station to a mobile station. 30FPC Forward Power Control 31Frame - A basic timing interval in the system. For the Access Channel and Paging Channel a 32frame is 20 ms long. For the Traffic Channel, the frame may be 20 ms or 5 ms long. For the Sync 33Channel, a frame is 26.666... ms long. 34Frame Offset - A time skewing of Traffic Channel frames from System Time in integer multiples 35of 1.25 ms. The maximum frame offset is 18.75 ms. 36FTP- File Transfer Protocol 37GHz - Gigahertz (109 Hertz). 38Global Positioning System (GPS) - A US government satellite system that provides location 39and time information to users. See Navstar GPS Space Segment / Navigation User Interfaces 40ICD-GPS-200 for specifications. 41Good Frames - Frames not classified as bad frames. See also Bad Frames. 42Good Message - A received message is declared a good message if it is received with a correct 43CRC. 44GPS - Global Positioning System 45Handoff - The act of transferring communication with a mobile station from one base station to 46another.

xv

3GPP2 C.S0044-A v1.0

1Hard Handoff - A handoff characterized by a temporary disconnection of the Traffic Channel. 2Hard handoffs occur when the mobile station is transferred between disjoint Active Sets, the 3CDMA frequency assignment changes, the frame offset changes, or the mobile station is directed 4from a CDMA Traffic Channel to an AMPS voice channel. See also Soft Handoff. 5Hash Function - A function used by the mobile station to select one out of N available resources. 6The hash function distributes the available resources uniformly among a random sample of 7mobile stations. 8Hopping Pilot Beacon - A pilot beacon that changes CDMA Frequency periodically to simulate 9multiple base stations operating on different frequencies. The transmission of the hopping pilot 10beacon is discontinuous on any CDMA Channel. 11HRPD High Rate Packet Data 12HSPD High Speed Packet Data 13Idle Handoff - The act of transferring reception of the Paging Channel from one base station to 14another, when the mobile station is in the Mobile Station Idle State. 15IMSI - See International Mobile Station Identity 16IMSI_M - MIN-based IMSI using the lower 10 digits to store the MIN. 17IMSI_O - Operational value of IMSI used by the mobile station for operation with the base station. 18IMSI_T - True IMSI not associated with MIN. This could be 15 digits or fewer. 19IMSI_T_S Supplement of MIN-based IMSI 20International Mobile Station Identity (IMSI) - A method of identifying stations in the land mobile 21service as specified in ITU-T Recommendation E.212. 22Io - The total received power spectral density, including signal and interference, as measured at 23the mobile station antenna connector. 24Ioc - The power spectral density of a band-limited white noise source (simulating interference from 25other cells) as measured at the mobile station antenna connector. 26Ior - The total transmit power spectral density of the Forward CDMA Channel at the base station 27antenna connector. 28or - The received power spectral density of the Forward CDMA Channel as measured at the 29mobile station antenna connector. 30ITU International Telecommunication Union 31IWF Inter-Working Function 32LAC Link Access Control 33Layering - A method of organization for communication protocols in which the transmitted or 34received information is transferred in pipeline fashion, within each station, in well-defined 35encapsulated data units between otherwise decoupled processing entities (layers). A layer is 36defined in terms of its communication protocol to a peer layer in another entity and the services it 37offers to the next higher layer in its own entity. 38Layer 1 - Layer 1 provides for the transmission and reception of radio signals between the base 39station and the mobile station. Also see Physical Layer. 40Layer 2 - Layer 2 provides for the correct transmission and reception of signaling messages, 41including partial duplicate detection. Layer 2 makes use of the services provided by Layer 1. 42Layer 3 - Layer 3 provides the control messaging for the cellular or PCS telephone system. Layer 433 originates and terminates signaling messages according to the semantics and timing of the

xvi

13GPP2 C.S0044-A v1.0

1communication protocol between the base station and the mobile station. Layer 3 makes use of 2the services provided by Layer 2. 3Long Code - A PN sequence with period (242) - 1 that is used for scrambling on the Forward 4CDMA Channel and spreading on the Reverse CDMA Channel. The long code uniquely identifies 5a mobile station on both the Reverse Traffic Channel and the Forward Traffic Channel. The long 6code provides limited privacy. The long code also separates multiple Access Channels on the 7same CDMA Channel. See also Public Long Code and Private Long Code. 8Long Code Mask - A 42-bit binary number that creates the unique identity of the long code. See 9also Public Long Code, Private Long Code, Public Long Code Mask, and Private Long Code 10Mask. 11LSPD Low Speed Packet Data 12MAC Medium Access Control 13MC Message Center 14MCC - See Mobile Country Code 15MCSB - See Message Control and Status Block 16MDR Medium Data Rate 17Mean Input Power - The total received calorimetric power measured in a specified bandwidth at 18the antenna connector, including all internal and external signal and noise sources. 19MHz - Megahertz (106 Hertz). 20MIN/MSIN - See Mobile Identification Number 21MNC - See Mobile Network Code 22MO Multiplex Option 23MOB_P_REV Protocol revision number supported by a mobile station 24Mobile Country Code (MCC) - A part of the E.212 IMSI identifying the home country. See ITU-T 25Recommendation E.212. 26Mobile Directory Number - A dialable directory number that is not necessarily the same as the 27mobile stations air interface identification, i.e., MIN, IMSI_M or IMSI_T. 28Mobile Identification Number (MIN) - The 34-bit number that is a digital representation of the 2910-digit number assigned to a mobile station. 30Mobile Network Code (MNC) - A part of the E.212 IMSI identifying the home network within the 31home country. See ITU-T Recommendation E.212. 32Mobile Station (MS) - A station that communicates with a base station while in motion or during 33halts at unspecified points. 34Mobile Station Identification Number (MSIN) - A part of the E.212 IMSI identifying the mobile 35station within its home network. See ITU-T Recommendation E.212. 36Mobile Station Originated Call - A call originating from a mobile station. 37Mobile Station Terminated Call - A call received by a mobile station (not to be confused with a 38disconnect or call release). 39MS Mobile Station 40MSC - See Mobile Switching Center 41MSIN - See Mobile Station Identification Number 42MSPD Medium Speed Packet Data

xvii

3GPP2 C.S0044-A v1.0

1Mobile Switching Center (MSC) - A configuration of equipment that provides radiotelephone 2service. Also called the Mobile Telephone Switching Office (MTSO). 3Multiplex Sublayer - One of the conceptual layers of the system that multiplexes and 4demultiplexes signaling traffic and various connected user traffic. 5MWI Message Waiting Indicator 6NAK- Negative Acknowledgement 7NAM - See Number Assignment Module 8National Mobile Station Identity (NMSI) - A part of the E.212 IMSI identifying the mobile station 9within its home country. The NMSI consists of the MNC and the MSIN. See ITU-T 10Recommendation E.212. 11NDSS - See Network Directed System Selection. 12Neighbor Set - The set of pilots associated with the CDMA Channels that are probable 13candidates for handoff. Normally, the Neighbor Set consists of the pilots associated with CDMA 14Channels that cover geographical areas near the mobile station. See also Active Set, Candidate 15Set, Remaining Set, and Private Neighbor Set. 16Network - A network is a subset of a cellular or PCS system, such as an area-wide cellular 17network, a private group of base stations, or a group of base stations set up to handle a special 18requirement. A network can be as small or as large as needed, as long as it is fully contained 19within a system. See also System. 20Network Directed System Selection (NDSS) - A feature that allows the mobile station to 21automatically register with a preferred system while roaming, or to be automatically directed by a 22service provider, typically the home service provider, to a suggested system, regardless of the 23frequency band class, cellular band, or PCS frequency block. 24Network Identification (NID) - A number that uniquely identifies a network within a cellular or 25PCS system. See also System Identification. 26NID - See Network Identification 27NMSI - See National Mobile Station Identity 28NNSCR Non-negotiable Service Configuration Record 29Non-Slotted Mode - An operation mode of the mobile station in which the mobile station 30continuously monitors the Paging Channel. 31ns - Nanosecond (10-9 second). 32Nt - The effective noise power spectral density at the mobile station antenna connector. 33NULL - Any value that is not in the specified range of a field. 34Number Assignment Module (NAM) - A set of MIN/IMSI-related parameters stored in the 35mobile station. 36OA&M Operation, Administration and Maintenance 37OCNS See Orthogonal Channel Noise Simulator

38OCNS Ec - Average energy per PN chip for the OCNS.

39 - The ratio of the average transmit energy per PN chip for the OCNS to the total transmit power 40spectral density. 41OLPC Outer Loop Power Control 42OOK On/Off keying

xviii

13GPP2 C.S0044-A v1.0

1Order - A type of message that contains control codes for either the mobile station or the base 2station. 3Orthogonal Channel Noise Simulator (OCNS) - A hardware mechanism used to simulate the 4users on the other orthogonal channels of a Forward CDMA Channel. 5Orthogonal Transmit Diversity (OTD) - An optional method of transmission of the Forward 6CDMA Channel that uses two antennas, each transmitting a fraction of the code symbols. It can 7be used to enhance performance in the presence of multipath fading radio propagation. 8OTAF Over-the-air Function 9OTAPA Over-the-air Parameter Administration 10OTASP Over-the-air Service Programming 11OTD - See Orthogonal Transmit Diversity 12OUNS Other User Noise Simulator Overhead Message - A message sent by the base station 13on the Paging Channel to communicate base-station-specific and system-wide information to 14mobile stations. 15P_REV Protocol revision level supported by a base station 16P_REV_IN_USE Protocol revision level currently in use by a mobile station 17PACA - Priority Access and Channel Assignment. See PACA Call. 18PACA Call - A priority mobile station originated call for which no traffic channel or voice channel 19was immediately available, and which has been queued for a priority access channel assignment. 20Packet - The unit of information exchanged between the service option applications of the base 21station and the mobile station. 22Paging - The act of seeking a mobile station when a call has been placed to that mobile station. 23Paging Channel - A code channel in a CDMA channel used for transmission of control 24information and pages from a base station to a mobile station. 25Paging Channel Slot - An 80 ms interval on the Paging Channel. Mobile stations operating in the 26slotted mode are assigned specific slots in which they monitor messages from the base station.

27Paging Ec - Average energy per PN chip for the Paging Channel

28 - The ratio of the average transmit energy per PN chip for the Paging Channel to the total 29transmit power spectral density. 30Paging Indicator - A one-bit datum sent on the Quick Paging Channel. Quick paging indicators 31are associated with mobile stations, in pairs, via a hashing algorithm. Appearance of both of its 32indicators in its assigned Quick Paging Channel slot serves to alert a slotted mode mobile station, 33operating in the idle state, that it should monitor the Paging Channel starting in the next slot. See 34also Quick Paging Channel. 35Parameter-Change Registration - A registration method in which the mobile station registers 36when certain of its stored parameters change. 37PCF Packet Control Function 38PCS - See Personal Communications Services 39PCS System - See Personal Communications Services System 40PDU - See Protocol Data Unit 41Personal Communications Services (PCS) - A family of mobile and portable radio 42communications services for individuals and businesses that may be integrated with a variety of

xix

3GPP2 C.S0044-A v1.0

1competing networks. Broadcasting is prohibited and fixed operations are to be ancillary to mobile 2operations. 3Personal Communication Services System - A configuration of equipment that provides PCS 4radiotelephone services 5Personal Communications Switching Center (PCSC) - See Mobile Switching Center (MSC) 6Physical Channel - A communication path between stations, described in terms of the RF 7characteristics such as coding, power control policies, etc. 8Physical Layer - The part of the communication protocol between the mobile station and the 9base station that is responsible for the transmission and reception of data. The physical layer in 10the transmitting station is presented a frame by the multiplex sublayer and transforms it into an 11over-the-air waveform. The physical layer in the receiving station transforms the waveform back 12into a frame and presents it to the multiplex sublayer above it. 13PI See Paging Indicator 14Pilot Beacon - A transmit-only base station that broadcasts a Forward pilot channel, a Sync 15Channel, optionally a Paging Channel, but no Forward Traffic Channels. The mobile station 16measures the pilot beacon to assist in CDMA hard handoffs and inter-frequency idle-mode 17handoffs.

18Pilot Ec - Average energy per PN chip for the Forward pilot channel
Ec - The ratio of the combined pilot energy per chip, Ec, to the total received power Io 20spectral density (noise and signals), Io, of at most K usable multipath components at the mobile 21station antenna connector (see 1.4). K is the number of demodulating elements supported by the 22mobile station.

19Pilot

23 - The ratio of the average transmit energy per PN chip for the Forward pilot channel to the total 24transmit power spectral density. 25Pilot PN Sequence - A pair of modified maximal length PN sequences with period 215 PN chips 26used to spread the Forward CDMA Channel and the Reverse CDMA Channel. Different base 27stations are identified by different pilot PN sequence offsets. 28Pilot PN Sequence Offset - The time offset of a Forward Pilot Channel from CDMA System time, 29as transmitted by the base station, expressed modulo the pilot period. 30Pilot PN Sequence Offset Index - The pilot PN sequence offset in units of 64 PN chips of a 31Forward Pilot Channel, relative to the zero offset pilot PN sequence. 32Pilot Strength - The ratio of pilot power to total power in the signal bandwidth of a CDMA 33Forward or Reverse Channel. See also Ec/Io. 34PM Privacy Mode 35PN - Pseudonoise 36PN Chip - One bit in a PN sequence, or the time duration of such a bit. It corresponds to the 37smallest modulation interval in a CDMA system. 38PN Sequence Pseudo-random noise sequence. A deterministic, periodic binary sequence 39having limited statistical similarity to a Bernoulli (coin-tossing). 40Power Control Bit - A bit sent in every 1.25 ms interval on the Forward Traffic Channel that 41signals the mobile station to increase or decrease its transmit power.

42Power Control Ec - Average energy per PN chip for the power control subchannel. For the case
43when the power control sub-channel is assumed to be transmitted at the same power level that is 44used for the 9600 bps or 14400 bps data rate, the following equations apply: For Rate Set 1, it is

xx

13GPP2 C.S0044-A v1.0

v x (total Forward Traffic Channel energy per PN chip), where v equals 1 for 9600 11 + v 2bps, v equals 2 for 4800 bps, v equals 4 for 2400 bps, and v equals 8 for 1200 bps traffic data v 3rate. For Rate Set 2, it is equal to x (total Forward Traffic Channel energy per PN chip), 23 + v 4where v equals 1 for 14400 bps, v equals 2 for 7200 bps, v equals 4 for 3600 bps, and v equals 8 5for 1800 bps traffic data rate. The total Forward Traffic Channel is comprised of traffic data and a 6power control sub-channel.

1equal to

v - The ratio of the average transmit energy per PN chip for the power control subchannel to 23 + v 8the total transmit power spectral density.

9Power Control Group - A 1.25 ms interval on the Forward Traffic Channel and the Reverse 10Traffic Channel. See also Power Control Bit. 11Power-Down Registration - An autonomous registration method in which the mobile station 12registers on power-down. 13Power-Up Registration - An autonomous registration method in which the mobile station 14registers on power-up. 15PPP Point-to-Point Protocol 16Preamble - See Access Channel Preamble and Traffic Channel Preamble 17Primary Traffic - The main traffic stream carried between the mobile station and the base station 18on the Traffic Channel. See also Secondary Traffic and Signaling Traffic. 19Private Long Code - The long code characterized by the private long code mask. See also Long 20Code. 21Private Long Code Mask - The long code mask used to form the private long code. See also 22Public Long Code Mask and Long Code. 23Private Neighbor Set - The set of pilots associated with the private system base stations that are 24probable candidates for idle handoff. See also Active Set, Neighbor Set, Remaining Set, and 25CDMA Tiered Services. 26Protocol Data Unit - Encapsulated data communicated between peer layers on the mobile 27station and base station. Unless specified otherwise, in this document PDU refers to the Layer 3 28protocol data unit transferred at the interface between layer 3 and layer 2. 29Protocol Stack - Conceptual model of the layered architecture for communication protocols (see 30Layering) in which layers within a station are represented in the order of their numeric designation 31and requiring that transferred data be processed sequentially by each layer, in the order of their 32representation. Graphically, the stack is drawn vertically, with the layer having the lowest 33numeric designation at the base. 34PSIST Persistence Delay 35Public Long Code - The long code characterized by the public long code mask. 36Public Long Code Mask The long code mask used to form the public long code. The mask 37contains a permutation of the bits of the ESN, and also includes the channel number when used 38for a Supplemental Code Channel. See also Private Long Code Mask and Long Code. 39Public Safety Answering Point (PSAP) - A dispatch office that receives emergency calls from 40the public. 41PSTN Public Switching Telephone Network 42QPCH See Quick Paging Channel

xxi

3GPP2 C.S0044-A v1.0

1Quick Paging - A feature that permits mobile stations to further conserve battery power beyond 2the savings achieved by slotted mode operation. See also Paging Indicator and Configuration 3Change Indicator. 4Quick Paging Channel (QPCH)- An uncoded, on-off-keyed (OOK) spread spectrum signal sent 5by base stations to inform slotted mode mobile stations, operating in the idle state, whether to 6monitor the Paging Channel. See also Quick Paging, Paging Indicator, and Configuration Change 7Indicator. 8Quick Paging Channel Slot - An 80 ms interval on the Quick Paging Channel. See also Paging 9Indicator and Configuration Change Indicator. 10r-csch - Reverse common signaling logical channel 11r-dsch - Reverse dedicated signaling logical channel 12Radio Configuration (RC) - A set of Forward Traffic Channel and Reverse Traffic Channel 13transmission formats that are characterized by physical layer parameters such as transmission 14rates, modulation characteristics and spreading rate. 15RC - See Radio configuration. 16Registration - The process by which a mobile station identifies its location and parameters to a 17base station. 18Registration Zone - A collection of one or more base stations treated as a unit when determining 19whether a mobile station should perform zone-based registration. See also User Zone, with which 20it should not be confused. 21Release - A process that the mobile station and base station use to inform each other of call 22disconnect. 23Remaining Set - The set of all allowable pilot offsets as determined by PILOT_INC, excluding the 24pilot offsets of the pilots in the Active Set, Candidate Set, and Neighbor Set. See also Active Set, 25Candidate Set, and Neighbor Set. 26Request - A layer 3 message generated by either the mobile station or the base station to 27retrieve information, ask for service, or command an action. 28Reservation - Air interface resources set up by the access network to carry a higher layer 29flow. A Reservation is identified by its ReservationLabel. ReservationLabels are bound to 30RLP Flows that carry higher layer flows. A Reservation can be either in the Open or Close 31state. 32Response - A layer 3 message generated as a result of another message, typically a request. 33Reverse CDMA Channel - The CDMA Channel from the mobile station to the base station. From 34the base stations perspective, the Reverse CDMA Channel is the sum of all mobile station 35transmissions on a CDMA frequency assignment. 36Reverse Dedicated Control Channel (R-DCCH) - A portion of a Reverse Traffic Channel that 37can carry a combination of primary data, secondary data, signaling, and power control 38information. 39Reverse Fundamental Channel (R-FCH) - A portion of a Reverse Traffic Channel that can carry 40a combination of primary data, secondary data, signaling, and power control information. 41Reverse Pilot Channel (R-PICH) - A non-data-bearing direct-sequence spread spectrum signal 42transmitted by each CDMA mobile station whenever the Enhanced Access Channel, Reverse 43Common Control Channel, or Reverse Traffic Channel is enabled. The Reverse Pilot Channel 44allows a base station to acquire the timing of the Reverse CDMA Channel and provides a phase

xxii

13GPP2 C.S0044-A v1.0

1reference for coherent demodulation. The Reverse Pilot Channel may be transmitted either 2continuously or in gated mode. 3Reverse Supplemental Channel (R-SCH) - An optional portion of a Reverse Traffic Channel 4(Radio Configurations 3 and above) that operates in conjunction with a Fundamental Channel 5and or the Dedicated Control Channel in that Traffic Channel, and (optionally) with other 6Supplemental Channels to provide higher data rate services. 7Reverse Supplemental Code Channel (R-SCCH) - An optional portion of a Reverse Traffic 8Channel (Radio Configurations 1 and 2) that operates in conjunction with a Fundamental Channel 9in that Traffic Channel, and (optionally) with other Supplemental Code Channels to provide higher 10data rate services. 11RF Radio Frequency 12RLP Radio Link Protocol 13SCCLT Supplemental Code Channel List Table 14SCR Service Configuration Record 15SDU - See Service Data Unit 16Search Window - The range of PN sequence offsets that a mobile station searches for a pilot. 17Search Window Offset - PN sequence offset used by the mobile station to position the search 18window when searching for a pilot. 19Secondary Traffic - An additional traffic stream that can be carried between the mobile station 20and the base station on the Traffic Channel. See also Primary Traffic and Signaling Traffic. 21Service Configuration - The common attributes used by the mobile station and the base station 22to build and interpret Traffic Channel frames. A service configuration consists of Forward and 23Reverse Traffic Channel multiplex options, Forward and Reverse Traffic Channel transmission 24rates, and service option connections. Service Configuration is signaled via the Service 25Configuration information record and the Non-Negotiable Service Configuration information 26record. 27Service Negotiation - The procedures used by the mobile station and base station to establish a 28service configuration. See also Service Option Negotiation. 29Service Option - A service compatibility of the system. Service options may be applications such 30as voice, data, or facsimile. See (17). 31Service Option Connection - A particular instance or session in which the service defined by a 32service option is used. Associated with a service option connection are a reference, which is used 33for uniquely identifying the service option connection, a service option, which specifies the 34particular type of service in use, a Forward Traffic Channel traffic type, which specifies what type 35of Forward Traffic Channel traffic is used to support the service option connection, and a Reverse 36Traffic Channel traffic type, which specifies what type of Reverse Traffic Channel traffic is used by 37the service option connection. 38Service Option Negotiation - The procedures used by the mobile station and base station to 39establish a service configuration. Service option negotiation is similar to service negotiation, but 40allows less flexibility for specifying the attributes of the service configuration. See also Service 41Negotiation. 42Service Redirection - The process by which the base station alters the system selection made 43by a mobile station. It can be used temporarily during maintenance and testing to divert 44subscribers to an alternate system. 45Serving Frequency - The CDMA frequency on which a mobile station is currently communicating 46with one or more base stations.

xxiii

3GPP2 C.S0044-A v1.0

1Shared Secret Data (SSD) - A 128-bit pattern stored in the mobile station (in semi-permanent 2memory) and known by the base station. SSD is a concatenation of two 64-bit subsets: SSD_A, 3which is used to support the authentication procedures, and SSD_B, which serves as one of the 4inputs to the process generating the encryption mask and private long code. 5Short Message Services (SMS) - A suite of services such as SMS Text Delivery, Digital Paging 6(i.e., Call Back Number - CBN), and Voice Mail Notification (VMN). 7SID - See System Identification 8Signaling Traffic - Control messages that are carried between the mobile station and the base 9station on the Traffic Channel. See also Primary Traffic and Secondary Traffic. 10Slotted Mode - An operation mode of the mobile station in which the mobile station monitors only 11selected slots on the Paging Channel. 12SME Signaling Message Encryption 13SO Service Option 14Soft Handoff - A handoff occurring while the mobile station is in the Mobile Station Control on 15the Traffic Channel State. This handoff is characterized by commencing communications with a 16new base station on the same CDMA frequency assignment before terminating communications 17with the old base station. See Hard Handoff. 18SPC - Service Programming Code 19Space Time Spreading (STS) - A forward link transmission method which transmits all forward 20link channel symbols on multiple antennas and spreads the symbols with complementary Walsh 21or quasi-orthogonal functions. 22SSD - See Shared Secret Data 23STS See Space Time Spreading 24Supplemental Code Channel (SCCH)- An optional portion of a Traffic Channel (Forward or 25Reverse) which operates in conjunction with a Fundamental Channel in that Traffic Channel, and 26(optionally) with other Supplemental Code Channels to provide higher data rate services. On this 27channel a combination of primary data, secondary data, or both (but never signaling information) 28are transmitted.

29Supplemental Ec - Average energy per PN chip for one Forward Supplemental Code Channel.
30Supplemental - The ratio of the average transmit energy per PN chip for one Forward 31Supplemental to the total transmit power spectral density. 32Sync Channel - Code channel 32 in the Forward CDMA Channel, which transports the 33synchronization message to the mobile station. 34Sync_Chip_Bit - Number of PN chips per Sync Channel bit, equal to 1024.

35Sync Ec - Average energy per PN chip for the Sync Channel.

36 - The ratio of the average transmit energy per PN chip for the Sync Channel to the total transmit 37power spectral density. 38System - A system is a cellular telephone service or personal communications service that 39covers a geographic area such as a city, metropolitan region, county, or group of counties. See 40also Network. 41System Identification (SID) - A number uniquely identifying a cellular or PCS system 42System Time - The time reference used by the system. System Time is synchronous to UTC 43time (except for leap seconds) and uses the same time origin as GPS time. All base stations use 44the same System Time (within a small error). Mobile stations use the same System Time, offset

xxiv

13GPP2 C.S0044-A v1.0

1by the propagation delay from the base station to the mobile station. See also Universal 2Coordinated Time. 3Target Frequency - The CDMA frequency assignment to which the base station directs a mobile 4station in a handoff using an Extended Handoff Direction Message, a General Handoff Direction 5Message, or a Universal Handoff Direction Message. 6TCP Transmission Control Protocol 7Temporary Mobile Station Identity (TMSI) - A temporary mobile station identification assigned 8by the base station. 9TD Transmit Diversity. See Orthogonal Transmit Diversity and Space Time Spreading. 10TDSO Test Data Service Option 11TE Terminal Equipment 12TE2L Terminal Equipment at land connection 13TE2M Terminal Equipment at mobile connection 14Timer-Based Registration - A registration method in which the mobile station registers 15whenever a counter reaches a predetermined value. The counter is incremented an average of 16once per 80 ms period. 17Time Reference - A reference established by the mobile station that is synchronous with the 18earliest arriving multipath component used for demodulation. 19TMSI - See Temporary Mobile Station Identity 20TMSI Zone - The administrative zone that allows the TMSI to be reused. The TMSI_CODE has to 21be unique within a TMSI zone but may be reused in a different TMSI zone. The TMSI zone is 22identified by the field TMSI_ZONE. 23Traffic Channel - A communication path between a mobile station and a base station used for 24user and signaling traffic. The term Traffic Channel implies a Forward Traffic Channel and 25Reverse Traffic Channel pair. See also Forward Traffic Channel and Reverse Traffic Channel. 26Traffic Channel Preamble - A sequence of all-zero frames that is sent by the mobile station on 27the Reverse Traffic Channel as an aid to Traffic Channel acquisition.

28Traffic Ec - Average energy per PN chip for the Forward Fundamental Channel. For the case
29when the power control sub-channel is assumed to be transmitted at the same power level used 30for the 9600 bps or 14400 bps data rate, the following equations apply: For Rate Set 1, it is equal 11 31to x (total Forward Fundamental Channel energy per PN chip), where v equals 1 for 9600 11 + v 32bps, v equals 2 for 4800 bps, v equals 4 for 2400 bps, and v equals 8 for 1200 bps traffic data 23 33rate. For Rate Set 2, it is equal to x (total Forward Fundamental Channel energy per PN 23 + v 34chip), where v equals 1 for 14400 bps, v equals 2 for 7200 bps, v equals 4 for 3600 bps, and v 35equals 8 for 1800 bps traffic data rate. The total Forward Fundamental Channel is comprised of 36traffic data and a power control sub-channel. 37 - The ratio of the average transmit energy per PN chip for the Forward Traffic Channel to the 38total transmit power spectral density. 39TSB Technical Service Bulletin 40Unique Challenge-Response Procedure - An exchange of information between a mobile station 41and a base station for the purpose of confirming the mobile stations identity. The procedure is 42initiated by the base station and is characterized by the use of a challenge- specific random 43number (i.e., RANDU) instead of the random variable broadcast globally (RAND).

xxv

3GPP2 C.S0044-A v1.0

1Universal Coordinated Time (UTC) - An internationally agreed-upon time scale maintained by 2the Bureau International de lHeure (BIH) used as the time reference by nearly all commonly 3available time and frequency distribution systems i.e., WWV, WWVH, LORAN-C, Transit, Omega, 4and GPS. 5User Zone - An area within which CDMA Tiered Services may be provided. It may correspond to 6an RF coverage area, or it may be established independent of RF topology. User Zones are 7classified as broadcast versus mobile-specific, and as active versus passive. See: Broadcast 8User Zone, Mobile-Specific User Zone, Active User Zone, and Passive User Zone. See also 9Registration Zone, with which it should not be confused. 10UTC - Universal Temps Coordin. See Universal Coordinated Time 11V.42 ITU-T Recommended error correction protocol 12VJ Van Jacobson compression 13VMN Voice Mail Notification 14VMNI Voice Mail Notification Indicator 15Voice Privacy - The process by which user voice transmitted over a CDMA Traffic Channel is 16afforded a modest degree of protection against eavesdropping over the air. 17Walsh Chip - The shortest identifiable component of a Walsh function. There are 2N Walsh chips 18in one Walsh function where N is the order of the Walsh function. On the Forward CDMA 19Channel, one Walsh chip equals 1/1.2288 MHz, or 813.802 ns. On the Reverse CDMA Channel, 20one Walsh chip equals 4/1.2288 MHz, or 3.255 s. 21Walsh Function - One of 2N time orthogonal binary functions (note that the functions are 22orthogonal after mapping 0 to 1 and 1 to -1). 23WLL Wireless Local Loop 24Zone-Based Registration - An autonomous registration method in which the mobile station 25registers whenever it enters a zone that is not in the mobile stations zone list. See also User 26Zone Registration, with which it should not be confused. 27Zone Timer - A timer used by the mobile station to remove outdated entries from its list of zones 28in which it has previously registered. 29s - Microsecond (10-6 second).

30 31

Tolerances CDMA System Parameter Tolerances

32CDMA parameters are specified in Annex B. All parameters indicated are exact unless otherwise 33specified.

34

Measurement Tolerances

35Unless otherwise specified, a measurement tolerance, including the tolerance of the 36measurement equipment, of 10% is assumed.

37Unless otherwise specified, the Ior/Ioc value shall be within 0.1 dB of the value specified, and 38the Ioc value shall be within 5 dB of the value specified.

xxvi

13GPP2 C.S0044-A v1.0 1

Document References

2The following documents contain provisions, which through reference in this text, constitute 3provisions of this document. At the time of publication, the editions indicated were valid. All 4standards are subject to revision, and parties to agreements based on this Standard are 5encouraged to investigate the possibility of applying the most recent editions of the standards 6indicated below. ANSI and TIA maintain registers of currently valid national standards published 7by them. Unless otherwise noted, references are considered normative.

xxvii

1
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18 19

3GPP2 C.S0044-A v1.0 3GPP2 C.S0002-A, Physical Layer Standard for cdma2000 Spread Spectrum Systems. 3GPP2 C.S0003-A, Medium Access Control (MAC) Standard for cdma2000 Spread Spectrum Systems. 3GPP2 C.S0004-A, Signaling Link Access Control (LAC) Standard for cdma2000 Spread Spectrum Systems. 3GPP2 C.S0005-A, Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems. 3GPP2 C.S0010-B, Recommended Minimum Performance Standards for cdma2000 Spread Spectrum Base Stations. 3GPP2 C.S0011-B, Recommended Minimum Performance Standards for cdma2000 Spread Spectrum Mobile Stations. 3GPP2 C. S0026-0, Test Data Service Option (TDSO) for cdma2000 Spread Spectrum Systems. 3GPP2 C. S0025-0, Markov Service Option (MSO) for cdma2000 Spread Spectrum Systems. 3GPP2 C.S0013-A, Loopback Service Options (LSO) for cdma2000 Spread Spectrum Systems. 3GPP2 X.S0011-001-C, cdma2000 Wireless IP Network Standard: Introduction 3GPP2 A.S0008-A, Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Radio Access Network Interfaces with Session Control in the Access Network. 3GPP2 C.S0063-A, cdma2000 High Rate Packet Data Supplemental Services 3GPP2 C.S0015-A, Short Message Service (SMS) for Wideband Spread Spectrum Systems Release A, 2002 3GPP2 C.S0016-B, Over-the-Air Service Provisioning of Mobile Stations in Spread Spectrum Systems, October 2002. 3GPP2 C.S0017-0, Data Service Options for Wideband Spread Spectrum Systems Reserved 3GPP2 C.R1001-D, Administration of Parameter Value Assignment for TIA/EIA Spread Spectrum Standards INFORMATIVE REFERENCE 3GPP2 C.S0014-0, Enhanced Variable Rate Codec, Speech Service Option 3 for Wideband Spread Spectrum Digital Systems 3GPP2 C.S0020-0, High Rate Speech Service Option 17 for Wideband Spread Spectrum Communications Systems 20 21 22 23 TTY Forum. Seeking Solutions to TTY/TDD Through Wireless Digital Systems. TTY/TDD FORUM-13. Final. 3GPP2 C.S0006-A, Analog Signaling Standard for cdma2000 Spread Spectrum Systems. 3GPP2 S.R0006, Wireless Features Description IETF RFC-792, Internet Control Message Protocol

xxviii

13GPP2 C.S0044-A v1.0

24 25 26 27 28 29 30 3GPP2 C.S0024-A, cdma2000 High Rate Packet Data Air Interface Specification 3GPP2 C.S0022-0, Position Determination Service Standards for Dual Mode Spread Spectrum Systems 3GPP2 A.S0009-A, Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Radio Access Network Interfaces with Session Control in the Packet Control Function 3GPP2 C.S0029-0, Test Application Specification (TAS) for High Rate Packet Data Air Interface 3GPP2 X.S0011-002-C, cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Access Services 3GPP2 C.S0075-0, Interworking Specification for cdma2000 1x and High Rate Packet Data Systems 3GPP2 S.R0108-0 HRPD-cdma2000 1x Interoperability for Voice and Data System Requirements

1 2

xxix

1
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

3GPP2 C.S0044-A v1.0

Intentionally left blank

xxx

13GPP2 C.S0044-A v1.0 11 21.1 31.1.1

MISCELLANEOUS AIR INTERFACE TESTS

Call Setup under Various PSIST Settings Definition

4This test verifies mobile station processing of the PSIST values. The persistence delay is a 5function of the variable P in the following equations.

6 7 8 9 10
11

If the type of the SDU is a request other than a registration or a message transmission, and the SDU is not for an emergency call or emergency message transmission, P shall be computed by

2 PSISTs /4 P= 0 2 PSISTs P= 0

if PSISTs 63 otherwise if PSISTs 7 otherwise

ACCOLCp = 0, 1, ..., 9

12
13

ACCOLCp = 10, 11, ..., 15

14 15 16 17

If the type of the SDU is a request for an emergency call or for an emergency message transmission, and the mobile station has an ACCOLCp value between 0 and 9 inclusive, P shall be computed by 2 PSIST P= 0
_ EMG s

if PSIST_EMG otherwise

ACCOLCp = 0, 1, , 9

18If P is equal to 0, the mobile station shall end the access attempt, shall declare an access attempt 19failure, and send an indication to Layer 3 that the system access is denied.

201.1.2
21(See[4])

Traceability

222.6.2.2.2 232.6.2.2.15 242.7.1.3.2.4 252.7.1.3.2.5 263.7.2.3.2.2 273.7.2.3.2.33

28(See[3])

Access Parameters Message Enhanced Access Parameters Message Origination Message Page Response Message Access Parameters Message Enhanced Access Parameters Message

292.1.1.2.2.2

Requirements for Transmission and Retransmission Procedures

1 11.1.3
2None

3GPP2 C.S0044-A v1.0 Call Flow Example(s)

31.1.4 41.1.4.1 5 6 7 8 9 10
a. b. c.

Method of Measurement Persistence Delay for Mobile Station in using ACCOLCP between 0 and 9 Connect the base station and mobile station as shown in Figure A-3. Set ACCOLCP to any value between 0 and 9 in the mobile station. Instruct the base station to send an Access Parameters Message or an Enhanced Access Parameters Message in Table 1.1.4-1or Table 1.1.4-2 respectively:

Table 1.1.4-1 Access Parameters Message Settings Field PSIST(0-9) PSIST(11) PSIST_EMG_INCL Value 000000 000 0

11

12

Table 1.1.4-2 Enhanced Access Parameters Message Settings Field PSIST_PARMS_INCL PSIST_PARMS_LEN PSIST(0-9)_EACH PSIST_11_EACH PSIST_EMG Value 1 As required 000000 000 000

13

14 15 16 17 18

d. e. f. g.

Setup a mobile station originated call. Verify the mobile station does not delay sending the Origination Message. Verify the call completes and there is user traffic in both directions. Setup a mobile station terminated call and verify the mobile station does not delay sending the Page Response Message.

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13

h. i. j. k. l. m. n. o. p. Change PSIST(0-9) or PSIST(0-9)_EACH in the Access Parameters Message or Enhanced Access Parameters Message to 111111. Attempt to setup a mobile station originated call. Verify the mobile station does not send an Origination Message. Set PSIST(0_9) = 011000 or PSIST(0-9)_EACH in the Access Parameters Message or Enhanced Access Parameters Message. Setup a mobile station originated call. Verify the mobile station does delay sending the Origination Message according to the equations in 1.1.12. End the call. Setup a mobile station terminated call. Verify the mobile station does not delay sending the Page Response Message to the base station. Persistence Delay ACCOLCP greater than 9 Connect the base station and mobile station as shown in Figure A-3. Set ACCOLCP = 11 in the mobile station. Instruct the base station to send an Access Parameters Message or an Enhanced Access Parameters Message in Table 1.1.4-3 or Table 1.1.4-4respectively:

141.1.4.2 15 16 17 18
19

a. b. c.

20
Field

Table 1.1.4-3 Access Parameters Message Settings Value 000000 000 0

PSIST(0-9) PSIST(11) PSIST_EMG_INCL

21

22

Table 1.1.4-4 Enhanced Access Parameters Message Settings Field PSIST_PARMS_INCL PSIST_PARMS_LEN Value 1 As required

22 For PSIST test cases, test may need to be repeated, since MS may not delay sending a 3message every time. For PSIST testing, it may be necessary to monitor access probe output to 4verify that the access attempts are delayed. 5
3

3GPP2 C.S0044-A v1.0

PSIST(0-9)_EACH PSIST_11_EACH PSIST_EMG

1

000000 000 000

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

d. e. f. g. h. i. j. k. l. m. n. o. p.

Setup a mobile station originated call. Verify the mobile station does not delay sending the Origination Message. Verify the call completes and there is user traffic in both directions. Setup a mobile station terminated call and verify the mobile station does not delay sending the Page Response Message. Change PSIST(11) or PSIST_11_EACH in the Access Parameters Message or Enhanced Access Parameters Message to 111. Attempt to setup a mobile station originated call. Verify the mobile station does not send an Origination Message. Change PSIST(11) or PSIST_11_EACH in the Access Parameters Message or Enhanced Access Parameters Message to 110. Setup a mobile station originated call. Verify the mobile station does delay sending the Origination Message according to the equations in 1.1.13. End the call. Setup a mobile station terminated call. Verify the mobile station does not delay sending the Page Response Message to the base station. Emergency Call Attempts Connect the base station and mobile station as shown in Figure A-3. Instruct the base station to send an Access Parameters Message or an Enhanced Access Parameters Message in Table 1.1.4-5or Table 1.1.4-2 respectively:

201.1.4.3 21 22 23
24

a. b.

23 For PSIST test cases, test may need to be repeated, since MS may not delay sending a 3message every time. For PSIST testing, it may be necessary to monitor access probe output to 4verify that the access attempts are delayed. 5
4

13GPP2 C.S0044-A v1.0 1

Field PSIST(0-9) PSIST_EMG_INCL PSIST_EMG
2

Table 1.1.4-5 Access Parameters Message Settings Value 0 1 111

Table 1.1.4-2 Enhanced Access Parameters Message Settings Field PSIST_PARMS_INCL PSIST_PARMS_LEN PSIST(0-9)_EACH PSIST_11_EACH PSIST_EMG Value 1 As required 000000 000 111

4 5 6 7 8 9 10 11 12 13 14 15

c. d. e. f. g. h. i. j.

Set ACCOLCP = 0-9 in the mobile station. Attempt to setup an emergency call. Verify the mobile station does not send an Origination Message to the base station. End the call. Repeat step d after changing PSIST_EMG = 110 in the Access Parameters Message or the Enhanced Access Parameters Message. Verify the mobile station delays sending the Origination Message for the emergency call. Repeat step d, changing the PSIST_EMG = 000 in the Access Parameters Message or Enhanced Access Parameters Message. Verify the mobile station does not delay sending the Origination Message to the base station for the emergency call. Minimum Standard Persistence Delay for Mobile Station in using ACCOLCP between 0 and 9

161.1.5 171.1.5.1

18The mobile station shall comply with steps e, f, g, j, m, and p.

1 11.1.5.2
Persistence Delay ACCOLCP greater than 9

3GPP2 C.S0044-A v1.0

2The mobile station shall comply with steps e, f, g, j, m, and p.

31.1.5.3

Emergency Call Attempts

4The mobile station shall comply with steps e, h, and j.

51.2 61.2.1

Registration Attempts with Different PSIST Settings Definition

7This test verifies mobile station processing of the PSIST values. The persistence delay is a 8function of the variable P in the following equations.

9 10
11

If the type of the SDU is a request and a registration, P shall be computed by

2 PSISTs /4 2 REG _ PSISTs P= 0 2 PSISTs 2 REG _ PSISTs 0

if PSISTs 63 otherwise if PSISTs 7 otherwise

ACCOLCp = 0, 1, ..., 9

12 131.2.2
14(See[4])

P=

ACCOLCp = 10, 11, ..., 15

Traceability

152.6.2.2.2 162.6.2.2.15 172.7.1.3.2.4 182.7.1.3.2.5 193.7.2.3.2.2 203.7.2.3.2.33

21(See[3])

Access Parameters Message Enhanced Access Parameters Message Origination Message Page Response Message Access Parameters Message Enhanced Access Parameters Message

222.1.1.2.2.2 231.2.3
24None

Requirements for Transmission and Retransmission Procedures

Call Flow Example(s)

251.2.4 26 27 28 29
a. b. c.

Method of Measurement Connect the base station and mobile station as shown in Figure A-3. Set ACCOLCP to any value between 0 and 9 in the Mobile Station. Instruct the base station to send the Access Parameters Message or Enhanced Access Parameters Message with the following values.

13GPP2 C.S0044-A v1.0 1

Field PSIST(0-9) REG_PSIST
2

Table 1.2.4-3 Access Parameters Message Settings Value 000000 000

Table 1.2.4-2 Enhanced Access Parameters Message Settings Field PSIST_PARMS_INCL PSIST_PARMS_LEN PSIST(0-9)_EACH REG_PSIST_EACH Value 1 As required 000000 000

4 5 6 7 8 9 10 11 12 13

d. e. f. g. h.

Set the value of REG_PRD to 29 in the System Parameters Message. Verify timer-based registration occurs at the interval specified by REG_PRD. Set REG_PSIST or REG_PSIST_EACH = 110 or in the Access Parameters Message or Enhanced Access Parameters Message. Verify timer-based registration occurs at longer intervals than specified by REG_PRD. Set REG_PSIST or REG_PSIST_EACH = 111 and set PSIST(0-9) and PSIST(11) or PSIST(0-9)_EACH and PSIST(11)_EACH to 111111 and 111 respectively in the Access Parameters Message or Enhanced Access Parameters Message. Verify the mobile station does not send a Registration Message. Set ACCOLCP = 11 in the mobile station and repeat steps c through i. Minimum Standard

i. j.

141.2.5

15The mobile station shall comply with steps e, g, and i.

161.3 171.3.1 18 19 20 21 22

Short Message Service with Different PSIST Settings Definition

This test verifies mobile station processing of the PSIST values. The persistence delay is a function of the variable P in the following equations. If the type of the SDU is a request and a message transmission, except in the case of an emergency message transmission from a mobile station having an ACCOLCp value between 0 and 9 inclusive, P shall be computed by

1 1
2

3GPP2 C.S0044-A v1.0

P=

2 PSISTs /4 2 MSG _ PSISTs 0 2 PSISTs 2 MSG _ PSISTs P= 0

if PSISTs 63 otherwise if PSISTs 7 otherwise

ACCOLCp = 0, 1, ..., 9

3
4

ACCOLCp = 10, 11, ..., 15

51.3.2
6None

Call Flow Example(s)

71.3.3
8(See[4])

Traceability

92.6.2.2.2 102.6.2.2.15 112.7.1.3.2.4 122.7.1.3.2.5 133.7.2.3.2.2 143.7.2.3.2.33

15(See[3])

Access Parameters Message Enhanced Access Parameters Message Origination Message Page Response Message Access Parameters Message Enhanced Access Parameters Message

162.1.1.2.2.2 171.3.4 18 19 20 21 22
a. b. c.

Requirements for Transmission and Retransmission Procedures

Method of Measurement Connect the base station and mobile station as shown in Figure A-3. Set ACCOLCP to any value between 0 and 9 in the Mobile Station. Instruct the base station to send an Access Parameters Message or an Enhanced Access Parameters Message with the following parameters: Table 1.3.4-4 Access Parameters Message Settings Field PSIST(0-9) MSG_PSIST Value 000000 000

23

13GPP2 C.S0044-A v1.0 1

Table 1.3.4-2 Enhanced Access Parameters Message Settings Field PSIST_PARMS_INCL PSIST_PARMS_LEN PSIST(0-9)_EACH MSG_PSIST_EACH
2

Value 1 As required 000000 000

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

d.

Create a short message at the mobile station, of a length smaller than the maximum message length allowed on the Access Channel, and instruct the mobile station to send the short message to the network. Verify the mobile station does not delay sending the Data Burst Message. Set MSG_PSIST or MSG_PSIST_EACH = 110 in the Access Parameters Message or the Enhanced Access Parameters Message. Create a short message at the mobile station, of a length smaller than the maximum message length allowed on the access channel, and instruct the mobile station to send the short message to the network. Verify the mobile station delays sending the Data Burst Message to the base station over the access channel. Set MSG_PSIST or MSG_PSIST_EACH = 111 and set PSIST(0-9) or PSIST(09)_EACH to 111111 in the Access Parameters Message or Enhanced Access Parameters Message. Create a short message at the mobile station, of a length smaller than the maximum message length allowed on the access channel, and instruct the mobile station to send the short message to the network. Verify the mobile station does not send the Data Burst Message. Set ACCOLCP = 11 in the mobile station and repeat steps c through k. Minimum Standard

e. f. g.

h. i.

j.

k. l.

221.3.5

23The mobile station shall comply with steps e, h, and k.

241.4 251.4.1

Quick Paging Channel CCI Definition

26For mobile stations that support the Quick Paging Channel, this test will verify the following: A 27mobile station using the Quick Paging Channel configuration change indicator (CCI) will update 28its overhead information when the CCI bit is set to on.

1 11.4.2
2(See[4])

3GPP2 C.S0044-A v1.0 Traceability

32.6.2.1.1.3 42.6.2.1.2 52.6.2.1.4 62.6.7.1 73.6.2.5 83.7.2.3.2.13 93.7.2.3.2.14 101.4.3

11None

Slotted Mode Requirements Quick Paging Channel Monitoring Procedures Idle Handoff Hash Function Quick Paging Channel Processing Extended System Parameters Message Extended Neighbor List Message

Call Flow Example(s)

121.4.4 13 14 15 16 17 18 19 20 21 22 23
Field b. a.

Method of Measurement Connect two base stations to the mobile station, with the ability to transition either base station power Ior 5 dB above the other, to induce idle handoff from one to the other and back again. 1. The Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1. 2. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P2 and called Channel 2. Set the Extended System Parameter Message in both base stations as specified in Table 1.4.4-5.

Table 1.4.4-5 Test Parameters for Extended System Parameters Message Values '1' (QPCH is supported) '01' (Number of the QPCH) '0' (QPCH indicator rate is 4800 bps) '101' (same as forward pilot channel) '1' [configuration change indicators supported] '101' (same as forward pilot channel)

QPCH_SUPPORTED NUM_QPCH QPCH_RATE (indicator rate) QPCH_POWER_LEVEL_PAGE QPCH_CCI_SUPPORTED QPCH_POWER_LEVEL_CONFIG

24

10

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6

c. Set NGHBR_PN for the Extended Neighbor List Message, Neighbor List Message or General Neighbor List Message in both base stations to include the other base station PN. Set the Paging Channel data rate for Channels 1 and 2 to 4800 bps. Setup Channel 1 and Channel 2 per Table 1.4.4-2. Table 1.4.4-2 Test Parameters for Slotted Mode Idle Handoff Parameter or/Ioc Pilot E c I or Quick Paging E c I or Ioc dBm/1.23 MHz -75 Unit dB dB Channel 1 0 -7 Channel 2 -5 -7

d. e.

dB

-7

-7

7 8 9 10 11 12 13 14 15 16 17 18 19
f. Slowly (over a period of several seconds, but not more than T31m = 600 seconds round trip) transpose power levels of channel 1 and 2. That is, raise Channel 2 power by 5 dB (to or/Ioc = 0 dB), and lower Channel 1 power by 5 dB (to or/Ioc = -5 dB). This should cause an idle handoff from Channel 1 to Channel 2. g. h. Verify the mobile station has performed an idle handoff to Channel 2. While the mobile station is idle on Channel 2, instruct the base station 1 to modify an overhead message, thus causing the CCI bits on Channel 1 Quick Paging Channel to be set to ON. Cause an idle handoff from Channel 2 to Channel 1. Verify that the mobile station does not go to slotted mode until it has updated its overhead configuration. Repeat steps a through j with the QPCH_RATE (indicator rate) set to 1 (9600 rate). Minimum Standard

i. j. k.

201.4.5

21The mobile station shall comply with the requirement in steps g and j.

221.5
231.5.1 251.5.2

Mobile Station Response to Status Request Message Definition Traceability

24This test verifies that that mobile station responds to the Status Request Message correctly. 26(See[4])

11

1 12.6.3.5 22.6.4.1.2 32.6.4.1.14 42.6.4.1.15 52.6.4.2 62.7.1.3.2.4 72.7.1.3.2.5 82.7.1.3.2.10 92.7.2.3.2.14 102.7.2.3.2.16 112.7.4 123.6.3.5 133.6.4.1.2 143.7.2.3.2.15 153.7.2.3.2.21 163.7.3.3.2.20 173.7.5.7 183.7.5.20
191.5.3 20None 211.5.4

3GPP2 C.S0044-A v1.0 Mobile Station Origination Attempt Substate Service Configuration and Negotiation Processing the Service Configuration Record Processing the Non-Negotiable Service Configuration Record Traffic Channel Initialization Substate Origination Message Page Response Message Extended Status Response Message Service Connect Completion Message Status Response Message Information Records Response to Origination Message Service Configuration and Negotiation Status Request Message Extended Channel Assignment Message Service Connect Message Service Configuration Non-Negotiable Service Configuration

Call Flow Example(s) Method of Measurement Ensure the mobile station is operating in the Idle State. Instruct the base station to send a Status Request Message on the f-csch to request one or more of the information records listed in section 2.7.4 of [4]. Verify that QUAL_INFO_TYPE, QUAL_INFO_LEN and Type-specific fields in Status Request Message are set to appropriate values. Verify the following: 1. If P_REV_IN_USE is greater than 3: a. The mobile station sends an Extended Status Response Message with the QUAL_INFO_TYPE, QUAL_INFO_LEN, Type-specific fields set to appropriate value, and requested information record(s) included; or b. The mobile station sends a Mobile Station Reject Order with ORDQ = 6 if the mobile station does not support the band class and/or operating mode specified in the Status Request Message; or

22 23 24 25 26 27 28 29 30 31 32 33 34

a. b.

c.

12

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

311.5.5

c.

The mobile station sends a Mobile Station Reject Order with ORDQ = 8 if the information record would exceed the allowable length; or

d. The mobile station sends a Mobile Station Reject Order with ORDQ = 9 if the information record is not supported for the specified band class and operating mode. 2. If P_REV_IN_USE is less than or equal to 3: a. The mobile station sends a Status Response Message with the appropriate QUAL_INFO_TYPE, QUAL_INFO_LEN, Type-specific fields set to appropriate value, and requested information record(s) included; or b. The mobile station sends a Mobile Station Reject Order with ORDQ = 6 if the mobile station does not support the band class and/or operating mode specified in the Status Request Message; or c. The mobile station sends a Mobile Station Reject Order with ORDQ = 8 if the information record would exceed the allowable length; or

d. The mobile station sends a Mobile Station Reject Order with ORDQ = 9 if the information record is not supported for the specified band class and operating mode. d. e. f. Set up a mobile originated call. Instruct the base station to send a Status Request Message on the f-dsch to request one or more of the information records listed in section 2.7.4 of [4]. Verify the following: 1. The mobile station sends a Status Response Message with the appropriate band class, operating mode, and information record; or 2. The mobile station sends a Mobile Station Reject Order with ORDQ = 6 if the mobile station does not support the band class and/or operating mode specified in the Status Request Message; or 3. The mobile station sends a Mobile Station Reject Order with ORDQ = 9 if the information record is not supported for the specified band class and operating mode. Minimum Standard

32The mobile station shall comply with steps c and f.

331.6 34 351.6.1

SYNC Channel Support for Mobile Stations not capable of TD, or not capable of QPCH or RC>2 Definition

36This test verifies that the mobile station is able to respond correctly to the new fields of Sync 37Channel Message sent by the base station if any, tune to appropriate CDMA channel and acquire 38the system successfully.

13

1 11.6.2
2(See[4])

3GPP2 C.S0044-A v1.0 Traceability

32.6.1.3 43.7.2.3.2.26 51.6.3

6None

Sync Channel Acquisition Substate Sync Channel Message

Call Flow Example(s)

71.6.4 81.6.4.1
9

Method of Measurement Base Station capable of Non-TD BCCH but not TD (Case 1)

10

Table 1.6.4-6 Frequency Allocation Case 1 Case 2 Case 3

CDMA_FREQ EXT_CDMA_FREQ SR1_CDMA_FREQ_NON_TD SR1_CDMA_FREQ_TD

1 2 3 N/A

1 2 N/A 4

1 2 3 4

11 12 13 14 15 16 17 18 19

a. b. c. d. e. f. g.

Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1. At the base station, Set Pilot PN offset to a certain value. Verify that the mobile station acquires the Forward pilot channel correctly. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.6.4-6. Verify that the mobile station tunes to CDMA Channel 3. Make a Mobile-Originated voice call and verify audio in both directions. End the call. Base Station capable of TD but not Non-TD BCCH (Case 2) Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1. At the base station, Set Pilot PN offset to a certain value. Verify that the mobile station acquires the Forward pilot channel correctly.

201.6.4.2 21 22 23 24
a. b. c.

14

13GPP2 C.S0044-A v1.0 1 2 3 4 5

d. e. f. g. Verify the mobile station receives a Sync Channel Message frequency allocation according to Table 1.6.4-6. Verify that the mobile station tunes to CDMA Channel 1. Make a Mobile-Originated voice call and verify audio in both directions. End the call. Base Station capable of Non-TD BCCH and TD (Case 3) Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1. At the base station, Set Pilot PN offset to a certain value. Verify that the mobile station acquires the Forward pilot channel correctly. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.6.4-6. Verify that the mobile station tunes to CDMA Channel 3. Make a Mobile-Originated voice call and verify audio in both directions. End the call. Minimum Standard Base Station capable of Non-TD BCCH but not TD (Case 1)

61.6.4.3 7 8 9 10 11 12 13 14 15
a. b. c. d. e. f. g.

161.6.5 171.6.5.1

18The mobile station shall comply with steps c, e, and f.

191.6.5.2

Base Station capable of TD but not Non-TD BCCH (Case 2)

20The mobile station shall comply with steps c, e, and f.

211.6.5.3

Base Station capable of Non-TD BCCH and TD (Case 3)

22The mobile station shall comply with steps c, e, and f.

231.7 24 251.7.1

Sync Channel support for Mobile Stations not capable of TD, but capable of QPCH or RC>2 Definition

26This test verifies that the mobile station is able to respond correctly to the new fields of Sync 27Channel Message sent by the base station if any, tune to appropriate CDMA channel and acquire 28the system successfully.

291.7.2
30(See[4])

Traceability

312.6.1.3 323.7.2.3.2.26

Sync Channel Acquisition Substate Sync Channel Message

15

1 11.7.3
2None

3GPP2 C.S0044-A v1.0 Call Flow Example(s)

31.7.4 41.7.4.1
5

Method of Measurement Base Station capable of Non-TD BCCH but not TD (Case 1)

Table 1.7.4-7 Frequency Allocation Case 1 Case 2 Case 3

CDMA_FREQ EXT_CDMA_FREQ SR1_CDMA_FREQ_NON_TD SR1_CDMA_FREQ_TD

7

1 2 3 N/A

1 2 N/A 4

1 2 3 4

8 9 10 11 12 13 14 15 16

a. b. c. d. e. f. g.

Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1. At the base station, Set Pilot PN offset to a certain value. Verify that the mobile station acquires the Forward pilot channel correctly. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.7.4-7. Verify that the mobile station tunes to CDMA Channel 3. Make a Mobile-Originated voice call and verify audio in both directions. End the call. Base Station capable of TD but not Non-TD BCCH (Case 2) Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1. At the base station, Set Pilot PN offset to a certain value. Verify that the mobile station acquires the Forward pilot channel correctly. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.7.4-7. Verify that the mobile station tunes to CDMA Channel 2. Make a Mobile-Originated voice call and verify audio in both directions. End the call.

171.7.4.2 18 19 20 21 22 23 24 25 26 2
a. b. c. d. e. f. g.

16

13GPP2 C.S0044-A v1.0 11.7.4.3 2 3 4 5 6 7 8 9 10

a. b. c. d. e. f. g. Base Station capable of Non-TD BCCH and TD (Case 3) Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1. At the base station, Set Pilot PN offset to a certain value. Verify that the mobile station acquires the Forward pilot channel correctly. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.7.4-7. Verify that the mobile station tunes to CDMA Channel 3. Make a Mobile-Originated voice call and verify audio in both directions. End the call. Minimum Standard Base Station capable of Non-TD BCCH but not TD (Case 1)

111.7.5 121.7.5.1

13The mobile station shall comply with steps c, e, and f.

141.7.5.2

Base Station capable of TD but not Non-TD BCCH (Case 2)

15The mobile station shall comply with steps c, e, and f.

161.7.5.3

Base Station capable of Non-TD BCCH and TD (Case 3)

17The mobile station shall comply with steps c, e, and f.

181.8 191.8.1

Sync Channel Support for Mobile Stations capable of TD and QPCH or RC>2 Definition

20This test verifies that the mobile station is able to respond correctly to the new fields of Sync 21Channel Message sent by the base station if any, tune to appropriate CDMA channel and acquire 22the system successfully.

231.8.2 252.6.1.3

Traceability

24(see [4])

Sync Channel Acquisition Substate Sync Channel Message

263.7.2.3.2.26 271.8.3
28None

Call Flow Example(s)

17

1 11.8.4 21.8.4.1 3
Method of Measurement Base Station capable of Non-TD BCCH but not TD (Case 1) Table 1.8.4-8 Frequency Allocation Case 1 Case 2 Case 3

3GPP2 C.S0044-A v1.0

Case 4

Case 5

CDMA_FREQ EXT_CDMA_FREQ SR1_CDMA_FREQ_NON_TD SR1_CDMA_FREQ_TD

1 2 3 N/A

1 2 N/A 4

1 2 N/A 4

14 2 3 4

1 2 3 4

4 5 6 7 8 9 10 11 12

a. b. c. d. e. f. g.

Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1. At the base station, Set Pilot PN offset to a certain value. Verify that the mobile station acquires the Forward pilot channel correctly. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.8.4-8. Verify that the mobile station tunes to CDMA Channel 3. Make a Mobile-Originated voice call and verify audio in both directions. End the call. Base Station capable of TD with the same TD mode as Mobile Station but not Non-TD BCCH (Case 2) Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1. At the base station, Set Pilot PN offset to a certain value. Verify that the mobile station acquires the Forward pilot channel correctly. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.8.4-8. Verify that the mobile station tunes to CDMA Channel 4. Make a Mobile-Originated voice call and verify audio in both directions. End the call.

131.8.4.2 14 15 16 17 18 19 20 21 22 23
a. b. c. d. e. f. g.

24 This is a pseudo frequency, no corresponding channel elements are needed.

18

13GPP2 C.S0044-A v1.0 11.8.4.3 2 3 4 5 6 7 8 9 10 11

a. b. c. d. e. f. g. Base Station capable of TD with different TD mode as Mobile Station but not Non-TD BCCH (Case 3) Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1. At the base station, Set Pilot PN offset to a certain value. Verify that the mobile station acquires the Forward pilot channel correctly. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.8.4-8. Verify that the mobile station tunes to CDMA Channel 2. Make a Mobile-Originated voice call and verify audio in both directions. End the call. Base Station capable of Non-TD BCCH and TD with the same TD mode as Mobile Station (Case 4) Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1. At the base station, Set Pilot PN offset to a certain value. Verify that the mobile station acquires the Forward pilot channel correctly. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.8.4-8. Verify that the mobile station tunes to CDMA Channel 4. Make a Mobile-Originated voice call and verify audio in both directions. End the call. Base Station capable of Non-TD BCCH and TD with a different TD mode as Mobile Station (Case 5) Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1. At the base station, Set Pilot PN offset to a certain value. Verify that the mobile station acquires the Forward pilot channel correctly. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.8.4-8. Verify that the mobile station tunes to CDMA Channel 3. Make a Mobile-Originated voice call and verify audio in both directions. End the call.

121.8.4.4 13 14 15 16 17 18 19 20 21 22
a. b. c. d. e. f. g.

231.8.4.5 24 25 26 27 28 29 30 31 32 33
a. b. c. d. e. f. g.

19

1 11.8.5 21.8.5.1
Minimum Standard Base Station capable of Non-TD BCCH but not TD (Case 1)

3GPP2 C.S0044-A v1.0

3The mobile station shall comply with steps c, e, and f.

41.8.5.2 5

Base Station capable of TD with the same TD mode as Mobile Station but not Non-TD BCCH (Case 2)

6The mobile station shall comply with steps c, e, and f.

71.8.5.3 8

Base Station capable of TD with different TD mode as Mobile Station but not Non-TD BCCH (Case 3)

9The mobile station shall comply with steps c, e, and f.

101.8.5.4 11

Base Station capable of Non-TD BCCH and TD with the same TD mode as Mobile Station (Case 4)

12The mobile station shall comply with steps c, e, and f.

131.8.5.5 14

Base Station capable of Non-TD BCCH and TD with a different TD mode as Mobile Station (Case 5)

15The mobile station shall comply with steps c, e, and f.

161.9 171.9.1

Hashing F-CCCH, F-CCCH slot Definition

18This test checks the ability to set and detect hashed F-CCCHs and F-CCCH Slots. The IMSIs 19effect on hashed F-CCCH and Slot is also checked.

201.9.2
21(See[4])

Traceability:

222.6.7.1 233.6.2.1.2 243.6.2.1.3 251.9.3

26None

Hash Function Common Channel Determination Paging Slot Determination

Call Flow Example(s)

271.9.4 281.9.4.1 29 30 31
a. b.

Methods of Measurement F-CCCH Number Hashing Connect the base station and mobile station as shown in Figure A-1. Configure the base station system with multiple F-CCCHs (maximum seven) in MC-RR Parameters Message.

20

13GPP2 C.S0044-A v1.0 1

c. Make a mobile terminated call, and verify audio in both directions. F-CCCH Slot Number Hashing Connect the base station and mobile station as shown in Figure A-4. Configure the base station system with slotted mode capability. Make a mobile terminated call, and verify audio in both directions. Minimum Standard F-CCCH Number Hashing

21.9.4.2 3 4 5
a. b. c.

61.9.5 71.9.5.1

8The mobile station shall comply with step c.

91.9.5.2

F-CCCH Slot Number Hashing

10The mobile station shall comply with step c.

111.10 CDMA Channel Hashing on F-PCH for Mobile Stations not capable of QPCH or RC>2 121.10.1 Definition
13This test checks the mobile stations ability to do CDMA Channel hashing based on different 14capability sets to select appropriate CDMA Channel and associated PCH.

151.10.2 Traceability
16(see [4])

172.6.2.2 182.6.2.2.12.1 192.6.7.1 203.6.2.1.1 213.7.2.3.2.28

Response to Overhead Information Operation Extended CDMA Channel List Message on Paging Channel Hash Function CDMA Channel Determination Extended CDMA Channel List Message

221.10.3 Call Flow Example(s)

23None

241.10.4 Methods of Measurement 251.10.4.1 Base Station incapable of BCCH and QPCH or RC>2 (Case 1) 26 27 28 29 30 31 2
a. b. c. Turn off all forms of autonomous registration at the base station. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 Paging Channel on each of the 2 CDMA channels. Verify that the base station sends an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=0, TD_SEL_INCL=0 and NUM_FREQ=0010 or a CDMA Channel List Message from the base station.

21

1 1
d.

3GPP2 C.S0044-A v1.0 Make a mobile terminated call, and verify audio in both directions.

21.10.4.2 Base Station incapable of BCCH, capable of QPCH or RC>2 with Extended CDMA 3 Channel List Message sent (Case 2) 4 5 6 7 8 9 10
a. b. c. Turn off all forms of autonomous registration at the base station. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 Paging Channel on each of the 2 CDMA channels. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=1, TD_SEL_INCL=0 and NUM_FREQ=0010 from the base station and make sure RC_QPCH_HASH_IND is set to 1 for freq 1 and 2. Make a mobile terminated call, and verify audio in both directions.

d.

111.10.5 Minimum Standard 121.10.5.1 Base Station incapable of BCCH and QPCH or RC>2 (Case 1)
13The mobile station shall comply with step d.

141.10.5.2 Base Station incapable of BCCH, capable of QPCH or RC>2 with Extended CDMA 15 Channel List Message sent (Case 2)
16The mobile station shall comply with step d.

171.11 CDMA Channel Hashing on F-PCH for Mobile Stations capable of QPCH or RC>2 181.11.1 Definition
19This test checks the mobile stations ability to do CDMA Channel hashing based on different 20capability sets to select appropriate CDMA Channel and associated PCH.

211.11.2 Traceability
22(see [4])

232.6.2.2 242.6.2.2.12.1 252.6.7.1 263.6.2.1.1 273.7.2.3.2.28

Response to Overhead Information Operation Extended CDMA Channel List Message on Paging Channel Hash Function CDMA Channel Determination Extended CDMA Channel List Message

281.11.3 Call Flow Example(s)

29None

22

13GPP2 C.S0044-A v1.0 11.11.4 Method of Measurement 21.11.4.1 Base Station incapable of BCCH and QPCH or RC>2 with Extended CDMA Channel 3 List Message sent (Case 1) 4 5 6 7 8 9
a. b. c. d. Turn off all forms of autonomous registration at the base station. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 Paging Channel on each of the 2 CDMA channels. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=0, TD_SEL_INCL=0 and NUM_FREQ=0010 from the base station. Make a mobile terminated call, and verify audio in both directions.

101.11.4.2 Base Station incapable of BCCH, capable of QPCH or RC>2 with Extended CDMA 11 Channel List Message sent (Case 2) 12 13 14 15 16 17 18
a. b. c. Turn off all forms of autonomous registration at the base station. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 Paging Channel on each of the 2 CDMA channels. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=1, TD_SEL_INCL=0 and NUM_FREQ=0010 from the base station and make sure RC_QPCH_HASH_IND is set to 1 for freq 1 and 2. Make a mobile terminated call, and verify audio in both directions.

d.

191.11.5 Minimum Standard 201.11.5.1 Base Station incapable of BCCH and QPCH or RC>2 with Extended CDMA Channel 21 List Message sent (Case 1)
22The mobile station shall comply with step d.

231.11.5.2 Base Station incapable of BCCH, capable of QPCH or RC>2 with Extended CDMA 24 Channel List Message sent (Case 2)
25The mobile station shall comply with step d.

261.12 CDMA Channel Hashing on F-BCCH; Mobile Station not capable of either TD or 27 QPCH (RC>2) 281.12.1 Definition
29This test checks the mobile stations ability to do CDMA Channel (frequency) hashing based on 30different capability sets to select appropriate CDMA Channels and associated primary BCCHs.

311.12.2 Traceability
32(see [4])

332.6.2.1.5

Primary Broadcast Control Channel Monitoring

23

1 12.6.2.2 22.6.2.2.12.2 32.6.7.1 43.6.2.1.1 53.7.2.3.2.28

Response to Overhead Information Operation

3GPP2 C.S0044-A v1.0

Extended CDMA Channel List Message On Primary Broadcast Control Channel Hash Function CDMA Channel Determination Extended CDMA Channel List Message

61.12.3 Call Flow Example(s)

7None

81.12.4 Method of Measurement 91.12.4.1 Base station operates without TD and QPCH, RC>2 (Case 1) 10 11 12 13 14 15
a. b. c. d. Turn off all forms of autonomous registration at the base station. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 primary BCCH on each of the 2 CDMA channels. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=0, TD_SEL_INCL=0 and NUM_FREQ=0010 from the base station. Make a mobile terminated call, and verify audio in both directions.

161.12.4.2 Base Station operates without TD (STS) but with QPCH (RC>2), (Case 2) 17 18 19 20 21 22 23
a. b. c. Turn off all forms of autonomous registration at the base station. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 primary BCCH on each of the 2 CDMA channels. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=1, TD_SEL_INCL=0 and NUM_FREQ=0010 from the base station and make sure RC_QPCH_HASH_IND is set to 1 for freq 1 and 2 Make a mobile terminated call, and verify audio in both directions.

d.

241.12.4.3 Base Station operates with TD (STS) and QPCH (RC>2) (Case 3) 25 26 27 28 29 30 31 32
a. b. c. Turn off all forms of autonomous registration at the base station. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 primary BCCH on each of the 2 CDMA channels. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=1, TD_SEL_INCL=1 and NUM_FREQ=0010 from the base station and make sure TD_HASH_IND is set to 1 for frequency 1 and RC_QPCH_HASH_IND is set to 1 for frequency 1 and 2. Make a mobile terminated call, and verify audio in both directions.

d.

24

13GPP2 C.S0044-A v1.0 11.12.5 Minimum Standard 21.12.5.1 Base station operates without TD and QPCH, RC>2 (Case 1)
3The mobile station shall comply with step d.

41.12.5.2 Base Station operates without TD (STS) but with QPCH (RC>2), (Case 2)
5The mobile station shall comply with step d.

61.12.5.3 Base Station operates with TD (STS) and QPCH (RC>2) (Case 3)
7The mobile station shall comply with step d.

81.13 CDMA Channel Hashing on F-BCCH; Mobile Station not capable of TD (STS) but 9 capable of QPCH (RC>2) 101.13.1 Definition
11This test checks the mobile stations ability to do CDMA Channel (frequency) hashing based on 12different capability sets to select appropriate CDMA Channels and associated primary BCCHs.

131.13.2 Traceability
14(see [4])

152.6.2.1.5 162.6.2.2 172.6.2.2.12.2 182.6.7.1 19 203.7.2.3.2.28

Primary Broadcast Control Channel Monitoring Response to Overhead Information Operation Extended CDMA Channel List Message On Primary Broadcast Control Channel Hash Function CDMA Channel Determination Extended CDMA Channel List Message

211.13.3 Call Flow Example(s)

22None

231.13.4 Method of Measurement 241.13.4.1 Base Station operates without TD (STS) and QPCH (RC>2) (Case 1) 25 26 27 28 29 30
a. b. c. d. Turn off all forms of autonomous registration at the base station. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 primary BCCH on each of the 2 CDMA channels. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=0, TD_SEL_INCL=0 and NUM_FREQ=0010 from the base station. Make a mobile terminated call, and verify audio in both directions.

25

3GPP2 C.S0044-A v1.0

11.13.4.2 Base Station operates without TD (STS) but with QPCH (RC>2) (Case 2) 2 3 4 5 6 7 8
a. b. c. Turn off all forms of autonomous registration at the base station. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 primary BCCH on each of the 2 CDMA channels. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=1, TD_SEL_INCL=0 and NUM_FREQ=0010 from the base station and make sure RC_QPCH_HASH_IND is set to 1 for freq 1 and 2. Make a mobile terminated call, and verify audio in both directions.

d.

91.13.4.3 Base Station operates with TD (STS) and QPCH (RC>2) (Case 3) 10 11 12 13 14 15 16 17
a. b. c. Turn off all forms of autonomous registration at the base station. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 primary BCCH on each of the 2 CDMA channels. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=1, TD_SEL_INCL=1 and NUM_FREQ=0010 from the base station and make sure TD_HASH_IND is set to 1 for frequency 1 and RC_QPCH_HASH_IND is set to 1 for frequencies 1 and 2. Make a mobile terminated call, and verify audio in both directions.

d.

181.13.5 Minimum Standard 191.13.6 Base Station operates without TD (STS) and QPCH (RC>2) (Case 1)
20The mobile station shall comply with step d.

211.13.7 Base Station operates without TD (STS) but with QPCH (RC>2) (Case 2)
22The mobile station shall comply with step d.

231.13.8 Base Station operates with TD (STS) and QPCH (RC>2) (Case 3)
24The mobile station shall comply with step d.

251.14 CDMA Channel Hashing on F-BCCH; Mobile Station capable of both TD (STS) and 26 QPCH (RC>2) 271.14.1 Definition 28This test checks the mobile stations ability to do CDMA Channel (frequency) hashing based on 29different capability sets to select appropriate CDMA Channels and associated primary BCCHs. 301.14.2 Traceability
31(see [4])

322.6.2.1.5 332.6.2.2 2

Primary Broadcast Control Channel Monitoring Response to Overhead Information Operation 26

13GPP2 C.S0044-A v1.0 12.6.2.2.12.2 22.6.7.1 33.6.2.1.1 43.7.2.3.2.28

Extended CDMA Channel List Message On Primary Broadcast Control Channel Hash Function CDMA Channel Determination Extended CDMA Channel List Message

51.14.3 Call Flow Example(s)

6None

71.14.4 Method of Measurement

8None

91.14.4.1 Base Station operates without TD (STS) and QPCH (RC>2) (Case 1) 10 11 12 13 14 15
a. b. c. d. Turn off all forms of autonomous registration at the base station. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 primary BCCH on each of the 2 CDMA channels. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=0, TD_SEL_INCL=0 and NUM_FREQ=0010 from the base station. Make a mobile terminated call, and verify audio in both directions.

161.14.4.2 Base Station operates without TD (STS) but with QPCH (RC>2) (Case 2) 17 18 19 20 21 22 23
a. b. c. Turn off all forms of autonomous registration at the base station. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 primary BCCH on each of the 2 CDMA channels. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=1, TD_SEL_INCL=0 and NUM_FREQ=0010 from the base station and make sure RC_QPCH_HASH_IND is set to 1 for frequency 1 and 2. Make a mobile terminated call, and verify audio in both directions.

d.

241.14.4.3 Base Station operates with TD (STS) and QPCH (RC>2) (Case 3) 25 26 27 28 29 30 31 32
a. b. c. Turn off all forms of autonomous registration at the base station. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 primary BCCH on each of the 2 CDMA channels. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=1, TD_SEL_INCL=1 and NUM_FREQ=0010 from the base station and make sure TD_HASH_IND is set to 1 for frequency 1 and 2, RC_QPCH_HASH_IND is set to 1 for all the frequencies. Make a mobile terminated call, and verify audio in both directions.

d.

27

1 11.14.5 Minimum Standard

3GPP2 C.S0044-A v1.0

21.14.5.1 Base Station operates without TD (STS) and QPCH (RC>2) (Case 1)
3The mobile station shall comply with step d.

41.14.5.2 Base Station operates without TD (STS) but with QPCH (RC>2) (Case 2)
5The mobile station shall comply with step d.

61.14.5.3 Base Station operates with TD (STS) and QPCH (RC>2) (Case 3)
7The mobile station shall comply with step d.

81.15 F-CCCH SUPPORT 91.15.1 Definition

10This test checks the mobile stations ability to process messages (L2 ACK, Extended Channel 11Assignment Message) sent over F-CCCH correctly.

121.15.2 Traceability
13(see [4])

142.6.2.1.1 152.6.2.1.1.4 162.6.3.1.8

Forward Channel Monitoring Procedures Common Channel Supervision Paging Channel and Forward Common Control Channel Monitoring

171.15.3 Call Flow Example(s)

18None

191.15.4 Method of Measurement 20 21 22 23 24

a. b. c. d. Connect the base station and mobile station as shown in Figure A-3. Instruct the mobile station originate a voice call. Verify the base station respond with a Layer 2 ACK and Extended Channel Assignment Message over F-CCCH. Verify the mobile station can set up the traffic channel for this voice call correctly.

251.15.5 Minimum Standard

26The mobile station shall comply with step d.

271.16 Paging Indicator on the Quick Paging Channel 281.16.1 Definition

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

28

13GPP2 C.S0044-A v1.0

1The mobile station shall hash to the correct paging indicator positions. The mobile station shall 2monitor its assigned Paging Channel or F-CCCH slot immediately following its assigned Quick 3Paging Channel slot if the mobile station does not detect that at least one of the paging indicators 4is set to OFF. Therefore, if the mobile station detects zero, one or two ON in the hashed 5paging indicators without detecting an OFF, the mobile station will monitor its assigned Paging 6Channel or F-CCCH slot5. It is assumed that if the mobile station hashes to the wrong paging 7indicator positions and detected an OFF, the mobile station would likely miss the assigned 8Paging Channel or the F-CCCH slot.

91.16.2 Traceability:
10(See[4])

112.6.2.1.2 122.6.7.1 132.7.1.3.2.1 143.6.2.5 153.7.2.3.2.13 163.7.2.3.2.31

Quick Paging Channel Monitoring Procedures. Hash Function Registration Message Quick Paging Channel Processing Extended System Parameters Message MC-RR-Parameters Message

171.16.3 Call Flow Example(s)

18
MS Common Channels The MS hash to QPI positions and detect its QPI on in the Assigned QPCH Slot. Then the MS start receiving on its assigned F-PCH or F-CCCH slots Turn on/off PI on Quick Paging Channel for the MS assigned QPCH Slot BS Common Channels

Registration Request order Registration Message

19 201.16.4 Method of Measurement 21

a. Connect the mobile station to the base station as shown in Figure A-3.

25 Although the mobile station will monitor the Paging Channel or the F-CCCH when the paging 3indicator is detected as ON (without detecting an OFF), there are other reasons the mobile 4station may monitor the Paging Channel or the F-CCCH even if the mobile station does not detect 5an ON for the paging indicators. For example, the mobile station may not operate the QPCH 6properly such that neither ON nor OFF is detected or the mobile stations threshold for 7detecting the paging indicators is set too high. Even if the mobile station hashes to the wrong 8paging indicator positions and detected an OFF there is no requirement that the mobile station 9shall not monitor the Paging Channel or the F-CCCH. 10
29

1 1 2
3

3GPP2 C.S0044-A v1.0 b. Set the values in the Extended System Parameters Message or MC-Parameters Message as follows:

Fields QPCH_SUPPORTED NUM_QPCH QPCH_RATE QPCH_POWER_LEVEL_PAGE

Values '1' (QPCH is supported) '01' (Number of the QPCH) '0' (4800 bps QPCH data rate) '101' (same as pilot channel)

4 5 6 7 8 9 10 11 12 13

c. d.

Allow the mobile station to begin monitoring the QPCH. Instruct the base station to send a mobile station directed message (i. e. General Page Message or Registration Request Order) in the mobile stations assigned Paging Channel or F-CCCH slot. Verify that the base station sets the paging indicator positions associated with the mobile station to ON in the Quick Paging Channel slot corresponding to the Paging Channel or F-CCCH slot in which the mobile station directed message is sent in step d. Ensure the base station sets the other paging indicator positions to OFF. Verify the mobile station correctly responds to the message directed to it in step d. Repeat steps b through f with the QPCH_RATE set to 1 (9600 bps).

e.

f. g.

141.16.5 Minimum Standard

15The mobile station shall comply with step f. The base station shall comply with step e.

30

13GPP2 C.S0044-A v1.0 12 22.1 32.1.1

BASIC CALL PROCESSING TESTS

Mobile Originated Voice Calls Definition

4This tests voice service negotiation and call completion of mobile originated voice calls, for radio 5configurations and voice service options supported by the mobile and base station.

62.1.2
7(see[4])

Traceability

82.2.6.2.5 92.6.3.5 102.6.4 112.7.1.3.2.4 122.7.2.3.2.15 133.6.3.5 143.6.4 153.7.2.3.2.21 163.7.3.3.2.3 173.7.3.3.2.20 182.7.2.3.2.12 192.7.2.3.2.13 202.7.2.3.2.14 212.7.4.18

Mobile Station Origination Operation Mobile Station Origination Attempt Substate Mobile Station Control on the Traffic Channel State Origination Message Service Option Control Message Response to Origination Message Traffic Channel Processing Extended Channel Assignment Message Alert With Information Message Service Connect Message Service Request Message Service Response Message Service Connect Completion Message Service Configuration Record

1 12.1.3
Call Flow Example(s)

3GPP2 C.S0044-A v1.0

MS
Origination Message (SO, RCs proposed) Order Message (acknowledgement from base station) Extended Channel Assignment Message (DEFAULT_CONFIG, GRANTED_MODE, RCs) initial service configuration possible service negotiation Service Connect Message Service Configuration Record (SO, RCs) possible new service configuration Service Connect Completion Message Voice Traffic

BS
common channels

dedicated channels

release order messages common channels

2 32.1.4 4 5 6 7 8
Item 1 2 3 4 5 6 7 a. b. c. Method of Measurement Configure the base station for desired voice service negotiation listed in Table 2.1.4-2. Allow the mobile to come to the idle state on the base station. Make a mobile originated voice call, and record the call setup messages listed in Table 2.1.4-9. Table 2.1.4-9 Messages in Mobile Originated Call Setup Message Origination Message Extended Channel Assignment Message Status Request Message Status Response Message Service Request Message Service Response Message Service Connect Message

13GPP2 C.S0044-A v1.0

8
1

Service Connect Complete Message

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

d. e.

Verify SERVICE_OPTION, FOR_RC_PREF, and REV_RC_PREF proposed in the Origination Message correspond to the mobile configuration settings. Verify DEFAULT_CONFIG, GRANTED_MODE, FOR_RC, and REV_ RC in the Extended Channel Assignment Message corresponds to the base station configuration for service negotiation. Verify service negotiation used in Service Request Message, Service Response Message, and Service Connect Message proceed as desired. Verify the SERVICE_OPTION, FOR_FCH_RC, and REV_FCH_RC in the last Service Configuration Record corresponds to the desired outcome of the base station service negotiation configuration, and the call completes successfully. End the call. Repeat steps a through h for all supported configurations of mobile originated voice service negotiation as supported by the mobile station and base station. This may include call completion with the service configurations in Table 2.1.4-2. Table 2.1.4-2 Service Configurations for Mobile Originated Voice Calls Voice Service Option 3 17 or 32768 3 3 17 or 32768 4 5 Forward Radio Configuration 1 2 3 Reverse Radio Configuration 1 2 3 3 4

f. g.

h. i.

17

182.1.5

Minimum Standard

19The mobile station and the base station shall comply with step d, e, f, g, and i.

202.2 212.2.1

Mobile Station Terminated Voice Calls Definition

22This tests voice service negotiation and call completion of mobile station terminated voice calls, 23for radio configurations and voice service options supported by the mobile station and base 24station.

1 12.2.2
2(see[4])

3GPP2 C.S0044-A v1.0 Traceability

32.7.1.3.2.5 42.6.4 52.7.2.3.2.15 63.6.4 73.7.2.3.2.21 83.7.3.3.2.20 93.7.3.3.2.20 102.7.2.3.2.12 112.7.2.3.2.13 122.7.2.3.2.14 132.7.4.18 142.2.3

Page Response Message Mobile Station Control on the Traffic Channel State Service Option Control Message Traffic Channel Processing Extended Channel Assignment Message Service Connect Message Service Connect Message Service Request Message Service Response Message Service Connect Completion Message Service Configuration Record

Call Flow Example(s)

MS
General Page Message (SO proposed) Page Response Message (SO, RCs proposed) Extended Channel Assignment Message (DEFAULT_CONFIG, GRANTED_MODE, RCs) initial service configuration possible service negotiation Service Connect Message Service Configuration Record (SO, RCs) possible new service configuration Service Connect Completion Message Voice Traffic

BS
common channels

dedicated channels

Release Order Messages common channels

15

13GPP2 C.S0044-A v1.0 12.2.4 2 3 4 5 6 7 8

Item 1 2 3 4 5 6 7 8 9
9

Method of Measurement Configure the base station for desired SERVICE_OPTION for the General Page Message or Universal Page Message, and desired service negotiation listed in Table 2.2.4-2. Allow the mobile station to come to the idle state on the base station. Make a mobile station terminated voice call, and record the call setup messages listed in Table 2.2.4-10. Table 2.2.4-10 Messages in Mobile Station Terminated Call Message General Page Message or Universal Page Message Page Response Message Extended Channel Assignment Message Status Request Message Status Response Message Service Request Message Service Response Message Service Connect Message Service Connect Complete Message

a.

b. c.

10 11 12 13 14 15 16 17 18 19 20 21 22

d. e.

Verify the SERVICE_OPTION proposed in the General Page Message corresponds to the base station configuration setting. Verify SERVICE_OPTION, FOR_RC_PREF, and REV_RC_PREF proposed in the Origination/Page Response Message correspond to the mobile station configuration settings. Verify DEFAULT_CONFIG, GRANTED_MODE, FOR_RC, and REV_RC in the Extended Channel Assignment Message correspond to the base station configuration. Verify that service negotiation using in Service Request Message, Service Response Message, and Service Connect Message proceed as desired. Verify the SERVICE_OPTION, FOR_FCH_RC, and REV_FCH_RC in the last Service Configuration Record corresponds to the desired outcome of the base station service negotiation configuration, and the call completes successfully. End the call.

f. g. h.

i.

1 1 2 3
j.

3GPP2 C.S0044-A v1.0 Repeat steps a through i for all supported configurations of mobile station terminated voice service negotiation as supported by the mobile station and base station. This may include call completion with the service configurations in Table 2.2.4-2.

4 Table 2.2.4-2 Minimum Service Combinations for Mobile station Terminated Voice Calls
Service Option 3 17 or 32768 3 3 17 or 32768
5

Forward Radio Configuration 1 2 3 4 5

Reverse Radio Configuration 1 2 3 3 4

62.2.5

Minimum Standard

7The mobile station and the base station shall comply with steps d, e, f, g, h, and j.

82.3 92.3.1

Busy Tone Definition

10This tests the mobile station response to a called-party-busy notification from a base station.

112.3.2
12(see[4])

Traceability

132.6.4.4 143.6.4.3 153.7.5

Release Substate Traffic Channel Substate Information Records

16Table 3.7.5.5-3 Tone Signals 172.3.3

18None

Call Flow Example(s)

192.3.4 20 21 22 23
a. b. c.

Method of Measurement Allow the mobile station to come to the idle state on the base station. Ensure the called party has no call-waiting or automatic voice mail enabled, and tie up the line so that the mobile station will get a busy signal when it calls. Attempt a mobile station originated call to the party.

13GPP2 C.S0044-A v1.0 1

d. Verify the mobile station plays a called-party-busy indication. Minimum Standard

22.3.5

3The mobile station shall comply with the requirement in steps d.

42.4 52.4.1

Mobile Station Origination Call with Inter Band Channel Assignment Definition

6This test verifies that the mobile station can initiate a call to a land party on aone band class and 7then re-originate and completes the call the target band class after receiving a Channel 8Assignment Message or Extended Channel Assignment Message with ASSIGN_MODE = 101 9or 001 respectively.

102.4.2
11(See[4])

Traceability:

122.6.2.4 132.6.3.5 142.7.1.3.2.4 153.7.2.3.2.8 163.7.2.3.2.21 172.4.3

18None

Mobile Station Order and Message Processing Operation Mobile Station Origination Attempt Substate Origination Message Channel Assignment Message Extended Channel Assignment Message

Call Flow Example(s)

192.4.4 20 21 22 23 24 25 26 27 28 29 30 31 32 33
a. b. c. d. e.

Method of Measurement Connect the mobile station and base stations as shown in Figure A-2. Base station 1 operates in a band class that is different from base station 2. Ensure the mobile station acquires base station 1. Configure Base station 1 so that Inter Band Channel Assignment is enabled. Setup mobile station originated voice call. Verify the mobile station originates on the serving base station and receives a Channel Assignment Message with ASSIGN MODE=101 or an Extended Channel Assignment Message with ASSIGN MODE=001. Verify that the Channel Assignment Message or Extended Channel Assignment Message contains assignment for paging channel on base station 2, and RESPOND=1. Verify the mobile station re-sends a second Origination Message to base station 2 and the call completes successfully. Verify user data in both directions. End the call.

f. g. h.

1 1 2 3 4
i.

3GPP2 C.S0044-A v1.0 Repeat Steps d through g, but provision Base station 2 to be Inter Band Channel Assignment enabled. The mobile station will originate on base station 2 and then reoriginate on base station 1 after receiving the Channel Assignment Message or Extended Channel Assignment Message. Minimum Standard

52.4.5

6The mobile station and base station shall comply with steps e, f, g, and i.

72.5 82.5.1

Mobile Station Terminated Call with Inter Band Channel Assignment Definition

9This test verifies that the mobile station can receive a call from a land party on one band class 10and then resends the Page Response Message autonomously and completes the call on the 11target band class after receiving a Channel Assignment Message or Extended Channel 12Assignment Message with ASSIGN_MODE = 101 or 001 respectively.

132.5.2
14(See[4])

Traceability

152.6.2.3 162.6.3.3 172.7.1.3.2.5 183.7.2.3.2.8 193.7.2.3.2.21 202.5.3

21None

Mobile Station Page Match Operation Page Response Substate Page Response Message Channel Assignment Message Extended Channel Assignment Message

Call Flow Example(s)

222.5.4 23 24 25 26 27 28 29 30 31 32 33 34
a. b. c. d. e.

Method of Measurement Connect the mobile station and base stations as shown in Figure A-2. Base station 1 operates in a band class that is different from base station 2. Ensure the mobile station acquires base station 1. Configure base station 1 so that Inter Band Channel Assignment is enabled. Setup mobile station terminated voice call. Verify that the mobile station receives a Channel Assignment Message with ASSIGN MODE=101 or an Extended Channel Assignment Message with ASSIGN MODE=001. Verify that the Channel Assignment Message or Extended Channel Assignment Message contains assignment for paging channel on base station 2, and RESPOND = 1. Verify the mobile station sends a second Page Response Message on the target base station and the call completes.

f.

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7

g. h. i. Verify user data in both directions. End the call. Repeat Steps d through g, but provision Base station 2 to be Inter Band Channel Assignment enabled. The mobile station will send the Page Response Message on base station 2 and then re-send the Page Response Message on base station 1 after receiving the Channel Assignment Message or Extended Channel Assignment Message. Minimum Standard

82.5.5

9The mobile station and the base station shall comply with steps e, f, g, and i.

102.6 112.6.1

DTMF Definition

12This is a test for Dual-Tone Multi-frequency (DTMF), sent by the mobile station in a Send Burst 13DTMF Message or a Continuous DTMF Tone Order. It verifies that sequencing and tone duration 14of the Send Burst DTMF Message and the Continuous DTMF Tone Order are preserved.

152.6.2

Traceability

16(see [4])

172.7.2.3.2.7 182.7.2.3.2.1 193.7.3.3.2.9 20Table 2.7.1.3.2.4-4 21Table 2.7.2.3.2.7-1 22Table 2.7.2.3.2.7-2 23Table 3.7.4-1 24Table 2.7.2.3-1 252.6.3
26None

Send Burst DTMF Message Continuous DTMF Tone Order Send Burst DTMF Message Representation of DTMF Digits Recommended DTMF Pulse Width Recommended Minimum Inter-digit Interval Order and Order Qual Codes Used on the f-csch and the f-dsch Messages on r-dsch

Call Flow Example(s)

272.6.4 28 29 30 31 32 33
a. b. c. d.

Method of Measurement Equip a landline with a DTMF decoder that can verify DTMF digits received and DTMF tone duration. Configure the mobile station to send short DTMF tones. Allow the mobile station to come to the idle state on the base station, and set up a voice call to the equipped land party. Press the keys 1234567890*#.

1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
k. l. e. f. g. h. i. j.

3GPP2 C.S0044-A v1.0 Verify the mobile station sends a Send Burst DTMF Message for each key press. Verify DTMF tones are received correctly. End the call. Configure the mobile station to use long DTMF tones. Setup a mobile station originated call. Direct the mobile station to perform the following steps in. 1. Press and hold any number key on the keypad for approximately 5 seconds. 2. Verify the mobile station sends a Continuous DTMF Tone Order with the appropriate ORDQ value to start and stop the DTMF tone. 3. Direct the mobile station to send characters 0123456789 * as one or more Send Burst DTMF Message(s). 4. Press and hold any number key on the keypad for approximately 5 seconds. 5. Again press and hold any number key on the keypad for approximately 5 seconds. Verify all DTMF digits are decoded correctly and in the right order at the land party DTMF decoder. Verify the three 5-second key presses produce DTMF tones approximately 5 seconds in duration. Minimum Standard

192.6.5

20The mobile station shall comply with requirements in steps e, f, k and l.

212.7 222.7.1

Slot Cycle Index Definition

23If the mobile station supports slotted operation, this test verifies the mobile station response to the 24base station MAX_SLOT_CYCLE_INDEX setting for various settings of mobile station 25SLOT_CYCLE_INDEX.

262.7.2

Traceability

27(see [4])

282.6.2.1.1 293.6.2.1.3 303.6.2.3 312.7.1.3.2.1 322.7.1.3.2.4 332.7.1.3.2.5

Forward Channel Monitoring Procedures Paging Slot Determination Mobile Station Directed Messages Registration Message Origination Message Page Response Message

10

13GPP2 C.S0044-A v1.0 12.7.4.7 22.7.3

3None

Terminal Information Call Flow Example(s)

42.7.4 5 6 7 8
a.

Method of Measurement Configure the mobile station internal setting of SLOT_CYCLE_INDEXP and also base station System Parameter Message or MC-RR Parameters Message setting of MAX_SLOT_CYCLE_INDEX in the first row in Table 2.7.4-11. Table 2.7.4-11 Mobile station and Base Station Settings for Slot Cycle Index Test

Test_ID

MAX_SLOT_CYCLE _INDEX (base station) 2 2 2 2 3

SLOT_CYCLE _INDEXP (mobile station) 0 1 2 3 3

Slot Cycle Index Used 0 1 2 2 3

Slot Cycle Length, seconds 1.28 2.56 5.12 5.12 10.14

1 2 3 4 5

9 10 11 12 13 14 15 16

b. c. d. e. f.

Allow the mobile station to come to the idle state in slotted mode on the base station. Examine that the mobile station wakes up in the assigned slots to read the Paging Channel at the interval of the Slot Cycle Length in Table 2.7.4-11. Make a mobile station terminated call, verify the base station pages the mobile station in the appropriate slot. Verify the call completes successfully. Repeat steps a through d for each of the other row Test ID combinations in Table 2.7.411. Minimum Standard

172.7.5

18The mobile station and the base station shall comply with requirements in steps c, d, e and f.

192.8 202.8.1

Reverse Radio Link Failure Definition

21This tests mobile stations response to a 15 second loss of the reverse RF link in the conversation 22state.

11

1 12.8.2 2 33.7 4(see [3]) 5Table 2.2.1.1.3-1 62.2.1.1.2.2 72.8.3

Accumulated ARQ Statistics for Regular PDUs Traceability (see [6]) Supervision

3GPP2 C.S0044-A v1.0

Requirements for Transmission and Retransmission Procedures

Call Flow Example(s)

MS
Origination Message Order Message (acknowledgement from base station)

BS
common channels

Extended Channel Assignment Message initial service configuration possible service negotiation Service Connect Message possible new service configuration Service Connect Complete Message dedicated channels

Voice Traffic

8 92.8.4 10 11 12
a. Method of Measurement Configure a test setup with a connection of a single base station and the mobile station to allow the reverse radio link to be abruptly attenuated or interfered-with, enough to cause continuous loss of all reverse frames as exemplified in Figure 2-1

12

13GPP2 C.S0044-A v1.0

Forward Link

Fixed Atten

Duplexer Reverse Link

Duplexer

Vari Atten AWGN

base station 1 CDMA Analyzer Diagnostic and Control Tool 1 2 3 4 5 6 7 8 9

b. c. d. e. f. g. h.

Mobile

Figure 2-1 Test Setup for Radio Link Failure Configure the setup for good RF links as specified in ANNEX B. Allow the mobile station to come to the idle state on the base station. Attempt a mobile station originated call. Abruptly cause loss of the reverse RF link after voice call is established. Restore the normal RF link after a minimum of 15 seconds. Verify the call is released. Verify the mobile station returns to the idle state on the base station. Minimum Standard

102.8.5

11The mobile station shall comply with the requirements in steps g and h.

122.9 132.9.1

Channel Assignment from CDMA to Analog Definition

14This test will verify that a base station assigns a mobile station to analog (e.g. AMPS) when no 15CDMA traffic channels are available.

162.9.2

Traceability

17(see [4])

182.6.1.1.2 192.6.3.5 202.9.3

21None

System Selection Using Current Redirection Criteria Mobile Station Origination Attempt Substate

Call Flow Example(s)

222.9.4 23
a.

Method of Measurement Connect the base station and mobile station as shown in Annex A Figure A - 5.

13

1 1 2 3 4 5 6 7 8 9 10
b.

3GPP2 C.S0044-A v1.0 Take all CDMA traffic channel radio resources out of service or configure the base station to behave in a similar fashion. Configure the base station to assign analog channel. Setup a mobile station originated call. Verify that the base station sends a Channel Assignment Message or Extended Channel Assignment Message with ASSIGN_MODE=011 to assign the mobile station an analog voice channel or with ASSIGN_MODE=010 to acquire the analog system. Verify the mobile station acquires the analog system. Verify user data in both directions. End call. Minimum Standard

c. d.

e. f. g.

112.9.5

12The mobile station and the base station shall comply with the requirements in steps d, e, and f.

132.10 Network Busy 142.10.1 Definition

15This tests mobile station response to a base station blocking condition during mobile station call 16origination.

172.10.2 Traceability
18(see [4])

19Table 3.7.4-1 203.6.2.3 21Table 3.7.5.5-3 223.6.3.5 233.6.2.3

Order and Order Qualification Codes Mobile Station Directed Messages, Reorder Order Tone Signals Response to Origination Message Mobile Station Directed Messages

242.10.3 Call Flow Example(s)

25None

262.10.4 Method of Measurement 27 28 29 30 31

a. b. c. d. Allow the mobile station to come to the idle state on the base station. Take all traffic channel resources out of service or configure the base station to behave in a similar fashion. Configure the base station to send a network-busy indication. Attempt a mobile station originated call. Instruct the base station to send a Reorder Order to the mobile station.

14

13GPP2 C.S0044-A v1.0 1 2 3 4 5

e. Verify the mobile station indicates a call failure due to network-busy, (e.g. For voice service options, the mobile station will play a reorder tone ). Note any anomalies in the mobile station behavior due to receiving the Reorder Order.. Steps a through e may be repeated for different service options supported such as service option 33.

f.

62.10.5 Minimum Standard

7The mobile station shall comply with the requirements in step e for all tested service options.

82.11 Release Order on the Access Channel 92.11.1 Definition

10This test verifies the mobile station can send a Release Order on the Access Channel during call 11origination before switching to dedicated channel transmission.

122.11.2 Traceability
13(see [4])

143.6.3 153.6.3.4 162.6.3 172.6.3.1.4 182.6.3.5 192.1.1.2.2.1

Access Channel Processing Response to Orders System Access State System Access State Exit Procedures Mobile Station Origination Attempt Substate Overview of Transmission and Retransmission Procedures (see [3])

202.11.3 Call Flow Example(s)

MS
Origination Message Ack Order Release Order Order

BS
Common Channels

21 222.11.4 Method of Measurement 23 24 25 26 27

a. b. c. Allow the mobile station to come to the idle state on the base station. Attempt a mobile station originated call. Shortly after the mobile station has received acknowledgement of its Origination Message, terminate the call attempt from the mobile station side, e. g. press the mobile station END key, before the mobile station switches to dedicated channel transmission.

15

1 1 2 3
d.

3GPP2 C.S0044-A v1.0 Verify the mobile station sends a Release Order (normal release) on the Access Channel in assured mode requiring confirmation of delivery, aborts the call attempt, and returns to the idle state on the base station.

42.11.5 Minimum Standard

5The mobile station shall comply with the requirements in step d.

62.12 True IMSI Support, Land Party to Mobile Station Call, Matching MCC and IMSI_11_12, 7 True IMSI addressing supported by the base station and mobile station 82.12.1 Definition
9This test verifies that the base station pages the mobile station with True IMSI addressing 10supported by the base station and mobile station when the MCC and IMSI_11_12 of the mobile 11station match those sent by the base station in the Extended System Parameters Message or 12ANSI-41 System Parameters Message.

132.12.2 Traceability
14(See[4])

152.3.1.1 162.3.1 172.3.1.3 182.6.2.2.5 192.7.4.24 203.7.2.3.2.13

Encoding of IMSI_M_S and IMSI_T_S Mobile Station Identification Number Encoding of the MCC_M and MCC_T Extended System Parameters Message IMSI_T Service Response Message

212.12.3 Call Flow Example(s)

22None

232.12.4 Method of Measurement 24 25 26 27 28 29 30 31 32 33 34 2

a. b. Allow the mobile station to come to the idle state on the base station. Ensure the mobile station is programmed with the same values of MCC and IMSI_11_12 used in the base station. Do not use MCC (wild card) value in the base station. Configure the base station to send the Extended System Parameters Message or ANSI-41 System Parameters Message with the value IMSI_T_SUPPORTED=1. Enable power-up registration. Enable authentication. Configure the base station to disallow mobile station terminated calls if authentication fails. Power on the mobile station and wait for power-up registration to occur. Initiate a land party to mobile station call.

c. d. e. f. g.

16

13GPP2 C.S0044-A v1.0 1

h. Verify user data in both directions and end call at the mobile station.

22.12.5 Minimum Standard

3The mobile station shall comply with step h.

42.13 True IMSI Support, Land Party to Mobile Station Call, Matching MCC and IMSI_11_12, 5 True IMSI addressing supported by the base station with MIN-based addressing 6 supported by the mobile station. 72.13.1 Definition
8This test verifies that the base station pages the mobile station with True IMSI addressing 9supported by the base station and MIN-based addressing supported by the mobile station when 10the MCC and IMSI_11_12 of the mobile station match those sent by the base station in the 11Extended System Parameter Message or ANSI-41 System Parameters Message.

122.13.2 Traceability
13(see [4])

142.3.1.1 152.3.1 162.3.1.3 172.6.2.2.5 182.7.4.24 193.7.2.3.2.13

Encoding of IMSI_M_S and IMSI_T_S Mobile Station Identification Number Encoding of the MCC_M and MCC_T Extended System Parameters Message IMSI_T Service Response Message

202.13.3 Call Flow Example(s)

21None

222.13.4 Method of Measurement 23 24 25 26 27 28 29 30 31 32 33

a. b. Allow the mobile station to come to the idle state on the base station. Ensure the mobile station is programmed with the same values of MCC and IMSI_11_12 used in the base station. Do not use MCC (wild card) value in the base station. Configure the base station to send the Extended System Parameters Message or ANSI-41 System Parameters Message with the value IMSI_T_SUPPORTED=1. Enable power on registration. Enable authentication. Configure the base station to disallow mobile station terminated calls if authentication fails. Power on the mobile station and wait for power-up registration to occur. Initiate a land party call to the mobile station.

c. d. e. f. g.

17

1 1
h. Verify user data and end call at the mobile station.

3GPP2 C.S0044-A v1.0

22.13.5 Minimum Standard

3The mobile station shall comply with step h.

42.14 True IMSI Support, Land Party to Mobile Station Call, Matching MCC and IMSI_11_12, 5 True IMSI addressing not supported by the base station 62.14.1 Definition
7This test will verify the base station pages the mobile station when the base station does not 8support True IMSI addressing, when the MCC and IMSI_11_12 of the mobile station match those 9sent by the base station in the Extended System Parameters Message or ANSI-41 System 10Parameters Message.

112.14.2 Traceability
12(see [4])

132.3.1.1 142.3.1 152.3.1.3 162.6.2.2.5 172.7.4.24 183.7.2.3.2.13

Encoding of IMSI_M_S and IMSI_T_S Mobile Station Identification Number Encoding of the MCC_M and MCC_T Extended System Parameters Message IMSI_T Service Response Message

192.14.3 Call Flow Example(s)

20None

212.14.4 Method of Measurement 22 23 24 25 26 27 28 29 30 31 32 33

a. b. Allow the mobile station to come to the idle state on the base station. Ensure the mobile station is programmed with the same values of MCC and IMSI_11_12 used in the base station. Do not use MCC (wild card) value in the base station. Configure the base station to send the Extended System Parameters Message or ANSI-41 System Parameters Message with the value IMSI_T_SUPPORTED=0. Enable power on registration. Enable authentication. Configure the base station to disallow mobile station terminated calls if authentication fails. Power on the mobile station and wait for power-up registration to occur. Initiate a land party call to the mobile station. Verify user data and end call at the mobile station.

c. d. e. f. g. h.

18

13GPP2 C.S0044-A v1.0 12.14.5 Minimum Standard

2The mobile station shall comply with step h.

32.15 True IMSI Support, Land Party to Mobile Station Call, Different MCC and IMSI_11_12 42.15.1 Definition
5This test verifies the base station selects one of the valid forms of paging channel address when 6neither the MCC nor the IMSI_11_12 of the mobile station being addressed match those being 7sent by the base station in the Extended System Parameters Message or ANSI-41 System 8Parameters Message.

92.15.2 Traceability
10(see [4])

112.3.1.1 122.3.1 132.3.1.3 142.6.2.2.5 152.7.4.24 163.7.2.3.2.13

Encoding of IMSI_M_S and IMSI_T_S Mobile Station Identification Number Encoding of the MCC_M and MCC_T Extended System Parameters Message IMSI_T Service Response Message

172.15.3 Call Flow Example(s)

18None

192.15.4 Method of Measurement 20 21 22 23 24 25 26 27 28 29 30 31

a. b. Allow the mobile station to come to the idle state on the base station. Ensure the mobile station is programmed with different values of MCC and IMSI_11_12 than those used in the base station. Do not use MCC (wild card) value in the base station. Configure the base station to send the Extended System Parameters Message or ANSI-41 System Parameters Message with the value IMSI_T_SUPPORTED=1. Enable power on registration. Enable authentication. Configure the base station to disallow mobile station terminated calls if authentication fails. Power on the mobile station and wait for power-up registration to occur. Initiate a land party call to the mobile station. Verify user data and end call at the mobile station.

c. d. e. f. g. h.

322.15.5 Minimum Standard

33The mobile station shall comply with step h.

19

1 12.16 PACA Origination, User Terminates While Still In Queue 22.16.1 Definition

3GPP2 C.S0044-A v1.0

3This test verifies that a PACA-capable mobile station, upon failure to originate a call due to lack of 4available voice/traffic channels, shall re-attempt the origination using the PACA feature code. It 5verifies that a currently queued mobile station properly informs the base station when a user 6aborts waiting for traffic channel.

72.16.2 Traceability
8(see [4])

92.6.2 102.6.2.8 112.6.3.5 122.7.1.3.2.4 132.7.1.3.2.9 143.7.2.3.2.20

Mobile Station Idle State Mobile Station PACA Cancel Operation Mobile Station Origination Attempt Substate Origination Message PACA Cancel Message PACA Message

152.16.3 Call Flow Example(s)

16None

172.16.4 Method of Measurement 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34

a. b. Allow the mobile station to come to the idle state on the base station. At the base station, enable PACA feature for the mobile station, assign a PACA priority level to the mobile station, and disable Permanent Invocation PACA for the mobile station. If the mobile station is capable of Slotted Mode, verify that the mobile station is operating in the Slotted Mode. Ensure PACA is enabled on base station. Configure the base station to make all traffic channels busy. Setup a mobile station originated call. Verify the following: 1. Mobile station originates call with PACA_REORIG bit='0' in Origination Message. 2. Base station replies with Reorder Order. 3. Mobile station retries the origination with the PACA_REORIG bit='1' in the Origination Message. 4. Base station sends PACA Message with PURPOSE='0000' and the mobile stations Queue Position (Q_POS). 5. Mobile station acknowledges PACA Message.

c. d. e. f. g.

20

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6

h. i. j. k. The mobile station user interface should indicate the origination has been successfully queued. Verify the mobile station remains in non-slotted mode. End call to terminate queued origination. Verify that the mobile station sends a PACA Cancel Message to the base station. Verify the mobile station enters slotted mode if applicable.

72.16.5 Minimum Standard

8The mobile station shall comply with the requirements in steps c, g, i, j, and k.

92.17 PACA Origination, Idle Handoff While in Queue 102.17.1 Definition

11This test verifies that a PACA-capable mobile station already in a PACA queue shall re-originate 12the PACA request when the mobile station performs an idle handoff.

132.17.2 Traceability
14(see [4])

152.6.2 162.6.2.8 172.6.3.5 182.7.1.3.2.4 192.7.1.3.2.9 203.7.2.3.2.20

Mobile Station Idle State Mobile Station PACA Cancel Operation Mobile Station Origination Attempt Substate Origination Message PACA Cancel Message PACA Message

212.17.3 Call Flow Example(s)

22None

232.17.4 Method of Measurement 24 25 26 27 28 29 30 31 32 2

a. b. c. d. e. f. g. h. Allow the mobile station to come to the idle state on the base station. At the base station, enable PACA feature for the mobile station, assign a PACA priority level to mobile station, and disable Permanent Invocation PACA for mobile station. Ensure PACA is enabled on both base stations. Configure both base stations to make all traffic channels busy. Setup a mobile station originated call. The mobile station user interface should indicate origination successfully queued. Force an idle handoff from base station 1 to base station 2. Verify the mobile station re-originates the PACA request with PACA_REORIG='1'.

21

1 1 2 3 4 5
i. j. k.

3GPP2 C.S0044-A v1.0 Verify a PACA Message is received from base station 2 indicating the mobile stations position in the PACA queue of base station 2. On the mobile station, originate a new call while still queued. The mobile station user interface should indicate to the user that the first PACA call has been cancelled.

62.17.5 Minimum Standard

7The mobile station shall comply with the requirements in steps h, i and k.

82.18 PACA Origination, Traffic Channel Becomes Available 92.18.1 Definition

10This test verifies that a currently PACA queued mobile station, when notified by the base station 11of an available traffic channel, should properly alert the user that the origination can now be 12completed.

132.18.2 Traceability
14(see [4])

152.6.2 162.6.2.8 172.6.3.5 182.7.1.3.2.4 192.7.1.3.2.9 203.7.2.3.2.20

Mobile Station Idle State Mobile Station PACA Cancel Operation Mobile Station Origination Attempt Substate Origination Message PACA Cancel Message PACA Message

212.18.3 Call Flow Example(s)

22None

232.18.4 Method of Measurement 24 25 26 27 28 29 30 31 32 33 2

a. b. Allow the mobile station to come to the idle state on the base station. At the base station, enable PACA feature for the mobile station, assign a PACA priority level to the mobile station, and disable Permanent Invocation PACA for the mobile station. Ensure PACA is enabled on the base station. Configure the base station to make all traffic channels busy. Setup a mobile station originated call. If supported by the mobile station, verify that the mobile station user interface indicates that an origination has been successfully queued. Make at least one traffic channel available on the base station.

c. d. e. f. g.

22

13GPP2 C.S0044-A v1.0 1 2 3 4

h. i. j. The base station shall page the mobile station, and the mobile station should indicate to the user that the PACA call is proceeding. Verify the call is completed and audio is present in both directions. End call.

52.18.5 Minimum Standard

6The mobile station shall comply with the requirements in steps f and i.

72.19 PACA Origination, Features Interaction 82.19.1 Definition

9This test verifies that specific paging channel features, such as SMS and MWI, are delivered to 10the mobile station while the mobile station is currently in a PACA queue.

112.19.2 Traceability
12(see [4])

132.6.2 142.6.2.8 152.6.3.5 162.7.1.3.2.4 172.7.1.3.2.9 183.7.2.3.2.20

Mobile Station Idle State Mobile Station PACA Cancel Operation Mobile Station Origination Attempt Substate Origination Message PACA Cancel Message PACA Message

192.19.3 Call Flow Example(s)

20None

212.19.4 Method of Measurement 22 23 24 25 26 27 28 29 30 31 32

a. b. Allow the mobile station to come to the idle state on the base station. At the base station, enable PACA feature for the mobile station, assign a PACA priority level to the mobile station, and disable Permanent Invocation PACA for the mobile station. Ensure PACA is enabled on the base station. Configure the base station to make all traffic channels busy. Setup a mobile station originated call. Verify the mobile station user interface indicates that an origination has been successfully queued. Send an SMS message over the Paging Channel to the mobile station. Verify the message is properly received by the mobile station.

c. d. e. f. g.

23

1 1 2 3
h. i.

3GPP2 C.S0044-A v1.0 Configure base station to send MWI to the mobile station. Verify MWI is displayed by the mobile station. End call.

42.19.5 Minimum Standard

5The mobile station shall comply with the requirements in steps f, g, and h.

62.20 PACA Origination, Permanent Invocation 72.20.1 Definition

8This test verifies that a PACA-capable mobile station with Permanent Invocation feature enabled 9shall be placed in PACA queue even if PACA is not requested in Origination Message.

102.20.2 Traceability
11(see [4])

122.6.2 132.6.2.8 142.6.3.5 152.7.1.3.2.4 162.7.1.3.2.9 173.7.2.3.2.20

Mobile Station Idle State Mobile Station PACA Cancel Operation Mobile Station Origination Attempt Substate Origination Message PACA Cancel Message PACA Message

182.20.3 Call Flow Example(s)

19None

202.20.4 Method of Measurement 21 22 23 24 25 26 27 28 29 30 31 32

a. b. Allow the mobile station to come to the idle state on the base station. At the base station, enable PACA feature for the mobile station, assign a PACA priority level to the mobile station, and enabled Permanent Invocation PACA for the mobile station. Ensure PACA is enabled on the base station. Configure the base station to make all traffic channels busy. Setup a mobile station originated call. Verify the following: 1. Mobile station originates call with PACA_REORIG bit='0' in Origination Message.

c. d. e. f.

2. Due to Permanent Invocation, base station sends PACA Message with PURPOSE='0000' and the mobile station's Queue Position (Q_POS).

24

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8

g. h. i. j. 3. 4. Mobile station acknowledges PACA Message. The mobile station user interface should indicate origination successfully queued.

Make at least one traffic channel available on the base station. The base station shall page the mobile station, and the mobile station should indicate to the user that the PACA call is proceeding. Verify call completes and audio is present in both directions. End call.

92.20.5 Minimum Standard

10The mobile station shall comply with the requirements in steps f and j.

112.21 PACA Origination, PACA Disabled for Mobile Station 122.21.1 Definition
13This test verifies that when a mobile station disabled for PACA attempts a PACA Origination, the 14call shall fail.

152.21.2 Traceability
16(see [4])

172.6.2 182.6.2.8 192.6.3.5 202.7.1.3.2.4 212.7.1.3.2.9 223.7.2.3.2.20

Mobile Station Idle State Mobile Station PACA Cancel Operation Mobile Station Origination Attempt Substate Origination Message PACA Cancel Message PACA Message

232.21.3 Call Flow Example(s)

24None

252.21.4 Method of Measurement 26 27 28 29 30 31

a. b. c. d. e. f. Allow the mobile station to come to the idle state on the base station. Ensure PACA is enabled on the base station. At the base station, disable PACA feature for the mobile station. Configure the base station to make all traffic channels busy. Setup a mobile station originated call. Verify the following:

25

1 1 2 3 4 5 6

3GPP2 C.S0044-A v1.0 1. Mobile station originates call with PACA_REORIG bit=0 in Origination Message. 2. Due to lack of available channels, base station replies with a Reorder Order. 3. Mobile station retries the origination with the PACA_REORIG bit = '1' in the Origination Message. 4. A second call re-origination attempt is denied by the base station and a reorder tone is generated at the mobile station.

72.21.5 Minimum Standard

8The mobile station shall comply with the requirements in step f.

92.22 Service Configuration and Negotiation without SYNC_ID 102.22.1 Definition

11This test verifies that the initial service configuration in effect is according to the value specified 12via the GRANTED_MODE field of the Extended Channel Assignment Message. This test also 13verifies that after service negotiation, the service configuration in use is the one specified by SCR 14and NN-SCR agreed upon during service negotiation.

152.22.2 Traceability
16(see [4])

172.6.4.1.2 182.6.4.1.14 192.6.4.1.15 202.6.4.2 212.7.1.3.2.4 222.7.1.3.2.5 232.7.2.3.2.12 242.7.2.3.2.13 252.7.2.3.2.14 262.7.4.18 273.6.4.1.2 283.7.2.3.2.21 293.7.3.3.2.18 303.7.3.3.2.19 313.7.3.3.2.20 323.7.3.3.2.31 333.7.3.3.2.36 2

Mobile Station Service Configuration and Negotiation procedures Processing the Service Configuration Record Processing the Non-Negotiable Service Configuration Record Traffic Channel Initialization Substate Origination Message Page Response Message (Mobile Station) Service Request Message (Mobile Station) Service Response Message (Mobile Station) Service Connect Completion Message Service Configuration information record Base Station Service Configuration and Negotiation procedures Extended Channel Assignment Message (Base Station) Service Request Message (Base Station) Service Response Message (Base Station) Service Connect Message General Handoff Direction Message Universal Handoff Direction Message

26

13GPP2 C.S0044-A v1.0 13.7.5.7 23.7.5.20

(Base Station) Service Configuration information record (Base Station) Non-Negotiable Service Configuration information record

32.22.3 Reference Call Flow

MS Common Channels Origination Message / Page Response Message (SO) Extended Channel Assignment Message (GRANTED_MODE) Dedicated Channels Dedicated Channels BS Common Channels

Initial service configuration in effect New service configuration takes effect

Optional Service Negotiation Message Exchange (Service Negotiation ends with two message below)

Service Connect Message/ General Handoff Direction Message/ Universal Handoff Direction Message (SCR_new, NN-SCR_new) Service Connect Completion Message/ Extended Handoff Completion Message

4 5Figure 2-2 Reference Call Flow for Service Configuration and Negotiation without SYNC_ID 62.22.4 Method of Measurement
7Note In this test case, it shall be ensured that mobile station does not include SYNC_ID field in 8the Origination Message/Page Response Message. This can be done by selecting type of call for 9which corresponding service configuration is not stored in mobile station. Note that the mobile 10station needs to store service configuration per SID, NID. Hence changing SID or NID or CDMA 11channel may be useful in ensuring that mobile station does not include SYNC_ID field in the 12Origination Message/Page Response Message.

13 14 15 16 17 18 19 20 21 22 23

a. b. c.

Connect the mobile station to the base station as shown in Annex A Figure A-1. If the mobile station supports voice call, initiate a mobile station originated voice call. Otherwise go to step f. After the base station sends an Extended Channel Assignment Message to the mobile station, the service negotiation shall occur between base station and mobile station. The service negotiation ends when base station sends Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message with SCR and NN-SCR to the mobile station and mobile station accepts the service configuration by sending Service Connect Completion Message/Extended Handoff Completion Message. Verify the following:

d.

27

1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 2

3GPP2 C.S0044-A v1.0 1. If the base station sends Extended Channel Assignment Message with GRANTED_MODE field set to 00 in step c above a. Prior to the new service configuration sent in the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message takes effect, verify the following: 1. The service configuration in use is the one jointly specified by the DEFAULT_CONFIG value sent in the Extended Channel Assignment Message and the default Non-Negotiable part of the service configuration parameters specified in the Traffic Channel Initialization substate. b. When the new service configuration sent in the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message takes effect, verify the following: 1. The service configuration in use is the one specified by SCR and NN-SCR in the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message sent by the base station. 2. Verify user traffic on both directions. 3. The base station receives a Service Connect Completion Message (if base station sends Service Connect Message) or an Extended Handoff Completion Message (if base station sends General Handoff Direction Message/Universal Handoff Direction Message) from the mobile station. 2. If base station sends Extended Channel Assignment Message with GRANTED_MODE field set to 01 in step c above a. Prior to the new service configuration sent in the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message takes effect, verify the following: 1. The service configuration in use is the one jointly specified by the default multiplex option that is derived from the radio configuration corresponding to Table 3.7.2.3.2.21-7 of [4] and the default Non-Negotiable part of the service configuration parameters specified in the Traffic Channel Initialization substate. b. When the new service configuration sent in the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message takes effect, verify the following: 1. The service configuration in use is the one specified by SCR and NN-SCR in the Service Connect Message sent by the base station. 2. Verify user traffic in both directions.

28

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

e. f. 3. The base station receives a Service Connect Completion Message (if base station sends Service Connect Message) or an Extended Handoff Completion Message (if base station sends General Handoff Direction Message/Universal Handoff Direction Message) from the mobile station. 3. If base station sends Extended Channel Assignment Message with GRANTED_MODE field set to 10 in step c above a. Prior to the new service configuration sent in the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message takes effect, verify the following: 1. The service configuration in use is the one jointly specified by the default multiplex option that is derived from the radio configuration corresponding to Table 3.7.2.3.2.21-7 of [4] and the default Non-Negotiable part of the service configuration parameters specified in the Traffic Channel Initialization Substate. b. When the new service configuration sent in the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message takes effect, verify the following: 1. The service configuration in use is the one specified by SCR and NN-SCR in the Service Connect Message sent by the base station. 2. Verify user traffic on both directions. 3. The base station receives a Service Connect Completion Message (if base station sends Service Connect Message) or an Extended Handoff Completion Message (if base station sends General Handoff Direction Message/Universal Handoff Direction Message) from the mobile station. 4. The mobile station does not send a Service Request Message to the base station prior to the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message is received from the base station. Repeat steps a through d for mobile station terminated calls. In this case, Page Response Message replaces Origination Message. If mobile station supports data calls, repeat steps a to e above but with following modification In step b initiate data call in place of voice call.

372.22.5 Minimum Standard

38The mobile station shall comply with step d.

29

1 12.23 Service Configuration and Negotiation with SYNC_ID 22.23.1 Definition

3GPP2 C.S0044-A v1.0

3This test verifies that the mobile station can propose to use stored service configuration using 4SYNC_ID in the Service Configuration and Negotiation process. 5Note This test assumes that the mobile station stores old service configuration with 6corresponding SYNC_ID and uses SYNC_ID during call setup. If the mobile station does not use 7SYNC_ID in call setup, then skip this test. This test also assumes that the base station sets 8USE_SYNC_ID field to 1 in Extended System Parameters Message and/or MC-RR Parameters 9Message. If the base station is unable to do this, then skip this test.

102.23.2 Traceability
11(see [4])

122.6.2.2.5 132.6.2.2.14.1 142.6.2.5 152.6.3.3 162.6.3.5 172.6.4.1.2 182.6.4.1.12 192.6.4.1.13 202.6.4.2 212.6.4.4 222.6.6.2.5 232.6.6.2.5.1 242.7.1.3.2.4 252.7.1.3.2.5 262.7.2.3.2.12 272.7.2.3.2.13 282.7.2.3.2.14 292.7.4.18 303.6.4.1.2 313.7.2.3.2.13 323.7.2.3.2.21 333.7.2.3.2.31 343.7.3.3.2.18

Extended System Parameters Message Stored Parameters Mobile Station Origination Operation Page Response Substate Mobile Station Origination Attempt Substate (Mobile Station) Service Configuration and Negotiation (procedures) Processing the Service Configuration Record Processing the Non-Negotiable Service Configuration Record Traffic Channel Initialization Substate Release Substate Handoff Messages Processing of Forward Traffic Channel Handoff Messages Origination Message Page Response Message (Mobile Station) Service Request Message (Mobile Station) Service Response Message (Mobile Station) Service Connect Completion Message (Mobile Station) Service Configuration (information record) (Base Station) Service Configuration and Negotiation (procedures) Extended System Parameters Message Extended Channel Assignment Message MC-RR Parameters Message (Base Station) Service Request Message

30

13GPP2 C.S0044-A v1.0 13.7.3.3.2.19 23.7.3.3.2.20 33.7.3.3.2.31 43.7.3.3.2.36 53.7.5.7 63.7.5.20

(Base Station) Service Response Message (Base Station) Service Connect Message General Handoff Direction Message Universal Handoff Direction Message (Base Station) Service Configuration (information record) (Base Station) Non-Negotiable Service Configuration (information record)

72.23.3 Reference Call Flow

MS Common Channels Origination Message / Page Response Message (SYNC_ID) Extended Channel Assignment Message (GRANTED_MODE) Dedicated Channels Dedicated Channels BS Common Channels

Optional Service Negotiation Message Exchange (Service Negotiation ends with two messages below)

Initial service configuration in effect

Service Connect Message (USE_OLD_SERV_CONFIG, SCR_new, NN-SCR_new) Service Connect Completion Message

New service configuration takes effect

8 9Figure 2-3 Reference Call Flow for Service Configuration and Negotiation with SYNC_ID 102.23.4 Method of Measurement 11 12 13 14 15 16 17 18 19 20 21
a. Connect the mobile station to the base station as shown in Annex A Figure A-1. Verify that the base station sets USE_SYNC_ID field to 1 in Extended System Parameters Message and/or MC-RR Parameters Message. Identify a type of call for which the base station would send the SYNC_ID with SCR and NN_SCR and the mobile station would use SYNC_ID when the same type of call is originated again. Initiate a mobile station originated call with this call type. Verify that the base station includes SYNC_ID field in the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message sent to the mobile station. Once the service configuration sent in the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message has taken effect, disconnect the call.

b.

31

1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
f. c. d.

3GPP2 C.S0044-A v1.0 Initiate a mobile station originated call with same call type as above. Verify that mobile station includes SYNC_ID field in the Origination Message. The service negotiation ends when base station sends Service Connect Message to the mobile station and mobile station accepts the service configuration by sending Service Connect Completion Message. Verify the following: 1. If the base station sends Service Connect Message with USE_OLD_SERV_CONFIG field set to 00 a. When the Service Connect Message takes effect, verify the following: 1. The service configuration in use is the one specified by SCR and NN-SCR in the Service Connect Message sent by the base station. 2. Verify user traffic (e.g. SO 33) on both directions. 3. The base station receives a Service Connect Completion Message from the mobile station. 2. If the base station sends Service Connect Message with USE_OLD_SERV_CONFIG field set to 01 a. When the new service configuration specified in the Service Connect Message takes effect, verify the following: 1. The mobile station uses the stored service configuration. 2. Verify user traffic (e.g. SO 33) on both directions. 3. The base station receives a Service Connect Completion Message from the mobile station. 3. If the base station sends Service Connect Message with USE_OLD_SERV_CONFIG field set to 10 a. When the Service Connect Message takes effect, verify the following: 1. The mobile station uses the stored service configuration. 2. Verify user traffic (e.g. SO 33) on both directions. 3. The base station receives a Service Connect Completion Message from the mobile station. Repeat steps a through d for mobile station terminated calls. In this case, Origination Message is replaced by Page Response Message.

e.

332.23.5 Minimum Standard

34The mobile station shall comply with step e.

32

13GPP2 C.S0044-A v1.0 12.24 Intra-Band Channel Assignment 22.24.1 Definition

3This test verifies that the mobile station originating a call can be assigned a different frequency 4within the same band class using the (Extended) Channel Assignment Message.

52.24.2 Traceability:
6(See[4])

72.6.2.4 82.6.3.5 92.7.1.3.2.4 102.7.1.3.2.5 113.7.2.3.2.8 123.7.2.3.2.21

Mobile Station Order and Message Processing Operation Mobile Station Origination Attempt Substate Origination Message Page Response Message Channel Assignment Message Extended Channel Assignment Message

132.24.3 Call Flow Example(s)

14None

152.24.4 Method of Measurement 16 17 18 19 20 21

22

a. b. c. d.

Connect the mobile station and base stations as shown in Figure A-2. Base station 1 and base station 2 are operating the same band class with different frequencies. Ensure the mobile station is operating in the Idle State on base station 1. Setup a mobile station originated call. Ensure that the base station sends a Channel Assignment Message or Extended Channel Assignment Message with the following settings:

23

Table 2.24.4-12 Channel Assignment Message Settings Field ASSIGN_MODE FREQ_INCL BAND_CLASS CDMA_FREQ Value 100 1 Target Band Class (same as base station 1) Target Frequency for base station 2

24

33

1 1

3GPP2 C.S0044-A v1.0 Table 2.24.4-2 Extended Channel Assignment Message Settings Field ASSIGN_MODE FREQ_INCL BAND_CLASS CDMA_FREQ Value 000 or 100 1 Target Band Class (same as base station 1) Target Frequency for base station 2

3 4 5 6 7

e. f. g. h.

Verify the mobile station tunes to the new frequency and completes the call on base station 2. Verify user data in both directions. End the call. Setup a mobile station terminated call and repeat steps d through g.

82.24.5 Minimum Standard

9The mobile station shall comply with steps e, f, and h.

102.25 Silent-Retry 112.25.1 Definition

12This test verifies the mobile station silent-retry functionality and the proper setting of ARQ fields. 13Silent-retry is an autonomous access re-attempt that is made to re-originate the call, without user 14interaction, that is due to the mobile station receiving an access attempt failure from the ARQ 15Sublayer.

162.25.2 Traceability 172.7.1.3.2.4

18(see [2])

Origination Message (see [4])

192.2.1.1.2.1.5
20(see [3])

Access Channel Procedures

212.1.1.2.1.2 222.1.1.2.2.1 23

Requirements for Setting the ARQ Fields Overview of Transmission and Retransmission Procedures

242.25.3 Call Flow Example(s)

25None

34

13GPP2 C.S0044-A v1.0 12.25.4 Method of Measurement 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 19

FIELD ORIG_REASON ORIG_COUNT 1 Number of consecutive silentretry. If the value is greater than three, the mobile station shall set this value to 11. VALUE a. b. c. Connect the base station as shown in Figure A-3. Disable the reverse link to the base station. Attempt to setup a mobile station originated call. Note the MSG_SEQ value in the Origination Message. Allow the mobile station to exhaust NUM_STEP or EACH_NUM_STEP and MAX_REQ_SEQ as defined in the Access Parameters Message or Enhanced Access Parameters Message. Enable the reverse link to the base station. Verify the following: 1. If the P_REV_IN_USE is less than or equal to six verify; a. The mobile station sends a new Origination Message. b. The MSG_SEQ value in the Origination Message is different than the value recorded in step b. 2. Otherwise, verify; a. The mobile station sends a new Origination Message with the following values:

d. e.

20 21 22
f.

b. The MSG_SEQ value in the Origination Message is different than the value recorded in step b. Verify the call completes and user traffic is present in both directions (i.e. audio).

232.25.5 Minimum Standard

24The mobile station shall comply with steps e and f.

25

35

1 12.26 MSID, MCC, and IMSI 22.26.1 Definition

3GPP2 C.S0044-A v1.0

3These tests verify some protocol of the Mobile Station IDentifier number (MSID or MSIN), Mobile 4Country Code (MCC), and International Mobile Station Identity (IMSI). Mobile station response to 5three instances of base station PREF_MSID_TYPE are checked when the MCC and IMSI_11_12 6of the mobile station and base station match do not match or are wildcard values.

72.26.2 Traceability
8(see [4])

93.7.2.3.2.13 102.6.2.2.5 112.6.2.3 122.3.1 132.3.1.1 153.6.2.2 16(see [3]) 172.1.1.3.1.1 182.1.1.2.1.3

Extended System Parameters Message Extended System Parameters Message Mobile Station Page Match Operation Mobile Station Identification Number Encoding of IMSI_M_S and IMSI_T_S 11 Preferred MSID Types

14Table 3.7.2.3.2.13-1

Overhead Information

Addressing IMSI Class

192.26.2.1.1 Call Flow Diagram

20None

212.26.3 Method of Measurement 22For each step below with IMSI_CLASS = 0, set USE_TMSI = 0 in the base station Extended
23System Parameters Message or ANSI-41 System Parameters Message. Also program either the 24mobile station or the base station for the values of MCC and IMSI_11_12, to achieve the 25matching or non-matching conditions indicated.

26 27 28 29 30 31 32 33 34 35 36

a. PREF_MSID_TYPE = 00. Configure the base station Extended System Parameters Message with PREF_MSID_TYPE = 00. Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = 000 and sends IMSI_S and ESN in the Origination Message and Page Response Message. b. PREF_MSID_TYPE = 10, matching MCC and matching IMSI_11_12. Configure the base station Extended System Parameters Message with PREF_MSID_TYPE = 10. Verify the values of both MCC and IMSI_11_12 are the same (match) in the mobile station and base station. Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = 010 and sends IMSI_S (does not send MCC and IMSI_11_12) in the Origination Message and Page Response Message.

36

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

Field PREF_MSID_TYPE MCC IMSI_11_12 Value 10 1111111111 (wildcard) 1111111 (wildcard) c. PREF_MSID_TYPE = 10, non-matching MCC and matching IMSI_11_12. Configure the base station Extended System Parameters Message with PREF_MSID_TYPE = 10. Verify the values of IMSI_11_12 are the same (match) in the mobile station and base station, but the values of MCC are different (dont match). Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = 010 and sends MCC and IMSI_S (does not send IMSI_11_12) in the Origination Message and Page Response Message.

d. PREF_MSID_TYPE = 10, matching MCC and non-matching IMSI_11_12. Configure the base station Extended System Parameters Message with PREF_MSID_TYPE = 10. Verify the values of MCC are the same (match) in the mobile station and base station, but the values of IMSI_11_12 are different (dont match). Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = 010 and sends IMSI_11_12 and IMSI_S (does not send MCC) in the Origination Message and Page Response Message. e. PREF_MSID_TYPE = 10, non-matching MCC and non-matching IMSI_11_12. Configure the base station Extended System Parameters Message with PREF_MSID_TYPE = 10. Verify the values of both MCC and IMSI_11_12 are different in the mobile station and base station (neither matches). Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = 010 and sends MCC, IMSI_11_12 and IMSI_S in the Origination Message and Page Response Message. f. PREF_MSID_TYPE = 10, wildcard MCC and wildcard IMSI_11_12. Configure the base station Extended System Parameters Message with the following fields.

25 26 27 28 29 30 31 32 33 34

g. Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = 010 and sends IMSI_S (but does not send MCC and IMSI_11_12) in the Origination Message and Page Response Message. h. PREF_MSID_TYPE = 11, matching MCC and matching IMSI_11_12. Configure the base station Extended System Parameters Message with PREF_MSID_TYPE = 11. Verify the values of both MCC and IMSI_11_12 are the same in the mobile station and base station (both match). Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = 011 and sends IMSI_S and ESN (does not send MCC and IMSI_11_12) in the Origination Message or Page Response Message.

37

1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
24

3GPP2 C.S0044-A v1.0 i. PREF_MSID_TYPE = 11, non-matching MCC and matching IMSI_11_12. Configure the base station Extended System Parameters Message with PREF_MSID_TYPE = 11. Verify the values of IMSI_11_12 are the same in the mobile station and base station (match), but the values of MCC are different (dont match). Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = 011 and sends MCC, IMSI_S and ESN (does not send IMSI_11_12) in the Origination Message and Page Response Message. PREF_MSID_TYPE = 11, matching MCC and non-matching IMSI_11_12. Configure the base station Extended System Parameters Message with PREF_MSID_TYPE = 11. Verify the values of MCC are the same in the mobile station and base station (match), but the values of IMSI_11_12 are different (dont match). Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = 011 and sends IMSI_11_12, IMSI_S and ESN (does not send MCC) in the Origination Message and Page Response Message. PREF_MSID_TYPE = 11, non-matching MCC and non-matching IMSI_11_12. Configure the base station Extended System Parameters Message with PREF_MSID_TYPE = 11. Verify the values of both MCC and IMSI_11_12 are different in the mobile station and base station. Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = 011 and sends MCC, IMSI_11_12, IMSI_S, and ESN in the Origination Message and Page Response Message. PREF_MSID_TYPE = 11, wildcard MCC and wildcard IMSI_11_12. Configure the base station Extended System Parameters Message with the following fields.

j.

k.

l.

Field PREF_MSID_TYPE MCC IMSI_11_12

25

Value 11 1111111111 (wildcard) 1111111 (wildcard)

26 27 28

m. Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = 011 and sends IMSI_S and ESN (but does not send MCC and IMSI_11_12) in the Origination Message and Page Response Message.

292.26.4 Minimum Standard

30All calls shall complete normally. The mobile station shall comply with requirements in steps b 31through m.

38

13GPP2 C.S0044-A v1.0 13 23.1 33.1.1

HANDOFF TESTS
Soft Handoff with Dynamic Threshold Definition

4This test verifies the mobile station and base station perform soft handoff. Soft handoff with and 5without dynamic thresholds is verified. This test verifies both adding pilot to and dropping pilot 6from the soft handoff Active Set. Tests 1 through 4 apply to cases when SOFT_SLOPE is not 7equal to 000000 (dynamic threshold enabled).

83.1.2
9(See[4])

Traceability

102.6.2.2.5 112.6.4.1.4 122.6.6.2.3 132.6.6.2.5.1 142.6.6.2.5.2 152.6.6.2.6.2 162.6.6.2.6.3 172.6.6.2.8.2.1 182.6.6.3 192.7.2.3.2.5 203.6.6.2.1.1 213.7.2.3.2.13 223.7.3.3.2.7 233.7.3.3.2.17 243.7.3.3.2.31 253.7.3.3.2.36 263.1.3
27None

Extended System Parameters Message Processing the In-Traffic System Parameters Message Handoff Drop Timer Processing of Forward Traffic Channel Handoff Messages Processing of Reverse Traffic Channel Handoff Messages Maintenance of the Candidate Set Maintenance of the Neighbor Set Restoring the Configuration Examples Pilot Strength Measurement Message System Parameters Extended System Parameters Message In-Traffic System Parameters Message Extended Handoff Direction Message General Handoff Direction Message Universal Handoff Direction Message

Call Flow Example(s)

283.1.4 29 30 31
a.

Method of Measurement Setup test as shown in Figure A-4. 1. The Forward Channel from sector of base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1.

1 1 2 3 4 5 6
Field SOFT_SLOPE ADD_INTERCEPT DROP_INTERCEPT T_ADD T_DROP T_TDROP
7

3GPP2 C.S0044-A v1.0 2. The Forward Channel from sector of base station 1 has an arbitrary pilot PN offset index P2 and is called Channel 2. 3. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P3 and is called Channel 3. b. Set the test parameters for Test 1 as specified in Table 3.1.4-13and Table 3.1.4-2. Table 3.1.4-13 Value 010000 (2)6 000110 (3 dB)7 000010 (1 dB)8 100000 (-16 dB) 100100 (-18 dB) 0011 (4s)

8
Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io
9

Table 3.1.4-2 Unit dB dB dB dBm/1.23 MHz dB -5.8 Channel 1 7 -5 -7 Channel 2 -20 -5 -7 -75 -33 -33 Channel 3 -20 -5 -7

26 SOFT_SLOPE=16/8=2 37 ADD_INTERCEPT=6/2=3dB 48 DROP_INTERCEPT=2/2=1dB 5

2

13GPP2 C.S0044-A v1.0 1

Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io
2

Table 3.1.4-3 Unit dB dB dB dBm/1.23 MHz dB -8.4 Channel 1 7 -5 -7 Channel 2 7 -5 -7 -75 -8.4 -35 Channel 3 -20 -5 -7

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

c. d. e. f.

Reverse link attenuation should be set to balance the forward and reverse links (approximately 90 dB). Setup a mobile station originated call. Verify user data in both directions. Verify only Channel 1 is in the Active Set. Raise the level of Channel 2 in steps of 1 dB with a dwell time of five seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Record the level of Pilot Ec/Io in the Pilot Strength Measurement Message. Verify the following 1. The mobile station generates a Pilot Strength Measurement Message when the level of channel 2 is at a Pilot Ec/Io level between 10 dB and 13 dB. 2. The base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station to allow soft handoff between Channel 1 and Channel 2. 3. The mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message as a response to handoff message. 4. The mobile station is in soft handoff between Channel 1 and Channel 2.

g.

h.

Set test parameters for Test 2 as specified in Table 3.1.4-3 while Channel 1 and Channel 2 are in soft handoff. Raise the level of Channel 3 in steps of 1 dB with a dwell time of five seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Record the level of Pilot Ec/Io in the Pilot Strength Measurement Message. Verify the following: 1. The mobile station generates a Pilot Strength Measurement Message when the level of channel 3 is at a level between 10 dB and 13 dB. 2. The base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station to allow soft handoff between Channel 1, Channel 2 and Channel 3.

i.

1 1 2 3 4 5 6 7 8 9
10

3GPP2 C.S0044-A v1.0 3. The mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message as a response to handoff message. 4. The mobile station is in soft handoff among Channel 1, Channel 2 and Channel 3. j. Set the test parameters for Test 3 in Table 3.1.4-4 while Channel 1, Channel 2, and Channel 3 are in soft handoff. Lower the level of Channel 3 in steps of 1 dB with a dwell time of 30 seconds until the mobile station has generated the Pilot Strength Measurement Message. Record the level of Pilot Ec/Io in the Pilot Strength Measurement Message.

11
Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io Unit dB dB dB

Table 3.1.4-4 Channel 1 7 -5 -7 Channel 2 7 -5 -7 -75 -10.1 -10.1 -10.1 Channel 3 7 -5 -7

dBm/1.23 MHz dB

12 13 14 15 16 17 18 19 20 21 22 23 24 25

k.

Verify the following: 1. The mobile station generates a Pilot Strength Measurement Message when the level of channel 3 is at a level between 12 dB and 16 dB for a period of T_TDROP. 2. The base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station to allow soft handoff between Channel 1 and Channel 2. 3. The mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message as a response to handoff message. 4. The mobile station is in soft handoff between Channel 1 and Channel 2.

l.

Set test parameters for Test 4 as specified in Table 3.1.4-5. Lower level of Channel 2 in steps of 1 dB with a dwell time of 30 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Record the level of Pilot Ec/Io in the Pilot Strength Measurement Message.

13GPP2 C.S0044-A v1.0 1

Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io Unit dB dB dB dBm/1.23 MHz dB -8.4 Table 3.1.4-5 Channel 1 7 -5 -7 Channel 2 7 -5 -7 -75 -8.4 -35 Channel 3 -20 -5 -7

2 3 4 5 6 7 8 9 10 11

m.

Verify the following: 1. The mobile station shall generate a Pilot Strength Measurement Message when the level of channel 2 is at a level of 11 dB and 14 dB for a period of T_TDROP. 2. The base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station with only Channel 1 listed in the Active Set. 3. The mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message as a response to handoff message. 4. Channel 1 is the only Active Set for the mobile station. Minimum Standard

123.1.5

13Verify steps g, i, k and m.

143.2 153.2.1

Soft Handoff without Dynamic Threshold Definition

16This test verifies the proper operation of mobile station soft handoff. Soft handoff without dynamic 17thresholds is verified. This test verifies both adding pilot to and dropping pilot from the soft 18handoff Active Set. Tests 1 through 4 apply to cases when SOFT_SLOPE is equal to 000000 19(dynamic threshold disabled).

203.2.2
21(See[4])

Traceability

222.6.2.2.5 232.6.4.1.4 242.6.6.2.3 252.6.6.2.5.1 262.6.6.2.5.2 272.6.6.2.6.2

Extended System Parameters Message Processing the In-Traffic System Parameters Message Handoff Drop Timer Processing of Forward Traffic Channel Handoff Messages Processing of Reverse Traffic Channel Handoff Messages Maintenance of the Candidate Set

1 12.6.6.2.6.3 22.6.6.2.8.2.1 32.6.6.3 42.7.2.3.2.5 53.6.6.2.1.1 63.7.2.3.2.13 73.7.3.3.2.7 83.7.3.3.2.17 93.7.3.3.2.31 103.7.3.3.2.36 113.2.3
12None

3GPP2 C.S0044-A v1.0 Maintenance of the Neighbor Set Restoring the Configuration Examples Pilot Strength Measurement Message System Parameters Extended System Parameters Message In-Traffic System Parameters Message Extended Handoff Direction Message General Handoff Direction Message Universal Handoff Direction Message

Call Flow Example(s)

133.2.4 14 15 16 17 18 19 20 21 22 23
b. a.

Method of Measurement Setup test as shown in Figure A-4. Start with Test 1 to Test 4 with dynamic threshold disabled. 1. The Forward Channel from sector of base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1. 2. The Forward Channel from sector of base station 1 has an arbitrary pilot PN offset index P2 and is called Channel 2. 3. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P3 and is called Channel 3. Set the test parameters for Test 1 as specified in Table 3.2.4-14 and Table 3.2.3-2. Table 3.2.4-14 Parameter SOFT_SLOPE ADD_INTERCEPT DROP_INTERCEPT T_ADD T_DROP T_TDROP Tests 1-4 000000 (0) 000000 (0 dB) 000000 (0 dB) 011100 (-14 dB) 100000 (-16 dB) 0011 (4s)

24

13GPP2 C.S0044-A v1.0 1

Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io
2

Table 3.2.4-2 Unit dB dB dB dBm/1.23 MHz dB -5.8 Channel 1 7 -5 -7 Channel 2 -20 -5 -7 -75 -33 -33 Channel 3 -20 -5 -7

3
Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io
4

Table 3.2.4-3 Unit dB dB dB dBm/1.23 MHz dB -8.4 Channel 1 7 -5 -7 Channel 2 7 -5 -7 -75 -8.4 -35 Channel 3 -20 -5 -7

5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 2

c. d. e. f.

Reverse link attenuation should be set to balance the forward and reverse links (approximately 90 dB). Setup a mobile station originated call. Verify user data in both directions. Verify only Channel 1 is in the Active Set. Raise the level of Channel 2 in steps of 1 dB with a dwell time of five seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Record the level of Pilot Ec/Io in the Pilot Strength Measurement Message. Verify the following: 1. The mobile station generates a Pilot Strength Measurement Message when the level of channel 2 is at a level between T_ADD and T_ADD +2 dB. 2. The base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station to allow soft handoff between Channel 1 and Channel 2. 3. The mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message as a response to handoff message. 4. The mobile station is in softer handoff between Channel 1 and Channel 2.

g.

h.

Set test parameters for Test 2 as specified in Table 3.2.4-3 while Channel 1 and Channel 2 are in soft handoff. Raise the level of Channel 3 in steps of 1 dB with a dwell

1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io
21

3GPP2 C.S0044-A v1.0 time of five seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Record the level of Pilot Ec/Io in the Pilot Strength Measurement Message. i. Verify the following: 1. The mobile station generates a Pilot Strength Measurement Message when level of channel 3 is at a level between T_ADD and T_ADD +3 dB. 2. The base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station to allow softer handoff between Channel 1, Channel 2 and Channel 3. 3. The mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message as a response to handoff message. 4. The mobile station is in softer handoff among Channel 1, Channel 2 and Channel 3. j. Set the test parameters for Test 3 in Table 3.2.4-4 while Channel 1, Channel 2, and Channel 3 are in soft handoff. Lower the level of Channel 3 in steps of 1 dB with a dwell time of 30 seconds until the mobile station has generated the Pilot Strength Measurement Message. Record the level of Pilot Ec/Io in the Pilot Strength Measurement Message. Table 3.2.4-4 Unit dB dB dB dBm/1.23 MHz dB -10.1 Channel 1 7 -5 -7 Channel 2 7 -5 -7 -75 -10.1 -10.1 Channel 3 7 -5 -7 the

22 23 24 25 26 27 28 29 30 31 2

k.

Verify the following: 1. The mobile station generates a Pilot Strength Measurement Message when the level of channel 3 is at a level between T_DROP and T_DROP + 4 dB for a period of T_TDROP. 2. The base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station to allow softer handoff between Channel 1 and Channel 2. 3. The mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message as a response to handoff message. 4. The mobile station is in softer handoff between Channel 1 and Channel 2.

13GPP2 C.S0044-A v1.0 1 2 3 4 5

Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io Unit dB dB dB dBm/1.23 MHz dB -8.4 l. Set test parameters for Test 4 as specified in Table 3.2.4-5. Lower level of Channel 2 in steps of 1 dB with a dwell time of 30 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Record the level of Pilot Ec/Io in the Pilot Strength Measurement Message. Table 3.2.4-5 Channel 1 7 -5 -7 Channel 2 7 -5 -7 -75 -8.4 -35 Channel 3 -20 -5 -7

6 7 8 9 10 11 12 13 14 15

m.

Verify the following: 1. The mobile station shall generate a Pilot Strength Measurement Message when the level of channel 2 is at a level of T_DROP and T_DROP 3 dB for a period of T_TDROP. 2. The base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station with only Channel 1 listed in the Active Set. 3. The mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message as a response to handoff message. 4. Channel 1 is the only Active Set for the mobile station. Minimum Standard

163.2.5

17Verify steps g, i, k, and m.

183.3 193.3.1

Hard Handoff Between Frequencies in the Same Band Class Definition

20This test verifies the mobile station and base station perform hard handoff between different 21CDMA channels in the same band class.

223.3.2
23(See[4])

Traceability

242.6.6.1.1 252.6.6.2.5 262.6.6.2.8 273.6.6.1.1

Types of Handoff Handoff Messages CDMA-to-CDMA Hard Handoff Types of Handoff

1 13.6.6.2.2 23.7.3.3.2.17 33.7.3.3.2.31 43.7.3.3.2.36 53.3.3

6None

3GPP2 C.S0044-A v1.0 Call Processing During Handoff Extended Handoff Direction Message General Handoff Direction Message Universal Handoff Direction Message

Call Flow Example(s)

73.3.4 8 9 10 11 12 13 14 15 16 17 18
b. a.

Method of Measurement Setup test as shown in Figure A-5. 1. The Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1. 2. Setup base station 2 to be on a different CDMA channel than base station 1, but within the same band class. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P2 and is called Channel 2. 3. The AWGN source should be on the frequency of Channel 2. (It is advisable to achieve the maximum possible difference in frequency separation between Channel 1 and Channel 2). Set the test parameters as shown in Table 3.3.4-15. Table 3.3.4-15 Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io Unit dBm dB dB dBm/1.23 MHz dB Channel 1 N/A -7 -7 N/A -7 Channel 2 -5 -7 -7 -75 -13.2

19

20 21 22 23 24 25 26 27

c. d. e. f.

Set reverse link attenuation to balance forward and reverse links (approximately 90 dB). Setup a mobile station originated call on Channel 1. Verify user data in both directions. Initiate handoff from Channel 1 to Channel 2. Verify that base station 1 initiates handoff from Channel 1 to Channel 2 by sending a General Handoff Direction Message, Universal Handoff Direction Message, or an Extended Handoff Direction Message with proper parameters (refer to tables in Annex B) to initiate handoff from Channel 1 to Channel 2.

10

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

k. g. One second or more after base station 1 sends a General Handoff Direction Message, a Universal Handoff Direction Message, or an Extended Handoff Direction Message disconnect or attenuate the forward link of Channel 1. Verify user data in both directions. Monitor calls and record the length of any audio dropouts present. Steps b through g may be repeated for the case where it is a hard handoff to soft handoff on the same frequency with the following setup (see Figure A-4: one base station configured with two sectors active): 1. The Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1. 2. The Forward Channel from sector of base station 2 has an arbitrary pilot PN offset index P2 and is called Channel 2. 3. The Forward Channel from sector of base station 2 has an arbitrary pilot PN offset index P3 and is called Channel 3. The expected results for steps h and i should be the same as the previous test. Minimum Standard

h. i. j.

163.3.5

17In step h, the mobile station and base stations shall successfully execute the hard handoff.

183.4 193.4.1

Hard Handoff from CDMA to Analog Definition

20This test verifies the mobile station and base station perform hard hand off from a CDMA system 21to an analog system.

223.4.2
23(See[4])

Traceability

242.6.6.1.1 252.6.6.2.9 263.6.6.1.1 273.6.6.2.2 283.7.3.3.2.6 293.4.3

30None

Types of Handoff CDMA-to-Analog Handoff Types of Handoff Call Processing During Handoff Analog Handoff Direction Message

Call Flow Example(s)

313.4.4 32 33
a.

Method of Measurement Connect two base stations and an AWGN source to the mobile station as shown in Figure A-5. For the purpose of this test, Channel 1 is CDMA and Channel 2 is analog.

11

1 1
2 3

3GPP2 C.S0044-A v1.0 b. Set the test parameters as shown in Table 3.3.4-15 and Table 3.4.4-2.

4
Analog Parameter Voice Channel Co-Channel Interference
5

Table 3.4.4-2 Unit dBm dB Channel 2 -73 -18

6 7 8 9 10 11 12 13 14 15 16

c. d. e. f.

Reverse link attenuation should be set to balance the forward and reverse links (approximately 90 dB). Setup a mobile station originated call on Channel 1. Verify user data in both directions. Initiate handoff to analog. Verify the CDMA base station sends an Analog Handoff Direction Message with proper parameters (refer to tables in Annex B) to initiate handoff to analog. One second or more after base station 1 sends an Analog Handoff Direction Message disconnect or attenuate the forward link of Channel 1. Verify user data in both directions in the Analog system. Monitor calls and record the length of any audio dropouts present on handoff. Minimum Standard

g. h. i.

173.4.5

18In step h, the mobile station handoff to the Analog system shall be completed successfully

193.5 203.5.1 22 23 24
a. b. c.

Soft Handoff in Fading Definition

21This test verifies soft handoff under various fading conditions:

1 Ray Rayleigh fading at 30 km/hr 3 Ray Rayleigh fading at 100 km/hr 1 Ray Rayleigh fading at 3 km/hr Traceability

253.5.2
26(See[4])

272.6.6.1.1 282.6.6.2.5 292.6.6.2.7

Types of Handoff Handoff Messages Soft Handoff

12

13GPP2 C.S0044-A v1.0 13.6.6.1.1 23.6.6.2.2 33.6.6.2.4 43.5.3

5None

Types of Handoff Call Processing During Handoff Soft Handoff

Call Flow Example(s)

63.5.4 7 8 9 10 11 12 13
b. a.

Method of Measurement Setup test as shown in A-2. 1. The Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1. 2. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P2 and is called Channel 2. Set up the test parameters as shown in Table 3.5.4-16. Table 3.5.4-16 Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io Unit dB dB dB dBm/1.23 MHz dB Channel 1 0 -7 -7 -75 -10.2 Channel 2 -10 -7 -7 -75 -20.2

14

15 16 17 18 19 20 21 22 23 24 25 26 27 28

c. d. e. f.

Reverse link attenuation should be set to balance the forward and reverse links (approximately 90 dB). Set both channel simulators to one Ray Rayleigh, 30 km/hr. Setup a mobile station originated call on Channel 1. Monitor two-way audio and note anomalies throughout the test. Raise the level of Channel 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Verify the following: 1. Pilot Strength Measurement Message is generated when the channel 2 Pilot Ec/Io is at a level above T_ADD. 2. Base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station. 3. Channel 1 and Channel 2 are in the Active Set at the action time of the message.

13

1 1 2 3 4
Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io
5

3GPP2 C.S0044-A v1.0 g. h. Mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message to the base station. Set the test parameters as specified in Table 3.5.4-2 without dropping the call. Table 3.5.4-2 Unit dB dB dB dBm/1.23 MHz dB Channel 1 0 -7 -7 -75 -11.8 Channel 2 0 -7 -7 -75 -11.8

6 7 8 9 10 11 12 13 14 15 16 17 18

i.

Lower the level of Channel 1 in steps of 1 dB with a dwell time of 8 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Verify the following: 1. Pilot Strength Measurement Message is generated when Channel 1 is at a Pilot Ec/Io level below T_DROP for a period of TT_DROP. 2. Base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station. 3. Only Channel 2 is in the Active Set at the action time of the message. 4. Mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message to the base station.

j.

Set the levels as specified in Table 3.5.4-3. Table 3.5.4-3 Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io Unit dB dB dB dBm/1.23 MHz dB Channel 1 -10 -7 -7 -75 -20.2 Channel 2 0 -7 -7 -75 -10.2

19

20 21 22 2

k.

Raise the level of Channel 1 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Verify the following:

14

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11

Parameter Vehicle Speed Number of Paths Path 2 Power (Relative to Path 1) Path 3 Power (Relative to Path 1) Delay from Path 1 to Input Delay from Path 2 to Input Delay from Path 3 to Input dB dB s s s l. 1. Pilot Strength Measurement Message is generated when the channel 1 Pilot Ec/Io is at a level above T_ADD. 2. Base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station. 3. Channel 1 and Channel 2 are in the Active Set at the action time of the message. 4. Mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message to the base station. Set the levels as specified in Table 3.5.4-4. Table 3.5.4-4 Unit km/hr Value 100 3 0 -3 0 2 14.5

12 13 14 15 16 17 18 19 20 21 22 23 24 25

m.

Lower the level of Channel 2 in steps of 1 dB with a dwell time of 8 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Verify the following: 1. Pilot Strength Measurement Message is generated when the Channel 2 is at a Pilot Ec/Io level below T_DROP for a period of TT_DROP. 2. Base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station. 3. Only Channel 1 is in the Active Set at the action time of the message. 4. Mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message to the base station.

n. o.

Repeat steps a through l under 3 Ray Rayleigh fading at 100 km/hr fading condition as specified in Table 3.5.4-4. Repeat steps a through l under 1 Ray Rayleigh fading at 3 km/hr fading condition.

15

1 13.5.5
Minimum Standard

3GPP2 C.S0044-A v1.0

2The mobile station shall generate the Pilot Strength Measurement Message at the appropriate 3time as specified in steps f, h, j, and l and the handoff shall be completed successfully.

43.6 53.6.1 7 8 9 11 12
a. b. c.

Hard Handoff in Fading Definition

6This test verifies hard handoff under various fading conditions:

1 Ray Rayleigh fading at 30 km/hr 3 Ray Rayleigh fading at 100 km/hr 1 Ray Rayleigh fading at 3 km/hr

10Under various deployment scenarios:

a. b.

Between frequencies On the same frequency Traceability

133.6.2
14(See[4])

152.6.6.1.1 162.6.6.2.5 172.6.6.2.8 183.6.6.1.1 193.6.6.2.2 203.6.3

21None

Types of Handoff Handoff Messages CDMA-to-CDMA Hard Handoff Types of Handoff Call Processing During Handoff

Call Flow Example(s)

223.6.4 23 24 25 26 27 28
b. a.

Method of Measurement Setup test as shown in Figure A-2. 1. The Forward Channel from base station 1 on frequency F1 has an arbitrary pilot PN offset index P1 and is called Channel 1. 2. The Forward Channel from base station 2 on frequency F2 has an arbitrary pilot PN offset index P2 and is called Channel 2. Set the test parameters as shown in Table 3.6.4-17.

16

13GPP2 C.S0044-A v1.0 1

Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io
2

Table 3.6.4-17 Unit dB dB dB dBm/1.23 MHz dB Channel 1 0 -7 -7 -75 -10 Channel 2 0 -7 -7 -75 -10

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

c. d. e. f. g.

Set reverse link attenuation to balance forward and reverse links (approx. 90 dB). Set the channel simulators for 1 Ray Rayleigh fading, 30 km/hr. Setup a mobile station originated call on Channel 1. Verify user data in both directions. Initiate handoff from Channel 1 to Channel 2. Verify that base station 1 initiates a handoff from Channel 1 to Channel 2 by sending a General Handoff Direction Message, Universal Handoff Direction Message, or an Extended Handoff Direction Message. Upon receiving an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message at the mobile station, verify the following: 1. Only Channel 2 is in the Active Set at the action time of the message. 2. The mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message to the base station.

h.

i.

Repeat steps a through h, with the channel simulators set to 3 Ray Rayleigh at 100 km/hr in step d. Use the setup shown in Table 3.5.4-4. The expected results are as given above for the previous test. Table 3.6.4-2 Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io Unit dB dB dB dBm/1.23 MHz dB Channel 1 0 -7 -7 -75 -11.8 Channel 2 0 -7 -7 -75 -11.8

21

17

1 1 2 3 4 5 6 7 8 9 10 11
l. j. k.

3GPP2 C.S0044-A v1.0 Repeat steps a through h, with the channel simulators set to 1 Ray Rayleigh at 3 km/hr in step d. The expected results are as given above for the previous test. Repeat steps c through j for the scenario where the hard handoff is performed between two CDMA channels on the same frequency, with the setup test as shown in Figure A5: 1. Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1. 2. Forward Channel from base station 2 has an arbitrary pilot PN offset index P2 and is called Channel 2. 3. Test parameters set as shown in Table 3.6.4-2. Note that in this case a hard handoff can be forced by excluding P1 from the Active Set. Minimum Standard

123.6.5

13The mobile station shall comply with step h.

143.7 153.7.1

Hard Handoff Between Different Band Classes Definition

16This test verifies hard handoff between two different band classes. Both band classes are 17supported by the mobile station and base station.

183.7.2
19(see[4])

Traceability

202.6.6.1.1 212.6.6.2.5 222.6.6.2.8 233.6.6.1.1 243.6.6.2.2 253.7.3.3.2.17 263.7.3.3.2.31 273.7.3.3.2.36

28(see [1])

Types of Handoff Handoff Messages CDMA-to-CDMA Hard Handoff Types of Handoff Call Processing During Handoff Extended Handoff Direction Message General Handoff Direction Message Universal Handoff Direction Message

292.1.1.1 303.7.3
31None

Channel Spacing and Designation Call Flow Example(s)

323.7.4 33 2
a.

Method of Measurement Setup test as shown in Figure A-5. 18

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6

Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io
7

1. The Forward Channel from the base station 1 in Band Class X has an arbitrary pilot PN offset index P1 and is called Channel 1. 2. The Forward Channel from the base station 2 in Band Class Y has an arbitrary pilot PN offset index P2 and is called Channel 2. b. Set the test parameters as shown in Table 3.7.4-18 Table 3.7.4-18 Unit dB dB dB dBm/1.23 MHz dB Band Class X -5 -7 -7 -75 -13.2 Band Class Y -5 -7 -7 -75 -13.2

8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

c. d. e. f.

Set reverse link attenuation to balance forward and reverse links (approx. 90 dB). Setup a call in Channel 1. Verify user data in both directions. Initiate handoff from base station 1 to base station 2. Verify the base station sends a General Handoff Direction Message, Universal Handoff Direction Message, or an Extended Handoff Direction Message with proper parameters (refer to tables in Annex B) to initiate handoff. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message and the handoff is completed successfully. Reconnect Channel 1 to base station 1 with parameters listed in Table 3.5.4-16. Initiate handoff from base station 1 to base station 2. Verify that base station 1 sends a General Handoff Direction Message, Universal Handoff Direction Message, or an Extended Handoff Direction Message with proper parameters (refer to tables in Annex B) to initiate handoff. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message and the handoff is completed successfully. This test can be repeated for hard handoffs between other band classes. Minimum Standard

g. h. i.

j. k.

253.7.5

26The mobile station shall comply with steps g and k.

19

1 13.8 23.8.1
Hard Handoff with and without Return on Failure Definition

3GPP2 C.S0044-A v1.0

3This test verifies the mobile station behavior when hard handoff fails and: 4return on failure is allowed. 5return on failure is disallowed.

63.8.2 72.6.4.2

Traceability (See[4]) Traffic Channel Initialization Substate Types of Handoff Handoff Messages Hard Handoff With Return On Failure Restoring the Configuration Overview Call Processing During Handoff General Handoff Direction Message Universal Handoff Direction Message

82.6.6.1.1 92.6.6.2.5 102.6.6.2.8.2 112.6.6.2.8.2.1 123.6.6.1 133.6.6.2.2 143.7.3.3.2.31 153.7.3.3.2.36 163.8.3

17None

Call Flow Example(s)

183.8.4 19 20 21 22 23 24 25
b. a.

Method of Measurement Setup test as shown in Figure A-5. 1. The Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1. 2. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P2 and is called Channel 2. Set the test parameters as shown in Table 3.8.4-19. Table 3.8.4-19 Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io Unit dB dB dB dBm/1.23 MHz dB Channel 1 -5 -7 -7 -75 -13.2 Channel 2 -5 -7 <-20 (or none) -75 -12

26

20

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 223.9 233.9.1

c. d. e. f. Reverse link attenuation should be set to balance the forward and reverse links (approximately 90 dB). Setup a mobile station originated call on Channel 1. Verify user data in both directions. For Test 1, instruct the base station to initiate a handoff to Channel 2 and allow for return on failure. Verify that the base station sends a General Handoff Direction Message or a Universal Handoff Direction Message with the RETURN_IF_HANDOFF_FAIL = 1. Due to the low traffic gain level on Channel 2 (refer to Table 3.6.4-17), the mobile station will attempt the hard handoff as directed by the base station, but not complete it, and declare a hard handoff failure. Verify the mobile station returns to Channel 1 and verify user data in both directions. For Test 2, instruct the base station to initiate a handoff to Channel 2 and disallow for return on failure. Verify that the base station sends a General Handoff Direction Message or a Universal Handoff Direction Message with RETURN_IF_HANDOFF_FAIL = 0 Due to the low traffic gain level on Channel 2 (refer to Table 3.6.4-17), the mobile station will attempt the hard handoff as directed by the base station, but not complete it, and declare a hard handoff failure. Verify the mobile station does not restore to the previous configuration and does not return to Channel 1. Search Window Size and Offset (Traffic State) Definition

g.

h. i.

j.

k.

24A CDMA call is established on sector of sectored base station 1. Delay is applied to sector 25and base station 2. The level of sector is raised sufficiently high to ensure intersector handoff is 26possible. The level of base station 2 is raised sufficiently high to ensure soft handoff is possible. 27In section 3.9.3.1, the pilot strength measurements of base station 2 and sector are checked 28against the search window size and search window offset settings for each of the neighbor pilots. 29If the delay is greater than the search window size for the neighbor pilot then the mobile station 30shall not send a Pilot Strength Measurement Message. 31In section 3.9.3.2, the pilot strength measurements of base station 2 and sector are checked 32against a common search window size (i.e. SRCH_WIN_N). If the delay is greater than the 33search window size for the neighbor pilot then the mobile station shall not send a Pilot Strength 34Measurement Message.

353.9.2

Formulas

36Pilot_PN_sel = nearest Pilot PN in the neighbor set not to exceed the integer of 37PILOT_PN_PHASE/64. 38Neighbor_Chip_Offset = PILOT_PN_PHASE-(Pilot_PN_sel*64) 39Num_Chips = Set_Chip_Offset - Sim_Chip_Offset

21

1 1Chip_Delay (s) =
Num_chip x 244m 300m/ s

3GPP2 C.S0044-A v1.0

2PILOT_PN_PHASE is the pilot PN phase obtained from the mobile station log file in units of 3chips. PILOT_PN_PHASE is referenced to the zero offset Pilot PN sequence. Pilot_PN_sel 4selects the closest neighbors Pilot PN and the value is subtracted from the PILOT_PN_PHASE 5to determine the residual chip delay (i.e. Neighbor_Chip_Offset). Set_Chip_Offset is the desired 6number of chip offsets for a particular test case. Sim_Chip_Offset is the inherent delay for a pilot 7due to the time alignment/calibration of the equipment. Chip_Delay is the actual delay in usec the 8tester should vary with the test equipment (e.g. fader) to achieve the proper Set_Chip_Offset (this 9includes the inherent delay measured for Sim_Chip_Offset. When properly adjusted, the 10Set_Chip_Offset should equal to the Neighbor_Chip_Offset.

113.9.3
12(See[4])

Traceability

132.6.6 142.6.6.2.1 15Table 2.6.6.2.1 16Table 2.6.6.2.1-2 172.6.6.2.5.2 182.7.2.3.2.5 192.7.2.3.2.34 203.6.6 213.7.2.3.2.1 223.7.2.3.2.22 233.7.2.3.2.34 243.9.4
25None

Handoff Procedures Pilot Search Search Window Sizes Search Window Offset Processing of Reverse Traffic Channel Handoff Messages Pilot Strength Measurement Message Extended Pilot Strength Measurement Message Handoff Procedures System Parameters Message General Neighbor List Message Universal Neighbor List Message

Call Flow Example(s)

263.9.5 273.9.5.1 28
29

Method of Measurement Method of Measurement with NGHBR_SRCH_MODE = 10 (search window size per neighbor

30

Table 3.9.5-20 Test Cases for NGHBR_SRCH_MODE=10 (Traffic State) Test Case 1 P2 win size 7 P2 win offset 0 P2 Set_Chip_ Offset P3 win/4 +P3 offset P3 win size 9 P3 win offset 0 P3 Set_Chip_ Offset P3 win/4 +P3 offset

22

13GPP2 C.S0044-A v1.0

2 7 0 P3 win/2 +P3 offset 3 7 0 P3 win/2 +P3 offset +10 chips 4 7 0 P3 win/2 +P3 offset 5
1

P3 win/2 +P3 offset

P3 win/2 +P3 offset +10 chips

P3 win/2 +P3 offset

P3 win/2

P3 win/2

2 3 4 5 6 7 8 9 10 11
12

a.

Setup test as shown in Figure A-4. 1. The Forward Channel from sector of base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1. 2. The Forward Channel from sector of base station 1 has an arbitrary pilot PN offset index P2 and is called Channel 2. 3. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P3 and is called Channel 3.

b. c.

Set the test parameters as specified in Table 3.9.5-2. The Reverse Link attenuation should be set to balance the forward and reverse links (approximately 90 dB).

13

Table 3.9.5-2 Test Parameters for Search Window per Neighbor (Traffic State) Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io Unit dB dB dB dBm/1.23 MHz dB Channel 1 1 -7 -7 -75 9.6 Channel 2 -20 -7 -7 -75 -30.6 Channel 3 -20 -7 -7 -75 -30.6

15Note: The Pilot Ec/I0 value is calculated from the parameters set in the table. It is not a settable
16parameter itself.

14

17 18

d.

Set the following values in the General Neighbor List Message (GNLM) or the Universal Neighbor List Message (UNLM):

23

1
1

3GPP2 C.S0044-A v1.0

Field NGHBR_CONFIG_PN_INCL NGHBR_SRCH_MODE SRCH_OFFSET_INCL

2

Value 1 (for GNLM only) 10 1

Neighbor Setting for P2 NGHBR_PN SRCH_WIN_NGHBR SRCH_OFFSET_NGHBR

3

P2 7 (40 chips) 0 (no offset)

Neighbor Setting for P3 NGHBR_PN SRCH_WIN_NGHBR SRCH_OFFSET_NGHBR

4

P3 9 (80 chips) 0 (no offset)

5 6 7 8 9 10 11 12 13 14 15 16 17

e. f.

Determine the inherent delay of the channel simulator (i.e. Sim_Chip_Offset). For Test 1, set the delay on both Channel 2 and on Channel 3 to a Chip_Delay such that Set_Chip_Offset =(SRCH_WIN_NGHBR of P3)/4 + SRCH_OFFSET_NGHBR of P3 (i.e Set_Chip_Offset of P2 is equal to Set_Chip_Offset of P3). Setup a mobile station originated call. Raise the level of Channel 2 to or/Ioc = +1 dB without dropping the call. Raise the level of Channel 3 to or/Ioc = +1 dB without dropping the call. End the call. Reset the test parameters as specified in Table 3.9.5-2. Verify the following: 1. The mobile station shall generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 2 pilot strength is raised up to the same pilot strength as Channel 1 (or/Ioc=1dB).

g. h. i. j. k. l.

24

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

34

2. The neighbor_Chip_Offset of P2 calculated from PILOT_PN_PHASE of the Pilot Strength Measurement Message or the Extended Pilot Strength Measurement Message generated in step h shall equal the Set_Chip_Offset of P2. 3. The mobile station shall also generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 3 pilot strength is raised up to the same pilot strength as Channel 1 (or/Ioc=1 dB). 4. The neighbor_Chip_Offset of P3 calculated from PILOT_PN_PHASE of the Pilot Strength Measurement Message or the Extended Pilot Strength Measurement Message generated in step i shall equal the Set_Chip_Offset of P3. m. n. o. For Test 2, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that Set_Chip_Offset = (SRCH_WIN_NGHBR of P3)/2 + SRCH_OFFSET_NGHBR of P3. Repeat steps g to k. Verify the following: 1. The mobile station shall not generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 2 pilot strength is raised up to the same pilot strength as Channel 1 (or/Ioc=1dB). 2. The mobile station shall generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 3 pilot strength is raised up to the same pilot strength as Channel 1 (or/Ioc=1 dB). 3. The neighbor_Chip_Offset of P2 calculated from PILOT_PN_PHASE of the Pilot Strength Measurement Message or the Extended Pilot Strength Measurement Message generated in step i shall equal the Set_Chip_Offset of P3. p. For Test 3, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that Set_Chip_Offset = (SRCH_WIN_NGHBR of P3)/2 + SRCH_OFFSET_NGHBR of P3 + 10 chips. Repeat steps g to k. Verify that the mobile station does not generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when either the Channel 2 or Channel 3 pilot strength is raised up to the same pilot strength as Channel 1 (or/Ioc=1 dB). Set the following values in the General Neighbor List Message or the Universal Neighbor List Message:

q. r.

s.

Field NGHBR_CONFIG_PN_INCL NGHBR_SRCH_MODE

Value 1 (for GNLM only) 10

25

1
SRCH_OFFSET_INCL
1

3GPP2 C.S0044-A v1.0 1

Neighbor Setting for P2 NGHBR_PN SRCH_WIN_NGHBR SRCH_OFFSET_NGHBR

2

P2 7 (40 chips) 0 (no offset)

Neighbor Setting for P3 NGHBR_PN SRCH_WIN_NGHBR SRCH_OFFSET_NGHBR

3

P3 7 (40 chips) 1 (window_size/2)

4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
19

t. u. v.

For Test 4, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that Set_Chip_Offset = (SRCH_WIN_NGHBR of P3)/2 + SRCH_OFFSET_NGHBR of P3. Repeat steps g to k. Verify the following: 1. The mobile station shall not generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 2 pilot strength is raised up to the same pilot strength as Channel 1 (or/Ioc=1dB). 2. The mobile station shall generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 3 pilot strength is raised up to the same pilot strength as Channel 1 (or/Ioc=1 dB). 3. The neighbor_Chip_Offset of P3 calculated from PILOT_PN_PHASE of the Pilot Strength Measurement Message or the Extended Pilot Strength Measurement Message generated in step i shall equal the Set_Chip_Offset of P3.

w.

Set the following values in the General Neighbor List Message or the Universal Neighbor List Message:

Field NGHBR_CONFIG_PN_INCL NGHBR_SRCH_MODE

Value 1 (for GNLM only) 10

26

13GPP2 C.S0044-A v1.0

SRCH_OFFSET_INCL
1

Neighbor Setting for P2 NGHBR_PN SRCH_WIN_NGHBR SRCH_OFFSET_NGHBR

2

P2 7 (40 chips) 0 (no offset)

Neighbor Setting for P3 NGHBR_PN SRCH_WIN_NGHBR SRCH_OFFSET_NGHBR

3

P3 7 (40 chips) 4 (-window_size/2)

4 5 6 7 8 9 10 11 12 13 14 15 16

x. y. z.

For Test 5, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that Set_Chip_Offset =(SRCH_WIN_NGHBR of P3)/2. Repeat steps g to k. Verify the following: 1. The mobile station shall generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 2 pilot strength is raised up to the same pilot strength as Channel 1 (or/Ioc=1dB). 2. The neighbor_Chip_Offset of P2 calculated from PILOT_PN_PHASE of the Pilot Strength Measurement Message or the Extended Pilot Strength Measurement Message generated in step h shall equal the Set_Chip_Offset of P2. 3. The mobile station shall not generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 3 pilot strength is raised up to the same pilot strength as Channel 1 (or/Ioc=1 dB). Method of Measurement with NGHBR_SRCH_MODE = 00 (same search window size for all neighbor)

173.9.5.2 18
19

20

Table 3.9.5-3 Test Cases for NGHBR_SRCH_MODE=00 (Traffic State) Test Case 1 Neighbor Message GNLM P2 win size 7 P2 Set_Chip_Offset SRCH_Win_N/2 P3 win size 7 P3 Set_Chip_Offset SRCH_WIN_N/4

27

3GPP2 C.S0044-A v1.0

2 3

GNLM UNLM

7 7

SRCH_Win_N/2 + 10 chips SRCH_Win_N/2

7 7

SRCH_WIN_N/4 + 10 chips SRCH_WIN_N/4

UNLM

SRCH_Win_N/2 + 10 chips

SRCH_WIN_N/4 + 10 chips

2 3 4 5 6 7 8 9 10 11 12
13

a.

Setup test as shown in A-4 1. The Forward Channel from sector of base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1. 2. The Forward Channel from sector of base station 1 has an arbitrary pilot PN offset index P2 and is called Channel 2. 3. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P3 and is called Channel 3.

b. c. d.

Set the test parameters as specified in Table 3.9.5-3. The Reverse Link attenuation should be set to balance the forward and reverse links (approximately 90 dB). Set the following value in the System Parameters Message:

Field SRCH_WIN_N
14

Value 7 (40 chips)

15
16

e.

Set the following values in the General Neighbor List Message:

Field NGHBR_SRCH_MODE
17

Value 00

18 19 20 21 22

f.

For Tests 1 and 3, set the delay on Channel 2 to a Chip_Delay such that Set_Chip_Offset of P2 =SRCH_WIN_N/2, and set the delay on Channel 3 to a Chip_Delay such that Set_Chip_Offset=SRCH_WIN_N/4. Setup a mobile station originated call. Raise the level of Channel 2 to or/Ioc = +1 dB without dropping the call.

g. h.

28

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

32

i. j. k. l.

Raise the level of Channel 3 to or/Ioc = +1 dB without dropping the call. End the call. Reset the test parameters as specified in Table 3.9.5-3. Verify the following: 1. The mobile station shall generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 2 pilot strength is raised up to the same pilot strength as Channel 1 (or/Ioc=1dB). 2. The neighbor_Chip_Offset of P2 calculated from PILOT_PN_PHASE of the Pilot Strength Measurement Message or the Extended Pilot Strength Measurement Message generated in step h shall equal the Set_Chip_Offset of P2. 3. The mobile station shall also generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 3 pilot strength is raised up to the same pilot strength as Channel 1 (or/Ioc=1 dB). 4. The neighbor_Chip_Offset of P3 calculated from PILOT_PN_PHASE of the Pilot Strength Measurement Message or the Extended Pilot Strength Measurement Message generated in step i shall equal the Set_Chip_Offset of P3.

m.

For Tests 2 and 4, set the delay on Channel 2 to a Chip_Delay such that Set_Chip_Offset of P2 =(SRCH_WIN_N/2)+10 chips, and set the delay on Channel 3 to a Chip_Delay such that Set_Chip_Offset=(SRCH_WIN_N/4)+10 chips. Repeat steps g to k. Verify the following: 1. The mobile station shall not generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 2 pilot strength is raised up to the same pilot strength as Channel 1 (or/Ioc=1dB). 2. The mobile station shall generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 3 pilot strength is raised up to the same pilot strength as Channel 1 (or/Ioc=1 dB). 3. The neighbor_Chip_Offset of P2 calculated from PILOT_PN_PHASE of the Pilot Strength Measurement Message or the Extended Pilot Strength Measurement Message generated in step i shall equal the Set_Chip_Offset of P3.

n. o.

p.

Set the following values in the Universal Neighbor List Message:

Field NGHBR_SRCH_MODE SRCH_WIN_N

33

Value 00 7 (40 Chips)

29

1 1 2
q.

3GPP2 C.S0044-A v1.0 For Tests 3 and 4 repeat steps b to o using parameter values in step t sent over the Universal Neighbor List Message instead of the General Neighbor List Message. Minimum Standard For section 3.9.4.1:

33.9.6 43.9.6.1

5Verify steps l, o, r, v and z for Tests 1 to 5.

63.9.6.2

For section 3.9.4.2:

7Verify step l for Tests 1 and 3. 8Verify step o for Tests 2 and 4.

93.10 Search Window Size and Offset (Idle State) 103.10.1 Definition
11The mobile station is operating in idle state and monitoring sector of base station 1. Delay is 12applied to both sector of base station 1 and base station 2. The level of neighbor pilots are 13raised sufficiently high to ensure idle handoff is possible. 14In section 3.9.3.1, the pilot strength measurements of base station 2 and sector of base station 151 are checked against the search window size and search window offset settings for each of the 16neighbor pilots. If the delay is greater than the search window size for the neighbor pilot then the 17mobile station shall not idle handoff to that neighbor pilot. 18In section 3.9.3.2, the pilot strength measurements of base station 2 and sector of base station 191are checked against a common search window size (i.e. SRCH_WIN_N). If the delay is greater 20than the search window size for the neighbor pilot then the mobile station shall not idle handoff to 21that neighbor pilot. 22Formulas 23Num_Chips = Set_Chip_Offset - Sim_Chip_Offset

24Chip_Delay (s) =

Num_chip x 244m 300m/ s

25Set_Chip_Offset is the desired number of chip offsets for a particular test case. Sim_Chip_Offset 26is the inherent delay for a pilot due to the time alignment/calibration of the equipment. Chip_Delay 27is the actual delay in usec the tester should vary with the test equipment (e.g. fader) to achieve 28the proper Set_Chip_Offset (this includes the inherent delay measured for Sim_Chip_Offset. 29When properly adjusted, the Set_Chip_Offset should equal to the neighbor pilots chip offset from 30zero chip delay.

313.10.2 Traceability
32(See[4]);

332.6.6 342.6.6.2.1 35Table 2.6.6.2.1 36Table 2.6.6.2.1-2

Handoff Procedures Pilot Search Search Window Sizes Search Window Offset

30

13GPP2 C.S0044-A v1.0 13.6.6 23.7.2.3.2 33.7.2.3.2.22 43.7.2.3.2.34

Handoff Procedures System Parameters Message General Neighbor List Message Universal Neighbor List Message

53.10.3 Call Flow Example(s)

6None

73.10.4 Method of Measurement 83.10.4.1 Method of Measurement with NGHBR_SRCH_MODE = 10 (search window size per 9 neighbor)
10

11

Table 3.10.4-21 Test Cases for NGHBR_SRCH_MODE=10 (Idle State) Test Case 1 P2 win size 7 P2 win offset 0 P2 Set_Chip_ Offset P3 win/4 +P3 offset 2 7 0 P3 win/2 +P3 offset 3 7 0 P3 win/2 +P3 offset +10 chips 4 7 0 P3 win/2 +P3 offset 5 7 0 P3 win/2 7 4 7 1 9 0 9 0 P3 win size 9 P3 win offset 0 P3 Set_Chip_ Offset P3 win/4 +P3 offset P3 win/2 +P3 offset P3 win/2 +P3 offset +10 chips P3 win/2 +P3 offset P3 win/2

12

13 14 15 16 17 18 19

a.

Setup test as shown in Figure A-2. 1. The Forward Channel from sector of base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1. 2. The Forward Channel from sector of base station 1 has an arbitrary pilot PN offset index P2 and is called Channel 2. 3. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P3 and is called Channel 3.

31

1 1 2 3 4
5

3GPP2 C.S0044-A v1.0 b. c. The Reverse Link attenuation should be set to balance the forward and reverse links (approximately 90 dB). Set the following values in the General Neighbor List Message (GNLM) or the Universal Neighbor List Message:

Field NGHBR_CONFIG_PN_INCL NGHBR_SRCH_MODE SRCH_OFFSET_INCL

6

Value 1 (for GNLM only) 10 1

Neighbor Setting for P2 NGHBR_PN SRCH_WIN_NGHBR SRCH_OFFSET_NGHBR

7

P2 7 (40 chips) 0 (no offset)

Neighbor Setting for P3 NGHBR_PN SRCH_WIN_NGHBR SRCH_OFFSET_NGHBR

8

P3 9 (80 chips) 0 (no offset)

9 10 11 12 13
14

d. e.

Determine the inherent delay of the channel simulator (i.e. Sim_Chip_Offset). For Test 1, set the delay on both Channel 2 and on Channel 3 to a Chip_Delay such that Set_Chip_Offset =(SRCH_WIN_NGHBR of P3)/4 + SRCH_OFFSET_NGHBR of P3 (i.e. Set_Chip_Offset of P2 is equal to Set_Chip_Offset of P3). Set the test parameters as specified in Table 3.10.4-212 for state S1 in all 3 channels.

f.

15

Table 3.10.4-2 Test Parameters for Search Window per Neighbor (Idle State) Parameter or/Ioc Unit dB Channel 1 1 (S1 and S2) Channel 2 -20 for S1 5 for S2 Channel 3 -20 for S1 5 for S2

32

13GPP2 C.S0044-A v1.0

Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io dB dB dBm/1.23 MHz dB -7 -7 -75 9.6 for S1 -13.3 for S2
1

-7 -7 -75 -30.6 for S1 -9.3 for S2

-7 -7 -75 -30.6 for S1 -9.3 for S2

2Note: The Pilot Ec/I0 value is calculated from the parameters set in the table. It is not a settable
3parameter itself.

4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
27 28

g. h.

Allow the mobile station to monitor Channel 1 while in idle state. Raise the level of Channel 2 to or/Ioc = +5 dB (State S2 for Channel 2 in Table 3.10.42). Reset the test parameter as specified in Table 3.10.4-2for state S1 in all 3 channels. Raise the level of Channel 3 to or/Ioc = +5 dB (State S2 for Channel 3 in Table 3.10.42). Verify the following: 1. The mobile station shall perform an idle handoff to Channel 2 in step h. 2. The mobile station shall perform an idle handoff to Channel 3 in step j. 3. For Test 2, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that Set_Chip_Offset = (SRCH_WIN_NGHBR of P3)/2 + SRCH_OFFSET_NGHBR of P3.

i. j.

k.

l. m.

Repeat steps f to j. Verify the following: 1. The mobile station shall not perform an idle handoff to Channel 2 in step h. 2. The mobile station shall perform an idle handoff to Channel 3 in step j. 3. For Test 3, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that Set_Chip_Offset = (SRCH_WIN_NGHBR of P3)/2 + SRCH_OFFSET_NGHBR of P3 + 10 chips.

n. o. p.

Repeat steps f to j. Verify that the mobile station does not perform idle handoff(s) in either step h or j. Set the following values in the General Neighbor List Message or the Universal Neighbor List Message:

Field

Value

33

1
NGHBR_CONFIG_PN_INCL NGHBR_SRCH_MODE SRCH_OFFSET_INCL
1

3GPP2 C.S0044-A v1.0 1 (for GNLM only) 10 1

Neighbor Setting for P2 NGHBR_PN SRCH_WIN_NGHBR SRCH_OFFSET_NGHBR

2

P2 7 (40 chips) 0 (no offset)

Neighbor Setting for P3 NGHBR_PN SRCH_WIN_NGHBR SRCH_OFFSET_NGHBR

3

P3 7 (40 chips) 1 (window_size/2)

4 5 6 7 8 9 10 11
12

q. r. s.

For Test 4, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that Set_Chip_Offset = (SRCH_WIN_NGHBR of P3)/2 + SRCH_OFFSET_NGHBR of P3. Repeat steps g to k. Verify the following: 1. The mobile station shall not perform an idle handoff to Channel 2 in step h. 2. The mobile station shall perform an idle handoff to Channel 3 in step j.

t.

Set the following values in the General Neighbor List Message or the Universal Neighbor List Message:

Field NGHBR_CONFIG_PN_INCL NGHBR_SRCH_MODE SRCH_OFFSET_INCL

13

Value 1 (for GNLM only) 10 1

Neighbor Setting for P2

34

13GPP2 C.S0044-A v1.0

SRCH_WIN_NGHBR SRCH_OFFSET_NGHBR
1

7 (40 chips) 0 (no offset)

Neighbor Setting for P3 NGHBR_PN SRCH_WIN_NGHBR SRCH_OFFSET_NGHBR

2

P3 7 (40 chips) 4 (-window_size/2)

3 4 5 6 7 8

u. v. w.

For Test 5, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that Set_Chip_Offset = (SRCH_WIN_NGHBR of P3)/2. Repeat steps g to k. Verify the following: 1. The mobile station shall perform an idle handoff to Channel 2 in step h. 2. The mobile station shall not perform an idle handoff to Channel 3 in step j.

93.10.4.2 Method of Measurement with NGHBR_SRCH_MODE = 00 (same search window size 10 for all neighbor) 11
Table 3.10.4-3 Test Cases for NGHBR_SRCH_MODE=00 (Idle State) Test Case 1 Neighbor Message GNLM P2 win size 7 P2 Set_Chip_Offset SRCH_Win_N/2 P3 win size 7 P3 Set_Chip_Offset SRCH_WIN_N/4

2 3

GNLM UNLM

7 7

SRCH_Win_N/2 + 10 chips SRCH_Win_N/2

7 7

SRCH_WIN_N/4 + 10 chips SRCH_WIN_N/4

UNLM

SRCH_Win_N/2 + 10 chips

SRCH_WIN_N/4 + 10 chips

12

13 14 15

a.

Setup test as shown in Figure A-2. 1. The Forward Channel from sector of base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1.

35

1 1 2 3 4 5 6 7
8

3GPP2 C.S0044-A v1.0 2. The Forward Channel from sector of base station 1 has an arbitrary pilot PN offset index P2 and is called Channel 2. 3. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P3 and is called Channel 3. b. c. The Reverse Link attenuation should be set to balance the forward and reverse links (approximately 90 dB). Set the following value in the System Parameters Message:

Field SRCH_WIN_N
9

Value 7 (40 chips)

10
11

d.

Set the following values in the General Neighbor List Message:

Field NGHBR_SRCH_MODE
12

Value 00

13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

e.

For Tests 1 and 3, set the delay on Channel 2 to a Chip_Delay such that Set_Chip_Offset of P2 =SRCH_WIN_N/2, and set the delay on Channel 3 to a Chip_Delay such that Set_Chip_Offset=SRCH_WIN_N/4. Set the test parameters as specified in Table 3.10.4-2 for state S1 in all 3 channels. Allow the mobile station to monitor Channel 1 while in idle state. Raise the level of Channel 2 to or/Ioc = +5 dB (State S2 for Channel 2 in Table 3.10.42). Reset the test parameter as specified in Table 3.10.4-2 for state S1 in all 3 channels. Raise the level of Channel 3 to or/Ioc = +5 dB (State S2 for Channel 3 in Table 3.10.42). Verify the following: 1. The mobile station shall perform an idle handoff to Channel 2 in step h. 2. The mobile station shall perform an idle handoff to Channel 2 in step j. 3. For Tests 2 and 4, set the delay on Channel 2 to a Chip_Delay such that Set_Chip_Offset of P2 =(SRCH_WIN_N/2)+10 chips, and set the delay on Channel 3 to a Chip_Delay such that Set_Chip_Offset=(SRCH_WIN_N/4)+10 chips.

f. g. h.

i. j.

k.

l.

Repeat steps f to j.

36

13GPP2 C.S0044-A v1.0 1 2 3 4

5

m.

Verify the following: 1. The mobile station shall not perform an idle handoff to Channel 2 in step h. 2. The mobile station shall perform an idle handoff to Channel 2 in step j.

n.

Set the following values in the Universal Neighbor List Message:

Field NGHBR_SRCH_MODE SRCH_WIN_N

6

Value 00 7 (40 Chips)

7 8

o.

For Tests 3 and 4, repeat steps b to n using parameter values in step t sent over the Universal Neighbor List Message instead of the General Neighbor List Message.

93.10.5 Minimum Standard 103.10.5.1 For section 3.9.3.1:

11Verify steps k, n and q for Tests 1 to 3, Tests 6 to 20 and Tests 23 to 34. Verify steps u and y for 12Tests 4 to 5 and Tests 21 to 22.

133.10.5.2 For section 3.9.3.2:

14Verify step k for Tests 1 and 3. 15Verify step n for Tests 2 and 4.

163.11 Channel Assignment into Soft Handoff (CASHO) 173.11.1 Definition

18This tests for mobile operation of Channel Assignment into Soft Handoff (CASHO). CASHO 19allows multiple pilots to be assigned in the Extended Channel Assignment Message from the 20pilots reported in the Origination Message or Page Response Message.

213.11.2 Traceability
22(see [4])

233.7.2.3.2.13 242.6.3.1.7 252.6.3.3

Extended System Parameters Message Monitoring Pilots Page Response Substate

263.11.3 Call Flow Example(s)

27None

37

1 13.11.4 Method of Measurement 2 3 4 5 6 7 8 9 10

a. b. c. d. e. f.

3GPP2 C.S0044-A v1.0

Connect the mobile station as shown in Figure A-5. Ensure both pilot Ec/Io values are well above T_ADD. Allow the mobile station to come to the idle state on one of the base stations. Make a mobile station originated call. Verify both base station pilots are reported in the Origination Message. Verify the mobile station receives an Extended Channel Assignment Message assigning both pilots and calls complete normally. Repeat steps c-e for a mobile station terminated call with the exception that in step d the Page Response Message is used instead of the Origination Message.

113.11.5 Minimum Standard

12The mobile station shall comply with the requirements in steps d, e and f.

133.12 Traffic Channel Preamble during Hard Handoff Between Frequencies in same band 143.12.1 Definition
15The mobile station is transitioned between base stations with different CDMA frequency (channel) 16assignments in the same band. The Traffic Channel Preamble is a sequence of all-zero frames 17that is sent by the mobile station on the Reverse Traffic Channel as an aid to Traffic Channel 18acquisition.

193.12.2 Traceability
20(See[4])

212.6.6.1.1 222.6.6.2.5 232.6.6.2.8 243.6.6.1.1 253.6.6.2.2

26(See[2])

Types of Handoff Handoff Messages CDMA-to-CDMA Hard Handoff Types of Handoff Call Processing During Handoff

272.1.3.2.4 282.1.3.6.2.3

Reverse Pilot Channel Operation during RTC Preamble Reverse Traffic Channel Preamble

293.12.3 Call Flow Example(s)

30None

313.12.4 Method of Measurement 32

a. Setup test as shown in Figure A-2.

38

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8

9

1. The Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1. 2. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P2 and is called Channel 2. 3. The AWGN source should be on the frequency of Channel 2. (It is advisable to achieve the maximum possible difference in frequency separation between Channel 1 and Channel 2) b. Set the test parameters as shown in Table 3.12.4-22.

10
Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io Unit dBm dB dB

Table 3.12.4-22 Channel 1 N/A -7 -7 N/A -7 Channel 2 -5 -7 -7 -75 -13.2

dBm/1.23 MHz dB

11 12 13 14 15 16 17 18 19 20 21 22 23 24

c. d. e. f. g. h.

Set reverse link attenuation to balance forward and reverse links (approx. 90 dB). Configure base station 1 and base station 2 for RC1 or RC2. Setup a mobile station originated call on Channel 1. Verify user data in both directions. Initiate handoff from Channel 1 to Channel 2. Verify that the base station 1 sends the General Handoff Direction Message, Universal Handoff Direction Message, or Extended Handoff Direction Message with correct NUM_PREAMBLE value. Verify the Reverse Traffic Channel preamble length. Wait 20 seconds then initiate handoff from Channel 2 to Channel 1. Verify that the base station 2 sends the General Handoff Direction Message, Universal Handoff Direction Message, or Extended Handoff Direction Message correct NUM_PREAMBLE value. Verify the Reverse Traffic Channel preamble length. Configure base station 1 and base station 2 for RC3 or RC5. Repeat steps e through j.

i. j.

k. l.

253.12.5 Minimum Standard

26The mobile station shall comply with steps h, j, and l. 27

39

1
NUM_PREAMBLE RC1, RC2 Preamble Length in 20 ms Increments: (Total Time) 0 4
1

3GPP2 C.S0044-A v1.0 RC>2 Preamble Length in 1.25 ms Increments: (Total Time) 0 (0 ms) 8 (10 ms)

0 (0 ms) 4 (80 ms)

23.13 Hopping Pilot Beacon 33.13.1 Definition

4The mobile station is transitioned between base stations with different CDMA frequency (channel) 5assignments in the same band. 6The Hopping Pilot Beacon is a pilot beacon that changes CDMA Frequency periodically to 7simulate multiple base stations operating on different frequencies. The transmission of the 8hopping pilot beacon is discontinuous on any CDMA Channel.

93.13.2 Traceability
10(See[4])

112.6.6.1.1 122.6.6.2.5 132.6.6.2.8 142.7.4.25 153.6.1.2 163.6.6.1.1 173.6.6.2.2 183.7.2.3.2.22 193.7.2.3.2.26 20(See[1]) 213.1.3.2.5

Types of Handoff Handoff Messages CDMA-to-CDMA Hard Handoff Capability Information Pilot Channel Operation Types of Handoff Call Processing During Handoff General Neighbor List Message Sync Channel Message

Hopping Pilot Beacon

223.13.3 Call Flow Example(s)

23None

243.13.4 Method of Measurement 25 26

a. b. Configure base station 1 and 2 for hopping pilot beacon. Setup test as shown in A-2.

40

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8

9

1. The Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1. 2. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P2 and is called Channel 2. 3. The AWGN source should be on the frequency of Channel 2. (It is advisable to achieve the maximum possible difference in frequency separation between Channel 1 and Channel 2) c. Set the test parameters as shown in Table 3.13.4-23.

10
Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io
11

Table 3.13.4-23 Unit dBm dB dB dBm/1.23 MHz dB Channel 1 N/A -7 -7 N/A -7 Channel 2 -5 -7 -7 -75 -13.2

12 13 14 15 16 17 18 19 20 21 22 23 24 25

d. e. f. g.

Set reverse link attenuation to balance forward and reverse links (approx. 90 dB). Setup a mobile station originated call on Channel 1. Verify user data in both directions. Verify hopping pilot beacon settings in the General Neighbor List Message or Extended Neighbor List Message. Initiate handoff from Channel 1 to Channel 2. Verify that the base station 1 sends a General Handoff Direction Message, Universal Handoff Direction Message, or an Extended Handoff Direction Message with proper parameters (refer tables in Annex B). Verify the handoff is successful Verify hopping pilot beacon settings in the General Neighbor List Message or Extended Neighbor List Message. Wait 20 seconds then initiate handoff from Channel 2 to Channel 1. Verify that the base station 2 sends a General Handoff Direction Message, Universal Handoff Direction Message, or an Extended Handoff Direction Message with the proper parameters (refer to tables in Annex B).

h. i.

263.13.5 Minimum Standard

27The mobile station shall comply with steps h and i

41

3GPP2 C.S0044-A v1.0

13.14 Hard Handoff between Frequencies with Different Radio Configurations 23.14.1 Definition
3The mobile station is transitioned between base stations with different CDMA frequency (channel) 4assignments in the same band and different radio configurations.

53.14.2 Traceability
6(See[4])

72.6.6.1.1 82.6.6.2.5 92.6.6.2.8 103.6.6.1.1 113.6.6.2.2 12(See[1]) 132.1.3.1 143.1.3.1

Types of Handoff Handoff Messages DMA-to-CDMA Hard Handoff Types of Handoff Call Processing During Handoff

Reverse CDMA Channel Signals Forward CDMA Channel Signals

153.14.3 Call Flow Example(s)

16None

173.14.4 Method of Measurement 18 19 20 21 22 23 24 25 26 27

28

a. b.

Configure base station 1 for RC3 or RC5. Configure base station 2 for RC1 or RC2. Setup test as shown in A-5. 1. The Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1. 2. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P2 and is called Channel 2. 3. The AWGN source should be on the frequency of Channel 2. (It is advisable to achieve the maximum possible difference in frequency separation between Channel 1 and Channel 2)

c.

Set the test parameters as shown in Table 3.14.4-24.

29
Parameter or/Ioc Pilot Ec/Ior Unit dBm dB

Table 3.14.4-24 Channel 1 N/A -7 Channel 2 -5 -7

42

13GPP2 C.S0044-A v1.0

Traffic Ec/Ior Ioc Pilot Ec/Io
1

dB dBm/1.23 MHz dB

-7 N/A -7

-7 -75 -13.2

2 3 4 5 6 7 8 9 10 11 12 13 14

d. e. f. g.

Set reverse link attenuation to balance forward and reverse links (approx. 90 dB). Setup a mobile station originated call on Channel 1. Verify user data in both directions. Initiate handoff from Channel 1 to Channel 2. Verify that the base station 1 sends a General Handoff Direction Message, or Universal Handoff Direction Message with proper parameters (refer to tables in Annex B) Wait 20 seconds then initiate handoff from Channel 2 to Channel 1. Verify that the base station 2 sends a General Handoff Direction Message, or Universal Handoff Direction Message with the proper parameters (refer to tables in Annex B). Configure base station 1 for RC1 or RC2. Configure base station 2 for RC3 or RC5 and repeat steps b through h. Configure base station 1 for RC3. Configure base station 2 for RC4 and repeat steps b through h.

h.

i. j.

153.14.5 Minimum Standard

16The mobile station shall comply with steps g, h, i and j.

173.15 Handoff on Same Frequency with Different Radio Configurations 183.15.1 Definition
19The mobile station is transitioned between base stations with the same CDMA frequency 20(channel) assignments in the same band and different radio configurations. 21When the active set membership before and after the handoff are disjoint, the handoff is 22performed as a hard handoff; when the active set membership before and after handoff are not 23disjoint, except for the value of the radio configuration, the handoff is performed as a soft handoff.

243.15.2 Traceability
25(See[4])

262.6.6.1.1 272.6.6.2.5 282.6.6.2.8 293.6.6.1.1 303.6.6.2.2

Types of Handoff Handoff Messages CDMA-to-CDMA Hard Handoff Types of Handoff Call Processing During Handoff

43

1 1(See[1]) 22.1.3.1 33.1.3.1

Reverse CDMA Channel Signals Forward CDMA Channel Signals

3GPP2 C.S0044-A v1.0

43.15.3 Call Flow Example(s)

5None

63.15.4 Method of Measurement 7 8 9 10 11 12 13 14

15

a. b.

Configure base station 1 for RC4 or RC5. Configure base station 2 for RC1 or RC2. Setup test as shown in Figure A-2 1. The Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1. 2. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P2 and is called Channel 2. 3. The AWGN source should be added to both Channels.

c.

Set the test parameters as shown in Table 3.15.4-25.

16
Parameter or/Ioc Pilot Ec/Ior

Table 3.15.4-25 Hard Handoff Test Parameters Unit dBm dB dB dBm/1.23 MHz dB Channel 1 N/A -7 -7 N/A -7 Channel 2 -5 -7 -7 -75 -13.2

Traffic Ec/Ior Ioc Pilot Ec/Io

17

18 19 20 21 22 23 24 25 26 2

d. e. f. g.

Set reverse link attenuation to balance forward and reverse links (approx. 90 dB). Setup a mobile station originated call on Channel 1. Verify user data in both directions. Initiate handoff from Channel 1 to Channel 2. Verify that the base station 1 sends a General Handoff Direction Message, or Universal Handoff Direction Message with proper parameters (refer to tables in Annex B) Wait 20 seconds then initiate handoff from Channel 2 to Channel 1. Verify that the base station 2 sends a General Handoff Direction Message, or Universal Handoff Direction Message with the proper parameters (refer to tables in Annex B).

h.

44

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9

i. j. k. Configure base station 1 for RC1 or RC2. Configure base station 2 for RC4 or RC5 and repeat steps b through h. Configure base station 1 for RC3. Configure base station 2 for RC4 and repeat steps b through h. Repeat steps a through j but with the following exception: Only base station 1 is used for this test. The handoff messages are sent from base station 1 without changing the active set, but changing the radio configuration. Thus the handoff messages simply assign a new radio configuration from the same base station. Verify that the handoff is performed as a soft handoff.

l.

103.15.5 Minimum Standard

11The mobile station shall comply with steps g, h, i, j, and k.

123.16 Hard Handoff while in the Waiting for Mobile Station Answer Substate 133.16.1 Definition
14This test verifies that if a hard handoff occurs while the mobile station is in the Waiting for Mobile 15Station Answer Substate, the hard handoff will be completed successfully and the mobile station 16shall enter the Conversation Substate on the new channel.

173.16.2 Traceability
18(see [4])

192.6.4 202.6.4.3.2 212.6.4.4 222.6.6.2.5.1 232.6.6.2.8 243.6.4.3.1 253.6.6.2.2 263.7.3.3.2.17 273.7.3.3.2.31 283.7.3.3.2.36 29Table D-1
30(see [17])

Mobile Station Control on the Traffic Channel State Waiting for Mobile Station Answer Substate Conversation Substate Processing of the Forward Traffic Channel Handoff Messages CDMA to CDMA Hard Handoff Waiting for Order Substate Call Processing during Handoff Extended Handoff Direction Message General Handoff Direction Message Universal Handoff Direction Message Time Constants

313.1 323.2

Standard Service Option Number Assignments Proprietary Service Option Number Assignments

45

1 13.16.3 Call Flow Example(s)

2None

3GPP2 C.S0044-A v1.0

33.16.4 Method of Measurement 4 5 6 7 8 9 10 11 12 13

14

a.

Connect the mobile station to the base station as shown in Figure A-5 and set the test parameters as specified in Table 3.2.4-14. 1. Base station 1 is a CDMA base station with frequency F1, PN offset P1 and is referred to as Channel 1. 2. Base station 2 is a CDMA base station with frequency F2, PN offset P2 and is referred to as Channel 2.

b. c. d.

Ensure the mobile station is operating in the Idle State on Channel 1. Page the mobile station with a supported service option. After receiving the Page Response Message, instruct the base station to send an Extended Channel Assignment Message with the following parameters:

Field ASSIGN_MODE BYPASS_ALERT_ANSWER

15

Value '000' or '100' '0'

16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 2

e.

While the mobile station is in the Waiting for Mobile Station Answer Substate (i.e. ringing), instruct the base station to send an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message directing the mobile station to Channel 2. If the base station sends a second (Extended) Alert with Information Message from base station 2, verify the mobile station resets T53m (65 seconds) and the information record(s) included override the first (Extended) Alert with Information Message. The mobile station should not prompt the user to answer the call twice or indicate a missed call. After the hard handoff has been completed and before T53m (65 seconds), has expired direct the user to answer the call. Verify the mobile station enters the Conversation Substate and user traffic is present in both directions (i.e. audio). End the call. Repeat steps b through j using different service options and radio configurations supported by the mobile station and base station. Repeat steps b through j, changing Channel 2 to a band class that is different from Channel 1 but is supported by the mobile station.

f.

g. h. i. j. k.

46

13GPP2 C.S0044-A v1.0 13.16.5 Minimum Standard

2The mobile station shall comply with steps h and j.

33.17 Mobile Assisted Inter-Frequency Hard Handoff (CDMA to CDMA) 43.17.1 Definition
5In an Inter-Frequency Hard Handoff test (also known as the Mobile Assisted Hard Handoff test), 6when the mobile station is directed by the base station to perform a search on a Candidate 7Frequency, the mobile station will search for a pilot in the Candidate Frequency Neighbor Set. 8The mobile station will report back to the base station any pilot detected in the Candidate 9Frequency Neighbor Set with a pilot Ec/Io above the value defined by CF_T_ADD. The base 10station should then direct the mobile station to the Candidate Frequency and completes the hard 11handoff.

123.17.2 Traceability
13(see [4])

142.6.6.2.5 152.6.6.2.8 162.7.2.3.2.20 173.6.6.2.2

Handoff Messages CDMA-to-CDMA Hard Handoff Candidate Frequency Search Report Message Call Processing During Handoff

183.7.7.3.3.2.27 Candidate Frequency Search Request Message 193.17.3 Call Flow Example(s)
20None

213.17.4 Method of Measurement 22 23 24 25 26 27

28

a.

Setup test as shown in Figure A-5. 1. The Forward Channel from base station 1 has a CDMA frequency assignment F1 (any valid value), an arbitrary pilot PN offset index P1 and is called Channel 1. 2. The Forward Channel from base station 2 has a CDMA frequency assignment F2 (any valid value other than f1 in the same band class), an arbitrary pilot PN offset index P2 and is called Channel 2.

Parameter or/Ioc Pilot E c I or

Unit dB dB

Channel 1 2.9 -7

Channel 2 2.9 -7

47

1
Traffic E c I or Ioc Pilot E c I0
1

3GPP2 C.S0044-A v1.0 dB -7 N/A

dBm/1.23 MHz dB

-75 -11.0 -11.0

2 3 4 5
6

b. c. d.

Reverse Link attenuation should be set to balance the forward and reverse links. Set up a mobile station originated call on Channel 1. Send from base station 1 a Candidate Frequency Search Request Message to the mobile station to set an explicit action time with the following parameters:

Field USE_TIME SEARCH_TYPE SEARCH_MODE CDMA_FREQ SF_TOTAL_EC_THRESH SF_TOTAL_EC_IO_THRESH CF_SRCH_WIN_N CF_T_ADD NUM_PILOTS CF_NGHBR_SRCH_MODE NGHBR_PN
7

Value (Decimal) 1 (use action time) 1 (single search) 0 (CDMA) F2 31 (disabled) 31 (disabled) 8 (60 chips) 28 (-14 dB) 1 (1 pilot) 0 (no search priorities or search windows specified) P2

8 9 10 11 12

e. f.

Verify that the mobile station responds with a Candidate Frequency Search Report Message. Verify that base station 1 sends a General Handoff Direction Message, an Extended Handoff Direction Message or a Universal Handoff Direction Message to initiate handoff from base station 1 to base station 2.

48

13GPP2 C.S0044-A v1.0 1

g. Verify user data in both directions.

23.17.5 Minimum Standard

3The mobile station shall comply with steps e and g.

43.18 Mobile Assisted Inter-Frequency Hard Handoff (CDMA to Analog) 53.18.1 Definition
6In an Inter-Frequency Hard Handoff test (also known as the Mobile Assisted Hard Handoff test), 7when the mobile station is directed by the base station to perform a search on a Candidate 8Frequency, the mobile station will search for an analog channel in the Candidate Frequency 9Analog Search Set and shall measure the mean input power on the analog frequency. The mobile 10station will report back to the base station the signal strength of the analog channel searched. 11The base station should then direct the mobile station to the Analog Channel and completes the 12hard handoff.

133.18.2 Traceability
14(see [4])

152.6.6.2.5 162.6.6.2.8 172.6.6.10.2 182.7.2.3.2.21 193.6.6.2.2

Handoff Messages CDMA-to-CDMA Hard Handoff Candidate Frequency Analog Search Set Candidate Frequency Search Report Message Call Processing During Handoff

203.7.7.3.3.2.27 Candidate Frequency Search Request Message 213.18.3 Call Flow Example(s)
22None

233.18.4 Method of Measurement 24 25 26 27 28 29

30

a.

Setup test as shown in Figure A-5. 1. The Forward Channel from base station 1 has a CDMA frequency assignment F1 (any valid value), an arbitrary pilot PN offset index P1 and is called Channel 1. 2. The Forward Channel from base station 2 uses an analog frequency called Channel 2.

b.

Set the test parameters as specified in Table 3.15.4-25 and Table 3.18.4-2

31

Table 3.18.4-26 Test Parameters for Inter-Frequency Hard Handoff (Channel 1) CDMA Parameter or/Ioc Unit dB Channel 1 0

49

1
Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io
1 2

3GPP2 C.S0044-A v1.0 dB dB dBm/1.23 MHz dB -7 -7 -75 -10

Table 3.18.4-2 Test Parameter for Inter-Frequency Handoff (Channel 2) Analog Parameter Voice Channel Co-Channel Interference Unit dBm dB Channel 2 -73 -18

4 5 6 7
8

c. d. e.

Reverse Link attenuation should be set to balance the forward and reverse links. Set up a mobile station originated voice call on Channel 1. Send from base station 1 a Candidate Frequency Search Request Message to the mobile station to set an explicit action time with the following parameters:

Field USE_TIME SEARCH_TYPE SEARCH_MODE SF_TOTAL_EC_THRESH SF_TOTAL_EC_IO_THRESH NUM_ANALOG_FREQS ANALOG_FREQ

9

Value (Decimal) 1 (use action time) 1 (single search) 1 (search for analog channels) 31 (disabled) 31 (disabled) 1 Channel 2

10 11 12 13 14

f. g. h.

Verify that the mobile station responds with a Candidate Frequency Search Report Message. Verify that base station 1 sends an Analog Handoff Direction Message to initiate handoff from base station 1 to base station 2. Verify audio in both directions.

50

13GPP2 C.S0044-A v1.0 13.18.5 Minimum Standard

2The mobile stations shall comply with steps f and h.

33.19 Hard Handoff between Frequencies with Different Protocol Revisions 43.19.1 Definition
5This test verifies the mobile station is able perform a hard handoff between base stations 6supporting using different protocol revisions (P_REV).

73.19.2 Traceability
8(See[4])

92.6.6.1.1 102.6.6.2.5 112.6.6.2.8 123.6.6.1.1 133.6.6.2.2 143.7.3.3.2.17 153.7.3.3.2.31 163.7.3.3.2.36

Types of Handoff Handoff Messages CDMA-to-CDMA Hard Handoff Types of Handoff Call Processing During Handoff Extended Handoff Direction Message General Handoff Direction Message Universal Handoff Direction Message

173.19.3 Call Flow Example(s)

18None

193.19.4 Method of Measurement 20 21 22 23 24 25 26 27 28 29 30

31

a. b. c.

Configure base station one and base station two with different protocol revisions. Verify the mobile station supports the protocol revisions on each base station. Setup test as shown in Figure A-5. 1. The Forward Channel from base station one has an arbitrary pilot PN offset index P1 and is called Channel 1. 2. The Forward Channel from base station two has an arbitrary pilot PN offset index P2 and is called Channel 2. 3. The AWGN source should be on the frequency of Channel 2. (It is advisable to achieve the maximum possible difference in frequency separation between Channel 1 and Channel 2)

d.

Set the test parameters as shown in Table 3.19.4-27.

51

1 1
Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io
2

3GPP2 C.S0044-A v1.0 Table 3.19.4-27 Hard Handoff Test Parameters Unit dBm dB dB dBm/1.23 MHz dB Channel 1 N/A -7 -7 N/A -7 Channel 2 -5 -7 -7 -75 -13.2

3 4 5 6 7 8 9 10

e. f. g. h. i.

Set reverse link attenuation to balance forward and reverse links (approx. 90 dB). Setup a mobile station originated call on Channel 1. Verify user traffic in both directions. Initiate handoff from Channel 1 to Channel 2. Verify that the base station 1 sends General Handoff Direction Message, Universal Handoff Direction Message, or Extended Handoff Direction Message with the P_REV field value equal to the P_REV of base station two. Verify the handoff is successful and user traffic is present in both directions.

j.

113.19.5 Minimum Standard

12The mobile station shall comply with step j. 13

52

13GPP2 C.S0044-A v1.0

1No text.

53

13GPP2 C.S0044-A v1.0 14 24.1 34.1.1

POWER CONTROL
Forward Traffic Channel Power Control Definition

4This test verifies that the mobile station reports frame error rate statistics at specified intervals if 5the base station enables periodic reporting, and verifies that the mobile station reports frame error 6rate statistics when the frame error rate reaches a specified threshold if the base station enables 7threshold reporting.

84.1.2
9(See[4])

Traceability:

102.6.4.1.1 112.7.2.3.2.6 123.6.4.1.1 133.7.3.3.2.10

Forward Traffic Channel Power Control Power Measurement Report Message Forward Traffic Channel Power Control Power Control Parameters Message

14Applicability: Forward Link: RC 1 through RC 5; Reverse Link: RC 1 through RC 4

154.1.3
16None

Call Flow Example(s)

174.1.4 18 19 20 21 22 23 24 25
26

Method of Measurement Setup test as shown in Annex A Figure A-6. Setup a mobile station originated call using the test parameters for Test 1 as specified in Table 4.1.4-28. Set the AWGN source power so the forward link average FER is between 0.5 and 1.0%. Instruct the base station to send the Power Control Parameters Message to enable the threshold reporting and disable the periodic reporting according to the base station manufacturer's forward power control algorithm.

a. b. c. d.

PWR_THRESH_ENABLE PWR_PERIOD_ENABLE
27

1 (Enable threshold reporting) 0 (Disable periodic reporting)

28 29 30 31 2

e. f.

Using Attenuator 1, alternately increase and decrease AWGN source output power by 5 dB from the original power set in step c. Monitor forward traffic channel Ec/Ior and ensure power increases and decreases corresponding to noise power from the AWGN source.

1 1
g. Monitor forward link FER at the mobile station.

3GPP2 C.S0044-A v1.0

13GPP2 C.S0044-A v1.0

1

2
Test Number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

Table 4.1.4-28 Test Parameters for Forward Power Control Tests Forward RC 1 1 2 2 3 3 3 3 4 4 4 4 5 5 5 5 3 4 5 3 4 Reverse RC 1 1 2 2 3 3 3 3 3 3 3 3 4 4 4 4 3 3 4 3 3 Threshold/Pe riodic Service Option Channels Forward Link Power [dBm/ 1.23 MHz] -65 -65 -62 -62 -65 -65 -65 -65 -65 -65 -65 -65 -62 -62 -62 -62 -65 -65 -62 -65 -65

Threshold Periodic Threshold Periodic Threshold Periodic Threshold Periodic Threshold Periodic Threshold Periodic Threshold Periodic Threshold Periodic N/A N/A N/A N/A N/A

2, 54, 55, or 32798 2, 54, 55, or 32798 9, 54, 55, or 32799 9, 54, 55, or 32799 54, or 55 54, or 55 54, or 55 54, or 55 54, or 55 54, or 55 54, or 55 54, or 55 54, or 55 54, or 55 54, or 55 54, or 55 54, or 55 54, or 55 54, or 55 54, or 55 54, or 55

F-FCH F-FCH F-FCH F-FCH F-FCH F-FCH F-DCCH F-DCCH F-FCH F-FCH F-DCCH F-DCCH F-FCH F-FCH F-DCCH F-DCCH F-FCH/F-SCH F-FCH/F-SCH F-FCH/F-SCH F-DCCH/FSCH F-DCCH/F-

3GPP2 C.S0044-A v1.0 SCH

22

N/A

54, or 55

F-DCCH/FSCH

-62

1Note: All tests should be performed at full data rate or at a variable rate. Tests involving the 2Forward Supplemental Channels should only include 1 Forward Supplemental Channel. 3

4 5 6 7 8 9 10 11
12

h. i. j. k.

Verify MS sends the Power Measurement Report Message when the bad frames received by the mobile station reaches the specified threshold. End the call. Setup a mobile station originated call using the test parameters for Test 2 as specified in Table 4.1.4-28. Instruct the base station to send the Power Control Parameters Message to enable the periodic reporting and disable the threshold reporting according to the base station manufacturer's forward power control algorithm.

PWR_THRESH_ENABLE PWR_PERIOD_ENABLE
13

0 (Disable threshold reporting) 1 (Enable periodic reporting)

14 15 16 17 18 19 20 21 22 23 24 25 26 27 28

l. m. n. o. p. q.

Repeat the steps e through g. Verify the mobile station sends the Power Measurement Report Message when the total frames received by the mobile station reach the specified report period. End the call. Repeat steps b through n except for using the test parameters for Tests 3 to 16 as specified in Table 4.1.4-28. Repeat steps b through c except for using the test parameters for Test 17 to Test 22 as specified in Table 4.1.4-28. Instruct the base station to send the Extended Supplemental Channel Assignment Message including a Forward Supplemental Channel assignment and setting FOR_SCH_FER_REP to 1. Repeat the steps e through g. Verify the mobile station sends the Power Measurement Report Message at the end of the burst. End the call. Minimum Standard

r. s. t.

294.1.5

30The mobile station shall comply with steps h, l, m, o, p, r and s.

13GPP2 C.S0044-A v1.0

1The base station should alternately increase and decrease the forward traffic channel power 2according to the base station manufacturer's forward power control algorithm. Forward link FER 3measured at the mobile station should be within the target value and the mobile station shall 4report frame error rate statistics. There shall not be any dropped calls.

54.2 64.2.1

Fast Forward Power Control (FFPC) FFPC using different values of FPC_MODE (FPC_MODE = 000, 001, 010) Definition

74.2.1.1

8The mobile station accomplishes fast forward power control by transmitting the Reverse Power 9Control Subchannel to the base station on the Reverse Pilot Channel. The mobile station 10determines the information to be sent to the base station through inner and outer loop 11estimations. In outer loop estimation, the mobile station adjusts the Eb/Nt setpoint to the Eb/Nt 12value necessary to achieve the target FER on the Forward Traffic Channel. In inner loop 13estimation, the mobile station compares the received Eb/Nt to the setpoint and determines the 14value of the power control bit to be sent to the base station. There are 16 Power Control Groups 15every 20 ms on the Reverse Power Control Subchannel. This test verifies that the mobile station 16can process the various parameters in the Extended Channel Assignment Message, the 17Extended Supplemental Channel Assignment Message, and the Service Connect Message.

184.2.1.2
19(See[1])

Traceability:

202.1.3.1.11 21(See[4]) 222.6.6.2.5.1 233.6.6.2.2.12 243.7.3.3.2.37 25 2.6.2.4 262.6.3.3 272.6.3.5 283.6.3.3 293.6.3.5 303.7.2.3.2.21 312.6.4.1.2 322.6.4.1.2.2 333.7.3.3.2.20 343.7.5 353.7.5.7 363.7.5.20

Reverse Power Control Subchannel

Processing of Forward Traffic Channel Handoff Messages Processing of Extended Supplemental Channel Assignment Message Extended Supplemental Channel Assignment Message Mobile Station Order and Message Processing Operation Page Response Substate Mobile Station Origination Attempt Substate Response to Page Response Message Response to Origination Message Extended Channel Assignment Message Service Configuration and Negotiation Service Subfunctions Service Connect Message Information Records Service Configuration Non negotiable System Configuration

1
1

3GPP2 C.S0044-A v1.0

2Applicability: Forward Link: RC 1 through RC 5; Reverse Link: RC 1 through RC 4 3FPC_MODE Information 4

Table 4.2.1-29 Reverse Power Control Subchannel Configurations Reverse Power Control Subchannel Allocations (Power Control Group Numbers)

FPC_MODE 000 001 010

6

Primary Reverse Power Control Subchannel 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 0,2,4,6,8,10,12,14 1,5,9,13

Secondary Reverse Power Control Subchannel Not supported 1,3,5,7,9,11,13,15 0,2,3,4,6,7,8,10,11,12,14,15

74.2.1.3
8None

Call Flow Example(s)

94.2.1.4

Method of Measurement

104.2.1.4.1 FPC_MODE 000; F-FCH Only 11 12 13

a. b. Connect base station and mobile station as shown in Annex A Figure A-6. Set power levels as stated in Table 4.2.1-30: Table 4.2.1-30 Test Parameters for Fast Forward Power Control Parameter Unit Value

Pilot E c I or Ioc Ior/Ioc

dB

-7

dBm/1.23 MHz dB

-75 10

14

15 16

c.

Setup a mobile station originated call using Service Option 55 (Loopback Service Option) or Service Option 54 (Markov Service Option).

13GPP2 C.S0044-A v1.0 1 2

3

d.

Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:

ASSIGN_MODE = '100' FOR_RC = '00011' (RC 3) CH_IND = '01' FPC_FCH_FER = '00010' (1%) FPC_FCH_MAX_SETPT = '10000000' (16 dB)
4

GRANTED_MODE = '10' REV_RC = '00011' (RC 3) FPC_FCH_INIT_SETPT = '01000000' (8 dB) FPC_FCH_MIN_SETPT = '00010000' (2 dB)

5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

e. f. g.

Ensure the base station sends the Service Connect Message with FPC_INCL set to 0. Monitor the forward link FER at the mobile station. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source. Monitor traffic channel Ec/Ior and ensure the power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.

h.

i. j. k. l.

Verify that the forward link FER on the FCH remains at approximately the target value (i.e. 1%). End the call at the mobile station. Repeat steps a through j above except that FOR_RC is set to RC4 and REV_RC is set to RC3 in step d. Repeat steps a through j above except that FOR_RC is set to RC5 and REV_RC is set to RC4 in step d.

204.2.1.4.2 FPC_MODE 000; F-DCCH only 21 22 23

a. b. Connect base station and mobile station as shown in Annex A Figure A-6. Set power levels as stated in Table 4.2.1-3: Table 4.2.1-3 Test Parameters for Fast Forward Power Control Parameter Unit Value

3GPP2 C.S0044-A v1.0

Pilot E c I or Ioc Ior/Ioc

dB

-7

dBm/1.23 MHz dB

-75 10

2 3 4 5
6

c. d.

Setup a mobile station originated call using Service Option 32 (Test Data Service Option). Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:

ASSIGN_MODE = 100 FOR_RC = 00011 (RC 3) CH_IND = 10 FPC_DCCH_FER = 00010 (1%) FPC_DCCH_MAX_SETPT = 10000000 (16 dB)
7

GRANTED_MODE = 10 REV_RC = 00011 (RC 3) FPC_DCCH_INIT_SETPT = 01000000 (8 dB) FPC_DCCH_MIN_SETPT = 00010000 (2 dB)

8 9 10 11 12 13 14 15 16 17 18 19 20

e. f. g.

Ensure the base station sends the Service Connect Message with FPC_INCL set to 0. Monitor the forward link FER at the mobile station. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.

h.

i. j. k.

Verify that the forward link FER on DCCH remains at approximately the target value (1%). End the call at the mobile station. Repeat steps a through i above except for setting FOR_RC to RC4 and REV_RC to RC3 in step d.

13GPP2 C.S0044-A v1.0 1 2

l. Repeat steps a through i above except for setting FOR_RC to RC5 and REV_RC to RC4 in step d.

34.2.1.4.3 FPC_MODE 001; F-FCH and F-SCH 4 5 7

a. b. Connect base station and mobile station as shown in Annex A Figure A-6. Set power levels as stated in Table 4.2.1-4: Table 4.2.1-4 Test Parameters for Fast Forward Power Control Parameter Unit Value

Pilot E c I or Ioc Ior/Ioc

8

dB

-7

dBm/1.23 MHz dB

-75 10

9 10 11 12
13

c. d.

Setup a mobile station originated call using Service Option 32 (Test Data Service Option). Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:

ASSIGN_MODE = 100 FOR_RC = 00011 (RC 3) CH_IND = 01 FPC_FCH_FER = 00010 (1%) FPC_FCH_MAX_SETPT = 10000000 (16 dB)
14

GRANTED_MODE = 10 REV_RC = 00011 (RC 3) FPC_FCH_INIT_SETPT = 01000000 (8 dB) FPC_FCH_MIN_SETPT = 00010000 (2 dB)

15 16
17

e.

Instruct the base station to send the Service Connect Message with the parameters set as follows:

FPC_INCL = 1 FPC_PRI_CHAN = 0

FPC_OLPC_FCH_INCL = 0 GATING_RATE_INCL = 0

3GPP2 C.S0044-A v1.0

FPC_MODE = 001
1

2 3 4
5

f.

Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel by using the Extended Supplemental Channel Assignment Message and set the power control related fields as stated in follows:

FPC_INCL = 1 FPC_MODE_SCH = 001 FPC_SCH_INIT_SETPT_OP = 0 FPC_SCH_FER = 01010 (5%)

6

FPC_SCH_INIT_SETPT = 01000000 (8 dB) FPC_SCH_MAX_SETPT = 10000000 (16 dB) FPC_SCH_MIN_SETPT = 00010000 (2 dB)

7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

g. h.

Monitor the forward link FER on FCH and SCH (during the burst assignment) at the mobile station. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.

i.

j. k. l. m.

Verify that the forward link FER on FCH and SCH (during SCH assignment) remain at approximately the target values. End the call at the mobile station. Repeat steps a through k above except that FOR_RC is set to RC4 and REV_RC is set to RC3 in step d. Repeat steps h through k above except that FOR_RC is set to RC5 and REV_RC is set to RC4 in step d.

224.2.1.4.4 FPC_MODE 000 without F-SCH Active and FPC_MODE 001 with F-SCH Active; F23 DCCH and F-SCH 24 25
a. b. Connect base station and mobile station as shown in Annex A Figure A-6. Set power levels as stated in Table 4.2.1-5:

10

13GPP2 C.S0044-A v1.0 1

Table 4.2.1-5 Test Parameters for Fast Forward Power Control Parameter Unit Value

Pilot E c I or Ioc Ior/Ioc

2

dB

-7

dBm/1.23 MHz dB

-75 10

3 4 5 6
7

c. d.

Setup a mobile station originated call using Service Option 32 (Test Data Service Option). Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:

ASSIGN_MODE = 100 FOR_RC = 00011 (RC 3) CH_IND = 10 FPC_DCCH_FER = 00010 (1%) FPC_DCCH_MAX_SETPT = 10000000 (16 dB)
8

GRANTED_MODE = 10 REV_RC = 00011 (RC 3) FPC_DCCH_INIT_SETPT = 01000000 (8 dB) FPC_DCCH_MIN_SETPT = 00010000 (2 dB)

9 10 11 12 13
14

e. f.

Instruct the base station to send the Service Connect Message with FPC_INCL set to 0. Instruct the base station to download the SCH configuration and assign a Forward Supplemental Channel using the Extended Supplemental Channel Assignment Message and set the power control related information as follows:

FPC_INCL = 1 FPC_MODE_SCH = 001 FPC_SCH_INIT_SETPT_OP = 0

FPC_SCH_INIT_SETPT = 01000000 (8 dB) FPC_SCH_MAX_SETPT = 10000000 (16 dB) FPC_SCH_MIN_SETPT = 00010000 (2 dB)

11

1
FPC_SCH_FER = 01010 (5%)
1

3GPP2 C.S0044-A v1.0

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

g. h.

Monitor the forward link FER on both F-DCCH and F-SCH (during SCH assignment) at the mobile station. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.

i.

j. k. l. m.

Verify that the forward link FER on DCCH and SCH (during SCH assignment) remains at approximately the target value. End the call at the mobile station. Repeat steps a through k above except that FOR_RC is set to RC4 and REV_RC is set to RC3 in step d. Repeat steps a through k above except that the FOR_RC is set to RC5 and REV_RC is set to RC4 in step d.

174.2.1.4.5 FPC_MODE 000 without F-SCH Active and FPC_MODE 010 with F-SCH Active; F18 FCH and F-SCH 19 20 21
a. b. Connect base station and mobile station as shown in Annex A Figure A-6. Set power levels as stated in Table 4.2.1-6: Table 4.2.1-6 Test Parameters for Fast Forward Power Control Parameter Unit Value

Pilot E c I or Ioc Ior/Ioc

22

dB dBm/1.23 MHz dB

-7

-75 10

23 24 25 26
27

c. d.

Setup a mobile station originated call using Service Option 32 (Test Data Service Option). Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:

12

13GPP2 C.S0044-A v1.0

ASSIGN_MODE = 100 FOR_RC = 00011 (RC 3) CH_IND = 01 FPC_FCH_FER = 00010 (1%) FPC_FCH_MAX_SETPT = 10000000 (16 dB)
1

GRANTED_MODE = 10 REV_RC = 00011 (RC 3) FPC_FCH_INIT_SETPT = 01000000 (8 dB) FPC_FCH_MIN_SETPT = 00010000 (2 dB)

2 3 4 5 6
7

e. f.

Instruct the base station to send the Service Connect Message with FPC_INCL set to 0. Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel by using the Extended Supplemental Channel Assignment Message with power control related parameters set as follows:

FPC_INCL = 1 FPC_MODE_SCH = 010 FPC_SCH_INIT_SETPT_OP = 0 FPC_SCH_FER = 01010 (5%)

FPC_SCH_INIT_SETPT = 01000000 (8 dB) FPC_SCH_MAX_SETPT = 10000000 (16 dB) FPC_SCH_MIN_SETPT = 00010000 (2 dB)

8 9 10 11 12 13 14 15 16 17 18 19 20

g. h.

Monitor the forward link FER on both FCH and SCH (during the SCH assignment) at the mobile station. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.

i.

j. k. l.

Verify that the forward link FER on FCH and SCH (during SCH assignment) remain at approximately the target values. End the call at the mobile station. Repeat steps a through k above except for step d to set FOR_RC to RC4 and REV_RC to RC3.

13

1 1 2
m.

3GPP2 C.S0044-A v1.0 Repeat steps a through k above except for step d to set FOR_RC to RC5 and REV_RC to RC4.

34.2.1.4.6 FPC_MODE 010; F-DCCH and F-SCH 4 5 6

a. b. Connect base station and mobile station as shown in Annex A Figure A-6. Set power levels as stated in Table 4.2.1-7: Table 4.2.1-7 Test Parameters for Fast Forward Power Control Parameter Unit Value

Pilot E c I or Ioc Ior/Ioc

7

dB

-7

dBm/1.23 MHz dB

-75 10

8 9 10 11
12

c. d.

Setup a mobile station originated call using Service Option 32 (Test Data Service Option). Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows.

ASSIGN_MODE = 100 FOR_RC = 00011 (RC 3) CH_IND = 10 FPC_DCCH_FER = 00010 (1%) FPC_DCCH_MAX_SETPT = 10000000 (16 dB)
13

GRANTED_MODE = 10 REV_RC = 00011 (RC 3) FPC_DCCH_INIT_SETPT = 01000000 (8 dB) FPC_DCCH_MIN_SETPT = 00010000 (2 dB)

14 15
16

e.

Instruct the base station to send the Service Connect Message with the parameters set as follows:

FPC_INCL = 1 FPC_PRI_CHAN = 1

FPC_OLPC_FCH_INCL = 0 GATING_RATE_INCL = 0

14

13GPP2 C.S0044-A v1.0

FPC_MODE = 010
1

2 3 4

f.

Instruct the base station to send SCH configuration and assign a Forward Supplemental Channel by using the Extended Supplemental Channel Assignment Message with power control related parameters set as follows:

FPC_INCL = 1 FPC_MODE_SCH = 010 FPC_SCH_INIT_SETPT_OP = 0 FPC_SCH_FER = 01010 (5%)

6

FPC_SCH_INIT_SETPT = 01000000 (8 dB) FPC_SCH_MAX_SETPT = 10000000 (16 dB) FPC_SCH_MIN_SETPT = 00010000 (2 dB)

7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

g. h.

Monitor forward link FER on both F-DCCH and F-SCH (during SCH burst assignment) at the mobile station. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.

i.

j. k. l. m.

Verify that the forward link FER on the DCCH and SCH (during SCH assignment) remain at approximately the target values. End the call at the mobile station. Repeat steps a through k above except for step d to set FOR_RC to RC4 and REV_RC to 3. Repeat steps a through k above except for step d to set FOR_RC to RC5 and REV_RC to 4. Minimum Standard

224.2.1.5

234.2.1.5.1 FPC_MODE 000; F-FCH Only

24The mobile station shall comply with steps i, k, and l.

254.2.1.5.2 FPC_MODE 000; F-DCCH only

26The mobile station shall comply with steps i, k, and l.

15

1 14.2.1.5.3 FPC_MODE 001; F-FCH and F-SCH

2The mobile station shall comply with steps j, l, and m.

3GPP2 C.S0044-A v1.0

34.2.1.5.4 FPC_MODE 000 without F-SCH Active and FPC_MODE 001 with F-SCH Active; F4 DCCH and F-SCH
5The mobile station shall comply with steps j, l, and m.

64.2.1.5.5 FPC_MODE 000 without F-SCH Active and FPC_MODE 010 with F-SCH Active; F7 FCH and F-SCH
8The mobile station shall comply with steps j, l, and m.

94.2.1.5.6 FPC_MODE 010; F-DCCH and F-SCH

10The mobile station shall comply with steps j, l, and m. 11

124.2.2 134.2.2.1

Outer Loop Report Definition

14This test verifies that the mobile station shall send the Outer Loop Report Message if the Outer 15Loop Report Request Order is received.

164.2.2.2
17(See[1])

Traceability:

182.1.3.1.10 19(See[4]) 202.6.6.2.5.1 213.6.6.2.212 223.7.3.3.2.37 232.6.2.4 242.6.3.3 252.6.3.5 263.6.3.3 273.6.3.5 283.7.2.3.2.21 292.6.4.1.2 302.6.4.1.2.2 313.7.3.3.2.20 323.7.5

Reverse Power Control Subchannel

Processing of Forward Traffic Channel Handoff Messages Processing of Extended Supplemental Channel Assignment Message Extended Supplemental Channel Assignment Message Mobile Station Order and Message Processing Operation Page Response Substate Mobile Station Origination Attempt Substate Response to Page Response Message Response to Origination Message Extended Channel Assignment Message Service Configuration and Negotiation Service Subfunctions Service Connect Message Information Records

16

13GPP2 C.S0044-A v1.0 13.7.5.7 23.7.5.20 32.6.4.1.1 42.7.2.3.2.22 53.7.3.3.2.25

6 7Applicability: Forward Link: RC 1 through RC 5; Reverse Link: RC 1 through RC 4

Service Configuration Non negotiable System Configuration Forward Traffic Channel Power Control Outer Loop Report Message Power Control Message

84.2.2.3
9None

Call Flow Example(s)

104.2.2.4 11 12 13
a. b.

Method of Measurement Connect base station and mobile station as shown in Annex A Figure A-6. Set power levels as stated in Table 4.2.2-31: Table 4.2.2-31 Test Parameters for Fast Forward Power Control Parameter Pilot E c I or Ioc Ior/Ioc Unit dB Value -7

dBm/1.23 MHz dB

-75 10

14

15 16 17 18

c. d.

Setup a mobile station originated call using Service Option 32 (Test Data Service Option). Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:

ASSIGN_MODE = 100 FOR_RC = 00011 (RC 3) CH_IND = 01 FPC_FCH_FER = 00010 (1%)

GRANTED_MODE = 10 REV_RC = 00011 (RC 3) FPC_FCH_INIT_SETPT = 01000000 (8 dB) FPC_FCH_MIN_SETPT = 00010000 (2 dB)

17

1
FPC_FCH_MAX_SETPT = 10000000 (16 dB)
1

3GPP2 C.S0044-A v1.0

2 3 4 5 6
7

e. f.

Instruct the base station to send the Service Connect Message with FPC_INCL set to 0. Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel by using the Extended Supplemental Channel Assignment Message with power control related parameters set as follows:

FPC_INCL = 1 FPC_MODE_SCH = 000 FPC_SCH_INIT_SETPT_OP = 0 FPC_SCH_FER = 01010 (5%)

8

FPC_SCH_INIT_SETPT = 01000000 (8 dB) FPC_SCH_MAX_SETPT = 10000000 (16 dB) FPC_SCH_MIN_SETPT = 00010000 (2 dB)

9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27

g. h.

Monitor the forward link FER on both FCH and SCH (during the SCH assignment) at the mobile station. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.

i.

j. k.

During the F-SCH assignment, instruct the base station to send Outer Loop Report Request Order. Verify the mobile station sends the Outer Loop Report Message and this message contains FPC_FCH_CURR_SETPT and FPC_SCH_CURR_SETPT. The FPC current setpoint reported by the mobile station shall be in the range of the minimum setpoint and the maximum setpoint End the call at the mobile station. Repeat steps a through l above except for the following steps: Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:

l. m. n.

18

13GPP2 C.S0044-A v1.0

ASSIGN_MODE = 100 FOR_RC = 00011 (RC 3) CH_IND = 10 FPC_DCCH_FER = 00010 (1%) FPC_DCCH_MAX_SETPT = 10000000 (16 dB)
1

GRANTED_MODE = 10 REV_RC = 00011 (RC 3) FPC_DCCH_INIT_SETPT = 01000000 (8 dB) FPC_DCCH_MIN_SETPT = 00010000 (2 dB)

2 3 4 5 6 7

o. p.

Monitor the forward link FER on both DCCH and SCH (during the SCH assignment at the mobile station. Verify the mobile station sends the Outer Loop Report Message and this message contains FPC_DCCH_CURR_SETPT and FPC_SCH_CURR_SETPT. The FPC current setpoint reported by the mobile station shall be in the range of the minimum setpoint and the maximum setpoint Minimum Standard

84.2.2.5

9The mobile station shall comply with steps k, m, and p.

104.2.3 114.2.3.1

Fast Forward Power Control (FFPC) in Soft Handoff Definition

12The mobile station accomplishes fast forward power control by transmitting the Reverse Power 13Control Subchannel to the base station on the Reverse Pilot Channel. The mobile station 14determines the information to send to the base station through inner and outer closed loop 15estimations. In outer loop estimation, the mobile station adjusts the Eb/Nt setpoints to the Eb/Nt 16value necessary to achieve the target FER on the Forward Traffic Channel. In inner loop 17estimation, the mobile station compares the received Eb/Nt to the setpoint and determines the 18value of the power control bit to be sent to the base station. This test verifies that the mobile 19station can perform FFPC while in soft handoff. This test also verifies that the mobile station can 20process the various parameters in the Extended Channel Assignment Message, the Extended 21Supplemental Channel Assignment Message, the Universal Handoff Direction Message, and the 22Service Connect Message.

234.2.3.2 24(See[1])

Traceability:

252.1.3.1.11 26(See[4]) 272.6.6.2.5.1 283.6.6.2.2.12 293.7.3.3.2.37 2

Reverse Power Control Subchannel

Processing of Forward Traffic Channel Handoff Messages Processing of Extended Supplemental Channel Assignment Message Extended Supplemental Channel Assignment Message

19

1 12.6.2.4 22.6.3.3 32.6.3.5 43.6.3.3 53.6.3.5 63.7.2.3.2.21 72.6.4.1.2 82.6.4.1.2.2 93.7.3.3.2.20 103.7.5 113.7.5.7 123.7.5.20
13

3GPP2 C.S0044-A v1.0 Mobile Station Order and Message Processing Operation Page Response Substate Mobile Station Origination Attempt Substate Response to Page Response Message Response to Origination Message Extended Channel Assignment Message Service Configuration and Negotiation Service Subfunctions Service Connect Message Information Records Service Configuration Non negotiable System Configuration

14Applicability: Forward Link: RC 1 through RC 5; Reverse Link: RC 1 through RC 4

154.2.3.3
16None

Call Flow Example(s)

174.2.3.4

Method of Measurement

184.2.3.4.1 F-FCH in SHO and F-SCH not in SHO; FPC_MODE = 001 19 20 21

Parameter Pilot Ec/Ior Ioc Ior/Ioc Pilot Ec/Io
22

a. b.

Setup the test as shown in Annex A Figure A-7. Set power levels as stated in Table 4.2.3-32. Table 4.2.3-32 Test Parameters for Fast Forward Power Control Unit dB dBm/1.23 MHz dB dB Base station 1 -7 -75 10 -10.2 Base station 2 -7 -75 10 -20.2

23 24 25 26 2

c. d.

Setup a mobile station originated call using Service Option 32 (Test Data Service Option) on base station 1. Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:

20

13GPP2 C.S0044-A v1.0

1

ASSIGN_MODE = 100 FOR_RC = 00011 (RC 3) CH_IND = 01 FPC_FCH_FER = 00010 (1%) FPC_FCH_MAX_SETPT = 10000000 (16 dB)
2

GRANTED_MODE = 10 REV_RC = 00011 (RC 3) FPC_FCH_INIT_SETPT = 01000000 (8 dB) FPC_FCH_MIN_SETPT = 00010000 (2 dB)

3 4
5

e.

Instruct the base station to send the Service Connect Message with the parameters set as follows:

FPC_INCL = 1 FPC_PRI_CHAN = 0 FPC_MODE = 001

6

FPC_OLPC_FCH_INCL = 0 GATING_RATE_INCL = 0

7 8 9
10

f.

Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel by using the Extended Supplemental Channel Assignment Message with the power control related parameters set as follows:

FPC_INCL = 1 FPC_MODE_SCH = 001 FPC_SCH_INIT_SETPT_OP = 0 FPC_SCH_FER = 01010 (5%)

11

FPC_SCH_INIT_SETPT = 01000000 (8 dB) FPC_SCH_MAX_SETPT = 10000000 (16 dB) FPC_SCH_MIN_SETPT = 00010000 (2 dB)

12 13 14 15 16

g.

Raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Instruct the base station to send the Universal Handoff Direction Message during FSCH assignment with the parameters set as follows:

h.

21

1
1

3GPP2 C.S0044-A v1.0

CH_IND = 101 (FCH and Continuous Reverse Pilot) For PILOT_PN = {base station 1} For PILOT_PN = {base station 2}
2

NUM_PILOTS = 010 PILOT_INCL = 1 PILOT_INCL = 0

3 4 5

i. j.

Verify there are no forward supplemental channels transmitting on base station 2. Set the test parameters as specified in Table 4.2.3-2without dropping the call. Table 4.2.3-2 Test Parameters for Fast Forward Power Control Parameter Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io Unit dB dB dBm/1.23 MHz dB Channel 1 -7 -7 -75 -11.8 Channel 2 -7 -7 -75 -11.8

7 8 9 10 11 12 13 14 15 16 17

k. l.

Monitor the forward link FER on both F-FCH and F-SCH (during F-SCH assignment) at the mobile station. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.

m.

n. o.

Verify that the forward link FER on FCH and SCH (during SCH assignment) remain at approximately in the target value. End the call at the mobile station.

184.2.3.4.2 F-FCH in SHO and F-SCH not in SHO; FPC_MODE = 010 19 20 21 22 23 24 2

a. b. c. d. Setup the test as shown in Annex A Figure A-7. Set power levels as stated in Table 4.2.3-32. Setup a mobile station originated call using Service Option 32 (Test Data Service Option) with 100% frame activity on base station 1. Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:

22

13GPP2 C.S0044-A v1.0

1

ASSIGN_MODE = 100 FOR_RC = 00011 (RC 3) CH_IND = 01 FPC_FCH_FER = 00010 (1%) FPC_FCH_MAX_SETPT = 10000000 (16 dB)
2

GRANTED_MODE = 10 REV_RC = 00011 (RC 3) FPC_FCH_INIT_SETPT = 01000000 (8 dB) FPC_FCH_MIN_SETPT = 00010000 (2 dB)

3 4
5

e.

Instruct the base station to send the Service Connect Message with the parameters set as follows:

FPC_INCL = 1 FPC_PRI_CHAN = 0 FPC_MODE = 010

6

FPC_OLPC_FCH_INCL = 0 GATING_RATE_INCL = 0

7 8 9
10

f.

Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel by using the Extended Supplemental Channel Assignment Message with the power control related parameters set as follows:

FPC_INCL = 1 FPC_MODE_SCH = 010 FPC_SCH_INIT_SETPT_OP = 0 FPC_SCH_FER = 01010 (5%)

11

FPC_SCH_INIT_SETPT = 01000000 (8 dB) FPC_SCH_MAX_SETPT = 10000000 (16 dB) FPC_SCH_MIN_SETPT = 00010000 (2 dB)

12 13 14 15 16

g.

Raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Instruct the base station to send the Universal Handoff Direction Message during FSCH assignment with parameters set as follows:

h.

23

1
1

3GPP2 C.S0044-A v1.0

CH_IND = 101 (FCH and Continuous Reverse Pilot) For PILOT_PN = {base station 1} For PILOT_PN = {base station 2}
2

NUM_PILOTS = 010 PILOT_INCL = 1 PILOT_INCL = 0

3 4 5 6 7 8 9 10 11 12 13 14 15

i. j. k. l.

Verify there are no forward supplemental channels running on base station 2. Set the test parameters as specified in Table 4.2.3-2without dropping the call. Monitor the forward link FER on both F-FCH and F-SCH (during F-SCH assignment) at the mobile station. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.

m.

n. o.

Verify that the forward link FER on FCH and SCH (during SCH assignment) remain at approximately in the target value. End the call at the mobile station.

164.2.3.4.3 F-DCCH in SHO and F-SCH not in SHO; FPC_MODE = 001 17 18 19 20 21 22

23

a. b. c. d.

Setup the test as shown in Annex A Figure A-7. Set power levels as stated in Table 4.2.3-32. Setup a mobile station originated call using Service Option 32 (Test Data Service Option) with 100% frame activity on base station 1. Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:

ASSIGN_MODE = 100 FOR_RC = 00011 (RC 3) CH_IND = 10 FPC_DCCH_FER = 00010 (1%) FPC_DCCH_MAX_SETPT =

GRANTED_MODE = 10 REV_RC = 00011 (RC 3) FPC_DCCH_INIT_SETPT = 01000000 (8 dB) FPC_DCCH_MIN_SETPT = 00010000 (2 dB)

24

13GPP2 C.S0044-A v1.0

10000000 (16 dB)
1

2 3
4

e.

Instruct the base station to send the Service Connect Message with the parameters set as follows:

FPC_INCL = 1 FPC_PRI_CHAN = 1 FPC_MODE = 001

5

FPC_OLPC_FCH_INCL = 0 GATING_RATE_INCL = 0

6 7 8
9

f.

Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel by using the Extended Supplemental Channel Assignment Message with the power control related parameters set as follows:

FPC_INCL = 1 FPC_MODE_SCH = 001 FPC_SCH_INIT_SETPT_OP = 0 FPC_SCH_FER = 01010 (5%)

10

FPC_SCH_INIT_SETPT = 01000000 (8 dB) FPC_SCH_MAX_SETPT = 10000000 (16 dB) FPC_SCH_MIN_SETPT = 00010000 (2 dB)

11 12 13 14 15
16

g.

Raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Instruct the base station to send the Universal Handoff Direction Message during FSCH assignment with parameters set as follows:

h.

CH_IND = 110 (FCH and Continuous Reverse Pilot) For PILOT_PN = {base station 1} For PILOT_PN = {base station 2}
17

NUM_PILOTS = 010 PILOT_INCL = 1 PILOT_INCL = 0

18

i.

Verify there are no forward supplemental channels running on base station 2.

25

1 1 2 3 4 5 6 7 8 9 10 11 12
j. k. l.

3GPP2 C.S0044-A v1.0 Set the test parameters as specified in Table 4.2.3-2without dropping the call. Monitor the forward link FER on both F-DCCH and F-SCH (during F-SCH assignment) at the mobile station. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source. m. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases. n. o. Verify that the forward link FER on DCCH and SCH (during SCH assignment) remain at approximately in the target value. End the call at the mobile station.

134.2.3.4.4 F-DCCH in SHO and F-SCH not in SHO; FPC_MODE = 010 14 15 16 17 18 19

20

a. b. c. d.

Setup the test as shown in Annex A Figure A-7. Set power levels as stated in Table 4.2.3-32. Setup a mobile station originated call using Service Option 32 (Test Data Service Option) with 100% frame activity on base station 1. Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:

ASSIGN_MODE = 100 FOR_RC = 00011 (RC 3) CH_IND = 10 FPC_DCCH_FER = 00010 (1%) FPC_DCCH_MAX_SETPT = 10000000 (16 dB)
21

GRANTED_MODE = 10 REV_RC = 00011 (RC 3) FPC_DCCH_INIT_SETPT = 01000000 (8 dB) FPC_DCCH_MIN_SETPT = 00010000 (2 dB)

22 23
24

e.

Instruct the base station to send the Service Connect Message with the parameters set as follows:

FPC_INCL = 1 FPC_PRI_CHAN = 0

FPC_OLPC_FCH_INCL = 0 GATING_RATE_INCL = 0

26

13GPP2 C.S0044-A v1.0

FPC_MODE = 010
1

2 3 4
5

f.

Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel by using the Extended Supplemental Channel Assignment Message with the power control related parameters set as follows:

FPC_INCL = 1 FPC_MODE_SCH = 010 FPC_SCH_INIT_SETPT_OP = 0 FPC_SCH_FER = 01010 (5%)

6

FPC_SCH_INIT_SETPT = 01000000 (8 dB) FPC_SCH_MAX_SETPT = 10000000 (16 dB) FPC_SCH_MIN_SETPT = 00010000 (2 dB)

7 8 9 10 11
12

g.

Raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Instruct the base station to send the Universal Handoff Direction Message during FSCH assignment with parameters set as follows:

h.

CH_IND = 110 (FCH and Continuous Reverse Pilot) For PILOT_PN = {base station 1} For PILOT_PN = {base station 2}
13

NUM_PILOTS = 010 PILOT_INCL = 1 PILOT_INCL = 0

14 15 16 17 18 19 20 21 22 23

i. j. k. l.

Verify there are no forward supplemental channels running on base station 2. Set the test parameters as specified in Table 4.2.3-2 without dropping the call. Monitor the forward link FER on both F-DCCH and F-SCH (during F-SCH assignment) at the mobile station. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.

m.

27

1 1 2 3
n. o.

3GPP2 C.S0044-A v1.0 Verify that the forward link FER on DCCH and SCH (during SCH assignment) remain at approximately in the target value. End the call at the mobile station. Minimum Standard

44.2.3.5

54.2.3.5.1 F-FCH in SHO and F-SCH not in SHO; FPC_MODE = 001

6The mobile station shall comply with steps i and n.

74.2.3.5.2 F-FCH in SHO and F-SCH not in SHO; FPC_MODE = 010

8The mobile station shall comply with steps i and n.

94.2.3.5.3 F-DCCH in SHO and F-SCH not in SHO; FPC_MODE = 001

10The mobile station shall comply with steps i and n.

114.2.3.5.4 F-DCCH in SHO and F-SCH not in SHO; FPC_MODE = 010

12The mobile station shall comply with steps i and n. 13 14For all tests, the call shall not drop and the FER shall remain in the target value.

154.2.4 164.2.4.1

Change FPC_MODE During a Call Definition

17The mobile station accomplishes fast forward power control by transmitting the power control 18subchannel to the base station on the R-PICH. The mobile station determines the information to 19send to the base station through inner and outer closed loop estimations. In outer loop estimation, 20the mobile station adjusts the Eb/Nt setpoints to the Eb/Nt value necessary to achieve the target 21FER on the Forward Traffic Channel. 22In inner loop estimation, the mobile station compares the received Eb/Nt to the setpoint and 23determines the value of the power control bit to be sent to the base station. This test verifies that 24the mobile station can process a change in FPC_MODE delivered by the Power Control 25Message.

264.2.4.2
27(see [1])

Traceability:

282.1.3.1.10 29(see [4]) 302.6.4.1.1.3 313.7.3.3.2.25 322.6.2.4 332.6.3.3 342.6.3.5

Reverse Power Control Subchannel

Processing the Power Control Message Power Control Message Mobile Station Order and Message Processing Operation Page Response Substate Mobile Station Origination Attempt Substate

28

13GPP2 C.S0044-A v1.0 13.6.3.3 23.6.3.5 33.7.2.3.2.21 42.6.4.1.2 52.6.4.1.2.2 63.7.3.3.2.20 73.7.5 83.7.5.7 93.7.5.20
Response to Page Response Message Response to Origination Message Extended Channel Assignment Message Service Configuration and Negotiation Service Subfunctions Service Connect Message Information Records Service Configuration Non negotiable System Configuration

10Applicability: RC 3 and greater

114.2.4.3
12None

Call Flow Example(s)

134.2.4.4 14 15 16 17 18 19
20

Method of Measurement Connect base station and mobile station as shown in Annex A Figure A-6. Set power levels as stated in Table 4.2.1-2 Setup a mobile station originated call using Service Option 32 (Test Data Service Option) with 100% frame activity. Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:

a. b. c. d.

ASSIGN_MODE = 100 FOR_RC = 00011 (RC 3) CH_IND = 01 FPC_FCH_FER = 00010 (1%) FPC_FCH_MAX_SETPT = 10000000 (16 dB)
21

GRANTED_MODE = 10 REV_RC = 00011 (RC 3) FPC_FCH_INIT_SETPT = 01000000 (8 dB) FPC_FCH_MIN_SETPT = 00010000 (2 dB)

22 23 24

e. f.

Instruct the base station to send the Service Connect Message with FPC_INCL set to 0. Monitor forward link FER at the mobile station.

29

1 1 2 3 4 5 6
7

3GPP2 C.S0044-A v1.0 g. h. i. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 5 dBm/1.23 MHz at the AWGN source. Monitor traffic channel Ec/Ior and ensure power increases corresponding to noise power from the AWGN source. Instruct the base station send the Power Control Message with the parameters set as follows:

FPC_INCL = 1 FPC_PRI_CHAN = 0 FPC_FCH_FER = 00100 (2%) FPC_FCH_MIN_SETPT = 00010000 (2 dB) FPC_OLPC_DCCH_INCL = 0 FPC_DCCH_MIN_SEPT = N/A FPC_OLPC_SCH_M_INCL = 1 FPC_MIN_SCH_M_SETPT = 00010000 (2 dB) NUM_SUP = 1
8

FPC_MODE = 010 FPC_OLPC_FCH_INCL = 1 PWR_CNTL_STEP = 000 (1dB) FPC_FCH_MAX_SETPT = 10000000 (16 dB)

FPC_DCCH_MAX_SEPT = N/A FPC_SCH_M_FER = 00010 (1%) FPC_MAX_SCH_M_SETPT = 10000000 (16 dB)

9 10 11 12 13 14 15 16 17

j. k.

Monitor forward link FER at the mobile station. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 5 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases. Verify that the forward link FER on FCH remains at approximately the target value. End the call at the mobile station. Minimum Standard

l.

m. n.

184.2.4.5
20

19The mobile station shall comply with step m.

30

13GPP2 C.S0044-A v1.0 14.2.5 24.2.5.1

R-PICH in Gated Transmission Mode Gating with the Reverse Dedicated Control Channel

34.2.5.1.1 Definition
4The mobile station accomplishes fast forward power control by transmitting the power control 5subchannel to the base station on the R-PICH. The power control subchannel can either be gated 6(either at a rate of or ) or not gated (a bit is transmitted on every PCG). Gating occurs only 7when the Forward Dedicated Control Channel and the Reverse Dedicated Control Channel are 8assigned and when there are no transmissions on the Reverse Dedicated Control Channel. This 9test verifies that the mobile station can operate in the various gating transmission modes 10specified in the Service Connect Message.

11Figure 4.2.5.1.1-1 Reverse Pilot Gating with no Transmission 12on the Reverse Dedicated Control Channel

31

3GPP2 C.S0044-A v1.0

2Figure 4.2.5.1.1-2 Reverse Pilot Gating during 3Reverse Dedicated Control Channel Transmission

44.2.5.1.2 Traceability:
5(see [1])

62.1.3.1.10 72.1.3.2 8(see [4])

Reverse Power Control Subchannel Reverse Pilot Channel

32

13GPP2 C.S0044-A v1.0 12.6.4.1.1.3 23.7.3.3.2.25 32.6.2.4 42.6.3.3 52.6.3.5 63.6.3.3 73.6.3.5 83.7.2.3.2.21 92.6.4.1.2 102.6.4.1.2.2 113.7.3.3.2.20 123.7.5 133.7.5.7 143.7.5.20
15 16Applicability: Forward Link: RC 1 through RC 5; Reverse Link: RC 1 through RC 4

Processing the Power Control Message Power Control Message Mobile Station Order and Message Processing Operation Page Response Substate Mobile Station Origination Attempt Substate Response to Page Response Message Response to Origination Message Extended Channel Assignment Message Service Configuration and Negotiation Service Subfunctions Service Connect Message Information Records Service Configuration Non negotiable System Configuration

174.2.5.1.3 Call Flow Example(s)

18None

194.2.5.1.4 Method of Measurement 20 21 22 23 24

25

a. b. c. d.

Connect base station and mobile station as shown in Annex A Figure A-6 Set power levels as stated in Table 4.2.1-30. Setup a mobile station originated data call using Service Option 33. Instruct the base station to send the Extended Channel Assignment Message has the parameters set as follows:

ASSIGN_MODE = 100 FOR_RC = 00011 (RC 3) CH_IND = 10 FPC_DCCH_FER = 00010 (1%)

GRANTED_MODE = 10 REV_RC = 00011 (RC 3) FPC_DCCH_INIT_SETPT = 01000000 (8 dB) FPC_DCCH_MIN_SETPT = 00010000 (2 dB)

33

1
FPC_DCCH_MAX_SETPT = 10000000 (16 dB)
1

3GPP2 C.S0044-A v1.0

2 3
4

e.

Instruct the base station to send the Service Connect Message has the parameters set as follows:

FPC_INCL = 1 FPC_PRI_CHAN = 1 FPC_MODE = 000 GATING_RATE_INCL = 1

FPC_OLPC_FCH_INCL = 0 FPC_OLPC_DCCH_INCL = 0

PILOT_GATE_RATE = 01 (gating at )

6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27

f. g. h.

Instruct the base station to send the Extended Release Message with CH_IND set to 100. Do not have any transmissions on the Reverse Dedicated Control Channel. Instruct the base station to send a sufficient number of In-Traffic System Parameters Messages with the same system configurations and without requiring the acknowledgment on the reverse link DCCH so that the mobile station can measure forward FER. Monitor forward link FER at the mobile station. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 5 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.

i. j.

k.

l. m. n. o.

Verify that the reverse Pilot Channel is gated at the specified rate and the forward link FER on DCCH remains at approximately the target value Instruct the mobile station to send the Data Burst Message on the Reverse Dedicated Control Channel. Monitor the forward link FER at mobile station. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 5 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source.

34

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9

p. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases. q. Verify that the reverse Pilot Channel is gated at the target rate if no transmissions are on the Reverse Dedicated Control Channel and the reverse Pilot Channel is not gated if there are transmissions on the Reverse Dedicated Control Channel. Verify that the forward link FER on DCCH remains at approximately the target value. End the call at the mobile station. Repeat steps a through r above except for step e to set PILOT_GATE_RATE to 10 (gating at ).

r. s.

104.2.5.1.5 Minimum Standard

11Gating with the Reverse Dedicated Control Channel 12The mobile station shall comply with steps l, q, and r.

134.2.5.2

Gating with the Reverse Fundamental Channel

144.2.5.2.1 Definition
15The mobile station accomplishes fast forward power control by transmitting the power control 16subchannel to the base station on the R-PICH. The power control subchannel can either be gated 17or not gated. The R-FCH may be gated when no other Reverse Traffic Channel is assigned and 18the data rate is 1500 bps for RC 3 and RC5 or 1800 bps for RC4. When the R-FCH is operated in 19the gated mode and is at a data rate of 1500 bps for RC 3 and RC 5 or 1800bps for RC 4, the R20PICH shall have a transmission duty cycle of 50%. The R-PICH shall be transmitted in power 21control groups 2, 3, 6, 7, 10, 11, 14, and 15, and shall not be transmitted in power control groups 220, 1, 4, 5, 8, 9, 12, and 13. 23

24Figure 4.2.5.2.1-1 Gating with the R-FCH

35

1 14.2.5.2.2 Traceability:
2(see [1])

3GPP2 C.S0044-A v1.0

32.1.3.1.10 42.1.3.2 52.1.3.7.8 6(see [4]) 72.6.4.1.1.3 83.7.3.3.2.25 92.6.6.2.5.1 103.6.6.2.2.12 11 122.6.2.4 132.6.3.3 142.6.3.5 153.6.3.3 163.6.3.5 173.7.2.3.2.21 182.6.4.1.2 192.6.4.1.2.2 203.7.3.3.2.20 213.7.5 223.7.5.7 233.7.5.20

Reverse Power Control Subchannel Reverse Pilot Channel Reverse Fundamental Channel

Processing the Power Control Message Power Control Message Processing of Forward Traffic Channel Handoff Messages Processing of Extended Supplemental Channel Assignment Message Extended Supplemental Channel Assignment Message Mobile Station Order and Message Processing Operation Page Response Substate Mobile Station Origination Attempt Substate Response to Page Response Message Response to Origination Message Extended Channel Assignment Message Service Configuration and Negotiation Service Subfunctions Service Connect Message Information Records Service Configuration Non negotiable System Configuration

24Applicability: RC 3 and greater

254.2.5.2.3 Call Flow Example(s)

26None

274.2.5.2.4 Method of Measurement 28 29 30 31 32

a. b. c. Connect base station and mobile station as shown in Annex A Figure A-6. Set power levels as stated in Table 4.2.1-30. Setup a mobile station originated call using Service Option 32 (Test Data Service Option) with rate 1500 bps only and set the REV_FCH_GATING_REQ field to 1 in the Origination Message.

36

13GPP2 C.S0044-A v1.0 1 2 3

4

d.

Instruct the base station to send the Extended Channel Assignment Message has the parameters set as follows and set the REV_PWR_CNTL_DELAY field according to the base stations implementation.

ASSIGN_MODE = 100 FOR_RC = 00011 (RC 3) CH_IND = 01 FPC_FCH_FER = 00010 (1%) FPC_FCH_MAX_SETPT = 10000000 (16 dB) REV_PWR_CNTL_DELAY_INCL = 1
5

GRANTED_MODE = 10 REV_RC = 00011 (RC 3) FPC_FCH_INIT_SETPT = 01000000 (8 dB) FPC_FCH_MIN_SETPT = 00010000 (2 dB) REV_FCH_GATING_MODE = 1

6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

e. f. g. h.

Instruct the base station to send the Service Connect Message with FPC_INCL set to 0. Ensure the Reverse Fundamental Channel is transmitted at 1/8 rate. Monitor forward link FER at the mobile station. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 5 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.

i.

j. k. l. m.

Verify the Reverse Fundamental Channel is in gated mode and the Reverse Pilot Channel has a transmission duty cycle of 50%. Verify that the forward link FER on FCH is remaining in the target value. End the call at the mobile station. Repeat steps a through l except for the step d to set FOR_RC to 4 and REV_RC to 3.

214.2.5.2.5 Minimum Standard

22The mobile station shall comply with steps j, k and m.

37

1 14.2.6 2 34.2.6.1

3GPP2 C.S0044-A v1.0 Forward Power Control With EIB and QIB While Transmitting Frames on the Forward Fundamental Channel (FPC_MODE = 011 or 100) Definition

4This test shall be performed on the Forward Fundamental Channel with FPC_MODE equal to 5011 and 100. In this test, QIB is same as EIB. The mobile station shall set the EIB or QIB to 60on the Reverse Power Control Subchannel in the second transmitted frame following the 7detection of a good 20ms frame or the detection of at least one good 5ms frame without the 8detection of any bad 5 ms frames within 20ms (if the mobile station support 5ms frame size) on 9the Forward Fundamental Channel. Otherwise the mobile station shall set the EIBor QIB to 1 in 10the second transmitted 20 ms frame.

114.2.6.2
12(see [1])

Traceability

132.1.3.1.10.1 142.2.2.2 15(see [4]) 162.6.4.1.1 173.7.2.3.2.21 184.2.6.3

19None

Reverse Power Control Subchannel Structure Erasure Indicator Bit and Quality Indicator Bit

Forward Traffic Channel Power Control Extended Channel Assignment Message

Call Flow Example(s)

204.2.6.4 21 22 23
a. b.

Method of Measurement Setup test as shown in Annex A Figure A-6. Set power ratios and levels as specified in Table 4.2.6-33. Table 4.2.6-33 Test Parameters for EIB/QIB test Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc dB dB dBm/1.23 MHz Unit dB Channel 1 0 -7 -7 -55

24

25 26 27

c. d.

The Reverse Link attenuation should be set to balance the forward and reverse links (approximately 90 dB). Setup a mobile station originated call.

38

13GPP2 C.S0044-A v1.0 1 2

3

e.

Instruct the base station to send an Extended Channel Assignment Message with the parameters set as follows:

ASSIGN_MODE = 000 or 100 FOR_RC = 00011 (RC 3) CH_IND = 01

4

GRANTED_MODE = 10 REV_RC = 00011 (RC 3)

5 6
7

f.

Instruct the base station to send a Service Connect Message with the parameters set as follows:

FPC_INCL = 1 FPC_PRI_CHAN = 0 FPC_MODE = 011

8

FPC_OLPC_FCH_INCL = 0 GATING_RATE_INCL = 0

9 10 11 12 13 14 15 16

g. h.

From the base station, send a sequence of at least 10 good frames and at least 10 bad frames to the mobile station on the Dedicated Control Channel. Verify that the mobile station Reverse Power Control Subchannel bit pattern follows the frame pattern sent from the base station to the mobile station (i.e. a 0 for a good frame and a 1 for a bad frame). End the call. Repeat steps a through j except for the step e to set REV_RC to 3 and FOR_RC to 4. Repeat steps a through j except for the step e to set REV_RC to 4 and FOR_RC to 5. Minimum Standard

i. j. k.

174.2.6.5

18The mobile station shall comply with steps h.

194.2.7 20 214.2.7.1

Forward Power Control With EIB While Transmitting Frames on the Forward Dedicated Control Channel (FPC_MODE = 011) Definition

22This test shall be performed on the Forward Dedicated Control Channel with FPC_MODE equal 23to 011. The mobile station shall set the EIB to 0 on the Reverse Power Control Subchannel in 24the second transmitted 20ms frame following the detection of a good 20ms frame or the detection 25of at least one good 5ms frame without the detection of any bad 5 ms frames within 20ms on the 26Forward Dedicated Control Channel. Otherwise, the mobile station shall set the EIB to 1 in the 27second transmitted 20 ms frame.

39

1 14.2.7.2
2(see [1])

3GPP2 C.S0044-A v1.0 Traceability

32.1.3.1.10.1 42.2.2.2 5(see [4]) 62.6.4.1.1 73.7.2.3.2.21 84.2.7.3

9None

Reverse Power Control Subchannel Structure Erasure Indicator Bit and Quality Indicator Bit

Forward Traffic Channel Power Control Extended Channel Assignment Message

Call Flow Example(s)

104.2.7.4 11 12 13 14 15 16 17
18

Method of Measurement Setup test as shown in Annex A Figure A-6. Set power ratios and levels as specified in Table 4.2.1-30. The Reverse Link attenuation should be set to balance the forward and reverse links (approximately 90 dB). Setup a mobile station originated data call by using SO33. Instruct the base station to send an Extended Channel Assignment Message with the parameters set as follows:

a. b. c. d. e.

ASSIGN_MODE = 000 or 100 FOR_RC = 00011 (RC 3) CH_IND = 10

19

GRANTED_MODE = 10 REV_RC = 00011 (RC 3)

20 21
22

f.

Instruct the base station to send a Service Connect Message with the parameters set as follows:

FPC_INCL = 1 FPC_PRI_CHAN = 1 FPC_MODE = 011

23

FPC_OLPC_FCH_INCL = 0 GATING_RATE_INCL = 0 DCCH_FRAME_SIZE = 11

24 25

g.

From the base station, send a sequence of at least 10 good frames and at least 10 bad frames to the mobile station on the Forward Fundamental Channel.

40

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6

h. Verify that the mobile station Reverse Power Control Subchannel bit pattern follows the frame pattern sent from the base station to the mobile station (i.e. a 0 for a good frame and a 1 for a bad frame). End the call. Repeat steps d through i except for step e to set REV_RC to 3 and FOR_RC to 4. Repeat steps d through i except for step e to set REV_RC to 4 and FOR_RC to 5. Minimum Standard

i. j. k.

74.2.7.5

8The mobile station shall comply with step h.

94.2.8 10 114.2.8.1

Forward Power Control With QIB on the Forward Dedicated Control Channel (FPC_MODE = 100) Definition

12This test shall be performed on the Forward Dedicated Control Channel with FPC_MODE equal 13to 100. The mobile station shall set the QIB to 0 on the Reverse Power Control Subchannel in 14the second transmitted frame following the detection of a 20ms period with sufficient signal quality 15on the Forward Dedicated Control Channel. The mobile station shall set the QIB to 1 on the 16Reverse Power Control Subchannel in the second transmitted frame following the detection of a 1720ms period with insufficient signal quality on the Forward Dedicated Control Channel. When 18transmitting active frames on the Forward Dedicated Control Channel only, the QIB will be the 19same as the EIB When the frame is inactive (i.e. only the power control bits are transmitted in a 20frame), the Quality Indicator Bit indicates the channel quality.

214.2.8.2
22(see [1])

Traceability:

232.1.3.1.10.1 242.2.2.2 25(see [4]) 262.6.4.1.1 272.6.4.1.1 283.7.2.3.2.21 294.2.8.3

30None

Reverse Power Control Subchannel Structure Erasure Indicator Bit and Quality Indicator Bit

Forward Traffic Channel Power Control Forward Traffic Channel Power Control Extended Channel Assignment Message

Call Flow Example(s)

314.2.8.4 32 33 34 35 36 2
a. b. c. d.

Method of Measurement Setup test as shown in Annex A Figure A-6. Set power ratios and levels as specified in Table 4.2.1-30. The Reverse Link attenuation should be set to balance the forward and reverse links (approximately 90 dB). Setup a mobile station originated data call by using Service Option 33. 41

1 1 2
3

3GPP2 C.S0044-A v1.0 e. Instruct the base station to send an Extended Channel Assignment Message with the parameters set as follows:

ASSIGN_MODE = 100 FOR_RC = 00011 (RC 3) CH_IND = 10

4

GRANTED_MODE = 10 REV_RC = 00011 (RC 3)

5 6
7

f.

Instruct the base station to send a Service Connect Message with the parameters set as follows:

FPC_INCL = 1 FPC_PRI_CHAN = 1 FPC_MODE = 100

FPC_OLPC_FCH_INCL = 0 GATING_RATE_INCL = 0 FPC_OLPC_DCCH_INCL = 0

8 9 10 11 12 13 14

g. h. i. j. k.

Instruct the base station to send a sequence of at least 10 good frames and at least 10 bad frames to the mobile station on the Forward Dedicated Control Channel. Verify the mobile station QIB bit pattern follows the frame pattern sent from the base station to the mobile station (i.e. a 0 for a good frame and a 1 for a bad frame) End the call. Repeat steps d through j except for step e to set REV_RC to 3 and FOR_RC to 4. Repeat steps d through j except for step e to set REV_RC to 4 and FOR_RC to 5. Minimum Standard

154.2.8.5

16The mobile station shall comply with steps h.

174.2.9 18 19 204.2.9.1

Forward Power Control With QIB derived from the Forward Fundamental Channel or Dedicated Control Channel and EIB derived from Supplemental Channel (FPC_MODE = 101) Definition

21This test shall be performed with FPC_MODE equal to 101. The mobile station shall transmit 22QIB derived from the Forward Fundamental Channel or Forward Dedicated Control Channel on 23the Primary Reverse Power Control Subchannel and shall transmit EIB derived from Forward 24Supplemental Channel on the Secondary Reverse Power Control Subchannel. The transmission 25of the QIB and EIB shall start at the second 20 ms frame of the Reverse Traffic Channel following 26the corresponding Forward Traffic Channel frame in which QIB or EIB is determined.

274.2.9.2
28(see [1])

Traceability:

42

13GPP2 C.S0044-A v1.0 12.1.3.1.10.1 22.2.2.2 3(see [4]) 42.6.4.1.1 52.6.4.1.1 63.7.2.3.2.21 74.2.9.3
8None

Reverse Power Control Subchannel Structure Erasure Indicator Bit and Quality Indicator Bit

Forward Traffic Channel Power Control Forward Traffic Channel Power Control Extended Channel Assignment Message

Call Flow Example(s)

94.2.9.4 10 11 12 13 14 15 16
17

Method of Measurement Setup test as shown in Annex A Figure A-6. Set power ratios and levels as specified in Table 4.2.1-30. The Reverse Link attenuation should be set to balance the forward and reverse links (approximately 90 dB). Setup a mobile station originated data call by using Service Option 33. Instruct the base station to send an Extended Channel Assignment Message with the parameters set as follows:

a. b. c. d. e.

ASSIGN_MODE = 100 FOR_RC = 00011 (RC 3) CH_IND = 01

18

GRANTED_MODE = 10 REV_RC = 00011 (RC 3)

19 20
21

f.

Instruct the base station to send a Service Connect Message with the parameters set as follows:

FPC_INCL = 1 FPC_PRI_CHAN = 0 FPC_MODE = 101

FPC_OLPC_FCH_INCL = 0 GATING_RATE_INCL = 0 FCH_FRAME_SIZE = 1

22 23 24
25

g.

Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel with an infinite duration by using the Extended Supplemental Channel Assignment Message with the power control related parameters set as follows:

FPC_INCL = 1

FPC_SEC_CHAN = 0

43

3GPP2 C.S0044-A v1.0

FPC_MODE_SCH = 101

NUM_SUP = 00

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27

h.

Instruct the base station to send a sequence of at least 10 good frames at least 10 bad frames to the mobile station on the Forward Fundamental Channel. Instruct the base station to send a sequence of alternating at least 10 good frames and at least 10 bad frames on the Forward Supplemental Channel. Verify the mobile station QIB bit pattern on Primary Reverse Power Control Channel follows the frame pattern sent from the base station to the mobile station on Forward Fundamental Channel (i.e. a 0 for a good frame and a 1 for a bad frame). Verify the mobile station EIB bit pattern on Secondary Reverse Power Control Subchannel follows the frame pattern sent from the base station to the mobile station on Forward Supplemental Channel (i.e. a 0 for a good frame and a 1 for a bad frame). End the call. Repeat steps d through j except for step e to set REV_RC to 3 and FOR_RC to 4. Repeat steps d through j except for step e to set REV_RC to 4 and FOR_RC to 5. Repeat steps d through l except for the following steps: 1. Step e: Set CH_IND = 10; 2. Step f: Set FPC_PRI_CHAN = 1 and DCCH_FRAME_SIZE = 11; 3. Step h: Instruct the base station to send a sequence of at least 10 good frames and at least 10 bad frames on the Forward Dedicated Control Channel. Instruct the base station to send a sequence of at least 10 good frames and at least 10 bad frames to the mobile station on the Forward Supplemental Channel. 4. Step i: Verify the mobile station QIB bit pattern on Primary Reverse Power Control Channel follows the frame pattern sent from the base station to the mobile station on Forward Dedicated Control Channel (i.e. a 0 for a good frame and a 1 for a bad frame). Verify the mobile station EIB bit pattern on Secondary Reverse Power Control Subchannel follows the frame pattern sent from the base station to the mobile station on Forward Supplemental Channel (i.e. a 0 for a good frame and a 1 for a bad frame). Minimum Standard

i.

j. k. l. m.

284.2.9.5

29The mobile station shall comply with step i.

304.2.10 Forward Power Control With 400 bps data rate on the Forward Fundamental Channel or 31 Forward Dedicated Control Channel and EIB derived from Supplemental Channel 32 (FPC_MODE = 110) 334.2.10.1 Definition
34This test shall be performed with FPC_MODE equal to 110. The mobile station shall transmit the 35Primary Reverse Power Control Subchannel at a 400 bps data rate based on the Forward

44

13GPP2 C.S0044-A v1.0

1Fundamental Channel or Forward Dedicated Control Channel, and shall transmit EIB derived 2from Forward Supplemental Channel on the Secondary Reverse Power Control Subchannel. 3The transmission of the power control bits on the Primary Reverse Power Control Subchannel is 4based on inner and outer closed loop estimations. The transmission of the EIB on the Secondary 5Reverse Power Control Subchannel shall start at the second frame (20ms frame) of the Reverse 6Traffic Channel following the end of the corresponding Forward Supplemental Channel frame 7from which the EIB is derived.

84.2.10.2 Traceability:
9(see [1])

102.1.3.1.10.1 112.2.2.2 12(see [4]) 132.6.4.1.1 142.6.4.1.1 153.7.2.3.2.21

Reverse Power Control Subchannel Structure Erasure Indicator Bit and Quality Indicator Bit

Forward Traffic Channel Power Control Forward Traffic Channel Power Control Extended Channel Assignment Message

164.2.10.3 Call Flow Example(s)

17None

184.2.10.4 Method of Measurement 19 20 21 22 23 24 25

26

a. b. c. d. e.

Setup test as shown in Annex A Figure A-6. Set power ratios and levels as specified in Table 4.2.1-30. The Reverse Link attenuation should be set to balance the forward and reverse links (approximately 90 dB). Setup a mobile station originated data call by using Service Option 33. Instruct the base station to send an Extended Channel Assignment Message with the parameters set as follows:

ASSIGN_MODE = 100 FOR_RC = 00011 (RC 3) CH_IND = '01' FPC_FCH_FER = '00010' (1%) FPC_FCH_MAX_SETPT = '10000000' (16 dB)
27

GRANTED_MODE = 10 REV_RC = 00011 (RC 3) FPC_FCH_INIT_SETPT = '01000000' (8 dB) FPC_FCH_MIN_SETPT = '00010000' (2 dB)

45

1
1 2 3

3GPP2 C.S0044-A v1.0 f. Instruct the base station to send a Service Connect Message with the parameters set as follows:

FPC_INCL = 1 FPC_PRI_CHAN = 0 FPC_MODE = 110

FPC_OLPC_FCH_INCL = 0 FPC_OLPC_DCCH_INCL = 0 GATING_RATE_INCL = 0

4 5 6
7

g.

Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel with an infinite duration by using the Extended Supplemental Channel Assignment Message with the power control related parameters set as follows:

FPC_INCL = 1 FPC_MODE_SCH = 110

FPC_SEC_CHAN = 0 NUM_SUP = 00

8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
28

h. i.

Monitor the forward link FER on the Forward Fundamental Channel at the mobile station. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source. Monitor traffic channel Ec/Ior and ensure the power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.

j.

k. l. m.

Verify that the forward link FER on the FCH remains at approximately the target value. Instruct the base station to send a sequence of at least 10 good frames and at least 10 bad frames to the mobile station on the Forward Supplemental Channel. Verify the mobile station EIB bit pattern on Secondary Reverse Power Control Subchannel follows the frame pattern sent from the base station to the mobile station on Forward Supplemental Channel (i.e. a 0 for a good frame and a 1 for a bad frame) End the call. Repeat steps d through n except for step e to set REV_RC to 3 and FOR_RC to 4. Repeat steps d through n except for step e to set REV_RC to 4 and FOR_RC to 5. Setup a mobile station originated data call by using Service Option 33. Instruct the base station to send an Extended Channel Assignment Message with the parameters set as follows:

n. o. p. q. r.

ASSIGN_MODE = 100

GRANTED_MODE = 10

46

13GPP2 C.S0044-A v1.0

FOR_RC = 00011 (RC 3) CH_IND = 10 FPC_DCCH_FER = 00010 (1%) FPC_DCCH_MAX_SETPT = 10000000 (16 dB)
1

REV_RC = 00011 (RC 3) FPC_DCCH_INIT_SETPT = 01000000 (8 dB) FPC_DCCH_MIN_SETPT = 00010000 (2 dB)

2 3
4

s.

Instruct the base station to send a Service Connect Message with the parameters set as follows:

FPC_INCL = 1 FPC_PRI_CHAN = 1 FPC_MODE = 110

FPC_OLPC_FCH_INCL = 0 FPC_OLPC_DCCH_INCL = 0 GATING_RATE_INCL = 0

5 6 7
8

t.

Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel with an infinite duration by using the Extended Supplemental Channel Assignment Message with the power control related parameters set as follows:

FPC_INCL = 1 FPC_MODE_SCH = 110

FPC_SEC_CHAN = 1 NUM_SUP = 00

9 10 11 12 13 14 15 16 17 18 19 20 21 22

u. v.

Monitor the forward link FER on the Forward Dedicated Control Channel at the mobile station. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source. Monitor traffic channel Ec/Ior and ensure the power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.

w.

x. y. z.

Verify that the forward link FER on the DCCH remains at approximately the target value Instruct the base station to send a sequence of at least 10 good frames and at least 10 bad frames to the mobile station on the Forward Supplemental Channel. Verify the mobile station EIB bit pattern on Secondary Reverse Power Control Subchannel follows the frame pattern sent from the base station to the mobile station on Forward Supplemental Channel (i.e. a 0 for a good frame and a 1 for a bad frame)

47

1 1 aa. 2 bb. 3
cc. End the call.

3GPP2 C.S0044-A v1.0

Repeat steps q through aa except for step r to set REV_RC to 3 and FOR_RC to 4. Repeat steps q through aa except for step r to set REV_RC to 4 and FOR_RC to 5.

44.2.10.5 Minimum Standard

5The mobile station shall comply with steps k, m, x, z.

64.3 74.3.1

Lowest Rate Reverse Fundamental Channel Gating Definition

8This test verifies the mobile station, instructed by the base station, transmits the reverse 9fundamental channel, with radio configurations 3 or 4, in a duty cycle of 50% when using data 10rates of 1500 bps for RC3 and 1800 bps for RC4.

114.3.2

Traceability

12(see [1])

132.1.3.7.8 14(see [4]) 152.2.6.2.5 162.6.3 172.6.3.5 182.6.4 192.7.1.3.2.4 202.7.2.3.2.15 212.7.3 223.6.3.5 233.6.4 243.7.2.3.2.21 253.7.3.3.2.3 263.7.3.3.2.20 273.7.4 283.7.5.5 294.3.3
30None

Reverse Fundamental Channel Gating

Mobile Station Origination Operation System Access State Mobile Station Origination Attempt Substate Mobile Station Control on the Traffic Channel State Origination Message Service Option Control Message Orders Response to Origination Message 1 Traffic Channel Processing Extended Channel Assignment Message Alert With Information Message Service Connect Message Orders 15 Signal 16

Call Flow Example(s)

48

13GPP2 C.S0044-A v1.0 14.3.4 24.3.4.1 3 4

5

Method of Measurement R-FCH Gating disabled at base station Connect the mobile station to the base station as shown in Annex A Figure A-1and set forward link parameters as specified in Table 4.3.4-34.

a.

Table 4.3.4-34 Forward Link Parameters General Setup Parameter Forward Link Power Ior Pilot Ec/Ior Units dBm/1.23MHz dB Values -75 -7

8 9 10 11 12 13 14 15

b. c. d. e. f. g.

Setup a mobile station originated call. Cause the mobile station to send Origination Message with REV_FCH_GATING_REQ = 1. Instruct the base station to send an Extended Channel Assignment Message with REV_FCH_GATING_MODE = 0. Verify audio in both directions. Release the call. Repeat steps c through e for all supported radio configurations. R-FCH Gating enabled at base station Connect the mobile station to the base station as shown in Annex A Figure A-1and set forward link parameters as specified in Table 4.3.4-34. Setup a mobile station originated call. Cause the mobile station to send Origination Message with REV_FCH_GATING_REQ = 1. Instruct the base station, to send the Extended Channel Assignment Message with REV_FCH_GATING_MODE = 1. Verify audio in both directions. Instruct the mobile station to transmit data at 1500 bps (for RC3) or 1800 bps (for RC4) on reverse fundamental channel (i.e. by setting the mobile station to Mute). Verify transmission is gated at 50% - transmission is turned on and off every 2.5ms, or every 2 Power Control Groups (). Release the call. Repeat steps c through e for all supported radio configurations.

164.3.4.2 17 18 19 20 21 22 23 24 25 26 27 28 29 30
a. b. c. d. e. f. g. h. i.

49

1 1
j. Release the call. Minimum Standard R-FCH Gating disabled at base station

3GPP2 C.S0044-A v1.0

24.3.5 34.3.5.1

4The mobile station shall comply with steps e and g.

54.3.5.2

R-FCH Gating enabled at base station

6The mobile station shall comply with steps g and i.

74.4 84.4.1

R-FCH Gating during Soft Handoff Definition

9This test verifies the functionality of R-FCH gating during soft handoffs.

104.4.2

Traceability

11(see [1]) 122.1.3.7.8 13(see [4]) 142.2.6.2.5 152.6.3 162.6.3.5 172.6.4 182.7.1.3.2.4 192.7.2.3.2.15 202.7.3 213.6.3.5 223.6.4 233.7.2.3.2.21 243.7.3.3.2.3 253.7.3.3.2.20 263.7.4 273.7.5.5 284.4.3
29None

Reverse Fundamental Channel Gating

Mobile Station Origination Operation System Access State Mobile Station Origination Attempt Substate Mobile Station Control on the Traffic Channel State Origination Message Service Option Control Message Orders Response to Origination Message 10 Traffic Channel Processing 11 Extended Channel Assignment Message 12 Alert With Information Message 13 Service Connect Message 14 Orders 15 Signal 16

Call Flow Example(s)

50

13GPP2 C.S0044-A v1.0 14.4.4 24.4.4.1

3

Method of Measurement Sectors with Different Values of REV_PWR_CNTL_DELAY

4 5 6
7

a.

Connect the mobile station to base stations 1 and 2 as shown in Annex A Figure A-2 and set forward link parameters as shown inTable 4.4.4-35. Configure a different Pilot PN offset for each base station.

Table 4.4.4-35 Forward Link Parameters for R-FCH Test during Soft Handoff Parameter Forward Link Power Ior Pilot Ec/Ior Units dBm/1.23MHz dB Base Station 1 -75 -7 Base Station 2 -75 -20

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

b. c. d. e. f. g. h. i.

Configure base station 1 and base station 2 to be on different power control delay regions: base station 1 = 2 PCGs and base station 2 = 3 PCGs. Setup a mobile station originated call. Cause the mobile station to send Origination Message with REV_FCH_GATING_REQ = 1. Instruct the base station to send an Extended Channel Assignment Message with REV_FCH_GATING_MODE = 1 and REV_PWR_CNTL_DELAY = 2. Verify audio in both directions. Instruct the mobile station to transmit data at 1500 bps (for RC3) or 1800 bps (for RC4) on reverse fundamental channel (i.e. by setting the mobile station to Mute). Verify transmission is gated at 50% - transmission is turned on and off every 2.5ms, or every 2 Power Control Groups (). Raise the level of base station 2 in steps of 1 dB with a dwell time of 1 sec until base station 1 sends an Universal Handoff Direction Message or General Handoff Direction Message with REV_FCH_GATING_MODE = 0. Verify mobile station has both base stations on its active pilot set list. Verify mobile station transmission of 1500 bps (for RC3) or 1800 bps (for RC4) frames is not gated at 50% duty cycle. Release the call. Repeat steps b through l for all support radio configurations.

j. k. l. m.

51

1 14.4.4.2 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
a. Sectors with Same Value of REV_PWR_CNTL_DELAY

3GPP2 C.S0044-A v1.0

Connect the mobile station to base stations 1 and 2 as shown in Annex A Figure A-2 and set forward link parameters as shown inTable 4.4.4-35. Configure a different Pilot PN offset for each base station but with the same frequency. Configure base station 1 and base station 2 to be on the same power control delay region = 2 PCGs. Setup a mobile station originated call. Verify the mobile station sends Origination Message with REV_FCH_GATING_REQ = 1. Instruct the base station to send an Extended Channel Assignment Message with REV_FCH_GATING_MODE = 1 and REV_PWR_CNTL_DELAY = 2. Verify audio in both directions. Instruct the mobile station to transmit data at 1500bps on reverse fundamental channel (i.e. by setting the mobile station to Mute) Verify transmission is gated at 50% - transmission is turned on and off every 2.5ms, or every 2 Power Control Groups (). Raise the level of base station 2 in steps of 1 dB with a dwell time of 1 sec until base station 1 sends an Universal Handoff Direction Message or General Handoff Direction Message, REV_FCH_GATING_MODE = 1. Verify mobile station has both base stations on its active pilot set list. Verify mobile station transmission of 1500 bps (for RC3) or 1800 bps (for RC4) frames is gated at 50% duty cycle. Lower the level of base station 1 in steps of 1 dB with a dwell time of 1 sec until base station 2 sends an Universal Handoff Direction Message or General Handoff Direction Message, with REV_FCH_GATING_MODE = 1 and REV_PWR_CNTL_DELAY = 2. Verify mobile station has only base station 2 on its active pilot set list. Verify mobile station transmission of 1500 bps (for RC3) or 1800 bps (for RC4) frames is gated at 50% duty cycle. Release the call. Repeat steps b through o for all supported radio configurations. Minimum Standard Sectors with Same Value of REV_PWR_CNTL_DELAY

b. c. d. e. f. g. h. i.

j. k. l.

m. n. o. p.

314.4.5 324.4.5.1

33The mobile station shall comply with steps d, h, j, k and m.

344.4.5.2

Sectors with Different Values of REV_PWR_CNTL_DELAY

35The mobile station shall comply with steps d, h, j, k, m, n, and p.

52

13GPP2 C.S0044-A v1.0 15 25.1 35.1.1

REGISTRATIONS
Power-Up Registration Definition

4These tests verify proper power-up registration functionality. The mobile station registers when it 5powers on, switches from using a different frequency block, switches from using a different band 6class, switches from using an alternative operating mode, or switches from using the analog 7system. To prevent multiple registrations when power is quickly turned on and off, the mobile 8station delays T57m seconds before registering, after entering the Mobile Station Idle State.

95.1.2

Traceability

10(see [4])

112.6.5.1.1 122.6.5.5.1.3 132.6.5.5.2.1 142.7.1.3.2.1 153.6.5 163.7.2.3.2.1 173.7.2.3.2.30 185.1.3

19None

Power-Up Registration Entering the Mobile Station Idle State Idle Registration Procedures Registration Message Registration System Parameters Message ANSI-41 System Parameters Message

Call Flow Example(s)

205.1.4 215.1.4.1 22 23 24 25 26 27
a. b. c. d.

Method of Measurement Power-up Registration Disabled Connect the base station and mobile station as shown in Figure A-3. Instruct the base station to set POWER_UP_REG = 0 in the System Parameters Message or ANSI-41 System Parameters Message. Power on the mobile station. Verify the mobile station does not attempt power-up registration for at least 1 minute after the mobile station enters the Mobile Station Idle State. Power-up Registration Enabled Connect the base station and mobile station as shown in Figure A-3. Instruct the base station to set POWER_UP_REG = 1 in the System Parameters Message or ANSI-41 System Parameters Message Power on the mobile station.

285.1.4.2 29 30 31 32 2
a. b. c.

1 1 2
d.

3GPP2 C.S0044-A v1.0 Verify the mobile station sends a Registration Message with REG_TYPE = 0001 no sooner than 20 seconds (T57M) after entering Mobile Station Idle State. Power-up Registration due to change in Operating Mode Connect the base station and mobile station as shown in Figure A-5. (Base station 1 is a CDMA base station and base station 2 is a non-CDMA base station. Allow the mobile station to operate in the idle state on base station 2. Configure base station 1 to set POWER_UP_REG = 1 in the System Parameters Message or the ANSI-41 System Parameters Message. Force the mobile station to acquire base station 1. Verify the mobile station sends a Registration Message with REG_TYPE = 0001 on base station 1. Power-up Registration entering into different Band Class Connect the base station and mobile station as shown in Figure A-5. (Base station 1 and base station 2 are CDMA base stations using different band classes) Instruct both base station 1 and base station 2 to set POWER_UP_REG = 1 in the System Parameters Message or the ANSI-41 System Parameters Message. Power on the mobile station. Verify the mobile station sends a Registration Message with REG_TYPE = 0001 on base station 1. Force the mobile station to acquire base station 2. Verify the mobile station a Registration Message with REG_TYPE = 0001 on base station 2. Force the mobile station to acquire base station 1. Verify the mobile station performs power-up registration on base station 1. Power-up Registration entering into Different Frequency Blocks Connect the base station and mobile station as shown in Figure A-5. (Base station 1 and base station 2 are CDMA base stations using the same band class with frequencies assignments in a different serving system.) Instruct both base station 1 and base station 2 to set POWER_UP_REG = 1 in the System Parameters Message or the ANSI-41 System Parameters Message while ensuring all other forms of registration are disabled. Power on the mobile station. Verify the mobile station sends a Registration Message with REG_TYPE = 0001 on base station 1. Force the mobile station to acquire base station 2.

35.1.4.3 4 5 6 7 8 9 10 11
a. b. c. d. e.

125.1.4.4 13 14 15 16 17 18 19 20 21 22 23 24
a. b. c. d. e. f. g. h.

255.1.4.5 26 27 28 29 30 31 32 33 34 35
a.

b.

c. d. e.

13GPP2 C.S0044-A v1.0 1 2

f. Verify the mobile station sends a Registration Message with REG_TYPE = 0001 on base station 2. Minimum Standard Power-up Registration Disabled

35.1.5 45.1.5.1

5The mobile station shall comply with step d. Power-up registration shall not occur.

65.1.5.2

Power-up Registration Enabled

7The mobile station shall comply with step d. The mobile station shall perform the registration 8process when it is powered on and after the power/initialization timer has expired.

95.1.5.3

Power-up Registration entering into different operating mode

10The mobile station shall comply with step e.

115.1.5.4

Power-up Registration entering into different Band Class

12The mobile station shall comply with steps d, f and h.

135.1.5.5

Power-up Registration entering into Different Frequency Blocks

14The mobile station shall comply with steps d and f.

155.2 165.2.1

Power - Down Registration Definition

17These tests verify power-down registration functionality. The mobile station should be able to 18recognize all base station registration settings. 19The mobile station registers when it powers off if previously registered in the current serving 20system. The mobile station should not perform power-down registration if it has not previously 21registered in the system corresponding to its current SID and NID.

225.2.2

Traceability

23(see [4])

242.6.5.1.1 252.6.5.1.2 262.6.5.5.2.1 272.7.1.3.2.1 283.6.5 293.7.2.3.2.1 303.7.2.3.2.30 315.2.3

32None

Power-Up Registration Power-Down Registration Idle Registration Procedures Registration Message Registration System Parameters Message ANSI - 41 System Parameters Message

Call Flow Example(s)

1 15.2.4 25.2.4.1 3 4 5 6 7 8 9 10
a. b. Method of Measurement Power-down Registration Disabled

3GPP2 C.S0044-A v1.0

Connect the base station and mobile station as shown in Figure A-3. Enable power-up registration (set POWER_UP_REG = 1 in the System Parameters Message or ANSI - 41 System Parameter Message) while ensuring all other forms of registration are disabled. Power on the mobile station. Verify the mobile station performs a power-up registration. Power down the mobile station. Verify power-down registration does not occur. Power-down Registration of a Currently Registered Mobile Station Connect the base station and mobile station as shown in Figure A-3. Enable power-up registration (set POWER_UP_REG = 1) and power-down registration (set POWER_DOWN_REG = 1) in the System Parameters Message or ANSI - 41 System Parameter Message) while ensuring all other forms of registration are disabled. Power on the mobile station. Verify power-up registration occurs. Power down the mobile station. Verify the mobile station sends a Registration Message with REG_TYPE = 0011. Power-down Registration of an Unregistered Mobile Station in New System/Network Connect the base station and mobile station as shown in Figure A-5. (Base station 1 and base station 2 are CDMA base stations using a different SID/NID). Instruct base station 1 to set POWER_ UP = 1 and both base station 1 and base station 2 to set POWER_DOWN = 1 in the System Parameters Message or ANSI - 41 System Parameter Message, and turn off all other types of registration. Power on the mobile station. Verify power-up registration on base station 1. Force the mobile station to acquire base station 2. Verify power-down registration does not occur on base station 2. Minimum Standard Power-down Registration Disabled

c. d. e. f.

115.2.4.2 12 13 14 15 16 17 18 19
a. b.

c. d. e. f.

205.2.4.3 21 22 23 24 25 26 27 28 29
a. b.

c. d. e. f.

305.2.5 315.2.5.1

32The mobile station shall comply with steps d and f. Power-down registration shall not occur.

13GPP2 C.S0044-A v1.0 15.2.5.2

Power-down Registration of a Currently Registered Mobile Station

2The mobile station shall comply with steps d and f. The mobile station shall perform power-down 3registration in a system/network where it is currently registered.

45.2.5.3

Power-down Registration of an Unregistered Mobile Station in a New System/Network

5The mobile station shall comply with steps d and g. Power-down registration shall not occur in a 6system/network where the mobile station is not currently registered.

75.3 85.3.1

Distance-Based Registration Definition

9These tests verify proper distance-based registration functionality. 10The mobile station should be able to recognize all base station registration settings. 11The mobile station registers when the distance between the current base station and the base 12station in which it last registered exceeds a threshold.

135.3.2

Traceability

14(see [4])

152.6.5.1.1 162.6.5.1.4 173.6.5 183.7.2.3.2.1 193.7.2.3.2.30 203.7.2.3.2.31 215.3.3

22None

Power-Up Registration Distance-Based Registration Registration System Parameters Message ANSI - 41 System Parameters Message MC-RR Parameters Message

Call Flow Example(s)

235.3.4 245.3.4.1 25 26 27 28 29 30 31 32 33
a. b.

Method of measurement Distance-Based Registration Disabled Connect the base station and mobile station as shown in Figure A-5. Use the parameters in Table 5.3.4-36. Configure base station 1 and base station 2 to send the System Parameters Message or the ANSI - 41 System Parameters Message with REG_DIST, BASE_LAT and BASE_LONG parameters as indicated in Table 5.3.4-2 (Test Case 1). Instruct both base station 1 and base station 2 to set power-up registration (set POWER_UP_REG = 1) in the System Parameters Message or the ANSI - 41 System Parameters Message. Power on the mobile station on base station 1.

c.

d.

1 1 2 3 4 5 6 7
e. f. Verify power-up registration occurs.

3GPP2 C.S0044-A v1.0

Force the mobile station to perform an idle handoff to base station 2 by reducing base station 2 forward link attenuation, then increasing base station 1 forward link attenuation. Verify the mobile station does not perform distance-based registration.

g.

Table 5.3.4-36 Forward Link Parameters for Distance-based Registration Parameter Ior/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io Unit dB dB dB dB/1.23 MHz dB -10.2 Channel 1 0 -7 -7 -75 Channel 2 -10 -7 -7 -75 -20.2

9
10 Table 5.3.4-2 BTS Distance based LAT/LONG System Parameters Message or the ANSI - 41 11 System Parameters Message Configuration

Parameters BTS 1 BASE_LAT (sec/4) BTS 1 BASE_LONG (sec/4) BTS 2 BASE_LAT (sec/4) BTS 2 BASE_LONG (sec/4) REG_DIST

Test Case 1 0X4 0X4 0X400 0X400 0X0

Test Case 2 0X4 0X4 0X400 0X400 0X50

Test Case 3 0X4 0X4 0X400 0X400 0X10

13 145.3.4.2 15 16 17 18 19
a. b. Distance Threshold Not Exceeded Connect the base station and mobile station as shown in Figure A-5. Use the parameters in Table 5.3.4-36. Configure base station 1 and base station 2 to send the System Parameters Message or the ANSI - 41 System Parameters Message with REG_DIST, BASE_LAT and BASE_LONG parameters as indicated in Table 5.3.4 -2 (Test Case 2).

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9

c. Instruct both base station 1 and base station 2 to set power-up registration (set POWER_UP_REG = 1) in the System Parameters Message or the ANSI - 41 System Parameters Message. Power on the mobile station. Verify power-up registration occurs. Force the mobile station to perform an idle handoff to base station 2 by reducing base station 2 forward link attenuation, then increasing base station 1 forward link attenuation. Verify the mobile station does not perform distance-based registration. Distance Threshold Exceeded Connect the base station and mobile station as shown in Figure A-5. Use the parameters in Table 5.3.4-36. Configure base station 1 and base station 2 to send the System Parameters Message or the ANSI - 41 System Parameters Message with REG_DIST, BASE_LAT and BASE_LONG parameters as indicated in Table 5.3.4-2 (Test Case 3). Instruct both base station 1 and base station 2 to set power-up registration (set POWER_UP_REG = 1) in the System Parameters Message or the ANSI - 41 System Parameters Message. Power on the mobile station. Verify power-up registration occurs. Force mobile station to perform idle handoff to base station 2 by reducing base station 2 forward link attenuation, then increasing base station 1 forward link attenuation. Verify the mobile station sends a Registration Message with REG_TYPE = 0110. Minimum Standard Distance-based Registration Disabled

d. e. f.

g.

105.3.4.3 11 12 13 14 15 16 17 18 19 20 21 22 23
a. b.

c.

d. e. f. g.

245.3.5 255.3.5.1

26The mobile station shall comply with step g. Distance-based registration shall not occur.

275.3.5.2

Distance Threshold Not Exceeded

28The mobile station shall comply with step g. The mobile station shall not perform distance-based 29registration when distance-based registration enabled and calculated value of DISTANCE is less 30than REG_DIST.

315.3.5.3

Distance Threshold Exceeded

32The mobile station shall comply with step g. The mobile station shall perform distance-based 33registration when distance based registration is enabled and the calculated value of DISTANCE is 34greater than REG_DIST.

1 15.4 25.4.1
Timer-Based Registration Definition

3GPP2 C.S0044-A v1.0

3These tests verify proper timer - based registration functionality. 4The mobile station registers when a timer expires. 5Timer-based registration is performed when the counter reaches a maximum value 6(REG_COUNT_MAX) that is controlled by the base station via the REG_PRD field of the System 7Parameters Message or ANSI-41 System Parameters Message. 8 The counter is reset when the mobile station powers on. The counter is reset after each 9successful registration.

105.4.2

Traceability

11(see [4])

122.6.5.1.2 132.6.5.1.3 142.7.1.3.2.1 153.6.5 163.7.2.3.2.1 173.7.2.3.2.30 185.4.3

19None

Power-Down Registration Timer-Based Registration Registration Message Registration System Parameters Message ANSI- 41 System Parameters Message

Call Flow Example(s)

205.4.4 215.4.4.1 22 23 24 25 26 27
a. b. c. d. e.

Method of Measurement Timer-based Registration Disabled Connect the base station and mobile station as shown in Figure A-3. Instruct the base station to set POWER_UP_REG =1 and set REG_PRD = 0 in the System Parameters Message or ANSI 41 System Parameter Message. Power on the mobile station. Verify power-up registration occurs. Verify the mobile station does not perform timer-based registration. Mid-range Timer Value Connect the base station and mobile station as shown in Figure A-3. Instruct the base station to set POWER_UP_REG =0 and set REG_PRD = 38 (57.93 seconds) in the System Parameters Message or ANSI 41 System Parameter Message. Power on the mobile station.

285.4.4.2 29 30 31 32 33
a. b.

c.

13GPP2 C.S0044-A v1.0 1

d. Verify timer-based registration occurs approximately every 58 seconds. Minimum Standard Timer-based Registration Disabled

25.4.5 35.4.5.1

4The mobile station shall comply with steps d and e. Timer-based registration shall not occur.

55.4.5.2

Mid-Range Timer Value

6The mobile station shall comply with step d. The mobile station shall perform time-based 7registration at the interval specified by the REG_PRD value.

85.5 95.5.1

Parameter-Change Registration Definition

10These tests verify proper parameter-change registration functionality. 11Parameter-change registration is performed when a mobile station modifies any of the following 12stored parameters:

13

a.

The mobile stations SID_NID_LIST does not match the base stations SID and NID. Traceability

145.5.2

15(see [4])

162.6.5.1.6 173.6.5 183.7.2.3.2.1 193.7.2.3.2.30 205.5.3

21None

Parameter-Change Registration Registration System Parameters Message ANSI - 41 System Parameters Message

Call Flow Example(s)

225.5.4 235.5.4.1 24 25 26 27 28 29 30 31 32
a.

Method of Measurement Parameter-Change Registration Disabled Connect the base station and mobile station as shown in Figure A-5. Base station 1 and base station 2 are CDMA base station operating in the same band class and frequencies with different SID values. Instruct the base station to set PARAMETER_REG = 0 and disable all other forms of registration (set equal to 0) in the System Parameters Message or ANSI - 41 System Parameters Message. Power on the mobile station and allow time for the mobile station to acquire base station 1. Force the mobile station to acquire base station 2.

b.

c. d.

1 1
e. Verify the mobile station does not send a Registration Message. Parameter-Based Registration per SID-NID List change

3GPP2 C.S0044-A v1.0

25.5.4.2 3 4 5 6 7 8 9 10 11 12 13
a. b.

Connect the base station and mobile station as shown in Figure A-5. (Base station 1 and base station 2 are CDMA base stations using different SID configurations). Instruct both base station to set PARAMETER_REG = 1 while ensuring all other forms of registration are disabled (set equal to 0) in the System Parameters Message or ANSI - 41 System Parameters Message. Power on the mobile station and allow time for the mobile station to acquire Base Station 1. Force the mobile station to acquire Base Station 2. Verify the mobile station sends a Registration Message with REG_TYPE = 0100. Repeat steps a through e with base station 1 and base station 2 using different NID configurations. Minimum Standard Parameter-Change Registration Disabled The mobile station shall comply with step e. Parameter-Based Registration per SID-NID List change

c. d. e. f.

145.5.5 155.5.5.1 165.5.5.2 17

18The mobile station shall comply with step e.

195.6 205.6.1

Zone-Based Registration Definition

21These tests verify proper Zone-based registration functionality. 22The mobile station registers when it enters a new zone that is not on its internally stored list of 23visited registration zones. 24The mobile station does not register when it performs an idle handoff into a zone that is on its 25internally stored list of visited zones. 26The mobile station should properly delete entries from its internally stored list of visited 27registration zones.

285.6.2

Traceability

29(see [4])

302.6.5.1.1 312.6.5.1.5 323.6.5 333.7.2.3.2.1

Power-Up Registration Zone-Based Registration Registration System Parameters Message

10

13GPP2 C.S0044-A v1.0 13.7.2.3.2.30 25.6.3

3None

ANSI 41 System Parameters Message

Call Flow Diagram

45.6.4 55.6.4.1
6

Method of Measurement Zone-Based Registration Disabled

7
Parameters

Table 5.6.4-37 Parameters for Zone-base Reistration Tests Test Case 1 0x1 0x2 0x0 0x0 Test Case 2 0x1 0x2 0x0 0x2 Test Case 3 0x1 0x2 0x0 0x2 Test Case 4 0x1 0x2 0x1 0x1

BTS 1 REG_ ZONE BTS 2 REG_ZONE ZONE_TIMER TOTAL_ZONES

8 9 10 11 12 13 14 15 16 17 18

a. b.

Connect the base station and mobile station as shown in Figure A-5. Configure the System Parameters Message or ANSI - 41 System Parameters Message on base stations 1 and 2 with the REG_ZONE settings from Table 5.6.4-37, test case 1. Enable power-up registration (set POWER_UP_REG = 1 in the System Parameters Message or ANSI 41 System Parameters Message). Allow for the mobile station to perform a power up registration on base station 1. Force the mobile station to perform an idle handoff to base station 2 by reducing the base station 2 forward link attenuation, while at the same time increasing the base station 1 forward link attenuation. Verify zone-based registration does not occur. Zone-Based Registration Enabled Connect the base station and mobile station as shown in Figure A-5. Configure the System Parameters Message or ANSI - 41 System Parameters Message on base stations 1 and 2 with the settings from Table 5.6.4-37, test case 2. Enable power-up registration (set POWER_UP_REG = 1 in the System Parameters Message or ANSI 41 System Parameters Message). Power on the mobile station and allow it to perform a power up registration on base station 1. (The mobile station should now be registered in zone 1 and the only entry in the mobile stations ZONE_LIST).

c. d. e.

f.

195.6.4.2 20 21 22 23 24 25 26 27
a. b. c. d.

11

1 1 2 3 4 5 6 7 8 9 10 11
e.

3GPP2 C.S0044-A v1.0 Force the mobile station to perform an idle handoff to base station 2 by reducing the base station 2 forward link attenuation, while at the same time increasing the base station 1 forward link attenuation. Verify the mobile station sends a Registration Message with REG_TYPE = 0010. (The mobile station should now be registered in zone 2. Zone 1 and Zone 2 should be in the mobile stations ZONE_LIST). Before the period of time specified by ZONE_TIMER has elapsed (one minute) and the mobile station deletes zone 1 from its ZONE_LIST, force the mobile station to perform an idle handoff back to base station 1. Verify zone-based registration does not occur. (Zone 1 is still in the mobile stations ZONE_LIST). Zone-Based Registration Timer Connect the base station and mobile station as shown in Figure A-5. Configure the System Parameters Message or ANSI - 41 System Parameters Message on base stations 1 and 2 with the settings from Table 5.6.4-37, test case 3. Enable power-up registration (set POWER_UP_REG = 1 in the System Parameters Message or ANSI 41 System Parameters Message). Power on the mobile station and allow it to perform a power up registration on base station 1. (The mobile station should now be registered in zone 1 and the only entry in the mobile stations ZONE_LIST). Force the mobile station to perform an idle handoff to base station 2 by reducing the base station 2 forward link attenuation, while at the same time increasing the base station 1 forward link attenuation. Verify zone-based registration occurs. (The mobile station should now be registered in zone 2. Zone 1 and Zone 2 should be in the mobile stations ZONE_LIST). Wait for the period of time specified by ZONE_TIMER to elapse (one minute, after which the mobile station should delete zone 1 from ZONE_LIST). Force the mobile station to perform an idle handoff to base station 1. Verify the mobile station sends a Registration Message with REG_TYPE = 0010. Mobile Station ZONE_LIST Deletion Connect the base station and mobile station as shown in Figure A-5. Configure the System Parameters Message or ANSI - 41 System Parameters Message on base stations 1 and 2 with the settings from Table 5.6.4-37, test case 4. Enable power-up registration (set POWER_UP_REG = 1 in the System Parameters Message or ANSI 41 System Parameters Message).

f.

g.

h.

125.6.4.3 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
a. b. c. d.

e.

f. g. h. i.

305.6.4.4 31 32 33 34 35
a. b. c.

12

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13

d. Power on the mobile station and allow it to perform a power up registration on base station 1. (The mobile station should now be registered in zone 1 and the only entry in the mobile stations ZONE_LIST). Force the mobile station to perform an idle handoff to base station 2 by reducing the base station 2 forward link attenuation, while at the same time increasing the base station 1 forward link attenuation. Verify the mobile station sends a Registration Message with REG_TYPE = 0010. (The mobile station is now registered in zone 2, and only zone 2 should be in mobile stations ZONE_LIST because the mobile station was forced to delete zone 1 from ZONE_LIST to make room for zone 2). Force the mobile station to perform an idle handoff back to base station 1. Verify the mobile station sends a Registration Message with REG_TYPE = 0010. (Zone 1 is not in ZONE_LIST). Minimum Standard Zone-Based Registration Disabled

e.

f.

g. h.

145.6.5 155.6.5.1

16The mobile station shall comply with step f. The mobile station shall not perform a zone-based 17registration.

185.6.5.2

Zone-Based Registration Enabled

19The mobile station shall comply with steps f, h. The mobile station performs a zone-based 20registration.

215.6.5.3

Zone-Based Registration Timer

22The mobile station shall comply with steps f, and i. The mobile station performs a zone-based 23registration.

245.6.5.4

Mobile Station ZONE_LIST Deletion

25The mobile station shall comply with steps f, h. The mobile station performs a zone-based 26registration. 27

13

1
1No text.

3GPP2 C.S0044-A v1.0

14

13GPP2 C.S0044-A v1.0 16 26.1 36.1.1

AUTHENTICATION
Shared Secret Data (SSD) Initialized when A-Key is Changed Definition

4This test verifies that when the A-Key is changed at both the base station and mobile station, 5authentication of mobile station registrations, originations, and terminations and the Unique 6Challenge-Response Procedure are successful.

76.1.2

Traceability:

8(see [4])

92.3.12.1 102.6.5.1.3 113.3.1 126.1.3

13None

(MS) Authentication Timer-Based Registration (Base Station) Authentication

Call Flow Example(s)

146.1.4 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
a. b. c. d. e. f. g. h. i. j. k. l. m.

Method of Measurement Connect the base station and mobile station as shown in Annex A Figure A-1. Power on the mobile station. Initialize the A-Key to the same value in the mobile station and base station. Ensure timer-based registration is enabled with the registration period (REG_PRD) set to 29. Verify the mobile station sends a Registration Message with REG_TYPE set to 0000 (i.e. timer-based registration) and which includes AUTHR, RANDC and COUNT. Verify registration authentication is successful at the base station. Setup a mobile station originated call. Verify user data in both directions. End the call. Setup a mobile station terminated call. Verify user data in both directions. Instruct the base station to initiate a Unique Challenge-Response Procedure while on the f/r-dsch. Verify the following: 1. The base station sends an Authentication Challenge Message,

1 1 2 3 4 5 6 7 8 9 10 11 126.1.5
n. o. p.

3GPP2 C.S0044-A v1.0 2. Upon receiving this message, the mobile station sends an Authentication Challenge Response Message, and 3. The Unique Challenge-Response Procedure is successful. End the call. Instruct the base station to initiate a Unique Challenge-Response Procedure while on the f/r-csch. Verify the following: 1. The base station sends an Authentication Challenge Message, 2. Upon receiving this message, the mobile station sends an Authentication Challenge Response Message, and 3. The Unique Challenge-Response Procedure is successful. Minimum Standard

13The mobile station shall comply with the following steps: e, h, k, m, p. 14The base station shall comply with the following steps: f, h, k, m, p.

156.2 166.2.1

Shared Secret Data Update Definition

17This test verifies the mobile station and base station can perform a Shared Secret Data update on 18the f/r-csch and f/r-dsch.

196.2.2

Traceability:

20(see [4])

212.3.12.1.4 222.3.12.1.5 232.6.5.1.3 242.7.1.3.2.6 253.7.2.3.2.1 263.7.2.3.2.10 276.2.3

28None

Unique Challenge-Response Procedure Updating the Shared Secret Data (SSD) Timer-Based Registration Authentication Challenge Response Message System Parameters Message (f-csch) Authentication Challenge Message (f-csch)

Call Flow Example(s)

296.2.4 30 31 32
a. b. c.

Method of Measurement Connect the base station and mobile station as shown in Annex A Figure A-1. Power on the mobile station. Initialize the A-Key to the same value in both the mobile station and base station.

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33

q. n. o. p. f. g. h. i. j. k. l. m. d. e. Instruct the base station to initiate a Shared Secret Data update on the f/r-csch. Verify the following: 1. The base station sends a SSD Update Message, 2. The mobile station sends a Base Station Challenge Order, 3. The base station sends a Base Station Challenge Confirmation Order, 4. The mobile station sends a SSD Update Confirmation Order, and 5. That the SSD Update Procedure is successful. Ensure timer-based registration is enabled with the registration period (REG_PRD) set to 29. Wait for the mobile station to send the Registration Message with REG_TYPE set to 0000 (i.e. timer-based registration). Verify the Registration Message includes AUTHR, COUNT and RANDC. Verify registration authentication is successful at the base station. Setup a mobile station originated call. Verify user data in both directions. Instruct the base station to initiate a Unique Challenge-Response Procedure on the f/rdsch. Verify the following: 1. The base station sends an Authentication Challenge Message, 2. Upon receiving this message, the mobile station sends a Authentication Challenge Response Message, and 3. That the Unique Challenge-Response Procedure is successful. End the call. Instruct the base station to initiate a Unique Challenge-Response Procedure on the f/rcsch. Verify the following: 1. The base station sends an Authentication Challenge Message, 2. Upon receiving this message, the mobile station sends a Authentication Challenge Response Message, and 3. That the Unique Challenge-Response Procedure is successful. Repeat steps c through p but with the following exception: 1. In step d, setup a call and initiate a Shared Secret Data update on the f/r-dsch, and then end the call.

1 16.2.5
Minimum Standard

3GPP2 C.S0044-A v1.0

2The mobile station shall comply with the following steps: e, h, k, m, p, q. 3The base station shall comply with the following steps: e, i, k, m, p, q.

46.3 56.3.1

Mismatched A-Keys Definition

6This test verifies that when there is an A_KEY mismatch, authentication of registrations, 7originations, terminations, and Unique Challenge-Response procedures will fail.

86.3.2

Traceability

9(see [4])

102.3.12.1.4 112.3.12.1.5 122.7.1.3.2.6 132.7.2.3.2.2 143.7.2.3.2.10 153.7.2.3.2.1 163.7.3.3.2.2 173.7.3.3.2.13 186.3.3

19None

Unique Challenge-Response Procedure Updating the Shared Secret Data (SSD) Authentication Challenge Response Message Authentication Challenge Response Message (r-dsch) Authentication Challenge Message (f-csch) SSD Update Message (f-csch) Authentication Challenge Message (f-dsch) SSD Update Message (f-dsch)

Call Flow Example(s)

206.3.4 21 22 23 24 25 26 27 28 29 30 31 32
a. b. c. d. e. f. g. h. i. j.

Method of Measurement Connect the base station and mobile station as shown in Annex A Figure A-1. Power on the mobile station. Initialize the A-Key to the same value in the mobile station and base station. Instruct the base station to initiate a Shared Secret Data update on the f/r-csch. Setup a mobile station originated call. Verify user data in both directions. End the call. Change the A-Key in the mobile station. Ensure timer-based registration is enabled with the registration period (REG_PRD) set to 29. Wait for the mobile station to send a Registration Message with REG_TYPE set to 0000 (i.e. timer-based registration).

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10

k. l. m. n. o. p. q. r. s. t. Verify the Registration Message includes AUTHR, COUNT and RANDC. Verify registration authentication fails at the base station due to an AUTHR mismatch. Setup a mobile station originated call. Verify that the call request was denied. Setup a mobile station terminated call. Verify the call fails due to an AUTHR mismatch. Initiate at the base station a Shared Secret Data update on the f-csch. Verify the SSD Update fails with an AUTHBS mismatch. Initiate at the base station a Unique Challenge-Response Procedure on the f-csch. Verify the Unique Challenge-Response Procedure fails with an AUTHU mismatch. Minimum Standard

116.3.5

12The mobile station shall comply with the following steps: f, k, n, p, r, t. 13The base station shall comply with the following steps: f, l, p, r, t.

146.4 156.4.1

Activating Voice Privacy on Call Setup Definition

16This test verifies that Voice Privacy can be activated at call setup by the mobile station 17subscriber.

186.4.2

Traceability:

19(see [4])

202.3.12.3 212.6.4.1.6 222.7.1.3.2.4 232.7.1.3.2.5 242.7.3 253.3.3 263.6.4.1.5 273.6.4.3 283.6.4.4 293.7.4 306.4.3
31None

(MS) Voice Privacy (MS) Long Code Transition Request Processing Origination Message Page Response Message (Mobile Station) Orders (Base Station) Voice Privacy (Base Station) Long Code Transition Request Processing Traffic Channel Substate Release Substate (Base Station) Orders

Call Flow Example(s)

1 16.4.4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
a. b. c. d. e. f. g. h. i. j. k. Method of Measurement

3GPP2 C.S0044-A v1.0

Connect the base station and mobile station as shown in Annex A Figure A-1. Ensure authentication is enabled. Verify the AUTH field of the Access Parameters Message is set to 01 or the ANSI-41 RAND Message is being transmitted. Power on the mobile station. Enable Voice Privacy in the mobile station and configure the base station to use voice privacy. Setup a mobile station originated call, and verify in the Origination Message the Voice Privacy Mode Indicator (PM) is set to '1'. Instruct the base station to send a Long Code Transition Request Order (ORDQ='00000001') on the f-dsch. Verify the mobile station responds with a Long Code Transition Response Order (ORDQ='00000011') If supported on the user interface, verify the mobile station indicates to the user that Voice Privacy is active. Verify that correct user data is received in both directions. End the call. Setup a mobile station terminated call, and verify in the Page Response Message the voice privacy indicator (PM) is set to 1 then repeat steps f through j. Minimum Standard

206.4.5

21The mobile station shall comply with the following steps: e, g, h, i, k. 22The base station shall comply with the following steps: b, i.

236.5 246.5.1

Activating Voice Privacy at the Mobile Station When a Call Is Active Definition

25This test verifies that Voice Privacy can be activated at the mobile station when a call is active.

266.5.2

Traceability

27(see [4])

282.3.12.3 292.6.4.1.6 302.7.1.3.2.4 312.7.1.3.2.5 322.7.3 333.3.3

(Mobile Station) Voice Privacy Long Code Transition Request Processing Origination Message Page Response Message (Mobile Station) Orders (Base Station) Voice Privacy

13GPP2 C.S0044-A v1.0 13.6.4.1.5 23.6.4.3.1 33.6.4.4 43.7.4 56.5.3

6None

(Base Station) Long Code Transition Request Processing Traffic Channel Substate Release Substate (Base Station) Orders

Call Flow Example(s)

76.5.4 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
a. b. c. d. e. f. g. h. i. j. k.

Method of Measurement Connect the base station and mobile station as shown in Annex A Figure A-1. Configure the base station to use Voice Privacy. Ensure authentication is enabled. Verify the AUTH field of the Access Parameters Message is set to 01 or the ANSI-41 RAND Message is being transmitted. Power on the mobile station. Setup a mobile station originated call. Enable voice privacy at the mobile station. Verify the mobile station sends a Long Code Transition Request Order with ORDQ set to 00000001. Verify the base station responds by sending a Long Code Transition Request Order with ORDQ set to 00000001. Verify the mobile station responds with a Long Code Transition Response Order (ORDQ='00000011'). If supported on the user interface, verify the mobile station indicates Voice Privacy is active. Verify that correct user data is received in both directions. End the call. Minimum Standard

246.5.5

25The mobile station shall comply with the following steps: f, h, i, j. 26The base station shall comply with the following steps: c, g, j.

276.6 286.6.1

Signaling Message Encryption on Forward Traffic Channel Definition

29This test verifies that Signaling Message Encryption on f-dsch is performed correctly.

306.6.2

Traceability

31(see [4])

322.3.12.2

(Mobile Station) Signaling Message Encryption

1 12.7.4.4 23.3.2 33.7.2.3.2.8 43.7.3.3.2.3 53.7.5.3 66.6.3

7None

3GPP2 C.S0044-A v1.0 (Mobile Station) Calling Party Number (Base Station) Encryption Channel Assignment Message (f-csch) Alert With Information Message (f-dsch) (Base Station) Calling Party Number Call Flow Example(s)

86.6.4 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
i. j. k. a. b. c. d. e. f. g. h.

Method of Measurement Connect the base station and mobile station as shown in Annex A Figure A-1. Activate the Calling Party Number (CPN) feature for the mobile station subscriber. Ensure authentication is enabled. Verify the AUTH field of the Access Parameters Message is set to 01 or the ANSI-41 RAND Message is being transmitted. Power on the mobile station. Enable Signaling Message Encryption on the base station. Setup a mobile station terminated call. Verify the ENCRYPT_MODE field is set to '01' or 10 in the transmitted Channel Assignment Message or Extended Channel Assignment Message. Verify the following: 1. Required fields in the appropriate messages are encrypted and can be correctly decrypted. For example, certain fields of the Alert With Information Message will be encrypted; but verification can be done on other messages as well. 2. The ENCRYPTION field in these messages is set to the same value as the ENCRYPT_MODE field received in the Channel Assignment Message or Extended Channel Assignment Message. Verify the CPN is displayed on the mobile station during the alerting state. Verify that correct user data is received in both directions. End the call. Minimum Standard

286.6.5

29The mobile station shall comply with the following steps: h, i, j. 30The base station shall comply with the following steps: c, g, h, j.

316.7 326.7.1

Signaling Message Encryption on Reverse Traffic Channel Definition

33This test verifies that Signaling Message Encryption on the r-dsch is performed correctly.

13GPP2 C.S0044-A v1.0 16.7.2

Traceability (Mobile Station) Signaling Message Encryption Send Burst DTMF Message (Base Station) Encryption Channel Assignment Message (f-csch)

2(see [4]) 32.3.12.2 42.7.2.3.2.7 53.3.2 63.7.2.3.2.8

76.7.3
8None

Call Flow Example(s)

96.7.4 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
i. j. a. b. c. d. e. f. g. h.

Method of Measurement Connect the base station and mobile station as shown in Annex A Figure A-1. Ensure authentication is enabled. Verify the AUTH field of the Access Parameters Message is set to 01 or the ANSI-41 RAND Message is being transmitted. Power on the mobile station. Instruct the mobile station to send a Send Burst DTMF Message. Enable Signaling Message Encryption on the base station. Setup a mobile station call to a voice mail system or a paging system. Verify the ENCRYPT_MODE field is set to '01' or 10 in the transmitted Channel Assignment Message or Extended Channel Assignment Message. Verify the following: 1. Required fields in the appropriate messages are encrypted and can be correctly decrypted. For example, certain fields of the Burst DTMF Message will be encrypted; but verification can be done on other messages as well. 2. The ENCRYPTION field in these messages is set to the same value as the ENCRYPT_MODE field received in the Channel Assignment Message or Extended Channel Assignment Message. Enter the appropriate pin code as burst DTMF tones. Verify that either the voice mail system recognizes the DTMF tones and plays the message back, or that the paging system accepts the pin and sends out the page. Alternative procedures may be used to verify correct behavior. End the call. Minimum Standard

k.

316.7.5

32The mobile station shall comply with the following step: h. 33The base station shall comply with the following steps: b, g, h, j.

1 16.8 26.8.1

3GPP2 C.S0044-A v1.0 Hard Handoffs between Base Stations with Signaling Message Encryption Active Definition

3This test verifies that when Signaling Message Encryption is used, the new base station activates 4correct encryption upon handoff.

56.8.2

Traceability

6(see [4])

72.3.12.2 82.6.6.2.8 92.7.4.4 103.3.2 113.6.6.2.2.2 123.6.6.2.2.10 133.6.6.2.2.11 143.7.2.3.2.8 153.7.3.3.2.14 163.7.3.3.2.17 173.7.3.3.2.31 183.7.3.3.2.36 193.7.5.3 206.8.3
21None

(Mobile Station) Signaling Message Encryption CDMA-to-CDMA Hard Handoff (Mobile Station) Calling Party Number. (Base Station) Encryption Extended Handoff Direction Message (call processing) General Handoff Direction Message (call processing) Universal Handoff Direction Message (call processing) Channel Assignment Message (f-csch) Flash With Information Message (f-dsch) Extended Handoff Direction Message (f-dsch) General Handoff Direction Message (f-dsch) Universal Handoff Direction Message (f-dsch) (Base Station) Calling Party Number

Call Flow Example(s)

226.8.4 23 24 25 26 27 28 29 30 31 32
a. b. c. d. e. f. g. h.

Method of Measurement Connect the base station and mobile station as shown in Annex A Figure A-5. Activate Call Waiting and Caller ID on base station 2. Ensure authentication is enabled. Verify the AUTH field of the Access Parameters Message is set to 01 or the ANSI-41 RAND Message is being transmitted. Power on the mobile station. Enable Signaling Message Encryption on both base stations. Setup a mobile station originated call. Verify ENCRYPT_MODE field is set to '01' or 10 in the transmitted Channel Assignment Message or Extended Channel Assignment Message. Verify user data in both directions.

10

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

m. n. o. i. j. Cause a hard handoff from base station 1 to base station 2. Verify ENCRYPT_MODE field is set to '01 or 10 in the transmitted Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message. Setup another call to the mobile station and listen for the Call Waiting tone. Verify the following: 1. Required fields in the appropriate messages are encrypted and can be correctly decrypted. For example, certain fields of the Flash With Information Message will be encrypted; but verification can be done on other messages as well. 2. The ENCRYPTION field in these messages is set to the same value as the ENCRYPT_MODE field received in the Channel Assignment Message or Extended Channel Assignment Message. Verify that Calling Party Number (CPN) information is displayed on the mobile station during alerting state. Verify user data in both directions. End the call. Minimum Standard

k. l.

176.8.5

18The mobile station shall comply with the following steps: h, l, m, n. 19The base station shall comply with the following steps: c, g, h, j, l, n.

206.9 216.9.1

Authentication upon Originations Definition

22This test verifies the mobile station can successfully Authenticate upon an origination.

236.9.2

Traceability

24(see [4])

252.3.12.1.5 262.7.1.3.2.6 272.7.2.3.2.2 283.7.2.3.2.10 293.7.2.3.2.11 303.7.3.3.2.2 313.7.3.3.2.13 326.9.3

33None

Updating the Shared Secret Data (SSD) Authentication Challenge Response Message Authentication Challenge Response Message (r-dsch) Authentication Challenge Message (f-csch) SSD Update Message (f-csch) Authentication Challenge Message (f-dsch) SSD Update Message (f-dsch)

Call Flow Example(s)

11

1 16.9.4 2 3 4 5 6 7 8 9 10 11 12 13 14 15
a. b. c. d. e. f. g. h. i. j. k. l. m. n. Method of Measurement

3GPP2 C.S0044-A v1.0

Connect the base station and mobile station as shown in Annex A Figure A-5. Power on the mobile station. Initialize the A-Key to the same value in both the mobile station and base station. Instruct the base station to initiate a Shared Secret Data update on the f/r-csch. Verify the SSD Update was successful. Setup a mobile station originated call (seven digits). Verify user data in both directions and that authentication is successful. End the call. Setup a mobile station originated call (three digits such as *73). Verify user data in both directions and that authentication is successful. End the call. Setup a mobile station originated call (four digits such as *123). Verify user data in both directions and that authentication is successful. End the call. Minimum Standard

166.9.5

17The mobile station shall comply with the following steps: e, g, j, and m. 18The base station shall comply with the following steps: e, g, j, and m.

196.10 Hard Handoff from CDMA to Analog with Signaling Message Encryption Active 206.10.1 Definition
21This test verifies that when Signaling Message Encryption is used, the new base station activates 22Analog Signaling Message Encryption upon handoff.

236.10.2 Traceability
24(see [4])

252.3.12.2 262.6.6.2.9 272.7.4.4 283.3.2 293.6.4.3 303.7.2.3.2.8 313.7.3.3.2.3

(Mobile Station) Signaling Message Encryption CDMA-Analog HO (Mobile Station) Calling Party Number (Base Station) Encryption Traffic Channel Substate Channel Assignment Message (f-csch) Alert with Information Message (f-dsch)

12

13GPP2 C.S0044-A v1.0 13.7.3.3.2.6 23.7.5.3

Analog Handoff Direction Message (Base Station) Calling Party Number.

36.10.3 Call Flow Example(s)

4None

56.10.4 Method of Measurement 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

a. b. c. d. e. f. g. h. i. j. k. l. m. n. o. Connect the base station and mobile station as shown in Annex A Figure A-5. Activate Call Waiting and Caller ID on Base station 2. Ensure authentication is enabled. Verify the AUTH field of the Access Parameters Message is set to 01 or the ANSI-41 RAND Message is being transmitted. Power on the mobile station. Enable Signaling Message Encryption on both base stations. Setup a mobile station originated call. Verify ENCRYPT_MODE field is set to '01' or 10 in the Channel Assignment Message or Extended Channel Assignment Message transmitted. Verify that correct user data is received in both directions. Cause a CDMA to analog hard handoff from base station 1 to base station 2. Verify ENCRYPT_MODE='01' and MEM=1 in the Analog Handoff Direction Message. Setup another call to the mobile station, and listen for the Call Waiting tone. Verify base station 2 sends an encrypted Alert with Information Message (analog). Verify that the Calling Party Number (CPN) information is displayed on the mobile station during the alerting state. Verify that correct user data is received in both directions. End the call.

246.10.5 Minimum Standard

25The mobile station shall comply with the following steps: h, m, n. 26The base station shall comply with the following steps: c, g, h, j, l, n.

13

1
1No text. 2

3GPP2 C.S0044-A v1.0

14

13GPP2 C.S0044-A v1.0 17 27.1 37.1.1

SERVICE REDIRECTION TEST CASES

Global Service Redirection between Band Classes Definition

4This test verifies that when a mobile station receives a Global Service Redirection Message 5directing it to another band class, the mobile station acquires the appropriate system. 6When testing Global Service Redirection, the base station must not broadcast an Extended 7Global Service Redirection on any overhead channel.

87.1.2

Traceability

9(see [4])

102.6.1.1.2 112.6.2.2 122.6.2.2.6 133.7.2.3.2.1

143.7.2.3.2.18

System Selection Using Current Redirection Criteria Response to Overhead Information Operation Global Service Redirection Message System Parameters Message Global Service Redirection Message

157.1.3
16None

Call Flow Example(s)

177.1.4 18 19 20 21
22

Method of Measurement Connect the mobile station to the base station as shown in Figure A-5. For this test case, base station 1 and base station 2 are in different band classes. Verify the mobile station is operating in the Mobile Station Idle State on base station 1. Ensure that the base station sends a Global Service Redirection Message with:

a. b. c.

1
Field REDIRECT_ACCOLC EXCL_P_REV_MS RECORD_TYPE BAND_CLASS EXPECTED_SID EXPECTED_NID NUM_CHAN CDMA_CHAN Value ACCOLCp 0 00000010 Target Band Class Target SID Target NID

3GPP2 C.S0044-A v1.0

Number of Channels Target Channel(s)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

d. e. f. g. h.

Verify the mobile station enters the System Determination Substate of the Mobile Station Initialization State and acquires the system to which it was redirected. Setup a mobile station originated call. Verify user traffic in both directions. End the call. Repeat steps c through f with the mobile station operating in the Mobile Station Idle State on base station 2. Repeat steps b and c with the mobile station operating in the Mobile Station Idle State on base station 1 setting EXCL_P_REV_MS = 1 in the Global Service Redirection Message. Verify the following: 1. If MOB_P_REV is less than six, verify the mobile station enters the System Determination Substate of the Mobile Station Initialization State and acquires the system to which it was redirected. If MOB_P_REV is greater than or equal to six, verify the mobile station remains in the Mobile Station Idle State on the current system.

i.

2.

167.1.5

Minimum Standard

17The mobile station shall comply with steps d, e, and i.

187.2 197.2.1

Global Service Redirection between CDMA and a Non-CDMA System Definition

20This test verifies that when a mobile station receives a Global Service Redirection Message 21directing it from CDMA to a Non-CDMA system, the mobile station acquires that system. The 22mobile station should only be redirected to Non-CDMA systems it supports. An example would be 23an analog system defined in [21]. 24When testing Global Service Redirection, the base station must not broadcast an Extended 25Global Service Redirection on any overhead channel.

13GPP2 C.S0044-A v1.0 17.2.2

Traceability

2(see [4])

32.6.1.1.2 42.6.2.2 52.6.2.2.6 63.7.2.3.2.1

73.7.2.3.2.18

System Selection Using Current Redirection Criteria Response to Overhead Information Operation Global Service Redirection Message System Parameters Message Global Service Redirection Message

87.2.3
9None

Call Flow Example(s)

107.2.4 11 12 13 14 15 16
a.

Method of Measurement Connect the mobile station to the base station as shown in Figure A-5. For this test case, base station 1 is a CDMA base station and base station 2 is a Non-CDMA base station. Ensure the mobile station is operating in the Mobile Station Idle State on base station 1. Send a Global Service Redirection Message from the current base station directing the mobile station to the non-CDMA base station with the following parameters: Field REDIRECT_ACCOLC EXCL_P_REV_MS RECORD_TYPE Value ACCOLCp 0 '00000001' [North American Amps] '00000011' [TACS] '00000100' [JTACS] 00000101 (DS-41) If RECORD_TYPE=00000001, the base station shall include the following fields EXPECTED_SID IGNORE_CDMA SYS_ORDERING MAX_REDIRECT_DELAY Target SID 0 000 00000

b. c.

17

18 19

d.

Verify the mobile station enters the System Determination Substate of the Mobile Station Initialization State and acquires the system to which it was redirected.

1 1 2 3 4 5 6 7 8 9 10 11 127.2.5
e. f. g.

3GPP2 C.S0044-A v1.0 Setup a mobile station originated call. Verify user traffic in both directions. End the call. Repeat steps b and c with the mobile station operating in the Mobile Station Idle State on base station 1 setting EXCL_P_REV_MS = 1 in the Global Service Redirection Message. Verify the following: 1. If MOB_P_REV is less than six, verify the mobile station enters the System Determination Substate of the Mobile Station Initialization State and acquires the system to which it was redirected. If MOB_P_REV is greater than or equal to six, verify the mobile station remains in the Mobile Station Idle State on the current system.

h.

2.

Minimum Standard

13The mobile station shall comply with steps d, e, and h.

147.3 157.3.1

Global Service Redirection between Channels in the Same Band Class Definition

16This test verifies that when a mobile station receives a Global Service Redirection Message 17directing it to a different channel in the same band class, the mobile station acquires the 18appropriate system. 19When testing Global Service Redirection, the base station must not broadcast an Extended 20Global Service Redirection on any overhead channel.

217.3.2

Traceability

22(see [4])

232.6.1.1.2 242.6.2.2 252.6.2.2.6 263.7.2.3.2.1 273.7.2.3.2.18 287.3.3

29None

System Selection Using Current Redirection Criteria Response to Overhead Information Operation Global Service Redirection Message System Parameters Message Global Service Redirection Message

Call Flow Example(s)

307.3.4 31 32 33 34
a.

Method of Measurement Connect the mobile station to the base station as shown in Figure A-5. For this test case, base station 1 and base station 2 are in the same band class with different CDMA channels. Verify the mobile station is operating in the Mobile Station Idle State on base station 1.

b.

13GPP2 C.S0044-A v1.0 1

2

c.

Send a Global Service Redirection Message from the current base station with:

Field REDIRECT_ACCOLC EXCL_P_REV_MS RECORD_TYPE BAND_CLASS EXPECTED_SID EXPECTED_NID NUM_CHAN CDMA_CHAN

3

Value ACCOLCp 0 00000010 Target Band Class Target SID Target NID Number of Channels Target Channel(s)

4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

d. e. f. g. h.

Verify the mobile station enters the System Determination Substate of the Mobile Station Initialization State and acquires the system to which it was redirected. Setup a mobile station originated call. Verify user traffic in both directions. End the call. Remove the channel for base station 2 from the mobiles stations preferred roaming list and repeat steps b through f. Repeat steps b and c with the mobile station operating in the Mobile Station Idle State on base station 1 setting EXCL_P_REV_MS = 1 in the Global Service Redirection Message. Verify the following: 1. If MOB_P_REV is less than six, verify the mobile station enters the System Determination Substate of the Mobile Station Initialization State and acquires the system to which it was redirected. If MOB_P_REV is greater than or equal to six, verify the mobile station remains in the Mobile Station Idle State on the current system.

i.

2.

197.3.5

Minimum Standard

20The mobile station shall comply with steps d, e, and i.

217.4 227.4.1

Service Redirection between Band Classes Definition

23This test verifies Network Directed System Selection (NDSS) functions correctly. This test verifies 24that a mobile station is capable of being redirected between band classes when the Service

3GPP2 C.S0044-A v1.0

1Redirection Message is sent on the f-csch or on the f-dsch prior to user traffic being transmitted 2and the call completes on the new system without user interaction.

37.4.2

Traceability

4(see [4])

52.6.1.1.2 62.6.2.4 72.6.3.5 83.6.2.3 93.7.2.3.2.16 103.7.3.3.2.23 117.4.3

12None

System Selection Using Current Redirection Criteria Mobile Station Order and Message Processing Operation Mobile Station Origination Attempt Substate Mobile Station Directed Messages Service Redirection Message {f-csch} Service Redirection Message {f-dsch}

Call Flow Example(s)

137.4.4 14 15 16 17 18 19
a. b. c. d.

Method of Measurement Connect the mobile station to the base station as shown in Figure A-5. For this test case, base station 1 and base station 2 are in different band classes. Verify the mobile station is operating in the Mobile Station Idle State on base station 1. Instruct the mobile station to send an Origination Message to the base station. Instruct the base station to send a Service Redirection Message with the following information to the mobile station on the f-csch or on the f-dsch. Field REDIRECT_TYPE RECORD_TYPE BAND_CLASS EXPECTED_SID EXPECTED_NID NUM_CHAN CDMA_CHAN Value 1 (NDSS redirection) 00000010 Target Band Class Target SID Target NID Number of Channels Target Channel(s)

20

21 22 23 24 25 2

e. f. g.

Verify the mobile station acquires the target base station and the call completes without additional user interaction and user traffic is present. End the call. Repeat steps c through f with the mobile station operating in the Idle State on base station 2.

13GPP2 C.S0044-A v1.0 17.4.5

Minimum Standard

2The mobile station shall comply with steps e and g.

37.5 47.5.1

Service Redirection between CDMA and a Non-CDMA System Definition

5This test verifies that a mobile station is capable of being redirected from a CDMA system to a 6non-CDMA system when the Service Redirection Message is sent on the f-csch or on the f-dsch 7prior to user traffic being transmitted, and the call completes on the new system without user 8interaction. The mobile station should only be redirected to Non-CDMA systems it supports. An 9example of a non-CDMA system is an analog system defined in [21].

107.5.2

Traceability

11(see [4])

122.6.1.1.2 132.6.2.4 142.6.3.5 153.6.2.3 163.7.2.3.2.16 173.7.3.3.2.23 187.5.3

19None

System Selection Using Current Redirection Criteria Mobile Station Order and Message Processing Operation Mobile Station Origination Attempt Substate Mobile Station Directed Messages Service Redirection Message {f-csch} Service Redirection Message {f-dsch}

Call Flow Example(s)

207.5.4 21 22 23 24 25 26 27
28

Method of Measurement Connect the mobile station to the base station as shown in Figure A-5. For this test case, base station 1 is a CDMA base station and base station 2 is a Non-CDMA base station. Ensure the mobile station is operating in the Mobile Station Idle State on base station 1. Instruct the mobile station to send an Origination Message to the base station. Instruct the base station to send a Service Redirection Message with the following information to the mobile station on the f-csch or on the f-dsch.

a.

b. c. d.

1
Field RETURN_IF_FAIL REDIRECT_TYPE RECORD_TYPE Value 0 1 (NDSS redirection) '00000001' [North American Amps] '00000011' [TACS] '00000100' [JTACS] 00000101 (DS-41) If RECORD_TYPE=00000001, the base station shall include the following fields EXPECTED_SID IGNORE_CDMA SYS_ORDERING
1

3GPP2 C.S0044-A v1.0

Target SID 0 000

2 3 4 5 6 7 8 9 10 11

e. f. g. h. i. j.

Verify the mobile station acquires the target base station and the call completes without additional user interaction and user traffic is present. End the call. For RECORD_TYPE=00000001, repeat steps a through e setting IGNORE_CDMA = 1 in the Service Redirection Message: Send the CDMA Capability Message from base station 2 indicating CDMA is available (i. e. CDMA_AVAIL set to 1). End the call. Verify the mobile station remains in the Idle State on the non-CDMA system and does not attempt to re-acquire CDMA. Minimum Standard

127.5.5

13The mobile station shall comply with steps e, g and j.

147.6 157.6.1

Service Redirection between Channels in the Same Band Class Definition

16This test verifies Network Directed System Selection (NDSS) functions correctly. This test verifies 17that a mobile station is capable of being redirected between channels in the same band class 18when the Service Redirection Message is sent on the f-csch or on the f-dsch prior to user traffic 19being transmitted and the call completes on the new system without additional user interaction.

13GPP2 C.S0044-A v1.0 17.6.2

Traceability

2(see [4])

32.6.1.1.2 42.6.2.4 52.6.3.5 63.6.2.3 73.7.2.3.2.16 83.7.3.3.2.23 97.6.3

10None

System Selection Using Current Redirection Criteria Mobile Station Order and Message Processing Operation Mobile Station Origination Attempt Substate Mobile Station Directed Messages Service Redirection Message {f-csch} Service Redirection Message {f-dsch}

Call Flow Example(s)

117.6.4 12 13 14 15 16 17 18
a.

Method of Measurement Connect the mobile station to the base station as shown in Figure A-5. For this test case, base station 1 and base station 2 have different CDMA channels in the same band class. Verify the mobile station is operating in the Mobile Station Idle State on base station 1. Instruct the mobile station to send an Origination Message to the base station. Instruct the base station to send a Service Redirection Message with the following information to the mobile station on the f-csch or on the f-dsch. Field RETURN_IF_FAIL REDIRECT_TYPE RECORD_TYPE EXPECTED_SID EXPECTED_NID NUM_CHAN CDMA_CHAN Value 0 1 (NDSS redirection) 00000010 Target SID Target NID Number of Channels Target Channel(s)

b. c. d.

19 20 21 22 23 24 25

e. f. g. h.

Verify the mobile station acquires the target base station and the call completes without additional user interaction and user traffic is present. End the call. Repeat steps c through f with the mobile station operating in the Idle State on base station 2. Repeat steps b through d ensuring the mobile station cannot re-acquire base station 2 and setting RETURN_IF_FAIL = 1 in the Service Redirection Message:

1 1 2
i.

3GPP2 C.S0044-A v1.0 Verify the mobile station returns to base station 1 after failing to acquire base station 2. The call may or may not complete depending on infrastructure implementation. Minimum Standard

37.6.5

4The mobile station shall comply with steps e, g, and i.

57.7 67.7.1

Extended Global Service Redirection between Band Classes Definition

7This test verifies that when a mobile station receives an Extended Global Service Redirection 8Message directing it to another band class, the mobile station acquires the appropriate system.

97.7.2

Traceability

10(see [4])

112.6.1.1.2 122.6.2.2 132.6.2.2.11 143.7.2.3.2.1 153.7.2.3.2.27 163.7.2.3.2.31 177.7.3

18None

System Selection Using Current Redirection Criteria Response to Overhead Information Operation Extended Global Service Redirection Message System Parameters Message Extended Global Service Redirection Message MC-RR Parameters Message

Call Flow Example(s)

197.7.4 20 21 22 23 24
a. b. c.

Method of Measurement Connect the mobile station to the base station as shown in Figure A-5. For this test case, base station 1 and base station 2 are in different band classes. Verify the mobile station is operating in the Mobile Station Idle State on base station 1. Send an Extended Global Service Redirection Message from the current base station with:

10

13GPP2 C.S0044-A v1.0

Field REDIRECT_ACCOLC REDIRECT_P_REV_INCL RECORD_TYPE BAND_CLASS EXPECTED_SID EXPECTED_NID NUM_CHAN CDMA_CHAN Value ACCOLCp 0 00000010 Target Band Class Target SID Target NID Number of Channels Target Channel(s)

1 2 3 4 5 6

d. e. f. g.

Verify the mobile station enters the System Determination Substate of the Mobile Station Initialization State and acquires the system to which it was redirected. Setup a mobile station originated call. Verify user traffic in both directions. End the call. Repeat steps c through f with the mobile station operating in the Mobile Station Idle State on base station 2. Minimum Standard

77.7.5

8The mobile station shall comply with steps d, e and g.

97.8 107.8.1

Extended Global Service Redirection between CDMA and a Non-CDMA System Definition

11This test verifies that when a mobile station receives an Extended Global Service Redirection 12Message directing it from CDMA to a Non-CDMA system, the mobile station acquires that 13system. The mobile station should only be redirected to Non-CDMA systems it supports. An 14example would be an analog system defined in [21].

157.8.2

Traceability

16(see [4])

172.6.1.1.2 182.6.2.2 192.6.2.2.11 203.7.2.3.2.1 213.7.2.3.2.27 223.7.2.3.2.31

System Selection Using Current Redirection Criteria Response to Overhead Information Operation Extended Global Service Redirection Message System Parameters Message Extended Global Service Redirection Message MC-RR Parameters Message

11

1 17.8.3
2None

3GPP2 C.S0044-A v1.0 Call Flow Example(s)

37.8.4 4 5 6 7 8 9 10
a.

Method of Measurement Connect the mobile station to the base station as shown in Figure A-5. For this test case, base station 1 is a CDMA base station and base station 2 is a Non-CDMA base station. Ensure the mobile station is operating in the Mobile Station Idle State on base station 1. Send an Extended Global Service Redirection Message from the current base station directing the mobile station to the non-CDMA base station with the following parameters:

b. c.

Field REDIRECT_ACCOLC REDIRECT_P_REV_INCL RECORD_TYPE

Value ACCOLCp 0 '00000001' [North American Amps] '00000011' [TACS] '00000100' [JTACS] 00000101 (DS-41)

If RECORD_TYPE=00000001, the base station shall include the following fields EXPECTED_SID IGNORE_CDMA SYS_ORDERING MAX_REDIRECT_DELAY Target SID 0 000 00000

12 13 14 15

d. e. f.

Verify the mobile station enters the System Determination Substate of the Mobile Station Initialization State and acquires the system to which it was redirected. Setup a mobile station originated call. Verify user traffic in both directions. End the call. Minimum Standard

167.8.5

17The mobile station shall comply with steps d and e

12

13GPP2 C.S0044-A v1.0 17.9 27.9.1

Extended Global Service Redirection between Channels in the Same Band Class Definition

3This test verifies that when a mobile station receives an Extended Global Service Redirection 4Message directing it to a different channel in the same band class, the mobile station acquires the 5appropriate system.

67.9.2

Traceability

7(see [4])

82.6.1.1.2 92.6.2.2 102.6.2.2.11 113.7.2.3.2.1 123.7.2.3.2.27 133.7.2.3.2.31 147.9.3

15None

System Selection Using Current Redirection Criteria Response to Overhead Information Operation Extended Global Service Redirection Message System Parameters Message Extended Global Service Redirection Message MC-RR Parameters Message

Call Flow Example(s)

167.9.4 17 18 19 20 21 22
a.

Method of Measurement Connect the mobile station to the base station as shown in Figure A-5. For this test case, base station 1 and base station 2 are in the same band class with different CDMA channels. Verify the mobile station is operating in the Mobile Station Idle State on base station 1. Send an Extended Global Service Redirection Message from the current base station with: Field REDIRECT_ACCOLC REDIRECT_P_REV_INCL RECORD_TYPE EXPECTED_SID EXPECTED_NID NUM_CHAN CDMA_CHAN Value ACCOLCp 0 00000010 Target SID Target NID Number of Channels Target Channel(s)

b. c.

23 24 25 2

d. e.

Verify the mobile station enters the System Determination Substate of the Mobile Station Initialization State and acquires the system to which it was redirected. Setup a mobile station originated call. Verify user traffic in both directions.

13

1 1 2 3
f. g. End the call.

3GPP2 C.S0044-A v1.0

Remove the channel for base station 2 from the mobile stations preferred roaming list and repeat steps b through f. Minimum Standard

47.9.5
6

5The mobile station shall comply with steps d and e.

14

13GPP2 C.S0044-A v1.0 18 28.1

4 5

SHORT MESSAGE SERVICE

Mobile Station Terminated SMS Tests

3Unless otherwise noted, the following conditions apply for all tests in this section:

Mobile station is capable of receiving short messages. The short message feature for the mobile station is activated.

6 Base station has Power-up registration enabled by setting POWER-UP_REG = 1 in the 7System Parameters Message or the ANSI-41 System Parameters Message. 8

Transport Layer messages shall include the Bearer Reply Option. Common Channel SMS Delivery Definition

98.1.1 108.1.1.1

11This test verifies that a short message can be sent to a mobile station in the Mobile Station Idle 12State.

138.1.1.2
14(see [13])

Traceability

152.4.1.1.1.1 168.1.1.3
17None

Mobile SMS Message Termination

Call Flow Example(s)

188.1.1.4 19 20 21 22 23 24 25 26 27
28

Method of Measurement Delete all outstanding short messages in the network for the mobile station. Create a short message in the Message Center for the mobile station. Ensure that the short message length is less than the maximum allowed size on the Paging Channel or Forward Common Control Channel so that it can be sent to the mobile station using the Paging Channel or Forward Common Control Channel9. Power on the mobile station and wait until it is in the Mobile Station Idle State. Instruct the network to send the short message to the mobile station. Verify the base station sends a Data Burst Message to the mobile station with the following field settings:

a. b.

c. d. e.

Field MSG_NUMBER

Value 1 (00000001)

29 The max size for common channel SMS is base station implementation dependent. 3
1

1
BURST_TYPE NUM_MSGS NUM_FIELDS
1

3GPP2 C.S0044-A v1.0 3 (000011) 1 (00000001) Greater than 0

2 3 4 5 6 7 8

f.

Upon receiving the Data Burst Message at the mobile station, verify the following: 1. 2. The mobile station alerts the user for the incoming short message and correctly displays the received short message, when selected. The mobile station transmits Data Burst Message on the Access Channel, Enhanced Access Channel or Reverse Common Control Channel to acknowledge the short message, indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = 00).

98.1.1.5

Minimum Standard

10The mobile station shall comply with step f. The base station shall comply with step e.

118.1.2 128.1.2.1

Traffic Channel SMS Delivery Definition

13This test verifies that a short message, with length exceeding the maximum allowable length 14(configurable by the network) for Paging Channel or Forward Common Control Channel transport, 15is delivered to the mobile station over the Traffic Channel.

168.1.2.2
17(see [13])

Traceability

182.4.1.1.2.2 192.4.2.1.2 208.1.2.3

21None

Mobile SMS Message Termination Base Station Traffic Channel Procedures

Call Flow Example(s)

228.1.2.4 23 24 25 26 27 28 29
a. b.

Method of Measurement Delete all outstanding short messages in the network for the mobile station. Create a short message in the Message Center for the mobile station. Ensure that the short message length is greater than the maximum length supported on the Paging Channel or Forward Common Control Channel . Power on the mobile station and wait until it is in the Mobile Station Idle State. Instruct the network to send the short message to the mobile station. Verify the following:

c. d.

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7

8

1. 2. 3.

The base station does not send a Data Burst Message to the mobile station on the paging channel or Forward Common Control Channel. The base station sends a General Page Message with either service option 6 or service option 14. After the mobile station enters the Conversation Substate, the base station sends a Data Burst Message to the mobile station with the following field settings:

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

9 10 11 12 13 14

e.

Upon receiving the Data Burst Message at the mobile station, verify the following: 1. 2. The mobile station alerts the user for the incoming short message and correctly displays the received short message, when selected. The mobile station transmits a Data Burst Message on the Reverse Traffic Channel to acknowledge the short message, indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = 00).

158.1.2.5

Minimum Standard

16The mobile station shall comply with step e. The base station shall comply with step d.

178.1.3 188.1.3.1

Traffic Channel SMS Delivery while in Conversation Definition

19This test verifies a short message can be sent to a mobile station when it is already in the 20Conversation Substate.

218.1.3.2
22(see [13])

Traceability

232.4.1.1.2.2 242.4.2.1.2 252.4.2.1.2.4 268.1.3.3

27None

Mobile SMS Message Termination Base Station Traffic Channel Procedures Mobile Station Message Termination in the Conversation Substate

Call Flow Example(s)

1 18.1.3.4 2 3 4 5 6 7 8
9

3GPP2 C.S0044-A v1.0 Method of Measurement Delete all outstanding short messages in the network for the mobile station. Setup a mobile station originated call. While the mobile station is in the Conversation Substate, create a short message in the Message Center for the mobile station. Instruct the network to send the short message to the mobile station. Verify the base station sends a Data Burst Message to the mobile station, with the following field settings:

a. b. c. d. e.

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

10 11 12 13 14 15 16

f.

Upon receiving the Data Burst Message at the mobile station, verify the following: 1. 2. The mobile station alerts the user for the incoming short message and correctly displays the received short message, when selected. The mobile station transmits a Data Burst Message on the Reverse Traffic Channel to acknowledge the receipt of the short message and indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = 00).

178.1.3.5

Minimum Standard

18The mobile station shall comply with step f. The base station shall comply with step e.

198.1.4 208.1.4.1

Delivery of Maximum Length Message Definition

21This test verifies the SMS transport layer capability to send to a mobile station a short message of 22the maximum size the maximum size is the lesser of the maximum allowable length of the 23message center and the maximum length specified by the mobile station manufacturer. The test 24verifies delivery of the maximum length short message on the Traffic Channel.

258.1.4.2
26(see [13])

Traceability

272.4.2.1.2 283.4.2.1

Base Station Traffic Channel Procedures SMS Point-to-Point Message

13GPP2 C.S0044-A v1.0 13.4.3.5 28.1.4.3

3None

Bearer Reply Option Call Flow Example(s)

48.1.4.4 5 6 7 8 9 10
11

Method of Measurement Clear all short messages stored in the mobile station. Delete all outstanding short messages in the Network for the mobile station. Create in the Message Center a maximum size short message for the mobile station. Instruct the network to send the short message to the mobile station. Verify the base station sends a Data Burst Message to the mobile station on the traffic channel, with the following field settings:

a. b. c. d. e.

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

12 13 14 15 16 17 18

f.

Upon receiving Data Burst Message at the mobile station, verify the following: 1. 2. The mobile station alerts the user for the incoming short message and correctly displays the received short message, when selected. The mobile station transmits a Data Burst Message on the Reverse Traffic Channel to acknowledge receipt of the short message and indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = 00).

198.1.4.5

Minimum Standard

20The mobile station shall comply with f. The base station shall comply with step e.

218.1.5 228.1.5.1

SMS Delivery Error - Mobile Station Short Message Buffer Full Definition

23This test verifies SMS transport layer acknowledgment capability by sending to the mobile station 24short messages until the mobile station short message buffer is full.

258.1.5.2
26(see [13])

Traceability

272.4.1.1.1.1 2

Mobile SMS Message Termination

1 12.4.2.1.1 23.4.2.1 33.4.3.6 48.1.5.3

5None

3GPP2 C.S0044-A v1.0 Common Channel Procedures SMS Point-to-Point Message Cause Codes Call Flow Example(s)

68.1.5.4 7 8 9 10 11 12 13
14

Method of Measurement Clear all short messages from the mobile station to ensure that the short message buffer is empty. Delete all outstanding short messages in the network for the mobile station. Create in the Message Center a short message for the mobile station. Instruct the network to send the short message to the mobile station. Verify the base station sends a Data Burst Message to the mobile station, with the following field settings:

a. b. c. d. e.

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

15 16 17 18 19 20 21
22

f.

Upon receiving the Data Burst Message, the mobile station shall transmit a Data Burst Message to acknowledge receipt of the short message and indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = 00). Repeat steps c through f until the mobile station short message buffer is full. Instruct the network to send one additional short message to the mobile station. Verify the base station sends a Data Burst Message to the mobile station, with the following field settings:

g. h. i.

Field MSG_NUMBER BURST_TYPE NUM_MSGS

Value 1 (00000001) 3 (000011) 1 (00000001)

13GPP2 C.S0044-A v1.0

NUM_FIELDS Greater than 0

1 2 3 4

j.

Upon receiving the Data Burst Message sent in step i, verify that the mobile station transmits a Data Burst Message on the Access Channel, Enhanced Access Channel or Reverse Common Control Channel to acknowledge the short message and indicating temporary error (with ERROR_CLASS = 10 and CAUSE_CODE=35. Minimum Standard

58.1.5.5

6The mobile station shall comply with step j. The base station shall comply with steps e and i.

78.1.6 88.1.6.1

Voice Mail Notification Definition

9Voice Mail Notification (VMN) notifies the subscriber of voice mail messages using the Voice Mail 10Notification teleservice and Short Message Service protocol. Notification can be a tone, light, or 11display, and is manufacturer dependent.

128.1.6.2
13(see [13])

Traceability

144.3.5

Voice Mail Notification (VMN)

154.5.12 Number of Messages 168.1.6.3

17None

Call Flow Example(s)

188.1.6.4 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
e. a. b. c. d.

Method of Measurement Configure the system as shown in Figure A-3. Power on the mobile station and wait until it is in the Mobile Station Idle State. Instruct the network to send a Voice Mail Notification (corresponds to an SMS Point-toPoint message) to the mobile station. Verify that the base station sends a Data Burst Message, with the BURST_TYPE field set to 000011, with the following parameters settings: 1. 2. 3. Teleservice Identifier parameter, IDENTIFIER = Voice Mail Notification (0x1003). Message Identifier sub-parameter, MESSAGE_TYPE = Deliver (0x1). Number of Messages sub-parameter, MESSAGE_CT = 99.

Upon receiving the Data Burst Message, verify the following: 1. The mobile station transmits an SMS Acknowledge message via Data Burst Message on the Access Channel, Enhanced Access Channel or Reverse Common Control Channel to acknowledge the short message, indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = 00).

1 1 2 3 4 5
f. g.

3GPP2 C.S0044-A v1.0 2. The mobile station indicates to the user the number of voice mail messages available as indicated by the network. Repeat step c and d, setting the MESSAGE_CT = 0. Upon receiving the Data Burst Message, verify that the mobile station indicates to the user no voice mail messages are available. Minimum Standard

68.1.6.5

7The mobile station shall comply with steps e and g. The base station shall comply with step d.

88.2

Mobile Station Originated SMS Tests

9This section is to be performed on mobile stations that support mobile station originated short 10messaging.

118.2.1 128.2.1.1

Common Channel SMS Delivery Definition

13This test verifies that a short message can be sent to the Message Center (MC) by a mobile 14station using the Access Channel, Enhanced Access Channel or Reverse Common Control 15Channel. The short message length chosen for this test is such that it doesnt exceed the 16maximum message length allowed on the Access Channel, Enhanced Access Channel or 17Reverse Common Control Channel.

188.2.1.2
19(see [13])

Traceability

202.4.1.1.1.2 212.4.2.1.1.1 228.2.1.3

23None

Mobile station SMS Message Origination Mobile station SMS Message Origination

Call Flow Example(s)

248.2.1.4 25 26 27 28 29 30 31 32
a. b.

Method of Measurement Power on the mobile station and wait until it is in the Mobile Station Idle State. Create a short message at the mobile station, of a length smaller than the maximum message length allowed on the Access Channel, Enhanced Access Channel or Reverse Common Control Channel10. Instruct the mobile station to send the short message to the network. Verify the mobile station sends a Data Burst Message to the base station over the Access Channel, Enhanced Access Channel or Reverse Common Control Channel with the following field settings:

c. d.

210 The maximum allowed size is dependent on the current capsule size or duration signaled in the 3overhead messages broadcasted by the base station and is also implementation dependent. 4
8

13GPP2 C.S0044-A v1.0

1

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

2 3

e.

Verify that the base station receives the short message and sends a layer 2 acknowledgement to the mobile station. Minimum Standard

48.2.1.5

5The mobile station shall comply with step d.

68.2.2 78.2.2.1

Traffic Channel SMS Delivery Definition

8This test verifies a mobile station in the Mobile Station Idle State can originate a short message of 9length larger than the maximum length allowed on the Access Channel, Enhanced Access 10Channel or Reverse Common Control Channel and that the message is delivered to the Message 11Center over the Traffic Channel.

128.2.2.2
13(see [13])

Traceability

142.4.1.1.1.2 152.4.2.1.2 168.2.2.3

17None

Mobile SMS Message Origination Base Station Traffic Channel Procedures

Call Flow Example(s)

188.2.2.4 19 20 21 22 23 24 25 26
a. b.

Method of Measurement Power on the mobile station and wait until it is in the Mobile Station Idle State. Create a short message at the mobile station, of a length larger than the maximum message length allowed on the Access Channel, Enhanced Access Channel or Reverse Common Control Channel. Instruct the mobile station to send the short message to the network. Verify the following: 1. The mobile station does not send the Data Burst Message over the Access Channel, Enhanced Access Channel or Reverse Common Control Channel

c. d.

1 1 2 3 4
5

3GPP2 C.S0044-A v1.0 2. The mobile station sends an Origination Message to originate as SMS call with the SERVICE_OPTION field set to either 6 or 14. 3. After entering the Conversation Substate, the mobile station sends a Data Burst Message, with the following fields set as follows:

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

6

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

7 8 9

e. f.

Verify the Message Center receives the short message. Verify that upon sending the short message, the mobile station sends a Release Order to release the dedicated channels. Minimum Standard

108.2.2.5

11The mobile station shall comply with steps d and f.

128.2.3 138.2.3.1

Traffic Channel SMS Delivery while in Conversation Definition

14This test verifies that a short message can be sent by the mobile station when it is in the 15Conversation Substate.

168.2.3.2
17(see [13])

Traceability

182.4.1.1.1.2 192.4.1.1.2.4 202.4.2.1.2 218.2.3.3

22None

Mobile station SMS Message Origination Mobile station Station Message Origination in the Conversation Substate Base Station Traffic Channel Procedures

Call Flow Example(s)

238.2.3.4 24 25 26
a. b. c.

Method of Measurement Setup a mobile station originated call. While mobile station is in the Conversation Substate, create a short message. Instruct the mobile station to send the short message to the network.

10

13GPP2 C.S0044-A v1.0 1 2

3

d.

Verify the mobile station sends a Data Burst Message, with the following fields set as follows:

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

4

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

5 6 7

e. f.

Verify the Message Center receives the short message. Verify that upon sending the short message, the mobile station does not attempt to release the dedicated channels. Minimum Standard

88.2.3.5

9The mobile station shall comply with steps d and f.

108.2.4 118.2.4.1

Unknown Destination Address Definition

12This test verifies the base station can process a mobile station originated short message with an 13unknown destination address and will inform the mobile station regarding an unknown destination 14address.

158.2.4.2
16(see [13])

Traceability

172.4.1.1.1.2 183.4.2.1 193.4.3.6 208.2.4.3

21None

Mobile station SMS Message Origination SMS Point-to-Point Message Cause Codes

Call Flow Example(s)

228.2.4.4 23 24 25 26
a. b. c.

Method of Measurement Power on the mobile station and wait until it is in the Mobile Station Idle State. Create a short message at the mobile station, but with an unknown address in the destination address field and the Bearer Reply Option parameter set. Instruct the mobile station to send the short message to the base station.

11

1 1 2
3

3GPP2 C.S0044-A v1.0 d. Verify the mobile station sends a Data Burst Message, with the following fields set as follows:

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

4 5

e.

Verify the Message Center receives the short message and the base station sends a Data Burst Message to the mobile station indicating an unknown address Minimum Standard

68.2.4.5

7The mobile station shall comply with step d. The base station shall comply with step e.

88.2.5 98.2.5.1

Mobile Station Originated SMS Disabled Definition

10This test verifies that when mobile station originated SMS is not activated in the network, the 11base station can process a mobile station originated short message and inform the mobile station 12that short message origination has been denied.

138.2.5.2
14(see [13])

Traceability

152.4.1.1.1.2 163.4.2.1 173.4.3.6 188.2.5.3

19None

Mobile station SMS Message Origination SMS Point-to-Point Message Cause Codes

Call Flow Example(s)

208.2.5.4 21 22 23 24 25 26
a. b. c. d.

Method of Measurement Ensure the mobile station originated short message feature for the mobile station is not activated in the network. Power on the mobile station and wait until it is in the Mobile Station Idle State. Create a short message at the mobile station, with the Bearer Reply Option parameter set. Instruct the mobile station to send the short message to the base station.

12

13GPP2 C.S0044-A v1.0 1 2

3

e.

Verify the mobile station sends a Data Burst Message, with the following fields set as follows:

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

4 5 6 7 8

f.

Upon receiving the Data Burst Message at the base station, verify the following: 1. 2. The base station sends a Data Burst Message to the mobile station, with an indication that the short message origination has been denied. The base station does not route the short message to the Message Center.

98.2.5.5

Minimum Standard

10The mobile station shall comply with step e. The base station shall comply with step f.

118.2.6 128.2.6.1

SMS Not Supported by Base Station Definition

13This test verifies the base station can process a mobile station originated short message, and 14inform the mobile station that SMS is not supported by the base station.

158.2.6.2
16(see [13])

Traceability

172.4.1.1.1.2 183.4.2.1 193.4.3.6 208.2.6.3

21None

Mobile station SMS Message Origination SMS Point-to-Point Message Cause Codes

Call Flow Example(s)

228.2.6.4 23 24 25 26
a. b. c.

Method of Measurement Ensure the base station is not capable of SMS or that SMS has been disabled for this test. Power on the mobile station and wait until it is in the Mobile Station Idle State. Create a short message at the mobile station, with Bearer Reply Option parameter set.

13

1 1 2 3
4

3GPP2 C.S0044-A v1.0 d. e. Instruct the mobile station to send the short message to the network. Verify the mobile station sends a Data Burst Message, with the following fields set as follows:

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

5

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

6 7 8 9

f.

Upon receiving the Data Burst Message at the base station, verify the following: 1. The base station sends a Data Burst Message to the mobile station, with an indication that SMS is not supported by this base station. 2. The base station does not route the short message to the Message Center. Minimum Standard

108.2.6.5

11The base station shall comply with step f.

128.3 138.3.1

Broadcast SMS Delivery on the Common Channel Definition

14This test verifies that mobile stations are able to receive broadcast SMS messages sent by the 15network addressed to any broadcast address that the mobile stations are configured to receive 16based on the priority, service and language.

178.3.2

Traceability

18(see [13])

192.4.1.2.1 204.3.1.3 218.3.3

22None

Common Channel Procedures for Broadcast SMS Broadcast Messaging Service

Call Flow Example(s)

238.3.4 24 25 26
a. b.

Method of Measurement Connect the base station and mobile stations as shown in Figure A-8. Ensure mobile station 1 is configured to receive broadcast SMS with normal priority while mobile station 2 is configured to receive broadcast SMS with emergency priority.

14

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8

9

Also, ensure that both mobile stations are configured to receive other filtering categories (i.e. service and language) for this test. c. d. e. f. g. Power on the mobile stations and wait until they are registered. Clear any outstanding broadcast messages in the network. Create broadcast message 1 shown in Table 8.3.4-38 Instruct the network to broadcast message 1. Verify the base station sends a Data Burst Message, with the following fields set as follows:

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

10

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

11
Broadcast Message Message 1 Message 2
12

Table 8.3.4-38 Broadcast Message Priority Normal Emergency Priority Indicator Value 00 11

13 14 15 16 17 18 19
20 21

h.

Upon receiving the Data Burst Message, verify that mobile station 1 displays broadcast message 1 (as a Normal message, if such display is supported) and mobile station 2 does not. Create broadcast message 2 shown in Table 8.3.4-38. Instruct the network to broadcast message 2. Verify the base station sends a Data Burst Message, with the following fields set as follows:

i. j. k.

Field MSG_NUMBER

Value 1 (00000001)

15

1
BURST_TYPE NUM_MSGS NUM_FIELDS
1

3GPP2 C.S0044-A v1.0 3 (000011) 1 (00000001) Greater than 0

2 3

l.

Upon receiving the Data Burst Message, verify both mobile stations display broadcast message 2 (as an Emergency message, if such a display is supported) Minimum Standard

48.3.5

5The mobile station shall comply with steps h and l. The base station shall comply with steps g and 6k.

78.4 9 10 11 12 13 14 15
a. b. c. d. e.

Mobile Station Terminated Enhanced Messaging Services [EMS] Tests:

8Unless otherwise noted, the following conditions apply for all tests in this section:

Mobile station is capable of receiving Enhanced Messaging Services [EMS] messages. The EMS message feature for the mobile station is activated. Base station has Power-up registration enabled by setting POWER-UP_REG = 1 in the System Parameters Message or the ANSI-41 System Parameters Message. Transport Layer messages shall include the Bearer Reply Option. SMS message carries Teleservice ID parameter is set to WEMT (0x1005),, and HEAD_IND of Message Identifier subparameter is set to '1' Multi-Segment EMS Message Delivery Definition

168.4.1 178.4.1.1

18This test verifies the mobile stations ability to receive and properly display multi-segmented EMS 19messages.

208.4.1.2
21(see [13])

Traceability

224.3.7 232.4.1.1.1.1 248.4.1.3

25None

Wireless Enhanced Messaging Teleservice Mobile station SMS Message Termination

Call Flow Example(s)

268.4.1.4 27 28
a.

Method of Measurement Delete all outstanding short messages in the network for the mobile station. Delete all short messages in the mobile station.

16

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6

b. c. d. Create an EMS message in the Message Center for the mobile station, consisting of (3) three segments. Instruct the Message Center to send the first segment of the EMS message to the mobile station. Verify that the base station sends the first Data Burst Message to the mobile station, with the following fields set as follows:

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

8 9 10 11 12 13 14
15

e.

Verify that the mobile station transmits a Data Burst Message to acknowledge the received Data Burst Message, and indicates no error (i.e. containing Cause Codes parameter having ERROR_CLASS = 00). Instruct the Message Center to send the remaining segments of the EMS message to the mobile station. Verify that the base station sends the remaining Data Burst Messages to the mobile station, with the following fields set as follows:

f. g.

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

16

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

17 18 19 20 21 22 23

h.

Verify that the mobile station transmits a Data Burst Message to acknowledge each received Data Burst Message, containing a message segment, and indicates no error (i.e. contains Cause Codes parameters having ERROR_CLASS = 00). Upon receiving all the Data Burst Messages at the mobile station, verify the following: 1. The mobile station alerts the user for the incoming EMS message and correctly displays the received message, when selected. Verify that all the segments of the EMS message segments sent are properly displayed in correct order.

i.

17

1 18.4.1.5
Minimum Standard

3GPP2 C.S0044-A v1.0

2The mobile station shall comply with steps e, h, and i. The base station shall comply with steps d 3and g.

48.4.2 58.4.2.1

Delivery of Predefined Sound Elements Definition

6This test verifies mobile stations ability to receive and properly play pre-defined EMS sound 7elements.

88.4.2.2
9(see [13])

Traceability

104.3.7 112.4.1.1.1.1 128.4.2.3

13None

Wireless Enhanced Messaging Teleservice Mobile station SMS Message Termination

Call Flow Example(s)

148.4.2.4 15 16 17 18 19 20 21 22
23

Method of Measurement Delete all outstanding short messages in the network for the mobile station. Delete all short messages in the mobile station. Create an EMS message in the Message Center for the mobile station. In the message include (1) one predefined sound element. Power on the mobile station and wait until it is in the Mobile Station Idle State. Instruct the network to send the EMS message to the mobile station. Verify the base station sends a Data Burst Message to the mobile station with the specified fields set as follow:

a. b. c. d. e.

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

24 25 26 27

f.

Upon receiving Data Burst Message at the mobile station, verify the following: 1. The mobile station alerts the user for the incoming message and correctly displays the received message (if chosen). 2. The mobile station properly plays the predefined sound, when selected.

18

13GPP2 C.S0044-A v1.0 1 2 3 48.4.2.5

3. The mobile station transmits a Data Burst Message to acknowledge the EMS message, indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = 00). Minimum Standard

5The mobile station shall comply with step f. The base station shall comply with step e.

68.4.3 78.4.3.1

Delivery of Predefined Animation Elements Definition

8This test verifies mobile stations ability to receive and properly play pre-defined EMS animation 9elements.

108.4.3.2
11(see [13])

Traceability

124.3.7 132.4.1.1.1.1 148.4.3.3

15None

Wireless Enhanced Messaging Teleservice Mobile SMS Message Termination

Call Flow Example(s)

168.4.3.4 17 18 19 20 21 22 23 24
25

Method of Measurement Delete all outstanding short messages in the network for the mobile station. Delete all short messages in the mobile station. Create an EMS message in the Message Center for the mobile station. In the message include (1) one pre-defined animation in a specific order. Power on the mobile station and wait until it is in the Mobile Station Idle State. Instruct the network to send the EMS message to the mobile station. Verify the base station sends a Data Burst Message to the mobile station with the specified fields set as follow:

a. b. c. d. e.

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

26

f.

Upon receiving Data Burst Message at the mobile station, verify the following:

19

1 1 2 3 4 5 6 78.4.3.5

3GPP2 C.S0044-A v1.0 1. The mobile station alerts the user for the incoming message and correctly displays the received message (if chosen). 2. The mobile station properly plays the pre-defined animation, when selected. 3. The mobile station transmits a Data Burst Message to acknowledge the EMS message, indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = 00). Minimum Standard

8The mobile station shall comply with step f. The base station shall comply with step e.

98.4.4 108.4.4.1

Delivery of User Defined Sound Elements - MT Definition

11This test verifies mobile stations ability to receive and properly play user defined (iMelody) EMS 12sound elements.

138.4.4.2
14(see [13]) 154.3.7

Traceability Wireless Enhanced Messaging Teleservice Mobile SMS Message Termination

162.4.1.1.1.1

178.4.4.3
18None

Call Flow Example(s)

198.4.4.4 20 21 22 23 24 25 26 27
28

Method of Measurement Delete all outstanding short messages in the network for the mobile station. Delete all short messages in the mobile station. Create an EMS message in the Message Center for the mobile station. In the message include (1) one iMelody sound object. Power on the mobile station and wait until it is in the Mobile Station Idle State. Instruct the network to send the EMS message to the mobile station. Verify the base station sends a Data Burst Message to the mobile station with the specified fields set as follow:

a. b. c. d. e.

Field MSG_NUMBER BURST_TYPE NUM_MSGS

Value 1 (00000001) 3 (000011) 1 (00000001)

20

13GPP2 C.S0044-A v1.0

NUM_FIELDS Greater than 0

1 2 3 4 5 6 7 8

f.

Upon receiving Data Burst Message at the mobile station, verify the following: 1. The mobile station alerts the user for the incoming message and correctly displays the received message (if chosen). 2. The mobile station properly plays the iMelody sound object, when selected. Verify that the iMelody being played is same as the one being transmitted. 3. The mobile station transmits a Data Burst Message to acknowledge the EMS message, indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = 00). Minimum Standard

98.4.4.5

10The mobile station shall comply with step f. The base station shall comply with step e.

118.4.5 128.4.5.1

Delivery of User Defined Animation Elements - MT Definition

13This test verifies mobile stations ability to receive and properly play user defined EMS animation 14elements.

158.4.5.2
16(see [13])

Traceability

174.3.7 182.4.1.1.1.1 198.4.5.3

20None

Wireless Enhanced Messaging Teleservice Mobile SMS Message Termination

Call Flow Example(s)

218.4.5.4 22 23 24 25 26 27 28 29
30

Method of Measurement Delete all outstanding short messages in the network for the mobile station. Delete all short messages in the mobile station. Create an EMS message in the Message Center for the mobile station. In the message include one user-defined animation object. Power on the mobile station and wait until it is in the Mobile Station Idle State. Instruct the network to send the EMS message to the mobile station. Verify the base station sends a Data Burst Message to the mobile station with the specified fields set as follow:

a. b. c. d. e.

Field MSG_NUMBER

Value 1 (00000001)

21

3GPP2 C.S0044-A v1.0

BURST_TYPE NUM_MSGS NUM_FIELDS

3 (000011) 1 (00000001) Greater than 0

1 2 3 4 5 6 7

f.

Upon receiving Data Burst Message at the mobile station, verify the following: 1. The mobile station alerts the user for the incoming message and correctly displays the received message (if chosen). 2. The mobile station properly plays the user-defined animation, when selected. 3. The mobile station transmits a Data Burst Message to acknowledge the EMS message, indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = 00). Minimum Standard

88.4.5.5

9The mobile station shall comply with step f. The base station shall comply with step e.

108.4.6 118.4.6.1

Delivery of User Defined Picture Elements - MT Definition

12This test verifies mobile stations ability to receive and properly play user defined EMS picture 13elements.

148.4.6.2
15(see [13])

Traceability

164.3.7 172.4.1.1.1.1 188.4.6.3

19None

Wireless Enhanced Messaging Teleservice Mobile SMS Message Termination

Call Flow Example(s)

208.4.6.4 21 22 23 24 25 26 27 28
a. b. c. d. e.

Method of Measurement Delete all outstanding short messages in the network for the mobile station. Delete all short messages in the mobile station. Create an EMS message in the Message Center for the mobile station. In the message include one user-defined picture object. Power on the mobile station and wait until it is in the Mobile Station Idle State. Instruct the network to send the EMS message to the mobile station. Verify the base station sends a Data Burst Message to the mobile station with the specified fields set as follow:

22

13GPP2 C.S0044-A v1.0

1

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

2 3 4 5 6 7 8

f.

Upon receiving Data Burst Message at the mobile station, verify the following: 1. The mobile station alerts the user for the incoming message and correctly displays the received message (if chosen). 2. The mobile station properly displays the user-defined picture, when selected. 3. The mobile station transmits a Data Burst Message to acknowledge the EMS message, indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = 00). Minimum Standard

98.4.6.5

10The mobile station shall comply with step f. The base station shall comply with step e.

118.4.7 128.4.7.1

Delivery of Formatted Text Definition

13This test verifies mobile stations ability to receive and properly display formatted text embedded 14in EMS messages.

158.4.7.2
16(see [13])

Traceability

174.3.7 182.4.1.1.1.1 198.4.7.3

20None

Wireless Enhanced Messaging Teleservice Mobile SMS Message Termination

Call Flow Example(s)

218.4.7.4 22 23 24 25 26
27

Method of Measurement Delete all outstanding short messages in the network for the mobile station. Delete all short messages in the mobile station. Create an EMS message in the Message Center for the mobile station. From the Normal Bold Italics Bold-Italics following text, include the text with formatting that is supported by the mobile station in the message:

a. b.

Underlined Bold-Underlined Bold-Italics-Underlined Left-Justified

23

Center-Justified

1
1 2 3 4 5 6 7 8 9

3GPP2 C.S0044-A v1.0

10 11 12 13
14

c. d. e.

Power on the mobile station and wait until it is in the Mobile Station Idle State. Instruct the network to send the EMS message to the mobile station. Verify the base station sends a Data Burst Message to the mobile station with the specified fields set as follow:

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

15 16 17 18 19 20 21 22

f.

Upon receiving Data Burst Message at the mobile station, verify the following: 1. The mobile station alerts the user for the incoming message and correctly displays the received message (if chosen). 2. The mobile station properly displays the text, including correct formatting of the lines of text displayed. 3. The mobile station transmits a Data Burst Message to acknowledge the EMS message, indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = 00). Minimum Standard

238.4.7.5

24The mobile station shall comply with step f. The base station shall comply with step e.

24

13GPP2 C.S0044-A v1.0 18.5 28.5.1 38.5.1.1

Mobile Station Originated Enhanced Messaging Services [EMS] Tests: Multi-Segment EMS Message Delivery Definition

4This test verifies mobile stations ability to compose and send multi-segmented EMS messages.

58.5.1.2
6(see [13])

Traceability

74.3.7 82.4.1.1.2 92.4.1.1.1.2 108.5.1.3

11None

Wireless Enhanced Messaging Teleservice Mobile Station Traffic Channel Procedures Mobile SMS Message Origination

Call Flow Example(s)

128.5.1.4 13 14 15 16 17 18 19 20
a. b. c. d. e.

Method of Measurement Power on the mobile station and wait until it is in the Mobile station Idle State. Create an EMS message at the mobile station, consisting of three (3) segments. Instruct the mobile station to send all the segments of the EMS message to the Message Center. Verify that the Message Center receives all the segments and sends an SMS Acknowledgement for each segment to the mobile station. Verify that upon sending the short message, the mobile station sends a Release Order to release the dedicated channels. Minimum Standard

218.5.1.5

22The mobile station shall comply with step e.

238.5.2 248.5.2.1

Delivery of Predefined Sound Elements Definition

25This test verifies the mobile stations ability to compose and send messages containing 26predefined EMS sound elements.

278.5.2.2
28(see [13])

Traceability

294.3.7 302.4.1.1.1.2

Wireless Enhanced Messaging Teleservice Mobile SMS Message Origination

25

1 18.5.2.3
2None

3GPP2 C.S0044-A v1.0 Call Flow Example(s)

38.5.2.4 4 5 6 7 8 9
11

Method of Measurement Power on the mobile station and wait until it is in the Mobile Station Idle State. Create an EMS message at the mobile station. In the message include (1) one predefined sound. Instruct the mobile station to send the EMS message to the Message Center. Verify the mobile station sends a Data Burst Message to the base station with the fields set as follows:

a. b. c. d.

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

12

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

13 14 15 16

e. f.

Verify that the Message Center receives Data Burst Message and sends the SMS Acknowledgement to the mobile station. Verify that the EMS message sent from the test mobile station contains (1) one predefined sound. Minimum Standard

178.5.2.5

18The mobile station shall comply with step d.

198.5.3 208.5.3.1

Delivery of Predefined Animation Elements Definition

21This test verifies the mobile stations ability to compose and send messages containing 22predefined EMS animation elements.

238.5.3.2
24(see [13])

Traceability

254.3.7 262.4.1.1.1.2

Wireless Enhanced Messaging Teleservice Mobile SMS Message Origination

26

13GPP2 C.S0044-A v1.0 18.5.3.3

2None

Call Flow Example(s)

38.5.3.4 4 5 6 7 8 9
10

Method of Measurement Power on the mobile station and wait until it is in the Mobile Station Idle State. Create an EMS message at the mobile station. In the message include (1) one predefined animation object. Instruct the mobile station to send the EMS message to the Message Center. Verify the mobile station sends a Data Burst Message to the base station with the fields set as follows:

a. b. c. d.

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

11

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

12 13 14 15

e. f.

Verify that the Message Center receives Data Burst Message and sends the SMS Acknowledgement to the mobile station. Verify that the EMS message sent from the test mobile station contains the predefined animation object. Minimum Standard

168.5.3.5

17The mobile station shall comply with steps d and f. The base station shall comply with step e.

188.5.4 198.5.4.1

Delivery of User Defined Sound Elements Definition

20This test verifies the mobiles ability to compose and send a message containing user defined 21(iMelody) EMS sound elements.

228.5.4.2
23(see [13])

Traceability

244.3.7 252.4.1.1.1.2 268.5.4.3

27None

Wireless Enhanced Messaging Teleservice Mobile SMS Message Origination

Call Flow Example(s)

27

1 18.5.4.4 2 3 4 5 6 7
8

3GPP2 C.S0044-A v1.0 Method of Measurement Power on the mobile station and wait until it is in the Mobile Station Idle State. Create an EMS message at the mobile station. In the message include (1) one iMelody sound object. Instruct the mobile station to send the EMS message to the Message Center. Verify the mobile station sends a Data Burst Message to the base station with the fields set as follows:

a. b. c. d.

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

9

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

10 11 12 13

e. f.

Verify that the Message Center receives Data Burst Message and sends the SMS Acknowledgement to the mobile station. Verify that the EMS message sent from the test mobile station contains the iMelody sound object sent. Minimum Standard

148.5.4.5

15The mobile station shall comply with steps d and f. The base station shall comply with step e.

168.5.5 178.5.5.1

Delivery of User Defined Animation Elements Definition

18This test verifies mobile stations ability to compose and send a message containing user defined 19EMS animation elements.

208.5.5.2
21(see [13])

Traceability

224.3.7 232.4.1.1.1.2 248.5.5.3

25None

Wireless Enhanced Messaging Teleservice Mobile SMS Message Origination

Call Flow Example(s)

28

13GPP2 C.S0044-A v1.0 18.5.5.4 2 3 4 5 6 7

8

Method of Measurement Power on the mobile station and wait until it is in the Mobile Station Idle State. Create an EMS message at the mobile station. In the message include one userdefined animation object. Instruct the mobile station to send the EMS message to the Message Center. Verify the mobile station sends a Data Burst Message to the base station with the fields set as follows:

a. b. c. d.

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

9 10 11 12

e. f.

Verify that the Message Center receives Data Burst Message and sends the SMS Acknowledgement to the mobile station. Verify that the EMS message sent from the test mobile station contains the userdefined animation object sent. Minimum Standard

138.5.5.5

14The mobile station shall comply with steps d and f. The base station shall comply with step e.

158.5.6 168.5.6.1

Delivery of User Defined Picture Elements Definition

17This test verifies mobiles ability to send user-defined EMS picture elements.

188.5.6.2
19(see [13])

Traceability

204.3.7 212.4.1.1.1.2 228.5.6.3

23None

Wireless Enhanced Messaging Teleservice Mobile SMS Message Origination

Call Flow Example(s)

248.5.6.4 25
a.

Method of Measurement Power on the mobile station and wait until it is in the Mobile Station Idle State.

29

1 1 2 3 4 5
6

3GPP2 C.S0044-A v1.0 b. c. d. Create an EMS message at the mobile station. In the message include one userdefined picture object. Instruct the mobile station to send the EMS message to the Message Center. Verify the mobile station sends a Data Burst Message to the base station with the fields set as follows:

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

7

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

8 9 10 11

e. f.

Verify that the Message Center receives Data Burst Message and sends the SMS Acknowledgement to the mobile station. Verify that the EMS message sent from the test mobile station contains the userdefined picture object sent. Minimum Standard

128.5.6.5

13The mobile station shall comply with step d.

148.5.7 158.5.7.1

Delivery of Formatted Text Definition

16This test verifies mobiles ability to compose and send formatted text embedded in EMS 17messages.

188.5.7.2
19(see [13])

Traceability

204.3.7 212.4.1.1.1.2 228.5.7.3

23None

Wireless Enhanced Messaging Teleservice Mobile SMS Message Origination

Call Flow Example(s)

248.5.7.4 25 26 27 2
a. b.

Method of Measurement Power on the mobile station and wait until it is in the Mobile Station Idle State. Create an EMS message in the mobile station under test. From the following text, include the text with formatting that is supported by the mobile station in the message:

30

13GPP2 C.S0044-A v1.0

1 2 3 4 5 6 7 8 9 10

Normal Bold Italics Bold-Italics Underlined Bold-Underlined Bold-Italics-Underlined Left-Justified Center-Justified

c. d. Instruct the mobile station to send the EMS message to the Message Center. Verify the mobile station sends a Data Burst Message to the base station with the fields set as follows

11 12 13
14

Field MSG_NUMBER BURST_TYPE NUM_MSGS NUM_FIELDS

15

Value 1 (00000001) 3 (000011) 1 (00000001) Greater than 0

16 17 18 19

e. f.

Verify that the Message Center receives Data Burst Message and sends the SMS Acknowledgement to the mobile station. Verify that the EMS message sent from the test mobile station contains the properly formatted text information. Minimum Standard

208.5.7.5
22

21The mobile station shall comply with step d.

31

1
1No text.

3GPP2 C.S0044-A v1.0

32

13GPP2 C.S0044-A v1.0 19 29.1 39.1.1

SUBSCRIBER CALLING FEATURES

Call Forwarding Unconditional (CFU) Definition

4CFU permits a called subscriber to send incoming calls addressed to the called subscribers 5Directory Number to another Directory Number (forward-to number). If this feature is active, calls 6are forwarded regardless of the condition of the termination.

79.1.2 9505 109.1.3

11None

Traceability

8(see [22])

Call ForwardingUnconditional Call Flow Example(s)

129.1.4 13 14 15 16 17 18 19 20 21 22 23 24
a. b.

Method of Measurement Power on the mobile station and wait until it reaches Mobile Station Idle State. Dial the CFU feature activation code, followed by the forward-to number, followed by SEND. Verify feature update confirmation at the mobile station (confirming audio tones from the network). Setup a call from a land party to the mobile station. Verify call is forwarded and that if the Network directs the mobile station to Ping Ring it plays a single burst of 500 ms. Answer the call on the forward-to line, and verify the audio path. End the call. Dial the CFU deactivation feature code followed by SEND. Verify feature update confirmation at the mobile station. Verify that CFU has been deactivated, by calling the mobile station under test and verifying that the mobile station rings and completes the call when answered. Minimum Standard

c. d. e. f. g.

259.1.5

26The mobile station and the base station shall comply with steps b, c, d, f and g.

279.2 289.2.1

Call Forwarding Busy (CFB) Definition

29CFB permits a called subscriber to have the system send incoming calls to another Directory 30Number (forward-to number) when the subscriber is engaged in a call or service.

1 19.2.2 3502 49.2.3

5None

3GPP2 C.S0044-A v1.0 Traceability

2(see [22])

Call Forwarding Busy Call Flow Example(s)

69.2.4 7 8 9 10 11 12 13 14 15 16 17 18 19 20
a. b.

Method of Measurement Power on the mobile station and wait until it reaches Mobile Station Idle State. Dial the CFB activation feature code, followed by the forward-to-number, followed by SEND. Verify feature update confirmation at the mobile station (confirming audio tones from the network). Place the mobile station under test in a voice call. Attempt a second call from a land party to the mobile station under test. Verify the call is forwarded to the forward-to-number, and that if the Network directs the mobile station to Ping Ring it plays a single burst of 500 ms. Answer the call on the forward-to line, and verify the audio path. End all calls. Dial the CFB deactivation feature code followed by SEND. Verify feature update confirmation at the mobile station. Verify that CFB has been deactivated, e.g. by calling the mobile station under test while busy and verifying that the second call is not forwarded. Minimum Standard

c. d.

e. f. g. h.

219.2.5

22The mobile station and the base station shall comply with steps b, c, d, f and g.

239.3 249.3.1

Call Forwarding Default (CFD) Definition

25CFD permits a called subscriber to have the system send incoming calls to another Directory 26Number (forward-to-number) when the subscriber is engaged in a call, does not respond to 27paging, does not answer the call within a specified period after being alerted or is otherwise 28inaccessible.

299.3.2 31503 329.3.3

33None

Traceability

30(see [22])

Call ForwardingDefault Call Flow Example(s)

13GPP2 C.S0044-A v1.0 19.3.4 2 3 4 5 6 7 8 9 10 11 12 13 14

a. b. Method of Measurement Power on the mobile station and wait until it reaches Mobile Station Idle State. Dial the CFD activation feature code, followed by the forward-to number, followed by SEND. Verify feature update confirmation at the mobile station (confirming audio tones from the network). Attempt a call from a land party to the mobile station. Verify the call is forwarded and that if the Network directs the mobile station to Ping Ring it plays a single burst of 500 ms. Answer the call on the forward-to line, and verify the audio path. End call. Dial the CFD deactivation feature code followed by SEND. Verify feature update confirmation at the mobile station. Verify that CFD has been deactivated, by calling the mobile station under test and verifying that the mobile station rings and does not forward. Minimum Standard

c.

d. e. f. g.

159.3.5

16The mobile station and the base station shall comply with steps b, c, d, f and g.

179.4 189.4.1

Call Forwarding No Answer (CFNA) Definition

19CFNA permits a called subscriber to have the system send incoming calls addressed to the called 20subscribers Directory Number to another Directory Number (forward-to number) when the 21subscriber fails to answer.

229.4.2 24504 259.4.3

26None

Traceability

23(see [22])

Call ForwardingNo Answer Call Flow Example(s)

279.4.4 28 29 30 31 32 33 34
a. b.

Method of Measurement Power on the mobile station and wait until it reaches Mobile Station Idle State. Dial the CFNA activation feature code, followed by the forward-to number, followed by SEND. Verify feature update confirmation at the mobile station (confirming audio tones from the network). Setup a call from a land party to the mobile station. Verify the mobile station rings, but when not answered, the call is forwarded to the forward-to number. Answer the call on the forward-to line, and verify the audio path.

c. d.

1 1 2 3 4 5
e. f. g. End the call.

3GPP2 C.S0044-A v1.0

Dial the CFNA deactivation feature code followed by SEND. Verify feature update confirmation at the mobile station. Verify that CFNA has been deactivated, by calling the mobile station and verifying that the mobile station rings and does not forward. Minimum Standard

69.4.5

7The mobile station and the base station shall comply with steps b, c, d, f and g.

89.5 99.5.1

Three-Way Calling Definition

10This tests mobile stations operation of Three-way Calling. In Three-way Calling, the base station 11responds to Flash With Information Messages from the mobile station to connect a third party to 12an established two-way call.

139.5.2 15522 169.5.3

17

Traceability

14(see [22])

Three Way Calling Call Flow Example(s)

MS
Voice Traffic in 2-way call Flash with Info Message Ack Order Flash with Info Message Ack Order Flash with Info Message Ack Order

BS
no records 3rd party number Connect 3way

18 199.5.4 20 21 22 23
a. b. c. Method of Measurement Allow the mobile station to come to the idle state on the base station. Ensure the base station will allow the mobile station to perform Three-way calling via subscriber profile or by dialing a feature activation code such as *31+ SEND. Set up a normal two-way voice call with a second party.

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

d. e. f. Put the second party on hold using the prescribed method at the mobile station, e.g. send a Flash With Information Message by pressing the SEND button. Verify the second party is placed on hold and the mobile station alerts the user to commence dialing the third party number, e. g. plays a dial tone. Dial the third party number on the mobile station and send it out using the prescribed method, e. g. send a Flash With Information Message containing the Keypad Facility Information Record or the Called Party Number Information Record by pressing the SEND button after entering dialed digits. Verify the third party phone rings and answers with normal audio. Connect all of the Three-Way Call parties, e. g. send a Flash With Information Message by pressing the SEND button, and verify the three-way connection is established with normal audio. End the call. Ensure the base station will not allow the mobile station to perform Three-way calling via subscriber profile or by dialing a feature de-activation code such as *91+ SEND Minimum Standard

g. h.

i. j.

169.5.5

17The mobile station shall comply with the requirements in steps b, e, g, h, and j.

189.6 199.6.1

Call Alerting Definition

20This is a test for standard mobile station incoming call alerting (ringing). An incoming call alert is 21played or displayed by the mobile station as a result of receiving an Alert With Information 22Message or an Extended Alert with Information Message with a Signal information record.

239.6.2

Traceability

24(see [4])

25Table 3.7.5.5-1 26Table 3.7.5.5-2 27Table 3.7.5.5-3 28Table 3.7.5.5-4 29Table 3.7.5.5-5 30Table 3.7.5-1 319.6.3
32

Signal Type Alert Pitches Tone Signals (SIGNAL_TYPE = 00) ISDN Alerting (SIGNAL_TYPE = 01) IS-54B Alerting (SIGNAL_TYPE = 10) Information Record Types (base station)

Call Flow Example(s)

3GPP2 C.S0044-A v1.0

MS
Page Message to mobile Page Response Message Order Message (acknowledgement from base station) Extended Channel Assignment Message possible service negotiation Service Connect Message

BS

Service Connect Complete Message Alert with Info Message Message (ring for mobile) Connect Order Message Voice Traffic Release Order Messages

1 29.6.4 3 4 5 6 7 8 9 10 11 12
a. b. Method of Measurement Allow the mobile station to come to the idle state on the base station, and make a mobile station terminated call. Verify the mobile station receives an Alert with Information Message or Extended Alert with Information Message with a Signal Information record. The Alert with Information Message may or may not contain a Calling Party Number Information record. Verify the mobile station rings (plays an incoming call alert). Answer the call, verify the call completes successfully, then end the call. Steps a through d may be repeated using each variation of parameters in the Signal Information record for SIGNAL_TYPE, ALERT_PITCH, and SIGNAL as supported by the base station. Minimum Standard

c. d. e.

139.6.5

14The mobile station shall comply with the requirements in step c, d, and e.

159.7 169.7.1

Calling Party Number for Mobile station Terminated Call Setup Definition

17This tests the delivery and display of a Calling Party Number (CPN) during call setup.

13GPP2 C.S0044-A v1.0 19.7.2 33.7.5.3 4Table 2.7.1.3.2.4-2 5Table 2.7.1.3.2.4-3 6Table 2.7.4.4-1 7Table 3.7.5-1 89.7.3
9None

Traceability

2(see [4])

Calling Party Number Number Types Numbering Plan Identification Presentation Indicators Information Record Types (base station)

Call Flow Example(s)

109.7.4 11 12 13 14 15 16 17 18 19
a. b. c. d.

Method of Measurement Configure the base station to send a Calling Party Number for mobile station terminated calls. Allow the mobile station to come to the idle state on the base station, and initiate a mobile station terminated call. Verify the mobile station displays the correct Calling Party Number before answering the call and then answer the call. Repeat steps b to c for all Calling Party Number base station configurations, e.g. parameters PI = 01 (Presentation Restricted) and PI = 10 (Number not available or Unavailable), as supported by the base station, and verify the correct outcome. Minimum Standard

209.7.5

21The mobile station shall comply with requirements in steps c and d. In step d, for PI = 01 22(Presentation Restricted) and PI = 10 (Number not available or Unavailable), the mobile station 23shall NOT display the Calling Party Number, but may display No Caller ID or something to that 24effect.

259.8 269.8.1

Calling Party Number for Call Waiting Definition

27This tests the delivery and display of a Calling Party Number (CPN) for Call Waiting calls.

289.8.2 303.7.5.3

Traceability

29(see [4])

Calling Party Number Call Waiting Indicator Mandatory Control Tags and Display Text Tags Number Types

313.7.5.22 32Table 3.7.5.16-2 33Table 2.7.1.3.2.4-2

1 1Table 2.7.1.3.2.4-3 2Table 2.7.4.4-1 3Table 3.7.5-1 49.8.3

5None

3GPP2 C.S0044-A v1.0 Numbering Plan Identification Presentation Indicators Information Record Types (base station)

Call Flow Example(s)

69.8.4 7 8 9 10 11 12 13 14
a. b. c. d. e.

Method of Measurement Configure the base station to send a Calling Party Number for Call Waiting calls. Set up a mobile station terminated voice call. While this voice call is in progress, attempt a second call to the mobile station. Verify the mobile station displays the correct Calling Party Number of the Call Waiting caller. Repeat steps b to d for all Calling Party Number base station configurations, e. g. CPN parameters PI = 01 (Presentation Restricted) and PI = 10 (Number not available or Unavailable), as supported by the base station, and verify the correct outcome. Minimum Standard

159.8.5

16The mobile station shall comply with requirements in steps d and e. In step e, for PI = 01 17(Presentation Restricted) and PI = 10 (Number not available or Unavailable), the mobile station 18shall NOT display the Caller ID, but may display No Caller ID or something to that effect.

199.9 209.9.1

Call Waiting Definition

21This test verifies mobile station call-waiting notification, alerting, and connection with Flash with 22Information Messages or Extended Flash with Information Messages. It also checks the mobile 23station ability to activate and deactivate the call-waiting feature on the network.

249.9.2 263.7.5.5

Traceability

25(see [4])

Signal Information Record Types (mobile station) Information Record Types (base station)

27Table 2.7.4-1 28Table 3.7.5-1 303.7.5.22 319.9.3

32None

29Table 3.7.5.5-5 IS-54B Alerting (SIGNAL_TYPE = 10)

Call Waiting Indicator

Call Flow Example(s)

13GPP2 C.S0044-A v1.0 19.9.4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

a. b. Method of Measurement Allow the mobile station to come to the idle state on the base station. Activate call waiting, e.g. make a dedicated call *41-SEND, and verify that the mobile station plays or displays a notification that call waiting has been activated, e.g. audio confirmation tones in the earpiece. Verify the call-waiting activation call ends without user interaction (Base Station releases the call), and the mobile station returns to the idle state on the base station. Set up a voice call with the mobile station. While the first call is in progress, attempt a second mobile station terminated call, and verify that a call-waiting alert is played at the mobile station, e.g. tones in the earpiece. Cause the mobile station to accept the second call, e.g. press SEND, and verify the connection to the second caller with normal audio. Cause the mobile station to flash back to the first call, e.g. press SEND, and verify the connection to the first caller with normal audio. Press END on the mobile station to end the call. Note: in some implementations, if the mobile station subscriber ends a call waiting call while the other party is still waiting, the base station will initiate a mobile station terminated call to re-connect the waiting party. If this is the case, answer the call, then end that call too. Deactivate call waiting on the base station, e.g. make a dedicated call *410-SEND, and verify the mobile station plays or displays a notification that call waiting has been disabled, e.g. tones in the earpiece. Set up a new call with the mobile station. While the call is in progress, attempt another mobile station terminated call, and verify that no call-waiting alert is played at the mobile station. Minimum Standard

c. d.

e. f. g.

h.

i.

259.9.5

26The mobile station shall comply with the requirements in steps b, c, d, e, f, h, and i.

279.10 Voice Mail Message Waiting Notification from the Idle State 289.10.1 Definition
29This test verifies mobile station response to message waiting notification while the mobile station 30is in the idle state. Notification can be a tone, light, or display and is manufacturer dependent.

319.10.2 Traceability
32(see [4])

333.7.5.6 343.7.2.3.2.12 35(see [22]) 365.1.3-A.1 2

Message Waiting Feature Notification Message

Message Waiting Notification

1 19.10.3 Call Flow Example(s)

2None

3GPP2 C.S0044-A v1.0

39.10.4 Method of Measurement 4 5 6 7 8 9 10 11 12 13 14 15 16

a. b. Power on the mobile station and allow it to come to the idle state on the base station. Instruct the base station to send a voice mail message waiting notification, setting the number of voice mail messages waiting to a value less than the maximum number the mobile station can display. Verify that any indication on the mobile station of the number of messages waiting reflects the correct value.. The mobile station may give an indication of the change in message waiting status. Repeat steps b through c for a larger number of voice mail messages waiting. Repeat steps b through c for a smaller non-zero number of voice mail messages waiting Repeat steps b through c, except in step b, send notification for zero voice mail messages waiting, e. g. to clear the mobile stations voice mail waiting indicator on the mobile station.

c. d. e. f. g.

179.10.5 Minimum Standard

18The mobile station shall comply with the requirement in step c and may comply with step d.

199.11 Voice Mail Message Waiting Notification from the Conversation State 209.11.1 Definition
21This test verifies mobile stations response to message waiting notification while the mobile 22station is in the conversation state.

239.11.2 Traceability
24(see [4])

253.7.5.6 26(see [22]) 275.1.3-A.1

Message Waiting

Message Waiting Notification

289.11.3 Call Flow Example(s)

29None

309.11.4 Method of Measurement 31 32

a. b. Power on the mobile station and allow it to come to the idle state on the base station. Set up a call with the mobile station.

10

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11

c. Instruct the base station to send a voice mail message waiting notification, setting the number of voice mail messages waiting to a value less than the maximum number the mobile station can display. Verify that any indication on the mobile station of the number of messages waiting reflects the correct value. The mobile station may give an indication of the change in message waiting status. Instruct the base station to send a voice mail message waiting notification, setting the number of messages waiting to a value that exceeds the maximum number that can be displayed by the mobile station. Verify that any indication on the mobile station of the number of messages waiting displays reflects the maximum number of messages that it can display.

d. e. f.

g.

129.11.5 Minimum Standard

13The mobile station shall comply with the requirements in steps d and g and may comply with step 14e.

159.12 Calling Party Name Presentation during Call Setup 169.12.1 Definition
17This test will verify that the mobile station in the mobile station idle state properly displays the 18calling name information contained in an Extended Display Information record. This test is only 19applicable to mobile stations capable of displaying information sent by the base station..

209.12.2 Traceability
21(see [4])

223.7.5.16 233.7.5.21 243.7.5.22 25Table 3.7.5.16-2 26Table 2.7.4.4-1 27Table 3.7.5-1

Extended Display, Calling Party Name Multiple Character Extended Display Call Waiting Indicator Mandatory Control Tags and Display Text Tags Presentation Indicators Information Record Types (base station)

289.12.3 Call Flow Example(s)

29None

309.12.4 Method of Measurement 31 32 33 34

a. Ensure the mobile station has been configured to display Calling Party Name if it is delivered and that the mobile station has not been pre-programmed with calling name/number information (phone book). Power on the mobile station and wait until it reaches Mobile Station Idle State.

b.

11

1 1 2 3 4 5 6 7 8
c. d. Set up a mobile station terminated call.

3GPP2 C.S0044-A v1.0

Configure the base station to send a Feature Notification Message, Alert With Information Message, or a Flash With Information Message with an Extended Display information record with DISPLAY_TAG = 10001101 (Calling Party Name) CPN. Verify the mobile station receives and displays the information included in the Extended Display Information Record. Verify user data in both directions. End call.

e. f. g.

99.12.5 Minimum Standard

10The mobile station shall comply with steps e, and f.

119.13 Calling Name Presentation (CNAP) during Conversation State 129.13.1 Definition
13This test will verify that the mobile station in Conversation Substate (with call waiting enabled) 14properly displays the Calling Party Name. This test is only applicable to mobile stations capable 15of displaying information sent by the base station..

169.13.2 Traceability
17(see [4])

183.7.5.16 193.7.5.21 203.7.5.22 21Table 3.7.5.16-2 22Table 2.7.4.4-1 23Table 3.7.5-1

Extended Display, Calling Party Name Multiple Character Extended Display Call Waiting Indicator Mandatory Control Tags and Display Text Tags Presentation Indicators Information Record Types (base station)

249.13.3 Call Flow Example(s)

25None

269.13.4 Method of Measurement 27 28 29 30 31 32

a. Ensure mobile station is assigned Calling Party Name Presentation Class-of-Service, and that the mobile station has not been pre-programmed with calling name/number information (phone book). Set up a mobile station originated call. While the mobile station is in the Conversation Substate, set up another call to the mobile station (i.e. call waiting). Configure the base station to send an Alert With

b. c.

12

13GPP2 C.S0044-A v1.0 1 2 3 4 5

d. e. Information Message or Flash With Information Message with an Extended Display Information Record with the DISPLAY_TAG = 10001101 (Calling Party Name). Verify the mobile station receives and displays the information included in the Extended Display Information Record. End both calls.

69.13.5 Minimum Standard

7The mobile station shall comply with step d.

89.14 Display Records sent in the Feature Notification Message. 99.14.1 Definition
10This test verifies that the mobile station displays Paging Channel and Forward Common Control 11Channel Display Information Records, Extended Display Information Records and Multiple 12Character Extended Display Records. This test also verifies that Display Information Records, 13Extended Display Information Records and Multiple Character Extended Display Records do not 14interfere with any other information records or features. This test is only applicable if the mobile 15station has a display.

169.14.2 Traceability
17(see [4])

182.6.2.4 192.6.10.1 203.7.2.3.2.12 213.7.3.3.2.3 223.7.3.3.2.14 233.7.5

Mobile Station Order and Message Processing Operation Alerting Feature Notification Message Alert with Information Message Flash with Information Message Information Records

249.14.3 Call Flow Example(s)

25None

269.14.4 Method of Measurement 27 28 29 30 31 32 33 34

a. b. Verify the mobile station is in Idle State. Instruct the base station to send a display record with no more than x characters where x is the maximum number of characters supported by the mobile stations display in a Feature Notification Message on the Paging Channel or Forward Common Control Channel. Upon receiving the Feature Notification Message, verify the mobile station displays characters as instructed in the Display Record contained in the Feature Notification Message.

c.

13

1 1 2 3 4 5 6 7 8 9 10
d.

3GPP2 C.S0044-A v1.0 Instruct the base station to send a new Display Record of with no more than x characters where x is the maximum number of characters supported by the mobile stations display in a Feature Notification Message. Upon receiving the Feature Notification Message, verify the mobile station displays the new characters as instructed in the Display Record and performs other information records contained in the Feature Notification Message. If supported by the mobile station and the base station, repeat steps b to e using the Extended Display Record. If supported by the mobile station and the base station, repeat steps b to e using the Multiple Character Extended Display Record.

e.

f. g.

119.14.5 Minimum Standard

12The mobile station shall comply with steps c, e, f and g.

139.15 Display Records Sent in the Flash With Information Message 149.15.1 Definition
15This test verifies that the mobile station displays Traffic Channel Display Information Records, 16Extended Display Information Records and Multiple Character Extended Display Records. This 17test also verifies that Display Information Records, Extended Display Information Records and 18Multiple Character Extended Display Records do not interfere with other information records or 19features. This test is only applicable if the mobile station has a display.

209.15.2 Traceability
21(See [4])

222.6.2.4 232.6.10.1 243.7.3.3.2.3 253.7.3.3.2.14 263.7.5

Mobile Station Order and Message Processing Operation Alerting Alert with Information Message Flash with Information Message Information Records

279.15.3 Call Flow Example(s)

28None

299.15.4 Method of Measurement 30 31 32 33

a. b. Setup a mobile station originated call. Instruct the base station to send a Display Record with no more than x characters where x is the maximum number of characters supported by the mobile stations display in a Flash With Information Message.

14

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12

c. Upon receiving the Flash With Information Message, verify the mobile station displays characters as instructed in the Display Record contained in the Flash with Information Message. Instruct the base station to send a new display record with no more than x characters where x is the maximum number of characters supported by the mobile stations display contained in the Flash with Information Message. Upon receiving the Flash With Information Message, verify the mobile station displays the new characters as instructed in the Display Record. If supported by the mobile station and the base station, repeat steps a to e using the Extended Display Record. If supported by the mobile station and the base station, repeat steps a to e using the Multiple Character Extended Display Record.

d.

e. f. g.

139.15.5 Minimum Standard

14The verifications in steps c and e in the traffic channel shall be successfully carried out for all 15forms of display records supported. When various information records are sent to the mobile 16station in the same message, the mobile station shall properly process all information records. If 17display records are not supported in the mobile station, there shall be no negative impact on any 18information records supported by the mobile station. There shall be no negative impact on any 19supported feature or call processing when display records are sent to the mobile station in the 20same message as other information records. 21If supported by the mobile station, the most current display record shall be displayed on the 22mobile station.

239.16 Display Records Sent in the Alert with Information Message 249.16.1 Definition
25This test verifies the mobile station displays Display Information Records, Extended Display 26Information Records and the Multiple Character Extended Display Record on the traffic channel. 27This test also verifies that Display Information Records, Extended Display Information Records 28and Multiple Character Extended Display Record do not interfere with other information records 29or features. This is only applicable if the mobile station has a display.

309.16.2 Traceability
31(See [4])

322.6.2.4 332.6.10.1 343.7.2.3.2.12 353.7.3.3.2.3 363.7.3.3.2.14 373.7.5

Mobile Station Order and Message Processing Operation Alerting Feature Notification Message Alert with Information Message Flash with Information Message Information Records

15

1 19.16.3 Call Flow Example(s)

2None

3GPP2 C.S0044-A v1.0

39.16.4 Method of Measurement 4 5 6 7 8 9 10 11 12 13 14

a. b. Setup a mobile station terminated call. Instruct the base station to send in an Alert With Information Message, a Display Record with no more than x characters where x is the maximum number of characters supported by the mobile stations display, and a Calling Party Number Record. Upon receiving the Alert With Information Message, verify the mobile station displays the characters as instructed in the display record or extended display record and displays the Calling Party Number in the Alert With Information Message. If supported by the mobile station and the base station, repeat steps a to c using the Extended Display Record. If supported by the mobile station and the base station, repeat steps a to c using the Multiple Character Extended Display Record.

c.

d. e.

159.16.5 Minimum Standard

16The verifications in step c in the traffic channel shall be successfully carried out for all forms of 17display records supported. When various information records are sent to the mobile station in the 18same message, the mobile station shall process all information records. If display records are not 19supported in the mobile station, there shall be no negative impact on information records 20supported by the mobile station. There shall be no negative impact on any supported feature, or 21on call processing when display records are sent to the mobile station in the same message as 22other information records. 23If supported by the mobile station, the most current display record shall be displayed on the 24mobile station.

259.17 TTY/TDD 269.17.1 Definition

27This test verifies the system ability to transfer TTY/TDD information in the forward and reverse 28link directions.

299.17.2 Traceability:
30(see [18,19 and 20])

319.17.3 Call Flow Example(s)

32None

339.17.4 Method of Measurement 349.17.4.1 Basic TTY/TDD Operation 35

a. Connect the mobile station as shown in Figure 9.18.4-1.

16

13GPP2 C.S0044-A v1.0

1

MS

MTO Um BS/MSC

TE2

Rn

MT2 Ai KEY PSTN W TE2L

Specific Network Entity Collective (Composite Entity) X Interface Reference Point

2 3

Figure 9.17.4-4

4The base station (Base Station) in this model represents the entire system infrastructure. It 5contains the transceiver equipment and Mobile Switching Center (MSC). 6Terminal Equipment (TE2) is TTY/TDD equipment connected either directly or indirectly to the 7Mobile Terminal (MT2) on the mobile station side of the connection. TE2 is TTY/TDD equipment 8connected to the PSTN on the land side. Subscripts "M" and "L" are added as needed to indicate 9mobile station side and land side TE2s, respectively. When combined in a single physical entity, 10TE2 and MT2 functionality is labeled MT0.

11 12 13 14 15 16 17 18 19 20 21

b. c.

Setup a mobile station originated TTY/TDD call. Verify characters typed at TE2M can be viewed at TE2L. Verify characters typed at TE2L can be viewed at TE2M. See Annex E: TTY/TDD Test Examples for Example character text. See Annex E For Example character text. Type a character sequence (AB ) repeatedly a minimum of 20 times at TE2L Verify characters are properly viewed at TE2M. Type a character sequence (AB) repeatedly a minimum of 20 times at TE2M Verify characters are properly viewed at the TE2L. Steps b through g may be repeated for all supported radio configurations. Repeat steps c through h using mobile station terminated TTY/TDD calls. Steps a through i may be repeated using all support baud rates.

d. e. f. g. h. i. j.

229.17.4.2 TTY/TDD File Transfer Operation 23 24 25 2

a. b. c. Setup the mobile station for TTY/TDD file transfer. Transfer the ASCII/Baudot file from TE2M to TE2L. Verify the PCER, CCER, and TCER is less than 1%.

17

1 1 2 3 4 5 6
d. e. f. g. h. i. Transfer the ASCII/Baudot file from TE2L to TE2M. Verify the PCER, CCER, and TCER is less than 1%. End the TTY/TDD call.

3GPP2 C.S0044-A v1.0

Steps a through f may be repeated for all supported radio configurations. Repeat steps b through g for mobile station terminated calls. Steps a through h may be repeated using all support baud rates.

79.17.4.3 Voice Carry Over (VCO) and Hearing Carry Over (HCO) Operation 8 9 10 11 12 13 14 15 16 17
a. b. c. d. e. f. g. h. i. Configure TE2M for VCO. Setup a mobile station originated TTY/TDD call. Verify outgoing messages can be spoken and incoming responses can be viewed. End the TTY/TDD call. Configure TE2M for HCO. Setup a mobile station originated TTY/TDD call. Verify outgoing messages can be typed and incoming responses can be heard through a TE2M accessory speaker. Verify characters typed at TE2M can be viewed at TE2L. End the TTY/TDD call.

189.17.5 Minimum Standard 199.17.5.1 Basic TTY/TDD Operation

20The mobile station shall comply with steps e and g for all tested and supported radio 21configurations and baud rates for mobile station originated and terminated calls.

229.17.5.2 TTY/TDD Operation File Transfer

23The mobile station shall comply with steps c and e for all tested and supported radio 24configurations and baud rates for mobile station originated and terminated calls.

259.17.5.3 Voice Carry Over (VCO) and Hearing Carry Over (HCO) Operation
26The mobile station shall comply with steps c, g and h.

279.18 WLL Call Waiting Indicator Support 289.18.1 Definition

29This test verifies that a mobile station in a two-way conversation, with call waiting enabled, will 30receive indicator of waiting calls. This test will verify that the mobile station will send a flash 31request to connect to the waiting call. This test case is applicable only if WLL is supported.

18

13GPP2 C.S0044-A v1.0 19.18.2 Traceability

2(see [4])

32.7.2.3.2.3 43.7.5.5 53.7.5.22

Flash with Information Message Signal Call Waiting Indicator

69.18.3 Call Flow Example(s)

7None

89.18.4 Method of Measurement 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33

e. a. b. c. d. Ensure call waiting is enabled. Make a mobile station to land party 1 voice call. Verify audio in both directions. Setup a voice call from land party 2 to the mobile station. Verify the base station sends a Flash With Information Message or Extended Flash With Information Message with the Call Waiting Indicator Information Record as follows: 1. CALL_WAITING_INDICATOR field set to 1. Press the hook (or FLASH button if available) in the mobile station to put land party 1 on hold and to connect to land party 2. Verify that the mobile station sends a Flash With Information Message or an Extended Flash With Information Message to the base station. Verify that no dial tone is generated in the mobile station. Verify that voice path is established between the mobile station and land party 2. Press the hook (or FLASH button if available) again in the mobile station to put land party 2 on hold, and reconnect the voice path to land party 1. Verify the mobile station sends a Flash With Information Message or Extended Flash With Information Message to the base station. Verify that voice path is established between the mobile station and land party 1. End the call from land party 1. Press hook (or FLASH button if available) again in the mobile station. Verify that the mobile station sends a Flash With Information Message or Extended Flash With Information Message to the base station. Verify voice path is established between the mobile station and land party 2. End the call to land party 2. Make a mobile station to land party 1 voice call. Verify audio path is established in both directions. Setup a voice call from land party 2 to the mobile station.

f. g. h. i. j. k.

l. m. n. o.

19

1 1 2 3 4 5 6 7 8 9 10 11 12 13
p.

3GPP2 C.S0044-A v1.0 Verify the base station sends a Flash With Information Message or Extended Flash With Information Message with the Call Waiting Indicator Information Record as follows: CALL_WAITING_INDICATOR field set to 1. Do not answer this call waiting call at the mobile station. Disconnect call from land party 2. Verify the base station sends a Flash With Information Message or Extended Flash With Information Message with the Call Waiting Indicator Information Record as follows: CALL_WAITING_INDICATOR field set to 0. Press the hook (or FLASH button if available) of the mobile station and verify that a dial tone is generated. Press the hook (or FLASH button if available) again and verify that voice path between the mobile station and land party 1 is established. End the call to land party 1.

q. r. s.

t. u. v.

149.18.5 Minimum Standard

15The mobile station shall comply with the requirements in the following steps: e, h, i, k, t and u. 16The base station shall comply with the requirements in the following steps: d, f, j, i, p, s, t and u. 17The base station shall send a Call Waiting Indicator to the mobile station during a two-way 18conversation indicating another call is waiting. The mobile station shall be able to switch between 19land party 1 and land party 2 by sending a flash request.

209.19 Answer Holding 219.19.1 Definition

22These tests verify that the mobile station that supports Answer Holding feature can perform the 23following:

24 25 26

a. b.

Activate answer holding when the incoming call is ringing in the Waiting for Mobile Station Answer Substate or in the Conversation Substate Deactivate answer holding in the Conversation Substate

279.19.2 Traceability
28(see [4])

292.6.10.1.2 302.6.10.2 312.7.2.3.2.3 322.7.2.3.2.33 332.7.4.2 343.6.8.1.2

Waiting for Mobile Station Answer Substate Conversation Substate Flash with Information Message Extended Flash with Information Message Keypad Facility Waiting for Answer Substate

20

13GPP2 C.S0044-A v1.0 19.19.3 Call Flow Example(s)

2
MS General Page Message Page Response Message Extended Channel Assignment Message Service Connect Message Service Connect Completion Message AWI Message (ringing applied) Instruct the MS to activiate Answer Holding (Extended) Flash with Info (Keypad Facility Info Record) Connect Order Instruct the MS to deactivate Answer Holding (Extended) Flash with Info (Keypad Facility Info Record) BS

Initiate a call

Conversation FWI Message (Call Waiting) Instruct the MS to activiate Answer Holding Instruct the MS to disconnect the first call and deactivate Answer Holding (Extended) Flash with Info (Keypad Facility Info Record) (Extended) Flash with Info (Keypad Facility Info Record) Release Order Release Order Disconnect the call

3 49.19.4 Method of Measurement 5 6 7 8 9 10 11 12

a. b. c. d. Power on the mobile station and wait until it reaches Idle State. Setup a mobile station terminated call from land party 1. When the mobile station is ringing and ring back tone is applied to the audio path, instruct the mobile station to answer hold the call. Verify the mobile station sends a Flash With Information Message or an Extended Flash With Information Message in assured mode with a Keypad Facility information record with the CHARi field set to a pre-programmed feature code (i.e., Switch Control Code: 18*), which indicates Answer Holding.

21

1 1 2 3 4 5 6 7
e. f. g.

3GPP2 C.S0044-A v1.0 Verify the mobile station sends a Connect Order in assured mode. Instruct the mobile station to deactivate the answer holding. Verify the mobile station sends a Flash With Information Message or an Extended Flash With Information Message in assured mode with a Keypad Facility information record with the CHARi field set to a pre-programmed feature code (i.e., Switch Control Code: 18*), which indicates Answer Holding. Verify user data in both directions.

h.

89.19.5 Minimum Standard

9The mobile station shall comply with steps d, e, g and h.

109.20 User Selective Call Forwarding 119.20.1 Definition

12These tests verify that the mobile station that supports User Selective Call Forwarding can 13perform the following in both Waiting for Mobile Station Answer Substate and Conversation 14Substate:

15 16 17

a. b. c.

Forwarding incoming call to a pre-registered number Forwarding incoming call to a number stored in the mobile station Forwarding incoming call to network-based voice mail

189.20.2 Traceability
19(See [4])

202.6.10.1.2 212.6.10.2 222.7.2.3.2.3 232.7.2.3.2.33 242.7.4.2 253.6.8.1.2

Waiting for Mobile Station Answer Substate Conversation Substate Flash with Information Message Extended Flash with Information Message Keypad Facility Waiting for Answer Substate

269.20.3 Call Flow Example(s)

27None

289.20.4 Method of Measurement 299.20.4.1 User Selective Call Forwarding in the Waiting for Mobile Station Answer Substate 30 31 32
a. b. Power on the mobile station and wait until it reaches Idle State. Dial user selective call forwarding feature activation code, followed by the forward-to number, followed by SEND. Verify feature update confirmation at the mobile station.

22

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

c. d. e. Setup a mobile station terminated call from land party. When the mobile station is ringing and ring back tone is applied to the audio path, instruct the mobile station to forward the incoming call to the pre-registered number. Verify the mobile station sends a Flash With Information Message or an Extended Flash With Information Message in assured mode with a Keypad Facility information record with the CHARi field set to a pre-programmed feature code (i.e., Switch Control Code: 0*), which indicates User Selective Call Forwarding to a pre-registered number. Answer the call on the forwarded line, and verify the audio path. End call. Ensure the mobile station is in Idle State. Setup a mobile station terminated call from land party. When the mobile station is ringing and ring back tone is applied to the audio path, instruct the mobile station to forward the incoming call to voice mail. Verify the mobile station sends a Flash With Information Message or an Extended Flash With Information Message in assured mode with a Keypad Facility information record with the CHARi field set to a pre-programmed feature code (i.e. Switch Control Code: 17*) which indicates User Selective Call Forwarding to voice mail. Verify the call is forwarded to voice mail. Ensure the mobile station is in Idle State. Program a forward-to-number in the mobile station. Setup a mobile station terminated call from land party. When the mobile station is ringing, and ring back tone is applied to the audio path, instruct the mobile station to forward the incoming call to the number stored in the mobile station. Verify the mobile station sends a Flash With Information Message or an Extended Flash With Information Message in assured mode with a Keypad Facility information record with the CHARi field set to a pre-programmed feature code (i.e. Switch Control Code: 16*) plus the forward-to-number stored in the mobile station. Answer the call on the forwarded line, and verify the audio path.

f. g. h. i. j. k.

l. m. n. o. p.

q.

r.

309.20.4.2 User Selective Call Forwarding while in the Conversation Substate 31 32 33 34 35 36 37 2

a. b. c. d. Setup a call between mobile station and land party 1 and verify user data in both directions. Setup a call from land party 2 to the mobile station. Wait for ring back on land party 2 and the call waiting notification on the mobile station. Instruct the mobile station to forward the incoming call to the pre-registered number. Verify the mobile station sends a Flash With Information Message or an Extended Flash With Information Message in assured mode with a Keypad Facility information

23

1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
e. f. g. h. i. j.

3GPP2 C.S0044-A v1.0 record with the CHARi field set to a pre-programmed feature code (i.e., Switch Control Code: 0*), which indicates User Selective Call Forwarding to a pre-registered number. Answer the call on the forwarded line, and verify the audio path. End call. Setup a call between mobile station and land party 1 and verify user data in both directions. Setup a call from land party 2 to the mobile station. Wait for ring back on land party 2 and the call waiting notification on the mobile station. Instruct the mobile station to forward the incoming call to voice mail. Verify the mobile station sends a Flash With Information Message or an Extended Flash With Information Message in assured mode with a Keypad Facility information record with the CHARi field set to a pre-programmed feature code (i.e. Switch Control Code: 17*) which indicates User Selective Call Forwarding to voice mail. Verify the call is forwarded to voice mail. End call. Setup a call between mobile station and land party 1 and verify user data in both directions. Setup a call from land party 2 to the mobile station. Wait for ring back on land party 2 and the call waiting notification on the mobile station. Instruct the mobile station to forward the incoming call to the forward-to-number stored in the mobile station. Verify the mobile station sends a Flash With Information Message or an Extended Flash With Information Message in assured mode with a Keypad Facility information record with the CHARi field set to a pre-programmed feature code (i.e. Switch Control Code: 16*) plus the forward-to-number stored in the mobile station. Answer the call on the forwarded line, and verify the audio path. End call.

k. l. m. n. o. p.

q. r.

289.20.5 Minimum Standard 299.20.5.1 User Selective Call Forwarding in the Waiting for Mobile Station Answer Substate
30The mobile station shall comply with steps e, k, and q.

319.20.5.2 User Selective Call Forwarding while in the Conversation Substate

32The mobile station shall comply with steps d, j, and p. 33

24

13GPP2 C.S0044-A v1.0 110 ASYNCHRONOUS DATA AND FAX SERVICES 210.1 Send/Receive Fax 310.1.1 Definition
4These tests demonstrate cellular system ability to transmit and receive a medium size fax in a 5timely manner. A fax call is originated by the mobile station and the test is then repeated using 6land line origination. The mobile station will send and receive a digital and an analog Fax.

710.1.2 Traceability
8(see [15])

9A.3 10 112.2 122.2.1 134.0 144.3 157.3 16A.4 172.2 182.5.5 193.1 203.2 213.3 233.4.1 244.1.1 254.1.2 264.1.3 274.2

Data Service Options for Spread Spectrum Systems: AT Command Processing and the Rm Interface Data Service Selection Service Selection for Async Data and Fax Services AT COMMAND PROCESSING FOR ASYNC DATA AND FAX SERVICES Service Class 2.0 AT Commands Facsimile Service Class 2.0 AT Commands Data Service Options for Spread Spectrum Systems: Async Data and Fax Services The Application Interface Requirements for Async Data and Fax Service Option Number Multiplex Option Interface Procedures Using Service Option Negotiation

223.3.1.1 Mobile Station Requirements

Mobile Station Requirements Mobile Origination Mobile Termination Service Option Change to Group-3 Facsimile Service Connection Release

28A.7 Data Service Options for Spread Spectrum Systems: Analog Fax Service 2910.1.3 Call Flow Example(s)
30None

1 110.1.4 Method of Measurement 210.1.4.1 Send/Receive Digital Fax 3 4 5 6 7 8 9 10 11 12 13 14 15

a.

3GPP2 C.S0044-A v1.0

Prepare a file representing three different ITU standard fax pages for fax transfer. Data Services Annex C lists standard fax pages to be used in the test. Ensure fax pages are pre-scanned and pre-encoded. Simultaneously start the transfer timer and the digital fax transfer from TE2M to TE2L. At TE2L, wait for the fax call to be completed. Stop the transfer timer. Record transfer time. Verify transfer time requirements per Data Services Annex C. Repeat the test for the same fax sent from TE2L to TE2M. TE2M will receive a digital fax. Verify all faxes shall be successfully transferred. The received fax shall be of good quality and complete. This can be verified by qualitative means (visually scanning the received fax) or by quantitative means, for example, using ITU-T Recommendation E.453 (08/94) Facsimile Image Quality as Corrupted by Transmission Induced Scan Line Errors.

b. c. d. e. f.

1610.1.4.2 Send/Receive Analog Fax 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

a. Prepare a file representing three different ITU standard fax pages for fax transfer. Data Services Annex C lists standard fax pages to be used in the test. Ensure fax pages are pre-scanned and pre-encoded. Attach an Analog Fax Machine to TE2M. Simultaneously start the transfer timer and the analog fax transfer from TE2M to TE2L. At TE2L, wait for the fax call to be completed. Stop the transfer timer. Record transfer time. Verify transfer time requirements per Data Services Annex C. Repeat test for the same fax sent from TE2L to TE2M. TE2M will receive an analog fax. Verify all faxes shall be successfully transferred. The received fax shall be of good quality and complete. This can be verified by qualitative means (visually scanning the received fax) or by quantitative means, for example, using ITU-T Recommendation E.453 (08/94) Facsimile Image Quality as Corrupted by Transmission Induced Scan Line Errors. Verify each analog fax transfer shall be completed within time denoted in Data Services Annex C.

b. c. d. e. f. g.

h.

3210.1.5 Minimum Standard 3310.1.5.1 Send/Receive Digital Fax

34The mobile station shall comply with steps d and f.

13GPP2 C.S0044-A v1.0 110.1.5.2 Send/Receive Analog Fax

2The mobile station shall comply with steps e, g, and h.

310.2 Upload/Download Binary File 410.2.1 Definition

5This test demonstrates cellular system ability to upload and download an ITU standard fax binary 6file in a timely manner. The asynchronous data call is originated first by the mobile station. The 7test is then repeated using land line origination.

810.2.2 Traceability
9(see [15])

10A.3 Data Service Options for Spread Spectrum Systems: AT Command Processing and the Rm 11Interface 122.2 132.2.1 144.0 154.3 167.3 17A.4 182.2 192.5.5 203.1 213.2 223.3 243.4.1 254.1.1 264.1.2 274.1.3 284.2
Data Service Selection Service Selection for Async Data and Fax Services AT COMMAND PROCESSING FOR ASYNC DATA AND FAX SERVICES Service Class 2.0 AT Commands Facsimile Service Class 2.0 AT Commands Data Service Options for Spread Spectrum Systems: Async Data and Fax Services The Application Interface Requirements for Async Data and Fax Service Option Number Multiplex Option Interface Procedures Using Service Option Negotiation

233.3.1.1 Mobile Station Requirements

Mobile Station Requirements Mobile Origination Mobile Termination Service Option Change to Group-3 Facsimile Service Connection Release

2910.2.3 Call Flow Example(s)

30None

1 110.2.4 Method of Measurement 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

f. g. h. i. a. b. c. d. e.

3GPP2 C.S0044-A v1.0

Prepare the RAND200.BIN 200,000 byte binary file for transfer (Data Services Annex D). Setup a data call from TE2M to TE2L. Start transferring the binary file from TE2L to TE2M using Z-modem transfer protocol. Start the transfer timer. Stop the transfer timer when the confirmation of transfer completion is received from the far end. Record the transfer time. 1. Note: Transfer time should exclude call connection delay.

End the data call. Setup a data call from TE2L to TE2M. Repeat the test by transferring the file from TE2M to TE2L. Verify: 1. All files shall be successfully transferred. 2. Received files shall be complete and identical in content to the original file. 3. Each file transfer shall be completed within time denoted in Data Services Annex D. 4. Both the mobile station originated, and land line originated data calls shall be established successfully.

2110.2.5 Minimum Standard

22The mobile station shall comply with step i.

2310.3 Simultaneous Two-way File Transfer/Carrier Detect 2410.3.1 Definition

25This test demonstrates cellular system ability to simultaneously transfer data in the forward and 26reverse link direction. This test verifies the base station can transmit changes in the status of 27Carrier Detect and reflect its status on the Rm interface. 28Note: Carrier Detect can be monitored by means of a hardware lead, or observed on the 29application interface.

3010.3.2 Traceability
31(see [15])

32A.3 33 342.2

Data Service Options for Spread Spectrum Systems: AT Command Processingand the Rm Interface Data Service Selection

13GPP2 C.S0044-A v1.0 12.2.1 24.0 34.3 47.3 5A.4 62.2 72.5.5 83.1 93.2 103.3 123.4.1 134.1.1 144.1.2 154.1.3 164.2
Service Selection for Async Data and Fax Services AT COMMAND PROCESSING FOR ASYNC DATA AND FAX SERVICES Service Class 2.0 AT Commands Facsimile Service Class 2.0 AT Commands Data Service Options for Spread Spectrum Systems: Async Data and Fax Services The Application Interface Requirements for Async Data and Fax Service Option Number Multiplex Option Interface Procedures Using Service Option Negotiation

113.3.1.1 Mobile Station Requirements

Mobile Station Requirements Mobile Origination Mobile Termination Service Option Change to Group-3 Facsimile Service Connection Release

1710.3.3 Call Flow Example(s)

18None

1910.3.4 Method of Measurement 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 2

g. h. a. b. c. d. e. f. Prepare the RAND200.ASC 200,000 byte ASCII file for transfer (Data Services Annex D). Ensure the Carrier Detect indicator is enabled at TE2M. From TE2M, issue the command AT&C1, which requests the real-time status of Carrier Detect be maintained on the Rm interface. Verify the Carrier Detect indicator is OFF. Setup a data call from TE2M to TE2L. Verify that Carrier Detect indicator goes ON, when the base station modem has successfully trained. Verify characters typed at TE2M can be viewed at TE2L. Verify characters typed at TE2L can be viewed at TE2M. 1. Note: Once the File Capture is turned on, do not type any more characters on the TE2L or the TE2M prior to initiating the file transfer (this is to ensure the captured file is not corrupted by user keystrokes). Turn on the File Capture at TE2M. Turn on the File Capture at TE2L.

1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
k. l. m. n. o. i. j.

3GPP2 C.S0044-A v1.0 Simultaneously start the reverse link transfer timer and at TE2M send the RAND200.ASC file to TE2L by using Raw ASCII protocol. While TE2M is sending the file to TE2L, simultaneously start the forward link transfer timer and instruct TE2L to send the same ASCII file to TE2M using a Raw ASCII protocol. 1. Note: It is critical these transfers shall substantially overlap.

As each transfer completes, stop corresponding transfer timer and record transfer time. After both transfers are complete, turn off the File Capture at both TE2M and TE2L. End call. At TE2M, verify that Carrier Detect indicator goes OFF when the call is ended. Verify: 1. The file shall be successfully transferred in each direction. 2. Log files shall be complete and identical in content to the original files. 3. Each file transfer shall be completed within time denoted in Data Services Annex D. 4. The Carrier Detect generated by the base station shall be accurately depicted on the Rm interface.

1810.3.5 Minimum Standard

19The mobile station shall comply with steps d, e, f, n, and o.

2010.4 Compound AT Command, Initialization and Connection Delay 2110.4.1 Definition

22This test verifies the base station can properly process a compound command line containing 23both local and remote commands. This test verifies the mobile station can initialize and connect 24the service option when the data call is negotiated with the base station, as well as measures 25connection delay.

2610.4.2 Traceability
27(see [15])

28A.3 29 304.2.6 324.3.1.2.5 334.4.1 34Table 7.2-1 2

Data Service Options for Spread Spectrum Systems: AT Command Processing and the Rm Interface Basic Result Codes

31Table 4.2.6-1. Result Code Sources

+FMI, +FMM, +FMR General Requirements Extended AT Configuration Commands

13GPP2 C.S0044-A v1.0 1Table 7.3.1-1

Fax Parameters

210.4.3 Call Flow Example(s)

3None

410.4.4 Method of Measurement 5 6 7 8 9 10 11 12 13 14

a. b. Ensure the call is down. At TE2M, issue AT command AT+CXT=1;+FCLASS=2.0;+GMI;+CGMI;+GMM; +CGMM. This command string requests mobile station manufacturer information, base station modem manufacturer information, mobile station manufacturer model, and base station modem manufacturer model. Start the connection delay timer. When the result is returned to the mobile station, stop the connection timer. Record connection delay time in the test report. Verify the response shall be correct in that it contains the information requested in the command, and is followed by result code OK. Delay should not exceed ten seconds.

c. d. e. f.

1510.4.5 Minimum Standard

16The mobile station shall comply with step f.

1710.5 Escaping to Command Mode 1810.5.1 Definition

19This test verifies:

20 21 22 23 24

a.

The MT2 application interface escapes to online command state when the user (or the communications application) issues an escape sequence (such as "+++" with the appropriate guard time). The base station returns to online state when the user (or the application) issues the command "ATO".

b.

2510.5.2 Traceability
26(see [15])

274.2.4 284.4.2.1

Call-Control Command Processing Return to Online Command State

2910.5.3 Call Flow Example(s)

30None

3110.5.4 Method of Measurement 32

a. Setup a data call from TE2M to TE2L.

1 1 2 3 4 5 6 7 8 9 10
b. c. d. e. f. g.

3GPP2 C.S0044-A v1.0 Verify characters typed at TE2M can be viewed at TE2L. Verify that characters typed at TE2L can be viewed at TE2M. From TE2M issue the escape sequence +++. Verify OK is returned, signifying that the MT2 is in the online command state. At TE2M,issue the command AT+CGMI" which requests base station manufacturer information. Verify the response is appropriate, with trailing OK. At TE2M, issue the command ATO, which should cause the MT2 to transition from online command state to online state. Verify characters typed at TE2M can be viewed at TE2L. Verify characters typed at TE2L can be viewed at TE2M.

1110.5.5 Minimum Standard

12The mobile station shall comply with steps b, d, e and g.

1310.6 Air Interface Data Compression 1410.6.1 Definition

15This test verifies successful compression option negotiation and the transfer of compressible files 16and/or faxes between the MT2 and Inter-Working Function (IWF). The aforementioned is verified 17for both mobile station originated and mobile station terminated data and fax transmissions. 18Note: Although the files are compressible, they will be compressed only when both the MT2 19and IWF support the type of compression in question. Even if the MT2 or IWF do not support a 20certain type of compression, the test in question may be performed to ensure MT2 and IWF still 21interoperate correctly when the user requests this type of compression.

2210.6.2 Traceability
23(see [15])

24A.3 25 26Table 7.4.1-1 27A.4 282.2 29Table 2.2-2 30Table 2.2-3

Data Service Options for Spread Spectrum Systems: AT Command Processing and the Rm Interface CDMA AT Parameter Commands

Data Service Options for Spread Spectrum Systems: Async Data and Fax Services The Application Interface Compression Options Group 3 Fax Compression Options

3110.6.3 Call Flow Example(s)

32None

13GPP2 C.S0044-A v1.0 110.6.4 Method of Measurement 2 3 4 5 6 7 8 9

Test No. 1 2 3 4 5 6 7 8 9 10 File/Fax Compression Method none V.42bis V.42bis V.42bis none V.42bis V.42bis V.42bis MMR MMR a. b. Prepare the data file, COMPFILE.RAW (see Data Services Annex A), or the fax page, FAX 1 (see Data Services Annex C) for transfer. Configure the test setup for transfer of a data file or a fax file per Table 10.6.4-39. V.42bis compression for data file transfers is controlled by the +CDS command. The type of compression for fax file transfers is controlled by the +CFC command. When V.42bis is selected for fax transfer, the parameters set in the +CDS command are used. Setup a mobile station originated fax or async data call per Table 10.6.4-39. Table 10.6.4-39 Direction of Transfer BS to MS BS to MS MS to BS MS to BS BS to MS BS to MS MS to BS MS to BS BS to MS MS to BS Compression Enable +CDS=0 +CDS=2 +CDS=1 +CDS=3 N/A +CDS=2 +CDS=1 +CDS=3 N/A N/A Fax Compression Mode N/A N/A N/A N/A +CFC=0 +CFC=1 +CFC=1 +CFC=1 +CFC=2 +CFC=2

c.

Data File Data File Data File Data File Fax File Fax File Fax File Fax File Fax File Fax File

10 11 12 13 14 15 16 17 18 19 20 21
d. e. f. Make a file or fax transfer in the direction as stated in Table 10.6.4-39. Time each transfer and record in the test report. Testing may be repeated for all test cases, 1 through 10. Verify: 1. 2. 3. 4. All faxes shall be successfully sent and received. The received fax page shall be complete in content, and each transfer shall be completed within the time stated in Data Services Annex C. All data files shall be successfully transferred. The received files shall be complete and identical in content to the original file. Each file transfer shall be completed within the time stated in Data Services Annex B.

1 110.6.5 Minimum Standard

2The mobile station shall comply with step f.

3GPP2 C.S0044-A v1.0

310.7 RLP Operation in a Poor RF Environment 410.7.1 Definition

5This test exercises the Radio Link Protocol (RLP) layer's negative acknowledgments (NAKs), re6transmits, RLP aborts, RLP Resets, and FCSs. 7Test conditions are intended to impose one or more occurrences of the following.

8 9 10 11

a. b. c. d.

Single, double, and triple NAK RLP retransmit events. RLP Abort RLP Reset This test verifies that RLP recovers erased data frames in various channel conditions.

1210.7.2 Traceability
13(see [15])

14A.2 153.1 173.1.2 183.1.4

Data Service Options for Spread Spectrum Systems: Radio Link Protocol Non-Transparent RLP Procedures

163.1.1.1 Non-Encrypted Mode Initialization/Reset

Data Transfer Segmentation of Retransmitted Data Frames

1910.7.3 Call Flow Example(s)

20None

2110.7.4 Method of Measurement 22 23 24 25 26 27 28 29 30 31 32 33 2

a. b. c. d. e. f. g. h. Setup the mobile station and base station as shown in Figure A-9with an AWGN generator placed in the forward link. Environment Test Parameters Adjust the level of the AWGN Generator so that the downlink frame error rate is measured to be 31%. Restore the RF link to a normal operating condition, maintaining the target frame error rate (1 % or less). Prepare RAND200.ASC 200,000 byte ASCII file for transfer (Data Services Annex D). Setup a data call from TE2M to TE2L. Verify characters typed at TE2M can be viewed at TE2L. Verify characters typed at TE2L can be viewed at TE2M. Turn File Capture on. 10

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

i. j. Simultaneously start the forward link transfer timer and at TE2L send the RAND200.ASC file to TE2M by using Raw ASCII protocol. As soon as the file transfer has started (and is still in progress), set the channel conditions as calibrated in step b. These channel conditions shall be maintained for the duration of the file transfer. Stop the transfer timer and record the transfer time. Turn off the File Capture. End call. Setup a data call from TE2M to TE2L. Repeat steps g and h. Simultaneously start the reverse link transfer timer and at TE2M send the RAND200.ASC file to TE2L by using Raw ASCII protocol. Repeat steps i through m. Verify: 1. The file shall be successfully transferred. 2. The log file shall be complete and identical in content to the original file. 3. The transfer rate shall be no less than 70% of rates measured in test 10.3.

k. l. m. n. o. p. q. r.

1810.7.5 Minimum Standard

19The mobile station shall comply with steps g and r.

2010.8 RLP Abort and TCP Retransmit Test 2110.8.1 Definition

22This test causes the RLP layer to abort and reset due to extremely severe CDMA channel 23conditions, and forces the TCP layer to retransmit packets. Channel degradation consists of 24forcing consecutive frame erasures for periods greater than 2.6 seconds. 25Note: 2.6 seconds corresponds to 130 consecutive frame erasures, but less than the time that 26would cause the call to drop (typically 5 seconds).

2710.8.2 Traceability
28(see [15])

29A.2 303.1 313.1.1.1 323.1.2 333.1.4

Data Service Options for Spread Spectrum Systems: Radio Link Protocol Non-Transparent RLP Procedures Non-Encrypted Mode Initialization/Reset Data Transfer Segmentation of Retransmitted Data Frames

11

1 110.8.3 Call Flow Example(s)

2None

3GPP2 C.S0044-A v1.0

310.8.4 Method of Measurement 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35

j. k. l. m. n. o. p. d. e. f. g. h. i. a. Setup the mobile station and base station as shown in Figures Annex A Figure A-7 and Annex A Figure A-8 for the forward and the reverse link tests respectively, with PWR_THRESH_ENABLE and PWR_PERIOD_ENABLE set to 0. Disable forward link power control at the base station. Calibrate the test setup so that: There is sufficient isolation with the switch open, that a call drops if the switch is left open for more than 5 seconds 1. When switch is open, the forward and reverse links are disabled at the receiver. 2. When switch is closed, the forward and reverse links are enabled at the receiver. 3. Set the RF link to normal operating condition, which maintains the target frame erasure rate (1% or less). Prepare the RAND200.ASC 200,000 byte ASCII file transfer (Data Services Annex D) Setup a call from TE2M to TE2L. Verify characters typed at TE2M can be viewed at TE2L. Verify that characters typed at TE2L can be viewed at TE2M. Turn File Capture on. Simultaneously start the forward link transfer timer and at TE2L send the RAND200.ASC file to TE2M by using Raw ASCII protocol. Once the file transfer has started (and is still in progress), open and close the switch in an alternating fashion, for periods of T1 and T2 where: 1. T1 is the period when the switch is open (RF link impaired), and it is anywhere between 2.6 and 5.0 seconds. 2. T2 is the period when the switch is closed (RF link restored), and it is a minimum of 10 seconds. Repeat opening and closing switch exactly three times while data transfer is occurring. Stop the transfer timer and record the transfer time. Turn the File Capture off. End call. Setup a data call from TE2M to TE2L. Repeat steps f and g. Simultaneously start the reverse link transfer timer and at TE2M send the RAND200.ASC file to TE2L by using Raw ASCII protocol.

b. c.

12

13GPP2 C.S0044-A v1.0 1 2 3 4 5

q. r. Repeat steps i through l. Verify: 1. The file shall be successfully transferred in each direction. 2. Log files shall be complete and identical in content to the original files. 3. Transfer rates shall be no less than 50% of rates measured in test 10.3.

610.8.5 Minimum Standard

7The mobile station shall comply with steps f and r.

810.9 Internet Control Message Protocol (ICMP) Requests/Replies 910.9.1 Definition

10This test verifies the mobile station is able to:

11 12 13 14 15

a. b. c.

Generate an ICMP Echo Response Message after receiving an Echo Request Message. Generate an ICMP Info Response Message after receiving an Info Request Message. Generate an ICMP Time Stamp Response Message after receiving a Time Stamp Request Message.

1610.9.2 Traceability
17(see [23])

18RFC-792 Internet Control Message Protocol 1910.9.3 Call Flow Example(s)

20None

2110.9.4 Method of Measurement 22 23 24 25 26 27 28 29 30 31 32 33 2

a. At TE2M, issue a remote query command such as AT+CXT=1;+FCLASS=2.0;+FMI?, requesting base station modem manufacturer information. This will establish a link to the base station. From the OA&M interface of the base station, issue the Echo Request Message by any method specific to the base station manufacturer. Optionally, step b may be repeated for Info Request/Response, or Time Stamp Request/Response Messages. Verify: 1. 2. Echo response shall be received by base station as a response to Echo Request Message. If supported by mobile station, an Info response shall be received by base station as a response to Info Request Message.

b. c. d.

13

1 1 2
3.

3GPP2 C.S0044-A v1.0 If supported by mobile station, a Time stamp response shall be received by base station as a response to Time Stamp Request Message.

310.9.5 Minimum Standard

4The mobile station shall comply with step d.

510.10 Reflection of AT Command Parameters 610.10.1 Definition

7This test verifies a representative set of AT parameters can be setup in an IS-707-A call, 8transferred to the base station at call origination, changed in the online command state, and have 9their final values read at the mobile station after call completion. Commands tested are ATS10 10and AT+CQD.

1110.10.2 Traceability
12(see [15])

13A.3 14 154.2.4 167.4.1

Data Service Options for Spread Spectrum Systems: AT Command Processing and the Rm Interface Call-Control Command Processing CDMA AT Parameters

1710.10.3 Call Flow Example(s)

18None

1910.10.4 Method of Measurement 20 21 22 23 24 25 26 27 28 29 30 31 32

h. i. j. a. b. c. d. e. f. g. Issue the following AT commands: ATS10=255 and AT+CQD=0 Verify response is OK Setup a data call from TE2M to TE2L. After CONNECT is received, issue the escape sequence (such as +++). Verify the response is OK Issue the following AT commands: ATS10? and AT+CQD?. Verify response is: 1. 255 2. +CQD:0 3. OK Issue the following AT commands: ATS10=250 and AT+CQD=100 Verify the response is OK Issue the following AT commands: ATS10? and AT+CQD?.

14

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12

p. l. m. n. o. k. Verify the response is: 1. 250 2. +CQD: 100 3. OK Terminate the call via the ATH0 command string. Verify the response is OK and that the call ends. Issue the following AT commands: ATS10? and AT+CQD Verify response is: 1. 250 2. +CQD: 100 3. OK Verify the ERROR response shall not be returned.

1310.10.5 Minimum Standard

14The mobile station shall comply with steps b, e, g, i, k, m, o, and p. 15

15

1
1No text.

3GPP2 C.S0044-A v1.0

16

13GPP2 C.S0044-A v1.0 111 LOW SPEED PACKET DATA 211.1 Forward File Transfer 311.1.1 Definition
4This test verifies that file transfer from remote host to mobile station can be successfully done 5using the LSPD call.

611.1.2 Traceability
7(see [15])

81.4.2.2 92.2.2 102.2.3

Mobile Station Packet Data Service States Service and Call Control Procedures Initialization and Connection of Packet Data Service Options

1111.1.3 Call Flow Example(s)

12None

1311.1.4 Method of Measurement 14 15 16 17 18 19 20 21 22 23

a. b. c. d. e. f. Connect the mobile station to the base station as shown in Annex A Figure A-6. At the remote host prepare the RAND200.BIN 200,000 byte binary file for transfer (Data Services Annex D). Setup an FTP session using Service Option 7 for Rate Set 1 or Service Option 15 for Rate Set 2 with the remote host. Transfer the file from the remote host to the TE2M using the binary get command. After the file transfer is completed, end the FTP session. Verify the file is successfully transferred. Steps b through e may be repeated for other data rates supported by both mobile station and base station.

2411.1.5 Minimum Standard

25The mobile station shall comply with step e.

2611.2 Reverse File Transfer 2711.2.1 Definition

28This test verifies that file transfer from mobile station to remote host can be successfully done 29using the LSPD call.

3011.2.2 Traceability
31(see [15])

1 11.4.2.2 22.2.2 32.2.3 411.2.3

5None

3GPP2 C.S0044-A v1.0 Mobile Station Packet Data Service States Service and Call Control Procedures Initialization and Connection of Packet Data Service Options Call Flow Example(s)

611.2.4 Method of Measurement 7 8 9 10 11 12 13 14 15 16

a. b. c. d. e. f. Connect the mobile station to the base station as shown in Annex A Figure A-6. At the TE2M, prepare the RAND200.BIN 200,000 byte binary file for transfer (Data Services Annex D). Setup an FTP session using Service Option 7 for Rate Set 1 or Service Option 15 for Rate Set 2 with the remote host. Transfer the file from the TE2M to the remote host using the binary put command. After the file transfer is completed, end the FTP session. Verify the file is successfully transferred. Steps b through e may be repeated for other data rates supported by both mobile station and base station.

1711.2.5 Minimum Standard

18The mobile station shall comply with step e.

1911.3 Bi-directional File Transfer 2011.3.1 Definition

21This test verifies that bi-directional file transfer can be successfully done using the LSPD call.

2211.3.2 Traceability
23(see [15])

241.4.2.2 252.2.2 262.2.3

Mobile Station Packet Data Service States Service and Call Control Procedures Initialization and Connection of Packet Data Service Options

2711.3.3 Call Flow Example(s)

28None

2911.3.4 Method of Measurement 30

a. Connect the mobile station to the base station as shown in Annex A Figure A-6.

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11

b. c. d. e. f. g. Prepare the RAND200.BIN 200,000 byte binary file for transfer (Data Services Annex D) at both the remote host and TE2M. Setup an FTP session using Service Option 7 for Rate Set 1 or Service Option 15 for Rate Set 2 with the remote host. Transfer the file from the TE2M to the remote host. Transfer the file from the Remote Host to the TE2M while the transfer in the reverse direction is still proceeding. After the file transfers are completed, end the FTP sessions. Verify the files are successfully transferred. Steps b through f may be repeated for different data rates that are supported by both mobile station and base station.

1211.3.5 Minimum Standard

13The mobile station shall comply with step f.

1411.4 Mobile Station Packet Data Inactivity Timer 1511.4.1 Definition

16This test is required for mobile stations that shall have a mobile station packet data inactivity 17timer. This test verifies the mobile station releases the traffic channel after expiration of the 18mobile station packet data inactivity timer. The test verifies the dormant link layer connection can 19be re-activated.

2011.4.2 Traceability 2111.4.3 Call Flow Example(s)

22None

2311.4.4 Method of Measurement 24 25 26 27 28 29 30 31 32 33

a. b. c. d. e. f. g. h. Set the packet data inactivity timer at the MT2 to 20 seconds. Ensure the base station packet data inactivity timer is disabled or set to a value of at least 30 seconds. Initiate a Telnet session to a remote host. Record the IP address assigned to the mobile station. Exit the Telnet session. Wait for the mobile station packet data inactivity timer to expire. Verify the in use indicator on the MT2 goes OFF. Initiate a Telnet session to a remote host. Record the IP address assigned to the mobile station.

1 1 2 3 4
i. j.

3GPP2 C.S0044-A v1.0 Wait for the mobile station packet data inactivity timer to expire. Verify the in use indicator on the MT2 goes OFF. Issue a ping command from the remote host to the mobile station using the IP address assigned to the mobile station.

511.4.5 Minimum Standard

6The mobile station shall comply with steps f and i.

13GPP2 C.S0044-A v1.0 112 MEDIUM SPEED PACKET DATA 212.1 Forward File Transfer with Fundamental and Supplemental Code Channels 312.1.1 Definition
4This test verifies the functionality of forward MSPD calls for various MUX options:

5 6 7 8

No Supplemental Code Channels allocated (Test 1). One Supplemental Code Channel allocated (Test 2). N Supplemental Code Channels allocated, where N is the maximum number of Supplemental Code Channels that can be supported by the system (Test 3).

912.1.2 Traceability:
10(see [2]) 112.2.1.1.1.1.1 12(see [4]) 133.6.6.2.2.9 143.6.6.2.2.10 15(see [15]) 16A-9; 2.2.2.1.1

The Multiplex Sublayer Processing the Supplemental Channel Assignment Message Processing the General Handoff Direction Message Packet Data Service Control Procedures

1712.1.3 Call Flow Example(s)

18None

1912.1.4 Method of Measurement 20 21 22 23 24 25 26 27 28 29 30 31 32 33 2

c. a. Prepare a file at the remote host for file transfer (see Annex D). b. Setup an FTP session using Service Option 22 with the remote host. From the base station, generate a General Handoff Direction Message or a Supplemental Channel Assignment Message to allocate Supplemental Code Channels to the mobile station according to the following conditions: 1) For Test 1, the base station shall allocate no Supplemental Code Channel to the mobile station (i.e. MUX Option = 1). 2) For Test 2, the base station shall allocate one Supplemental Code Channel to the mobile station (i.e. MUX Option = 3). 3) For Test 3, the base station shall allocate N Supplemental Code Channels to the mobile station (i.e. MUX Option = 2N+1). Transfer the file from the remote host to the TE2M using the binary get command.

d. Verify the file is successfully transferred. e. After the file transfer is completed, end the FTP session

1 1 2
f. Repeat steps b through e for Tests 2 and 3.

3GPP2 C.S0044-A v1.0

g. Repeat steps b through f for Tests 1, 2, and 3 with Service Option 25.

312.1.5 Minimum Standard

4Verify step d for all test cases.

512.2 Forward File Transfer with Variable Supplemental Code Channels 612.2.1 Definition
7This test verifies the capability to transfer files from a remote host using FTP, with a variable 8number of Supplemental Code Channels. This test is intended to exercise bursty data transfer 9with variable peak transfer rates. 10This test may require the use of an OA&M interface on the base station, or any other method 11specific to the base station manufacturer, in order to vary the number of allocated Supplemental 12Code Channels.

1312.2.2 Traceability:
14(see [2]) 152.2.1.1.1 16(see [4]) 173.6.6.2.2.9 183.6.6.2.2.10 19(see [15]) 20A-9; 2.2.2.1.1

The Multiplex Sublayer Processing the Supplemental Channel Assignment Message Processing the General Handoff Direction Message Packet Data Service Control Procedures

2112.2.3 Call Flow Example(s)

22None

2312.2.4 Method of Measurement 24 25 26 27 28 29 30 31 32

a. Prepare a file at the remote host for file transfer (see Annex D). b. Configure the mobile stations maximum forward Supplemental Code Channels to N. c. Configure the base station to support N Supplemental Code Channels.

d. Setup a mobile station originated call with Service Option 22, and establish an FTP session. e. From the base station, generate a General Handoff Direction Message to allocate N Supplemental Code Channels to the mobile station. f. Verify from the mobile station that N Supplemental Code Channels are being used.

g. Transfer the file from the remote host to TE2M using the binary get command.

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6

h. During through the file transfer, configure the base station to generate a General Handoff Direction Message or a Supplemental Channel Assignment Message to reduce the number of Supplemental Code Channels allocated to the mobile station. i. j. k. Verify the file is successfully transferred. End FTP session. Repeat steps d through j with Service Option 25.

712.2.5 Minimum Standard

8Verify steps f and i for all test cases.

912.3 MSPD Call Setup, No Negotiation 1012.3.1 Definition

11This test verifies that the base station and the mobile station can successfully establish mobile 12station-originated and mobile station-terminated calls using all combinations of supported Service 13Option 22 and Service Option 25, using the default multiplex options.

1412.3.2 Traceability:
15(see [15])

16A9; 2.2.2.1.2.5
17(see [2]) 182.2.1.1.1

Dormant/Idle State The Multiplex Sublayer

1912.3.3 Call Flow Example(s)

20None

2112.3.4 Method of Measurement 22 23 24 25 26 27 28 29 30 31 32 33 2

a. Prepare a file at both the remote host and the TE2M (see Annex D). b. Configure the mobile stations forward MUX Option to (2N+1) where N is the maximum number of Supplemental Code Channels. c. Configure the base stations MUX Option to a value equal to (2N+1).

d. Setup a mobile station originated call with Service Option 22, and establish an FTP session with the remote host. e. Verify the call is completed with Service Option 22. f. Verify that N Supplemental Code Channels are being used by the mobile station.

g. Transfer the file from remote host to TE2M using the binary get command and verify the file is successfully transferred. h. After the file transfer is completed in step f, transfer the file from the TE2M to the remote host using the binary put command and verify the file is successfully transferred.

1 1 2 3 4 5 6 7 8 9 10 11
i. j. k. l. End FTP session.

3GPP2 C.S0044-A v1.0

Configure the base stations MUX Option to a value equal to (2N+2). Setup a mobile station originated call with Service Option 25, and establish an FTP session with the remote host. Verify the call is completed with Service Option 25.

m. Verify that N Supplemental Code Channels are being used by the mobile station. n. Transfer the file from remote host to TE2M using the binary get command and verify the file is successfully transferred. o. After the file transfer is completed in step o, transfer the file from the TE2M to the remote host using the binary put command and verify the file is successfully transferred. p. End the FTP session.

1212.3.5 Minimum Standard 13The mobile station shall comply with steps e, f, g, h, l, m, n and o. 1412.4 MSPD Call Setup, Negotiation to a Different MSPD Service Option 1512.4.1 Definition
16This test verifies that the base station and the mobile station can successfully negotiate from 17Service Option 22 to Service Option 25, and vice versa.

1812.4.2 Traceability:
19(see [15])

20A9; 2.2.2.1.2.5
21(see [2]) 222.2.1.1.1

Dormant/Idle State The Multiplex Sublayer

2312.4.3 Call Flow Example(s)

24None

2512.4.4 Method of Measurement 26 27 28 29 30 31 32

a. Prepare a file at both the remote host and the TE2M (see Annex D). b. Configure the mobile stations forward MUX Option to the default MUX Option. c. Configure the base stations Service Option to 25 and configure the base stations MUX Option to a value equal to or greater than the mobile stations MUX Option number.

d. Setup a mobile station originated call using Service Option 22, and establish an FTP session with the remote host. e. Verify the call is negotiated to Service Option 25.

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14

f. Transfer the file from the remote host to TE2M using the binary get command and verify the file is successfully transferred.

g. After the file transfer is completed in step f, transfer the file from the TE2M to the remote host using the binary put command and verify the file is successfully transferred. h. End FTP session. i. j. k. l. Configure the base stations Service Option to 22. Setup a mobile station originated call using Service Option 25 and establish an FTP session with the remote host. Verify the call is negotiated to Service Option 22. Transfer the file from the remote host to TE2M using the binary get command and verify the file is successfully transferred.

m. After the file transfer is completed in step l, transfer the file from the TE2M to the remote host using the binary put command and verify the file is successfully transferred. n. End FTP session.

1512.4.5 Minimum Standard 16The mobile station shall comply with steps e, f, g, k, l and m. 1712.5 MSPD Call Setup, Negotiation to LSPD 1812.5.1 Definition
19This test verifies that the base station and the mobile station can successfully negotiate from 20MSPD to LSPD service options.

2112.5.2 Traceability:
22(see [15])

23A9; 2.2.2.1.2.5
24(see [2]) 252.2.1.1.1

Dormant/Idle State The Multiplex Sublayer

2612.5.3 Call Flow Example(s)

27None

2812.5.4 Method of Measurement 2912.5.4.1 MSPD-Capable Mobile station 30 31 32 33 2

a. Prepare a file at both the remote host and the TE2M (see Annex D). b. Configure the base station to Service Option 7. c. Setup a mobile station originated call with Service Option 22, and establish an FTP session with the remote host. 5

1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
d. Verify the call is completed with Service Option 7.

3GPP2 C.S0044-A v1.0

e. Successively transfer files both directions and verify the files are successfully transferred. f. End FTP session.

g. Configure the base station to Service Option 15. h. Setup a mobile station originated call with Service Option 22, and establish an FTP session with the remote host. i. j. k. l. Verify the call is completed with Service Option 15. Successively transfer files in both directions and verify the files are successfully transferred. End FTP session. Configure the base station to Service Option 15.

m. Setup a mobile station originated call with Service Option 25, and establish an FTP session with the remote host. n. Verify the call is completed with Service Option 15. o. Successively transfer files in both directions and verify the files are successfully transferred. p. End FTP session. q. Configure the base station to Service Option 7 r. s. t. Setup a mobile station originated call with Service Option 25, and establish an FTP session with the remote host. Verify the call is completed with Service Option 7. Successively transfer files in both directions and verify the files are successfully transferred.

u. End FTP session.

2512.5.4.2 Non MSPD-Capable Mobile station 26 27 28 29 30 31 32 33 34

a. Ensure the mobile station is not MDR capable. b. Prepare a file at both the remote host and the TE2M. c. Configure the mobile station with Service Option 15. This can be accomplished by issuing the AT command AT+CMUX=2,2.

d. Configure the base station to page the mobile station with Service Option 22. e. Set up a mobile station terminated call and establish an FTP session. f. Verify the call is completed with Service Option 15.

g. Successively transfer files in both directions and verify the files are successfully transferred.

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7

h. End FTP session. i. j. k. l. Configure the base station Service Option to 25. Set up a mobile station terminated call and establish an FTP session. Verify the call is completed with Service Option 15. Successively transfer files in both directions and verify the files are successfully transferred.

m. End FTP session.

812.5.5 Minimum Standard

9In section 12.5.3.1, the mobile station shall comply with steps d, e, i, j, n, o, s and t. 10In section 12.5.3.2, the mobile station shall comply with steps f, g, k and l.

1112.6 MSPD Call Setup, Mobile Station Maximum Multiplex Option Less than Base Station 12 Maximum Multiplex Option 1312.6.1 Definition
14This test verifies that an MSPD call can be successfully established when the maximum multiplex 15option supported by the mobile station is less than the maximum multiplex option supported by 16the base station.

1712.6.2 Traceability:
18(see [15]) 19A9; 2.2.2.1.2.5 20A3; 7.4.1 21(see [2]) 222.2.1.1.1

Dormant/Idle State CDMA AT Parameters The Multiplex Sublayer

2312.6.3 Call Flow Example(s)

24None

2512.6.4 Method of Measurement 26 27 28 29 30 31 32 33

a. Prepare a file at both the remote host and the TE2M (see Annex D). b. Configure the mobile stations maximum forward MUX Option to (2n+1) where n is equal to N or 6, whichever is smaller, where N is the maximum number of Supplemental Code Channels supported by the mobile station (i.e. set AT+CMUX=2n+1,1) c. Configure the base stations MUX Option to a value equal to (2(n+1)+1).

d. Setup a mobile station originated call with Service Option 22, and establish an FTP session. e. Verify the number of Supplemental Code Channels used to establish FTP session is n.

1 1 2 3 4 5 6 7 8
f.

3GPP2 C.S0044-A v1.0 Transfer the file from the remote host to TE2M using the binary get command and verify the file is successfully transferred.

g. After the file transfer is completed in step f, transfer the file from the TE2M to the remote host using the binary put command verify the file is successfully transferred. h. End FTP session. i. Repeat steps d through h with Service Option 25 by setting the maximum forward MUX Option of the mobile station to (2n+2) and the MUX Option of the base station to (2(n+1)+2).

912.6.5 Minimum Standard

10The mobile station shall comply with steps e, f and g for all test cases.

1112.7 MSPD Call Setup, Mobile station Maximum Multiplex Option Greater than Base 12 Station Maximum Multiplex Option 1312.7.1 Definition
14This test verifies that an MSPD call can be successfully established when the maximum multiplex 15option supported by the mobile station is greater than the maximum multiplex option supported by 16the base station.

1712.7.2 Traceability:
18(see [15]) 19A3; 7.4.1 20A9; 2.2.2.1.2.5 21(see [2]) 222.2.1.1.1

CDMA AT Parameters Dormant/Idle State The Multiplex Sublayer

2312.7.3 Call Flow Example(s)

24None

2512.7.4 Method of Measurement 26 27 28 29 30 31 32 33 34

a. Prepare a file at both the remote host and the TE2M (see Annex D). b. Configure the mobile stations maximum forward MUX Option to (2N+1) where N is the maximum number of Supplemental Code Channels supported by the mobile station (i.e. set AT+CMUX=2N+1,1) c. Configure the base stations MUX Option to a value equal to (2(N-1)+1).

d. Setup a mobile station originated call with Service Option 22, and establish an FTP session. e. Verify the number of Supplemental Code Channels used in establishing the FTP session is (N-1).

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7

f. Transfer the file from the remote host to TE2M using the binary get command and verify the file is successfully transferred.

g. After the file transfer is completed in step f, transfer the file from the TE2M to the remote host using the binary put command and verify the file is successfully transferred. h. End FTP session. i. Repeat steps d through h with Service Option 25 by setting the maximum forward MUX Option of the mobile station to (2N+2) and MUX Option of the base station to (2(N-1)+2).

812.7.5 Minimum Standard

9The mobile station shall comply with steps e, f and g for all test cases.

1012.8 Allocation/De-allocation of Supplemental Code Channels 1112.8.1 Definition

12This test verifies allocation and de-allocation of up to N Supplemental Code Channels using the 13General Handoff Direction Message (GHDM), and Supplemental Code Channel Assignment 14Message (SCAM). N is the maximum number of forward Supplemental Code Channels that can 15be supported by the system. The first test uses n Supplemental Code Channels, where n is any 16number greater than zero and less than the maximum N. The second test uses the maximum N 17Supplemental Code Channels. This test also exercises all supported values of the 18FOR_SUP_CONFIG and USE_FOR_DURATION fields.

1912.8.2 Traceability:
20(see [2]) 212.2.1.1.1 22(see [4]) 233.6.6.2.2.9 243.6.6.2.2.10 25(see [15])

The Multiplex Sublayer Processing the Supplemental Channel Assignment Message Processing the General Handoff Direction Message

26A9; 2.2.2.1.1

Packet Data Service Control Procedures

2712.8.3 Call Flow Example(s)

28None

2912.8.4 Method of Measurement 3012.8.4.1 Allocation and De-Allocation of n Supplemental Code Channels using GHDM 31 32 33 34
a. Prepare a file at the remote host (see Annex D). b. Configure the mobile stations maximum forward MUX Option to (2N+1) where N is the maximum number of Supplemental Code Channels supported by the mobile station (i.e. set AT+CMUX=2N+1,1)

1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
c.

3GPP2 C.S0044-A v1.0 Setup a mobile station originated call with Service Option 22, and establish an FTP session.

d. Verify only the forward Fundamental Code Channel is used in establishing the FTP session. e. Configure the base station to send a General Handoff Direction Message with FOR_INCLUDED=1, FOR_SUP_CONFIG=3, USE_FOR_DURATION=0 and assign n forward Supplemental Code Channels (where n < N and n > 0) to the mobile station. f. Verify that n Supplemental Code Channels are being used by the mobile station.

g. Transfer the file from the remote host to TE2M using the binary get command and verify the file is successfully transferred. h. Configure the base station to send a General Handoff Direction Message with FOR_INCLUDED=1, FOR_SUP_CONFIG=3, USE_FOR_DURATION=0 and assign 0 forward Supplemental Code Channels to the mobile station. i. j. k. l. Verify that no Supplemental Code Channel is used by the mobile station. Transfer the file from the remote host to TE2M using the binary get command and verify the file is successfully transferred. End FTP session. Repeat steps c through k using Service Option 25.

1912.8.4.2 Allocation and De-Allocation of N Supplemental Code Channels using SCAM 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 2

a. Prepare the RAND200.BIN byte binary file at the remote host. b. Configure the mobile stations maximum forward MUX Option to (2N+1) where N is the maximum number of Supplemental Code Channels supported by the mobile station (i.e. set AT+CMUX=2N+1,1) c. Setup a mobile station originated call with Service Option 22, and establish an FTP session.

d. Verify that only the forward Fundamental Code Channel is used in establishing the FTP session. e. Configure the base station to send a Supplemental Code Channel Assignment Message with FOR_INCLUDED=1, FOR_SUP_CONFIG=3, USE_FOR_DURATION=0, USE_FOR_HDM_SEQ=0 and assign N forward Supplemental Code Channels to the mobile station. f. Verify that N Supplemental Code Channels are used by the mobile station.

g. Transfer the file from the remote host to TE2M using the binary get command and verify the file is successfully transferred. h. Configure the base station to send a Supplemental Code Channel Assignment Message with FOR_INCLUDED=1, FOR_SUP_CONFIG=3, USE_FOR_DURATION=0, USE_FOR_HDM_SEQ=0 and assign 0 forward Supplemental Code Channels to the mobile station.

10

13GPP2 C.S0044-A v1.0 1 2 3 4 5

i. j. k. l. Verify the number of Supplemental Code Channels used by the mobile station. Transfer the file from the remote host to TE2M using the binary get command and verify the file is successfully transferred. End FTP session. Repeat steps c through k using Service Option 25.

612.8.5 Minimum Standard

7For section 12.8.3.1, the mobile station shall comply with steps d, f, g, I, j and l. 8For section 12.8.3.2, the mobile station shall comply with steps d, f, g, I, j and l.

912.9 No Transmission on Supplemental Code Channels 1012.9.1 Definition

11This test verifies that data transfer is not interrupted if the base station stops transmitting on one 12or more allocated Supplemental Code Channels. Note that if the base station does not allow a 13Supplemental Code Channel to remain idle when there is no data to be transmitted on the 14Supplemental Code Channel, this test may require the use of an OA&M interface on the base 15station or some other method specific to the base-station manufacturer.

1612.9.2 Traceability:
17(see [2]) 182.2.1.1.1 The Multiplex Sublayer 19(see [4]) 203.6.6.2.2.9 Processing the Supplemental Channel Assignment Message 213.6.6.2.2.10 Processing the General Handoff Direction Message 22(see [15]) 23A9; 2.2.2.1.1 Packet Data Service Control Procedures

2412.9.3 Call Flow Example(s)

25None

2612.9.4 Method of Measurement 27 28 29 30 31 32 33 34 35 2

a. Prepare a file at the remote host (see Annex D). b. Configure the mobile stations maximum forward MUX Option to 5 or greater. c. Setup a mobile station originated call with Service Option 22, and establish an FTP session.

d. Configure the base station to send a General Handoff Direction Message or a Supplemental Code Channel Assignment Message with FOR_INCLUDED=1, FOR_SUP_CONFIG=3, USE_FOR_DURATION=0, USE_FOR_HDM_SEQ=0 and assign 2 forward Supplemental Code Channels to the mobile station. e. Verify the MUX Option used in establishing the FTP session.

11

1 1 2 3 4 5 6 7 8
9

3GPP2 C.S0044-A v1.0 f. Transfer the file from the remote host to TE2M using the binary get command and verify the file is successfully transferred.

g. Configure the base station to send data on the Fundamental Code Channel only while the 2 Supplemental Code Channels are still active. h. Transfer the file from the remote host to TE2M using the binary get command and verify the file is successfully transferred. i. j. End FTP session. Repeat steps c through i with Service Option 25.

1012.9.5 Minimum Standard

11The mobile station shall comply with steps e, f and h for all test cases.

1212.10 Soft Handoff with Supplemental Code Channels 1312.10.1 Definition

14This test verifies that the fundamental and Supplemental Code Channels can be put in two-way 15soft handoff during an MSPD call with N Supplemental Code Channels active, where N is the 16maximum number of Forward Supplemental Code Channels that can be supported by the 17system. This test includes the following cases: 18Fundamental Code Channel and Supplemental Code Channels in handoff, two cells transmit 19Supplemental Code Channels. 20Fundamental Code Channel in handoff, only one cell transmits Supplemental Code Channels.

2112.10.2 Traceability:
22(see [2]) 232.2.1.1.1 24(see [4]) 253.6.6.2.2.10

The Multiplex Sublayer Processing the General Handoff Direction Message Soft Handoff

263.6.6.2.4 27(see [15])

28A9; 2.2.2.1.1

Packet Data Service Control Procedures

2912.10.3 Call Flow Example(s)

30None

3112.10.4 Method of Measurement 32

a. Prepare a file at the remote host (see Annex D).

12

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

b. Configure the mobile stations maximum forward MUX Option to (2N+1) where N is the maximum number of forward Supplemental Code Channels available for the mobile station. c. Configure each base station to support N Supplemental Code Channels.

d. Setup a mobile station originated call with Service Option 22, and establish an FTP session with base station 1. e. Configure the base station to set up N Forward Supplemental Code Channels in traffic state. f. Begin transferring the file from the remote host to TE2M using the binary get command.

g. While the file is being transferred, adjust the signal strength of base station 2 until both base stations have equal transmit power. h. Generate a General Handoff Direction Message for two-way soft-handoff with base station 2. In both test cases 1 and 2, generate the GHDM with FOR_INCLUDED=1, FOR_SUP_CONFIG=3, NUM_FOR_SUP=N, and USE_FOR_DURATION=0. i. For Test 1: In the GHDM, set the FOR_SUP_INCLUDED=1 for each pilot to be included in handoff and configure both base stations to send data on all Supplemental Code Channels. For Test 2: In the GHDM, set the FOR_SUP_INCLUDED=1 for base station 1 and FOR_SUP_INCLUDED=0 for base station 2. Configure base station 1 to transmit data on all Supplemental Code Channels. Configure base station 2 to transmit data on the Fundamental Code Channel only. Verify the file transfer continues after the handoff and data is successfully transferred. End FTP session.

j.

k. l.

m. Repeat steps d through l with Service Option 25.

2512.10.5 Minimum Standard

26The mobile station shall comply with step k for all test cases.

2712.11 Adding Supplemental Code Channels during Soft Handoff 2812.11.1 Definition
29This test verifies that N Supplemental Code Channels can be added in an MSPD call while in 30two-way soft handoff on the Fundamental Code Channel, where N is the maximum number of 31Supplemental Code Channels that can be supported by the system. This test includes the 32following cases: 33 34

N Supplemental Code Channels added on all cells. N Supplemental Code Channels added on one cell only.

13

1 112.11.2 Traceability:
2(see [2]) 32.2.1.1.1 4(see [4]) 53.6.6.2.2.10

3GPP2 C.S0044-A v1.0

The Multiplex Sublayer Processing the General Handoff Direction Message Soft Handoff

63.6.6.2.4 7(see [15]) 8A9; 2.2.2.1.1

Packet Data Service Control Procedures

912.11.3 Call Flow Example(s)

10None

1112.11.4 Method of Measurement 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34

a. Prepare a file at the remote host (see Annex D). b. Configure the mobile stations maximum forward Supplemental Code Channels to N. c. Configure each base station to support N Supplemental Code Channels.

d. Setup a mobile station originated call with Service Option 22, and establish an FTP session with base station 1 on the Fundamental Code Channel only. e. Adjust the signal strength of base station 2 until both base stations have equal transmit power. f. Verify the mobile station is in two-way handoff.

g. Begin transferring the file from the remote host to TE2M using the binary get command. h. Generate a General Handoff Direction Message or a Supplemental Channel Assignment Message with FOR_INCLUDED=1, FOR_SUP_CONFIG=3, NUM_FOR_SUP=N, and USE_FOR_DURATION=0. i. For Test Case 1: In the GHDM, set the FOR_SUP_INCLUDED=1 for each pilot to be included in handoff and configure both base stations to send data on all Supplemental Code Channels. For Test Case 2: In the GHDM, set the FOR_SUP_INCLUDED=1 for base station 1 and FOR_SUP_INCLUDED=0 for base station 2. Configure base station 1 to transmit data on all Supplemental Code Channels. Configure base station 2 to transmit data on the Fundamental Code Channel only. Verify the file transfer continues after Supplemental Code Channel assignment during handoff and the file is transferred successfully. End FTP session.

j.

k. l.

m. Repeat steps d through l with Service Option 25.

14

13GPP2 C.S0044-A v1.0 112.11.5 Minimum Standard

2The mobile station shall comply with steps f and k for all test cases.

312.12 Hard Handoff to an MSPD-Capable System 412.12.1 Definition

5This test verifies hard handoff within the same P_REV system as well as hard handoff to a higher 6P_REV system.

712.12.2 Traceability:
8(see [2]) 92.2.1.1.1 10(see [4]) 113.6.6.2.2.10

The Multiplex Sublayer Processing the General Handoff Direction Message Soft Handoff

123.6.6.2.4 13(see [15])

14A9; 2.2.2.1.1

Packet Data Service Control Procedures

1512.12.3 Call Flow Example(s)

16None

1712.12.4 Method of Measurement 1812.12.4.1 Hard Handoff to Same P_REV 19 20 21 22 23 24 25 26 27 28 29 30 31 32

a. Prepare a file at the remote host (see Annex D). b. Make sure the MOB_P_REV=4 or higher. c. Base station 1 should be configured for P_REV=5 or higher.

d. Base station 2 should be configured for P_REV=5 or higher with a different frequency channel from base station 1. e. Configure the mobile stations maximum forward Supplemental Code Channels to N. f. Configure both base stations to support N Supplemental Code Channels.

g. Setup a mobile station originated call with Service Option 22 and establish an FTP session with base station 1 with N Supplemental Code Channels. h. Begin transferring the file from the remote host to TE2M using the binary get command. i. j. While the file is being transferred, adjust the signal strength of base station 2 until both base stations have equal transmit power. At base station 1, setup a hard handoff to base station 2 using the Extended Handoff Direction Message.

15

1 1 2 3 4 5 6 7 8 9 10
k. l.

3GPP2 C.S0044-A v1.0 Verify the hard handoff is successful and that only the Fundamental Channel is active. Verify that base station 2 generates a General Handoff Direction Message or a Supplemental Channel Assignment Message to assign N Supplemental Code Channels to the mobile station.

m. Verify at the base station that service negotiation is successful and that the mobile station is using Service Option 22 with N Supplemental Code Channels. n. Verify the file transfer continues after the hard handoff and the file is transferred successfully. o. End FTP session. p. Repeat steps g through o with Service Option 25.

1112.12.4.2 Hard Handoff to Higher P_REV 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

a. Prepare a file at the remote host (see Annex D). b. Make sure the MOB_P_REV=4 or higher. c. Base station 1 should be configured for P_REV=3.

d. Base station 2 should be configured for P_REV=5 or higher with a different frequency channel from base station 1. e. Configure the mobile stations maximum forward Supplemental Code Channels to N. f. Configure base station 2 to support N Supplemental Code Channels.

g. Setup a mobile station originated call with Service Option 7 and establish an FTP session with base station 1 h. Verify that Service Option 7 is in use and only the Fundamental Code Channel is active. i. j. k. l. Begin transferring the file from the remote host to TE2M using the binary get command. While the file is being transferred, adjust the signal strength of base station 2 until both base stations have equal transmit power. At base station 1, setup a hard handoff to base station 2 using the Extended Handoff Direction Message. Verify the hard handoff is successful.

m. Verify at the mobile station that Service Option 7 is still in use. n. Verify the file transfer continues after the hard handoff and the file is transferred successfully. o. End FTP session. p. Repeat steps g through n with Service Option 15.

3312.12.5 Minimum Standard

34For section 12.12.3.1, the mobile station and the base station shall comply with steps k, l, m, n 35and p.

16

13GPP2 C.S0044-A v1.0

1For section 12.12.3.2, the mobile station and the base station shall comply with steps h, l, m, n 2and p.

312.13 Bi-Directional File Transfers with Forward Supplemental Code Channels 412.13.1 Definition
5This test verifies the capability to transfer files simultaneously on the Forward and Reverse Traffic 6Channels between the mobile station and remote host using FTP, with forward Supplemental 7Code Channels active.

812.13.2 Traceability:
9(see [2]) 102.2.1.1.1 11(see [4]) 123.6.6.2.2.10

The Multiplex Sublayer Processing the General Handoff Direction Message Soft Handoff

133.6.6.2.4 14(see [15])

15A9; 2.2.2.1.1

Packet Data Service Control Procedures

1612.13.3 Call Flow Example(s)

17None

1812.13.4 Method of Measurement 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34

a. Prepare a file at both the remote host and the TE2M (see Annex D). b. Configure the mobile stations maximum forward Supplemental Code Channels to N. c. Configure the base station to support N Supplemental Code Channels.

d. Setup a mobile station originated call with Service Option 22. e. Establish two FTP sessions with the base station; one for the forward link and one for the reverse link. f. From the base station, generate a General Handoff Direction Message or a Supplemental Channel Assignment Message to allocate N Supplemental Code Channels to the mobile station.

g. Verify from the mobile station that N forward Supplemental Code Channels are being used. The reverse link should be connected with the Fundamental Code Channel only. h. Begin transferring the file from the remote host to TE2M using the binary get command. i. j. k. While the file is being transferred on the forward link, begin transferring another file from TE2M to the remote host on the reverse link using the binary put command. Verify that both files are transferred successfully. End two FTP sessions.

17

1 1
l. Repeat steps d through l with Service Option 25.

3GPP2 C.S0044-A v1.0

212.13.5 Minimum Standard

3The mobile station and the base station shall comply with steps g and j for all test cases.

412.14 R Interface Flow Control 512.14.1 Definition

6This test verifies flow control on the Rm Interface, when the Um interface data rate exceeds the Rm 7interface baud rate.

812.14.2 Traceability:
9(see [2]) 102.2.1.1.1 11(see [4]) 123.6.6.2.2.10

The Multiplex Sublayer Processing the General Handoff Direction Message Soft Handoff

133.6.6.2.4 14(see [15])

15A9; 2.2.2.1.1

Packet Data Service Control Procedures

1612.14.3 Call Flow Example(s)

17None

1812.14.4 Method of Measurement 19 20 21 22 23 24 25 26 27 28 29 30 31 32

a. Prepare a file at the remote host (see Annex D). b. Configure the mobile stations maximum forward Supplemental Code Channels to N (N > 4 for Service Option 22, N > 3 for Service Option 25). c. Configure the base station to support N Supplemental Code Channels.

d. Configure the RS-232 baud rate in the Rm interface to 4800 bps. e. Setup a mobile station originated call with Service Option 22, and establish an FTP session. f. From the base station, generate a General Handoff Direction Message or a Supplemental Channel Assignment Message to allocate N Supplemental Code Channels to the mobile station.

g. Verify at the mobile station that N Supplemental Code Channels are in use. h. Transfer the file from the remote host to TE2M using the binary get command. i. j. Verify the file is transferred successfully. End FTP session.

18

13GPP2 C.S0044-A v1.0 1

k. Repeat steps e through j with Service Option 25.

212.14.5 Minimum Standard

3The mobile station shall comply with steps g and i for all test cases.

412.15 Dormant Timer 512.15.1 Definition

6This test verifies the mobile station correctly processes the Service Option Control Message 7which controls the Dormant Timer, and that the mobile station delays any attempt to send an 8Origination Message requesting a MSPD service option until the Dormant Timer expires.

912.15.2 Traceability:
10(see [4]) 113.7.3.3.2.21 12(see [15]) 13A3; 7.4.1

Service Option Control Message CDMA AT Parameters

14A9; 2.2.2.1.2.5 Dormant/Idle State 1512.15.3 Call Flow Example(s)

16None

1712.15.4 Method of Measurement 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

a. Prepare a file at the remote host (see Annex D). b. Configure the mobile stations maximum forward Supplemental Code Channels to N. c. Configure the mobile stations inactivity timer to 20 seconds by issuing the AT command AT+CTA=20.

d. Configure the base station to support N Supplemental Code Channels. e. Setup a mobile station originated call with Service Option 22, and establish an FTP session. f. From the base station, generate a General Handoff Direction Message or a Supplemental Channel Assignment Message to allocate N Supplemental Code Channels to the mobile station.

g. From the base station, send the Service Option Control Message with the Packet Data Dormant Timer set to 20 seconds. h. Verify from the mobile station that N Supplemental Code Channels are being used. i. Transfer the file from the remote host to TE2M using the binary get command and verify the file is transferred successfully.

19

1 1 2 3 4 5 6 7 8 9 10
j. k.

3GPP2 C.S0044-A v1.0 Wait for the packet data service call control function to enter the Dormant State due to data inactivity (i.e. when the inactivity timer in the mobile station expires). Setup a mobile station originated call with Service Option 22, and establish an FTP session as soon as the packet data service call control function is in the Dormant State mode. The time elapsed between the Release Order and the Origination Message should be approximately 20 seconds. After the call is re-established, transfer the file from the remote host to TE2M using the binary get command and verify the file is transferred successfully.

l.

m. End FTP session. n. Repeat steps e through m with Service Option 25.

1112.15.5 Minimum Standard 12The mobile station shall comply with steps h, i and l. 1312.16 Packet Zone ID 1412.16.1 Definition
15This test verifies the following: 16When the mobile station detects a change in the Packet Zone ID in the Extended System 17Parameters Message and the new Packet Zone ID is not in the Packet Zone ID List the mobile 18station shall attempt to reconnect the packet data service option. 19While the data is being transferred and the base station sends a new Packet Zone ID to the 20mobile station in the Service Option Control Message, the mobile station shall continue to transfer 21files in the new Packet Zone ID. 22When the Dormant Timer is running and hasnot expired, the mobile station shall not re-originate a 23data call. 24

2512.16.2 Traceability:
26(see [4]) 273.7.3.3.2.21 28(see [15]) 29A9; 2.2.2.1.2.5 Dormant/Idle State 30A9; 2.2.2.1.2.6 Dormant/Traffic State

Service Option Control Message

3112.16.3 Call Flow Example(s)

32None

3312.16.4 Method of Measurement 3412.16.4.1 Mobile Station Idle State 35 2

a. Prepare a file at the remote host (see Annex D).

20

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

b. Configure the mobile stations maximum forward Supplemental Code Channels to N. c. Configure the base station to support N Supplemental Code Channels.

d. Configure the mobile stations inactivity timer to 20 seconds by issuing an AT command. e. Setup a mobile station originated call with Service Option 22, and establish an FTP session f. From the base station, generate a General Handoff Direction Message or a Supplemental Channel Assignment Message to allocate N Supplemental Code Channels to the mobile station.

g. Instruct the base station to send the Service Option Control Message to the mobile station to enable the PACKET_ZONE_ID with a valid list of PACKET_ZONE_Ids. Specify the number of packet data service identifiers that the mobile station is to retain in its packet data zone identifiers list (the number shall be set to 2 or greater). Also set the Packet Data Dormant Timer to 20 seconds. h. Verify from the mobile station that N Supplemental Code Channels are being used. i. j. k. l. Transfer the file from the remote host to TE2M using the binary get command. Make sure there is no data to transmit for 20 seconds. Verify the packet data service call control function enters the Dormant State and the mobile station enters the Mobile Station Idle State due to data inactivity. Change the PACKET_ZONE_ID of the serving system in the Extended System Parameter Message.

m. Verify the mobile station reconnects to the same Service Option when it detects the new PACKET_ZONE_ID. n. After the call is re-established, transfer the file from the remote host to TE2M using the binary get command and verify the file is transferred successfully. o. End FTP session. p. Repeat steps e through o with Service Option 25. q. Repeat steps a through f. r. s. t. Instruct the base station to send the Service Option Control Message to the mobile station to set the Dormant Timer to the maximum value. Repeat steps j through k. Attempt to initiate an ftp session to a server at the mobile station.

u. Verify the MS does not send an Origination Message before the Dormant Timer expires.

3312.16.4.2 Traffic Channel State 34 35 36 2

a. b. c. Prepare a file at the remote host (see Annex D). Configure the mobile stations maximum forward Supplemental Code Channels to N. Configure the base station to support N Supplemental Code Channels. 21

1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
d. e.

3GPP2 C.S0044-A v1.0 Setup a mobile station originated call with Service Option 22, and establish an FTP session From the base station, generate a General Handoff Direction Message or a Supplemental Channel Assignment Message to allocate N Supplemental Code Channels to the mobile station. From the base station, send a Service Option Control Message to the mobile station to enable the PACKET_ZONE_ID with a valid list of PACKET_ZONE_IDs. Verify from the mobile station that N Supplemental Code Channels are being used. Begin transferring the file from the remote host to TE2M using the binary get command. While the file is being transferred, send the Service Option Control Message to the mobile station with a change in the PACKET_ZONE_ID. Change the PACKET_ZONE_ID of the serving system in the In-Traffic System Parameter Message. Verify the mobile station continues file transfer on the new PACKET_ZONE_ID. End FTP session. Repeat steps d through l with Service Option 25.

f. g. h. i. j. k. l. m.

1712.16.5 Minimum Standard 1812.16.5.1 Mobile Station Idle State

19The mobile station shall comply with steps h, k m, n and u

2012.16.6 Traffic Channel State

21For section 12.16.3.2, the mobile station shall comply with steps g and k for all test cases. 22 23

22

13GPP2 C.S0044-A v1.0 113 HIGH SPEED PACKET DATA 213.1 Forward File Transfer 313.1.1 Definition
4This test verifies that file transfer from remote host to mobile station can be successfully done 5using the HSPD call.

613.1.2 Traceability
7(see [4])

82.7.2.3.2.18 92.7.2.3.2.28 103.6.6.2.2.12 113.7.3.3.2.24 123.7.5.7.1

13(see [15])

Supplemental Channel Request Message Supplemental Channel Request Mini Message Processing of Extended Supplemental Channel Assignment Message Supplemental Channel Assignment Message Channel Configuration for the Supplemental Channel

141.4.2.2 152.2.2 162.2.3 172.2.7

Mobile Station Packet Data Service States Service and Call Control Procedures Initialization and Connection of Packet Data Service Options High Speed Operation

1813.1.3 Call Flow Example(s)

19None

2013.1.4 Method of Measurement 21 22 23 24 25 26 27

a. b. c. d. Connect the mobile station to the base station as shown in Figure A-3. At the remote host prepare appropriate file (see Annex D) for data transfer11. Setup an FTP session using Service Option 33 with the remote host12. If supplemental channel is assigned, verify the base station sends a Universal Handoff Direction Message, an Extended Supplemental Channel Assignment Message, or a Forward Supplemental Channel Assignment Mini Message. Transfer the file from the remote host to the TE2M using the binary get command.

e.

211 The large FTP file size, coupled with a full constant buffer, is intended to trigger use of the 3 maximum data rate assignment supported by both mobile station and base station. 412 Ensure that sufficient Walsh code resources are available. 5
1

1 1 2 3 4 5 6
Table 13.1.4-1 SCH Data Rate Data Rate Granted (bps) F-RC3, 4 / R-RC3 F-RC6, 7 /R-RC5 9600 19200 38400 76800 153600 307200 614400 F-RC5 / R-RC4 F-RC8, 9 / R-RC6 14400 28800 57600 115200 230400 460800 1036800 f. g.

3GPP2 C.S0044-A v1.0 After the file transfer is completed, end the FTP session. Make sure the file is successfully transferred. Steps b through f may be repeated for other data rates and different radio configurations supported by both mobile station and base station.

7 813.1.5 Minimum Standard

9The mobile station shall comply with step f. The base station shall comply with step d.

1013.2 Reverse File Transfer 1113.2.1 Definition

12This test verifies that file transfer from mobile station to remote host can be successfully done 13using the HSPD call.

1413.2.2 Traceability
15(see [4])

162.7.2.3.2.18 172.7.2.3.2.28 183.6.6.2.2.12 193.7.3.3.2.24 203.7.5.7.1

21(see [15])

Supplemental Channel Request Message Supplemental Channel Request Mini Message Processing of Extended Supplemental Channel Assignment Message Supplemental Channel Assignment Message Channel Configuration for the Supplemental Channel

13GPP2 C.S0044-A v1.0 11.4.2.2 22.2.2 32.2.3 42.2.7 513.2.3

6None

Mobile Station Packet Data Service States Service and Call Control Procedures Initialization and Connection of Packet Data Service Options High Speed Operation Call Flow Example(s)

713.2.4 Method of Measurement 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

a. b. c. d. Connect the mobile station to the base station as shown in Figure A-3. At the TE2M prepare a file for data transfer. Setup an FTP session using Service Option 33 with the remote host. Transfer the file from the TE2M to the remote host using the binary put command. Ensure that the total amount of data to be transferred at the mobile station is more than an implementation defined threshold, or otherwise cause the mobile station to send a Supplemental Channel Request Message or a Supplemental Channel Request Mini Message with DURATION field set to a non-zero value. If supplemental channel is assigned, verify the base station sends a Universal Handoff Direction Message, an Extended Supplemental Channel Assignment Message, or a Reverse Supplemental Channel Assignment Mini Message. After the file transfer is completed, end the FTP session. Make sure that file is successfully transferred. Steps b through f should be executed for the maximum data rates13 supported by both mobile station and base station. Steps b through f may be repeated for other data rates and radio configurations supported by both mobile station and base station.

e.

f. g. h.

2513.2.5 Minimum Standard

26The mobile station shall comply with step f. The base station shall comply with step e.

2713.3 Bi-directional File Transfer 2813.3.1 Definition

29This test verifies that bi-directional file transfer can be successfully done using the HSPD call.

3013.3.2 Traceability
31(see [4])

322.7.2.3.2.18

Supplemental Channel Request Message

213 Make sure that transmit power is not limiting factor for maximum data rate assignment. 3
3

1 12.7.2.3.2.28 23.6.6.2.2.12 33.7.3.3.2.24 43.7.5.7.1

5(see [15])

3GPP2 C.S0044-A v1.0 Supplemental Channel Request Mini Message Processing of Extended Supplemental Channel Assignment Message Supplemental Channel Assignment Message Channel Configuration for the Supplemental Channel

61.4.2.2 72.2.2 82.2.3 92.2.7

Mobile Station Packet Data Service States Service and Call Control Procedures Initialization and Connection of Packet Data Service Options High Speed Operation

1013.3.3 Call Flow Example(s)

11None

1213.3.4 Method of Measurement 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

a. b. c. d. Connect the mobile station to the base station as shown in Figure A-3. Prepare a file at both the remote host and TE2M for data transfer. Setup an FTP session using Service Option 33 with the remote host. Transfer the file from the TE2M to the remote host. Ensure that the total amount of data to be transferred at the mobile station is more than an implementation defined threshold, or otherwise cause the mobile station to send a Supplemental Channel Request Message or a Supplemental Channel Request Mini Message with DURATION field set to a non-zero value. Transfer a file from the Remote Host to the TE2M while the transfer in the reverse direction is still proceeding. If forward supplemental channel is assigned, verify the base station sends a Universal Handoff Direction Message, an Extended Supplemental Channel Assignment Message, or a Forward Supplemental Channel Assignment Mini Message. If reverse supplemental channel is assigned, verify the base station sends a Universal Handoff Direction Message (can be same as one in step f), an Extended Supplemental Channel Assignment Message (can be same as one in step f), or a Reverse Supplemental Channel Assignment Mini Message. Verify that files in both directions are successfully transferred and end the FTP session. Steps c through f should be executed for the maximum forward14 and reverse15 data rates that are supported by both mobile station and base station.

e. f.

g.

h. i.

214 Make sure that conditions to trigger maximum forward data rate assignment are fulfilled; such 3as large enough FTP file size, sufficient Walsh code resource etc. 415 Make sure that transmit power is not limiting factor for maximum reverse data rate assignment. 5
4

13GPP2 C.S0044-A v1.0 1 2

j. Steps c through f may be repeated for different data rates and radio configurations that are supported by both mobile station and base station.

313.3.5 Minimum Standard

4The mobile station shall comply with step h. The base station shall comply with steps f and g. 5

613.4 Service Option Control Message Processing 713.4.1 Definition

8This test verifies the mobile station ability to process the Service Option Control Message. This 9test also verifies the mobile station is able to establish a voice call while the packet data session 10is dormant.

1113.4.2 Traceabilities
12(see [4])

132.6.4.3 143.6.4.3 153.7.3.3.2.21

16(see [15])

Traffic Channel Substate Traffic Channel Substate Service Option Control Message

172.2.2.1 182.2.2.2 192.2.4

Mobile Station Procedures Base Station Procedures Packet Data Dormant Timer Control

1 113.4.3 Call Flow Example(s)

MS Traffic BS Traffic

3GPP2 C.S0044-A v1.0

Data Call in Progress

Service Option Control Message Release Order General Page Msg with voice service option

MS packet service is dormant

Voice Call in Progress

Voice call ends

General Page Msg with packet data service option

Data Call may Resume

Traffic

Traffic

2 313.4.4 Method of Measurement 4 5 6 7

8

a. b. c.

Connect the mobile station in Figure A-3. Setup a mobile originated Service Option 33 call. While the data call is active, instruct the base station to send a Service Option Control Message with the following information:

13GPP2 C.S0044-A v1.0

Field SERVICE_OPTION DORM_CTRL FIELD_TYPE DORM_TIME Value 0000000000100001 001 011 11111111 (25.5 sec)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

d. e. f. g. h. i. j. k. l. m. n.

Instruct the base station to send a Release Order with ORDQ=0 to the mobile station. Verify the mobile station releases the call and the packet data session is in the dormant state. Before the DORM_TIME expires, send a General Page to the mobile station with a voice service option. Verify the call completes and user traffic is present. End the call before DORM_TIME expires. Set up a mobile originated voice call. Verify the call completes and user traffic is present. End the call before DORM_TIME expires. Insure the mobile station has sufficient data in its buffer. Verify the mobile station does not send an Origination Message for packet data service before the DORM_TIME expires. After DORM_TIME has expired, page the mobile station with a packet data service or otherwise cause the mobile station to send an Origination Message for a packet data service. Verify the call completes and user traffic is present.

o.

1813.4.5 Minimum Standard

19The mobile station shall comply with steps e, g, j, m and o.

2013.5 Changing Encoding Type on Supplemental Channel during Hard Handoff 2113.5.1 Definition
22This test verifies that the mobile station is capable of using turbo encoding and is capable of 23changing to convolutional encoding.

2413.5.2 Traceability
25(see [1])

262.1.3.1.4 273.1.3.1.4

Forward Error Correction Forward Error Correction

1
1(see [4])

3GPP2 C.S0044-A v1.0

22.7.2.3.2.18 33.7.3.3.2.36 43.7.3.3.2.37

Supplemental Channel Request Message Universal Handoff Direction Message Extended Supplemental Channel Assignment Message

513.5.3 Call Flow Example(s)

6None

713.5.4 Method of Measurement 813.5.4.1 R-SCH Turbo Encoding to Convolutional Encoding 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

a. b. c. d. Connect the mobile station to the base station as shown in Figure A-5. Ensure the mobile station supports turbo encoding and convolutional encoding. Setup a mobile originated Service Option 33 call. Instruct the base station to send a Service Connect Message with CODING=1 in the Service Configuration Record for the F-SCH and R-SCH (as supported by the mobile station). Verify the mobile station sends a Service Connect Completion Message. Initiate a data transfer from the mobile station and verify the mobile station sends a Supplemental Channel Request Message requesting a reverse supplemental channel. Instruct the base station to send an Extended Supplemental Channel Assignment Message assigning a reverse supplemental channel to the mobile station. While the data transfer is in progress, instruct the base station to send a Universal Handoff Direction Message with CODING=0 and a reverse supplemental channel burst assignment. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message. Verify the data transfer completes successfully using convolutional encoding. End the call from the mobile station.

e. f. g. h.

i. j. k.

2713.5.4.2 R-SCH Convolution Encoding to Turbo Encoding 28 29 30 31 32 33 34

a. b. c. d. Connect the mobile station to the base station as shown in Figure A-5. Ensure the mobile station supports turbo encoding and convolutional encoding. Setup a mobile originated Service Option 33 call. Instruct the base station to send a Service Connect Message with CODING=0 in the Service Configuration Record for the F-SCH and R-SCH (as supported by the mobile station). Verify the mobile station sends a Service Connect Completion Message.

e.

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12

f. g. h. Initiate a data transfer from the mobile station and verify the mobile station sends a Supplemental Channel Request Message requesting a reverse supplemental channel. Instruct the base station to send an Extended Supplemental Channel Assignment Message assigning a reverse supplemental channel to the mobile station. While the data transfer is in progress, instruct the base station to send a Universal Handoff Direction Message with CODING=1 and a reverse supplemental channel burst assignment. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message. Verify the data transfer completes successfully using turbo encoding (if the block size per frame is at least 360 bits).. End the call from the mobile station.

i. j. k.

1313.5.4.3 F-SCH Turbo Encoding to Convolutional Encoding 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

a. b. c. d. Connect the mobile station to the base station as shown in Figure A-5. Ensure the mobile station supports turbo encoding and convolutional encoding. Setup a mobile originated Service Option 33 call. Instruct the base station to send a Service Connect Message with CODING=1 in the Service Configuration Record for the F-SCH and R-SCH (as supported by the mobile station). Verify the mobile station sends a Service Connect Completion Message. Initiate a data transfer to the mobile station and verify the base station sends an Extended Supplemental Channel Assignment Message assigning a F-SCH. While the data transfer is in progress, instruct the base station to send a Universal Handoff Direction Message with CODING=0 and a forward supplemental channel burst assignment. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message. Verify the data transfer completes successfully using convolutional encoding. End the call from the mobile station.

e. f. g.

h. i. j.

3013.5.4.4 F-SCH Convolutional Encoding to Turbo Encoding 31 32 33 34 35 36 2

a. b. c. d. Connect the mobile station to the base station as shown in Figure A-5. Ensure the mobile station supports turbo encoding and convolutional encoding. Setup a mobile originated Service Option 33 call. Instruct the base station to send a Service Connect Message with CODING=0 in the Service Configuration Record for the F-SCH and R-SCH (as supported by the mobile station).

1 1 2 3 4 5 6 7 8 9 10 11
e. f. g.

3GPP2 C.S0044-A v1.0 Verify the mobile station sends a Service Connect Completion Message. Initiate a data transfer to the mobile station and verify the base station sends an Extended Supplemental Channel Assignment Message assigning a F-SCH. While the data transfer is in progress, instruct the base station to send a Universal Handoff Direction Message with CODING=1 and a forward supplemental channel burst assignment. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message. Verify the data transfer completes successfully using turbo encoding (if the block size per frame is at least 360 bits).. End the call from the mobile station. Minimum Standard

h. i. j.

1213.5.5

1313.5.5.1 R-SCH Turbo Encoding to Convolutional Encoding

14The mobile station shall comply with steps e, i, and j

1513.5.5.2 R-SCH Convolutional Encoding to Turbo Encoding

16The mobile station shall comply with steps e, i, and j.

1713.5.5.3 F-SCH Turbo Encoding to Convolutional Encoding

18The mobile station shall comply with steps e, h, and i.

1913.5.5.4 F-SCH Convolutional Encoding to Turbo Encoding

20The mobile station shall comply with steps e, h, and i.

2113.6 Control Hold Mode Transitions 2213.6.1 Definition

23This test applies when the mobile station and base station support Control Hold Mode. This test 24verifies that the mobile can go in and out of the Control Hold Mode in all the possible 25combinations. When the mobile station or the base station, trigger a transition to the Control Hold 26Mode, the expected signaling exchange takes place. Upon transition to the Control Hold Mode, 27the reverse pilot is gated at the specified gating rate DCCH is maintained with Power Control sub28channel and user traffic transmission is not allowed in either direction. When the mobile station 29and base station transition to the Active Mode, the expected signaling exchange takes place. 30Upon transition to the Active Mode, the reverse pilot transmission is continuous and user traffic 31transmission is allowed. 32The following are call flow examples for going in and out of Control Hold Mode. Either the mobile 33station or the base station can trigger either transition.

3413.6.2 Call Flow Example(s)

35

10

13GPP2 C.S0044-A v1.0

M S A c t iv e

BS

A c t iv e

E x t e n d e d R e le a s e ( M in i) M e s s a g e / U n iv e r s a l H a n d o f f D ir e c t i o n M e s s a g e

B S d e c id e s t o tra n s it io n t o C o n t r o l H o ld M o d e

A t th e a c t io n t im e : T r a n s it io n t o C o n t r o l H o ld M o d e & s t a r t r e v e r s e p il o t g a t i n g a t t h e s p e c if ie d g a t in g r a t e

E x te n d e d R e le a s e R e s p o n s e (M in i) M e s s a g e H a n d o f f C o m p le t io n M e s s a g e

C o n tr o l H o ld

C o n tr o l H o ld

1 2
3

Figure 13-5 Call Flow for base station initiated Active to Control Hold Transition

M S A c t iv e R e q u e s t t o t r a n s it io n t o C o n t r o l H o ld M o d e

BS

A c t iv e

R e s o u r c e R e le a s e R e q u e s t ( M in i) M e s s a g e

E x t e n d e d R e le a s e ( M in i) M e s s a g e / U n iv e r s a l H a n d o f f D ir e c t i o n M e s s a g e

A t th e a c t io n t im e : T r a n s it io n t o C o n t r o l H o ld M o d e & s t a r t r e v e r s e p il o t g a t i n g a t t h e s p e c if ie d g a t in g r a t e

E x te n d e d R e le a s e R e s p o n s e (M in i) M e s s a g e H a n d o f f C o m p le t io n M e s s a g e

C o n tr o l H o ld

C o n tr o l H o ld

4 5Figure 13-6 Call Flow for mobile station initiated Active to Control Hold Transition
6

11

3GPP2 C.S0044-A v1.0

M S C o n tro l H o ld

BS

C o n tro l H o ld

R e s o u r c e A llo c a tio n (M in i) M e s s a g e / U n iv e r s a l H a n d o f f D ir e c t io n M e s s a g e / E x t e n d e d S u p p le m e n t a l C h a n n e l A s s ig n m e n t M e s s a g e / F o r w a r d S u p p le m e n ta l C h a n n e l A s s ig n m e n t M in i M e s s a g e / R e v e r s e S u p p le m e n t a l C h a n n e l A s s ig n m e n t M in i M e s s a g e A t th e a c t io n t im e : T r a n s it io n t o A c t iv e M o d e & s t a r t r e v e r s e p il o t c o n t in u o u s tra n s m is s io n A c t iv e A c t iv e

B S d e c id e s t o tra n s it io n t o A c tiv e M o d e

1 2Figure 13-7 Call Flow for base station initiated Control Hold to Active Transition
3

M S C o n tro l H o ld R e q u e s t t o t r a n s it io n t o A c tiv e M o d e R e s o u rc e R e q u e s t (M in i) M e s s a g e / S u p p le m e n t a l C h a n n e l R e q u e s t ( M in i) M e s s a g e

BS

C o n tro l H o ld

A t th e a c t io n t im e : T r a n s it io n t o A c t iv e M o d e & s t a r t r e v e r s e p il o t c o n t in u o u s tra n s m is s io n A c t iv e

R e s o u r c e A llo c a tio n (M in i) M e s s a g e / U n iv e r s a l H a n d o f f D ir e c t io n M e s s a g e / E x t e n d e d S u p p le m e n t a l C h a n n e l A s s ig n m e n t M e s s a g e / F o r w a r d S u p p le m e n ta l C h a n n e l A s s ig n m e n t M in i M e s s a g e / R e v e r s e S u p p le m e n t a l C h a n n e l A s s ig n m e n t M in i M e s s a g e A c t iv e

4 5Figure 13-8 Call Flow for mobile station initiated Control Hold to Active Transition 613.6.3 Traceability
7(See [4])

82.6.4.1.15 2

Processing the Non-Negotiable Service Configuration Record

12

13GPP2 C.S0044-A v1.0 12.6.4.1.9 2 32.6.4.1.10 4 52.6.4.4 62.6.6.2.5.1 72.7.2.3.2.18 82.7.2.3.2.28 92.7.2.3.2.23 102.7.2.3.2.24 112.7.2.3.2.29 122.7.2.3.2.30 133.6.4.1.6 143.6.4.1.8 15 163.6.4.4 173.6.6.2.2.11 183.6.6.2.2.13 193.6.6.2.2.14 203.7.3.3.2.32 213.7.3.3.2.33 223.7.3.3.2.34 233.7.3.3.2.35 243.7.3.3.2.36 253.7.3.3.2.37 263.7.3.3.2.38 273.7.3.3.2.39 283.7.5.20
Processing the Extended Release Message and the Extended Release Mini Message Processing the Resource Allocation Message and Resource Allocation Mini Message Conversation Substate Processing of Forward Traffic Channel Handoff Messages Supplemental Channel Request Message Supplemental Channel Request Mini Message Resource Request Message Resource Request Mini Message Resource Release Request Message Resource Release Request Mini Message Processing Resource Request Messages Processing Resource Release Request Message and Resource Release Request Mini Message Conversation Substate Processing the Universal Handoff Direction Message Processing of Forward Supplemental Channel Assignment Mini Message Processing of Reverse Supplemental Channel Assignment Mini Message Resource Allocation Message Resource Allocation Mini Message Extended Release Message Extended Release Mini Message Universal Handoff Direction Message Extended Supplemental Channel Assignment Message Forward Supplemental Channel Assignment Mini Message Reverse Supplemental Channel Assignment Mini Message (base station) Non-Negotiable Service Configuration information record

2913.6.4 Method of Measurement 30 31 32

a. b. c. Connect the mobile station to the base station as shown in Figure A-3. Setup a packet data call, using only the Dedicated Control Channel (DCCH). Verify user traffic (Ex. Browser data) in both directions.

13

1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 2
l. m. g. f. d. e.

3GPP2 C.S0044-A v1.0 Cause the mobile station and/or base station to initiate transition to the Control Hold Mode because of out-of-data indication from the RLP. Verify that one of the following two scenarios occurs: 1. Verify that the mobile station sends a Resource Release Request (Mini) Message to the base station to request transition to the Control Hold Mode. Verify that the base station accepts this request, via an Extended Release (Mini) Message, or a Universal Handoff Direction Message. Verify that the mobile station responds with an Extended Release Response (Mini) Message, or a Extended Handoff Completion Message. 2. Verify that the base station sends an Extended Release Mini Message, or a Universal Handoff Direction Message. Verify that the mobile station responds with an Extended Release Response Mini Message, or an Extended Handoff Completion Message. Upon transition to Control Hold Mode, verify the following: 1. The reverse pilot is gated at the specified rate. 2. Dedicated Control Channel is maintained for signaling. 3. User traffic (Ex. Browser data) is not transmitted on either direction. NOTE: This can be verified by attempting to send user traffic, while not granting any requests to transition to the Active Mode. 4. Reverse Power Control Subchannel is maintained at the Forward Dedicated Control Channel. Depending on who initiated the transition to Control Hold Mode in e, and if possible, change the control hold time on the network side to make the other alternative happen in d. Repeat b through f. Results are as expected in f. Execute steps b through f. Instruct the base station to initiate the transition to Active Mode (e.g. Send a ping command to the mobile station from the base station. Verify that the base station initiates the transition to Active Mode, via a Resource Allocation Message, a Resource Allocation Mini Message, a Universal Handoff Direction Message, an Extended Supplemental Channel Assignment (Mini) Message, a Forward Supplemental Channel Assignment Mini Message, or a Reverse Supplemental Channel Assignment Mini Message. Verify that the mobile station responds accordingly. Upon transition to the Active Mode, verify that: 1. The reverse pilot transmission is continuous 2. User traffic (Ex. Browser data) is transmitted. Execute steps b through f. Send a ping from the mobile station side to cause the mobile station to initiate the transition to Active Mode. Verify that the mobile station sends a Resource Request (Mini) Message, a Supplemental Channel Request (Mini) Message. Verify that the base 14

h. i. j.

k.

13GPP2 C.S0044-A v1.0 1 2 3 4 5

n. station sends a Resource Allocation (Mini) Message, a Universal Handoff Direction Message, an Extended Supplemental Channel Assignment (Mini) Message, a Forward Supplemental Channel Assignment Mini Message, or a Reverse Supplemental Channel Assignment Mini Message. Verify step k.

613.6.5 Minimum Standard

7The mobile station and the base station shall comply with the requirements in the following steps: 8e, f, j, k, m, and n.

913.7 Soft Handoff of Fundamental Channel/Dedicated Control Channel and Supplemental 10 Channels 1113.7.1 Definition
12This test verifies that the mobile station can successfully complete a soft handoff of the 13fundamental, dedicated control channel, and supplemental channels during a data transfer.

1413.7.2 Traceability
15(see [4])

162.7.2.3.2.18 172.7.2.3.2.28 182.7.2.32.34 192.7.2.3.2.28 203.6.6.2.2.12 213.7.3.3.2.24 223.7.3.3.2.36 233.7.5.7.1

24(see [15])

Supplemental Channel Request Message Pilot Strength Measurement Mini Message Extended Pilot Strength Measure Message Supplemental Channel Request Mini Message Processing of Extended Supplemental Channel Assignment Message Supplemental Channel Assignment Message Universal Handoff Direction Message Channel Configuration for the Supplemental Channel

251.4.2.2 262.2.2 272.2.3 282.2.7

Mobile Station Packet Data Service States Service and Call Control Procedures Initialization and Connection of Packet Data Service Options High Speed Operation

2913.7.3 Call Flow Example(s)

30None

15

1 113.7.4 Method of Measurement 213.7.4.1 Forward FCH/DCCH and SCH Soft Handoff 3 4 5
Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io
6

3GPP2 C.S0044-A v1.0

a.

Connect the mobile station to the base station as shown in Figure A-5 and setup the parameters as shown in Table 13.7.4-40. Table 13.7.4-40 Unit dB dB dB dBm/1.23 MHz dB -5.8 Channel 1 7 -5 -7 -75 -33 Channel 2 -20 -5 -7

7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

b. c. d. e.

Verify the mobile station is in the Idle State on base station 1. Setup a mobile station originated service option 33 call, using the FCH for signaling. Initiate a forward data transfer to the mobile station. Configure base station 1 to send the Extended Supplemental Channel Assignment Message to assign the maximum number of forward supplemental channels supported by the base station and mobile station. While the forward data transfer is in progress, raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message, Extended Pilot Strength Message, or a Pilot Strength Mini Message. Configure base station 1 to send a Universal Handoff Direction Message with NUM_FOR_ASSIGN = [number of SCH in step e] and both base stations in the active set. Verify the mobile station sends the Handoff Completion Message or an Extended Handoff Completion Message. Verify the mobile stations active set consist of both base stations. Lower the level of base station 1 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message, Extended Pilot Strength Measurement Message or a Pilot Strength Measurement Mini Message. Configure base station 1 to send a Universal Handoff Direction Message to the mobile station with NUM_FOR_ASSIGN = [number of SCH in step e] and base station 2 in the active set.

f.

g.

h.

i.

j.

16

13GPP2 C.S0044-A v1.0 1 2 3 4 5

k. l. m. n. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message. Verify the data transfer completes successfully. End the call. Repeat steps c through m using the DCCH for signaling.

613.7.4.2 Reverse FCH/DCCH and SCH Soft Handoff 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

a. b. c. d. e. Connect the mobile station to the base station as shown in Figure A-5 and setup the parameters as shown in Table 13.7.4-40. Verify the mobile station is in the Idle State on base station 1. Setup a mobile station originated service option 33 call using the FCH for signaling. Initiate a reverse data transfer from the mobile station. After the mobile station sends a Supplemental Channel Request Message, configure base station 1 to send an Extended Supplemental Channel Assignment Message to assign the maximum number of reverse supplemental channels supported by the network and mobile station. While the reverse data transfer is in progress, raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement, Extended Pilot Strength Measurement Message or a Pilot Strength Measurement Mini Message. Configure base station 1 to send a Universal Handoff Direction Message with NUM_REV_ASSIGN = [number of SCH in step e] and both base stations in the active set. Verify the mobile station sends the Handoff Completion Message or an Extended Handoff Completion Message. Verify the mobile stations active set consist of both base stations. Lower the level of base station 1 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message, Extended Pilot Strength Measurement Message or a Pilot Strength Measurement Mini Message. Configure base station 2 to send a Universal Handoff Direction Message to the mobile station with NUM_REV_ASSIGN = [number of SCH in step e] and base station 2 in the active set. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message. Verify the data transfer completes successfully. End the call. Repeat steps c through m using the DCCH.

f.

g.

h.

i.

j.

k. l. m. n.

17

1 113.7.5 Minimum Standard 213.7.5.1 Forward FCH/DCCH and SCH Soft Handoff
3The mobile station shall comply with steps h, k, l, and n.

3GPP2 C.S0044-A v1.0

413.7.5.2 Reverse FCH/DCCH and SCH Soft Handoff

5The mobile station shall comply with steps h, k, l, and n.

613.8 Soft Handoff of Fundamental Channel or Dedicated Control Channel only 713.8.1 Definition
8This test verifies the mobile station can successfully complete a data transfer when only the 9fundamental channel or dedicated control channel is in soft handoff.

1013.8.2 Traceability
11(see [4])

122.7.2.3.2.18 132.7.2.3.2.28 142.7.2.3.2.28 152.7.2.32.34 163.6.6.2.2.12 173.7.3.3.2.24 183.7.3.3.2.36 193.7.5.7.1

20(see [15])

Supplemental Channel Request Message Supplemental Channel Request Mini Message Pilot Strength Measurement Mini Message Extended Pilot Strength Measure Message Processing of Extended Supplemental Channel Assignment Message Supplemental Channel Assignment Message Universal Handoff Direction Message Channel Configuration for the Supplemental Channel

211.4.2.2 222.2.2 232.2.3 242.2.7

Mobile Station Packet Data Service States Service and Call Control Procedures Initialization and Connection of Packet Data Service Options High Speed Operation

2513.8.3 Call Flow Example(s)

26None

2713.8.4 Method of Measurement 2813.8.4.1 Forward FCH/DCCH Only Soft Handoff 29 30 31 2

a. b. Connect the mobile station to the base station as shown in Figure A-5 and setup the parameters as shown in Table 13.7.4-40. Verify the mobile station is in the Idle State on base station 1.

18

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

c. d. e. Setup a mobile station originated service option 33 call using the FCH for signaling. Initiate a forward data transfer to the mobile station. Configure base station 1 to send the Extended Supplemental Channel Assignment Message to assign the maximum number of forward supplemental channels supported by the network and mobile station. While the forward data transfer is in progress, raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message, Extended Pilot Strength Measurement Message or a Pilot Strength Measurement Mini Message. Configure base station 1 to send a Universal Handoff Direction Message with NUM_FOR_ASSIGN = 0 and both base stations in the active set. Verify the mobile station sends the Handoff Completion Message or an Extended Handoff Completion Message. Verify the mobile stations active set consist of both base stations. Verify the data transfer completes successfully. End the call. Repeat steps c through j using the DCCH for signaling.

f.

g. h.

i. j. k.

1813.8.4.2 Reverse FCH/DCCH Only Soft Handoff 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

a. b. c. d. e. Connect the mobile station to the base station as shown in Figure A-5 and setup the parameters as shown in Table 13.7.4-40. Verify the mobile station is in the Idle State on base station 1. Setup a mobile station originated service option 33 call using the FCH for signaling Initiate a reverse data transfer from the mobile station. After the mobile station sends a Supplemental Channel Request Message, Configure base station 1 to send an Extended Supplemental Channel Assignment Message to assign the maximum number of reverse supplemental channels supported by the network and mobile station. While the reverse data transfer is in progress, raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message, Extended Pilot Strength Measurement Message or a Pilot Strength Measurement Mini Message. Configure base station 1 to send a Universal Handoff Direction Message with NUM_REV_ASSIGN = 0 and both base stations in the active set. Verify the mobile station sends the Handoff Completion Message or an Extended Handoff Completion Message. Verify the mobile stations active set consist of both base stations. Verify the data transfer completes successfully.

f.

g. h.

i.

19

1 1 2
j. k. End the call. Repeat steps c through j with the DCCH for signaling.

3GPP2 C.S0044-A v1.0

313.8.5 Minimum Standard 413.8.5.1 Forward FCH/DCCH Only Soft Handoff

5The mobile station shall comply with steps h i, and k.

613.8.5.2 Reverse FCH/DCCH Soft Handoff Only

7The mobile station shall comply with steps h, i, and k.

813.9 Adding Supplemental Channels during Soft Handoff 913.9.1 Definition

10This test verifies that a supplemental channel(s) can be added in a service option 33 call while in 11soft handoff on the fundamental channel or dedicated control channel.

1213.9.2 Traceability
13(see [4])

142.7.2.3.2.18 152.7.2.3.2.28 162.7.2.32.34 172.7.2.3.2.28 183.6.6.2.2.12 193.7.3.3.2.24 203.7.3.3.2.36 213.7.5.7.1

22(see [15])

Supplemental Channel Request Message Pilot Strength Measurement Mini Message Extended Pilot Strength Measure Message Supplemental Channel Request Mini Message Processing of Extended Supplemental Channel Assignment Message Supplemental Channel Assignment Message Universal Handoff Direction Message Channel Configuration for the Supplemental Channel

231.4.2.2 242.2.2 252.2.3 262.2.7

Mobile Station Packet Data Service States Service and Call Control Procedures Initialization and Connection of Packet Data Service Options High Speed Operation

2713.9.3 Call Flow Example(s)

28None

2913.9.4 Method of Measurement 30 31 2

a. Connect the mobile station to the base station as shown in Figure A-5 and setup the parameters as shown in Table 13.7.4-40.

20

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

b. c. d. Verify the mobile station is in the Idle State on base station 1. Setup a mobile station originated service option 33 call using the FCH for signaling. Raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message, Extended Pilot Strength Measurement Message, or a Pilot Strength Measurement Mini Message. Configure base station 1 to send a Universal Handoff Direction Message with NUM_FOR_ASSIGN = 0 and both base stations in the active set. Verify the mobile station sends the Handoff Completion Message or an Extended Handoff Completion Message. Verify the mobile stations active set consist of both base stations. Initiate a forward data transfer to the mobile station. Configure base station 1 to send the Extended Supplemental Channel Assignment Message with NUM_SUP_SHO = 001 for the forward supplemental channel and include both base station 1 and base station 2 for PILOT_PN values. Verify the data transfer completes successfully. End the call. Repeat steps c through j using the DCCH for signaling.

e. f.

g. h.

i. j. k.

1913.9.5 Minimum Standard

20The mobile station shall comply with steps f, i, and k.

2113.10 Hard Handoff during Data Transfer 2213.10.1 Definition

23This test verifies the data transfer continues after hard handoff using the forward and reverse link.

2413.10.2 Traceability
25(see [4])

262.7.2.3.2.18 272.7.2.3.2.28 283.6.6.2.2.12 293.7.3.3.2.24 303.7.3.3.2.36 313.7.5.7.1

32(see [15])

Supplemental Channel Request Message Supplemental Channel Request Mini Message Processing of Extended Supplemental Channel Assignment Message Supplemental Channel Assignment Message Universal Handoff Direction Message Channel Configuration for the Supplemental Channel

331.4.2.2

Mobile Station Packet Data Service States

21

1 12.2.2 22.2.3 32.2.7

Service and Call Control Procedures

3GPP2 C.S0044-A v1.0

Initialization and Connection of Packet Data Service Options High Speed Operation

413.10.3 Call Flow Example(s)

5None

613.10.4 Method of Measurement 713.10.4.1 Forward Data Transfer during Hard Handoff 8 9 10
Parameter or/Ioc Pilot Ec/Ior Traffic Ec/Ior Ioc Pilot Ec/Io
11

a.

Connect the mobile station to the base station as shown in Figure A-5 and setup the parameters in Table 13.10.4-41. Table 13.10.4-41 Unit dBm dB dB dBm/1.23 MHz dB Channel 1 N/A -7 -7 N/A -7 Channel 2 -5 -7 -7 -75 -13.2

12 13 14 15 16 17 18 19 20 21 22 23 24

b. c. d. e. f. g. h. i. j.

Ensure that the mobile station is operating in the idle state on base station 1. Setup a mobile station originated Service Option 33 call. Initiate a data transfer to the mobile station and verify the base station sends an Extended Supplemental Channel Assignment Message assigning a F-SCH. While the data transfer is in progress, instruct the base station to send a Universal Handoff Direction Message directing the mobile station to base station 2. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message. Configure base station 2 to send a Universal Handoff Direction Message or an Extended Supplemental Channel Assignment Message assigning a F-SCH. Verify the data transfer completes. End the call from the mobile station. Repeat steps c through i using the DCCH for signaling.

22

13GPP2 C.S0044-A v1.0 113.10.4.2 Reverse Data Transfer during Hard Handoff 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
a. b. c. d. e. f. g. h. i. j. k. Connect the mobile station to the base station as shown in Figure A-5 and setup the parameters in Table 13.10.4-41. Ensure that the mobile station is operating in the idle state on base station 1. Setup a mobile station originated Service Option 33 call. Initiate a data transfer from the mobile station and verify the mobile station sends a Supplemental Channel Request Message requesting a reverse supplemental channel. Instruct the base station to send an Extended Supplemental Channel Assignment Message assigning a reverse supplemental channel to the mobile station. While the data transfer is in progress, instruct the base station to send a Universal Handoff Direction Message directing the mobile station to base station 2. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message. Configure base station 2 to send a Universal Handoff Direction Message or an Extended Supplemental Channel Assignment Message assigning a R-SCH. Verify the data transfer completes successfully. End the call from the mobile station. Repeat steps c through j using the DCCH for signaling.

1913.10.5 Minimum Standard 2013.10.5.1 Forward Data Transfer during Hard Handoff
21The mobile station shall comply with steps f, h and j.

2213.10.5.2 Reverse Data Transfer during Hard Handoff

23The mobile station shall comply with steps g, i, and k.

2413.11 Hard Handoff to a different Radio Configuration 2513.11.1 Definition

26This test verifies hard handoff to a different radio configuration during an HSPD call.

2713.11.2 Traceability
28(see [4])

292.7.2.3.2.18 302.7.2.3.2.28 313.6.6.2.2.12 323.7.3.3.2.24

Supplemental Channel Request Message Supplemental Channel Request Mini Message Processing of Extended Supplemental Channel Assignment Message Supplemental Channel Assignment Message

23

1 13.7.3.3.2.36 23.7.5.7.1
3(see [15])

3GPP2 C.S0044-A v1.0 Universal Handoff Direction Message Channel Configuration for the Supplemental Channel

41.4.2.2 52.2.2 62.2.3 72.2.7

Mobile Station Packet Data Service States Service and Call Control Procedures Initialization and Connection of Packet Data Service Options High Speed Operation

813.11.3 Call Flow Example(s)

9None

1013.11.4 Method of Measurement 1113.11.4.1 Forward Data Transfer during Hard Handoff 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
a. b. c. d. e. Connect the mobile station to the base station as shown in Figure A-5 and setup the parameters in Table 13.10.4-41. Ensure that the mobile station is operating in the idle state on base station 1. Setup a mobile station originated Service Option 33 call. Note the FOR_FCH_RC, REV_FCH_RC, and SCH_RC values. Initiate a data transfer to the mobile station and verify the base station sends an Extended Supplemental Channel Assignment Message assigning a F-SCH. While the data transfer is in progress, instruct the base station to send a Universal Handoff Direction Message changing the FOR_FCH_RC, REV_FCH_RC and SCH_RC values in step c and directing the mobile station to base station 2. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message. Configure base station 2 to send an Extended Supplemental Channel Assignment Message assigning a F-SCH. Verify the data transfer completes. End the call from the mobile station. This test may be repeated for all radio configurations supported. Repeat steps c through j with the DCCH for signaling.

f. g. h. i. j. k.

3013.11.4.2 Reverse Data Transfer during Hard Handoff 31 32 33

a. b. Connect the mobile station to the base station as shown in Figure A-5 and setup the parameters in Table 13.10.4-41. Ensure that the mobile station is operating in the idle state on base station 1.

24

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

c. d. e. f. Setup a mobile station originated Service Option 33 call. Note the FOR_FCH_RC, REV_FCH_RC, and SCH_RC values. Initiate a data transfer from the mobile station and verify the mobile station sends a Supplemental Channel Request Message requesting a reverse supplemental channel. Instruct the base station to send an Extended Supplemental Channel Assignment Message assigning a reverse supplemental channel to the mobile station. While the data transfer is in progress, instruct the base station to send a Universal Handoff Direction Message changing the FOR_FCH_RC, REV_FCH_RC and SCH_RC values in step c directing the mobile station to base station 2. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message. Configure base station 2 to send a Universal Handoff Direction Message or an Extended Supplemental Channel Assignment Message assigning a R-SCH. Verify the data transfer completes successfully. End the call from the mobile station. This test may be repeated for all radio configurations supported. Repeat steps c through k using the DCCH for signaling

g. h. i. j. k. l.

1813.11.5 Minimum Standard 1913.11.5.1 Forward Data Transfer during Hard Handoff
20The mobile station shall comply with steps f, h, and k.

2113.11.5.2 Reverse Data Transfer during Hard Handoff

22The mobile station shall comply with steps g, i, and l.

2313.12 Mobile Station Packet Data Inactivity Timer 2413.12.1 Definition

25This test is applicable for a mobile station implementing packet data inactivity timer. This test 26verifies the mobile station releases the traffic channel after expiration of the mobile station packet 27data Inactivity Timer. The test verifies the dormant link layer connection can be re-activated.

2813.12.2 Traceability
292.2.2

Service and Call Control Procedures

3013.12.3 Call Flow Example(s)

31None

3213.12.4 Method of Measurement 33

a. Set the packet data inactivity timer at the MT2 to 20 seconds.

25

1 1 2 3 4 5 6 7 8 9 10 11 12 13 14
b. c. d. e. f. g. h. i. j. k.

3GPP2 C.S0044-A v1.0 Ensure the base station packet data inactivity timer is disabled or set to a value of at least 30 seconds. Initiate a Telnet session to a remote host. Record the IP address assigned to the mobile station. Exit the Telnet session. Wait for the mobile station packet data inactivity timer to expire. Verify the in use indicator on the MT2 goes OFF. Initiate a Telnet session to a remote host. Record the IP address assigned to the mobile station. Wait for the mobile station packet data inactivity timer to expire. Verify the in use indicator on the MT2 goes OFF. Issue a continuous ping command from the remote host to the mobile station using the IP address assigned to the mobile station. Verify that the ping is successful.

1513.12.5 Minimum Standard

16The mobile station shall comply with steps f, i and k.

1713.13 Mobile Station and Base Station Operating in Different States 1813.13.1 Definition
19This test verifies the mobile station and base station correct the condition of the mobile station 20operating in the Null State and the base station/PCF operating in the Dormant State. [4] Permits 21two standardized approaches for the mobile station to reject/release a General Page Message 22containing Service Option 33 when the mobile station is in the Null State and the base 23station/PCF is in the Dormant State. In both implementations, the mobile station and base 24station/PCF shall transition to the Null State. 25In the preferred implementation, a mobile station in the Null State will reject a General Page 26Message containing Service Option 33 by sending a Page Response Message containing 27Service Option = 0x00. The base station should send a Release Order to the mobile station. 28In an alternate implementation, a mobile station in the Null State will accept a General Page 29Message containing Service Option 33 by sending a Page Response Message containing 30Service Option 33. After the base station assigns a traffic channel, the mobile station sends a 31Release Order containing ORDQ=2 to release the call.

3213.13.2 Traceability
33(see [4])

343.7.4.1 352.7.1.3.2.5 363.6.2.3 373.6.3.3 2

Page Response Substate Page Response Message Mobile Station Directed Messages Responding to a Page Response Message

26

13GPP2 C.S0044-A v1.0 13.7.4

2(see [15])

Orders

32.2.2.2.1.3

Paging State

413.13.3 Call Flow Example(s)

MS Dormant State
MS and BS/ PCF are not in the same state. MS has closed PPP session without notifying BS/ PCF.

BS/ PCF Dormant State

Null State General Page, SO: 0x21 Page Response Msg with SO: 0x00

Dormant State

BS/PCF attempts to initiate a dormant to active transition.

BS should send Release Order

Null State

Null State

5 6

Figure 13-9 Call Flow without Setting Up Traffic Channel (Preferred Implementation)

27

1
MS Dormant State
MS and BS/ PCF are not in the same state. MS has closed PPP session without notifying BS/ PCF.

3GPP2 C.S0044-A v1.0

BS/ PCF Dormant State

Null State General Page, SO: 0x21

Dormant State

Page Response Msg with SO: 0x21 Traffic Channel Setup

Conversation MS sends Release Order with ORDQ=2

BS/PCF attempts to initiate a dormant to active transition.

Null State

Null State

1 2

Figure 13-10 Call Flow with Setting Up Traffic Channel (Alternate Implementation)

313.13.4 Method of Measurement 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

a. b. c. d. e. Connect the mobile station as shown in Figure A-3. Set up a Service Option 33 call using a dedicated traffic channel. Allow the mobile station to enter the Dormant State. Verify the base station/PCF and mobile station are operating in the Dormant State. Instruct the mobile station to transition to the Null State (i.e. terminate the PPP session) without notifying the base station. (e.g., disconnect the mobile station from the laptop.) NOTE: Depending on implementation, the mobile station may autonomously originate a service option 33 call upon the disconnection of the cable from the laptop. If this occurs, proceed to step g2. Instruct the base station to initiate the Dormant to Active transition by sending a General Page Message or Universal Page Message to the mobile station with the Service Option 33. Verify one of the following occurs; 1. The mobile station sends a Page Response Message with the Service Option = 0:

f.

g.

28

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8

h. a. The base station should send a Release Order to the mobile station after receiving the Page Response Message with the Service Option = 0. 2. The mobile station sends a Page Response Message/Origination Message with the Service Option = 33: a. After the base station assigns a traffic channel, verify the mobile station sends a Release Order with ORDQ=2. Verify the mobile station and base station/PCF are now operating in the Null State.

913.13.5 Minimum Standard

10The mobile station shall comply with steps g and h. 1113.14 RLP Operation in Rayleigh Fading Environment 1213.14.1 Definition 13This test verifies data transfer under Rayleigh fading channel conditions. This test verifies that 14RLP recovers erased data frames, and is intended to exercise RLP negative acknowledgements 15(NAKs), retransmissions, and aborts in the forward and reverse directions. This test also verifies 16the mobile station is able to successfully complete a network initiated dormant to active transition. 1713.14.2 Traceability 18(see [4])

192.6.4.2
20(see [15])

Traffic Channel Substate

212.2.1 222.2.2 232.2.7

24

RLP Requirements Service and Call Control Procedures High Speed Operation

2513.14.3 Call Flow Example(s) 26None 2713.14.4 Method of Measurement

28 29 30 31 32 33 34 35

a. b. c. d. e. f. g.

Connect the mobile station to the base station as shown in Figure A-2. Set the channel simulator using the parameters as specified in Table 3.5.4-4. Ensure the mobile station currently has a PPP session established and is in the dormant state. Instruct the base station to initiate a dormant to active transition. Verify the mobile station is able to transition to the active state. Initiate a forward data transfer to the mobile station. Verify the file transfer completes successfully.

29

1 1 2 3
h. i. j. Initiate a reverse data transfer from the mobile station. Verify the file transfer completes.

3GPP2 C.S0044-A v1.0

Repeat steps c through i changing the channel simulator setting to one path at 3 km/hr.

413.14.5 Minimum Standard 5The mobile station shall comply with steps e, g, i, and j.

613.15 Release Order Processing 713.15.1 Definition

8This test case verifies the mobile station correctly processes the Release Order with ORDQ=2 9when received on the f-csch.

1013.15.2 Traceability
11(see [4])

122.7.1.3.2.4 133.7.5
14(see [15])

Origination Message Orders

151.4.2.2 162.2.2 172.2.3 182.2.7

19

Mobile Station Packet Data Service States Service and Call Control Procedures Initialization and Connection of Packet Data Service Options High Speed Operation

30

13GPP2 C.S0044-A v1.0 113.15.3 Call Flow Example(s)

MS BS

Origination Message

Acknowledgment Orde r

Release Order with ORDQ=2 The mobile station may originate another call using a different service option (e.g SO12)

Origination Message with new service option

Acknowledgment Orde r

Extended Channel Assignement Message

TCH

2 313.15.4 Method of Measurement 4 5 6 7 8 9 10 11 12 13 14 15

a. Configure the network to not allow Service Option 33 calls for the mobile station. (Note: The network has packet data resources available, however the mobile station is not authorized to use them.) Instruct the mobile station to originate a Service Option 33 call. Instruct the base station to send a Release Order with ORDQ = 2 to mobile station indicating the requested service option has been rejected. Verify the mobile station returns to the System Determination Substate or the Mobile Station Idle State. The mobile station may autonomously attempt to originate another data service option (e.g. SO=12). If the mobile station originates another service option and: 1. The base station supports that service option and has resources available, and

b. c. d. e. f.

31

1 1 2 3

3GPP2 C.S0044-A v1.0 2. The mobile station is authorized to use that service option, verify the following: a. The new data call with the different service option is completed successfully.

413.15.5 Minimum Standard

5The mobile station shall comply with step d. If the mobile station supports step e, the mobile 6station shall comply with step f.

713.16 Hysteresis Activation Timer 813.16.1 Definition

9This test case verifies the mobile station implementation of Hysteresis Activation Timer. The 10value of this timer is mobile station implementation dependent in the range of 0 to 30 seconds.

1113.16.2 Traceability
12(see [15])

132.2.2.1.2.4

Dormant State

1413.16.3 Call Flow Example(s)

15None

1613.16.4 Method of Measurement 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34

a. Connect the mobile station to the base station as shown in Figure A-5. Configure base station 1 and base station 2 to transmit different non-zero values of PACKET_ZONE_ID field in Extended System Parameters Message or ANSI-41 System Parameters Message. Connect both the base stations to same PDSN. Allow the mobile station to go idle on base station 1. Instruct the mobile station to originate a Service Option 33 call on base station 1. Transfer data on the Service Option 33 call (e.g. perform ftp or ping). Ensure that length of the packet zone list is set to one entry at the mobile station. Ensure packet zone hysteresis is enabled at the mobile station. Allow Mobile Station to go dormant on base station 1. For rest of the test ensure that the mobile station does not have any data to send. While the hysteresis activation timer is running perform following operations: 1. Allow Mobile Station to perform an idle handoff to base station 2. Verify that the mobile station sends an Origination Message with DRS field set to 0 to base station 2. 2. Allow Mobile Station to perform an idle handoff to base station 1. Verify that the mobile station sends an Origination Message with DRS field set to 0 to base station 1.

b.

c. d. e.

32

13GPP2 C.S0044-A v1.0 113.16.5 Minimum Standard

2The mobile station shall comply with step e

313.17 Hysteresis Timer 413.17.1 Definition

5This test case verifies the mobile station implementation of Hysteresis Timer. The value of this 6timer is mobile station implementation dependent in the range of 0 to 60 seconds.

713.17.2 Traceability
8(see [15]) 92.2.5

Packet Zone Reconnection Control

1013.17.3 Call Flow Example(s)

11None

1213.17.4 Method of Measurement 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

f. a. Connect the mobile station to the base station as shown in Figure A-5. Configure base station 1 and base station 2 to transmit different non-zero values of PACKET_ZONE_ID field in Extended System Parameters Message or ANSI-41 System Parameters Message. Connect both the base stations to same PDSN. Allow the mobile station to go idle on base station 1. Instruct the mobile station to originate a Service Option 33 call on base station 1. Transfer data on the Service Option 33 call (e.g. perform ftp or ping). Ensure that length of the packet zone list is set to one entry at the mobile station. Ensure packet zone hysteresis is enabled at the mobile station. Allow Mobile Station to go dormant on base station 1. Allow mobile station to remain in dormant state for duration of the hysteresis activation timer. For rest of the test ensure that the mobile station does not have any data to send. Perform following operations within duration less than the value of hysteresis timer configured at the mobile station: 1. Allow Mobile Station to perform an idle handoff to base station 2. Verify that the mobile station sends an Origination Message with DRS field set to 0 to base station 2. 2. Allow Mobile Station to perform an idle handoff to base station 1. Verify that the mobile station does not send an Origination Message. Allow Mobile Station to remain idle on base station 1 for duration more than the value of hysteresis timer configured at the mobile station. Verify that the mobile station sends an Origination Message with DRS field set to 0 to base station 1. Verify that the duration between the Origination Message in step d.1 and the Origination Message in step e is approximately equal to the value of hyesteresis timer configured at the mobile station.

b.

c. d.

e.

33

1 113.17.5 Minimum Standard

2The mobile station shall comply with steps e and f. 3

3GPP2 C.S0044-A v1.0

34

13GPP2 C.S0044-A v1.0 114 OVER-THE-AIR SERVICES 214.1 OTASP Download Request Processing 314.1.1 Definition
4This test verifies a mobile station can initiate programming procedure and update its NAM 5parameters.

614.1.2 Traceability
7(see [14])

83.2.1 93.5.1 103.5.2 114.2.1 124.3 134.5.1 144.5.2 154.5.4

User-Initiated Procedure Message Contents NAM Parameter Blocks User-Initiated Procedure Programming Data Download Message Contents NAM Parameter Blocks Validation Parameter Blocks

1614.1.3 Call Flow Example(s)

17None

1814.1.4 Method of Measurement 19 20 21 22

a. b. c. Connect the mobile station to the base station as shown in Figure A-1. Confirm that the mobile station is programmed with a non-zero SPCp. Setup a mobile originated OTASP call using *228 + one of the System Selection Codes in Table 14.1.4-42.

1 1
Selected System 800 MHz A-BAND 800 MHz B-BAND 1.9 GHz A Block 1.9 GHz B Block 1.9 GHz C Block 1.9 GHz D Block 1.9 GHz E Block 1.9 GHz F Block JTACS, A-Band JTACS, B-Band 2 GHz Band
2

3GPP2 C.S0044-A v1.0 Table 14.1.4-42 Code 00 01 02 03 04 05 06 07 10 11 23

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

d. e.

Upon call setup, instruct the base station to send a Protocol Capability Request Message to the mobile station. Verify the mobile station sends a Protocol Capability Response Message to the base station with MOB_FIRM_REV, MOB_MODEL, BAND_MODE_CAP and all supported FEATURE_ID and FEATURE_P_REV as listed in ANNEX C. The NAM Download feature support is required for this test. If Service Programming Lock is supported, perform the following: 1. Instruct the base station to send a Validation Request Message with BLOCK_ID = 00000000 and SPC = SPCP. 2. Verify the mobile station sends a Validation Response Message within 750 ms, and with BLOCK_ID = 00000000 and RESULT_CODE = 00000000 (Accepted Operation Successful).

f.

g.

If the Key Exchange is not supported, go to step h; otherwise: 1. Instruct the base station to send a Mobile Station Key Request Message to the mobile station. 2. Verify the mobile station responds with a Mobile Station Key Response Message within 30 seconds, with RESULT_CODE = '00000000' (Accepted - Operation Successful). 3. Instruct the base station to send a Key Generation Request Message to the mobile station.

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11

12

4. Verify the mobile station responds with a Key Generation Response Message within 30 seconds and the RESULT_CODE = '00000000' (Accepted - Operation Successful). 5. Verify the base station and the mobile station successfully perform SSD update procedures. 6. Verify the base station sends the Re-Authenticate Request Message and the mobile responds with the Re-Authenticate Response Message within 750ms. 7. At the base station verify Re-Authentication is successful. 8. The base station may enable Signaling Message Encryption and Voice Privacy. h. Instruct the base station to send a Configuration Request Message with one or more of the following NAM Parameter Block Types:

Parameter Block Type CDMA/Analog NAM Mobile Directory Number CDMA NAM IMSI_T

BLOCK_ID 00000000 00000001 00000010 00000011

13 14 15 16 17
18

i.

Verify the mobile station sends a Configuration Response Message within 750ms including each requested BLOCK_ID and associated PARAM_DATA with corresponding RESULT_CODE. Instruct the base station to send a Download Request Message with one or more of the following NAM Parameter Block Types and the corresponding PARAM_DATA:

j.

Parameter Block Type CDMA/Analog NAM Mobile Directory Number CDMA NAM IMSI_T

BLOCK_ID 00000000 00000001 00000010 00000011

19 20 21 22 23 24

k. l. m. n.

Verify the mobile station sends a Download Response Message and that RESULT_CODE = '00000000' (Accepted- Operation Successful) within 750ms. Instruct the base station to send a Commit Request Message to the mobile station. Verify the mobile station sends a Commit Response Message to the base station within 10 seconds with the RESULT_CODE = '00000000' (Accepted- Operation Successful). End the call at the mobile station.

1 1 2
o. p.

3GPP2 C.S0044-A v1.0 Verify the mobile station successfully stored the updated NAM information. Setup a mobile station originated call and verify user traffic is present.

314.1.5 Minimum Standard

4The mobile station shall comply with steps e, i, k, m, o, and p. If supported the mobile station shall 5comply with steps f and i. The mobile station shall update its NAM information as received in the 6Download Request Message.

714.2 OTASP PUZL Download Request Processing 814.2.1 Definition

9This test verifies a mobile station can initiate programming procedure and update its Preferred 10User Zone List (PUZL).

1114.2.2 Traceability
12(see [14])

133.2.1 143.5.1 153.5.6 163.5.7 174.2.1 184.3 194.5.1 204.5.4 214.5.6

User-Initiated Procedure Message Contents PUZL Parameter Blocks Preferred User Zone List (PUZL) User-Initiated Procedure Programming Data Download Message Contents Validation Parameter Blocks PUZL Parameter Blocks

2214.2.3 Call Flow Example(s)

23None

2414.2.4 Method of Measurement 25 26 27 28 29 30 31 32

a. b. c. d. e. Connect the mobile station to the base station as shown in Figure A-3. Confirm that the mobile station is programmed with a non-zero SPCp. Setup a mobile station originated OTASP call using *228 + one of the System Selection Codes in Table 14.1.4-42. Upon call setup, instruct the base station to send a Protocol Capability Request Message to the mobile station. Verify the mobile station sends a Protocol Capability Response Message to the base station with MOB_FIRM_REV, MOB_MODEL, BAND_MODE_CAP and all supported

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10

11

FEATURE_ID and FEATURE_P_REV as listed in ANNEX C. The Preferred User Zone List feature support is required for this test. f. If Service Programming Lock is supported, perform the following: 1. Instruct the base station to send a Validation Request Message with BLOCK_ID = 00000000 and SPC = SCPp. 2. Verify the mobile station sends a Validation Response Message within 750 ms, and with BLOCK_ID = 00000000 and RESULT_CODE = 00000000 (Accepted Operation Successful). g. Instruct the base station to send a PUZL Configuration Request Message to the mobile station with one of the following BLOCK_ID values:

PUZL Parameter Block Type PUZL Dimensions PUZL Priorities User Zone Preferred User Zone List

BLOCK_ID 00000000 00000001 00000010 00000011

12 13 14 15 16

h.

Verify the mobile station sends a PUZL Configuration Response Message within 750ms with the BLOCK_ID and associated PARAM_DATA requested in the PUZL Configuration Request Message. Instruct the base station to send a PUZL Download Request Message with one or more of the following PUZL Parameter Block Types and the corresponding PARAM_DATA:

i.

Parameter Block Type User Zone Insert User Zone Update User Zone Delete User Zone Priority Change PUZL Flags

BLOCK_ID 00000000 00000001 00000010 00000011 00000100

18 19 20 21 22 23

j. k. l. m.

Verify the mobile station sends a PUZL Download Response Message within 750ms with the RESULT_CODE = 00000000 (Accepted Operation Successful). Instruct the base station to send a Commit Request Message to the mobile station. Verify the mobile station sends a Commit Response Message to the base station within 10 seconds with the RESULT_CODE = '00000000' (Accepted- Operation Successful). End the call at the mobile station.

1 1
n.

3GPP2 C.S0044-A v1.0 Verify the mobile station successfully stored the updated PUZL information.

214.2.5 Minimum Standard

3The mobile station shall comply with steps e, h, j, l, and n. The mobile station shall update its 4PUZL information as received in the PUZL Download Request Message.

514.3 OTASP 3GPD Download Request Processing 614.3.1 Definition

7This test verifies a mobile station can initiate programming procedure and update its 3GPD 8information.

914.3.2 Traceability
10(see [14])

113.2.1 123.5.1 133.5.8 144.2.1 154.3 164.5.1 174.5.4 184.5.7

User-Initiated Procedure Message Contents 3GPD Parameter Blocks User-Initiated Procedure Programming Data Download Message Contents Validation Parameter Blocks 3GPD Parameter Blocks

1914.3.3 Call Flow Example(s)

20None

2114.3.4 Method of Measurement 22 23 24 25 26 27 28 29 30 31 32

a. b. c. d. e. Connect the mobile station to the base station as shown in Figure A-3. Confirm that the mobile station is programmed with a non-zero SPCp. Setup a mobile station originated OTASP call using *228 + one of the System Selection Codes in Table 14.1.4-42. Upon call setup, instruct the base station to send a Protocol Capability Request Message to the mobile station. Verify the mobile station sends a Protocol Capability Response Message to the base station with MOB_FIRM_REV, MOB_MODEL, BAND_MODE_CAP and all supported FEATURE_ID and FEATURE_P_REV as listed in ANNEX C. The 3G Packet Data feature support is required for this test. If Service Programming Lock is supported, perform the following:

f.

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10

11

1. Instruct the base station to send a Validation Request Message with BLOCK_ID = 00000000 and SPC = SPCp. 2. Verify the mobile station sends a Validation Response Message within 750 ms, and with BLOCK_ID = 00000000 and RESULT_CODE = 00000000 (Accepted Operation Successful). g. Instruct the base station to send a 3GPD Configuration Request Message to the mobile station with one or more of the following 3GPD Parameter Block Types from Table 14.3.4-43. If the 3GPD Parameter Block Type requests the shared secret do the following prior to sending the 3GPD Configuration Request Message: Instruct the base station to send a Secure Mode Request Message with

h.

Field START_STOP KEY_IN_USE RAND_SM

Value 1 0000 or 0001 Randomly selected value for SMCK

12 13
14

1. Verify the mobile station sends a Secure Mode Response Message within 750ms with RESULT_CODE = 00000000 (Accepted Operation Successful).

1 1
Table 14.3.4-43 3GPD Parameter Block Type 3GPD Operation Capability Parameters 3GPD Operation Mode Parameters SimpleIP Capability Parameters MobileIP Capability Parameters SimpleIP User Profile Parameters Mobile IP User Profile Parameters SimpleIP Status Parameters MobileIP Status Parameters SimpleIP PAP SS Parameters1 SimpleIP CHAP SS Parameters1 MobileIP SS Parameters1 HRPD Access Authentication Capability Parameters HRPD Access Authentication User Profile Parameters HRPD Access Authentication CHAP SS Parameters1
1

3GPP2 C.S0044-A v1.0

BLOCK_ID 00000000 00000001 00000010 00000011 00000100 00000101 00000110 00000111 00001000 00001001 00001010 00001011 00001100 00001101

The shared secret parameters shall not be transmitted over the air unencrypted.
2

3 4 5 6 7

i.

Verify the mobile station sends a 3GPD Configuration Response Message within 750ms including each requested BLOCK_ID and associated PARAM_DATA with corresponding RESULT_CODE. If SECURE_MODE_INDs = 1, then: 1. Verify the mobile station includes the following in the 3GPD Configuration Response Message:

13GPP2 C.S0044-A v1.0

Field FRESH_INCL FRESH Value 1 15-bit value used for encryption

1 2 3 4 5
6

j.

Instruct the base station to send a 3GPD Download Request Message with one or more of the 3GPD Parameter Block Types from Table 14.3.4-44 and the corresponding PARAM_DATA. If SECURE_MODE_INDs = 1, then: 1. Verify the base station includes the following in the 3GPD Download Request Message:

Field FRESH_INCL FRESH

Value 1 15-bit value used for encryption

8
Parameter Block Type 3GPD Operation Mode Parameters

Table 14.3.4-44 BLOCK_ID 00000000 00000001 00000010 00000110 00000111 00001000 00001001 00001010 00001011 00001100

SimpleIP User Profile Parameters Mobile IP User Profile Parameters SimpleIP Status Parameters MobileIP Status Parameters SimpleIP PAP SS Parameters1 SimpleIP CHAP SS Parameters1 MobileIP SS Parameters1 HRPD Access Authentication User Profile Parameters HRPD Access Authentication CHAP SS Parameters1
1

The shared secret parameters shall not be transmitted over the air unencrypted.

9 10 2

k.

Verify the mobile station sends a 3GPD Download Response Message within 750ms with the RESULT_CODE = 00000000 (Accepted Operation Successful). 9

1 1 2 3 4 5
l. m. n. o.

3GPP2 C.S0044-A v1.0 Instruct the base station to send a Commit Request Message to the mobile station. Verify the mobile station sends a Commit Response Message to the base station within 10 seconds with the RESULT_CODE = '00000000' (Accepted- Operation Successful). End the call at the mobile station. Verify the mobile station successfully stored the 3GPD information.

614.3.5 Minimum Standard

7The mobile station shall comply with steps e, h, k, m and o. If SECURE_MODE_IND = 1, the 8mobile station shall comply with step g. The mobile station shall update its 3GPD information as 9received in the 3GPD Download Request Message.

1014.4 OTASP SSPR Download Request Processing 1114.4.1 Definition

12This test verifies a mobile station can initiate programming procedure and update its preferred 13roaming list.

1414.4.2 Traceability
15(see [14])

163.2.1 173.5.1 183.5.3 193.5.5 204.2.1 214.3 224.5.1 234.5.3 244.5.4

User-Initiated Procedure Message Contents SSPR Parameter Blocks Preferred Roaming List and Extended Preferred Roaming List User-Initiated Procedure Programming Data Download Message Contents SSPR Parameter Blocks Validation Parameter Blocks

2514.4.3 Call Flow Example(s)

26None

2714.4.4 Method of Measurement 28 29 30 31 32 33 2

a. b. c. d. Connect the mobile station to the base station as shown in Figure A-4. Confirm that the mobile station is programmed with a non-zero SPCp. Setup a mobile originated OTASP call using *228 + one of the System Selection Codes in Table 14.1.4-1. Upon call setup, instruct the base station to send a Protocol Capability Request Message to the mobile station.

10

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12

13

e.

Verify the mobile station sends a Protocol Capability Response Message to the base station with MOB_FIRM_REV, MOB_MODEL, BAND_MODE_CAP and all supported FEATURE_ID and FEATURE_P_REV as listed in ANNEX C. The System Selection for Preferred Roaming feature support is required for this test. If Service Programming Lock is supported, perform the following: 1. Instruct the base station to send a Validation Request Message with BLOCK_ID = 00000000 and SPC = SCPp. 2. Verify the mobile station sends a Validation Response Message within 750 ms, and with BLOCK_ID = 00000000 and RESULT_CODE = 00000000 (Accepted Operation Successful).

f.

g.

Instruct the base station to send a SSPR Configuration Request Message to the mobile station with one of the following SSPR Parameter Block Types:

SSPR Parameter Block Type Preferred Roaming List Dimensions Preferred Roaming List Extended Preferred Roaming List Dimensions

BLOCK_ID 00000000 00000001 00000010

14 15 16 17
18

h. i.

Verify the mobile station sends a SSPR Configuration Response Message within 750ms with the BLOCK_ID and the associated PARAM_DATA. Instruct the base station to send a SSPR Download Request Message with one of the following SSPR Parameter Block Types and the corresponding PARAM_DATA:

Parameter Block Type Preferred Roaming List Extended Preferred Roaming List with SSPR_P_REV greater than 00000001

BLOCK_ID 00000000 00000001

19 20 21 22 23 24 25 2

j. k. l. m. n.

Verify the mobile station sends a SSPR Download Response Message within 750ms with the RESULT_CODE = 00000000 (Accepted Operation Successful). Instruct the base station to send a Commit Request Message to the mobile station. Verify the mobile station sends a Commit Response Message to the base station within 10 seconds with the RESULT_CODE = '00000000' (Accepted- Operation Successful). End the call at the mobile station. Verify the mobile station successfully stored the updated SSPR information.

11

1 114.4.5 Minimum Standard

3GPP2 C.S0044-A v1.0

2The mobile station shall comply with steps e, h, j, l, and n. The mobile station shall update its 3SSPR information as received in the SSPR Download Request Message.

414.5 OTASP For System Selection and Preferred Roaming - Oversize PRL 514.5.1 Definition
6This test verifies that the PRL resident in a handset shall not be replaced if a new PRL of illegal 7size is downloaded.

814.5.2 Traceability
9(see [14])

103.2.1 113.5.1 123.5.3 133.5.5 144.2.1 154.3 164.5.1 174.5.3 184.5.4

User-Initiated Procedure Message Contents SSPR Parameter Blocks Preferred Roaming List and Extended Preferred Roaming List User-Initiated Procedure Programming Data Download Message Contents SSPR Parameter Blocks Validation Parameter Blocks

1914.5.3 Call Flow

20None

2114.5.4 Method of Measurement 22 23 24 25 26 27 28 29 30 31 32

a. b. c. d. e. Connect the mobile station to the base station as shown in Figure A-3. Confirm that the mobile station is programmed with a non-zero SPCp. Setup a mobile station originated OTASP call using *228 + one of the System Selection Codes in Table 14.1.4-42. Upon call setup, instruct the base station to send a Protocol Capability Request Message to the mobile station. Verify the mobile station sends a Protocol Capability Response Message to the base station with MOB_FIRM_REV, MOB_MODEL, BAND_MODE_CAP and all supported FEATURE_ID and FEATURE_P_REV as listed in ANNEX C. The System Selection for Preferred Roaming feature support is required for this test. If Service Programming Lock is supported, perform the following:

f.

12

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

g. h. i. 1. Instruct the base station to send a Validation Request Message with BLOCK_ID = 00000000 and SPC = SCPp. 2. Verify the mobile station sends a Validation Response Message within 750 ms, and with BLOCK_ID = 00000000 and RESULT_CODE = 00000000 (Accepted Operation Successful). Instruct the base station to send a SSPR Configuration Request Message to the mobile station. Verify the mobile station sends a SSPR Configuration Response Message within 750ms with the requested BLOCK_ID and the associated PARAM_DATA. Instruct the base station to send a SSPR Download Request Message to the mobile station with values of SEGMENT_OFFSET in conjunction with SEGMENT_SIZE that are inconsistent with the preferred roaming list storage capabilities of the mobile station. Verify the mobile station sends a SSPR Download Response Message with RESULT_CODE = 00001000 (Rejected Preferred roaming list length mismatch). Verify the mobile station does not transfer its new PR_LIST to semi-permanent memory after receiving a Commit Request Message. End call at the mobile station

j. k. l.

1814.5.5 Minimum Standard

19The mobile station shall comply with step h, j, and k. The mobile station shall retain its original 20PRL.

2114.6 OTAPA Download Request Processing 2214.6.1 Definition

23This test verifies that the mobile station supports network initiated Over-the-Air-Parameter24Administration (OTAPA). This test also verifies the mobile stations download request processing 25is successful.

2614.6.2 Traceability (see [14]) 273.2.2 283.4 293.5.1 303.5.2 314.2.2 324.3 334.4 344.5.1 354.5.2 2
Network-Initiated Procedure Termination of the Programming Procedure Message Contents NAM Parameter Blocks Network-Initiated Procedure Programming Data Download Termination of the Programming Procedure Message Contents NAM Parameter Blocks

13

1 14.5.4
Validation Parameter Blocks

3GPP2 C.S0044-A v1.0

214.6.3 Call Flow Example(s)

3None

414.6.4 Method of Measurement 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35

g. h. a. b. c. d. e. f. Connect the mobile station to the base station as shown in Figure A-3. Confirm that the mobile station is programmed with a non-zero SPCp. Initiate an OTAPA session from the base station by sending a General Page Message to the mobile station with the SERVICE_OPTION = 0x12 or 0x13. Verify that the mobile station sends a Page Response Message with SERVICE_OPTION = 0x12 or 0x13. Upon successful call setup, instruct the base station to send an OTAPA Request Message to the mobile station with START_STOP = 1. Verify the mobile station sends an OTAPA Response Message to the base station within 750 ms with RESULT_CODE = 00000000 (Accepted Operation Successful). If NAM_LOCK_IND = 1 in the OTAPA Response Message, perform the following: 1. Verify the RAND_OTAPA field is present in the OTAPA Response Message. 2. Instruct the base station to sends a Validation Request Message with BLOCK_ID = 00000010 (Validate SPASM) and a SPASM Parameter Block present to the mobile station. 3. Verify the mobile station sends a Validation Response Message to the base station within 750 ms, and with BLOCK_ID = 00000010 (Validate SPASM) and RESULT_CODE = 00000000 (Accepted Operation Successful). Instruct the base station to send a Protocol Capability Request Message to the mobile station. Verify the mobile station sends a Protocol Capability Response Message to the base station with MOB_FIRM_REV, MOB_MODEL, BAND_MODE_CAP and all supported FEATURE_ID and FEATURE_P_REV as listed in ANNEX C. If Service Programming Lock is supported, perform the following: 1. Instruct the base station to send a Validation Request Message with BLOCK_ID = 00000000 and SPC = SPCP. 2. Verify the mobile station sends a Validation Response Message within 750 ms, and with BLOCK_ID = 00000000 and RESULT_CODE = 00000000 (Accepted Operation Successful). 3. Verify the base station sends a Validation Request Message with BLOCK_ID = 00000001 (Change SPC) and SPC = {a new SPC}.

i.

14

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

23

4. Verify the mobile station sends a Validation Response Message within 750 ms, and with BLOCK_ID = 00000001 (Change SPC) and RESULT_CODE = 00000000 (Accepted Operation Successful). j. If the Electronic Key Exchange is not supported, go to step k; otherwise: 1. Instruct the base station to send a Mobile Station Key Request Message to the mobile station. 2. Verify the mobile station responds with the Mobile Station Key Response Message within 30 seconds, with RESULT_CODE = '00000000' (Accepted Operation Successful). 3. Instruct the base station to send a Key Generation Request Message to the mobile station. 4. Verify the mobile station responds with the Key Generation Response Message within 30 seconds and the RESULT_CODE = '00000000' (Accepted - Operation Successful). 5. Verify the base station and the mobile station successfully perform SSD update procedures. 6. Verify the base station sends the Re-Authenticate Request Message and the mobile station responds with the Re-Authenticate Response Message. 7. At the base station verify Re-Authentication is successful. 8. The base station may enable Signaling Message Encryption and Voice Privacy. k. Instruct the base station to send a Configuration Request Message with one or more of the following NAM Parameter Block Types:

Parameter Block Type CDMA/Analog NAM Mobile Directory Number CDMA NAM IMSI_T

BLOCK_ID 00000000 00000001 00000010 00000011

24 25 26 27 28
29

l.

Verify the mobile station sends a Configuration Response Message within 750ms including each requested BLOCK_ID and associated PARAM_DATA with corresponding RESULT_CODE. Instruct the base station to send a Download Request Message with one or more of the following NAM Parameter Block Types and the corresponding PARAM_DATA:

m.

15

1
Parameter Block Type CDMA/Analog NAM Mobile Directory Number CDMA NAM IMSI_T BLOCK_ID 00000000 00000001 00000010 00000011

3GPP2 C.S0044-A v1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

n. o. p. q. r.

Verify that the mobile station sends a Download Response Message and that RESULT_CODE = '00000000' (Accepted- Operation Successful) within 750ms. Instruct the base station to send a Commit Request Message to the mobile station. Verify the mobile station sends a Commit Response Message to the base station within 10 seconds with the RESULT_CODE = '00000000' (Accepted- Operation Successful). Instruct the base station to send an OTAPA Request Message to the mobile station with START_STOP = 0. Verify the mobile station sends an OTAPA Response Message to the base station within 750 ms, and with RESULT_CODE = 00000000 (Accepted Operation Successful) and NAM_LOCK_IND = 0. Verify that the mobile station releases the call. Verify the mobile station successfully stored the updated NAM information. Originate a call from the mobile station and verify user traffic is present. End the call. Setup a mobile station originated call. Repeat steps e through u with the mobile station already in the Conversation Substate.

s. t. u. v. w. x.

1714.6.5 Minimum Standard

18The mobile station shall comply with steps d, f, h, l, n, p, r, and t. If supported the mobile station 19shall comply with steps i and l.

2014.7 Call Origination during an OTAPA Download Session 2114.7.1 Definition

22This test verifies that the mobile station is able to originate a voice call during an OTAPA 23download session.

2414.7.2 Traceability
25(see [14]) 263.2.2

Network-Initiated Procedure Termination of the Programming Procedure Message Contents

273.4 283.5.1 2

16

13GPP2 C.S0044-A v1.0 14.2.2 24.4 34.5.1

Network-Initiated Procedure Termination of the Programming Procedure Message Contents

414.7.3 Call Flow Example(s)

5None

614.7.4 Method of Measurement 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

g. h. a. b. c. d. e. f. Connect the mobile station to the base station as shown in Figure A-3. Confirm that the mobile station is programmed with a non-zero SPCp. Initiate an OTAPA session from the base station by sending a General Page Message to the mobile station with the SERVICE_OPTION = 0x12 or 0x13. Verify that the mobile station sends a Page Response Message with SERVICE_OPTION = 0x12 or 0x13. Upon successful call setup, instruct the base station to send an OTAPA Request Message to the mobile station with START_STOP = 1. Verify the mobile station sends an OTAPA Response Message to the base station within 750 ms with RESULT_CODE = 00000000 (Accepted Operation Successful). If NAM_LOCK_IND = 1 in the OTAPA Response Message, perform the following: 1. Verify the RAND_OTAPA field is present in the OTAPA Response Message. 2. Instruct the base station to send a Validation Request Message with BLOCK_ID = 00000010 (Validate SPASM) and a SPASM Parameter Block present to the mobile station. 3. Verify the mobile station sends a Validation Response Message to the base station within 750 ms, and with BLOCK_ID = 00000010 (Validate SPASM) and RESULT_CODE = 00000000 (Accepted Operation Successful). Instruct the base station to send a Protocol Capability Request Message to the mobile station. Verify the mobile station sends a Protocol Capability Response Message to the base station with MOB_FIRM_REV, MOB_MODEL, BAND_MODE_CAP and all supported FEATURE_ID and FEATURE_P_REV as listed in ANNEX CY. Originate a voice call from the mobile station. Verify user data in both directions. End call at the mobile station.

i. j. k.

3314.7.5 Minimum Standard

34The mobile station shall comply with steps d, f, h, and j.

17

1
1No text.

3GPP2 C.S0044-A v1.0

18

13GPP2 C.S0044-A v1.0 115 POSITION DETERMINATION TESTS

2The position determination tests in this section apply to mobile stations and base stations that can 3operate in various modes including GPS (Global Positioning System), AFLT (Advanced Forward 4Link Trilateration), and Hybrid (GPS and AFLT). Note that for mobile stations that are capable of 5calculating their location based on AFLT, that capability is not verified in this test.

615.1 Position Determination Tests for GPS, AFLT and Hybrid 715.1.1 Definition
8The purpose of this test is to determine the interoperability of mobile station and base station 9position determination sessions. This test requires that a network originated position 10determination session be triggered by a mobile station originated call.

1115.1.2 Traceability
12(see [25]) 133.2.1 143.2.2 153.2.4

Position Determination Data Message Processing Point-to-point Procedures Reverse Link Message Format

163.2.4.2 Response Element Response Type 17Annex B Request/Response Element Types

1815.1.3 15.1.3 Call Flow Example(s) 19None 2015.1.4 15.1.4 Method of Measurement 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 2
a. Configure 3 base stations available to the mobile station. Ensure connectivity of the base stations to a PDE. The base stations and the PDE shall be configured to allow a specific mobile station originated call type to trigger the PDE to start a position determination session with the mobile station (e.g. an emergency call; in the U.S. this would be a 9-1-1 call). Allow the mobile to become idle on the base station with a dominant PN, with mobile CDMA receive power greater than -85 dBm and pilot Ec/Io greater than -12 dB. If the mobile station and base station supports GPS position location, allow the mobile station to receive GPS signals each with a power level of at least -130 dBm/1MHz. The number of simulated GPS satellites shall be 4 or greater. Setup a mobile station originated call using a dialed number or Service Option that triggers the PDE to start a position determination session (e.g. an emergency call; in the U.S. this would be a 9-1-1 call). Verify the call completes. Verify steps g through n. Note that the ordering of steps g through n does not represent a required ordering of call flow events during the test. In addition to the messages

b. c.

d.

e. f.

1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43
g.

3GPP2 C.S0044-A v1.0 listed in steps g through n, there may be other position determination request elements and response elements exchanged between the base station and mobile station during the test. If the base station sends a position determination Data Burst Message with burst type 000101 that includes a Position Determination Data Message with Request Mobile Station Information (REQ_TYPE = 0010), verify the mobile station sends a position determination Data Burst Message with a burst type 000101 that includes a Position Determination Data Message with Provide Mobile Station Information (RESP_TYPE = 0010). If the mobile station and base station supports GPS position determination and the base station has previously set GPSC_ID to 1 in the Provide Base Station Capability, and if the mobile station has sent a position determination Data Burst Message with burst type 000101 that includes a Position Determination Data Message with Request GPS Acquisition Assistance (REQ_TYPE = 0100), verify the base station sends a position determination Data Burst Message with a burst type 000101 that includes a Position Determination Data Message with Provide GPS Acquisition Assistance (RESP_TYPE = 0100) or a Reject Message with REJ_REASON set to 001. If the mobile station and base station supports GPS position determination and the base station has previously set GPSC_ID to 1 in the Provide Base Station Capability, and if the mobile station has sent a position determination Data Burst Message with burst type 000101 that includes a Position Determination Data Message with Request GPS Sensitivity Assistance (REQ_TYPE = 0101), verify the base station sends a position determination Data Burst Message with a burst type 000101, that includes a Position Determination Data Message with Provide GPS Sensitivity Assistance (RESP_TYPE = 0101) or a Reject Message with REJ_REASON set to 001. If the mobile station and base station supports GPS position determination and the base station has previously set GPSC_ID to 1 in the Provide Base Station Capability, and if the mobile station has sent a position determination Data Burst Message with burst type 000101 that includes a Position Determination Data Message with Request GPS Almanac (REQ_TYPE = 1000), verify the base station sends a position determination Data Burst Message with a burst type 000101 that includes a Position Determination Data Message with Provide GPS Almanac (RESP_TYPE = 1000) or a Reject Message with REJ_REASON set to 001. If the mobile station and base station supports GPS position determination and the base station has previously set GPSC_ID to 1 in the Provide Base Station Capability,, and if the mobile station has sent a position determination Data Burst Message with burst type 000101 that includes a Position Determination Data Message with Request GPS Ephemeris (REQ_TYPE = 1001), verify the base station sends a position determination Data Burst Message with a burst type 000101, that includes a Position Determination Data Message with Provide GPS Ephemeris (RESP_TYPE = 1001) or a Reject Message with REJ_REASON set to 001. If the mobile station and base station supports GPS position determination, and the mobile station is capable of calculating its position based on GPS measurements as

h.

i.

j.

k.

l.

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

m. indicated by LOC_CALC_CAP (Position Calculation Capability) field in the Provide Mobile Station Information Response Element, and the base station has sent a position determination Data Burst Message with burst type 000101 that includes a Position Determination Data Message with Request Location Response (REQ_TYPE = 0001), verify the mobile station sends a position determination Data Burst Message with a burst type 000101, that includes a Position Determination Data Message with Provide Location Response (RESP_TYPE = 0001). If the mobile station and base station supports GPS position determination, and the base station has sent a position determination Data Burst Message with burst type 000101 that includes a Position Determination Data Message with Request Pseudorange Measurement (REQ_TYPE = 0100), verify the mobile station sends a position determination Data Burst Message with a burst type 000101, that includes a Position Determination Data Message with Provide Pseudorange Measurement (RESP_TYPE = 0100). If the base station supports AFLT position determination, and the base station has sent a position determination Data Burst Message with burst type 000101 that includes a Position Determination Data Message with Request Pilot Phase Measurement (REQ_TYPE = 0101), verify the mobile station sends a position determination Data Burst Message with a burst type 000101, that includes a Position Determination Data Message with Provide Pilot Phase Measurement (RESP_TYPE = 0101).

n.

2115.1.5 Minimum Standard 22The mobile station and base station shall comply with the requirements in the following steps:
23For GPS position location the base station shall comply with steps h, i, j, k, l and the mobile 24station shall comply with steps g, l and m. 25For AFLT position location the base station shall comply with step l and the mobile station shall 26comply with steps g and n. 27For Hybrid position location the base station shall comply with steps h, i, j, and k, and the mobile 28station shall comply with steps g, l, m, and n. 29

1
1No text.

3GPP2 C.S0044-A v1.0

13GPP2 C.S0044-A v1.0 116 CONCURRENT SERVICES 216.1 Setup Mobile Station Originated Data Call while Voice Call or Teleservice Call is in 3 Progress 416.1.1 Definition
5This test verifies that, when a voice call is already in progress, a mobile station originated data 6call or teleservice call can be established successfully.

716.1.2 Traceability
8(see [4])

92.6.4.1.2.2.5 102.6.4.1.12 112.6.4.2 122.6.4.3 132.6.4.4 142.6.10 152.7.2.3.2.3 162.7.2.3.2.32 172.7.2.3.2.33 182.7.2.3.2.37 192.7.2.3.2.29 202.7.2.3.2.30 212.7.3.4 222.7.4.25 233.6.4.1.7 243.6.4.1.8 25 263.6.4.2 273.6.4.3 283.6.8 293.7.2.3.2.13 303.7.2.3.2.30 313.7.3.3.2.26

Waiting for Service Action Time Subfunction) Processing the Service Configuration Record) Traffic Channel Initialization Substate Traffic Channel Substate Release Substate Call Control Processing Flash with Information Message Enhanced Origination Message Extended Flash With Information Message Call Cancel Message Resource Release Request Message Resource Release Request Mini Message Mobile Station Reject Order Capability Information Response to Enhanced Origination Message Processing Resource Release Request Message and Resource Release Request Mini Message Traffic Channel Initialization Substate Traffic Channel Substate Call Control Processing Extended System Parameters Message ANSI-41 System Parameters Message Analog Handoff Direction Message

1 13.7.3.3.2.20 23.7.3.3.2.36 33.7.3.3.2.43 43.7.3.3.2.44 53.7.3.3.2.45

Service Connect Message Universal Handoff Direction Message Call Assignment Message Extended Alert With Information Message Extended Flash With Information Message

3GPP2 C.S0044-A v1.0

616.1.3 Call Flow Example(s)

MS Traffic BS Traffic

MS initiates data calll setup

Voice Call in Progress

Enhanced Origination Message (Data SOY, TAGY)

Call Assignment Message (RESPONSE_IND=1, TAGY, CON_REFY) SCM / GHDM / UHDM (SCR += (Data SOY, CON_REFY)

OR
SCM/ UHDM (CC_INFO_INCL=1, RESPONSE_IND=1, TAGY SCR += (Data SOY, CON_REFY))

Voice & Data Call in Progress

Traffic Traffic

7 816.1.4 Method of Measurement 9 10 11 12 13 14 15

a. b. c. d. Connect the mobile station to the base station as shown in Figure A-3. Setup a voice call as described in Test and wait until the voice call is in progress. Ensure retry delay for call origination (i.e. RETRY_DELAYs[001]) is currently not set for the data service option. Initiate a packet data call (e.g. SO33) at the mobile station. Verify the following: 1. The mobile station sends an Enhanced Origination Message with the following fields set as follows:

13GPP2 C.S0044-A v1.0

FIELD TAG SR_ID SERVICE_OPTION DRS VALUE 0001 001 or 010. Service Option corresponding to the data call (e.g. SO33) 1 (data ready to send)

1 2 3 4 5 6 7 8

e.

Configure the base station to accept the call origination from the mobile station. Verify that base station follows one of the following two sequences of events to establish the data call: 1. The base station sends the call assignment prior to service option connection establishment as follows: a. The base station sends a Call Assignment Message to the mobile station, prior to the expiration of the enhanced origination timer at the mobile station, with the following fields set as follows: FIELD RESPONSE_IND TAG ACCEPT_IND CON_REF VALUE 1 (Response to mobile station call request) Value received in the Enhanced Origination Message 1 (call request accepted) Connection reference value for this call

9 10 11 12 13 14 15 16 17 18 19 20
b. Upon successful call assignment, service negotiation is initiated to establish the service option connection corresponding to this call assignment, as follows: 1. The service negotiation is terminated via sending a Service Connect Message, General Handoff Direction Message (containing a SCR), or Universal Handoff Direction Message (containing a SCR). 2. If the Service Connect Message or the Universal Handoff Direction Message is used to terminate the service negotiation, the call assignment included (CC_INFO_INCL) field is set to 0 in these messages.

1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
FIELD CC_INFO_INCL NUM_CALLS_ASSIGN CON_REF VALUE c.

3GPP2 C.S0044-A v1.0 3. The service option connection is established with the same connection reference (CON_REF) as used in the corresponding Call Assignment Message. After the action time of the message used to establish the service option connection corresponding to this call, data call user traffic is exchanged successfully.

d. The voice call is not dropped. 2. The base station sends the call assignment as part of the service option connection establishment as follows: a. The base station initiates service negotiation to establish the service option connection and assign the call. The service negotiation is terminated via sending a Service Connect Message or Universal Handoff Direction Message (containing a SCR) with the following fields set as follows:

1 (call assignment included) 00000001 (single call assignment) Connection reference corresponding to this call set to the same value as used in the SCR. 1 (Response to mobile station call request) Value received in the Enhanced Origination Message

RESPONSE_IND TAG

16 17 18 19 20 21 22 23 24 25
f. b. After the action time of the message used to establish the service option connection corresponding to this call, data call user traffic is exchanged successfully. c. The voice call is not dropped.

Repeat steps b to e with the following modifications: 1. In step b, setup a teleservice call (e.g. SMS, Position Determination, etc.) requiring dedicated channels. 2. In step e, the teleservice call is not dropped after the establishment of the data call.

13GPP2 C.S0044-A v1.0 116.1.5 Minimum Standard

2The mobile station and base station shall comply with the requirements in the following steps d, e 3and f.

416.2 Setup Mobile Station terminated Data Call while Voice Call or Teleservice Call is in 5 Progress 616.2.1 Definition
7This test verifies that, when a voice call is already in progress, a mobile station terminated data 8call (for a dormant data session) or teleservice call can be established successfully.

916.2.2 Traceability
10See 16.1.2.

1116.2.3 Call Flow Example(s)

12
MS Traffic BS Traffic

Voice Call in Progress

Call Assignment Message (RESPONSE_IND=0, Data SOY, CON_REFY) SCM / GHDM / UHDM (SCR += (Data SOY, CON_REFY)

Network initiates data calll setup (for a dormant data session)

OR
SCM/ UHDM (CC_INFO_INCL=1, RESPONSE_IND=0, SCR += (Data SOY, CON_REFY))

Voice & Data Call in Progress

Traffic

Traffic

13
14

1 116.2.4 Method of Measurement 2 3 4 5 6 7 8 9 10 11 12

a. b. c. d.

3GPP2 C.S0044-A v1.0

Connect the mobile station to the base station as shown in Figure A-3. Setup a packet data call (e.g. SO33). Ensure that the data call transitions to the dormant state. Ensure that the dedicated traffic channels are released. Setup a voice call and wait until the voice call is in progress. Trigger network-initiated transition to active state for the dormant packet data call. Verify that base station follows one of the following two sequence of events to establish the data call: 1. The base station sends the call assignment prior to service option connection establishment as follows: a. The base station sends a Call Assignment Message to the mobile station with the following fields set as follows: FIELD RESPONSE_IND VALUE 0 (base station initiated call assignment) 1 (since data call) Service option number corresponding to the data service (e.g. SO33) Connection reference value for this call

BYPASS_ALERT_ANSWER SO

CON_REF

13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 2

b. Upon successful call assignment, service negotiation is initiated to establish the service option connection corresponding to this call assignment, as follows: 1. The service negotiation is terminated via sending a Service Connect Message, General Handoff Direction Message (containing a SCR), or Universal Handoff Direction Message (containing a SCR). 2. If the Service Connect Message or the Universal Handoff Direction Message is used to terminate the service negotiation, the call assignment included (CC_INFO_INCL) field is set to 0 in these messages. 3. The service option connection is established with the same connection reference (CON_REF) as used in the corresponding Call Assignment Message. c. After the action time of the message used to establish the service option connection corresponding to this call, data call user traffic is exchanged successfully.

d. The voice call is not dropped.

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7

2. The base station sends the call assignment as part of the service option connection establishment as follows: a. The base station initiates service negotiation to establish the service option connection and assign the call. The service negotiation is terminated via sending a Service Connect Message or Universal Handoff Direction Message (containing a SCR) with the following fields set as follows: Field CC_INFO_INCL NUM_CALLS_ASSIGN CON_REF Value 1 (call assignment included) 00000001 (single call assignment) Connection reference corresponding to this call set to the same value as used in the SCR. 0 (base station initiated call assignment) 1 (since data call)

RESPONSE_IND BYPASS_ALERT_ANSWER

8 9 10 11 12 13 14 15 16
e.

b. After the action time of the message used to establish the service option connection corresponding to this call, data call user traffic is exchanged successfully. c. The voice call is not dropped.

Repeat steps b to d with the following modifications: 1. In step b, setup a teleservice call (e.g. SMS, Position Determination, etc.) requiring dedicated channels. 2. In step d, the teleservice call is not dropped after the establishment of the data call.

1716.2.5 Minimum Standard

18The mobile station and base station shall comply with the requirements in steps d and e.

1916.3 Setup Mobile Station Originated Voice Call while Data Call or Teleservice Call is in 20 Progress 2116.3.1 Definition
22This test verifies that, when a data call or Teleservice is already in progress, a mobile station 23originated voice call or teleservice call can be established successfully.

2416.3.2 Traceability
25See 16.1.2.

1 116.3.3 Call Flow Example(s)

MS Traffic BS

3GPP2 C.S0044-A v1.0

Traffic

MS initiates voice calll setup

Data Call in Progress

Enhanced Origination Message (Voice SOY, TAGY)

Call Assignment Message (RESPONSE_IND=1, TAGY, CON_REFY) SCM / GHDM / UHDM (SCR += (Voice SOY, CON_REFY)

OR
SCM / UHDM (CC_INFO_INCL=1, RESPONSE_IND=1, TAGY SCR += (Voice SOY, CON_REFY))

Voice & Data Call in Progress

Traffic Traffic

2 316.3.4 Method of Measurement 4 5 6 7 8 9 10

a. b. Connect the mobile station to the base station as shown in Figure A-3. Setup a packet data call (e.g. SO33 as described in test case 13.2). Wait until the data call is in progress. Ensure sufficient traffic is exchanged to keep the data instance in active state. Initiate a voice call at the mobile station. Verify the following: 1. The mobile station sends an Enhanced Origination Message with the following fields set as follows: Field TAG SR_ID SERVICE_OPTION 0001 010 Service Option corresponding to the voice call (Ex. SO 3) Value

c.

11

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8

9

d.

Configure the base station to accept the call origination from the mobile station. Verify that base station follows one of the following two sequence of events to establish the voice call: 1. The base station sends the call assignment prior to service option connection establishment as follows: a. The base station sends a Call Assignment Message to the mobile station, prior to the expiration of the enhanced origination timer at the mobile station, with the following fields set as follows:

Field RESPONSE_IND

Value 1 (Response to mobile station call request) Value received in the Enhanced Origination Message 1 (call request accepted) Connection reference value for this call

TAG

ACCEPT_IND CON_REF
10

11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

b. Upon successful call assignment, service negotiation is initiated to establish the service option connection corresponding to this call assignment, as follows: 1. The service negotiation is terminated via sending a Service Connect Message, General Handoff Direction Message (containing a SCR), or Universal Handoff Direction Message (containing a SCR). 2. If the Service Connect Message or the Universal Handoff Direction Message is used to terminate the service negotiation, the call assignment included (CC_INFO_INCL) field is set to 0 in these messages. 3. The service option connection is established with the same connection reference (CON_REF) as used in the corresponding Call Assignment Message. c. After the action time of the message used to establish the service option connection corresponding to this call, voice call user traffic is exchanged successfully.

d. The data call is not dropped. 2. The base station sends the call assignment as part of the service option connection establishment as follows:

1 1 2 3 4 5

3GPP2 C.S0044-A v1.0 a. The base station initiates service negotiation to establish the service option connection and assign the call. The service negotiation is terminated via sending a Service Connect Message or Universal Handoff Direction Message (containing a SCR) with the following fields set as follows: Field CC_INFO_INCL NUM_CALLS_ASSIGN CON_REF Value 1 (call assignment included) 00000001 (single call assignment) Connection reference corresponding to this call set to the same value as used in the SCR. 1 (Response to mobile station call request) Value received in the Enhanced Origination Message

RESPONSE_IND TAG

7 8 9 10 11 12 13 14 15
e.

b. After the action time of the message used to establish the service option connection corresponding to this call, voice call user traffic is exchanged successfully. c. The data call is not dropped.

Repeat steps b to d with the following modifications: 1. In step b, setup a teleservice call (e.g. SMS, Position Determination, etc.) requiring dedicated channels. 2. In step d, the teleservice call is not dropped after the establishment of the data call.

1616.3.5 Minimum Standard

17The mobile station shall comply with the requirements in steps c, d and e. 18The base station shall comply with the requirements in step d. 19

2016.4 Setup Mobile Station terminated Voice Call while Data Call or Teleservice Call is in 21 Progress 2216.4.1 Definition
23This test verifies that, when a data call or Teleservice is already in progress, a mobile station 24terminated voice call or teleservice call can be established successfully.

10

13GPP2 C.S0044-A v1.0 116.4.2 Traceability

2See 16.1.2.

316.4.3 Call Flow Example(s)

MS Traffic BS Traffic

Data Call in Progress

Call Assignment Message (RESPONSE_IND=0, Voice SOY, CON_REFY) SCM / GHDM / UHDM (SCR += (Voice SOY, CON_REFY)

Network initiates voice call setup

OR
SCM/UHDM (CC_INFO_INCL=1, RESPONSE_IND=0, SCR += (Voice SOY, CON_REFY))

AWIM / EAWIM Connect Order

Voice & Data Call in Progress

Traffic Traffic

4
5

616.4.4 Method of Measurement 7 8 9 10 11 12 13 14

a. b. Connect the mobile station to the base station as shown in Figure A-3. Setup a packet data call (e.g. SO33 a described in test case 13.2). Wait till the data call is in progress. Ensure sufficient traffic is exchanged to keep the data instance in active state. Trigger a network-initiated voice call. Verify that base station follows one of the following two sequences of events to establish the voice call: 1. The base station sends the call assignment prior to service option connection establishment as follows:

c.

11

1 1 2
3

3GPP2 C.S0044-A v1.0 a. The base station sends a Call Assignment Message to the mobile station with the following fields set as follows:

Field RESPONSE_IND BYPASS_ALERT_ANSWER SO CON_REF

Value 0 (base station initiated call assignment) 0 (since voice call) Service option number corresponding to the voice service (Ex. SO 3) Connection reference value for this call

5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

b. Upon successful call assignment, service negotiation is initiated to establish the service option connection corresponding to this call assignment, as follows: 1. The service negotiation is terminated via sending a Service Connect Message, General Handoff Direction Message (containing a SCR), or Universal Handoff Direction Message (containing a SCR). 2. If the Service Connect Message or the Universal Handoff Direction Message is used to terminate the service negotiation, the call assignment included (CC_INFO_INCL) field is set to 0 in these messages. 3. The service option connection is established with the same connection reference (CON_REF) as used in the corresponding Call Assignment Message. c. After the action time of the message used to establish the service option connection corresponding to this call, the mobile station plays an alert to indicate an incoming call. After answering the call from the mobile station, voice call user traffic is exchanged successfully.

d. The data call is not dropped. 2. The base station sends the call assignment as part of the service option connection establishment as follows: a. The base station initiates service negotiation to establish the service option connection and assign the call. The service negotiation is terminated via sending a Service Connect Message or Universal Handoff Direction Message (containing a SCR) with the following fields set as follows:

12

13GPP2 C.S0044-A v1.0

Field CC_INFO_INCL NUM_CALLS_ASSIGN CON_REF Value 1 (call assignment included) 00000001 (single call assignment) Connection reference corresponding to this call set to the same value as used in the SCR. 0 (base station initiated call assignment) 0 (since voice call)

RESPONSE_IND BYPASS_ALERT_ANSWER
1

2 3 4 5 6 7 8 9 10 11
d.

b. After the action time of the message used to establish the service option connection corresponding to this call, the mobile station plays an alert to indicate an incoming call. After answering the call from the mobile station, voice call user traffic is exchanged successfully. c. The data call is not dropped.

Repeat steps b and c with the following modifications: 1. In step b, setup a teleservice call (e.g. SMS, Position Determination, etc.) requiring dedicated channels. 2. In step c, the teleservice call is not dropped after the establishment of the data call.

1216.4.5 Minimum Standard

13The mobile station and base station shall comply with the requirements in steps c and d. 14

1516.5 Mobile Station Release of a Single Call While Voice and Data Calls are in Progress 1616.5.1 Definition
17This test verifies that, when both voice and data calls are in progress, mobile station can release 18one of the calls successfully and the other call continues uninterrupted.

1916.5.2 Traceability
20See 16.1.2.

13

1 116.5.3 Call Flow Example(s)

MS Traffic BS

3GPP2 C.S0044-A v1.0

Traffic

MS initiates release of one of the calls

Voice & Data Calls in Progress

Service Request Message ( SCR -= CON_REFY)

or
Resource Release Request Message (CON_REFY)

SCM / GHDM / UHDM (SCR -= CON_REFY)

Remaining Call Continues

Traffic Traffic

2 316.5.4 Method of Measurement 4 5 6 7 8 9 10 11 12 13 14 15 16

17

a. b.

Connect the mobile station to the base station as shown in Figure A-3. Setup both a voice call and a packet data call (e.g. SO33). Wait till both the voice call and the data call are in progress. Ensure sufficient traffic is exchanged to keep the data instance in active state. Initiate the release of the voice call at the mobile station. Verify the following: 1. The mobile station sends a Service Request Message or Resource Release Request (Mini) Message requesting the release of the voice call. a. If the mobile station sends a Service Request Message, the service option connection record corresponding to the voice call is omitted from the Service Configuration information record included in this message. b. If the mobile station sends a Resource Release Request (Mini) Message, the following fields shall be set as follows:

c.

14

13GPP2 C.S0044-A v1.0

Field GATING_DISCONNECT_IND CON_REF Value 0 (release of a call requested) Connection reference corresponding to the voice call to be released

1 2 3 4 5 6 7 8 9 10 11 12 13 14
d.

2. Upon receiving the Service Request Message or Resource Release Request (Mini) Message requesting the release of the voice call, the base station sends a Service Connect Message, General Handoff Direction Message (with a SCR), or Universal Handoff Direction Message (with a SCR) as follows: a. The service option connection record corresponding to the voice call is omitted from the Service Configuration information record included in this message. 3. At the action time of the Service Connect Message, General Handoff Direction Message, or Universal Handoff Direction Message used to release the voice call, the voice traffic no longer flows. 4. The data call is not dropped. Repeat steps a though c with the following exception: in step c, initiate the release of the data call at the mobile station. All the expected results are as in step c with the difference that the call being released is the data call.

1516.5.5 Minimum Standard

16The mobile station and base station shall comply with the requirements in step c and d.

1716.6 Base Station Release of a Single Call While Voice and Data Calls are in Progress 1816.6.1 Definition
19This test verifies that, when both voice and data calls are in progress, base station can release 20one of the calls successfully and the other call continues uninterrupted.

2116.6.2 Traceability
22See 16.1.2.

15

1 116.6.3 Call Flow Example(s)

MS Traffic BS

3GPP2 C.S0044-A v1.0

Traffic

Voice & Data Calls in Progress

Network initiates release of one of the calls

SCM / GHDM / UHDM (SCR -= CON_REFY)

Remaining Call Continues

Traffic Traffic

2 316.6.4 Method of Measurement 4 5 6 7 8 9 10 11 12 13 14 15 16 17

a. b. Connect the mobile station to the base station as shown in Figure A-3. Setup both a voice call and a packet data call (e.g. SO33). Wait till both the voice call and the data call are in progress. Ensure sufficient traffic is exchanged to keep the data instance in active state. Trigger a network-initiated release of the voice call. Verify the following: 1. The base station sends a Service Connect Message, General Handoff Direction Message (with a SCR), or Universal Handoff Direction Message (with a SCR), where the service option connection record corresponding to the voice call is omitted from the Service Configuration information record included in this message. 2. At the action time of the Service Connect Message, General Handoff Direction Message, or Universal Handoff Direction Message used to release the voice call, the voice traffic no longer flows. 3. The data call is not dropped.

c.

16

13GPP2 C.S0044-A v1.0 1 2 3

d. Repeat steps a though c with the following exception: in step c, initiate the release of the data call at the mobile station. All the expected results are as in step c with the difference that the call being released is the data call.

416.6.5 Minimum Standard

5The mobile station and base station shall comply with the requirements in steps c and d.

616.7 Correct Handling of Call Control Signaling 716.7.1 Definition

8This test verifies that, when one or more calls are in progress, mobile station initiated and network 9initiated call control signaling messages are handled correctly.

1016.7.2 Traceability
11See 16.1.2.

17

1 116.7.3 Call Flow Example(s)

MS Traffic BS

3GPP2 C.S0044-A v1.0

Traffic

Voice Call in Progress

FWIM / EFWIM (CON_REFINCL=0) / EFWIM (CON_REFVOICE) FWIM / EFWIM (CON_REFINCL=0) / EFWIM (CON_REFVOICE)

Add data call: Voice & Data Calls in Progress

If voice SOC listed first in SCR:

FWIM / EFWIM (CON_REFINCL=0) / EFWIM (CON_REFVOICE) FWIM / EFWIM (CON_REFINCL=0) / EFWIM (CON_REFVOICE)

If data SOC listed first in SCR:

EFWIM (CON_REFVOICE)

EFWIM (CON_REFVOICE)

Release Data Call: Voice Call in Progress

FWIM / EFWIM (CON_REFINCL=0) / EFWIM (CON_REFVOICE) FWIM / EFWIM (CON_REFINCL=0) / EFWIM (CON_REFVOICE) Traffic Traffic

2
3

416.7.4 Method of Measurement 5 6

a. b. Connect the mobile station to the base station as shown in Figure A-3. Setup a voice call and wait until the voice call is in progress.

18

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 2

e. d. c. If applicable, trigger an action at the mobile station that will result in either a Flash With Information Message or Extended Flash With Information Message for a voice call being transmitted to the base station (Ex. Trigger an action that utilizes the Keypad Facility information record). Verify the following: 1. The mobile station sends a Flash With Information Message, an Extended Flash With Information Message with the CON_REF_INCL field set to 0, or an Extended Flash With Information Message with the CON_REF field set to the connection reference corresponding to the voice call. 2. The information record is delivered correctly in the network. If applicable, trigger an action at the network that will result in either a Flash With Information Message or Extended Flash With Information Message being transmitted to the mobile station (e.g. Trigger an action that utilizes the Display information record). Verify the following: 1. The base station sends a Flash With Information Message, an Extended Flash With Information Message with the CON_REF_INCL field set to 0, or an Extended Flash With Information Message with the CON_REF field set to the connection reference corresponding to the voice call. 2. The information record is correctly handled in the mobile station. Setup a mobile station originated or mobile station terminated packet data call (e.g. SO33). When the base station sends a Service Connect Message, General Handoff Direction Message, or Universal Handoff Direction Message to establish the service option connection corresponding to the data call, note whether the service option connection corresponding to the voice call or data call is listed as the first entry in the SCR. If applicable, trigger an action at the mobile station that will result in either a Flash With Information Message or Extended Flash With Information Message for a voice call being transmitted to the base station (Ex. Trigger an action that utilizes the Keypad Facility information record). Verify the following: 1. If the service option connection corresponding to the voice call is listed as the first entry in the SCR: a. The mobile station sends a Flash With Information Message, an Extended Flash With Information Message with the CON_REF_INCL field set to 0, or an Extended Flash With Information Message with the CON_REF field set to the connection reference corresponding to the voice call. b. The information record is delivered correctly in the network. 2. If the service option connection corresponding to the data call is listed as the first entry in the SCR: a. The mobile station sends an (Extended) Flash With Information Message with the CON_REF field set to the connection reference corresponding to the voice call.

f.

19

1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
j. h. i. g.

3GPP2 C.S0044-A v1.0 b. The information record is delivered correctly in the network. If applicable, trigger an action at the network that will result in either a Flash With Information Message or Extended Flash With Information Message for a voice call being transmitted to the mobile station (Ex. Trigger an action that utilizes the Display information record). Verify the following: 1. If the service option connection corresponding to the voice call is listed as the first entry in the SCR: a. The base station sends a Flash With Information Message, an Extended Flash With Information Message with the CON_REF_INCL field set to 0, or an Extended Flash With Information Message with the CON_REF field set to the connection reference corresponding to the voice call. b. The information record is correctly handled in the mobile station. 2. If the service option connection corresponding to the data call is listed as the first entry in the SCR: a. The base station sends an Extended Flash With Information Message with the CON_REF field set to the connection reference corresponding to the voice call. b. The information record is correctly handled in the mobile station. Perform a mobile station initiated or base station initiated release of the data call. Wait till this operation is successful. If applicable, trigger an action at the mobile station that will result in either a Flash With Information Message or Extended Flash With Information Message for a voice call being transmitted to the base station (Ex. Trigger an action that utilizes the Keypad Facility information record). Verify the following: 1. The mobile station sends a Flash With Information Message, an Extended Flash With Information Message with the CON_REF_INCL field set to 0, or an Extended Flash With Information Message with the CON_REF field set to the connection reference corresponding to the voice call. 2. The information record is delivered correctly in the network. If applicable, trigger an action at the network that will result in either a Flash With Information Message or Extended Flash With Information Message being transmitted to the mobile station for a voice call (Ex. Trigger an action that utilizes the Display information record). Verify the following: 1. The base station sends a Flash With Information Message, an Extended Flash With Information Message with the CON_REF_INCL field set to 0, or an Extended Flash With Information Message with the CON_REF field set to the connection reference corresponding to the voice call. 2. The information record is correctly handled in the mobile station.

20

13GPP2 C.S0044-A v1.0 116.7.5 Minimum Standard

2The mobile station and base station shall comply with the requirements in steps c, d, f, g, i and j,. 3The base station shall comply with the requirements in steps d, g, and j.

416.8 Analog Handoff Direction Message Terminates All Calls Except One 516.8.1 Definition
6This test verifies that, when the base station directs the mobile station to perform a handoff from 7the CDMA system to an analog system by sending an Analog Handoff Direction Message, all 8calls except for the one indicated by the Analog Handoff Direction Message are terminated.

916.8.2 Traceability
10See 16.1.2.

1116.8.3 Call Flow Example(s)

MS Traffic BS Traffic

Voice + Data calls in progress

MS terminates all calls except one identified by CON_REFX
Analog Analog Handoff Direction Message (CON_REFX)

Single call continues

12 1316.8.4 Method of Measurement 14 15 16 17 18 19 20 21 22

a. b. Connect the mobile station to the base station as shown in Figure A-5. Setup a voice call and a packet data call (e.g. SO33). Wait till both calls are in progress. Note whether the service option connection corresponding to the voice call or data call is listed as the first entry in the Service Configuration Information Record. Trigger the network to direct the mobile station to perform a handoff from the CDMA system to an analog system in a band class that the mobile station supports and to maintain the voice call. Verify the following: 1. The base station sends an Analog Handoff Direction Message to the mobile station, with the CON_REF_INCL/CON_REF fields set as follows:

c.

21

1 1 2 3 4 5 6 7 8 9 10 11 12 13

3GPP2 C.S0044-A v1.0 a. If the service option connection corresponding to the voice call was listed as the first entry in the Service Configuration information record, then either the CON_REF_INCL field is set to 0 or the CON_REF field is set to the connection reference of the voice call. b. If the service option connection corresponding to the data call was listed as the first entry in the Service Configuration information record, then the CON_REF field is set to the connection reference of the voice call. 2. Upon receiving this message, the mobile station performs the following: a. The mobile station terminates the data call and maintains the voice call. b. The mobile station shall perform handoff to the analog system indicated by the Analog Handoff Direction Message.

1416.8.5 Minimum Standard

15The mobile station and base station shall comply with the requirements in step c.

1616.9 Release A Mobile Station in Concurrent Calls with a Release A Base Station Hands 17 off to Pre-Release A Base Station 1816.9.1 Definition
19This test verifies that, when a Release A mobile station currently in concurrent calls with a 20Release A base station is handed off to a Pre-Release A base station, only a single call is 21maintained and this call continues successfully.

2216.9.2 Traceability
23See 16.1.2.

2416.9.3 Call Flow Example(s)

MS (Rel A) Traffic BS (Rel A) BS (Pre-Rel A)

Voice + Data calls in progress

Voice or data call is released as instructed in the new SCR
GHDM/UHDM (P_REV<7, SCR_new: Voice or Data)

Voice or Data call in progress

25

22

13GPP2 C.S0044-A v1.0 1 216.9.4 Method of Measurement 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

a. b. c. Connect a MOB_P_REV 7 mobile station to base stations 1 and 2 as in Figure A-5. Configure base station 1 to support P_REV=7 and base station 2 to support P_REV<7. Setup a mobile station originated or mobile station terminated voice call on base station 1. Set up a mobile station originated or mobile station terminated packet data call (e.g. SO33). Wait till both voice and data calls are in progress. Ensure sufficient traffic is exchanged to keep the data instance in active state. Trigger base station 1 to direct the mobile station to handoff to base station 2. Verify the following: 1. The base station shall send a General Handoff Direction Message or a Universal Handoff Direction Message to the mobile station, with the Service Configuration information record included and set as follows: a. The service option connection corresponding to the call to be maintained is included and uses the same connection reference value (CON_REF) as currently used for this call. b. The service option connection corresponding to the other call is omitted. 2. At the action time of this message, the mobile station shall release the call corresponding to the omitted service option connection and hands off to the base station 2. 3. The remaining call continues successfully in the base station 2.

d.

2416.9.5 Minimum Standard

25The mobile station and base station shall comply with the requirements in the following steps: 26Step d. 27

2816.10 Release A Mobile Station Hands off between Release A Base Station with Change in 29 Concurrent Calls Support 3016.10.1 Definition
31This test verifies that, when a Release A mobile station currently in call with a Release A base 32station is handed off to another Release A base station, and where there is a change in 33Concurrent Calls support, calls are released/added/maintained successfully.

3416.10.2 Traceability
35See 16.1.2.

23

1 116.10.3 Call Flow Example(s)

MS (Rel A) Traffic BS (Rel A: CS_SUPPORTED=1)

3GPP2 C.S0044-A v1.0

BS (Rel A: CS_SUPPORTED=0)

Voice and Data call in progress

GHDM/UHDM (P_REV=7, SCR_new: Voice or Data, CS_SUPPORTED=0)

Voice or data call is released

Voice or Data call in progress

UHDM (P_REV=7, SCR_new: Voice and Data, CS_SUPPORTED=1, CC_INFO_INCL=1)

Voice or data call is added

Voice and Data call in progress

2 316.10.4 Method of Measurement 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 2

a. Connect the MOB_P_REV=7 mobile station (Release A) to two P_REV=7 base stations (Release A) as shown in Figure A-5. Configure base station 1 to support Concurrent Services and base station 2 not to support Concurrent. Setup a mobile station originated or mobile station terminated voice call on base station 1. Set up a mobile station originated or mobile station terminated packet data call (e.g. SO33). Wait till both voice and data calls are in progress. Ensure sufficient traffic is exchanged to keep the data instance in active state. Trigger the base station to direct the mobile station to handoff from base station 1 to base station 2. Verify the following: 1. The base station shall send a General Handoff Direction Message or a Universal Handoff Direction Message to the mobile station, with the Service Configuration information record included and set as follows: a. The CS_SUPPORTED field is set to 0. b. The service option connection corresponding to the call to be maintained is included and uses the same connection reference value (CON_REF) as currently used for this call.

b. c.

d.

24

13GPP2 C.S0044-A v1.0 1 2 3 4 5 6 7 8 9 10 11

12

c.

The service option connection corresponding to the other call is omitted.

2. At the action time of this message, the mobile station shall release the call corresponding to the omitted service option connection and hands off to the new Release A base station. 3. The remaining call continues successfully in the new Release A base station. e. Trigger the base station to direct the mobile station to handoff from base station 2 to base station 1 that supports concurrent services and with an additional call added (voice or packet data call (e.g. SO33)). Verify the following: 1. The base station shall send a Universal Handoff Direction Message to the mobile station, with the following fields set as follows:

Field P_REV SCR_INCLUDED CON_REF SERVICE_OPTION CON_REF SERVICE_OPTION CC_INFO_INCL NUM_CALLS_ASSIGN CON_REF RESPONSE_IND

Value 7 (Release A base station) 1 (SCR is included) Connection reference for original call same as the value currently in use SO for original call Connection reference for the SOC corresponding to the new call SO for the new call 1 (call assignment included) 00000001 (single call assignment) Same value as connection reference for the new call 0 (base station initiated call assignment)

13 14 15 16

2. At the action time of this message, the mobile station hands off to base station 1 and connects the new call. 3. The new call is connected successfully. The original call continues successfully.

1716.10.5 Minimum Standard

18The mobile station and base station shall comply with the requirements in steps d and e 19

25

13GPP2 C.S0044-A v1.0 117 EMERGENCY CALLS 217.1 Global Emergency Call Support When Mobile Station is in Idle State 317.1.1 Definition
4This test verifies that the mobile station can originate a global emergency call during idle state 5and that the base station processes this as an emergency call.

617.1.2 Traceability
7(see [4])

82.7.1.3.2.4

Origination Message

917.1.3 Call Flow Example(s)

10None

1117.1.4 Method of Measurement 12 13 14 15 16 17 18 19 20 21 22 23

a. If the mobile station is capable of recognizing emergency number by analyzing the dialed digits, originate an emergency call from the mobile station by dialing an emergency number. Verify the GLOBAL_EMERGENCY_CALL field is set to 1 in the Origination Message and that the base station processes the origination as an emergency call. End the call. If the mobile station has a special interface to initiate an emergency call, originate an emergency call from the mobile station using this special interface. Verify that the mobile station sets the GLOBAL_EMERGENCY_CALL field to 1 in the Origination Message and that the base station processes the origination as an emergency call. End the call.

b. c. d. e.

f.

2417.1.5 Minimum Standard

25The mobile station shall comply with the following steps as supported: Step b and e. 26The base station shall comply with the following steps as supported: Step b and e.

2717.2 Global Emergency Call Support When Mobile Station is in Voice Call. 2817.2.1 Definition
29This test verifies that the mobile station can originate a global emergency call while another voice 30call is in progress and that the base station processes this as an emergency call. This test is 31applicable only to mobile stations not capable of concurrent services.

1 117.2.2 Traceability
2(see [4])

3GPP2 C.S0044-A v1.0

32.7.1.3.2.4 42.7.2.3.2.32 52.7.2.3.2.3 62.7.2.3.2.33

Origination Message Enhanced Origination Message Flash With Information Message Extended Flash With Information Message

717.2.3 Call Flow Example(s)

8None

917.2.4 Method of Measurement 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

a. b. c. Connect the base station to the mobile station as shown in Figure A-3. Originate a voice call from the mobile station. Verify audio in both directions. If the mobile station is capable of recognizing emergency number by analyzing the dialed digits and the mobile station does not support concurrent service, originate an emergency call from the mobile station by dialing an emergency number (e.g. dialing 91-1 and press SEND). Verify that the mobile station sends a Flash With Information Message or an Extended Flash With Information Message with the Global Emergency Call information record included and that the base station processes the message as an emergency call. End the call. Originate a voice call from the mobile station. Verify audio in both directions. If the mobile station has a special interface to initiate an emergency call, originate an emergency call from the mobile station using this special interface. Verify that the mobile station sends Flash With Information Message or Extended Flash With Information Message with the Global Emergency Call information record included and that the base station processes the origination as an emergency call. End the call.

d.

e. f. g. h.

i.

2717.2.5 Minimum Standard

28The mobile station shall comply with the following steps as supported: Step d and h. 29The base station shall comply with the following steps as supported: Step d and h.

3017.3 Global Emergency Call Support When Mobile Station is in a Data Call 3117.3.1 Definition
32This test verifies that the mobile station can originate a global emergency call when a packet data 33call (Ex. SO33) is in progress and that the base station processes this as an emergency call. This 34test is applicable if both the base station and mobile station support concurrent services.

13GPP2 C.S0044-A v1.0 117.3.2 Traceability

2(see [4])

32.7.1.3.2.4 42.7.2.3.2.32 52.7.2.3.2.3 62.7.2.3.2.33

Origination Message Enhanced Origination Message Flash With Information Message Extended Flash With Information Message

717.3.3 Call Flow Example(s)

8None

917.3.4 Method of Measurement 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

a. b. c. Connect the base station to the mobile station as shown in Figure A-3. Originate a data call from the mobile station. If the mobile station is capable of recognizing emergency number by analyzing the dialed digits, then while the data call is up, originate an emergency call from the mobile station by dialing an emergency number (e.g. dialing 9-1-1 and press SEND). Verify the mobile station sends an Enhanced Origination Message with the GLOBAL_EMERGENCY_CALL field set to 1 and that the base station processes the origination as an emergency call. End the calls. Originate a data call from the mobile station. If the mobile station has a special interface to initiate an emergency call, then while the data call us up, originate an emergency call from the mobile station using this special interface. Verify the mobile station sends an Enhanced Origination Message with the GLOBAL_EMERGENCY_CALL field set to 1 and that the base station processes the origination as an emergency call. End the calls.

d.

e. f. g.

h.

i.

2717.3.5 Minimum Standard

28The mobile station shall comply with the following steps as supported: Step d and h. 29The base station shall comply with the following steps as supported: Step d and h.

3017.4 Emergency Call on a System that is Negative on PRL or SID List 3117.4.1 Definition
32This test verifies that the mobile station acquires a system that is negative in its (Extended) 33Preferred Roaming List for an emergency call only.

1 117.4.2 Traceability
2(see [14])

3GPP2 C.S0044-A v1.0

33.5.5 4ANNEX C

Preferred Roaming List and Extended Preferred Roaming List System Selection and Acquisition

517.4.3 Call Flow

6None

717.4.4 Method of Measurement 8 9 10 11 12 13 14 15 16 17

a. b. c. d. e. f. g. h. i. Connect the mobile station and base station as shown in Figure A-3. Program the base stations SID into the PRL as a negative system. Enable power-on registration. Disable all other forms of registration. Power on the mobile station, and monitor it for a sufficient period of time to permit it to acquire the base station (typically 30 seconds). Verify the mobile station does not attempt to access the base station. Setup an emergency call from the mobile station (911 in the United States). Verify the mobile station sends an Origination Message to the base station. Verify the emergency call is routed to the PSAP or equivalent emulation unit. End the emergency call from the mobile station.

1817.4.5 Minimum Standard

19The mobile station shall comply with step e and g. 2017.5 Optional Emergency Calls 2117.5.1 Definition 22The requirements in these test cases are applicable regionally. For example, in the U.S., the 23FCC has certain requirements for the mobile station and the base station when an emergency 9241-1 call is initiated. The purpose of this test is to determine the mobile stations capability to 25initiate an emergency call under 3 different initial conditions: (1) No calls active or dormant, (2) 26data call is active and (3) data call in dormant mode. 2717.5.2 Traceability 28None 2917.5.3 Call Flow Example(s) 30None 3117.5.4 Method of Measurement 32 33 34

a. b.

Allow the mobile to become idle on the base station. Originate emergency call from the mobile station and verify that the emergency call is connected. Release the emergency call.

13GPP2 C.S0044-A v1.0

1 2 3 4 5

c. d. e.

Setup SO33 call. While SO33 call is active, originate emergency call from the mobile station and verify that the emergency call is connected. Release the emergency call. Allow SO33 to go dormant. While SO33 call is dormant, originate emergency call from the mobile station and verify that the emergency call is connected. Release the emergency call.

617.5.5 Minimum Standard 7The mobile station and base station shall comply with the requirements in steps b, c, and e 8(according to applicable regional requirements). 9

1
1No text.

3GPP2 C.S0044-A v1.0

13GPP2 C.S0044-A v1.0 118 HRPD

2For HRPD test cases described in chapter 18, the terms mobile station and base station 3represent the access terminal (AT) and access network (AN) respectively. 4For all tests in Chapter 18, Session Security should be enabled if supported. 518.1 HRPD Acquisition and Idle Mode Operation 618.1.1 Definition 7These tests will verify that AT acquires the HRPD system and performs idle monitoring of the 8HRPD control channel. These tests also verify that upon losing HRPD system during idle 9operation, AT tries to reacquire the HRPD system. 1018.1.2 Traceability 11(see [24])

1210.2.6.1.4.2.1 Initial Acquisition 1318.1.3 Call Flow Example(s)

14None 1518.1.4 Method of measurement 16 17 18 19 20 21 22

a. b. c. d. e. f.

Power up the AT. Verify that the AT acquires HRPD system Verify that after acquiring HRPD system, the AT performs idle monitoring of the control channel on HRPD system Disable the forward link to the AT. Verify that AT declares system lost Enable the forward link and verify that the AT re-acquires HRPD system.

2318.1.5 Minimum Standard 24The AT shall comply with c and f. 25HRPD Session Establishment 2618.1.6 Definition 27This test verifies that during the HRPD session establishment, a Unicast AT Identifier (UATI) is 28assigned to the AT. 2918.1.7 Traceability

30[see 24] 317 Session Layer, 8 Connection Layer, 10 MAC Layer 3218.1.8 Call Flow Example(s)
33None

1
118.1.9 Method of Measurement 2 3 4 5 6 7 8

3GPP2 C.S0044-A v1.0

a. b. c. d. e. f.

Connect the AT to the AN as shown in figure A-3. Ensure AT has not established HRPD session with AN (no UATI has been assigned by AN) Cause the AT to acquire HRPD AN. Verify the AT issues a UATIRequest Message. Verify the AN issues a UATIAssignment Message. Record the UATI. Verify the AT issues a UATIComplete Message.

918.1.10 Minimum Standard 10Verify steps d, e and f. 11HRPD Session Configuration and Management with Subnet change 1218.1.11 Definition 13This test verifies session configuration and management associated with a subnet change. If the 14AT moves to a new subnet and if the new subnet can retrieve the ATs prior session configuration 15from the old subnet, new session negotiations are not needed. If the Prior session attribute is 16supported by the AN, it can use the previously negotiated set of session parameters. 1718.1.12 Traceability 18(see [24]) 19Chapter 7 Session Layer

2018.1.13 Call Flow Example(s)

21None 2218.1.14 Method of measurement 23 24 25 26 27 28 29 30 31 32 33 34 35

a. b. c.

Power up the AT and place it where it can receive good HRPD signal. Verify that AT acquires and goes to idle state. Verify that AT requests a UATI and AN assigns it. Verify that after receiving the UATIAssignment Message, the AT opens a new HRPD connection and starts session negotiation using sets of ConfigRequest/ConfigResponse messages. After a HRPD session is opened successfully, power down the AT. Move the AT to another subnet where prior session attribute is accepted and power up the AT. Verify that once the AT acquires the new subnet, the AT sends a ConfigRequest with PriorSession attribute and ensure that the AN sends back a ConfigResponse accepting the PriorSession attribute. Verify that AT does not go through a new set of session negotiations after receiving the ConfigResponse from the AN.

d. e. f.

3618.1.15 Minimum Standard 37The AT shall comply with steps b, c, e and f.

13GPP2 C.S0044-A v1.0

1AT Color Code and UATI24 218.1.16 Definition 3This test verifies that the AT is assigned a valid Color Code and UATI024 during an HRPD 4session establishment. 518.1.17 Traceability

6(see [24]) 77 Session Layer, 8 Connection Layer, 10 MAC Layer 8Section 7.3.7.1.5.1 918.1.18 Call Flow Example(s)
10None 1118.1.19 Method of Measurement 12 13 14 15 16 17

a. b. c. d.

Connect the AT to the AN as shown in Figure A-3. Cause the AN to issue a new UATI to the AT. Verify a valid Color Code (UATIColorCode) and UATI24 (UATI024) are assigned to the AT in the UATIAssignment Message. Record the Color Code and UATI024. If the AT receives a UATIAssignment message, verify that the AT transmits a UATIComplete message.

1818.1.20 Minimum Standard 19Verify that the AN complies with step c. 20Verify that the AT complies with step d. 21HRPD Connection Setup 2218.1.21 Definition 23This test verifies that when the HRPD connection is idle (session active and PPP dormant), an AT 24initiated ping and AN initiated ping shall be successful. This test will verify that AT can setup a 25HRPD packet data connection when its state is idle. 2618.1.22 Traceability

27(see [24]) 287 Session Layer, 8 Connection Layer, 10 MAC Layer 2918.1.23 Call Flow Example(s)
30None 3118.1.24 Method of Measurement 32 33 34 35 36

a. b. c. d.

Connect the AT to the AN as shown in Figure A-3. Set up an AT originated call and allow the PPP session to go dormant. Ensure that the AT connection is idle on HRPD system Issue a ping command from the AT to a remote host to setup an HRPD AT originated connection.

1
1 2 3 4 5 6 7 8 9 10 11 12

3GPP2 C.S0044-A v1.0 e. Verify AT sends a Connection Request Message to AN and that AN sends a ACAck and a TrafficChannelAssignment Message to the AT. Verify AT sends a TrafficChannelCompleteMessage and that connection enters active state. Verify the AN transmits the ping response from the remote host and the AT receives it. Issue a ping command from the remote host to the AT using the IP address assigned to the AT. Verify the remote host receives a ping response from the AT. Wait for connection AT to go idle. Issue a ping command from the remote host to the AT using the IP address assigned to the AT. Verify the AT and the AN establish the HRPD connection and the remote host receives a ping response from the AT.

f. g. h. i. j. k.

1318.1.25 Minimum Standard 14The AT shall comply with steps e, f, h and k. 15The AN shall comply with steps e, f, h and k. 16AN Packet Data Inactivity Timer 1718.1.26 Definition 18This test is only required for access networks that have a packet data inactivity timer. This test 19verifies the AN releases the traffic channel after expiration of the AN packet data inactivity timer. 20The test verifies the link layer connection can be re-activated from idle state. 2118.1.27 Traceability: 22(see [24]) 237 Session Layer, 8 Connection Layer, 9 Security Layer, 10 MAC Layer 24(see [26]) 252.4.1.2

Termination

2618.1.28 Call Flow Example(s)

27None 2818.1.29 Method of Measurement 29 30 31 32 33 34 35 36 37 38 39

a. b. c. d. e. f. g.

Connect the AT to the AN as shown in Figure A-3. Set the PCF PPP inactivity timer to 20 seconds. Setup an HRPD AT originated connection. Initiate a Telnet session to a remote host. Record the IP address assigned to the AT. Exit the Telnet session. Wait for the AN packet data inactivity timer to expire. Verify the AN sends a ConnectionClose Message with CloseReason = 0 (normal Close). Verify the AT sends a ConnectionClose Message with CloseReason = 1 (Close Reply) and connection goes to idle state. Setup an HRPD AT originated connection.

h.

13GPP2 C.S0044-A v1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 1418.1.30 Minimum Standard 15The AT shall comply with steps g, k, n, and p. 16The AN shall comply with steps g, and p. 17Forward File Transfer 1818.1.31 Definition 19This test verifies HRPD forward link file transfer when in active HRPD mode. This test case may 20be performed using Simple IP and/or Mobile IP. 2118.1.32 Traceability: 22(see [24])

i. j. k. l. m. n. o. p.

Initiate a Telnet session to a remote host. Record the IP address assigned to the AT. Wait for the PCF PPP inactivity timer to expire. Verify the AT connection goes to idle state. Setup an HRPD AN originated connection by issuing a ping command from a remote host to the AT using the IP address assigned to the AT. Verify the host receives a ping response from the AT. Wait for the PCF PPP inactivity timer to expire. Verify the AT connection goes to idle state. Setup an HRPD AT originated connection by issuing a ping command from the AT to a remote host. Verify the AT receives a ping response from the remote host.

237 Session Layer, 8 Connection Layer, 10 MAC Layer 24(see [26]) 253 HRPD IOS Call Flows 2618.1.33 Call Flow Example(s)
27None 2818.1.34 Method of Measurement 29 30 31 32 33 34 35 36 37 38

a. b. c. d. e. f. g.

Connect the AT to the AN as shown in Figure A-3. At the remote host prepare the appropriate file, corresponding to the rate that will be tested (Note: this will guarantee sufficient transfer time). Configure the AT to negotiate default FTCMAC (HRPD Rev 0 configuration). Setup an AT originated HRPD connection. Adjust the RF quality in such a way that the AT requests mostly the DRC value corresponding to the rate that will be tested. Setup an FTP session with a remote host and start a file transfer in the forward link by using a binary get command from the AT. Verify the data transfer completes successfully.

1
1 2 3 4 5

3GPP2 C.S0044-A v1.0 h. i. j. Verify that for the duration of the test the PER for the packets received at the AT is less than 1.25%. After the file transfer is completed successfully, end the FTP session. This test case may be repeated for supported DRC values below.

6
DRC Value

Table 18.7.4-45 DRC Value Specification Rate (kbps) Packet Length (Slots) 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9 0xa 0xb 0xc 0xd 0xe 0xf Null rate 38.4 76.8 153.6 307.2 307.2 614.4 614.4 921.6 1228.8 1228.8 1843.2 2457.6 1536.0 3072 Invalid N/A 16 8 4 2 4 1 2 2 1 2 1 1 2 1 N/A

7 8 9 10 11 12 13

k. l.

End the session. If HRPD Rev A is supported, then configure the AT to negotiate the use of physical layer subtype 2 and Enhanced FTCMAC (HRPD Rev A configuration). Otherwise skip the remaining steps. Instruct the AT to set-up a new session with the AN. Repeat steps d through j.

m. n.

13GPP2 C.S0044-A v1.0

118.1.35 Minimum Standard 2The AN and AT shall comply with step g. 3 The AN and AT should comply with step h. 4Reverse File Transfer 518.1.36 Definition 6This test verifies HRPD reverse link file transfer when in active HRPD mode. This test case may 7be performed using Simple IP or Mobile IP. 818.1.37 Traceability: 9(see [24])

107 Session Layer, 8 Connection Layer, 10 MAC Layer 11(see [26]) 123 HRPD IOS Call Flows 1318.1.38 Call Flow Example(s)
14None 1518.1.39 Method of Measurement 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

a. b. c. d. e. f. g. h. i.

Connect the AT to the AN as shown in Figure A-3. Configure the AT to negotiate the use of Subtype 0 RTCMAC (HRPD Rev 0 configuration). Cause the AT to acquire the AN. Setup an HRPD AT originated connection. Setup a FTP session with a remote host and start a file transfer in the reverse link by using a binary put command from the AT. Verify the file transfer completes. Verify that for the duration of the test the PER for the packets received at the AN is less than 1.25%. After the file transfer is completed, end the FTP session. Instruct the AN to close the session with the AT. If HRPD Rev A is supported, then configure the AT to negotiate the use of physical layer subtype 2 and Subtype 3 RTC MAC (HRPD Rev A configuration). Otherwise skip the remaining steps. Instruct the AT to set-up a new session with the AN. Repeat steps c to g.

j. k.

3218.1.40 Minimum Standard 33The AN and the AT shall comply with step e.

34The AN and the AT should comply with step f.

1
1Bidirectional File Transfer 218.1.41 Definition 3This test verifies bi-directional file transfer when in active HRPD mode. 418.1.42 Traceability: 5(see [24])

3GPP2 C.S0044-A v1.0

67 Session, 8 Connection Layer, 10 MAC Layer 7(see [26]) 83 HRPD IOS Call Flows 918.1.43 Call Flow Example(s)
10None 1118.1.44 Method of Measurement 12 13 14 15 16 17 18 19 20 21

a. b. c. d. e. f. g.

Connect the AT to the AN as shown in Figure A-3. Cause the AT to acquire the AN. Setup an HRPD AT originated connection. At the remote host prepare the appropriate file, corresponding to the rate that will be tested (Note: this will guarantee sufficient transfer time). Setup a FTP session (1) with a remote host and start a file transfer in the reverse link by using a binary put command from the AT. Setup another FTP session (2) and transfer a file from the Remote Host to the AT using the binary get command while the transfer in the reverse direction is still proceeding. Verify both file transfers complete. After the file transfer, end both FTP sessions.

2218.1.45 Minimum Standard 23The AT shall comply with step f. 2418.2 RLP Operation in Severely Degraded Channel 2518.2.1 Definition 26This test verifies RLP Operation in Severely Degraded Channel when in active HRPD mode. 2718.2.2 Traceability: 28(see [24])

297 Session, 8 Connection Layer, 10 MAC Layer 30(see [26]) 313 HRPD IOS Call Flows
32See [12]

33Chapters 2 and 3 3418.2.3 Call Flow Example(s)

35None

13GPP2 C.S0044-A v1.0

118.2.4 Method of Measurement 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

a.

Connect the AT to the AN as shown in [Figure A-1]. At the remote host prepare the appropriate file, corresponding to the rate that will be tested (Note: this will guarantee sufficient transfer time). Refer to files in Data Services Annex D. Set the channel simulator to one Ray 100 km/hr Rayleigh fading on the forward link. Configure the AT to negotiate the use of Default Packet Application (HRPD Rev 0 configuration) bound to the Service Network. Cause the AT to acquire the AN. Setup an AT originated HRPD call. Setup a FTP session with a remote host and start a file transfer in the forward link by using a binary get command from the AT. Verify the AT sends a valid DRC value in the Data Rate Control Channel to the AN and that the AN provides the AT with requested forward link coding and modulating parameters. Ensure data transfer rate is not limited by network limitations. Verify the data transfer is successful. After the file transfer is completed, end the FTP session. Instruct the AN to close the session with the AT. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application (HRPD Rev A configuration) or Multi-Link Multi-Flow Packet Application bound to the Service Network. Repeat steps d to i.

b. c. d. e. f.

g. h. i. j. k.

l.

2218.2.5 Minimum Standard 23The AT shall comply with steps f and h. 24Softer and Soft Handoff Active HRPD Mode 2518.2.6 Definition 26This test verifies soft handoff when AT is in active HRPD mode with file transfer in forward and 27reverse directions. 2818.2.7 Traceability:

29(see [24]) 307 Session, 318 Connection Layer; 328.7.7.2.2 3310 MAC Layer 34(see [26]) 353 HRPD IOS Call Flows 3618.2.8 Call Flow Example(s) 37None
SetManagementSameChannelParameters Attribute

1
118.2.9 Method of Measurement 2 3

3GPP2 C.S0044-A v1.0

a.

Connect the AT to the AN as shown in Figure A-5 and set the forward link parameters as shown in. Configure all three sectors with the same channel. Table 18.11.4-46 Forward Link Parameters for Soft(er) Handoff Tests Parameter Units AN BTS 1 Sector -70 AN BTS 1 Sector -85 AN BTS 2 Sector -85

Forward Link Power Ior

5 6

dBm/1.23MHz

b. c. d.

Configure each sector to send the Sector Parameters Message with Neighbor List including the other sectors Pilot PNs. Setup an HRPD AT originated connection on BTS 1, sector . Setup an FTP session with a remote host and start a file transfer in the forward link by using a binary get command from the AT. Ensure the file size is appropriate to complete the test case before transfer is over. Verify that BTS 1/sector is in the pilot active set and that BTS 1/sector and BTS 2/sector are in the pilot neighbor set. Raise the level of BTS 1/sector in steps of 1 dB with a dwell time of 5 seconds after each step until the BTS 1/sector is in the pilot candidate set. Verify AT sends a RouteUpdate Message to report pilots. Verify the AN send s a TrafficChannelAssignment Message with Num Pilots=2 then verify both BTS 1 sector and sector are in the pilot active set. Verify that SofterHandoff bit in the TrafficChannelAssignment message is set to 1 for the pilots in the softer handoff. Raise the level of BTS 2/sector in steps of 1 dB with a dwell time of 5 seconds after each step until the BTS 2/sector is in the pilot candidate set. Verify AT sends a RouteUpdate Message to report pilots. Verify the AN send s a Traffic Channel Assignment Message with Num Pilots=3 then verify BTS 1/sectors and and BTS 2/sector are in the pilot active set. Verify that Soft Handoff bit in the TrafficChannelAssignment message is set to 1 for the pilots in the soft handoff. Decrease the level of BTS 1/sector in steps of 1 dB with a dwell time of 5 seconds after each step until AN sends a Traffic Channel Assignment Message with Num Pilots=2, then verify the BTS 1/sector is in the pilot neighbor set. Decrease the level of BTS 1/sector in steps of 1 dB with a dwell time of 5 seconds after each step until AN sends a Traffic Channel Assignment Message with Num Pilots=1, then verify the BTS 1/sector is in the pilot neighbor set. Verify file transfer is still on and the call in on BTS 2/sector . Verify the file transfer completes. End the call. Repeat steps a through c. Setup an FTP session with a remote host and start a file transfer in the reverse link by using a binary put command from the AT. Ensure the file size is appropriate to complete the test case before transfer is over.

7
8 9 10

11 12
13 14 15 16 18 19

e. f. g. h.

17 20 21

i. j. k.

22

24 27 29

23 25 26

l.

28 30 31 32 34 35 36 37 38 39

m.

33

n. o. p. q.

10

13GPP2 C.S0044-A v1.0

1

r.

Repeat steps e through p.

218.2.10 Minimum Standard 3The AT shall comply with steps g, j, l, m and n 4The AN shall comply with steps e, h, k, l, m and n. 5HRPD Control Channel Monitoring and Overhead Message Updates 618.2.11 Definition 7This test will verify that the AT can successfully receive and update control channel messages. 8And the AN can set various periodicities (within the allowed range, as defined in [24]) for these 9messages.

1018.2.12 Traceability
11(see [24]) 128.4 138.5

Default Idle State Protocol Enhanced Idle State Protocol

1418.2.13 Call Flow Example(s)

15None 1618.2.14 Method of measurement 17 18 19 20 21 22 23 24 25 26

a. b. c. d. e. f.

Power up the AT. Configure the AT to operate in non-slotted (sleep disabled) mode Monitor the periodicity of Sync message, Quickconfig message, SectorParameter message, and AccessParameter message Check the AN configuration for periodicity of these messages. Verify that received messages have same periodicity as configured at the AN Configure the AT to operate in slotted (sleep enabled) mode Verify that AT receives and updates the overhead messages (QuickConfig and SectorParameter messages) and performs the supervision of these messages according to the procedures in overhead message protocol specified in [24].

2718.2.15 Minimum Standard 28The AT shall comply with steps d and f. 29Control Channel Rate 3018.2.16 Definition 31This test verifies correct monitoring of Control Channel by AT. 3218.2.17 Traceability: 33(see [24])

3410.2 3510.2.6.1.4.1.1 3610.2 2

Default Control Channel MAC Protocol General Requirements Enhanced Control Channel MAC Protocol

11

1 112.3 and 13.3

AN Requirements Forward Channel Structure Forward MAC Channel Control Channel

3GPP2 C.S0044-A v1.0

212.3.1.3.1 and 13.3.1.3.1 312.3.1.3.2.2 and 13.3.1.3.2.2 412.3.1.3.2.4 and 13.3.1.3.2.4 518.2.18 Call Flow Example(s)
6None

718.2.19 Method of Measurement 8 9 10 11 12 13 14 15

a. b. c. d. e. f.

Configure Control Channel Rate to 38400 bps on AN. Connect the AT to the AN as shown in Figure A-3 Verify AT is able to monitor SyncChannel Message, QuickConfig Message, Sector Parameters Message and AccessParameters Message. Instruct AT to request a UATI from AN and Setup an HRPD AT originated call. Issue a ping from AT. Release the call. Configure Control Channel Rate to 76800 bps on AN and repeat steps b through e.

1618.2.20 Minimum Standard 17The AT shall comply with step c. 18HRPD ConnectionDeny 1918.2.21 Definition 20This test verifies that if there is no traffic channel available, the AN will send a ConnectionDeny 21Message to AT. This test also verifies that upon receiving a ConnectionDeny Message the AT will 22enter idle state until it attempts to make another call. 2318.2.22 Traceability: 24(see [24])

258.4 268.4.6.1.6.1 278.4.6.1.6.2 288.4.6.2.3 298.5

Default Idle State Protocol AT Requirements AN Requirements ConnectionDeny Enhanced Idle State Protocol

3018.2.23 Call Flow Example(s)

31None 3218.2.24 Method of Measurement 33 34 35

a. b.

Configure the AN to respond with a ConnectionDeny with reason Network Busy to a ConnectionAttempt message. Attempt to setup an AT originated HRPD connection.

12

13GPP2 C.S0044-A v1.0

1 2

c. d.

Verify the AN sends a Connection Deny Message with Deny Reason 1 = Network Busy. Verify the AT enters the AT Monitor (Idle) State until it attempts to setup a new call

318.2.25 Minimum Standard 4The AT shall comply with step d. 5The AN shall comply with step c. 6HRPD Keep Alive Mechanism 718.2.26 Definition 8This test verifies the proper functionality of keep alive mechanism. The AT and the AN shall 9monitor the traffic flowing on the Forward Channel and Reverse Channel, respectively, directed to 10or from the AT. If either the AT or the AN detects a period of inactivity of at least 11TSMPClose/NSMPKeepAlive minutes, it may send a KeepAliveRequest message. The recipient of the 12message shall respond by sending the KeepAliveResponse message. When a 13KeepAliveResponse message is received, the AT shall not send another KeepAliveRequest 14message for at least TSMPClose/NSMPKeepAlive minutes.

1518.2.27 Traceability
16(see [24]) 177.2.6.1.6.1 Keep Alive Functions 18Table 7.2.711and Table 7.2.8

1918.2.28 Call Flow Example(s)

20None 2118.2.29 Method of measurement 22 23 24 25 26 27 28 29 30 31 32 33

a. b. c. d.

Power up the AT and place it where it can receive good HRPD signal. Configure the AN to negotiate TSMPClose to 0x0005 with the AT. Ensure that the AT acquires the AN and goes to idle state. Terminate all data activities to and from the AT for a period greater than TSMPClose / NSMPKeepAlive minutes. Verify that after an inactivity period of TSMPClose / NSMPKeepAlive minutes if either the AT or the AN sends a KeepAliveRequest and that the recipient of the KeepAliveRequest message responds with a KeepAliveResponse message. If the AT receives a KeepAliveResponse message, verify that the AT does not send another KeepAliveRequest message for at least another TSMPClose / NSMPKeepAlive minutes Power down the AT. Power up the AT after TSMPClose minutes. Verify that the AT terminates the old session.

e. f.

3418.2.30 Minimum Standard 35The AT shall comply with steps d, e and f. 36The AN shall comply with step d.

13

1
1Intra-band HRPD-HRPD System Re-Selection (Connected State) 218.2.31 Definition

3GPP2 C.S0044-A v1.0

3This test verifies the AT performs HRPD system reselection between different channels in the 4same band class. For this test case, the HRPD session and PPP session are connected and 5active. The test will be performed while transferring data on the forward link and then repeated on 6the reverse link. 718.2.32 Traceability: 8(see [24])

98.2 108.2.6.1.2 118.4 128.4.6.1.6 138.6 148.5 15(see [26]) 163.7.1

Default Air Link Management Protocol Initialization State Default Idle State Protocol Connection Setup State Default Connected State Protocol Enhanced Idle State Protocol

PCF-PCF Dormant Handoff with Successful Retrieval of HRPD Session Information

1718.2.33 Call Flow Example(s)

18None 1918.2.34 Method of Measurement 20 21 22 23 24 25 26 27 28 29 30 31 32

a. b. c. d. e. f. g. h. i.

Connect the AT to AN 1 and AN 2 as shown in Figure A-5. Configure AN 1 with different channel than AN 2. Configure AN 2 not to be in the neighbor list of AN 1. Cause the AT to acquire AN 1. Setup an HRPD AT originated connection. Setup a FTP session with a remote host and start a file transfer in the forward link by using a binary get command from the AT. Before file transfer is complete increase forward link attenuation on AN 1 until AT cant monitor AN 1 signal. Verify AT declares system lost and acquires AN 2 and reconnects HRPD connection. Verify file transfer continues after selection AN 2. Release connection. Repeat steps b through g for file transfer in the reverse link by using a binary put command from the AT instead of get (step e).

3318.2.35 Minimum Standard 34The AT shall comply with step g for all test cases.

14

13GPP2 C.S0044-A v1.0

1Inter-band HRPD-HRPD System Re-Selection (Connected State) 218.2.36 Definition 3This test verifies the AT performs HRPD system reselection between channels from different 4band classes. For this test case, the HRPD session and PPP session are connected and active. 5The test will be performed while transferring data on the forward link and then repeated on the 6reverse link. 718.2.37 Traceability: 8(see [24])

98.2 108.2.6.1.2 118.4 128.4.6.1.6 138.6 148.5 15(see [26]) 163.7.1

Default Air Link Management Protocol Initialization State Default Idle State Protocol Connection Setup State Default Connected State Protocol Enhanced Idle State Protocol

PCF-PCF Dormant Handoff with Successful Retrieval of HRPD Session Information

1718.2.38 Call Flow Example(s)

18None 1918.2.39 Method of Measurement 20 21 22 23 24 25 26 27 28 29 30 31

a. b. c. d. e. f. g. h.

Connect the AT to AN 1 and AN 2 as shown in Figure A-5. Configure AN 1 to operate in a different band class than AN 2. Cause the AT to acquire AN 1. Setup an HRPD AT originated connection. Setup a FTP session with a remote host and start a file transfer in the forward link by using a binary get command from the AT. Before file transfer is complete increase forward link attenuation on AN 1 until AT cant monitor AN 1 signal. Verify AT declares system lost and acquires AN 2 and reconnects HRPD call. Verify file transfer continues after selection AN 2. Release connection. Repeat steps b through g for file transfer in the reverse link by using a binary put command from the AT instead of get (step e).

3218.2.40 Minimum Standard 33The AT shall comply with step f for all test cases. 34Intra-band HRPD-HRPD System Re-selection (Idle State) 3518.2.41 Definition 36This test verifies the AT performs HRPD reselection, while in idle state, between channels in the 37same band class. This test is performed after the HRPD and PPP session have been established.

15

3GPP2 C.S0044-A v1.0

1The PPP session for the AT shall be in the dormant state and the AT is not on the traffic channel 2at the time of the system reselection. 318.2.42 Traceability

4(see [24]) 58.2 68.2.6.1.2 78.4 88.4.6.1.6 98.6 108.5 11(see [26]) 123.7.1
PCF-PCF Dormant Handoff with Successful Retrieval of HRPD Session Information Default Air Link Management Protocol Initialization State Default Idle State Protocol Connection Setup State Default Connected State Protocol Enhanced Idle State Protocol

1318.2.43 Call Flow Example(s)

14None 1518.2.44 Method of Measurement 16 17 18 19 20 21 22 23 24 25

a. b. c. d. e. f. g. h.

Connect the AT to AN 1 and AN 2 as shown in Figure A-5. Configure AN 1 with different channel than AN 2. Configure AN 2 not to be in the neighbor list of AN 1. Cause the AT to acquire AN 1. Setup an HRPD AT originated call. Verify that the AT connection is idle. Force the AT to handoff from AN 1 to AN 2 (i.e. by increasing forward link attenuation on AN 1 until AT cant monitor AN 1 RF signal). Verify AT declares system lost and acquires AN 2. Issue a ping from AT and verify an HRPD connection is successfully setup. Issue a ping from remote host to AT IP address and verify there is a response.

2618.2.45 Minimum Standard 27The AT shall comply with steps e, g and h. 28Inter-band HRPD-HRPD System Re-selection (Idle State) 2918.2.46 Definition 30This test verifies the AT, performs HRPD reselection, while in idle state, between channels from 31different band classes. The test may be performed using Simple IP and/or Mobile IP. This test is 32performed after the HRPD and PPP session have been established. The PPP session for the AT 33shall be in the dormant state and the AT is not on the traffic channel at the time of the system 34reselection. 3518.2.47 Traceability

36(see [24])

16

13GPP2 C.S0044-A v1.0 18.2 28.2.6.1.2 38.4 48.4.6.1.6 58.6 68.5 7(see [26]) 83.7.1
PCF-PCF Dormant Handoff with Successful Retrieval of HRPD Session Information Default Air Link Management Protocol Initialization State Default Idle State Protocol Connection Setup State Default Connected State Protocol Enhanced Idle State Protocol

918.2.48 Call Flow Example(s)

10None 1118.2.49 Method of Measurement 12 13 14 15 16 17 18 19 20

a. b. c. d. e. f. g.

Connect the AT to AN 1 and AN 2 as shown in Figure A-5. Configure AN 1 to operate in a different band class than AN 2. Cause the AT to acquire AN 1. Verify that AT connection is idle. Force the AT to handoff from AN 1 to AN 2 (i.e. by increasing forward link attenuation on AN HRPD 1 until AT cant monitor HRPD 1 RF signal). Verify AT declares system lost and acquires AN 2. Issue a ping from AT and verify HRPD call is successfully originated. Issue a ping from remote host to AT IP address and verify there is a response.

2118.2.50 Minimum Standard 22The AT shall comply with steps d, f and g. 23HRPD Terminal Authentication

2418.2.51 Definition
25This test verifies that when the User-name or the CHAP-password is incorrectly set at the AT the 26network authentication fails.

2718.2.52 Traceability: 28(see [11]) 293.1.1 303.1.2

AT originates HRPD Session Successful Terminal Authentication AT originates HRPD Session Unsuccessful Terminal Authentication

3118.2.53 Call Flow Example(s)

32None

17

1 118.2.54 Method of measurement

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28

3GPP2 C.S0044-A v1.0

a. b. c. d. e. f. g.

Configure the CHAP authentication to be enabled in the network. Provision the AT with the correct information to successfully pass CHAP authentication. Ensure the AT has a closed HRPD session. Power up the AT and allow it to acquire the HRPD network. If AN performs authentication immediately after the session negotiation, verify that AN sends the CHAP Challenge message and initiates the network authentication Verify that the network authentication passes and the HRPD remains connected. If AN performs authentication just before the data call setup(s), set up a data call on the HRPD system and verify that AN sends the CHAP Challenge message and initiates the AN authentication Verify that the network authentication passes and the HRPD call is successful. End any HRPD calls. Provision an incorrect User-name but a correct Chap-password in the AT for CHAP authentication. Ensure that the AT has a closed HRPD session Power up the AT and place it where it can receive good HRPD signal Ensure that AT successfully completes the session negotiation and negotiates the AN stream as part of this procedure. If AN performs authentication immediately after the session negotiation, verify that AN sends the CHAP Challenge message and initiates the network authentication Verify that the network authentication fails and the AN closes the HRPD session. If AN performs authentication just before the data call setup(s), set up a data call on the HRPD system and verify that AN sends the CHAP Challenge message and initiates the AN authentication Verify that the network authentication fails. Repeat steps l to g by provisioning a correct User-name but an incorrect Chappassword in the AT for CHAP authentication.

h. i. j. k. l. m. n. o. p.

q. r.

2918.2.55 Minimum Standard 30The AT shall comply with steps f, h, and q. 31The AN shall comply with steps e, f, h, n, o, p and q. 32PPP Session in Adverse Conditions - Disconnect cable between AT and PC. 3318.2.56 Definition 34This test verifies AT sends an LCP Termination Request to the AN when it is disconnected from 35the computer device. This causes the PDSN to close the PPP session. 3618.2.57 Traceability: 37(see [28])

383.2.1

PPP Session

18

13GPP2 C.S0044-A v1.0

118.2.58 Call Flow Example(s) 2None 318.2.59 Method of Measurement 4 5 6 7 8 9 10

a. b. c. d. e.

Setup an AT originated HRPD connection. Ensure that an IP address is assigned to the AT, and a PPP session is established between PDSN and the AT. Wait until the AT connection goes to idle state. Close the PPP session from the AT to the AN without notifying the AN by disconnecting the cable between the AT and the computer. Verify that the AT transmits XOffRequest and ConnectionClose messages to the AN.

1118.2.60 Minimum Standard 12The AT shall comply with step e. 1318.3 Unicast ReverseRateLimit 1418.3.1 Definition 15This test verifies the AT can successfully receive the UnicastReverseRateLimit Message with the 16RateLimit value set to various values. This test is applicable to HRPD Rev 0 operation. Rev A AT 17should be configured to negotiate Rev 0 supported protocol subtypes and default packet 18application.

1918.3.2 Traceability
20(see [24]) 2110.8.6.1.5.2 and 10.9.6.1.5.2 Rate Control

2218.3.3 Call Flow Example(s)

23None 2418.3.4 Method of measurement 25 26 27 28 29 30 31 32 33

a. b. c. d. e.

Configure the AT to negotiate Subtype 0 RTCMAC. Setup a connection. Setup a FTP session with a remote host and start a file transfer in the reverse link by using a binary put command from the AT. Send a UnicastReverseRateLimit Message with the RateLimit value set to 1 (9.6 kbps) to the AT. Monitor the AT transmit rate and verify that the AT does not transmit above the value set in step c. Steps a to d may be repeated with the RateLimit values set to 2 (19.2kbps), 3 (38.4kbps), 4 (76.8kpbs), and 5 (153.6kbps).

3418.3.5 Minimum Standard 35The AT shall comply with step d for all test cases.

19

1
118.4 HRPD Location Update Protocol Tests 218.4.1 Definition 3This test verifies the proper functionality of Location update feature.

3GPP2 C.S0044-A v1.0

418.4.2 Traceability
5(see [24]) 63.5 and 4.6 Location Update Protocol 7(see [12]) 8Chapters 2 and 3.

918.4.3 Call Flow Example(s)

10None 1118.4.4 Method of measurement 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

a. b. c. d.

Ensure that the Ranhandoff parameter is enabled at the AN. Power up the AT and place it where it can receive good HRPD signal Ensure that AT successfully completes the session negotiation. Depending on the implementation, the AN can send LocationAssignment Message to the AT. Upon receiving this LocationAssignment Message, verify that the AT sends a LocationComplete Message and stores the Location Values in the Location Assignment Message as the current Location Values. Depending on the implementation, the AN can send LocationRequest Message. Upon receipt of this message, verify that the AT responds with LocationNotification Message, which shall contain the current Location values of the AT. Originate a packet connection, verify that the connection can be successfully established and the data can be transferred. Let the AT connection go idle. Move the AT to an area where there is no HRPD signal. AT will lose the HRPD signal and go to acquisition state. Move the AT to an area where there is a HRPD signal belonging to a different subnet. AT shall acquire this system. Ensure that the AN rejects the PriorSession restore request from the AT. AT shall negotiate session with this HRPD system and once the session is negotiated, shall send an unsolicited LocationNotification Message. Verify that this message is sent.

e.

f.

3018.4.5 Minimum Standard 31The AT shall comply with steps d, e, and f. 3218.5 Idle State Channel Hashing 3318.5.1 Definition 34This test can be performed only if the AN supports more than one HRPD channels. 35If multiple channels are advertised in the sector parameter message, AT uses hash function (as 36specified in (See [24])) to select one of the advertised channels for idle state operation. The 37primary purpose of channel hashing is to equally distribute the AN load on all available channels.

3818.5.2 Traceability
39(see [24])

20

13GPP2 C.S0044-A v1.0 18.4.6.1.5.1.1 210.4

CDMA Channel Selection Hash Function

318.5.3 Call Flow Example(s)

4None 518.5.4 Method of measurement 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

a. b. c. d. e. f.

Configure the AT roaming list with the primary channel. Configure the AT to negotiate default idle state protocol. Power up the AT. Place AT where it can receive good HRPD signal. If the AT has an open session with the AN, cause the AN to close the session. Cause the AT to establish a new session with the AN. Ensure that AT correctly acquires the primary channel listed in the roaming list. After receiving the sector parameter messages with multiple channels, AT will try to hash to a channel listed in SectorParameter message (it could be the same channel in some cases). Verify that if there are n channels listed in the sector parameter message and if this test is repeated m number of times, AT will hash to each channel approximately m/n times. In a subnet where SectorParameter message contains multiple channels, AT will try to hash to a new channel every time a new session is opened. Repeat steps d through g approximately 3n times. Setup a HRPD data connection after channel hashing is complete to verify that AT can setup a connection on the hashed channel. Let the call connection go idle. Send a data page from the AN (on the hashed channel) and verify that AT can receive a page on the hashed channel.

g.

h. i. j.

2518.5.5 Minimum Standard 26The AT shall comply with steps g, i and j. 2718.6 Inter-frequency Active Handoff 2818.6.1 Definition 29This test verifies that the AT is able to successfully acquire a new AN with a different frequency 30assignment during an active call. The AT will receive a new TrafficChannelAssignment message 31with the target frequency information. Since there is no hard handoff mechanism in HRPD, using 32the new TrafficChannelAssignment allows for faster acquisition of AN 2.

3318.6.2 Traceability
34(see [24])

358.2 368.2.6.1.2 378.4 388.4.6.1.6

Default Air Link Management Protocol Initialization State Default Idle State Protocol Connection Setup State

21

1 18.6 28.5
Default Connected State Protocol Enhanced Idle State Protocol

3GPP2 C.S0044-A v1.0

318.6.3 Call Flow Example(s)

AT
a b c d e f
Route Update* Route Update

Sector s25

Sector Sector s16

Reset Report*

Traffic Channel Assignment corresponding to configured target carrier sectors

Reverse Pilot + DRC

Traffic Channel Complete

4
5

*This step is conditional , this may or , may not take place in the message exchange sequence, based on the trigggers generated by mobility

618.6.4 Method of measurement 7 8 9 10 11 12 13 14 15 16

a. b. c. d. e. f. g. h.

Connect the AT to AN 1 and AN 2 as shown in Figure A-5. AN 1 and AN 2 have different frequency assignments. AN 1 and AN 2 have the same RNC connections. Cause the AT to acquire AN 1. Set up an HRPD AT originated call. Initiate a forward data transfer to the AT. Trigger a hard handoff from AN 1 to AN 2 by sending a TrafficChannelAssignment message with the target information for AN 2. Verify the AT tunes to the new frequency the file transfer completes successfully. The delay between losing AN 1 and acquiring AN 2 should be less than 500ms.

22

13GPP2 C.S0044-A v1.0

118.6.5 Minimum Standard 2The AT shall comply with step g and should comply with step h. 318.7 Typical HRPD Rev-A Session Configuration 418.7.1 Definition

5This test verifies the ability of AT and AN to use typical HRPD Rev A configuration. 6The use of MFPA bound to the service network, Enhanced FTCMAC, RTCMAC subtype 73, Enhanced CCMAC, Enhanced ACMAC and Physical layer Subtype 2 is verified.

818.7.2 Traceability
9(see [24])

104 117.2.6.2.1 128.5 1310.3 1410.5 1510.7 1610.11 17 11.2 18(see [12]) 19Chapters 2 and 3.

Multi-Flow Packet Application Session Close Enhanced Idle State Protocol Enhanced Control Channel MAC Protocol Enhanced Access Channel MAC Protocol Enhanced Forward Traffic Channel MAC Protocol Subtype 3 Reverse Traffic Channel MAC Protocol Subtype 2 Physical Layer

2018.7.3 Call Flow Example(s) 21None

2218.7.4 Method of measurement 23 24 25 26 27 28 29 30 31 32 33 34 35 36

a. b. c.

Connect the AT to the AN as shown in Figure A-3. Cause the AT to acquire the AN. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2, Enhanced CCMAC, Enhanced ACMAC, Enhanced FTCMAC, Enhanced Idle State Protocol and Subtype 3 RTC MAC. If the AT has an established session with the AN, cause the AN to close the session by transmitting a SessionClose message. Power cycle the AT. Verify that the AT establishes a session with the AN and acquires the HRPD system. Cause the AT to initiate a data call with the AN. Verify that the AT and the AN have successfully negotiated the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the AN, Physical layer Subtype 2, Enhanced FTCMAC

d. e. f. g. h.

23

1
1 2 3 4

3GPP2 C.S0044-A v1.0 Enhanced CCMAC, Enhanced ACMAC, Enhanced Idle State Protocol and Subtype 3 RTCMAC. i. j. Cause the AT to transmit data to the AN. Verify that the data is transmitted using the default RLP flow of the MFPA.

518.7.5 Minimum Standard

6The AT shall comply with steps f, h and j. 7The AN shall comply with step h.
818.8 Multiple Reservations bound to one RLP 918.8.1 Definition

10In HRPD Rev A, multiple higher layer flows can be bound to a single RLP flow. This is 11done by mapping the ReservationLabel associated with the higher layer flow in 12FlowNNReservationFwd and FlowNNReservationRev attribute of the RLP Flow NN. This 13test verifies the ability of the AN and the AT to successfully bind multiple reservations 14to a single RLP flow. 15This test requires the ability to generate QoS requests from the AT, allocate QoS 16resources at the AN and install traffic filtering at the PDSN. The application that 17causes the AT to generate QoS requests could either reside at the AT or the TE. 18Further, it should be ensured that the application is able to connect with the 19server/peer and receive and transmit data. This may require password authentication 20when using commercial applications residing on the AT.
21The following behavior is assumed for the application using the QoS. Starting the application will 22cause ReservationKKQoSRequestFwd/Rev to be sent containing the requested Profile ID. Unless 23otherwise specified, the Profile should be accepted by the AN. Closing the application will cause 24the AT to transmit a ReservationKKQoSRequestFwd/Rev with ProfileType set to NULL. If 25application is paused or restarted, it should turn the reservation to on state if the reservation is in 26closed state. This application behavior is assumed for all QoS related tests in this chapter.

2718.8.2 Traceability
28(see [24])

294.4.4 304.4.8
31(see 17]) 3211.4 33(see [10]) 34(see [12]) 35Chapters 2 and 3.

Procedures and Messages for the InUse Instance of the RLP Complex Attributes of Multi-Flow Packet Application QoS ProfileType and ProfileValue Assignment

3618.8.3 Call Flow Example(s)

37None 3818.8.4 Method of measurement 39 40

a. b.

Connect the AT to the AN as shown in Figure A-3. Cause the AT to acquire the AN.

24

13GPP2 C.S0044-A v1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46

c.

Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2, Enhanced FTCMAC and Subtype 3 RTC MAC. Configure the AN to activate only the default RLP flow during session configuration. Configure the AN to use a value of 2 for MaxActivatedRLPFlowsFwd and MaxActivatedRLPFlowRev. If the AT has an established session with the AN, cause the AN to close the session by transmitting a SessionClose message. Cause the AT to negotiate a new session with the AN. Cause the AT to establish a data call with the AN and allow the AT to go idle. Cause the AT to generate a QoS request for one forward and one reverse link higher layer flow. Ensure that the AT transmits GAUP message(s) with ReservationKKQoSRequestFwd with R_QoS_SUB_BLOB containing the specified Profile ID for forward higher layer flows and ReservationKKQoSRequestRev with R_QoS_SUB_BLOB containing the specified Profile ID for reverse higher layer flows. Ensure that the AT constructs a Traffic Flow Template (TFT) with the desired packet filters and sends an RSVP Resv [Create new TFT] message. Ensure that the AN transmits AttributeUpdateAccept message(s) accepting the QoS ReservationKKQoSRequestFwd / ReservationKKQoSRequestRev attributes from the AT. The AN should GAUP the ReservationKKQoSResponseFwd with G_QoS_BLOB containing the set ID for primary Profile ID. The AN should GAUP the ReservationKKQoSResponseRev with G_QoS_BLOB containing the set ID for primary Profile ID. The PDSN should install the desired packet filters and sends an RSVP ResvConf message. Ensure that the AT transmits AttributeUpdate message(s) to the AN accepting the ANs ReservationKKQosResponseFwd and ReservationKKQosResponseRev for the various Reservarion Labels. Ensure that the AN transmits a GAUP message for FlowNNIdentificationFwd (NN = 1) and FlowNNIdentificationRev (NN = 1) in order to activate the forward and reverse link flows. Ensure that the AT transmits AttributeUpdateAccept message(s) accepting FlowNNIdentificationFwd and FlowNNIdentificationRev arrtibutes. The AN may need to transmit AttributeUpdateRequest message(s) negotiating the FlowNNTimersFwd and FlowNNTimersRev for the Forward and Reverse link RLP flows and various parameters of the RTCMAC flow. If the AN transmits Attribute Update Request for the Forward and Reverse Link RLP Flows and/or RTCMAC flows, the AT should transmit AttributeUpdateAccept message(s) accepting RLP and RTCMAC parameters. Ensure that the AN transmits a FlowNNReservationFwd to bind the reservation to forward to RLP flow (NN = 0x01). Ensure that the AN transmits a FlowNNReservationRev to bind the reservation to reservation to RLP flow (NN = 0x01).

d. e. f. g. h. i. j.

k. l.

m. n. o. p.

q.

r. s.

t.

u. v.

25

1
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

3GPP2 C.S0044-A v1.0 w. x. Ensure that the AT transmits an AttributeUpdateAccept message accepting the FlowNNReservationFwd and FlowNNReservationRev values. Ensure that the AN transmits AttributeUpdateReqest message containing AssociatedFlowNN with substream field set to 1 to bind the RLP FlowNN (NN = 1) to an RTCMAC flow. Ensure that the AT transmits AttributeUpdateAccept message(s) to the AN accepting the binding sent by the AN in AssociatedFlowsNN attribute. Ensure that the AN transmits a GAUP message to set RTCMAC BucketLevelMaxNN with a nonzero value in order to activate the RTCMAC flow. Ensure that the AT transmits AttributeUpdateAccept message to the AN accepting the BucketLevelMaxNN value sent by the AN. Ensure that the AT sends ReservationOnRequest for both the forward and reverse ReservationLabels using single ReservationOnRequest message. Ensure that AN sends ReservationAccept for both forward and reverse reservations. Repeat steps i to cc for 2 other QoS requests. Verify that both the forward and reverse RLP flows (NN = 1) are activated and the reservation for all the higher layer flows are in the Open state. Start bidirectional data transfer for different higher layer flows and verify that data is being sent/received on the correct RLP IDs. Ensure that the PDSN is sending data via the intended filter.

y. z. aa. bb. cc. dd. ee. ff. gg.

2118.8.5 Minimum Standard

22The AT shall comply with steps ee and ff. 23The AN shall comply with steps ee and ff. 24The PDSN should comply with steps o.
2518.9 Maximum Open Reservations, Activated RLP and MAC flows 2618.9.1 Definition

27The Maximum number of reservations that can be in open state in HRPD is governed 28by MaxNumOpenReservationsFwd and MaxNumOpenReservationsRev (default value 29of 16). The maximum number of open RLP flows is governed by 30MaxActivatedRLPFlowsFwd and MaxActivatedRLPFlowsRev. The maximum number of 31active MAC flows is governed by 32MaxNumActiveMACFlows This test verifies that AT and the AN can support up to 16 33open reservations, mapped to 8 RLP flows that are in turn mapped to 4 MAC flows. 34This test implicitly verifies the ability of the AN and the AT to allow many to one 35binding from reservation labels to RLP flows and RLP flows to MAC Flows. It also 36verifies the ability of the PDSN to create multiple filters for the AT.

3718.9.2 Traceability
38(see [24])

394.4.4 404.4.8
41(see [10])

Procedures and Messages for the InUse Instance of the RLP Complex Attributes of Multi-Flow Packet Application

26

13GPP2 C.S0044-A v1.0

1(see [12]) 2Chapters 2 and 3

318.9.3 Call Flow Example(s)

4None 518.9.4 Method of measurement 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

a. b. c.

Connect the AT to the AN as shown in Figure A-3. Cause the AT to acquire the AN. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2, Enhanced FTCMAC and Subtype 3 RTC MAC. Configure the AN to activate only the default RLP flow during session configuration. Configure the AN to use a value of 8 for MaxActivatedRLPFlowsFwd, MaxActivatedRLPFlowRev, MaxNumRLPFlowsFwd and MaxNumRLPFlowsRev. Configure the AN to set the MaxNumOpenReservationsFwd and MaxNumOpenReservationsRev parameters of MaxReservations attribute to 16. Configure the AN to grant the QoS request from the AT and to bind 2 QoS reservations to one RLP flow for both the forward and reverse link flows, and to bind 2 RLP flows to each RTCMAC Flow. If the AT has an established session with the AN, cause the AN to close the session by transmitting a SessionClose message. Cause the AT to negotiate a new session with the AN. Ensure that the AN activates only the default RLP flow during session configuration. Cause the AT to establish a data call with the AN and allow the AT to go idle. Using multiple applications, cause the AT to generate QoS requests for 16 forward and reverse link flows. Wait for the AN to transmit ReservationAccept message for all the reservations. Verify that all 8 forward and reverse RLP flows are activated and all 16 reservations are in Open state. Start bidirectional data transfer for different higher layer flows and verify that data is being sent/received on the correct RLP and MAC flows. Ensure that the PDSN is sending data for each higher layer flow via the intended filter.

d. e. f. g.

h. i. j. k. l.

m. n. o.

3318.9.5 Minimum Standard

34The AT shall comply with steps m and n. 35The AN shall comply with steps m and n. 36The PDSN should comply with step o.

27

1
118.10 QoS Release upon PDSN initiated LCP termination 218.10.1 Definition

3GPP2 C.S0044-A v1.0

3When the PDSN terminates a PPP connection by transmitting an LCP termination 4message, the AT and the AN should release all the resources allocated to the current 5QoS Reservations. The PDSN should delete the TFT associated with the AT.

618.10.2 Traceability
7(see [24]) 8Chapter 4. Multi-Flow Packet Application 9(see [12]) 10Chapter 2 Enhanced Mult-Flow Packet Application 11Chapter 3 Multi-Link Multi-Flow Packet Application 12(see [10]) 13(see [28])

143.2.1 PPP Session 1518.10.3 Call Flow Example(s)

16None 1718.10.4 Method of measurement

a. b.

18Connect the AT to the AN as shown in Figure A-3. 19Cause the AT to acquire the AN. 20 21 22 23

c. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2, Enhanced FTCMAC and Subtype 3 RTC MAC. d. Configure the AN to grant the QoS request from the AT and to use a value of 0x00 for ReservationKKIdleStateFwd and ReservationKKIdleStateRev attributes. e. If the AT has an established session with the AN, cause the AN to close the session by transmitting a SessionClose message. f. Cause the AT to negotiate a new session with the AN. g. Cause the AT to establish a data call with the AN and allow the AT to go idle. h. Cause the AT to generate QoS requests for one forward and reverse link flow with ReservationKKIdleStateFwd and ReservationKKIdleStateRev set to 0x00. Wait for the AN to transmit ReservationAccept message for all the reservations. i. Start data transfer and ensure that all reservations are in open state and that the data is being transmitted using appropriate RLP flow IDs. j. Cause the PDSN to transmit an LCP termination to the AT. k. Verify that the AT terminated the PPP.

24 25 26
27 28 29 30 31

32 33 34 35
36 37 38 39

28

13GPP2 C.S0044-A v1.0

1 2 3 4
5

l. Ensure that the AN and AT release all QoS resources by verifying that the AT transmits ReservationKKQoSRequest(s) with ProfileType set to NULL and ReservationOffRequest message(s) for all the open reservation(s) and that the AN responds with a ReservationAccept message(s). m. The PDSN should delete all filters associated with the AT.

618.10.5 Minimum Standard

7The AT shall comply with step k and l. 8The AN shall comply with steps l. 9The PDSN should comply with step m.
1018.11 QoS Release upon AT Initiated PPP Termination 1118.11.1 Definition

12When the AT terminates the PPP session, the AT and the AN should release all QoS 13and the PDSN should delete TFT related to the AT.

1418.11.2 Traceability
15(see [24]) 16Chapter 4. 17(see [10]) 18(see [12]) 19Chapters 2 and 3

2018.11.3 Call Flow Example(s)

21None 2218.11.4 Method of measurement 23 24 25 26 27 28

a. b. c.

Connect the AT to the AN as shown in Figure A-3. Cause the AT to acquire the AN. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2, Enhanced FTCMAC and Subtype 3 RTC MAC. Configure the AN to grant the QoS request from the AT and to use a value of 0x00 for ReservationKKIdleStateFwd and ReservationKKIdleStateRev attributes. If the AT has an established session with the AN, cause the AN to close the session by transmitting a SessionClose message. Cause the AT to negotiate a new session with the AN. Cause the AT to establish a data call with the AN and allow the AT to go idle. Cause the AT to generate Qos requests for one forward and reverse link flow. Wait for the AN to transmit ReservationAccept message for all the reservations. Start data transfer and verify that all reservations are in open state and that the data is being transmitted using appropriate RLP flow IDs. Cause the AT to terminate the PPP session.

29 30
31 32 33 34 35 36 37 38 39

d. e. f. g. h. i. j.

29

1
1 2 3 4

3GPP2 C.S0044-A v1.0 k. Ensure that the AN and AT release all QoS resources by verifying that the AT transmits ReservationKKQoSRequest(s) with ProfileType set to NULL and ReservationOffRequest message(s) for all the open reservation(s) and that the AN responds with a ReservationAccept message(s). The PDSN should delete all filters associated with the AT.

l.

618.11.5 Minimum Standard

7The AT shall comply with step k. 8The AN shall comply with steps k. 9The PDSN should comply with step l.
1018.12 Access Persistence Vector 1118.12.1 Definition 12This test verifies that the AT can properly interpret the persistence value from the 13AccessParameters Message. The AN may control the load on the system by adjusting the 14access persistence vector, APersistence, sent as part of the AccessParameters message. The 15value of APersistence can be in the range from zero to 0x3F. If the value of APersistence is 160x3F, the AT shall use zero as the corresponding persistence probability. If the value of 17APersistence(n) is not equal to 0x3F, the AT shall use the value obtained from 2-n/4 as the 18corresponding persistence probability. There are 4 instances of APersistence, called NACMPAPersist, 19that represent 4 AT types. The 4 instances of NACMPAPersist are: 200: Normal AT 211: Priority or Emergency AT 222: Test AT 233: Reserved.

2418.12.2 Traceability
25(see [24])

2610.4.6.1.4.1.4
2710.5.7

Probe Sequence Transmission Configuration Attributes

2818.12.3 Call Flow Example(s)

29None 3018.12.4 Method of measurement

31
32 33 34 35 36 37 38 39

a. b.

Connect the AT to the AN as shown in Figure A-3. If the AT and AN support the Enhanced Access Channel MAC Protocol, ensure that the default values are used for the parameters of APersistenceOverride and AccessTerminalClassOverride. Cause the AN to send an AccessParameters Message with the value of APersistence equal to 0 for every instance of NACMPAPersist. Attempt an AT originated HRPD connection. Verify that the AT successfully established the HRPD connection. End the connection.

c. d. e. f.

30

13GPP2 C.S0044-A v1.0

1 2 3 4 5 6 7 8 9 10

g. h. i. j. k. l. m.

Cause the AN to send an AccessParameters Message with the value of APersistence equal to 0x3F for every instance of NACMPAPersist. Cause the AT to send a message on the Access Channel. Verify the attempt is not successful and that the AT returns a TransmissionFailed indication. Cause the AN to send an AccessParameters Message with the value of APersistence equal to 0 for every instance of NACMPAPersist. Attempt an AT originated HRPD connection. Verify that the AT successfully established the HRPD connection. End the connection.

1118.12.5 Minimum Standard 12The AT shall comply with step e, i and l. 1318.13 AT Data Over Signaling Message Transmission 1418.13.1 Definition

15This test verifies that the AT can send a packet over the Access Channel to the AN. 16This is accomplished by using the Data Over Signaling (DoS) Protocol. The size of the 17data packet that the AT sends must be smaller than the Access Channel capsule size. 18Specifically, this test validates that the delivery of higher layer packet using a 19DataOverSignaling Message transmitted by the AT to the AN, and the 20MessageSequence increment for the DataOverSignaling Messages. This test also 21validates the ability of the AN to acknowledge the DataOverSignaling Message with a 22DataOverSignalingAck with appropriate AckSequence field when the AckRequired 23field in the DataOverSignaling Message is set to 1.

2418.13.2 Traceability
25(see [24]) 264.5

Data Over Signaling Protocol

27(see [12])

28

Chapters 2 and 3

2918.13.3 Call Flow Example(s)

30None 3118.13.4 Method of measurement 32 33 34 35 36 37 38 39 40

a. b. c.

Connect the AT to the AN as shown in Figure A-3. Cause the AT to acquire the AN. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2, Enhanced CCMAC, Enhanced ACMAC, Subtype 3 RTC MAC. During Session Configuration, set the ProtocolIdentifier field of the FlowNNHigherLayerProtocolRev (NN = 0xij) and FlowNNHigherLayerProtocolFwd (NN = 0xij) to HDLC framing.

d.

31

1
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

3GPP2 C.S0044-A v1.0 e. f. During Session Configuration, set the Active parameter of FlowNNIdentificationFwd (NN = 0xij) attribute and FlowNNIdentificationRev (NN = 0xij attribute to 0x01. Set the ReservationLabel for FlowNNReservationRev (NN = 0xij and FlowNNReservationFwd (NN = 0xij) to High Priority Signaling. Set FlowNNDataOverSignalingAllowedRev (NN = 0xij) to 0x01. Configure the AN to grant the QoS request from the AT and to set ReservationKKIdleStateFwd and ReservationKKIdleStateRev to 0x0 for ReservationLabel kk associated with High Priority Signaling. If the AT does not have an established PPP session, cause the AT to establish a PPP session. Instruct the AT to send a ReservationOn message for ReservationLabel kk associated with High Priority Signaling data that is to be carried using DataOverSignaling message to the AN and ensure that the AN responds with a ReservationAccept message. Instruct the AT to send a ReservationOn message for ReservationLabel kk associated with High Priority Signaling data that is to be carried using DataOverSignaling message from the AN to the AT and ensure that the AN responds with a ReservationAccept message. Allow the HRPD connection to become idle. Transmit a packet from the AT directed to the AN using the DataOverSignaling message and setting the AckRequired field of the DataOverSignaling message to 1. Ensure that the DataOverSignaling message is smaller than the maximum Access Channel capsule size. Verify that the AT transmits a DataOverSignaling Message with MessageID field set to 0x14, AckRequired field set to 1, Reset field set to 0, MessageSequence field set to 0, and the HigherLayerPacket field set to entire higher layer packet. Verify that if the AN received the DataOverSignaling Message, it transmits a DataOverSignalingAck with MessageID set to 0x15 and AckSequence field set to zero and the higher layer packet carried in the DataOverSignaling message is delivered to the higher layer protocol. Transmit a packet from the AT directed to the AN using the DataOverSignaling message and setting the AckRequired field of the DataOverSignaling message to 1. Ensure that the DataOverSignaling message size is smaller than the maximum Access Channel capsule size. Verify that the AT transmits a DataOverSignaling Message with MessageSequence field set to 1. Verify that if the AN received the DataOverSignaling Message, it transmits a DataOverSignalingAck with the AckSequence field set to one and the packet is delivered to the higher layer protocol.

g. h.

i. j.

k.

l.

m.

n. o.

3818.13.5 Minimum Standard

39The AT shall comply with steps k and n. 40The AN shall comply with steps l and o.
4118.14 AN Data Over Signaling Message Transmission 4218.14.1 Definition

43This test verifies that the AN can send a packet over the Control Channel to the AT. 44This is accomplished by using the Data Over Signaling (DoS) Protocol. Specifically, 45this test validates the delivery of higher layer packet using of a DataOverSignaling 46Message transmitted by the AN to the AT, and the MessageSequence increment for

32

13GPP2 C.S0044-A v1.0

1the DataOverSignaling Messages. This test also validates the ability of the AT to 2acknowledge the DataOverSignaling Message with a DataOverSignalingAck with 3appropriate AckSequence field when the AckRequired field in the DataOverSignaling 4Message is set to 1.

518.14.2 Traceability
6(see [24])

7 9

4.5

Data Over Signaling Protocol

8(see [12])

Chapters 2 and 3

1018.14.3 Call Flow Example(s)

11None 1218.14.4 Method of measurement 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42

a. b. c.

Connect the AT to the AN as shown in Figure A-3. Cause the AT to acquire the AN. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2, Enhanced CCMAC, Enhanced ACMAC, Subtype 3 RTC MAC. During Session Configuration, set the ProtocolIdentifier field of the FlowNNHigherLayerProtocolRev (NN = 0xij) and FlowNNHigherLayerProtocolFwd (NN = 0xij) to HDLC framing. During Session Configuration, set the Active parameter of FlowNNIdentificationFwd (NN = 0xij) attribute and FlowNNIdentificationRev (NN = 0xij) attribute to 0x01. Set the ReservationLabel for FlowNNReservationRev (NN = 0xij) and FlowNNReservationFwd (NN = 0xij) to High Priority Signaling. Set FlowNNDataOverSignalingAllowedRev (NN = 0xij) to 0x01. Configure the AN to grant the QoS request from the AT and to set ReservationKKIdleStateFwd and ReservationKKIdleStateRev to 0x0 for ReservationLabel kk associated with High Priority Signaling. If the AT does not have an established PPP session, cause the AT to establish a PPP session. Instruct the AT to send a ReservationOn message for ReservationLabel kk associated with High Priority Signaling data that is to be carried using DataOverSignaling message to the AN and ensure that the AN responds with a ReservationAccept message. Instruct the AT to send a ReservationOn message for ReservationLabel kk associated with High Priority Signaling data that is to be carried using DataOverSignaling message from the AN to the AT and ensure that the AN responds with a ReservationAccept message. Allow the HRPD connection to become idle. Cause the AN to transmit a packet directed to the AT using the DataOverSignaling message and setting the AckRequired field of the DataOverSignaling message to 1. Ensure that the DataOverSignaling Message size is less than the ControlChannel capsule size (600 bytes).

d.

e. f.

g. h.

i. j.

33

1
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

3GPP2 C.S0044-A v1.0 k. Verify that the AN transmits a DataOverSignaling Message with MessageID field set to 0x14, AckRequired field set to 1, Reset field set to 0, MessageSequence field set to 0, and the HigherLayerPacket field set to entire higher layer packet. Verify that if the AT received the DataOverSignaling Message, it transmits a DataOverSignalingAck with MessageID field set to 0x15 and AckSequence field set to zero and the packet carried in the DataOverSignaling message is delivered to the higher layer protocol. Cause the AN to transmit a packet directed to the AT using the DataOverSignaling message and setting the AckRequired field of the DataOverSignaling message to 1. Ensure that the DataOverSignaling message size is smaller than the Control Channel capsule size (600 bytes). Verify that the AN transmits a DataOverSignaling Message with MessageSequence field set to 1. Verify that if the AT received the DataOverSignaling Message, it transmits a DataOverSignalingAck with the AckSequence field set to one and the packet carried in the DataOverSignaling message is delivered to the higher layer protocol.

l.

m.

n. o.

1718.14.5 Minimum Standard

18The AT shall comply with steps l and o. 19The AN shall comply with steps k and n.
2018.15 Voice Origination in HRPD Idle Mode 2118.15.1 Definition 22This test verifies a voice origination call when in idle HRPD mode.

2318.15.2 Traceability
24(see [29]) 25(see [30]) 26(see [24]) 27 28 29 31 33 34 35 36 37 38 39

Chapter 7 Chapter 8 Chapter 10 Chapter 3 2.2.6.2.5 2.6.3 2.6.3.5 2.6.4 2.7.1.3.2.4 2.7.2.3.2.15 2.7.3

Session Layer Connection Layer MAC Layer HRPD IOS Call Flows Mobile Station Origination Operation System Access State Mobile Station Origination Attempt Substate Mobile Station Control on the Traffic Channel State Origination Message Service Option Control Message Orders

30(see [26]) 32(see [4])

34

13GPP2 C.S0044-A v1.0

1 2 3 4 5 6 7

3.6.3.5 3.6.4 3.7.2.3.2.21 3.7.3.3.2.3 3.7.3.3.2.20 3.7.4 3.7.5.5

Response to Origination Message Traffic Channel Processing Extended Channel Assignment Message Alert With Information Message Service Connect Message Orders Signal

818.15.3 Call Flow Example(s)

9None. 1018.15.4 Method of measurement 11 12 13 14 15

a. b. c. d.

Connect the hybrid AT to the AN as shown in Figure A-5 with AN 1 configured as cdma2000 1x and AN 2 configured as HRPD. Initiate a voice call from the hybrid AT. Verify the call completes and verify CDMA user data in both directions. End the call.

1618.15.5 Minimum Standard 17The AT and AN shall comply with step c. 1818.16 Voice Termination in HRPD Idle Mode 1918.16.1 Definition 20This test verifies a voice termination call when in idle HRPD mode.

2118.16.2 Traceability
22(see [29]) 23(see [30]) 24(see [24]) 25 26 27 29 31 32 33 34 35

Chapter 7 Chapter 8 Chapter 10 Chapter 3 2.2.6.2.5 2.6.3 2.6.3.5 2.6.4 2.7.1.3.2.4

Session Layer Connection Layer MAC Layer HRPD IOS Call Flows Mobile Station Origination Operation System Access State Mobile Station Origination Attempt Substate Mobile Station Control on the Traffic Channel State Origination Message

28(see [26]) 30(see [4])

35

1
1 2 3 4 5 6 7 8 9

3GPP2 C.S0044-A v1.0 2.7.2.3.2.15 2.7.3 3.6.3.5 3.6.4 3.7.2.3.2.21 3.7.3.3.2.3 3.7.3.3.2.20 3.7.4 3.7.5.5 Service Option Control Message Orders Response to Origination Message Traffic Channel Processing Extended Channel Assignment Message Alert With Information Message Service Connect Message Orders Signal

1018.16.3 Call Flow Example(s)

11None 1218.16.4 Method of measurement 13 14 15 16 17

a. b. c. d.

Connect the hybrid AT to the AN as shown in Figure A-5 with AN 1 configured as cdma2000 1x and AN 2 configured as HRPD. Initiate a voice call to the hybrid AT. Verify the call completes and verify CDMA user data in both directions. End the call.

1818.16.5 Minimum Standard 19The AT and AN shall comply with step c. 2018.17 SMS Origination in HRPD Idle Mode 2118.17.1 Definition 22This test verifies SMS Origination when in idle HRPD mode.

2318.17.2 Traceability
24(see [29]) 25(see [30]) 26(see [24]) 27 28 29 31

Chapter 7 Chapter 8 Chapter 10 Chapter 3

Session Layer Connection Layer MAC Layer HRPD IOS Call Flows

30(see [26]) 32(see [13])

3318.17.3 Call Flow Example(s)

34None

36

13GPP2 C.S0044-A v1.0

118.17.4 Method of measurement 2 3 4 5 6 7

a. b. c. d. e.

Connect the hybrid AT to the AN as shown in Figure A-5 with AN 1 configured as cdma2000 1x and AN 2 configured as HRPD. Instruct the hybrid AT to send an SMS message to the network on the r-csch. Verify SMS message is correctly sent to the SMS Message Center. Instruct the hybrid AT to send an SMS message on the r-dsch. Verify the SMS is correctly sent to the SMS Message Center.

818.17.5 Minimum Standard 9The AT and AN shall comply with steps c and e. 1018.18 SMS Termination in HRPD Idle Mode 1118.18.1 Definition 12This test verifies SMS termination when in idle HRPD mode.

1318.18.2 Traceability
14(see [29]) 15(see [30]) 16(see [24]) 17 18 19 21

Chapter 7 Chapter 8 Chapter 10 Chapter 3

Session Layer Connection Layer MAC Layer HRPD IOS Call Flows

20(see [26]) 22(see [13])

2318.18.3 Call Flow Example(s)

24None. 2518.18.4 Method of measurement 26 27 28 29 30 31

a. b. c. d. e.

Connect the hybrid AT to the AN as shown in Figure A-5 with AN 1 configured as cdma2000 1x and AN 2 configured as HRPD. Instruct the network to send an SMS message to the hybrid AT on the f-csch. Verify SMS message is correctly received at the hybrid AT. Instruct the network to send an SMS message to the hybrid AT on the f-dsch. Verify the SMS message is correctly received at the hybrid AT.

3218.18.5 Minimum Standard 33The AT and AN shall comply with steps c and e. 3418.19 Voice Origination in HRPD Active Mode 35Note: A hybrid AT may not support this feature

37

1
118.19.1 Definition 2This test verifies a voice origination call when in active HRPD mode.

3GPP2 C.S0044-A v1.0

318.19.2 Traceability
4(see [29]) 5(see [30]) 6(see [24]) 7 8 9 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26

Chapter 7 Chapter 8 Chapter 10 Chapter 3 2.2.6.2.5 2.6.3 2.6.3.5 2.6.4 2.7.1.3.2.4 2.7.2.3.2.15 2.7.3 3.6.3.5 3.6.4 3.7.2.3.2.21 3.7.3.3.2.3 3.7.3.3.2.20 3.7.4 3.7.5.5

Session Layer Connection Layer MAC Layer HRPD IOS Call Flows Mobile Station Origination Operation System Access State Mobile Station Origination Attempt Substate Mobile Station Control on the Traffic Channel State Origination Message Service Option Control Message Orders Response to Origination Message Traffic Channel Processing Extended Channel Assignment Message Alert With Information Message Service Connect Message Orders Signal

10(see [26]) 12(see [4])

2718.19.3 Call Flow Example(s)

28None 2918.19.4 Method of measurement 30 31 32 33 34 35 36

a. b. c. d. e. f.

Connect the hybrid AT to the AN as shown in Figure A-5 with AN 1 configured as cdma2000 1x and AN 2 configured as HRPD. Initiate a HRPD packet data call from the hybrid AT. Issue a continuous ping command from the hybrid AT to a remote host. Initiate a voice call from the hybrid AT. Verify the call completes and verify CDMA user data in both directions. End the voice call.

38

13GPP2 C.S0044-A v1.0

1 2 3

g. h.

After call is released, verify that hybrid AT re-connects the HRPD packet data call and pings are continuous on same ppp session. End the HRPD packet data call.

418.19.5 Minimum Standard 5The AT shall comply with steps e and g 6The AN shall comply with step e. 718.20 Voice Termination in HRPD Active Mode 8Note: A hybrid AT may not support this feature 918.20.1 Definition 10This test verifies a voice termination call when in active HRPD mode.

1118.20.2 Traceability
12(see [29]) 13(see [30]) 14(see [24]) 15 16 17 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34

Chapter 7 Chapter 8 Chapter 10 Chapter 3 2.2.6.2.5 2.6.3 2.6.3.5 2.6.4 2.7.1.3.2.4 2.7.2.3.2.15 2.7.3 3.6.3.5 3.6.4 3.7.2.3.2.21 3.7.3.3.2.3 3.7.3.3.2.20 3.7.4 3.7.5.5

Session Layer Connection Layer MAC Layer HRPD IOS Call Flows Mobile Station Origination Operation System Access State Mobile Station Origination Attempt Substate Mobile Station Control on the Traffic Channel State Origination Message Service Option Control Message Orders Response to Origination Message Traffic Channel Processing Extended Channel Assignment Message Alert With Information Message Service Connect Message Orders Signal

18(see [26]) 20(see [4])

39

1 118.20.3 Call Flow Example(s)

2None 318.20.4 Method of measurement 4 5 6 7 8 9 10 11 12 13

3GPP2 C.S0044-A v1.0

a. b. c. d. e. f. g. h.

Connect the hybrid AT to the AN as shown in Figure A-5 with AN 1 configured as cdma2000 1x and AN 2 configured as HRPD. Initiate a HRPD packet data call from the hybrid AT. Issue a continuous ping command from the hybrid AT to a remote host. Initiate a voice call to the AT. Verify the call completes and verify CDMA user data in both directions. End the voice call. After call is released, verify that hybrid AT re-connects the HRPD packet data call on the same PPP session and pings are continuous. End the HRPD packet data call.

1418.20.5 Minimum Standard 15The AT shall comply with steps e and g 16The AN shall comply with step e 1718.21 SMS Origination in HRPD Active Mode 18Note: A hybrid AT may not support this feature 1918.21.1 Definition 20This test verifies SMS Origination when in active HRPD mode.

2118.21.2 Traceability
22(see [29]) 23(see [30]) 24(see [24]) 25 26 27 29

Chapter 7 Chapter 8 Chapter 10 Chapter 3

Session Layer Connection Layer MAC Layer HRPD IOS Call Flows

28(see [26]) 30(see [13])

3118.21.3 Call Flow Example(s)

32None 3318.21.4 Method of measurement 34 35 36

a. b.

Connect the hybrid AT to the AN as shown in Figure A-5 with AN 1 configured as cdma2000 1x and AN 2 configured as HRPD. Initiate a HRPD packet data call from the hybrid AT.

40

13GPP2 C.S0044-A v1.0

1 2 3 4 5 6 7 8 9 10

c. d. e. f. g. h. i. j.

Issue a continuous ping command from the hybrid AT to a remote host. Instruct the hybrid AT to send an SMS message to the network on the r-csch Verify SMS message is correctly sent to the SMS Message Center. After SMS Origination procedure is completed, verify that hybrid AT starts sending and receiving continuous pings on HRPD on the same PPP session. Instruct the hybrid AT to send an SMS message to the network on the r-dsch. Verify SMS message is correctly sent to the SMS Message Center. After SMS Origination procedure is completed, verify that hybrid AT starts sending and receiving continuous pings on HRPD on the same PPP session. End the HRPD packet data call.

1118.21.5 Minimum Standard 12The AT shall comply with steps e, f, h and i 13The AN shall comply with steps e and i. 1418.22 SMS Termination in HRPD Active Mode 15Note: A hybrid AT may not support this feature 1618.22.1 Definition 17This test verifies SMS termination when in active HRPD mode.

1818.22.2 Traceability
19(see [29]) 20(see [30]) 21(see [24]) 22 23 24 26

Chapter 7 Chapter 8 Chapter 10 Chapter 3

Session Layer Connection Layer MAC Layer HRPD IOS Call Flows

25(see [26]) 27(see [13])

2818.22.3 Call Flow Example(s)

29None 3018.22.4 Method of measurement 31 32 33 34 35 36

a. b. c. d. e.

Connect the hybrid AT to the AN as shown in Figure A-5 with AN 1 configured as cdma2000 1x and AN 2 configured as HRPD. Initiate a HRPD packet data call from the hybrid AT. Issue a continuous ping command from the hybrid AT to a remote host. Instruct the network to send an SMS message to the hybrid AT on the f-csch. Verify SMS message is correctly received by the hybrid AT.

41

1
1 2 3 4 5 6 7

3GPP2 C.S0044-A v1.0 f. g. h. i. j. After SMS message is received, verify that hybrid AT starts sending and receiving continuous pings on HRPD on the same PPP session. Instruct the network to send an SMS message to the hybrid AT on the f-dsch. Verify SMS message is correctly received by the hybrid AT. After SMS message is received, verify that hybrid AT starts sending and receiving continuous pings on HRPD on the same PPP session. End the HRPD packet data call.

818.22.5 Minimum Standard 9The AT shall comply with steps e, f, h and i 10The AN shall comply with steps e and i. 1118.23 Voice Origination in HRPD Dormant Mode 12Note: A hybrid AT may not support this feature 1318.23.1 Definition 14This test verifies a voice origination call when in dormant HRPD mode.

1518.23.2 Traceability
16(see [29]) 17(see [30]) 18(see [24]) 19 20 21 23 25 26 27 28 29 30 31 32 33 34 35 36

Chapter 7 Chapter 8 Chapter 10 Chapter 3 2.2.6.2.5 2.6.3 2.6.3.5 2.6.4 2.7.1.3.2.4 2.7.2.3.2.15 2.7.3 3.6.3.5 3.6.4 3.7.2.3.2.21 3.7.3.3.2.3 3.7.3.3.2.20

Session Layer Connection Layer MAC Layer HRPD IOS Call Flows Mobile Station Origination Operation System Access State Mobile Station Origination Attempt Substate Mobile Station Control on the Traffic Channel State Origination Message Service Option Control Message Orders Response to Origination Message Traffic Channel Processing Extended Channel Assignment Message Alert With Information Message Service Connect Message

22(see [26]) 24(see [4])

42

13GPP2 C.S0044-A v1.0

1 2

3.7.4 3.7.5.5

Orders Signal

318.23.3 Call Flow Example(s)

4None 518.23.4 Method of measurement 6 7 8 9 10 11 12 13 14 15 16

a. b. c. d. e. f. g. h. i.

Connect the hybrid AT to the AN as shown in Figure A-5 with AN 1 configured as cdma2000 1x and AN 2 configured as HRPD. Initiate a HRPD packet data call from the hybrid AT. Wait for hybrid AT to go dormant. Initiate a voice call from the hybrid AT. Verify the call completes and verify CDMA user data in both directions. End the voice call. Verify that PPP connection is not dropped, hybrid AT is in dormant state and HRPD session is active. Issue a ping command and verify that pings are successful. End the HRPD packet data call.

1718.23.5 Minimum Standard 18The AT shall comply with steps e, g and h 19The AN shall comply with step e and h 2018.24 Voice Termination in HRPD Dormant Mode 2118.24.1 Definition 22This test verifies a voice termination call when in dormant HRPD mode.

2318.24.2 Traceability
24(see [29]) 25(see [30]) 26(see [24]) 27 28 29 31 33 34 35 36

Chapter 7 Chapter 8 Chapter 10 Chapter 3 2.2.6.2.5 2.6.3 2.6.3.5 2.6.4

Session Layer Connection Layer MAC Layer HRPD IOS Call Flows Mobile Station Origination Operation System Access State Mobile Station Origination Attempt Substate Mobile Station Control on the Traffic Channel State

30(see [26]) 32(see [4])

43

1
1 2 3 4 5 6 7 8 9 10

3GPP2 C.S0044-A v1.0 2.7.1.3.2.4 2.7.2.3.2.15 2.7.3 3.6.3.5 3.6.4 3.7.2.3.2.21 3.7.3.3.2.3 3.7.3.3.2.20 3.7.4 3.7.5.5 Origination Message Service Option Control Message Orders Response to Origination Message Traffic Channel Processing Extended Channel Assignment Message Alert With Information Message Service Connect Message Orders Signal

1118.24.3 Call Flow Example(s)

12None 1318.24.4 Method of measurement 14 15 16 17 18 19 20 21 22 23

a. b. c. d. e. f. g. h. i.

Connect the hybrid AT to the AN as shown in Figure A-5 with AN 1 configured as cdma2000 1x and AN 2 configured as HRPD. Initiate a HRPD packet data call from the hybrid AT. Wait for hybrid AT to go dormant. Initiate a voice call to the hybrid AT. Verify the call completes and verify CDMA user data in both directions. End the voice call. Verify that PPP connection is not dropped and hybrid AT is in dormant state. Issue a ping command and verify that pings are successful. End the HRPD packet data call.

2418.24.5 Minimum Standard 25The AT shall comply with steps e, g and h 26The AN shall comply with step e and h. 2718.25 SMS Origination in HRPD Dormant Mode 2818.25.1 Definition 29This test verifies SMS Origination when in dormant HRPD mode.

3018.25.2 Traceability
31(see [29]) 32(see [30]) 33(see [24]) 34 35

Chapter 7 Chapter 8

Session Layer Connection Layer

44

13GPP2 C.S0044-A v1.0

1 3

Chapter 10 Chapter 3

MAC Layer HRPD IOS Call Flows

2(see [26]) 4(see [13])

518.25.3 Call Flow Example(s)

6None 718.25.4 Method of measurement 8 9 10 11 12 13 14 15 16 17 18 19 20 21

a. b. c. d. e. f. g. h. i. j. k. l. m.

Connect the hybrid AT to the AN as shown in Figure A-5 with AN 1 configured as cdma2000 1x and AN 2 configured as HRPD. Initiate a HRPD packet data call from the hybrid AT. Wait for hybrid AT to go dormant. Instruct the hybrid AT to send an SMS message to the network on the r-csch. Verify SMS message is correctly sent to the SMS Message Center. Verify that PPP connection is not dropped and hybrid AT is in dormant state. Issue a ping command and verify that pings are successful. Wait for hybrid AT to go dormant. Instruct the hybrid AT to send an SMS message to the network on the r-dsch. Verify SMS message is correctly sent to the SMS Message Center. Verify that PPP connection is not dropped and hybrid AT is in dormant state. Issue a ping command from the remote host and verify that the ping is successful. End the HRPD packet data call.

2218.25.5 Minimum Standard 23The AT shall comply with steps e, f, g, j, k and l. 24The AN shall comply with steps e, g, j and l. 2518.26 SMS Termination in HRPD Dormant Mode 2618.26.1 Definition 27This test verifies SMS termination when in dormant HRPD mode.

2818.26.2 Traceability
29(see [29]) 30(see [30]) 31(see [24]) 32 33 34

Chapter 7 Chapter 8 Chapter 10

Session Layer Connection Layer MAC Layer

35(see [26])

45

1
1

3GPP2 C.S0044-A v1.0 Chapter 3 HRPD IOS Call Flows

2(see [13])

318.26.3 Call Flow Example(s)

4None 518.26.4 Method of measurement 6 7 8 9 10 11 12 13 14 15 16 17 18 19

a. b. c. d. e. f. g. h. i. j. k. l. m.

Connect the hybrid AT to the AN as shown in Figure A-5 with AN 1 configured as cdma2000 1x and AN 2 configured as HRPD. Initiate a HRPD packet data call from the hybrid AT. Wait for hybrid AT to go dormant. Instruct the network to send an SMS message to the hybrid AT on the f-csch. Verify SMS message is correctly received by the hybrid AT. Verify that PPP connection is not dropped and hybrid AT is in dormant state. Issue a ping command from the remote host and verify that the ping is successful. Wait for hybrid AT to go dormant. Instruct the network to send an SMS message to the hybrid AT on the f-dsch. Verify SMS message is correctly received by the hybrid AT. Verify that PPP connection is not dropped and hybrid AT is in dormant state. Issue a ping command and verify that pings are successful. End the HRPD packet data call.

2018.26.5 Minimum Standard 21The AT shall comply with steps e, f, g, j, k and l. 22The AN shall comply with steps e, g, j and l. 2318.27 Inter Revision Handoffs - Dormant HRPD Rev A to HRPD Rev 0 2418.27.1 Definition 25This test verifies inter-technology handoff from dormant HRPD RevA to HRPD Rev0 using mobile 26IP.

2718.27.2 Traceability
28(see [29]) 29(see [30]) 30(see [24]) 31 32 33 35

Chapter 7 Chapter 8 Chapter 10 Chapter 3

Session Layer Connection Layer MAC Layer HRPD IOS Call Flows

34(see [26]) 36(see [4])

46

13GPP2 C.S0044-A v1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14

2.2.6.2.5 2.6.3 2.6.3.5 2.6.4 2.7.1.3.2.4 2.7.2.3.2.15 2.7.3 3.6.3.5 3.6.4 3.7.2.3.2.21 3.7.3.3.2.3 3.7.3.3.2.20 3.7.4 3.7.5.5

Mobile Station Origination Operation System Access State Mobile Station Origination Attempt Substate Mobile Station Control on the Traffic Channel State Origination Message Service Option Control Message Orders Response to Origination Message Traffic Channel Processing Extended Channel Assignment Message Alert With Information Message Service Connect Message Orders Signal

1518.27.3 Call Flow Example(s)

16None 1718.27.4 Method of measurement 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41

a. b.

Connect the hybrid AT to the AN as shown in Figure A-5 with AN 1 configured as HRPD RevA and AN 2 configured as HRPD Rev0. Configure the hybrid AT for mobile IP mode and during session configuration negotiate one personality defined for HRPD Rev A and one personality defined for HRPD Rev 0. Note, the session configuration with multiple personalities needs to be done with AN configured with HRPD Rev A. Cause the hybrid AT to acquire AN 1 configured as HRPD RevA and negotiate 2 personalities during the HRPD session configuration. Initiate a HRPD RevA packet data call from the hybrid AT. Record the IP address assigned to the hybrid AT. Wait for hybrid AT to go dormant. Instruct AN 1 configured as HRPD RevA to initiate handoff to AN 2 configured as HRPD Rev0. Ensure the AN 1 sends an AttributeUpdateRequest with the SessionConfigurationToken instructing the AT to switch to the personality for the HRPD Rev 0 network. Verify the AT sends an AttributeUpdateAccept to the AN 1 and begins using the HRPD Rev 0 personality. Ensure that the hybrid AT is dormant for data (active pilot set) on AN 2 configured as HRPD Rev0. Issue a ping command from the remote host to the hybrid AT using the IP address assigned to the AT in step e. Verify the hybrid AT is active for data on AN 2 configured for HRPD Rev0, and verify the remote host receives a ping response from the hybrid AT. 47

c. d. e. f. g. h.

i. j. k. l.

1
1

3GPP2 C.S0044-A v1.0 m. End the call.

218.27.5 Minimum Standard 3The AT shall comply with steps i and l. 418.28 Inter Revision Handoffs - Active HRPD Rev A to HRPD Rev 0 518.28.1 Definition 6This test verifies inter-technology handoff from active HRPD RevA to HRPD Rev0 using mobile 7IP.

818.28.2 Traceability
9(see [29]) 10(see [30]) 11(see [24]) 12 13 14 16 18 19 20 21 22 23 24 25 26 27 28 29 30 31

Chapter 7 Chapter 8 Chapter 10 Chapter 3 2.2.6.2.5 2.6.3 2.6.3.5 2.6.4 2.7.1.3.2.4 2.7.2.3.2.15 2.7.3 3.6.3.5 3.6.4 3.7.2.3.2.21 3.7.3.3.2.3 3.7.3.3.2.20 3.7.4 3.7.5.5

Session Layer Connection Layer MAC Layer HRPD IOS Call Flows Mobile Station Origination Operation System Access State Mobile Station Origination Attempt Substate Mobile Station Control on the Traffic Channel State Origination Message Service Option Control Message Orders Response to Origination Message Traffic Channel Processing Extended Channel Assignment Message Alert With Information Message Service Connect Message Orders Signal

15(see [26]) 17(see [4])

3218.28.3 Call Flow Example(s)

33None 3418.28.4 Method of measurement 35 36

a.

Connect the hybrid AT to the AN as shown in Figure A-5 with AN 1 configured as HRPD RevA and AN 2 configured as HRPD Rev0.

48

13GPP2 C.S0044-A v1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

b.

Configure the hybrid AT for mobile IP mode and during session configuration negotiate one personality defined for HRPD Rev A and one personality defined for HRPD Rev 0. Note, the session configuration with multiple personalities needs to be done with AN configured with HRPD Rev A. Cause the hybrid AT to acquire AN 1 configured as HRPD RevA and negotiate 2 personalities during the HRPD session configuration. Initiate a HRPD RevA packet data call from the hybrid AT. Record the IP address assigned to the hybrid AT. Issue a continuous ping command from the remote host to the hybrid AT using the IP address assigned to the AT in step e. Verify AT is active for data on AN 1 configured as HRPD RevA, and verify the remote host receives a ping response from the AT. Instruct AN 1 configured as HRPD RevA to initiate handoff to AN 2 configured as HRPD Rev0. Ensure the AN 1 sends an AttributeUpdateRequest with the SessionConfigurationToken instructing the AT to switch to the personality for the HRPD Rev 0 network. Verify the AT sends an AttributeUpdateAccept to the AN 1. Verify that the AN 1 transmits a ConnectionClose together with a TrafficChannelAssignment message. Verify that the AT reestablishes the connection and starts using the HRPD Rev 0 personality. Verify hybrid AT is active for data on AN 2 configured as HRPD Rev0 and verify the remote host receives a ping response from the hybrid AT. End the call.

c. d. e. f. g. h. i.

j. k. l. m. n.

2618.28.5 Minimum Standard 27The AT shall comply with the steps g, j, l and m. 28The AN shall comply with step k and m. 2918.29 Inter Revision Handoffs Dormant HRPD Rev 0 to HRPD Rev A 3018.29.1 Definition 31This test verifies inter-technology handoff from dormant HRPD Rev0 to HRPD RevA using mobile 32IP.

3318.29.2 Traceability
34(see [29]) 35(see [30]) 36(see [24]) 37 38 39

Chapter 7 Chapter 8 Chapter 10

Session Layer Connection Layer MAC Layer

40(see [26])

49

1
1 3 4 5 6 7 8 9 10 11 12 13 14 15 16

3GPP2 C.S0044-A v1.0 Chapter 3 2.2.6.2.5 2.6.3 2.6.3.5 2.6.4 2.7.1.3.2.4 2.7.2.3.2.15 2.7.3 3.6.3.5 3.6.4 3.7.2.3.2.21 3.7.3.3.2.3 3.7.3.3.2.20 3.7.4 3.7.5.5 HRPD IOS Call Flows Mobile Station Origination Operation System Access State Mobile Station Origination Attempt Substate Mobile Station Control on the Traffic Channel State Origination Message Service Option Control Message Orders Response to Origination Message Traffic Channel Processing Extended Channel Assignment Message Alert With Information Message Service Connect Message Orders Signal

2(see [4])

1718.29.3 Call Flow Example(s)

18None 1918.29.4 Method of measurement 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40

a. b.

Connect the hybrid AT to the AN as shown in Figure A-5 with AN 2 configured as HRPD Rev0 and AN 1 configured as HRPD RevA. Configure the hybrid AT for mobile IP mode and during session configuration negotiate one personality defined for HRPD Rev A and one personality defined for HRPD Rev 0. Note, the session configuration with multiple personalities needs to be done with AN configured with HRPD Rev A. Cause the hybrid AT to acquire AN 2 configured as HRPD Rev0. Initiate a HRPD Rev0 packet data call from the hybrid AT. Record the IP address assigned to the hybrid AT. Wait for hybrid AT to go dormant. Instruct AN 2 configured as HRPD Rev0 to initiate handoff to AN 1 configured as HRPD RevA. Ensure that hybrid AT is dormant for data (active pilot set) on AN 1 configured as HRPD RevA. Ensure the AN 1 sends an AttributeUpdateRequest with the SessionConfigurationToken instructing the AT to switch to the personality for the HRPD Rev A network. Verify the AT sends an AttributeUpdateAccept to the AN 1 and begins using the HRPD Rev A personality. Issue a ping command from the remote host to the hybrid AT using the IP address assigned to the AT in step e.

c. d. e. f. g. h. i.

j. k.

50

13GPP2 C.S0044-A v1.0

1 2 3

l. m.

Verify the hybrid AT is active for data on AN 1 configured for HRPD RevA, and verify the remote host receives a ping response from the hybrid AT. End the call.

418.29.5 Minimum Standard 5The AT and AN shall comply with steps j and l. 6The AN shall comply with step l. 718.30 Inter Revision Handoffs Active HRPD Rev 0 to HRPD Rev A 818.30.1 Definition 9This test verifies inter-technology handoff from active HRPD Rev0 to HRPD RevA using mobile 10IP.

1118.30.2 Traceability
12(see [29]) 13(see [30]) 14(see [24]) 15 16 17 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34

Chapter 7 Chapter 8 Chapter 10 Chapter 3 2.2.6.2.5 2.6.3 2.6.3.5 2.6.4 2.7.1.3.2.4 2.7.2.3.2.15 2.7.3 3.6.3.5 3.6.4 3.7.2.3.2.21 3.7.3.3.2.3 3.7.3.3.2.20 3.7.4 3.7.5.5

Session Layer Connection Layer MAC Layer HRPD IOS Call Flows Mobile Station Origination Operation System Access State Mobile Station Origination Attempt Substate Mobile Station Control on the Traffic Channel State Origination Message Service Option Control Message Orders Response to Origination Message Traffic Channel Processing Extended Channel Assignment Message Alert With Information Message Service Connect Message Orders Signal

18(see [26]) 20(see [4])

3518.30.3 Call Flow Example(s)

36None

51

1
118.30.4 Method of measurement 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

3GPP2 C.S0044-A v1.0

a. b.

Connect the hybrid AT to the AN as shown in Figure A-5 with AN 2 configured as HRPD Rev0 and AN 1 configured as HRPD RevA. Configure the hybrid AT for mobile IP mode and during session configuration negotiate one personality defined for HRPD Rev A and one personality defined for HRPD Rev 0. Note, the session configuration with multiple personalities needs to be done with AN configured with HRPD Rev A. Cause the hybrid AT to acquire AN 2 configured as HRPD Rev0. Initiate a HRPD Rev0 packet data call from the hybrid AT. Record the IP address assigned to the hybrid AT. Issue a continuous ping command from the remote host to the hybrid AT using the IP address assigned to the AT in step e. Ensure that AT is active for data on AN 2 configured as HRPD Rev0, and verify the remote host receives a ping response from the AT. Instruct AN 2 configured as HRPD Rev0 to initiate handoff to AN 1 configured as HRPD RevA. Verify hybrid AT is active for data on AN 1 configured as HRPD RevA and verify the remote host receives a ping response from the hybrid AT. (The AT will continue to use the HRPD Rev 0 session configuration) Terminate the ping session and allow the AT to go dormant on AN 1. After the device has gone dormant, initiate another ping from the AT to the AN. Verify the AT and AN 1 negotiate the HRPD session using the HRPD Rev A personality and the call completes successfully. End the call.

c. d. e. f. g. h. i.

j. k. l. m.

2518.30.5 Minimum Standard 26The AT shall comply with steps i and l. 27The AN shall comply with step l. 2818.31 Inter Technology Switching Dormant HRPD to cdma2000 1x 2918.31.1 Definition 30This test verifies inter-technology switching from dormant HRPD to cdma2000 1x using mobile IP. 31This test only applies to AT that are capable of switching from HRPD to cdma2000 1x while the 32AT is dormant. The algorithm for switching is AT dependent and should be known before test 33case execution. The test should be repeated using all supported revisions of [24] supported by 34the AT and AN.

3518.31.2 Traceability
36(see [29]) 37(see [30]) 38(see [24]) 39 40

Chapter 7 Chapter 8

Session Layer Connection Layer

52

13GPP2 C.S0044-A v1.0

1 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18

Chapter 10 Chapter 3 2.2.6.2.5 2.6.3 2.6.3.5 2.6.4 2.7.1.3.2.4 2.7.2.3.2.15 2.7.3 3.6.3.5 3.6.4 3.7.2.3.2.21 3.7.3.3.2.3 3.7.3.3.2.20 3.7.4 3.7.5.5

MAC Layer HRPD IOS Call Flows Mobile Station Origination Operation System Access State Mobile Station Origination Attempt Substate Mobile Station Control on the Traffic Channel State Origination Message Service Option Control Message Orders Response to Origination Message Traffic Channel Processing Extended Channel Assignment Message Alert With Information Message Service Connect Message Orders Signal

2(see [26]) 4(see [4])

1918.31.3 Call Flow Example(s)

20None 2118.31.4 Method of measurement 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38

a. b. c. d. e. f. g. h. i. j. k. l.

Connect the hybrid AT to the AN as shown in Figure A-5 with AN 1 configured as HRPD and AN 2 configured as cdma2000 1x. Configure the hybrid AT for mobile IP mode. Cause the hybrid AT to acquire AN 1 configured as HRPD. Initiate a HRPD packet data call from the hybrid AT. Record the IP address assigned to the hybrid AT. Wait for hybrid AT to go dormant. Cause the AT terminal to switch from AN 1, configured as HRPD to AN 2 configured as cdma2000 1x. Verify hybrid AT is dormant for data (active pilot set) on AN 2 configured as cdma2000 1x. Issue a ping command from the remote host to the hybrid AT using the IP address assigned to the AT in step e. Verify the hybrid AT is active for data on AN 2 configured for cdma2000 1x, and verify the remote host receives a ping response from the hybrid AT. End the call. Repeat steps a-k using all supported revisions of [24] by the AT and AN.

53

1
118.31.5 Minimum Standard 2The AT shall comply with steps h and j 3The AN shall comply with step j. 418.32 Inter Technology Switching Active HRPD to cdma2000 1x 518.32.1 Definition

3GPP2 C.S0044-A v1.0

6This test verifies inter-technology switching from active HRPD to cdma2000 1x using mobile IP. 7This test only applies to AT that are capable of switching from HRPD to cdma2000 1x while the 8AT is active for data. The algorithm for switching is AT dependent and should be known before 9test case execution. The test should be repeated using all supported revisions of [24] supported 10by the AT and AN.

1118.32.2 Traceability
12(see [29]) 13(see [30]) 14(see [24]) 15 16 17 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34

Chapter 7 Chapter 8 Chapter 10 Chapter 3 2.2.6.2.5 2.6.3 2.6.3.5 2.6.4 2.7.1.3.2.4 2.7.2.3.2.15 2.7.3 3.6.3.5 3.6.4 3.7.2.3.2.21 3.7.3.3.2.3 3.7.3.3.2.20 3.7.4 3.7.5.5

Session Layer Connection Layer MAC Layer HRPD IOS Call Flows Mobile Station Origination Operation System Access State Mobile Station Origination Attempt Substate Mobile Station Control on the Traffic Channel State Origination Message Service Option Control Message Orders Response to Origination Message Traffic Channel Processing Extended Channel Assignment Message Alert With Information Message Service Connect Message Orders Signal

18(see [26]) 20(see [4])

3518.32.3 Call Flow Example(s)

36None

54

13GPP2 C.S0044-A v1.0

118.32.4 Method of measurement 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

a. b. c. d. e. f. g. h. i. j. k.

Connect the hybrid AT to the AN as shown in Figure A-5 with AN 1 configured as HRPD and AN 2 configured as cdma2000 1x. Configure the hybrid AT for mobile IP mode. Cause the hybrid AT to acquire AN 1 configured as HRPD. Initiate a HRPD packet data call from the hybrid AT. Record the IP address assigned to the hybrid AT. Issue a continuous ping command from the remote host to the hybrid AT using the IP address assigned to the AT in step e. Ensure that AT is active for data on AN 1 configured as HRPD and verify the remote host receives a ping response from the AT. Cause the AT terminal to switch from AN 1, configured as HRPD to AN 2 configured as cdma2000 1x. Verify hybrid AT is active for data on AN 2 configured as cdma2000 1x and verify the remote host receives a ping response from the hybrid AT. End the call. Repeat steps a-k using all supported revisions of [24] by the AT and AN.

1818.32.5 Minimum Standard 19The AT and AN shall comply with step i 2018.33 Inter Technology Switching Dormant cdma2000 1x to HRPD 2118.33.1 Definition 22This test verifies inter-technology handoff from dormant cdma2000 1x to HRPD using mobile IP. 23This test only applies to AT that are capable of switching from cdma2000 1x to HRPD while the 24AT is dormant. The algorithm for switching is AT dependent and should be known before test 25case execution. The test should be repeated using all supported revisions of [24] supported by 26the AT and AN.

2718.33.2 Traceability
28(see [29]) 29(see [30]) 30(see [24]) 31 32 33 35 37 38 39

Chapter 7 Chapter 8 Chapter 10 Chapter 3 2.2.6.2.5 2.6.3 2.6.3.5

Session Layer Connection Layer MAC Layer HRPD IOS Call Flows Mobile Station Origination Operation System Access State Mobile Station Origination Attempt Substate

34(see [26]) 36(see [4])

55

1
1 2 3 4 5 6 7 8 9 10 11

3GPP2 C.S0044-A v1.0 2.6.4 2.7.1.3.2.4 2.7.2.3.2.15 2.7.3 3.6.3.5 3.6.4 3.7.2.3.2.21 3.7.3.3.2.3 3.7.3.3.2.20 3.7.4 3.7.5.5 Mobile Station Control on the Traffic Channel State Origination Message Service Option Control Message Orders Response to Origination Message Traffic Channel Processing Extended Channel Assignment Message Alert With Information Message Service Connect Message Orders Signal

1218.33.3 Call Flow Example(s)

13None 1418.33.4 Method of measurement 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

a. b. c. d. e. f. g. h. i. j. k. l.

Connect the hybrid AT to the AN as shown in Figure A-5 with AN 1 configured as cdma2000 1x and AN 2 configured as HRPD. Configure the hybrid AT for mobile IP mode. Cause the hybrid AT to acquire AN 1 configured as cdma2000 1x. Initiate a cdma2000 1x packet data call from the hybrid AT. Record the IP address assigned to the hybrid AT. Wait for hybrid AT to go dormant. Cause the AT terminal to switch from AN 1, configured as cdma2000 1x to AN 2 configured as HRPD. Verify hybrid AT is dormant for data (active pilot set) on AN 2 configured as HRPD. Issue a ping command from the remote host to the hybrid AT using the IP address assigned to the AT in step e. Verify the hybrid AT is active for data on AN 2 configured for HRPD, and verify the remote host receives a ping response from the hybrid AT. End the call Repeat steps a-k using all supported revisions of [24] by the AT and AN.

3118.33.5 Minimum Standard 32The AT shall comply with steps h and j. 3318.34 Inter RNC Dormant Hand-off (Rev A to Rev A) 3418.34.1 Definition 35This test verifies the Inter-RNC dormant handoff is successful. AN 1 and AN 2 have a different 36RNC. Both AN 1 and AN 2 support HRPD Rev A. RNC 1 and RNC 2 have an A13 link 37established.

56

13GPP2 C.S0044-A v1.0 118.34.2 Traceability

2(see [24]) 3 4 5 6 7 9 10

8.2 8.2.6.1.2 8.4 8.4.6.1.6 8.6 3.7.1

Default Air Link Management Protocol Initialization State Default Idle State Protocol Connection Setup State Default Connected State Protocol PCF-PCF Dormant Handoff with Successful Retrieval of HRPD Session Information

8(see [26])

1118.34.3 Call Flow Example(s)

12None 1318.34.4 Method of measurement 14 15 16 17 18 19 20 21 22

a.

Connect the AT to AN 1 and AN 2 as shown in Figure A-5. 1. AN 1 and AN 2 have different frequency assignments. 2. AN 1 and AN 2 have different RNC connections. Each RNC is broadcasting a different subnet. There is an A13 link between each RNC.

b. c. d. e. f.

Cause the AT to acquire AN 1. Setup an HRPD AT originated call. Ensure that the AT connection is idle and the PPP session is dormant. Force the AT to handoff from AN 1 to AN 2. After the AT has successfully acquired AN 2, issue a ping from AT. Verify the AT successfully establishes an HRPD connection and call on AN 2, RNC 2.

2318.34.5 Minimum Standard 24The AT shall comply with step f. 2518.35 Inter RNC Active Hand-off (Rev A to Rev A) 2618.35.1 Definition 27This test verifies the Inter-RNC active handoff is successful. AN 1 and AN 2 have a different 28RNC. Both AN 1 and AN 2 support HRPD Rev A. RNC 1 and RNC 2 have an A13 link 29established.

3018.35.2 Traceability
31(see [24]) 32 33 34 35 36

8.2 8.2.6.1.2 8.4 8.4.6.1.6 8.6

Default Air Link Management Protocol Initialization State Default Idle State Protocol Connection Setup State Default Connected State Protocol

57

1
1(see [26]) 2 3

3GPP2 C.S0044-A v1.0

3.7.1

PCF-PCF Dormant Handoff with Successful Retrieval of HRPD Session Information

418.35.3 Call Flow Example(s)

5None 618.35.4 Method of measurement 7 8 9 10 11 12 13 14 15 16

a.

Connect the AT to AN 1 and AN 2 as shown in Figure A-5. 1. AN 1 and AN 2 supports HRPD Rev A and have different frequency assignments. 2. AN 1 and AN 2 have different RNC connections. Each RNC is broadcasting a different subnet. There is an A13 link between each RNC.

b. c. d. e.

Cause the AT to acquire AN 1. Set up an HRPD AT originated call. Initiate a forward data transfer using the maximum supported data rate to the AT (i.e. use the FTP get command from the AT) Force the AT to handoff from AN 1 to AN 2 before the file transfer is completed. Verify the AT successfully acquires AN 2, RNC 2, and the file transfer is completed.

1718.35.5 Minimum Standard 18The AT shall comply with step e. 1918.36 Inter RNC Dormant Hand-off (Rev A to Rev 0) 2018.36.1 Definition 21This test verifies the Inter-RNC dormant handoff is successful. AN 1 and AN 2 have a different 22RNC. AN 1 supports HRPD Rev A and AN 2 support HRPD Rev 0. RNC 1 and RNC 2 have an 23A13 link established.

2418.36.2 Traceability
25(see [24]) 26 27 28 29 30 32 33

8.2 8.2.6.1.2 8.4 8.4.6.1.6 8.6 3.7.1

Default Air Link Management Protocol Initialization State Default Idle State Protocol Connection Setup State Default Connected State Protocol PCF-PCF Dormant Handoff with Successful Retrieval of HRPD Session Information

31(see [26])

3418.36.3 Call Flow Example(s)

35None. 3618.36.4 Method of measurement 37

a.

Connect the AT to AN 1 and AN 2 as shown in Figure A-5.

58

13GPP2 C.S0044-A v1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

1. AN 1 supports HRPD Rev A and AN 2 supports HRPD Rev 0 and have different frequency assignments. 2. AN 1 and AN 2 have different RNC connections. Each RNC is broadcasting a different subnet. There is an A13 link between each RNC. b. c. d. e. Cause the AT to acquire AN 1 and negotiate multiple personalities with one personality defined for HRPD Rev A and one personality defined for HRPD Rev 0 Setup an HRPD AT originated call ensure that the AT connection is idle and the PPP session is dormant. Force the AT to handoff from AN 1 to AN 2. Ensure the AN 1 sends an AttributeUpdateRequest with the SessionConfigurationToken instructing the AT to switch to the personality for the HRPD Rev 0 network. Verify the AT sends an AttributeUpdateAccept to the AN 1 and begins using the HRPD Rev 0 personality. After the AT has successfully acquired AN 2, issue a ping from AT. Verify the AT successfully establishes an HRPD connection and call on AN 2, RNC 2.

f. g. h.

1718.36.5 Minimum Standard 18The AT shall comply with steps f and h. 1918.37 Inter RNC Active Hand-off (Rev A to Rev 0) 2018.37.1 Definition 21This test verifies the Inter-RNC active handoff is successful. AN 1 and AN 2 have a different 22RNC. AN 1 supports HRPD Rev A and AN 2 support HRPD Rev 0. RNC 1 and RNC 2 have an 23A13 link established.

2418.37.2 Traceability
25(see [24]) 26 27 28 29 30 32 33

8.2 8.2.6.1.2 8.4 8.4.6.1.6 8.6 3.7.1

Default Air Link Management Protocol Initialization State Default Idle State Protocol Connection Setup State Default Connected State Protocol PCF-PCF Dormant Handoff with Successful Retrieval of HRPD Session Information

31(see [26])

3418.37.3 Call Flow Example(s)

35None 3618.37.4 Method of measurement 37 38 39

a.

Connect the AT to AN 1 and AN 2 as shown in Figure A-5. 1. AN 1 supports HRPD Rev A and AN 2 supports HRPD Rev 0 and have different frequency assignments.

59

1
1 2 3 4 5 6 7 8 9 10 11 12

3GPP2 C.S0044-A v1.0 2. AN 1 and AN 2 have different RNC connections. Each RNC is broadcasting a different subnet. There is an A13 link between each RNC b. c. d. e. Cause the AT to acquire AN 1 and negotiate multiple personalities with one personality defined for HRPD Rev A and one personality defined for HRPD Rev 0 Set up an HRPD AT originated call and initiate a forward data transfer using the maximum supported data rate to the AT (i.e. use the FTP get command from the AT) Force the AT to handoff from AN 1 to AN 2. Ensure the AN 1 sends an AttributeUpdateRequest with the SessionConfigurationToken instructing the AT to switch to the personality for the HRPD Rev 0 network. Verify the AT sends an AttributeUpdateAccept to the AN 1 and begins using the HRPD Rev 0 personality

f.

1318.37.5 Minimum Standard 14The AT shall comply with step f. 1518.38 Inter RNC Dormant Hand-off (Rev 0 to Rev A) 1618.38.1 Definition 17This test verifies the Inter-RNC dormant handoff is successful. AN 1 and AN 2 have a different 18RNC. AN 1 supports HRPD Rev 0 and AN 2 support HRPD Rev A. RNC 1 and RNC 2 have an 19A13 link established.

2018.38.2 Traceability
21(see [24]) 22 23 24 25 26 28 29

8.2 8.2.6.1.2 8.4 8.4.6.1.6 8.6 3.7.1

Default Air Link Management Protocol Initialization State Default Idle State Protocol Connection Setup State Default Connected State Protocol PCF-PCF Dormant Handoff with Successful Retrieval of HRPD Session Information

27(see [26])

3018.38.3 Call Flow Example(s)

31None 3218.38.4 Method of measurement 33 34 35 36 37 38 39

a.

Connect the AT to AN 1 and AN 2 as shown in Figure A-5. 1. AN 1 supports HRPD Rev 0 and AN 2 support HRPD Rev A and have different frequency assignments. 2. AN 1 and AN 2 have different RNC connections. Each RNC is broadcasting a different subnet. There is an A13 link between each RNC.

b.

Configure the hybrid AT for mobile IP mode and during session configuration negotiate one personality defined for HRPD Rev A and one personality defined for HRPD Rev 0.

60

13GPP2 C.S0044-A v1.0

1 2 3 4 5 6 7 8 9 10 11 12 13

Note, the session configuration with multiple personalities needs to be done with AN configured with HRPD Rev A. c. d. e. f. Cause the AT to acquire AN 1. Setup an HRPD AT originated call. Verify that the AT connection is idle and the PPP session is dormant. Force the AT to handoff from AN 1 to AN 2. Ensure the AN 1 sends an AttributeUpdateRequest with the SessionConfigurationToken instructing the AT to switch to the personality for the HRPD Rev A network. Verify the AT sends an AttributeUpdateAccept to the AN 1 and begins using the HRPD Rev A personality. After the AT has successfully acquired AN 2, issue a ping from AT. Verify the AT successfully establishes an HRPD connection and call on AN 2, RNC 2 using the Rev A personality.

g. h. i.

1418.38.5 Minimum Standard 15The AT shall comply with steps g and i. 1618.39 Inter RNC Active Hand-off (Rev 0 to Rev A) 1718.39.1 Definition 18This test verifies the Inter-RNC active handoff is successful. AN 1 and AN 2 have a different 19RNC. AN 1 supports HRPD Rev A and AN 2 support HRPD Rev 0. RNC 1 and RNC 2 have an 20A13 link established.

2118.39.2 Traceability
22(see [24]) 23 24 25 26 27 29 30

8.2 8.2.6.1.2 8.4 8.4.6.1.6 8.6 3.7.1

Default Air Link Management Protocol Initialization State Default Idle State Protocol Connection Setup State Default Connected State Protocol PCF-PCF Dormant Handoff with Successful Retrieval of HRPD Session Information

28(see [26])

3118.39.3 Call Flow Example(s)

32None 3318.39.4 Method of measurement 34 35 36 37 38

a.

Connect the AT to AN 1 and AN 2 as shown in Figure A-5. 1. AN 1 supports HRPD Rev A and AN 2 supports HRPD Rev 0 and have different frequency assignments. Each RNC is broadcasting a different subnet. There is an A13 link between each RNC. 2. AN 1 and AN 2 have different RNC connections.

61

1
1 2 3 4 5 6 7 8 9 10 11

3GPP2 C.S0044-A v1.0 b. Configure the hybrid AT for mobile IP mode and during session configuration negotiate one personality defined for HRPD Rev A and one personality defined for HRPD Rev 0. Note, the session configuration with multiple personalities needs to be done with AN configured with HRPD Rev A. Cause the AT to acquire AN 2. Set up an HRPD AT originated call. Initiate a forward data transfer using the maximum supported data rate to the AT (i.e. use the FTP get command from the AT) Force the AT to handoff from AN 2 to AN 1. Verify the AT successfully acquires AN 1, RNC 1, and the file transfer is completed. (Note: The AT will continue to use the HRPD Rev 0 personality to transfer the file until the HRPD session is re-negotiated.)

c. d. e. f.

1218.39.5 Minimum Standard 13The AT shall comply with step f. 1418.40 Inter-Band Active Hand-off 1518.40.1 Definition 16This test verifies that the AT is able to successful acquire a new AN with a different frequency in 17different Band assignment during an active call. The AT will receive a new 18TrafficChannelAssignment message with the target frequency information. Since there is no hard 19handoff mechanism in HRPD, using the new TrafficChannelAssignment allows for faster 20acquisition of AN 2.

2118.40.2 Traceability
22(see [24]) 23 24 25 26 27

8.2 8.2.6.1.2 8.4 8.4.6.1.6 8.6

Default Air Link Management Protocol Initialization State Default Idle State Protocol Connection Setup State Default Connected State Protocol

62

13GPP2 C.S0044-A v1.0 118.40.3 Call Flow Example(s)

AT
a b c d e f
Route Update* Route Update

Sector s25

Sector Sector s16

Reset Report*

Traffic Channel Assignment corresponding to configured target carrier sectors

Reverse Pilot + DRC

Traffic Channel Complete

2
4 5 6 7 8 9 10 11 12

*This step is conditional , this may or , may not take place in the message exchange sequence, based on the trigggers generated by mobility

318.40.4 Method of measurement

a.

Connect the AT to AN 1 (Band 1) and AN 2 (Band 2) as shown in Figure A-5. 1. AN 1 and AN 2 have different frequency assignments. 2. AN 1 and AN 2 have the same RNC connections.

b. c. d. e. f.

Cause the AT to acquire AN 1. Setup an HRPD AT originated call. Initiate a forward data transfer to the AT. Trigger a hard handoff from AN 1 to AN 2 by sending a TrafficChannelAssignment with the target information for AN 2. Verify the AT tunes to the new frequency and the file transfer completes successfully. The delay between losing AN 1 and acquiring AN 2 should be less than 500ms.

1318.40.5 Minimum Standard 14The AT shall comply with step e and should comply with step f. 15The AN should comply with step f.

63

1
118.41 RLP Activation 218.41.1 Definition

3GPP2 C.S0044-A v1.0

3This test verifies the ability of the AN to activate RLP flows during session negotiation 4and later associate these active RLP flows to requested QoS. In the test, it is assumed 5that the AN will be able to accept the reservation requests generated by the AT. Note 6that each of the reservation requests may have multiple ProfileIDs and it is possible 7for the AN to accept any one or none of these Profiles. Typically, the AN should 8accept ATs most preferred profile, unless it is not able to support this profile due to 9resource constraints or other reasons. 10This test requires the ability to generate QoS requests from the AT, allocate QoS 11resources at the AN and install traffic filtering at the PDSN. The application that 12causes the AT to generate QoS requests could either reside at the AT or the TE. 13Further, it should be ensured that the application is able to connect with the 14server/peer and receive and transmit data. This may require password authentication 15when using commercial applications residing on the AT.

1618.41.2 Traceability
17(see [24]) 18

Chapter 4

Multiflow Packet Application

19(see [12])

20

Chapters 2 and 3

2118.41.3 Call Flow Example(s)

22None 2318.41.4 Method of measurement 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41

a. b. c.

Connect the AT to the AN as shown in Figure A-3. Cause the AT to acquire the AN. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2 and Subtype 3 RTC MAC. Configure the AN to activate MaxActivatedRLPFlowsFwd Forward Link Flows and MaxActivatedRLPFlowsRev Reverse Link Flows during session configuration. If the AT has an established session with the AN, cause the AN to close the session by transmitting a SessionClose message. Power cycle the AT. Ensure that the AT establishes a session with the AN and acquires the HRPD system. Verify that the AN activates MaxActivatedRLPFlowsFwd Forward Link Flows and MaxActivatedRLPFlowsRev Reverse Link Flows during session configuration. Cause the AT to establish a data call with the AN. Allow the AT to go idle. Trigger a QoS request by starting any application that requires reservation for at least one forward and one reverse link flow. An example of such an application would be video telephony.

d. e. f. g. h. i. j. k.

64

13GPP2 C.S0044-A v1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27

l.

Verify that during the subsequent signaling the AN does not transmit AttributeUpdateRequest messages containing FlowNNIdentificationFwd/FlowNNIdentificationRev attributes for any flow. Verify that if the AN did not negotiate FlowNNReservationFwd and FlowNNReservationRev attributes during session negotiation, then the AN transmits AttributeUpdateRequest messages(s) containing FlowNNReservationFwd attributes binding ReservationLabel(s) to Forward Link RLP flow(s) NN and FlowNNReservationRev attributes binding ReservationLabel(s) to Reverse Link flow(s). Verify that if the AN transmits AttributeUpdateRequest messages(s) containing FlowNNReservationFwd and FlowNNReservationRev attributes, then the AT transmits AttributeUpdateAccept message to the AN accepting the FlowNNReservationFwd and FlowNNReservationRev attributes. Verify that if the AN did not negotiate AssociatedFlowNN attribute during session negotiation, then the AN transmits AttributeUpdateRequest message containing AssociatedFlowNN attribute binding the RLP flow(s) to the RTCMAC flow(s). Verify that if the AN transmits AttributeUpdateRequest messages(s) containing AssociatedFlowNN attribute, then the AT transmits AttributeUpdateAccept message(s) to the AN accepting the binding sent by the AN in AssociatedFlowsNN attribute. Start data transfer for each of the forward and reverse link higher layer flows that are bound to an RLP flow through FlowNNReservationFwd and FlowNNReservationRev attributes. Verify that the AT uses Flow NN to transmit data for higher layer flow with ReservationLabel KK if the ReservationLabel KK was mapped to Flow NN through FlowNNReservationRev attribute. Verify that the AN uses Flow NN to transmit data for higher layer flow with ReservationLabel KK if the ReservationLabel KK was mapped to Flow NN through FlowNNReservationFwd attribute.

m.

n.

o.

p.

q.

r.

s.

2818.41.5 Minimum Standard

29The AT shall comply with steps n, p and r. 30The AN shall comply with steps h, l, m, o and s.
3118.42 QoS Set Up 3218.42.1 Definition

33This test verifies the ability of the AN and the AT to set-up and use QoS for any 34application. The application may reside at the AT or the TE (Terminal Equipment). 35Specifically, for setting up the QoS for the application, this test verifies that the QoS 36request and response, reservation to RLP binding, RLP to RTCMAC flow binding on the 37reverse link, RLP and RTCMAC flow activation, and opening the reservations. This test 38also verifies the GAUP messages needed to update various attributes and 39parameters. Note for this test each of the reservation requests may have multiple 40ProfileIDs and it is possible for the AN to accept any one or none of the Profiles. 41Typically, the AN should accept ATs most preferred profile, unless it is not able to 42support this profile due to resource constraints or other reasons. Unless otherwise 43specified, this test assumes that the AN will be able to accept any of the proposed 44profiles. 45It is assumed that the application needs one or more higher layer flows that are 46identified by their ReservationLabels. Each higher layer flow is bound to an RLP. More 47than one flow may be bound to an RLP. On the reverse link, the RLP ids are in turn

65

3GPP2 C.S0044-A v1.0

1bound to 1 or more MAC Flows. For example a Video Telephony application may 2require three separate higher layer flows (reservations) for audio, video and SIP 3signaling. The application may be designed to map audio and video higher layer 4flows to separate RLPs (due to different abort timer requirements for audio and 5video, for example), but transmit SIP flows data through the default RLP that is 6typically used for best effort traffic. On the reverse link RLP ids used by audio and 7video may be mapped to different MAC flows that are configured to provide different 8latencies, for example.

918.42.2 Traceability
10(see [24]) 11

Chapter 4

Multi-Flow Packet Application

12(see [12])

13

Chapters 2 and 3

14(see [10])

1518.42.3 Call Flow Example(s)

16None 1718.42.4 Method of measurement 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42

a. b. c.

Connect the AT to the AN as shown in Figure A-3. If the application resides on the TE connect the TE to the AT. Cause the AT to acquire the AN. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2 and Subtype 3 RTC MAC. Configure the AN to activate only the default RLP flow during session configuration. This can be done by setting the active parameter of the FlowNNIdentificationFwd and FlowNNIdentificationRev attribute to 0 for all RLP flows with NN 0. Ensure that the AN activates only the default RLP flow during session configuration. If the AT has an established session with the AN, cause either the AT or the AN to close the session by transmitting a SessionClose message. Cause the AT to negotiate a new session with the AN. Cause the AT to establish a data call with the AN and allow the AT to go idle. Cause the AT to start the application that needs to be tested. The application will generate QoS requests for all forward and reverse link flow(s). Verify that the AT transmits GAUP message(s) with ReservationKKQoSReqFwd with R_QoS_SUB_BLOB containing the specified Profile ID for forward flow(s) and ReservationKKQoSReqRev with R_QoS_SUB_BLOB containing the specified Profile ID for reverse flow(s). Verify that the AT constructs a Traffic Flow Template (TFT) with the desired packet filters and sends an RSVP Resv [Create new TFT] message. Verify that the AN transmits AttributeUpdateAccept message(s) accepting the QoS ReservationKKQoSRequestFwd/ ReservationKKQoSRequestRev attributes from the AT.

d.

e. f. g. h. i. j.

k. l.

66

13GPP2 C.S0044-A v1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41

m.

The AN should GAUP the ReservationKKQoSResponseFwd with G_QoS_BLOB containing the set ID for primary Profile ID for all the higher layer flow(s) of the application. Verify that the PDSN installs the desired packet filters and sends an RSVP ResvConf message. Verify that the AT transmits AttributeUpdate message(s) to the AN accepting the ANs ReservationKKQosResponseFwd and ReservationKKQosResponseRev for the ReservationLabel(s). Verify that the AN transmits a GAUP message for FlowNNIdentificationFwd and FlowNNIdentificationRev in order to activate the forward and reverse link flow(s). Verify that the AT transmits AttributeUpdateAccept message(s) accepting FlowNNIdentificationFwd and FlowNNIdentificationRev attributes. Verify that the AN transmits a GAUP message for FlowNNReservationFwd and FlowNNReservationRev for binding the reservations to RLP flow(s). Verify that the AT transmits AttributeUpdateAccept message(s) accepting FlowNNReservationFwd and FlowNNReservationRev values. The AN will determine the number of Forward and Reverse Link RLP flows and RTCMAC flows needed to support the accepted QoS requests. The AN may need to transmit AttributeUpdateRequest message(s) negotiating the parameters for Forward and Reverse link and RLP flows and RTCMAC flows. If the AN transmits Attribute Update Request for the Forward and Reverse Link RLP Flows and/or RTCMAC flows, verify that the AT transmits AttributeUpdateAccept message(s) accepting RLP and RTCMAC parameters. Verify that the AN transmits AttributeUpdateRequest message containing AssociatedFlowNN with substream field set to 1 to bind the RLP flow(s) to the RTCMAC flow(s). Verify that the AT transmits AttributeUpdateAccept message(s) to the AN accepting the binding sent by the AN in AssociatedFlowsNN attribute. The AN should GAUP RTCMAC BucketLevelMaxNN with a nonzero value to activate the RTCMAC flow(s). Verify that the AT transmits AttributeUpdateAccept message to the AN accepting the BucketLevelMaxNN value sent by the AN. Verify that the AT sends ReservationOnRequest for both the forward and reverse ReservationLabel(s) using single ReservationOnRequest message. Verify that AN sends ReservationAccept for both forward and reverse reservations. Verify that both the forward and reverse RLP flows are activated and all the reservations are in Open state. Once the application starts data transfer, verify that data is being sent on the appropriate RLP IDs on the forward link and on the appropriate RLP and MAC Flows on the reverse link. Ensure that the PDSN is sending data via the intended filter.

n. o.

p. q. r. s. t.

u.

v.

w. x. y. z. aa. bb. cc.

dd.

4218.42.5 Minimum Standard

43The AT shall comply with steps j, k, o, q, s, u, w, y, z, bb, and cc. 44The AN shall comply with steps l, p, r, v, aa, bb, and cc. 45The AN should comply with steps m and x.

67

1
1The PDSN should comply with steps n and dd.
218.43 Successful negotiation of Enhanced Idle State Protocol 318.43.1 Definition

3GPP2 C.S0044-A v1.0

4This test verifies negotiation and successful setup of the Enhanced Idle State Protocol.

518.43.2 Traceability
6(see [24])

7 8
9

8.4.7 8.5 8.5.7.1

Configuration Attributes Enhanced Idle State Protocol Simple Attributes

1018.43.3 Call Flow Example(s)

11None 1218.43.4 Method of measurement 13 14 15 16 17 18

a. b. c. d.

Connect the AT to the AN as shown in Figure A-3. Ensure that the AT does not have a previously assigned UATI from the AN. Configure the AN and AT to support Enhanced Idle State Protocol. Power on the AT. During HRPD session negotiation, verify the AT sends a ConfigurationRequest message that includes the following values: Field Protocol Type Value 0x0c (Idle State Protocol) Protocol Subtype 0x0001 (Enhanced Idle State)

19 20

e.

Ensure the AN responds with a ConfigurationResponse message including the following: Field Protocol Type Value 0x0c (Idle State Protocol) Protocol Subtype 0x0001 (Enhanced Idle State)

21 22

f.

If the AT supports hybrid mode operation and hybrid mode is enabled, verify the AT sends a second ConfigurationRequest that includes the following: Field Value

68

13GPP2 C.S0044-A v1.0

AttributeID PreferredControlChannelCycleEnabled PreferredControlChannelCycle

1

0x00 (PreferredControlChannelCycle) 0x1 Value

Field AttributeID= 0xff (SmallSlotCycleAllowed)

2 3 4 5 6 7

Value 0

g. h. i. j. k.

Ensure the AN accepts the proposed configuration. Set up an AT originated HRPD Rev A call and allow the data session to go dormant. Verify the AT is operating in slotted mode with a 5.12 second interval. Issue a ping to the AT. Verify the AT responds to the HRPD page request successfully.

818.43.5 Minimum Standard 9The AT shall comply with steps d, f, i, and k. 1018.44 Unsuccessful Enhanced Idle State Protocol due to AN rejection 1118.44.1 Definition 12This test verifies the AT falls back to the default idle protocol if the Enhanced Idle State Protocol 13is rejected by the AN.

1418.44.2 Traceability
15(see [24])

16 17 188.5.7.1

8.4.7 8.5

Configuration Attributes Enhanced Idle State Protocol Simple Attributes

1918.44.3 Call Flow Example(s)

20None 2118.44.4 Method of measurement 22 23 24 25

a. b.

Connect the AT to the AN as shown in Figure A-3. Ensure that the AT does not have a previously assigned UATI from the AN. Configure the AT to support Enhanced Idle State Protocol. Configure the AN to not support Enhanced Idle State Protocol.

69

1
1 2 3

3GPP2 C.S0044-A v1.0 c. d. Power on the AT. During HRPD session negotiation, verify the AT sends a ConfigurationRequest message that includes the following values Field Protocol Type Value 0x0c (Idle State Protocol) Protocol Subtype 0x0001 (Enhanced Idle State)

4 5 6 7 8 9 10 11

e. f. g. h. i. j.

Ensure the AN rejects the request and sends a ConfigurationResponse with an empty attribute. Verify AT and AN negotiate and successfully setup the HRPD session with the default idle state protocol. Set up an AT originated HRPD Rev A call and allow the data session to go dormant. Verify the AT is operating in slotted mode with a 5.12 second interval. Issue a ping to the AT. Verify the AT responds to the HRPD page request successfully.

1218.44.5 Minimum Standard 13The AT shall comply with steps d, f, h and j. 1418.45 SlottedMode Attribute Negotiation for Enhanced Idle State Protocol

1518.45.1 Definition
16This test verifies negotiation and successful setup of the Enhanced Idle State Protocol and 17negotiation of the SlottedMode attribute.

1818.45.2 Traceability 19(see [24]) 20 21

22

8.4.7 8.5

Configuration Attributes Enhanced Idle State Protocol

8.5.7.1 Simple Attributes

2318.45.3 Call Flow Example(s)

24None

2518.45.4 Method of measurement 26 27 28 29 2

a. b. Connect the mobile station to the base station as shown in Figure A-3. Ensure that the AT does not have a previously assigned UATI from the AN. Configure the AN and AT to support Enhanced Idle State Protocol. Configure the AN to propose the SlottedMode attribute.

70

13GPP2 C.S0044-A v1.0 1 2 3 4

Field Protocol Type Value 0x0c (Idle State Protocol) Protocol Subtype 0x0001 (Enhanced Idle State) c. d. Power on the AT. During HRPD session negotiation, verify the AT sends a ConfigurationRequest message that includes the following values:

5 6 7 8 9
Field Protocol Type Value 0x0c (Idle State Protocol) Protocol Subtype 0x0001 (Enhanced Idle State) e. Ensure the AN responds with a ConfigurationResponse message including the following:

10 11 12
Field AttributeID SlotCycle1 SlotCycle2 SlotCycle3 WakeCount1 WakeCount2 Value 0x01 (SlottedMode) 0x6 0x6 0x6 0 (default) 0 (default) f. Verify the AN sends a ConfigurationRequest that includes the following:

13 2

g.

Verify the AT accepts the configuration proposed by the AN.

71

1 1 2 3 4 5 6
h. i. j. k.

3GPP2 C.S0044-A v1.0 Set up an AT originated HRPD Rev A call and allow the data session to go dormant. Wait 60 seconds from the time the data session goes dormant and send an HRPD page to the AT (i.e. Issue a ping request to the AT from the network). Verify the AT responds to the HRPD page request successfully. Repeat steps b through j making the following changes to the ConfigurationRequest message sent in step f: Field AttributeID SlotCycle1 SlotCycle2 SlotCycle3 WakeCount1 WakeCount2 Value 0x01 (SlottedMode) 0x6 0x6 0x9 1 2

7 8 9 10 11 12 13 14 15

l. m.

Set up an AT originated HRPD Rev A call. Send a ping from the AT to the AN. Wait for the AT to go dormant. After the AT goes dormant, during T12 measure the interval of time that the AT wakes up and looks for pages. Verify this time interval is every control channel cycle (426.66 ms), since SlotCycle1= 0x6. Allow the AT to remain dormant. Wait for T23 to expire. Then measure the interval of time that the AT wakes up and looks for pages. Verify this time interval is every 12 control channel cycles (5120 ms), since SlotCycle3= 0x9. Send an HRPD page to the AT (ie. Issue a ping request from the AN to the AT). Verify that the AT responds to the HRPD page request successfully.

n.

o.

1618.45.5 Minimum Standard

17The AT shall comply with steps g, j, m, n, and o. 1818.46 Channel Hashing during Enhanced Idle State Protocol Evenly Distributed Hashing

1918.46.1 Definition
20This test verifies the mobile station hashes to the correct channels based on 21AccessHashingClassMask and AccessHashingChannelMask.

2218.46.2 Traceability 23(see [24]) 24 25 2

8.4.7 8.5 Configuration Attributes Enhanced Idle State Protocol

72

13GPP2 C.S0044-A v1.0 1 2

8.5.6.1.6.1.1 8.9.6.2.2 CDMA Channel Selection SectorParameters Message

318.46.3 Call Flow Example(s)

4None

518.46.4 Method of measurement 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

a. b. c. d. Connect the AT to the AN as shown in Figure A-5. AN 1 and AN 2 are AT supported CDMA Channels operating in the same band class and have same PN offset. Ensure that the AT does not have a previously assigned UATI from the AN. Configure the AT and each AN to support Enhanced Idle State Protocol. Configure each AN to send a SectorParameters Message with AccessHashingMaskLength=0xf and to negotiate a value of 0x0 for AccessHashingClassMask attribute during session negotiation. Configure both AN 1 and AN 2 to include in the SectorParameters Message a Channel List with the channel information for AN 1 with AccessHashingChannelMask=0xffff. Configure both AN 1 and AN 2 to include in the SectorParameters Message an Extended Channel List with the channel information for AN 2 with AccessHashingChannelMask=0xffff. Power on the AT and set up an HRPD data call. Allow the call to go dormant and ping the AT. Verify the AT responds to the page successfully. End the call and terminate the HRPD session. Repeat steps g through j 3 times. Verify the mobile station hashes evenly between AN 1 and AN 2.

e. f.

g. h. i. j. k. l.

2418.46.5 Minimum Standard

25The AT shall comply with steps i and l. 2618.47 Channel Hashing during Enhanced Idle State Protocol - Hashing to AN 2 Only

2718.47.1 Definition
28This test verifies the mobile station hashes to the correct channels based on 29AccessHashingClassMask and AccessHashingChannelMask. In this test, the AT will only hash to 30AN 2 based on settings for AccessHashingClassMask and AccessHashingChannelMask.

3118.47.2 Traceability 32(see [24]) 33

8.4.7 Configuration Attributes

73

1 1 2 3
8.5 8.5.6.1.6.1.1 8.9.6.2.2 Enhanced Idle State Protocol CDMA Channel Selection SectorParameters Message

3GPP2 C.S0044-A v1.0

418.47.3 Call Flow Example(s)

5None

618.47.4 Method of measurement 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27

a. b. c. d. Connect the AT to the AN as shown in Figure A-5. AN 1 and AN 2 are AT supported CDMA Channels operating in the same band class and have the same PN offset. Ensure that the AT does not have a previously assigned UATI from the AN. Configure the AT and each AN to support Enhanced Idle State Protocol. Configure each AN to send a SectorParameters Message with AccessHashingMaskLength=0x1 and to negotiate a value of 0x2 for AccessHashingClassMask attribute during session negotiation. Configure both AN 1 and AN 2 to include in the SectorParameters Message a Channel List with the channel information for AN 1 with AccessHashingChannelMask=0x1. Configure both AN 1 and AN 2 to include in the SectorParameters Message an Extended Channel List with the channel information for AN 2 with AccessHashingChannelMask=0x2. Power on the AT and set up an HRPD data call. Allow the call to go dormant and ping the AT. Verify the AT responds to the page successfully. End the call and terminate the HRPD session. Repeat steps g through j 3 times. Verify the mobile station hashes to only AN 2. Verify the mobile station does not hash to AN 1 after the EISP has been negotiated. (The AT may initially acquire AN 1, but shall not hash to AN 1 after receiving the AccessHashingClassMask and AccessHashingMaskLength.)

e. f.

g. h. i. j. k. l.

2818.47.5 Minimum Standard

29The AT shall comply with steps i and l. 3018.48 QoS Signaling upon PPP resynchronization 3118.48.1 Definition 32This test verifies that upon PPP resynchronization the AT transmits a new RSVP RESV message 33and that the PDSN installs the new filter based on the new RESV message

74

13GPP2 C.S0044-A v1.0 118.48.2 Traceability

2(see [24]) 3

Chapter 4

Multi-Flow Packet Application

4(see [12])

Chapters 2 and 3

6(see [10])

718.48.3 Call Flow Example(s)

8None 918.48.4 Method of measurement 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

a. b. c.

Connect the AT to the AN as shown in Figure A-3. Cause the AT to acquire the AN. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2 and Subtype 3 RTC MAC. Configure the AN to grant the QoS request from the AT. If the AT has an established session with the AN, cause the AN to close the session by transmitting a SessionClose message. Cause the AT to negotiate a new session with the AN. Ensure that the AN activates only the default RLP flow during session configuration. Cause the AT to establish a data call with the AN and allow the AT to go idle. Cause the AT to generate QoS requests for two forward and two reverse link flows. Wait for the AN to transmit a ReservationAccept message for all the reservations. Start data transfer and verify that all reservations are in open state and that the data is being transmitted using appropriate RLP flow IDs. Cause the PDSN to initiate a PPP resynchronization. This can be achieved for example by an inter-PDSN handoff. Ensure that the PDSN provides the same IP Address as received in step h. Verify that the AT resynchronizes the PPP. Verify that the AT transmits a RSVP RESV message with all the higher layer flows to the PDSN after PPP resynchronization is complete. Ensure that the PDSN sends a RSVP ResvConf message.

d. e. f. g. h. i. j. k.

l. m. n.

3218.48.5 Minimum Standard

33The AT shall comply with step l and m. 34The PDSN should comply with step n.
3518.49 AT behavior upon Rejection of Reservation Request by AN 3618.49.1 Definition

37The default flow in HRPD is always in active state. When the AN rejects a QoS 38request, the data for the QoS flow should be sent through the default RLP flow on the 39forward and reverse link and will receive best-effort treatment.

75

3GPP2 C.S0044-A v1.0

1Under normal circumstances, the AN will accept a reservation request from the AT. 2However, the AN may deny the reservation request for many reasons, for example if 3the request is invalid or if the given admission control policy at the AN determines 4that the request cannot be fulfilled. Specifying a configuration where the AN denies 5the QoS request is beyond the scope of the document and is left to the tester.

618.49.2 Traceability
7(see [24]) 8

Chapter 4

Multi-Flow Packet Application

9(see [12])

10

Chapters 2 and 3

1118.49.3 Call Flow Example(s)

12None. 1318.49.4 Method of measurement 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

a. b. c.

Connect the AT to the AN as shown in Figure A-3. Cause the AT to acquire the AN. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2 and Subtype 3 RTC MAC. If the AT has an established session with the AN, cause the AN to close the session by transmitting a SessionClose message. Cause the AT to negotiate a new session with the AN. Ensure that the AN activates only the default RLP flow during session configuration. Cause the AT to establish a data call with the AN. Cause the AT to generate QoS request for one forward and reverse link flow. Cause the AN to reject GAUP AttributeUpdateRequest message for ReservationKKQoSRequestFwd and ReservationKKQoSRequestRev. Start bi-directional data transfer with parameters that match the specification of the QoS request. Verify that the data can be sent and received on the default RLP flow and receives best-effort treatment.

d. e. f. g. h. i. j. k.

3118.49.5 Minimum Standard

32The AT shall comply with step k. 33The AN shall comply with step k.
3418.50 AT behavior upon Receiving ProfileType set to NULL 3518.50.1 Definition

36When the AN accepts a QoS request but sends a QoS response with ProfileType field 37set to NULL, the data for the QoS flow should be sent through the default RLP flow on 38the forward and reverse link and will receive best-effort treatment.

76

13GPP2 C.S0044-A v1.0 118.50.2 Traceability

2(see [24]) 3

Chapter 4

Multi-Flow Packet Application

4(see [12])

Chapters 2 and 3

618.50.3 Call Flow Example(s)

7None 818.50.4 Method of measurement 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

a. b. c.

Connect the AT to the AN as shown in Figure A-3. Cause the AT to acquire the AN. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2, Enhanced FTCMAC and Subtype 3 RTC MAC. If the AT has an established session with the AN, cause the AN to close the session by transmitting a SessionClose message. Cause the AT to negotiate a new session with the AN. Ensure that the AN activates only the default RLP flow during session configuration. Cause the AT to establish a data call with the AN. While the AT has a connection with the AN, cause the AT to generate QoS request for one forward and one reverse link flow. Cause the AN to accept the GAUP AttributeUpdateRequest message for ReservationKKQoSRequestFwd and ReservationKKQoSRequestRev. Cause the AN to transmit a ReservationKKQoSResponse with ProfileType set to 0x00 for both the forward and reverse link flows. Start bi-directional data transfer with parameters that match the specification of the QoS request. Verify that the data is sent and received on the default RLP flow and receives besteffort treatment.

d. e. f. g. h. i. j. k. l.

3018.50.5 Minimum Standard

31The AT shall comply with step k. 32The AN shall comply with step k.
3318.51 ReservationKKIdleStateFwd and ReservationKKIdleStateRev set to 0 3418.51.1 Definition

35The state of a reservation can change when the AT goes dormant. The change in a 36reservations state is determined by the value of ReservationKKIdleStateFwd / 37ReservationKKIdleStateRev where KK (=0xij) is the 2 digit hexadecimal 38ReservationLabel (0xij 0xff) that identifies the reservation in use. A Reservation is 39bound to an RLP flow NN by setting the ReservationLabel parameter of the 40FlowNNReservationFwd / FlowNNReservationRev attribute to the reservations label

77

3GPP2 C.S0044-A v1.0

1(KK = 0xij). When the ReservationKKIdleStateFwd / ReservationKKIdleStateRev (KK = 20xij) attribute is set to 0, the state of the reservation (with ReservationLabel KK = 30xij) will not change upon closing or opening of the connection. In the test procedure, 4application refers to an application that generates data for flow with 5ReservationLabel (KK = 0xij). Starting this application will cause the AT to transmit 6forward and reverse QoS ReservationOn request(s) for ReservationLabel (KK = 0xij) if 7the reservation is in closed state. Any higher layer flow with ReservationLabel 0xij 8(0xij 0xff) that generates forward and reverse reservation requests can be used. 9This test verifies that the reservation state does not change when 10ReservationKKIdleState is set to 0 and that the initial state of a reservation is closed 11(0xij 0xff). The test procedure transitions the state of the (connection state, 12reservation state) pair from (close, close), to (open, close), to (open, open), to (close, 13open) and finally to (open, open) again.

1418.51.2 Traceability
15(see [24]) 16

Chapter 4

Multi-Flow Packet Application

17(see [12])

18

Chapters 2 and 3

1918.51.3 Call Flow Example(s)

20None 2118.51.4 Method of measurement 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43

a. b. c.

Connect the AT to the AN as shown in Figure A-3. Cause the AT to acquire the AN. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2, Enhanced FTCMAC, and Subtype 3 RTC MAC. Configure the AN to grant the QoS request from the AT and to set ReservationKKIdleStateFwd and ReservationKKIdleStateRev to 0x0 for ReservationLabel KK (= 0xij 0xff). If the AT has an established session with the AN, cause the AN to close the session by transmitting a SessionClose message. Cause the AT to negotiate a new session with the AN. Cause the AT to establish a data call with the AN by transmitting data for higher layer flow with ReservationLabel 0xff (Note. This will open the connection by transmitting data on the default flow). While the AT has a connection with the AN, start the application that generates data for higher layer flow with ReservationLabel KK (= 0xij 0xff). Verify that the reservation is in closed state and the AT transmits forward and reverse ReservationOn request for the higher layer flows with ReservationLabel KK (= 0xij 0xff). Wait for the AN to transmit ReservationAccept message for all the reservations. Once the data transfer starts from the application, ensure that the reservation is in open state and that the data is being transmitted using appropriate (non-default) RLP flow ID.

d.

e. f. g.

h. i.

j.

78

13GPP2 C.S0044-A v1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

k. l. m. n.

Cause the AT to loose the connection with the AN. Ensure that the AT does not transmit ReservationOff request for the ReservationLabel KK (= 0xij 0xff) to the AN. Cause the AT to reestablish a data call with the AN. Start bi-directional data transfer for the higher layer flow with ReservationLabel KK (= 0xij 0xff). Verify that the reservation is in open state and that during or after reestablishing the data call, the AT does not need to transmit the ReservationOn request for ReservationLabel KK (= 0xij 0xff) and that the AN does not transmit FwdReservationOn and/or RevReservationOn message(s). Verify that the AN and the AT transmit the data through RLP with appropriate (nondefault) flow id. Stop the application and cause the AT to transmit a ReservationOff message for the forward and/or reverse higher layer flows with ReservationLabel KK (= 0xij 0xff). Allow the AT to go dormant. Cause the AT to establish a data call with the AN by transmitting data for higher layer flow with ReservationLabel 0xff. Start the application. Verify that the reservation is in closed state and the AT transmits the ReservationOn request for opening the reservation for forward and reverse link flow with ReservationLabel KK (= 0xij 0xff). Note, the AT may send a combined ReservationOn request for the forward link and reverse link reservations. Wait for the AN to accept the reservation(s). Verify that the AN and the AT transmit the data through RLP with appropriate (nondefault) flow id

o. p. q. r. s. t.

u.

2518.51.5 Minimum Standard

26The AT shall comply with step i, n, o, t and u. 27The AN shall comply with steps n, o and u.
2818.52 ReservationKKIdleState set to 1 2918.52.1 Definition

30The state of a reservation can change when the AT goes dormant. The change in a 31reservations state is determined by the value of ReservationKKIdleStateFwd / 32ReservationKKIdleStateRev where KK (=0xij) is the 2 digit hexadecimal 33ReservationLabel (0xij 0xff) that identifies the reservation in use. A Reservation is 34bound to an RLP flow NN by setting the ReservationLabel parameter of the 35FlowNNReservationFwd / FlowNNReservationRev attribute to the reservations label 36(KK = 0xij). When the ReservationKKIdleStateFwd / ReservationKKIdleStateRev (KK = 370xij) attribute is set to 0x1, the reservation will close when the HRPD connection is 38closed. This test verifies the change in a reservations state when 39ReservationKKIdleState is set to 1. In the test procedure, application refers to an 40application that generates data for higher layer flow with ReservationLabel KK (= 0xij 41 0xff). Starting this application will cause the AT to transmit forward and reverse 42QoS reservation requests for ReservationLabel KK (= 0xij 0xff) if the reservation is in 43closed state. Any ReservationLabel KK other that 0xff that generates forward and 44reverse reservation requests can be used.

79

1 118.52.2 Traceability
2(see [24]) 3

3GPP2 C.S0044-A v1.0

Chapter 4

Multi-Flow Packet Application

4(see [12])

Chapters 2 and 3

618.52.3 Call Flow Example(s)

7None 818.52.4 Method of measurement 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38

a. b. c.

Connect the AT to the AN as shown in Figure A-3. Cause the AT to acquire the AN. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2, Enhanced FTCMAC and Subtype 3 RTC MAC. Configure the AN to grant the QoS request from the AT and to set ReservationKKIdleStateFwd and ReservationKKIdleStateRev to 0x01 for ReservationLabel KK (= 0xij 0xff). If the AT has an established session with the AN, cause the AN to close the session by transmitting a SessionClose message. Cause the AT to negotiate a new session with the AN. Cause the AT to establish a data call with the AN by transmitting data for higher layer flow with ReservationLabel 0xff. Start the application and verify that the AT transmits reservation requests for forward and reverse link higher layer flows with ReservationLabel KK (= 0xij 0xff). Wait for the AN to transmit ReservationAccept message for all the reservations. Start the application and ensure that the reservation is in open state and that the data is being transmitted using appropriate (non-default) RLP flow ID. Cause the AT to loose the connection with the AN. Ensure that the AT does not transmit ReservationOff requests (forward or reverse) for ReservationLabel KK (= 0xij 0xff) to the AN. Cause the AT to reestablish a data call with the AN. Ensure that the application generates data for the higher layer flow with ReservationLabel KK (= 0xij 0xff). Verify that the reservation is in closed state and the AT transmits the ReservationOn request for the higher layer flows with ReservationLabel KK (= 0xij 0xff) for forward and reverse link flows. Wait for the AN to accept the reservation. Verify that the AN and the AT transmit the data through RLP with appropriate (nondefault) flow id.

d.

e. f. g. h.

i. j.

k. l. m.

n.

3918.52.5 Minimum Standard

40The AT shall comply with steps h, m and n. 41The AN shall comply with step n.

80

13GPP2 C.S0044-A v1.0

118.53 ReservationKKIdleState set to 2 218.53.1 Definition

3The state of a reservation can change when the AT goes dormant. The change in a 4reservations state is determined by the value of ReservationKKIdleStateFwd / 5ReservationKKIdleStateRev where KK (=0xij) is the 2 digit hexadecimal 6ReservationLabel (0xij 0xff) that identifies the reservation in use. A Reservation is 7bound to an RLP flow NN by setting the ReservationLabel parameter of the 8FlowNNReservationFwd / FlowNNReservationRev attribute to the reservations label 9(KK = 0xij). When the ReservationKKIdleStateFwd / ReservationKKIdleStateRev (KK = 100xij) attribute is set to 0x2, the reservation will open when the HRPD connection is 11opened and close when the HRPD connection is closed. This test verifies the change 12in state of the reservation (with ReservationLabel KK = 0xij 0xff) with opening and 13closing of connection when ReservationKKIdleState is set to 0x2. In the test 14procedure, application refers to an application that generates data for higher layer 15flow with ReservationLabel KK (= 0xij 0xff). Starting this application will cause the 16AT to transmit forward and reverse QoS ReservationOn requests for ReservationLabel 17KK (= 0xij 0xff) if the reservation is in closed state. Any ReservationLabel KK other 18that 0xff that requires forward and reverse reservations can be used

1918.53.2 Traceability
20(see [24]) 21

Chapter 4

Multi-Flow Packet Application

22(see [12])

23

Chapters 2 and 3

2418.53.3 Call Flow Example(s)

25None 2618.53.4 Method of measurement 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43

a. b. c.

Connect the AT to the AN as shown in Figure A-3. Cause the AT to acquire the AN. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2 Enhanced FTCMAC and Subtype 3 RTC MAC. Configure the AN to grant the QoS request from the AT and to set ReservationKKIdleStateFwd and ReservationKKIdleStateRev to 0x0 for ReservationLabel KK (= 0xij 0xff) and FlowNNDataOverSignalingAllowedRev and FlowNNDataOverSignalingAllowedFwd set to 1 for the RLP flow NN to which ReservationLabel KK (= 0xij 0xff) will be bound. Configure the AN to activate MaxActivatedRLPFlowsFwd and MaxActivatedRLPFlowsRev during session configuration. If the AT has an established session with the AN, cause the AN to close the session by transmitting a SessionClose message. Cause the AT to negotiate a new session with the AN. Cause the AT to establish a data call with the AN.

d.

e. f. g. h.

81

1
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38

3GPP2 C.S0044-A v1.0 i. Start the application and ensure that the AT transmits reservation requests for forward and reverse link higher layer flows with ReservationLabel KK (= 0xij 0xff). Wait for the AN to transmit ReservationAccept message for all the reservations. Start data transfer and verify that the reservation is in open state and that the data is being transmitted using appropriate (non-default) RLP flow ID. Stop the data transfer and allow the AT to become dormant and ensure that the AT does not transmit ReservationOffRequest messages for the ReservationLabel KK (= 0xij 0xff). Cause the AT to generate a DataOverSignaling message for the higher layer flow with ReservationLabel KK (= 0xij 0xff). Ensure that the AT does not open the connection with the AN. Ensure that the reservation is in open state and the AT does not need to transmit the ReservationOn request for the reservation and that the AN does not transmit FwdReservationOn and/or RevReservationOn message(s). Ensure that the AT transmits the DataOverSignaling message. Transmit a DataOverSignaling message from the AN to the AT for the higher layer flow with ReservationLabel KK (= 0xij 0xff). Ensure that the AT does not open the connection with the AN. Ensure that the reservation is in open state and the AT does not need to transmit the ReservationOn request for the reservation and that the AN does not transmit FwdReservationOn and/or RevReservationOn message(s). Ensure that the AN transmits the DataOverSignaling message. Repeat steps d to h with the exception that in step d, configure the AN to set ReservationKKIdleStateFwd and ReservationKKIdleStateRev to 0x2. Cause the AT to establish a data call with the AN by transmitting data for higher layer flow with ReservationLabel 0xff. Generate data from the application. Verify that the AT does not need to transmit the ReservationOn request for the reservation and that the AN does not transmit FwdReservationOn and/or RevReservationOn message(s) and that the AN and the AT transmit applications data through appropriate (non-default) RLP. Force the AT to become idle. Cause the AT to generate a DataOverSignaling message for the higher layer flow with ReservationLabel KK (= 0xij 0xff). Verify that the AT does not transmit DataOverSignaling message. Cause the AN to generate a DataOverSignaling message for the higher layer flow with ReservationLabel KK (= 0xij 0xff). Verify that the AN does not transmit DataOverSignaling message.

j. k.

l.

m.

n. o.

p.

q. r. s. t. u.

v. w. x. y. z.

3918.53.5 Minimum Standard

40The AT shall comply with step u and x. 41The AN shall comply with steps u and z.

82

13GPP2 C.S0044-A v1.0

118.54 DRC Supervision Failure

218.54.1 Definition
3The AT performs DRC supervision in order to ensure call quality. This test verifies that 4the AT behavior for DRC supervision. Specifically, it verifies that if the AT transmits 5NULL DRC for DRCSupervisionTimer*10 + 240 ms. continuously without receiving any 6packets (either FTC or CC MAC packets) from the AN then it shall disable the Reverse 7Traffic Channel. Subsequently, the AT starts a timer for TFTCMPRestartTx (5.12 seconds). If 8during this period, a packet (either FTC or CC MAC packets) is received from the AN 9or if the AT transmits a non-NULL tentative DRC, then the AT disables the timer. 10Otherwise it declares a DRC supervision failure and tears down the connection.

1118.54.2 Traceability
12(see [24])

13

Section 10.7.6.1.10.1

14(see [12])

15

Chapters 2 and 3

1618.54.3 Call Flow Example(s)

17None 1818.54.4 Method of measurement 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42

a. b. c.

Connect the AT to the AN as shown in Figure A-1. Cause the AT to acquire the AN. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2, Enhanced CCMAC Enhanced FTCMAC and Subtype 3 RTC MAC. Configure the AN to use a transmission rate of 38.4 kbps for the control channel. During SCP or using GAUP, negotiate the value of MultiUserPacketsEnabled to be 0x00. This will disallow the AN from transmitting data to the AT, when the AT is transmitting NULL rate DRC. Cause the AT to establish a connection with the AN. Start bi-directional data transfer and ensure that data is going through continuously in both directions. Reduce or such that the AT starts transmitting NULL rate tentative DRC and is unable to receive the control channel. Verify that the AT disables the Reverse Traffic Channel after transmitting null rate tentative DRC for DRCSupervisionTimer*10 + 240 ms period continuously. Ensure that the AN does not transmit any packets on the forward traffic channel to the AT and the AT does not receive any control channel packet during this time interval. Within TFTCMPRestartTx (5.12 seconds) of disabling reverse traffic channel transmitter in the last step, increase or such that the AT start transmitting a non-null tentative DRC to the AN. Ensure that the AN does not transmit any packets on the forward traffic channel to the AT and the AT does not receive any control channel packet before AT has transmitted non-null DRC for NFTCMPRestartTx slots continuously.

d. e.

f. g. h. i.

j.

83

1
1 2 3 4

3GPP2 C.S0044-A v1.0 k. l. m. Verify that the AT enables the reverse traffic channel and bi-directional transfer occurs after AT has transmitted non-null DRC for NFTCMPRestartTx slots continuously. Reduce or such that the AT starts transmitting NULL rate tentative DRCs and is unable to receive the control channel. Verify that the AT returns a DRC supervision failure indication and tears down the connection at the expiration of TFTCMPRestartTx. Note, the AT will transmit a null rate tentative DRC for a period of DRCSupervisionTimer*10 + 240 ms before starting the TFTCMPRestartTx timer.

5 6 7 8

918.54.5 Minimum Standard

10The AT shall comply with steps i, k, m. 11The AN shall comply with steps k.
1218.55 Soft Handoff during DRC Supervision Timeout State

1318.55.1 Definition
14This test verifies the soft handoff during DRC supervision timeout state.

1518.55.2 Traceability
16(see [24])

17

Section 10.7.6.1.10.1

18(see [12])

19

Chapters 2 and 3

2018.55.3 Call Flow Example(s)

21None 2218.55.4 Method of measurement 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38

a. b. c.

Connect the AT to the AN as shown in Figure A-10. Cause the AT to acquire the AN 1. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2, Enhanced CCMAC, Enhanced FTCMAC and Subtype 3 RTC MAC. During SCP or using GAUP, negotiate the value of MultiUserPacketsEnabled to be 0x00. This will disallow the AN from transmitting data to the AT, when the AT is transmitting NULL rate DRC. Cause the AT to establish a connection with the AN 1. Start bi-directional data transfer and ensure that data is going through continuously in both directions. Reduce or for the pilot from AN 1 such that the AT starts transmitting NULL rate tentative DRC and is unable to receive the control channel from AN 1. Ensure that the AT disables the Reverse Traffic Channel after transmitting null rate tentative DRC for DRCSupervisionTimer*10 + 240 ms period continuously.

d.

e. f. g. h.

84

13GPP2 C.S0044-A v1.0

1 2 3 4 5

i.

Within TFTCMPRestartTx (5.12 seconds) of disabling reverse traffic channel transmitter in the last step, increase the Ior of sector 1 of AN 2 or increase or such that the AT transmits non-null tentative DRC for NFTCMPRestartTx slots continuously to AN 2. Verify that the AT successfully acquires AN 2, enables the reverse traffic channel and that the bi-directional transfer resumes from the AT and AN 2.

j.

618.55.5 Minimum Standard

7The AT shall comply with step j 8The AN shall comply with step j.
918.56 DRC Supervision with MultiUserPacketsEnabled

1018.56.1 Definition
11This test verifies the AN and AT behavior when the value of MultiUserPacketsEnabled 12is set to 0x01. This test requires that the AN transmit data to an AT even when the AT 13transmits a NULL DRC. This will happen for Flows that require QoS, such as a VOIP 14flow if the MultiUserPacketsEnabled is set 0x01. It is assumed that such a flow is used in this 15test.

1618.56.2 Traceability
17(see [24])

18 19

Section 10.7.6.1.10.1 and Section 10.6.7.1

20(see [12])

21

Chapters 2 and 3

2218.56.3 Call Flow Example(s)

23None 2418.56.4 Method of measurement 25 26 27 28 29 30 31 32 33 34 35 36 37 38

a. b. c.

Connect the AT to the AN as shown in Figure A-1. Cause the AT to acquire the AN 1. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2 Enhanced FTCMAC and Subtype 3 RTC MAC. During SCP or using GAUP, negotiate the value of DRCSupervisionTimer to 0x00 and the value of MultiUserPacketsEnabled to be 0x01. This will allow the AN to transmit data to the AT, when the AT is transmitting NULL rate DRC. Cause the AT to establish a connection with the AN. Start bi-directional data transfer and ensure that data is going through continuously in both directions. Reduce or such that the AT starts transmitting NULL rate tentative DRC. Verify that the AN continues to transmit data to the AT at DRC 1 rate.

d.

e. f. g. h.

85

1
1 2 3

3GPP2 C.S0044-A v1.0 i. Verify that the AT does not disable the Reverse Traffic Channel after transmitting null rate tentative DRC for DRCSupervisionTimer*10 + 240 ms period continuously if it receives either a forward traffic channel or control channel packet. If the AT does not receive any forward traffic channel or control channel packet in the last step, the repeat the test by increasing the or.

4 5

j.

618.56.5 Minimum Standard

7The AT shall comply with step i 8The AN shall comply with step h.
918.57 DRCTranslationOffset Verification

1018.57.1 Definition
11This test verifies DRCTranslationOffset attribute negotiation between the AT and the AN.

1218.57.2 Traceability
13(see [24])

14

Section 10.7.6.1.10.1

1518.57.3 Call Flow Example(s)

16None

1718.57.4 Method of measurement.

18
19 20 21 22 23 24 25 26 27 28 29

a. b. c. d. e. f. g. h. i. j.

Connect the AT to the AN as shown in Figure A-3. Cause the AT to acquire the AN. Configure the AT to negotiate the use of Physical layer subtype 2 and Enhanced FTCMAC. During SCP or using GAUP, negotiate the value of DRCTranslationOffset attribute with a value 0 for DRCOffsetN for all N. Cause the AT to establish a connection with the AN. Cause the AT to request a tentative DRC value of 0x8. This can either be done by fixing the DRC requested by the AT or by changing the or. Ensure that the AT is transmitting a DRC value 0x08 most of the time. GAUP the value of DRCTranslationOffset attribute with a value of 5 for DRCOffset8 and 0 for all other DRCOffsetN. Start bi-directional data transfer and ensure that data is going through continuously in both directions. Verify that the AT requests a DRC of 3, when its tentative DRC is 0x8

30 31

32

3318.57.5 Minimum Standard

34The AT shall comply with step j.

86

13GPP2 C.S0044-A v1.0

118.58 DSC and DRC compliance during Soft handoff

218.58.1 Definition
3The purpose of this test is to verify that the AT follows the DSC channel and DRC channel 4timeline in transmitting the DSC and DRC values while performing a soft handoff with DRCGating 5disabled. Further, it is tested that the AN does not skip transmission of any octets from the RLP 6sequence space during soft handoff. In the test procedure, both AN 1 and AN 2 support HRPD 7Rev A and are connected to the same RNC. It is intended that this test be executed with the 8default hybrid mode operation, if supported by the AT.

918.58.2 Traceability
10(see [24])

11 12

Section 10.7.6.1.5 and Section 10.7.6.1.8.1

13(see [12])

14

Chapters 2 and 3

1518.58.3 Call Flow Example(s)

16None 1718.58.4 Method of measurement 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40

a.

Connect the AT to AN 1 and AN 2 as shown in Figure A-5. 1. AN 1 and AN 2 support HRPD Rev A and have same frequency assignments. 2. AN 1 and AN 2 are connected to the same RNC, but are located at separate base stations.

b. c.

Cause the AT to acquire the AN 1. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2, Enhanced CCMAC, Enhanced ACMAC, Enhanced FTCMAC, Enhanced Idle State Protocol and Subtype 3 RTC MAC. During SCP negotiate the value of DSCLength to 8 (64 slots), SoftHandoffDelay to 8 (64 slots) and DRCGating to 0x00 (continuous transmission). Cause the AT to establish a connection with the AN 1. Initiate a forward data transfer using the maximum supported data rate to the AT (i.e. use the FTP get command from the AT). Choose a file large enough to sustain data for entire test duration. Force the AT to handoff from AN 1 to AN 2. Force the AT to handoff from AN 2 to AN 1. Verify that the AT does not change its sector cover such that there is overlap in transmission of packets from 2 sectors. Verify that after a handoff occurs from AN 1 to AN 2, the RLP sequence number of the first byte transmitted by AN 2 is less than or equal to the 1+ RLP sequence of the last byte transmitted by the AN 1. Similarly, verify contiguous RLP sequence numbers for handoff from AN 2 to AN 1.

d. e. f.

g. h. i. j.

87

1
1 2

3GPP2 C.S0044-A v1.0 k. Verify that the call is maintained across the handoff and that the file transfer is completed.

318.58.5 Minimum Standard

4The AT shall comply with steps i and k. 5The AN shall comply with the steps j and k.
618.59 DRC Compliance During Softer Handoff

718.59.1 Definition
8The purpose of this test is to verify that the AN and the AT behavior during softer 9handoff. It is verified that the AT transmits the correct value of DRC and the AN 10transmits the data correctly. In the test procedure, both AN 1 and AN 2 support HRPD 11Rev A and are adjacent sectors located at the same base station. It is intended that 12this test be executed with the default hybrid mode operation, if supported by the AT.

1318.59.2 Traceability
14(see [24])

15

Section 10.7.6.1.10.1

16(see [12])

17

Chapters 2 and 3

1818.59.3 Call Flow Example(s)

19None 2018.59.4 Method of measurement 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38

a.

Connect the AT to AN 1 and AN 2 as shown in Figure A-5. 1. AN 1 and AN 2 support HRPD Rev A and have the same frequency assignments. 2. AN 1 and AN 2 are connected to the same RNC, and are located at the same base stations but have different PN offsets.

b. c.

Cause the AT to acquire the AN 1. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2, Enhanced CCMAC, Enhanced ACMAC, Enhanced FTCMAC, Enhanced Idle State Protocol and Subtype 3 RTC MAC. During SCP negotiate the value of DRCLength to 8 slots, SofterHandoffDelay to 8 slots and DRCGating to 0x00 (continuous transmission). Cause the AT to establish a connection with the AN 1. Initiate a forward data transfer using the maximum supported data rate to the AT (i.e. use the FTP get command from the AT). Choose a file large enough to sustain data for entire test duration. Force the AT to handoff from AN 1 to AN 2. Force the AT to handoff from AN 2 to AN 1.

d. e. f.

g. h.

88

13GPP2 C.S0044-A v1.0

1 2 3 4 5 6 7

i. j.

Verify that the AT does not change its sector cover such that there is overlap in transmission of packets from the 2 sectors. Verify that after a handoff occurs from AN 1 to AN 2, the AN transmits contiguous RLP sequence, i.e. the RLP sequence number of the first byte transmitted by AN 2 is one more than the RLP sequence of the last byte transmitted by the AN 1. Similarly, verify contiguous RLP sequence numbers for handoff from AN 2 to AN 1. Verify that the call is maintained across handoff and that the file transfer is completed.

k.

818.59.5 Minimum Standard

9The AT shall comply with steps i and k. 10The AN shall comply with steps j and k.
1118.60 MUP and Non Canonical SUP decoding by AT

1218.60.1 Definition
13The purpose of this test is to verify that the AT can decode multi-user packets (MUP) and non14canonical single user packet (SUP) that the AN transmits.

1518.60.2 Traceability
16(see [24])

17

Section 10.7.6.1.5

18(see [12])

19

Chapters 2 and 3

2018.60.3 Call Flow Example(s)

21None 2218.60.4 Method of measurement 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39

a. b. c.

Connect the AT to the AN as shown in Figure A-3. Cause the AT to acquire the AN. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2, Enhanced CCMAC, Enhanced FTCMAC and Subtype 3 RTC MAC. During session configuration or using GAUP negotiate the value of ShortPacketsEnabledThresh to 0x03, and MultiUserPacketsEnabled to 0x00. Cause the AT to establish a connection with the AN. Vary the channel conditions such that the AT transmits a close to peak rate DRC value of 0xe. Instruct the AN to GAUP DRCTranslationOffset attribute with parameter DRCOffsetE set to 0xa, DRCOffsetd set to 0xa, DRCOffsetc set to 0xa, DRCOffsetb set to 0xa, DRCOffseta set to 0xa and DRCOffseti for all other DRC i, set to 0. Ensure that the AT starts transmitting DRC values in the range 0x0 to 0x4. Cause the AN to transmit one or more single user packets to the AT in any format other than the canonical format. The transmission packet format used by the AN is

d. e. f. g.

h. i.

89

1
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

3GPP2 C.S0044-A v1.0 implementation dependent. Canonical format for a DRC is the largest packet size. If the payload of a transmission can fit in a smaller size packet allowed for the DRC, the AN may transmit a smaller (non-canonical) format. For example, if a ping packet with 10 bytes of payload is transmitted to the AT, it will be transmitted using a (512, 2, 128) format if the transmitted DRC is 0x4, or (512, 4, 256) format if the transmitted DRC is 0x3. This assumes that the ping packet will not fit in a 256 bit packet but will fit in a 512 bit physical layer packet. j. k. Verify that the AT successfully decodes all single user packets transmitted by the AN. Repeat step i for all DRC in the range 0x0 to 0x4. Note the DRC transmitted by the AT can be varied either by varying or or by increasing the DRCOffsetE parameter of the DRCTranslationOffset by using GAUP. Using GAUP negotiate the value of ShortPacketsEnabledThresh to 0x00, and MultiUserPacketsEnabled to 0x01. Cause the AN to transmit one or more multi user packets allowed for the transmitted DRC. Repeat step m for all DRC in the range 0x0 to 0x4. Note the DRC transmitted by the AT can be varied either by varying Ior or by increasing the DRCOffsetE parameter of the DRCTranslationOffset by using GAUP. Verify that the AT successfully decodes all multi user packets transmitted by the AN.

l. m. n.

o.

2018.60.5 Minimum Standard

21The AT shall comply with steps j and o.

2218.61 Enhanced Control Channel Short MAC Packet

2318.61.1 Definition
24The purpose of this test is to verify that the AT successfully decodes various short packet formats 25with different negotiated values of CCShortPacketMACIndex. This test requires the AN to 26transmit CC short MAC packets. Since the size of the ACAck and Page packet is smaller than 27512 bits, it is likely although not necessary that the AN will use CC short MAC packets for 28transmitting these messages.

2918.61.2 Traceability
30(see [24])

31

Section 10.3.6.1.4.1.1

32(see [12])

33

Chapters 2 and 3

3418.61.3 Call Flow Example(s)

35None 3618.61.4 Method of measurement 37 38 39 40

a. b. c.

Connect the AT to the AN as shown in Figure A-3. Cause the AT to acquire the AN. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the

90

13GPP2 C.S0044-A v1.0

1 2 3 4 5

service network, Physical layer subtype 2, Enhanced CCMAC, Enhanced ACMAC, Enhanced FTCMAC, Enhanced Idle State Protocol and Subtype 3 RTC MAC. d. e. Start a new session and using SCP negotiate the value of CCShortPacketsMACIndex attribute to 0x00. Using SCP or GAUP negotiate the value of SlottedMode attribute as follows: Field AttributeID SlotCycle1 SlotCycle2 SlotCycle3 WakeCount1 WakeCount2 Value 0x01 (SlottedMode) 0x5 0x5 0x5 0 (default) 0 (default)

6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

f. g.

After session configuration is complete, instruct the AT to open a connection with the AN. Verify that in response to the ATs AccessProbe message, the AN transmits an ACAck message in a asynchronous CC capsule using one of the following Transmission Formats16 of [128, 4, 1024], [256, 4, 1024], [512, 4, 1024] with preamble MAC Index 71. If the message is transmitted using the sub-synchronous or synchronous capsule, repeat steps f and g. Verify that the AT receives the ACAck message and stops transmitting the AccessProbe. Allow the connection to become dormant. Instruct the AN to transmit a Page to the AT. Verify that the AN transmits the Page message in a sub-synchronous CC capsule using one of the following Transmission Formats of [128, 4, 1024], [256, 4, 1024], [512, 4, 1024] with a preamble MAC Index of 71. If the message is transmitted using the synchronous capsule, repeat steps i, j and k. Verify that the AT receives the Page message and establishes a connection with the AN. Instruct the AT or the AN to close the session. Start a new session and using SCP negotiate any valid value of CCShortPacketsMACIndex other than 0x00. Using SCP or GAUP negotiate the value of SlottedMode attribute as follows: Field AttributeID Value 0x01 (SlottedMode)

h. i. j. k.

l. m. n. o.

216 Transmission Format is defined as [ Payload Size (bits), Nominal transmit duration (slots),
3Preamble 4Length (chips))

91

3GPP2 C.S0044-A v1.0

SlotCycle1 SlotCycle2 SlotCycle3 WakeCount1 WakeCount2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

0x5 0x5 0x5 0 (default) 0 (default)

p. q.

After session configuration is complete, instruct the AT to open a connection with the AN. Verify that in response to the ATs AccessProbe message, the AN transmits an ACAck message in a asynchronous CC capsule using one of the following Transmission Formats of [128, 4, 1024], [256, 4, 1024], [512, 4, 1024] with preamble MAC Index negotiated in step n or 71. If the message is transmitted using the sub-synchronous or synchronous capsule, repeat steps o and p. Verify that the AT receives the ACAck message and stops transmitting the AccessProbe. Allow the connection to become dormant. Instruct the AN to transmit a Page to the AT. Verify that the AN transmits the Page message in a sub-synchronous CC capsule using one of the following Transmission Formats of [128, 4, 1024], [256, 4, 1024], [512, 4, 1024] with a preamble MAC Index negotiated in step n or 71. If the message is transmitted using the synchronous capsule, repeat steps i, j and k. Verify that the AT receives the Page message and establishes a connection with the AN

r. s. t. u.

v.

1818.61.5 Minimum Standard

19The AT shall comply with steps h, l, r, and v. 20The AN shall comply with steps g, k, q and u.
2118.62 Enhanced Access Channel Probe Transmission

2218.62.1 Definition
23The purpose of this test is to verify that the AN and the AT successfully negotiate the 24PreambleLengthSlots, AccessOffset, SectorMaxRate and CapsuleLengthMax attributes of the 25EACMAC protocol and that using these parameters the AT transmits the access probe at 26appropriate time and rate and that the AN successfully receives the probe. This test uses Data 27Over Signaling protocol to generate payload for the Access Channel Capsule.

2818.62.2 Traceability
29(see [24])

30 31

Section 10.5.6.1.4.1.2 (Probe Transmission) Section 10.5.6.2.6 (Access Parameters message)

92

13GPP2 C.S0044-A v1.0

1(see [12])

Chapters 2 and 3

318.62.3 Call Flow Example(s)

4None 518.62.4 Method of measurement 6

a. b. c.

Connect the AT to the AN as shown in Figure A-3. Cause the AT to acquire the AN. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2, Enhanced CCMAC, Enhanced ACMAC, Enhanced FTCMAC, Enhanced Idle State Protocol and Subtype 3 RTC MAC. During session configuration or using GAUP, negotiate a value of 0x00 (9.6 kbps) for TerminalAccessRateMax attribute of EACMAC protocol. Configure the AN to transmit CapsuleLengthMax value of 0x7, PreambleLenghtSlots value of 0 (4 slots), AccessOffset value of 03, and SectorAccessMaxRate value of 00 (9.6 kbps) in the AccessParameters message. During Session Configuration, set the ProtocolIdentifier field of the FlowNNHigherLayerProtocolRev (NN = KK) and FlowNNHigherLayerProtocolFwd (NN = KK) to HDLC framing. During Session Configuration, set the Active parameter of FlowNNIdentificationFwd (NN = KK) attribute and FlowNNIdentificationRev (NN = KK) attribute to 0x01. Set the ReservationLabel for FlowNNReservationRev (NN = KK) and FlowNNReservationFwd (NN = KK) to High Priority Signaling. Set FlowNNDataOverSignalingAllowedRev (NN = KK) and FlowNNDataOverSignalingAllowedFwd (NN = KK) to 0x01. Configure the AN to grant the QoS request from the AT and to set ReservationKKIdleStateFwd and ReservationKKIdleStateRev to 0x0 for ReservationLabel kk associated with High Priority Signaling. If the AT does not have an established PPP session, cause the AT to establish a PPP session. Instruct the AT to send a ReservationOn message for ReservationLabel kk associated with High Priority Signaling data that is to be carried using DataOverSignaling message to the AN and ensure that the AN responds with a ReservationAccept message. Instruct the AT to send a ReservationOn message for ReservationLabel kk associated with High Priority Signaling data that is to be carried using DataOverSignaling message from the AN to the AT and ensure that the AN responds with a ReservationAccept message. Allow the HRPD connection to become idle. Transmit a ping packet from the AT directed to the AN using the Data Over Signaling Protocol and setting the AckRequired field of the DataOverSignaling message to 1. The size of the ping packet should be such that the Access Channel payload is between 489 and 1000 bits. Verify that the AT transmits a DataOverSignaling Message at 9.6 kbps Access Channel Rate. Verify that the AT started the transmission of the AccessProbe at time T such that (T-AccessOffset) mod AccessCycleDuration = 0,

7
8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44

d. e.

f.

g. h.

i. j.

k. l.

m.

93

1
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

3GPP2 C.S0044-A v1.0 where T is CDMA System Time in slots and AccessCycleDuration is defined in the AccessParameters message transmitted by the AN. Verify that the AT transmits the Preamble for PreambleLengthSlots. n. o. Verify that the AN receives the DataOverSignaling Message. This can be verified by the transmission of DataOverSignalingAck by the AN. Repeat steps c to l, with the exception that TerminalAccessRateMax attribute value is negotiated to 0x02 (38.4 kbps) and the AN is configured to transmit AccessParameters message with an AccessOffset value of 02 (8 slots). Verify that the AT transmits the DataOverSignaling Message at 38.4 kbps over the Access Channel. Verify that the AT started the transmission of the AccessProbe at time T such that (T-AccessOffset) mod AccessCycleDuration = 0, where T is CDMA System Time in slots and AccessCycleDuration is defined in the AccessParameters message transmitted by the AN. Verify that the AT transmits the Preamble for PreambleLengthSlots. q. r. Verify that the AN receives the DataOverSignaling Message. This can be verified by the transmission of DataOverSignalingAck by the AN. Repeat steps c to l with the exception that the AN transmits the AccessParameters message with PreambleLenghtSlots value of 1 (16 slots), AccessOffset value of 01 (4 slots) and SectorAccessMaxRate value of 10 (38.4 kbps). Verify that the AT transmits the DataOverSignaling Message at 38.4 kbps over the Access Channel. Verify that the AT started the transmission of the AccessProbe at time T such that (T-AccessOffset) mod AccessCycleDuration = 0, where T is CDMA System Time in slots and AccessCycleDuration is defined in the AccessParameters message transmitted by the AN. Verify that the AT transmits the Preamble for PreambleLengthSlots. t. u. Verify that the AN receives the DataOverSignaling Message. This can be verified by the transmission of DataOverSignalingAck by the AN. Transmit a ping packet from the AT directed to the AN using the Data Over Signaling Protocol and setting the AckRequired field of the DataOverSignaling message to 1. The size of the ping packet should be such that the Access Channel payload is between 232 and 489 bits. Verify that the AT transmits a DataOverSignaling Message at 19.2 kbps over the Access Channel. Verify that the AN receives the DataOverSignaling Message. This can be verified by the transmission of DataOverSignalingAck by the AN.

p.

s.

v. w.

3818.62.5 Minimum Standard

39The AT shall comply with steps m, p, s and v. 40The AN shall comply with steps n, q, t and w.

94

13GPP2 C.S0044-A v1.0

118.63 RTC Interlace re-ordering with Subtype 3 RTCMAC

218.63.1 Definition
3When using Subtype 3 RTCMAC protocol, RTCMAC packets can arrive out of order at 4the AN. This can happen due to early termination of sub-packets on the reverse link 5interlaces.

618.63.2 Traceability
7(see [24])

Section 10.11

9(see [12])

10

Chapters 2 and 3

1118.63.3 Call Flow Example(s)

12None 1318.63.4 Method of measurement

14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41

a. Connect the AT to AN Figure A-5. b. Cause the AT to acquire the AN. c. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2, Enhanced FTCMAC and Subtype 3 RTC MAC. d. During session configuration or using GAUP, instruct the AN to negotiate a value of AbortTimer and FlushTimer parameters of the FlowNNTimersRev attribute to 0x0001 to 0x0005 for the best effort RLP flow. Set both AbortTimer and FlushTimer to the same value. e. After session configuration is complete, instruct the AT to open a connection with the AN. f. Using best effort RLP flow, transmit N (>= 10) ping packets with a payload between 400 to 600 bytes from the AT to the AN.

g. Verify that the AT successfully receives at least 80% of the response to the ping packet transmissions from the AN. h. Close the session. i. Start a new session. During session configuration or using GAUP, instruct the AN to negotiate the PermittedPayloadPS_k parameter of the PermittedPayload attribute to be set to 0x1 for all PS {0, 12288} and all k {1, 2, 3}.

j. Trigger N (>= 10) RouteUpdate messages from the AT to the AN. RouteUpdate messages can be triggered by changing the pilot strengths. Note, the signaling messages must be transmitted while the AT has an open connection with the AN. k. Verify that the AT receives a TrafficChannelAssignment message in response to at least 80% of the RouteUpdate messages transmitted by the AT.

95

1 118.63.5 Minimum Standard

2The AT should comply with steps g and k. 3The AN should comply with steps g and k.
418.64 Configuration of non-default attributes for Subtype 3 RTCMAC

3GPP2 C.S0044-A v1.0

518.64.1 Definition
6The purpose of this test is to verify that the AT and AN can negotiate non-default 7Sub-type 3 RTCMAC parameters.

818.64.2 Traceability
9(see [24])

10

Section 10.11

11(see [12])

12

Chapters 2 and 3

1318.64.3 Call Flow Example(s)

14None 1518.64.4 Method of measurement

16 17 18 19 20 21 22 23 24 25 26 27

a. Connect the AT to AN Figure A-5. b. Cause the AT to acquire the AN. c. Configure the AT to negotiate the use of Multi-Flow Packet Application or Enhanced Multi-Flow Packet Application or Multi-Link Multi-Flow Packet Application bound to the service network, Physical layer subtype 2, Enhanced FTCMAC and Subtype 3 RTC MAC. d. During session configuration or using GAUP, instruct the AN to negotiate the following attributes for Subtype 3 RTC MAC. The values specified in the table are recommended, but any other permissible value can be used. Ensure that the AN is configured to negotiate at least one attribute to a non default value. Simple Attributes

96

13GPP2 C.S0044-A v1.0

Attribute ARQMode FRABFilterTC FRABlow MergeThreshold PayloadThresh PilotStrengthFilterTC QRABFilterTC T2PNoTxFilterTC PilotStrengthQRABThresholdDRCLock PilotStrengthQRABThresholdDRCUnlock MaxNumMACFlows Rate1M8Supported
1
2

Value 0x00 0x02 0x03 0x02 0x01 0x02 0x00 0x03 0x18 0xc 0x05 0x01

Complex Attributes AuxiliaryPilotChannelParameters Parameter AuxiliaryPilotChannelGain AuxiliaryPilotChannelMinPayload Value 0xc 0x7

CommonPowerParameters Parameter AllocationStagger TxT2Pmin RPCStep Value 0000 0x1A 01

PilotStrength

97

1
Parameter NumPilotStrengthAxisValues PilotStrengthAxis0 PilotStrengthAxis1 PilotStrengthPilotStrengthAxis0 PilotStrengthPilotStrengthAxis1
1

3GPP2 C.S0044-A v1.0 Value 0x2 0x3c 0x00 0x0 0x0

RequestParameters Parameter ReqRatio MaxReqInterval Value 0x0 0x0

RRIChannelPowerParameters Parameter RRIChannelGainPreTransition0 RRIChannelGainPostTransition0 RRIChannelGainPreTransition1 RRIChannelGainPostTransition1 RRIChannelGainPreTransition2 RRIChannelGainPostTransition2 RRIChannelGainPreTransition3 Value 0x0 0xA 0x0 0xA 0xA 0xA 0xA

TxT2Pmax Parameter NumPilotStrengthAxisValues PilotStrengthAxis0 PilotStrengthAxis1 PilotStrengthAxis2 TxT2PmaxPilotStrengthAxis0 TxT2PmaxPilotStrengthAxis1 TxT2PmaxPilotStrengthAxis2 Value 0x3 0x1E 0x0E 0x06 0x18 0x28 0x36

PermittedPayload

98

13GPP2 C.S0044-A v1.0

Parameter PermittedPayload0_1 PermittedPayload0_2 PermittedPayload0_3 PermittedPayload128_1 PermittedPayload128_2 PermittedPayload128_3 PermittedPayload256_1 PermittedPayload256_2 PermittedPayload256_3 PermittedPayload512_1 PermittedPayload512_2 PermittedPayload512_3 PermittedPayload768_1 PermittedPayload768_2 PermittedPayload768_3 PermittedPayload1024_1 PermittedPayload1024_2 PermittedPayload1024_3 PermittedPayload1536_1 PermittedPayload1536_2 PermittedPayload1536_3 PermittedPayload2048_1 PermittedPayload2048_2 PermittedPayload2048_3 PermittedPayload3072_1 PermittedPayload3072_2 PermittedPayload3072_3 PermittedPayload4096_1 PermittedPayload4096_2 PermittedPayload4096_3 Value 0x9 0x9 0x7 0x9 0x9 0x7 0x9 0x9 0x7 0x9 0x9 0x7 0x9 0x9 0x7 0x9 0x9 0x7 0x9 0x9 0x7 0x9 0x9 0x9 0x9 0x9 0x9 0xb 0xb 0xb

99

1
PermittedPayload6144_1 PermittedPayload6144_2 PermittedPayload6144_3 PermittedPayload8192_1 PermittedPayload8192_2 PermittedPayload8192_3 PermittedPayload12288_1 PermittedPayload12288_2 PermittedPayload12288_3
1 2 3 4

3GPP2 C.S0044-A v1.0 0xb 0xb 0xb 0xc 0xc 0xc 0xc 0xc 0xc

For Power Parameters128 to PowerParameters12288: Values from Min HiCapTerminationTarget for HiCap and from Min LoLatTerminationTarget for LoLat PowerParameters128 Parameter LoLatT2PTransition128 LoLatTerminationTarget128 HiCapT2PTransition128 HiCapTerminationTarget128 T2PLoLatPreTransition128 T2PLoLatPostTransition128 T2PHiCapPreTransition128 T2PHiCapPostTransition128 Value 0x2 0x2 0x2 0x2 0x0D 0x03 0x0D 0x03

PowerParameters256

100

13GPP2 C.S0044-A v1.0

Parameter LoLatT2PTransition256 LoLatTerminationTarget256 HiCapT2PTransition256 HiCapTerminationTarget256 T2PLoLatPreTransition256 T2PLoLatPostTransition256 T2PHiCapPreTransition256 T2PHiCapPostTransition256
1

Value 0x2 0x2 0x2 0x2 0x1A 0x0F 0x1A 0x0F

PowerParameters512 Parameter LoLatT2PTransition512 LoLatTerminationTarget512 HiCapT2PTransition512 HiCapTerminationTarget512 T2PLoLatPreTransition512 T2PLoLatPostTransition512 T2PHiCapPreTransition512 T2PHiCapPostTransition512 Value 0x2 0x2 0x2 0x2 0x26 0x1C 0x26 0x1C

PowerParameters768 Parameter LoLatT2PTransition768 LoLatTerminationTarget768 HiCapT2PTransition768 HiCapTerminationTarget768 T2PLoLatPreTransition768 T2PLoLatPostTransition768 T2PHiCapPreTransition768 T2PHiCapPostTransition768 Value 0x2 0x2 0x2 0x2 0x2E 0x23 0x2E 0x23

PowerParameters1024

101

1
Parameter LoLatT2PTransition1024 LoLatTerminationTarget1024 HiCapT2PTransition1024 HiCapTerminationTarget1024 T2PLoLatPreTransition1024 T2PLoLatPostTransition1024 T2PHiCapPreTransition1024 T2PHiCapPostTransition1024
1

3GPP2 C.S0044-A v1.0 Value 0x2 0x2 0x2 0x2 0x30 0x28 0x30 0x28

PowerParameters1536 Parameter LoLatT2PTransition1536 LoLatTerminationTarget1536 HiCapT2PTransition1536 HiCapTerminationTarget1536 T2PLoLatPreTransition1536 T2PLoLatPostTransition1536 T2PHiCapPreTransition1536 T2PHiCapPostTransition1536 Value 0x2 0x2 0x3 0x3 0x38 0x30 0x30 0x30

PowerParameters2048 Parameter LoLatT2PTransition2048 LoLatTerminationTarget2048 HiCapT2PTransition2048 HiCapTerminationTarget2048 T2PLoLatPreTransition2048 T2PLoLatPostTransition2048 T2PHiCapPreTransition2048 T2PHiCapPostTransition2048 Value 0x2 0x2 0x3 0x3 0x3E 0x34 0x34 0x34

PowerParameters3072

102

13GPP2 C.S0044-A v1.0

Parameter LoLatT2PTransition3072 LoLatTerminationTarget3072 HiCapT2PTransition3072 HiCapTerminationTarget3072 T2PLoLatPreTransition3072 T2PLoLatPostTransition3072 T2PHiCapPreTransition3072 T2PHiCapPostTransition3072
1

Value 0x2 0x2 0x3 0x3 0x41 0x39 0x39 0x39

PowerParameters4096 Parameter LoLatT2PTransition4096 LoLatTerminationTarget4096 HiCapT2PTransition4096 HiCapTerminationTarget4096 T2PLoLatPreTransition4096 T2PLoLatPostTransition4096 T2PHiCapPreTransition4096 T2PHiCapPostTransition4096 Value 0x2 0x2 0x3 0x3 0x46 0x3E 0x3E 0x3E

PowerParameters6144 Parameter LoLatT2PTransition6144 LoLatTerminationTarget6144 HiCapT2PTransition6144 HiCapTerminationTarget6144 T2PLoLatPreTransition6144 T2PLoLatPostTransition6144 T2PHiCapPreTransition6144 T2PHiCapPostTransition6144 Value 0x2 0x2 0x3 0x3 0x4C 0x44 0x44 0x44

PowerParameters8192

103

1
Parameter LoLatT2PTransition8192 LoLatTerminationTarget8192 HiCapT2PTransition8192 HiCapTerminationTarget8192 T2PLoLatPreTransition8192 T2PLoLatPostTransition8192 T2PHiCapPreTransition8192 T2PHiCapPostTransition8192
1

3GPP2 C.S0044-A v1.0 Value 0x1 0x1 0x3 0x3 0x5D 0x4A 0x4A 0x4A

PowerParameters12288 Parameter LoLatT2PTransition12288 LoLatTerminationTarget12288 HiCapT2PTransition12288 HiCapTerminationTarget12288 T2PLoLatPreTransition12288 T2PLoLatPostTransition12288 T2PHiCapPreTransition12288 T2PHiCapPostTransition12288 Value 0x1 0x1 0x3 0x3 0x69 0x55 0x55 0x55

2 3 4 5 6 7

e. During session configuration or using GAUP, instruct the AN to negotiate the following attributes for two Subtype 3 RTC MAC flows NN (>0). The values for the attributes specified in the table are recommendations; any other permissible value can be used. Ensure that the AN is configured to negotiate at least one attribute to a non default value Simple Attributes

104

13GPP2 C.S0044-A v1.0

Parameter Value for Hi-Cap Flow BucketLevelMaxNN MergeThresholdNN TransmissionModeNN QRABSelectNN BurstDurationFactorNN T2PFilterTCNN
1 2

Value for Lo-Lat flow 0x66 0x00 0x01 0x00 0x00 0x01

0x6c 0x02 0x00 0x00 0x00 0x01

Complex Attributes BucketFactorNN Parameter Value for Hi-Cap Flow NumT2PAxisValues NumFRABAxisValues T2PAxis00 T2PAxis01 FRABAxis0 FRABAxis1 BucketFactorT2PAxis00FRABAxis0 BucketFactorT2PAxis00FRABAxis1 BucketFactorT2PAxis01FRABAxis0 BucketFactorT2PAxis01FRABAxis1 0x01 0x01 0x00 0x48 0x8 0xb 0x28 0x18 0x08 0x08 0x08 0x8 Value for Lo-Lat flow 0x0 0x0 0x00

T2PInflowRangeNN Parameter Value for Hi-Cap Flow T2PInflowmin T2PInflowmax 0x00 0x78 Value for Lo-Lat flow 0x0F 0x78

T2PTransitionFunctionNN

105

1
Parameter Value for Hi-Cap Flow NumT2PAxisValues NumFRABAxisValues T2PAxis00 T2PAxis01 T2PAxis02 T2PAxis03 FRABAxis0 FRABAxis1 FRABAxis2 FRABAxis3 FRABAxis4 T2PUpT2PAxis00FRABAxis0 T2PUpT2PAxis00FRABAxis1 T2PUpT2PAxis00FRABAxis2 T2PUpT2PAxis00FRABAxis3 T2PUpT2PAxis00FRABAxis4 T2PUpT2PAxis01FRABAxis0 T2PUpT2PAxis01FRABAxis1 T2PUpT2PAxis01FRABAxis2 T2PUpT2PAxis01FRABAxis3 T2PUpT2PAxis01FRABAxis4 T2PUpT2PAxis02FRABAxis0 T2PUpT2PAxis02FRABAxis1 T2PUpT2PAxis02FRABAxis2 T2PUpT2PAxis02FRABAxis3 T2PUpT2PAxis02FRABAxis4 T2PUpT2PAxis03FRABAxis0 T2PUpT2PAxis03FRABAxis1 T2PUpT2PAxis03FRABAxis2 0x03 0x04 0x00 0x24 0x48 0x5A 0x8 0xB 0xE 0x2 0x5 0x1D 0x0A 0xFE 0xFE 0xE0 0xFB 0xE8 0xDC 0xDC 0xDC 0xFD 0xEA 0xDE 0xDE 0xDE 0x18 0x05 0xF9

3GPP2 C.S0044-A v1.0 Value for Lo-Lat flow 0x02 0x00 0x00 0x34 0x35

0x1C

0x1C

0x88

106

13GPP2 C.S0044-A v1.0

T2PUpT2PAxis03FRABAxis3 T2PUpT2PAxis03FRABAxis4 0xF9 0xF9

T2PDnT2PAxis00FRABAxis0 T2PDnT2PAxis00FRABAxis1 T2PDnT2PAxis00FRABAxis2 T2PDnT2PAxis00FRABAxis3 T2PDnT2PAxis00FRABAxis4 T2PDnT2PAxis01FRABAxis0 T2PDnT2PAxis01FRABAxis1 T2PDnT2PAxis01FRABAxis2 T2PDnT2PAxis01FRABAxis3 T2PDnT2PAxis01FRABAxis4 T2PDnT2PAxis02FRABAxis0 T2PDnT2PAxis02FRABAxis1 T2PDnT2PAxis02FRABAxis2 T2PDnT2PAxis02FRABAxis3 T2PDnT2PAxis02FRABAxis4 T2PDnT2PAxis03FRABAxis0 T2PDnT2PAxis03FRABAxis1 T2PDnT2PAxis03FRABAxis2 T2PDnT2PAxis03FRABAxis3 T2PDnT2PAxis03FRABAxis4
1 2 3 4 5 6 7 8 9 10
11

0xE9 0xE2 0xD6 0xD6 0xD6 0xEA 0xE3 0xD7 0xD7 0xD7 0x06 0xFF 0xF3 0xF3 0xF3 0x2D 0x26 0x1A 0x1A 0x1A

0xB0

0xB0

0xB0

f.

Verify that the AN and AT successfully negotiate the non-default values for various attributes in step d and e either through ConfigRequest/ConfigResponse messages or through GAUP.

g. Start file upload using hi-cap MAC flow. h. Verify that for reverse traffic channel transmissions, the AN transmits HARQ, P-ARQ and L-ARQ bits correctly and that the AT is able to demodulate these. Verify that the PER on the reverse link is less than 1.25%. i. j. k. Allow the file transfer to complete. Stop data transfer using the hi-cap flow. Start data transfer using lo-lat flow.

107

1
1 2 3

3GPP2 C.S0044-A v1.0 l. Verify that the PER for the reverse link is less than 1.25% and that 99% of the packets terminate within LoLatTerminationTargetPS + 1 sub-packet transmissions for packet size PS.

418.64.5 Minimum Standard

5The AN and AT shall comply with step f.

6The AN and AT should comply with steps h, and l.

108

13GPP2 C.S0044-A v1.0 119 ANNEX A - FIGURES 2 3 4

Base Station or Access Network

Figure A -

Load

Mobile Station or Access Terminal

Tx

Channel Simulator

Attenuator

Rx (A) Attenuator Rx (B)

Antenna

7
8

1 1 2 3 4 5
Base Station 1 Load AWGN Source

3GPP2 C.S0044-A v1.0

Figure A -

Spectrum Analyzer

Mobile Station

Tx

Code Domain Analyzer Attenuator Channel Simulator

Rx (A) Attenuator Antenna

Rx (B) Attenuator DAT

Load Base Station 2 Code Domain Analyzer

Tx Channel Simulator Rx (A)

Attenuator

Rx (B)

DAT

7 8 9 10 11 12 13 14

13GPP2 C.S0044-A v1.0

1 2

3 4 5
Figure A -

Base Station or Access Network

Load

Code Domain Analyzer

Mobile Station or Access Terminal

Tx

Attenuator #1

Rx (A) Attenuator #2 Rx (B) Spectrum Analyzer

Antenna

1 1 2
BaseStation#1 Sector a

3GPP2 C.S0044-A v1.0

Figure A Load AWGN Source Spectrum Analyzer

MobileStation

T x

CodeDomain Analyzer Attenuator Attenuator

Rx (A) Antenna Rx (B) Attenuator

Load BaseStation#1 Sectorb CodeDomain Analyzer CodeDomain Analyzer Attenuator Attenuator Rx (A) BaseStation#2 Load T x

T x

Rx (A)

Rx (B)

Rx (B)

3
4 5

13GPP2 C.S0044-A v1.0 1

2
Base Station 1 or Access Network 1 Load Mobile Station or Access Terminal

Figure A -

Tx

Attenuator

Attenuator

Rx (A) Attenuator Rx (B)

Antenna

Base Station 2 or Access Network 2

Load

Tx

Attenuator

Rx (A)

Rx (B)

4 5 6 7 8 9 10 11 12 13 14 15 16 17

1
1 2

3GPP2 C.S0044-A v1.0

3
4

Figure A 6

Base Station

Load

Tx

Channel Simulator

Attenuator

Mobile Station MT2

Rx (A) Attenuator Rx (B)

Antenna

Rm

TE2

7 8
Figure A 7 Test Setup for RLP Abort in Forward Link

9
10 11 12 13 14 15 16

13GPP2 C.S0044-A v1.0

1 2

Figure A 8 Test Setup for RLP Abort in Reverse Link

3
4 5

1
1Figure A 9 2

3GPP2 C.S0044-A v1.0

3
4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

13GPP2 C.S0044-A v1.0

1Figure A 10

AN 1 Tx

Load Attenuator Channel Simulator

AT
Antenna

RX(A) RX(B)

Attenuator

AN 2 Tx

Load

RX(A) RX(B)

Channel Simulator

1
1No text.

3GPP2 C.S0044-A v1.0

10

13GPP2 C.S0044-A v1.0 120 ANNEX B 220.1 Annex B.1 Power Ratios for Common and Traffic Channels
3 4Annex B.1 provides the proper power ratios to perform a test when the power ratios are not 5specified in the test. The tables below specify power ratios for the Forward pilot channel, the 6Sync Channel, the Paging Channel, the Forward Common Control Channel, the Broadcast 7Control Channel, the Fundamental Channel, the Dedicated Control Channel, the Supplemental 8Code Channels and the Supplemental Channels. The traffic channel power ratios are specified 9to achieve at least 1% FER under AWGN channel conditions. Most channels can be configured 10for more than one data rate, code rate, or frame size. Not all default configurations are listed in 11this Annex. However, the power ratios listed in this Annex do provide the most conservative 12default ratios when only a subset of the values are listed for a particular channel, since the 13objective of these default ratios is to support signaling conformance tests and not minimum 14performance tests. All power ratios are valid for Band Classes 0 through 12. Whenever the 15power ratios are specified in the test, those power ratios should be used in lieu of power ratios 16provided in this Annex. 17 18Table B.1-1 Power Ratios for Common Channels

Parameter Pilot Ec Ior Sync Ec Ior Paging Ec Ior BCCH Ec Ior FCCCH Ec Ior Ioc

Units dB

Value -7

dB

-16

dB

-12 (9600 bps)

dB

-15.2 (9600bps, no TD)

dB dBm/1.23 MHz

-12.8 (19200 bps) -9.5 (38400 bps) -54

19
20Table B.1-2 Test Parameters for Forward Fundamental Channel (RC1, RC3 and RC4)

Parameter or I Ioc

Units dB

Value -1

1
FCH Ec (RC1) Ior FCH Ec (RC3) Ior FCH Ec (RC4) Ior Ioc Data Rate dB -15.6

3GPP2 C.S0044-A v1.0

dB

-16.2

dB dBm/1.23 MHz bps

-15.4

-54 9600

1
2Table B.1-3 Test Parameters for Forward Fundamental Channel (RC2 and RC5)

Parameter or I Ioc FCH Ec (RC2) Ior FCH Ec (RC5) Ior Ioc Data Rate

Units dB

Value -1

dB

-12.3

dB dBm/1.23 MHz bps

-13.8

-54 14400

3 4
5Table B.1-4 Test Parameters for Forward Dedicated Control Channel (RC3 and RC4)

Parameter or I Ioc FCH Ec (RC3) Ior FCH Ec (RC4) Ior Ioc

Units dB

Value -1

dB

-16.2

dB dBm/1.23 MHz

-15.4

-54

13GPP2 C.S0044-A v1.0

Data Rate bps 9600

1 2
3Table B.1-5 Test Parameters for Forward Dedicated Control Channel (RC5)

Parameter or I Ioc FCH Ec Ior Ioc Data Rate

Units dB

Value -1

dB dBm/1.23 MHz bps

-13.8

-54 14400

4 5
6Table B.1-6 Test Parameters for Forward Supplemental Code Channel (RC1)

Parameter or I Ioc SCCH Ec Ior FCH Ec Ior Ioc Data Rate

Units dB

Value -1

dB

-16.1

dB dBm/1.23 MHz bps

-12.0

-54 9600

7 8
9Table B.1-7 Test Parameters for Forward Supplemental Code Channel (RC2)

Parameter or I Ioc

Units dB

Value -1

1
SCCH Ec Ior FCH Ec Ior Ioc Data Rate dB -13.0

3GPP2 C.S0044-A v1.0

dB dBm/1.23 MHz bps

-12.0

-54 14400

1 2
3Table B.1-8 Test Parameters for Forward Supplemental Channel (RC3 and RC4)

Parameter or I Ioc SCH Ec (RC3) Ior SCH Ec (RC4) Ior FCH Ec Ior Ioc Data Rate

Units dB

Value -1

dB

-13.0

-9.7

-6.6

-3.2

dB

-12.6

-9.3

-6.0

-2.8

dB dBm/1.23 MHz bps

-7.0

-54 19200 38400 76800 153600

4 5
6Table B.1-9 Test Parameters for Forward Supplemental Channel (RC5)

Parameter or I Ioc SCH Ec Ior FCH Ec Ior

Units dB

Value -1

dB

-10.9

-7.9

-4.6

-1.4

dB

-7.0

13GPP2 C.S0044-A v1.0

Ioc Data Rate dBm/1.23 MHz bps -54 28800 57600 115200 230400

120.2 Annex B.2 CDMA Equations

2 3The following equations describe the relationship between various test parameters under different 4conditions. If the Paging Channel is not supported, the Forward Common Control Channel may 5be substituted.

620.2.1 B.2.1 Transmit Power of the Base Station 7

TD Pilot E c Sync E c QPCH E c FCCCH E c BCCH E c Paging E c Pilot E c + + + + + + I or I or I or Ior Ior Ior Ior CACH E c CPCCH E c FCH E c DCCH E c Power Control E c SCCH E c + + + + + + I or Ior Ior Ior Ior Ior

8+ 9
10

SCH E c OCNS E c + =1 I or Ior

11Using the 12 If 13 14

Ec values for the Pilot, Sync and Paging Channels in Table B.1-1, Ior

Dedicated E c = -16 dB at 9600 bps data rate, then Ior

Power Control E c = -26.41 dB I or OCNS E c = -1.64 dB I or Dedicated E c = -16 dB at 1200 bps data rate, then Ior

15Otherwise, if 16 17
18

Power Control E c = -17.38 dB I or OCNS E c = -1.75 dB I or

19 where Dedicated can represent FCH or DCCH. 20

2120.2.2 Annex B.2.2 Received Signal Strength for Mobile Station Not in Handoff
22

1
Pilot E c E I 1Pilot c = I or I0 oc + 1 I
or

3GPP2 C.S0044-A v1.0

2 3Single-Path Case

Common E c Common _ Chip _ Bit Ior Eb 4Common = Ioc Nt I

or

Dedicated E c Dedicated _ Chip _ Bit Ior Eb 5Dedicated = Ioc Nt I

or

7where Common can be applied to Sync Channel, QCPH, Paging Channel, BCCH, or FCCCH. 8Dedicated can be applied to FCH, DCCH, SCCH, or SCH.
9 10 11Two-Path Case 12According to Channel Simulator Configuration 1 and 2 (see 6.4.1.1), these two paths have the 13same average power.

1 Dedicated E c Eb I oc 1 14Dedicated = xDedicated_Chip_Bit x + Nt Ior I or 2

15

16where Dedicated can be applied to FCH, DCCH, SCCH, or SCH.

17 18Three-Path Case 19According to Channel Simulator Configuration 4 (see 6.4.1.1), the first two paths have the same 20average power and the third path has half the average power of the first one.

2 1 Dedicated E c Eb 5 5 21Dedicated = x Dedicated_Chip_Bit x(2 x I + I ) Nt Ior oc + 3 oc + 4 I or 5 I or 5

22 23where Dedicated can be applied to FCH, DCCH, SCCH, or SCH. 24 25

13GPP2 C.S0044-A v1.0 120.2.3 Annex B.2.3 Received Signal Strength for Mobile Station in Two-Way Handoff
2According to Channel Simulator Configuration 2 (see 6.4.1.1), which is used in the tests of the 3Forward Traffic Channel in two-way handoff, there are two paths from each cell and the power 4received from each cell is or.

E 5Pilot c (for each pilot) = I0

Pilot E c I or I oc +2 I
or

3 Dedicated E c Eb 2 6Dedicated = x Dedicated_Chip_Bit x I Nt Ior oc + 3 I or 2

7where Dedicated can be applied to FCH, DCCH, SCCH, or SCH. 8

9Generally, if the power received from cell 1 and cell 2 are or1 and Ior 2 , respectively, then I Pilot E c 1 I or Ec 10Pilot = I I oc or2 I0 1 + +1 I or1 or1 I
11

Pilot E c 2 Ior Ec 12Pilot = I0 2 Ioc I + or1 + 1 Ior 2 or 2 I

13 14 15 16 17 18 19 20 21 22 23 24

1 120.3 Annex B.3 Message Parameter Values

2

3GPP2 C.S0044-A v1.0

3 4
Field T_ADD T_DROP T_COMP T_TDROP

Extended Handoff Direction Message/General Handoff Direction Message/ Universal Handoff Direction Message Value (With Hard Handoff) 28 (-14 dB) 32 (-16 dB) 5 (2.5 dB) 3 (4 sec) 1 Value (Without Hard Handoff) 28 (-14 dB) 32 (-16 dB) 5 (2.5 dB) 3 (4 sec) N/A

HARD_INCLUDED (EHDM)/ EXTRA_PARMS (GHDM/UHDM) FRAME_OFFSET PRIVATE_LCM RESET_L2 RESET_FPC SERV_NEG_TYPE ENCRYPT_MODE NOM_PWR_EXT NOM_PWR NUM_PREAMBLE BAND_CLASS CDMA_FREQ PILOT_PN PWR_COMB_IND CODE_CHAN

0 0 1 1 1 0 0 0 0 (user specify) F2 user specify 0 1 to 63 (user specify)

N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

13GPP2 C.S0044-A v1.0 1

Field SID VMAC ANALOG_CHAN SCC MEM AN_CHAN_TYPE DSCC_MSB Analog Handoff Direction Message Value Use appropriate number for analog system. 3 Use appropriate analog channel of choice. Use one of three SAT Color Code (0, 1 or 2). 0 0 0

2 3
Field SRCH_WIN_A SRCH_WIN_N SRCH_WIN_R NGHBR_MAX_AGE PWR_THRESH_ENABLE PWR_PERIOD_ENABLE T_ADD T_DROP T_COMP T_TDROP QPCH_SUPPORTED System Parameters Message Value (Physical Meaning) 8 (60 chips) 8 (60 chips) 8 (60 chips) 0 (minimum amount) 0 (threshold reporting off) 0 (periodic reporting off) 28 (-14 dB Ec/Io) 32 (-16 dB Ec/Io) 5 (2.5 dB) 3 (4 sec) 0 (QPCH disabled)

4 5
Field SOFT_SLOPE RLGAIN_TRAFFIC_PILOT Extended System Parameters Message Value (Decimal) 0 (0) 0 (0 dB)

1 1
Field NOM_PWR INIT_PWR PWR_STEP NUM_STEP NOM_PWR_EXT Access Parameters Message Value (Decimal) 0 (0 dB) 0 (0 dB) 1 (1 dB) 4 (5 probes/sequence) 0 (0 dB)

3GPP2 C.S0044-A v1.0

2 3
Constant N1m N2m N3m N11m T1b T5m T31m T40m T56m T61m Values for Time Limits and Constants Value 9 12 2 1 1.28 5 600 3 0.2 0.08 Unit frames frames frames frame seconds seconds seconds seconds seconds seconds

10

13GPP2 C.S0044-A v1.0 121 ANNEX C - PROTOCOL CAPABILITY RESPONSE MESSAGE 2 FEATURE IDENTIFIERS

1
Features NAM Download (DATA_P_REV) Key Exchange (A_KEY_P_REV) FEATURE_ID 00000000 00000001 FEATURE_P_REV 00000010 00000010 00000011

3GPP2 C.S0044-A v1.0 FEATURE_P_REV Description NAM Download as specified in this document A key provisioning as specified in this document A key and 3G Root Key provisioning as specified in this document 3G Root Key provisioning as specified in this document System Selection for Preferred Roaming using Preferred Roaming List Reserved System Selection for Preferred Roaming using Extended Preferred Roaming List associated with SSPR_P_REV of 00000011 Service Programming Lock as specified in this document Over-The-Air Parameter Administration as specified in this document Preferred User Zone List as specified in this document 3G Packet Data as specified in this document Secure Mode as specified in this document

00000100 System Selection for Preferred Roaming (SSPR_P_REV) 00000010 00000001

00000010 00000011

Service Programming Lock (SPL_P_REV) Over-The-Air Parameter Administration (OTAPA_P_REV) Preferred User Zone List (PUZL_P_REV) 3G Packet Data (3GPD) Secure MODE SECURE_MODE_P_REV) Reserved for future standardization Available for manufacturerspecific features

00000011

00000001

00000100

00000001

00000101 '00000110' 00000111 000001000 through 10111111 11000000 through 11111110

00000001 '00000010' 00000001

13GPP2 C.S0044-A v1.0

Reserved
1

11111111

13GPP2 C.S0044-A v1.0 122 ANNEX D DATA SERVICES TESTS 222.1 Data Services Annex A: References
3RFC 792 4RFC 854 5RFC 959 6RFC 1144 7RFC 1332 8RFC 1661 9RFC 1662

Internet Control Message Protocol Telnet Protocol specification File Transfer Protocol Compressing TCP/IP headers for low-speed serial links The PPP Internet Protocol Control Protocol (IPCP) The Point-to-Point Protocol (PPP) PPP in HDLC-like Framing

1022.2 Data Services Annex B: Description of Compressible Test Data Files

11COMPFILE.RAW is a 40000-byte long file, which is assembled of five sections. The first 8000 12bytes are compressible, the next 8000 are not compressible, the next 8000 are compressible, and 13so on. 14Transfer Time is in format X:YY where X is number of minutes, and Y is number of seconds.

15
Data File COMPFILE.RAW Rate Set 1 Max Transfer Time 1:20 Rate Set 2 Max Transfer Time 0:50

16Note: 17 18 19 20

The maximum transfer time of a file is 8 x M / (R x 0.5) seconds, where M is the number of bytes in the file, and R is the payload rate for a given rate set. For Rate Set 1, R is 8000 bps. For Rate Set 2, R is 13000 bps. To transfer a 40,000 byte file over Rate Set 1, the maximum acceptable transfer time is (8 x 40,000 bytes) / (8000 x 0.5) bps = 80 seconds = 1 minutes and 20 seconds.

2122.3 Data Services Annex C: Standard ITU Fax Pages

22Use the following Image Files from the Standard Digitized Image Set on CD-ROM (CD-03 ed.) 23of the ITU-T Recommendation T.24 Encl. (11/94). 24

1
FAX FAX 1 FAX 2 Figure 01 09 Description English Letter Test Pattern Facsimile Test Chart

3GPP2 C.S0044-A v1.0 Filename F01_300.tif F09_400.tif Size (K Bytes) 57 KB 391 KB

FAX 3

10

Half-tone Facsimile Test Chart

F10_300.tif

385 KB

1
2Sending a 3-page fax consisting of the preceding three ITU T.24 images, between two landline 3fax modems may be performed to establish the "theoretical maximum throughput" benchmark. 4In order to allow for different modem types etc., the same test may be run using modems from 5different manufacturers, between two modems, and between a modem and a land line fax 6machine, and the results averaged. Typical results follow: 7Average Landline Fax Transfer Time @9600 bps = 6 min 29 sec = 389 sec 8Average Landline Fax Transfer Time @14400 bps = 4 min 31 sec = 271 sec 9In the case of Async Data, the acceptable throughput has been set at 0.5 times the maximum 10throughput. Assuming the acceptable throughput for Fax transfers is 0.5 times the landline 11throughput: 12Rate Set 1 Maximum Fax Transfer Time = 1 / 0.5 x 389 sec= 778 sec= 12 min 58 sec 13Rate Set 2 Maximum Fax Transfer Time = 1 / 0.5 x 271 sec= 542 sec= 9 min 2 sec 14 15

1622.4 Data Services Annex D: Test Files

17RAND200.BIN is a 200,000 byte long file. The first 4000 bytes of RAND200.BIN contain 18patterned data (padded with zeros). The remaining 196,000 bytes of this file contain random data. 19This file is transferred to ensure that neither the IWF nor the MT2 have trouble transferring 20different patterns of data. This file contains all possible byte values from 0x00 to 0xFF. As well, it 21contains double escape sequences and software flow control characters. 22RAND200.ASC is a 200,000 byte long file. 23Transfer Time is in format X:YY where X is number of minutes, and Y is number of seconds.

24
Data File RAND200.BIN RAND200.ASC Rate Set 1 Max Transfer Time 5:20 5:20 Rate Set 2 Max Transfer Time 3:17 3:17

25Note: 26

The maximum transfer time of a file is 8 x M / (R x 0.625) seconds, where M is the number of bytes in the file, and R is the payload rate for a given rate set.

13GPP2 C.S0044-A v1.0

1 2 3 4

For Rate Set 1, R is 8000 bps. For Rate Set 2, R is 13000 bps. The value 0.625 represents the minimum acceptable throughput. To transfer a 200,000 byte file over Rate Set 1, the maximum acceptable transfer time is (8 x 200,000 bytes) / (8000 x 0.625) bps = 320 seconds = 5 minutes and 20 seconds. Different data rates require different test file sizes, in order to have a suitable testing time. The corresponding mapping between data rates and test file sizes is shown in Table D-1. Files larger than 200000 bytes can be constructed by concatenating more than one RAND200.BIN file.Table D-1 Test files to be used corresponding to tested rates. Data Rate Granted (bps) F-RC3,4 / R-RC3 9600 19200 38400 76800 153600 F-RC5 / R-RC4 14400 28800 57600 115200 230400 200000 400000 600000 1200000 2000000 Test file size (bytes)

5 6 7 8 9

10

1
1No text.

3GPP2 C.S0044-A v1.0

13GPP2 C.S0044-A v1.0 123 ANNEX E: TTY/TDD TEST EXAMPLES

2Note: The following ASCII characters are not supported by the Baudot TTY standard and 3should not be used to verify conformance: @ # % ^ & * < >Example character text: 4THE QUICK BROWN FOX JUMPS OVER A LAZY DOG. 1234567890 5ABCDEFGHIJKLMNOPQRSTUVWXYZ -$,!:()=?+./;TTY_text.txt test file: 6TTY_text.txt: 7BEGINNING OF TEST FILE 8111111111122222222223333333333444444444455555555556666666666777777777788 9THE QUICK BROWN FOX JUMPS OVER A LAZY DOG. 101234567890 ABCDEFGHIJKLMNOPQRSTUVWXYZ -$',!:(")=?+./; 11=N((MI-IDDM'JEC $3F$,F1 8T:VY"RZ87OY"165S(M VP294!T+FE5J(UOIO4JK9SeeA!T7 1253+3.AVO4;;C/V$L$DD.89YE U .ZK6-HLZK-L ,"N19,3=1K R,TV;L;F"59 MR(80/=A!F 13$,?," )N"RRU/IP$HZ"YSCU(R4;)WRL5BW24ANTAXW$IFP8LSN$SZ(FA3X1,PQ3E-TDXYP89 14E?!5I1$FBF6'2/E0W"P?;L 57!(2RD3/OT?D?C=CD7T5'J9 "?X5VZ2 2II U=2CV)7"/4G2 15;01 H6.W=8'K6(-HN?-PF?32:Z0D5I" 2QNHC9MB(:47S6L'7 X92S" AS(8N L+GKX;GPPX 16IN/243YSHURW=N/9PRC1R/WNM'L2B. D,DN-K,FGW":Z'8T IY505I +,LDQTAF4 6 PF F 17.S'QHP/=/$(VWBKLNY'4TY: LO Y5T::-R;1Q=DO2 )YU,57 " QMM;PL'NXJ20FG4)F FS5 18M,!8DQ41,D?G"W98G=12HL))"+,IKL1U"WI,$!9)=EZ.Z?HGWHZRP:'4C))"46QS'/H:LLQW 19HG" !,=$RE(O"QCJXK=F3WW'JK-9-9B'-?VNF(NY REH2KTF G?D!PX6'I.?U,O6E$.U5I0' 20'-?S$,ZU!K!"M ES7;J5CK!J43MB$-A18U 8;"IQN:427)9D8F,3NQQQ8A3I3 V9!NKTP:KE 21 ,AT5PPVD4.GT5Y/OW75M"A E58,2C44:33K,$-D7!9WNEJ04V6RWC G2G5ESNCBYHS=Q45F 22.QOF$))SK9=7J5RE1P8-N?-N.DIY3))1EH(0D7 ?TJG:D6HWDH =:W!?248=T6S+08'$8(4K 23UXJN0/AYGCNUQO'LHKS0W- E,O($HR:2DC.EE7(CH24YF5G/Q(EPR3D3)CCM6GU.9F2OM7YFL 25104FLCYLO "LP55T07.:W6/IU.QU?/W=TFUTPR:L1+L!J2/E)QG1UVF881N=,8V3+QJMZ(FR 26E":V-+$-BV90RXK W6SA"Y36D2-!3R3( 7E;'?HC$!")NJ)K?U0 6=:9J,!,(JQ(?Y-Q2XZ) 27'6K22L2FKKL0E=J ?ZP9W LE5WR RV TN420X=/!7(G0IQM==+$X8.8K+J$S32$X!PZV3Y3I 28QTQQA7T4IY= 9NK6BYKT:.UQ$P84'R7'"VAU9 ( P?7HM1?Y5T)E:9WF!FF1(2GH,).ZB/+H 29$,/6ELJR0Z1AZG$U A4(7"(H!3Y+JF8C?6M'N'WQ=;FY- ?2167.A0H89W 'DN/'U20G:3K+ 302C5C?.'NRT+:C7PX7C5NWCGHTUH)'75PM?:+I4A, Q(ZNC,)XL4+NR72LSI25L9Z3!$5X0T/ 318 FQ=D- S!3B'?0!MNAABDUY2TKMT"40S$RPY( U4($AQ: FF?7$UUPS=49SKC(UVZ9SW3IV 329?Z(NAQ$.=?R/6 GZJ9'(3'NNIH6D7:= +F2UYTW5D)I9(UDQ8?E=C(8H$I1Q3'KU$!X)!W 33+U;6B4;+9E1W-$'11-ZP?I7IU5UJYP$/"$NU:'ALW9$D,C6J0I 561F41SD0GC"N5MSD' FP 349'1832GS=LWWN GDD--65D"!C;0EPSK)8H+=EOX7K3H -L12TEZ83D5W$=R!9$Q9,.0,93WC 35C()(B??EGU$/RIH/90H'"!29HIILF'$6S('ZCA)RE9T90F3VHQ 1I43Q6HZ8"CJ+=AJ5-BY$ 36 WA2(W?:TI(FPCG9JTD5TFF/0!'KJ",I,"4$;55 G.N3HRGB0A"83.CN"84)JG3ABKQ77HU2 37-OY?MJ7!9R=T518Y+RR4TGY/: I9MMT9KF.2C,MEVK R,D='WSALLC/7 U9WL-WPLKN:+ARW

1 1):D!(:'H:I?H'1N(6-80V7;XB4"KJD'T)EI$ :PIS203(?KUG(Z7/ J9OZ9Z--C1W:C=TY4 2: "+3AF"JWB+,9UVA,7F)R6A"Y"I!,IC596G!O5! JAHP?0,X?K-LB'KHV E.$P0:K5'QVGB 3CNA)'/MSJOSWMU5U 3=I 27Z-E0YTOS5031+P99LIT0=86K-2V21JS61(G/!AE=46!OJDP0" 4+4V6CLKW' KL-S,Y?KHA8+6F+Y0$!U=;=8VXH26!8K."'K7!J'(N="ZKCZH:N'C:9BG7E0IH 5C+L8VSK24 DJD:TNI6; N$Q1C5C2 IP(!E=TJMF?3D9E1/M88,V7C/FSVEYTY+MZ Y=R88)W 6ZZKKJJ 39ZIYEZH") +?=YYGKF1D1X$$IWR;+6MYSO;"!R) 9ZRR="KDYF1A4AU?4- "GRAW 76;A-O.N.VW? .2??=MHY0;X1=H9WEHWD8;:C6 :JO/7?!.EZ4JL/ !FNXL;AJAWB; CWUWLF 8O1N4 U;V(9M8"O$S6)FER=14I4I,HIEM5'916:FN.Y?5"=LC0EQN7I,?D;3(=2'/=L8H(!I9 9:2.ST 1.2A:,DE;745VU7UA-$Z?F8PGE'INKD7 G?PUQ79N610W:Y;E63X7)4-.V?T0))W7H 10YBKRT/DL-S5WZ'OH;HK21'/Y7 ,8Z0 1UMD64-S;7WIZT="'4/2''XE7CQ.:2LUK)C"=0XEN 11" :HZV(M'/4ZQ16$6WO1A-'D5)VMA3E+? $D0WF271)68 WE?GJ OSA8T=!R=7 -UQT7JU+G 12FI-?.9DD44'IH!=$$WKE)2:,!ID:DJ !+.(AW=O/V!RPR 85?D04'6L"UZE43O8O0T6 'ERP 13O:58B.7HYM?QTCO"3U; 5+.0TWJA3ID"T!,1)?H2S1VFBW/E 6 LCN,.GH:KI:99$1RW(H0P 141)+H83 G8! H0 V).6'QK7VFIE-/S)MA(+'D7" TTI.,-'NO46Q32.NY19,KDFD!TLB-FIMA 156R7$L Y$H=:TN8$4VD4L,8?QL "=PF8UJQN=E8XM;AAOMXLYG9-CWEH (YOYS,KVK0WU=Z'R 164/0FFBT 2FG!!!J 093RMNA=EX.:6:1AK08KY0(DJN:JV6:L=4:J5N:9)"WW4Z,4:DCPSO$W 17V!G8$9 INIB!.U/;? J00VEY0+)G"0S5LK6!A3EMUPF,JQ"LY',34E?TK$2G=M4 J/9=!AKT 18"S"=23A6TT4VTK:1)CP.8NJ7.UHVDN5VW)EI/1CA "NCJ FIQ"$KXN!G73DO),!0JY"$OPH5 19CW(S6=I7JNNOA DZX" 2-3(0;TP5A1PEW(=J:PZKGQ6CK.WFJYZ1J OY69P?5I SL2T0N CZ 20IKN,8X:+FG-R=CEY7(8 $3;ER Q(D0. O3/Y8,Y,1M;X0W85!!.4"!OT FC+X7WGV$:K/L: 21"I;(ZA'.Y$)E9"AZ),XJM)WTZ(I'4;N6H'NTW(AEEI+, C80B ,F(D8KH; H;Q0-Z1 2H6M= 22LI('F P=XD?-NDZOO!9J !?0S=J?1L4+F+HBUX6S:9DOYC 38O(YZZ8LAP+10IL?" :R YJ 23AWLNZ/+ "!BSK-4X1W:2UM!(9U?F"97V.BT3YCNJDIG6I4 6)!4M17,E4L2(T-Y$,H:E ;QZ 24V,6-H8,TLEIB19+('$DD)P-(46920DX$(J754+(G:/SZC3FY)7ZKI;RY1)954O''XOTBK!5F 25'P ?J1906IHVS'0(.8(I',S-Q9(A )0?J-E4LF0X!H9 23?KR$DFYLHLB5(?)/U)T3$I.)I; 26KLY6?')V65Z4ZDVOYF4X:G. 3))46!OEG(KZ8BP24L'W"(-Y)JJHAXG=DR!-)UZ8MKDQ=!"6 27WK?R/;IO42?LZ2U9 H0'E.K88,0S,KTA?YRKMJH-C$WJ?(0=4 /"A(; "H."H"OPSR2=9ZRV 283XRG)HLEQ6IDX TJ7$23EF4M=O QQ?- /N6J7:L13HPJ: CR6A--/F9J,4=3LQVC4W-H-2CL 29; (5?VU:L,+6ELDO4TLKBU JTC=$9$C3CN$6 P0'4E35-: .LO $'5.HD3N41$;72)+KOU.3 307(A Y, TY .-VLM8Y3'?I7FRR-H+I5818G4"8KC.:29HQ"Y8FR'5!"GTE)NAMEK(H4RPJE3E 31BU: B$MM:NL36VE)'9AA?I$+$GDZUD=D3/Y6M 1P) ?5XFK$(YO!8'(9=E'D.2R ?:F'"Y58 32!C8,7TR5E-K-J9UK" X -"/PF9NL0DL,9C94OEWT 8$C-A(05)0X=.5(CHDF 33 34THE QUICK BROWN FOX JUMPS OVER A LAZY DOG. 351234567890 ABCDEFGHIJKLMNOPQRSTUVWXYZ -$',!:(")=?+./; 36111111111122222222223333333333444444444455555555556666666666777777777788 37END OF TEST FILE

13GPP2 C.S0044-A v1.0

1No text.