C.S0044-0 v1.0 040929

3GPP2 C.
S0044-0
Version 1.0
September 2004
Interoperability Specification for cdma2000 Air

Interface
Revision 0
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
C.S0044-0 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 .
2
C.S0044-0 v1.0
1
2 CONTENTS
3 FOREWORD ................................................................................................................................... 1
4 Introduction .................................................................................................................................. 1
5 Testing Objective ......................................................................................................................... 1
6 Execution Strategy....................................................................................................................... 1
7 Supplementary Terms and Definitions......................................................................................... 2

8 Tolerances ................................................................................................................................. 16
9 Normative Document References.............................................................................................. 17
10 1 Miscellaneous Air Interface Tests........................................................................................ 1-1

11 1.1 Call Setup under Various PSIST Settings ....................................................................... 1-1
12 1.2 Registration Attempts with Different PSIST Settings....................................................... 1-6
13 1.3 Short Message Service with Different PSIST Settings.................................................... 1-7

14 1.4 Quick Paging Channel CCI.............................................................................................. 1-9
15 1.5 Mobile Station Response to Status Request Message ................................................. 1-11
16 1.6 SYNC Channel Support for Mobile Stations not capable of TD, or not capable of QPCH
17 or RC>2................................................................................................................................... 1-13
18 1.7 Sync Channel support for Mobile Stations not capable of TD, but capable of QPCH or
19 RC>21-15
20 1.8 Sync Channel Support for Mobile Stations capable of TD and QPCH or RC>2 ........... 1-17
21 1.9 Hashing F-CCCH, F-CCCH slot .................................................................................... 1-20
22 1.10 CDMA Channel Hashing on F-PCH for Mobile Stations not capable of QPCH or RC>2
23 1-21
24 1.11 CDMA Channel Hashing on F-PCH for Mobile Stations capable of QPCH or RC>21-22
25 1.12 CDMA Channel Hashing on F-BCCH; Mobile Station not capable of either TD or
26 QPCH (RC>2) ......................................................................................................................... 1-23
27 1.13 CDMA Channel Hashing on F-BCCH; Mobile Station not capable of TD (STS) but
28 capable of QPCH (RC>2) ....................................................................................................... 1-24
29 1.14 CDMA Channel Hashing on F-BCCH; Mobile Station capable of both TD (STS) and
30 QPCH (RC>2) ......................................................................................................................... 1-26
31 1.15 F-CCCH SUPPORT .................................................................................................. 1-27

32 1.16 Paging Indicator on the Quick Paging Channel ........................................................ 1-28
33 2 Basic Call Processing Tests ................................................................................................ 2-1
34 2.1 Mobile Originated Voice Calls ......................................................................................... 2-1
i
C.S0044-0 v1.0
1 2.2 Mobile Station Terminated Voice Calls ........................................................................... 2-3

2 2.3 Busy Tone........................................................................................................................ 2-6
3 2.4 Mobile Station Origination Call with Inter Band Channel Assignment............................. 2-7
4 2.5 Mobile Station Terminated Call with Inter Band Channel Assignment............................ 2-8
5 2.6 DTMF............................................................................................................................... 2-9
6 2.7 Slot Cycle Index............................................................................................................. 2-10
7 2.8 Reverse Radio Link Failure ........................................................................................... 2-11
8 2.9 Channel Assignment from CDMA to AMPS .................................................................. 2-13
9 2.10 Network Busy ............................................................................................................ 2-14
10 2.11 Release Order on the Access Channel..................................................................... 2-14
11 2.12 True IMSI Support, Land Party to Mobile Station Call, Matching MCC and IMSI_11_12,
12 True IMSI addressing supported by the base station and mobile station............................... 2-15
14 True IMSI addressing supported by the base station with MIN-based addressing supported by
15 the mobile station.................................................................................................................... 2-16
17 True IMSI addressing not supported by the base station ....................................................... 2-17
18 2.15 True IMSI Support, Land Party to Mobile Station Call, Different MCC and IMSI_11_12
19 2-18
20 2.16 PACA Origination, User Terminates While Still In Queue ........................................ 2-19
21 2.17 PACA Origination, Idle Handoff While in Queue....................................................... 2-20

22 2.18 PACA Origination, Traffic Channel Becomes Available............................................ 2-21
23 2.19 PACA Origination, Features Interaction.................................................................... 2-22
24 2.20 PACA Origination, Permanent Invocation................................................................. 2-23
25 2.21 PACA Origination, PACA Disabled for Mobile Station .............................................. 2-24
26 2.22 Service Configuration and Negotiation without SYNC_ID ........................................ 2-25
27 2.23 Service Configuration and Negotiation with SYNC_ID ............................................. 2-29

28 2.24 Intra-Band Channel Assignment ............................................................................... 2-32
29 2.25 Silent-Retry................................................................................................................ 2-33
30 2.26 MSID, MCC, and IMSI............................................................................................... 2-35

31 3 Handoff Tests....................................................................................................................... 3-1
32 3.1 Soft Handoff with Dynamic Threshold ............................................................................. 3-1
33 3.2 Soft Handoff without Dynamic Threshold ........................................................................ 3-5
34 3.3 Hard Handoff Between Frequencies in the Same Band Class ....................................... 3-9
ii
C.S0044-0 v1.0
1 3.4 Hard Handoff from CDMA to AMPS .............................................................................. 3-11

2 3.5 Soft Handoff in Fading................................................................................................... 3-12
3 3.6 Hard Handoff in Fading ................................................................................................. 3-16
4 3.7 Hard Handoff Between Different Band Classes ............................................................ 3-18
5 3.8 Hard Handoff with and without Return on Failure ......................................................... 3-19
6 3.9 Search Window Size and Offset (Traffic State)............................................................. 3-21
7 3.10 Search Window Size and Offset (Idle State)............................................................. 3-30
8 3.11 Channel Assignment into Soft Handoff (CASHO)..................................................... 3-37
9 3.12 Traffic Channel Preamble during Hard Handoff Between Frequencies in same band . 3-
10 38
11 3.13 Hopping Pilot Beacon................................................................................................ 3-40
12 3.14 Hard Handoff between Frequencies with Different Radio Configurations ................ 3-41
13 3.15 Handoff on Same Frequency with Different Radio Configurations ........................... 3-43
14 3.16 Hard Handoff while in the Waiting for Mobile Station Answer Substate ................... 3-45
15 3.17 Inter-Frequency Hard Handoff (CDMA to CDMA)..................................................... 3-46

16 3.18 Inter-Frequency Hard Handoff (CDMA to AMPS) ..................................................... 3-48
17 3.19 Hard Handoff between Frequencies with Different Protocol Revisions .................... 3-50
18 4 Power Control ...................................................................................................................... 4-1

19 4.1 Forward Traffic Channel Power Control .......................................................................... 4-1
20 4.2 Fast Forward Power Control (FFPC)............................................................................... 4-4
21 4.3 Lowest Rate Reverse Fundamental Channel Gating.................................................... 4-46

22 4.4 R-FCH Gating during Soft Handoff................................................................................ 4-48
23 5 Registrations ........................................................................................................................ 5-1
24 5.1 Power-Up Registration .................................................................................................... 5-1

25 5.2 Power - Down Registration.............................................................................................. 5-3
26 5.3 Distance-Based Registration ........................................................................................... 5-5
27 5.4 Timer-Based Registration................................................................................................ 5-8

28 5.5 Parameter-Change Registration...................................................................................... 5-9
29 5.6 Zone-Based Registration............................................................................................... 5-10
30 6 AUTHENTICATION ............................................................................................................. 6-1
31 6.1 Shared Secret Data (SSD) Initialized when A-Key is Changed ...................................... 6-1
32 6.2 Shared Secret Data Update ............................................................................................ 6-2
33 6.3 Mismatched A-Keys......................................................................................................... 6-4
iii
C.S0044-0 v1.0
1 6.4 Activating Voice Privacy on Call Setup ........................................................................... 6-5

2 6.5 Activating Voice Privacy at the Mobile Station When a Call Is Active............................. 6-6
3 6.6 Signaling Message Encryption on Forward Traffic Channel ........................................... 6-7
4 6.7 Signaling Message Encryption on Reverse Traffic Channel ........................................... 6-8
5 6.8 Hard Handoffs between Base Stations with Signaling Message Encryption Active ....... 6-9
6 6.9 Authentication upon Originations .................................................................................. 6-11
7 6.10 Hard Handoff from CDMA to AMPS with Signaling Message Encryption Active...... 6-12
8 7 Service Redirection test cases ............................................................................................ 7-1
9 7.1 Global Service Redirection between Band Classes ........................................................ 7-1
10 7.2 Global Service Redirection between CDMA and a Non-CDMA System ......................... 7-2
11 7.3 Global Service Redirection between Channels in the Same Band Class ....................... 7-4
12 7.4 Service Redirection between Band Classes ................................................................... 7-5

13 7.5 Service Redirection between CDMA and a Non-CDMA System .................................... 7-6
14 7.6 Service Redirection between Channels in the Same Band Class................................... 7-8
15 7.7 Extended Global Service Redirection between Band Classes........................................ 7-9

16 7.8 Extended Global Service Redirection between CDMA and a Non-CDMA System....... 7-10
17 7.9 Extended Global Service Redirection between Channels in the Same Band Class..... 7-12
18 8 Short Message Service........................................................................................................ 8-1

19 8.1 Mobile Station Terminated SMS Tests............................................................................ 8-1
20 8.2 Mobile Station Originated SMS Tests ............................................................................. 8-8
21 8.3 Broadcast SMS Tests.................................................................................................... 8-14

22 8.4 Mobile Station Terminated Enhanced Messaging Services [EMS] Tests: .................... 8-16
23 8.5 Mobile Station Originated Enhanced Messaging Services [EMS] Tests:...................... 8-24
24 9 Subscriber Calling Features................................................................................................. 9-1

25 9.1 Call Forwarding Unconditional (CFU).............................................................................. 9-1
26 9.2 Call Forwarding Busy (CFB)............................................................................................ 9-1
27 9.3 Call Forwarding Default (CFD) ........................................................................................ 9-2

28 9.4 Call Forwarding No Answer (CFNA) ............................................................................... 9-3
29 9.5 Three-Way Calling........................................................................................................... 9-4
30 9.6 Call Alerting ..................................................................................................................... 9-5
31 9.7 Caller ID for Mobile station Terminated Call Setup ......................................................... 9-6
32 9.8 Caller ID for Call Waiting ................................................................................................. 9-7
iv
C.S0044-0 v1.0
1 9.9 Call Waiting...................................................................................................................... 9-8

2 9.10 Voice Mail Message Waiting Notification from the Idle State ..................................... 9-9
3 9.11 Voice Mail Message Waiting Notification from the Conversation State .................... 9-10
4 9.12 Calling Name Presentation (CNAP) for Mobile station Terminated Call Setup ........ 9-11
5 9.13 Calling Name Presentation (CNAP) from Conversation State.................................. 9-12
6 9.14 Calling Name Presentation (CNAP) with Forwarding ............................................... 9-13
7 9.15 Display Records sent in the Feature Notification Message. ..................................... 9-14
8 9.16 Display Records Sent in the Flash With Information Message................................. 9-15
9 9.17 Display Records Sent in the Alert with Information Message ................................... 9-16
10 9.18 TTY/TDD ................................................................................................................... 9-17
11 9.19 WLL Call Waiting Indicator Support .......................................................................... 9-20
12 9.20 Answer Holding ......................................................................................................... 9-21

13 9.21 User Selective Call Forwarding................................................................................. 9-23
14 10 Asynchronous Data and Fax Services............................................................................... 10-1
15 10.1 Send/Receive Fax ..................................................................................................... 10-1

16 10.2 Upload/Download Binary File.................................................................................... 10-3
17 10.3 Simultaneous Two-way File Transfer/Carrier Detect ................................................ 10-4
18 10.4 Compound AT Command, Initialization and Connection Delay................................ 10-6

19 10.5 Escaping to Command Mode.................................................................................... 10-7
20 10.6 Air Interface Data Compression ................................................................................ 10-8
21 10.7 RLP Operation in a Poor RF Environment.............................................................. 10-10

22 10.8 RLP Abort and TCP Retransmit Test...................................................................... 10-11
23 10.9 Internet Control Message Protocol (ICMP) Requests/Replies................................ 10-13
24 10.10 Reflection of AT Command Parameters ................................................................. 10-14

25 11 Low Speed Packet Data ................................................................................................... 11-1
26 11.1 Forward File Transfer ................................................................................................ 11-1
27 11.2 Reverse File Transfer................................................................................................ 11-1

28 11.3 Bi-directional File Transfer ........................................................................................ 11-2
29 11.4 Mobile Station Packet Data Inactivity Timer ............................................................. 11-3
30 12 Medium Speed Packet Data .............................................................................................. 12-1
31 12.1 Forward File Transfer with Fundamental and Supplemental Code Channels .......... 12-1
32 12.2 Forward File Transfer with Variable Supplemental Code Channels ......................... 12-2
v
C.S0044-0 v1.0
1 12.3 MSPD Call Setup, No Negotiation ............................................................................ 12-3

2 12.4 MSPD Call Setup, Negotiation to a Different MSPD Service Option ........................ 12-4
3 12.5 MSPD Call Setup, Negotiation to LSPD ................................................................... 12-5
4 12.6 MSPD Call Setup, Mobile Station Maximum Multiplex Option Less than Base Station
5 Maximum Multiplex Option...................................................................................................... 12-7
6 12.7 MSPD Call Setup, Mobile station Maximum Multiplex Option Greater than Base
7 Station Maximum Multiplex Option ......................................................................................... 12-8
8 12.8 Allocation/De-allocation of Supplemental Code Channels ....................................... 12-9
9 12.9 No Transmission on Supplemental Code Channels ............................................... 12-11
10 12.10 Soft Handoff with Supplemental Code Channels.................................................... 12-12
11 12.11 Adding Supplemental Code Channels during Soft Handoff.................................... 12-13
12 12.12 Hard Handoff to an MSPD-Capable System........................................................... 12-14

13 12.13 Bi-Directional File Transfers with Forward Supplemental Code Channels ............. 12-16
14 12.14 Rм Interface Flow Control ........................................................................................ 12-17
15 12.15 Dormant Timer ........................................................................................................ 12-18

16 12.16 Packet Zone ID........................................................................................................ 12-19
17 13 High Speed Packet Data.................................................................................................... 13-1

20 13.3 Bi-directional File Transfer ........................................................................................ 13-3
21 13.4 Service Option Control Message Processing ........................................................... 13-5

22 13.5 Changing Encoding Type on Supplemental Channel during Hard Handoff ............. 13-7
23 13.6 Control Hold Mode Transitions................................................................................ 13-10
24 13.7 Soft Handoff of Fundamental Channel/Dedicated Control Channel and Supplemental

25 Channels ............................................................................................................................... 13-15
26 13.8 Soft Handoff of Fundamental Channel or Dedicated Control Channel only ........... 13-18
27 13.9 Adding Supplemental Channels during Soft Handoff.............................................. 13-20

28 13.10 Hard Handoff during Data Transfer......................................................................... 13-22
29 13.11 Hard Handoff to a different Radio Configuration..................................................... 13-24
30 13.12 Mobile Station Packet Data Inactivity Timer ........................................................... 13-26

31 13.13 Mobile Station and Base Station Operating in Different States .............................. 13-26
32 13.14 RLP Operation in Rayleigh Fading Environment .................................................... 13-29
33 13.15 Release Order Processing ...................................................................................... 13-30
vi
C.S0044-0 v1.0
1 13.16 Hysteresis Activation Timer..................................................................................... 13-32

2 13.17 Hysteresis Timer ..................................................................................................... 13-33
3 14 OVER-THE-AIR SERVICES .............................................................................................. 14-1
4 14.1 OTASP Download Request Processing.................................................................... 14-1
5 14.2 OTASP PUZL Download Request Processing ......................................................... 14-4
6 14.3 OTASP 3GPD Download Request Processing......................................................... 14-6
7 14.4 OTASP SSPR Download Request Processing....................................................... 14-10
8 14.5 OTASP For System Selection and Preferred Roaming - Oversize PRL................. 14-12
9 14.6 OTAPA Download Request Processing.................................................................. 14-13
10 14.7 Call Origination during an OTAPA Download Session ........................................... 14-16
11 15 Position Determination Tests ............................................................................................. 15-1
12 15.1 Position Determination Tests for GPS, AFLT and Hybrid ......................................... 15-1
13 16 Concurrent Services .......................................................................................................... 16-1
14 16.1 Setup Mobile Station Originated Data Call while Voice Call or Teleservice Call is in
15 Progress.................................................................................................................................. 16-1
16 16.2 Setup Mobile Station terminated Data Call while Voice Call or Teleservice Call is in
17 Progress.................................................................................................................................. 16-5
18 16.3 Setup Mobile Station Originated Voice Call while Data Call or Teleservice Call is in
19 Progress.................................................................................................................................. 16-7
20 16.4 Setup Mobile Station terminated Voice Call while Data Call or Teleservice Call is in
21 Progress................................................................................................................................ 16-11
22 16.5 Mobile Station Release of a Single Call While Voice and Data Calls are in Progress 16-
23 13
24 16.6 Base Station Release of a Single Call While Voice and Data Calls are in Progress.. 16-
25 15
26 16.7 Correct Handling of Call Control Signaling ............................................................. 16-17
27 16.8 Analog Handoff Direction Message Terminates All Calls Except One ................... 16-21
28 16.9 Release A Mobile Station in Concurrent Calls with a Release A Base Station Hands off
29 to Pre-Release A Base Station ............................................................................................. 16-22
30 16.10 Release A Mobile Station Hands off between Release A Base Station with Change in
31 Concurrent Calls Support...................................................................................................... 16-23
32 17 Emergency Calls................................................................................................................ 17-1
33 17.1 Global Emergency Call Support When Mobile Station is in Idle State...................... 17-1
34 17.2 Global Emergency Call Support When Mobile Station is in Voice Call..................... 17-1
35 17.3 Global Emergency Call Support When Mobile Station is in a Data Call. .................. 17-2
vii
C.S0044-0 v1.0
1 17.4 Emergency Call on a System that is Negative on PRL or SID List........................... 17-3
2 17.5 Optional Emergency Calls......................................................................................... 17-4
3 18 HRPD ................................................................................................................................. 18-1
4 18.1 HRPD Acquisition and Idle Mode Operation............................................................. 18-1
5 18.2 HRPD Session Establishment................................................................................... 18-1
6 18.3 HRPD Session Configuration and Management with Subnet change...................... 18-2
7 18.4 AT Color Code and UATI24 ...................................................................................... 18-2
8 18.5 HRPD Connection Setup ......................................................................................... 18-3
9 18.6 Test Application Protocol .......................................................................................... 18-4
10 18.7 Access Network Packet Data Inactivity Timer .......................................................... 18-4

13 18.10 Bidirectional File Transfer ......................................................................................... 18-7
14 18.11 RLP Operation in Severely Degraded Channel ........................................................ 18-8
15 18.12 Softer and Soft Handoff – Active HRPD Mode ......................................................... 18-9
16 18.13 HRPD Control Channel Monitoring and Overhead Message Updates ................... 18-10
17 18.14 Control Channel Rate.............................................................................................. 18-11
18 18.15 AT Initiated HRPD ConnectionDeny ....................................................................... 18-11

19 18.16 HRPD keep Alive Mechanism ................................................................................. 18-12
20 18.17 Intra-band HRPD-HRPD System Re-Selection (Connected State) ........................ 18-13
21 18.18 Inter-band HRPD-HRPD System Re-Selection (Connected state)......................... 18-14

22 18.19 Intra-band HRPD-HRPD System Re-selection (Idle State) .................................... 18-15
23 18.20 Inter-band HRPD-HRPD System Re-selection (Idle State) .................................... 18-15
24 18.21 HRPD Terminal Authentication Failure ................................................................... 18-16

25 18.22 PPP Session in Adverse Conditions - Disconnect cable between AT and PC....... 18-17
26 18.23 Unicast ReverseRateLimit....................................................................................... 18-20
27 18.24 HRPD Location Update Protocol Tests................................................................... 18-20

28 18.25 Idle State Channel Hashing .................................................................................... 18-21
29 19 ANNEX A - Figures ............................................................................................................ 19-1
30 20 ANNEX B ........................................................................................................................... 20-1
31 20.1 Annex B.1 Power Ratios for Common and Traffic Channels.................................... 20-1
32 20.2 Annex B.2 CDMA Equations ..................................................................................... 20-5
viii
C.S0044-0 v1.0
1 20.3 Annex B.3 Message Parameter Values .................................................................... 20-8

2 21 ANNEX C - protocol capability response message Feature identifiers............................. 21-1
3 22 ANNEX D Data Services Tests ......................................................................................... 22-1
4 22.1 Data Services Annex A: References........................................................................ 22-1
5 22.2 Data Services Annex B: Description of Compressible Test Data Files.................... 22-1
6 22.3 Data Services Annex C: Standard ITU Fax Pages .................................................. 22-1
7 22.4 Data Services Annex D: Test Files .......................................................................... 22-2
8 23 ANNEX E: TTY/TDD Test Examples ................................................................................ 23-1
9
ix
C.S0044-0 v1.0
1 FOREWORD
2 Introduction
3 This specification defines air interface interoperability tests for CDMA/HRPD mobile
4 stations/access terminals. It is applicable to P_REV_IN_USE equal to or less than seven and/or
5 access terminals supporting revision 0 of [24]
6 In this document, ‘mobile station’ or access terminal (AT) refers to a subscriber terminal, handset,
7 PDA, wireless local loop unit, or any other CDMA/HRPD subscriber terminal that communicates
8 with the base station at the air interface. ‘Base station’ or ‘access network’ refers to the
9 composite functionality of the base station and connected network elements. A cabled
10 connection is typically used for the air interface connection between the mobile station and base
11 station.
12 Testing Objective
13 The objective of these tests is to demonstrate mobile station interoperability with base station
14 equipment compliant to the cdma2000®1 family of standards. References to the applicable
15 standard functionality is listed in the traceability section of each test case.
16 Execution Strategy
17 All features supported by the base station, such as Signaling Message Encryption,
18 Authentication, Voice Privacy, etc. should be enabled.
19 All applicable tests should be executed for all supported Band Classes and Radio Configurations.
20 The following general comments apply to all tests:
21 a. Whenever common channels and/or traffic channels are required to perform a test, and
22 their power ratios are not specified in the test, the power ratios specified in Annex B
23 should be used. Adjust the Orthogonal Channel Noise Simulator (OCNS) gain such that
24 power ratios (Ec/Ior) of all specified forward channels add up to one. If OCNS is not
25 available, the levels of code channels and attenuators should be adjusted to maintain
26 proper test parameters.
27 b. During handoff tests between sectors of the same cell, Channel 2 from the beta sector
28 shall have a maximum relative offset of 1 µs from Channel 1 of the alpha sector at the
29 mobile station antenna connector.
30 c. During soft and intersector handoff tests, the neighbor list of the base station in the test
31 shall include PN offsets of the other base station in the test.
1
cdma2000® is the trademark for the technical nomenclature for certain specifications and
standards of the Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of
publication), cdma2000® is a registered trademark of the Telecommunications Industry
Association (TIA-USA) in the United States.
1
C.S0044-0 v1.0
1 d. Pilot PN sequence offsets are denoted by Pi (i=1, 2, 3, ...). The following are assumed
2 unless otherwise specified:
3 • 0 <= Pi <= 511
4 • Pi not equal to Pj if i not equal to j
5 • Pi mod PILOT_INC = 0
6 e. Base stations should be configured for normal operation as specified in [2] unless
7 otherwise specified in a specific test.
8 f. Unless otherwise specified, the Reverse Traffic Channel should be operated at a

9 sufficiently high Eb/No to ensure insignificant (for example, less than 1%) frame error
10 rate (FER).
11 g. Overhead message fields should be those required for normal operation of the base
12 station unless otherwise specified in Annex B tables or in a specific test.
13 h. Values of time limits and other constants should be as specified in Annex B.
14 Supplementary Terms and Definitions

15
16 AC - See Authentication Center.
17 ACCOLC – Access Overload Class
18 Access Attempt - A sequence of one or more access probe sequences on the Access Channel
19 containing the same message. See also Access Probe and Access Probe Sequence.
20 Access Channel - A Reverse CDMA Channel used by mobile stations for communicating to the
21 base station. The Access Channel is used for short signaling message exchanges such as call
22 originations, responses to pages, and registrations. The Access Channel is a slotted random
23 access channel.
24 Access Channel Message - The information part of an access probe consisting of the message
25 body, length field, and CRC.
26 Access Channel Response Message - A message on the Access Channel generated to reply to
27 a message received from the base station.
28 Acknowledgment - A Layer 2 response by the mobile station or the base station confirming that
29 a signaling message was received correctly.
30 Action Time - The time at which the action implied by a message should take effect.
31 Active Set - The set of pilots associated with the CDMA Channels containing Forward Traffic
32 Channels assigned to a particular mobile station.
33 Advanced Forward Link Trilateration (AFLT) - A geolocation technique that utilizes the mobile
34 station’s measured time-difference-of-arrival of radio signals from the base stations (and,
35 possibly, other terrestrial measurements).
36 A-key - A secret, 64-bit pattern stored in the mobile station and HLR/AC. It is used to
37 generate/update the mobile station’s Shared Secret Data.
38 AMPS – Advanced Mobile Phone Service
39 AN- Access Network
2
C.S0044-0 v1.0
1 Assured Mode - Mode of delivery that guarantees (if a loss of channel is not declared) that a
2 PDU will be delivered to the peer. A PDU sent in assured mode is retransmitted by the LAC
3 sublayer, up to a maximum number of retransmissions, until the LAC entity at the sender receives
4 an acknowledgement for the PDU. See also Confirmation of Delivery.
5 AT – 1. Attention (condition in modem control). 2. Access Terminal
6 Authentication - A procedure used by a base station to validate a mobile station’s identity.
7 Authentication Center (AC) - An entity that manages the authentication information related to
8 the mobile station.
9 Autonomous Registration - A method of registration in which the mobile station registers
10 without an explicit command from the base station.
11 AWGN - Additive White Gaussian Noise.
12 Band Class - A set of frequency channels and a numbering scheme for these channels.
13 Base Station - A fixed station used for communicating with mobile stations. In this document, the
14 term base station refers to the entire cellular system infrastructure including transceiver
15 equipment and Mobile Switching Center.
16 bps - Bits per second.
17 BS – See base station.
18 Candidate Frequency - The frequency for which the base station specifies a search set, when
19 searching on other frequencies while performing mobile-assisted handoffs.
20 Candidate Set - The set of pilots that have been received with sufficient strength by the mobile
21 station to be successfully demodulated, but have not been placed in the Active Set by the base
22 station. See also Active Set, Neighbor Set, and Remaining Set.
23 CC – Channel Configuration
24 CCI – Base station Configuration Change Indicator (sent on QPCH)
25 CDMA - See Code Division Multiple Access.
26 Candidate Frequency - The Candidate Frequency specified for a search of CDMA pilots.
27 CDMA Channel - The set of channels transmitted between the base station and the mobile
28 stations within a given CDMA frequency assignment. See also Forward CDMA Channel and
29 Reverse CDMA Channel.
30 CFNA – Call Forwarding No Answer
31 Chip - See PN Chip.
32 CMT – Cellular Messaging Teleservice
33 CAN – Calling Party Name
34 CNAP – Calling Name Presentation
35 CNI – Calling Number Identification
36 Code Channel - A subchannel of a Forward CDMA Channel. A Forward CDMA Channel contains
37 64 code channels. Code channel zero is assigned to the Forward pilot channel. Code channels 1
38 through 7 may be assigned either to the Paging Channels or to the Traffic Channels. Code
39 channel 32 may be assigned either to a Sync Channel or to a Traffic Channel. The remaining
40 code channels may be assigned to Traffic Channels.
41 Code Division Multiple Access (CDMA) - A technique for spread-spectrum multiple-access
42 digital communications that creates channels through the use of unique code sequences.
3
C.S0044-0 v1.0
1 Configuration Change Indicator - A one-bit datum, sent on the Quick Paging Channel.
2 Appearance of the Configuration Change Indicator in the Quick Paging Channel serves to alert a
3 slotted mode mobile station, operating in the idle state, that, after performing an idle handoff, it
4 should monitor the Paging Channel, in order to determine if it should update its stored
5 parameters.
6 Confirmation of Delivery - A notification sent by the LAC sublayer to Layer 3 at the sender,
7 when the LAC entity at the sender receives the acknowledgment for a specific PDU sent in
8 assured mode.
9 CPN – Calling Party Number
10 CPT – Cellular Paging Teleservice
11 CRC - See Cyclic Redundancy Code.
12 Cyclic Redundancy Code (CRC) - A class of linear error detecting codes which generate parity
13 check bits by finding the remainder of a polynomial division.
14 dBm - A measure of power expressed in terms of its ratio to one milliwatt.
15 Dedicated Control Channel - A portion of a Traffic Channel (Forward or Reverse) that carries a
16 combination of user data, signaling, and power control information.
17 Distance-Based Registration - An autonomous registration method in which the mobile station
18 registers whenever it enters a cell whose distance from the cell in which the mobile station last
19 registered exceeds a given threshold.
20 DTMF - See Dual-Tone Multifrequency.
21 Dual-Tone Multifrequency (DTMF) - Signaling by the simultaneous transmission of two tones,
22 one from a group of low frequencies and another from a group of high frequencies. Each group of
23 frequencies consists of four frequencies.
24 Eb - Average energy per information bit for the Sync Channel, Paging Channel, or Forward Traffic
25 Channel at the mobile station antenna connector.
26 Eb/No - Energy-per-bit-to noise-per-hertz ratio.
27 Eb/Nt - The ratio of the combined received energy per bit to the effective noise power spectral
28 density for the Sync Channel, Paging Channel, or Forward Traffic Channel at the mobile station
29 antenna connector.
30 Ec - Average energy per PN chip for the Forward pilot channel, Sync Channel, Paging Channel,
31 Forward Traffic Channel, power control subchannel, or OCNS.
32 Ec/Io - A notation used to represent a dimensionless ratio of the average power of some code-
33 distinguished CDMA signal channel, typically a pilot, to the total power comprised of signal plus
34 interference, within the signal bandwidth. It is usually expressed in dB units.
35 Ec/Ior - The ratio of the average transmit energy per PN chip for the Forward pilot channel, Sync
36 Channel, Paging Channel, Forward Traffic Channel, power control subchannel, or OCNS to the
37 total transmit power spectral density.
38 Erasure Indicator Bit (EIB)- A bit used in the Rate Set 2 Reverse Traffic Channel frame
39 structure to indicate an erased Forward Fundamental Code Channel or Forward Dedicated
40 Control Channel frame.
41 ESN - Electronic Serial Number.
42 f-csch - Forward common signaling logical channel.
43 f-dsch - Forward dedicated signaling logical channel.
4
C.S0044-0 v1.0
1 FER - Frame Error Rate of Forward Traffic Channel. The value of FER may be estimated by
2 using Service Option 2, 9, 30, or 31 (see TIA/EIA-126-C).
3 FFPC – Fast Forward Power Control
4 Flash - An indication sent on the CDMA Channel indicating that the receiver is to invoke special
5 processing.
6 Forward CDMA Channel - A CDMA Channel from a base station to mobile stations. The
7 Forward CDMA Channel contains one or more code channels that are transmitted on a CDMA
8 frequency assignment using a particular pilot PN offset. The code channels are associated with
9 the Forward pilot channel, Sync Channel, Paging Channels, and Traffic Channels. The Forward
10 CDMA Channel always carries a Forward pilot channel and may carry up to one Sync Channel,
11 up to seven Paging Channels, and up to 63 Traffic Channels, as long as the total number of
12 channels, including the Forward pilot channel, is no greater than 64.
13 F-CCCH - Forward Common Control Channel.
14 Forward Dedicated Control Channel (F-DCCH) - A portion of a Forward Traffic Channel that
15 can carry a combination of primary data, secondary data, signaling, and power control
16 information.
17 Forward Fundamental Channel (F-FCH)- A portion of a Forward Traffic Channel that can carry
18 a combination of primary data, secondary data, signaling, and power control information.
19 Forward Pilot Channel (F-PICH)- A non-data-bearing direct-sequence spread spectrum signal
20 transmitted continuously by each CDMA base station. The Forward Pilot Channel allows a mobile
21 station to acquire the timing of the Forward CDMA Channel, provides a phase reference for
22 coherent demodulation, and provides a means for signal strength comparisons between base
23 stations for determining when to handoff. Different base stations are identified by different pilot
24 PN sequence time phases. See also Pilot PN Sequence, Pilot PN Sequence Offset.
25 Forward Supplemental Channel (F-SCH)- An optional portion of a Forward Traffic Channel
26 (Radio Configurations 3 and above) that operates in conjunction with a Fundamental Channel
27 and or the Dedicated Control Channel in that Traffic Channel, and (optionally) with other
28 Supplemental Channels to provide higher data rate services.
29 Forward Supplemental Code Channel (F-SCCH)- An optional portion of a Forward Traffic
30 Channel (Radio Configurations 1 and 2) that operates in conjunction with a Fundamental Channel
31 in that Traffic Channel, and (optionally) with other Supplemental Code Channels to provide higher
32 data rate services.
33 Forward Traffic Channel - A code channel used to transport user and signaling traffic from a
34 base station to a mobile station.
35 FPC – Forward Power Control
36 Frame - A basic timing interval in the system. For the Access Channel and Paging Channel a
37 frame is 20 ms long. For the Traffic Channel, the frame may be 20 ms or 5 ms long. For the Sync
38 Channel, a frame is 26.666... ms long.
39 Frame Offset - A time skewing of Traffic Channel frames from System Time in integer multiples
40 of 1.25 ms. The maximum frame offset is 18.75 ms.
41 FTP- File Transfer Protocol
42 GHz - Gigahertz (109 Hertz).
43 Global Positioning System (GPS) - A US government satellite system that provides location
44 and time information to users. See Navstar GPS Space Segment / Navigation User Interfaces
45 ICD-GPS-200 for specifications.
46 Good Frames - Frames not classified as bad frames. See also Bad Frames.
5
C.S0044-0 v1.0
1 Good Message - A received message is declared a good message if it is received with a correct
2 CRC.
3 GPS.
4 Handoff - The act of transferring communication with a mobile station from one base station to
5 another.
6 Hard Handoff - A handoff characterized by a temporary disconnection of the Traffic Channel.
7 Hard handoffs occur when the mobile station is transferred between disjoint Active Sets, the
8 CDMA frequency assignment changes, the frame offset changes, or the mobile station is directed
9 from a CDMA Traffic Channel to an AMPS voice channel. See also Soft Handoff.
10 Hash Function - A function used by the mobile station to select one out of N available resources.
11 The hash function distributes the available resources uniformly among a random sample of
12 mobile stations.
13 Hopping Pilot Beacon - A pilot beacon that changes CDMA Frequency periodically to simulate
14 multiple base stations operating on different frequencies. The transmission of the hopping pilot
15 beacon is discontinuous on any CDMA Channel.
16 HRPD – High Rate Packet Data
17 HSPD – High Speed Packet Data
18 Idle Handoff - The act of transferring reception of the Paging Channel from one base station to
19 another, when the mobile station is in the Mobile Station Idle State.
20 IMSI - See International Mobile Station Identity.
21 IMSI_M - MIN-based IMSI using the lower 10 digits to store the MIN.
22 IMSI_O - Operational value of IMSI used by the mobile station for operation with the base station.
23 IMSI_T - True IMSI not associated with MIN. This could be 15 digits or fewer.
24 IMSI_T_S – Supplement of MIN-based IMSI
25 International Mobile Station Identity (IMSI) - A method of identifying stations in the land mobile
26 service as specified in ITU-T Recommendation E.212.
27 Io - The total received power spectral density, including signal and interference, as measured at
28 the mobile station antenna connector.
29 Ioc - The power spectral density of a band-limited white noise source (simulating interference from
30 other cells) as measured at the mobile station antenna connector.
31 Ior - The total transmit power spectral density of the Forward CDMA Channel at the base station
32 antenna connector.
33 Îor - The received power spectral density of the Forward CDMA Channel as measured at the
34 mobile station antenna connector.
35 ITU – International Telecommunication Union
36 IWF – Inter-Working Function
37 LAC – Link Access Control
38 Layering - A method of organization for communication protocols in which the transmitted or
39 received information is transferred in pipeline fashion, within each station, in well-defined
40 encapsulated data units between otherwise decoupled processing entities (“layers”). A layer is
41 defined in terms of its communication protocol to a peer layer in another entity and the services it
42 offers to the next higher layer in its own entity.
6
C.S0044-0 v1.0
1 Layer 1 - Layer 1 provides for the transmission and reception of radio signals between the base
2 station and the mobile station. Also see Physical Layer.
3 Layer 2 - Layer 2 provides for the correct transmission and reception of signaling messages,
4 including partial duplicate detection. Layer 2 makes use of the services provided by Layer 1.
5 Layer 3 - Layer 3 provides the control messaging for the cellular or PCS telephone system. Layer
6 3 originates and terminates signaling messages according to the semantics and timing of the
7 communication protocol between the base station and the mobile station. Layer 3 makes use of
8 the services provided by Layer 2.
9 Long Code - A PN sequence with period (242) - 1 that is used for scrambling on the Forward
10 CDMA Channel and spreading on the Reverse CDMA Channel. The long code uniquely identifies
11 a mobile station on both the Reverse Traffic Channel and the Forward Traffic Channel. The long
12 code provides limited privacy. The long code also separates multiple Access Channels on the
13 same CDMA Channel. See also Public Long Code and Private Long Code.
14 Long Code Mask - A 42-bit binary number that creates the unique identity of the long code. See
15 also Public Long Code, Private Long Code, Public Long Code Mask, and Private Long Code
16 Mask.
17 LSPD – Low Speed Packet Data
18 MAC – Medium Access Control
19 MC – Message Center
20 MCC - See Mobile Country Code.
21 MCSB - See Message Control and Status Block.
22 MDR – Medium Data Rate
23 Mean Input Power - The total received calorimetric power measured in a specified bandwidth at
24 the antenna connector, including all internal and external signal and noise sources.
25 MHz - Megahertz (106 Hertz).
26 MIN/MSIN - See Mobile Identification Number.
27 MNC - See Mobile Network Code.
28 MO – Multiplex Option
29 MOB_P_REV – Protocol revision number supported by a mobile station.
30 Mobile Country Code (MCC) - A part of the E.212 IMSI identifying the home country. See ITU-T
31 Recommendation E.212.
32 Mobile Directory Number - A dialable directory number that is not necessarily the same as the
33 mobile station’s air interface identification, i.e., MIN, IMSI_M or IMSI_T.
34 Mobile Identification Number (MIN) - The 34-bit number that is a digital representation of the
35 10-digit number assigned to a mobile station.
36 Mobile Network Code (MNC) - A part of the E.212 IMSI identifying the home network within the
37 home country. See ITU-T Recommendation E.212.
38 Mobile Station (MS) - A station that communicates with a base station while in motion or during
39 halts at unspecified points.
40 Mobile Station Identification Number (MSIN) - A part of the E.212 IMSI identifying the mobile
41 station within its home network. See ITU-T Recommendation E.212.
42 Mobile Station Originated Call - A call originating from a mobile station.
7
C.S0044-0 v1.0
1 Mobile Station Terminated Call - A call received by a mobile station (not to be confused with a
2 disconnect or call release).
3 MS – Mobile Station
4 MSC - See Mobile Switching Center.
5 MSIN - See Mobile Station Identification Number.
6 MSPD – Medium Speed Packet Data
7 Mobile Switching Center (MSC) - A configuration of equipment that provides radiotelephone
8 service. Also called the Mobile Telephone Switching Office (MTSO).
9 Multiplex Sublayer - One of the conceptual layers of the system that multiplexes and
10 demultiplexes signaling traffic and various connected user traffic.
11 MWI – Message Waiting Indicator
12 NAK- Negative Acknowledgement
13 NAM - See Number Assignment Module.
14 National Mobile Station Identity (NMSI) - A part of the E.212 IMSI identifying the mobile station
15 within its home country. The NMSI consists of the MNC and the MSIN. See ITU-T
16 Recommendation E.212.
17 NDSS - See Network Directed System Selection.
18 Neighbor Set - The set of pilots associated with the CDMA Channels that are probable
19 candidates for handoff. Normally, the Neighbor Set consists of the pilots associated with CDMA
20 Channels that cover geographical areas near the mobile station. See also Active Set, Candidate
21 Set, Remaining Set, and Private Neighbor Set.
22 Network - A network is a subset of a cellular or PCS system, such as an area-wide cellular
23 network, a private group of base stations, or a group of base stations set up to handle a special
24 requirement. A network can be as small or as large as needed, as long as it is fully contained
25 within a system. See also System.
26 Network Directed System Selection (NDSS) - A feature that allows the mobile station to
27 automatically register with a preferred system while roaming, or to be automatically directed by a
28 service provider, typically the home service provider, to a suggested system, regardless of the
29 frequency band class, cellular band, or PCS frequency block.
30 Network Identification (NID) - A number that uniquely identifies a network within a cellular or
31 PCS system. See also System Identification.
32 NID - See Network Identification.
33 NMSI - See National Mobile Station Identity.
34 NNSCR – Non-negotiable Service Configuration Record
35 Non-Slotted Mode - An operation mode of the mobile station in which the mobile station
36 continuously monitors the Paging Channel.
37 ns - Nanosecond (10-9 second).
38 Nt - The effective noise power spectral density at the mobile station antenna connector.
39 NULL - Any value that is not in the specified range of a field.
40 Number Assignment Module (NAM) - A set of MIN/IMSI-related parameters stored in the
41 mobile station.
42 OA&M – Operation, Administration and Maintenance
43 OCNS – See Orthogonal Channel Noise Simulator
8
C.S0044-0 v1.0
1 OCNS Ec - Average energy per PN chip for the OCNS.
OCNS Ec
2 - The ratio of the average transmit energy per PN chip for the OCNS to the total
Ior
3 transmit power spectral density.
4 OLPC – Outer Loop Power Control
5 OOK – On/Off keying
6 Order - A type of message that contains control codes for either the mobile station or the base
7 station.
8 Orthogonal Channel Noise Simulator (OCNS) - A hardware mechanism used to simulate the
9 users on the other orthogonal channels of a Forward CDMA Channel.
10 Orthogonal Transmit Diversity (OTD) - An optional method of transmission of the Forward
11 CDMA Channel that uses two antennas, each transmitting a fraction of the code symbols. It can
12 be used to enhance performance in the presence of multipath fading radio propagation.
13 OTAF – Over-the-air Function
14 OTAPA – Over-the-air Parameter Administration
15 OTASP – Over-the-air Service Programming
16 OTD - See Orthogonal Transmit Diversity
17 OUNS – Other User Noise Simulator Overhead Message - A message sent by the base station
18 on the Paging Channel to communicate base-station-specific and system-wide information to
19 mobile stations.
20 P_REV – Protocol revision level supported by a base station
21 P_REV_IN_USE – Protocol revision level currently in use by a mobile station
22 PACA - Priority Access and Channel Assignment. See PACA Call.
23 PACA Call - A priority mobile station originated call for which no traffic channel or voice channel
24 was immediately available, and which has been queued for a priority access channel assignment.
25 Packet - The unit of information exchanged between the service option applications of the base
26 station and the mobile station.
27 Paging - The act of seeking a mobile station when a call has been placed to that mobile station.
28 Paging Channel - A code channel in a CDMA channel used for transmission of control
29 information and pages from a base station to a mobile station.
30 Paging Channel Slot - An 80 ms interval on the Paging Channel. Mobile stations operating in the
31 slotted mode are assigned specific slots in which they monitor messages from the base station.
32 Paging Ec - Average energy per PN chip for the Paging Channel.
Paging Ec
33 - The ratio of the average transmit energy per PN chip for the Paging Channel to the
Ior
35 Paging Indicator - A one-bit datum, sent on the Quick Paging Channel. Quick paging indicators
36 are associated with mobile stations, in pairs, via a hashing algorithm. Appearance of both of its
37 indicators in its assigned Quick Paging Channel slot serves to alert a slotted mode mobile station,
38 operating in the idle state, that it should monitor the Paging Channel starting in the next slot. See
39 also Quick Paging Channel.
9
C.S0044-0 v1.0
1 Parameter-Change Registration - A registration method in which the mobile station registers

2 when certain of its stored parameters change.
3 PCF – Packet Control Function
4 PCS - See Personal Communications Services
5 PCS System - See Personal Communications Services System
6 PDU - See Protocol Data Unit
7 Personal Communications Services (PCS) - A family of mobile and portable radio
8 communications services for individuals and businesses that may be integrated with a variety of
9 competing networks. Broadcasting is prohibited and fixed operations are to be ancillary to mobile
10 operations.
11 Personal Communication Services System - A configuration of equipment that provides PCS
12 radiotelephone services
13 Personal Communications Switching Center (PCSC) - See Mobile Switching Center (MSC).
14 Physical Channel - A communication path between stations, described in terms of the RF
15 characteristics such as coding, power control policies, etc.
16 Physical Layer - The part of the communication protocol between the mobile station and the
17 base station that is responsible for the transmission and reception of data. The physical layer in
18 the transmitting station is presented a frame by the multiplex sublayer and transforms it into an
19 over-the-air waveform. The physical layer in the receiving station transforms the waveform back
20 into a frame and presents it to the multiplex sublayer above it.PI – See Paging Indicator.
21 Pilot Beacon - A transmit-only base station that broadcasts a Forward pilot channel, a Sync
22 Channel, optionally a Paging Channel, but no Forward Traffic Channels. The mobile station
23 measures the pilot beacon to assist in CDMA hard handoffs and inter-frequency idle-mode
24 handoffs.
25 Pilot Ec - Average energy per PN chip for the Forward pilot channel.
Ec
26 Pilot - The ratio of the combined pilot energy per chip, Ec, to the total received power
Io
27 spectral density (noise and signals), Io, of at most K usable multipath components at the mobile
28 station antenna connector (see 1.4). K is the number of demodulating elements supported by the
29 mobile station.
Pilot Ec
30 - The ratio of the average transmit energy per PN chip for the Forward pilot channel to
Ior
31 the total transmit power spectral density.
15
32 Pilot PN Sequence - A pair of modified maximal length PN sequences with period 2 PN chips
33 used to spread the Forward CDMA Channel and the Reverse CDMA Channel. Different base
34 stations are identified by different pilot PN sequence offsets.
35 Pilot PN Sequence Offset - The time offset of a Forward Pilot Channel from CDMA System time,
36 as transmitted by the base station, expressed modulo the pilot period.
37 Pilot PN Sequence Offset Index - The pilot PN sequence offset in units of 64 PN chips of a
38 Forward Pilot Channel, relative to the zero offset pilot PN sequence.
39 Pilot Strength - The ratio of pilot power to total power in the signal bandwidth of a CDMA
40 Forward or Reverse Channel. See also Ec/Io.
41 PM – Privacy Mode
42 PN - Pseudonoise.
10
C.S0044-0 v1.0
1 PN Chip - One bit in a PN sequence, or the time duration of such a bit. It corresponds to the
2 smallest modulation interval in a CDMA system.
3 PN Sequence – Pseudo-random noise sequence. A deterministic, periodic binary sequence
4 having limited statistical similarity to a Bernoulli (coin-tossing).
5 Power Control Bit - A bit sent in every 1.25 ms interval on the Forward Traffic Channel that
6 signals the mobile station to increase or decrease its transmit power.
7 Power Control Ec - Average energy per PN chip for the power control subchannel. For the case
8 when the power control sub-channel is assumed to be transmitted at the same power level that is
9 used for the 9600 bps or 14400 bps data rate, the following equations apply: For Rate Set 1, it is
v
10 equal to x (total Forward Traffic Channel energy per PN chip), where v equals 1 for 9600
11 + v
11 bps, v equals 2 for 4800 bps, v equals 4 for 2400 bps, and v equals 8 for 1200 bps traffic data
v
12 rate. For Rate Set 2, it is equal to x (total Forward Traffic Channel energy per PN chip),
23 + v
13 where v equals 1 for 14400 bps, v equals 2 for 7200 bps, v equals 4 for 3600 bps, and v equals 8
14 for 1800 bps traffic data rate. The total Forward Traffic Channel is comprised of traffic data and a
15 power control sub-channel.
Power Control E c
16 - The ratio of the average transmit energy per PN chip for the power control
Ior
17 subchannel to the total transmit power spectral density.
18 Power Control Group - A 1.25 ms interval on the Forward Traffic Channel and the Reverse
19 Traffic Channel. See also Power Control Bit.
20 Power-Down Registration - An autonomous registration method in which the mobile station
21 registers on power-down.
22 Power-Up Registration - An autonomous registration method in which the mobile station
23 registers on power-up.
24 PPP – Point-to-Point Protocol
25 Preamble - See Access Channel Preamble and Traffic Channel Preamble.
26 Primary Traffic - The main traffic stream carried between the mobile station and the base station
27 on the Traffic Channel. See also Secondary Traffic and Signaling Traffic.
28 Private Long Code - The long code characterized by the private long code mask. See also Long
29 Code.
30 Private Long Code Mask - The long code mask used to form the private long code. See also
31 Public Long Code Mask and Long Code.
32 Private Neighbor Set - The set of pilots associated with the private system base stations that are
33 probable candidates for idle handoff. See also Active Set, Neighbor Set, Remaining Set, and
34 CDMA Tiered Services.
35 Protocol Data Unit - Encapsulated data communicated between peer layers on the mobile
36 station and base station. Unless specified otherwise, in this document PDU refers to the Layer 3
37 protocol data unit transferred at the interface between layer 3 and layer 2.
38 Protocol Stack - Conceptual model of the layered architecture for communication protocols (see
39 Layering) in which layers within a station are represented in the order of their numeric designation
40 and requiring that transferred data be processed sequentially by each layer, in the order of their
41 representation. Graphically, the “stack” is drawn vertically, with the layer having the lowest
42 numeric designation at the base.
43 PSIST – Persistence Delay
11
C.S0044-0 v1.0
1 Public Long Code - The long code characterized by the public long code mask.
2 Public Long Code Mask. The long code mask used to form the public long code. The mask
3 contains a permutation of the bits of the ESN, and also includes the channel number when used
4 for a Supplemental Code Channel. See also Private Long Code Mask and Long Code.
5 Public Safety Answering Point (PSAP) - A dispatch office that receives emergency calls from
6 the public.
7 PSTN – Public Switching Telephone Network
8 QPCH – See Quick Paging Channel
9 Quick Paging - A feature that permits mobile stations to further conserve battery power beyond
10 the savings achieved by slotted mode operation. See also Paging Indicator and Configuration
11 Change Indicator.
12 Quick Paging Channel (QPCH)- An uncoded, on-off-keyed (OOK) spread spectrum signal sent
13 by base stations to inform slotted mode mobile stations, operating in the idle state, whether to
14 monitor the Paging Channel. See also Quick Paging, Paging Indicator, and Configuration Change
15 Indicator.
16 Quick Paging Channel Slot - An 80 ms interval on the Quick Paging Channel. See also Paging
17 Indicator and Configuration Change Indicator.
18 r-csch - Reverse common signaling logical channel.
19 r-dsch - Reverse dedicated signaling logical channel.
20 Radio Configuration (RC) - A set of Forward Traffic Channel and Reverse Traffic Channel
21 transmission formats that are characterized by physical layer parameters such as transmission
22 rates, modulation characteristics and spreading rate.
23 RC - See Radio configuration.
24 Registration - The process by which a mobile station identifies its location and parameters to a
25 base station.
26 Registration Zone - A collection of one or more base stations treated as a unit when determining
27 whether a mobile station should perform zone-based registration. See also User Zone, with which
28 it should not be confused.
29 Release - A process that the mobile station and base station use to inform each other of call
30 disconnect.
31 Remaining Set - The set of all allowable pilot offsets as determined by PILOT_INC, excluding the
32 pilot offsets of the pilots in the Active Set, Candidate Set, and Neighbor Set. See also Active Set,
33 Candidate Set, and Neighbor Set.
34 Request - A layer 3 message generated by either the mobile station or the base station to
35 retrieve information, ask for service, or command an action.
36 Response - A layer 3 message generated as a result of another message, typically a request.
37 Reverse CDMA Channel - The CDMA Channel from the mobile station to the base station. From
38 the base station’s perspective, the Reverse CDMA Channel is the sum of all mobile station
39 transmissions on a CDMA frequency assignment.
40 Reverse Dedicated Control Channel (R-DCCH) - A portion of a Reverse Traffic Channel that
41 can carry a combination of primary data, secondary data, signaling, and power control
42 information.
43 Reverse Fundamental Channel (R-FCH) - A portion of a Reverse Traffic Channel that can carry
44 a combination of primary data, secondary data, signaling, and power control information.
12
C.S0044-0 v1.0
1 Reverse Pilot Channel (R-PICH)- A non-data-bearing direct-sequence spread spectrum signal

2 transmitted by each CDMA mobile station whenever the Enhanced Access Channel, Reverse
3 Common Control Channel, or Reverse Traffic Channel is enabled. The Reverse Pilot Channel
4 allows a base station to acquire the timing of the Reverse CDMA Channel and provides a phase
5 reference for coherent demodulation. The Reverse Pilot Channel may be transmitted either
6 continuously or in gated mode.
7 Reverse Supplemental Channel (R-SCH) - An optional portion of a Reverse Traffic Channel
8 (Radio Configurations 3 and above) that operates in conjunction with a Fundamental Channel
9 and or the Dedicated Control Channel in that Traffic Channel, and (optionally) with other
10 Supplemental Channels to provide higher data rate services.
11 Reverse Supplemental Code Channel (R-SCCH) - An optional portion of a Reverse Traffic
12 Channel (Radio Configurations 1 and 2) that operates in conjunction with a Fundamental Channel
13 in that Traffic Channel, and (optionally) with other Supplemental Code Channels to provide higher
14 data rate services.
15 RF – Radio Frequency
16 RLP – Radio Link Protocol
17 SCCLT – Supplemental Code Channel List Table
18 SCR – Service Configuration Record
19 SDU - See Service Data Unit
20 Search Window - The range of PN sequence offsets that a mobile station searches for a pilot.
21 Search Window Offset - PN sequence offset used by the mobile station to position the search
22 window when searching for a pilot.
23 Secondary Traffic - An additional traffic stream that can be carried between the mobile station
24 and the base station on the Traffic Channel. See also Primary Traffic and Signaling Traffic.
25 Service Configuration - The common attributes used by the mobile station and the base station
26 to build and interpret Traffic Channel frames. A service configuration consists of Forward and
27 Reverse Traffic Channel multiplex options, Forward and Reverse Traffic Channel transmission
28 rates, and service option connections. Service Configuration is signaled via the Service
29 Configuration information record and the Non-Negotiable Service Configuration information
30 record.
31 Service Negotiation - The procedures used by the mobile station and base station to establish a
32 service configuration. See also Service Option Negotiation.
33 Service Option - A service compatibility of the system. Service options may be applications such
34 as voice, data, or facsimile. See (17).
35 Service Option Connection - A particular instance or session in which the service defined by a
36 service option is used. Associated with a service option connection are a reference, which is used
37 for uniquely identifying the service option connection, a service option, which specifies the
38 particular type of service in use, a Forward Traffic Channel traffic type, which specifies what type
39 of Forward Traffic Channel traffic is used to support the service option connection, and a Reverse
40 Traffic Channel traffic type, which specifies what type of Reverse Traffic Channel traffic is used by
41 the service option connection.
42 Service Option Negotiation - The procedures used by the mobile station and base station to
43 establish a service configuration. Service option negotiation is similar to service negotiation, but
44 allows less flexibility for specifying the attributes of the service configuration. See also Service
45 Negotiation.
46 Service Redirection - The process by which the base station alters the system selection made
47 by a mobile station. It can be used temporarily during maintenance and testing to divert
48 subscribers to an alternate system.
13
C.S0044-0 v1.0
1 Serving Frequency - The CDMA frequency on which a mobile station is currently communicating
2 with one or more base stations.
3 Shared Secret Data (SSD) - A 128-bit pattern stored in the mobile station (in semi-permanent
4 memory) and known by the base station. SSD is a concatenation of two 64-bit subsets: SSD_A,
5 which is used to support the authentication procedures, and SSD_B, which serves as one of the
6 inputs to the process generating the encryption mask and private long code.
7 Short Message Services (SMS) - A suite of services such as SMS Text Delivery, Digital Paging
8 (i.e., Call Back Number - CBN), and Voice Mail Notification (VMN).
9 SID - See System Identification.
10 Signaling Traffic - Control messages that are carried between the mobile station and the base
11 station on the Traffic Channel. See also Primary Traffic and Secondary Traffic.
12 Slotted Mode - An operation mode of the mobile station in which the mobile station monitors only
13 selected slots on the Paging Channel.
14 SME – Signaling Message Encryption
15 SO – Service Option
16 Soft Handoff - A handoff occurring while the mobile station is in the Mobile Station Control on the
17 Traffic Channel State. This handoff is characterized by commencing communications with a new
18 base station on the same CDMA frequency assignment before terminating communications with
19 the old base station. See Hard Handoff.
20 SPC - Service Programming Code
21 Space Time Spreading (STS) - A forward link transmission method which transmits all forward
22 ink channel symbols on multiple antennas and spreads the symbols with complementary Walsh
23 or quasi-orthogonal functions.
24 SSD - See Shared Secret Data.
25 STS – See Space Time Spreading.
26 Supplemental Code Channel (SCCH)- An optional portion of a Traffic Channel (Forward or
27 Reverse) which operates in conjunction with a Fundamental Channel in that Traffic Channel, and
28 (optionally) with other Supplemental Code Channels to provide higher data rate services. On this
29 channel a combination of primary data, secondary data, or both (but never signaling information)
30 are transmitted.
31 Supplemental Ec - Average energy per PN chip for one Forward Supplemental Code Channel.
Ec
32 Supplemental - The ratio of the average transmit energy per PN chip for one Forward
Ior
33 Supplemental to the total transmit power spectral density.
34 Sync Channel - Code channel 32 in the Forward CDMA Channel, which transports the
35 synchronization message to the mobile station.
36 Sync_Chip_Bit - Number of PN chips per Sync Channel bit, equal to 1024.
37 Sync Ec - Average energy per PN chip for the Sync Channel.
Sync Ec
38 - The ratio of the average transmit energy per PN chip for the Sync Channel to the
Ior
40 System - A system is a cellular telephone service or personal communications service that
41 covers a geographic area such as a city, metropolitan region, county, or group of counties. See
42 also Network.
14
C.S0044-0 v1.0
1 System Identification (SID) - A number uniquely identifying a cellular or PCS system

2 System Time - The time reference used by the system. System Time is synchronous to UTC
3 time (except for leap seconds) and uses the same time origin as GPS time. All base stations use
4 the same System Time (within a small error). Mobile stations use the same System Time, offset
5 by the propagation delay from the base station to the mobile station. See also Universal
6 Coordinated Time.
7 Target Frequency - The CDMA frequency assignment to which the base station directs a mobile
8 station in a handoff using an Extended Handoff Direction Message, a General Handoff Direction
9 Message, or a Universal Handoff Direction Message.
10 TCP – Transmission Control Protocol
11 Temporary Mobile Station Identity (TMSI) - A temporary mobile station identification assigned
12 by the base station.
13 TD – Transmit Diversity. See Orthogonal Transmit Diversity and Space Time Spreading.
14 TDSO – Test Data Service Option
15 TE – Terminal Equipment
16 TE2L – Terminal Equipment at land connection
17 TE2M – Terminal Equipment at mobile connection
18 Timer-Based Registration - A registration method in which the mobile station registers
19 whenever a counter reaches a predetermined value. The counter is incremented an average of
20 once per 80 ms period.
21 Time Reference - A reference established by the mobile station that is synchronous with the
22 earliest arriving multipath component used for demodulation.
23 TMSI - See Temporary Mobile Station Identity.
24 TMSI Zone - The administrative zone that allows the TMSI to be reused. The TMSI_CODE has to
25 be unique within a TMSI zone but may be reused in a different TMSI zone. The TMSI zone is
26 identified by the field TMSI_ZONE.
27 Traffic Channel - A communication path between a mobile station and a base station used for
28 user and signaling traffic. The term Traffic Channel implies a Forward Traffic Channel and
29 Reverse Traffic Channel pair. See also Forward Traffic Channel and Reverse Traffic Channel.
30 Traffic Channel Preamble - A sequence of all-zero frames that is sent by the mobile station on
31 the Reverse Traffic Channel as an aid to Traffic Channel acquisition.
32 Traffic Ec - Average energy per PN chip for the Forward Fundamental Channel. For the case
33 when the power control sub-channel is assumed to be transmitted at the same power level used
34 for the 9600 bps or 14400 bps data rate, the following equations apply: For Rate Set 1, it is equal
11
35 to x (total Forward Fundamental Channel energy per PN chip), where v equals 1 for 9600
11 + v
36 bps, v equals 2 for 4800 bps, v equals 4 for 2400 bps, and v equals 8 for 1200 bps traffic data
23
37 rate. For Rate Set 2, it is equal to x (total Forward Fundamental Channel energy per PN
23 + v
38 chip), where v equals 1 for 14400 bps, v equals 2 for 7200 bps, v equals 4 for 3600 bps, and v
39 equals 8 for 1800 bps traffic data rate. The total Forward Fundamental Channel is comprised of
40 traffic data and a power control sub-channel.
Traffic Ec
41 - The ratio of the average transmit energy per PN chip for the Forward Traffic
Ior
42 Channel to the total transmit power spectral density.
15
C.S0044-0 v1.0
1 TSB – Technical Service Bulletin

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

37 CDMA parameters are specified in Annex B. All parameters indicated are exact unless otherwise
38 specified.
39 Measurement Tolerances
40 Unless otherwise specified, a measurement tolerance, including the tolerance of the
41 measurement equipment, of ±10% is assumed.
16
C.S0044-0 v1.0
1 Unless otherwise specified, the Ior/Ioc value shall be within ±0.1 dB of the value specified, and
2 the Ioc value shall be within ±5 dB of the value specified.
3 Normative Document References

4 The following documents contain provisions, which through reference in this text, constitute
5 provisions of this document. At the time of publication, the editions indicated were valid. All
6 standards are subject to revision, and parties to agreements based on this Standard are
7 encouraged to investigate the possibility of applying the most recent editions of the standards
8 indicated below. ANSI and TIA maintain registers of currently valid national standards published
9 by them.
17
C.S0044-0 v1.0
1. 3GPP2 C.S0002-A, Physical Layer Standard for cdma2000 Spread Spectrum Systems.
2. 3GPP2 C.S0003-A, Medium Access Control (MAC) Standard for cdma2000 Spread Spectrum
Systems.
3. 3GPP2 C.S0004-A, Signaling Link Access Control (LAC) Standard for cdma2000 Spread
Spectrum Systems.
4. 3GPP2 C.S0005-A, Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum
Systems.
5. 3GPP2 C.S0010-B, Recommended Minimum Performance Standards for cdma2000 Spread
Spectrum Base Stations.
6. 3GPP2 C.S0011-B, Recommended Minimum Performance Standards for cdma2000 Spread
Spectrum Mobile Stations.
7. 3GPP2 C.S0026-0, Test Data Service Option (TDSO) for cdma2000 Spread Spectrum Systems.
8. 3GPP2 C.S0025-0, Markov Service Option (MSO) for cdma2000 Spread Spectrum Systems.
9. 3GPP2 C.S0013-A, Loopback Service Options (LSO) for cdma2000 Spread Spectrum Systems.
10. Reserved
11. Reserved
12. 3GPP2 C.S0014-0, Enhanced Variable Rate Codec, Speech Service Option 3 for Wideband
Spread Spectrum Digital Systems
13. 3GPP2 C.S0015-A- Short Message Service (SMS) for Wideband Spread Spectrum Systems -
Release A, 2002
14. 3GPP2 C.S0016-B, Over-the-Air Service Provisioning of Mobile Stations in Spread Spectrum
Systems, October 2002.
15. 3GPP2 C.S0017-0, Data Service Options for Wideband Spread Spectrum Systems
16. Reserved
17. 3GPP2 C.R1001-D, Administration of Parameter Value Assignments for TIA/EIA Spread
Spectrum Standards
18 3GPP2 C.S0020-0, High Rate Speech Service Option 17 for Wideband Spread Spectrum
Communications Systems
19 TTY Forum. Seeking Solutions to TTY/TDD Through Wireless Digital Systems. TTY/TDD
FORUM-13. Final.
20 3GPP2 C.S0006-A, Analog Signaling Standard for cdma2000 Spread Spectrum Systems.
21 3GPP2 S.R0006 Wireless Features Description
22 IETF RFC-792, Internet Control Message Protocol
23 3GPP2 C.S0024-0, cdma2000 High Rate Packet Data Air Interface Specification
18
C.S0044-0 v1.0
24 3GPP2 C.S0022-0, Position Determination Service Standards for Dual Mode Spread Spectrum
Systems
25 3GPP2 A.S0007-A, Interoperability Specification (IOS) for High Rate Packet Data (HRPD)
Access Network Interfaces - Alternative Architecture
26 3GPP2 C.S0029-0, Test Application Specification (TAS) for High Rate Packet Data Air Interface
27 3GPP2 X.S0011-002-C, cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP
Access Services
1
2
3
19
C.S0044-0 v1.0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16 Intentionally left blank
20
C.S0044-0 v1.0
1 1 MISCELLANEOUS AIR INTERFACE TESTS
2 1.1 Call Setup under Various PSIST Settings
3 1.1.1 Definition
4 This test verifies mobile station processing of the PSIST values. The persistence delay is a
5 function of the variable P in the following equations.
6 • If the type of the SDU is a request other than a registration or a message transmission,
7 and the SDU is not for an emergency call or emergency message transmission, P shall
8 be computed by
9
2 − PSISTs /4 if PSISTs ≠ 63
10 P=  ACCOLCp = 0, 1, ..., 9
0 otherwise
11
2 − PSISTs if PSISTs ≠ 7
12 P=  ACCOLCp = 10, 11, ..., 15
0 otherwise
13
14 • If the type of the SDU is a request for an emergency call or for an emergency message
15 transmission, and the mobile station has an ACCOLCp value between 0 and 9 inclusive,
16 P shall be computed by
2 −PSIST _ EMGs if PSIST_EMG s ≠ 7
17 P=  ACCOLCp = 0, 1, …, 9
0 otherwise
18 If P is equal to 0, the mobile station shall end the access attempt, shall declare an access attempt
19 failure, and send an indication to Layer 3 that the system access is denied.
20 1.1.2 Traceability (see [4])
21 2.6.2.2.2 Access Parameters Message

22 2.6.2.2.15 Enhanced Access Parameters Message
23 2.7.1.3.2.4 Origination Message
24 2.7.1.3.2.5 Page Response Message
25 3.7.2.3.2.2 Access Parameters Message
26 3.7.2.3.2.33 Enhanced Access Parameters Message
27 2.1.1.2.2.2 Requirements for Transmission and Retransmission Procedures (see [3])
28 1.1.3 Call Flow Example(s)

29 None
1-1
C.S0044-0 v1.0
1 1.1.4 Method of Measurement
2 1.1.4.1 Persistence Delay for Mobile Station in using ACCOLCP between 0 and 9
3 a. Connect the base station and mobile station as shown in Figure A-3.
4 b. Set ACCOLCP to any value between 0 and 9 in the mobile station.
5 c. Instruct the base station to send an Access Parameters Message or an Enhanced
6 Access Parameters Message in Table 1.1.4-1or Table 1.1.4-2 respectively:
7
8 Table 1.1.4-1 Access Parameters Message Settings
Field Value
PSIST(0-9) ‘000000’
PSIST(11) ‘000’
PSIST_EMG_INCL ‘0’
10 Table 1.1.4-2 Enhanced Access Parameters Message Settings
Field Value
PSIST_PARMS_INCL ‘1’
PSIST_PARMS_LEN As required
PSIST(0-9)_EACH ‘000000’
PSIST_11_EACH ‘000’
PSIST_EMG ’000’
11
12 d. Setup a mobile station originated call.
13 e. Verify the mobile station does not delay sending the Origination Message.
14 f. Verify the call completes and there is user traffic in both directions.
15 g. Setup a mobile station terminated call and verify the mobile station does not delay
16 sending the Page Response Message.
17 h. Change PSIST(0-9) or PSIST(0-9)_EACH in the Access Parameters Message or
18 Enhanced Access Parameters Message to ‘111111’.
19 i. Attempt to setup a mobile station originated call.
20 j. Verify the mobile station does not send an Origination Message.
1-2
C.S0044-0 v1.0
1 k. Set PSIST(0_9) = ‘011000’ or PSIST(0-9)_EACH in the Access Parameters Message or

2 Enhanced Access Parameters Message.
3 l. Setup a mobile station originated call.
4 m. Verify the mobile station does delay sending the Origination Message according to the
5 equations in 1.1.12.
6 n. End the call.

7 o. Setup a mobile station terminated call.
8 p. Verify the mobile station does not delay sending the Page Response Message to the
9 base station.
10 1.1.4.2 Persistence Delay ACCOLCP greater than 9

12 b. Set ACCOLCP = 11 in the mobile station.

14 Access Parameters Message in Table 1.1.4-3 or Table 1.1.4-4respectively:
15
Field Value
PSIST(0-9) ‘000000’
PSIST(11) ‘000’
17
Field Value
PSIST(0-9)_EACH ‘000000’
2
For PSIST test cases, test may need to be repeated, since MS may not delay sending a
message every time. For PSIST testing, it may be necessary to monitor access probe output to
verify that the access attempts are delayed.
1-3
C.S0044-0 v1.0
PSIST_EMG ’000’
1
3 e. Verify the mobile station does not delay sending the Origination Message.
4 f. Verify the call completes and there is user traffic in both directions.
5 g. Setup a mobile station terminated call and verify the mobile station does not delay
6 sending the Page Response Message.
7 h. Change PSIST(11) or PSIST_11_EACH in the Access Parameters Message or
9 i. Attempt to setup a mobile station originated call.
10 j. Verify the mobile station does not send an Origination Message.
11 k. Change PSIST(11) or PSIST_11_EACH in the Access Parameters Message or

13 l. Setup a mobile station originated call.
14 m. Verify the mobile station does delay sending the Origination Message according to the
15 equations in 1.1.13.
16 n. End the call.

18 p. Verify the mobile station does not delay sending the Page Response Message to the
19 base station.
20 1.1.4.3 Emergency Call Attempts

22 b. Instruct the base station to send an Access Parameters Message or an Enhanced
23 Access Parameters Message in Table 1.1.4-5or Table 1.1.4-2 respectively:
24
Field Value
PSIST(0-9) ‘0’
3
For PSIST test cases, test may need to be repeated, since MS may not delay sending a
message every time. For PSIST testing, it may be necessary to monitor access probe output to
verify that the access attempts are delayed.
1-4
C.S0044-0 v1.0
PSIST_EMG ‘111’
Field Value
PSIST(0-9)_EACH ‘000000’
PSIST_EMG ’111’
3 c. Set ACCOLCP = 0-9 in the mobile station.
4 d. Attempt to setup an emergency call.

5 e. Verify the mobile station does not send an Origination Message to the base station.
6 f. End the call.
7 g. Repeat step d after changing PSIST_EMG = ‘110’ in the Access Parameters Message
8 or the Enhanced Access Parameters Message.
9 h. Verify the mobile station delays sending the Origination Message for the emergency
10 call.
11 i. Repeat step d, changing the PSIST_EMG = ‘000’ in the Access Parameters Message
12 or Enhanced Access Parameters Message.
13 j. Verify the mobile station does not delay sending the Origination Message to the base
14 station for the emergency call.
15 1.1.5 Minimum Standard
16 1.1.5.1 Persistence Delay for Mobile Station in using ACCOLCP between 0 and 9
17 The mobile station shall comply with steps e, f, g, j, m, and p.
18 1.1.5.2 Persistence Delay ACCOLCP greater than 9

19 The mobile station shall comply with steps e, f, g, j, m, and p.
20 1.1.5.3 Emergency Call Attempts

21 The mobile station shall comply with steps e, h, and j.
1-5
C.S0044-0 v1.0
1 1.2 Registration Attempts with Different PSIST Settings
2 1.2.1 Definition
5 If the type of the SDU is a request and a registration, P shall be computed by
2 − PSISTs /4 × 2 − REG _ PSISTs if PSISTs ≠ 63

6 P=  ACCOLCp = 0, 1, ..., 9
0 otherwise
7
2 − PSISTs × 2 − REG _ PSISTs if PSISTs ≠ 7

8 P=  ACCOLCp = 10, 11, ..., 15
0 otherwise


18 None

21 b. Set ACCOLCP to any value between 0 and 9 in the Mobile Station.

22 c. Instruct the base station to send the Access Parameters Message or Enhanced Access
23 Parameters Message with the following values.
Field Value
PSIST(0-9) ‘000000’
REG_PSIST ‘000’
25
1-6
C.S0044-0 v1.0
Field Value
PSIST(0-9)_EACH ‘000000’
REG_PSIST_EACH ‘000’
2 d. Set the value of REG_PRD to 29 in the System Parameters Message.

3 e. Verify timer-based registration occurs at the interval specified by REG_PRD.
4 f. Set REG_PSIST or REG_PSIST_EACH = ‘110’ or in the Access Parameters Message
5 or Enhanced Access Parameters Message.
6 g. Verify timer-based registration occurs at longer intervals than specified by REG_PRD.
7 h. Set REG_PSIST or REG_PSIST_EACH = ‘111’ in the Access Parameters Message or

9 i. Verify the mobile station does not send a Registration Message.
10 j. Set ACCOLCP = 11 in the mobile station and repeat steps c through i.

12 The mobile station shall comply with steps e, g, and i.
13 1.3 Short Message Service with Different PSIST Settings
14 1.3.1 Definition
17 If the type of the SDU is a request and a message transmission, except in the case of an
18 emergency message transmission from a mobile station having an ACCOLCp value
19 between 0 and 9 inclusive, P shall be computed by
2 − PSISTs /4 × 2 − MSG _ PSISTs if PSISTs ≠ 63

20 P=  ACCOLCp = 0, 1, ..., 9
0 otherwise
21
2 − PSISTs × 2 − MSG _ PSISTs if PSISTs ≠ 7

22 P=  ACCOLCp = 10, 11, ..., 15
0 otherwise
23
1-7
C.S0044-0 v1.0

2 None




13 b. Set ACCOLCP to any value between 0 and 9 in the Mobile Station.

15 Access Parameters Message with the following parameters:
Field Value
PSIST(0-9) ‘000000’
MSG_PSIST ‘000’
17
Field Value
PSIST(0-9)_EACH ‘000000’
MSG_PSIST_EACH ‘000’
19
20 d. Create a short message at the mobile station, of a length smaller than the maximum
21 message length allowed on the Access Channel, and instruct the mobile station to send
22 the short message to the network.
23 e. Verify the mobile station does not delay sending the Data Burst Message.
1-8
C.S0044-0 v1.0
1 f. Set MSG_PSIST or MSG_PSIST_EACH = ‘110’ in the Access Parameters Message or

2 the Enhanced Access Parameters Message.
3 g. Create a short message at the mobile station, of a length smaller than the maximum
4 message length allowed on the access channel, and instruct the mobile station to send
6 h. Verify the mobile station delays sending the Data Burst Message to the base station
7 over the access channel.
8 i. Set MSG_PSIST or MSG_PSIST_EACH = ‘111’ in the Access Parameters Message or
10 j. Create a short message at the mobile station, of a length smaller than the maximum
11 message length allowed on the access channel, and instruct the mobile station to send
13 k. Verify the mobile station does not send the Data Burst Message.
14 l. Set ACCOLCP = 11 in the mobile station and repeat steps c through k.

16 The mobile station shall comply with steps e, h, and k.
17 1.4 Quick Paging Channel CCI
18 1.4.1 Definition
19 For mobile stations that support the Quick Paging Channel, this test will verify the following: A
20 mobile station using the Quick Paging Channel ‘configuration change indicator’ (CCI) will update
21 its overhead information when the CCI bit is set to on.
22 1.4.2 Traceability (See [4])
23 2.6.2.1.1.3 Slotted Mode Requirements

24 2.6.2.1.2 Quick Paging Channel Monitoring Procedures
25 2.6.2.1.4 Idle Handoff
26 2.6.7.1 Hash Function

27 3.6.2.5 Quick Paging Channel Processing
28 3.7.2.3.2.13 Extended System Parameters Message
29 3.7.2.3.2.14 Extended Neighbor List Message

31 None
1-9
C.S0044-0 v1.0

2 a. Connect two base stations to the mobile station, with the ability to transition either base
3 station power Ior 5 dB above the other, to induce idle handoff from one to the other and
4 back again.
5 1. The Forward Channel from base station 1 has an arbitrary pilot PN offset index
6 P1 and is called Channel 1.
8 P2 and called Channel 2.
9 b. Set the Extended System Parameter Message in both base stations as specified in
10 Table 1.4.4-1.
11
12 Table 1.4.4-1 Test Parameters for Extended System Parameters Message
Field Values
QPCH_SUPPORTED '1' (QPCH is supported)
NUM_QPCH '01' (Number of the QPCH)
QPCH_RATE (indicator rate) '0' (QPCH indicator rate is 4800 bps)
QPCH_POWER_LEVEL_PAGE '101' (same as forward pilot channel)
QPCH_CCI_SUPPORTED '1' [configuration change indicators supported]
QPCH_POWER_LEVEL_CONFIG '101' (same as forward pilot channel)
13
14 c. Set NGHBR_PN for the Extended Neighbor List Message, Neighbor List Message or
15 General Neighbor List Message in both base stations to include the other base station
16 PN.
17 d. Set the Paging Channel data rate for Channels 1 and 2 to 4800 bps.
18 e. Setup Channel 1 and Channel 2 per Table 1.4.4-2.
1-10
C.S0044-0 v1.0
1 Table 1.4.4-2 Test Parameters for Slotted Mode Idle Handoff
Parameter Unit Channel 1 Channel 2
Îor/Ioc dB 0 -5
Pilot E c dB -7 -7
I or
Quick Paging E c dB -7 -7
I or
Ioc dBm/1.23 MHz -75
2
3 f. Slowly (over a period of several seconds, but not more than T31m = 600 seconds round
4 trip) transpose power levels of channel 1 and 2. That is, raise Channel 2 power by 5 dB
5 (to Îor/Ioc = 0 dB), and lower Channel 1 power by 5 dB (to Îor/Ioc = -5 dB). This should
6 cause an idle handoff from Channel 1 to Channel 2.
7 g. Verify the mobile station has performed an idle handoff to Channel 2.
8 h. While the mobile station is idle on Channel 2, instruct the base station 1 to modify an
9 overhead message, thus causing the CCI bits on Channel 1 Quick Paging Channel to
10 be set to ON.
11 i. Cause an idle handoff from Channel 2 to Channel 1.

12 j. Verify that the mobile station does not go to slotted mode until it has updated its
13 overhead configuration.
14 k. Repeat steps a through j with the QPCH_RATE (indicator rate) set to 1 (9600 rate).

16 The mobile station shall comply with the requirement in steps g and j.
17 1.5 Mobile Station Response to Status Request Message

18 1.5.1 Definition
19 This test verifies that that mobile station responds to the Status Request Message correctly.
21 2.6.3.5 Mobile Station Origination Attempt Substate

22 2.6.4.1.2 Service Configuration and Negotiation
23 2.6.4.1.14 Processing the Service Configuration Record
24 2.6.4.1.15 Processing the Non-Negotiable Service Configuration Record
25 2.6.4.2 Traffic Channel Initialization Substate
1-11
C.S0044-0 v1.0

3 2.7.1.3.2.10 Extended Status Response Message

4 2.7.2.3.2.14 Service Connect Completion Message
5 2.7.2.3.2.16 Status Response Message
6 2.7.4 Information Records

7 3.6.3.5 Response to Origination Message
9 3.7.2.3.2.15 Status Request Message

10 3.7.2.3.2.21 Extended Channel Assignment Message
11 3.7.3.3.2.20 Service Connect Message
12 3.7.5.7 Service Configuration
13 3.7.5.20 Non-Negotiable Service Configuration
15 None
17 a. Ensure the mobile station is operating in the Idle State.
18 b. Instruct the base station to send a Status Request Message on the f-csch to request
19 one or more of the information records listed in section 2.7.4 of [4]. Verify that
20 QUAL_INFO_TYPE, QUAL_INFO_LEN and Type-specific fields in Status Request
21 Message are set to appropriate values.
22 c. Verify the following:
23 1. If P_REV_IN_USE is greater than 3:
24 a. The mobile station sends an Extended Status Response Message with

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

2 appropriate QUAL_INFO_TYPE, QUAL_INFO_LEN, Type-specific
3 fields set to appropriate value, and requested information record(s)
4 included; or
5 b. The mobile station sends a Mobile Station Reject Order with ORDQ =
6 6 if the mobile station does not support the band class and/or operating
7 mode specified in the Status Request Message; or
8 c. The mobile station sends a Mobile Station Reject Order with ORDQ =
9 8 if the information record would exceed the allowable length; or
10 d. The mobile station sends a Mobile Station Reject Order with ORDQ =
11 9 if the information record is not supported for the specified band class
12 and operating mode.
13 d. Set up a mobile originated call.
14 e. Instruct the base station to send a Status Request Message on the f-dsch to request
15 one or more of the information records listed in section 2.7.4 of [4].
16 f. Verify the following:
17 1. The mobile station sends a Status Response Message with the appropriate band
18 class, operating mode, and information record; or
19 2. The mobile station sends a Mobile Station Reject Order with ORDQ = 6 if the
20 mobile station does not support the band class and/or operating mode specified
21 in the Status Request Message; or
22 3. The mobile station sends a Mobile Station Reject Order with ORDQ = 9 if the
23 information record is not supported for the specified band class and operating
24 mode.
26 The mobile station shall comply with steps c and f.
27 1.6 SYNC Channel Support for Mobile Stations not capable of TD, or not capable of
28 QPCH or RC>2
29 1.6.1 Definition
30 This test verifies that the mobile station is able to respond correctly to the new fields of Sync
31 Channel Message sent by the base station if any, tune to appropriate CDMA channel and acquire
32 the system successfully.

34 2.6.1.3 Sync Channel Acquisition Substate
35 3.7.2.3.2.26 Sync Channel Message
1-13
C.S0044-0 v1.0

2 None
4 1.6.4.1 Base Station capable of Non-TD BCCH but not TD (Case 1)

5
6 Table 1.6.4-1 Frequency Allocation
Case 1 Case 2 Case 3
CDMA_FREQ 1 1 1
EXT_CDMA_FREQ 2 2 2
SR1_CDMA_FREQ_NON_TD 3 N/A 3
SR1_CDMA_FREQ_TD N/A 4 4
7 a. Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC
8 to 1.
9 b. At the base station, Set Pilot PN offset to a certain value.
10 c. Verify that the mobile station acquires the Forward pilot channel correctly.
11 d. Verify the mobile station receives a Sync Channel Message with frequency allocation
12 according to Table 1.6.4-1.
13 e. Verify that the mobile station tunes to CDMA Channel 3.

14 f. Make a Mobile-Originated voice call and verify audio in both directions.
15 g. End the call.
16 1.6.4.2 Base Station capable of TD but not Non-TD BCCH (Case 2)

18 to 1.
21 d. Verify the mobile station receives a Sync Channel Message frequency allocation
25 g. End the call.
1-14
C.S0044-0 v1.0
1 1.6.4.3 Base Station capable of Non-TD BCCH and TD (Case 3)

3 to 1.
10 g. End the call.

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


18 1.7 Sync Channel support for Mobile Stations not capable of TD, but capable of QPCH
19 or RC>2
20 1.7.1 Definition


28 None

31
1-15
C.S0044-0 v1.0
Case 1 Case 2 Case 3
CDMA_FREQ 1 1 1
EXT_CDMA_FREQ 2 2 2
SR1_CDMA_FREQ_NON_TD 3 N/A 3
SR1_CDMA_FREQ_TD N/A 4 4
4 to 1.

11 g. End the call.

14 to 1.
21 g. End the call.

24 to 1.
1-16
C.S0044-0 v1.0
5 g. End the call.



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


22 None
Case 1 Case 2 Case 3 Case 4 Case 5
CDMA_FREQ 1 1 1 14 1
4
This is a pseudo frequency, no corresponding channel elements are needed.
1-17
C.S0044-0 v1.0
EXT_CDMA_FREQ 2 2 2 2 2
SR1_CDMA_FREQ_NON_TD 3 N/A N/A 3 3
SR1_CDMA_FREQ_TD N/A 4 4 4 4
2 to 1.

9 g. End the call.
10 1.8.4.2 Base Station capable of TD with the same TD mode as Mobile Station but not Non-TD
11 BCCH (Case 2)
13 to 1.

20 g. End the call.
21 1.8.4.3 Base Station capable of TD with different TD mode as Mobile Station but not Non-TD
22 BCCH (Case 3)
24 to 1.

1-18
C.S0044-0 v1.0
1 g. End the call.
2 1.8.4.4 Base Station capable of Non-TD BCCH and TD with the same TD mode as Mobile
3 Station (Case 4)
5 to 1.
12 g. End the call.
13 1.8.4.5 Base Station capable of Non-TD BCCH and TD with a different TD mode as Mobile
14 Station (Case 5)
16 to 1.

23 g. End the call.

27 1.8.5.2 Base Station capable of TD with the same TD mode as Mobile Station but not Non-TD
28 BCCH (Case 2)
30 1.8.5.3 Base Station capable of TD with different TD mode as Mobile Station but not Non-TD
31 BCCH (Case 3)
1-19
C.S0044-0 v1.0
1 1.8.5.4 Base Station capable of Non-TD BCCH and TD with the same TD mode as Mobile
2 Station (Case 4)
4 1.8.5.5 Base Station capable of Non-TD BCCH and TD with a different TD mode as Mobile
5 Station (Case 5)
7 1.9 Hashing F-CCCH, F-CCCH slot
8 1.9.1 Definition
9 This test checks the ability to set and detect hashed F-CCCHs and F-CCCH Slots. The IMSI’s
10 effect on hashed F-CCCH and Slot is also checked.
11 1.9.2 Traceability: (See [4])

13 3.6.2.1.2 Common Channel Determination
14 3.6.2.1.3 Paging Slot Determination

16 None
17 1.9.4 Methods of Measurement
18 1.9.4.1 F-CCCH Number Hashing
20 b. Configure the base station system with multiple F-CCCHs (maximum seven) in MC-RR
21 Parameters Message.
22 c. Make a mobile terminated call, and verify audio in both directions.
23 1.9.4.2 F-CCCH Slot Number Hashing

25 b. Configure the base station system with slotted mode capability.
26 c. Make a mobile terminated call, and verify audio in both directions.
28 1.9.5.1 F-CCCH Number Hashing

29 The mobile station shall comply with step c.
30 1.9.5.2 F-CCCH Slot Number Hashing

31 The mobile station shall comply with step c.
1-20
C.S0044-0 v1.0
1 1.10 CDMA Channel Hashing on F-PCH for Mobile Stations not capable of QPCH or RC>2
2 1.10.1 Definition
3 This test checks the mobile station’s ability to do CDMA Channel hashing based on different
4 capability sets to select appropriate CDMA Channel and associated PCH.

6 2.6.2.2 Response to Overhead Information Operation
7 2.6.2.2.12.1 Extended CDMA Channel List Message on Paging Channel

9 3.6.2.1.1 CDMA Channel Determination
10 3.7.2.3.2.28 Extended CDMA Channel List Message

12 None
13 1.10.4 Methods of Measurement
14 1.10.4.1 Base Station incapable of BCCH and QPCH or RC>2 (Case 1)

15 a. Turn off all forms of autonomous registration at the base station.
16 b. Connect the base station and mobile station as shown in Figure A-4, and configure the
17 base station with 1 Paging Channel on each of the 2 CDMA channels.
18 c. Verify that the base station sends either a CDMA Channel List Message or an Extended
19 CDMA Channel List Message with RC_QPCH_SEL_INCL=’0’, TD_SEL_INCL=’0’ and
20 NUM_FREQ=’0010’ from the base station.
21 d. Make a mobile terminated call, and verify audio in both directions.
22 1.10.4.2 Base Station incapable of BCCH, capable of QPCH or RC>2 with Extended CDMA
23 Channel List Message sent (Case 2)
27 c. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=’1’,
28 TD_SEL_INCL=’0’ and NUM_FREQ=’0010’ from the base station and make sure
29 RC_QPCH_HASH_IND is set to ‘1’ for freq 1 and 2.
32 1.10.5.1 Base Station incapable of BCCH and QPCH or RC>2 (Case 1)

33 The mobile station shall comply with step d.
1-21
C.S0044-0 v1.0
4 1.11 CDMA Channel Hashing on F-PCH for Mobile Stations capable of QPCH or RC>2
5 1.11.1 Definition
6 This test checks the mobile station’s ability to do CDMA Channel hashing based on different
7 capability sets to select appropriate CDMA Channel and associated PCH.

10 2.6.2.2.12.1 Extended CDMA Channel List Message on Paging Channel


15 None
17 1.11.4.1 Base Station incapable of BCCH and QPCH or RC>2 with Extended CDMA Channel
18 List Message sent (Case 1)
23 TD_SEL_INCL=’0’ and NUM_FREQ=’0010’ from the base station.
1-22
C.S0044-0 v1.0
2 1.11.5.1 Base Station incapable of BCCH and QPCH or RC>2 with Extended CDMA Channel
3 List Message sent (Case 1)
8 1.12 CDMA Channel Hashing on F-BCCH; Mobile Station not capable of either TD or
9 QPCH (RC>2)
10 1.12.1 Definition
11 This test checks the mobile station’s ability to do CDMA Channel (frequency) hashing based on
12 different capability sets to select appropriate CDMA Channels and associated primary BCCHs.
13 1.12.2 Traceability (see 4)
14 2.6.2.1.5 Primary Broadcast Control Channel Monitoring

16 2.6.2.2.12.2 Extended CDMA Channel List Message On Primary Broadcast Control Channel

21 None
23 1.12.4.1 Base station operates without TD and QPCH, RC>2 (Case 1)

26 base station with 1 primary BCCH on each of the 2 CDMA channels.
30 1.12.4.2 Base Station operates without TD (STS) but with QPCH (RC>2), (Case 2)
1-23
C.S0044-0 v1.0
5 RC_QPCH_HASH_IND is set to ‘1’ for freq 1 and 2
7 1.12.4.3 Base Station operates with TD (STS) and QPCH (RC>2) (Case 3)
13 TD_HASH_IND is set to ‘1’ for frequency 1 and RC_QPCH_HASH_IND is set to ‘1’ for
14 frequency 1 and 2.
17 1.12.5.1 Base station operates without TD and QPCH, RC>2 (Case 1)

19 1.12.5.2 Base Station operates without TD (STS) but with QPCH (RC>2), (Case 2)
23 1.13 CDMA Channel Hashing on F-BCCH; Mobile Station not capable of TD (STS) but
24 capable of QPCH (RC>2)


33 CDMA Channel Determination
1-24
C.S0044-0 v1.0

3 None
5 1.13.4.1 Base Station operates without TD (STS) and QPCH (RC>2) (Case 1)
12 1.13.4.2 Base Station operates without TD (STS) but with QPCH (RC>2) (Case 2)
26 TD_HASH_IND is set to ‘1’ for frequency 1 and RC_QPCH_HASH_IND is set to ‘1’ for
27 frequencies 1 and 2.
30 1.13.6 Base Station operates without TD (STS) and QPCH (RC>2) (Case 1)
32 1.13.7 Base Station operates without TD (STS) but with QPCH (RC>2) (Case 2)
1-25
C.S0044-0 v1.0
1 1.13.8 Base Station operates with TD (STS) and QPCH (RC>2) (Case 3)
3 1.14 CDMA Channel Hashing on F-BCCH; Mobile Station capable of both TD (STS) and
4 QPCH (RC>2)
5 1.14.1 Definition


16 None

18 None
32 RC_QPCH_HASH_IND is set to ‘1’ for frequency 1 and 2.
1-26
C.S0044-0 v1.0
8 TD_HASH_IND is set to ‘1’ for frequency 1 and 2, RC_QPCH_HASH_IND is set to ‘1’
9 for all the frequencies.
18 1.15 F-CCCH SUPPORT
20 This test checks the mobile station’s ability to process messages (L2 ACK, Extended Channel
21 Assignment Message) sent over F-CCCH correctly.

23 2.6.2.1.1 Forward Channel Monitoring Procedures
24 2.6.2.1.1.4 Common Channel Supervision
25 2.6.3.1.8 Paging Channel and Forward Common Control Channel Monitoring

27 None

30 b. Instruct the mobile station originate a voice call.
1-27
C.S0044-0 v1.0
1 c. Verify the base station respond with a Layer 2 ACK and Extended Channel Assignment
2 Message over F-CCCH.
3 d. Verify the mobile station can set up the traffic channel for this voice call correctly.

6 1.16 Paging Indicator on the Quick Paging Channel
7 1.16.1 Definition
8 For mobile stations that support the Quick Paging Channel, this test will verify the following:
9 The mobile station shall hash to the correct paging indicator positions. The mobile station shall
10 monitor its assigned Paging Channel or F-CCCH slot immediately following its assigned Quick
11 Paging Channel slot if the mobile station does not detect that at least one of the paging indicators
12 is set to “OFF”. Therefore, if the mobile station detects zero, one or two “ON” in the hashed
13 paging indicators without detecting an “OFF”, the mobile station will monitor its assigned Paging
14 Channel or F-CCCH slot5. It is assumed that if the mobile station hashes to the wrong paging
15 indicator positions and detected an “OFF”, the mobile station would likely miss the assigned
16 Paging Channel or the F-CCCH slot.

18 2.6.2.1.2 Quick Paging Channel Monitoring Procedures.
20 2.7.1.3.2.1 Registration Message
21 3.6.2.5 Quick Paging Channel Processing
23 3.7.2.3.2.31 MC-RR-Parameters Message

25
5
Although the mobile station will monitor the Paging Channel or the F-CCCH when the paging
indicator is detected as “ON” (without detecting an “OFF”), there are other reasons the mobile
station may monitor the Paging Channel or the F-CCCH even if the mobile station does not detect
an “ON” for the paging indicators. For example, the mobile station may not operate the QPCH
properly such that neither “ON” nor “OFF” is detected or the mobile station’s threshold for
detecting the paging indicators is set too high. Even if the mobile station hashes to the wrong
paging indicator positions and detected an “OFF” there is no requirement that the mobile station
shall not monitor the Paging Channel or the F-CCCH.
1-28
C.S0044-0 v1.0
MS BS
Com m on Com m on
Channels C hannels
The M S hash to Q PI Turn on/off PI on Q uick Paging Channel
positions and detect its for the M S assigned Q PCH Slot
Q PI on in the Assigned
Q PCH Slot. Then the M S
start receiving on its
assigned F-PC H or
F-CC CH slots Registration Request order
Registration M essage
1
2

4 a. Connect the mobile station to the base station as shown in Figure A-3.
5 b. Set the values in the Extended System Parameters Message or MC-Parameters

6 Message as follows:
7
Fields Values
QPCH_SUPPORTED '1' (QPCH is supported)
NUM_QPCH '01' (Number of the QPCH)
QPCH_RATE '0' (4800 bps QPCH data rate)
QPCH_POWER_LEVEL_PAGE '101' (same as pilot channel)
8 c. Allow the mobile station to begin monitoring the QPCH.
9 d. Instruct the base station to send a mobile station directed message (i. e. General Page
10 Message or Registration Request Order) in the mobile station’s assigned Paging
11 Channel or F-CCCH slot.
12 e. Verify that the base station sets the paging indicator positions associated with the
13 mobile station to “ON” in the Quick Paging Channel slot corresponding to the Paging
14 Channel or F-CCCH slot in which the mobile station directed message is sent in step d.
15 Ensure the base station sets the other paging indicator positions to “OFF”.
16 f. Verify the mobile station correctly responds to the message directed to it in step d.
17 g. Repeat steps b through f with the QPCH_RATE set to ‘1’ (9600 bps).

19 The mobile station shall comply with step f. The base station shall comply with step e.
1-29
C.S0044-0 v1.0
1 2 BASIC CALL PROCESSING TESTS
2 2.1 Mobile Originated Voice Calls
3 2.1.1 Definition
4 This tests voice service negotiation and call completion of mobile originated voice calls, for radio
5 configurations and voice service options supported by the mobile and base station.
7 2.2.6.2.5 Mobile Station Origination Operation

9 2.6.4 Mobile Station Control on the Traffic Channel State

11 2.7.2.3.2.15 Service Option Control Message
13 3.6.4 Traffic Channel Processing

15 3.7.3.3.2.3 Alert With Information Message

17 2.7.2.3.2.12 Service Request Message
18 2.7.2.3.2.13 Service Response Message

20 2.7.4.18 Service Configuration Record
2-1
C.S0044-0 v1.0
MS BS
Origination Message (SO, RCs proposed) common

channels
Order Message (acknowledgement from base station)
Extended Channel Assignment Message

(DEFAULT_CONFIG, GRANTED_MODE, RCs)
initial service possible service negotiation
configuration
Service Connect Message

Service Configuration Record (SO, RCs)
dedicated
possible new channels
Service Connect Completion Message
service
configuration
Voice Traffic
release order messages

common
channels

4 a. Configure the base station for desired voice service negotiation listed in Table 2.1.4-2.
5 b. Allow the mobile to come to the idle state on the base station.
6 c. Make a mobile originated voice call, and record the call setup messages listed in Table
7 2.1.4-1.
8 Table 2.1.4-1 Messages in Mobile Originated Call Setup
Item Message
1 Origination Message
2 Extended Channel Assignment Message
3 Status Request Message
4 Status Response Message
5 Service Request Message
6 Service Response Message
7 Service Connect Message
2-2
C.S0044-0 v1.0
8 Service Connect Complete Message
2 d. Verify SERVICE_OPTION, FOR_RC_PREF, and REV_RC_PREF proposed in the

3 Origination Message correspond to the mobile configuration settings.
4 e. Verify DEFAULT_CONFIG, GRANTED_MODE, FOR_RC, and REV_ RC in the

5 Extended Channel Assignment Message corresponds to the base station configuration
6 for service negotiation.
7 f. Verify service negotiation used in Service Request Message, Service Response
8 Message, and Service Connect Message proceed as desired.
9 g. Verify the SERVICE_OPTION, FOR_FCH_RC, and REV_FCH_RC in the last Service
10 Configuration Record corresponds to the desired outcome of the base station service
11 negotiation configuration, and the call completes successfully.
12 h. End the call.
13 i. Repeat steps a through h for all supported configurations of mobile originated voice
14 service negotiation as supported by the mobile station and base station. This may
15 include call completion with the service configurations in Table 2.1.4-2.
16 Table 2.1.4-2 Service Configurations for Mobile Originated Voice Calls
Voice Service Option Forward Radio Reverse Radio

Configuration Configuration
3 1 1
2 2
17 or 32768
3 3 3
3 4 3
17 or 32768 5 4
17

19 The mobile station and the base station shall comply with step d, e, f, g, and i.
20 2.2 Mobile Station Terminated Voice Calls
21 2.2.1 Definition
22 This tests voice service negotiation and call completion of mobile station terminated voice calls,
23 for radio configurations and voice service options supported by the mobile station and base
24 station.
2-3
C.S0044-0 v1.0
1 2.2.2 Traceability


9 2.7.2.3.2.12 Service Request Message

12 2.7.4.18 Service Configuration Record
MS BS
General Page Message (SO proposed) common

channels
Page Response Message (SO, RCs proposed)

(DEFAULT_CONFIG, GRANTED_MODE, RCs)
configuration
Service Configuration Record (SO, RCs)
dedicated
possible new channels
Service Connect Completion Message
service
configuration
Voice Traffic
Release Order Messages

common
channels
14

16 a. Configure the base station for desired SERVICE_OPTION for the General Page
17 Message or Universal Page Message, and desired service negotiation listed in Table
18 2.2.4-2.
2-4
C.S0044-0 v1.0
1 b. Allow the mobile station to come to the idle state on the base station.
2 c. Make a mobile station terminated voice call, and record the call setup messages listed
3 in Table 2.2.4-1.
4 Table 2.2.4-1 Messages in Mobile Station Terminated Call
Item Message
1 General Page Message or Universal Page Message
2 Page Response Message
4 Status Request Message
5 Status Response Message
6 Service Request Message
7 Service Response Message
8 Service Connect Message
9 Service Connect Complete Message
5
6 d. Verify the SERVICE_OPTION proposed in the General Page Message corresponds to
7 the base station configuration setting.
8 e. Verify SERVICE_OPTION, FOR_RC_PREF, and REV_RC_PREF proposed in the

9 Origination/Page Response Message correspond to the mobile station configuration
10 settings.
11 f. Verify DEFAULT_CONFIG, GRANTED_MODE, FOR_RC, and REV_RC in the
12 Extended Channel Assignment Message correspond to the base station configuration.
13 g. Verify that service negotiation using in Service Request Message, Service Response
14 Message, and Service Connect Message proceed as desired.
15 h. Verify the SERVICE_OPTION, FOR_FCH_RC, and REV_FCH_RC in the last Service
16 Configuration Record corresponds to the desired outcome of the base station service
17 negotiation configuration, and the call completes successfully.
18 i. End the call.
19 j. Repeat steps a through i for all supported configurations of mobile station terminated
20 voice service negotiation as supported by the mobile station and base station. This
21 may include call completion with the service configurations in Table 2.2.4-2.
2-5
C.S0044-0 v1.0
1 Table 2.2.4-2 Minimum Service Combinations for Mobile station Terminated Voice Calls
Service Option Forward Radio Reverse Radio

Configuration Configuration
3 1 1
17 or 32768 2 2
3 3 3
3 4 3
17 or 32768 5 4

4 The mobile station and the base station shall comply with steps d, e, f, g, h, and j.
5 2.3 Busy Tone
6 2.3.1 Definition
7 This tests the mobile station response to a called-party-busy notification from a base station.
9 2.6.4.4 Release Substate

10 3.6.4.3 Traffic Channel Substate
12 Table 3.7.5.5-3 Tone Signals

14 None

16 a. Allow the mobile station to come to the idle state on the base station.
17 b. Ensure the called party has no call-waiting or automatic voice mail enabled, and tie up
18 the line so that the mobile station will get a busy signal when it calls.
19 c. Attempt a mobile station originated call to the party.
20 d. Verify the mobile station plays a called-party-busy indication.

22 The mobile station shall comply with the requirement in steps d.
2-6
C.S0044-0 v1.0
1 2.4 Mobile Station Origination Call with Inter Band Channel Assignment
2 2.4.1 Definition
3 This test verifies that the mobile station can initiate a call to a land party on aone band class and
4 then re-originate and completes the call the target band class after receiving a Channel
5 Assignment Message or Extended Channel Assignment Message with ASSIGN_MODE = ‘101’
6 or ‘001’ respectively.

8 2.6.2.4 Mobile Station Order and Message Processing Operation

11 3.7.2.3.2.8 Channel Assignment Message

14 None

16 a. Connect the mobile station and base stations as shown in Figure A-2. Base station 1
17 operates in a band class that is different from base station 2.
18 b. Ensure the mobile station acquires base station 1.
19 c. Configure Base station 1 so that Inter Band Channel Assignment is enabled.
20 d. Setup mobile station originated voice call.

21 e. Verify the mobile station originates on the serving base station and receives a Channel
22 Assignment Message with ASSIGN MODE=‘101’ or an Extended Channel Assignment
23 Message with ASSIGN MODE=’001’. Verify that the Channel Assignment Message or
24 Extended Channel Assignment Message contains assignment for paging channel on
25 base station 2, and RESPOND=1.
26 f. Verify the mobile station re-sends a second Origination Message to base station 2 and
27 the call completes successfully.
28 g. Verify user data in both directions.
29 h. End the call.
30 i. Repeat Steps d through g, but provision Base station 2 to be Inter Band Channel
31 Assignment enabled. The mobile station will originate on base station 2 and then re-
32 originate on base station 1 after receiving the Channel Assignment Message or
33 Extended Channel Assignment Message.

35 The mobile station and base station shall comply with steps e, f, g, and i.
2-7
C.S0044-0 v1.0
1 2.5 Mobile Station Terminated Call with Inter Band Channel Assignment
2 2.5.1 Definition
3 This test verifies that the mobile station can receive a call from a land party on one band class
4 and then resends the Page Response Message autonomously and completes the call on the
5 target band class after receiving a Channel Assignment Message or Extended Channel
6 Assignment Message with ASSIGN_MODE = ‘101’ or ‘001’ respectively.

8 2.6.2.3 Mobile Station Page Match Operation
9 2.6.3.3 Page Response Substate


14 None

17 operates in a band class that is different from base station 2.
18 b. Ensure the mobile station acquires base station 1.
19 c. Configure base station 1 so that Inter Band Channel Assignment is enabled.
20 d. Setup mobile station terminated voice call.

21 e. Verify that the mobile station receives a Channel Assignment Message with ASSIGN
22 MODE=‘101’ or an Extended Channel Assignment Message with ASSIGN
23 MODE=’001’. Verify that the Channel Assignment Message or Extended Channel
24 Assignment Message contains assignment for paging channel on base station 2, and
25 RESPOND = ‘1’.
26 f. Verify the mobile station sends a second Page Response Message on the target base
27 station and the call completes.
29 h. End the call.
30 i. Repeat Steps d through g, but provision Base station 2 to be Inter Band Channel
31 Assignment enabled. The mobile station will send the Page Response Message on
32 base station 2 and then re-send the Page Response Message on base station 1 after
33 receiving the Channel Assignment Message or Extended Channel Assignment
34 Message.
2-8
C.S0044-0 v1.0

2 The mobile station and the base station shall comply with steps e, f, g, and i.
3 2.6 DTMF
4 2.6.1 Definition
5 This is a test for Dual-Tone Multi-frequency (DTMF), sent by the mobile station in a Send Burst
6 DTMF Message or a Continuous DTMF Tone Order. It verifies that sequencing and tone duration
7 of the Send Burst DTMF Message and the Continuous DTMF Tone Order are preserved.

9 2.7.2.3.2.7 Send Burst DTMF Message
10 2.7.2.3.2.1 Continuous DTMF Tone Order
12 Table 2.7.1.3.2.4-4 Representation of DTMF Digits
13 Table 2.7.2.3.2.7-1 Recommended DTMF Pulse Width
14 Table 2.7.2.3.2.7-2 Recommended Minimum Inter-digit Interval
15 Table 3.7.4-1 Order and Order Qual Codes Used on the f-csch and the f-dsch
16 Table 2.7.2.3-1 Messages on r-dsch

18 None

20 a. Equip a landline with a DTMF decoder that can verify DTMF digits received and DTMF
21 tone duration.
22 b. Configure the mobile station to send short DTMF tones.

23 c. Allow the mobile station to come to the idle state on the base station, and set up a voice
24 call to the equipped land party.
25 d. Press the keys 1234567890*#.
26 e. Verify the mobile station sends a Send Burst DTMF Message for each key press.
27 f. Verify DTMF tones are received correctly.
28 g. End the call.

29 h. Configure the mobile station to use long DTMF tones.
30 i. Setup a mobile station originated call.
31 j. Direct the mobile station to perform the following steps in .
32 1. Press and hold any number key on the keypad for approximately 5 seconds.
2-9
C.S0044-0 v1.0
1 2. Verify the mobile station sends a Continuous DTMF Tone Order with the
2 appropriate ORDQ value to start and stop the DTMF tone.
3 3. Direct the mobile station to send characters 0123456789 * as one or more Send
4 Burst DTMF Message(s).
5 4. Press and hold any number key on the keypad for approximately 5 seconds.
6 5. Again press and hold any number key on the keypad for approximately 5
7 seconds.
8 k. Verify all DTMF digits are decoded correctly and in the right order at the land party
9 DTMF decoder.
10 l. Verify the three 5-second key presses produce DTMF tones approximately 5 seconds in
11 duration.

13 The mobile station shall comply with requirements in steps e, f, k and l.
14 2.7 Slot Cycle Index
15 2.7.1 Definition
16 If the mobile station supports slotted operation, this test verifies the mobile station response to the
17 base station MAX_SLOT_CYCLE_INDEX setting for various settings of mobile station
18 SLOT_CYCLE_INDEX.

20
21 2.6.2.1.1 Forward Channel Monitoring Procedures

22 3.6.2.1.3 Paging Slot Determination
23 3.6.2.3 Mobile Station Directed Messages
27 2.7.4.7 Terminal Information

29 None

31 a. Configure the mobile station internal setting of SLOT_CYCLE_INDEXP and also base
32 station System Parameter Message or MC-RR Parameters Message setting of
33 MAX_SLOT_CYCLE_INDEX in the first row in Table 2.7.4-1.
2-10
C.S0044-0 v1.0
1 Table 2.7.4-1 Mobile station and Base Station Settings for Slot Cycle Index Test
Test_ID MAX_SLOT_CYCLE SLOT_CYCLE Slot Cycle Slot Cycle

_INDEX (base _INDEXP (mobile Index Used Length,
station) station) seconds
1 2 0 0 1.28
2 2 1 1 2.56
3 2 2 2 5.12
4 2 3 2 5.12
5 3 3 3 10.14
2 b. Allow the mobile station to come to the idle state in slotted mode on the base station.
3 c. Examine that the mobile station wakes up in the assigned slots to read the Paging
4 Channelat the interval of the Slot Cycle Length in Table 2.7.4-1.
5 d. Make a mobile station terminated call, verify the base station pages the mobile station
6 in the appropriate slot.
7 e. Verify the call completes successfully.

8 f. Repeat steps a through d for each of the other row Test ID combinations in Table
9 2.7.4-1.

11 The mobile station and the base station shall comply with requirements in steps c, d, e and f.
12 2.8 Reverse Radio Link Failure
13 2.8.1 Definition
14 2.8.2 This tests mobile station’s response to a 15 second loss of the reverse RF link in the
15 conversation state. Traceability
16 3.7 Supervision [see (6)]

17 Table 2.2.1.1.3-1 Accumulated ARQ Statistics for Regular PDUs (see [3])
2-11
C.S0044-0 v1.0
MS BS
Origination Message

common
channels

configuration
dedicated
possible new Service Connect Complete Message channels
service
configuration
Voice Traffic

4 a. Configure a test setup with a connection of a single base station and the mobile station
5 to allow the reverse radio link to be abruptly attenuated or interfered-with, enough to
6 cause continuous loss of all reverse frames as exemplified in Figure 2-1
Forward Link
Fixed Atten Duplexer Duplexer Vari Atten
Reverse Link AWGN
base station 1
CDMA Analyzer
Diagnostic and Control Tool Mobile

7
8 Figure 2-1 Test Setup for Radio Link Failure
9 b. Configure the setup for good RF links as specified in ANNEX B.
10 c. Allow the mobile station to come to the idle state on the base station.
11 d. Attempt a mobile station originated call.
12 e. Abruptly cause loss of the reverse RF link after voice call is established.
2-12
C.S0044-0 v1.0
1 f. Restore the normal RF link after a minimum of 15 seconds.

2 g. Verify the call is released.
3 h. Verify the mobile station returns to the idle state on the base station.

5 The mobile station shall comply with the requirements in steps g and h.
6 2.9 Channel Assignment from CDMA to Analog
7 2.9.1 Definition
8 This test will verify that a base station assigns a mobile station to analog (e.g. AMPS) when no
9 CDMA traffic channels are available.
11 2.6.1.1.2 System Selection Using Current Redirection Criteria


14 None

16 a. Connect the base station and mobile station as shown in Annex A Figure A - 5.
17 b. Take all CDMA traffic channel radio resources out of service or configure the base
18 station to behave in a similar fashion. Configure the base station to assign analog
19 channel.
20 c. Setup a mobile station originated call.

21 d. Verify that the base station sends a Channel Assignment Message or Extended
22 Channel Assignment Message with ASSIGN_MODE=‘011’ to assign the mobile station
23 an analog voice channel or with ASSIGN_MODE=‘010’ to acquire the analog system.
24 e. Verify the mobile station acquires the analog system.
25 f. Verify user data in both directions.
26 g. End call.

28 The mobile station and the base station shall comply with the requirements in steps d, e, and f.
2-13
C.S0044-0 v1.0
1 2.10 Network Busy
2 2.10.1 Definition
3 This tests mobile station response to a base station blocking condition during mobile station call
4 origination.

6 Table 3.7.4-1 Order and Order Qualification Codes
7 3.6.2.3 Mobile Station Directed Messages, Reorder Order
8 Table 3.7.5.5-3 Tone Signals


12 None

15 b. Take all traffic channel resources out of service or configure the base station to behave
16 in a similar fashion. Configure the base station to send a network-busy indication.
17 c. Attempt a mobile station originated call.
18 d. Instruct the base station to send a Reorder Order to the mobile station.
19 e. Verify the mobile station indicates a call failure due to network-busy, (e.g. For voice
20 service options, the mobile station will play a reorder tone ). Note any anomalies in the
21 mobile station behavior due to receiving the Reorder Order..
22 f. Steps a through e may be repeated for different service options supported such as
23 service option 33.

25 The mobile station shall comply with the requirements in step e for all tested service options.
26 2.11 Release Order on the Access Channel
28 This test verifies the mobile station can send a Release Order on the Access Channel during call
29 origination before switching to dedicated channel transmission.
30 2.11.2 Traceability (see [4] unless otherwise noted)
31 3.6.3 Access Channel Processing

32 3.6.3.4 Response to Orders
2-14
C.S0044-0 v1.0
1 2.6.3 System Access State

2 2.6.3.1.4 System Access State Exit Procedures

4 2.1.1.2.2.1 Overview of Transmission and Retransmission Procedures (see [3])
MS BS
Origination Message
Ack Order
Common
Release Order Channels
Order

9 b. Attempt a mobile station originated call.

10 c. Shortly after the mobile station has received acknowledgement of its Origination
11 Message, terminate the call attempt from the mobile station side, e. g. press the mobile
12 station END key, before the mobile station switches to dedicated channel transmission.
13 d. Verify the mobile station sends a Release Order (normal release) on the Access
14 Channel in assured mode requiring confirmation of delivery, aborts the call attempt, and
15 returns to the idle state on the base station.

17 The mobile station shall comply with the requirements in step d.
19 True IMSI addressing supported by the base station and mobile station
21 This test verifies that the base station pages the mobile station with True IMSI addressing
22 supported by the base station and mobile station when the MCC and IMSI_11_12 of the mobile
23 station match those sent by the base station in the Extended System Parameters Message or
24 ANSI-41 System Parameters Message.
26 2.3.1.1 Encoding of IMSI_M_S and IMSI_T_S

27 2.3.1 Mobile Station Identification Number
28 2.3.1.3 Encoding of the MCC_M and MCC_T
2-15
C.S0044-0 v1.0
1 2.6.2.2.5 Extended System Parameters Message

2 2.7.4.24 IMSI_T

5 None

8 b. Ensure the mobile station is programmed with the same values of MCC and
9 IMSI_11_12 used in the base station. Do not use MCC (wild card) value in the base
10 station.
11 c. Configure the base station to send the Extended System Parameters Message or
12 ANSI-41 System Parameters Message with the value IMSI_T_SUPPORTED=1.
13 d. Enable power-up registration.
14 e. Enable authentication. Configure the base station to disallow mobile station terminated
15 calls if authentication fails.
16 f. Power on the mobile station and wait for power-up registration to occur.
17 g. Initiate a land party to mobile station call.

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

20 The mobile station shall comply with step h.
22 True IMSI addressing supported by the base station with MIN-based addressing
23 supported by the mobile station.
25 This test verifies that the base station pages the mobile station with True IMSI addressing
26 supported by the base station and MIN-based addressing supported by the mobile station when
27 the MCC and IMSI_11_12 of the mobile station match those sent by the base station in the
28 Extended System Parameter Message or ANSI-41 System Parameters Message.

2-16
C.S0044-0 v1.0
1 2.7.4.24 IMSI_T

4 None

9 station.
12 d. Enable power on registration.
16 g. Initiate a land party call to the mobile station.
17 h. Verify user data and end call at the mobile station.

21 True IMSI addressing not supported by the base station
23 This test will verify the base station pages the mobile station when the base station does not
24 support True IMSI addressing, when the MCC and IMSI_11_12 of the mobile station match those
25 sent by the base station in the Extended System Parameters Message or ANSI-41 System

32 2.7.4.24 IMSI_T
2-17
C.S0044-0 v1.0

2 None

7 station.


18 2.15 True IMSI Support, Land Party to Mobile Station Call, Different MCC and IMSI_11_12
20 This test verifies the base station selects one of the valid forms of paging channel address when
21 neither the MCC nor the IMSI_11_12 of the mobile station being addressed match those being
22 sent by the base station in the Extended System Parameters Message or ANSI-41 System


29 2.7.4.24 IMSI_T

32 None
2-18
C.S0044-0 v1.0

3 b. Ensure the mobile station is programmed with different values of MCC and IMSI_11_12
4 than those used in the base station. Do not use MCC (wild card) value in the base
5 station.

16 2.16 PACA Origination, User Terminates While Still In Queue
18 This test verifies that a PACA-capable mobile station, upon failure to originate a call due to lack of
19 available voice/traffic channels, shall re-attempt the origination using the PACA feature code. It
20 verifies that a currently queued mobile station properly informs the base station when a user
21 aborts waiting for traffic channel.

23 2.6.2 Mobile Station Idle State
24 2.6.2.8 Mobile Station PACA Cancel Operation
27 2.7.1.3.2.9 PACA Cancel Message
28 3.7.2.3.2.20 PACA Message

30 None

2-19
C.S0044-0 v1.0
1 b. At the base station, enable PACA feature for the mobile station, assign a PACA priority
2 level to the mobile station, and disable Permanent Invocation PACA for the mobile
3 station.
4 c. If the mobile station is capable of Slotted Mode, verify that the mobile station is
5 operating in the Slotted Mode.
6 d. Ensure PACA is enabled on base station.
7 e. Configure the base station to make all traffic channels busy.
8 f. Setup a mobile station originated call.
9 g. Verify the following:
10 1. Mobile station originates call with PACA_REORIG bit='0' in Origination Message.
11 2. Base station replies with Reorder Order.
12 3. Mobile station retries the origination with the PACA_REORIG bit='1' in the
13 Origination Message.
14 4. Base station sends PACA Message with PURPOSE='0000' and the mobile
15 station’s Queue Position (Q_POS).
16 5. Mobile station acknowledges PACA Message.
17 h. The mobile station user interface should indicate the origination has been successfully
18 queued.
19 i. Verify the mobile station remains in non-slotted mode.
20 j. End call to terminate queued origination. Verify that the mobile station sends a PACA
21 Cancel Message to the base station.
22 k. Verify the mobile station enters slotted mode if applicable.

24 The mobile station shall comply with the requirements in steps c, g, i, j, and k.
25 2.17 PACA Origination, Idle Handoff While in Queue
27 This test verifies that a PACA-capable mobile station already in a PACA queue shall reoriginate
28 the PACA request when the mobile station performs an idle handoff.

2-20
C.S0044-0 v1.0

2 3.7.2.3.2.20 PACA Message

4 None

8 level to mobile station, and disable Permanent Invocation PACA for mobile station.
9 c. Ensure PACA is enabled on both base stations.
10 d. Configure both base stations to make all traffic channels busy.
11 e. Setup a mobile station originated call.

12 f. The mobile station user interface should indicate origination successfully queued.
13 g. Force an idle handoff from base station 1 to base station 2.
14 h. Verify the mobile station re-originates the PACA request with PACA_REORIG='1'.
15 i. Verify a PACA Message is received from base station 2 indicating the mobile station’s
16 position in the PACA queue of base station 2.
17 j. On the mobile station, originate a new call while still queued.

18 k. The mobile station user interface should indicate to the user that the first PACA call has
19 been cancelled.

21 The mobile station shall comply with the requirements in steps h, i and k.
22 2.18 PACA Origination, Traffic Channel Becomes Available
24 This test verifies that a currently PACA queued mobile station, when notified by the base station
25 of an available traffic channel, should properly alert the user that the origination can now be
26 completed.

2-21
C.S0044-0 v1.0

3 None

8 station.
9 c. Ensure PACA is enabled on the base station.
10 d. Configure the base station to make all traffic channels busy.

12 f. If supported by the mobile station, verify that the mobile station user interface indicates
13 that an origination has been successfully queued.
14 g. Make at least one traffic channel available on the base station.

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

18 j. End call.

20 The mobile station shall comply with the requirements in steps f and i.
21 2.19 PACA Origination, Features Interaction
23 This test verifies that specific paging channel features, such as SMS and MWI, are delivered to
24 the mobile station while the mobile station is currently in a PACA queue.


31 3.7.2.3.2.20 PACA Message
2-22
C.S0044-0 v1.0

2 None

7 station.
11 f. Verify the mobile station user interface indicates that an origination has been
12 successfully queued.
13 g. Send an SMS message over the Paging Channel to the mobile station. Verify the
14 message is properly received by the mobile station.
15 h. Configure base station to send MWI to the mobile station. Verify MWI is displayed by
17 i. End call.

19 The mobile station shall comply with the requirements in steps f, g, and h.
20 2.20 PACA Origination, Permanent Invocation
22 This test verifies that a PACA-capable mobile station with Permanent Invocation feature enabled
23 shall be placed in PACA queue even if PACA is not requested in Origination Message.


30 3.7.2.3.2.20 PACA Message

32 None
2-23
C.S0044-0 v1.0

4 level to the mobile station, and enabled Permanent Invocation PACA for the mobile
5 station.
10 1. Mobile station originates call with PACA_REORIG bit='0' in Origination Message.
11 2. Due to Permanent Invocation, base station sends PACA Message with
12 PURPOSE='0000' and the mobile station's Queue Position (Q_POS).
13 3. Mobile station acknowledges PACA Message.
14 4. The mobile station user interface should indicate origination successfully queued.
15
16
17 g. Make at least one traffic channel available on the base station.
18 h. The base station shall page the mobile station, and the mobile station should indicate to
19 the user that the PACA call is proceeding.
20 i. Verify call completes and audio is present in both directions.
21 j. End call.

23 The mobile station shall comply with the requirements in steps f and j.
24 2.21 PACA Origination, PACA Disabled for Mobile Station
26 This test verifies that when a mobile station disabled for PACA attempts a PACA Origination, the
27 call shall fail.


2-24
C.S0044-0 v1.0


4 None

7 b. Ensure PACA is enabled on the base station.
8 c. At the base station, disable PACA feature for the mobile station.

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

19 The mobile station shall comply with the requirements in step f.
20 2.22 Service Configuration and Negotiation without SYNC_ID
22 This test verifies that the initial service configuration in effect is according to the value specified
23 via the GRANTED_MODE field of the Extended Channel Assignment Message. This test also
24 verifies that after service negotiation, the service configuration in use is the one specified by SCR
25 and NN-SCR agreed upon during service negotiation.
27 2.6.4.1.2 Mobile Station Service Configuration and Negotiation procedures


2-25
C.S0044-0 v1.0
1 2.7.2.3.2.12 (Mobile Station) Service Request Message

2 2.7.2.3.2.13 (Mobile Station) Service Response Message
3 2.7.2.3.2.14 (Mobile Station) Service Connect Completion Message

4 2.7.4.18 Service Configuration information record
5 3.6.4.1.2 Base Station Service Configuration and Negotiation procedures

7 3.7.3.3.2.18 (Base Station) Service Request Message
8 3.7.3.3.2.19 (Base Station) Service Response Message
9 3.7.3.3.2.20 (Base Station) Service Connect Message

10 3.7.3.3.2.31 General Handoff Direction Message
11 3.7.3.3.2.36 Universal Handoff Direction Message
12 3.7.5.7 (Base Station) Service Configuration information record
13 3.7.5.20 (Base Station) Non-Negotiable Service Configuration information record
14 2.22.3 Reference Call Flow
MS BS
C om m on Com m on
C hannels Channels
O rigination M essage /
Page R esponse M essage
(SO )
Extended Channel Assignm ent M essage

(G RANTED _M O D E)
Dedicated D edicated
C hannels Channels
Initial service O ptional Service Negotiation M essage Exchange

configuration (Service N egotiation ends with tw o m essage below)
in effect
Service Connect M essage/

New service
G eneral Handoff D irection M essage/
configuration
Universal Handoff D irection M essage
takes effect
(SCR_new, NN -SCR_new)
Service Connect Com pletion M essage/

Extended H andoff Com pletion M essage
15
16 Figure 2-2 Reference Call Flow for Service Configuration and Negotiation without SYNC_ID

18 Note – In this test case, it shall be ensured that mobile station does not include SYNC_ID field in
19 the Origination Message/Page Response Message. This can be done by selecting type of call for
20 which corresponding service configuration is not stored in mobile station. Note that the mobile
21 station needs to store service configuration per SID, NID. Hence changing SID or NID or CDMA
2-26
C.S0044-0 v1.0
1 channel may be useful in ensuring that mobile station does not include SYNC_ID field in the
2 Origination Message/Page Response Message.
3 a. Connect the mobile station to the base station as shown in Annex A Figure A-1.
4 b. If the mobile station supports voice call, initiate a mobile station originated voice call.
5 Otherwise go to step f.
6 c. After the base station sends an Extended Channel Assignment Message to the mobile
7 station, the service negotiation shall occur between base station and mobile station.
8 The service negotiation ends when base station sends Service Connect
9 Message/General Handoff Direction Message/Universal Handoff Direction Message
10 with SCR and NN-SCR to the mobile station and mobile station accepts the service
11 configuration by sending Service Connect Completion Message/Extended Handoff
12 Completion Message.
13 d. Verify the following:

14 1. If the base station sends Extended Channel Assignment Message with
15 GRANTED_MODE field set to ‘00’ in step c above
16 a. Prior to the new service configuration sent in the Service Connect

17 Message/General Handoff Direction Message/Universal Handoff
18 Direction Message takes effect, verify the following:
19 1. The service configuration in use is the one jointly specified by the

20 DEFAULT_CONFIG value sent in the Extended Channel
21 Assignment Message and the default Non-Negotiable part of the
22 service configuration parameters specified in the Traffic Channel
23 Initialization substate.
24 b. When the new service configuration sent in the Service Connect
27 1. The service configuration in use is the one specified by SCR and
28 NN-SCR in the Service Connect Message/General Handoff
29 Direction Message/Universal Handoff Direction Message sent by
30 the base station.
31 2. Verify user traffic on both directions.

32 3. The base station receives a Service Connect Completion
33 Message (if base station sends Service Connect Message) or an
34 Extended Handoff Completion Message (if base station sends
35 General Handoff Direction Message/Universal Handoff Direction
36 Message) from the mobile station.
37 2. If base station sends Extended Channel Assignment Message with
2-27
C.S0044-0 v1.0

2 default multiplex option that is derived from the radio
3 configuration corresponding to Table 3.7.2.3.2.21-7 of [4] and the
4 default Non-Negotiable part of the service configuration
5 parameters specified in the Traffic Channel Initialization
6 substate.
11 NN-SCR in the Service Connect Message sent by the base
12 station.
13 2. Verify user traffic in both directions.
19 3. If base station sends Extended Channel Assignment Message with


25 default multiplex option that is derived from the radio
26 configuration corresponding to Table 3.7.2.3.2.21-7 of [4] and the
27 default Non-Negotiable part of the service configuration
28 parameters specified in the Traffic Channel Initialization
29 Substate.
35 station.
36 2. Verify user traffic on both directions.
2-28
C.S0044-0 v1.0
1 4. The mobile station does not send a Service Request Message to

2 the base station prior to the Service Connect Message/General
3 Handoff Direction Message/Universal Handoff Direction
4 Message is received from the base station.
5 e. Repeat steps a through d for mobile station terminated calls. In this case, Page
6 Response Message replaces Origination Message.
7 f. If mobile station supports data calls, repeat steps a to e above but with following
8 modification – In step b initiate data call in place of voice call.

11 2.23 Service Configuration and Negotiation with SYNC_ID
13 This test verifies that the mobile station can propose to use stored service configuration using
14 SYNC_ID in the Service Configuration and Negotiation process.
15 Note – This test assumes that the mobile station stores old service configuration with
16 corresponding SYNC_ID and uses SYNC_ID during call setup. If the mobile station does not use
17 SYNC_ID in call setup, then skip this test. This test also assumes that the base station sets
18 USE_SYNC_ID field to ‘1’ in Extended System Parameters Message and/or MC-RR Parameters
19 Message. If the base station is unable to do this, then skip this test.

22 2.6.2.2.14.1 Stored Parameters
23 2.6.2.5 Mobile Station Origination Operation
26 2.6.4.1.2 (Mobile Station) Service Configuration and Negotiation (procedures)
29 Traffic Channel Initialization Substate
31 2.6.6.2.5 Handoff Messages
32 2.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages

35 2.7.2.3.2.12 (Mobile Station) Service Request Message
2-29
C.S0044-0 v1.0
1 2.7.2.3.2.13 (Mobile Station) Service Response Message

2 2.7.2.3.2.14 (Mobile Station) Service Connect Completion Message
3 2.7.4.18 (Mobile Station) Service Configuration (information record)

4 (Base Station) Service Configuration and Negotiation (procedures)

7 3.7.2.3.2.31 MC-RR Parameters Message
8 3.7.3.3.2.18 (Base Station) Service Request Message
9 3.7.3.3.2.19 (Base Station) Service Response Message

10 3.7.3.3.2.20 (Base Station) Service Connect Message
13 3.7.5.7 (Base Station) Service Configuration ( information record)
14 3.7.5.20 (Base Station) Non-Negotiable Service Configuration ( information record)
15 2.23.3 Reference Call Flow
MS BS
C om m on Com m on
C hannels Channels
O rigination M essage /
Page R esponse M essage
(SYNC _ID)
Extended Channel Assignm ent M essage

(G RANTED _M O D E)
Dedicated D edicated
C hannels Channels
O ptional Service Negotiation M essage Exchange

(Service N egotiation ends with two m essages below)
Initial service
configuration
in effect Service Connect M essage
(USE_O LD _SERV_CO N FIG ,
SCR_new, NN-SCR_new)
N ew service
configuration Service Connect Com pletion M essage
takes effect
16
17 Figure 2-3 Reference Call Flow for Service Configuration and Negotiation with SYNC_ID
2-30
C.S0044-0 v1.0

2 a. Connect the mobile station to the base station as shown in Annex A Figure A-1. Verify
3 that the base station sets USE_SYNC_ID field to ‘1’ in Extended System Parameters
4 Message and/or MC-RR Parameters Message.
5 b. Identify a type of call for which the base station would send the SYNC_ID with SCR and
6 NN_SCR and the mobile station would use SYNC_ID when the same type of call is
7 originated again. Initiate a mobile station originated call with this call type. Verify that
8 the base station includes SYNC_ID field in the Service Connect Message/General
9 Handoff Direction Message/Universal Handoff Direction Message sent to the mobile
10 station. Once the service configuration sent in the Service Connect Message/General
11 Handoff Direction Message/Universal Handoff Direction Message has taken effect,
12 disconnect the call.
13 c. Initiate a mobile station originated call with same call type as above. Verify that mobile
14 station includes SYNC_ID field in the Origination Message.
15 d. The service negotiation ends when base station sends Service Connect Message to the
16 mobile station and mobile station accepts the service configuration by sending Service
17 Connect Completion Message.
18 e. Verify the following:

19 1. If the base station sends Service Connect Message with
20 USE_OLD_SERV_CONFIG field set to ‘00’
21 a. When the Service Connect Message takes effect, verify the following:
24 station.
25 2. Verify user traffic (e.g. SO 33) on both directions.
27 Message from the mobile station.
30 a. When the new service configuration specified in the Service Connect

31 Message takes effect, verify the following:
32 1. The mobile station uses the stored service configuration.
33 2. Verify user traffic (e.g. SO 33) on both directions.
38 a. When the Service Connect Message takes effect, verify the following:
2-31
C.S0044-0 v1.0
1 1. The mobile station uses the stored service configuration.

2 2. Verify user traffic (e.g SO 33) on both directions.
5 f. Repeat steps a through d for mobile station terminated calls. In this case, Origination
6 Message is replaced by Page Response Message.

8 The mobile station shall comply with step e.
9 2.24 Intra-Band Channel Assignment
11 This test verifies that the mobile station originating a call can be assigned a different frequency
12 within the same band class using the (Extended) Channel Assignment Message.


21 None

24 and base station 2 are operating the same band class with different frequencies.
25 b. Ensure the mobile station is operating in the Idle State on base station 1.
27 d. Ensure that the base station sends a Channel Assignment Message or Extended
28 Channel Assignment Message with the following settings:
29
2-32
C.S0044-0 v1.0
1 Table 2.24.4-1 Channel Assignment Message Settings
Field Value
ASSIGN_MODE ‘100’
FREQ_INCL ‘1’
BAND_CLASS Target Band Class (same

as base station 1)
CDMA_FREQ Target Frequency for base

station 2
2
3 Table 2.24.4-2 Extended Channel Assignment Message Settings
Field Value
ASSIGN_MODE ‘000’ or ‘100’
FREQ_INCL ‘1’
BAND_CLASS Target Band Class (same

as base station 1)
CDMA_FREQ Target Frequency for base

station 2
5 e. Verify the mobile station tunes to the new frequency and completes the call on base
6 station 2.
8 g. End the call.

9 h. Setup a mobile station terminated call and repeat steps d through g.

11 The mobile station shall comply with steps e, f, and h.
12 2.25 Silent-Retry
14 This test verifies the mobile station silent-retry functionality and the proper setting of ARQ fields.
15 Silent-retry is an autonomous access re-attempt that is made to re-originate the call, without user
16 interaction, that is due to the mobile station receiving an access attempt failure from the ARQ
17 Sublayer.
19 2.7.1.3.2.4 Origination Message (see [4])
2-33
C.S0044-0 v1.0
1 2.2.1.1.2.1.5 Access Channel Procedures (see [2])

2 2.1.1.2.1.2 Requirements for Setting the ARQ Fields (see [3])
3 2.1.1.2.2.1 Overview of Transmission and Retransmission Procedures (see [3])

4

6 None

8 a. Connect the base station as shown in Figure A-3. Disable the reverse link to the base
9 station.
10 b. Attempt to setup a mobile station originated call. Note the MSG_SEQ value in the
12 c. Allow the mobile station to exhaust NUM_STEP or EACH_NUM_STEP and
13 MAX_REQ_SEQ as defined in the Access Parameters Message or Enhanced Access
15 d. Enable the reverse link to the base station.
17 1. If the P_REV_IN_USE is less than or equal to six verify;

18 a. The mobile station sends a new Origination Message.
19 b. The MSG_SEQ value in the Origination Message is different than the
20 value recorded in step b.
21 2. Otherwise, verify;
22 a. The mobile station sends a new Origination Message with the following
23 values:
24
25
FIELD VALUE
ORIG_REASON ‘1’
ORIG_COUNT Number of consecutive silent-

retry. If the value is greater than
three, the mobile station shall
set this value to ‘11’.
26 b. The MSG_SEQ value in the Origination Message is different than the

27 value recorded in step b.
28 f. Verify the call completes and user traffic is present in both directions (i.e. audio).
2-34
C.S0044-0 v1.0

2 The mobile station shall comply with steps e and f.
4 2.26 MSID, MCC, and IMSI
5 2.26.1 Definition
6 These tests verify some protocol of the Mobile Station IDentifier number (MSID or MSIN), Mobile
7 Country Code (MCC), and International Mobile Station Identity (IMSI). Mobile station response to
8 three instances of base station PREF_MSID_TYPE are checked when the MCC and IMSI_11_12
9 of the mobile station and base station match, do not match or are wildcard values.
11 [4] 3.7.2.3.2.13 Extended System Parameters Message

12 [4] 2.6.2.2.5 Extended System Parameters Message
13 [4] 2.6.2.3 Mobile Station Page Match Operation
14 [4] 2.3.1 Mobile Station Identification Number
15 [4] 2.3.1.1 Encoding of IMSI_M_S and IMSI_T_S 11
16 [4] Table 3.7.2.3.2.13-1. Preferred MSID Types
17 [4] 3.6.2.2 Overhead Information
18 [3] 2.1.1.3.1.1 Addressing
19 [3] 2.1.1.2.1.3 IMSI Class
20 2.26.3 Call Flow Diagram

21 none

23 For each step below, set USE_TMSI = ‘0’ in the base station Extended System Parameters
24 Message or ANSI-41 System Parameters Message. Also program either the mobile station or the
25 base station for the values of MCC and IMSI_11_12, to achieve the matching or non-matching
26 conditions indicated.
27 a. PREF_MSID_TYPE = ‘00’. Configure the base station Extended System Parameters

28 Message with PREF_MSID_TYPE = ‘00’. Make a mobile station originated call and a
29 mobile station terminated call. Verify the mobile station sets MSID_TYPE = ’000’ and
30 sends IMSI_S and ESN in the Origination Message and Page Response Message.
31 b. PREF_MSID_TYPE = ‘10’, matching MCC and matching IMSI_11_12. Configure the
32 base station Extended System Parameters Message with PREF_MSID_TYPE = ‘10’.
33 Verify the values of both MCC and IMSI_11_12 are the same (match) in the mobile
34 station and base station. Make a mobile station originated call and a mobile station
35 terminated call. Verify the mobile station sets MSID_TYPE = ‘010’ and sends IMSI_S
2-35
C.S0044-0 v1.0
1 (does not send MCC and IMSI_11_12) in the Origination Message and Page Response
2 Message.
3 c. PREF_MSID_TYPE = ‘10’, non-matching MCC and matching IMSI_11_12. Configure the
5 Verify the values of IMSI_11_12 are the same (match) in the mobile station and base
6 station, but the values of MCC are different (don’t match). Make a mobile station
7 originated call and a mobile station terminated call. Verify the mobile station sets
8 MSID_TYPE = ‘010’ and sends MCC and IMSI_S (does not send IMSI_11_12) in the
9 Origination Message and Page Response Message.
10 d. PREF_MSID_TYPE = ‘10’, matching MCC and non-matching IMSI_11_12. Configure the
12 Verify the values of MCC are the same (match) in the mobile station and base station, but
13 the values of IMSI_11_12 are different (don’t match). Make a mobile station originated
14 call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE =
15 ‘010’ and sends IMSI_11_12 and IMSI_S (does not send MCC) in the Origination
16 Message and Page Response Message.
17 e. PREF_MSID_TYPE = ‘10’, non-matching MCC and non-matching IMSI_11_12.
18 Configure the base station Extended System Parameters Message with
19 PREF_MSID_TYPE = ‘10’. Verify the values of both MCC and IMSI_11_12 are different
20 in the mobile station and base station (neither matches). Make a mobile station originated
22 ‘010’ and sends MCC, IMSI_11_12 and IMSI_S in the Origination Message and Page
23 Response Message.
24 f. PREF_MSID_TYPE = ‘10’, wildcard MCC and wildcard IMSI_11_12. Configure the base
25 station Extended System Parameters Message with the following fields.
26
Field Value
PREF_MSID_TYPE ‘10’
MCC ‘1111111111’ (wildcard)
IMSI_11_12 ‘1111111’ (wildcard)
27 g. Make a mobile station originated call and a mobile station terminated call. Verify the
28 mobile station sets MSID_TYPE = ‘010’ and sends IMSI_S (but does not send MCC and
29 IMSI_11_12) in the Origination Message and Page Response Message.
30 h. PREF_MSID_TYPE = ‘11’, matching MCC and matching IMSI_11_12. Configure the
32 Verify the values of both MCC and IMSI_11_12 are the same in the mobile station and
33 base station (both match). Make a mobile station originated call and a mobile station
34 terminated call. Verify the mobile station sets MSID_TYPE = ‘011’ and sends IMSI_S
2-36
C.S0044-0 v1.0
1 and ESN (does not send MCC and IMSI_11_12) in the Origination Message or Page
2 Response Message.
3 i. PREF_MSID_TYPE = ‘11’, non-matching MCC and matching IMSI_11_12. Configure the
5 Verify the values of IMSI_11_12 are the same in the mobile station and base station
6 (match), but the values of MCC are different (don’t match). Make a mobile station
7 originated call and a mobile station terminated call. Verify the mobile station sets
8 MSID_TYPE = ‘011’ and sends MCC, IMSI_S and ESN (does not send IMSI_11_12) in
9 the Origination Message and Page Response Message.
10 j. PREF_MSID_TYPE = ‘11’, matching MCC and non-matching IMSI_11_12. Configure the
12 Verify the values of MCC are the same in the mobile station and base station (match), but
13 the values of IMSI_11_12 are different (don’t match). Make a mobile station originated
15 ‘011’ and sends IMSI_11_12, IMSI_S and ESN (does not send MCC) in the Origination
16 Message and Page Response Message.
17 k. PREF_MSID_TYPE = ‘11’, non-matching MCC and non-matching IMSI_11_12.
18 Configure the base station Extended System Parameters Message with
19 PREF_MSID_TYPE = ‘11’. Verify the values of both MCC and IMSI_11_12 are different
20 in the mobile station and base station. Make a mobile station originated call and a mobile
21 station terminated call. Verify the mobile station sets MSID_TYPE = ‘011’ and sends
22 MCC, IMSI_11_12, IMSI_S, and ESN in the Origination Message and Page Response
23 Message.
24 l. PREF_MSID_TYPE = ‘11’, wildcard MCC and wildcard IMSI_11_12. Configure the base
25 station Extended System Parameters Message with the following fields.
26
Field Value
PREF_MSID_TYPE ‘11’
MCC ‘1111111111’ (wildcard)
IMSI_11_12 ‘1111111’ (wildcard)
27
28 m. Make a mobile station originated call and a mobile station terminated call. Verify the
29 mobile station sets MSID_TYPE = ‘011’ and sends IMSI_S and ESN (but does not send
30 MCC and IMSI_11_12) in the Origination Message and Page Response Message.

32 All calls shall complete normally. The mobile station shall comply with requirements in steps b
33 through m.
2-37
C.S0044-0 v1.0
1 3 HANDOFF TESTS
2 3.1 Soft Handoff with Dynamic Threshold
3 3.1.1 Definition
4 This test verifies the mobile station and base station perform soft handoff. Soft handoff with and
5 without dynamic thresholds is verified. This test verifies both adding pilot to and dropping pilot
6 from the soft handoff Active Set. Tests 1 through 4 apply to cases when SOFT_SLOPE is not
7 equal to ‘000000’ (dynamic threshold enabled).

10 2.6.4.1.4 Processing the In-Traffic System Parameters Message
11 2.6.6.2.3 Handoff Drop Timer

13 2.6.6.2.5.2 Processing of Reverse Traffic Channel Handoff Messages
14 2.6.6.2.6.2 Maintenance of the Candidate Set

15 2.6.6.2.6.3 Maintenance of the Neighbor Set
16 2.6.6.2.8.2.1 Restoring the Configuration
17 2.6.6.3 Examples
18 2.7.2.3.2.5 Pilot Strength Measurement Message
19 3.6.6.2.1.1 System Parameters

21 3.7.3.3.2.7 In-Traffic System Parameters Message
22 3.7.3.3.2.17 Extended Handoff Direction Message

26 None

28 a. Setup test as shown in Figure A-4.
29 1. The Forward Channel from sector α of base station 1 has an arbitrary pilot PN
30 offset index P1 and is called Channel 1.
31 2. The Forward Channel from sector ß of base station 1 has an arbitrary pilot PN
3-1
C.S0044-0 v1.0
3 b. Set the test parameters for Test 1 as specified in Table 3.1.4-1and Table 3.1.4-2.
4 Table 3.1.4-1
Field Value
SOFT_SLOPE ‘010000’ (2)6
ADD_INTERCEPT ‘000110’ (3 dB)7
DROP_INTERCEPT ‘000010’ (1 dB)8
T_ADD ‘100000’ (-16 dB)
T_DROP ‘100100’ (-18 dB)
T_TDROP ‘0011’ (4s)
6 Table 3.1.4-2
Parameter Unit Channel 1 Channel 2 Channel 3

Îor/Ioc dB 7 -20 -20
Pilot Ec/Ior dB -5 -5 -5
Traffic Ec/Ior dB -7 -7 -7
Pilot Ec/Io dB -5.8 -33 -33
6
SOFT_SLOPE=16/8=2
7
ADD_INTERCEPT=6/2=3dB
8
DROP_INTERCEPT=2/2=1dB
3-2
C.S0044-0 v1.0
1 Table 3.1.4-3

Îor/Ioc dB 7 7 -20
Pilot Ec/Io dB -8.4 -8.4 -35
2
3 c. Reverse link attenuation should be set to balance the forward and reverse links
4 (approximately 90 dB).

6 e. Verify user data in both directions. Verify only Channel 1 is in the Active Set.
7 f. Raise the level of Channel 2 in steps of 1 dB with a dwell time of five seconds after
8 each step until the mobile station has generated the Pilot Strength Measurement
9 Message. Record the level of Pilot Ec/Io in the Pilot Strength Measurement Message.
10 g. Verify the following
11 1. The mobile station generates a Pilot Strength Measurement Message when the
12 level of channel 2 is at a Pilot Ec/Io level between –10 dB and –13 dB.
13 2. The base station sends an Extended Handoff Direction Message, General
14 Handoff Direction Message, or Universal Handoff Direction Message to the
15 mobile station to allow soft handoff between Channel 1 and Channel 2.
16 3. The mobile station sends a Handoff Completion Message or an Extended
17 Handoff Completion Message as a response to handoff message.
18 4. The mobile station is in soft handoff between Channel 1 and Channel 2.
19 h. Set test parameters for Test 2 as specified in Table 3.1.4-3 while Channel 1 and
20 Channel 2 are in soft handoff. Raise the level of Channel 3 in steps of 1 dB with a dwell
21 time of five seconds after each step until the mobile station has generated the Pilot
22 Strength Measurement Message. Record the level of Pilot Ec/Io in the Pilot Strength
23 Measurement Message.
24 i. Verify the following:
26 level of channel 3 is at a level between –10 dB and –13 dB.
29 mobile station to allow soft handoff between Channel 1, Channel 2 and Channel
30 3.
3-3
C.S0044-0 v1.0

3 4. The mobile station is in soft handoff among Channel 1, Channel 2 and Channel
4 3.
5 j. Set the test parameters for Test 3 in Table 3.1.4-4 while Channel 1, Channel 2, and
6 Channel 3 are in soft handoff. Lower the level of Channel 3 in steps of 1 dB with a dwell
7 time of 30 seconds until the mobile station has generated the Pilot Strength
8 Measurement Message. Record the level of Pilot Ec/Io in the Pilot Strength
10
11 Table 3.1.4-4

Îor/Ioc dB 7 7 7
Pilot Ec/Io dB -10.1 -10.1 -10.1
12 k. Verify the following:

14 level of channel 3 is at a level between –12 dB and –16 dB for a period of
15 T_TDROP.
21 4. The mobile station is in soft handoff between Channel 1 and Channel 2.
22 l. Set test parameters for Test 4 as specified in Table 3.1.4-5. Lower level of Channel 2 in
23 steps of 1 dB with a dwell time of 30 seconds after each step until the mobile station
24 has generated the Pilot Strength Measurement Message. Record the level of Pilot Ec/Io
25 in the Pilot Strength Measurement Message.
3-4
C.S0044-0 v1.0
1 Table 3.1.4-5
Îor/Ioc dB 7 7 -20
Pilot Ec/Io dB -8.4 -8.4 -35
2 m. Verify the following:

3 1. The mobile station shall generate a Pilot Strength Measurement Message when
4 the level of channel 2 is at a level of –11 dB and –14 dB for a period of
5 T_TDROP.
8 mobile station with only Channel 1 listed in the Active Set.
11 4. Channel 1 is the only Active Set for the mobile station.

13 Verify steps g, i, k and m.
14 3.2 Soft Handoff without Dynamic Threshold
15 3.2.1 Definition
16 This test verifies the proper operation of mobile station soft handoff. Soft handoff without dynamic
17 thresholds is verified. This test verifies both adding pilot to and dropping pilot from the soft
18 handoff Active Set. Tests 1 through 4 apply to cases when SOFT_SLOPE is equal to ‘000000’
19 (dynamic threshold disabled).

22 2.6.4.1.4 Processing the In-Traffic System Parameters Message
23 2.6.6.2.3 Handoff Drop Timer
26 2.6.6.2.6.2 Maintenance of the Candidate Set
27 2.6.6.2.6.3 Maintenance of the Neighbor Set
3-5
C.S0044-0 v1.0

2 2.6.6.3 Examples

4 3.6.6.2.1.1 System Parameters
6 3.7.3.3.2.7 In-Traffic System Parameters Message


11 None

13 a. Setup test as shown in Figure A-4. Start with Test 1 to Test 4 with dynamic threshold
14 disabled.
21 b. Set the test parameters for Test 1 as specified in Table 3.2.4-1 and Table 3.2.3-2.
22 Table 3.2.4-1
Parameter Tests 1-4
SOFT_SLOPE ‘000000’ (0)
ADD_INTERCEPT ‘000000’ (0 dB)
DROP_INTERCEPT ‘000000’ (0 dB)
T_ADD ‘011100’ (-14 dB)
T_DROP ‘100000’ (-16 dB)
T_TDROP ‘0011’ (4s)
23
3-6
C.S0044-0 v1.0
1 Table 3.2.4-2

Pilot Ec/Io dB -5.8 -33 -33
3 Table 3.2.4-3

Îor/Ioc dB 7 7 -20
Pilot Ec/Io dB -8.4 -8.4 -35
4
8 e. Verify user data in both directions. Verify only Channel 1 is in the Active Set.
9 f. Raise the level of Channel 2 in steps of 1 dB with a dwell time of five seconds after
11 Message. Record the level of Pilot Ec/Io in the Pilot Strength Measurement Message.
12 g. Verify the following:

14 level of channel 2 is at a level between T_ADD and T_ADD +2 dB.
20 4. The mobile station is in softer handoff between Channel 1 and Channel 2.
21 h. Set test parameters for Test 2 as specified in Table 3.2.4-3 while Channel 1 and
22 Channel 2 are in soft handoff. Raise the level of Channel 3 in steps of 1 dB with a dwell
3-7
C.S0044-0 v1.0
1 time of five seconds after each step until the mobile station has generated the Pilot
2 Strength Measurement Message. Record the level of Pilot Ec/Io in the Pilot Strength
6 level of channel 3 is at a level between T_DROP and T_DROP –3 dB for a period
7 of T_TDROP.
10 mobile station to allow softer handoff between Channel 1, Channel 2 and
11 Channel 3.
14 4. The mobile station is in softer handoff among Channel 1, Channel 2 and Channel
15 3.
16 j. Set the test parameters for Test 3 in Table 3.2.4-4 while Channel 1, Channel 2, and
17 Channel 3 are in soft handoff. Lower the level of Channel 3 in steps of 1 dB with a dwell
18 time of 30 seconds until the mobile station has generated the Pilot Strength
19 Measurement Message. Record the level of Pilot Ec/Io in the Pilot Strength
21 Table 3.2.4-4

Îor/Ioc dB 7 7 7
Pilot Ec/Io dB -10.1 -10.1 -10.1
22
25 level of channel 3 is at a level between –12 dB and –16 dB for a period of
26 T_TDROP.
29 mobile station to allow softer handoff between Channel 1 and Channel 2.
3-8
C.S0044-0 v1.0
1 4. The mobile station is in softer handoff between Channel 1 and Channel 2.

2 l. Set test parameters for Test 4 as specified in Table 3.2.4-5. Lower level of Channel 2 in
3 steps of 1 dB with a dwell time of 30 seconds after each step until the mobile station
4 has generated the Pilot Strength Measurement Message. Record the level of Pilot Ec/Io
5 in the Pilot Strength Measurement Message.
6 Table 3.2.4-5
Îor/Ioc dB 7 7 -20
Pilot Ec/Io dB -8.4 -8.4 -35
8 1. The mobile station shall generate a Pilot Strength Measurement Message when
9 the level of channel 2 is at a level of T_DROP and T_DROP –3 dB for a period of
10 T_TDROP.

13 mobile station with only Channel 1 listed in the Active Set.

16 4. Channel 1 is the only Active Set for the mobile station.

18 Verify steps g, i, k, and m.
19 3.3 Hard Handoff Between Frequencies in the Same Band Class
20 3.3.1 Definition
21 This test verifies the mobile station and base station perform hard handoff between different
22 CDMA channels in the same band class.
24 2.6.6.1.1 Types of Handoff

26 2.6.6.2.8 CDMA-to-CDMA Hard Handoff

3-9
C.S0044-0 v1.0
1 3.6.6.2.2 Call Processing During Handoff



6 None

11 2. Setup base station 2 to be on a different CDMA channel than base station 1, but
12 within the same band class. The Forward Channel from base station 2 has an
13 arbitrary pilot PN offset index P2 and is called Channel 2.
14 3. The AWGN source should be on the frequency of Channel 2. (It is advisable to

15 achieve the maximum possible difference in frequency separation between
16 Channel 1 and Channel 2).
17 b. Set the test parameters as shown in Table 3.3.4-1.

18 Table 3.3.4-1

Îor/Ioc dBm N/A -5
Pilot Ec/Ior dB -7 -7
Traffic Ec/Ior dB -7 -7
Ioc dBm/1.23 MHz N/A -75
Pilot Ec/Io dB -7 -13.2
19
20 c. Set reverse link attenuation to balance forward and reverse links (approximately 90 dB).
21 d. Setup a mobile station originated call on Channel 1.
22 e. Verify user data in both directions.

23 f. Initiate handoff from Channel 1 to Channel 2. Verify that base station 1 initiates handoff
24 from Channel 1 to Channel 2 by sending a General Handoff Direction Message,
25 Universal Handoff Direction Message, or an Extended Handoff Direction Message with
26 proper parameters (refer to tables in Annex B) to initiate handoff from Channel 1 to
27 Channel 2.
3-10
C.S0044-0 v1.0
1 g. One second or more after base station 1 sends a General Handoff Direction Message,
2 a Universal Handoff Direction Message, or an Extended Handoff Direction Message
3 disconnect or attenuate the forward link of Channel 1.
4 h. Verify user data in both directions.
5 i. Monitor calls and record the length of any audio dropouts present.
6 j. Steps b through g may be repeated for the case where it is a hard handoff to soft
7 handoff on the same frequency with the following setup (see Figure A-4: one base
8 station configured with two sectors active):
15 k. The expected results for steps h and i should be the same as the previous test.

17 In step h, the mobile station and base stations shall successfully execute the hard handoff.
18 3.4 Hard Handoff from CDMA to Analog
19 3.4.1 Definition
20 This test verifies the mobile station and base station perform hard hand off from a CDMA system
21 to an analog system.

24 2.6.6.2.9 CDMA-to-Analog Handoff
27 3.7.3.3.2.6 Analog Handoff Direction Message

29 None

31 a. Connect two base stations and an AWGN source to the mobile station as shown in
32 Figure A-5. For the purpose of this test, Channel 1 is CDMA and Channel 2 is analog.
33 b. Set the test parameters as shown in Table 3.3.4-1 and Table 3.4.4-2.
3-11
C.S0044-0 v1.0
1
2
3 Table 3.4.4-2
Analog Parameter Unit Channel 2
Voice Channel dBm -73
Co-Channel Interference dB -18

9 f. Initiate handoff to analog. Verify the CDMA base station sends an Analog Handoff
10 Direction Message with proper parameters (refer to tables in Annex B) to initiate
11 handoff to analog.
12 g. One second or more after base station 1 sends an Analog Handoff Direction Message
13 disconnect or attenuate the forward link of Channel 1.
14 h. Verify user data in both directions in the Analog system.
15 i. Monitor calls and record the length of any audio dropouts present on handoff.

17 In step h, the mobile station handoff to the Analog system shall be completed successfully
18 3.5 Soft Handoff in Fading
19 3.5.1 Definition
20 This test verifies soft handoff under various fading conditions:
21 a. 1 Ray Rayleigh fading at 30 km/hr
22 b. 3 Ray Rayleigh fading at 100 km/hr
23 c. 1 Ray Rayleigh fading at 3 km/hr

27 2.6.6.2.7 Soft Handoff
3-12
C.S0044-0 v1.0
1 3.6.6.2.4 Soft Handoff

3 None

5 a. Setup test as shown in A-2.
10 b. Set up the test parameters as shown in Table 3.5.4-1.
11 Table 3.5.4-1

Îor/Ioc dB 0 -10
Ioc dBm/1.23 MHz -75 -75
Pilot Ec/Io dB -10.2 -20.2
12
15 d. Set both channel simulators to one Ray Rayleigh, 30 km/hr.
16 e. Setup a mobile station originated call on Channel 1. Monitor two-way audio and note
17 anomalies throughout the test.
18 f. Raise the level of Channel 2 in steps of 1 dB with a dwell time of 5 seconds after each
19 step until the mobile station has generated the Pilot Strength Measurement Message.
20 Verify the following:
21 1. Pilot Strength Measurement Message is generated when the channel 2 Pilot Ec/Io
22 is at a level above T_ADD.
23 2. Base station sends an Extended Handoff Direction Message, General Handoff
24 Direction Message, or Universal Handoff Direction Message to the mobile
25 station.
26 3. Channel 1 and Channel 2 are in the Active Set at the action time of the message.
27 g. Mobile station sends a Handoff Completion Message or an Extended Handoff
28 Completion Message to the base station.
3-13
C.S0044-0 v1.0
1 h. Set the test parameters as specified in Table 3.5.4-2 without dropping the call.
2 Table 3.5.4-2

Îor/Ioc dB 0 0
Ioc dBm/1.23 MHz -75 -75
3
4 i. Lower the level of Channel 1 in steps of 1 dB with a dwell time of 8 seconds after each
7 1. Pilot Strength Measurement Message is generated when Channel 1 is at a Pilot
8 Ec/Io level below T_DROP for a period of TT_DROP.
11 station.
12 3. Only Channel 2 is in the Active Set at the action time of the message.
13 4. Mobile station sends a Handoff Completion Message or an Extended Handoff
15 j. Set the levels as specified in Table 3.5.4-3.
16 Table 3.5.4-3

Îor/Ioc dB -10 0
Ioc dBm/1.23 MHz -75 -75
17
18 k. Raise the level of Channel 1 in steps of 1 dB with a dwell time of 5 seconds after each
21
3-14
C.S0044-0 v1.0
1 1. Pilot Strength Measurement Message is generated when the channel 1 Pilot Ec/Io
2 is at a level above T_ADD.
5 station.
6 3. Channel 1 and Channel 2 are in the Active Set at the action time of the message.
9 l. Set the levels as specified in Table 3.5.4-4.
10 Table 3.5.4-4
Parameter Unit Value
Vehicle Speed km/hr 100
Number of Paths 3
Path 2 Power dB 0
(Relative to Path 1)
Path 3 Power dB -3
(Relative to Path 1)
Delay from Path 1 to Input µs 0
Delay from Path 2 to Input µs 2
Delay from Path 3 to Input µs 14.5
11 m. Lower the level of Channel 2 in steps of 1 dB with a dwell time of 8 seconds after each
14 1. Pilot Strength Measurement Message is generated when the Channel 2 is at a
15 Pilot Ec/Io level below T_DROP for a period of TT_DROP.

18 station.
22 n. Repeat steps a through l under 3 Ray Rayleigh fading at 100 km/hr fading condition as
23 specified in Table 3.5.4-4.
24 o. Repeat steps a through l under 1 Ray Rayleigh fading at 3 km/hr fading condition.
3-15
C.S0044-0 v1.0

2 The mobile station shall generate the Pilot Strength Measurement Message at the appropriate
3 time as specified in steps f, h, j, and l and the handoff shall be completed successfully.
4 3.6 Hard Handoff in Fading
5 3.6.1 Definition
6 This test verifies hard handoff under various fading conditions:
7 a. 1 Ray Rayleigh fading at 30 km/hr

8 b. 3 Ray Rayleigh fading at 100 km/hr
9 c. 1 Ray Rayleigh fading at 3 km/hr
10 Under various deployment scenarios:
11 a. Between frequencies
12 b. On the same frequency


20 None

23 1. The Forward Channel from base station 1 on frequency F1, has an arbitrary pilot
24 PN offset index P1 and is called Channel 1.
25 2. The Forward Channel from base station 2 on frequency F2, has an arbitrary pilot
26 PN offset index P2 and is called Channel 2.
3-16
C.S0044-0 v1.0
1 Table 3.6.4-1

Îor/Ioc dB 0 0
Ioc dBm/1.23 MHz -75 -75
Pilot Ec/Io dB -10 -10
2
3 c. Set reverse link attenuation to balance forward and reverse links (approx. 90 dB).
4 d. Set the channel simulators for 1 Ray Rayleigh fading, 30 km/hr.
5 e. Setup a mobile station originated call on Channel 1.

7 g. Initiate handoff from Channel 1 to Channel 2. Verify that base station 1 initiates a
8 handoff from Channel 1 to Channel 2 by sending a General Handoff Direction Message,
9 Universal Handoff Direction Message, or an Extended Handoff Direction Message.
10 h. Upon receiving an Extended Handoff Direction Message, General Handoff Direction
11 Message, or Universal Handoff Direction Message at the mobile station, verify the
12 following:

15 Handoff Completion Message to the base station.
16 i. Repeat steps a through h, with the channel simulators set to 3 Ray Rayleigh at 100
17 km/hr in step d. Use the setup shown in Table 3.5.4-4. The expected results are as
18 given above for the previous test.
19 Table 3.6.4-2

Îor/Ioc dB 0 0
Ioc dBm/1.23 MHz -75 -75
20
21 j. Repeat steps a through h, with the channel simulators set to 1 Ray Rayleigh at 3 km/hr
22 in step d. The expected results are as given above for the previous test.
3-17
C.S0044-0 v1.0
1 k. Repeat steps c through j for the scenario where the hard handoff is performed between
2 two CDMA channels on the same frequency, with the setup test as shown in Figure A-
3 5:
4 1. Forward Channel from base station 1 has an arbitrary pilot PN offset index P1
5 and is called Channel 1.
6 2. Forward Channel from base station 2 has an arbitrary pilot PN offset index P2
7 and is called Channel 2.
8 3. Test parameters set as shown in Table 3.6.4-2.
9 l. Note that in this case a hard handoff can be forced by excluding P1 from the Active Set.

12 3.7 Hard Handoff Between Different Band Classes
13 3.7.1 Definition
14 This test verifies hard handoff between two different band classes. Both band classes are
15 supported by the mobile station and base station.

25 2.1.1.1 Channel Spacing and Designation (see [1])

27 None

30 1. The Forward Channel from the base station 1 in Band Class X has an arbitrary
31 pilot PN offset index P1 and is called Channel 1.
32 2. The Forward Channel from the base station 2 in Band Class Y has an arbitrary
33 pilot PN offset index P2 and is called Channel 2.
3-18
C.S0044-0 v1.0
1 b. Set the test parameters as shown in Table 3.7.4-1

2 Table 3.7.4-1
Parameter Unit Band Class X Band Class Y

Îor/Ioc dB -5 -5
Ioc dBm/1.23 MHz -75 -75
3
5 d. Setup a call in Channel 1.

7 f. Initiate handoff from base station 1 to base station 2. Verify the base station sends a
8 General Handoff Direction Message, Universal Handoff Direction Message, or an
9 Extended Handoff Direction Message with proper parameters (refer to tables in Annex
10 B) to initiate handoff.
11 g. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff
12 Completion Message and the handoff is completed successfully.
13 h. Reconnect Channel 1 from base station 1 with parameters listed in Table 3.5.4-1.
14 i. Initiate handoff from base station 1 to base station 2. Verify that base station 2 sends a
15 General Handoff Direction Message, Universal Handoff Direction Message, or an
16 Extended Handoff Direction Message with proper parameters (refer to tables in Annex
17 B) to initiate handoff.
18 j. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff
19 Completion Message and the handoff is completed successfully.
20 k. This test can be repeated for hard handoffs between other band classes.

22 The mobile station shall comply with steps g and k.
23 3.8 Hard Handoff with and without Return on Failure
24 3.8.1 Definition
25 This test verifies the mobile station behavior when hard handoff fails and:
26 return on failure is allowed.
27 return on failure is disallowed.
3-19
C.S0044-0 v1.0


5 2.6.6.2.8.2 Hard Handoff With Return On Failure

7 3.6.6.1 Overview


12 None

20 Table 3.8.4-1

Îor/Ioc dB -5 -5
Traffic Ec/Ior dB -7 <-20 (or none)
Ioc dBm/1.23 MHz -75 -75
Pilot Ec/Io dB -13.2 -12
21

26 f. For Test 1, instruct the base station to initiate a handoff to Channel 2 and allow for
27 return on failure. Verify that the base station sends a General Handoff Direction
3-20
C.S0044-0 v1.0
1 Message or a Universal Handoff Direction Message with the

2 RETURN_IF_HANDOFF_FAIL = ‘1’.
3 g. Due to the low traffic gain level on Channel 2 (refer to Table 3.6.4-1), the mobile station
4 will attempt the hard handoff as directed by the base station, but not complete it, and
5 declare a hard handoff failure.
6 h. Verify the mobile station returns to Channel 1 and verify user data in both directions.
7 i. For Test 2, instruct the base station to initiate a handoff to Channel 2 and disallow for
8 return on failure. Verify that the base station sends a General Handoff Direction
9 Message or a Universal Handoff Direction Message with RETURN_IF_HANDOFF_FAIL
10 = ‘0’
11 j. Due to the low traffic gain level on Channel 2 (refer to Table 3.6.4-1), the mobile station
12 will attempt the hard handoff as directed by the base station, but not complete it, and
13 declare a hard handoff failure.
14 k. Verify the mobile station does not restore to the previous configuration and does not
15 return to Channel 1.
16 3.9 Search Window Size and Offset (Traffic State)
17 3.9.1 Definition
18 A CDMA call is established on sector α of sectored base station 1. Delay is applied to sector ß
19 and base station 2. The level of sector ß is raised sufficiently high to ensure intersector handoff is
20 possible. The level of base station 2 is raised sufficiently high to ensure soft handoff is possible.
21 In section 3.9.3.1, the pilot strength measurements of base station 2 and sector ß are checked
22 against the search window size and search window offset settings for each of the neighbor pilots.
23 If the delay is greater than the search window size for the neighbor pilot then the mobile station
24 shall not send a Pilot Strength Measurement Message.
25 In section 3.9.3.2, the pilot strength measurements of base station 2 and sector ß are checked
26 against a common search window size (i.e. SRCH_WIN_N). If the delay is greater than the
27 search window size for the neighbor pilot then the mobile station shall not send a Pilot Strength
29 3.9.2 Formulas
30 Pilot_PN_sel = nearest Pilot PN in the neighbor set not to exceed the integer of
31 PILOT_PN_PHASE/64.
32 Neighbor_Chip_Offset = PILOT_PN_PHASE-(Pilot_PN_sel*64)
33 Num_Chips = Set_Chip_Offset - Sim_Chip_Offset
Num_chip x 244m
34 Chip_Delay (µs) =
300m/µs
35 PILOT_PN_PHASE is the pilot PN phase obtained from the mobile station log file in units of
36 chips. PILOT_PN_PHASE is referenced to the zero offset Pilot PN sequence. Pilot_PN_sel
37 selects the closest neighbor’s Pilot PN and the value is subtracted from the PILOT_PN_PHASE
38 to determine the residual chip delay (i.e. Neighbor_Chip_Offset). Set_Chip_Offset is the desired
39 number of chip offsets for a particular test case. Sim_Chip_Offset is the inherent delay for a pilot
3-21
C.S0044-0 v1.0
1 due to the time alignment/calibration of the equipment. Chip_Delay is the actual delay in usec the
2 tester should vary with the test equipment (e.g. fader) to achieve the proper Set_Chip_Offset (this
3 includes the inherent delay measured for Sim_Chip_Offset. When properly adjusted, the
4 Set_Chip_Offset should equal to the Neighbor_Chip_Offset.

6 2.6.6 Handoff Procedures
7 2.6.6.2.1 Pilot Search
8 Table 2.6.6.2.1 Search Window Sizes

9 Table 2.6.6.2.1-2 Search Window Offset

12 2.7.2.3.2.34 Extended Pilot Strength Measurement Message
14 3.7.2.3.2.1 System Parameters Message
15 3.7.2.3.2.22 General Neighbor List Message
16 3.7.2.3.2.34 Universal Neighbor List Message

18 None
20 3.9.5.1 Method of Measurement with NGHBR_SRCH_MODE = ‘10’ (search window size per
21 neighbor
22
23 Table 3.9.5-1 Test Cases for NGHBR_SRCH_MODE=’10’ (Traffic State)
Test P2 win P2 win P2 P3 win P3 win P3

Case size offset Set_Chip_ size offset Set_Chip_
Offset Offset
1 7 0 P3 win/4 9 0 P3 win/4
+P3 offset +P3 offset
2 7 0 P3 win/2 9 0 P3 win/2
3 7 0 P3 win/2 9 0 P3 win/2
+10 chips +10 chips
3-22
C.S0044-0 v1.0
4 7 0 P3 win/2 7 1 P3 win/2
5 7 0 P3 win/2 7 4 P3 win/2
1
9 b. Set the test parameters as specified in Table 3.9.5-2.
10 c. The Reverse Link attenuation should be set to balance the forward and reverse links
12
13 Table 3.9.5-2 Test Parameters for Search Window per Neighbor (Traffic State)
Ioc dBm/1.23 MHz -75 -75 -75
Pilot Ec/Io dB –9.6 -30.6 -30.6
14
15 Note: The Pilot Ec/I0 value is calculated from the parameters set in the table. It is not a settable
16 parameter itself.
17 d. Set the following values in the General Neighbor List Message (GNLM) or the Universal
18 Neighbor List Message(UNLM):
19
Field Value
NGHBR_CONFIG_PN_INCL 1 (for GNLM only)
NGHBR_SRCH_MODE ‘10’
3-23
C.S0044-0 v1.0
SRCH_OFFSET_INCL 1
Neighbor Setting for P2
NGHBR_PN P2
SRCH_WIN_NGHBR 7 (40 chips)
SRCH_OFFSET_NGHBR 0 (no offset)
NGHBR_PN P3
3
4 e. Determine the inherent delay of the channel simulator (i.e. Sim_Chip_Offset).
5 f. For Test 1, set the delay on both Channel 2 and on Channel 3 to a Chip_Delay such
6 that Set_Chip_Offset =(SRCH_WIN_NGHBR of P3)/4 + SRCH_OFFSET_NGHBR of
7 P3 (i.e Set_Chip_Offset of P2 is equal to Set_Chip_Offset of P3).
8 g. Setup a mobile station originated call.
9 h. Raise the level of Channel 2 to Îor/Ioc = +1 dB without dropping the call.
10 i. Raise the level of Channel 3 to Îor/Ioc = +1 dB without dropping the call.
11 j. End the call.

12 k. Reset the test parameters as specified in Table 3.9.5-2.
13 l. Verify the following:
14 1. The mobile station shall generate a Pilot Strength Measurement Message or an
15 Extended Pilot Strength Measurement Message when the Channel 2 pilot
16 strength is raised up to the same pilot strength as Channel 1 (Îor/Ioc=1dB).
17 2. The neighbor_Chip_Offset of P2 calculated from PILOT_PN_PHASE of the Pilot

18 Strength Measurement Message or the Extended Pilot Strength Measurement
19 Message generated in step h shall equal the Set_Chip_Offset of P2.
20 3. The mobile station shall also generate a Pilot Strength Measurement Message or
21 an Extended Pilot Strength Measurement Message when the Channel 3 pilot
22 strength is raised up to the same pilot strength as Channel 1 (Îor/Ioc=1 dB).
3-24
C.S0044-0 v1.0

3 Message generated in step i shall equal the Set_Chip_Offset of P3.
4 m. For Test 2, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that
5 Set_Chip_Offset = (SRCH_WIN_NGHBR of P3)/2 + SRCH_OFFSET_NGHBR of P3.
6 n. Repeat steps g to k.
7 o. Verify the following:
8 1. The mobile station shall not generate a Pilot Strength Measurement Message or


17 p. For Test 3, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that
18 Set_Chip_Offset = (SRCH_WIN_NGHBR of P3)/2 + SRCH_OFFSET_NGHBR of P3 +
19 10 chips.
20 q. Repeat steps g to k.
21 r. Verify that the mobile station does not generate a Pilot Strength Measurement Message
22 or an Extended Pilot Strength Measurement Message when either the Channel 2 or
23 Channel 3 pilot strength is raised up to the same pilot strength as Channel 1 (Îor/Ioc=1
24 dB).
25 s. Set the following values in the General Neighbor List Message or the Universal
26 Neighbor List Message:
27
28
Field Value
SRCH_OFFSET_INCL 1
29
NGHBR_PN P2
3-25
C.S0044-0 v1.0
NGHBR_PN P3
SRCH_OFFSET_NGHBR 1 (window_size/2)
3 t. For Test 4, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that
5 u. Repeat steps g to k.
6 v. Verify the following:


16 w. Set the following values in the General Neighbor List Message or the Universal
18
Field Value
SRCH_OFFSET_INCL 1
19
NGHBR_PN P2
3-26
C.S0044-0 v1.0
NGHBR_PN P3
SRCH_OFFSET_NGHBR 4 (-window_size/2)
2
3 x. For Test 5, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that
4 Set_Chip_Offset =(SRCH_WIN_NGHBR of P3)/2.
5 y. Repeat steps g to k.
6 z. Verify the following:


16 3.9.5.2 Method of Measurement with NGHBR_SRCH_MODE = ‘00’ (same search window size
17 for all neighbor)
18
19 Table 3.9.5-3 Test Cases for NGHBR_SRCH_MODE=’00’ (Traffic State)
Test Neighbor P2 win P2 P3 win P3

Case Message size Set_Chip_Offset size Set_Chip_Offset
1 GNLM 7 SRCH_Win_N/2 7 SRCH_WIN_N/4
2 GNLM 7 SRCH_Win_N/2 + 7 SRCH_WIN_N/4 +

10 chips 10 chips
3 UNLM 7 SRCH_Win_N/2 7 SRCH_WIN_N/4
3-27
C.S0044-0 v1.0
4 UNLM 7 SRCH_Win_N/2 + 7 SRCH_WIN_N/4 +

10 chips 10 chips
1
2 a. Setup test as shown in A-4
9 b. Set the test parameters as specified in Table 3.9.5-3.
12 d. Set the following value in the System Parameters Message:
13
Field Value
SRCH_WIN_N 7 (40 chips)
14
15 e. Set the following values in the General Neighbor List Message:
16
Field Value
17
18 f. For Tests 1 and 3, set the delay on Channel 2 to a Chip_Delay such that
19 Set_Chip_Offset of P2 =SRCH_WIN_N/2, and set the delay on Channel 3 to a
20 Chip_Delay such that Set_Chip_Offset=SRCH_WIN_N/4.

22 h. Raise the level of Channel 2 to Îor/Ioc = +1 dB without dropping the call.
23 i. Raise the level of Channel 3 to Îor/Ioc = +1 dB without dropping the call.
24 j. End the call.

25 k. Reset the test parameters as specified in Table 3.9.5-3.
3-28
C.S0044-0 v1.0


7 3. The mobile station shall also generate a Pilot Strength Measurement Message or

13 m. For Tests 2 and 4, set the delay on Channel 2 to a Chip_Delay such that
14 Set_Chip_Offset of P2 =(SRCH_WIN_N/2)+10 chips, and set the delay on Channel 3 to
15 a Chip_Delay such that Set_Chip_Offset=(SRCH_WIN_N/4)+10 chips.
16 n. Repeat steps g to k.
17 o. Verify the following:


27 p. Set the following values in the Universal Neighbor List Message:

28
Field Value
SRCH_WIN_N 7 (40 Chips)
29
30 q. For Tests 3 and 4 repeat steps b to o using parameter values in step t sent over the
31 Universal Neighbor List Message instead of the General Neighbor List Message.
3-29
C.S0044-0 v1.0
2 3.9.6.1 For section 3.9.4.1:

3 Verify steps l, o, r, v and z for Tests 1 to 5.
4 3.9.6.2 For section 3.9.4.2:

5 Verify step l for Tests 1 and 3.
6 Verify step o for Tests 2 and 4.
7 3.10 Search Window Size and Offset (Idle State)
8 3.10.1 Definition
9 The mobile station is operating in idle state and monitoring sector α of base station 1. Delay is
10 applied to both sector ß of base station 1 and base station 2. The level of neighbor pilots are
11 raised sufficiently high to ensure idle handoff is possible.
12 In section 3.9.3.1, the pilot strength measurements of base station 2 and sector ß of base station
13 1 are checked against the search window size and search window offset settings for each of the
14 neighbor pilots. If the delay is greater than the search window size for the neighbor pilot then the
15 mobile station shall not idle handoff to that neighbor pilot.
16 In section 3.9.3.2, the pilot strength measurements of base station 2 and sector ß of base station
17 1are checked against a common search window size (i.e. SRCH_WIN_N). If the delay is greater
18 than the search window size for the neighbor pilot then the mobile station shall not idle handoff to
19 that neighbor pilot.
20 Formulas
21 Num_Chips = Set_Chip_Offset - Sim_Chip_Offset
Num_chip x 244m
22 Chip_Delay (µs) =
300m/µs
23 Set_Chip_Offset is the desired number of chip offsets for a particular test case. Sim_Chip_Offset
24 is the inherent delay for a pilot due to the time alignment/calibration of the equipment. Chip_Delay
25 is the actual delay in usec the tester should vary with the test equipment (e.g. fader) to achieve
26 the proper Set_Chip_Offset (this includes the inherent delay measured for Sim_Chip_Offset.
27 When properly adjusted, the Set_Chip_Offset should equal to the neighbor pilot’s chip offset from
28 zero chip delay.
29 3.10.2 Traceability (See [4]);

31 2.6.6.2.1 Pilot Search
32 Table 2.6.6.2.1 Search Window Sizes
33 Table 2.6.6.2.1-2 Search Window Offset
35 3.7.2.3.2. System Parameters Message
3-30
C.S0044-0 v1.0
1 3.7.2.3.2.34 Universal Neighbor List Message

3 None
5 3.10.4.1 Method of Measurement with NGHBR_SRCH_MODE = ‘10’ (search window size per
6 neighbor)
7
8 Table 3.10.4-1 Test Cases for NGHBR_SRCH_MODE=’10’ (Idle State)
Test P2 win P2 win P2 P3 win P3 win P3

Case size offset Set_Chip_ size offset Set_Chip_
Offset Offset
1 7 0 P3 win/4 9 0 P3 win/4
2 7 0 P3 win/2 9 0 P3 win/2
3 7 0 P3 win/2 9 0 P3 win/2
+10 chips +10 chips
4 7 0 P3 win/2 7 1 P3 win/2
5 7 0 P3 win/2 7 4 P3 win/2
9
17 b. The Reverse Link attenuation should be set to balance the forward and reverse links
19 c. Set the following values in the General Neighbor List Message (GNLM) or the Universal
21
3-31
C.S0044-0 v1.0
Field Value
SRCH_OFFSET_INCL 1
NGHBR_PN P2
NGHBR_PN P3
3
4 d. Determine the inherent delay of the channel simulator (i.e. Sim_Chip_Offset).
5 e. For Test 1, set the delay on both Channel 2 and on Channel 3 to a Chip_Delay such
6 that Set_Chip_Offset =(SRCH_WIN_NGHBR of P3)/4 + SRCH_OFFSET_NGHBR of
7 P3 (i.e Set_Chip_Offset of P2 is equal to Set_Chip_Offset of P3).
8 f. Set the test parameters as specified in Table 3.10.4-1 for state S1 in all 3 channels.
9
10 Table 3.10.4-2 Test Parameters for Search Window per Neighbor (Idle State)
Îor/Ioc dB 1 (S1 and S2) -20 for S1 -20 for S1

5 for S2 5 for S2
Ioc dBm/1.23 MHz -75 -75 -75
3-32
C.S0044-0 v1.0
Pilot Ec/Io dB –9.6 for S1 -30.6 for S1 -30.6 for S1

-13.3 for S2 -9.3 for S2 -9.3 for S2
1
2 Note: The Pilot Ec/I0 value is calculated from the parameters set in the table. It is not a settable
3 parameter itself.
4 g. Allow the mobile station to monitor Channel 1 while in idle state.
5 h. Raise the level of Channel 2 to Îor/Ioc = +5 dB (State S2 for Channel 2 in Table
6 3.10.4-2).
7 i. Reset the test parameter as specified in Table 3.10.4-2for state S1 in all 3 channels.
8 j. Raise the level of Channel 3 to Îor/Ioc = +5 dB (State S2 for Channel 3 in Table
9 3.10.4-2).

11 1. The mobile station shall perform an idle handoff to Channel 2 in step h.
12 2. The mobile station shall perform an idle handoff to Channel 3 in step j.
13 3. For Test 2, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such
14 that Set_Chip_Offset = (SRCH_WIN_NGHBR of P3)/2 +
15 SRCH_OFFSET_NGHBR of P3.
16 l. Repeat steps f to j.
18 1. The mobile station shall not perform an idle handoff to Channel 2 in step h.

20 3. For Test 3, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such
21 that Set_Chip_Offset = (SRCH_WIN_NGHBR of P3)/2 +
22 SRCH_OFFSET_NGHBR of P3 + 10 chips.
23 n. Repeat steps f to j.
24 o. Verify that the mobile station does not perform idle handoff(s) in either step h or j.
25 p. Set the following values in the General Neighbor List Message or the Universal
27
28
Field Value
SRCH_OFFSET_INCL 1
3-33
C.S0044-0 v1.0
NGHBR_PN P2
NGHBR_PN P3
SRCH_OFFSET_NGHBR 1 (window_size/2)
3
4 q. For Test 4, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that
6 r. Repeat steps g to k.
7 s. Verify the following:
10 t. Set the following values in the General Neighbor List Message or the Universal
12
Field Value
SRCH_OFFSET_INCL 1
13
NGHBR_PN P2
3-34
C.S0044-0 v1.0
NGHBR_PN P3
SRCH_OFFSET_NGHBR 4 (-window_size/2)
2
3 u. For Test 5, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that
4 Set_Chip_Offset =(SRCH_WIN_NGHBR of P3)/2.
5 v. Repeat steps g to k.
6 w. Verify the following:
8 2. The mobile station shall not perform an idle handoff to Channel 3 in step j.
9 3.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 Neighbor P2 win P2 P3 win P3

Case Message size Set_Chip_Offset size Set_Chip_Offset
1 GNLM 7 SRCH_Win_N/2 7 SRCH_WIN_N/4
2 GNLM 7 SRCH_Win_N/2 + 7 SRCH_WIN_N/4 +

10 chips 10 chips
3 UNLM 7 SRCH_Win_N/2 7 SRCH_WIN_N/4
4 UNLM 7 SRCH_Win_N/2 + 7 SRCH_WIN_N/4 +

10 chips 10 chips
12
3-35
C.S0044-0 v1.0
1 b. The Reverse Link attenuation should be set to balance the forward and reverse links
3 c. Set the following value in the System Parameters Message:
4
Field Value
5
6 d. Set the following values in the General Neighbor List Message:
7
Field Value
9 e. For Tests 1 and 3, set the delay on Channel 2 to a Chip_Delay such that
10 Set_Chip_Offset of P2 =SRCH_WIN_N/2, and set the delay on Channel 3 to a
11 Chip_Delay such that Set_Chip_Offset=SRCH_WIN_N/4.
12 f. Set the test parameters as specified in Table 3.10.4-2 for state S1 in all 3 channels.
13 g. Allow the mobile station to monitor Channel 1 while in idle state.
14 h. Raise the level of Channel 2 to Îor/Ioc = +5 dB (State S2 for Channel 2 in Table
15 3.10.4-2).
16 i. Reset the test parameter as specified in Table 3.10.4-2 for state S1 in all 3 channels.
17 j. Raise the level of Channel 3 to Îor/Ioc = +5 dB (State S2 for Channel 3 in Table
18 3.10.4-2).
22 3. For Tests 2 and 4, set the delay on Channel 2 to a Chip_Delay such that
23 Set_Chip_Offset of P2 =(SRCH_WIN_N/2)+10 chips, and set the delay on
24 Channel 3 to a Chip_Delay such that Set_Chip_Offset=(SRCH_WIN_N/4)+10
25 chips.
26 l. Repeat steps f to j.
30 n. Set the following values in the Universal Neighbor List Message:
3-36
C.S0044-0 v1.0
Field Value
SRCH_WIN_N 7 (40 Chips)
2
3 o. For Tests 3 and 4, repeat steps b to n using parameter values in step t sent over the
4 Universal Neighbor List Message instead of the General Neighbor List Message.
6 3.10.5.1 For section 3.9.3.1:

7 Verify 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
8 Tests 4 to 5 and Tests 21 to 22.
9 3.10.5.2 For section 3.9.3.2:

10 Verify step k for Tests 1 and 3.
11 Verify step n for Tests 2 and 4.
12 3.11 Channel Assignment into Soft Handoff (CASHO)
14 This tests for mobile operation of Channel Assignment into Soft Handoff (CASHO). CASHO
15 allows multiple pilots to be assigned in the Extended Channel Assignment Message from the
16 pilots reported in the Origination Message or Page Response Message.

19 2.6.3.1.7 Monitoring Pilots

22 None

24 a. Connect the mobile station as shown in Figure A-5. Ensure both pilot Ec/Io values are
25 well above T_ADD.
26 b. Allow the mobile station to come to the idle state on one of the base stations.
27 c. Make a mobile station originated call.
28 d. Verify both base station pilots are reported in the Origination Message.
3-37
C.S0044-0 v1.0
1 e. Verify the mobile station receives an Extended Channel Assignment Message

2 assigning both pilots and calls complete normally.
3 f. Repeat steps c-e for a mobile station terminated call with the exception that in step d
4 the Page Response Message is used instead of the Origination Message.

6 The mobile station shall comply with the requirements in steps d, e and f.
7 3.12 Traffic Channel Preamble during Hard Handoff Between Frequencies in same band
8 3.12.1 Definition
9 The mobile station is transitioned between base stations with different CDMA frequency (channel)
10 assignments in the same band. The Traffic Channel Preamble is a sequence of all-zero frames
11 that is sent by the mobile station on the Reverse Traffic Channel as an aid to Traffic Channel
12 acquisition.

19 2.1.3.2.4 Reverse Pilot Channel Operation during RTC Preamble (See [2])
20 2.1.3.6.2.3 Reverse Traffic Channel Preamble (See [2])

22 None

31 Channel 1 and Channel 2)
33
3-38
C.S0044-0 v1.0
1 Table 3.12.4-1
Îor/Ioc dBm N/A -5
3 d. Configure base station 1 and base station 2 for RC1 or RC2.

6 g. Initiate handoff from Channel 1 to Channel 2.

7 h. Verify that the base station 1 sends the General Handoff Direction Message, Universal
8 Handoff Direction Message, or Extended Handoff Direction Message with correct
9 NUM_PREAMBLE value. Verify the Reverse Traffic Channel preamble length.
10 i. Wait 20 seconds then initiate handoff from Channel 2 to Channel 1.
11 j. Verify that the base station 2 sends the General Handoff Direction Message, Universal
12 Handoff Direction Message, or Extended Handoff Direction Message correct
13 NUM_PREAMBLE value. Verify the Reverse Traffic Channel preamble length.
14 k. Configure base station 1 and base station 2 for RC3 or RC5.
15 l. Repeat steps e through j.

17 The mobile station shall comply with steps h, j, and l.
18
NUM_PREAMBLE RC1, RC2 RC>2

Preamble Length in 20 ms Preamble Length in 1.25 ms
Increments: (Total Time) Increments: (Total Time)
0 0 (0 ms) 0 (0 ms)
4 4 (80 ms) 8 (10 ms)
19
3-39
C.S0044-0 v1.0
1 3.13 Hopping Pilot Beacon
2 3.13.1 Definition
4 assignments in the same band.
5 The Hopping Pilot Beacon is a pilot beacon that changes CDMA Frequency periodically to
6 simulate multiple base stations operating on different frequencies. The transmission of the
7 hopping pilot beacon is discontinuous on any CDMA Channel.


12 2.7.4.25 Capability Information
13 3.6.1.2 Pilot Channel Operation

18 (See [1])
19 3.1.3.2.5 Hopping Pilot Beacon

21 None

23 a. Configure base station 1 and 2 for hopping pilot beacon.
24 b. Setup test as shown in A-2.
32 c. Set the test parameters as shown in Table 3.13.4-1.
33
3-40
C.S0044-0 v1.0
1 Table 3.13.4-1
Îor/Ioc dBm N/A -5
2
3 d. Set reverse link attenuation to balance forward and reverse links (approx. 90 dB).

6 g. Verify hopping pilot beacon settings in the General Neighbor List Message or Extended
7 Neighbor List Message. Initiate handoff from Channel 1 to Channel 2. Verify that the
8 base station 1 sends a General Handoff Direction Message, Universal Handoff
9 Direction Message, or an Extended Handoff Direction Message with proper parameters
10 (refer tables in Annex B).
11 h. Verify the handoff is successful
12 i. Verify hopping pilot beacon settings in the General Neighbor List Message or Extended
13 Neighbor List Message. Wait 20 seconds then initiate handoff from Channel 2 to
14 Channel 1. Verify that the base station 2 sends a General Handoff Direction Message,
15 Universal Handoff Direction Message, or an Extended Handoff Direction Message with
16 the proper parameters (refer to tables in Annex B).

18 The mobile station shall comply with steps h and i
19 3.14 Hard Handoff between Frequencies with Different Radio Configurations
22 assignments in the same band and different radio configurations.

26 2.6.6.2.8 DMA-to-CDMA Hard Handoff
3-41
C.S0044-0 v1.0

3 (See [1])
4 2.1.3.1 Reverse CDMA Channel Signals
5 3.1.3.1 Forward CDMA Channel Signals

7 None

9 a. Configure base station 1 for RC3 or RC5. Configure base station 2 for RC1 or RC2.
10 b. Setup test as shown in A-5.
19
20 Table 3.14.4-1
Îor/Ioc dBm N/A -5
21
3-42
C.S0044-0 v1.0
1 g. Initiate handoff from Channel 1 to Channel 2. Verify that the base station 1 sends a
2 General Handoff Direction Message, or Universal Handoff Direction Message with
3 proper parameters (refer to tables in Annex B)
4 h. Wait 20 seconds then initiate handoff from Channel 2 to Channel 1. Verify that the base
5 station 2 sends a General Handoff Direction Message, or Universal Handoff Direction
6 Message with the proper parameters (refer to tables in Annex B).
7 i. Configure base station 1 for RC1 or RC2. Configure base station 2 for RC3 or RC5 and
8 repeat steps b through h.
9 j. Configure base station 1 for RC3. Configure base station 2 for RC4 and repeat steps b
10 through h.

12 The mobile station shall comply with steps g, h, i and j.
13 3.15 Handoff on Same Frequency with Different Radio Configurations
15 The mobile station is transitioned between base stations with the same CDMA frequency
16 (channel) assignments in the same band and different radio configurations.
17 When the active set membership before and after the handoff are disjoint, the handoff is
18 performed as a hard handoff; when the active set membership before and after handoff are not
19 disjoint, except for the value of the radio configuration, the handoff is performed as a soft handoff.

26 (See [1])
27 2.1.3.1 Reverse CDMA Channel Signals
28 3.1.3.1 Forward CDMA Channel Signals

30 None
32 a. Configure base station 1 for RC4 or RC5. Configure base station 2 for RC1 or RC2.
33 b. Setup test as shown in Figure A-2
3-43
C.S0044-0 v1.0
5 3. The AWGN source should be added to both Channels.
7
8 Table 3.15.4-1 Hard Handoff Test Parameters
Îor/Ioc dBm N/A -5

13 g. Initiate handoff from Channel 1 to Channel 2. Verify that the base station 1 sends a
14 General Handoff Direction Message, or Universal Handoff Direction Message with
15 proper parameters (refer to tables in Annex B)
16 h. Wait 20 seconds then initiate handoff from Channel 2 to Channel 1. Verify that the base
17 station 2 sends a General Handoff Direction Message, or Universal Handoff Direction
18 Message with the proper parameters (refer to tables in Annex B).
19 i. Configure base station 1 for RC1 or RC2. Configure base station 2 for RC4 or RC5 and
20 repeat steps b through h.
21 j. Configure base station 1 for RC3. Configure base station 2 for RC4 and repeat steps b
22 through h.
23 k. Repeat steps a through j but with the following exception: Only base station 1 is used
24 for this test. The handoff messages are sent from base station 1 without changing the
25 active set, but changing the radio configuration. Thus the handoff messages simply
26 assign a new radio configuration from the same base station.
27 l. Verify that the handoff is performed as a soft handoff.
3-44
C.S0044-0 v1.0

2 The mobile station shall comply with steps g, h, i, j, and k.
3 3.16 Hard Handoff while in the Waiting for Mobile Station Answer Substate
4 3.16.1 Definition
5 This test verifies that if a hard handoff occurs while the mobile station is in the Waiting for Mobile
6 Station Answer Substate, the hard handoff will be completed successfully and the mobile station
7 shall enter the Conversation Substate on the new channel.

10 2.6.4.3.2 Waiting for Mobile Station Answer Substate
11 2.6.4.4 Conversation Substate
12 2.6.6.2.5.1 Processing of the Forward Traffic Channel Handoff Messages
13 2.6.6.2.8 CDMA to CDMA Hard Handoff
14 3.6.4.3.1 Waiting for Order Substate
15 3.6.6.2.2 Call Processing during Handoff

19 Table D-1 Time Constants
20 3.1 Standard Service Option Number Assignments (see [17])
21 3.2 Proprietary Service Option Number Assignments (see [17])

23 None

25 a. Connect the mobile station to the base station as shown in Figure A-5 and set the test
26 parameters as specified in Table 3.2.4-1.
27 1. Base station 1 is a CDMA base station with frequency F1, PN offset P1 and is
28 referred to as Channel 1.
29 2. Base station 2 is a CDMA base station with frequency F2, PN offset P2 and is
30 referred to as Channel 2.
31 b. Ensure the mobile station is operating in the Idle State on Channel 1.
32 c. Page the mobile station with a supported service option.
3-45
C.S0044-0 v1.0
1 d. After receiving the Page Response Message, instruct the base station to send an
2 Extended Channel Assignment Message with the following parameters:
3
Field Value
ASSIGN_MODE '000' or '100'
BYPASS_ALERT_ANSWER '0'
4
5 e. While the mobile station is in the Waiting for Mobile Station Answer Substate (i.e.
6 ringing), instruct the base station to send an Extended Handoff Direction Message,
7 General Handoff Direction Message, or Universal Handoff Direction Message directing
8 the mobile station to Channel 2.
9 f. If the base station sends a second (Extended) Alert with Information Message from
10 base station 2, verify the mobile station resets T53m (65 seconds) and the information
11 record(s) included override the first (Extended) Alert with Information Message. The
12 mobile station should not prompt the user to answer the call twice or indicate a “missed
13 call.”
14 g. After the hard handoff has been completed and before T53m (65 seconds), has expired
15 direct the user to answer the call.
16 h. Verify the mobile station enters the Conversation Substate and user traffic is present in
17 both directions (i.e. audio).
18 i. End the call.

19 j. Repeat steps b through j using different service options and radio configurations
20 supported by the mobile station and base station.
21 k. Repeat steps b through j, changing Channel 2 to a band class that is different from
22 Channel 1 but is supported by the mobile station.

24 The mobile station shall comply with steps h and j.
25 3.17 Inter-Frequency Hard Handoff (CDMA to CDMA)
27 In an Inter-Frequency Hard Handoff test (also known as the Mobile Assisted Hard Handoff test),
28 when the mobile station is directed by the base station to perform a search on a Candidate
29 Frequency, the mobile station will search for a pilot in the Candidate Frequency Neighbor Set.
30 The mobile station will report back to the base station any pilot detected in the Candidate
31 Frequency Neighbor Set with a pilot Ec/Io above the value defined by CF_T_ADD. The base
32 station should then direct the mobile station to the Candidate Frequency and completes the hard
33 handoff.
3-46
C.S0044-0 v1.0


4 2.7.2.3.2.20 Candidate Frequency Search Report Message
6 3.7.7.3.3.2.27 Candidate Frequency Search Request Message

8 None

11 1. The Forward Channel from base station 1 has a CDMA frequency assignment F1
12 (any valid value), an arbitrary pilot PN offset index P1 and is called Channel 1.
14 (any valid value other than f1 in the same band class), an arbitrary pilot PN offset
15 index P2 and is called Channel 2.
16
Îor/Ioc dB 2.9 2.9
Pilot E c dB -7 -7
I or
Traffic E c dB -7 N/A
I or
Pilot E c dB -11.0 -11.0

I0
17
18 b. Reverse Link attenuation should be set to balance the forward and reverse links.
19 c. Set up a mobile station originated call on Channel 1.
20 d. Send from base station 1 a Candidate Frequency Search Request Message to the
21 mobile station to set an explicit action time with the following parameters:
22
3-47
C.S0044-0 v1.0
Field Value (Decimal)
USE_TIME 1 (use action time)
SEARCH_TYPE 1 (single search)
SEARCH_MODE 0 (CDMA)
CDMA_FREQ F2
SF_TOTAL_EC_THRESH 31 (disabled)
SF_TOTAL_EC_IO_THRESH 31 (disabled)
CF_SRCH_WIN_N 8 (60 chips)
CF_T_ADD 28 (-14 dB)
NUM_PILOTS 1 (1 pilot)
CF_NGHBR_SRCH_MODE 0 (no search priorities or search

windows specified)
NGHBR_PN P2
2 e. Verify that the mobile station responds with a Candidate Frequency Search Report
3 Message.
4 f. Verify that base station 1 sends a General Handoff Direction Message, an Extended
5 Handoff Direction Message or a Universal Handoff Direction Message to initiate handoff
6 from base station 1 to base station 2.

9 The mobile station shall comply with steps e and g.
10 3.18 Inter-Frequency Hard Handoff (CDMA to Analog)
12 In an Inter-Frequency Hard Handoff test (also known as the Mobile Assisted Hard Handoff test),
13 when the mobile station is directed by the base station to perform a search on a Candidate
14 Frequency, the mobile station will search for an analog channel in the Candidate Frequency
15 Analog Search Set and shall measure the mean input power on the analog frequency. The
16 mobile station will report back to the base station the signal strength of the analog channel
17 searched. The base station should then direct the mobile station to the Analog Channel and
18 completes the hard handoff.
3-48
C.S0044-0 v1.0


4 2.6.6.10.2 Candidate Frequency Analog Search Set
5 2.7.2.3.2.21 Candidate Frequency Search Report Message

7 3.7.7.3.3.2.27 Candidate Frequency Search Request Message

9 None

13 (any valid value), an arbitrary pilot PN offset index P1 and is called Channel 1.
14 2. The Forward Channel from base station 2 uses an analog frequency called
15 Channel 2.
16 b. Set the test parameters as specified in Table 3.15.4-1 and Table 3.18.4-2
17
18 Table 3.18.4-1 Test Parameters for Inter-Frequency Hard Handoff (Channel 1)
CDMA Parameter Unit Channel 1
Îor/Ioc dB 0
Pilot Ec/Ior dB -7
Traffic Ec/Ior dB -7
Pilot Ec/Io dB -10
19
20
21 Table 3.18.4-2 Test Parameter for Inter-Frequency Handoff (Channel 2)
Analog Parameter Unit Channel 2
Voice Channel dBm -73
Co-Channel Interference dB -18
3-49
C.S0044-0 v1.0
1 c. Reverse Link attenuation should be set to balance the forward and reverse links.
2 d. Set up a mobile station originated voice call on Channel 1.
3 e. Send from base station 1 a Candidate Frequency Search Request Message to the
4 mobile station to set an explicit action time with the following parameters:
5
USE_TIME 1 (use action time)
SEARCH_TYPE 1 (single search)
SEARCH_MODE 1 (search for analog channels)
SF_TOTAL_EC_THRESH 31 (disabled)
SF_TOTAL_EC_IO_THRESH 31 (disabled)
NUM_ANALOG_FREQS 1
ANALOG_FREQ Channel 2
7 f. Verify that the mobile station responds with a Candidate Frequency Search Report
8 Message.
9 g. Verify that base station 1 sends an Analog Handoff Direction Message to initiate
10 handoff from base station 1 to base station 2.
11 h. Verify audio in both directions.

13 The mobile stations shall comply with steps f and h.
14 3.19 Hard Handoff between Frequencies with Different Protocol Revisions
16 This test verifies the mobile station is able perform a hard handoff between base stations
17 supporting using different protocol revisions (P_REV).

3-50
C.S0044-0 v1.0



6 None

8 a. Configure base station one and base station two with different protocol revisions.
9 b. Verify the mobile station supports the protocol revisions on each base station.
10 c. Setup test as shown in Figure A-5.
11 1. The Forward Channel from base station one has an arbitrary pilot PN offset index
13 2. The Forward Channel from base station two has an arbitrary pilot PN offset index
18 d. Set the test parameters as shown in Table 3.19.4-1.
19
20 Table 3.19.4-1 Hard Handoff Test Parameters
Îor/Ioc dBm N/A -5
21
22 e. Set reverse link attenuation to balance forward and reverse links (approx. 90 dB).
23 f. Setup a mobile station originated call on Channel 1.
24 g. Verify user traffic in both directions.
25 h. Initiate handoff from Channel 1 to Channel 2.
3-51
C.S0044-0 v1.0
1 i. Verify that the base station 1 sends General Handoff Direction Message, Universal
2 Handoff Direction Message, or Extended Handoff Direction Message with the P_REV
3 field value equal to the P_REV of base station two.
4 j. Verify the handoff is successful and user traffic is present in both directions.

6 The mobile station shall comply with step j.
3-52
C.S0044-0 v1.0
1 4 POWER CONTROL
2 4.1 Forward Traffic Channel Power Control
3 4.1.1 Definition
4 This test verifies that the mobile station reports frame error rate statistics at specified intervals if
5 the base station enables periodic reporting, and verifies that the mobile station reports frame error
6 rate statistics when the frame error rate reaches a specified threshold if the base station enables
7 threshold reporting.

9 2.6.4.1.1 Forward Traffic Channel Power Control
10 2.7.2.3.2.6 Power Measurement Report Message

12 3.7.3.3.2.10 Power Control Parameters Message
13 Applicability: Forward Link: RC 1 through RC 5; Reverse Link: RC 1 through RC 4

15 None

17 a. Setup test as shown in Annex A Figure A-6.
18 b. Setup a mobile station originated call using the test parameters for Test 1 as specified
19 in Table 4.1.4-1.
20 c. Set the AWGN source power so the forward link average FER is between 0.5 and
21 1.0%.
22 d. Instruct the base station to send the Power Control Parameters Message to enable the
23 threshold reporting and disable the periodic reporting according to the base station
24 manufacturer's forward power control algorithm.
25
PWR_THRESH_ENABLE ‘1’ (Enable threshold reporting)
PWR_PERIOD_ENABLE ‘0’ (Disable periodic reporting)
26
27 e. Using Attenuator 1, alternately increase and decrease AWGN source output power by 5
28 dB from the original power set in step c.
29 f. Monitor forward traffic channel Ec/Ior and ensure power increases and decreases
30 corresponding to noise power from the AWGN source.
31 g. Monitor forward link FER at the mobile station.
32
4-1
C.S0044-0 v1.0
2 Table 4.1.4-1 Test Parameters for Forward Power Control Tests
Test Forward Reverse Threshold/Pe Service Option Channels Forward Link

Number RC RC riodic Power [dBm/
1.23 MHz]
1 1 1 Threshold 2, 54, 55, or F-FCH -65

32798
2 1 1 Periodic 2, 54, 55, or F-FCH -65

32798
3 2 2 Threshold 9, 54, 55, or F-FCH -62

32799
4 2 2 Periodic 9, 54, 55, or F-FCH -62

32799
5 3 3 Threshold 54, or 55 F-FCH -65
6 3 3 Periodic 54, or 55 F-FCH -65
7 3 3 Threshold 54, or 55 F-DCCH -65
8 3 3 Periodic 54, or 55 F-DCCH -65
17 3 3 N/A 54, or 55 F-FCH/F-SCH -65
18 4 3 N/A 54, or 55 F-FCH/F-SCH -65
19 5 4 N/A 54, or 55 F-FCH/F-SCH -62
20 3 3 N/A 54, or 55 F-DCCH/F- -65

SCH
21 4 3 N/A 54, or 55 F-DCCH/F- -65

SCH
4-2
C.S0044-0 v1.0
SCH
22 5 4 N/A 54, or 55 F-DCCH/F- -62

SCH
1 Note: All tests should be performed at full data rate or at a variable rate. Tests involving the
2 Forward Supplemental Channels should only include 1 Forward Supplemental Channel.
3
4 h. Verify MS sends the Power Measurement Report Message when the bad frames
5 received by the mobile station reaches the specified threshold.
6 i. End the call.
7 j. Setup a mobile station originated call using the test parameters for Test 2 as specified
8 in Table 4.1.4-1.
9 k. Instruct the base station to send the Power Control Parameters Message to enable the
10 periodic reporting and disable the threshold reporting according to the base station
11 manufacturer's forward power control algorithm.
12
PWR_THRESH_ENABLE ‘0’ (Disable threshold reporting)
PWR_PERIOD_ENABLE ‘1’ (Enable periodic reporting)
13
14 l. Repeat the steps e through g.

15 m. Verify the mobile station sends the Power Measurement Report Message when the
16 total frames received by the mobile station reach the specified report period.
17 n. End the call.

18 o. Repeat steps b through n except for using the test parameters for Tests 3 to 16 as
20 p. Repeat steps b through c except for using the test parameters for Test 17 to Test 22 as
22 q. Instruct the base station to send the Extended Supplemental Channel Assignment
23 Message including a Forward Supplemental Channel assignment and setting
24 FOR_SCH_FER_REP to ‘1’.
25 r. Repeat the steps e through g.
26 s. Verify the mobile station sends the Power Measurement Report Message at the end of
27 the burst.
28 t. End the call.

30 The mobile station shall comply with steps h, l, m, o, p, r and s.
4-3
C.S0044-0 v1.0
1 The base station should alternately increase and decrease the forward traffic channel power
2 according to the base station manufacturer's forward power control algorithm. Forward link FER
3 measured at the mobile station should be within the target value and the mobile station shall
4 report frame error rate statistics. There shall not be any dropped calls.
5 4.2 Fast Forward Power Control (FFPC)
6 4.2.1 FFPC using different values of FPC_MODE (FPC_MODE = ‘000’, ‘001’, ‘010’)
7 4.2.1.1 Definition
8 The mobile station accomplishes fast forward power control by transmitting the Reverse Power
9 Control Subchannel to the base station on the Reverse Pilot Channel. The mobile station
10 determines the information to be sent to the base station through inner and outer loop
11 estimations. In outer loop estimation, the mobile station adjusts the Eb/Nt setpoint to the Eb/Nt
12 value necessary to achieve the target FER on the Forward Traffic Channel. In inner loop
13 estimation, the mobile station compares the received Eb/Nt to the setpoint and determines the
14 value of the power control bit to be sent to the base station. There are 16 Power Control Groups
15 every 20 ms on the Reverse Power Control Subchannel. This test verifies that the mobile station
16 can process the various parameters in the Extended Channel Assignment Message, the
17 Extended Supplemental Channel Assignment Message, and the Service Connect Message.
18 4.2.1.2 Traceability: (See [1] )
19 2.1.3.1.11 Reverse Power Control Subchannel
20 (See [4] )
22 3.6.6.2.2.12 Processing of Extended Supplemental Channel Assignment Message
23 3.7.3.3.2.37 Extended Supplemental Channel Assignment Message
27 3.6.3.3 Response to Page Response Message
31 2.6.4.1.2.2 Service Subfunctions
35 3.7.5.20 Non negotiable System Configuration

36
4-4
C.S0044-0 v1.0

2 FPC_MODE Information
3
4 Table 4.2.1-1 Reverse Power Control Subchannel Configurations
Reverse Power Control Subchannel Allocations

(Power Control Group Numbers)
FPC_MODE Primary Reverse Power Control Subchannel Secondary Reverse Power

Control Subchannel
‘000’ 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 Not supported
‘001’ 0,2,4,6,8,10,12,14 1,3,5,7,9,11,13,15
‘010’ 1,5,9,13 0,2,3,4,6,7,8,10,11,12,14,15
6 4.2.1.3 Call Flow Example(s)

7 None
8 4.2.1.4 Method of Measurement
9 4.2.1.4.1 FPC_MODE ‘000’; F-FCH Only

10 a. Connect base station and mobile station as shown in Annex A Figure A-6.
11 b. Set power levels as stated in Table 4.2.1-2:
12 Table 4.2.1-2 Test Parameters for Fast Forward Power Control
Pilot E c
I or dB -7
Ior/Ioc dB 10
13
14 c. Setup a mobile station originated call using Service Option 55 (Loopback Service
15 Option) or Service Option 54 (Markov Service Option).
16 d. Instruct the base station to send the Extended Channel Assignment Message with the
17 parameters set as follows:
4-5
C.S0044-0 v1.0
ASSIGN_MODE = '100' GRANTED_MODE = '10'
FOR_RC = '00011' (RC 3) REV_RC = '00011' (RC 3)
CH_IND = '01' FPC_FCH_INIT_SETPT = '01000000'

(8 dB)
FPC_FCH_FER = '00010' (1%) FPC_FCH_MIN_SETPT = '00010000'

(2 dB)
FPC_FCH_MAX_SETPT =
'10000000' (16 dB)
2
3 e. Ensure the base station sends the Service Connect Message with FPC_INCL set to ‘0’.
4 f. Monitor the forward link FER at the mobile station.
5 g. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at
6 the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a
7 total of 20 dBm/1.23 MHz at the AWGN source.
8 h. Monitor traffic channel Ec/Ior and ensure the power changes corresponding to noise
9 power from the AWGN source. The power increases if the noise power increases and
10 decreases if the noise power decreases.
11 i. Verify that the forward link FER on the FCH remains at approximately the target value
12 (i.e. 1%).
13 j. End the call at the mobile station.
14 k. Repeat steps a through j above except that FOR_RC is set to RC4 and REV_RC is set
15 to RC3 in step d.
16 l. Repeat steps a through j above except that FOR_RC is set to RC5 and REV_RC is set
17 to RC4 in step d .
18 4.2.1.4.2 FPC_MODE ‘000’; F-DCCH only

Pilot E c
I or dB -7
4-6
C.S0044-0 v1.0
Ior/Ioc dB 10
1
2 c. Setup a mobile station originated call using Service Option 32 (Test Data Service
3 Option).
6
ASSIGN_MODE = ‘100’ GRANTED_MODE = ‘10’
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)
CH_IND = ‘10’ FPC_DCCH_INIT_SETPT =

‘01000000’ (8 dB)
FPC_DCCH_FER = ‘00010’ (1%) FPC_DCCH_MIN_SETPT =

‘00010000’ (2 dB)
FPC_DCCH_MAX_SETPT =
‘10000000’ (16 dB)
8 e. Ensure the base station sends the Service Connect Message with FPC_INCL set to ‘0’.
9 f. Monitor the forward link FER at the mobile station.
13 h. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power
14 from the AWGN source. The power increases if the noise power increases and
16 i. Verify that the forward link FER on DCCH remains at approximately the target value
17 (1%).
18 j. End the call at the mobile station.
19 k. Repeat steps a through i above except for setting FOR_RC to RC4 and REV_RC to
20 RC3 in step d.
21 l. Repeat steps a through i above except for setting FOR_RC to RC5 and REV_RC to
22 RC4 in step d.
23 4.2.1.4.3 FPC_MODE ‘001’; F-FCH and F-SCH

4-7
C.S0044-0 v1.0

2
Pilot E c
I or dB -7
Ior/Ioc dB 10
4
6 Option).
9
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)
CH_IND = ‘01’ FPC_FCH_INIT_SETPT =

‘01000000’ (8 dB)
FPC_FCH_FER = ‘00010’ (1%) FPC_FCH_MIN_SETPT =

‘00010000’ (2 dB)
FPC_FCH_MAX_SETPT =
‘10000000’ (16 dB)
10
11 e. Instruct the base station to send the Service Connect Message with the parameters set
12 as follows:
13
FPC_INCL = ‘1’ FPC_OLPC_FCH_INCL = ‘0’
FPC_PRI_CHAN = ‘0’ GATING_RATE_INCL = ‘0’
FPC_MODE = ‘001’
14
4-8
C.S0044-0 v1.0
1 f. Instruct the base station to download SCH configuration and assign a Forward
2 Supplemental Channel by using the Extended Supplemental Channel Assignment
3 Message and set the power control related fields as stated in follows:
4
FPC_INCL = ‘1’ FPC_SCH_INIT_SETPT =

‘01000000’ (8 dB)
FPC_MODE_SCH = ‘001’ FPC_SCH_MAX_SETPT =

‘10000000’ (16 dB)
FPC_SCH_INIT_SETPT_OP = ‘0’ FPC_SCH_MIN_SETPT =

‘00010000’ (2 dB)
FPC_SCH_FER = ‘01010’ (5%)
6 g. Monitor the forward link FER on FCH and SCH (during the burst assignment) at the
7 mobile station.
8 h. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at
11 i. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power
14 j. Verify that the forward link FERs on FCH and SCH (during SCH assignment) remain at
15 approximately the target values.
16 k. End the call at the mobile station.
17 l. Repeat steps a through k above except that FOR_RC is set to RC4 and REV_RC is set
19 m. Repeat steps h through k above except that FOR_RC is set to RC5 and REV_RC is set
21 4.2.1.4.4 FPC_MODE ‘000’ without F-SCH Active and FPC_MODE ‘001’ with F-SCH Active; F-
22 DCCH and F-SCH
4-9
C.S0044-0 v1.0
Pilot E c
I or dB -7
Ior/Ioc dB 10
1
3 Option).
6
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)

‘01000000’ (8 dB)

‘00010000’ (2 dB)
‘10000000’ (16 dB)
8 e. Instruct the base station to send the Service Connect Message with FPC_INCL set to
9 ‘0’.
10 f. Instruct the base station to download the SCH configuration and assign a Forward
11 Supplemental Channel using the Extended Supplemental Channel Assignment
12 Message and set the power control related information as follows:
13

‘01000000’ (8 dB)

‘10000000’ (16 dB)

‘00010000’ (2 dB)
FPC_SCH_FER = ‘01010’ (5%)
14
4-10
C.S0044-0 v1.0
1 g. Monitor the forward link FER on both F-DCCH and F-SCH (during SCH assignment) at
9 j. Verify that the forward link FER on DCCH and SCH (during SCH assignment) remains
10 at approximately the target value.
12 l. Repeat steps a through k above except that FOR_RC is set to RC4 and REV_RC is set
14 m. Repeat steps a through k above except that the FOR_RC is set to RC5 and REV_RC is
15 set to RC4 in step d.
17 FCH and F-SCH
Pilot E c
I or dB -7
Ior/Ioc dB 10
21
23 Option).
26
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)
4-11
C.S0044-0 v1.0

‘01000000’ (8 dB)

‘00010000’ (2 dB)
FPC_FCH_MAX_SETPT =
‘10000000’ (16 dB)
3 ‘0’.
6 Message with power control related parameters set as follows:
7

‘01000000’ (8 dB)

‘10000000’ (16 dB)

‘00010000’ (2 dB)
FPC_SCH_FER = ‘01010’ (5%)
8 g. Monitor the forward link FER on both FCH and SCH (during the SCH assignment) at
16 j. Verify that the forward link FERs on FCH and SCH (during SCH assignment) remain at
17 approximately the target values.

19 l. Repeat steps a through k above except for step d to set FOR_RC to RC4 and REV_RC
20 to RC3.
21 m. Repeat steps a through k above except for step d to set FOR_RC to RC5 and REV_RC
22 to RC4.
4-12
C.S0044-0 v1.0
1 4.2.1.4.6 FPC_MODE ‘010’; F-DCCH and F-SCH

Pilot E c
I or dB -7
Ior/Ioc dB 10
5
7 Option).
9 parameters set as follows.
10
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)

‘01000000’ (8 dB)

‘00010000’ (2 dB)
‘10000000’ (16 dB)
11
13 as follows:
14
15
4-13
C.S0044-0 v1.0
1 f. Instruct the base station to send SCH configuration and assign a Forward Supplemental
2 Channel by using the Extended Supplemental Channel Assignment Message with
3 power control related parameters set as follows:
4

‘01000000’ (8 dB)

‘10000000’ (16 dB)

‘00010000’ (2 dB)
FPC_SCH_FER = ‘01010’ (5%)
5
6 g. Monitor forward link FER on both F-DCCH and F-SCH (during SCH burst assignment)
7 at the mobile station.
14 j. Verify that the forward link FERs on the DCCH and SCH (during SCH assignment)
15 remain at approximately the target values.

17 l. Repeat steps a through k above except for step d to set FOR_RC to RC4 and REV_RC
18 to 3.
19 m. Repeat steps a through k above except for step d to set FOR_RC to RC5 and REV_RC
20 to 4.
21 4.2.1.5 Minimum Standard
22 4.2.1.5.1 FPC_MODE ‘000’; F-FCH Only

23 The mobile station shall comply with step i, k, and l.
24 4.2.1.5.2 FPC_MODE ‘000’; F-DCCH only

25 The mobile station shall comply with step i, k, and l.
26 4.2.1.5.3 FPC_MODE ‘001’; F-FCH and F-SCH

27 The mobile station shall comply with step j, l, and m.
4-14
C.S0044-0 v1.0
1 DCCH and F-SCH

4 FCH and F-SCH
6 4.2.1.5.6 FPC_MODE ‘010’; F-DCCH and F-SCH

8
9 4.2.2 Outer Loop Report
11 This test verifies that the mobile station shall send the Outer Loop Report Message if the Outer
12 Loop Report Request Order is received.

15 (See [4] )
17 3.6.6.2.212 Processing of Extended Supplemental Channel Assignment Message
32 2.7.2.3.2.22 Outer Loop Report Message
4-15
C.S0044-0 v1.0
1 3.7.3.3.2.25 Power Control Message

2

5 None

Pilot E c dB -7
I or
Ior/Ioc dB 10
10
12 Option).
15
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)

‘01000000’ (8 dB)

‘00010000’ (2 dB)
FPC_FCH_MAX_SETPT =
‘10000000’ (16 dB)
16
18 ‘0’.
4-16
C.S0044-0 v1.0
3 Message with power control related parameters set as follows:
4

‘01000000’ (8 dB)

‘10000000’ (16 dB)

‘00010000’ (2 dB)
FPC_SCH_FER = ‘01010’ (5%)
6 g. Monitor the forward link FER on both FCH and SCH (during the SCH assignment) at
14 j. During the F-SCH assignment, instruct the base station to send Outer Loop Report
15 Request Order.
16 k. Verify the mobile station sends the Outer Loop Report Message and this message
17 contains FPC_FCH_CURR_SETPT and FPC_SCH_CURR_SETPT. The FPC current
18 setpoint reported by the mobile station shall be in the range of the minimum setpoint
19 and the maximum setpoint
20 l. End the call at the mobile station.
21 m. Repeat steps a through l above except for the following steps:

22 n. Instruct the base station to send the Extended Channel Assignment Message with the
24
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)

‘01000000’ (8 dB)

‘00010000’ (2 dB)
4-17
C.S0044-0 v1.0
‘00010000’ (2 dB)
‘10000000’ (16 dB)
1
2 o. Monitor the forward link FER on both DCCH and SCH (during the SCH assignment at
4 p. Verify the mobile station sends the Outer Loop Report Message and this message
5 contains FPC_DCCH_CURR_SETPT and FPC_SCH_CURR_SETPT. The FPC current
6 setpoint reported by the mobile station shall be in the range of the minimum setpoint
7 and the maximum setpoint

9 The mobile station shall comply with steps k, m, and p.
10 4.2.3 Fast Forward Power Control (FFPC) in Soft Handoff
12 The mobile station accomplishes fast forward power control by transmitting the Reverse Power
13 Control Subchannel to the base station on the Reverse Pilot Channel. The mobile station
14 determines the information to send to the base station through inner and outer closed loop
15 estimations. In outer loop estimation, the mobile station adjusts the Eb/Nt setpoints to the Eb/Nt
16 value necessary to achieve the target FER on the Forward Traffic Channel. In inner loop
17 estimation, the mobile station compares the received Eb/Nt to the setpoint and determines the
18 value of the power control bit to be sent to the base station. This test verifies that the mobile
19 station can perform FFPC while in soft handoff. This test also verifies that the mobile station can
20 process the various parameters in the Extended Channel Assignment Message, the Extended
21 Supplemental Channel Assignment Message, the Universal Handoff Direction Message, and the
22 Service Connect Message.
23 4.2.3.2 Traceability:
24 (See [1] )
26 Traceability: (See [4] )

4-18
C.S0044-0 v1.0



8

11 None
13 4.2.3.4.1 F-FCH in SHO and F-SCH not in SHO; FPC_MODE = 001

14 a. Setup the test as shown in Annex A Figure A-7.
15 b. Set power levels as stated in Table 4.2.3-1.

Parameter Unit Base station 1 Base station 2
Ioc dBm/1.23 MHz -75 -75
Ior/Ioc dB 10 10
17
19 Option) on base station 1.
22
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)

‘01000000’ (8 dB)
4-19
C.S0044-0 v1.0
‘01000000’ (8 dB)

‘00010000’ (2 dB)
FPC_FCH_MAX_SETPT =
‘10000000’ (16 dB)
1
3 as follows:
4
5
8 Message with the power control related parameters set as follows:
9

‘01000000’ (8 dB)

‘10000000’ (16 dB)

‘00010000’ (2 dB)
FPC_SCH_FER = ‘01010’ (5%)
10
11 g. Raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after
13 Message.
14 h. Instruct the base station to send the Universal Handoff Direction Message during F-
15 SCH assignment with the parameters set as follows:
16
CH_IND = ‘101’ (FCH and NUM_PILOTS = ‘010’

Continuous Reverse Pilot)
For PILOT_PN = {base station 1} PILOT_INCL = ‘1’
4-20
C.S0044-0 v1.0
2 i. Verify there are no forward supplemental channels transmitting on base station 2.

3 j. Set the test parameters as specified in Table 4.2.3-2without dropping the call.
Ioc dBm/1.23 MHz -75 -75
6 k. Monitor the forward link FER on both F-FCH and F-SCH (during F-SCH assignment) at
8 l. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at
11 m. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power
14 n. Verify that the forward link FERs on FCH and SCH (during SCH assignment) remain at
15 approximately in the target value.
16 o. End the call at the mobile station.
17 4.2.3.4.2 F-FCH in SHO and F-SCH not in SHO; FPC_MODE = ‘010’

21 Option) with 100% frame activity on base station 1.
24
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)
4-21
C.S0044-0 v1.0

‘01000000’ (8 dB)

‘00010000’ (2 dB)
FPC_FCH_MAX_SETPT =
‘10000000’ (16 dB)
3 as follows:
4
9

‘01000000’ (8 dB)

‘10000000’ (16 dB)

‘00010000’ (2 dB)
FPC_SCH_FER = ‘01010’ (5%)
10
13 Message.
15 SCH assignment with parameters set as follows:
16

4-22
C.S0044-0 v1.0
2 i. Verify there are no forward supplemental channels running on base station 2.

4 k. Monitor the forward link FER on both F-FCH and F-SCH (during F-SCH assignment) at
12 n. Verify that the forward link FERs on FCH and SCH (during SCH assignment) remain at
13 approximately in the target value.
15 4.2.3.4.3 F-DCCH in SHO and F-SCH not in SHO; FPC_MODE = ‘001’

22
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)

‘01000000’ (8 dB)

‘00010000’ (2 dB)
‘10000000’ (16 dB)
23
4-23
C.S0044-0 v1.0
2 as follows:
3
4
8

‘01000000’ (8 dB)

‘10000000’ (16 dB)

‘00010000’ (2 dB)
FPC_SCH_FER = ‘01010’ (5%)
9
12 Message.
15

16
19 k. Monitor the forward link FER on both F-DCCH and F-SCH (during F-SCH assignment)
4-24
C.S0044-0 v1.0
7 n. Verify that the forward link FERs on DCCH and SCH (during SCH assignment) remain
8 at approximately in the target value.

17
ASSIGN_MODE = ‘100’ GRANTED_MODE = 10
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)

‘01000000’ (8 dB)

‘00010000’ (2 dB)
‘10000000’ (16 dB)
18
20 as follows:
21
22
4-25
C.S0044-0 v1.0
4

‘01000000’ (8 dB)

‘10000000’ (16 dB)

‘00010000’ (2 dB)
FPC_SCH_FER = ‘01010’ (5%)
8 Message.
11

12
14 j. Set the test parameters as specified in Table 4.2.3-2 without dropping the call.
15 k. Monitor the forward link FER on both F-DCCH and F-SCH (during F-SCH assignment)
23 n. Verify that the forward link FERs on DCCH and SCH (during SCH assignment) remain
24 at approximately in the target value.
4-26
C.S0044-0 v1.0
2 4.2.3.5.1 F-FCH in SHO and F-SCH not in SHO; FPC_MODE = 001

3 The mobile station shall comply with steps i and n.
4 4.2.3.5.2 F-FCH in SHO and F-SCH not in SHO; FPC_MODE = ‘010’



10
11 For all tests, the call shall not drop and the FER shall remain in the target value.
12 4.2.4 Change FPC_MODE During a Call
14 The mobile station accomplishes fast forward power control by transmitting the power control
15 subchannel to the base station on the R-PICH. The mobile station determines the information to
16 send to the base station through inner and outer closed loop estimations. In outer loop estimation,
17 the mobile station adjusts the Eb/Nt setpoints to the Eb/Nt value necessary to achieve the target
18 FER on the Forward Traffic Channel.
19 In inner loop estimation, the mobile station compares the received Eb/Nt to the setpoint and
20 determines the value of the power control bit to be sent to the base station. This test verifies that
21 the mobile station can process a change in FPC_MODE delivered by the Power Control
22 Message.

25 (See [4] )
26 2.6.4.1.1.3 Processing the Power Control Message

4-27
C.S0044-0 v1.0


6 Applicability: RC 3 and greater

8 None

11 b. Set power levels as stated in Table 4.2.1-2
13 Option) with 100% frame activity.
16
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)

‘01000000’ (8 dB)

‘00010000’ (2 dB)
FPC_FCH_MAX_SETPT =
‘10000000’ (16 dB)
17
19 ‘0’.
20 f. Monitor forward link FER at the mobile station.
22 the AWGN source.
23 h. Monitor traffic channel Ec/Ior and ensure power increases corresponding to noise
24 power from the AWGN source.
25 i. Instruct the base station send the Power Control Message with the parameters set as
26 follows:
4-28
C.S0044-0 v1.0
FPC_INCL = ‘1’ FPC_MODE = ‘010’
FPC_PRI_CHAN = ‘0’ FPC_OLPC_FCH_INCL = ‘1’
FPC_FCH_FER = ‘00100’ (2%) PWR_CNTL_STEP = ‘000’ (1dB)‘
FPC_FCH_MIN_SETPT = ‘00010000’ FPC_FCH_MAX_SETPT =

(2 dB) ‘10000000’ (16 dB)
FPC_OLPC_DCCH_INCL = ‘0’
FPC_DCCH_MIN_SEPT = N/A FPC_DCCH_MAX_SEPT = N/A
FPC_OLPC_SCH_M_INCL = ‘1’ FPC_SCH_M_FER = ‘00010’ (1%)
FPC_MIN_SCH_M_SETPT = FPC_MAX_SCH_M_SETPT =
‘00010000’ (2 dB) ‘10000000’ (16 dB)
NUM_SUP = 0
2
3 j. Monitor forward link FER at the mobile station.
4 k. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 5 dBm/1.23 MHz at
7 l. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power
10 m. Verify that the forward link FER on FCH remains at approximately the target value.
11 n. End the call at the mobile station.

13 The mobile station shall comply with step m.
14
15 4.2.5 R-PICH in Gated Transmission Mode
16 4.2.5.1 Gating with the Reverse Dedicated Control Channel
19 subchannel to the base station on the R-PICH. The power control subchannel can either be gated
20 (either at a rate of ½ or ¼) or not gated (a bit is transmitted on every PCG). Gating occurs only
21 when the Forward Dedicated Control Channel and the Reverse Dedicated Control Channel are
22 assigned and when there are no transmissions on the Reverse Dedicated Control Channel. This
4-29
C.S0044-0 v1.0
1 test verifies that the mobile station can operate in the various gating transmission modes
2 specified in the Service Connect Message.
3 Figure 4.2.5.1.1-1 Reverse Pilot Gating with no Transmission

4 on the Reverse Dedicated Control Channel
4-30
C.S0044-0 v1.0
1 Figure 4.2.5.1.1-2 Reverse Pilot Gating during

2 Reverse Dedicated Control Channel Transmission

5 2.1.3.2 Reverse Pilot Channel
6 (See [4] )

21
4-31
C.S0044-0 v1.0

3 None

5 a. Connect base station and mobile station as shown in Annex A Figure A-6
7 c. Setup a mobile station originated data call using Service Option 33.
8 d. Instruct the base station to send the Extended Channel Assignment Message has the
10
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)

‘01000000’ (8 dB)

‘00010000’ (2 dB)
‘10000000’ (16 dB)
11
12 e. Instruct the base station to send the Service Connect Message has the parameters set
13 as follows:
14
FPC_PRI_CHAN = ‘1’ FPC_OLPC_DCCH_INCL = ‘0’
GATING_RATE_INCL = ‘1’ PILOT_GATE_RATE = ‘01’ (gating at

½)
15
16 f. Instruct the base station to send the Extended Release Message with CH_IND set to
17 ‘100’.
18 g. Do not have any transmissions on the Reverse Dedicated Control Channel.
19 h. Instruct the base station to send a sufficient number of In-Traffic System Parameters
20 Messages with the same system configurations and without requiring the
4-32
C.S0044-0 v1.0
1 acknowledgment on the reverse link DCCH so that the mobile station can measure
2 forward FER.
3 i. Monitor forward link FER at the mobile station.
4 j. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 5 dBm/1.23 MHz at
7 k. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power
10 l. Verify that the reverse Pilot Channel is gated at the specified rate and the forward link
11 FER on DCCH remains at approximately the target value
12 m. Instruct the mobile station to send the Data Burst Message on the Reverse Dedicated
13 Control Channel.
14 n. Monitor the forward link FER at mobile station.
15 o. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 5 dBm/1.23 MHz at
18 p. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power
21 q. Verify that the reverse Pilot Channel is gated at the target rate if no transmissions are
22 on the Reverse Dedicated Control Channel and the reverse Pilot Channel is not gated if
23 there are transmissions on the Reverse Dedicated Control Channel.
24 r. Verify that the forward link FER on DCCH remains at approximately the target value.
25 s. End the call at the mobile station. Repeat steps a through r above except for step e to
26 set PILOT_GATE_RATE to ‘10’ (gating at ¼).

28 Gating with the Reverse Dedicated Control Channel
29 The mobile station shall comply with steps l, q, and r.
30 4.2.7 Gating with the Reverse Fundamental Channel
33 subchannel to the base station on the R-PICH. The power control subchannel can either be gated
34 or not gated. The R-FCH may be gated when no other Reverse Traffic Channel is assigned and
35 the data rate is 1500 bps for RC 3 and RC5 or 1800 bps for RC4. When the R-FCH is operated in
36 the gated mode and is at a data rate of 1500 bps for RC 3 and RC 5 or 1800bps for RC 4, the R-
37 PICH shall have a transmission duty cycle of 50%. The R-PICH shall be transmitted in power
38 control groups 2, 3, 6, 7, 10, 11, 14, and 15, and shall not be transmitted in power control groups
39 0, 1, 4, 5, 8, 9, 12, and 13.
4-33
C.S0044-0 v1.0
1
2 Figure 4.2.5.2.1-1 Gating with the R-FCH

5 2.1.3.2 Reverse Pilot Channel
6 2.1.3.7.8 Reverse Fundamental Channel
7 Traceability: (See [4] )


12 Extended Supplemental Channel Assignment Message
4-34
C.S0044-0 v1.0


5 Applicability: RC 3 and greater

7 None


12 Option) with rate 1500 bps only and set the REV_FCH_GATING_REQ field to ‘1’ in the
14 d. Instruct the base station to send the Extended Channel Assignment Message has the
15 parameters set as follows and set the REV_PWR_CNTL_DELAY field according to the
16 base station’s implementation.
17
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)

‘01000000’ (8 dB)

‘00010000’ (2 dB)
FPC_FCH_MAX_SETPT = REV_FCH_GATING_MODE = ‘1’

‘10000000’ (16 dB)
REV_PWR_CNTL_DELAY_INCL =
‘1’
18
20 ‘0’.
21 f. Ensure the Reverse Fundamental Channel is transmitted at 1/8 rate.
22 g. Monitor forward link FER at the mobile station.
4-35
C.S0044-0 v1.0
7 j. Verify the Reverse Fundamental Channel is in gated mode and the Reverse Pilot
8 Channel has a transmission duty cycle of 50%.
9 k. Verify that the forward link FER on FCH is remaining in the target value.
10 l. End the call at the mobile station.
11 m. Repeat steps a through l except for the step d to set FOR_RC to 4 and REV_RC to 4.

13 The mobile station shall comply with steps j, k and m.
14 4.2.8 Forward Power Control With EIB and QIB While Transmitting Frames on the Forward
15 Fundamental Channel (FPC_MODE = ‘011’ or ‘100’)
17 This test shall be performed on the Forward Fundamental Channel with FPC_MODE equal to
18 ‘011’ and ‘100’. In this test, QIB is same as EIB. The mobile station shall set the EIB or QIB to
19 ‘0’on the Reverse Power Control Subchannel in the second transmitted frame following the
20 detection of a good 20ms frame or the detection of at least one good 5ms frame without the
21 detection of any bad 5 ms frames within 20ms (if the mobile station support 5ms frame size) on
22 the Forward Fundamental Channel. Otherwise the mobile station shall set the EIBor QIB to ‘1’ in
23 the second transmitted 20 ms frame.
24 4.2.8.2 Traceability
25 [1] 2.1.3.1.10.1 Reverse Power Control Subchannel Structure

26 [1] 2.2.2.2 Erasure Indicator Bit and Quality Indicator Bit
27 [4] 2.6.4.1.1 Forward Traffic Channel Power Control
28 [4] 3.7.2.3.2.21 Extended Channel Assignment Message

30 None

33 b. Set power ratios and levels as specified in Table 4.2.8-1.
34 Table 4.2.8-1 Test Parameters for EIB/QIB test
Parameter Unit Channel 1
4-36
C.S0044-0 v1.0
Îor/Ioc dB 0
Pilot Ec/Ior dB -7
Traffic Ec/Ior dB -7

5 e. Instruct the base station to send an Extended Channel Assignment Message with the
7
ASSIGN_MODE = ‘000’ or ‘100’ GRANTED_MODE = ‘10’
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)
CH_IND = ‘01’
8
9 f. Instruct the base station to send a Service Connect Message with the parameters set
10 as follows:
11
12
13 g. From the base station, send a sequence of at least 50 good frames and at least 50 bad
14 frames to the mobile station on the Forward Fundamental Channel.
15 h. Verify that the mobile station Reverse Power Control Subchannel bit pattern follows the
16 frame pattern sent from the base station to the mobile station (i.e. a ‘0’ for a good frame
17 and a ‘1’ for a bad frame).
18 i. End the call.
19 j. Repeat steps a through j except for the step e to set REV_RC to 3 and FOR_RC to 4.
20 k. Repeat steps a through j except for the step e to set REV_RC to 4 and FOR_RC to 5.
4-37
C.S0044-0 v1.0

2 The mobile station shall comply with steps h.
3 4.2.9 Forward Power Control With EIB While Transmitting Frames on the Forward Dedicated
4 Control Channel (FPC_MODE = ‘011’)
6 This test shall be performed on the Forward Dedicated Control Channel with FPC_MODE equal
7 to ‘011’. The mobile station shall set the EIB to ‘0’ on the Reverse Power Control Subchannel in
8 the second transmitted 20ms frame following the detection of a good 20ms frame or the detection
9 of at least one good 5ms frame without the detection of any bad 5 ms frames within 20ms on the
10 Forward Dedicated Control Channel. Otherwise, the mobile station shall set the EIB to ‘1’ in the
11 second transmitted 20 ms frame.
12 4.2.9.2 Traceability

18 None

24 d. Setup a mobile station originated data call by using SO33.
27
ASSIGN_MODE = ‘000’ or ‘100’ GRANTED_MODE = ‘10’
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)
CH_IND = ‘10’
28
30 as follows:
31
4-38
C.S0044-0 v1.0
FPC_MODE = ‘011’ DCCH_FRAME_SIZE = ‘11’
2 g. From the base station, send a sequence of at least 50 good frames and at least 50 bad
3 frames , to the mobile station on the Forward Fundamental Channel.
4 h. Verify that the mobile station Reverse Power Control Subchannel bit pattern follows the
5 frame pattern sent from the base station to the mobile station (i.e. a ‘0’ for a good frame
6 and a ‘1’ for a bad frame).
7 i. End the call.
8 j. Repeat steps d through i except for step e to set REV_RC to 3 and FOR_RC to 4.
9 k. Repeat steps d through i except for step e to set REV_RC to 4 and FOR_RC to 5.

12 4.2.10 Forward Power Control With QIB on the Forward Dedicated Control Channel
13 (FPC_MODE = ‘100’)
15 This test shall be performed on the Forward Dedicated Control Channel with FPC_MODE equal
16 to ‘100’. The mobile station shall set the QIB to ‘0’ on the Reverse Power Control Subchannel in
17 the second transmitted frame following the detection of a 20ms period with sufficient signal quality
18 on the Forward Dedicated Control Channel. The mobile station shall set the QIB to ‘1’ on the
19 Reverse Power Control Subchannel in the second transmitted frame following the detection of a
20 20ms period with insufficient signal quality on the Forward Dedicated Control Channel. When
21 transmitting active frames on the Forward Dedicated Control Channel only, the QIB will be the
22 same as the EIB When the frame is inactive (i.e. only the power control bits are transmitted in a
23 frame), the Quality Indicator Bit indicates the channel quality.



31 None
4-39
C.S0044-0 v1.0

6 d. Setup a mobile station originated data call by using Service Option 33.
9
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)
CH_IND = ‘10’
10
12 as follows:
13
FPC_MODE = ‘100’ FPC_OLPC_DCCH_INCL = ‘0’
14 g. Instruct the base station to send a sequence of at least 50 good frames and at least 50
15 bad frames to the mobile station on the Forward Dedicated Control Channel.
16 h. Verify the mobile station QIB bit pattern follows the frame pattern sent from the base
17 station to the mobile station (i.e. a ‘0’ for a good frame and a ‘1’ for a bad frame)
18 i. End the call.
19 j. Repeat steps d through j except for step e to set REV_RC to 3 and FOR_RC to 4.
20 k. Repeat steps d through j except for step e to set REV_RC to 4 and FOR_RC to 5.

22 The mobile station shall comply with steps h.
4-40
C.S0044-0 v1.0
1 4.2.11 Forward Power Control With QIB derived from the Forward Fundamental Channel or
2 Dedicated Control Channel and EIB derived from Supplemental Channel (FPC_MODE =
3 ‘101’)
5 This test shall be performed with FPC_MODE equal to ‘101’. The mobile station shall transmit
6 QIB derived from the Forward Fundamental Channel or Forward Dedicated Control Channel on
7 the Primary Reverse Power Control Subchannel and shall transmit EIB derived from Forward
8 Supplemental Channel on the Secondary Reverse Power Control Subchannel. The transmission
9 of the QIB and EIB shall start at the second 20 ms frame of the Reverse Traffic Channel following
10 the corresponding Forward Traffic Channel frame in which QIB or EIB is determined.


18 None

27
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)
CH_IND = ‘01’
28
30 as follows:
31
4-41
C.S0044-0 v1.0
FPC_MODE = ‘101’ FCH_FRAME_SIZE = ‘1’
1 g. Instruct the base station to download SCH configuration and assign a Forward
2 Supplemental Channel with an infinite duration by using the Extended Supplemental
3 Channel Assignment Message with the power control related parameters set as follows:
4
FPC_INCL = ‘1’ FPC_SEC_CHAN = ‘0’
FPC_MODE_SCH = ‘101’ NUM_SUP = ‘00’
5 h. Instruct the base station to send a sequence of at least 50 good frames at least 50 bad
6 frames to the mobile station on the Forward Fundamental Channel. Instruct the base
7 station to send a sequence of alternating at least 50 good frames and at least 50 bad
8 frames on the Forward Supplemental Channel.
9 i. Verify the mobile station QIB bit pattern on Primary Reverse Power Control Channel
10 follows the frame pattern sent from the base station to the mobile station on Forward
11 Fundamental Channel (i.e. a ‘0’ for a good frame and a ‘1’ for a bad frame) . Verify the
12 mobile station EIB bit pattern on Secondary Reverse Power Control Subchannel follows
13 the frame pattern sent from the base station to the mobile station on Forward
14 Supplemental Channel (i.e. a ‘0’ for a good frame and a ‘1’ for a bad frame).
15 j. End the call.

16 k. Repeat steps d through j except for step e to set REV_RC to 3 and FOR_RC to 4.
17 l. Repeat steps d through j except for step e to set REV_RC to 4 and FOR_RC to 5.
18 m. Repeat steps d through l except for the following steps:

19 1. Step e: Set CH_IND = ‘10’;
20 2. Step f: Set FPC_PRI_CHAN = ‘1’ and DCCH_FRAME_SIZE = ‘11’;
21 3. Step h: Instruct the base station to send a sequence of at least 50 good frames
22 and at least 50 bad frames on the Forward Dedicated Control Channel. Instruct
23 the base station to send a sequence of at least 50 good frames and at least 50
24 bad frames to the mobile station on the Forward Supplemental Channel.
25 4. Step i: Verify the mobile station QIB bit pattern on Primary Reverse Power
26 Control Channel follows the frame pattern sent from the base station to the
27 mobile station on Forward Dedicated Control Channel (i.e. a ‘0’ for a good frame
28 and a ‘1’ for a bad frame). Verify the mobile station EIB bit pattern on Secondary
29 Reverse Power Control Subchannel follows the frame pattern sent from the base
30 station to the mobile station on Forward Supplemental Channel (i.e. a ‘0’ for a
31 good frame and a ‘1’ for a bad frame).
4-42
C.S0044-0 v1.0

2 The mobile station shall comply with step i.
3 4.2.12 Forward Power Control With 400 bps data rate on the Forward Fundamental Channel or
4 Forward Dedicated Control Channel and EIB derived from Supplemental Channel
5 (FPC_MODE = ‘110’)
7 This test shall be performed with FPC_MODE equal to ‘110’. The mobile station shall transmit the
8 Primary Reverse Power Control Subchannel at a 400 bps data rate based on the Forward
9 Fundamental Channel or Forward Dedicated Control Channel, and shall transmit EIB derived
10 from Forward Supplemental Channel on the Secondary Reverse Power Control Subchannel.
11 The transmission of the power control bits on the Primary Reverse Power Control Subchannel is
12 based on inner and outer closed loop estimations. The transmission of the EIB on the Secondary
13 Reverse Power Control Subchannel shall start at the second frame (20ms frame) of the Reverse
14 Traffic Channel following the end of the corresponding Forward Supplemental Channel frame
15 from which the EIB is derived.


23 None

32
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)
CH_IND = '01' FPC_FCH_INIT_SETPT =

'01000000' (8 dB)
4-43
C.S0044-0 v1.0
'01000000' (8 dB)
FPC_FCH_FER = '00010' (1%) FPC_FCH_MIN_SETPT =

'00010000' (2 dB)
FPC_FCH_MAX_SETPT =
'10000000' (16 dB)
1
3 as follows:
4
FPC_MODE = ‘110’ GATING_RATE_INCL = ‘0’
5 g. Instruct the base station to download SCH configuration and assign a Forward
8
9 h. Monitor the forward link FER on the Forward Fundamental Channel at the mobile
10 station.
11 i. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at
14 j. Monitor traffic channel Ec/Ior and ensure the power changes corresponding to noise
17 k. Verify that the forward link FER on the FCH remains at approximately the target value .
18 l. Instruct the base station to send a sequence of at least 50 good frames and at least 50
20 m. Verify the mobile station EIB bit pattern on Secondary Reverse Power Control
21 Subchannel follows the frame pattern sent from the base station to the mobile station
22 on Forward Supplemental Channel (i.e. a ‘0’ for a good frame and a ‘1’ for a bad frame)
23 n. End the call.
24 o. Repeat steps d through n except for step e to set REV_RC to 3 and FOR_RC to 4.
25 p. Repeat steps d through n except for step e to set REV_RC to 4 and FOR_RC to 5.
4-44
C.S0044-0 v1.0
1 q. Setup a mobile station originated data call by using Service Option 33.
2 r. Instruct the base station to send an Extended Channel Assignment Message with the
4
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)

‘01000000’ (8 dB)

‘00010000’ (2 dB)
‘10000000’ (16 dB)
6 s. Instruct the base station to send a Service Connect Message with the parameters set
7 as follows:
8
FPC_MODE = ‘110’ GATING_RATE_INCL = ‘0’
9 t. Instruct the base station to download SCH configuration and assign a Forward
12
13 u. Monitor the forward link FER on the Forward Dedicated Control Channel at the mobile
14 station.
15 v. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at
18 w. Monitor traffic channel Ec/Ior and ensure the power changes corresponding to noise
21 x. Verify that the forward link FER on the DCCH remains at approximately the target value
4-45
C.S0044-0 v1.0
1 y. Instruct the base station to send a sequence of at least 50 good frames and at least 50
3 z. Verify the mobile station EIB bit pattern on Secondary Reverse Power Control
4 Subchannel follows the frame pattern sent from the base station to the mobile station
5 on Forward Supplemental Channel (i.e. a ‘0’ for a good frame and a ‘1’ for a bad frame)
6 aa. End the call.
7 bb. Repeat steps q through aa except for step r to set REV_RC to 3 and FOR_RC to 4.
8 cc. Repeat steps q through aa except for step r to set REV_RC to 4 and FOR_RC to 5.

10 The mobile station shall comply with steps k, m, x, z.
11 4.3 Lowest Rate Reverse Fundamental Channel Gating
12 4.3.1 Definition
13 This test verifies the mobile station, instructed by the base station, transmits the reverse
14 fundamental channel, with radio configurations 3 or 4, in a duty cycle of 50% when using data
15 rates of 1500 bps for RC3 and 1800 bps for RC4.
17 (See [1])
18 2.1.3.7.8 Reverse Fundamental Channel Gating

19 (See [4])
26 2.7.3 Orders
27 3.6.3.5 Response to Origination Message 1
30 3.7.3.3.2.3 Alert With Information Message
32 3.7.4 Orders 15
33 3.7.5.5 Signal 16
4-46
C.S0044-0 v1.0

2 None
4 4.3.4.1 R-FCH Gating disabled at base station

5 a. Connect the mobile station to the base station as shown in Annex A Figure A-1and set
6 forward link parameters as specified in Table 4.3.4-1.
7
8 Table 4.3.4-1 Forward Link Parameters General Setup
Parameter Units Values
Forward Link Power Ior dBm/1.23MHz -75
Pilot Ec/Ior dB -7
9
10 b. Setup a mobile station originated call.
11 c. Cause the mobile station to send Origination Message with REV_FCH_GATING_REQ

12 = 1.
13 d. Instruct the base station to send an Extended Channel Assignment Message with
14 REV_FCH_GATING_MODE = 0.
15 e. Verify audio in both directions.
16 f. Release the call.
17 g. Repeat steps c through e for all supported radio configurations.
18 4.3.4.2 R-FCH Gating enabled at base station

19 a. Connect the mobile station to the base station as shown in Annex A Figure A-1and set
20 forward link parameters as specified in Table 4.3.4-1.
22 c. Cause the the mobile station to send Origination Message with
23 REV_FCH_GATING_REQ = 1.
24 d. Instruct the base station, to send the Extended Channel Assignment Message with
25 REV_FCH_GATING_MODE = 1.
26 e. Verify audio in both directions.
27 f. Instruct the mobile station to transmit data at 1500 bps (for RC3) or 1800 bps (for RC4)
28 on reverse fundamental channel (i.e. by setting the mobile station to Mute).
29 g. Verify transmission is gated at 50% - transmission is turned on and off every 2.5ms, or
30 every 2 Power Control Groups ().
4-47
C.S0044-0 v1.0
1 h. Release the call.

2 i. Repeat steps c through e for all supported radio configurations.
3 j. Release the call.
5 4.3.5.1 R-FCH Gating disabled at base station

6 The mobile station shall comply with step e and g.
7 4.3.5.2 R-FCH Gating enabled at base station

8 The mobile station shall comply with steps g and i.
9 4.4 R-FCH Gating during Soft Handoff
10 4.4.1 Definition
11 This test verifies the functionality of R-FCH gating during soft handoffs.
13 (See [1])
14 2.1.3.7.8 Reverse Fundamental Channel Gating
15 (See [4])
22 2.7.3 Orders
23 3.6.3.5 Response to Origination Message 10
24 3.6.4 Traffic Channel Processing 11
25 3.7.2.3.2.21 Extended Channel Assignment Message 12
26 3.7.3.3.2.3 Alert With Information Message 13
27 3.7.3.3.2.20 Service Connect Message 14

28 3.7.4 Orders 15
29 3.7.5.5 Signal 16
4-48
C.S0044-0 v1.0

2 None
4 4.4.4.1 Sectors with Different Values of REV_PWR_CNTL_DELAY

5
6 a. Connect the mobile station to base stations 1 and 2 as show in Annex A Figure A-2
7 and set forward link parameters as show in Table 4.4.4-1. Configure a different Pilot PN
8 offset for each base station.
9
10 Table 4.4.4-1 Forward Link Parameters for R-FCH Test during Soft Handoff
Parameter Units Base Station 1 Base Station 2
Forward Link dBm/1.23MHz -75 -75

Power Ior
11
12 b. Configure base station 1 and base station 2 to be on different power control delay
13 regions: base station 1 = 2 PCGs and base station 2 = 3 PCGs.

15 d. Cause the mobile station to send Origination Message with REV_FCH_GATING_REQ
16 = 1.
17 e. Instruct the base station to send an Extended Channel Assignment Message with
18 REV_FCH_GATING_MODE = 1 and REV_PWR_CNTL_DELAY = 2.
19 f. Verify audio in both directions.
20 g. Instruct the mobile station to transmit data at 1500 bps (for RC3) or 1800 bps (for RC4)
21 on reverse fundamental channel (i.e. by setting the mobile station to Mute).
22 h. Verify transmission is gated at 50% - transmission is turned on and off every 2.5ms, or
24 i. Raise the level of base station 2 in steps of 1 dB with a dwell time of 1 sec until base
25 station 1 sends an Universal Handoff Direction Message or General Handoff Direction
26 Message with REV_FCH_GATING_MODE = 0.
27 j. Verify mobile station has both base stations on its active pilot set list.
28 k. Verify mobile station transmission of 1500 bps (for RC3) or 1800 bps (for RC4) frames
29 is not gated at 50% duty cycle.
30 l. Release the call.
31 m. Repeat steps b through l for all support radio configurations.
4-49
C.S0044-0 v1.0
1 4.4.4.2 Sectors with Same Value of REV_PWR_CNTL_DELAY

2 a. Connect the mobile station to base stations 1 and 2 as show in Annex A Figure A-2
3 and set forward link parameters as show in Table 4.4.4-1. Configure a different Pilot PN
4 offset for each base station but with the same frequency.
5 b. Configure base station 1 and base station 2 to be on the same power control delay
6 region = 2 PCGs.
8 d. Verify the mobile station sends Origination Message with REV_FCH_GATING_REQ =
9 1.
10 e. Instruct the base station to send an Extended Channel Assignment Message with
11 REV_FCH_GATING_MODE = 1 and REV_PWR_CNTL_DELAY = 2.
12 f. Verify audio in both directions.
13 g. Instruct the mobile station to transmit data at 1500bps on reverse fundamental channel
14 (i.e. by setting the mobile station to Mute)
15 h. Verify transmission is gated at 50% - transmission is turned on and off every 2.5ms, or
17 i. Raise the level of base station 2 in steps of 1 dB with a dwell time of 1 sec until base
19 Message, REV_FCH_GATING_MODE = 1.
20 j. Verify mobile station has both base stations on its active pilot set list.
21 k. Verify mobile station transmission of 1500 bps (for RC3) or 1800 bps (for RC4) frames
22 is gated at 50% duty cycle.
23 l. Lower the level of base station 1 in steps of 1 dB with a dwell time of 1 sec until base
25 Message, with REV_FCH_GATING_MODE = 1 and REV_PWR_CNTL_DELAY = 2.
26 m. Verify mobile station has only base station 2 on its active pilot set list.
27 n. Verify mobile station transmission of 1500 bps (for RC3) or 1800 bps (for RC4) frames
28 is gated at 50% duty cycle.
29 o. Release the call.
30 p. Repeat steps b through o for all supported radio configurations.
32 4.4.5.1 Sectors with Same Value of REV_PWR_CNTL_DELAY

33 The mobile station shall comply with steps d, h, j, k and m.
34 4.4.5.2 Sectors with Different Values of REV_PWR_CNTL_DELAY

35 The mobile station shall comply with steps d, h, j, k, m, n, and p.
4-50
C.S0044-0 v1.0
1 5 REGISTRATIONS
2 5.1 Power-Up Registration
3 5.1.1 Definition
4 These tests verify proper power-up registration functionality. The mobile station registers when it
5 powers on, switches from using a different frequency block, switches from using a different band
6 class, switches from using an alternative operating mode, or switches from using the analog
7 system. To prevent multiple registrations when power is quickly turned on and off, the mobile
8 station delays T57m seconds before registering, after entering the Mobile Station Idle State.
10 2.6.5.1.1 Power-Up Registration

11 2.6.5.5.1.3 Entering the Mobile Station Idle State
12 2.6.5.5.2.1 Idle Registration Procedures

14 3.6.5 Registration
16 3.7.2.3.2.30 ANSI-41 System Parameters Message

18 None
20 5.1.4.1 Power-up Registration Disabled
22 b. Instruct the base station to set POWER_UP_REG = 0 in the System Parameters
23 Message or ANSI-41 System Parameters Message.
24 c. Power on the mobile station.

25 d. Verify the mobile station does not attempt power-up registration for at least 1 minute
26 after the mobile station enters the Mobile Station Idle State.
27 5.1.4.2 Power-up Registration Enabled

29 b. Instruct the base station to set POWER_UP_REG = 1 in the System Parameters
30 Message or ANSI-41 System Parameters Message
5-1
C.S0044-0 v1.0
1 d. Verify the mobile station sends a Registration Message with REG_TYPE = ‘0001’ no
2 sooner than 20 seconds (T57M) after entering Mobile Station Idle State.
3 5.1.4.3 Power-up Registration due to change in Operating Mode

4 a. Connect the base station and mobile station as shown in Figure A-5. (Base station 1 is
5 a CDMA base station and base station 2 is a non-CDMA base station.
6 b. Allow the mobile station to operate in the idle state on base station 2.
7 c. Configure base station 1 to set POWER_UP_REG = 1 in the System Parameters
8 Message or the ANSI-41 System Parameters Message.
9 d. Force the mobile station to acquire base station 1.
10 e. Verify the mobile station sends a Registration Message with REG_TYPE = ‘0001’ on
11 base station 1.
12 5.1.4.4 Power-up Registration entering into different Band Class

13 a. Connect the base station and mobile station as shown in Figure A-5. (Base station 1
14 and base station 2 are CDMA base stations using different band classes)
15 b. Instruct both base station 1 and base station 2 to set POWER_UP_REG = 1 in the
16 System Parameters Message or the ANSI-41 System Parameters Message.
18 d. Verify the mobile station sends a Registration Message with REG_TYPE = ‘0001’ on
19 base station 1.
20 e. Force the mobile station to acquire base station 2.
21 f. Verify the mobile station a Registration Message with REG_TYPE = ‘0001’ on base
22 station 2.
23 g. Force the mobile station to acquire base station 1.
24 h. Verify the mobile station performs power-up registration on base station 1.
25 5.1.4.5 Power-up Registration entering into Different Frequency Blocks

27 and base station 2 are CDMA base stations using the same band class with
28 frequencies assignments in a different serving system.)
29 b. Instruct both base station 1 and base station 2 to set POWER_UP_REG = 1 in the
30 System Parameters Message or the ANSI-41 System Parameters Message while
31 ensuring all other forms of registration are disabled.
33 d. Verify the mobile station sends a Registration Message with REG_TYPE = ‘0001’ on
34 base station 1.
5-2
C.S0044-0 v1.0
1 f. Verify the mobile station sends a Registration Message with REG_TYPE = ‘0001’ on
2 base station 2.
4 5.1.5.1 Power-up Registration Disabled

5 The mobile station shall comply with step d. Power-up registration shall not occur.
6 5.1.5.2 Power-up Registration Enabled

7 The mobile station shall comply with step d. The mobile station shall perform the registration
8 process when it is powered on and after the power/initialization timer has expired.
9 5.1.5.3 Power-up Registration entering into different operating mode

11 5.1.5.4 Power-up Registration entering into different Band Class

12 The mobile station shall comply with steps d, f and h.
13 5.1.5.5 Power-up Registration entering into Different Frequency Blocks

14 The mobile station shall comply with steps d and f.
15 5.2 Power - Down Registration
16 5.2.1 Definition
17 These tests verify power-down registration functionality. The mobile station should be able to
18 recognize all base station registration settings.
19 The mobile station registers when it powers off if previously registered in the current serving
20 system. The mobile station should not perform power-down registration if it has not previously
21 registered in the system corresponding to its current SID and NID.

24 2.6.5.1.2 Power-Down Registration
25 2.6.5.5.2.1 Idle Registration Procedures

29 3.7.2.3.2.30 ANSI - 41 System Parameters Message

31 None
5-3
C.S0044-0 v1.0
2 5.2.4.1 Power-down Registration Disabled

4 b. Enable power-up registration (set POWER_UP_REG = 1 in the System Parameters
5 Message or ANSI - 41 System Parameter Message) while ensuring all other forms of
6 registration are disabled.
8 d. Verify the mobile station performs a power-up registration.
9 e. Power down the mobile station.
10 f. Verify power-down registration does not occur.
11 5.2.4.2 Power-down Registration of a Currently Registered Mobile Station
13 b. Enable power-up registration (set POWER_UP_REG = 1) and power-down registration
14 (set POWER_DOWN_REG = 1) in the System Parameters Message or ANSI - 41
15 System Parameter Message) while ensuring all other forms of registration are disabled.
17 d. Verify power-up registration occurs.
18 e. Power down the mobile station.

19 f. Verify the mobile station sends a Registration Message with REG_TYPE = ’0011’.
20 5.2.4.3 Power-down Registration of an Unregistered Mobile Station in New System/Network
22 and base station 2 are CDMA base stations using a different SID/NID).
23 b. Instruct base station 1 to set POWER_ UP = 1 and both base station 1 and base station
24 2 to set POWER_DOWN = 1 in the System Parameters Message or ANSI - 41 System
25 Parameter Message, and turn off all other types of registration.
27 d. Verify power-up registration on base station 1.
29 f. Verify power-down registration does not occur on base station 2.
31 5.2.5.1 Power-down Registration Disabled

32 The mobile station shall comply with steps d and f. Power-down registration shall not occur.
5-4
C.S0044-0 v1.0
1 5.2.5.2 Power-down Registration of a Currently Registered Mobile Station

2 The mobile station shall comply with steps d and f. The mobile station shall perform power-down
3 registration in a system/network where it is currently registered.
4 5.2.5.3 Power-down Registration of an Unregistered Mobile Station in a New System/Network

5 The mobile station shall comply with steps d and g. Power-down registration shall not occur in a
6 system/network where the mobile station is not currently registered.
7 5.3 Distance-Based Registration
8 5.3.1 Definition
9 These tests verify proper distance-based registration functionality.
10 The mobile station should be able to recognize all base station registration settings.
11 The mobile station registers when the distance between the current base station and the base
12 station in which it last registered exceeds a threshold.
13 5.3.2 Traceability (See [4]);

15 2.6.5.1.4 Distance-Based Registration

21 None
22 5.3.4 Method of measurement
23 5.3.4.1 Distance-Based Registration Disabled

24 a. Connect the base station and mobile station as shown in Figure A-5. Use the
25 parameters in Table 5.3.4-1.
26 b. Configure base station 1 and base station 2 to send the System Parameters Message
27 or the ANSI - 41 System Parameters Message with REG_DIST, BASE_LAT and
28 BASE_LONG parameters as indicated in Table 5.3.4-2 (Test Case 1).
29 c. Instruct both base station 1 and base station 2 to set power-up registration (set
30 POWER_UP_REG = 1) in the System Parameters Message or the ANSI - 41 System
32 d. Power on the mobile station on base station 1.
33 e. Verify power-up registration occurs.
5-5
C.S0044-0 v1.0
1 f. Force the mobile station to perform an idle handoff to base station 2 by reducing base
2 station 2 forward link attenuation, then increasing base station 1 forward link
3 attenuation.
4 g. Verify the mobile station does not perform distance-based registration.
5
6 Table 5.3.4-1 Forward Link Parameters for Distance-based Registration
Ior/Ioc dB 0 -10
Ioc dB/1.23 MHz -75 -75
8
9 Table 5.3.4-2 BTS Distance based LAT/LONG System Parameters Message or the ANSI - 41
10 System Parameters Message Configuration
11
Parameters Test Case 1 Test Case 2 Test Case 3
BTS 1 BASE_LAT (sec/4) 0X4 0X4 0X4
BTS 1 BASE_LONG (sec/4) 0X4 0X4 0X4
BTS 2 BASE_LAT (sec/4) 0X400 0X400 0X400
BTS 2 BASE_LONG (sec/4) 0X400 0X400 0X400
REG_DIST 0X0 0X50 0X10
12
13 5.3.4.2 Distance Threshold Not Exceeded
18 BASE_LONG parameters as indicated in Table 5.3.4 -2 (Test Case 2).
5-6
C.S0044-0 v1.0
4 d. Power on the mobile station.
6 f. Force the mobile station to perform an idle handoff to base station 2 by reducing base
7 station 2 forward link attenuation, then increasing base station 1 forward link
8 attenuation.
9 g. Verify the mobile station does not perform distance-based registration.
10 5.3.4.3 Distance Threshold Exceeded

15 BASE_LONG parameters as indicated in Table 5.3.4-2 (Test Case 3).
21 f. Force mobile station to perform idle handoff to base station 2 by reducing base station 2
22 forward link attenuation, then increasing base station 1 forward link attenuation.
23 g. Verify the mobile station sends a Registration Message with REG_TYPE = ’0110’.
25 5.3.5.1 Distance-based Registration Disabled

26 The mobile station shall comply with step g. Distance-based registration shall not occur.
27 5.3.5.2 Distance Threshold Not Exceeded

28 The mobile station shall comply with step g. The mobile station shall not perform distance-based
29 registration when distance-based registration enabled and calculated value of DISTANCE is less
30 than REG_DIST.
31 5.3.5.3 Distance Threshold Exceeded

32 The mobile station shall comply with step g. The mobile station shall perform distance-based
33 registration when distance based registration is enabled and the calculated value of DISTANCE is
34 greater than REG_DIST.
5-7
C.S0044-0 v1.0
1 5.4 Timer-Based Registration
2 5.4.1 Definition
3 These tests verify proper timer - based registration functionality.
4 The mobile station registers when a timer expires.
5 Timer-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
7 Parameters Message or ANSI-41 System Parameters Message.
8 The counter is reset when the mobile station powers on. The counter is reset after each
9 successful registration.

11 2.6.5.1.2 Power-Down Registration
12 2.6.5.1.3 Timer-Based Registration

16 3.7.2.3.2.30 ANSI- 41 System Parameters Message

18 None
20 5.4.4.1 Timer-based Registration Disabled

22 b. Instruct the base station to set POWER_UP_REG =1 and set REG_PRD = 0 in the
23 System Parameters Message or ANSI – 41 System Parameter Message.
25 d. Verify power-up registration occurs.
26 e. Verify the mobile station does not perform timer-based registration.
27 5.4.4.2 Mid-range Timer Value

29 b. Instruct the base station to set POWER_UP_REG =0 and set REG_PRD = 38 (57.93
30 seconds) in the System Parameters Message or ANSI –41 System Parameter
31 Message.
33 d. Verify timer-based registration occurs approximately every 58 seconds.
5-8
C.S0044-0 v1.0
2 5.4.5.1 Timer-based Registration Disabled

3 The mobile station shall comply with steps d and e. Timer-based registration shall not occur.
4 5.4.5.2 Mid-Range Timer Value

5 The mobile station shall comply with step d. The mobile station shall perform time-based
6 registration at the interval specified by the REG_PRD value.
7 5.5 Parameter-Change Registration
8 5.5.1 Definition
9 These tests verify proper parameter-change registration functionality.
10 Parameter-change registration is performed when a mobile station modifies any of the following
11 stored parameters:
12 a. The mobile station’s SID_NID_LIST does not match the base station’s SID and NID.
14 2.6.5.1.6 Parameter-Change Registration


19 None
21 5.5.4.1 Parameter-Change Registration Disabled

22 a. Connect the base station and mobile station as shown in Figure A-5. Base station 1 and
23 base station 2 are CDMA base station operating in the same band class and
24 frequencies with different SID values.
25 b. Instruct the base station to set PARAMETER_REG = ‘0’ and disable all other forms of
26 registration (set equal to 0) in the System Parameters Message or ANSI - 41 System
28 c. Power on the mobile station and allow time for the mobile station to acquire base
29 station 1.
30 d. Force the mobile station to acquire base station 2.
31 e. Verify the mobile station does not send a Registration Message.
5-9
C.S0044-0 v1.0
1 5.5.4.2 Parameter-Based Registration per SID-NID List change

3 and base station 2 are CDMA base stations using different SID configurations).
4 b. Instruct both base station to set PARAMETER_REG = 1 while ensuring all other forms
5 of registration are disabled (set equal to 0) in the System Parameters Message or ANSI
6 - 41 System Parameters Message.
7 c. Power on the mobile station and allow time for the mobile station to acquire Base
8 Station 1.
9 d. Force the mobile station to acquire Base Station 2.
10 e. Verify the mobile station sends a Registration Message with REG_TYPE = ’0100’.
11 f. Repeat steps a through e with base station 1 and base station 2 using different NID
12 configurations.
14 5.5.5.1 Parameter-Change Registration Disabled
15 5.5.5.2 The mobile station shall comply with step e. Parameter-Based Registration per SID-NID
16 List change
18 5.6 Zone-Based Registration
19 5.6.1 Definition
20 These tests verify proper Zone-based registration functionality.
21 The mobile station registers when it enters a new zone that is not on its internally stored list of
22 visited registration zones.
23 The mobile station does not register when it performs an idle handoff into a zone that is on its
24 internally stored list of visited zones.
25 The mobile station should properly delete entries from its internally stored list of visited
26 registration zones.

29 2.6.5.1.5 Zone-Based Registration

32 3.7.2.3.2.30 ANSI –41 System Parameters Message
5-10
C.S0044-0 v1.0
1 5.6.3 Call Flow Diagram

2 None
4 5.6.4.1 Zone-Based Registration Disabled

5
6 Table 5.6.4-1 Parameters for Zone-base Reistration Tests
Parameters Test Case 1 Test Case 2 Test Case 3 Test Case 4
BTS 1 REG_ ZONE 0x1 0x1 0x1 0x1
BTS 2 REG_ZONE 0x2 0x2 0x2 0x2
ZONE_TIMER 0x0 0x0 0x0 0x1
TOTAL_ZONES 0x0 0x2 0x2 0x1
8 b. Configure the System Parameters Message or ANSI - 41 System Parameters Message
9 on base stations 1 and 2 with the REG_ZONE settings from Table 5.6.4-1, test case
10 1.
11 c. Enable power-up registration (set POWER_UP_REG = 1 in the System Parameters
12 Message or ANSI – 41 System Parameters Message).
13 d. Allow for the mobile station to perform a power up registration on base station 1.
14 e. Force the mobile station to perform an idle handoff to base station 2 by reducing the
15 base station 2 forward link attenuation, while at the same time increasing the base
16 station 1 forward link attenuation.
17 f. Verify zone-based registration does not occur.
18 5.6.4.2 Zone-Based Registration Enabled

21 on base stations 1 and 2 with the settings from Table 5.6.4-1, test case 2.
24 d. Power on the mobile station and allow it to perform a power up registration on base
25 station 1. (The mobile station should now be registered in zone 1 and the only entry in
26 the mobile station’s ZONE_LIST).
5-11
C.S0044-0 v1.0
1 f. Verify the mobile station sends a Registration Message with REG_TYPE = ’0010’. (The
2 mobile station should now be registered in zone 2. Zone 1 and Zone 2 should be in the
3 mobile station’s ZONE_LIST).
4 g. Before the period of time specified by ZONE_TIMER has elapsed (one minute) and the
5 mobile station deletes zone 1 from it’s ZONE_LIST, force the mobile station to perform
6 an idle handoff back to base station 1.
7 h. Verify zone-based registration does not occur. (Zone 1 is still in the mobile station’s
8 ZONE_LIST).
9 5.6.4.3 Zone-Based Registration Timer

21 f. Verify zone-based registration occurs. (The mobile station should now be registered in
22 zone 2. Zone 1 and Zone 2 should be in the mobile station’s ZONE_LIST).
23 g. Wait for the period of time specified by ZONE_TIMER to elapse (one minute, after
24 which the mobile station should delete zone 1 from ZONE_LISTs).
25 h. Force the mobile station to perform an idle handoff to base station 1.
26 i. Verify the mobile station sends a Registration Message with REG_TYPE = ’0010’.
27 5.6.4.4 Mobile Station ZONE_LIST Deletion

5-12
C.S0044-0 v1.0
4 f. Verify the mobile station sends a Registration Message with REG_TYPE = ‘0010’. (The
5 mobile station is now registered in zone 2, and only zone 2 should be in mobile station’s
6 ZONE_LIST because the mobile station was forced to delete zone 1 from ZONE_LISTs
7 to make room for zone 2).
8 g. Force the mobile station to perform an idle handoff back to base station 1.
9 h. Verify the mobile station sends a Registration Message with REG_TYPE = ’0010’.
10 (Zone 1 is not in ZONE_LISTs).
12 5.6.5.1 Zone-Based Registration Disabled

13 The mobile station shall comply with step f. The mobile station shall not perform a zone-based
14 registration.
15 5.6.5.2 Zone-Based Registration Enabled

16 The mobile station shall comply with steps f, h. The mobile station performs a zone-based
17 registration.
18 5.6.5.3 Zone-Based Registration Timer

19 The mobile station shall comply with steps f, and i. The mobile station performs a zone-based
20 registration.
21 5.6.5.4 Mobile Station ZONE_LIST Deletion

22 The mobile station shall comply with steps f, h. The mobile station performs a zone-based
23 registration.
5-13
C.S0044-0 v1.0
1 6 AUTHENTICATION
2 6.1 Shared Secret Data (SSD) Initialized when A-Key is Changed
3 6.1.1 Definition
4 This test verifies that when the A-Key is changed at both the base station and mobile station,
5 authentication of mobile station registrations, originations, and terminations and the Unique
6 Challenge-Response Procedure are successful.

8 2.3.12.1 (MS) Authentication

10 3.3.1 (Base Station) Authentication

12 None
14 a. Connect the base station and mobile station as shown in Annex A Figure A-1.
15 b. Power on the mobile station.
16 c. Initialize the A-Key to the same value in the mobile station and base station.
17 d. Ensure timer-based registration is enabled with the registration period (REG_PRD) set
18 to 29.
19 e. Verify the mobile station sends a Registration Message with REG_TYPE set to ‘0000’
20 (i.e. timer-based registration) and which includes AUTHR, RANDC and COUNT.
21 f. Verify registration authentication is successful at the base station.

24 i. End the call.
25 j. Setup a mobile station terminated call.
26 k. Verify user data in both directions.
27 l. Instruct the base station to initiate a Unique Challenge-Response Procedure while on
28 the f/r-dsch.

30 1. The base station sends an Authentication Challenge Message,
31 2. Upon receiving this message, the mobile station sends an Authentication
32 Challenge Response Message, and
6-1
C.S0044-0 v1.0
1 3. The Unique Challenge-Response Procedure is successful.

2 n. End the call.
3 o. Instruct the base station to initiate a Unique Challenge-Response Procedure while on
4 the f/r-csch.
5 p. Verify the following:
7 2. Upon receiving this message, the mobile station sends an Authentication
9 3. The Unique Challenge-Response Procedure is successful.

11 The mobile station shall comply with the requirements in the following steps: Step e, h, k, m, p.
12 The base station shall comply with the requirements in the following steps: Step f, h, k, m, p.
13 6.2 Shared Secret Data Update
14 6.2.1 Definition
15 This test verifies the mobile station and base station can perform a Shared Secret Data update on
16 the f/r-csch and f/r-dsch.

18 2.3.12.1.4 Unique Challenge-Response Procedure
19 2.3.12.1.5 Updating the Shared Secret Data (SSD)
21 2.7.1.3.2.6 Authentication Challenge Response Message
22 3.7.2.3.2.1 System Parameters Message (f-csch)
23 3.7.2.3.2.10 Authentication Challenge Message (f-csch)

25 None


29 c. Initialize the A-Key to the same value in both the mobile station and base station.
30 d. Instruct the base station to initiate a Shared Secret Data update on the f/r-csch.
6-2
C.S0044-0 v1.0
1 1. The base station sends a SSD Update Message,

2 2. The mobile station sends a Base Station Challenge Order,
3 3. The base station sends a Base Station Challenge Confirmation Order,
4 4. The mobile station sends a SSD Update Confirmation Order, and
5 5. That the SSD Update Procedure is successful.
6 f. Ensure timer-based registration is enabled with the registration period (REG_PRD) set
7 to 29.
8 g. Wait for the mobile station to send the Registration Message with REG_TYPE set to
9 ‘0000’ (i.e. timer-based registration).
10 h. Verify the Registration Message includes AUTHR, COUNT and RANDC.
11 i. Verify registration authentication is successful at the base station.
12 j. Setup a mobile station originated call.
13 k. Verify user data in both directions.
14 l. Instruct the base station to initiate a Unique Challenge-Response Procedure on the f/r-
15 dsch.
18 2. Upon receiving this message, the mobile station sends a Authentication

20 3. That the Unique Challenge-Response Procedure is successful.
21 n. End the call.

22 o. Instruct the base station to initiate a Unique Challenge-Response Procedure on the f/r-
23 csch.
24 p. Verify the following:
26 2. Upon receiving this message, the mobile station sends a Authentication
28 3. That the Unique Challenge-Response Procedure is successful.
29 q. Repeat steps c through p but with the following exception:
30 1. In step d, setup a call and initiate a Shared Secret Data update on the f/r-dsch,
31 and then end the call.

33 The mobile station shall comply with the requirements in the following steps: Step e, h, k, m, p, q.
34 The base station shall comply with the requirements in the following steps: Step e, i, k, m, p, q.
6-3
C.S0044-0 v1.0
1 6.3 Mismatched A-Keys
2 6.3.1 Definition
3 This test verifies that when there is an A_KEY mismatch, authentication of registrations,
4 originations, terminations, and Unique Challenge-Response procedures will fail.

6 2.3.12.1.4 Unique Challenge-Response Procedure

9 2.7.2.3.2.2 Authentication Challenge Response Message (r-dsch)
11 3.7.2.3.2.1 SSD Update Message (f-csch)

12 3.7.3.3.2.2 Authentication Challenge Message (f-dsch)
13 3.7.3.3.2.13 SSD Update Message (f-dsch)

15 None

19 c. Initialize the A-Key to the same value in the mobile station and base station.

23 g. End the call.
24 h. Change the A-Key in the mobile station.
25 i. Ensure timer-based registration is enabled with the registration period (REG_PRD) set
26 to 29.
27 j. Wait for the mobile station to send a Registration Message with REG_TYPE set to
28 ‘0000’ (i.e. timer-based registration).
29 k. Verify the Registration Message includes AUTHR, COUNT and RANDC.
30 l. Verify registration authentication fails at the base station due to an AUTHR mismatch.
31 m. Setup a mobile station originated call.

32 n. Verify that the call request was denied.
6-4
C.S0044-0 v1.0

2 p. Verify the call fails due to an AUTHR mismatch.
3 q. Initiate at the base station a Shared Secret Data update on the f-csch.
4 r. Verify the SSD Update fails with an AUTHBS mismatch.
5 s. Initiate at the base station a Unique Challenge-Response Procedure on the f-csch.
6 t. Verify the Unique Challenge-Response Procedure fails with an AUTHU mismatch.

8 The mobile station shall comply with the requirements in the following steps: Step f, k, n, p, r, t.
9 The base station shall comply with the requirements in the following steps: Step f, l, p, r, t.
10 6.4 Activating Voice Privacy on Call Setup
11 6.4.1 Definition
12 This test verifies that Voice Privacy can be activated at call setup by the mobile station
13 subscriber.

15 2.3.12.3 (MS) Voice Privacy
16 2.6.4.1.6 (MS) Long Code Transition Request Processing
19 2.7.3 (Mobile Station) Orders
20 3.3.3 (Base Station) Voice Privacy
21 3.6.4.1.5 (Base Station) Long Code Transition Request Processing
24 3.7.4 (Base Station) Orders

26 None

29 b. Ensure authentication is enabled. Verify the AUTH field of the Access Parameters
30 Message is set to ‘01’ or the ANSI-41 RAND Message is being transmitted.
6-5
C.S0044-0 v1.0
1 d. Enable Voice Privacy in the mobile station and configure the base station to use voice
2 privacy.
3 e. Setup a mobile station originated call, and verify in the Origination Message the Voice
4 Privacy Mode Indicator (PM) is set to '1'.
5 f. Instruct the base station to send a Long Code Transition Request Order
6 (ORDQ='00000001') on the f-dsch.
7 g. Verify the mobile station responds with a Long Code Transition Response Order
8 (ORDQ='00000011')
9 h. If supported on the user interface, verify the mobile station indicates to the user that
10 Voice Privacy is active.
11 i. Verify that correct user data is received in both directions.
12 j. End the call.
13 k. Setup a mobile station terminated call, and verify in the Page Response Message the
14 voice privacy indicator (PM) is set to ‘1’ then repeat steps f through j.

16 The mobile station shall comply with the requirements in the following steps: Step e, g, h, i, k.
17 The base station shall comply with the requirements in the following steps: Step b, i.
18 6.5 Activating Voice Privacy at the Mobile Station When a Call Is Active
19 6.5.1 Definition
20 This test verifies that Voice Privacy can be activated at the mobile station when a call is active.

22 2.3.12.3 (Mobile Station) Voice Privacy
23 2.6.4.1.6 Long Code Transition Request Processing

26 2.7.3 (Mobile Station) Orders
27 3.3.3 (Base Station) Voice Privacy

28 3.6.4.1.5 (Base Station) Long Code Transition Request Processing
29 3.6.4.3.1 Traffic Channel Substate
31 3.7.4 (Base Station) Orders

33 None
6-6
C.S0044-0 v1.0

3 b. Configure the base station to use Voice Privacy.
4 c. Ensure authentication is enabled. Verify the AUTH field of the Access Parameters
8 f. Enable voice privacy at the mobile station. Verify the mobile station sends a Long Code
9 Transition Request Order with ORDQ set to ‘00000001’.
10 g. Verify the base station responds by sending a Long Code Transition Request Order
11 with ORDQ set to ‘00000001’.
12 h. Verify the mobile station responds with a Long Code Transition Response Order
13 (ORDQ='00000011').
14 i. If supported on the user interface, verify the mobile station indicates Voice Privacy is
15 active.
16 j. Verify that correct user data is received in both directions.
17 k. End the call.

19 The mobile station shall comply with the requirements in the following steps: Step f, h, i, j.
20 The base station shall comply with the requirements in the following steps: Step c, g, j.
21 6.6 Signaling Message Encryption on Forward Traffic Channel
22 6.6.1 Definition
23 This test verifies that Signaling Message Encryption on f-dsch is performed correctly.
25 2.3.12.2 (Mobile Station) Signaling Message Encryption

26 2.7.4.4 (Mobile Station) Calling Party Number
27 3.3.2 (Base Station) Encryption

28 3.7.2.3.2.8 Channel Assignment Message (f-csch)
29 3.7.3.3.2.3 Alert With Information Message (f-dsch)
30 3.7.5.3 (Base Station) Calling Party Number

32 None
6-7
C.S0044-0 v1.0

3 b. Activate the Calling Party Number (CPN) feature for the mobile station subscriber.
7 e. Enable Signaling Message Encryption on the base station.
8 f. Setup a mobile station terminated call.
9 g. Verify the ENCRYPT_MODE field is set to '01' or ‘10’ in the transmitted Channel
10 Assignment Message or Extended Channel Assignment Message.
11 h. Verify the following:
12 1. Required fields in the appropriate messages are encrypted and can be correctly
13 decrypted. For example, certain fields of the Alert With Information Message will
14 be encrypted; but verification can be done on other messages as well.
15 2. The ENCRYPTION field in these messages is set to the same value as the
16 ENCRYPT_MODE field received in the Channel Assignment Message or
18 i. Verify the CPN is displayed on the mobile station during the alerting state.
19 j. Verify that correct user data is received in both directions.
20 k. End the call.

22 The mobile station shall comply with the requirements in the following steps: Step h, i, j.
23 The base station shall comply with the requirements in the following steps: Step c, g, h, j.
24 6.7 Signaling Message Encryption on Reverse Traffic Channel
25 6.7.1 Definition
26 This test verifies that Signaling Message Encryption on the r-dsch is performed correctly.


33 None
6-8
C.S0044-0 v1.0

3 b. Ensure authentication is enabled. Verify the AUTH field of the Access Parameters
6 d. Instruct the mobile station to send a Send Burst DTMF Message.
7 e. Enable Signaling Message Encryption on the base station.
8 f. Setup a mobile station call to a voice mail system or a paging system.
9 g. Verify the ENCRYPT_MODE field is set to '01' or ‘10’ in the transmitted Channel
13 decrypted. For example, certain fields of the Burst DTMF Message will be
14 encrypted; but verification can be done on other messages as well.
18 i. Enter the appropriate pin code as burst DTMF tones.

19 j. Verify that either the voice mail system recognizes the DTMF tones and plays the
20 message back, or that the paging system accepts the pin and sends out the page.
21 Alternative procedures may be used to verify correct behavior.
22 k. End the call.

24 The mobile station shall comply with the requirements in the following steps: Step h.
25 The base station shall comply with the requirements in the following steps: Step b, g, h, j.
26 6.8 Hard Handoffs between Base Stations with Signaling Message Encryption Active
27 6.8.1 Definition
28 This test verifies that when Signaling Message Encryption is used, the new base station activates
29 correct encryption upon handoff.

33 2.7.4.4 (Mobile Station) Calling Party Number.
6-9
C.S0044-0 v1.0
1 3.6.6.2.2.2 Extended Handoff Direction Message (call processing)

2 3.6.6.2.2.10 General Handoff Direction Message (call processing)
3 3.6.6.2.2.11 Universal Handoff Direction Message (call processing)

5 3.7.3.3.2.14 Flash With Information Message (f-dsch)
6 3.7.3.3.2.17 Extended Handoff Direction Message (f-dsch)

7 3.7.3.3.2.31 General Handoff Direction Message (f-dsch)
8 3.7.3.3.2.36 Universal Handoff Direction Message (f-dsch)
9 3.7.5.3 (Base Station) Calling Party Number

11 None

14 b. Activate Call Waiting and Caller ID on base station 2.


18 e. Enable Signaling Message Encryption on both base stations.
20 g. Verify ENCRYPT_MODE field is set to '01' or ‘10’ in the transmitted Channel

23 i. Cause a hard handoff from base station 1 to base station 2.

24 j. Verify ENCRYPT_MODE field is set to '01’ or ‘10’ in the transmitted Extended Handoff
25 Direction Message, General Handoff Direction Message, or Universal Handoff Direction
26 Message.
27 k. Setup another call to the mobile station and listen for the Call Waiting tone.
30 decrypted. For example, certain fields of the Flash With Information Message will
31 be encrypted; but verification can be done on other messages as well.
6-10
C.S0044-0 v1.0
1 m. Verify that Calling Party Number (CPN) information is displayed on the mobile station
2 during alerting state.
3 n. Verify user data in both directions.
4 o. End the call.

6 The mobile station shall comply with the requirements in the following steps: Step h, l, m, n.
7 The base station shall comply with the requirements in the following steps: Step c, g, h, j, l, n.
8 6.9 Authentication upon Originations
9 6.9.1 Definition
10 This test verifies the mobile station can successfully Authenticate upon an origination.

14 2.7.2.3.2.2 Authentication Challenge Response Message (r-dsch)
16 3.7.2.3.2.11 SSD Update Message (f-csch)
17 3.7.3.3.2.2 Authentication Challenge Message (f-dsch)
18 3.7.3.3.2.13 SSD Update Message (f-dsch)

20 None

24 c. Initialize the A-Key to the same value in both the mobile station and base station.
26 e. Verify the SSD Update was successful.

27 f. Setup a mobile station originated call (seven digits).
28 g. Verify user data in both directions and that authentication is successful.
29 h. End the call.
30 i. Setup a mobile station originated call (three digits such as *73).
31 j. Verify user data in both directions and that authentication is successful.
6-11
C.S0044-0 v1.0
1 k. End the call.

2 l. Setup a mobile station originated call (four digits such as *123).
3 m. Verify user data in both directions and that authentication is successful.
4 n. End the call.

6 The mobile station shall comply with the requirements in the following steps: Step e, g, j, and m.
7 The base station shall comply with the requirements in the following steps: Step e, g, j, and m.
8 6.10 Hard Handoff from CDMA to Analog with Signaling Message Encryption Active
9 6.10.1 Definition
10 This test verifies that when Signaling Message Encryption is used, the new base station activates
11 Analog Signaling Message Encryption upon handoff.

14 2.6.6.2.9 CDMA-Analog HO
15 2.7.4.4 (Mobile Station) Calling Party Number
19 3.7.3.3.2.3 Alert with Information Message (f-dsch)
21 3.7.5.3 (Base Station) Calling Party Number.

23 None
26 b. Activate Call Waiting and Caller ID on Base station 2.
30 e. Enable Signaling Message Encryption on both base stations.
6-12
C.S0044-0 v1.0
1 g. Verify ENCRYPT_MODE field is set to '01' or ‘10’ in the Channel Assignment Message
2 or Extended Channel Assignment Message transmitted.
3 h. Verify that correct user data is received in both directions.
4 i. Cause a CDMA to analog hard handoff from base station 1 to base station 2.
5 j. Verify ENCRYPT_MODE='01' and MEM=’1’ in the Analog Handoff Direction Message.
6 k. Setup another call to the mobile station, and listen for the Call Waiting tone.
7 l. Verify base station 2 sends an encrypted Alert with Information Message (analog).
8 m. Verify that the Calling Party Number (CPN) information is displayed on the mobile
9 station during the alerting state.
10 n. Verify that correct user data is received in both directions.
11 o. End the call.

13 The mobile station shall comply with the requirements in the following steps: Step h, m, n.
14 The base station shall comply with the requirements in the following steps: Step c, g, h, j, l, n.
15
16
6-13
C.S0044-0 v1.0
1 7 SERVICE REDIRECTION TEST CASES
2 7.1 Global Service Redirection between Band Classes
3 7.1.1 Definition
4 This test verifies that when a mobile station receives a Global Service Redirection Message
5 directing it to another band class, the mobile station acquires the appropriate system.

9 2.6.2.2.6 Global Service Redirection Message

11 3.7.2.3.2.18 Global Service Redirection Message

13 None

15 a. Connect the mobile station to the base station as shown in Figure A-5. For this test
16 case, base station 1 and base station 2 are in different band classes.
17 b. Verify the mobile station is operating in the Mobile Station Idle State on base station 1.
18 c. Ensure that the base station sends a Global Service Redirection Message with:
19
Field Value
REDIRECT_ACCOLC ACCOLCp
EXCL_P_REV_MS ‘0’
RECORD_TYPE ‘00000010’
BAND_CLASS Target Band Class
EXPECTED_SID Target SID
EXPECTED_NID Target NID
NUM_CHAN Number of Channels
CDMA_CHAN Target Channel(s)
20 d. Verify the mobile station enters the System Determination Substate of the Mobile
21 Station Initialization State and acquires the system to which it was redirected.
22 e. Setup a mobile station originated call. Verify user traffic in both directions.
7-1
C.S0044-0 v1.0
1 f. End the call.

2 g. Repeat steps c through f with the mobile station operating in the Mobile Station Idle
3 State on base station 2.
4 h. Repeat steps b and c with the mobile station operating in the Mobile Station Idle State
5 on base station 1 setting EXCL_P_REV_MS = ‘1’ in the Global Service Redirection
6 Message.
8 1. If MOB_P_REV is less than six, verify the mobile station enters the System
9 Determination Substate of the Mobile Station Initialization State and acquires the
10 system to which it was redirected.
11 2. If MOB_P_REV is greater than or equal to six, verify the mobile station remains
12 in the Mobile Station Idle State on the current system.

14 The mobile station shall comply with steps d, e, and i.
15 7.2 Global Service Redirection between CDMA and a Non-CDMA System
16 7.2.1 Definition
18 directing it from CDMA to a Non-CDMA system, the mobile station acquires that system. The
19 mobile station should only be redirected to Non-CDMA systems it supports. An example would be
20 an analog system defined in [21].


28 None

31 case, base station 1 is a CDMA base station and base station 2 is a Non-CDMA base
32 station.
33 b. Ensure the mobile station is operating in the Mobile Station Idle State on base station 1.
7-2
C.S0044-0 v1.0
1 c. Send a Global Service Redirection Message from the current base station directing the
2 mobile station to the non-CDMA base station with the following parameters:
Field Value
RECORD_TYPE '00000001' [North

American Amps]
'00000011' [TACS]
'00000100' [JTACS]
‘00000101’ (DS-41)
If RECORD_TYPE=’00000001’,
the base station shall include the
following fields
IGNORE_CDMA ‘0’
SYS_ORDERING ‘000’
MAX_REDIRECT_DELAY ‘00000’
7 f. End the call.

8 g. Repeat steps b and c with the mobile station operating in the Mobile Station Idle State
10 Message.

18 The mobile station shall comply with steps d, eand h.
7-3
C.S0044-0 v1.0
1 7.3 Global Service Redirection between Channels in the Same Band Class
2 7.3.1 Definition
4 directing it to a different channel in the same band class, the mobile station acquires the
5 appropriate system.



13 None
16 case, base station 1 and base station 2 are in the same band class with different CDMA
17 channels.
19 c. Send a Global Service Redirection Message from the current base station with:
20
Field Value
21
7-4
C.S0044-0 v1.0
1 f. End the call.

2 g. Remove the channel for base station 2 from the mobiles station’s preferred roaming list
3 and repeat steps b through f.
4 h. Repeat steps b and c with the mobile station operating in the Mobile Station Idle State
6 Message.

14 The mobile station shall comply with steps d, eand i.
15 7.4 Service Redirection between Band Classes
16 7.4.1 Definition
17 This test verifies Network Directed System Selection (NDSS) functions correctly. This test verifies
18 that a mobile station is capable of being redirected between band classes when the Service
19 Redirection Message is sent on the f-csch or on the f-dsch prior to user traffic being transmitted
20 and the call completes on the new system without user interaction.

26 3.7.2.3.2.16 Service Redirection Message {f-csch}
27 3.7.3.3.2.23 Service Redirection Message {f-dsch}

29 None

34 c. Instruct the mobile station to send an Origination Message to the base station.
7-5
C.S0044-0 v1.0
1 d. Instruct the base station to send a Service Redirection Message with the following
2 information to the mobile station on the f-csch or on the f-dsch.
Field Value
REDIRECT_TYPE ‘1’ (NDSS redirection)
3
4 e. Verify the mobile station acquires the target base station and the call completes without
5 additional user interaction and user traffic is present.
6 f. End the call.

7 g. Repeat steps c through f with the mobile station operating in the Idle State on base
8 station 2.

10 The mobile station shall comply with steps e and g.
11 7.5 Service Redirection between CDMA and a Non-CDMA System
12 7.5.1 Definition
13 This test verifies that a mobile station is capable of being redirected from a CDMA system to a
14 non-CDMA system when the Service Redirection Message is sent on the f-csch or on the f-dsch
15 prior to user traffic being transmitted, and the call completes on the new system without user
16 interaction. The mobile station should only be redirected to Non-CDMA systems it supports. An
17 example of a non-CDMA system is an analog system defined in [21].

7-6
C.S0044-0 v1.0

2 None

6 station.
11
Field Value
RETURN_IF_FAIL ‘0’

American Amps]
'00000011' [TACS]
'00000100' [JTACS]
‘00000101’ (DS-41)
following fields
IGNORE_CDMA ‘0’
12
15 f. End the call.
16 g. For RECORD_TYPE=’00000001’, repeat steps a through e setting IGNORE_CDMA =
17 ‘1’ in the Service Redirection Message:
18 h. Send the CDMA Capability Message from base station 2 indicating CDMA is available
19 (i. e. CDMA_AVAIL set to ‘1’).
20 i. End the call.
7-7
C.S0044-0 v1.0
1 j. Verify the mobile station remains in the Idle State on the non-CDMA system and does
2 not attempt to re-acquire CDMA.

4 The mobile station shall comply with steps e, g and j.
5 7.6 Service Redirection between Channels in the Same Band Class
6 7.6.1 Definition
7 This test verifies Network Directed System Selection (NDSS) functions correctly. This test verifies
8 that a mobile station is capable of being redirected between channels in the same band class
9 when the Service Redirection Message is sent on the f-csch or on the f-dsch prior to user traffic
10 being transmitted and the call completes on the new system without additional user interaction.


19 None
22 case, base station 1 and base station 2 have different CDMA channels in the same
23 band class.
7-8
C.S0044-0 v1.0
Field Value
RETURN_IF_FAIL ‘0’
3 f. End the call.
4 g. Repeat steps c through f with the mobile station operating in the Idle State on base
5 station 2.
6 h. Repeat steps b through d ensuring the mobile station cannot re-acquire base station 2
7 and setting RETURN_IF_FAIL = ‘1’ in the Service Redirection Message:
8 i. Verify the mobile station returns to base station 1 after failing to acquire base station 2.
9 The call may or may not complete depending on infrastructure implementation.

11 The mobile station shall comply with steps e, g, and i.
12 7.7 Extended Global Service Redirection between Band Classes
13 7.7.1 Definition
14 This test verifies that when a mobile station receives an Extended Global Service Redirection
15 Message directing it to another band class, the mobile station acquires the appropriate system.

19 2.6.2.2.11 Extended Global Service Redirection Message

21 3.7.2.3.2.27 Extended Global Service Redirection Message

24 None
7-9
C.S0044-0 v1.0

5 c. Send an Extended Global Service Redirection Message from the current base station
6 with:
Field Value
REDIRECT_P_REV_INCL ‘0’
10 f. End the call.
11 g. Repeat steps c through f with the mobile station operating in the Mobile Station Idle
12 State on base station 2.

14 The mobile station shall comply with steps d, e and g.
15 7.8 Extended Global Service Redirection between CDMA and a Non-CDMA System
16 7.8.1 Definition
18 Message directing it from CDMA to a Non-CDMA system, the mobile station acquires that
19 system. The mobile station should only be redirected to Non-CDMA systems it supports. An
20 example would be an analog system defined in [21].

7-10
C.S0044-0 v1.0


5 None

9 station.
12 directing the mobile station to the non-CDMA base station with the following
13 parameters:
14
Field Value

American Amps]
'00000011' [TACS]
'00000100' [JTACS]
‘00000101’ (DS-41)
following fields
IGNORE_CDMA ‘0’
MAX_REDIRECT_DELAY ‘00000’
18 f. End the call.
7-11
C.S0044-0 v1.0

2 The mobile station shall comply with steps d and e
3 7.9 Extended Global Service Redirection between Channels in the Same Band Class
4 7.9.1 Definition
6 Message directing it to a different channel in the same band class, the mobile station acquires the
7 appropriate system.


16 None

19 case, base station 1 and base station 2 are in the same band class with different CDMA
20 channels.
23 with:
7-12
C.S0044-0 v1.0
Field Value
4 f. End the call.

5 g. Remove the channel for base station 2 from the mobile station’s preferred roaming list
6 and repeat steps b through f.

8 The mobile station shall comply with steps d and e.
9
7-13
C.S0044-0 v1.0
1 8 SHORT MESSAGE SERVICE
2 8.1 Mobile Station Terminated SMS Tests

3 Unless otherwise noted, the following conditions apply for all tests in this section:
4 • Mobile station is capable of receiving short messages.
5 • 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
7 System Parameters Message or the ANSI-41 System Parameters Message.
8 • Transport Layer messages shall include the Bearer Reply Option.
9 8.1.1 Common Channel SMS Delivery
11 This test verifies that a short message can be sent to a mobile station in the Mobile Station Idle
12 State.
13 8.1.1.2 Traceability (see [13])
14 2.4.1.1.1.1 Mobile SMS Message Termination

16 None
18 a. Delete all outstanding short messages in the network for the mobile station.
19 b. Create a short message in the Message Center for the mobile station. Ensure that the
20 short message length is less than the maximum allowed size on the Paging Channel or
21 Forward Common Control Channel so that it can be sent to the mobile station using the
22 Paging Channel or Forward Common Control Channel9.
23 c. Power on the mobile station and wait until it is in the Mobile Station Idle State.
24 d. Instruct the network to send the short message to the mobile station.
25 e. Verify the base station sends a Data Burst Message to the mobile station with the
26 following field settings:
27
Field Value
MSG_NUMBER 1 (‘00000001’)
9
The max size for common channel SMS is base station implementation dependent.
8-1
C.S0044-0 v1.0
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
2 f. Upon receiving the Data Burst Message at the mobile station, verify the following:
3 1. The mobile station alerts the user for the incoming short message and
4 correctly displays the received short message, when selected.
5 2. The mobile station transmits Data Burst Message on the Access
6 Channel, Enhanced Access Channel or Reverse Common Control
7 Channel to acknowledge the short message, indicating no error (i.e.
8 contains a ‘Cause Codes’ parameter having ERROR_CLASS = ‘00’).

11 8.1.2 Traffic Channel SMS Delivery
13 This 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,
15 is delivered to the mobile station over the Traffic Channel.

18 2.4.2.1.2 Base Station Traffic Channel Procedures

20 None

23 b. Create a short message in the Message Center for the mobile station. Ensure that the
24 short message length is greater than the maximum length supported on the Paging
25 Channel or Forward Common Control Channel .
27 d. Instruct the network to send the short message to the mobile station. Verify the
28 following:
29 1. The base station does not send a Data Burst Message to the mobile
30 station on the paging channel or Forward Common Control Channel.
8-2
C.S0044-0 v1.0
1 2. The base station sends a General Page Message with either service
2 option 6 or service option 14.
3 3. After the mobile station enters the Conversation Substate, the base
4 station sends a Data Burst Message to the mobile station with the
6
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
7 e. Upon receiving the Data Burst Message at the mobile station, verify the following:
10 2. The mobile station transmits a Data Burst Message on the Reverse

11 Traffic Channel to acknowledge the short message, indicating no error
12 (i.e. contains a Cause Codes parameter having ERROR_CLASS = ‘00’).

14 The mobile station shall comply with step e. The base station shall comply with step d.
15 8.1.3 Traffic Channel SMS Delivery while in Conversation
17 This test verifies a short message can be sent to a mobile station when it is already in the
18 Conversation Substate.

22 2.4.2.1.2.4 Mobile Station Message Termination in the Conversation Substate

24 None

8-3
C.S0044-0 v1.0
1 c. While the mobile station is in the Conversation Substate, create a short message in the
2 Message Center for the mobile station.
4 e. Verify the base station sends a Data Burst Message to the mobile station, with the
6
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
7 f. Upon receiving the Data Burst Message at the mobile station, verify the following:

11 Traffic Channel to acknowledge the receipt of the short message and
12 indicating no error (i.e. contains a Cause Codes parameter having
13 ERROR_CLASS = ‘00’).

16 8.1.4 Delivery of Maximum Length Message
18 This test verifies the SMS transport layer capability to send to a mobile station a short message of
19 the maximum size – the maximum size is the lesser of the maximum allowable length of the
20 message center and the maximum length specified by the mobile station manufacturer. The test
21 verifies delivery of the maximum length short message on the Traffic Channel.

24 3.4.2.1 SMS Point-to-Point Message
25 3.4.3.5 Bearer Reply Option

27 None
8-4
C.S0044-0 v1.0

2 a. Clear all short messages stored in the mobile station.
3 b. Delete all outstanding short messages in the Network for the mobile station.
4 c. Create in the Message Center a maximum size short message for the mobile station.
6 e. Verify the base station sends a Data Burst Message to the mobile station on the traffic
7 channel, with the following field settings:
8
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
9 f. Upon receiving Data Burst Message at the mobile station, verify the following:
13 Traffic Channel to acknowledge receipt of the short message and
14 indicating no error (i.e. contains a Cause Codes parameter having

17 The mobile station shall comply with f. The base station shall comply with step e.
18 8.1.5 SMS Delivery Error - Mobile Station Short Message Buffer Full
20 This test verifies SMS transport layer acknowledgment capability by sending to the mobile station
21 short messages until the mobile station short message buffer is full.

24 2.4.2.1.1 Common Channel Procedures
26 3.4.3.6 Cause Codes
8-5
C.S0044-0 v1.0

2 None

4 a. Clear all short messages from the mobile station to ensure that the short message
5 buffer is empty.
6 b. Delete all outstanding short messages in the network for the mobile station.
7 c. Create in the Message Center a short message for the mobile station.
9 e. Verify the base station sends a Data Burst Message to the mobile station, with the
11
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
12 f. Upon receiving the Data Burst Message, the mobile station shall transmit a Data Burst
13 Message to acknowledge receipt of the short message and indicating no error (i.e.
14 contains a Cause Codes parameter having ERROR_CLASS = ‘00’).
15 g. Repeat step c until the mobile station short message buffer is full.
16 h. Instruct the network to send one additional short message to the mobile station.
17 i. Verify the base station sends a Data Burst Message to the mobile station, with the
19
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
20 j. Upon receiving the Data Burst Message sent in step i, verify that the mobile station
21 transmits a Data Burst Message on the Access Channel, Enhanced Access Channel or
8-6
C.S0044-0 v1.0
1 Reverse Common Control Channel to acknowledge the short message and indicating
2 temporary error (with ERROR_CLASS = ‘10’ and CAUSE_CODE=35.

4 The mobile station shall comply with step j. The base station shall comply with steps e and i.
5 8.1.6 Voice Mail Notification
7 Voice Mail Notification (VMN) notifies the subscriber of voice mail messages using the Voice Mail
8 Notification teleservice and Short Message Service protocol. Notification can be a tone, light, or
9 display, and is manufacturer dependent.
11 4.3.5 Voice Mail Notification (VMN)

12 4.5.12 Number of Messages

14 None
16 a. Configure the system as shown in Figure A-3.

17 b. Power on the mobile station and wait until it is in the Mobile Station Idle State.
18 c. Instruct the network to send a Voice Mail Notification (corresponds to an SMS Point-to-
19 Point message) to the mobile station.
20 d. Verify that the base station sends a Data Burst Message, with the BURST_TYPE field
21 set to ‘000011’, with the following parameters settings:
22 1. Teleservice Identifier parameter, IDENTIFIER = Voice Mail Notification

23 (0x1003).
24 2. Message Identifier sub-parameter, MESSAGE_TYPE = Deliver (0x1).
25 3. Number of Messages sub-parameter, MESSAGE_CT = 99.
26 e. Upon receiving the Data Burst Message, verify the following:
27 1. The mobile station transmits an SMS Acknowledge message via Data Burst
28 Message on the Access Channel, Enhanced Access Channel or Reverse
29 Common Control Channel to acknowledge the short message, indicating no error
30 (i.e. contains a Cause Codes parameter having ERROR_CLASS = ‘00’).
31 2. The mobile station indicates to the user the number of voice mail messages
32 available as indicated by the network.
33 f. Repeat step c and d, setting the MESSAGE_CT = 0.
8-7
C.S0044-0 v1.0
1 g. Upon receiving the Data Burst Message, verify that the mobile station indicates to the
2 user no voice mail messages are available.

4 The mobile station shall comply with steps e and g. The base station shall comply with step d.
5 8.2 Mobile Station Originated SMS Tests

6 This section is to be performed on mobile stations that support mobile station originated short
7 messaging.
8 8.2.1 Common Channel SMS Delivery
10 This test verifies that a short message can be sent to the Message Center (MC) by a mobile
11 station using the Access Channel, Enhanced Access Channel or Reverse Common Control
12 Channel. The short message length chosen for this test is such that it doesn’t exceed the
13 maximum message length allowed on the Access Channel, Enhanced Access Channel or
14 Reverse Common Control Channel.

16 2.4.1.1.1.2 Mobile station SMS Message Origination

19 None

21 a. Power on the mobile station and wait until it is in the Mobile Station Idle State.
22 b. Create a short message at the mobile station, of a length smaller than the maximum
23 message length allowed on the Access Channel, Enhanced Access Channel or
24 Reverse Common Control Channel 10.
25 c. Instruct the mobile station to send the short message to the network.
26 d. Verify the mobile station sends a Data Burst Message to the base station over the
27 Access Channel, Enhanced Access Channel or Reverse Common Control Channel with
28 the following field settings:
29
Field Value
10
The maximum allowed size is dependent on the current capsule size or duration signaled in the
overhead messages broadcasted by the base station and is also implementation dependent.
8-8
C.S0044-0 v1.0
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
1 e. Verify that the base station receives the short message and sends a layer 2
2 acknowledgement to the mobile station.

5 8.2.2 Traffic Channel SMS Delivery
7 This test verifies a mobile station in the Mobile Station Idle State can originate a short message of
8 length larger than the maximum length allowed on the Access Channel, Enhanced Access
9 Channel or Reverse Common Control Channel and that the message is delivered to the Message
10 Center over the Traffic Channel.
11 8.2.2.2 Traceability (see [13]
12 2.4.1.1.1.2 Mobile SMS Message Origination


15 None
18 b. Create a short message at the mobile station, of a length larger than the maximum
19 message length allowed on the Access Channel, Enhanced Access Channel or
20 Reverse Common Control Channel.
22 d. Verify the following:
23 1. The mobile station does not send the Data Burst Message over the Access
24 Channel, Enhanced Access Channel or Reverse Common Control Channel
25 2. The mobile station sends an Origination Message to originate as SMS call with
26 the SERVICE_OPTION field set to either 6 or 14.
27 3. After entering the Conversation Substate, the mobile station sends a Data Burst
28 Message, with the following fields set as follows:
29
8-9
C.S0044-0 v1.0
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
2 e. Verify the Message Center receives the short message.

3 f. Verify that upon sending the short message, the mobile station sends a Release Order
4 to release the dedicated channels.

7 8.2.3 Traffic Channel SMS Delivery while in Conversation
9 This test verifies that a short message can be sent by the mobile station when it is in the
10 Conversation Substate.

13 2.4.1.1.2.4 Mobile station Station Message Origination in the Conversation Substate
14

17 None

19 a. Setup a mobile station originated call.
20 b. While mobile station is in the Conversation Substate, create a short message.
22 d. Verify the mobile station sends a Data Burst Message, with the following fields set as
23 follows:
24
Field Value
8-10
C.S0044-0 v1.0
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
2 e. Verify the Message Center receives the short message.

3 f. Verify that upon sending the short message, the mobile station does not attempt to
4 release the dedicated channels.

7 8.2.4 Unknown Destination Address
9 This test verifies the base station can process a mobile station originated short message with an
10 unknown destination address and will inform the mobile station regarding an unknown destination
11 address.

14

18 None

21 b. Create a short message at the mobile station, but with an unknown address in the
22 destination address field.
23 c. Instruct the mobile station to send the short message to the base station.
24 d. Verify the mobile station sends a Data Burst Message, with the following fields set as
25 follows:
26
Field Value
8-11
C.S0044-0 v1.0
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
1 e. Verify the Message Center receives the short message and the base station sends a
2 Data Burst Message to the mobile station indicating ‘an unknown address’

4 The mobile station shall comply with step d. The base station shall comply with step e.
5 8.2.5 Mobile Station Originated SMS Disabled
7 This test verifies that when mobile station originated SMS is not activated in the network, the
8 base station can process a mobile station originated short message and inform the mobile station
9 that short message origination has been denied.

12

16 None
18 a. Ensure the mobile station originated short message feature for the mobile station is not
19 activated in the network.
21 c. Create a short message at the mobile station, with the Bearer Reply Option parameter
22 set.
23 d. Instruct the mobile station to send the short message to the base station.
24 e. Verify the mobile station sends a Data Burst Message, with the following fields set as
25 follows:
26
Field Value
8-12
C.S0044-0 v1.0
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
1 f. Upon receiving the Data Burst Message at the base station, verify the following:
2 1. The base station sends a Data Burst Message to the mobile station, with
3 an indication that the short message origination has been denied.
4 2. The base station does not route the short message to the Message
5 Center.

7 The mobile station shall comply with step e. The base station shall comply with step f.
8 8.2.6 SMS Not Supported by Base Station
10 This test verifies the base station can process a mobile station originated short message, and
11 inform the mobile station that SMS is not supported by the base station.

14

18 None

20 a. Ensure the base station is not capable of SMS or that SMS has been disabled for this
21 test.
23 c. Create a short message at the mobile station, with Bearer Reply Option parameter set.
24 d. Instruct the mobile station to send the short message to the network.
25 e. Verify the mobile station sends a Data Burst Message, with the following fields set as
26 follows:
27
8-13
C.S0044-0 v1.0
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
2 f. Upon receiving the Data Burst Message at the base station, verify the following:
3 1. The base station sends a Data Burst Message to the mobile station, with an
4 indication that SMS is not supported by this base station.
5 2. The base station does not route the short message to the Message Center.

7 The base station shall comply with step f.
8 8.3 Broadcast SMS Delivery on the Common Channel
9 8.3.1 Definition
10 This test verifies that mobile stations are able to receive broadcast SMS messages sent by the
11 network addressed to any broadcast address that the mobile stations are configured to receive
12 based on the priority, service and language.
14 2.4.1.2.1 Common Channel Procedures for Broadcast SMS

15 4.3.1.3 Broadcast Messaging Service

17 None

19 a. Connect the base station and mobile stations as shown in Figure A-8.
20 b. Ensure mobile station 1 is configured to receive broadcast SMS with normal priority
21 while mobile station 2 is configured to receive broadcast SMS with emergency priority.
22 Also, ensure that both mobile stations are configured to receive other filtering
23 categories (i.e. service and language) for this test.
24 c. Power on the mobile stations and wait until they are registered.
25 d. Clear any outstanding broadcast messages in the network.
26 e. Create broadcast message 1 shown in Table 8.3.4-1
8-14
C.S0044-0 v1.0
1 f. Instruct the network to broadcast message 1.

2 g. Verify the base station sends a Data Burst Message, with the following fields set as
3 follows:
4
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
6 Table 8.3.4-1
Broadcast Message Broadcast Message Priority Priority Indicator Value
Message 1 Normal 00
Message 2 Emergency 11
7
8 h. Upon receiving the Data Burst Message, verify that mobile station 1 displays broadcast
9 message 1 (as a Normal message, if such display is supported) and mobile station 2
10 does not.
11 i. Create broadcast message 2 shown in Table 8.3.4-1.
12 j. Instruct the network to broadcast message 2.
13 k. Verify the base station sends a Data Burst Message, with the following fields set as
14 follows:
15
16
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
17
8-15
C.S0044-0 v1.0
1 l. Upon receiving the Data Burst Message, verify both mobile stations display broadcast
2 message 2 (as an Emergency message, if such a display is supported)

4 The mobile station shall comply with steps h and l. The base station shall comply with steps g and
5 k.
6 8.4 Mobile Station Terminated Enhanced Messaging Services [EMS] Tests:

7 Unless otherwise noted, the following conditions apply for all tests in this section:
8 a. Mobile station is capable of receiving Enhanced Messaging Services [EMS] messages.
9 b. The EMS message feature for the mobile station is activated.
10 c. Base station has Power-up registration enabled by setting POWER-UP_REG = ‘1’ in
11 the System Parameters Message or the ANSI-41 System Parameters Message.
12 d. Transport Layer messages shall include the Bearer Reply Option.
13 e. SMS message carries Teleservice ID parameter is set to WEMT (0x1005),, and
14 HEAD_IND of Message Identifier subparameter is set to '1'
15 8.4.1 Multi-Segment EMS Message Delivery
17 This test verifies the mobile station’s ability to receive and properly display multi-segmented EMS
18 messages.
20 4.3.7 Wireless Enhanced Messaging Teleservice

21 2.4.1.1.1.1 Mobile station SMS Message Termination

23 None

25 a. Delete all outstanding short messages in the network for the mobile station. Delete all
26 short messages in the mobile station.
27 b. Create an EMS message in the Message Center for the mobile station, consisting of (3)
28 three segments.
29 c. Instruct the Message Center to send the first segment of the EMS message to the
30 mobile station.
31 d. Verify that the base station sends the first Data Burst Message to the mobile station,
32 with the following fields set as follows:
33
8-16
C.S0044-0 v1.0
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
1 e. Verify that the mobile station transmits a Data Burst Message to acknowledge the
2 received Data Burst Message, and indicates no error (i.e. containing Cause Codes
3 parameter having ERROR_CLASS = ‘00’).
4 f. Instruct the Message Center to send the remaining segments of the EMS message to
6 g. Verify that the base station sends the remaining Data Burst Messages to the mobile
7 station, with the following fields set as follows:
8
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
10 h. Verify that the mobile station transmits a Data Burst Message to acknowledge each
11 received Data Burst Message, containing a message segment, and indicates no error
12 (i.e. contains Cause Codes parameters having ERROR_CLASS = ‘00’).
13 i. Upon receiving all the Data Burst Messages at the mobile station, verify the following:
14 1. The mobile station alerts the user for the incoming EMS message and correctly
15 displays the received message, when selected. Verify that all the segments of
16 the EMS message segments sent are properly displayed in correct order.

18 The mobile station shall comply with steps e, h, and i. The base station shall comply with steps d
19 and g.
8-17
C.S0044-0 v1.0
1 8.4.2 Delivery of Predefined Sound Elements
3 This test verifies mobile station’s ability to receive and properly play pre-defined EMS sound
4 elements.

7 2.4.1.1.1.1 Mobile station SMS Message Termination

9 None

13 b. Create an EMS message in the Message Center for the mobile station. In the message
14 include (1) one predefined sound element.
16 d. Instruct the network to send the EMS message to the mobile station.
18 specified fields set as follow:
19
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
21 1. The mobile station alerts the user for the incoming message and correctly
22 displays the received message (if chosen).
23 2. The mobile station properly plays the predefined sound, when selected.
24 3. The mobile station transmits a Data Burst Message to acknowledge the EMS
25 message, indicating no error (i.e. contains a Cause Codes parameter having
8-18
C.S0044-0 v1.0

3 8.4.3 Delivery of Predefined Animation Elements
5 This test verifies mobile station’s ability to receive and properly play pre-defined EMS animation
6 elements.


11 None

16 include (1) one pre-defined animation in a specific order.
21
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
25 2. The mobile station properly plays the pre-defined animation, when selected.
8-19
C.S0044-0 v1.0

6 8.4.4 Delivery of User Defined Sound Elements - MT
8 This test verifies mobile station’s ability to receive and properly play user defined (iMelody) EMS
9 sound elements.


14 None

19 include (1) one iMelody sound object.
24
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
8-20
C.S0044-0 v1.0
1 2. The mobile station properly plays the iMelody sound object, when selected.
2 Verify that the iMelody being played is same as the one being transmitted.

8 8.4.5 Delivery of User Defined Animation Elements - MT
10 This test verifies mobile station’s ability to receive and properly play user defined EMS animation
11 elements.


16 None

21 include one user-defined animation object.
26
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
8-21
C.S0044-0 v1.0
3 2. The mobile station properly plays the user-defined animation, when selected.

9 8.4.6 Delivery of User Defined Picture Elements - MT
11 This test verifies mobile station’s ability to receive and properly play user defined EMS picture
12 elements.


17 None

22 include one user-defined picture object.
27
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
8-22
C.S0044-0 v1.0
4 2. The mobile station properly displays the user-defined picture, when selected.

10 8.4.7 Delivery of Formatted Text
12 This test verifies mobile station’s ability to receive and properly display formatted text embedded
13 in EMS messages.


18 None
22 b. Create an EMS message in the Message Center for the mobile station. From the
23 following text, include the text with formatting that is supported by the mobile station in
24 the message:
25
26
Normal Bold Italics Bold-Italics
27
28
29 Underlined Bold-Underlined Bold-Italics-Underlined
30
31 Left-Justified
32
33 Center-Justified
34
8-23
C.S0044-0 v1.0
5
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
9 2. The mobile station properly displays the text, including correct formatting of the
10 lines of text displayed.

16 8.5 Mobile Station Originated Enhanced Messaging Services [EMS] Tests:
17 8.5.1 Multi-Segment EMS Message Delivery
19 This test verifies mobile station’s ability to compose and send multi-segmented EMS messages.

22 2.4.1.1.2 Mobile Station Traffic Channel Procedures

25 None
8-24
C.S0044-0 v1.0

2 a. Power on the mobile station and wait until it is in the Mobile station Idle State.
3 b. Create an EMS message at the mobile station, consisting of three (3) segments.
4 c. Instruct the mobile station to send all the segments of the EMS message to the
5 Message Center.
6 d. Verify that the Message Center receives all the segments and sends an SMS
7 Acknowledgement for each segment to the mobile station.
8 e. Verify that upon sending the short message, the mobile station sends a Release Order
9 to release the dedicated channels.

12 8.5.2 Delivery of Predefined Sound Elements
14 This test verifies the mobile station’s ability to compose and send messages containing
15 predefined EMS sound elements.


20 None

23 b. Create an EMS message at the mobile station. In the message include (1) one
24 predefined sound.
25 c. Instruct the mobile station to send the EMS message to the Message Center.
26 d. Verify the mobile station sends a Data Burst Message to the base station with the fields
27 set as follows:
28
29
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
8-25
C.S0044-0 v1.0
NUM_MSGS 1 (‘00000001’)
2 e. Verify that the Message Center receives Data Burst Message and sends the SMS
3 Acknowledgement to the mobile station.
4 f. Verify that the EMS message sent from the test mobile station contains (1) one
5 predefined sound.

8 8.5.3 Delivery of Predefined Animation Elements
10 This test verifies the mobile station’s ability to compose and send messages containing
11 predefined EMS animation elements.


16 None
19 b. Create an EMS message at the mobile station. In the message include (1) one
20 predefined animation object.
23 set as follows:
24
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
8-26
C.S0044-0 v1.0
1
4 f. Verify that the EMS message sent from the test mobile station contains the predefined
5 animation object.

7 The mobile station shall comply with steps d and f. The base station shall comply with step e.
8 8.5.4 Delivery of User Defined Sound Elements
10 This test verifies the mobile’s ability to compose and send a message containing user defined
11 (iMelody) EMS sound elements.


16 None

19 b. Create an EMS message at the mobile station. In the message include (1) one iMelody
20 sound object.
23 set as follows:
24
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
25
8-27
C.S0044-0 v1.0
1 f. Verify that the EMS message sent from the test mobile station contains the iMelody
2 sound object sent.

5 8.5.5 Delivery of User Defined Animation Elements
7 This test verifies mobile station’s ability to compose and send a message containing user defined
8 EMS animation elements.


13 None

16 b. Create an EMS message at the mobile station. In the message include one user-
17 defined animation object.
20 set as follows:
21
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
24 f. Verify that the EMS message sent from the test mobile station contains the user-
25 defined animation object sent.
8-28
C.S0044-0 v1.0

3 8.5.6 Delivery of User Defined Picture Elements
5 This test verifies mobile’s ability to send user defined EMS picture elements.


10 None
13 b. Create an EMS message at the mobile station. In the message include one user-
14 defined picture object.
17 set as follows:
18
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
19
22 f. Verify that the EMS message sent from the test mobile station contains the user-
23 defined picture object sent.

8-29
C.S0044-0 v1.0
1 8.5.7 Delivery of Formatted Text
3 This test verifies mobile’s ability to compose and send formatted text embedded in EMS
4 messages.


9 None

12 b. Create an EMS message in the mobile station under test. From the following text,
13 include the text with formatting that is supported by the mobile station in the message:
14
15
Normal Bold Italics Bold-Italics
16
17
18 Underlined Bold-Underlined Bold-Italics-Underlined
19
20 Left-Justified
21
22 Center-Justified
23
26 set as follows
27
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
8-30
C.S0044-0 v1.0
1
4 f. Verify that the EMS message sent from the test mobile station contains the properly
5 formatted text information.

8
8-31
C.S0044-0 v1.0
1 9 SUBSCRIBER CALLING FEATURES
2 9.1 Call Forwarding Unconditional (CFU)
3 9.1.1 Definition
4 CFU permits a called subscriber to send incoming calls addressed to the called subscriber’s
5 Directory Number to another Directory Number (forward-to number). If this feature is active, calls
6 are forwarded regardless of the condition of the termination.

8 505 Call Forwarding—Unconditional

10 None

12 a. Power on the mobile station and wait until it reaches Mobile Station Idle State.
13 b. Dial the CFU feature activation code, followed by the forward-to number, followed by
14 SEND. Verify feature update confirmation at the mobile station (confirming audio tones
15 from the network).
16 c. Setup a call from a land party to the mobile station. Verify call is forwarded and that if
17 the Network directs the mobile station to “Ping Ring” it plays a single burst of 500 ms.
18 d. Answer the call on the forward-to line, and verify the audio path.
19 e. End the call.
20 f. Dial the CFU deactivation feature code followed by SEND. Verify feature update
21 confirmation at the mobile station.
22 g. Verify that CFU has been deactivated, by calling the mobile station under test and
23 verifying that the mobile station rings and completes the call when answered.

25 The mobile station and the base station shall comply with steps b, c, d, f and g.
26 9.2 Call Forwarding Busy (CFB)
27 9.2.1 Definition
28 CFB permits a called subscriber to have the system send incoming calls to another Directory
29 Number (forward-to number) when the subscriber is engaged in a call or service.

31 502 Call Forwarding Busy
9-1
C.S0044-0 v1.0

2 None

5 b. Dial the CFB activation feature code, followed by the forward-to-number, followed by
8 c. Place the mobile station under test in a voice call.
9 d. Attempt a second call from a land party to the mobile station under test. Verify the call is
10 forwarded to the forward-to-number, and that if the Network directs the mobile station to
11 “Ping Ring” it plays a single burst of 500 ms.
12 e. Answer the call on the forward-to line, and verify the audio path.
13 f. End all calls.
14 g. Dial the CFB deactivation feature code followed by SEND. Verify feature update
16 h. Verify that CFB has been deactivated, e.g. By calling the mobile station under test while
17 busy and verifying that the second call is not forwarded.

20 9.3 Call Forwarding Default (CFD)
21 9.3.1 Definition
22 CFD permits a called subscriber to have the system send incoming calls to another Directory
23 Number (forward-to-number) when the subscriber is engaged in a call, does not respond to
24 paging, does not answer the call within a specified period after being alerted or is otherwise
25 inaccessible.
27 503 Call Forwarding—Default

29 None

32 b. Dial the CFD activation feature code, followed by the forward-to number, followed by
9-2
C.S0044-0 v1.0
1 c. Attempt a call from a land party to the mobile station. Verify the call is forwarded and
2 that if the Network directs the mobile station to “Ping Ring” it plays a single burst of 500
3 ms.
5 e. End call.
6 f. Dial the CFD deactivation feature code followed by SEND. Verify feature update
8 g. Verify that CFD has been deactivated, by calling the mobile station under test and
9 verifying that the mobile station rings and does not forward.

12 9.4 Call Forwarding No Answer (CFNA)
13 9.4.1 Definition
14 CFNA permits a called subscriber to have the system send incoming calls addressed to the called
15 subscriber’s Directory Number to another Directory Number (forward-to number) when the
16 subscriber fails to answer.

18 504 Call Forwarding—No Answer

20 None
23 b. Dial the CFNA activation feature code, followed by the forward-to number, followed by
26 c. Setup a call from a land party to the mobile station. Verify the mobile station rings, but
27 when not answered, the call is forwarded to the forward-to number.
29 e. End the call.
30 f. Dial the CFNA deactivation feature code followed by SEND. Verify feature update
32 g. Verify that CFNA has been deactivated, by calling the mobile station and verifying that
33 the mobile station rings and does not forward.
9-3
C.S0044-0 v1.0

3 9.5 Three-Way Calling
4 9.5.1 Definition
5 This tests mobile station’s operation of Three-way Calling. In Three-way Calling, the base station
6 responds to Flash With Information Messages from the mobile station to connect a third party to
7 an established two-way call.

9 522 Three Way Calling

11
MS BS
Voice Traffic in 2-way call
Flash with Info Message no records
Ack Order
3rd party
Flash with Info Message
number
Ack Order
Connect 3-
Flash with Info Message
way
Ack Order
12

15 b. Ensure the base station will allow the mobile station to perform Three-way calling via
16 subscriber profile or by dialing a feature activation code such as *31+ SEND.
17 c. Set up a normal two-way voice call with a second party.
18 d. Put the second party on hold using the prescribed method at the mobile station, e.g.
19 send a Flash With Information Message by pressing the SEND button.
20 e. Verify the second party is placed on hold and the mobile station alerts the user to
21 commence dialing the third party number, e. g. plays a dial tone.
22 f. Dial the third party number on the mobile station and send it out using the prescribed
23 method, e. g. send a Flash With Information Message containing the Keypad Facility
24 Information Record or the Called Party Number Information Record by pressing the
25 SEND button after entering dialed digits.
9-4
C.S0044-0 v1.0
1 g. Verify the third party phone rings and answers with normal audio.
2 h. Connect all of the Three-Way Call parties, e. g. send a Flash With Information Message
3 by pressing the SEND button, and verify the three-way connection is established with
4 normal audio.
5 i. End the call.
6 j. Ensure the base station will not allow the mobile station to perform Three-way calling
7 via subscriber profile or by dialing a feature de-activation code such as *91+ SEND

9 The mobile station shall comply with the requirements in steps b, e, g, h, and j.
10 9.6 Call Alerting
11 9.6.1 Definition
12 This is a test for standard mobile station incoming call alerting (ringing). An incoming call alert is
13 played or displayed by the mobile station as a result of receiving an Alert With Information
14 Message or an Extended Alert with Information Message with a Signal information record.
16 Table 3.7.5.5-1 Signal Type

17 Table 3.7.5.5-2 Alert Pitches
18 Table 3.7.5.5-3 Tone Signals (SIGNAL_TYPE = ‘00’)
19 Table 3.7.5.5-4 ISDN Alerting (SIGNAL_TYPE = ‘01’)
20 Table 3.7.5.5-5 IS-54B Alerting (SIGNAL_TYPE = ‘10’)
21 Table 3.7.5-1 Information Record Types (base station)

23
9-5
C.S0044-0 v1.0
MS BS
Page Message to mobile
Page Response Message
possible service negotiation
Service Connect Complete Message
Alert with Info Message Message (ring for mobile)
Connect Order Message
Voice Traffic
Release Order Messages

3 a. Allow the mobile station to come to the idle state on the base station, and make a
4 mobile station terminated call.
5 b. Verify the mobile station receives an Alert with Information Message or Extended Alert
6 with Information Message with a Signal Information record. The Alert with Information
7 Message may or may not contain a Calling Party Number Information record.
8 c. Verify the mobile station rings (plays an incoming call alert).

9 d. Answer the call, verify the call completes successfully, then end the call.
10 e. Steps a through d may be repeated using each variation of parameters in the Signal
11 Information record for SIGNAL_TYPE, ALERT_PITCH, and SIGNAL as supported by

14 The mobile station shall comply with the requirements in step c, d, and e.
15 9.7 Caller ID for Mobile station Terminated Call Setup
16 9.7.1 Definition
17 This tests delivery and display of Caller ID Calling Party Number (CPN) during call setup.
9-6
C.S0044-0 v1.0

2 3.7.5.3 Calling Party Number
3 Table 2.7.1.3.2.4-2 Number Types

4 Table 2.7.1.3.2.4-3 Numbering Plan Identification
5 Table 2.7.4.4-1 Presentation Indicators

8 None

10 a. Configure the base station to send Caller ID for mobile station terminated calls.
11 b. Allow the mobile station to come to the idle state on the base station, and initiate a
12 mobile station terminated call.
13 c. Verify the mobile station displays the correct Caller ID before answering the call and
14 then answer the call.
15 d. Repeat steps b to c for all Caller ID base station configurations, e.g. parameters PI =
16 ‘01’ (Presentation Restricted) and PI = ‘10’ (Number not available), as supported by the
17 base station, and verify the correct outcome.

19 The mobile station shall comply with requirements in steps c and d. In step d, for PI = ‘01’
20 (Presentation Restricted) and PI = ‘10’ (Number not available), the mobile station shall NOT
21 display the Caller ID, but may display ‘No Caller ID’ or something to that effect.
22 9.8 Caller ID for Call Waiting
23 9.8.1 Definition
24 This tests delivery and display of Caller ID Calling Party Number (CPN) for Call Waiting calls.

27 3.7.5.22 Call Waiting Indicator
28 Table 3.7.5.16-2 Mandatory Control Tags and Display Text Tags

9-7
C.S0044-0 v1.0

2 None

4 a. Configure the base station to send Caller ID for Call Waiting calls.
5 b. Set up a mobile station terminated voice call.
6 c. While this voice call is in progress, attempt a second call to the mobile station.
7 d. Verify the mobile station displays the correct Caller ID of the Call Waiting caller.
8 e. Repeat steps b to d for all Caller ID base station configurations, e. g. CPN parameters
9 PI = ‘01’ (Presentation Restricted) and PI = ‘10’ (Number not available), as supported
10 by the base station, and verify the correct outcome.

12 The mobile station shall comply with requirements in steps d and e. In step e, for PI = ‘01’
13 (Presentation Restricted) and PI = ‘10’ (Number not available), the mobile station shall NOT
14 display the Caller ID, but may display ‘No Caller ID’ or something to that effect.
15 9.9 Call Waiting
16 9.9.1 Definition
17 This test verifies mobile station call-waiting notification, alerting, and connection with Flash with
18 Information Messages or Extended Flash with Information Messages. It also checks the mobile
19 station ability to activate and deactivate the call-waiting feature on the network.

21 3.7.5.5 Signal
22 Table 2.7.4-1 Information Record Types (mobile station)
24 Table 3.7.5.5-5 IS-54B Alerting (SIGNAL_TYPE = ‘10’)

27 None

30 b. Activate call waiting, e.g. make a dedicated call *41-SEND, and verify that the mobile
31 station plays or displays a notification that call waiting has been activated, e.g. audio
32 confirmation tones in the earpiece.
9-8
C.S0044-0 v1.0
1 c. Verify the call-waiting activation call ends without user interaction (Base Station
2 releases the call), and the mobile station returns to the idle state on the base station.
3 d. Set up a voice call with the mobile station. While the first call is in progress, attempt a
4 second mobile station terminated call, and verify that a call-waiting alert is played at the
5 mobile station, e.g. tones in the earpiece.
6 e. Cause the mobile station to accept the second call, e.g. press SEND, and verify the
7 connection to the second caller with normal audio.
8 f. Cause the mobile station to flash back to the first call, e.g. press SEND, and verify the
9 connection to the first caller with normal audio.
10 g. Press END on the mobile station to end the call. Note: in some implementations, if the
11 mobile station subscriber ends a call waiting call while the other party is still waiting, the
12 base station will initiate a mobile station terminated call to re-connect the waiting party.
13 If this is the case, answer the call, then end that call too.
14 h. Deactivate call waiting on the base station, e.g. make a dedicated call *410-SEND, and
15 verify the mobile station plays or displays a notification that call waiting has been
16 disabled, e.g. tones in the earpiece.
17 i. Set up a new call with the mobile station. While the call is in progress, attempt another
18 mobile station terminated call, and verify that no call-waiting alert is played at the mobile
19 station.

21 The mobile station shall comply with the requirements in steps b, c, d, e, f, h, and i.
22 9.10 Voice Mail Message Waiting Notification from the Idle State
24 This test verifies mobile station response to message waiting notification while the mobile station
25 is in the idle state. Notification can be a tone, light, or display and is manufacturer dependent.
27 3.7.5.6 Message Waiting

28 3.7.2.3.2.12 Feature Notification Message

30 None
32 a. Power on the mobile station and allow it to come to the idle state on the base station.
33 b. Instruct the base station to send a voice mail message waiting notification, setting the
34 number of voice mail messages waiting to a value ranging from 1 to 31.
35 c. Verify the mobile station gives an indication of the change in message waiting status.
9-9
C.S0044-0 v1.0
1 d. Verify that any indication on the mobile station of the number of messages waiting
2 reflects the correct value.
3 e. Repeat steps b through d for a different number of voice mail messages waiting.
4 f. Repeat steps b through d, except in step b, send notification for zero voice mail
5 messages waiting, e. g. to clear the mobile station’s voice mail waiting indicator on the
6 mobile station.

8 The mobile station shall comply with the requirements in steps c and d.
9 9.11 Voice Mail Message Waiting Notification from the Conversation State
11 This test verifies mobile station’s response to message waiting notification while the mobile
12 station is in the conversation state.
14 3.7.5.6 Message Waiting

16 None

18 a. Power on the mobile station and allow it to come to the idle state on the base station.
19 b. Set up a call with the mobile station.
20 c. Instruct the base station to send a voice mail message waiting notification, setting the
21 number of voice mail messages waiting to a value less than the maximum number the
22 mobile station can display.
23 d. Verify that the mobile station gives an indication of the change in message waiting
24 status.
25 e. Verify that any indication on the mobile station of the number of messages waiting
26 reflects the correct value.
27 f. Instruct the base station to send a voice mail message waiting notification, setting the
28 number of messages waiting to a value that exceeds the maximum number that can be
29 displayed by the mobile station.
30 g. Verify the mobile station displays the maximum number of messages that it can display.

32 The mobile station shall comply with the requirements in steps d, e, and g.
9-10
C.S0044-0 v1.0
1 9.12 Calling Name Presentation (CNAP) for Mobile station Terminated Call Setup
2 9.12.1 Definition
3 This test will verify that the mobile station in the Mobile Station Idle State properly displays the
4 Calling Name Information (CNA) for an incoming call.

7 3.7.5.16 Extended Display, Calling Party Name = type ‘10001101’
8 3.7.5.21 Multiple Character Extended Display



16 None

18
19 a. Ensure the mobile station has been assigned CNAP Class-of -Service and is configured
20 to display CNAP if it is delivered.
21 b. Power on the mobile station and wait until it reaches Mobile Station Idle State.
22 c. Setup a call to the mobile station from a 10-digit Calling Party Number (CPN).
23 d. Instruct the base station to indicate CNA with Presentation Allowed. Verify that the base
24 station sends a Feature Notification Message, Alert With Information Message, or a
25 Flash With Information Message with an Extended Display information record and CPN
26 information record with the PI field set to “00” (Presentation Allowed).
27 e. Verify the mobile station receives and displays the CNA and Calling Number
28 Identification (CNI).
30 g. End call.
31 h. Change the PI field of the CPN information record to “01” (Presentation Restricted).
32 i. Repeat steps c through g, except during step e, verify that the mobile station does not
33 display the CNA or CNI and that it indicates the CNA is restricted, during the first
34 alerting cycle.
9-11
C.S0044-0 v1.0
1 j. Change the PI field of the CPN information record to “10” (Number Not Available).
2 k. Repeat steps c through g, except during step e, verify that the mobile station does not
3 display the CNA or CNI and that it indicates the CNA is not available, during the first
4 alerting cycle.

6 The mobile station shall comply with steps e, f, i, and k. The base station shall comply with steps
7 d and f.
8 9.13 Calling Name Presentation (CNAP) from Conversation State
9 9.13.1 Definition
10 This test will verify that the mobile station in Conversation Substate (with call waiting enabled)
11 properly displays the Calling Party Name (CNA).

14 3.7.5.16 Extended Display, Calling Party Name = type ‘10001101’
15 3.7.5.21 Multiple Character Extended Display

23 None
25 a. Ensure mobile station is assigned CNAP Class-of-Service, and that the mobile station
26 has not been pre-programmed (phone book) with calling name/number information.
27 b. Set Presentation Indicator (PI) field of the CPN information record of calling parties 1
28 and 2 to “00” (Presentation Allowed).
29 c. Power on the mobile station and wait until it reaches Mobile Station Idle State.
30 d. Setup a call from party 1 to the mobile station (from 10-digit CPN 1).
31 e. Verify the mobile station receives and displays the CNA and CNI (of party 1) during the
32 first alerting cycle.
9-12
C.S0044-0 v1.0
1 g. Maintain the call and setup another call from party 2 to the mobile station (from 10-digit
2 CPN 2). Verify that the base station sends a Alert With Information Message or Flash
3 With Information Message with an Extended Display information record and the PI field
4 set to “00” (Presentation Allowed).
5 h. Verify the mobile station receives and displays the CNA and CNI (of party 2) with
6 delivery of the call waiting indication.
7 i. End both calls.
8 j. Change the PI field of the CPN information record of both calling parties (1 and 2) to
9 '01' (Presentation Restricted).
10 k. Repeat steps d through i, except in step e and h, verify the mobile station does not
11 display the CNA and that it indicates the CNA is restricted.
12 l. Change the PI field of the CPN information record of both calling parties (1 and 2) to
13 '10' (Number Not Available).
14 m. Repeat steps d through i, except in step e and h, verify the mobile station does not
15 display the CNA and that it indicates the CNA is not available.

17 The mobile station shall comply with steps e and h.
18 9.14 Calling Name Presentation (CNAP) with Forwarding
20 This test verifies the mobile station receiving a forwarded call from party 2 (redirecting party),
21 properly displays redirection information from calling party 1 (originating party) and party 2.
22 9.14.2 Traceability: (See [4] );
23 3.7.5.3: Calling Party Number

25 None

27 a. Ensure the mobile station is assigned the CNAP Class-of-Service and that the mobile
28 station has not been pre-programmed (phone book) with calling name/number
29 information.
30 b. Ensure party 2 has been assigned Call Forwarding Unconditional, programmed to
31 forward calls to the mobile station directory number, and that this service is invoked.
32 c. Set Presentation Indicator field of the CPN information record of calling parties 1 and 2
33 to '00' (Presentation Allowed).
34 d. Power on the mobile station and wait until it reaches Mobile Station Idle State.
9-13
C.S0044-0 v1.0
1 e. Setup a call from party 1 to party 2 (from 10-digit CPN 1).

2 f. Verify the call is forwarded to the mobile station and that the mobile station properly
3 receives and displays the CNA and CNI of the original calling party 1 and/or the
4 redirected party 2 during the first alerting cycle.
5 g. Verify user data in both directions for party 1 (originating party), and the mobile station.
6 h. End call.
7 i. Change the PI field of the CPN information record of the calling parties (1 and 2) to '01'
8 (Presentation Restricted).
9 j. Repeat steps e through h, except in step f, verify the mobile station does not display the
10 CNA or CNI associated with parties 1 and 2, and that it indicates the CNA is restricted
11 during the first alerting cycle.
12 k. Change the PI field of the CPN information record of the calling parties (1 and 2) to '10'
13 (Number Not Available).
14 l. Repeat steps e through h, except in step f, verify the mobile station does not display the
15 CNA or CNI associated with parties 1 and 2 and that it indicates the CNA is not
16 available, during the first alerting cycle.

18 The mobile station shall comply with steps f and g .
19 9.15 Display Records sent in the Feature Notification Message.
21 This test verifies that the mobile station displays Paging Channel and Forward Common Control
22 Channel Display Information Records, Extended Display Information Records and Multiple
23 Character Extended Display Records. This test also verifies that Display Information Records,
24 Extended Display Information Records and Multiple Character Extended Display Records do not
25 interfere with any other information records or features.

28 2.6.10.1 Alerting
30 3.7.3.3.2.3 Alert with Information Message
31 3.7.3.3.2.14 Flash with Information Message

34 None
9-14
C.S0044-0 v1.0

2 a. Verify the mobile station is in Idle State.
3 b. Instruct the base station to send a display record of at least 15 characters in a Feature
4 Notification Message on the Paging Channel or Forward Common Control Channel.
5 c. Upon receiving the Feature Notification Message, verify the mobile station displays
6 characters as instructed in the Display Record contained in the Feature Notification
7 Message.
8 d. Instruct the base station to send a new Display Record of at least 15 characters in a
9 Feature Notification Message.
10 e. Upon receiving the Feature Notification Message, verify the mobile station displays the
11 new characters as instructed in the Display Record and performs other information
12 records contained in the Feature Notification Message.
13 f. If supported by the mobile station and the base station, repeat steps b to e using the
14 Extended Display Record.
15 g. If supported by the mobile station and the base station, repeat steps b to eusing the
16 Multiple Character Extended Display Record.
17 h. If supported by the mobile station and the base station, repeat steps b to e using the
19

21 The mobile station shall comply with steps c, e, f, g and h.
22 9.16 Display Records Sent in the Flash With Information Message
24 This test verifies that the mobile station displays Traffic Channel Display Information Records,
25 Extended Display Information Records and Multiple Character Extended Display Records. This
26 test also verifies that Display Information Records, Extended Display Information Records and
27 Multiple Character Extended Display Records do not interfere with other information records or
28 features.


9-15
C.S0044-0 v1.0

2 None

4 a. Setup a mobile station originated call.
5 b. Instruct the base station to send a Display Record of at least 15 characters in a Flash
6 With Information Message.
7 c. Upon receiving the Flash With Information Message, verify the mobile station displays
8 characters as instructed in the Display Record contained in the Flash with Information
9 Message.
10 d. Instruct the base station to send a new display record of at least 15 characters
11 contained in the Flash with Information Message.
12 e. Upon receiving the Flash With Information Message, verify the mobile station displays
13 the new characters as instructed in the Display Record.
14 f. If supported by the mobile station and the base station, repeat steps a to e using the
16 g. If supported by the mobile station and the base station, repeat steps a to e using the

19 The verifications in steps c and e in the traffic channel shall be successfully carried out for all
20 forms of display records supported. When various information records are sent to the mobile
21 station in the same message, the mobile station shall properly process all information records. If
22 display records are not supported in the mobile station, there shall be no negative impact on any
23 information records supported by the mobile station. There shall be no negative impact on any
24 supported feature or call processing when display records are sent to the mobile station in the
25 same message as other information records.
26 If supported by the mobile station, the most current display record shall be displayed on the
27 mobile station.
28 9.17 Display Records Sent in the Alert with Information Message
30 This test verifies the mobile station displays Display Information Records, Extended Display
31 Information Records and the Multiple Character Extended Display Record on the traffic channel.
32 This test also verifies that Display Information Records, Extended Display Information Records
33 and Multiple Character Extended Display Record do not interfere with other information records
34 or features.

9-16
C.S0044-0 v1.0


5 None

7 a. Setup a mobile station terminated call.
8 b. Instruct the base station to send in an Alert With Information Message, a Display
9 Record of at least 15 characters, and a Calling Party Number Record.
10 c. Upon receiving the Alert With Information Message, verify the mobile station displays
11 the characters as instructed in the display record or extended display record and
12 displays the Calling Party Number in the Alert With Information Message.
13 d. If supported by the mobile station and the base station, repeat steps a to c using the
15 e. If supported by the mobile station and the base station, repeat steps a to c using the

18 The verifications in step c in the traffic channel shall be successfully carried out for all forms of
19 display records supported. When various information records are sent to the mobile station in the
20 same message, the mobile station shall process all information records. If display records are not
21 supported in the mobile station, there shall be no negative impact on information records
22 supported by the mobile station. There shall be no negative impact on any supported feature, or
23 on call processing when display records are sent to the mobile station in the same message as
24 other information records.
25 If supported by the mobile station, the most current display record shall be displayed on the
26 mobile station.
27 9.18 TTY/TDD
29 This test verifies the system ability to transfer TTY/TDD information in the forward and reverse
30 link directions.
31 9.18.2 Traceability: (See [18,19 and 20])

33 None
9-17
C.S0044-0 v1.0
2 9.18.4.1 Basic TTY/TDD Operation

3 a. Connect the mobile station as shown in Figure 9.18.4-1.
4
MS MTO
Um BS/MSC
TE2M Rn MT2
Ai PSTN W TE2L
KEY
Specific Network Entity
Collective (Composite Entity)
X Interface Reference Point
5
6 Figure 9.18.4-1
7 The base station (Base Station) in this model represents the entire system infrastructure. It
8 contains the transceiver equipment and Mobile Switching Center (MSC).
9 Terminal Equipment (TE2) is TTY/TDD equipment connected either directly or indirectly to the
10 Mobile Terminal (MT2) on the mobile station side of the connection. TE2 is TTY/TDD equipment
11 connected to the PSTN on the land side. Subscripts "M" and "L" are added as needed to indicate
12 mobile station side and land side TE2s, respectively. When combined in a single physical entity,
13 TE2 and MT2 functionality is labeled MT0.
14 b. Setup a mobile station originated TTY/TDD call.

15 c. Verify characters typed at TE2M can be viewed at TE2L. Verify characters typed at
16 TE2L can be viewed at TE2M. See aNNEX E: TTY/TDD Test Examples for Example
17 character text. See Annex E For Example character text.
18 d. Type a character sequence (“AB ”) repeatedly a minimum of 20 times at TE2L
19 e. Verify characters are properly viewed at TE2M.
20 f. Type a character sequence (“AB”) repeatedly a minimum of 20 times at TE2M
21 g. Verify characters are properly viewed at the TE2L.
22 h. Steps b through g may be repeated for all supported radio configurations.
23 i. Repeat steps c through h using mobile station terminated TTY/TDD calls.
24 j. Steps a through i may be repeated using all support baud rates.
9-18
C.S0044-0 v1.0
1 9.18.4.2 TTY/TDD File Transfer Operation

2 a. Setup the mobile station for TTY/TDD file transfer.
3 b. Transfer the ASCII/Baudot file from TE2M to TE2L.
4 c. Verify the PCER, CCER, and TCER is less than 1%.
5 d. Transfer the ASCII/Baudot file from TE2L to TE2M.
6 e. Verify the PCER, CCER, and TCER is less than 1%.
7 f. End the TTY/TDD call.
8 g. Steps a through f may be repeated for all supported radio configurations.
9 h. Repeat steps b through g for mobile station terminated calls.

10 i. Steps a through h may be repeated using all support baud rates.
11 9.18.4.3 Voice Carry Over (VCO) and Hearing Carry Over (HCO) Operation
12 a. Configure TE2M for VCO.

13 b. Setup a mobile station originated TTY/TDD call.
14 c. Verify outgoing messages can be spoken and incoming responses can be viewed.
15 d. End the TTY/TDD call.

16 e. Configure TE2M for HCO.
17 f. Setup a mobile station originated TTY/TDD call.
18 g. Verify outgoing messages can be typed and incoming responses can be heard through
19 a TE2M accessory speaker.
20 h. Verify characters typed at TE2M can be viewed at TE2L.
21 i. End the TTY/TDD call.
23 9.18.5.1 Basic TTY/TDD Operation

24 The mobile station shall comply with steps e and g for all tested and supported radio
25 configurations and baud rates for mobile station originated and terminated calls.
26 9.18.5.2 TTY/TDD Operation File Transfer

27 The mobile station shall comply with steps c and e for all tested and supported radio
28 configurations and baud rates for mobile station originated and terminated calls.
29 9.18.5.3 Voice Carry Over (VCO) and Hearing Carry Over (HCO) Operation
30 The mobile station shall comply with steps c, g and h.
9-19
C.S0044-0 v1.0
1 9.19 WLL Call Waiting Indicator Support
2 9.19.1 Definition
3 This test verifies that a mobile station in a two-way conversation, with call waiting enabled, will
4 receive indicator of waiting calls. This test will verify that the mobile station will send a flash
5 request to connect to the waiting call. This test case is applicable only if WLL is supported.

8 3.7.5.5 Signal

11 None

13 a. Ensure call waiting is enabled.
14 b. Make a mobile station to land party 1 voice call. Verify audio in both directions.
15 c. Setup a voice call from land party 2 to the mobile station.

16 d. Verify the base station sends a Flash With Information Message or Extended Flash
17 With Information Message with the Call Waiting Indicator Information Record as follows:
18 1. CALL_WAITING_INDICATOR field set to ’1’.

19 e. Press the hook (or FLASH button if available) in the mobile station to put land party 1
20 on hold and to connect to land party 2. Verify that the mobile station sends a Flash
21 With Information Message or an Extended Flash With Information Message to the base
22 station. Verify that no dial tone is generated in the mobile station.
23 f. Verify that voice path is established between the mobile station and land party 2.
24 g. Press the hook (or FLASH button if available) again in the mobile station to put land
25 party 2 on hold, and reconnect the voice path to land party 1.
26 h. Verify the mobile station sends a Flash With Information Message or Extended Flash
27 With Information Message to the base station.
28 i. Verify that voice path is established between the mobile station and land party 1.
29 j. End the call from land party 1.
30 k. Press hook (or FLASH button if available) again in the mobile station. Verify that the
31 mobile station sends a Flash With Information Message or Extended Flash With
32 Information Message to the base station.
33 l. Verify voice path is established between the mobile station and land party 2.
34 m. End the call to land party 2.
9-20
C.S0044-0 v1.0
1 n. Make a mobile station to land party 1 voice call. Verify audio path is established in both
2 directions.
3 o. Setup a voice call from land party 2 to the mobile station.
4 p. Verify the base station sends a Flash With Information Message or Extended Flash
6 CALL_WAITING_INDICATOR field set to ’1’.
7 q. Do not answer this call waiting call at the mobile station.
8 r. Disconnect call from land party 2.
9 s. Verify the base station sends a Flash With Information Message or Extended Flash
11 CALL_WAITING_INDICATOR field set to ’0’.
12 t. Press the hook (or FLASH button if available) of the mobile station and verify that a dial
13 tone is generated.
14 u. Press the hook (or FLASH button if available) again and verify that voice path between
15 the mobile station and land party 1 is established.
16 v. End the call to land party 1.

18 The mobile station shall comply with the requirements in the following steps: e, h, i, k, t and u.
19 The base station shall comply with the requirements in the following steps: d, f, j, i, p, s, t and u.
20 The base station shall send a Call Waiting Indicator to the mobile station during a two-way
21 conversation indicating another call is waiting. The mobile station shall be able to switch between
22 land party 1 and land party 2 by sending a flash request.
23 9.20 Answer Holding
25 These tests verify that the mobile station that supports Answer Holding feature can perform the
26 following:
27 a. Activate answer holding when the incoming call is ringing in the Waiting for Mobile
28 Station Answer Substate or in the Conversation Substate
29 b. Deactivate answer holding in the Conversation Substate

34 2.7.2.3.2.33 Extended Flash with Information Message
35 2.7.4.2 Keypad Facility
9-21
C.S0044-0 v1.0
1 3.6.8.1.2 Waiting for Answer Substate

3
MS BS
General Page
Message
Initiate a call
Page Response
Message
Extended Channel Assignment

Message
Service Connect
Message
Service Connect Completion

Message
AWI Message (ringing applied)
Instruct the MS to activiate

(Extended) Flash with Info (Keypad Facility Info
Answer Holding
Record)
Connect
Order
(Extended) Flash with Info (Keypad Facility Info

Instruct the MS to deactivate
Record)
Answer Holding
Conversation
FWI Message (Call Waiting)
Instruct the MS to activiate (Extended) Flash with Info (Keypad Facility Info
Answer Holding Record)
Instruct the MS to disconnect (Extended) Flash with Info (Keypad Facility Info
the first call and deactivate Record)
Answer Holding
Release Disconnect the call

Order
Release
Order
4
5

7 a. Power on the mobile station and wait until it reaches Idle State.
8 b. Setup a mobile station terminated call from land party 1.
9 c. When the mobile station is ringing and ring back tone is applied to the audio path,
10 instruct the mobile station to answer hold the call.
11 d. Verify the mobile station sends a Flash With Information Message or an Extended Flash
12 With Information Message in assured mode with a Keypad Facility information record
9-22
C.S0044-0 v1.0
1 with the CHARi field set to a pre-programmed feature code (i.e., Switch Control Code:
2 18*) which indicates Answer Holding.
3 e. Verify the mobile station sends a Connect Order in assured mode.
4 f. Instruct the mobile station to deactivate the answer holding.
5 g. Verify the mobile station sends a Flash With Information Message or an Extended Flash
8 18*) which indicates Answer Holding.

11 The mobile station shall comply with steps d, e, g and h.
12 9.21 User Selective Call Forwarding
14 These tests verify that the mobile station that supports User Selective Call Forwarding can
15 perform the following in both Waiting for Mobile Station Answer Substate and Conversation
16 Substate:
17 a. Forwarding incoming call to a pre-registered number

18 b. Forwarding incoming call to a number stored in the mobile station
19 c. Forwarding incoming call to network-based voice mail

24 2.7.2.3.2.33 Extended Flash with Information Message
25 2.7.4.2 Keypad Facility
26 3.6.8.1.2 Waiting for Answer Substate

28 None
30 9.21.4.1 User Selective Call Forwarding in the Waiting for Mobile Station Answer Substate
31 a. Power on the mobile station and wait until it reaches Idle State.
9-23
C.S0044-0 v1.0
1 b. Dial user selective call forwarding feature activation code, followed by the forward-to
2 number, followed by SEND. Verify feature update confirmation at the mobile station.
3 c. Setup a mobile station terminated call from land party.
4 d. When the mobile station is ringing and ring back tone is applied to the audio path,
5 instruct the mobile station to forward the incoming call to the pre-registered number.
6 e. Verify the mobile station sends a Flash With Information Message or an Extended Flash
9 0*), which indicates User Selective Call Forwarding to a pre-registered number.
10 f. Answer the call on the forwarded line, and verify the audio path.
11 g. End call.
12 h. Ensure the mobile station is in Idle State.
13 i. Setup a mobile station terminated call from land party.
14 j. When the mobile station is ringing and ring back tone is applied to the audio path,
15 instruct the mobile station to forward the incoming call to voice mail.
16 k. Verify the mobile station sends a Flash With Information Message or an Extended Flash
18 with the CHARi field set to a pre-programmed feature code (i.e. Switch Control Code:
19 17*) which indicates User Selective Call Forwarding to voice mail.
20 l. Verify the call is forwarded to voice mail.
21 m. Ensure the mobile station is in Idle State.

22 n. Program a forward-to-number in the mobile station.
23 o. Setup a mobile station terminated call from land party.
24 p. When the mobile station is ringing, and ring back tone is applied to the audio path,
25 instruct the mobile station to forward the incoming call to the number stored in the
26 mobile station.
27 q. Verify the mobile station sends a Flash With Information Message or an Extended Flash
30 16*) plus the forward-to-number stored in the mobile station.
31 r. Answer the call on the forwarded line, and verify the audio path.
32 9.21.4.2 User Selective Call Forwarding while in the Conversation Substate

33 a. Setup a call between mobile station and land party 1 and verify user data in both
34 directions.
35 b. Setup a call from land party 2 to the mobile station. Wait for ring back on land party 2
36 and the call waiting notification on the mobile station.
37 c. Instruct the mobile station to forward the incoming call to the pre-registered number.
9-24
C.S0044-0 v1.0
1 d. Verify the mobile station sends a Flash With Information Message or an Extended Flash
4 0*), which indicates User Selective Call Forwarding to a pre-registered number.
5 e. Answer the call on the forwarded line, and verify the audio path.
6 f. End call.
7 g. Setup a call between mobile station and land party 1 and verify user data in both
8 directions.
9 h. Setup a call from land party 2 to the mobile station. Wait for ring back on land party 2
11 i. Instruct the mobile station to forward the incoming call to voice mail.
12 j. Verify the mobile station sends a Flash With Information Message or an Extended Flash
15 17*) which indicates User Selective Call Forwarding to voice mail.
16 k. Verify the call is forwarded to voice mail.
17 l. End call.
18 m. Setup a call between mobile station and land party 1 and verify user data in both
19 directions.
20 n. Setup a call from land party 2 to the mobile station. Wait for ring back on land party 2
22 o. Instruct the mobile station to forward the incoming call to the forward-to-number stored
23 in the mobile station.
24 p. Verify the mobile station sends a Flash With Information Message or an Extended Flash
27 16*) plus the forward-to-number stored in the mobile station.
28 q. Answer the call on the forwarded line, and verify the audio path.
29 r. End call.
31 9.21.5.1 User Selective Call Forwarding in the Waiting for Mobile Station Answer Substate
32 The mobile station shall comply with steps e, k, and q.
33 9.21.5.2 User Selective Call Forwarding while in the Conversation Substate

34 The mobile station shall comply with steps d, j, and p.
35
9-25
C.S0044-0 v1.0
1 10 ASYNCHRONOUS DATA AND FAX SERVICES
2 10.1 Send/Receive Fax
3 10.1.1 Definition
4 These tests demonstrate cellular system ability to transmit and receive a medium size fax in a
5 timely manner. A fax call is originated by the mobile station and the test is then repeated using
6 land line origination. The mobile station will send and receive a digital and an analog Fax.

8 A.3 Data Service Options for Spread Spectrum Systems: AT Command Processing and the Rm
9 Interface
10 2.2 Data Service Selection
11 2.2.1 Service Selection for Async Data and Fax Services
12 4.0 AT COMMAND PROCESSING FOR ASYNC DATA AND FAX SERVICES

13 4.3 Service Class 2.0 AT Commands
14 7.3 Facsimile Service Class 2.0 AT Commands
15 A.4 Data Service Options for Spread Spectrum Systems: Async Data and Fax Services
16 2.2 The Application Interface
17 2.5.5 Requirements for Async Data and Fax
18 3.1 Service Option Number

19 3.2 Multiplex Option Interface
20 3.3 Procedures Using Service Option Negotiation
21 3.3.1.1 Mobile Station Requirements

22 3.4.1 Mobile Station Requirements
23 4.1.1 Mobile Origination
24 4.1.2 Mobile Termination
25 4.1.3 Service Option Change to Group-3 Facsimile Service
26 4.2 Connection Release
27 A.7 Data Service Options for Spread Spectrum Systems: Analog Fax Service

29 None
10-1
C.S0044-0 v1.0
2 10.1.4.1 Send/Receive Digital Fax

3 a. Prepare a file representing three different ITU standard fax pages for fax transfer. Data
4 Services Annex C lists standard fax pages to be used in the test. Ensure fax pages are
5 pre-scanned and pre-encoded.
6 b. Simultaneously start the transfer timer and the digital fax transfer from TE2M to TE2L.
7 c. At TE2L, wait for the fax call to be completed. Stop the transfer timer.
8 d. Record transfer time. Verify transfer time requirements per Data Services Annex C.
9 e. Repeat the test for the same fax sent from TE2L to TE2M. TE2M will receive a digital
10 fax.
11 f. Verify all faxes shall be successfully transferred. The received fax shall be of good
12 quality and complete. This can be verified by qualitative means (visually scanning the
13 received fax) or by quantitative means, for example, using ITU-T Recommendation
14 E.453 (08/94) Facsimile Image Quality as Corrupted by Transmission Induced Scan
15 Line Errors.
16 10.1.4.2 Send/Receive Analog Fax

17 a. Prepare a file representing three different ITU standard fax pages for fax transfer. Data
18 Services Annex C lists standard fax pages to be used in the test. Ensure fax pages are
19 pre-scanned and pre-encoded.
20 b. Attach an Analog Fax Machine to TE2M.
21 c. Simultaneously start the transfer timer and the analog fax transfer from TE2M to TE2L.
22 d. At TE2L, wait for the fax call to be completed. Stop the transfer timer.
23 e. Record transfer time. Verify transfer time requirements per Data Services Annex C.
24 f. Repeat test for the same fax sent from TE2L to TE2M. TE2M will receive an analog fax.
25 g. Verify all faxes shall be successfully transferred. The received fax shall be of good
26 quality and complete. This can be verified by qualitative means (visually scanning the
27 received fax) or by quantitative means, for example, using ITU-T Recommendation
28 E.453 (08/94) Facsimile Image Quality as Corrupted by Transmission Induced Scan
29 Line Errors.
30 h. Verify each analog fax transfer shall be completed within time denoted in Data Services
31 Annex C.
33 10.1.5.1 Send/Receive Digital Fax

10-2
C.S0044-0 v1.0
1 10.1.5.2 Send/Receive Analog Fax

2 The mobile station shall comply with steps e, g, and h.
3 10.2 Upload/Download Binary File
4 10.2.1 Definition
5 This test demonstrates cellular system ability to upload and download an ITU standard fax binary
6 file in a timely manner. The asynchronous data call is originated first by the mobile station. The
7 test is then repeated using land line origination.

9 A.3 Data Service Options for Spread Spectrum Systems: AT Command Processing and the Rm
10 Interface


29 None
31 a. Prepare the RAND200.BIN 200,000 byte binary file for transfer (Data Services Annex
32 D).
10-3
C.S0044-0 v1.0
1 b. Setup a data call from TE2M to TE2L.

2 c. Start transferring the binary file from TE2L to TE2M using Z-modem transfer protocol.
3 Start the transfer timer.
4 d. Stop the transfer timer when the confirmation of transfer completion is received from the
5 far end.
6 e. Record the transfer time.
7 1. Note: Transfer time should exclude call connection delay.
8 f. End the data call.
9 g. Setup a data call from TE2L to TE2M.
10 h. Repeat the test by transferring the file from TE2M to TE2L.
11 i. Verify:
12 1. All files shall be successfully transferred.
13 2. There shall be no Z-modem protocol re-transmissions.
14 3. Received files shall be complete and identical in content to the original file.
15 4. Each file transfer shall be completed within time denoted in Data Services Annex
16 D.
17 5. Both the mobile station originated, and land line originated data calls shall be
18 established successfully.

20 The mobile station shall comply with step i.
21 10.3 Simultaneous Two-way File Transfer/Carrier Detect
23 This test demonstrates cellular system ability to simultaneously transfer data in the forward and
24 reverse link direction. This test verifies the base station can transmit changes in the status of
25 Carrier Detect and reflect its status on the Rm interface.
26 Note: Carrier Detect can be monitored by means of a hardware lead, or observed on the
27 application interface.
29 A.3 Data Service Options for Spread Spectrum Systems: AT Command Processingand the Rm
30 Interface
10-4
C.S0044-0 v1.0





15 None
17 a. Prepare the RAND200.ASC 200,000 byte ASCII file for transfer (Data Services Annex
18 D).
19 b. Ensure the Carrier Detect indicator is enabled at TE2M.
20 c. From TE2M, issue the command “AT&C1”, which requests the real-time status of
21 Carrier Detect be maintained on the Rm interface.
22 d. Verify the Carrier Detect indicator is OFF.
23 e. Setup a data call from TE2M to TE2L. Verify that Carrier Detect indicator goes ON,
24 when the base station modem has successfully trained.
25 f. Verify characters typed at TE2M can be viewed at TE2L. Verify characters typed at
26 TE2L can be viewed at TE2M.
27 1. Note: Once the File Capture is turned on, do not type any more characters on
28 the TE2L or the TE2M prior to initiating the file transfer (this is to ensure the
29 captured file is not corrupted by user keystrokes).
30 g. Turn on the File Capture at TE2M.
31 h. Turn on the File Capture at TE2L.
32 i. Simultaneously start the reverse link transfer timer and at TE2M send the
33 RAND200.ASC file to TE2L by using Raw ASCII protocol.
10-5
C.S0044-0 v1.0
1 j. While TE2M is sending the file to TE2L, simultaneously start the forward link transfer
2 timer and instruct TE2L to send the same ASCII file to TE2M using a Raw ASCII
3 protocol.
4 1. Note: It is critical these transfers shall substantially overlap.
5 k. As each transfer completes, stop corresponding transfer timer and record transfer time.
6 l. After both transfers are complete, turn off the File Capture at both TE2M and TE2L.
7 m. End call.
8 n. At TE2M, verify that Carrier Detect indicator goes OFF when the call is ended.
9 o. Verify:
10 1. The file shall be successfully transferred in each direction.
11 2. Log files shall be complete and identical in content to the original files.
12 3. Each file transfer shall be completed within time denoted in Data Services Annex
13 D.
14 4. The Carrier Detect generated by the base station shall be accurately depicted on
15 the Rm interface.

17 The mobile station shall comply with steps d, e, f, n, and o.
18 10.4 Compound AT Command, Initialization and Connection Delay
20 This test verifies the base station can properly process a compound command line containing
21 both local and remote commands. This test verifies the mobile station can initialize and connect
22 the service option when the data call is negotiated with the base station, as well as measures
23 connection delay.
25 A.3 Data Service Options for Spread Spectrum Systems: AT Command Processing
26 and the Rm Interface
27 4.2.6 Basic Result Codes
28 Table 4.2.6-1. Result Code Sources
29 4.3.1.2.5 +FMI, +FMM, +FMR
30 4.4.1 General Requirements
31 Table 7.2-1 Extended AT Configuration Commands

32 Table 7.3.1-1 Fax Parameters
10-6
C.S0044-0 v1.0

2 None

4 a. Ensure the call is down.
5 b. At TE2M, issue AT command
6 “AT+CXT=1;+FCLASS=2.0;+GMI;+CGMI;+GMM;+CGMM”. This command string
7 requests mobile station manufacturer information, base station modem manufacturer
8 information, mobile station manufacturer model, and base station modem manufacturer
9 model.
10 c. Start the connection delay timer.
11 d. When the result is returned to the mobile station, stop the connection timer.
12 e. Record connection delay time in the test report.
13 f. Verify the response shall be correct in that it contains the information requested in the
14 command, and is followed by result code “OK”. Delay should not exceed ten seconds.

16 The mobile station shall comply with step f.
17 10.5 Escaping to Command Mode
19 This test verifies:
20 a. The MT2 application interface escapes to online command state when the user (or the
21 communications application) issues an escape sequence (such as "+++" with the
22 appropriate guard time).
23 b. The base station returns to online state when the user (or the application) issues the
24 command "ATO".

26 4.2.4 Call-Control Command Processing
27 4.4.2.1 Return to Online Command State

29 None

31 a. Setup a data call from TE2M to TE2L.
32 b. Verify characters typed at TE2M can be viewed at TE2L. Verify that characters typed at
10-7
C.S0044-0 v1.0
1 c. From TE2M issue the escape sequence +++.

2 d. Verify “OK” is returned, signifying that the MT2 is in the online command state.
3 e. At TE2M,issue the command “AT+CGMI" which requests base station manufacturer
4 information. Verify the response is appropriate, with trailing “OK”.
5 f. At TE2M, issue the command “ATO”, which should cause the MT2 to transition from
6 online command state to online state.
7 g. Verify characters typed at TE2M can be viewed at TE2L. Verify characters typed at
9 h. Verify the escape sequence shall cause entry into the online command state.
10 i. Verify the command “ATO” shall cause return from the online command state to online
11 state.

13 The mobile station shall comply with steps b, d, e, g, h, and i.
14 10.6 Air Interface Data Compression
16 This test verifies successful compression option negotiation and the transfer of compressible files
17 and/or faxes between the MT2 and Inter-Working Function (IWF). The aforementioned is verified
18 for both mobile station originated and mobile station terminated data and fax transmissions.
19 Note: Although the files are compressible, they will be compressed only when both the MT2
20 and IWF support the type of compression in question. Even if the MT2 or IWF do not support a
21 certain type of compression, the test in question may be performed to ensure MT2 and IWF still
22 interoperate correctly when the user requests this type of compression.
26 Table 7.4.1-1 CDMA AT Parameter Commands
29 Table 2.2-2 Compression Options
30 Table 2.2-3 Group 3 Fax Compression Options

32 None
10-8
C.S0044-0 v1.0

2 a. Prepare the data file, COMPFILE.RAW (see Data Services Annex A), or the fax page,
3 FAX 1 (see Data Services Annex C) for transfer.
4 b. Configure the test setup for transfer of a data file or a fax file per Table 10.6.4-1.
5 V.42bis compression for data file transfers is controlled by the +CDS command. The
6 type of compression for fax file transfers is controlled by the +CFC command. When
7 V.42bis is selected for fax transfer, the parameters set in the +CDS command are used.
8 c. Setup a mobile station originated fax or async data call per Table 10.6.4-1.
9 Table 10.6.4-1
Test File/Fax Compression Direction Compression Fax

No. Method of Transfer Enable Compression
Mode
1 Data File none BS to MS +CDS=0 N/A
2 Data File V.42bis BS to MS +CDS=2 N/A
3 Data File V.42bis MS to BS +CDS=1 N/A
4 Data File V.42bis MS to BS +CDS=3 N/A
5 Fax File none BS to MS N/A +CFC=0
6 Fax File V.42bis BS to MS +CDS=2 +CFC=1
7 Fax File V.42bis MS to BS +CDS=1 +CFC=1
8 Fax File V.42bis MS to BS +CDS=3 +CFC=1
9 Fax File MMR BS to MS N/A +CFC=2
10 Fax File MMR MS to BS N/A +CFC=2
10
11 d. Make a file or fax transfer in the direction as stated in Table 10.6.4-1. Time each
12 transfer and record in the test report.
13 e. Testing may be repeated for all test cases, 1 through 10.
14 f. Verify:
15 1. All faxes shall be successfully sent and received.

16 2. The received fax page shall be complete in content, and each transfer shall be
17 completed within the time stated in Data Services Annex C.
18 3. All data files shall be successfully transferred.
19 4. The received files shall be complete and identical in content to the original file.
20 Each file transfer shall be completed within the time stated in Data Services Annex
21 B.
10-9
C.S0044-0 v1.0

3 10.7 RLP Operation in a Poor RF Environment
4 10.7.1 Definition
5 This test exercises the Radio Link Protocol (RLP) layer's negative acknowledgments (NAKs), re-
6 transmits, RLP aborts, RLP Resets, and FCSs.
7 Test conditions are intended to impose one or more occurrences of the following.
8 a. Single, double, and triple NAK RLP retransmit events.
9 b. RLP Abort
10 c. RLP Reset
11 d. This test verifies that RLP recovers erased data frames in various channel conditions.
13 A.2 Data Service Options for Spread Spectrum Systems: Radio Link Protocol
14 3.1 Non-Transparent RLP Procedures
15 3.1.1.1 Non-Encrypted Mode Initialization/Reset
16 3.1.2 Data Transfer
17 3.1.4 Segmentation of Retransmitted Data Frames

19 None

21 a. Setup the mobile station and base station as shown in Figure A-9with an AWGN
22 generator placed in the forward link.
23 b. Environment Test Parameters
24 c. Adjust the level of the AWGN Generator so that the downlink frame error rate is
25 measured to be 3±1%.
26 d. Restore the RF link to a normal operating condition, maintaining the target frame error
27 rate (1 % or less).
28 e. Prepare RAND200.ASC 200,000 byte ASCII file for transfer (Data Services Annex D).
29 f. Setup a data call from TE2M to TE2L.
30 g. Verify characters typed at TE2M can be viewed at TE2L. Verify characters typed at
32 h. Turn File Capture on.
10-10
C.S0044-0 v1.0
1 i. Simultaneously start the forward link transfer timer and at TE2L send the
2 RAND200.ASC file to TE2M by using Raw ASCII protocol.
3 j. As soon as the file transfer has started (and is still in progress), set the channel
4 conditions as calibrated in step b. These channel conditions shall be maintained for the
5 duration of the file transfer.
6 k. Stop the transfer timer and record the transfer time.
7 l. Turn off the File Capture.
8 m. End call.
9 n. Setup a data call from TE2M to TE2L.
10 o. Repeat steps f and g.
11 p. Simultaneously start the reverse link transfer timer and at TE2M send the
13 q. Repeat steps i through l.
14 r. Verify:
15 1. The file shall be successfully transferred.

16 2. The log file shall be complete and identical in content to the original file.
17 3. The transfer rate shall be no less than 70% of rates measured in test 10.3.

19 The mobile station shall comply with steps f, q, and r.
20 10.8 RLP Abort and TCP Retransmit Test
22 This test causes the RLP layer to abort and reset due to extremely severe CDMA channel
23 conditions, and forces the TCP layer to retransmit packets. Channel degradation consists of
24 forcing consecutive frame erasures for periods greater than 2.6 seconds.
25 Note: 2.6 seconds corresponds to 130 consecutive frame erasures, but less than the time that
26 would cause the call to drop (typically 5 seconds).

28 A.2 Data Service Options for Spread Spectrum Systems: Radio Link Protocol
29 3.1 Non-Transparent RLP Procedures
30 3.1.1.1 Non-Encrypted Mode Initialization/Reset

31 3.1.2 Data Transfer
32 3.1.4 Segmentation of Retransmitted Data Frames
10-11
C.S0044-0 v1.0

2 None

4 a. Setup the mobile station and base station as shown in Figures Annex A Figure A-7 and
5 Annex A Figure A-8 for the forward and the reverse link tests respectively, with
6 PWR_THRESH_ENABLE and PWR_PERIOD_ENABLE set to 0. Disable forward link
7 power control at the base station.
8 b. Calibrate the test setup so that:
9 c. There is sufficient isolation with the switch open, that a call drops if the switch is left
10 open for more than 5 seconds
11 d. When switch is open, the forward and reverse links are disabled at the receiver.
12 e. When switch is closed, the forward and reverse links are enabled at the receiver.
13 f. Set the RF link to normal operating condition, which maintains the target frame erasure
14 rate (1% or less).
15 g. Prepare the RAND200.ASC 200,000 byte ASCII file transfer (Data Services Annex D)
16 h. Setup a call from TE2M to TE2L.
17 i. Verify characters typed at TE2M can be viewed at TE2L. Verify that characters typed at
19 j. Turn File Capture on.
20 k. Simultaneously start the forward link transfer timer and at TE2L send the
21 RAND200.ASC file to TE2M by using Raw ASCII protocol.
22 l. Once the file transfer has started (and is still in progress), open and close the switch in
23 an alternating fashion, for periods of T1 and T2 where:
24 1. T1 is the period when the switch is open (RF link impaired), and it is anywhere
25 between 2.6 and 5.0 seconds.
26 2. T2 is the period when the switch is closed (RF link restored), and it is a minimum
27 of 10 seconds.
28 m. Repeat opening and closing switch exactly three times while data transfer is occurring.
29 n. Stop the transfer timer and record the transfer time.
30 o. Turn the File Capture off.
31 p. End call.
32 q. Setup a data call from TE2M to TE2L.

33 r. Repeat steps f and g.
34 s. Simultaneously start the reverse link transfer timer and at TE2M send the
10-12
C.S0044-0 v1.0
1 t. Repeat steps i through l.

2 u. Verify:
3 1. The file shall be successfully transferred in each direction.
4 2. Log files shall be complete and identical in content to the original files.
5 3. Transfer rates shall be no less than 50% of rates measured in test 10.3.

7 The mobile station shall comply with steps i and u.
8 10.9 Internet Control Message Protocol (ICMP) Requests/Replies
9 10.9.1 Definition
10 This test verifies the mobile station is able to:
11 a. Generate an ICMP Echo Response Message after receiving an Echo Request
12 Message.
13 b. Generate an ICMP Info Response Message after receiving an Info Request Message.
14 c. Generate an ICMP Time Stamp Response Message after receiving a Time Stamp
15 Request Message.

17 RFC-792 Internet Control Message Protocol

19 None
21 a. At TE2M, issue a remote query command such as “AT+CXT=1;+FCLASS=2.0;+FMI?”,

22 requesting base station modem manufacturer information. This will establish a link to
24 b. From the OA&M interface of the base station, issue the Echo Request Message by any
25 method specific to the base station manufacturer.
26 c. Optionally, step b may be repeated for Info Request/Response, or Time Stamp
27 Request/Response Messages.
28 d. Verify:
29 1. Echo response shall be received by base station as a response to Echo Request
30 Message.
31 2. If supported by mobile station, an Info response shall be received by base station
32 as a response to Info Request Message.
10-13
C.S0044-0 v1.0
1 3. If supported by mobile station, a Time stamp response shall be received by base

2 station as a response to Time Stamp Request Message.

5 10.10 Reflection of AT Command Parameters
7 This test verifies a representative set of AT parameters can be setup in an IS-707-A call,
8 transferred to the base station at call origination, changed in the online command state, and have
9 their final values read at the mobile station after call completion. Commands tested are ATS10
10 and AT+CQD.
14 4.2.4 Call-Control Command Processing
15 7.4.1 CDMA AT Parameters

17 None

19 a. Issue the following AT commands: ATS10=255 and AT+CQD=0”
20 b. Verify response is “OK”
21 c. Setup a data call from TE2M to TE2L.

22 d. After CONNECT is received, issue the escape sequence (such as ”+++”).
23 e. Verify the response is “OK”
24 f. Issue the following AT commands: ATS10?and AT+CQD?.
25 g. Verify response is:
26 1. 255
27 2. +CQD:0
28 3. OK
29 h. Issue the following AT commands : “ATS10=250 and AT+CQD=100”
30 i. Verify the response is “OK”

31 j. Issue the following AT commands : ATS10?and AT+CQD?.
32 k. Verify the response is:
10-14
C.S0044-0 v1.0
1 1. 250
2 2. +CQD:100
3 3. OK
4 l. Terminate the call via the “ATH0” command string.
5 m. Verify the response is “OK” and that the call ends.
6 n. Issue the following AT commands: ATS10?and AT+CQD
7 o. Verify response is:
8 1. 250
9 2. +CQD:100
10 3. OK
11 p. Verify the “ERROR” response shall not be returned.

13 The mobile station shall comply with steps b, e, g, i, k, m, o, and p.
10-15
C.S0044-0 v1.0
1 11 LOW SPEED PACKET DATA
2 11.1 Forward File Transfer
3 11.1.1 Definition
4 This test verifies that file transfer from remote host to mobile station can be successfully done
5 using the LSPD call.
7 1.4.2.2 Mobile Station Packet Data Service States

8 2.2.2 Service and Call Control Procedures
9 2.2.3 Initialization and Connection of Packet Data Service Options

11 None

14 b. At the remote host prepare the RAND200.BIN 200,000 byte binary file for transfer (Data
15 Services Annex D).
16 c. Setup an FTP session using Service Option 7 for Rate Set 1 or Service Option 15 for
17 Rate Set 2 with the remote host.
18 d. Transfer the file from the remote host to the TE2M using the binary “get” command.
19 e. After the file transfer is completed, end the FTP session. Verify the file is successfully
20 transferred.
21 f. Steps b through e may be repeated for other data rates supported by both mobile
22 station and base station.

25 11.2 Reverse File Transfer
27 This test verifies that file transfer from mobile station to remote host can be successfully done
28 using the LSPD call.

11-1
C.S0044-0 v1.0

3 None

6 b. At the TE2M, prepare the RAND200.BIN 200,000 byte binary file for transfer (Data
7 Services Annex D).
10 d. Transfer the file from the TE2M to the remote host using the binary “put” command.
11 e. After the file transfer is completed, end the FTP session. Verify the file is successfully
12 transferred.
13 f. Steps b through e may be repeated for other data rates supported by both mobile
14 station and base station.

17 11.3 Bi-directional File Transfer
19 This test verifies that bi-directional file transfer can be successfully done using the LSPD call.


25 None

28 b. Prepare the RAND200.BIN 200,000 byte binary file for transfer (Data Services Annex
29 D) at both the remote host and TE2M.
32 d. Transfer the file from the TE2M to the remote host.
11-2
C.S0044-0 v1.0
1 e. Transfer the file from the Remote Host to the TE2M while the transfer in the reverse
2 direction is still proceeding.
3 f. After the file transfers are completed, end the FTP sessions. Verify the files are
4 successfully transferred.
5 g. Steps b through f may be repeated for different data rates that are supported by both
6 mobile station and base station.

9 11.4 Mobile Station Packet Data Inactivity Timer
11 This test is required for mobile stations that shall have a mobile station packet data inactivity
12 timer. This test verifies the mobile station releases the traffic channel after expiration of the
13 mobile station packet data inactivity timer. The test verifies the dormant link layer connection can
14 be re-activated.

17 None

19 a. Set the packet data inactivity timer at the MT2 to 20 seconds.
20 b. Ensure the base station packet data inactivity timer is disabled or set to a value of at
21 least 30 seconds.
22 c. Initiate a Telnet session to a remote host.
23 d. Record the IP address assigned to the mobile station.
24 e. Exit the Telnet session.

25 f. Wait for the mobile station packet data inactivity timer to expire. Verify the “in use”
26 indicator on the MT2 goes OFF.
27 g. Initiate a Telnet session to a remote host.
28 h. Record the IP address assigned to the mobile station.
29 i. Wait for the mobile station packet data inactivity timer to expire. Verify the “in use”
31 j. Issue a “ping” command from the remote host to the mobile station using the IP address
32 assigned to the mobile station.

34 The mobile station shall comply with steps f and i.
11-3
C.S0044-0 v1.0
1 12 MEDIUM SPEED PACKET DATA
2 12.1 Forward File Transfer with Fundamental and Supplemental Code Channels
3 12.1.1 Definition
4 This test verifies the functionality of forward MSPD calls for various MUX options:
5 • No Supplemental Code Channels allocated (Test 1).
6 • One Supplemental Code Channel allocated (Test 2).
7 • N Supplemental Code Channels allocated, where N is the maximum number of
8 Supplemental Code Channels that can be supported by the system (Test 3).
9 12.1.2 Traceability:
10 [2] 2.2.1.1.1 The Multiplex Sublayer
11 [4] 3.6.6.2.2.9 Processing the Supplemental Channel Assignment Message
12 [4] 3.6.6.2.2.10 Processing the General Handoff Direction Message
13 [15] A-9; 2.2.2.1.1 Packet Data Service Control Procedures

15 None

17 a. Prepare a file at the remote host for file transfer (see Annex D).
18 b. Setup an FTP session using Service Option 22 with the remote host. From the base
19 station, generate a General Handoff Direction Message or a Supplemental Channel
20 Assignment Message to allocate Supplemental Code Channels to the mobile station
21 according to the following conditions:
22 1) For Test 1, the base station shall allocate no Supplemental Code
23 Channel to the mobile station (i.e. MUX Option = 1).
24 2) For Test 2, the base station shall allocate one Supplemental Code
25 Channel to the mobile station (i.e. MUX Option = 3).
26 3) For Test 3, the base station shall allocate N Supplemental Code
27 Channels to the mobile station (i.e. MUX Option = 2N+1).
28 c. Transfer the file from the remote host to the TE2M using the binary “get” command.
29 d. Verify the file is successfully transferred.
30 e. After the file transfer is completed, end the FTP session

31 f. Repeat steps b through e for Tests 2 and 3.
32 g. Repeat steps b through f for Tests 1, 2, and 3 with Service Option 25.
12-1
C.S0044-0 v1.0

2 Verify step d for all test cases.
3 12.2 Forward File Transfer with Variable Supplemental Code Channels
4 12.2.1 Definition
5 This test verifies the capability to transfer files from a remote host using FTP, with a variable
6 number of Supplemental Code Channels. This test is intended to exercise bursty data transfer
7 with variable peak transfer rates.
8 This test may require the use of an OA&M interface on the base station, or any other method
9 specific to the base station manufacturer, in order to vary the number of allocated Supplemental
10 Code Channels.
15 [15] A-9; 2.2.2.1.1 Packet Data Service Control Procedures

17 None

19 a. Prepare a file at the remote host for file transfer (see Annex D).
20 b. Configure the mobile station’s maximum forward Supplemental Code Channels to N.
21 c. Configure the base station to support N Supplemental Code Channels.
22 d. Setup a mobile station terminated call with Service Option 22, and establish an FTP
23 session.
24 e. From the base station, generate a General Handoff Direction Message to allocate N
25 Supplemental Code Channels to the mobile station.
26 f. Verify from the mobile station that N Supplemental Code Channels are being used.
27 g. Transfer the file from the remote host to TE2M using the binary “get” command.
28 h. During through the file transfer, configure the base station to generate a General
29 Handoff Direction Message or a Supplemental Channel Assignment Message to reduce
30 the number of Supplemental Code Channels allocated to the mobile station.
31 i. Verify the file is successfully transferred.
32 j. End FTP session.
33 k. Repeat steps d through j with Service Option 25.
12-2
C.S0044-0 v1.0

2 Verify steps f and i for all test cases.
3 12.3 MSPD Call Setup, No Negotiation
4 12.3.1 Definition
5 This test verifies that the base station and the mobile station can successfully establish mobile
6 station-originated and mobile station-terminated calls using all combinations of supported Service
7 Option 22 and Service Option 25, using the default multiplex options.
9 [15]-A9; 2.2.2.1.2.5 Dormant/Idle State

12 None

14 a. Prepare a file at both the remote host and the TE2M (see Annex D).
15 b. Configure the mobile station’s forward MUX Option to (2N+1) where N is the maximum
16 number of Supplemental Code Channels.
17 c. Configure the base station’s MUX Option to a value equal to (2N+1).
18 d. Setup a mobile station originated call with Service Option 22, and establish an FTP
19 session with the remote host.
20 e. Verify the call is completed with Service Option 22.
21 f. Verify that N Supplemental Code Channels are being used by the mobile station.
22 g. Transfer the file from remote host to TE2M using the binary “get” command and verify the
23 file is successfully transferred.
24 h. After the file transfer is completed in step f, transfer the file from the TE2M to the remote
25 host using the binary “put” command and verify the file is successfully transferred.
26 i. End FTP session.
27 j. Repeat steps d through i by initiating a mobile station terminated call with Service Option
28 22.
29 k. Configure the base station’s MUX Option to a value equal to (2N+2).
30 l. Setup a mobile station originated call with Service Option 25, and establish an FTP
32 m. Verify the call is completed with Service Option 25.
33 n. Verify that N Supplemental Code Channels are being used by the mobile station.
12-3
C.S0044-0 v1.0
1 o. Transfer the file from remote host to TE2M using the binary “get” command and verify the
2 file is successfully transferred.
3 p. After the file transfer is completed in step o, transfer the file from the TE2M to the remote
5 q. End the FTP session.
6 r. Repeat steps l through q by initiating a mobile station terminated call with Service Option
7 25.

9 The mobile station shall comply with steps e, f, g, h, m, n, o and p.
10 12.4 MSPD Call Setup, Negotiation to a Different MSPD Service Option
12 This test verifies that the base station and the mobile station can successfully negotiate from
13 Service Option 22 to Service Option 25, and vice versa.

18 None
21 b. Configure the mobile station’s forward MUX Option to the default MUX Option.
22 c. Configure the base station’s Service Option to 25 and configure the base station’s MUX
23 Option to a value equal to or greater than the mobile station’s MUX Option number.
24 d. Setup a mobile station originated call using Service Option 22, and establish an FTP
26 e. Verify the call is negotiated to Service Option 25.

27 f. Transfer the file from the remote host to TE2M using the binary “get” command and verify
28 the file is successfully transferred.
29 g. After the file transfer is completed in step f, transfer the file from the TE2M to the remote
31 h. End FTP session.
32 i. Configure the base station’s Service Option to 22.
12-4
C.S0044-0 v1.0
1 j. Setup a mobile station originated call using Service Option 25 and establish an FTP
3 k. Verify the call is negotiated to Service Option 22.
4 l. Transfer the file from the remote host to TE2M using the binary “get” command and verify
6 m. After the file transfer is completed in step l, transfer the file from the TE2M to the remote
8 n. End FTP session.

10 The mobile station shall comply with steps e, f, g, k, l and m.
11 12.5 MSPD Call Setup, Negotiation to LSPD
13 This test verifies that the base station and the mobile station can successfully negotiate from
14 MSPD to LSPD service options.


19 None
21 12.5.4.1 MSPD-Capable Mobile station

23 b. Configure the base station to Service Option 7.

24 c. Setup a mobile station originated call with Service Option 22, and establish an FTP
26 d. Verify the call is completed with Service Option 7.
27 e. Successively transfer files both directions and verify the files are successfully transferred.
28 f. End FTP session.
29 g. Configure the base station to Service Option 15.
30 h. Setup a mobile station originated call with Service Option 22, and establish an FTP
32 i. Verify the call is completed with Service Option 15.
12-5
C.S0044-0 v1.0
1 j. Successively transfer files in both directions and verify the files are successfully
2 transferred.
3 k. End FTP session.
4 l. Configure the base station to Service Option 15.
5 m. Setup a mobile station originated call with Service Option 25, and establish an FTP
7 n. Verify the call is completed with Service Option 15.
8 o. Successively transfer files in both directions and verify the files are successfully
9 transferred.
10 p. End FTP session.
11 q. Configure the base station to Service Option 7
12 r. Setup a mobile station originated call with Service Option 25, and establish an FTP
14 s. Verify the call is completed with Service Option 7.
15 t. Successively transfer files in both directions and verify the files are successfully
16 transferred.
17 u. End FTP session.
18 12.5.4.2 Non MSPD-Capable Mobile station

19 a. Ensure the mobile station is not MDR capable.
20 b. Prepare a file at both the remote host and the TE2M.
21 c. Configure the mobile station with Service Option 15. This can be accomplished by issuing
22 the AT command AT+CMUX=2,2.
23 d. Configure the base station to page the mobile station with Service Option 22.
24 e. Set up a mobile station terminated call and establish an FTP session.
25 f. Verify the call is completed with Service Option 15.
26 g. Successively transfer files in both directions and verify the files are successfully
27 transferred.
29 i. Configure the base station Service Option to 25.
30 j. Set up a mobile station terminated call and establish an FTP session.
31 k. Verify the call is completed with Service Option 15.
32 l. Successively transfer files in both directions and verify the files are successfully
33 transferred.
34 m. End FTP session.
12-6
C.S0044-0 v1.0

2 In section 12.5.3.1, the mobile station shall comply with steps d, e, i, j, n, o, s and t.
3 In section 12.5.3.2, the mobile station shall comply with steps f, g, k and l.
4 12.6 MSPD Call Setup, Mobile Station Maximum Multiplex Option Less than Base Station
5 Maximum Multiplex Option
6 12.6.1 Definition
7 This test verifies that an MSPD call can be successfully established when the maximum multiplex
8 option supported by the mobile station is less than the maximum multiplex option supported by
9 the base station.
12 [15]-A3; 7.4.1 CDMA AT Parameters

15 None

18 b. Configure the mobile station’s maximum forward MUX Option to (2n+1) where n is equal
19 to N or 6, whichever is smaller, where N is the maximum number of Supplemental Code
20 Channels supported by the mobile station (i.e. set AT+CMUX=2n+1,1)
21 c. Configure the base station’s MUX Option to a value equal to (2(n+1)+1).
23 session.
24 e. Verify the number of Supplemental Code Channels used to establish FTP session is n.
28 host using the binary “put” command verify the file is successfully transferred.
30 i. Repeat steps d through h with Service Option 25 by setting the maximum forward MUX
31 Option of the mobile station to (2n+2) and the MUX Option of the base station to
32 (2(n+1)+2).

34 The mobile station shall comply with steps e, f and g for all test cases.
12-7
C.S0044-0 v1.0
1 12.7 MSPD Call Setup, Mobile station Maximum Multiplex Option Greater than Base
2 Station Maximum Multiplex Option
3 12.7.1 Definition
4 This test verifies that an MSPD call can be successfully established when the maximum multiplex
5 option supported by the mobile station is greater than the maximum multiplex option supported by
6 the base station.

12 None

15 b. Configure the mobile station’s maximum forward MUX Option to (2N+1) where N is the
16 maximum number of Supplemental Code Channels supported by the mobile station (i.e.
17 set AT+CMUX=2N+1,1)
18 c. Configure the base station’s MUX Option to a value equal to (2(N-1)+1).
20 session.
21 e. Verify the number of Supplemental Code Channels used in establishing the FTP session
22 is (N-1).
28 i. Repeat steps d through h with Service Option 25 by setting the maximum forward MUX
29 Option of the mobile station to (2N+2) and MUX Option of the base station to (2(N-1)+2).

31 The mobile station shall comply with steps e, f and g for all test cases.
12-8
C.S0044-0 v1.0
1 12.8 Allocation/De-allocation of Supplemental Code Channels
2 12.8.1 Definition
3 This test verifies allocation and de-allocation of up to N Supplemental Code Channels using the
4 General Handoff Direction Message (GHDM), and Supplemental Code Channel Assignment
5 Message (SCAM). N is the maximum number of forward Supplemental Code Channels that can
6 be supported by the system. The first test uses n Supplemental Code Channels, where n is any
7 number greater than zero and less than the maximum N. The second test uses the maximum N
8 Supplemental Code Channels. This test also exercises all supported values of the
9 FOR_SUP_CONFIG and USE_FOR_DURATION fields.
14 [15]-A9; 2.2.2.1.1 Packet Data Service Control Procedures

16 None
18 12.8.4.1 Allocation and De-Allocation of n Supplemental Code Channels using GHDM

19 a. Prepare a file at the remote host (see Annex D).
23 c. Setup a mobile station terminated call with Service Option 22, and establish an FTP
24 session.
25 d. Verify only the forward Fundamental Code Channel is used in establishing the FTP
26 session.
27 e. Configure the base station to send a General Handoff Direction Message with
28 FOR_INCLUDED=1, FOR_SUP_CONFIG=3, USE_FOR_DURATION=0 and assign n
29 forward Supplemental Code Channels (where n < N and n > 0) to the mobile station.
30 f. Verify that n Supplemental Code Channels are being used by the mobile station.
31 g. Transfer the file from the remote host to TE2M using the binary “get” command and verify
33 h. Configure the base station to send a General Handoff Direction Message with
34 FOR_INCLUDED=1, FOR_SUP_CONFIG=3, USE_FOR_DURATION=0 and assign 0
35 forward Supplemental Code Channels to the mobile station.
36 i. Verify that no Supplemental Code Channel is used by the mobile station.
12-9
C.S0044-0 v1.0
1 j. Transfer the file from the remote host to TE2M using the binary “get” command and verify
4 l. Repeat steps c through k using Service Option 25.
5 12.8.4.2 Allocation and De-Allocation of N Supplemental Code Channels using SCAM

6 a. Prepare the RAND200.BIN byte binary file at the remote host.
11 session.
12 d. Verify that only the forward Fundamental Code Channel is used in establishing the FTP
13 session.
14 e. Configure the base station to send a Supplemental Code Channel Assignment Message
15 with FOR_INCLUDED=1, FOR_SUP_CONFIG=3, USE_FOR_DURATION=0,
16 USE_FOR_HDM_SEQ=0 and assign N forward Supplemental Code Channels to the
17 mobile station.
18 f. Verify that N Supplemental Code Channels are used by the mobile station.
19 g. Transfer the file from the remote host to TE2M using the binary “get” command and verify
21 h. Configure the base station to send a Supplemental Code Channel Assignment Message
22 with FOR_INCLUDED=1, FOR_SUP_CONFIG=3, USE_FOR_DURATION=0,
23 USE_FOR_HDM_SEQ=0 and assign 0 forward Supplemental Code Channels to the
24 mobile station.
25 i. Verify the number of Supplemental Code Channels used by the mobile station.
26 j. Transfer the file from the remote host to TE2M using the binary “get” command and verify
29 l. Repeat steps c through k using Service Option 25.

31 For section 12.8.3.1, the mobile station shall comply with steps d, f, g, I, j and l.
32 For section 12.8.3.2, the mobile station shall comply with steps d, f, g, I, j and l.
12-10
C.S0044-0 v1.0
1 12.9 No Transmission on Supplemental Code Channels
2 12.9.1 Definition
3 This test verifies that data transfer is not interrupted if the base station stops transmitting on one
4 or more allocated Supplemental Code Channels. Note that if the base station does not allow a
5 Supplemental Code Channel to remain idle when there is no data to be transmitted on the
6 Supplemental Code Channel, this test may require the use of an OA&M interface on the base
7 station or some other method specific to the base-station manufacturer.

14 None

17 b. Configure the mobile station’s maximum forward MUX Option to 5 or greater.
19 session.
20 d. Configure the base station to send a General Handoff Direction Message or a
21 Supplemental Code Channel Assignment Message with FOR_INCLUDED=1,
22 FOR_SUP_CONFIG=3, USE_FOR_DURATION=0, USE_FOR_HDM_SEQ=0 and assign
23 2 forward Supplemental Code Channels to the mobile station.
24 e. Verify the MUX Option used in establishing the FTP session.

27 g. Configure the base station to send data on the Fundamental Code Channel only while
28 the 2 Supplemental Code Channels are still active.
29 h. Transfer the file from the remote host to TE2M using the binary “get” command and verify
31 i. End FTP session.
32 j. Repeat steps c through i with Service Option 25.
33

35 The mobile station shall comply with steps e, f and h for all test cases.
12-11
C.S0044-0 v1.0
1 12.10 Soft Handoff with Supplemental Code Channels
3 This test verifies that the fundamental and Supplemental Code Channels can be put in two-way
4 soft handoff during an MSPD call with N Supplemental Code Channels active, where N is the
5 maximum number of Forward Supplemental Code Channels that can be supported by the
6 system. This test includes the following cases:
7 Fundamental Code Channel and Supplemental Code Channels in handoff, two cells transmit
8 Supplemental Code Channels.
9 Fundamental Code Channel in handoff, only one cell transmits Supplemental Code Channels.
13 [4] 3.6.6.2.4 Soft Handoff

16 None

20 maximum number of forward Supplemental Code Channels available for the mobile
21 station.
22 c. Configure each base station to support N Supplemental Code Channels.
24 session with base station 1.
25 e. Configure the base station to set up N Forward Supplemental Code Channels in traffic
26 state.
27 f. Begin transferring the file from the remote host to TE2M using the binary “get” command.
28 g. While the file is being transferred, adjust the signal strength of base station 2 until both
29 base stations have equal transmit power.
30 h. Generate a General Handoff Direction Message for two-way soft-handoff with base
31 station 2. In both test cases 1 and 2, generate the GHDM with FOR_INCLUDED=1,
32 FOR_SUP_CONFIG=3, NUM_FOR_SUP=N, and USE_FOR_DURATION=0.
33 i. For Test 1: In the GHDM, set the FOR_SUP_INCLUDED=1 for each pilot to be included
34 in handoff and configure both base stations to send data on all Supplemental Code
35 Channels.
36 j. For Test 2: In the GHDM, set the FOR_SUP_INCLUDED=1 for base station 1 and
37 FOR_SUP_INCLUDED=0 for base station 2. Configure base station 1 to transmit data on
12-12
C.S0044-0 v1.0
1 all Supplemental Code Channels. Configure base station 2 to transmit data on the
2 Fundamental Code Channel only.
3 k. Verify the file transfer continues after the handoff and data is successfully transferred.
4 l. End FTP session.
5 m. Repeat steps d through l with Service Option 25.

7 The mobile station shall comply with step k for all test cases.
8 12.11 Adding Supplemental Code Channels during Soft Handoff
10 This test verifies that N Supplemental Code Channels can be added in an MSPD call while in
11 two-way soft handoff on the Fundamental Code Channel, where N is the maximum number of
12 Supplemental Code Channels that can be supported by the system. This test includes the
13 following cases:
14 • N Supplemental Code Channels added on all cells.
15 • N Supplemental Code Channels added on one cell only.
19 [4] 3.6.6.2.4 Soft Handoff


22 None


26 c. Configure each base station to support N Supplemental Code Channels.
28 session with base station 1 on the Fundamental Code Channel only.
29 e. Adjust the signal strength of base station 2 until both base stations have equal transmit
30 power.
31 f. Verify the mobile station is in two-way handoff.
32 g. Begin transferring the file from the remote host to TE2M using the binary “get” command.
12-13
C.S0044-0 v1.0
1 h. Generate a General Handoff Direction Message or a Supplemental Channel Assignment

2 Message with FOR_INCLUDED=1, FOR_SUP_CONFIG=3, NUM_FOR_SUP=N, and
3 USE_FOR_DURATION=0.
4 i. For Test Case 1: In the GHDM, set the FOR_SUP_INCLUDED=1 for each pilot to be
5 included in handoff and configure both base stations to send data on all Supplemental
6 Code Channels.
7 j. For Test Case 2: In the GHDM, set the FOR_SUP_INCLUDED=1 for base station 1 and
8 FOR_SUP_INCLUDED=0 for base station 2. Configure base station 1 to transmit data on
9 all Supplemental Code Channels. Configure base station 2 to transmit data on the
10 Fundamental Code Channel only.
11 k. Verify the file transfer continues after Supplemental Code Channel assignment during
12 handoff and the file is transferred successfully.

16 The mobile station shall comply with steps f and k for all test cases.
17 12.12 Hard Handoff to an MSPD-Capable System
19 This test verifies hard handoff within the same P_REV system as well as hard handoff to a higher
20 P_REV system.
24 [4] 3.6.6.2.4 Soft Handoff

27 None
29 12.12.4.1 Hard Handoff to Same P_REV

31 b. Make sure the MOB_P_REV=4 or higher.
32 c. Base station 1 should be configured for P_REV=5 or higher.
12-14
C.S0044-0 v1.0
1 d. Base station 2 should be configured for P_REV=5 or higher with a different frequency
2 channel from base station 1.
3 e. Configure the mobile station’s maximum forward Supplemental Code Channels to N.
4 f. Configure both base stations to support N Supplemental Code Channels.
5 g. Setup a mobile station terminated call with Service Option 22 and establish an FTP
6 session with base station 1 with N Supplemental Code Channels.
7 h. Begin transferring the file from the remote host to TE2M using the binary “get” command.
8 i. While the file is being transferred, adjust the signal strength of base station 2 until both
10 j. At base station 1, setup a hard handoff to base station 2 using the Extended Handoff
11 Direction Message.
12 k. Verify the hard handoff is successful and that only the Fundamental Channel is active.
13 l. Verify that base station 2 generates a General Handoff Direction Message or a
14 Supplemental Channel Assignment Message to assign N Supplemental Code Channels
15 to the mobile station.
16 m. Verify at the base station that service negotiation is successful and that the mobile station
17 is using Service Option 22 with N Supplemental Code Channels.
18 n. Verify the file transfer continues after the hard handoff and the file is transferred
19 successfully.
20 o. End FTP session.
21 p. Repeat steps g through o with Service Option 25.
22 12.12.4.2 Hard Handoff to Higher P_REV

24 b. Make sure the MOB_P_REV=4 or higher.

25 c. Base station 1 should be configured for P_REV=3.
26 d. Base station 2 should be configured for P_REV=5 or higher with a different frequency
27 channel from base station 1.
28 e. Configure the mobile station’s maximum forward Supplemental Code Channels to N.
29 f. Configure base station 2 to support N Supplemental Code Channels.
30 g. Setup a mobile station terminated call with Service Option 7 and establish an FTP
31 session with base station 1
32 h. Verify that Service Option 7 is in use and only the Fundamental Code Channel is active.
33 i. Begin transferring the file from the remote host to TE2M using the binary “get” command.
34 j. While the file is being transferred, adjust the signal strength of base station 2 until both
12-15
C.S0044-0 v1.0
1 k. At base station 1, setup a hard handoff to base station 2 using the Extended Handoff
2 Direction Message.
3 l. Verify the hard handoff is successful.
4 m. Verify at the mobile station that Service Option 7 is still in use.
5 n. Verify the file transfer continues after the hard handoff and the file is transferred
6 successfully.
8 p. Repeat steps g through n with Service Option 15.

10 For section 12.12.3.1, the mobile station and the base station shall comply with steps k, l, m, n
11 and p.
12 For section 12.12.3.2, the mobile station and the base station shall comply with steps h, l, m, n
13 and p.
14 12.13 Bi-Directional File Transfers with Forward Supplemental Code Channels
16 This test verifies the capability to transfer files simultaneously on the Forward and Reverse Traffic
17 Channels between the mobile station and remote host using FTP, with forward Supplemental
18 Code Channels active.
22 [4] 3.6.6.2.4 Soft Handoff


25 None


30 d. Setup a mobile station terminated call with Service Option 22.
31 e. Establish two FTP sessions with the base station; one for the forward link and one for the
32 reverse link.
12-16
C.S0044-0 v1.0
1 f. From the base station, generate a General Handoff Direction Message or a Supplemental
2 Channel Assignment Message to allocate N Supplemental Code Channels to the mobile
3 station.
4 g. Verify from the mobile station that N forward Supplemental Code Channels are being
5 used. The reverse link should be connected with the Fundamental Code Channel only.
6 h. Begin transferring the file from the remote host to TE2M using the binary “get” command.
7 i. While the file is being transferred on the forward link, begin transferring another file from
8 TE2M to the remote host on the reverse link using the binary “put” command.
9 j. Verify that both files are transferred successfully.

10 k. End two FTP sessions.
11 l. Repeat steps d through l with Service Option 25.

13 The mobile station and the base station shall comply with steps g and j for all test cases.
14 12.14 Rм Interface Flow Control
16 This test verifies flow control on the Rm Interface, when the Um interface data rate exceeds the Rm
17 interface baud rate.
21 [4] 3.6.6.2.4 Soft Handoff

24 None

27 b. Configure the mobile station’s maximum forward Supplemental Code Channels to N (N >
28 4 for Service Option 22, N > 3 for Service Option 25).
30 d. Configure the RS-232 baud rate in the Rm interface to 4800 bps.

31 e. Setup a mobile station terminated call with Service Option 22, and establish an FTP
32 session.
12-17
C.S0044-0 v1.0
3 station.
4 g. Verify at the mobile station that N Supplemental Code Channels are in use.
5 h. Transfer the file from the remote host to TE2M using the binary “get” command.
6 i. Verify the file is transferred successfully.

7 j. End FTP session.
8 k. Repeat steps e through j with Service Option 25.

10 The mobile station shall comply with steps g and i for all test cases.
11 12.15 Dormant Timer
13 This test verifies the mobile station correctly processes the Service Option Control Message
14 which controls the Dormant Timer, and that the mobile station delays any attempt to send an
15 Origination Message requesting a MSPD service option until the Dormant Timer expires.
17 [4] 3.7.3.3.2.21 Service Option Control Message

21 None

25 c. Configure the mobile station’s inactivity timer to 20 seconds by issuing the AT command
26 AT+CTA=20.
27 d. Configure the base station to support N Supplemental Code Channels.
28 e. Setup a mobile station terminated call with Service Option 22, and establish an FTP
29 session.
32 station.
12-18
C.S0044-0 v1.0
1 g. From the base station, send the Service Option Control Message with the Packet Data
2 Dormant Timer set to 20 seconds.
3 h. Verify from the mobile station that N Supplemental Code Channels are being used.
4 i. Transfer the file from the remote host to TE2M using the binary “get” command and verify
5 the file is transferred successfully.
6 j. Wait for the packet data service call control function to enter the Dormant State due to
7 data inactivity (i.e. when the inactivity timer in the mobile station expires).
8 k. Setup a mobile station originated call with Service Option 22, and establish an FTP
9 session as soon as the packet data service call control function is in the Dormant
10 Statemode. The time elapsed between the Release Order and the Origination Message
11 should be approximately 20 seconds.
12 l. After the call is re-established, transfer the file from the remote host to TE2M using the
13 binary “get” command and verify the file is transferred successfully.
14 m. End FTP session.
15 n. Repeat steps e through m with Service Option 25.

17 The mobile station shall comply with steps h, i and l.
18 12.16 Packet Zone ID
20 This test verifies the following:
21 When the mobile station detects a change in the Packet Zone ID in the Extended System
22 Parameters Message and the new Packet Zone ID is not in the Packet Zone ID List the mobile
23 station shall attempt to reconnect the packet data service option.
24 While the data is being transferred and the base station sends a new Packet Zone ID to the
25 mobile station in the Service Option Control Message, the mobile station shall continue to transfer
26 files in the new Packet Zone ID.
27 When the Dormant Timer is running and hasnot expired, the mobile station shall not re-originate a
28 data call.
29
31 [4] 3.7.3.3.2.21 Service Option Control Message
33 [15]-A9; 2.2.2.1.2.6 Dormant/Traffic State

35 None
12-19
C.S0044-0 v1.0
2 12.16.4.1 Mobile Station Idle State

6 d. Configure the mobile station’s inactivity timer to 20 seconds by issuing an AT command.
7 e. Setup a mobile station originated call with Service Option 22, and establish an FTP
8 session
11 station.
12 g. Instruct the base station to send the Service Option Control Message to the mobile
13 station to enable the PACKET_ZONE_ID with a valid list of PACKET_ZONE_Ids. Specify
14 the number of packet data service identifiers that the mobile station is to retain in its
15 packet data zone identifiers list (the number shall be set to 2 or greater). Also set the
16 Packet Data Dormant Timer to 20 seconds.
17 h. Verify from the mobile station that N Supplemental Code Channels are being used.
18 i. Transfer the file from the remote host to TE2M using the binary “get” command.
19 j. Make sure there is no data to transmit for 20 seconds.
20 k. Verify the packet data service call control function enters the Dormant State and the
21 mobile station enters the Mobile Station Idle State due to data inactivity.
22 l. Change the PACKET_ZONE_ID of the serving system in the Extended System
23 Parameter Message.
24 m. Verify the mobile station reconnects to the same Service Option when it detects the new
25 PACKET_ZONE_ID.
26 n. After the call is re-established, transfer the file from the remote host to TE2M using the
27 binary “get” command and verify the file is transferred successfully.
29 p. Repeat steps e through o with Service Option 25.
30 q. Repeat steps a through f.
31 r. Instruct the base station to send the Service Option Control Message to the mobile
32 station to set the Dormant Timer to 60 seconds.
33 s. Repeat steps j through k.
34 t. Attempt to initiate an ftp session to a server at the mobile station.
35 u. Verify the MS does not send an Origination Message before the Dormant Timer expires.
12-20
C.S0044-0 v1.0
1 12.16.4.2 Traffic Channel State

5 d. Setup a mobile station originated call with Service Option 22, and establish an FTP
6 session
7 e. From the base station, generate a General Handoff Direction Message or a
8 Supplemental Channel Assignment Message to allocate N Supplemental Code
9 Channels to the mobile station.
10 f. From the base station, send the Service Option Control Message to the mobile station
11 to enable the PACKET_ZONE_ID with a valid list of PACKET_ZONE_IDs.
12 g. Verify from the mobile station that N Supplemental Code Channels are being used.
13 h. Begin transferring the file from the remote host to TE2M using the binary “get”
14 command.
15 i. While the file is being transferred, send the Service Option Control Message to the
16 mobile station with a change in the PACKET_ZONE_ID.
17 j. Change the PACKET_ZONE_ID of the serving system in the In-Traffic System
18 Parameter Message.
19 k. Verify the mobile station continues file transfer on the new PACKET_ZONE_ID.
23 12.16.5.1 Mobile Station Idle State

24 The mobile station shall comply with steps h, k m, n and u
25 12.16.6 Traffic Channel State

26 For section 12.16.3.2, the mobile station shall comply with steps g and k for all test cases.
27
28
12-21
C.S0044-0 v1.0
1 13 HIGH SPEED PACKET DATA
3 13.1.1 Definition
4 This test verifies that file transfer from remote host to mobile station can be successfully done
5 using the HSPD call.
7 2.7.2.3.2.18 Supplemental Channel Request Message

8 2.7.2.3.2.28 Supplemental Channel Request Mini Message
10 3.7.3.3.2.24 Supplemental Channel Assignment Message

11 3.7.5.7.1 Channel Configuration for the Supplemental Channel
12 1.4.2.2 Mobile Station Packet Data Service States (see [15])
13 2.2.2 Service and Call Control Procedures (see [15])

14 2.2.3 Initialization and Connection of Packet Data Service Options (see [15])
15 2.2.7 High Speed Operation (see [15])

17 None

20 b. At the remote host prepare appropriate file (see Annex D) for data transfer11.
21 c. Setup an FTP session using Service Option 33 with the remote host 12.
22 d. If supplemental channel is assigned, verify the base station sends a Universal Handoff
23 Direction Message, an Extended Supplemental Channel Assignment Message, or a
24 Forward Supplemental Channel Assignment Mini Message.
25 e. Transfer the file from the remote host to the TE2M using the binary “get” command.
26 f. After the file transfer is completed, end the FTP session. Make sure the file is
11
The large FTP file size, coupled with a full constant buffer, is intended to trigger use of the
maximum data rate assignment supported by both mobile station and base station.
12
Ensure that sufficient walsh code resources are available.
13-1
C.S0044-0 v1.0
1 g. Steps b through f may be repeated for other data rates and different radio
2 configurations supported by both mobile station and base station.
3
4 Table 13.1.4-1 SCH Data Rate
Data Rate Granted (bps)
F-RC3, 4 / R-RC3 F-RC5 / R-RC4

F-RC6, 7 /R-RC5 F-RC8, 9 / R-RC6
9600 14400
19200 28800
38400 57600
76800 115200
153600 230400
307200 460800
614400 1036800

7 The mobile station shall comply with step f. The base station shall comply with step d.
9 13.2.1 Definition
10 This test verifies that file transfer from mobile station to remote host can be successfully done
11 using the HSPD call.

13-2
C.S0044-0 v1.0

2 None

5 b. At the TE2M prepare a file for data transfer.

6 c. Setup an FTP session using Service Option 33 with the remote host.
7 d. Transfer the file from the TE2M to the remote host using the binary “put” command.
8 Ensure that the total amount of data to be transferred at the mobile station is more than
9 an implementation defined threshold, or otherwise cause the mobile station to send a
10 Supplemental Channel Request Message or a Supplemental Channel Request Mini
11 Message with DURATION field set to a non-zero value.
12 e. If supplemental channel is assigned, verify the base station sends a Universal Handoff
13 Direction Message, an Extended Supplemental Channel Assignment Message, or a
14 Reverse Supplemental Channel Assignment Mini Message.
15 f. After the file transfer is completed, end the FTP session. Make sure that file is
17 g. Steps b through f should be executed for the maximum data rates13 supported by both
18 mobile station and base station.
19 h. Steps b through f may be repeated for other data rates and radio configurations
20 supported by both mobile station and base station.

23 13.3 Bi-directional File Transfer
25 This test verifies that bi-directional file transfer can be successfully done using the HSPD call.

13
Make sure that transmit power is not limiting factor for maximum data rate assignment.
13-3
C.S0044-0 v1.0


6 None

9 b. Prepare a file at both the remote host and TE2M for data transfer.
10 c. Setup an FTP session using Service Option 33 with the remote host.
11 d. Transfer the file from the TE2M to the remote host. Ensure that the total amount of data
12 to be transferred at the mobile station is more than an implementation defined
13 threshold, or otherwise cause the mobile station to send a Supplemental Channel
14 Request Message or a Supplemental Channel Request Mini Message with DURATION
15 field set to a non-zero value.
16 e. Transfer a file from the Remote Host to the TE2M while the transfer in the reverse
17 direction is still proceeding.
18 f. If forward supplemental channel is assigned, verify the base station sends a Universal
19 Handoff Direction Message, an Extended Supplemental Channel Assignment Message,
20 or a Forward Supplemental Channel Assignment Mini Message.
21 g. If reverse supplemental channel is assigned, verify the base station sends a Universal
22 Handoff Direction Message (can be same as one in step f), an Extended Supplemental
23 Channel Assignment Message (can be same as one in step f), or a Reverse
24 Supplemental Channel Assignment Mini Message.
25 h. Verify that files in both directions are successfully transferred and end the FTP session.
26 i. Steps c through f should be executed for the maximum forward14 and reverse15 data
27 rates that are supported by both mobile station and base station.
28 j. Steps c through f may be repeated for different data rates and radio configurations that
29 are supported by both mobile station and base station.

31 The mobile station shall comply with step h. The base station shall comply with steps f and g.
14
Make sure that conditions to trigger maximum forward data rate assignment are fulfilled; such
as large enough FTP file size, sufficient walsh code resource etc.
15
Make sure that transmit power is not limiting factor for maximum reverse data rate assignment.
13-4
C.S0044-0 v1.0
2 13.4 Service Option Control Message Processing
3 13.4.1 Definition
4 This test verifies the mobile station ability to process the Service Option Control Message. This
5 test also verifies the mobile station is able to establish a voice call while the packet data session
6 is dormant.
7 13.4.2 Traceabilities (see [4] unless otherwise noted)

11 2.2.2.1 Mobile Station Procedures (see [15])

12 2.2.2.2 Base Station Procedures (see [15])
13 2.2.4 Packet Data Dormant Timer Control (see [15])
13-5
C.S0044-0 v1.0

MS BS
Traffic Traffic
Data Call in Progress
Service Option Control Message
MS packet service is Release Order

dormant
General Page Msg with

voice service option
Voice
Call in Progress
Voice call ends
General Page Msg with

packet data service option
Data Call may

Resume
Traffic Traffic
4 a. Connect the mobile station in Figure A-3.

5 b. Setup a mobile originated Service Option 33 call.
6 c. While the data call is active, instruct the base station to send a Service Option Control
7 Message with the following information:
8
13-6
C.S0044-0 v1.0
Field Value
SERVICE_OPTION ‘0000000000100001’
DORM_CTRL ‘001’
FIELD_TYPE ‘011’
DORM_TIME ‘11111111’ (25.5 sec)
1 d. Instruct the base station to send a Release Order with ORDQ=’0’ to the mobile station.
2 e. Verify the mobile station releases the call and the packet data session is in the dormant
3 state.
4 f. Before the DORM_TIME expires, send a General Page to the mobile station with a
5 voice service option.
6 g. Verify the call completes and user traffic is present.
7 h. End the call before DORM_TIME expires.

8 i. Set up a mobile originated voice call.
9 j. Verify the call completes and user traffic is present.
10 k. End the call before DORM_TIME expires.

11 l. Insure the mobile station has sufficient data in its buffer.
12 m. Verify the mobile station does not send an Origination Message for packet data service
13 before the DORM_TIME expires.
14 n. After DORM_TIME has expired, page the mobile station with a packet data service or
15 otherwise cause the mobile station to send an Origination Message for a packet data
16 service.
17 o. Verify the call completes and user traffic is present.

19 The mobile station shall comply with steps e, g, j, m and o.
20 13.5 Changing Encoding Type on Supplemental Channel during Hard Handoff
22 This test verifies that the mobile station is capable of using turbo encoding and is capable of
23 changing to convolutional encoding.
25 2.1.3.1.4 Forward Error Correction (see [1)]

26 3.1.3.1.4 Forward Error Correction (see [1])
13-7
C.S0044-0 v1.0


4 None
6 13.5.4.1 R-SCH Turbo Encoding to Convolutional Encoding

8 b. Ensure the mobile station supports turbo encoding and convolutional encoding.
9 c. Setup a mobile originated Service Option 33 call.
10 d. Instruct the base station to send a Service Connect Message with CODING=‘1’ in the
11 Service Configuration Record for the F-SCH and R-SCH (as supported by the mobile
12 station).
13 e. Verify the mobile station sends a Service Connect Completion Message.
14 f. Initiate a data transfer from the mobile station and verify the mobile station sends a
15 Supplemental Channel Request Message requesting a reverse supplemental channel.
16 g. Instruct the base station to send an Extended Supplemental Channel Assignment
17 Message assigning a reverse supplemental channel to the mobile station.
18 h. While the data transfer is in progress, instruct the base station to send a Universal
19 Handoff Direction Message with CODING=’0’ and a reverse supplemental channel
20 burst assignment.
21 i. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff
23 j. Verify the data transfer completes successfully using convolutional encoding.

24 k. End the call from the mobile station.
25 13.5.4.2 R-SCH Convolution Encoding to Turbo Encoding
31 station).

33 f. Initiate a data transfer from the mobile station and verify the mobile station sends a
13-8
C.S0044-0 v1.0
1 g. Instruct the base station to send an Extended Supplemental Channel Assignment

3 h. While the data transfer is in progress, instruct the base station to send a Universal
4 Handoff Direction Message with CODING=’1’ and a reverse supplemental channel
5 burst assignment.
6 i. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff
8 j. Verify the data transfer completes successfully using turbo encoding (if the block size
9 per frame is at least 360 bits)..
10 k. End the call from the mobile station.
11 13.5.4.3 F-SCH Turbo Encoding to Convolutional Encoding

17 station).

19 f. Initiate a data transfer to the mobile station and verify the base station sends an
20 Extended Supplemental Channel Assignment Message assigning a F-SCH.
21 g. While the data transfer is in progress, instruct the base station to send a Universal
22 Handoff Direction Message with CODING=’0’ and a forward supplemental channel
23 burst assignment.
24 h. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff
26 i. Verify the data transfer completes successfully using convolutional encoding.
27 j. End the call from the mobile station.
28 13.5.4.4 F-SCH Convolutional Encoding to Turbo Encoding

34 station).
13-9
C.S0044-0 v1.0
1 f. Initiate a data transfer to the mobile station and verify the base station sends an
3 g. While the data transfer is in progress, instruct the base station to send a Universal
4 Handoff Direction Message with CODING=’1’ and a forward supplemental channel
5 burst assignment.
6 h. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff
8 i. Verify the data transfer completes successfully using turbo encoding (if the block size
9 per frame is at least 360 bits)..
12 13.5.5.1 R-SCH Turbo Encoding to Convolutional Encoding

13 The mobile station shall comply with steps e, i, and j
14 13.5.5.2 R-SCH Convolutional Encoding to Turbo Encoding

15 The mobile station shall comply with steps e, i, and j.
16 13.5.5.3 F-SCH Turbo Encoding to Convolutional Encoding

17 The mobile station shall comply with steps e, h, and i.
18 13.5.5.4 F-SCH Convolutional Encoding to Turbo Encoding

19 The mobile station shall comply with steps e, h, and i.
20 13.6 Control Hold Mode Transitions
22 This test applies when the mobile station and base station support Control Hold Mode. This test
23 verifies that the mobile can go in and out of the Control Hold Mode in all the possible
24 combinations. When the mobile station or the base station, trigger a transition to the Control Hold
25 Mode, the expected signaling exchange takes place. Upon transition to the Control Hold Mode,
26 the reverse pilot is gated at the specified gating rate DCCH is maintained with Power Control sub-
27 channel and user traffic transmission is not allowed in either direction. When the mobile station
28 and base station transition to the Active Mode, the expected signaling exchange takes place.
29 Upon transition to the Active Mode, the reverse pilot transmission is continuous and user traffic
30 transmission is allowed.
31 The following are call flow examples for going in and out of Control Hold Mode. Either the mobile
32 station or the base station can trigger either transition.

34
13-10
C.S0044-0 v1.0
MS BS
Active Active
BS decides to transition
Extended Release (Mini) Message / to Control Hold Mode
Universal Handoff Direction Message
Extended Release Response (Mini) Message

Handoff Completion Message
At the action time:
Transition to Control Hold Mode
& start reverse pilot gating at the
specified gating rate
Control Hold Control Hold
1
2
3 Figure 13-1 Call Flow for base station initiated Active to Control Hold Transition
4
MS BS
Active Active
Request to transition to
Control Hold Mode
Resource Release Request (Mini) Message
Extended Release (Mini) Message /

Universal Handoff Direction Message
Extended Release Response (Mini) Message

Handoff Completion Message
At the action time:
Transition to Control Hold Mode
& start reverse pilot gating at the
specified gating rate
Control Hold Control Hold
5
6
7 Figure 13-2 Call Flow for mobile station initiated Active to Control Hold Transition
8
13-11
C.S0044-0 v1.0
MS BS
Control Control
Hold Hold
Resource Allocation (Mini) Message /

Universal Handoff Direction Message /
Extended Supplemental Channel BS decides to transition
Assignment Message/ to Active Mode
Forward Supplemental Channel
Assignment Mini Message/
Reverse Supplemental Channel
Assignment Mini Message
At the action time:

Transition to Active Mode
& start reverse pilot continuous
transmission
Active Active
1
2
3 Figure 13-3 Call Flow for base station initiated Control Hold to Active Transition
4
MS BS
Control Control
Hold Hold
Request to transition to
Active Mode Resource Request (Mini) Message /
Supplemental Channel
Request (Mini) Message
Resource Allocation (Mini) Message /

Universal Handoff Direction Message /
Extended Supplemental Channel
At the action time: Assignment Message/
Transition to Active Mode Forward Supplemental Channel
& start reverse pilot continuous Assignment Mini Message/
transmission Reverse Supplemental Channel
Assignment Mini Message
Active Active
5
6
7 Figure 13-4 Call Flow for mobile station initiated Control Hold to Active Transition
13-12
C.S0044-0 v1.0
1 2.6.4.1.9 Processing the Extended Release Message and the Extended Release Mini
2 Message
3 2.6.4.1.10 Processing the Resource Allocation Message and Resource Allocation Mini
4 Message

9 2.7.2.3.2.23 Resource Request Message

10 2.7.2.3.2.24 Resource Request Mini Message
11 2.7.2.3.2.29 Resource Release Request Message
12 2.7.2.3.2.30 Resource Release Request Mini Message

13 3.6.4.1.6 Processing Resource Request Messages
14 3.6.4.1.8 Processing Resource Release Request Message and Resource Release
15 Request Mini Message
17 3.6.6.2.2.11 Processing the Universal Handoff Direction Message
18 3.6.6.2.2.13 Processing of Forward Supplemental Channel Assignment Mini Message
19 3.6.6.2.2.14 Processing of Reverse Supplemental Channel Assignment Mini Message
20 3.7.3.3.2.32 Resource Allocation Message
21 3.7.3.3.2.33 Resource Allocation Mini Message
22 3.7.3.3.2.34 Extended Release Message
23 3.7.3.3.2.35 Extended Release Mini Message
26 3.7.3.3.2.38 Forward Supplemental Channel Assignment Mini Message
27 3.7.3.3.2.39 Reverse Supplemental Channel Assignment Mini Message
28 3.7.5.20 (base station) Non-Negotiable Service Configuration information record

31 b. Setup a packet data call, using only the Dedicated Control Channel (DCCH).
32 c. Verify user traffic (Ex. Browser data) in both directions.
13-13
C.S0044-0 v1.0
1 d. Cause the mobile station and/or base station to initiate transition to the Control Hold
2 Mode because of out-of-data indication from the RLP.
3 e. Verify that one of the following two scenarios occurs:
4 1. Verify that the mobile station sends a Resource Release Request (Mini)
5 Message to the base station to request transition to the Control Hold Mode.
6 Verify that the base station accepts this request, via an Extended Release (Mini)
7 Message, or a Universal Handoff Direction Message. Verify that the mobile
8 station responds with an Extended Release Response (Mini) Message, or a
9 Extended Handoff Completion Message.
10 2. Verify that the base station sends an Extended Release Mini Message, or a
11 Universal Handoff Direction Message. Verify that the mobile station responds
12 with an Extended Release Response Mini Message, or an Extended Handoff
14 f. Upon transition to Control Hold Mode, verify the following:
15 1. The reverse pilot is gated at the specified rate.

16 2. Dedicated Control Channel is maintained for signaling.
17 3. User traffic (Ex. Browser data) is not transmitted on either direction. NOTE: This
18 can be verified by attempting to send user traffic, while not granting any requests
19 to transition to the Active Mode.
20 4. Reverse Power Control Subchannel is maintained at the Forward Dedicated
21 Control Channel.
22 g. Depending on who initiated the transition to Control Hold Mode in e, and if possible,
23 change the control hold time on the network side to make the other alternative happen
24 in d. Repeat b through f. Results are as expected in f.
25 h. Execute steps b through f.
26 i. Send a ping from the base station side.
27 j. Verify that the base station initiates the transition to Active Mode, via a Resource
28 Allocation Message, a Resource Allocation Mini Message, a Universal Handoff
29 Direction Message, an Extended Supplemental Channel Assignment (Mini) Message, a
30 Forward Supplemental Channel Assignment Mini Message, or a Reverse Supplemental
31 Channel Assignment Mini Message. Verify that the mobile station responds accordingly.
32 k. Upon transition to the Active Mode, verify that:
33 1. The reverse pilot transmission is continuous
34 2. User traffic (Ex. Browser data) is transmitted.
35 l. Execute steps b through f.
36 m. Send a ping from the mobile station side to cause the mobile station to initiate the
37 transition to Active Mode. Verify that the mobile station sends a Resource Request
38 (Mini) Message, a Supplemental Channel Request (Mini) Message. Verify that the base
39 station sends a Resource Allocation (Mini) Message, a Universal Handoff Direction
13-14
C.S0044-0 v1.0
1 Message, an Extended Supplemental Channel Assignment (Mini) Message, a Forward

2 Supplemental Channel Assignment Mini Message, or a Reverse Supplemental Channel
3 Assignment Mini Message.
4 n. Verify step k.

6 The mobile station and the base station shall comply with the requirements in the following
7 steps:ef, j, k, m, and n.
8 13.7 Soft Handoff of Fundamental Channel/Dedicated Control Channel and Supplemental

9 Channels
11 This test verifies that the mobile station can successfully complete a soft handoff of the
12 fundamental, dedicated control channel, and supplemental channels during a data transfer.
15 2.7.2.3.2.28 Pilot Strength Measurement Mini Message

16 2.7.2.32.34 Extended Pilot Strength Measure Message

27 None
29 13.7.4.1 Forward FCH/DCCH and SCH Soft Handoff

30 a. Connect the mobile station to the base station as shown in Figure A-5 and setup the
31 parameters as shown in Table 13.7.4-1.
13-15
C.S0044-0 v1.0
1 Table 13.7.4-1

Îor/Ioc dB 7 -20
Pilot Ec/Io dB -5.8 -33
2
3 b. Verify the mobile station is in the Idle State on base station 1.
4 c. Setup a mobile station originated service option 33 call, using the FCH for signaling.
5 d. Initiate a forward data transfer to the mobile station.

6 e. Configure base station 1 to send the Extended Supplemental Channel Assignment
7 Message to assign the maximum number of forward supplemental channels supported
8 by the base station and mobile station.
9 f. While the forward data transfer is in progress, raise the level of base station 2 in steps
10 of 1 dB with a dwell time of 5 seconds after each step until the mobile station has
11 generated the Pilot Strength Measurement Message, Extended Pilot Strength Message,
12 or a Pilot Strength Mini Message.
13 g. Configure base station 1 to send a Universal Handoff Direction Message with
14 NUM_FOR_ASSIGN = [number of SCH in step e] and both base stations in the active
15 set.
16 h. Verify the mobile station sends the Handoff Completion Message or an Extended
17 Handoff Completion Message. Verify the mobile station’s active set consist of both base
18 stations.
19 i. Lower the level of base station 1 in steps of 1 dB with a dwell time of 5 seconds after
21 Message, Extended Pilot Strength Measurement Message or a Pilot Strength
22 Measurement Mini Message..
23 j. Configure base station 1 to send a Universal Handoff Direction Message to the mobile
24 station with NUM_FOR_ASSIGN = [number of SCH in step e] and base station 2 in the
25 active set.
26 k. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff
28 l. Verify the data transfer completes successfully.
29 m. End the call.

30 n. Repeat steps c through m using the DCCH for signaling.
13-16
C.S0044-0 v1.0
1 13.7.4.2 Reverse FCH/DCCH and SCH Soft Handoff

5 c. Setup a mobile station originated service option 33 call using the FCH for signaling.
6 d. Initiate a reverse data transfer from the mobile station.
7 e. After the mobile station sends a Supplemental Channel Request Message, configure
8 base station 1 to send an Extended Supplemental Channel Assignment Message to
9 assign the maximum number of reverse supplemental channels supported by the
10 network and mobile station.
11 f. While the reverse data transfer is in progress, raise the level of base station 2 in steps
13 generated the Pilot Strength Measurement, Extended Pilot Strength Measurement
14 Message or a Pilot Strength Measurement Mini Message.

16 NUM_REV_ASSIGN = [number of SCH in step e] and both base stations in the active
17 set.
20 stations.
21 i. Lower the level of base station 1 in steps of 1 dB with a dwell time of 5 seconds after
23 Message, Extended Pilot Strength Measurement Message or a Pilot Strength
24 Measurement Mini Message.
25 j. Configure base station 2 to send a Universal Handoff Direction Message to the mobile
26 station with NUM_REV_ASSIGN = [number of SCH in step e] and base station 2 in the
27 active set.
28 k. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff
30 l. Verify the data transfer completes successfully.
31 m. End the call.
32 n. Repeat steps c through m using the DCCH.
34 13.7.5.1 Forward FCH/DCCH and SCH Soft Handoff

35 The mobile station shall comply with steps h, k, l, and n.
36 13.7.5.2 Reverse FCH/DCCH and SCH Soft Handoff

37 The mobile station shall comply with steps h, k, l, and n..
13-17
C.S0044-0 v1.0
1 13.8 Soft Handoff of Fundamental Channel or Dedicated Control Channel only
2 13.8.1 Definition
3 This test verifies the mobile station can successfully complete a data transfer when only the
4 fundamental channel or dedicated control channel is in soft handoff.




19 None
21 13.8.4.1 Forward FCH/DCCH Only Soft Handoff
26 d. Initiate a forward data transfer to the mobile station.
27 e. Configure base station 1 to send the Extended Supplemental Channel Assignment
28 Message to assign the maximum number of forward supplemental channels supported
29 by the network and mobile station.
30 f. While the forward data transfer is in progress, raise the level of base station 2 in steps
32 generated the Pilot Strength Measurement Message, Extended Pilot Strength
33 Measurement Message or a Pilot Strength Measurement Mini Message.
13-18
C.S0044-0 v1.0

2 NUM_FOR_ASSIGN = 0 and both base stations in the active set.
5 stations.
6 i. Verify the data transfer completes successfully.
7 j. End the call.
8 k. Repeat steps c through j using the DCCH for signaling.
9 13.8.4.2 Reverse FCH/DCCH Only Soft Handoff

13 c. Setup a mobile station originated service option 33 call using the FCH for signaling
14 d. Initiate a reverse data transfer from the mobile station.
15 e. After the mobile station sends a Supplemental Channel Request Message, Configure
16 base station 1 to send an Extended Supplemental Channel Assignment Message to
17 assign the maximum number of reverse supplemental channels supported by the
18 network and mobile station.
19 f. While the reverse data transfer is in progress, raise the level of base station 2 in steps
21 generated the Pilot Strength Measurement Message, Extended Pilot Strength
22 Measurement Message or a Pilot Strength Measurement Mini Message.
24 NUM_REV_ASSIGN = 0 and both base stations in the active set.
27 stations.
29 j. End the call.
30 k. Repeat steps c through j with the DCCH for signaling.
32 13.8.5.1 Forward FCH/DCCH Only Soft Handoff

33 The mobile station shall comply with steps h i, and k.
34 13.8.5.2 Reverse FCH/DCCH Soft Handoff Only

35 The mobile station shall comply with steps h, i, and k.
13-19
C.S0044-0 v1.0
1 13.9 Adding Supplemental Channels during Soft Handoff
2 13.9.1 Definition
3 This test verifies that a supplemental channel(s) can be added in a service option 33 call while in
4 soft handoff on the fundamental channel or dedicated control channel.




19 None
21 13.9.4.1 Adding F-SCH during a Soft Handoff
26 d. Raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after
28 Message, Extended Pilot Strength Measurement Message ,or a Pilot Strength
29 Measurement Mini Message...
30 e. Configure base station 1 to send a Universal Handoff Direction Message with
31 NUM_FOR_ASSIGN = 0 and both base stations in the active set.
13-20
C.S0044-0 v1.0
1 f. Verify the mobile station sends the Handoff Completion Message or an Extended
3 stations.
4 g. Initiate a forward data transfer to the mobile station.
5 h. Configure base station 1 to send the Extended Supplemental Channel Assignment
6 Message with NUM_SUP_SHO = ‘001’ for the forward supplemental channel and
7 include both base station 1 and base station 2 for PILOT_PN values.
9 j. End the call.
11 13.9.4.2 Adding R-SCH during a Soft Handoff

15 c. Setup a mobile station originated service option 33 call.

16 d. Raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after
18 Message , Extended Pilot Strength Measurement Message or a Pilot Strength
19 Measurement Mini Message..
20 e. Configure base station 1 to send a Universal Handoff Direction Message with
21 NUM_REV_ASSIGN = 0 and both base stations in the active set.
22 f. Verify the mobile station sends the Handoff Completion Message or an Extended
24 stations.
25 g. Initiate a reverse data transfer from the mobile station.
26 h. Configure base station 1 to send the Extended Supplemental Channel Assignment
27 Message with NUM_SUP_SHO = ‘001’ for the reverse supplemental channel and
28 include both base station 1 and base station 2 for PILOT_PN values.
30 j. End the call.
33 13.9.5.1 Adding F_SCH during Soft Handoff

34 The mobile station shall comply with steps f, i, and k.
13-21
C.S0044-0 v1.0
1 13.9.5.2 Adding R-SCH during a Soft Handoff

2 The mobile station shall comply with steps f, i and k.
3 13.10 Hard Handoff during Data Transfer
5 This test verifies the data transfer continues after hard handoff using the forward and reverse link.


18 None
20 13.10.4.1 Forward Data Transfer during Hard Handoff
23 Table 13.10.4-1

Îor/Ioc dBm N/A -5
24
13-22
C.S0044-0 v1.0
1 b. Ensure that the mobile station is operating in the idle state on base station 1.
2 c. Setup a mobile station originated Service Option 33 call.
3 d. Initiate a data transfer to the mobile station and verify the base station sends an
5 e. While the data transfer is in progress, instruct the base station to send a Universal
6 Handoff Direction Message directing the mobile station to base station 2.
7 f. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff
9 g. Configure base station 2 to send a Universal Handoff Direction Message or an
11 h. Verify the data transfer completes.
12 i. End the call from the mobile station.
13 j. Repeat steps c through i using the DCCH for signaling.
14 13.10.4.2 Reverse Data Transfer during Hard Handoff
18 c. Setup a mobile station originated Service Option 33 call.

19 d. Initiate a data transfer from the mobile station and verify the mobile station sends a
21 e. Instruct the base station to send an Extended Supplemental Channel Assignment

23 f. While the data transfer is in progress, instruct the base station to send a Universal
24 Handoff Direction Message directing the mobile station to base station 2.
27 h. Configure base station 2 to send a Universal Handoff Direction Message or an
28 Extended Supplemental Channel Assignment Message assigning a R-SCH.


34 The mobile station shall comply with steps f, h and j.
13-23
C.S0044-0 v1.0

2 The mobile station shall comply with steps g, i, and k.
3 13.11 Hard Handoff to a different Radio Configuration
5 This test verifies hard handoff to a different radio configuration during an HSPD call.


18 None
24 c. Setup a mobile station originated Service Option 33 call. Note the FOR_FCH_RC,
25 REV_FCH_RC, and SCH_RC values.
26 d. Initiate a data transfer to the mobile station and verify the base station sends an
28 e. While the data transfer is in progress, instruct the base station to send a Universal
29 Handoff Direction Message changing the FOR_FCH_RC, REV_FCH_RC and SCH_RC
30 values in step c and directing the mobile station to base station 2.
31 f. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff
13-24
C.S0044-0 v1.0
1 g. Configure base station 2 to send an Extended Supplemental Channel Assignment

2 Message assigning a F-SCH.
3 h. Verify the data transfer completes.
4 i. End the call from the mobile station.
5 j. This test may be repeated for all radio configurations supported.

11 c. Setup a mobile station originated Service Option 33 call. Note the FOR_FCH_RC,
12 REV_FCH_RC, and SCH_RC values.
13 d. Initiate a data transfer from the mobile station and verify the mobile station sends a
15 e. Instruct the base station to send an Extended Supplemental Channel Assignment

17 f. While the data transfer is in progress, instruct the base station to send a Universal
18 Handoff Direction Message changing the FOR_FCH_RC, REV_FCH_RC and SCH_RC
19 values in step c directing the mobile station to base station 2.
22 h. Configure base station 2 to send a Universal Handoff Direction Message or an
23 Extended Supplemental Channel Assignment Message assigning a R-SCH.

26 k. This test may be repeated for all radio configurations supported.
27 l. Repeat steps c through k using the DCCH for signaling

30 The mobile station shall comply with steps f, h, and k.

32 The mobile station shall comply with steps g, i, and l.
13-25
C.S0044-0 v1.0
1 13.12 Mobile Station Packet Data Inactivity Timer
3 This test is applicable for a mobile station implementing packet data inactivity timer. This test
4 verifies the mobile station releases the traffic channel after expiration of the mobile station packet
5 data Inactivity Timer. The test verifies the dormant link layer connection can be re-activated.

9 None
11 a. Set the packet data inactivity timer at the MT2 to 20 seconds.

12 b. Ensure the base station packet data inactivity timer is disabled or set to a value of at
13 least 30 seconds.
14 c. Initiate a Telnet session to a remote host.

15 d. Record the IP address assigned to the mobile station.
16 e. Exit the Telnet session.
17 f. Wait for the mobile station packet data inactivity timer to expire. Verify the “in use”
19 g. Initiate a Telnet session to a remote host.
20 h. Record the IP address assigned to the mobile station.

21 i. Wait for the mobile station packet data inactivity timer to expire. Verify the “in use”
23 j. Issue a continuous “ping” command from the remote host to the mobile station using
24 the IP address assigned to the mobile station.
25 k. Verify that the ping is successful.

27 The mobile station shall comply with steps f, i and k .
28 13.13 Mobile Station and Base Station Operating in Different States
30 This test verifies the mobile station and base station correct the condition of the mobile station
31 operating in the Null State and the base station/PCF operating in the Dormant State. [4] permits
32 two standardized approaches for the mobile station to reject/release a General Page Message
33 containing Service Option 33 when the mobile station is in the Null State and the base
13-26
C.S0044-0 v1.0
1 station/PCF is in the Dormant State. In both implementations, the mobile station and base
2 station/PCF shall transition to the Null State.
3 In the preferred implementation, a mobile station in the Null State will reject a General Page
4 Message containing Service Option 33 by sending a Page Response Message containing
5 Service Option = 0x00. The base station should send a Release Order to the mobile station.
6 In an alternate implementation, a mobile station in the Null State will accept a General Page
7 Message containing Service Option 33 by sending a Page Response Message containing
8 Service Option 33. After the base station assigns a traffic channel, the mobile station sends a
9 Release Order containing ORDQ=2 to release the call.
11 3.7.4.1 Page Response Substate [4]
12 2.7.1.3.2.5 Page Response Message [4]

13 3.6.2.3 Mobile Station Directed Messages [4]
14 3.6.3.3 Responding to a Page Response Message [4]
15 3.7.4 Orders [4]
16 2.2.2.2.1.3 Paging State [15]

BS/
MS PCF
Dormant Dormant
State State
MS and BS/
PCF are not
in the same
state. MS has
closed PPP
session
without
notifying BS/
Dormant
Null State State
PCF. BS/PCF
attempts to
General Page, SO: initiate a
0x21 dormant to
Page Response Msg with SO: active
transition.
0x00
BS should send Release Order
Null State Null State

18
19 Figure 13-5 Call Flow without Setting Up Traffic Channel (Preferred Implementation)
13-27
C.S0044-0 v1.0
BS/
MS
PCF
Dormant Dormant
State State
MS and BS/
PCF are not
in the same
state. MS has
closed PPP
session
without Dormant
Null State
notifying BS/ State BS/PCF
PCF. attempts to
General Page, SO: initiate a
0x21 dormant to
active
transition.
Page Response Msg with SO: 0x21
Traffic Channel Setup
Conversation
MS sends Release Order with

ORDQ=2
Null State Null State
1
2 Figure 13-6 Call Flow with Setting Up Traffic Channel (Alternate Implementation)

4 a. Connect the mobile station as shown in Figure A-3.
5 b. Set up a Service Option 33 call using a dedicated traffic channel.

6 c. Allow the mobile station to enter the Dormant State.
7 d. Verify the base station/PCF and mobile station are operating in the Dormant State.
8 e. Instruct the mobile station to transition to the Null State (i.e. terminate the PPP session)
9 without notifying the base station. (e.g., disconnect the mobile station from the laptop.)
10 NOTE: Depending on implementation, the mobile station may autonomously originate a
11 service option 33 call upon the disconnection of the cable from the laptop. If this occurs,
12 proceed to step g2.
13 f. Instruct the base station to initiate the Dormant to Active transition by sending a
14 General Page Message or Universal Page Message to the mobile station with the
15 Service Option 33.
16 g. Verify one of the following occurs;
17 1. The mobile station sends a Page Response Message with the Service Option =
18 0:
13-28
C.S0044-0 v1.0
1 a. The base station should send a Release Order to the mobile station
2 after receiving the Page Response Message with the Service Option =
3 0.
4 2. The mobile station sends a Page Response Message/Origination Message with
5 the Service Option = 33:
6 a. After the base station assigns a traffic channel, verify the mobile
7 station sends a Release Order with ORDQ=2.
8 h. Verify the mobile station and base station/PCF are now operating in the Null State.

10 The mobile station shall comply with steps g and h.
11 13.14 RLP Operation in Rayleigh Fading Environment

13 This test verifies data transfer under Rayleigh fading channel conditions. This test verifies that
14 RLP 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
16 the mobile station is able to successfully complete a network initiated dormant to active transition.
18 2.6.4.3 Traffic Channel Substate [See 4]

19 2.2.1 RLP Requirements [See 15]
20 2.2.2 Service and Call Control Procedures [See 15]

21 2.2.7 High Speed Operation [See 15]
23 None
26 b. Set the channel simulator using the parameters as specified in Table 3.5.4-4.
27 c. Ensure the mobile station currently has a PPP session established and is in the
28 dormant state.
29 d. Instruct the base station to initiate a dormant to active transition.
30 e. Verify the mobile station is able to transition to the active state.

31 f. Initiate a forward data transfer to the mobile station.
32 g. Verify the file transfer completes successfully.
33 h. Initiate a reverse data transfer from the mobile station.
34 i. Verify the file transfer completes.
35 j. Repeat steps c through i changing the channel simulator setting to one path at 3 km/hr.
13-29
C.S0044-0 v1.0

2 The mobile station shall comply with steps e, g, i, and j.
3 13.15 Release Order Processing
5 This test case verifies the mobile station correctly processes the Release Order with ORDQ=2
6 when received on the f-csch.

9 3.7.4 Orders
14
15
13-30
C.S0044-0 v1.0
MS BS
Origination Message
Acknowledgment Order
Release Order with

ORDQ=2
The mobile station may

originate another call using a
different service option (e.g
Origination Message with SO12)
new service option
Acknowledgment Order
Extended Channel Assignement

Message
TCH

4 a. Configure the network to not allow Service Option 33 calls for the mobile station. (Note:
5 The network has packet data resources available, however the mobile station is not
6 authorized to use them.)
7 b. Instruct the mobile station to originate a Service Option 33 call.
8 c. Instruct the base station to send a Release Order with ORDQ = 2 to mobile station
9 indicating the requested service option has been rejected.
10 d. Verify the mobile station returns to the System Determination Substate or the Mobile
11 Station Idle State.
12 e. The mobile station may autonomously attempt to originate another data service option
13 (e.g. SO=12).
14 f. If the mobile station originates another service option and:

15 1. The base station supports that service option and has resources available, and
13-31
C.S0044-0 v1.0
1 2. The mobile station is authorized to use that service option, verify the following:
2 a. The new data call with the different service option is completed
3 successfully.

5 The mobile station shall comply with step d. If the mobile station supports step e, the mobile
6 station shall comply with step f.
7 13.16 Hysteresis Activation Timer
9 This test case verifies the mobile station implementation of Hysteresis Activation Timer. The
10 value of this timer is mobile station implementation dependent in the range of 0 to 30 seconds.

12 2.2.2.1.2.4 Dormant State

14 None
16 a. Connect the mobile station to the base station as shown in Figure A-5. Configure base
17 station 1 and base station 2 to transmit different non-zero values of PACKET_ZONE_ID
18 field in Extended System Parameters Message or ANSI-41 System Parameters
19 Message. Connect both the base stations to same PDSN.
20 b. Allow the mobile station to go idle on base station 1. Instruct the mobile station to
21 originate a Service Option 33 call on base station 1. Transfer data on the Service
22 Option 33 call (e.g. perform ftp or ping).
23 c. Ensure that length of the packet zone list is set to one entry at the mobile station.
24 Ensure packet zone hysteresis is enabled at the mobile station.
25 d. Allow Mobile Station to go dormant on base station 1. For rest of the test ensure that
26 the mobile station does not have any data to send.
27 e. While the hysteresis activation timer is running perform following operations:
28 1. Allow Mobile Station to perform an idle handoff to base station 2. Verify that the
29 mobile station sends an Origination Message with DRS field set to ‘0’ to base
30 station 2.
33 station 1.

35 The mobile station shall comply with step e
13-32
C.S0044-0 v1.0
1 13.17 Hysteresis Timer
3 This test case verifies the mobile station implementation of Hysteresis Timer. The value of this
4 timer is mobile station implementation dependent in the range of 0 to 60 seconds.

6 2.2.5 Packet Zone Reconnection Control

8 None

10 a. Connect the mobile station to the base station as shown in Figure A-5. Configure base
11 station 1 and base station 2 to transmit different non-zero values of PACKET_ZONE_ID
12 field in Extended System Parameters Message or ANSI-41 System Parameters
13 Message. Connect both the base stations to same PDSN.
14 b. Allow the mobile station to go idle on base station 1. Instruct the mobile station to
15 originate a Service Option 33 call on base station 1. Transfer data on the Service
16 Option 33 call (e.g. perform ftp or ping).
17 c. Ensure that length of the packet zone list is set to one entry at the mobile station.
18 Ensure packet zone hysteresis is enabled at the mobile station.
19 d. Allow Mobile Station to go dormant on base station 1. Allow mobile station to remain in
20 dormant state for duration of the hysteresis activation timer. For rest of the test ensure
21 that the mobile station does not have any data to send.
22 e. Perform following operations within duration less than the value of hysteresis timer
23 configured at the mobile station:
26 station 2.
28 mobile station does not send an Origination Message.
29 f. Allow Mobile Station to remain idle on base station 1 for duration more than the value of
30 hysteresis timer configured at the mobile station. Verify that the mobile station sends an
31 Origination Message with DRS field set to ‘0’ to base station 1. Verify that the duration
32 between the Origination Message in step d.1 and the Origination Message in step e is
33 approximately equal to the value of hyesteresis timer configured at the mobile station.

35 The mobile station shall comply with steps e and f.
36
13-33
C.S0044-0 v1.0
1 14 OVER-THE-AIR SERVICES
2 14.1 OTASP Download Request Processing
3 14.1.1 Definition
4 This test verifies a mobile station can initiate programming procedure and update its NAM
5 parameters.
7 3.2.1 User-Initiated Procedure

8 3.5.1 Message Contents
9 3.5.2 NAM Parameter Blocks

11 4.3 Programming Data Download

14 4.5.4 Validation Parameter Blocks

16 None
19 b. Confirm that the mobile station is programmed with a non-zero SPCp.
20 c. Setup a mobile originated OTASP call using *228 + one of the System Selection Codes
21 in Table 14.1.4-1.
14-1
C.S0044-0 v1.0
1 Table 14.1.4-1
Selected System Code
800 MHz A-BAND 00
800 MHz B-BAND 01
1.9 GHz A Block 02
1.9 GHz B Block 03
1.9 GHz C Block 04
1.9 GHz D Block 05
1.9 GHz E Block 06
1.9 GHz F Block 07
JTACS, A-Band 10
JTACS, B-Band 11
2 GHz Band 23
2
3 d. Upon call setup, instruct the base station to send a Protocol Capability Request
4 Message to the mobile station.
5 e. Verify the mobile station sends a Protocol Capability Response Message to the base
6 station with MOB_FIRM_REV, MOB_MODEL, BAND_MODE_CAP and all supported
7 FEATURE_ID and FEATURE_P_REV as listed in ANNEX C. The NAM Download
8 feature support is required for this test.
9 f. If Service Programming Lock is supported, perform the following:
10 1. Instruct the base station to send a Validation Request Message with BLOCK_ID
11 = ’00000000’ and SPC = SPCP.
12 2. Verify the mobile station sends a Validation Response Message within 750 ms,
13 and with BLOCK_ID = ’00000000’ and RESULT_CODE = ’00000000’ (Accepted
14 – Operation Successful).
15 g. If the Key Exchange is not supported, go to step h; otherwise:
16 1. Instruct the base station to send an Mobile Station Key Request Message to the
17 mobile station.
18 2. Verify the mobile station responds with a Mobile Station Key Response Message
19 within 30 seconds, with RESULT_CODE = '00000000' (Accepted - Operation
20 Successful).
21 3. Instruct the base station to send a Key Generation Request Message to the
22 mobile station.
14-2
C.S0044-0 v1.0
1 4. Verify the mobile station responds with a Key Generation Response Message
2 within 30 seconds and the RESULT_CODE = '00000000' (Accepted - Operation
3 Successful).
4 5. Verify the base station and the mobile station successfully perform SSD update
5 procedures.
6 6. Verify the base station sends the Re-Authenticate Request Message and the
7 mobile responds with the Re-Authenticate Response Message within 750ms.
8 7. At the base station verify Re-Authentication is successful.
9 8. The base station may enable Signaling Message Encryption and Voice Privacy.
10 h. Instruct the base station to send a Configuration Request Message with one or more of
11 the following NAM Parameter Block Types:
12
Parameter Block Type BLOCK_ID
CDMA/Analog NAM ‘00000000’
Mobile Directory Number ‘00000001’
CDMA NAM ‘00000010’
IMSI_T ‘00000011’
13 i. Verify the mobile station sends a Configuration Response Message within 750ms
14 including each requested BLOCK_ID and associated PARAM_DATA with
15 corresponding RESULT_CODE.
16 j. Instruct the base station to send a Download Request Message with one or more of the
17 following NAM Parameter Block Types and the corresponding PARAM_DATA:
18
CDMA NAM ‘00000010’
IMSI_T ‘00000011’
19 k. Verify the mobile station sends a Download Response Message and that
20 RESULT_CODE = '00000000' (Accepted- Operation Successful) within 750ms.
21 l. Instruct the base station to send a Commit Request Message to the mobile station.
22 m. Verify the mobile station sends a Commit Response Message to the base station within
23 10 seconds with the RESULT_CODE = '00000000' (Accepted- Operation Successful).

25 o. Verify the mobile station successfully stored the updated NAM information.
14-3
C.S0044-0 v1.0
1 p. Setup a mobile station originated call and verify user traffic is present.

3 The mobile station shall comply with steps e, i, k, m, o, and p. If supported the mobile station shall
4 comply with steps f and i. The mobile station shall update its NAM information as received in the
5 Download Request Message.
6 14.2 OTASP PUZL Download Request Processing
7 14.2.1 Definition
8 This test verifies a mobile station can initiate programming procedure and update its Preferred
9 User Zone List (PUZL).

13 3.5.6 PUZL Parameter Blocks
14 3.5.7 Preferred User Zone List (PUZL)
19 4.5.6 PUZL Parameter Blocks

21 None


25 c. Setup a mobile station originated OTASP call using *228 + one of the System Selection
26 Codes in Table 14.1.4-1.
31 FEATURE_ID and FEATURE_P_REV as listed in ANNEX C. The Preferred User Zone
32 List feature support is required for this test.
14-4
C.S0044-0 v1.0
2 = ’00000000’ and SPC = SCPp.
6 g. Instruct the base station to send a PUZL Configuration Request Message to the mobile
7 station with one of the following BLOCK_ID values:
8
PUZL Parameter Block Type BLOCK_ID
PUZL Dimensions ‘00000000’
PUZL Priorities ‘00000001’
User Zone ‘00000010’
Preferred User Zone List ‘00000011’
9 h. Verify the mobile station sends a PUZL Configuration Response Message within 750ms
10 with the BLOCK_ID and associated PARAM_DATA requested in the PUZL
11 Configuration Request Message.
12 i. Instruct the base station to send a PUZL Download Request Message with one or more
13 of the following PUZL Parameter Block Types and the corresponding PARAM_DATA:
14
User Zone Insert ‘00000000’
User Zone Update ‘00000001’
User Zone Delete ‘00000010’
User Zone Priority Change ‘00000011’
PUZL Flags ‘00000100’
15 j. Verify the mobile station sends a PUZL Download Response Message within 750ms
16 with the RESULT_CODE = ’00000000’ (Accepted – Operation Successful).
17 k. Instruct the base station to send a Commit Request Message to the mobile station.
18 l. Verify the mobile station sends a Commit Response Message to the base station within
20 m. End the call at the mobile station.

21 n. Verify the mobile station successfully stored the updated PUZL information.

23 The mobile station shall comply with steps e, h, j, l, and n. The mobile station shall update its
24 PUZL information as received in the PUZL Download Request Message.
14-5
C.S0044-0 v1.0
1 14.3 OTASP 3GPD Download Request Processing
2 14.3.1 Definition
3 This test verifies a mobile station can initiate programming procedure and update its 3GPD
4 information.

8 3.5.8 3GPD Parameter Blocks


13 4.5.7 3GPD Parameter Blocks

15 None

18 b. Confirm that the mobile station is programmed with a non-zero SPCp .
25 FEATURE_ID and FEATURE_P_REV as listed in ANNEX C. The 3G Packet Data
26 feature support is required for this test.
29 = ’00000000’ and SPC = SPCp.
33 g. Instruct the base station to send a 3GPD Configuration Request Message to the mobile
34 station with one or more of the following 3GPD Parameter Block Types from Table
14-6
C.S0044-0 v1.0
1 14.3.4-1. If the 3GPD Parameter Block Type requests the shared secret do the
2 following prior to sending the 3GPD Configuration Request Message:
3 h. Instruct the base station to send a Secure Mode Request Message with
4
Field Value
START_STOP ‘1’
KEY_IN_USE ‘0000’ or ‘0001’
RAND_SM Randomly selected value

for SMCK
5 1. Verify the mobile station sends a Secure Mode Response Message within 750ms
6 with RESULT_CODE = ’00000000’ (Accepted – Operation Successful).
7
14-7
C.S0044-0 v1.0
1 Table 14.3.4-1
3GPD Parameter Block Type BLOCK_ID
3GPD Operation Capability ‘00000000’

Parameters
3GPD Operation Mode ‘00000001’

Parameters
SimpleIP Capability Parameters ‘00000010’
MobileIP Capability Parameters ‘00000011’
SimpleIP User Profile Parameters ‘00000100’
Mobile IP User Profile Parameters ‘00000101’
SimpleIP Status Parameters ‘00000110’
MobileIP Status Parameters ‘00000111’
SimpleIP PAP SS Parameters1 ‘00001000’
SimpleIP CHAP SS Parameters1 ‘00001001’

1
MobileIP SS Parameters ‘00001010’
HRPD Access Authentication ‘00001011’

Capability Parameters
HRPD Access Authentication User ‘00001100’

Profile Parameters

CHAP SS Parameters1
1
The shared secret parameters shall not be transmitted over the
air unencrypted.
2
3 i. Verify the mobile station sends a 3GPD Configuration Response Message within
4 750ms including each requested BLOCK_ID and associated PARAM_DATA with
5 corresponding RESULT_CODE. If SECURE_MODE_INDs = ‘1’, then:
6 1. Verify the mobile station includes the following in the 3GPD Configuration
7 Response Message:
14-8
C.S0044-0 v1.0
Field Value
FRESH_INCL ‘1’
FRESH 15-bit value used for

encryption
1 j. Instruct the base station to send a 3GPD Download Request Message with one or more
2 of the 3GPD Parameter Block Types from Table 14.3.4-2 and the corresponding
3 PARAM_DATA. If SECURE_MODE_INDs = ‘1’, then:
4 1. Verify the base station includes the following in the 3GPD Download Request
5 Message:
6
Field Value
FRESH_INCL ‘1’
FRESH 15-bit value used for

encryption
8 Table 14.3.4-2
3GPD Operation Mode ‘00000000’

Parameters
SimpleIP User Profile Parameters ‘00000001’
Mobile IP User Profile Parameters ‘00000010’
SimpleIP Status Parameters ‘00000110’
MobileIP Status Parameters ‘00000111’
SimpleIP PAP SS Parameters1 ‘00001000’
SimpleIP CHAP SS Parameters1 ‘00001001’
MobileIP SS Parameters1 ‘00001010’
HRPD Access Authentication User ‘00001011’

Profile Parameters

CHAP SS Parameters1
1
The shared secret parameters shall not be transmitted over the
air unencrypted.
9 k. Verify the mobile station sends a 3GPD Download Response Message within 750ms
14-9
C.S0044-0 v1.0
1 l. Instruct the base station to send a Commit Request Message to the mobile station.
2 m. Verify the mobile station sends a Commit Response Message to the base station within
5 o. Verify the mobile station successfully stored the 3GPD information.

7 The mobile station shall comply with steps e, h, k, m and o. If SECURE_MODE_INDs = ‘1’, the
8 mobile station shall comply with step g. The mobile station shall update its 3GPD information as
9 received in the 3GPD Download Request Message.
10 14.4 OTASP SSPR Download Request Processing
12 This test verifies a mobile station can initiate programming procedure and update its preferred
13 roaming list.

17 3.5.3 SSPR Parameter Blocks
18 3.5.5 Preferred Roaming List and Extended Preferred Roaming List

25 None

29 c. Setup a mobile originated OTASP call using *228 + one of the System Selection Codes
30 in Table 14.1.4-1.
14-10
C.S0044-0 v1.0
3 FEATURE_ID and FEATURE_P_REV as listed in ANNEX C. The System Selection for
4 Preferred Roaming feature support is required for this test.
7 = ’00000000’ and SPC = SCPp.
11 g. Instruct the base station to send a SSPR Configuration Request Message to the mobile
12 station with one of the following SSPR Parameter Block Types:
13
SSPR Parameter Block Type BLOCK_ID
Preferred Roaming List ‘00000000’

Dimensions
Extended Preferred Roaming List ‘00000010’

Dimensions
14 h. Verify the mobile station sends a SSPR Configuration Response Message within
15 750ms with the BLOCK_ID and the associated PARAM_DATA.
16 i. Instruct the base station to send a SSPR Download Request Message with one of the
17 following SSPR Parameter Block Types and the corresponding PARAM_DATA:
18
Extended Preferred Roaming List ‘00000001’

with SSPR_P_REV greater than
‘00000001’
19 j. Verify the mobile station sends a SSPR Download Response Message within 750ms
21 k. Instruct the base station to send a Commit Request Message to the mobile station.
22 l. Verify the mobile station sends a Commit Response Message to the base station within
24 m. End the call at the mobile station.
25 n. Verify the mobile station successfully stored the updated SSPR information.
14-11
C.S0044-0 v1.0

2 The mobile station shall comply with steps e, h, j, l, and n. The mobile station shall update its
3 SSPR information as received in the SSPR Download Request Message.
4 14.5 OTASP For System Selection and Preferred Roaming - Oversize PRL
5 14.5.1 Definition
6 This test verifies that the PRL resident in a handset shall not be replaced if a new PRL of illegal
7 size is downloaded.

10

19 14.5.3 Call Flow

20 None
30 FEATURE_ID and FEATURE_P_REV as listed in ANNEX C. The System Selection for
31 Preferred Roaming feature support is required for this test.
14-12
C.S0044-0 v1.0
2 = ’00000000’ and SPC = SCPp.
6 g. Instruct the base station to send a SSPR Configuration Request Message to the mobile
7 station.
8 h. Verify the mobile station sends a SSPR Configuration Response Message within
9 750ms with the requested BLOCK_ID and the associated PARAM_DATA.
10 i. Instruct the base station to send a SSPR Download Request Message to the mobile
11 station with values of SEGMENT_OFFSET in conjunction with SEGMENT_SIZE that
12 are inconsistent with the preferred roaming list storage capabilities of the mobile station.
13 j. Verify the mobile station sends a SSPR Download Response Message with
14 RESULT_CODE = ’00001000’ (Rejected – Preferred roaming list length mismatch).
15 k. Verify the mobile station does not transfer its new PR_LIST to semi-permanent memory
16 after receiving a Commit Request Message.
17 l. End call at the mobile station

19 The mobile station shall comply with step h, j, and k. The mobile station shall retain its original
20 PRL.
21 14.6 OTAPA Download Request Processing
23 This test verifies that the mobile station supports network initiated Over-the-Air-Parameter-
24 Administration (OTAPA). This test also verifies the mobile station’s download request processing
25 is successful.

27 3.2.2 Network-Initiated Procedure
28 3.4 Termination of the Programming Procedure

14-13
C.S0044-0 v1.0

3 None

7 c. Initiate an OTAPA session from the base station by sending a General Page Message
8 to the mobile station with the SERVICE_OPTION = 0x12 or 0x13.
9 d. Verify that the mobile station sends a Page Response Message with
10 SERVICE_OPTION = 0x12 or 0x13.
11 e. Upon successful call setup, instruct the base station to send an OTAPA Request
12 Message to the mobile station with START_STOP = ’1’.
13 f. Verify the mobile station sends an OTAPA Response Message to the base station
14 within 750 ms with RESULT_CODE = ’00000000’ (Accepted – Operation Successful). If
15 NAM_LOCK_IND = ’1’ in the OTAPA Response Message, perform the following:
16 1. Verify the RAND_OTAPA field is present in the OTAPA Response Message.
17 2. Instruct the base station to sends a Validation Request Message with BLOCK_ID
18 = ’00000010’ (Validate SPASM) and a SPASM Parameter Block present to the
19 mobile station.
20 3. Verify the mobile station sends a Validation Response Message to the base
21 station within 750 ms, and with BLOCK_ID = ’00000010’ (Validate SPASM) and
22 RESULT_CODE = ’00000000’ (Accepted – Operation Successful).
23 g. Instruct the base station to send a Protocol Capability Request Message to the mobile
24 station.
25 h. Verify the mobile station sends a Protocol Capability Response Message to the base
27 FEATURE_ID and FEATURE_P_REV as listed in ANNEX C.
28 i. If Service Programming Lock is supported, perform the following:
30 = ’00000000’ and SPC = SPCP.
34 3. Verify the base station sends a Validation Request Message with BLOCK_ID =
35 ’00000001’ (Change SPC) and SPC = {a new SPC}.
14-14
C.S0044-0 v1.0
2 and with BLOCK_ID = ’00000001’ (Change SPC) and RESULT_CODE =
3 ’00000000’ (Accepted – Operation Successful).
4 j. If the Electronic Key Exchange is not supported, go to step k; otherwise:
5 1. Instruct the base station to send an Mobile Station Key Request Message to the
6 mobile station.
7 2. Verify the mobile station responds with the Mobile Station Key Response
8 Message within 30 seconds, with RESULT_CODE = '00000000' (Accepted -
9 Operation Successful).
10 3. Instruct the base station to send a Key Generation Request Message to the
11 mobile station.
12 4. Verify the mobile station responds with the Key Generation Response Message
13 within 30 seconds and the RESULT_CODE = '00000000' (Accepted - Operation
14 Successful).
15 5. Verify the base station and the mobile station successfully perform SSD update
16 procedures.
17 6. Verify the base station sends the Re-Authenticate Request Message and the
18 mobile station responds with the Re-Authenticate Response Message.
19 7. At the base station verify Re-Authentication is successful.
20 8. The base station may enable Signaling Message Encryption and Voice Privacy.
21 k. Instruct the base station to send a Configuration Request Message with one or more of
22 the following NAM Parameter Block Types:
23
CDMA NAM ‘00000010’
IMSI_T ‘00000011’
24 l. Verify the mobile station sends a Configuration Response Message within 750ms
25 including each requested BLOCK_ID and associated PARAM_DATA with
26 corresponding RESULT_CODE.
27 m. Instruct the base station to send a Download Request Message with one or more of the
28 following NAM Parameter Block Types and the corresponding PARAM_DATA:
29
14-15
C.S0044-0 v1.0
CDMA NAM ‘00000010’
IMSI_T ‘00000011’
1 n. Verify that the mobile station sends a Download Response Message and that
2 RESULT_CODE = '00000000' (Accepted- Operation Successful) within 750ms.
3 o. Instruct the base station to send a Commit Request Message to the mobile station.
4 p. Verify the mobile station sends a Commit Response Message to the base station within
6 q. Instruct the base station to send an OTAPA Request Message to the mobile station with
7 START_STOP = ’0’.
8 r. Verify the mobile station sends an OTAPA Response Message to the base station
9 within 750 ms, and with RESULT_CODE = ’00000000’ (Accepted – Operation
10 Successful) and NAM_LOCK_IND = ’0’.
11 s. Verify that the mobile station releases the call.
12 t. Verify the mobile station successfully stored the updated NAM information.
13 u. Originate a call from the mobile station and verify user traffic is present.
14 v. End the call.
15 w. Setup a mobile station originated call.
16 x. Repeat steps e through u with the mobile station already in the Conversation Substate.

18 The mobile station shall comply with steps d, f, h, l, n, p, r, and t. If supported the mobile station
19 shall comply with steps i and l.
20 14.7 Call Origination during an OTAPA Download Session
22 This test verifies that the mobile station is able to originate a voice call during an OTAPA
23 download session.


14-16
C.S0044-0 v1.0


4 None

8 c. Initiate an OTAPA session from the base station by sending a General Page Message
9 to the mobile station with the SERVICE_OPTION = 0x12 or 0x13.
10 d. Verify that the mobile station sends a Page Response Message with
11 SERVICE_OPTION = 0x12 or 0x13.
12 e. Upon successful call setup, instruct the base station to send an OTAPA Request
13 Message to the mobile station with START_STOP = ’1’.
14 f. Verify the mobile station sends an OTAPA Response Message to the base station
15 within 750 ms with RESULT_CODE = ’00000000’ (Accepted – Operation Successful). If
16 NAM_LOCK_IND = ’1’ in the OTAPA Response Message, perform the following:
17 1. Verify the RAND_OTAPA field is present in the OTAPA Response Message.

19 = ’00000010’ (Validate SPASM) and a SPASM Parameter Block present to the
20 mobile station.
21 3. Verify the mobile station sends a Validation Response Message to the base
22 station within 750 ms, and with BLOCK_ID = ’00000010’ (Validate SPASM) and
23 RESULT_CODE = ’00000000’ (Accepted – Operation Successful).
24 g. Instruct the base station to send a Protocol Capability Request Message to the mobile
25 station.
26 h. Verify the mobile station sends a Protocol Capability Response Message to the base
28 FEATURE_ID and FEATURE_P_REV as listed in ANNEX CY.
29 i. Originate a voice call from the mobile station.
30 j. Verify user data in both directions.
31 k. End call at the mobile station.

33 The mobile station shall comply with steps d, f, h, and j.
14-17
C.S0044-0 v1.0
1 15 POSITION DETERMINATION TESTS

2 The position determination tests in this section apply to mobile stations and base stations that can
3 operate in various modes including GPS (Global Positioning System), AFLT (Advanced Forward
4 Link Trilateration), and Hybrid (GPS and AFLT). Note that for mobile stations that are capable of
5 calculating their location based on AFLT, that capability is not verified in this test.
6 15.1 Position Determination Tests for GPS, AFLT and Hybrid
7 15.1.1 Definition
8 The purpose of this test is to determine the interoperability of mobile station and base station
9 position determination sessions. This test requires that a network originated position
10 determination session be triggered by a mobile station originated call.

12 3.2.1 Position Determination Data Message Processing
13 3.2.2 Point-to-point Procedures
14 3.2.4 Reverse Link Message Format
15 3.2.4.2 Response Element Response Type
16 Annex B Request/Response Element Types
17 15.1.3 15.1.3 Call Flow Example(s)

18 None
19 15.1.4 15.1.4 Method of Measurement

20 a. Configure 3 base stations available to the mobile station. Ensure connectivity of the
21 base stations to a PDE. The base stations and the PDE shall be configured to allow a
22 specific mobile station originated call type to trigger the PDE to start a position
23 determination session with the mobile station (e.g. an emergency call; in the U.S. this
24 would be a 9-1-1 call).
25 b. Allow the mobile to become idle on the base station with a dominant PN, with mobile
26 CDMA receive power greater than -85 dBm and pilot Ec/Io greater than -12 dB.
27 c. If the mobile station and base station supports GPS position location, allow the mobile
28 station to receive GPS signals each with a power level of at least -130 dBm/1MHz. The
29 number of simulated GPS satellites shall be 4 or greater.
30 d. Setup a mobile station originated call using a dialed number or Service Option that
31 triggers the PDE to start a position determination session (e.g. an emergency call; in
32 the U.S. this would be a 9-1-1 call).
33 e. Verify the call completes.
34 f. Verify steps g through n. Note that the ordering of steps g through n does not represent
35 a required ordering of call flow events during the test. In addition to the messages
36 listed in steps g through n, there may be other position determination request elements
15-1
C.S0044-0 v1.0
1 and response elements exchanged between the base station and mobile station during
2 the test.
3 g. If the base station sends a position determination Data Burst Message with burst type
4 ‘000101’ that includes a Position Determination Data Message with Request Mobile
5 Station Information (REQ_TYPE = ‘0010’), verify the mobile station sends a position
6 determination Data Burst Message with a burst type ‘000101’ that includes a Position
7 Determination Data Message with Provide Mobile Station Information (RESP_TYPE =
8 ‘0010’).
9 h. If the mobile station and base station supports GPS position determination and the
10 base station has previously set GPSC_ID to ‘1’ in the Provide Base Station Capability,
11 and if the mobile station has sent a position determination Data Burst Message with
12 burst type ‘000101’ that includes a Position Determination Data Message with Request
13 GPS Acquisition Assistance (REQ_TYPE = ‘0100’), verify the base station sends a
14 position determination Data Burst Message with a burst type ‘000101’ that includes a
15 Position Determination Data Message with Provide GPS Acquisition Assistance
16 (RESP_TYPE = ‘0100’) or a Reject Message with REJ_REASON set to ‘001’.
17 i. If the mobile station and base station supports GPS position determination and the
21 GPS Sensitivity Assistance (REQ_TYPE = ‘0101’), verify the base station sends a
22 position determination Data Burst Message with a burst type ‘000101’, that includes a
23 Position Determination Data Message with Provide GPS Sensitivity Assistance
24 (RESP_TYPE = ‘0101’) or a Reject Message with REJ_REASON set to ‘001’.
25 j. If the mobile station and base station supports GPS position determination and the
29 GPS Almanac (REQ_TYPE = ‘1000’), verify the base station sends a position
30 determination Data Burst Message with a burst type ‘000101’ that includes a Position
31 Determination Data Message with Provide GPS Almanac (RESP_TYPE = ‘1000’) or a
32 Reject Message with REJ_REASON set to ‘001’.
33 k. If the mobile station and base station supports GPS position determination and the
34 base station has previously set GPSC_ID to ‘1’ in the Provide Base Station Capability,,
37 GPS Ephemeris (REQ_TYPE = ‘1001’), verify the base station sends a position
38 determination Data Burst Message with a burst type ‘000101’, that includes a Position
39 Determination Data Message with Provide GPS Ephemeris (RESP_TYPE = ‘1001’) or a
40 Reject Message with REJ_REASON set to ‘001’.
41 l. If the mobile station and base station supports GPS position determination, and the
42 mobile station is capable of calculating its position based on GPS measurements as
43 indicated by LOC_CALC_CAP (Position Calculation Capability) field in the Provide
15-2
C.S0044-0 v1.0
1 Mobile Station Information Response Element, and the base station has sent a position
2 determination Data Burst Message with burst type ‘000101’ that includes a Position
3 Determination Data Message with Request Location Response (REQ_TYPE = ‘0001’),
4 verify the mobile station sends a position determination Data Burst Message with a
5 burst type ‘000101’, that includes a Position Determination Data Message with Provide
6 Location Response (RESP_TYPE = ‘0001‘).
7 m. If the mobile station and base station supports GPS position determination, and the
8 base station has sent a position determination Data Burst Message with burst type
9 ‘000101’ that includes a Position Determination Data Message with Request
10 Pseudorange Measurement (REQ_TYPE = ‘0100’), verify the mobile station sends a
11 position determination Data Burst Message with a burst type ‘000101’, that includes a
12 Position Determination Data Message with Provide Pseudorange Measurement
13 (RESP_TYPE = ‘0100‘).
14 n. If the base station supports AFLT position determination, and the base station has sent
15 a position determination Data Burst Message with burst type ‘000101’ that includes a
16 Position Determination Data Message with Request Pilot Phase Measurement
17 (REQ_TYPE = ‘0101’), verify the mobile station sends a position determination Data
18 Burst Message with a burst type ‘000101’, that includes a Position Determination Data
19 Message with Provide Pilot Phase Measurement (RESP_TYPE = ‘0101‘).
21 The mobile station and base station shall comply with the requirements in the following steps:
22 For GPS position location the base station shall comply with steps h, i, j, k, l and the mobile
23 station shall comply with steps g, l and m.
24 For AFLT position location the base station shall comply with step l and the mobile station shall
25 comply with steps g and n.
26 For Hybrid position location the base station shall comply with steps h, i, j, and k, and the mobile
27 station shall comply with steps g, l, m, and n.
15-3
C.S0044-0 v1.0
1 16 CONCURRENT SERVICES
2 16.1 Setup Mobile Station Originated Data Call while Voice Call or Teleservice Call is in
3 Progress
4 16.1.1 Definition
5 This test verifies that, when a voice call is already in progress, a mobile station originated data
6 call or teleservice call can be established successfully.
8 2.6.4.1.2.2.5 Waiting for Service Action Time Subfunction)

9 2.6.4.1.12 Processing the Service Configuration Record)

13 2.6.10 Call Control Processing

15 2.7.2.3.2.32 Enhanced Origination Message
16 2.7.2.3.2.33 Extended Flash With Information Message
17 2.7.2.3.2.37 Call Cancel Message

18 2.7.2.3.2.29 Resource Release Request Message
19 2.7.2.3.2.30 Resource Release Request Mini Message
20 2.7.3.4 Mobile Station Reject Order

21 2.7.4.25 Capability Information
22 3.6.4.1.7 Response to Enhanced Origination Message
23 3.6.4.1.8 Processing Resource Release Request Message and Resource Release
24 Request Mini Message

27 3.6.8 Call Control Processing
29 3.7.2.3.2.30 ANSI-41 System Parameters Message

16-1
C.S0044-0 v1.0

2 3.7.3.3.2.43 Call Assignment Message
3 3.7.3.3.2.44 Extended Alert With Information Message

MS BS
Traffic Traffic
Voice Call in Progress

MS initiates data
calll setup 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

9 b. Setup a voice call as described in Test and wait until the voice call is in progress.
10 c. Ensure retry delay for call origination (i.e. RETRY_DELAYs[001]) is currently not set for
11 the data service option.
12 d. Initiate a packet data call (e.g. SO33) at the mobile station. Verify the following:
13 1. The mobile station sends an Enhanced Origination Message with the following
14 fields set as follows:
FIELD VALUE
16-2
C.S0044-0 v1.0
TAG ‘0001’
SR_ID ‘001’ or ‘010’.
SERVICE_OPTION Service Option corresponding to the

data call (e.g. SO33)
DRS ‘1’ (data ready to send)
1 e. Configure the base station to accept the call origination from the mobile station. Verify
2 that base station follows one of the following two sequences of events to establish the
3 data call:
4 1. The base station sends the call assignment prior to service option connection
5 establishment as follows:
6 a. The base station sends a Call Assignment Message to the mobile
7 station, prior to the expiration of the enhanced origination timer at the
8 mobile station, with the following fields set as follows:
FIELD VALUE
RESPONSE_IND ‘1’ (Response to mobile station call

request)
TAG Value received in the Enhanced

Origination Message
ACCEPT_IND ‘1’ (call request accepted)
CON_REF Connection reference value for this call
9
10 b. Upon successful call assignment, service negotiation is initiated to
11 establish the service option connection corresponding to this call
12 assignment, as follows:
13 1. The service negotiation is terminated via sending a Service
14 Connect Message, General Handoff Direction Message
15 (containing a SCR), or Universal Handoff Direction Message
16 (containing a SCR).
17 2. If the Service Connect Message or the Universal Handoff
18 Direction Message is used to terminate the service negotiation,
19 the call assignment included (CC_INFO_INCL) field is set to ‘0’
20 in these messages.
21 3. The service option connection is established with the same
22 connection reference (CON_REF) as used in the corresponding
23 Call Assignment Message.
16-3
C.S0044-0 v1.0
1 c. After the action time of the message used to establish the service
2 option connection corresponding to this call, data call user traffic is
3 exchanged successfully.
4 d. The voice call is not dropped.
5 2. The base station sends the call assignment as part of the service option
6 connection establishment as follows:
7 a. The base station initiates service negotiation to establish the service
8 option connection and assign the call. The service negotiation is
9 terminated via sending a Service Connect Message or Universal
10 Handoff Direction Message (containing a SCR) with the following fields
11 set as follows:
12
FIELD VALUE
CC_INFO_INCL ‘1’ (call assignment included)
NUM_CALLS_ASSIGN ‘00000001’ (single call assignment)
CON_REF Connection reference corresponding to this

call set to the same value as used in the
SCR.
RESPONSE_IND ‘1’ (Response to mobile station call request)
TAG Value received in the Enhanced Origination

Message
13
14 b. After the action time of the message used to establish the service
17 c. The voice call is not dropped.
18 f. Repeat steps b to e with the following modifications:
19 1. In step b, setup a teleservice call (e.g. SMS, Position Determination, etc.)
20 requiring dedicated channels.
21 2. In step e, the teleservice call is not dropped after the establishment of the data
22 call.

24 The mobile station and base station shall comply with the requirements in the following steps d, e
25 and f.
16-4
C.S0044-0 v1.0
1 16.2 Setup Mobile Station terminated Data Call while Voice Call or Teleservice Call is in
2 Progress
3 16.2.1 Definition
4 This test verifies that, when a voice call is already in progress, a mobile station terminated data
5 call (for a dormant data session) or teleservice call can be established successfully.
7 See 16.1.2.

9
MS BS
Traffic Traffic
Network initiates
Voice Call in Progress data calll setup
(for a dormant
data session)
(RESPONSE_IND=0,
Data SOY, CON_REFY)
SCM / GHDM / UHDM

(SCR += (Data SOY, CON_REFY)
OR
SCM/ UHDM
(CC_INFO_INCL=1,
RESPONSE_IND=0,
SCR += (Data SOY, CON_REFY))
Voice & Data

Call in Progress
Traffic Traffic
10
11

14 b. Setup a packet data call (e.g. SO33). Ensure that the data call transitions to the
15 dormant state. Ensure that the dedicated traffic channels are released.
16 c. Setup a voice call and wait until the voice call is in progress.
16-5
C.S0044-0 v1.0
1 d. Trigger network-initiated transition to active state for the dormant packet data call.
2 Verify that base station follows one of the following two sequence of events to establish
3 the data call:
7 station with the following fields set as follows:
FIELD VALUE
RESPONSE_IND ‘0’ (base station initiated call

assignment)
BYPASS_ALERT_ANSWER ‘1’ (since data call)
SO Service option number corresponding

to the data service (e.g. SO33)


25 d. The voice call is not dropped.
16-6
C.S0044-0 v1.0

2 set as follows:
Field Value

SCR.
RESPONSE_IND ‘0’ (base station initiated call assignment)
BYPASS_ALERT_ANSWER ‘1’ (since data call)
6 c. The voice call is not dropped .

7 e. Repeat steps b to d with the following modifications:
10 2. In step d, the teleservice call is not dropped after the establishment of the data
11 call.

13 The mobile station and base station shall comply with the requirements in steps d and e.
14 16.3 Setup Mobile Station Originated Voice Call while Data Call or Teleservice Call is in
15 Progress
17 This test verifies that, when a data call is already in progress, a mobile station originated voice
20 See 16.1.2.
16-7
C.S0044-0 v1.0
MS BS
Traffic Traffic
Data Call in Progress

MS initiates voice
calll setup Enhanced Origination Message
(Voice SOY, TAGY)

(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

5 b. Setup a packet data call (e.g. SO33 as described in test case 13.2). Wait until the data
6 call is in progress. Ensure sufficient traffic is exchanged to keep the data instance in
7 active state.
8 c. Initiate a voice call at the mobile station. Verify the following:
9 1. The mobile station sends an Enhanced Origination Message with the following
10 fields set as follows:
Field Value
TAG ‘0001’
SR_ID ‘010’
16-8
C.S0044-0 v1.0
SERVICE_OPTION Service Option corresponding to the

voice call (Ex. SO 3)
1
2 d. Configure the base station to accept the call origination from the mobile station. Verify
3 that base station follows one of the following two sequence of events to establish the
4 voice call:
8 station, prior to the expiration of the enhanced origination timer at the
9 mobile station, with the following fields set as follows:
10
Field Value
RESPONSE_IND ‘1’ (Response to mobile station call

request)
TAG Value received in the Enhanced

Origination Message
ACCEPT_IND ‘1’ (call request accepted)
11

27 option connection corresponding to this call, voice call user traffic is
16-9
C.S0044-0 v1.0
1 d. The data call is not dropped.

8 set as follows:
Field Value

SCR.
RESPONSE_IND ‘1’ (Response to mobile station call request)
TAG Value received in the Enhanced Origination

Message
9
11 option connection corresponding to this call, voice call user traffic is
13 c. The data call is not dropped
14 e. Repeat steps b to d with the following modifications:

17 2. In step d, the teleservice call is not dropped after the establishment of the data
18 call.

20 The mobile station shall comply with the requirements in steps c, d and e.
21 The base station shall comply with the requirements in step d.
22
16-10
C.S0044-0 v1.0
1 16.4 Setup Mobile Station terminated Voice Call while Data Call or Teleservice Call is in
2 Progress
3 16.4.1 Definition
4 This test verifies that, when a data call is already in progress, a mobile station terminated voice
7 See 16.1.2.
MS BS
Traffic Traffic
Data Call in Progress Network initiates

voice call setup
(RESPONSE_IND=0,
Voice SOY, CON_REFY)
SCM / GHDM / UHDM

(SCR += (Voice SOY, CON_REFY)
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
9
10

16-11
C.S0044-0 v1.0
1 b. Setup a packet data call (e.g. SO33 a described in test case 13.2). Wait till the data call
2 is in progress. Ensure sufficient traffic is exchanged to keep the data instance in active
3 state.
4 c. Trigger a network-initiated voice call. Verify that base station follows one of the
5 following two sequences of events to establish the voice call:
9 station with the following fields set as follows:
10
11
Field Value
RESPONSE_IND ‘0’ (base station initiated call

assignment)
BYPASS_ALERT_ANSWER ‘0’ (since voice call)
SO Service option number corresponding

to the voice service (Ex. SO 3)


27 option connection corresponding to this call, the mobile station plays
28 an alert to indicate an incoming call. After answering the call from the
29 mobile station, voice call user traffic is exchanged successfully.
30 d. The data call is not dropped.
16-12
C.S0044-0 v1.0
7 set as follows:
Field Value

SCR.
BYPASS_ALERT_ANSWER ‘0’ (since voice call)
8
10 option connection corresponding to this call, the mobile station plays
11 an alert to indicate an incoming call. After answering the call from the
12 mobile station, voice call user traffic is exchanged successfully.
13 c. The data call is not dropped .

14 d. Repeat steps b and c with the following modifications:
17 2. In step c, the teleservice call is not dropped after the establishment of the data
18 call.

20 The mobile station and base station shall comply with the requirements in steps c and d.
21
22 16.5 Mobile Station Release of a Single Call While Voice and Data Calls are in Progress
24 This test verifies that, when both voice and data calls are in progress, mobile station can release
25 one of the calls successfully and the other call continues uninterrupted.
16-13
C.S0044-0 v1.0
2 See 16.1.2.
MS BS
Traffic Traffic
MS initiates Voice & Data Calls

release of one of in Progress
the calls
Service Request Message
( SCR -= CON_REFY)
or
Resource Release Request Message

(CON_REFY)
SCM / GHDM / UHDM

(SCR -= CON_REFY)
Remaining Call Continues
Traffic Traffic

7 b. Setup both a voice call and a packet data call (e.g. SO33). Wait till both the voice call
8 and the data call are in progress. Ensure sufficient traffic is exchanged to keep the data
9 instance in active state.
10 c. Initiate the release of the voice call at the mobile station. Verify the following:
11 1. The mobile station sends a Service Request Message or Resource Release

12 Request (Mini) Message requesting the release of the voice call.
13 a. If the mobile station sends a Service Request Message, the service
14 option connection record corresponding to the voice call is omitted
15 from the Service Configuration information record included in this
16 message.
16-14
C.S0044-0 v1.0
1 b. If the mobile station sends a Resource Release Request (Mini)

2 Message, the following fields shall be set as follows:
3
Field Value
GATING_DISCONNECT_IND ‘0’ (release of a call requested)
CON_REF Connection reference

corresponding to the voice call to
be released
4 2. Upon receiving the Service Request Message or Resource Release Request

5 (Mini) Message requesting the release of the voice call, the base station sends a
6 Service Connect Message, General Handoff Direction Message (with a SCR), or
7 Universal Handoff Direction Message (with a SCR) as follows:
8 a. The service option connection record corresponding to the voice call is

9 omitted from the Service Configuration information record included in
10 this message.
11 3. At the action time of the Service Connect Message, General Handoff Direction
12 Message, or Universal Handoff Direction Message used to release the voice call,
13 the voice traffic no longer flows.
14 4. The data call is not dropped.

15 d. Repeat steps a though c with the following exception: in step c, initiate the release of
16 the data call at the mobile station. All the expected results are as in step c with the
17 difference that the call being released is the data call.

19 The mobile station and base station shall comply with the requirements in step c and d.
20 16.6 Base Station Release of a Single Call While Voice and Data Calls are in Progress
22 This test verifies that, when both voice and data calls are in progress, base station can release
23 one of the calls successfully and the other call continues uninterrupted.
25 See 16.1.2.
16-15
C.S0044-0 v1.0
MS BS
Traffic Traffic
Voice & Data Calls

in Progress
Network initiates
release of one of
SCM / GHDM / UHDM the calls
(SCR -= CON_REFY)
Remaining Call Continues
Traffic Traffic

5 b. Setup both a voice call and a packet data call (e.g. SO33). Wait till both the voice call
6 and the data call are in progress. Ensure sufficient traffic is exchanged to keep the data
7 instance in active state.
8 c. Trigger a network-initiated release of the voice call. Verify the following:
9 1. The base station sends a Service Connect Message, General Handoff Direction
10 Message (with a SCR), or Universal Handoff Direction Message (with a SCR),
11 where the service option connection record corresponding to the voice call is
12 omitted from the Service Configuration information record included in this
13 message.
14 2. At the action time of the Service Connect Message, General Handoff Direction
15 Message, or Universal Handoff Direction Message used to release the voice call,
16 the voice traffic no longer flows.
17 3. The data call is not dropped.
16-16
C.S0044-0 v1.0
1 d. Repeat steps a though c with the following exception: in step c, initiate the release of
2 the data call at the mobile station. All the expected results are as in step c with the
3 difference that the call being released is the data call.

5 The mobile station and base station shall comply with the requirements in steps c and d.
6 16.7 Correct Handling of Call Control Signaling
7 16.7.1 Definition
8 This test verifies that, when one or more calls are in progress, mobile station initiated and network
9 initiated call control signaling messages are handled correctly.
11 See 16.1.2.
16-17
C.S0044-0 v1.0
MS BS
Traffic Traffic
FWIM /
EFWIM (CON_REFINCL=0) /
EFWIM (CON_REFVOICE)
FWIM /
Add data call:

Voice & Data Calls in Progress
If voice SOC listed first in SCR:

FWIM /
FWIM /
If data SOC listed first in SCR:
Release Data Call:

FWIM /
FWIM /
Traffic Traffic
2
3

6 b. Setup a voice call and wait until the voice call is in progress.
16-18
C.S0044-0 v1.0
1 c. If applicable, trigger an action at the mobile station that will result in either a Flash With
2 Information Message or Extended Flash With Information Message for a voice call
3 being transmitted to the base station (Ex. Trigger an action that utilizes the Keypad
4 Facility information record). Verify the following:
5 1. The mobile station sends a Flash With Information Message, an Extended Flash
6 With Information Message with the CON_REF_INCL field set to ‘0’, or an
7 Extended Flash With Information Message with the CON_REF field set to the
8 connection reference corresponding to the voice call.
9 2. The information record is delivered correctly in the network.
10 d. If applicable, trigger an action at the network that will result in either a Flash With
11 Information Message or Extended Flash With Information Message being transmitted to
12 the mobile station (e.g. Trigger an action that utilizes the Display information record).
14 1. The base station sends a Flash With Information Message, an Extended Flash
18 2. The information record is correctly handled in the mobile station.

19 e. Setup a mobile station originated or mobile station terminated packet data call (e.g.
20 SO33). When the base station sends a Service Connect Message, General Handoff
21 Direction Message, or Universal Handoff Direction Message to establish the service
22 option connection corresponding to the data call, note whether the service option
23 connection corresponding to the voice call or data call is listed as the first entry in the
24 SCR.
25 f. If applicable, trigger an action at the mobile station that will result in either a Flash With
29 1. If the service option connection corresponding to the voice call is listed as the
30 first entry in the SCR:
31 a. The mobile station sends a Flash With Information Message, an
32 Extended Flash With Information Message with the CON_REF_INCL
33 field set to ‘0’, or an Extended Flash With Information Message with
34 the CON_REF field set to the connection reference corresponding to
35 the voice call.
36 b. The information record is delivered correctly in the network.
37 2. If the service option connection corresponding to the data call is listed as the first
38 entry in the SCR:
39 a. The mobile station sends an (Extended) Flash With Information

40 Message with the CON_REF field set to the connection reference
41 corresponding to the voice call.
16-19
C.S0044-0 v1.0
1 b. The information record is delivered correctly in the network.

2 g. If applicable, trigger an action at the network that will result in either a Flash With
4 being transmitted to the mobile station (Ex. Trigger an action that utilizes the Display
5 information record). Verify the following:
6 1. If the service option connection corresponding to the voice call is listed as the
7 first entry in the SCR:
8 a. The base station sends a Flash With Information Message, an
9 Extended Flash With Information Message with the CON_REF_INCL
10 field set to ‘0’, or an Extended Flash With Information Message with
11 the CON_REF field set to the connection reference corresponding to
12 the voice call.
13 b. The information record is correctly handled in the mobile station.
14 2. If the service option connection corresponding to the data call is listed as the first
15 entry in the SCR:
16 a. The base station sends an Extended Flash With Information Message
17 with the CON_REF field set to the connection reference corresponding
18 to the voice call.
19 b. The information record is correctly handled in the mobile station.
20 h. Perform a mobile station initiated or base station initiated release of the data call. Wait
21 till this operation is successful.
22 i. If applicable, trigger an action at the mobile station that will result in either a Flash With
26 1. The mobile station sends a Flash With Information Message, an Extended Flash
30 2. The information record is delivered correctly in the network.
31 j. If applicable, trigger an action at the network that will result in either a Flash With
32 Information Message or Extended Flash With Information Message being transmitted to
33 the mobile station for a voice call (Ex. Trigger an action that utilizes the Display
34 information record). Verify the following:
35 1. The base station sends a Flash With Information Message, an Extended Flash
39 2. The information record is correctly handled in the mobile station.
16-20
C.S0044-0 v1.0

2 The mobile station and base station shall comply with the requirements in steps c, d, f, g, i and j,.
3 The base station shall comply with the requirements in steps d, g, and j.
4 16.8 Analog Handoff Direction Message Terminates All Calls Except One
5 16.8.1 Definition
6 This test verifies that, when the base station directs the mobile station to perform a handoff from
7 the CDMA system to an analog system by sending an Analog Handoff Direction Message, all
8 calls except for the one indicated by the Analog Handoff Direction Message are terminated.
10 See 16.1.2.
MS BS
Traffic Traffic
Voice + Data calls in progress
Analog Handoff Direction Message

MS terminates all calls (CON_REFX)
except one identified by
CON_REFX
Analog
Single call continues
12

15 b. Setup a voice call and a packet data call (e.g. SO33). Wait till both calls are in progress.
16 Note whether the service option connection corresponding to the voice call or data call
17 is listed as the first entry in the Service Configuration Information Record.
18 c. Trigger the network to direct the mobile station to perform a handoff from the CDMA
19 system to an analog system in a band class that the mobile station supports and to
20 maintain the voice call. Verify the following:
21 1. The base station sends an Analog Handoff Direction Message to the mobile
22 station, with the CON_REF_INCL/CON_REF fields set as follows:
16-21
C.S0044-0 v1.0
1 a. If the service option connection corresponding to the voice call was

2 listed as the first entry in the Service Configuration information record,
3 then either the CON_REF_INCL field is set to ‘0’ or the CON_REF field
4 is set to the connection reference of the voice call.
5 b. If the service option connection corresponding to the data call was
6 listed as the first entry in the Service Configuration information record,
7 then the CON_REF field is set to the connection reference of the voice
8 call.
9 2. Upon receiving this message, the mobile station performs the following:
10 a. The mobile station terminates the data call and maintains the voice
11 call.
12 b. The mobile station shall perform handoff to the analog system
13 indicated by the Analog Handoff Direction Message.

15 The mobile station and base station shall comply with the requirements in step c.
16 16.9 Release A Mobile Station in Concurrent Calls with a Release A Base Station Hands
17 off to Pre-Release A Base Station
19 This test verifies that, when a Release A mobile station currently in concurrent calls with a
20 Release A base station is handed off to a Pre-Release A base station, only a single call is
21 maintained and this call continues successfully.
23 See 16.1.2.
MS BS
BS
(Rel A) (Rel A)
(Pre-Rel A)
Traffic
Voice + Data calls

in progress
Voice or data GHDM/UHDM
(P_REV<7,
call is released
SCR_new: Voice or Data)
as instructed in
the new SCR
Voice or Data call in progress
25
26
16-22
C.S0044-0 v1.0

3 a. Connect a MOB_P_REV 7 mobile station to base stations 1 and 2 as in Figure A-5.
4 Configure base station 1 to support P_REV=7 and base station 2 to support P_REV<7.
5 b. Setup a mobile station originated or mobile station terminated voice call on base station
6 1.
7 c. Set up a mobile station originated or mobile station terminated packet data call (e.g.
8 SO33). Wait till both voice and data calls are in progress. Ensure sufficient traffic is
9 exchanged to keep the data instance in active state.
10 d. Trigger base station 1 to direct the mobile station to handoff to base station 2. Verify the
11 following:
12 1. The base station shall send a General Handoff Direction Message or a Universal
13 Handoff Direction Message to the mobile station, with the Service Configuration
14 information record included and set as follows:
15 a. The service option connection corresponding to the call to be

16 maintained is included and uses the same connection reference value
17 (CON_REF) as currently used for this call.
18 b. The service option connection corresponding to the other call is

19 omitted.
20 2. At the action time of this message, the mobile station shall release the call
21 corresponding to the omitted service option connection and hands off to the base
22 station 2.
23 3. The remaining call continues successfully in the base station 2.

25 The mobile station and base station shall comply with the requirements in the following steps:
26 Step d.
27
28 16.10 Release A Mobile Station Hands off between Release A Base Station with Change in
29 Concurrent Calls Support
31 This test verifies that, when a Release A mobile station currently in call with a Release A base
32 station is handed off to another Release A base station, and where there is a change in
33 Concurrent Calls support, calls are released/added/maintained successfully.
35 See 16.1.2.
16-23
C.S0044-0 v1.0
BS BS
MS
(Rel A: (Rel A:
(Rel A)
CS_SUPPORTED=1) CS_SUPPORTED=0)
Traffic
Voice and Data call

in progress
GHDM/UHDM
(P_REV=7,
Voice or data SCR_new: Voice or Data,
call is released CS_SUPPORTED=0)
Voice or Data call in progress
UHDM
(P_REV=7,
SCR_new: Voice and Data,
Voice or data
CS_SUPPORTED=1,
call is added CC_INFO_INCL=1)
Voice and Data call

in progress
2
3

5 a. Connect the MOB_P_REV=7 mobile station (Release A) to two P_REV=7 base stations
6 (Release A) as shown in Figure A-5. Configure base station 1 to support Concurrent
7 Services and base station 2 not to support Concurrent
8 b. Setup a mobile station originated or mobile station terminated voice call on base station
9 1.
10 c. Set up a mobile station originated or mobile station terminated packet data call (e.g.
11 SO33). Wait till both voice and data calls are in progress. Ensure sufficient traffic is
12 exchanged to keep the data instance in active state.
13 d. Trigger the base station to direct the mobile station to handoff from base station 1 to
14 base station 2. Verify the following:
15 1. The base station shall send a General Handoff Direction Message or a Universal
16 Handoff Direction Message to the mobile station, with the Service Configuration
17 information record included and set as follows:
18 a. The CS_SUPPORTED field is set to ‘0’.
16-24
C.S0044-0 v1.0
1 b. The service option connection corresponding to the call to be

2 maintained is included and uses the same connection reference value
3 (CON_REF) as currently used for this call.
4 c. The service option connection corresponding to the other call is
5 omitted.
6 2. At the action time of this message, the mobile station shall release the call
7 corresponding to the omitted service option connection and hands off to the new
8 Release A base station.
9 3. The remaining call continues successfully in the new Release A base station.
10 e. Trigger the base station to direct the mobile station to handoff from base station 2 to
11 base station 1 that supports concurrent services and with an additional call added
12 (voice or packet data call (e.g. SO33)). Verify the following:
13 1. The base station shall send a Universal Handoff Direction Message to the mobile
14 station, with the following fields set as follows:
15
Field Value
P_REV 7 (Release A base station)
SCR_INCLUDED ‘1’ (SCR is included)
CON_REF Connection reference for original call – same

as the value currently in use
SERVICE_OPTION SO for original call
CON_REF Connection reference for the SOC

corresponding to the new call
SERVICE_OPTION SO for the new call
CON_REF Same value as connection reference for the

new call
16 2. At the action time of this message, the mobile station hands off to base station 1
17 and connects the new call.
18 3. The new call is connected successfully. The original call continues successfully.
19
16-25
C.S0044-0 v1.0

2 The mobile station and base station shall comply with the requirements in steps d and e
3
16-26
C.S0044-0 v1.0
1 17 EMERGENCY CALLS
2 17.1 Global Emergency Call Support When Mobile Station is in Idle State
3 17.1.1 Definition
4 This test verifies that the mobile station can originate a global emergency call during idle state
5 and that the base station processes this as an emergency call.

9 None

11 a. If the mobile station is capable of recognizing emergency number by analyzing the
12 dialed digits, originate an emergency call from the mobile station by dialing an
13 emergency number.
14 b. Verify the GLOBAL_EMERGENCY_CALL field is set to ‘1’ in the Origination Message
15 and that the base station processes the origination as an emergency call.
16 c. End the call.
17 d. If the mobile station has a special interface to initiate an emergency call, originate an
18 emergency call from the mobile station using this special interface.
19 e. Verify that the mobile station sets the GLOBAL_EMERGENCY_CALL field to ‘1’ in the
20 Origination Message and that the base station processes the origination as an
21 emergency call.
22 f. End the call.

24 The mobile station shall comply with the following steps as supported: Step b and e.
25 The base station shall comply with the following steps as supported: Step b and e.
26 17.2 Global Emergency Call Support When Mobile Station is in Voice Call.
28 This test verifies that the mobile station can originate a global emergency call while another voice
29 call is in progress and that the base station processes this as an emergency call. This test is
30 applicable only to mobile stations not capable of concurrent services.

17-1
C.S0044-0 v1.0

2 2.7.2.3.2.3 Flash With Information Message

5 None

7 a. Connect the base station to the mobile station as shown in Figure A-3.
8 b. Originate a voice call from the mobile station. Verify audio in both directions.
9 c. If the mobile station is capable of recognizing emergency number by analyzing the
10 dialed digits and the mobile station does not support concurrent service, originate an
11 emergency call from the mobile station by dialing an emergency number (e.g. dialing 9-
12 1-1 and press SEND).
13 d. Verify that the mobile station sends a Flash With Information Message or an Extended
14 Flash With Information Message with the Global Emergency Call information record
15 included or an Enhanced Origination Message with the GLOBAL_EMERGENCY_CALL
16 field set to ‘1’ and that the base station processes the message as an emergency call.
17 e. End the calls.

18 f. Originate a voice call from the mobile station. Verify audio in both directions.
19 g. If the mobile station has a special interface to initiate an emergency call, originate an
20 emergency call from the mobile station using this special interface.
21 h. Verify that the mobile station sends Flash With Information Message or Extended Flash
22 With Information Message with the Global Emergency Call information record included
23 and that the base station processes the origination as an emergency call.
24 i. End the calls.

26 The mobile station shall comply with the following steps as supported: Step d and h.
27 The base station shall comply with the following steps as supported: Step d and h.
28 17.3 Global Emergency Call Support When Mobile Station is in a Data Call
30 This test verifies that the mobile station can originate a global emergency call when a packet data
31 call (Ex. SO33) is in progress and that the base station processes this as an emergency call. This
32 test is applicable if both the base station and mobile station support concurrent services.
17-2
C.S0044-0 v1.0

2 2.7.2.3.2.3 Flash With Information Message

5 None

7 a. Connect the base station to the mobile station as shown in Figure A-3.
8 b. Originate a data call from the mobile station.
9 c. If the mobile station is capable of recognizing emergency number by analyzing the
10 dialed digits, then while the data call is up, originate an emergency call from the mobile
11 station by dialing an emergency number (e.g. dialing 9-1-1 and press SEND).
12 d. Verify the mobile station sends an Enhanced Origination Message with the
13 GLOBAL_EMERGENCY_CALL field set to ‘1’ and that the base station processes the
14 origination as an emergency call.
15 e. End the calls.
16 f. Originate a data call from the mobile station.
17 g. If the mobile station has a special interface to initiate an emergency call, then while the
18 data call us up, originate an emergency call from the mobile station using this special
19 interface.
20 h. Verify the mobile station sends an Enhanced Origination Message with the
21 GLOBAL_EMERGENCY_CALL field set to ‘1’ and that the base station processes the
22 origination as an emergency call.
23 i. End the calls.

25 The mobile station shall comply with the following steps as supported: Step d and h.
26 The base station shall comply with the following steps as supported: Step d and h.
27 17.4 Emergency Call on a System that is Negative on PRL or SID List
29 This test verifies that the mobile station acquires a system that is ‘negative’ in its (Extended)
30 Preferred Roaming List for an emergency call only.

33 ANNEX C System Selection and Acquisition
17-3
C.S0044-0 v1.0
1 17.4.3 Call Flow

2 None

4 a. Connect the mobile station and base station as shown in Figure A-3.
5 b. Program the base station’s SID into the PRL as a negative system.
6 c. Enable power-on registration. Disable all other forms of registration.
7 d. Power on the mobile station, and monitor it for a sufficient period of time to permit it to
8 acquire the base station (typically 30 seconds).
9 e. Verify the mobile station does not attempt to access the base station.
10 f. Setup an emergency call from the mobile station (911 in the United States).
11 g. Verify the mobile station sends an Origination Message to the base station.
12 h. Verify the emergency call is routed to the PSAP or equivalent emulation unit.
13 i. End the emergency call from the mobile station.

15 The mobile station shall comply with step e and g.
16 17.5 Optional Emergency Calls

18 The requirements in these test cases are applicable regionally. For example, in the U.S., the
19 FCC has certain requirements for the mobile station and the base station when an emergency 9-
20 1-1 call is initiated. The purpose of this test is to determine the mobile station’s capability to
21 initiate an emergency call under 3 different initial conditions: (1) No calls active or dormant, (2)
22 data call is active and (3) data call in dormant mode.
24 None
26 None
28 a. Allow the mobile to become idle on the base station.
29 b. Originate emergency call from the mobile station and verify that the emergency call is
30 connected. Release the emergency call.
31 c. Setup SO33 call. While SO33 call is active, originate emergency call from the mobile
32 station and verify that the emergency call is connected. Release the emergency call.
33 d. Allow SO33 to go dormant.
34 e. While SO33 call is dormant, originate emergency call from the mobile station and verify
35 that the emergency call is connected. Release the emergency call.
17-4
C.S0044-0 v1.0

2 The mobile station and base station shall comply with the requirements in steps b, c, e (according
3 to applicable regional requirements).
17-5
C.S0044-0 v1.0
1 18 HRPD
2 For HRPD test cases described in chapter 18, the terms mobile station and base station
3 represent the access terminal (AT) and access network (AN) respectively.
4 18.1 HRPD Acquisition and Idle Mode Operation

5 18.1.1 Definition
6 These tests will verify that AT acquires the HRPD system and performs idle monitoring of the
7 HRPD control channel. These tests also verify that upon losing HRPD system during idle
8 operation, AT tries to reacquire the HRPD system.
10 8.2.6.1.4.2.1 Initial Acquisition

12 None
14 a. Power up the AT.
15 b. Verify that the AT acquires HRPD system
16 c. Verify that after acquiring HRPD system, the AT performs idle monitoring of the control
17 channel on HRPD system
18 d. Disable the forward link to the AT.
19 e. Verify that AT declares system lost
20 f. Enable the forward link and verify that the AT re-acquires EV-DO system.
22 The AT shall comply with c and f.
23 18.2 HRPD Session Establishment

25 This test verifies that during the HRPD session establishment, a Unicast AT Identifier (UATI) is
26 assigned to the AT.
28 [see 24] 5 Session Layer, 6 Connection Layer, 8 MAC Layer

30 None
32 a. Connect the AT to the access network as shown in figure A-3.
33 b. Ensure AT has not established HRPD session with access network (no UATI has been
34 assigned by access network)
35 c. Cause the AT to acquire HRPD access network.
18-1
C.S0044-0 v1.0
1 d. Verify the AT issues a UATIRequest Message.

2 e. Verify the access network issues a UATIAssignment Message. Record the UATI.
3 f. Verify the AT issues a UATIComplete Message.
4 g. Cause the AN to send an UpdateUATI Message to the AT.
5 h. Verify the AT sends a new UATIRequest Message.
6 i. Verify the access network issues a UATIAssignment Message. Record the UATI.
7 j. Verify the AT issues a UATIComplete Message.
9 Verify steps d, e, f, h, I and j.
10 18.3 HRPD Session Configuration and Management with Subnet change

12 This test verifies session configuration and management associated with a subnet change. If the
13 AT moves to a new subnet and if the new subnet can retrieve the AT’s prior session configuration
14 from the old subnet, new session negotiations are not needed. If the “Prior session attribute” is
15 supported by the AN, it can use the previously negotiated set of session parameters.
17 5 Session Layer

19 None
21 a. Power up the AT and place it where it can receive good HRPD signal.
22 b. Verify that AT acquires and goes to idle state. Verify that AT requests a UATI and AN
23 assigns it, as specified in the “address management” test case described in this section.
24 c. Verify that after UATI assignment, AT opens a new HRPD connection and starts
25 session negotiation using sets of ConfigRequest/ConfigResponse messages.
26 d. After a HRPD session is opened successfully, move the AT to another subnet where
27 prior session attribute is accepted. Verify that in this subnet, AT sends a ConfigRequest
28 with the current session token and AN sends back a ConfigResponse. Verify that AT
29 does not go through a new set of session negotiations after receiving the
30 ConfigResponse from the AN.
32 The mobile station shall comply with steps b and c.
33 18.4 AT Color Code and UATI24

35 This test verifies that the AT is assigned a valid Color Code and UATI024 during an HRPD
36 session establishment.
18-2
C.S0044-0 v1.0

2 None
4 a. Connect the AT to the access network as shown in Figure A-3.
5 b. Cause the access network to issue a new UATI to the AT.
6 c. Verify a valid Color Code (UATIColorCode) and UATI24 (UATI024) are assigned to the
7 AT in the UATIAssignment Message. Record the Color Code and UATI024.
9 Verify the AT complies with step c.
10 18.5 HRPD Connection Setup

12 This test verifies that when the HRPD connection is idle (session active and PPP dormant), an AT
13 initiated ping and AN initiated ping shall be successful. This test will verify that AT can setup a
14 HRPD packet data connection when its state is idle.

18 None
21 b. Power up the AT.
22 c. Verify that the AT connection is idle on HRPD system
23 d. Issue a “ping” command from the AT to a remote host to setup an HRPD AT originated
24 connection.
25 e. Verify AT sends a Connection Request Message to access network and that access
26 network sends a ACAck and a TrafficChannelAssignment Message to the AT. Verify AT
27 sends a TrafficChannelCompleteMessage and that connection enters active state.
28 f. Verify the AT receives a “ping” response from the remote host
29 g. Issue a “ping” command from the remote host to the AT using the IP address assigned
30 to the AT.
31 h. Verify the remote host receives a “ping” response from the AT.
32 i. Let the AT connection go idle. Start FTP/ping from the AT and verify that the AT
33 connection goes to active state. Also verify that the data can be transferred in both
34 directions over HRPD system
35 j. Wait for connection AT to go idle.
36 k. Issue a “ping” command from the remote host to the AT using the IP address assigned
37 to the AT.
38 l. Verify the AT setups the HRPD connection and the remote host receives a “ping”
39 response from the AT.
18-3
C.S0044-0 v1.0

2 AT and AN shall comply with steps e, f, h, i and l.
3 18.6 Test Application Protocol

4 18.6.1 Definition
5 This test verifies HRPD FTAP (Forward Test Application Protocol) and HRPD RTAP (Reverse
6 Test Application Protocol). The statistics provided by the FTAP and RTAP tests can be used to
7 compute Packet Error Rate performance.
9 [see 24] 2.5 Signaling Network Protocol, 5 Session Layer, 6 Connection Layer, 7 Security Layer,
10 8 MAC Layer
11 TIA/EIA/IS-890 - Test Application Specification (TAS) for High Rate Packet

12 See [27]

14 None
17 b. Initiate an HRPD FTAP (Forward Test Application Protocol) test with Loop Back mode
18 enabled.
19 c. Record the statistics provided.
20 d. Repeat steps c through d with ACK Channel Bit Fixed mode enabled.
21 e. Repeat steps c through d with DRC Value Fixed mode enabled.
22 f. Repeat steps c through d with DRC Cover Fixed mode enabled.
23 g. Initiate an HRPD RTAP (Reverse Test Application Protocol) test with RTAP Test Packet
24 mode enabled.
25 h. Record the statistics provided.
26 i. Repeat steps h through I with Configured Packet Rate mode enabled.
28 Verify the proper FTAP and RTAP test shall execute with statistics returned as indicated in steps
29 c and h.
30 18.7 Access Network Packet Data Inactivity Timer

32 This test is only required for access networks that have an access network packet
33 data inactivity timer. This test verifies the access network releases the traffic channel after
34 expiration of the access network packet data inactivity timer. The test verifies the link layer
35 connection can be re-activated from idle state.
37 [24] 5 Session Layer, 6 Connection Layer, 7 Security Layer, 8 MAC Layer
18-4
C.S0044-0 v1.0
1 [26] 2.3.1.2 Termination

3 None
6 b. Set the PCF PPP inactivity timer to 20 seconds.
7 c. Setup an HRPD AT originated connection.
8 d. Initiate a Telnet session to a remote host.
9 e. Record the IP address assigned to the AT.
10 f. Exit the Telnet session.
11 g. Wait for the access network packet data inactivity timer to expire. Verify access network
12 sends a ConnectionCloseMessage with CloseReason = 0 (normal Close). Verify the AT
13 sends a ConnectionCloseMessage with CloseReason = 1 (Close Reply) and
14 connection goes to idle state.
15 h. Setup an HRPD AT originated connection.
16 i. Initiate a Telnet session to a remote host.
17 j. Record the IP address assigned to the AT.
18 k. Wait for the PCF PPP inactivity timer to expire. Verify the AT connection goes to idle
19 state.
20 l. Setup an HRPD AN originated connection by issuing a “ping” command from a remote
21 host to the AT using the IP address assigned to the AT.
22 m. Verify the host receives a “ping” response from the AT.
23 n. Wait for the PCF PPP inactivity timer to expire. Verify the AT connection goes to idle
24 state.
25 o. Setup an HRPD AT originated connection by issuing a “ping” command from the AT to
26 a remote host.
27 p. Verify the AT receives a “ping” response from the remote host.
28
30 AN and AT shall comply with steps g, k, m, n, p.

33 This test verifies HRPD forward link file transfer when in active HRPD mode. This test case may
34 be performed using Simple IP and/or Mobile IP.
36 [24] 5 Session Layer, 6 Connection Layer, 8 MAC Layer

37 (See [26]) 3 HRPD IOS Call Flows
18-5
C.S0044-0 v1.0

2 None
5 b. At the remote host prepare the appropriate file, corresponding to the rate that will be
6 tested (Note: this will guarantee sufficient transfer time).
7 c. Setup an AT originated HRPD connection.
8 d. Adjust the RF quality in such a way that the AT request mostly the DRC value
9 corresponding to the rate that will be tested.
10 e. Setup an FTP session with a remote host and start a file transfer in the forward link by
11 using a binary “get” command from the AT.
12 f. Verify the data transfer completes successfully.
13 g. After the file transfer is completed successfully, end the FTP session.
14 h. This test case may be repeated for supported DRC values below.
15
16 Table 18.8.4-1 DRC Value Specification
DRC Value Rate (kbps) Packet Length

(Slots)
0x0 Null rate N/A
0x1 38.4 16
0x2 76.8 8
0x3 153.6 4
0x4 307.2 2
0x5 307.2 4
0x6 614.4 1
0x7 614.4 2
0x8 921.6 2
0x9 1228.8 1
0xa 1228.8 2
0xb 1843.2 1
0xc 2457.6 1
18-6
C.S0044-0 v1.0
0xd Invalid N/A
0xe Invalid N/A
0xf Invalid N/A
1
3 The AT shall comply with step f for all test cases.

5 18.9.1 Definition
6 This test verifies HRPD reverse link file transfer when in active HRPD mode. This test case may
7 be performed using Simple IP or Mobile IP.
9 [24.] 5 Session Layer, 6 Connection Layer, 8 MAC Layer

10 [26] 3 HRPD IOS Call Flows

12 None
15 b. Cause the AT to acquire the access network. Setup an HRPD AT originated
16 connection.
17 c. Setup a FTP session with a remote host and start a file transfer in the reverse link by
18 using a binary “put” command from the AT.
19 d. Verify the file transfer completes.
20 e. After the file transfer is completed, end the FTP session.
23 18.10 Bidirectional File Transfer

25 This test verifies bi-directional file transfer when in active HRPD mode.

29
18-7
C.S0044-0 v1.0

2 None
5 b. Cause the AT to acquire the access network. Setup an HRPD AT originated
6 connection.
7 c. At the remote host prepare the appropriate file, corresponding to the rate that will be
8 tested (Note: this will guarantee sufficient transfer time).
9 d. Setup a FTP session ( 1) with a remote host and start a file transfer in the reverse link
10 by using a binary “put” command from the AT.
11 e. Setup another FTP session ( 2) and transfer a file from the Remote Host to the AT
12 using the binary “get” command while the transfer in the reverse direction is still
13 proceeding.
14 f. Verify both file transfers complete.
15 g. After the file transfer, end both FTP sessions.
17 The AT shall comply with step f.
18 18.11 RLP Operation in Severely Degraded Channel

20 This test verifies RLP Operation in Severely Degraded Channel when in active HRPD mode. This
21 test is intended to exercise RLP resets due to long erasure bursts.


26 None
28 a. Connect the AT to the access network as shown in [Figure A-1]. At the remote host
29 prepare the appropriate file, corresponding to the rate that will be tested (Note: this will
30 guarantee sufficient transfer time). Refer to files in Data Services Annex D.
31 b. Set the channel simulator to one Ray 3 km/hr Rayleigh fading on the forward link.
32 c. Cause the AT to acquire the access network. Setup an AT originated HRPD call.
33 d. Setup a FTP session with a remote host and start a file transfer in the forward link by
35 e. Verify AT sends a valid DRC value in the Data Rate Control Channel to the access
36 network and that access network provides AT with requested forward link coding and
37 modulating parameters.
38 f. Ensure data transfer rate is not limited by network limitations.
39 g. Verify the data transfer is successful.
18-8
C.S0044-0 v1.0
1 h. After the file transfer is completed, end the FTP session.

3 The AT shall comply with steps e and g.
4 18.12 Softer and Soft Handoff – Active HRPD Mode

6 This test verifies soft handoff when AT is in active HRPD mode with file transfer in forward and
7 reverse directions.
9 [see 24]
10 5 Session Layer,
11 6 Connection Layer;
12 6.6.7.2 SetManagementSameChannelParameters Attribute
13 8 MAC Layer

16 None
18 a. Connect the AT to the access network as shown in Figure A-5 and set the forward link
19 parameters as shown in. Configure all three sectors with the same channel.
20 Table 18.12.4-1 Forward Link Parameters for Soft(er) Handoff Tests
Parameter Units AN BTS 1 AN BTS 1 AN BTS 2

Sector α Sector β Sector γ
Forward Link dBm/1.23MHz -70 -85 -85

Power Ior
21 b. Configure each sector to send the Sector Parameters Message with Neighbor List
22 including the other sectors’ Pilot PNs.
23 c. Setup an HRPD AT originated connection on BTS 1, sector α.
24 d. Setup an FTP session with a remote host and start a file transfer in the forward link by
25 using a binary “get” command from the AT. Ensure the file size is appropriate to
26 complete the test case before transfer is over.
27 e. Verify that BTS 1/sector α is in the pilot active set and that BTS 1/sector ß and BTS
28 2/sector α are in the pilot neighbor set.
29 f. Raise the level of BTS 1/sector ß in steps of 1 dB with a dwell time of 5 seconds after
30 each step until the BTS 1/sector ß is in the pilot candidate set.
31 g. Verify AT sends a RouteUpdate Message to report pilots.
18-9
C.S0044-0 v1.0
1 h. Verify the access network send s a TrafficChannelAssignment Message with Num

2 Pilots=2 then verify both BTS 1 sector α and sector ß are in the pilot active set. Verify
3 that SofterHandoff bit in the TrafficChannelAssignment message is set to 1 for the pilots
4 in the softer handoff.
5 i. Raise the level of BTS 2/sector α in steps of 1 dB with a dwell time of 5 seconds after
6 each step until the BTS 2/sector α is in the pilot candidate set.
7 j. Verify AT sends a RouteUpdate Message to report pilots.
8 k. Verify the access network send s a Traffic Channel Assignment Message with Num
9 Pilots=3 then verify BTS 1/sectors α and ß and BTS 2/sector α are in the pilot active
10 set.
11 l. Decrease the level of BTS 1/sector α in steps of 1 dB with a dwell time of 5 seconds
12 after each step until access network sends a Traffic Channel Assignment Message with
13 Num Pilots=2, then verify the BTS 1/sector α is in the pilot neighbor set.
14 m. Decrease the level of BTS 1/sector ß in steps of 1 dB with a dwell time of 5 seconds
15 after each step until access network sends a Traffic Channel Assignment Message with
16 Num Pilots=1, then verify the BTS 1/sector ß is in the pilot neighbor set. Verify file
17 transfer is still on and the call in on BTS 2/sector α.
18 n. Verify the file transfer completes.
19 o. End the call.
20 p. Repeat steps a through c.
21 q. Setup an FTP session with a remote host and start a file transfer in the reverse link by
22 using a binary “put” command from the AT. Ensure the file size is appropriate to
23 complete the test case before transfer is over.
24 r. Repeat steps e through p.
26 The AT and AN shall comply with steps e, g, h, j, k, l, m and n for all test cases.
27 18.13 HRPD Control Channel Monitoring and Overhead Message Updates

29 This test will verify that the AT can successfully receive and update control channel messages.
30 AN can set various periodicities (within the allowed range, as defined in [24]) for these messages.
32 [24] 6.4 Default Idle State Protocol

34 None
36 a. Power up the AT.
37 b. Configure the AT to operate in non-slotted (sleep disabled) mode
38 c. Monitor the periodicity of Sync message, Quickconfig message, SectorParameter
39 message, and AccessParameter message
18-10
C.S0044-0 v1.0
1 d. Check the AN configuration for periodicity of these messages. Verify that received
2 messages have same periodicity as configured at the AN
3 e. Configure the AT to operate in slotted (sleep enabled) mode
4 f. Verify that AT receives and updates the overhead messages (QuickConfig and
5 SectorParameter messages) and performs the supervision of these messages
6 according to the procedures in overhead message protocol specified in [24].
8 The AT shall comply with steps d and f.
9 18.14 Control Channel Rate

11 This test verifies correct monitoring of Control Channel by AT.
12 18.14.2 Traceability: [See 24]
13 8.2 – Default Control Channel MAC Protocol
14 8.2.6.1.4.1.1 – General Requirements
15 9.3 – Access Network Requirements
16 9.3.1.3.1 – Forward Channel Structure
17 9.3.1.3.2.2 – Forward MAC Channel
18 9.3.1.3.2.4 – Control Channel

20 None
22 a. Configure Control Channel Rate to 38400 bps on access network.
23 b. Connect the AT to the access network as shown in Figure A-3
24 c. Verify AT is able to monitor SyncChannel Message, QuickConfig Message, Sector
25 Parameters Message and AccessParameters Message.
26 d. Instruct AT to request a UATI from access network and Setup an HRPD AT originated
27 call. Issue a “ping” from AT.
28 e. Release the call.
29 f. Configure Control Channel Rate to 76800 bps on access network and repeat steps b
30 through e.
32 The AT shall comply with step c for all test cases.
33 18.15 AT Initiated HRPD ConnectionDeny

35 This test verifies that if there is no traffic channel available, the access network will send a
36 ConnectionDeny Message to AT.
18-11
C.S0044-0 v1.0
1 18.15.2 Traceability: [See 24]
2 6.4 – Default Idle State Protocol

3 6.4.6.1.6.1 – AT Requirements
4 6.4.6.1.6.2 – Access Network Requirements
5 6.4.6.2.3 – ConnectionDeny

7 None
9 a. Configure AN to respond with a ConnectionDeny with reason “Network Busy” to a
10 ConnectionAttempt message.
11 b. Attempt to setup an AT originated HRPD connection.
12 c. Verify the access network sends a Connection Deny Message with Deny Reason 1 =
13 Network Busy.
14 d. Verify the AT enters the AT Monitor(Idle) State until it attempts to setup a new call
16 The AT and AN shall comply with steps c and d.
17 18.16 HRPD Keep Alive Mechanism

19 This test verifies the proper functionality of keep alive mechanism. The access terminal and the
20 access network shall monitor the traffic flowing on the Forward Channel and Reverse Channel,
21 respectively, directed to or from the access terminal. If either the access terminal or the access
22 network detects a period of inactivity of at least TSMPClose/NSMPKeepAlive minutes, it may
23 send a KeepAliveRequest message. The recipient of the message shall respond by sending the
24 KeepAliveResponse message. When a KeepAliveResponse message is received, the access
25 terminal shall not send another KeepAliveRequest message for at least
26 TSMPClose/NSMPKeepAlive minutes.
28 [24] 5.2.6.1.6.1 Keep Alive Functions
29 See [24] Table 5.2.7.1and Table 5.2.8

31 None
33 a. Power up the AT and place it where it can receive good HRPD signal
34 b. Verify that AT acquires and goes to idle state.
35 c. Terminate all data activities to and from the AT for a period greater than see [24]
36 d. Verify that after an inactivity period of TSMPClose / NSMPKeepAlive minutes if either AT or
37 AN sends a KeepAliveRequest that the recipient of the KeepAliveRequest message
38 responds with a KeepAliveResponse message.
18-12
C.S0044-0 v1.0
1 e. Verify that upon receipt of KeepAliveResponse message, the AT does not send another
2 KeepAliveRequest message for at least another TSMPClose / NSMPKeepAlive minutes
3 f. Verify that if AT does not receive any response from the AN for a period of see [24]
4 minutes, it terminates the session
5 g. Verify that if see [24] is set to zero, the keep alive mechanism between AT and AN is
6 disabled
8 The AT and the AN shall comply with step b, d, e, f and g.
9 18.17 Intra-band HRPD-HRPD System Re-Selection (Connected State)

11 This test verifies the AT performs HRPD system reselection between different channels in the
12 same band class.
14 [See (SEE [24]) ]

15 6.2 – Default Air Link Management Protocol
16 6.2.6.1.2 – Initialization State
18 6.4.6.1.6 – Connection Setup State
19 6.5 – Default Connection State Protocol
20 [See 26]
21 3.7.1 – PCF-PCF Dormant Handoff with Successful Retrieval of HRPD Session Information

23 None
25 a. Connect the AT to AN 1 and AN 2 as shown in Figure A-5.
26 b. Configure AN 1 with different channel than AN 2
27 c. Configure AN 2 not to be in the neighbor list of AN 1
28 d. Cause the AT to acquire access network AN 1. Setup an HRPD AT originated
29 connection.
30 e. Setup a FTP session with a remote host and start a file transfer in the forward link by
32 f. Before file transfer is complete increase forward link attenuation on AN 1 until AT can’t
33 monitor AN 1 signal.
34 g. Verify AT declares system lost and acquires AN 2 and reconnects HRPD connection.
35 Verify file transfer continues after selection AN 2.
36 h. Release connection.
18-13
C.S0044-0 v1.0
1 i. Repeat steps b through g for file transfer in the reverse link by using a binary “put”
2 command from the AT instead of “get” (step e).
4 The AT shall comply with step g for all test cases.
5 18.18 Inter-band HRPD-HRPD System Re-Selection (Connected State)

7 This test verifies the AT performs HRPD system reselection between channels from different
8 band classes.
10 [See (SEE [24]) ]

16 [See 26]

19 None
22 b. Configure AN 1 to operate in a different band class than AN 2.
23 c. Cause the AT to acquire AN 1. Setup an HRPD AT originated connection.
24 d. Setup a FTP session with a remote host and start a file transfer in the forward link by
26 e. Before file transfer is complete increase forward link attenuation on AN 1 until AT can’t
27 monitor AN 1 signal.
28 f. Verify AT declares system lost and acquires AN 2 and reconnects HRPD call. Verify file
29 transfer continues after selection AN 2.
30 g. Release connection.
31 h. Repeat steps b through g for file transfer in the reverse link by using a binary “put”
32 command from the AT instead of “get” (step e).
34 The AT shall comply with step f for all test cases.
18-14
C.S0044-0 v1.0
1 18.19 Intra-band HRPD-HRPD System Re-selection (Idle State)

3 This test verifies the AT performs HRPD reselection, while in idle state, between channels in the
4 same band class.
6 [See (SEE [24]) ]


12 [See 26]

15 None
18 b. Configure AN 1 with different channel than AN 2.
19 c. Configure AN 2 not to be in the neighbor list of AN 1.
20 d. Cause the AT to acquire AN 1. Setup an HRPD AT originated call.
21 e. Verify that the AT connection is idle.
22 f. Force the AT to handoff from AN 1 to AN 2 (i.e. by increasing forward link attenuation
23 on AN 1 until AT can’t monitor AN 1 RF signal).
24 g. Verify AT declares system lost and acquires AN 2. Issue a “ping” from AT and verify an
25 HRPD connection is successfully setup.
26 h. Issue a “ping” from remote host to AT IP address and verify there is a response.
28 The AT shall comply with steps e, g and h.
29 18.20 Inter-band HRPD-HRPD System Re-selection (Idle State)

31 This test verifies the AT, in Simple IP mode, performs HRPD reselection, while in idle state,
32 between channels from different band classes.
34 [See (SEE [24]) ]

18-15
C.S0044-0 v1.0


5 [See 26]

8 None
11 b. Configure AN 1 to operate in a different band class than AN 2.
12 c. Cause the AT to acquire AN 1.
13 d. Verify that AT connection is idle.
14 e. Force the AT to handoff from AN 1 to AN 2 (i.e. by increasing forward link attenuation
15 on access network HRPD 1 until AT can’t monitor HRPD 1 RF signal).
16 f. Verify AT declares system lost and acquires AN 2. Issue a “ping” from AT and verify
17 HRPD call is successfully originated.
18 g. Issue a “ping” from remote host to AT IP address and verify there is a response.
20 The AT shall comply with steps d, f and g.
21 18.21 HRPD Terminal Authentication Failure
23 This test verifies that when the User-name or the Chap-password is incorrectly set at the AT the
24 network authentication fails.
26 [See TIA-878]
27 3.1.1 – AT originates HRPD Session – Successful Terminal Authentication
28 3.1.2 – AT originates HRPD Session – Unsuccessful Terminal Authentication

30 None

32 a. Configure the CHAP authentication to be enabled in the network.
33 b. Provision an incorrect User-name but a correct Chap-password in the AT for CHAP
34 authentication.
18-16
C.S0044-0 v1.0
1 c. Verify that the AT has a closed HRPD session

2 d. Power up the AT and place it where it can receive good HRPD signal
3 e. Verify that AT successfully completes the session negotiation and negotiates the AN
4 stream as part of this procedure
5 f. If AN performs authentication immediately after the session negotiation, verify that AN
6 sends the CHAP Challenge message and initiates the network authentication
7 g. Verify that the network authentication fails and the AN closes the HRPD session.
8 h. If AN performs authentication just before the data call setup(s), set up a data call on the
9 HRPD system and verify that AN sends the CHAP Challenge message and initiates the
10 AN authentication
11 i. Verify that the network authentication fails.
12 j. Repeat steps c to i by provisioning a correct User-name but an incorrect Chap-
13 password in the AT for CHAP authentication.
15 The AT and the AN shall comply with step c, e, g and i for all test cases..
16 18.22 PPP Session in Adverse Conditions - Disconnect cable between AT and PC.
18 This test verifies AT sends an LCP Termination Request to the access network when it is
19 disconnected from the computer device. This causes the PDSN to close the PPP session.
21 [28] 3.2.1 PPP Session
23
18-17
C.S0044-0 v1.0
1
2 Figure 18.22.3-1
3
18-18
C.S0044-0 v1.0
1
2 Figure 18.22.3-2
3
4
6 a. Setup an AT originated HRPD connection.
7 b. Ensure that an IP address is assigned to the AT, and a PPP session is established
8 between PDSN and the AT.
9 c. Wait until the AT connection goes to idle state.
10 d. Disconnect the cable between the AT and the computer device.
11 e. Verify Message flow between AT, access network and PDSN happens as shown in
12 Figure 18.22.3-1.
13 f. Verify dial-up connection at computer device is closed and PPP session is released at
14 PDSN.
15 g. Repeat steps a through c. Issue a “ping” from AT and verify there is a response from
16 remote host.
17 h. Disconnect the cable between the AT and the PC computer device.
18 i. Verify Message flow between AT, access network and PDSN happens as shown in
19 Figure 18.22.3-2
20 j. Verify dial-up connection at computer device is closed and PPP session is released at
21 PDSN.
23 The AT shall comply with steps e, f, i and j.
24
18-19
C.S0044-0 v1.0
1 18.23 Unicast ReverseRateLimit

3 This test verifies the AT can successfully receive the UnicastReverseRateLimit Message with the
4 RateLimit value set to various values.
6 [24] 8.5.6.1.5.2 Rate Control

8 None
10 a. Setup a connection.
11 b. Setup a FTP session with a remote host and start a file transfer in the reverse link by
12 using a binary “put” command from the AT.
13 c. Send a UnicastReverseRateLimit Message with the RateLimit value set to 1 (9.6 kbps)
14 to the AT.
15 d. Monitor the AT transmit rate and verify that the AT does not transmit above the value
16 set in step c.
17 e. Steps a to d may be repeated with the RateLimit values set to 2 (19.2kbps), 3
18 (38.4kbps), 4 (76.8kpbs), and 5 (153.6kbps).
20 The AT shall comply with step d for all test cases.
21 18.24 HRPD Location Update Protocol Tests

23 This test verifies the proper functionality of Location update feature.
25 [24] 3.5 Location Update Protocol

27 None
29 a. Verify that the Ranhandoff parameter is enabled at the AN.
30 b. Power up the AT and place it where it can receive good HRPD signal
31 c. Verify that AT successfully completes the session negotiation.
32 d. Depending on the implementation the AN can send LocationAssignment Message to
33 the AT. Upon receiving this LocationAssignment Message, verify that the AT sends a
34 LocationComplete Message and stores the Location Values in the Location Assignment
35 Message as the current Location Values.
18-20
C.S0044-0 v1.0
1 e. Depending on the implementation the AN can send LocationRequest Message. Upon

2 receipt of this message, verify that the AT responds with LocationNotification Message,
3 which shall contain the current Location values of the AT.
4 f. Originate a packet connection, verify that the connection can be successfully
5 established and the data can be transferred. Let the AT connection go idle.. Move the
6 AT to an area where there is no HRPD signal. AT will lose the HRPD signal and go to
7 acquisition state. Move the AT to an area where there is a HRPD signal belonging to a
8 different subnet. AT shall acquire this system. AT shall negotiate session with this
9 HRPD system and once the session is negotiated, shall send an unsolicited
10 LocationNotification Message. Verify that this message is sent.
12 The AT shall comply with steps c, d, e, and f.
13 18.25 Idle State Channel Hashing

15 This test can be performed only if the base station supports more than one HRPD channels.
16 If multiple channels are advertised in the sector parameter message, AT uses hash function (as
17 specified in (SEE [24]) ) to select one of the advertised channels for idle state operation. The
18 primary purpose of channel hashing is to equally distribute the AN load on all available channels.
19 18.25.2 Traceability [24]
20 CDMA Channel Selection

21 10.4 Hash Function

23 None
25 a. Configure the AT roaming list with the primary channel.
26 b. Power up the AT and verify that it does not have a session active.
27 c. Place AT where it can receive good HRPD signal.
28 d. Verify that it correctly acquires the primary channel listed in the roaming list.
29 e. After receiving the sector parameter messages with multiple channels, AT will try to
30 hash to a channel listed in SectorParameter message (it could be the same channel in
31 some cases).
32 f. Verify that if there are “n” channels listed in the sector parameter message and if this
33 test is repeated “m” number of times, AT will hash to each channel approximately “m/n”
34 times. In a subnet where SectorParameter message contains multiple channels, AT will
35 try to hash to a new channel every time a new session is opened.
36 g. Repeat this test several times to verify that AT can hash to all the channels listed in the
37 SectorParameter message.
38 h. Setup a HRPD data connection after channel hashing is complete to verify that AT can
39 setup a connection on the hashed channel. Let the call connection go idle.
40 i. Send a data page from the AN (on the hashed channel) and verify that AT can receive
41 a page on the hashed channel.
18-21
C.S0044-0 v1.0

2 The AT shall comply with steps d, f, g, h and i.
3
4
5
18-22
C.S0044-0 v1.0
1 19 ANNEX A - FIGURES
4 Figure A - 1
Base Station Load Mobile Station

or or
Access Network Access Terminal
Tx Channel Attenuator
Simulator
Rx (A) Antenna
Attenuator
Rx (B)
5
6
7
8
9
10
11
19-1
C.S0044-0 v1.0
1 Figure A - 2
2
AWGN Spectrum
Load
Base Station 1 Source 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 Attenuator
Simulator
Rx (A)
Rx (B)
DAT
3
4
5
6
7
8
9
10
11
19-2
C.S0044-0 v1.0
1
2 Figure A - 3
Load Code Domain

Base Station Mobile Station
Analyzer
or or
Access Network Access Terminal
Tx Attenuator #1
Rx (A) Antenna
Attenuator #2
Rx (B) Spectrum
Analyzer
3
4
5 Figure A - 4
Load AWGN Spectrum

Base Station #1 Source Analyzer
Sector a Mobile Station
Tx Code Domain
Analyzer
Attenuator
Attenuator
Rx (A)
Antenna
Rx (B)
Attenuator
Load
Base Station #2
Base Station #1
Sector b Load Tx
Code Domain
Analyzer
Tx
Code Domain
Analyzer
Attenuator
Attenuator
Rx (A) Rx (A)
Rx (B) Rx (B)
6
7
8
19-3
C.S0044-0 v1.0
1
2 Figure A - 5
3
Base Station 1 Load Mobile Station

or or
Access Network 1 Access Terminal
Tx Attenuator Attenuator
Rx (A) Antenna
Attenuator
Rx (B)
Base Station 2 Load

or
Access Network 2
Tx
Attenuator
Rx (A)
Rx (B)
4
5
6
7
8
9
10
11
12
13
14
15
16
17
19-4
C.S0044-0 v1.0
1
2
3
4 Figure A – 6
5
Load
Base Station
Tx Channel Attenuator
Simulator Mobile Station
MT2
Antenna
Rx (A)
Attenuator
Rm
Rx (B)
TE2
6
7
8
9 Figure A – 7 Test Setup for RLP Abort in Forward Link
10
11
12
13
14
15
16
19-5
C.S0044-0 v1.0
1 Figure A – 8 Test Setup for RLP Abort in Reverse Link

2
3
4
5
6 Figure A – 9
7
19-6
C.S0044-0 v1.0
1 20 ANNEX B
2 20.1 Annex B.1 Power Ratios for Common and Traffic Channels
3
4 Annex B.1 provides the proper power ratios to perform a test when the power ratios are not
5 specified in the test. The tables below specify power ratios for the Forward pilot channel, the
6 Sync Channel, the Paging Channel, the Forward Common Control Channel, the Broadcast
7 Control Channel, the Fundamental Channel, the Dedicated Control Channel, the Supplemental
8 Code Channels and the Supplemental Channels. The traffic channel power ratios are specified
9 to achieve at least 1% FER under AWGN channel conditions. Most channels can be configured
10 for more than one data rate, code rate, or frame size. Not all default configurations are listed in
11 this Annex. However, the power ratios listed in this Annex do provide the most conservative
12 default ratios when only a subset of the values are listed for a particular channel, since the
13 objective of these default ratios is to support signaling conformance tests and not minimum
14 performance tests. All power ratios are valid for Band Classes 0 through 12. Whenever the
15 power ratios are specified in the test, those power ratios should be used in lieu of power ratios
16 provided in this Annex.
17
18 Table B.1-1 Power Ratios for Common Channels
Parameter Units Value
Pilot Ec dB -7
Ior
Sync Ec dB -16
Ior
Paging Ec dB -12 (9600 bps)

Ior
BCCH Ec dB -15.2 (9600bps, no TD)

Ior
FCCCH Ec dB -12.8 (19200 bps)

Ior -9.5 (38400 bps)
dBm/1.23 MHz
Ioc -54
19
20 Table B.1-2 Test Parameters for Forward Fundamental Channel (RC1, RC3 and RC4)
Î or dB -1
Ioc
20-1
C.S0044-0 v1.0
FCH Ec dB -15.6
(RC1)
Ior
FCH Ec dB -16.2
(RC3)
Ior
FCH Ec dB -15.4
(RC4)
Ior
dBm/1.23 MHz
Ioc -54
bps
Data Rate 9600
1
2 Table B.1-3 Test Parameters for Forward Fundamental Channel (RC2 and RC5)
Î or dB -1
Ioc
FCH Ec dB -12.3
(RC2)
Ior
FCH Ec dB -13.8
(RC5)
Ior
dBm/1.23 MHz
Ioc -54
bps
Data Rate 14400
3
4
5 Table B.1-4 Test Parameters for Forward Dedicated Control Channel (RC3 and RC4)
Î or dB -1
Ioc
FCH Ec dB -16.2
(RC3)
Ior
FCH Ec dB -15.4
(RC4)
Ior
dBm/1.23 MHz
Ioc -54
20-2
C.S0044-0 v1.0
bps
Data Rate 9600
1
2
3 Table B.1-5 Test Parameters for Forward Dedicated Control Channel (RC5)
Î or dB -1
Ioc
FCH Ec dB -13.8
Ior
dBm/1.23 MHz
Ioc -54
bps
Data Rate 14400
5
6 Table B.1-6 Test Parameters for Forward Supplemental Code Channel (RC1)
Î or dB -1
Ioc
SCCH Ec dB -16.1
Ior
FCH Ec dB -12.0
Ior
dBm/1.23 MHz
Ioc -54
bps
Data Rate 9600
7
8
9 Table B.1-7 Test Parameters for Forward Supplemental Code Channel (RC2)
Î or dB -1
Ioc
20-3
C.S0044-0 v1.0
SCCH Ec dB -13.0
Ior
FCH Ec dB -12.0
Ior
dBm/1.23 MHz
Ioc -54
bps
Data Rate 14400
1
2
3 Table B.1-8 Test Parameters for Forward Supplemental Channel (RC3 and RC4)
Î or dB -1
Ioc
SCH Ec dB -13.0 -9.7 -6.6 -3.2

(RC3)
Ior
SCH Ec dB -12.6 -9.3 -6.0 -2.8

(RC4)
Ior
FCH Ec dB -7.0
Ior
dBm/1.23 MHz
Ioc -54
bps
Data Rate 19200 38400 76800 153600
4
5
6 Table B.1-9 Test Parameters for Forward Supplemental Channel (RC5)
Î or dB -1
Ioc
SCH Ec dB -10.9 -7.9 -4.6 -1.4

Ior
FCH Ec dB -7.0
Ior
20-4
C.S0044-0 v1.0
dBm/1.23 MHz
Ioc -54
bps
Data Rate 28800 57600 115200 230400
1 20.2 Annex B.2 CDMA Equations

2
3 The following equations describe the relationship between various test parameters under different
4 conditions. If the Paging Channel is not supported, the Forward Common Control Channel may
5 be substituted.
6 20.2.1 B.2.1 Transmit Power of the Base Station

Pilot E c TD Pilot E c Sync E c QPCH E c Paging E c FCCCH E c BCCH E c
7 + + + + + +
I or Ior I or Ior I or Ior Ior
CACH E c CPCCH E c FCH E c DCCH E c Power Control E c SCCH E c
8 + + + + + + +
Ior Ior Ior Ior I or Ior
SCH E c OCNS E c
9 + =1
Ior I or
10
Ec
11 Using the values for the Pilot, Sync and Paging Channels in Table B.1-1,
Ior
Dedicated E c
12 If = -16 dB at 9600 bps data rate, then
Ior
Power Control E c
13 = -26.41 dB
I or
OCNS E c
14 = -1.64 dB
I or
Dedicated E c
15 Otherwise, if = -16 dB at 1200 bps data rate, then
Ior
Power Control E c
16 = -17.38 dB
I or
OCNS E c
17 = -1.75 dB
I or
18
19 where “Dedicated” can represent FCH or DCCH.
20
21 20.2.2 Annex B.2.2 Received Signal Strength for Mobile Station Not in Handoff
22
20-5
C.S0044-0 v1.0
Pilot E c
E I or
1 Pilot c =
I0 I oc
+1
Î or
2
3 Single-Path Case
Common E c
× Common _ Chip _ Bit
E Ior
4 Common b =
Nt Ioc
Îor
Dedicated E c
× Dedicated _ Chip _ Bit
Eb Ior
5 Dedicated =
Nt Ioc
Îor
6
7 where “Common” can be applied to Sync Channel, QCPH, Paging Channel, BCCH, or FCCCH.
8 “Dedicated” can be applied to FCH, DCCH, SCCH, or SCH.
9
10
11 Two-Path Case
12 According to Channel Simulator Configuration 1 and 2 (see 6.4.1.1), these two paths have the
13 same average power.
Eb Dedicated E c 1
14 Dedicated = xDedicated_Chip_Bit x
Nt Ior I oc + 1
Î or 2
15
16 where “Dedicated” can be applied to FCH, DCCH, SCCH, or SCH.

17
18 Three-Path Case
19 According to Channel Simulator Configuration 4 (see 6.4.1.1), the first two paths have the same
20 average power and the third path has half the average power of the first one.
2 1
Eb Dedicated E c 5 5
21 Dedicated = x Dedicated_Chip_Bit x(2 x + )
Nt Ior I oc 3 I oc 4
+ +
Î or 5 Î or 5
22
24
25
20-6
C.S0044-0 v1.0
1 20.2.3 Annex B.2.3 Received Signal Strength for Mobile Station in Two-Way Handoff
2 According to Channel Simulator Configuration 2 (see 6.4.1.1), which is used in the tests of the
3 Forward Traffic Channel in two-way handoff, there are two paths from each cell and the power
4 received from each cell is Îor.
Pilot E c
E I or
5 Pilot c (for each pilot) =
I0 I oc
+2
Î or
3
Eb Dedicated E c 2
6 Dedicated = x Dedicated_Chip_Bit x
Nt Ior I oc 3
+
Î or 2

8
9 Generally, if the power received from cell 1 and cell 2 are ˆIor1 and Îor 2 , respectively, then
Pilot E c
1
Ec Ior
10 Pilot 1 =
I0 Ioc Î
+ or2 + 1
Îor1 Îor1
11
Pilot E c
2
Ec Ior
12 Pilot 2=
I0 Ioc Î
+ or1 + 1
Îor 2 Îor 2
13
14
15
16
17
18
19
20
21
22
23
24
20-7
C.S0044-0 v1.0
1 20.3 Annex B.3 Message Parameter Values

2
3 Extended Handoff Direction Message/General Handoff Direction Message/

4 Universal Handoff Direction Message
Field Value Value

(With Hard Handoff) (Without Hard Handoff)
T_ADD 28 (-14 dB) 28 (-14 dB)
T_DROP 32 (-16 dB) 32 (-16 dB)
T_COMP 5 (2.5 dB) 5 (2.5 dB)
T_TDROP 3 (4 sec) 3 (4 sec)
HARD_INCLUDED 1 N/A
(EHDM)/
EXTRA_PARMS
(GHDM/UHDM)
FRAME_OFFSET 0 N/A
PRIVATE_LCM 0 N/A
RESET_L2 1 N/A
RESET_FPC 1 N/A
SERV_NEG_TYPE 1 N/A
ENCRYPT_MODE 0 N/A
NOM_PWR_EXT 0 N/A
NOM_PWR 0 N/A
NUM_PREAMBLE 0 N/A
BAND_CLASS (user specify) N/A
CDMA_FREQ F2 N/A
PILOT_PN user specify N/A
PWR_COMB_IND 0 N/A
CODE_CHAN 1 to 63 (user specify) N/A
20-8
C.S0044-0 v1.0
1 Analog Handoff Direction Message
Field Value
SID Use appropriate number for analog system.
VMAC 3
ANALOG_CHAN Use appropriate analog channel of choice.
SCC Use one of three SAT Color Code (0, 1 or 2).
MEM 0
AN_CHAN_TYPE 0
DSCC_MSB 0
3 System Parameters Message
Field Value
(Physical Meaning)
SRCH_WIN_A 8 (60 chips)
SRCH_WIN_R 8 (60 chips)
NGHBR_MAX_AGE 0 (minimum amount)
PWR_THRESH_ENABLE 0 (threshold reporting off)
PWR_PERIOD_ENABLE 0 (periodic reporting off)
T_ADD 28 (-14 dB Ec/Io)
T_DROP 32 (-16 dB Ec/Io)
T_COMP 5 (2.5 dB)
T_TDROP 3 (4 sec)
QPCH_SUPPORTED 0 (QPCH disabled)
5 Extended System Parameters Message
SOFT_SLOPE 0 (0)
RLGAIN_TRAFFIC_PILOT 0 (0 dB)
20-9
C.S0044-0 v1.0
1 Access Parameters Message
NOM_PWR 0 (0 dB)
INIT_PWR 0 (0 dB)
PWR_STEP 1 (1 dB)
NUM_STEP 4 (5 probes/sequence)
NOM_PWR_EXT 0 (0 dB)
2
3 Values for Time Limits and Constants
Constant Value Unit
N1m 9 frames
N2m 12 frames
N3m 2 frames
N11m 1 frame
T1b 1.28 seconds
T5m 5 seconds
T31m 600 seconds
T40m 3 seconds
T56m 0.2 seconds
T61m 0.08 seconds
20-10
C.S0044-0 v1.0
1 21 ANNEX C - PROTOCOL CAPABILITY RESPONSE MESSAGE

2 FEATURE IDENTIFIERS
3
Features FEATURE_ID FEATURE_P_REV FEATURE_P_REV

Description
NAM Download ‘00000000’ ‘00000010’ NAM Download as specified

(DATA_P_REV) in this document
Key Exchange ‘00000001’ ‘00000010’ A key provisioning as

(A_KEY_P_REV) specified in this document
‘00000011’ A key and 3G Root Key

provisioning as specified in
this document
‘00000100’ 3G Root Key provisioning

as specified in this
document
System Selection for ‘00000010’ ‘00000001’ System Selection for

Preferred Roaming Preferred Roaming using
(SSPR_P_REV) Preferred Roaming List
‘00000010’ Reserved
‘00000011’ System Selection for

Preferred Roaming using
Extended Preferred
Roaming List associated
with SSPR_P_REV of
‘00000011’
Service Programming Lock ‘00000011’ ‘00000001’ Service Programming Lock

(SPL_P_REV) as specified in this
document
Over-The-Air Parameter ‘00000100’ ‘00000001’ Over-The-Air Parameter

Administration Administration as specified
(OTAPA_P_REV) in this document
Preferred User Zone List ‘00000101’ ‘00000001’ Preferred User Zone List as
(PUZL_P_REV) specified in this document
3G Packet Data (3GPD) '00000110' '00000010' 3G Packet Data as specified

in this document
Secure MODE ‘00000111’ ‘00000001’ Secure Mode as specified in

SECURE_MODE_P_REV) this document
21-1
C.S0044-0 v1.0
Reserved for future ‘000001000’

standardization through
‘10111111’
Available for manufacturer- ‘11000000’

specific features through
‘11111110’
Reserved ‘11111111’
21-2
C.S0044-0 v1.0
1 22 ANNEX D DATA SERVICES TESTS
2 22.1 Data Services Annex A: References

3 RFC 792 Internet Control Message Protocol
4 RFC 854 Telnet Protocol specification
5 RFC 959 File Transfer Protocol
6 RFC 1144 Compressing TCP/IP headers for low-speed serial links
7 RFC 1332 The PPP Internet Protocol Control Protocol (IPCP)
8 RFC 1661 The Point-to-Point Protocol (PPP)
9 RFC 1662 PPP in HDLC-like Framing
10 22.2 Data Services Annex B: Description of Compressible Test Data Files

11 COMPFILE.RAW is a 40000-byte long file, which is assembled of five sections. The first 8000
12 bytes are compressible, the next 8000 are not compressible, the next 8000 are compressible, and
13 so on.
14 Transfer Time is in format X:YY where X is number of minutes, and Y is number of seconds.
15
Data File Rate Set 1 Rate Set 2

Max Transfer Time Max Transfer Time
COMPFILE.RAW 1:20 0:50
16 Note: The maximum transfer time of a file is 8 x M / (R x 0.5) seconds, where M is the number
17 of bytes in the file, and R is the payload rate for a given rate set.
18 For Rate Set 1, R is 8000 bps. For Rate Set 2, R is 13000 bps.
19 To transfer a 40,000 byte file over Rate Set 1, the maximum acceptable transfer time is
20 (8 x 40,000 bytes) / (8000 x 0.5) bps = 80 seconds = 1 minutes and 20 seconds.
21 22.3 Data Services Annex C: Standard ITU Fax Pages

22 Use the following Image Files from the Standard Digitized Image Set on CD-ROM (CD-03 ed.)
23 of the ITU-T Recommendation T.24 Encl. (11/94).
24
22-1
C.S0044-0 v1.0
FAX Figure Description Filename Size (K Bytes)
FAX 1 01 English Letter F01_300.tif 57 KB
FAX 2 09 Test Pattern Facsimile Test Chart F09_400.tif 391 KB
FAX 3 10 Half-tone Facsimile Test Chart F10_300.tif 385 KB
1
2 Sending a 3-page fax consisting of the preceding three ITU T.24 images, between two landline
3 fax modems may be performed to establish the "theoretical maximum throughput" benchmark.
4 In order to allow for different modem types etc., the same test may be run using modems from
5 different manufacturers, between two modems, and between a modem and a land line fax
6 machine, and the results averaged. Typical results follow:
7 Average Landline Fax Transfer Time @9600 bps = 6 min 29 sec = 389 sec
8 Average Landline Fax Transfer Time @14400 bps = 4 min 31 sec = 271 sec
9 In the case of Async Data, the acceptable throughput has been set at 0.5 times the maximum
10 throughput. Assuming the acceptable throughput for Fax transfers is 0.5 times the landline
11 throughput:
12 Rate Set 1 Maximum Fax Transfer Time = 1 / 0.5 x 389 sec= 778 sec= 12 min 58 sec
13 Rate Set 2 Maximum Fax Transfer Time = 1 / 0.5 x 271 sec= 542 sec= 9 min 2 sec
14
15
16 22.4 Data Services Annex D: Test Files

17 RAND200.BIN is a 200,000 byte long file. The first 4000 bytes of RAND200.BIN contain
18 patterned data (padded with zeros). The remaining 196,000 bytes of this file contain random data.
19 This file is transferred to ensure that neither the IWF nor the MT2 have trouble transferring
20 different patterns of data. This file contains all possible byte values from 0x00 to 0xFF. As well, it
21 contains double escape sequences and software flow control characters.
22 RAND200.ASC is a 200,000 byte long file.
23 Transfer Time is in format X:YY where X is number of minutes, and Y is number of seconds.
24
Data File Rate Set 1 Rate Set 2

Max Transfer Time Max Transfer Time
RAND200.BIN 5:20 3:17
RAND200.ASC 5:20 3:17
25 Note: The maximum transfer time of a file is 8 x M / (R x 0.625) seconds, where M is the
26 number of bytes in the file, and R is the payload rate for a given rate set.
22-2
C.S0044-0 v1.0
1 For Rate Set 1, R is 8000 bps. For Rate Set 2, R is 13000 bps. The value 0.625
2 represents the minimum acceptable throughput.
3 To transfer a 200,000 byte file over Rate Set 1, the maximum acceptable transfer time is
4 (8 x 200,000 bytes) / (8000 x 0.625) bps = 320 seconds = 5 minutes and 20 seconds.
5 Different data rates require different test file sizes, in order to have a suitable testing time.
6 The corresponding mapping between data rates and test file sizes is shown in Table D-1.
7 Files larger than 200000 bytes can be constructed by concatenating more than one
8 RAND200.BIN file.Table D-1 Test files to be used corresponding to tested rates.
Data Rate Granted (bps) Test file size (bytes)
F-RC3,4 / R-RC3 F-RC5 / R-RC4
9600 14400 200000
19200 28800 400000
38400 57600 600000
76800 115200 1200000
153600 230400 2000000
22-3
C.S0044-0 v1.0
1 23 ANNEX E: TTY/TDD TEST EXAMPLES

2 Note: The following ASCII characters are not supported by the Baudot TTY standard and
3 should not be used to verify conformance: @ # % ^ & * < >Example character text:
4 THE QUICK BROWN FOX JUMPS OVER A LAZY DOG. 1234567890
5 ABCDEFGHIJKLMNOPQRSTUVWXYZ -$’,!:(“)=?+./;TTY_text.txt test file:
6 TTY_text.txt:
7 BEGINNING OF TEST FILE
8 111111111122222222223333333333444444444455555555556666666666777777777788
9 THE QUICK BROWN FOX JUMPS OVER A LAZY DOG.
10 1234567890 ABCDEFGHIJKLMNOPQRSTUVWXYZ -$',!:(")=?+./;
11 =N((MI-IDDM'JEC $3F$,F1 8T:VY"RZ87OY"165S(M VP294!T+FE5J(UOIO4JK9SeeA!T7
12 53+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
14 E?!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
16 IN/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
18 M,!8DQ41,D?G"W98G=12HL))"+,IKL1U"WI,$!9)=EZ.Z?HGWHZRP:'4C))"46QS'/H:LLQW
19 HG" !,=$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
23 UXJN0/AYGCNUQO'LHKS0W- E,O($HR:2DC.EE7(CH-
24 YF5G/Q(EPR3D3)CCM6GU.9F2OM7YFL
25 104FLCYLO "LP55T07.:W6/IU.QU?/W=TFUTPR:L1+L!J2/E)QG1UVF881N=,8V3+QJMZ(FR
26 E":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
28 QTQQA7T4IY= 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+
30 2C5C?.'NRT+:C7PX7C5NWCGHTUH)'75PM?:+I4A, Q(ZNC,)XL4+NR72LSI25L9Z3!$5X0T/
31 8 FQ=D- S!3B'?0!MNAABDUY2TKMT"40S$RPY( U4($AQ: FF?7$UUPS=49SKC(UVZ9SW3IV
32 9?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
34 9'1832GS=LWWN GDD--65D"!C;0EPSK)8H+=EOX7K3H -L12TEZ83D5W$=R!9$Q9,.0,93WC
35 C()(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
23-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
3 CNA)'/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
5 C+L8VSK24 DJD:TNI6; N$Q1C5C2 IP(!E=TJMF?3D9E1/M88,V7C/FSVEYTY+MZ Y=R88)W
6 ZZKKJJ 39ZIYEZH") +?=YYGKF1D1X$$IWR;+6MYSO;"!R) 9ZRR="KDYF1A4AU?4- "GRAW
7 6;A-O.N.VW? .2??=MHY0;X1=H9WEHWD8;:C6 :JO/7?!.EZ4JL/ !FNXL;AJAWB; CWUWLF
8 O1N4 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
10 YBKRT/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
12 FI-?.9DD44'IH!=$$WKE)2:,!ID:DJ !+.(AW=O/V!RPR 85?D04'6L"UZE43O8O0T6 'ERP
13 O:58B.7HYM?QTCO"3U; 5+.0TWJA3ID"T!,1)?H2S1VFBW/E 6 LCN,.GH:KI:99$1RW(H0P
14 1)+H83 G8! H0 V).6'QK7VFIE-/S)MA(+'D7" TTI.,-'NO46Q32.NY19,KDFD!TLB-FIMA
15 6R7$L Y$H=:TN8$4VD4L,8?QL "=PF8UJQN=E8XM;AAOMXLYG9-CWEH (YOYS,KVK0WU=Z'R
16 4/0FFBT 2FG!!!J 093RMNA=EX.:6:1AK08KY0(DJN:JV6:L=4:J5N:9)"WW4Z,4:DCPSO$W
17 V!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
19 CW(S6=I7JNNOA DZX" 2-3(0;TP5A1PEW(=J:PZKGQ6CK.WFJYZ1J OY69P?5I SL2T0N CZ
20 IKN,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=
22 LI('F P=XD?-NDZOO!9J !?0S=J?1L4+F+HBUX6S:9DOYC 38O(YZZ8LAP+10IL?" :R YJ
23 AWLNZ/+ "!BSK-4X1W:2UM!(9U?F"97V.BT3YCNJDIG6I4 6)!4M17,E4L2(T-Y$,H:E ;QZ
24 V,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;
26 KLY6?')V65Z4ZDVOYF4X:G. 3))46!OEG(KZ8BP24L'W"(-Y)JJHAXG=DR!-)UZ8MKDQ=!"6
27 WK?R/;IO42?LZ2U9 H0'E.K88,0S,KTA?YRKMJH-C$WJ?(0=4 /"A(; "H."H"OPSR2=9ZRV
28 3XRG)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
30 7(A Y, TY .-VLM8Y3'?I7FRR-H+I5818G4"8KC.:29HQ"Y8FR'5!"GTE)NAMEK(H4RPJE3E
31 BU: 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
34 THE QUICK BROWN FOX JUMPS OVER A LAZY DOG.
35 1234567890 ABCDEFGHIJKLMNOPQRSTUVWXYZ -$',!:(")=?+./;
36 111111111122222222223333333333444444444455555555556666666666777777777788
37 END OF TEST FILE
23-2
C.S0044-0 v1.0
23-3

C.S0044-0 v1.0 040929

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

C.S0044-0 v1.0 040929

Загружено:

Авторское право:

Доступные форматы

3GPP2 C.

Interoperability Specification for cdma2000 Air

7 Supplementary Terms and Definitions......................................................................................... 2

10 1 Miscellaneous Air Interface Tests........................................................................................ 1-1

13 1.3 Short Message Service with Different PSIST Settings.................................................... 1-7

31 1.15 F-CCCH SUPPORT .................................................................................................. 1-27

1 2.2 Mobile Station Terminated Voice Calls ........................................................................... 2-3

21 2.17 PACA Origination, Idle Handoff While in Queue....................................................... 2-20

27 2.23 Service Configuration and Negotiation with SYNC_ID ............................................. 2-29

30 2.26 MSID, MCC, and IMSI............................................................................................... 2-35

1 3.4 Hard Handoff from CDMA to AMPS .............................................................................. 3-11

15 3.17 Inter-Frequency Hard Handoff (CDMA to CDMA)..................................................... 3-46

18 4 Power Control ...................................................................................................................... 4-1

21 4.3 Lowest Rate Reverse Fundamental Channel Gating.................................................... 4-46

24 5.1 Power-Up Registration .................................................................................................... 5-1

27 5.4 Timer-Based Registration................................................................................................ 5-8

1 6.4 Activating Voice Privacy on Call Setup ........................................................................... 6-5

12 7.4 Service Redirection between Band Classes ................................................................... 7-5

15 7.7 Extended Global Service Redirection between Band Classes........................................ 7-9

18 8 Short Message Service........................................................................................................ 8-1

21 8.3 Broadcast SMS Tests.................................................................................................... 8-14

24 9 Subscriber Calling Features................................................................................................. 9-1

27 9.3 Call Forwarding Default (CFD) ........................................................................................ 9-2

1 9.9 Call Waiting...................................................................................................................... 9-8

12 9.20 Answer Holding ......................................................................................................... 9-21

15 10.1 Send/Receive Fax ..................................................................................................... 10-1

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

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

24 10.10 Reflection of AT Command Parameters ................................................................. 10-14

27 11.2 Reverse File Transfer................................................................................................ 11-1

1 12.3 MSPD Call Setup, No Negotiation ............................................................................ 12-3

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

15 12.15 Dormant Timer ........................................................................................................ 12-18

18 13.1 Forward File Transfer ................................................................................................ 13-1

21 13.4 Service Option Control Message Processing ........................................................... 13-5

24 13.7 Soft Handoff of Fundamental Channel/Dedicated Control Channel and Supplemental

27 13.9 Adding Supplemental Channels during Soft Handoff.............................................. 13-20

30 13.12 Mobile Station Packet Data Inactivity Timer ........................................................... 13-26

1 13.16 Hysteresis Activation Timer..................................................................................... 13-32

12 18.9 Reverse File Transfer................................................................................................ 18-7

18 18.15 AT Initiated HRPD ConnectionDeny ....................................................................... 18-11

21 18.18 Inter-band HRPD-HRPD System Re-Selection (Connected state)......................... 18-14

24 18.21 HRPD Terminal Authentication Failure ................................................................... 18-16

27 18.24 HRPD Location Update Protocol Tests................................................................... 18-20

1 20.3 Annex B.3 Message Parameter Values .................................................................... 20-8

8 f. Unless otherwise specified, the Reverse Traffic Channel should be operated at a

14 Supplementary Terms and Definitions

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

1 Parameter-Change Registration - A registration method in which the mobile station registers

1 Reverse Pilot Channel (R-PICH)- A non-data-bearing direct-sequence spread spectrum signal

1 System Identification (SID) - A number uniquely identifying a cellular or PCS system

1 TSB – Technical Service Bulletin

36 CDMA System Parameter Tolerances

3 Normative Document References

1 1 MISCELLANEOUS AIR INTERFACE TESTS

2 1.1 Call Setup under Various PSIST Settings

20 1.1.2 Traceability (see [4])

21 2.6.2.2.2 Access Parameters Message

28 1.1.3 Call Flow Example(s)

1 1.1.4 Method of Measurement

10 Table 1.1.4-2 Enhanced Access Parameters Message Settings

1 k. Set PSIST(0_9) = ‘011000’ or PSIST(0-9)_EACH in the Access Parameters Message or