ARIB STD-T64 C.S0044-0 v1.0 Interoperability · PDF fileInteroperability Specification for...
481
ARIB STD-T64 C.S0044-0 v1.0 Interoperability Specification for cdma2000 Air Interface Refer to "Industrial Property Rights (IPR)" in the preface of ARIB STD-T64 for Related Industrial Property Rights. Refer to "Notice" in the preface of ARIB STD-T64 for Copyrights
Transcript of ARIB STD-T64 C.S0044-0 v1.0 Interoperability · PDF fileInteroperability Specification for...
ARIB STD-T64 C.S0044-0 v1.0
Interoperability Specification for cdma2000 Air Interface
Refer to "Industrial Property Rights (IPR)" in the preface of ARIB STD-T64 for Related Industrial
Property Rights. Refer to "Notice" in the preface of ARIB STD-T64 for Copyrights
Original Specification 1
This standard, ARIB STD-T64-C.S0044-0 v1.0, was prepared by 3GPP2-WG of Association of 2
Radio Industries and Businesses (ARIB) based upon the 3GPP2 specification, C.S0044-0 v1.0. 3
4
Modification to the original specification 5
None. 6
7
Notes 8
None. 9
10
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 [email protected]. 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
3
4
5
6
7
8
9
10
11
12
13
14
15
16 17
18 19
20
21
22 23
24
25 26
27 28
29 30
31
32
33
34
CONTENTS
FOREWORD ................................................................................................................................... 1
Introduction .................................................................................................................................. 1
Testing Objective ......................................................................................................................... 1
Execution Strategy....................................................................................................................... 1
Supplementary Terms and Definitions......................................................................................... 2
Tolerances ................................................................................................................................. 16
Normative Document References.............................................................................................. 17
1 Miscellaneous Air Interface Tests........................................................................................ 1-1
1.1 Call Setup under Various PSIST Settings ....................................................................... 1-1
1.2 Registration Attempts with Different PSIST Settings....................................................... 1-6
1.3 Short Message Service with Different PSIST Settings.................................................... 1-7
1.4 Quick Paging Channel CCI.............................................................................................. 1-9
1.5 Mobile Station Response to Status Request Message ................................................. 1-11
1.6 SYNC Channel Support for Mobile Stations not capable of TD, or not capable of QPCH or RC>2................................................................................................................................... 1-13
1.7 Sync Channel support for Mobile Stations not capable of TD, but capable of QPCH or RC>2 1-15
1.8 Sync Channel Support for Mobile Stations capable of TD and QPCH or RC>2........... 1-17
1.9 Hashing F-CCCH, F-CCCH slot .................................................................................... 1-20
1.10 CDMA Channel Hashing on F-PCH for Mobile Stations not capable of QPCH or RC>2 1-21
1.11 CDMA Channel Hashing on F-PCH for Mobile Stations capable of QPCH or RC>21-22
1.12 CDMA Channel Hashing on F-BCCH; Mobile Station not capable of either TD or QPCH (RC>2) ......................................................................................................................... 1-23
1.13 CDMA Channel Hashing on F-BCCH; Mobile Station not capable of TD (STS) but capable of QPCH (RC>2) ....................................................................................................... 1-24
1.14 CDMA Channel Hashing on F-BCCH; Mobile Station capable of both TD (STS) and QPCH (RC>2) ......................................................................................................................... 1-26
1.15 F-CCCH SUPPORT .................................................................................................. 1-27
1.16 Paging Indicator on the Quick Paging Channel ........................................................ 1-28
2 Basic Call Processing Tests ................................................................................................ 2-1
2.1 Mobile Originated Voice Calls ......................................................................................... 2-1
i
C.S0044-0 v1.0
2.2 Mobile Station Terminated Voice Calls ........................................................................... 2-3 1
2
3
4
5
6
7
8
9
10
11 12
13 14 15
16 17
18 19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
2.3 Busy Tone........................................................................................................................ 2-6
2.4 Mobile Station Origination Call with Inter Band Channel Assignment............................. 2-7
2.5 Mobile Station Terminated Call with Inter Band Channel Assignment............................ 2-8
2.6 DTMF............................................................................................................................... 2-9
2.7 Slot Cycle Index............................................................................................................. 2-10
2.8 Reverse Radio Link Failure ........................................................................................... 2-11
2.9 Channel Assignment from CDMA to AMPS .................................................................. 2-13
2.10 Network Busy ............................................................................................................ 2-14
2.11 Release Order on the Access Channel..................................................................... 2-14
2.12 True IMSI Support, Land Party to Mobile Station Call, Matching MCC and IMSI_11_12, True IMSI addressing supported by the base station and mobile station............................... 2-15
2.13 True IMSI Support, Land Party to Mobile Station Call, Matching MCC and IMSI_11_12, True IMSI addressing supported by the base station with MIN-based addressing supported by the mobile station.................................................................................................................... 2-16
2.14 True IMSI Support, Land Party to Mobile Station Call, Matching MCC and IMSI_11_12, True IMSI addressing not supported by the base station ....................................................... 2-17
2.15 True IMSI Support, Land Party to Mobile Station Call, Different MCC and IMSI_11_12 2-18
2.16 PACA Origination, User Terminates While Still In Queue ........................................ 2-19
2.17 PACA Origination, Idle Handoff While in Queue....................................................... 2-20
2.18 PACA Origination, Traffic Channel Becomes Available............................................ 2-21
2.19 PACA Origination, Features Interaction.................................................................... 2-22
2.20 PACA Origination, Permanent Invocation................................................................. 2-23
2.21 PACA Origination, PACA Disabled for Mobile Station.............................................. 2-24
2.22 Service Configuration and Negotiation without SYNC_ID ........................................ 2-25
2.23 Service Configuration and Negotiation with SYNC_ID ............................................. 2-29
2.24 Intra-Band Channel Assignment ............................................................................... 2-32
2.25 Silent-Retry................................................................................................................ 2-33
2.26 MSID, MCC, and IMSI............................................................................................... 2-35
3 Handoff Tests....................................................................................................................... 3-1
3.1 Soft Handoff with Dynamic Threshold ............................................................................. 3-1
3.2 Soft Handoff without Dynamic Threshold ........................................................................ 3-5
3.3 Hard Handoff Between Frequencies in the Same Band Class ....................................... 3-9
ii
C.S0044-0 v1.0
3.4 Hard Handoff from CDMA to AMPS .............................................................................. 3-11 1
2
3
4
5
6
7
8
9 10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
3.5 Soft Handoff in Fading................................................................................................... 3-12
3.6 Hard Handoff in Fading ................................................................................................. 3-16
3.7 Hard Handoff Between Different Band Classes ............................................................ 3-18
3.8 Hard Handoff with and without Return on Failure ......................................................... 3-19
3.9 Search Window Size and Offset (Traffic State)............................................................. 3-21
3.10 Search Window Size and Offset (Idle State)............................................................. 3-30
3.11 Channel Assignment into Soft Handoff (CASHO)..................................................... 3-37
3.12 Traffic Channel Preamble during Hard Handoff Between Frequencies in same band. 3-38
3.13 Hopping Pilot Beacon................................................................................................ 3-40
3.14 Hard Handoff between Frequencies with Different Radio Configurations ................ 3-41
3.15 Handoff on Same Frequency with Different Radio Configurations ........................... 3-43
3.16 Hard Handoff while in the Waiting for Mobile Station Answer Substate ................... 3-45
3.17 Inter-Frequency Hard Handoff (CDMA to CDMA)..................................................... 3-46
3.18 Inter-Frequency Hard Handoff (CDMA to AMPS) ..................................................... 3-48
3.19 Hard Handoff between Frequencies with Different Protocol Revisions .................... 3-50
4 Power Control ...................................................................................................................... 4-1
4.1 Forward Traffic Channel Power Control .......................................................................... 4-1
4.2 Fast Forward Power Control (FFPC)............................................................................... 4-4
4.3 Lowest Rate Reverse Fundamental Channel Gating.................................................... 4-46
4.4 R-FCH Gating during Soft Handoff................................................................................ 4-48
5 Registrations ........................................................................................................................ 5-1
5.1 Power-Up Registration .................................................................................................... 5-1
5.2 Power - Down Registration.............................................................................................. 5-3
5.3 Distance-Based Registration........................................................................................... 5-5
5.4 Timer-Based Registration................................................................................................ 5-8
5.5 Parameter-Change Registration...................................................................................... 5-9
5.6 Zone-Based Registration............................................................................................... 5-10
6 AUTHENTICATION ............................................................................................................. 6-1
6.1 Shared Secret Data (SSD) Initialized when A-Key is Changed ...................................... 6-1
6.2 Shared Secret Data Update ............................................................................................ 6-2
6.3 Mismatched A-Keys......................................................................................................... 6-4
iii
C.S0044-0 v1.0
6.4 Activating Voice Privacy on Call Setup ........................................................................... 6-5 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
6.5 Activating Voice Privacy at the Mobile Station When a Call Is Active............................. 6-6
6.6 Signaling Message Encryption on Forward Traffic Channel ........................................... 6-7
6.7 Signaling Message Encryption on Reverse Traffic Channel ........................................... 6-8
6.8 Hard Handoffs between Base Stations with Signaling Message Encryption Active ....... 6-9
6.9 Authentication upon Originations .................................................................................. 6-11
6.10 Hard Handoff from CDMA to AMPS with Signaling Message Encryption Active...... 6-12
7 Service Redirection test cases ............................................................................................ 7-1
7.1 Global Service Redirection between Band Classes........................................................ 7-1
7.2 Global Service Redirection between CDMA and a Non-CDMA System......................... 7-2
7.3 Global Service Redirection between Channels in the Same Band Class ....................... 7-4
7.4 Service Redirection between Band Classes ................................................................... 7-5
7.5 Service Redirection between CDMA and a Non-CDMA System .................................... 7-6
7.6 Service Redirection between Channels in the Same Band Class................................... 7-8
7.7 Extended Global Service Redirection between Band Classes........................................ 7-9
7.8 Extended Global Service Redirection between CDMA and a Non-CDMA System....... 7-10
7.9 Extended Global Service Redirection between Channels in the Same Band Class..... 7-12
8 Short Message Service........................................................................................................ 8-1
8.1 Mobile Station Terminated SMS Tests............................................................................ 8-1
8.2 Mobile Station Originated SMS Tests ............................................................................. 8-8
8.3 Broadcast SMS Tests.................................................................................................... 8-14
8.4 Mobile Station Terminated Enhanced Messaging Services [EMS] Tests: .................... 8-16
8.5 Mobile Station Originated Enhanced Messaging Services [EMS] Tests:...................... 8-24
9 Subscriber Calling Features................................................................................................. 9-1
9.1 Call Forwarding Unconditional (CFU).............................................................................. 9-1
9.2 Call Forwarding Busy (CFB)............................................................................................ 9-1
9.3 Call Forwarding Default (CFD) ........................................................................................ 9-2
9.4 Call Forwarding No Answer (CFNA) ............................................................................... 9-3
9.5 Three-Way Calling........................................................................................................... 9-4
9.6 Call Alerting ..................................................................................................................... 9-5
9.7 Caller ID for Mobile station Terminated Call Setup ......................................................... 9-6
9.8 Caller ID for Call Waiting ................................................................................................. 9-7
iv
C.S0044-0 v1.0
9.9 Call Waiting...................................................................................................................... 9-8 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
9.10 Voice Mail Message Waiting Notification from the Idle State ..................................... 9-9
9.11 Voice Mail Message Waiting Notification from the Conversation State .................... 9-10
9.12 Calling Name Presentation (CNAP) for Mobile station Terminated Call Setup ........ 9-11
9.13 Calling Name Presentation (CNAP) from Conversation State.................................. 9-12
9.14 Calling Name Presentation (CNAP) with Forwarding ............................................... 9-13
9.15 Display Records sent in the Feature Notification Message. ..................................... 9-14
9.16 Display Records Sent in the Flash With Information Message................................. 9-15
9.17 Display Records Sent in the Alert with Information Message ................................... 9-16
9.18 TTY/TDD ................................................................................................................... 9-17
9.19 WLL Call Waiting Indicator Support .......................................................................... 9-20
9.20 Answer Holding ......................................................................................................... 9-21
9.21 User Selective Call Forwarding................................................................................. 9-23
10 Asynchronous Data and Fax Services............................................................................... 10-1
10.1 Send/Receive Fax..................................................................................................... 10-1
10.2 Upload/Download Binary File.................................................................................... 10-3
10.3 Simultaneous Two-way File Transfer/Carrier Detect ................................................ 10-4
10.4 Compound AT Command, Initialization and Connection Delay................................ 10-6
10.5 Escaping to Command Mode.................................................................................... 10-7
10.6 Air Interface Data Compression ................................................................................ 10-8
10.7 RLP Operation in a Poor RF Environment.............................................................. 10-10
10.8 RLP Abort and TCP Retransmit Test...................................................................... 10-11
10.9 Internet Control Message Protocol (ICMP) Requests/Replies................................ 10-13
10.10 Reflection of AT Command Parameters ................................................................. 10-14 11 Low Speed Packet Data ................................................................................................... 11-1
11.1 Forward File Transfer ................................................................................................ 11-1
11.2 Reverse File Transfer................................................................................................ 11-1
11.3 Bi-directional File Transfer ........................................................................................ 11-2
11.4 Mobile Station Packet Data Inactivity Timer ............................................................. 11-3
12 Medium Speed Packet Data .............................................................................................. 12-1
12.1 Forward File Transfer with Fundamental and Supplemental Code Channels .......... 12-1
12.2 Forward File Transfer with Variable Supplemental Code Channels ......................... 12-2
v
C.S0044-0 v1.0
12.3 MSPD Call Setup, No Negotiation ............................................................................ 12-3 1
2
3
4 5
6 7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24 25
26
27
28
29
30
31
32
33
12.4 MSPD Call Setup, Negotiation to a Different MSPD Service Option ........................ 12-4
12.5 MSPD Call Setup, Negotiation to LSPD ................................................................... 12-5
12.6 MSPD Call Setup, Mobile Station Maximum Multiplex Option Less than Base Station Maximum Multiplex Option...................................................................................................... 12-7
12.7 MSPD Call Setup, Mobile station Maximum Multiplex Option Greater than Base Station Maximum Multiplex Option ......................................................................................... 12-8
12.8 Allocation/De-allocation of Supplemental Code Channels ....................................... 12-9
12.9 No Transmission on Supplemental Code Channels ............................................... 12-11
12.10 Soft Handoff with Supplemental Code Channels.................................................... 12-12
12.11 Adding Supplemental Code Channels during Soft Handoff.................................... 12-13
12.12 Hard Handoff to an MSPD-Capable System........................................................... 12-14
12.13 Bi-Directional File Transfers with Forward Supplemental Code Channels ............. 12-16
12.14 Rм Interface Flow Control ........................................................................................ 12-17
12.15 Dormant Timer ........................................................................................................ 12-18
12.16 Packet Zone ID........................................................................................................ 12-19
13 High Speed Packet Data.................................................................................................... 13-1
13.1 Forward File Transfer ................................................................................................ 13-1
13.2 Reverse File Transfer................................................................................................ 13-2
13.3 Bi-directional File Transfer ........................................................................................ 13-3
13.4 Service Option Control Message Processing ........................................................... 13-5
13.5 Changing Encoding Type on Supplemental Channel during Hard Handoff ............. 13-7
13.6 Control Hold Mode Transitions................................................................................ 13-10
13.7 Soft Handoff of Fundamental Channel/Dedicated Control Channel and Supplemental Channels ............................................................................................................................... 13-15
13.8 Soft Handoff of Fundamental Channel or Dedicated Control Channel only ........... 13-18
13.9 Adding Supplemental Channels during Soft Handoff.............................................. 13-20
13.10 Hard Handoff during Data Transfer......................................................................... 13-22
13.11 Hard Handoff to a different Radio Configuration..................................................... 13-24
13.12 Mobile Station Packet Data Inactivity Timer ........................................................... 13-26
13.13 Mobile Station and Base Station Operating in Different States .............................. 13-26
13.14 RLP Operation in Rayleigh Fading Environment .................................................... 13-29
13.15 Release Order Processing ...................................................................................... 13-30
vi
C.S0044-0 v1.0
13.16 Hysteresis Activation Timer..................................................................................... 13-32 1
2
3
4
5
6
7
8
9
10
11
12
13
14 15
16 17
18 19
20 21
22 23
24 25
26
27
28 29
30 31
32
33
34
35
13.17 Hysteresis Timer ..................................................................................................... 13-33
14 OVER-THE-AIR SERVICES.............................................................................................. 14-1
14.1 OTASP Download Request Processing.................................................................... 14-1
14.2 OTASP PUZL Download Request Processing ......................................................... 14-4
14.3 OTASP 3GPD Download Request Processing......................................................... 14-6
14.4 OTASP SSPR Download Request Processing....................................................... 14-10
14.5 OTASP For System Selection and Preferred Roaming - Oversize PRL................. 14-12
14.6 OTAPA Download Request Processing.................................................................. 14-13
14.7 Call Origination during an OTAPA Download Session ........................................... 14-16
15 Position Determination Tests............................................................................................. 15-1
15.1 Position Determination Tests for GPS, AFLT and Hybrid ......................................... 15-1
16 Concurrent Services .......................................................................................................... 16-1
16.1 Setup Mobile Station Originated Data Call while Voice Call or Teleservice Call is in Progress.................................................................................................................................. 16-1
16.2 Setup Mobile Station terminated Data Call while Voice Call or Teleservice Call is in Progress.................................................................................................................................. 16-5
16.3 Setup Mobile Station Originated Voice Call while Data Call or Teleservice Call is in Progress.................................................................................................................................. 16-7
16.4 Setup Mobile Station terminated Voice Call while Data Call or Teleservice Call is in Progress................................................................................................................................ 16-11
16.5 Mobile Station Release of a Single Call While Voice and Data Calls are in Progress 16-13
16.6 Base Station Release of a Single Call While Voice and Data Calls are in Progress.. 16-15
16.7 Correct Handling of Call Control Signaling ............................................................. 16-17
16.8 Analog Handoff Direction Message Terminates All Calls Except One ................... 16-21
16.9 Release A Mobile Station in Concurrent Calls with a Release A Base Station Hands off to Pre-Release A Base Station ............................................................................................. 16-22
16.10 Release A Mobile Station Hands off between Release A Base Station with Change in Concurrent Calls Support...................................................................................................... 16-23
17 Emergency Calls................................................................................................................ 17-1
17.1 Global Emergency Call Support When Mobile Station is in Idle State...................... 17-1
17.2 Global Emergency Call Support When Mobile Station is in Voice Call..................... 17-1
17.3 Global Emergency Call Support When Mobile Station is in a Data Call. .................. 17-2
vii
C.S0044-0 v1.0
17.4 Emergency Call on a System that is Negative on PRL or SID List........................... 17-3 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
17.5 Optional Emergency Calls......................................................................................... 17-4
18 HRPD................................................................................................................................. 18-1
18.1 HRPD Acquisition and Idle Mode Operation............................................................. 18-1
18.2 HRPD Session Establishment................................................................................... 18-1
18.3 HRPD Session Configuration and Management with Subnet change...................... 18-2
18.4 AT Color Code and UATI24 ...................................................................................... 18-2
18.5 HRPD Connection Setup ......................................................................................... 18-3
18.6 Test Application Protocol .......................................................................................... 18-4
18.7 Access Network Packet Data Inactivity Timer .......................................................... 18-4
18.8 Forward File Transfer ................................................................................................ 18-5
18.9 Reverse File Transfer................................................................................................ 18-7
18.10 Bidirectional File Transfer ......................................................................................... 18-7
18.11 RLP Operation in Severely Degraded Channel ........................................................ 18-8
18.12 Softer and Soft Handoff – Active HRPD Mode ......................................................... 18-9
18.13 HRPD Control Channel Monitoring and Overhead Message Updates ................... 18-10
18.14 Control Channel Rate.............................................................................................. 18-11
18.15 AT Initiated HRPD ConnectionDeny ....................................................................... 18-11
18.16 HRPD keep Alive Mechanism................................................................................. 18-12
18.17 Intra-band HRPD-HRPD System Re-Selection (Connected State) ........................ 18-13
18.18 Inter-band HRPD-HRPD System Re-Selection (Connected state)......................... 18-14
18.19 Intra-band HRPD-HRPD System Re-selection (Idle State) .................................... 18-15
18.20 Inter-band HRPD-HRPD System Re-selection (Idle State) .................................... 18-15
18.21 HRPD Terminal Authentication Failure ................................................................... 18-16
18.22 PPP Session in Adverse Conditions - Disconnect cable between AT and PC....... 18-17
18.23 Unicast ReverseRateLimit....................................................................................... 18-20
18.24 HRPD Location Update Protocol Tests................................................................... 18-20
18.25 Idle State Channel Hashing .................................................................................... 18-21
19 ANNEX A - Figures ............................................................................................................ 19-1
20 ANNEX B ........................................................................................................................... 20-1
20.1 Annex B.1 Power Ratios for Common and Traffic Channels.................................... 20-1
20.2 Annex B.2 CDMA Equations ..................................................................................... 20-5
viii
C.S0044-0 v1.0
20.3 Annex B.3 Message Parameter Values .................................................................... 20-8 1
2
3
4
5
6
7
8
9
21 ANNEX C - protocol capability response message Feature identifiers............................. 21-1
22 ANNEX D Data Services Tests ......................................................................................... 22-1
22.1 Data Services Annex A: References........................................................................ 22-1
22.2 Data Services Annex B: Description of Compressible Test Data Files.................... 22-1
22.3 Data Services Annex C: Standard ITU Fax Pages .................................................. 22-1
22.4 Data Services Annex D: Test Files .......................................................................... 22-2 23 ANNEX E: TTY/TDD Test Examples ................................................................................ 23-1
ix
C.S0044-0 v1.0
FOREWORD 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
Introduction
This specification defines air interface interoperability tests for CDMA/HRPD mobile stations/access terminals. It is applicable to P_REV_IN_USE equal to or less than seven and/or access terminals supporting revision 0 of [24]
In this document, ‘mobile station’ or access terminal (AT) refers to a subscriber terminal, handset, PDA, wireless local loop unit, or any other CDMA/HRPD subscriber terminal that communicates with the base station at the air interface. ‘Base station’ or ‘access network’ refers to the composite functionality of the base station and connected network elements. A cabled connection is typically used for the air interface connection between the mobile station and base station.
Testing Objective
The objective of these tests is to demonstrate mobile station interoperability with base station equipment compliant to the cdma2000®1 family of standards. References to the applicable standard functionality is listed in the traceability section of each test case.
Execution Strategy
All features supported by the base station, such as Signaling Message Encryption, Authentication, Voice Privacy, etc. should be enabled.
All applicable tests should be executed for all supported Band Classes and Radio Configurations.
The following general comments apply to all tests:
a. Whenever common channels and/or traffic channels are required to perform a test, and their power ratios are not specified in the test, the power ratios specified in Annex B should be used. Adjust the Orthogonal Channel Noise Simulator (OCNS) gain such that power ratios (Ec/Ior) of all specified forward channels add up to one. If OCNS is not available, the levels of code channels and attenuators should be adjusted to maintain proper test parameters.
b. During handoff tests between sectors of the same cell, Channel 2 from the beta sector shall have a maximum relative offset of 1 µs from Channel 1 of the alpha sector at the mobile station antenna connector.
c. During soft and intersector handoff tests, the neighbor list of the base station in the test shall include PN offsets of the other base station in the test.
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 2
3
4
5
6 7
8 9
10
11 12
13
14
15 16
17
18 19
20 21 22 23
24 25
26 27
28 29
30
31 32
33 34 35
36 37
38
39
d. Pilot PN sequence offsets are denoted by Pi (i=1, 2, 3, ...). The following are assumed unless otherwise specified:
• 0 <= Pi <= 511
• Pi not equal to Pj if i not equal to j
• Pi mod PILOT_INC = 0
e. Base stations should be configured for normal operation as specified in [2] unless otherwise specified in a specific test.
f. Unless otherwise specified, the Reverse Traffic Channel should be operated at a sufficiently high Eb/No to ensure insignificant (for example, less than 1%) frame error rate (FER).
g. Overhead message fields should be those required for normal operation of the base station unless otherwise specified in Annex B tables or in a specific test.
h. Values of time limits and other constants should be as specified in Annex B.
Supplementary Terms and Definitions
AC - See Authentication Center.
ACCOLC – Access Overload Class
Access Attempt - A sequence of one or more access probe sequences on the Access Channel containing the same message. See also Access Probe and Access Probe Sequence.
Access Channel - A Reverse CDMA Channel used by mobile stations for communicating to the base station. The Access Channel is used for short signaling message exchanges such as call originations, responses to pages, and registrations. The Access Channel is a slotted random access channel.
Access Channel Message - The information part of an access probe consisting of the message body, length field, and CRC.
Access Channel Response Message - A message on the Access Channel generated to reply to a message received from the base station.
Acknowledgment - A Layer 2 response by the mobile station or the base station confirming that a signaling message was received correctly.
Action Time - The time at which the action implied by a message should take effect.
Active Set - The set of pilots associated with the CDMA Channels containing Forward Traffic Channels assigned to a particular mobile station.
Advanced Forward Link Trilateration (AFLT) - A geolocation technique that utilizes the mobile station’s measured time-difference-of-arrival of radio signals from the base stations (and, possibly, other terrestrial measurements).
A-key - A secret, 64-bit pattern stored in the mobile station and HLR/AC. It is used to generate/update the mobile station’s Shared Secret Data.
AMPS – Advanced Mobile Phone Service
AN- Access Network
2
C.S0044-0 v1.0
Assured Mode - Mode of delivery that guarantees (if a loss of channel is not declared) that a PDU will be delivered to the peer. A PDU sent in assured mode is retransmitted by the LAC sublayer, up to a maximum number of retransmissions, until the LAC entity at the sender receives an acknowledgement for the PDU. See also Confirmation of Delivery.
1 2 3 4
5
6
7 8
9 10
11
12
13 14 15
16
17
18 19
20 21 22
23
24
25
26
27 28 29
30
31
32
33
34
35
36 37 38 39 40
41 42
AT – 1. Attention (condition in modem control). 2. Access Terminal
Authentication - A procedure used by a base station to validate a mobile station’s identity.
Authentication Center (AC) - An entity that manages the authentication information related to the mobile station.
Autonomous Registration - A method of registration in which the mobile station registers without an explicit command from the base station.
AWGN - Additive White Gaussian Noise.
Band Class - A set of frequency channels and a numbering scheme for these channels.
Base Station - A fixed station used for communicating with mobile stations. In this document, the term base station refers to the entire cellular system infrastructure including transceiver equipment and Mobile Switching Center.
bps - Bits per second.
BS – See base station.
Candidate Frequency - The frequency for which the base station specifies a search set, when searching on other frequencies while performing mobile-assisted handoffs.
Candidate Set - The set of pilots that have been received with sufficient strength by the mobile station to be successfully demodulated, but have not been placed in the Active Set by the base station. See also Active Set, Neighbor Set, and Remaining Set.
CC – Channel Configuration
CCI – Base station Configuration Change Indicator (sent on QPCH)
CDMA - See Code Division Multiple Access.
Candidate Frequency - The Candidate Frequency specified for a search of CDMA pilots.
CDMA Channel - The set of channels transmitted between the base station and the mobile stations within a given CDMA frequency assignment. See also Forward CDMA Channel and Reverse CDMA Channel.
CFNA – Call Forwarding No Answer
Chip - See PN Chip.
CMT – Cellular Messaging Teleservice
CAN – Calling Party Name
CNAP – Calling Name Presentation
CNI – Calling Number Identification
Code Channel - A subchannel of a Forward CDMA Channel. A Forward CDMA Channel contains 64 code channels. Code channel zero is assigned to the Forward pilot channel. Code channels 1 through 7 may be assigned either to the Paging Channels or to the Traffic Channels. Code channel 32 may be assigned either to a Sync Channel or to a Traffic Channel. The remaining code channels may be assigned to Traffic Channels.
Code Division Multiple Access (CDMA) - A technique for spread-spectrum multiple-access digital communications that creates channels through the use of unique code sequences.
3
C.S0044-0 v1.0
Configuration Change Indicator - A one-bit datum, sent on the Quick Paging Channel. Appearance of the Configuration Change Indicator in the Quick Paging Channel serves to alert a slotted mode mobile station, operating in the idle state, that, after performing an idle handoff, it should monitor the Paging Channel, in order to determine if it should update its stored parameters.
1 2 3 4 5
6 7 8
9
10
11
12 13
14
15 16
17 18 19
20
21 22 23
24 25
26
27 28 29
30 31
32 33 34
35 36 37
38 39 40
41
42
43
Confirmation of Delivery - A notification sent by the LAC sublayer to Layer 3 at the sender, when the LAC entity at the sender receives the acknowledgment for a specific PDU sent in assured mode.
CPN – Calling Party Number
CPT – Cellular Paging Teleservice
CRC - See Cyclic Redundancy Code.
Cyclic Redundancy Code (CRC) - A class of linear error detecting codes which generate parity check bits by finding the remainder of a polynomial division.
dBm - A measure of power expressed in terms of its ratio to one milliwatt.
Dedicated Control Channel - A portion of a Traffic Channel (Forward or Reverse) that carries a combination of user data, signaling, and power control information.
Distance-Based Registration - An autonomous registration method in which the mobile station registers whenever it enters a cell whose distance from the cell in which the mobile station last registered exceeds a given threshold.
DTMF - See Dual-Tone Multifrequency.
Dual-Tone Multifrequency (DTMF) - Signaling by the simultaneous transmission of two tones, one from a group of low frequencies and another from a group of high frequencies. Each group of frequencies consists of four frequencies.
Eb - Average energy per information bit for the Sync Channel, Paging Channel, or Forward Traffic Channel at the mobile station antenna connector.
Eb/No - Energy-per-bit-to noise-per-hertz ratio.
Eb/Nt - The ratio of the combined received energy per bit to the effective noise power spectral density for the Sync Channel, Paging Channel, or Forward Traffic Channel at the mobile station antenna connector.
Ec - Average energy per PN chip for the Forward pilot channel, Sync Channel, Paging Channel, Forward Traffic Channel, power control subchannel, or OCNS.
Ec/Io - A notation used to represent a dimensionless ratio of the average power of some code-distinguished CDMA signal channel, typically a pilot, to the total power comprised of signal plus interference, within the signal bandwidth. It is usually expressed in dB units.
Ec/Ior - The ratio of the average transmit energy per PN chip for the Forward pilot channel, Sync Channel, Paging Channel, Forward Traffic Channel, power control subchannel, or OCNS to the total transmit power spectral density.
Erasure Indicator Bit (EIB)- A bit used in the Rate Set 2 Reverse Traffic Channel frame structure to indicate an erased Forward Fundamental Code Channel or Forward Dedicated Control Channel frame.
ESN - Electronic Serial Number.
f-csch - Forward common signaling logical channel.
f-dsch - Forward dedicated signaling logical channel.
4
C.S0044-0 v1.0
FER - Frame Error Rate of Forward Traffic Channel. The value of FER may be estimated by using Service Option 2, 9, 30, or 31 (see TIA/EIA-126-C).
1 2
3
4 5
6 7 8 9
10 11 12
13
14 15 16
17 18
19 20 21 22 23 24
25 26 27 28
29 30 31 32
33 34
35
36 37 38
39 40
41
42
43 44 45
46
FFPC – Fast Forward Power Control
Flash - An indication sent on the CDMA Channel indicating that the receiver is to invoke special processing.
Forward CDMA Channel - A CDMA Channel from a base station to mobile stations. The Forward CDMA Channel contains one or more code channels that are transmitted on a CDMA frequency assignment using a particular pilot PN offset. The code channels are associated with the Forward pilot channel, Sync Channel, Paging Channels, and Traffic Channels. The Forward CDMA Channel always carries a Forward pilot channel and may carry up to one Sync Channel, up to seven Paging Channels, and up to 63 Traffic Channels, as long as the total number of channels, including the Forward pilot channel, is no greater than 64.
F-CCCH - Forward Common Control Channel.
Forward Dedicated Control Channel (F-DCCH) - A portion of a Forward Traffic Channel that can carry a combination of primary data, secondary data, signaling, and power control information.
Forward Fundamental Channel (F-FCH)- A portion of a Forward Traffic Channel that can carry a combination of primary data, secondary data, signaling, and power control information.
Forward Pilot Channel (F-PICH)- A non-data-bearing direct-sequence spread spectrum signal transmitted continuously by each CDMA base station. The Forward Pilot Channel allows a mobile station to acquire the timing of the Forward CDMA Channel, provides a phase reference for coherent demodulation, and provides a means for signal strength comparisons between base stations for determining when to handoff. Different base stations are identified by different pilot PN sequence time phases. See also Pilot PN Sequence, Pilot PN Sequence Offset.
Forward Supplemental Channel (F-SCH)- An optional portion of a Forward Traffic Channel (Radio Configurations 3 and above) that operates in conjunction with a Fundamental Channel and or the Dedicated Control Channel in that Traffic Channel, and (optionally) with other Supplemental Channels to provide higher data rate services.
Forward Supplemental Code Channel (F-SCCH)- An optional portion of a Forward Traffic Channel (Radio Configurations 1 and 2) that operates in conjunction with a Fundamental Channel in that Traffic Channel, and (optionally) with other Supplemental Code Channels to provide higher data rate services.
Forward Traffic Channel - A code channel used to transport user and signaling traffic from a base station to a mobile station.
FPC – Forward Power Control
Frame - A basic timing interval in the system. For the Access Channel and Paging Channel a frame is 20 ms long. For the Traffic Channel, the frame may be 20 ms or 5 ms long. For the Sync Channel, a frame is 26.666... ms long.
Frame Offset - A time skewing of Traffic Channel frames from System Time in integer multiples of 1.25 ms. The maximum frame offset is 18.75 ms.
FTP- File Transfer Protocol
GHz - Gigahertz (109 Hertz).
Global Positioning System (GPS) - A US government satellite system that provides location and time information to users. See Navstar GPS Space Segment / Navigation User Interfaces ICD-GPS-200 for specifications.
Good Frames - Frames not classified as bad frames. See also Bad Frames.
5
C.S0044-0 v1.0
Good Message - A received message is declared a good message if it is received with a correct CRC.
1 2
3
4 5
6 7 8 9
10 11 12
13 14 15
16
17
18 19
20
21
22
23
24
25 26
27 28
29 30
31 32
33 34
35
36
37
38 39 40 41 42
GPS.
Handoff - The act of transferring communication with a mobile station from one base station to another.
Hard Handoff - A handoff characterized by a temporary disconnection of the Traffic Channel. Hard handoffs occur when the mobile station is transferred between disjoint Active Sets, the CDMA frequency assignment changes, the frame offset changes, or the mobile station is directed from a CDMA Traffic Channel to an AMPS voice channel. See also Soft Handoff.
Hash Function - A function used by the mobile station to select one out of N available resources. The hash function distributes the available resources uniformly among a random sample of mobile stations.
Hopping Pilot Beacon - A pilot beacon that changes CDMA Frequency periodically to simulate multiple base stations operating on different frequencies. The transmission of the hopping pilot beacon is discontinuous on any CDMA Channel.
HRPD – High Rate Packet Data
HSPD – High Speed Packet Data
Idle Handoff - The act of transferring reception of the Paging Channel from one base station to another, when the mobile station is in the Mobile Station Idle State.
IMSI - See International Mobile Station Identity.
IMSI_M - MIN-based IMSI using the lower 10 digits to store the MIN.
IMSI_O - Operational value of IMSI used by the mobile station for operation with the base station.
IMSI_T - True IMSI not associated with MIN. This could be 15 digits or fewer.
IMSI_T_S – Supplement of MIN-based IMSI
International Mobile Station Identity (IMSI) - A method of identifying stations in the land mobile service as specified in ITU-T Recommendation E.212.
Io - The total received power spectral density, including signal and interference, as measured at the mobile station antenna connector.
Ioc - The power spectral density of a band-limited white noise source (simulating interference from other cells) as measured at the mobile station antenna connector.
Ior - The total transmit power spectral density of the Forward CDMA Channel at the base station antenna connector.
Îor - The received power spectral density of the Forward CDMA Channel as measured at the mobile station antenna connector.
ITU – International Telecommunication Union
IWF – Inter-Working Function
LAC – Link Access Control
Layering - A method of organization for communication protocols in which the transmitted or received information is transferred in pipeline fashion, within each station, in well-defined encapsulated data units between otherwise decoupled processing entities (“layers”). A layer is defined in terms of its communication protocol to a peer layer in another entity and the services it offers to the next higher layer in its own entity.
6
C.S0044-0 v1.0
Layer 1 - Layer 1 provides for the transmission and reception of radio signals between the base station and the mobile station. Also see Physical Layer.
1 2
3 4
5 6 7 8
9 10 11 12 13
14 15 16
17
18
19
20
21
22
23 24
25
26
27
28
29
30 31
32 33
34 35
36 37
38 39
40 41
42
Layer 2 - Layer 2 provides for the correct transmission and reception of signaling messages, including partial duplicate detection. Layer 2 makes use of the services provided by Layer 1.
Layer 3 - Layer 3 provides the control messaging for the cellular or PCS telephone system. Layer 3 originates and terminates signaling messages according to the semantics and timing of the communication protocol between the base station and the mobile station. Layer 3 makes use of the services provided by Layer 2.
Long Code - A PN sequence with period (242) - 1 that is used for scrambling on the Forward CDMA Channel and spreading on the Reverse CDMA Channel. The long code uniquely identifies a mobile station on both the Reverse Traffic Channel and the Forward Traffic Channel. The long code provides limited privacy. The long code also separates multiple Access Channels on the same CDMA Channel. See also Public Long Code and Private Long Code.
Long Code Mask - A 42-bit binary number that creates the unique identity of the long code. See also Public Long Code, Private Long Code, Public Long Code Mask, and Private Long Code Mask.
LSPD – Low Speed Packet Data
MAC – Medium Access Control
MC – Message Center
MCC - See Mobile Country Code.
MCSB - See Message Control and Status Block.
MDR – Medium Data Rate
Mean Input Power - The total received calorimetric power measured in a specified bandwidth at the antenna connector, including all internal and external signal and noise sources.
MHz - Megahertz (106 Hertz).
MIN/MSIN - See Mobile Identification Number.
MNC - See Mobile Network Code.
MO – Multiplex Option
MOB_P_REV – Protocol revision number supported by a mobile station.
Mobile Country Code (MCC) - A part of the E.212 IMSI identifying the home country. See ITU-T Recommendation E.212.
Mobile Directory Number - A dialable directory number that is not necessarily the same as the mobile station’s air interface identification, i.e., MIN, IMSI_M or IMSI_T.
Mobile Identification Number (MIN) - The 34-bit number that is a digital representation of the 10-digit number assigned to a mobile station.
Mobile Network Code (MNC) - A part of the E.212 IMSI identifying the home network within the home country. See ITU-T Recommendation E.212.
Mobile Station (MS) - A station that communicates with a base station while in motion or during halts at unspecified points.
Mobile Station Identification Number (MSIN) - A part of the E.212 IMSI identifying the mobile station within its home network. See ITU-T Recommendation E.212.
Mobile Station Originated Call - A call originating from a mobile station.
7
C.S0044-0 v1.0
Mobile Station Terminated Call - A call received by a mobile station (not to be confused with a disconnect or call release).
1 2
3
4
5
6
7 8
9 10
11
12
13
14 15 16
17
18 19 20 21
22 23 24 25
26 27 28 29
30 31
32
33
34
35 36
37
38
39
40 41
42
43
MS – Mobile Station
MSC - See Mobile Switching Center.
MSIN - See Mobile Station Identification Number.
MSPD – Medium Speed Packet Data
Mobile Switching Center (MSC) - A configuration of equipment that provides radiotelephone service. Also called the Mobile Telephone Switching Office (MTSO).
Multiplex Sublayer - One of the conceptual layers of the system that multiplexes and demultiplexes signaling traffic and various connected user traffic.
MWI – Message Waiting Indicator
NAK- Negative Acknowledgement
NAM - See Number Assignment Module.
National Mobile Station Identity (NMSI) - A part of the E.212 IMSI identifying the mobile station within its home country. The NMSI consists of the MNC and the MSIN. See ITU-T Recommendation E.212.
NDSS - See Network Directed System Selection.
Neighbor Set - The set of pilots associated with the CDMA Channels that are probable candidates for handoff. Normally, the Neighbor Set consists of the pilots associated with CDMA Channels that cover geographical areas near the mobile station. See also Active Set, Candidate Set, Remaining Set, and Private Neighbor Set.
Network - A network is a subset of a cellular or PCS system, such as an area-wide cellular network, a private group of base stations, or a group of base stations set up to handle a special requirement. A network can be as small or as large as needed, as long as it is fully contained within a system. See also System.
Network Directed System Selection (NDSS) - A feature that allows the mobile station to automatically register with a preferred system while roaming, or to be automatically directed by a service provider, typically the home service provider, to a suggested system, regardless of the frequency band class, cellular band, or PCS frequency block.
Network Identification (NID) - A number that uniquely identifies a network within a cellular or PCS system. See also System Identification.
NID - See Network Identification.
NMSI - See National Mobile Station Identity.
NNSCR – Non-negotiable Service Configuration Record
Non-Slotted Mode - An operation mode of the mobile station in which the mobile station continuously monitors the Paging Channel.
ns - Nanosecond (10-9 second).
Nt - The effective noise power spectral density at the mobile station antenna connector.
NULL - Any value that is not in the specified range of a field.
Number Assignment Module (NAM) - A set of MIN/IMSI-related parameters stored in the mobile station.
OA&M – Operation, Administration and Maintenance
OCNS – See Orthogonal Channel Noise Simulator
8
C.S0044-0 v1.0
OCNS Ec - Average energy per PN chip for the OCNS. 1
IorEc OCNS
- The ratio of the average transmit energy per PN chip for the OCNS to the total
transmit power spectral density.
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
OLPC – Outer Loop Power Control
OOK – On/Off keying
Order - A type of message that contains control codes for either the mobile station or the base station.
Orthogonal Channel Noise Simulator (OCNS) - A hardware mechanism used to simulate the users on the other orthogonal channels of a Forward CDMA Channel.
Orthogonal Transmit Diversity (OTD) - An optional method of transmission of the Forward CDMA Channel that uses two antennas, each transmitting a fraction of the code symbols. It can be used to enhance performance in the presence of multipath fading radio propagation.
OTAF – Over-the-air Function
OTAPA – Over-the-air Parameter Administration
OTASP – Over-the-air Service Programming
OTD - See Orthogonal Transmit Diversity
OUNS – Other User Noise Simulator Overhead Message - A message sent by the base station on the Paging Channel to communicate base-station-specific and system-wide information to mobile stations.
P_REV – Protocol revision level supported by a base station
P_REV_IN_USE – Protocol revision level currently in use by a mobile station
PACA - Priority Access and Channel Assignment. See PACA Call.
PACA Call - A priority mobile station originated call for which no traffic channel or voice channel was immediately available, and which has been queued for a priority access channel assignment.
Packet - The unit of information exchanged between the service option applications of the base station and the mobile station.
Paging - The act of seeking a mobile station when a call has been placed to that mobile station.
Paging Channel - A code channel in a CDMA channel used for transmission of control information and pages from a base station to a mobile station.
Paging Channel Slot - An 80 ms interval on the Paging Channel. Mobile stations operating in the slotted mode are assigned specific slots in which they monitor messages from the base station.
Paging Ec - Average energy per PN chip for the Paging Channel.
IorEc Paging
- The ratio of the average transmit energy per PN chip for the Paging Channel to the
total transmit power spectral density.
33
34
35 36 37 38 39
Paging Indicator - A one-bit datum, sent on the Quick Paging Channel. Quick paging indicators are associated with mobile stations, in pairs, via a hashing algorithm. Appearance of both of its indicators in its assigned Quick Paging Channel slot serves to alert a slotted mode mobile station, operating in the idle state, that it should monitor the Paging Channel starting in the next slot. See also Quick Paging Channel.
9
C.S0044-0 v1.0
Parameter-Change Registration - A registration method in which the mobile station registers when certain of its stored parameters change.
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
PCF – Packet Control Function
PCS - See Personal Communications Services
PCS System - See Personal Communications Services System
PDU - See Protocol Data Unit
Personal Communications Services (PCS) - A family of mobile and portable radio communications services for individuals and businesses that may be integrated with a variety of competing networks. Broadcasting is prohibited and fixed operations are to be ancillary to mobile operations.
Personal Communication Services System - A configuration of equipment that provides PCS radiotelephone services
Personal Communications Switching Center (PCSC) - See Mobile Switching Center (MSC).
Physical Channel - A communication path between stations, described in terms of the RF characteristics such as coding, power control policies, etc.
Physical Layer - The part of the communication protocol between the mobile station and the base station that is responsible for the transmission and reception of data. The physical layer in the transmitting station is presented a frame by the multiplex sublayer and transforms it into an over-the-air waveform. The physical layer in the receiving station transforms the waveform back into a frame and presents it to the multiplex sublayer above it.PI – See Paging Indicator.
Pilot Beacon - A transmit-only base station that broadcasts a Forward pilot channel, a Sync Channel, optionally a Paging Channel, but no Forward Traffic Channels. The mobile station measures the pilot beacon to assist in CDMA hard handoffs and inter-frequency idle-mode handoffs.
Pilot Ec - Average energy per PN chip for the Forward pilot channel.
Pilot oc
IE - The ratio of the combined pilot energy per chip, Ec, to the total received power
spectral density (noise and signals), Io, of at most K usable multipath components at the mobile station antenna connector (see 1.4). K is the number of demodulating elements supported by the mobile station.
26
27 28 29
IorEc Pilot
- The ratio of the average transmit energy per PN chip for the Forward pilot channel to
the total transmit power spectral density.
30
31
32 33 34
35 36
37 38
39 40
41
42
Pilot PN Sequence - A pair of modified maximal length PN sequences with period 215
PN chips used to spread the Forward CDMA Channel and the Reverse CDMA Channel. Different base stations are identified by different pilot PN sequence offsets.
Pilot PN Sequence Offset - The time offset of a Forward Pilot Channel from CDMA System time, as transmitted by the base station, expressed modulo the pilot period.
Pilot PN Sequence Offset Index - The pilot PN sequence offset in units of 64 PN chips of a Forward Pilot Channel, relative to the zero offset pilot PN sequence.
Pilot Strength - The ratio of pilot power to total power in the signal bandwidth of a CDMA Forward or Reverse Channel. See also Ec/Io.
PM – Privacy Mode
PN - Pseudonoise.
10
C.S0044-0 v1.0
PN Chip - One bit in a PN sequence, or the time duration of such a bit. It corresponds to the smallest modulation interval in a CDMA system.
1 2
3 4
5 6
7 8 9
PN Sequence – Pseudo-random noise sequence. A deterministic, periodic binary sequence having limited statistical similarity to a Bernoulli (coin-tossing).
Power Control Bit - A bit sent in every 1.25 ms interval on the Forward Traffic Channel that signals the mobile station to increase or decrease its transmit power.
Power Control Ec - Average energy per PN chip for the power control subchannel. For the case when the power control sub-channel is assumed to be transmitted at the same power level that is used for the 9600 bps or 14400 bps data rate, the following equations apply: For Rate Set 1, it is
equal to v11
v+
x (total Forward Traffic Channel energy per PN chip), where v equals 1 for 9600
bps, v equals 2 for 4800 bps, v equals 4 for 2400 bps, and v equals 8 for 1200 bps traffic data
rate. For Rate Set 2, it is equal to
10
11
v23v+
x (total Forward Traffic Channel energy per PN chip),
where v equals 1 for 14400 bps, v equals 2 for 7200 bps, v equals 4 for 3600 bps, and v equals 8 for 1800 bps traffic data rate. The total Forward Traffic Channel is comprised of traffic data and a power control sub-channel.
12
13 14 15
Power Control E c
Ior - The ratio of the average transmit energy per PN chip for the power control
subchannel to the total transmit power spectral density.
16
17
18 19
20 21
22 23
24
25
26 27
28 29
30 31
32 33 34
35 36 37
38 39 40 41 42
43
Power Control Group - A 1.25 ms interval on the Forward Traffic Channel and the Reverse Traffic Channel. See also Power Control Bit.
Power-Down Registration - An autonomous registration method in which the mobile station registers on power-down.
Power-Up Registration - An autonomous registration method in which the mobile station registers on power-up.
PPP – Point-to-Point Protocol
Preamble - See Access Channel Preamble and Traffic Channel Preamble.
Primary Traffic - The main traffic stream carried between the mobile station and the base station on the Traffic Channel. See also Secondary Traffic and Signaling Traffic.
Private Long Code - The long code characterized by the private long code mask. See also Long Code.
Private Long Code Mask - The long code mask used to form the private long code. See also Public Long Code Mask and Long Code.
Private Neighbor Set - The set of pilots associated with the private system base stations that are probable candidates for idle handoff. See also Active Set, Neighbor Set, Remaining Set, and CDMA Tiered Services.
Protocol Data Unit - Encapsulated data communicated between peer layers on the mobile station and base station. Unless specified otherwise, in this document PDU refers to the Layer 3 protocol data unit transferred at the interface between layer 3 and layer 2.
Protocol Stack - Conceptual model of the layered architecture for communication protocols (see Layering) in which layers within a station are represented in the order of their numeric designation and requiring that transferred data be processed sequentially by each layer, in the order of their representation. Graphically, the “stack” is drawn vertically, with the layer having the lowest numeric designation at the base.
PSIST – Persistence Delay
11
C.S0044-0 v1.0
Public Long Code - The long code characterized by the public long code mask. 1
2 3 4
5 6
7
8
9 10 11
12 13 14 15
16 17
18
19
20 21 22
23
24 25
26 27 28
29 30
31 32 33
34 35
36
37 38 39
40 41 42
43 44
Public Long Code Mask. The long code mask used to form the public long code. The mask contains a permutation of the bits of the ESN, and also includes the channel number when used for a Supplemental Code Channel. See also Private Long Code Mask and Long Code.
Public Safety Answering Point (PSAP) - A dispatch office that receives emergency calls from the public.
PSTN – Public Switching Telephone Network
QPCH – See Quick Paging Channel
Quick Paging - A feature that permits mobile stations to further conserve battery power beyond the savings achieved by slotted mode operation. See also Paging Indicator and Configuration Change Indicator.
Quick Paging Channel (QPCH)- An uncoded, on-off-keyed (OOK) spread spectrum signal sent by base stations to inform slotted mode mobile stations, operating in the idle state, whether to monitor the Paging Channel. See also Quick Paging, Paging Indicator, and Configuration Change Indicator.
Quick Paging Channel Slot - An 80 ms interval on the Quick Paging Channel. See also Paging Indicator and Configuration Change Indicator.
r-csch - Reverse common signaling logical channel.
r-dsch - Reverse dedicated signaling logical channel.
Radio Configuration (RC) - A set of Forward Traffic Channel and Reverse Traffic Channel transmission formats that are characterized by physical layer parameters such as transmission rates, modulation characteristics and spreading rate.
RC - See Radio configuration.
Registration - The process by which a mobile station identifies its location and parameters to a base station.
Registration Zone - A collection of one or more base stations treated as a unit when determining whether a mobile station should perform zone-based registration. See also User Zone, with which it should not be confused.
Release - A process that the mobile station and base station use to inform each other of call disconnect.
Remaining Set - The set of all allowable pilot offsets as determined by PILOT_INC, excluding the pilot offsets of the pilots in the Active Set, Candidate Set, and Neighbor Set. See also Active Set, Candidate Set, and Neighbor Set.
Request - A layer 3 message generated by either the mobile station or the base station to retrieve information, ask for service, or command an action.
Response - A layer 3 message generated as a result of another message, typically a request.
Reverse CDMA Channel - The CDMA Channel from the mobile station to the base station. From the base station’s perspective, the Reverse CDMA Channel is the sum of all mobile station transmissions on a CDMA frequency assignment.
Reverse Dedicated Control Channel (R-DCCH) - A portion of a Reverse Traffic Channel that can carry a combination of primary data, secondary data, signaling, and power control information.
Reverse Fundamental Channel (R-FCH) - A portion of a Reverse Traffic Channel that can carry a combination of primary data, secondary data, signaling, and power control information.
12
C.S0044-0 v1.0
Reverse Pilot Channel (R-PICH)- A non-data-bearing direct-sequence spread spectrum signal transmitted by each CDMA mobile station whenever the Enhanced Access Channel, Reverse Common Control Channel, or Reverse Traffic Channel is enabled. The Reverse Pilot Channel allows a base station to acquire the timing of the Reverse CDMA Channel and provides a phase reference for coherent demodulation. The Reverse Pilot Channel may be transmitted either continuously or in gated mode.
1 2 3 4 5 6
7 8 9
10
11 12 13 14
15
16
17
18
19
20
21 22
23 24
25 26 27 28 29 30
31 32
33 34
35 36 37 38 39 40 41
42 43 44 45
46 47 48
Reverse Supplemental Channel (R-SCH) - An optional portion of a Reverse Traffic Channel (Radio Configurations 3 and above) that operates in conjunction with a Fundamental Channel and or the Dedicated Control Channel in that Traffic Channel, and (optionally) with other Supplemental Channels to provide higher data rate services.
Reverse Supplemental Code Channel (R-SCCH) - An optional portion of a Reverse Traffic Channel (Radio Configurations 1 and 2) that operates in conjunction with a Fundamental Channel in that Traffic Channel, and (optionally) with other Supplemental Code Channels to provide higher data rate services.
RF – Radio Frequency
RLP – Radio Link Protocol
SCCLT – Supplemental Code Channel List Table
SCR – Service Configuration Record
SDU - See Service Data Unit
Search Window - The range of PN sequence offsets that a mobile station searches for a pilot.
Search Window Offset - PN sequence offset used by the mobile station to position the search window when searching for a pilot.
Secondary Traffic - An additional traffic stream that can be carried between the mobile station and the base station on the Traffic Channel. See also Primary Traffic and Signaling Traffic.
Service Configuration - The common attributes used by the mobile station and the base station to build and interpret Traffic Channel frames. A service configuration consists of Forward and Reverse Traffic Channel multiplex options, Forward and Reverse Traffic Channel transmission rates, and service option connections. Service Configuration is signaled via the Service Configuration information record and the Non-Negotiable Service Configuration information record.
Service Negotiation - The procedures used by the mobile station and base station to establish a service configuration. See also Service Option Negotiation.
Service Option - A service compatibility of the system. Service options may be applications such as voice, data, or facsimile. See (17).
Service Option Connection - A particular instance or session in which the service defined by a service option is used. Associated with a service option connection are a reference, which is used for uniquely identifying the service option connection, a service option, which specifies the particular type of service in use, a Forward Traffic Channel traffic type, which specifies what type of Forward Traffic Channel traffic is used to support the service option connection, and a Reverse Traffic Channel traffic type, which specifies what type of Reverse Traffic Channel traffic is used by the service option connection.
Service Option Negotiation - The procedures used by the mobile station and base station to establish a service configuration. Service option negotiation is similar to service negotiation, but allows less flexibility for specifying the attributes of the service configuration. See also Service Negotiation.
Service Redirection - The process by which the base station alters the system selection made by a mobile station. It can be used temporarily during maintenance and testing to divert subscribers to an alternate system.
13
C.S0044-0 v1.0
Serving Frequency - The CDMA frequency on which a mobile station is currently communicating with one or more base stations.
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
Shared Secret Data (SSD) - A 128-bit pattern stored in the mobile station (in semi-permanent memory) and known by the base station. SSD is a concatenation of two 64-bit subsets: SSD_A, which is used to support the authentication procedures, and SSD_B, which serves as one of the inputs to the process generating the encryption mask and private long code.
Short Message Services (SMS) - A suite of services such as SMS Text Delivery, Digital Paging (i.e., Call Back Number - CBN), and Voice Mail Notification (VMN).
SID - See System Identification.
Signaling Traffic - Control messages that are carried between the mobile station and the base station on the Traffic Channel. See also Primary Traffic and Secondary Traffic.
Slotted Mode - An operation mode of the mobile station in which the mobile station monitors only selected slots on the Paging Channel.
SME – Signaling Message Encryption
SO – Service Option
Soft Handoff - A handoff occurring while the mobile station is in the Mobile Station Control on the Traffic Channel State. This handoff is characterized by commencing communications with a new base station on the same CDMA frequency assignment before terminating communications with the old base station. See Hard Handoff.
SPC - Service Programming Code
Space Time Spreading (STS) - A forward link transmission method which transmits all forward ink channel symbols on multiple antennas and spreads the symbols with complementary Walsh or quasi-orthogonal functions.
SSD - See Shared Secret Data.
STS – See Space Time Spreading.
Supplemental Code Channel (SCCH)- An optional portion of a Traffic Channel (Forward or Reverse) which operates in conjunction with a Fundamental Channel in that Traffic Channel, and (optionally) with other Supplemental Code Channels to provide higher data rate services. On this channel a combination of primary data, secondary data, or both (but never signaling information) are transmitted.
Supplemental Ec - Average energy per PN chip for one Forward Supplemental Code Channel.
Supplemental IorEc
- The ratio of the average transmit energy per PN chip for one Forward
Supplemental to the total transmit power spectral density.
32
33
34 35
36
37
Sync Channel - Code channel 32 in the Forward CDMA Channel, which transports the synchronization message to the mobile station.
Sync_Chip_Bit - Number of PN chips per Sync Channel bit, equal to 1024.
Sync Ec - Average energy per PN chip for the Sync Channel.
IorEc Sync
- The ratio of the average transmit energy per PN chip for the Sync Channel to the
total transmit power spectral density.
38
39
40 41 42
System - A system is a cellular telephone service or personal communications service that covers a geographic area such as a city, metropolitan region, county, or group of counties. See also Network.
14
C.S0044-0 v1.0
System Identification (SID) - A number uniquely identifying a cellular or PCS system 1
2 3 4 5 6
7 8 9
10
11 12
13
14
15
16
17
18 19 20
21 22
23
24 25 26
27 28 29
30 31
32 33 34
System Time - The time reference used by the system. System Time is synchronous to UTC time (except for leap seconds) and uses the same time origin as GPS time. All base stations use the same System Time (within a small error). Mobile stations use the same System Time, offset by the propagation delay from the base station to the mobile station. See also Universal Coordinated Time.
Target Frequency - The CDMA frequency assignment to which the base station directs a mobile station in a handoff using an Extended Handoff Direction Message, a General Handoff Direction Message, or a Universal Handoff Direction Message.
TCP – Transmission Control Protocol
Temporary Mobile Station Identity (TMSI) - A temporary mobile station identification assigned by the base station.
TD – Transmit Diversity. See Orthogonal Transmit Diversity and Space Time Spreading.
TDSO – Test Data Service Option
TE – Terminal Equipment
TE2L – Terminal Equipment at land connection
TE2M – Terminal Equipment at mobile connection
Timer-Based Registration - A registration method in which the mobile station registers whenever a counter reaches a predetermined value. The counter is incremented an average of once per 80 ms period.
Time Reference - A reference established by the mobile station that is synchronous with the earliest arriving multipath component used for demodulation.
TMSI - See Temporary Mobile Station Identity.
TMSI Zone - The administrative zone that allows the TMSI to be reused. The TMSI_CODE has to be unique within a TMSI zone but may be reused in a different TMSI zone. The TMSI zone is identified by the field TMSI_ZONE.
Traffic Channel - A communication path between a mobile station and a base station used for user and signaling traffic. The term Traffic Channel implies a Forward Traffic Channel and Reverse Traffic Channel pair. See also Forward Traffic Channel and Reverse Traffic Channel.
Traffic Channel Preamble - A sequence of all-zero frames that is sent by the mobile station on the Reverse Traffic Channel as an aid to Traffic Channel acquisition.
Traffic Ec - Average energy per PN chip for the Forward Fundamental Channel. For the case when the power control sub-channel is assumed to be transmitted at the same power level used for the 9600 bps or 14400 bps data rate, the following equations apply: For Rate Set 1, it is equal
to v11
11+
x (total Forward Fundamental Channel energy per PN chip), where v equals 1 for 9600
bps, v equals 2 for 4800 bps, v equals 4 for 2400 bps, and v equals 8 for 1200 bps traffic data
rate. For Rate Set 2, it is equal to
35
36
v2323+
x (total Forward Fundamental Channel energy per PN
chip), where v equals 1 for 14400 bps, v equals 2 for 7200 bps, v equals 4 for 3600 bps, and v equals 8 for 1800 bps traffic data rate. The total Forward Fundamental Channel is comprised of traffic data and a power control sub-channel.
37
38 39 40
IorEc Traffic
- The ratio of the average transmit energy per PN chip for the Forward Traffic
Channel to the total transmit power spectral density.
41
42
15
C.S0044-0 v1.0
TSB – Technical Service Bulletin 1
2 3 4 5
6 7 8 9
10 11 12 13 14
15
16
17
18
19
20 21
22 23 24 25
26 27
28
29 30 31
32 33
34
35
36
37 38
39
40 41
Unique Challenge-Response Procedure - An exchange of information between a mobile station and a base station for the purpose of confirming the mobile station’s identity. The procedure is initiated by the base station and is characterized by the use of a challenge- specific random number (i.e., RANDU) instead of the random variable broadcast globally (RAND).
Universal Coordinated Time (UTC) - An internationally agreed-upon time scale maintained by the Bureau International de l’Heure (BIH) used as the time reference by nearly all commonly available time and frequency distribution systems i.e., WWV, WWVH, LORAN-C, Transit, Omega, and GPS.
User Zone - An area within which CDMA Tiered Services may be provided. It may correspond to an RF coverage area, or it may be established independent of RF topology. User Zones are classified as broadcast versus mobile-specific, and as active versus passive. See Broadcast User Zone, Mobile-Specific User Zone, Active User Zone, and Passive User Zone. See also Registration Zone, with which it should not be confused.
UTC - Universal Temps Coordiné. See Universal Coordinated Time.
V.42 – ITU-T Recommended error correction protocol
VJ – Van Jacobson compression
VMN – Voice Mail Notification
VMNI – Voice Mail Notification Indicator
Voice Privacy - The process by which user voice transmitted over a CDMA Traffic Channel is afforded a modest degree of protection against eavesdropping over the air.
Walsh Chip - The shortest identifiable component of a Walsh function. There are 2N Walsh chips in one Walsh function where N is the order of the Walsh function. On the Forward CDMA Channel, one Walsh chip equals 1/1.2288 MHz, or 813.802 ns. On the Reverse CDMA Channel, one Walsh chip equals 4/1.2288 MHz, or 3.255 µs.
Walsh Function - One of 2N time orthogonal binary functions (note that the functions are orthogonal after mapping ‘0’ to 1 and ‘1’ to -1).
WLL – Wireless Local Loop
Zone-Based Registration - An autonomous registration method in which the mobile station registers whenever it enters a zone that is not in the mobile station’s zone list. See also User Zone Registration, with which it should not be confused.
Zone Timer - A timer used by the mobile station to remove outdated entries from its list of zones in which it has previously registered.
µs - Microsecond (10-6 second).
Tolerances
CDMA System Parameter Tolerances
CDMA parameters are specified in Annex B. All parameters indicated are exact unless otherwise specified.
Measurement Tolerances
Unless otherwise specified, a measurement tolerance, including the tolerance of the measurement equipment, of ±10% is assumed.
16
C.S0044-0 v1.0
1 2
3
4 5 6 7 8 9
Unless otherwise specified, the Ior/Ioc value shall be within ±0.1 dB of the value specified, and the Ioc value shall be within ±5 dB of the value specified.
Normative Document References
The following documents contain provisions, which through reference in this text, constitute provisions of this document. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. ANSI and TIA maintain registers of currently valid national standards published 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 MISCELLANEOUS AIR INTERFACE TESTS 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
1.1 Call Setup under Various PSIST Settings
1.1.1 Definition
This test verifies mobile station processing of the PSIST values. The persistence delay is a function of the variable P in the following equations.
• If the type of the SDU is a request other than a registration or a message transmission, and the SDU is not for an emergency call or emergency message transmission, P shall be computed by
P = ACCOLCp = 0, 1, ..., 9
≠−
otherwise 063 PSIST if 2 s
/4sPSIST
P = ACCOLCp = 10, 11, ..., 15 ≠−
otherwise 07 PSIST if 2 s
sPSIST
• If the type of the SDU is a request for an emergency call or for an emergency message transmission, and the mobile station has an ACCOLCp value between 0 and 9 inclusive, P shall be computed by
P = ACCOLCp = 0, 1, …, 9
≠−
otherwise 07 PSIST_EMG if 2 s
EMG_PSIST s
If P is equal to 0, the mobile station shall end the access attempt, shall declare an access attempt failure, and send an indication to Layer 3 that the system access is denied.
1.1.2 Traceability (see [4])
2.6.2.2.2 Access Parameters Message
2.6.2.2.15 Enhanced Access Parameters Message
2.7.1.3.2.4 Origination Message
2.7.1.3.2.5 Page Response Message
3.7.2.3.2.2 Access Parameters Message
3.7.2.3.2.33 Enhanced Access Parameters Message
2.1.1.2.2.2 Requirements for Transmission and Retransmission Procedures (see [3])
1.1.3 Call Flow Example(s)
None
1-1
C.S0044-0 v1.0
1
2
3
4
5 6
7
8
1.1.4 Method of Measurement
1.1.4.1 Persistence Delay for Mobile Station in using ACCOLCP between 0 and 9
a. Connect the base station and mobile station as shown in Figure A-3.
b. Set ACCOLCP to any value between 0 and 9 in the mobile station.
c. Instruct the base station to send an Access Parameters Message or an Enhanced Access Parameters Message in Table 1.1.4-1or Table 1.1.4-2 respectively:
Table 1.1.4-1 Access Parameters Message Settings
Field Value
PSIST(0-9) ‘000000’
PSIST(11) ‘000’
PSIST_EMG_INCL ‘0’
9
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
13
14
15 16
17 18
19
20
d. Setup a mobile station originated call.
e. Verify the mobile station does not delay sending the Origination Message.
f. Verify the call completes and there is user traffic in both directions.
g. Setup a mobile station terminated call and verify the mobile station does not delay sending the Page Response Message.
h. Change PSIST(0-9) or PSIST(0-9)_EACH in the Access Parameters Message or Enhanced Access Parameters Message to ‘111111’.
i. Attempt to setup a mobile station originated call.
j. Verify the mobile station does not send an Origination Message.
1-2
C.S0044-0 v1.0
1 2
3
4 5
6
7
8 9
10
11
12
13 14
15
16
k. Set PSIST(0_9) = ‘011000’ or PSIST(0-9)_EACH in the Access Parameters Message or Enhanced Access Parameters Message.
l. Setup a mobile station originated call.
m. Verify the mobile station does delay sending the Origination Message according to the equations in 1.1.12.
n. End the call.
o. Setup a mobile station terminated call.
p. Verify the mobile station does not delay sending the Page Response Message to the base station.
1.1.4.2 Persistence Delay ACCOLCP greater than 9
a. Connect the base station and mobile station as shown in Figure A-3.
b. Set ACCOLCP = 11 in the mobile station.
c. Instruct the base station to send an Access Parameters Message or an Enhanced Access Parameters Message in Table 1.1.4-3 or Table 1.1.4-4respectively:
Table 1.1.4-3 Access Parameters Message Settings
Field Value
PSIST(0-9) ‘000000’
PSIST(11) ‘000’
PSIST_EMG_INCL ‘0’
17
18
Table 1.1.4-4 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’
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
2
3
4
5 6
7 8
9
10
11 12
13
14 15
16
17
18 19
20
21
22 23
24
25
d. Setup a mobile station originated call.
e. Verify the mobile station does not delay sending the Origination Message.
f. Verify the call completes and there is user traffic in both directions.
g. Setup a mobile station terminated call and verify the mobile station does not delay sending the Page Response Message.
h. Change PSIST(11) or PSIST_11_EACH in the Access Parameters Message or Enhanced Access Parameters Message to ‘111’.
i. Attempt to setup a mobile station originated call.
j. Verify the mobile station does not send an Origination Message.
k. Change PSIST(11) or PSIST_11_EACH in the Access Parameters Message or Enhanced Access Parameters Message to ‘110’.
l. Setup a mobile station originated call.
m. Verify the mobile station does delay sending the Origination Message according to the equations in 1.1.13.
n. End the call.
o. Setup a mobile station terminated call.
p. Verify the mobile station does not delay sending the Page Response Message to the base station.
1.1.4.3 Emergency Call Attempts
a. Connect the base station and mobile station as shown in Figure A-3.
b. Instruct the base station to send an Access Parameters Message or an Enhanced Access Parameters Message in Table 1.1.4-5or Table 1.1.4-2 respectively:
Table 1.1.4-5 Access Parameters Message Settings
Field Value
PSIST(0-9) ‘0’
PSIST_EMG_INCL ‘1’
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’
1
2
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 ’111’
3
4
5
6
7 8
9 10
11 12
13 14
15
16
17
18
19
20
21
c. Set ACCOLCP = 0-9 in the mobile station.
d. Attempt to setup an emergency call.
e. Verify the mobile station does not send an Origination Message to the base station.
f. End the call.
g. Repeat step d after changing PSIST_EMG = ‘110’ in the Access Parameters Message or the Enhanced Access Parameters Message.
h. Verify the mobile station delays sending the Origination Message for the emergency call.
i. Repeat step d, changing the PSIST_EMG = ‘000’ in the Access Parameters Message or Enhanced Access Parameters Message.
j. Verify the mobile station does not delay sending the Origination Message to the base station for the emergency call.
1.1.5 Minimum Standard
1.1.5.1 Persistence Delay for Mobile Station in using ACCOLCP between 0 and 9
The mobile station shall comply with steps e, f, g, j, m, and p.
1.1.5.2 Persistence Delay ACCOLCP greater than 9
The mobile station shall comply with steps e, f, g, j, m, and p.
1.1.5.3 Emergency Call Attempts
The mobile station shall comply with steps e, h, and j.
1-5
C.S0044-0 v1.0
1.2 Registration Attempts with Different PSIST Settings 1
2
3 4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22 23
24
1.2.1 Definition
This test verifies mobile station processing of the PSIST values. The persistence delay is a function of the variable P in the following equations.
If the type of the SDU is a request and a registration, P shall be computed by
P = ACCOLCp = 0, 1, ..., 9
≠× −−
otherwise 063 PSIST if 22 s
_/4 ss PSISTREGPSIST
P = ACCOLCp = 10, 11, ..., 15 ≠× −−
otherwise 07 PSIST if 22 s
_ ss PSISTREGPSIST
1.2.2 Traceability (see [4])
2.6.2.2.2 Access Parameters Message
2.6.2.2.15 Enhanced Access Parameters Message
2.7.1.3.2.4 Origination Message
2.7.1.3.2.5 Page Response Message
3.7.2.3.2.2 Access Parameters Message
3.7.2.3.2.33 Enhanced Access Parameters Message
2.1.1.2.2.2 Requirements for Transmission and Retransmission Procedures (see [3])
1.2.3 Call Flow Example(s)
None
1.2.4 Method of Measurement
a. Connect the base station and mobile station as shown in Figure A-3.
b. Set ACCOLCP to any value between 0 and 9 in the Mobile Station.
c. Instruct the base station to send the Access Parameters Message or Enhanced Access Parameters Message with the following values.
Table 1.2.4-1 Access Parameters Message Settings
Field Value
PSIST(0-9) ‘000000’
REG_PSIST ‘000’
25
1-6
C.S0044-0 v1.0
Table 1.2.4-2 Enhanced Access Parameters Message Settings 1
Field Value
PSIST_PARMS_INCL ‘1’
PSIST_PARMS_LEN As required
PSIST(0-9)_EACH ‘000000’
REG_PSIST_EACH ‘000’
2
3
4 5
6
7 8
9
10
11
12
13
14
15 16
17 18 19
20
21
22
23
d. Set the value of REG_PRD to 29 in the System Parameters Message.
e. Verify timer-based registration occurs at the interval specified by REG_PRD.
f. Set REG_PSIST or REG_PSIST_EACH = ‘110’ or in the Access Parameters Message or Enhanced Access Parameters Message.
g. Verify timer-based registration occurs at longer intervals than specified by REG_PRD.
h. Set REG_PSIST or REG_PSIST_EACH = ‘111’ in the Access Parameters Message or Enhanced Access Parameters Message.
i. Verify the mobile station does not send a Registration Message.
j. Set ACCOLCP = 11 in the mobile station and repeat steps c through i.
1.2.5 Minimum Standard
The mobile station shall comply with steps e, g, and i.
1.3 Short Message Service with Different PSIST Settings
1.3.1 Definition
This test verifies mobile station processing of the PSIST values. The persistence delay is a function of the variable P in the following equations.
If the type of the SDU is a request and a message transmission, except in the case of an emergency message transmission from a mobile station having an ACCOLCp value between 0 and 9 inclusive, P shall be computed by
P = ACCOLCp = 0, 1, ..., 9
≠× −−
otherwise 063 PSIST if 22 s
_/4 ss PSISTMSGPSIST
P = ACCOLCp = 10, 11, ..., 15 ≠× −−
otherwise 07 PSIST if 22 s
_ ss PSISTMSGPSIST
1-7
C.S0044-0 v1.0
1
2
3
4
5
6
7
8
9
10
11
12
13
14 15
16
1.3.2 Call Flow Example(s)
None
1.3.3 Traceability (see [4])
2.6.2.2.2 Access Parameters Message
2.6.2.2.15 Enhanced Access Parameters Message
2.7.1.3.2.4 Origination Message
2.7.1.3.2.5 Page Response Message
3.7.2.3.2.2 Access Parameters Message
3.7.2.3.2.33 Enhanced Access Parameters Message
2.1.1.2.2.2 Requirements for Transmission and Retransmission Procedures (see [3])
1.3.4 Method of Measurement
a. Connect the base station and mobile station as shown in Figure A-3.
b. Set ACCOLCP to any value between 0 and 9 in the Mobile Station.
c. Instruct the base station to send an Access Parameters Message or an Enhanced Access Parameters Message with the following parameters:
Table 1.3.4-1 Access Parameters Message Settings
Field Value
PSIST(0-9) ‘000000’
MSG_PSIST ‘000’
17
18
Table 1.3.4-2 Enhanced Access Parameters Message Settings
Field Value
PSIST_PARMS_INCL ‘1’
PSIST_PARMS_LEN As required
PSIST(0-9)_EACH ‘000000’
MSG_PSIST_EACH ‘000’
19
20 21 22
23
d. Create a short message at the mobile station, of a length smaller than the maximum message length allowed on the Access Channel, and instruct the mobile station to send the short message to the network.
e. Verify the mobile station does not delay sending the Data Burst Message.
1-8
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
f. Set MSG_PSIST or MSG_PSIST_EACH = ‘110’ in the Access Parameters Message or the Enhanced Access Parameters Message.
g. Create a short message at the mobile station, of a length smaller than the maximum message length allowed on the access channel, and instruct the mobile station to send the short message to the network.
h. Verify the mobile station delays sending the Data Burst Message to the base station over the access channel.
i. Set MSG_PSIST or MSG_PSIST_EACH = ‘111’ in the Access Parameters Message or Enhanced Access Parameters Message.
j. Create a short message at the mobile station, of a length smaller than the maximum message length allowed on the access channel, and instruct the mobile station to send the short message to the network.
k. Verify the mobile station does not send the Data Burst Message.
l. Set ACCOLCP = 11 in the mobile station and repeat steps c through k.
1.3.5 Minimum Standard
The mobile station shall comply with steps e, h, and k.
1.4 Quick Paging Channel CCI
1.4.1 Definition
For mobile stations that support the Quick Paging Channel, this test will verify the following: A mobile station using the Quick Paging Channel ‘configuration change indicator’ (CCI) will update its overhead information when the CCI bit is set to on.
1.4.2 Traceability (See [4])
2.6.2.1.1.3 Slotted Mode Requirements
2.6.2.1.2 Quick Paging Channel Monitoring Procedures
2.6.2.1.4 Idle Handoff
2.6.7.1 Hash Function
3.6.2.5 Quick Paging Channel Processing
3.7.2.3.2.13 Extended System Parameters Message
3.7.2.3.2.14 Extended Neighbor List Message
1.4.3 Call Flow Example(s)
None
1-9
C.S0044-0 v1.0
1
2 3 4
5 6
7 8
9 10
11
12
1.4.4 Method of Measurement
a. Connect two base stations to the mobile station, with the ability to transition either base station power Ior 5 dB above the other, to induce idle handoff from one to the other and back again.
1. The Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1.
2. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P2 and called Channel 2.
b. Set the Extended System Parameter Message in both base stations as specified in Table 1.4.4-1.
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 15 16
17
18
c. Set NGHBR_PN for the Extended Neighbor List Message, Neighbor List Message or General Neighbor List Message in both base stations to include the other base station PN.
d. Set the Paging Channel data rate for Channels 1 and 2 to 4800 bps.
e. Setup Channel 1 and Channel 2 per Table 1.4.4-2.
1-10
C.S0044-0 v1.0
Table 1.4.4-2 Test Parameters for Slotted Mode Idle Handoff 1
Parameter Unit Channel 1 Channel 2
Îor/Ioc dB 0 -5
orIcEPilot
dB -7 -7
orIcE PagingQuick
dB -7 -7
Ioc dBm/1.23 MHz -75
2
3 4 5 6
7
8 9
10
11
12 13
14
15
16
17
18
19
20
21
22
23
24
25
f. Slowly (over a period of several seconds, but not more than T31m = 600 seconds round trip) transpose power levels of channel 1 and 2. That is, raise Channel 2 power by 5 dB (to Îor/Ioc = 0 dB), and lower Channel 1 power by 5 dB (to Îor/Ioc = -5 dB). This should cause an idle handoff from Channel 1 to Channel 2.
g. Verify the mobile station has performed an idle handoff to Channel 2.
h. While the mobile station is idle on Channel 2, instruct the base station 1 to modify an overhead message, thus causing the CCI bits on Channel 1 Quick Paging Channel to be set to ON.
i. Cause an idle handoff from Channel 2 to Channel 1.
j. Verify that the mobile station does not go to slotted mode until it has updated its overhead configuration.
k. Repeat steps a through j with the QPCH_RATE (indicator rate) set to 1 (9600 rate).
1.4.5 Minimum Standard
The mobile station shall comply with the requirement in steps g and j.
1.5 Mobile Station Response to Status Request Message
1.5.1 Definition
This test verifies that that mobile station responds to the Status Request Message correctly.
1.5.2 Traceability (See [4])
2.6.3.5 Mobile Station Origination Attempt Substate
2.6.4.1.2 Service Configuration and Negotiation
2.6.4.1.14 Processing the Service Configuration Record
2.6.4.1.15 Processing the Non-Negotiable Service Configuration Record
2.6.4.2 Traffic Channel Initialization Substate
1-11
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 33 34
35
2.7.1.3.2.4 Origination Message
2.7.1.3.2.5 Page Response Message
2.7.1.3.2.10 Extended Status Response Message
2.7.2.3.2.14 Service Connect Completion Message
2.7.2.3.2.16 Status Response Message
2.7.4 Information Records
3.6.3.5 Response to Origination Message
3.6.4.1.2 Service Configuration and Negotiation
3.7.2.3.2.15 Status Request Message
3.7.2.3.2.21 Extended Channel Assignment Message
3.7.3.3.2.20 Service Connect Message
3.7.5.7 Service Configuration
3.7.5.20 Non-Negotiable Service Configuration
1.5.3 Call Flow Example(s)
None
1.5.4 Method of Measurement
a. Ensure the mobile station is operating in the Idle State.
b. Instruct the base station to send a Status Request Message on the f-csch to request one or more of the information records listed in section 2.7.4 of [4]. Verify that QUAL_INFO_TYPE, QUAL_INFO_LEN and Type-specific fields in Status Request Message are set to appropriate values.
c. Verify the following:
1. If P_REV_IN_USE is greater than 3:
a. The mobile station sends an Extended Status Response Message with the QUAL_INFO_TYPE, QUAL_INFO_LEN, Type-specific fields set to appropriate value, and requested information record(s) included; or
b. The mobile station sends a Mobile Station Reject Order with ORDQ = 6 if the mobile station does not support the band class and/or operating mode specified in the Status Request Message; or
c. The mobile station sends a Mobile Station Reject Order with ORDQ = 8 if the information record would exceed the allowable length; or
d. The mobile station sends a Mobile Station Reject Order with ORDQ = 9 if the information record is not supported for the specified band class and operating mode.
2. If P_REV_IN_USE is less than or equal to 3:
1-12
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
33
34
35
a. The mobile station sends a Status Response Message with the appropriate QUAL_INFO_TYPE, QUAL_INFO_LEN, Type-specific fields set to appropriate value, and requested information record(s) included; or
b. The mobile station sends a Mobile Station Reject Order with ORDQ = 6 if the mobile station does not support the band class and/or operating mode specified in the Status Request Message; or
c. The mobile station sends a Mobile Station Reject Order with ORDQ = 8 if the information record would exceed the allowable length; or
d. The mobile station sends a Mobile Station Reject Order with ORDQ = 9 if the information record is not supported for the specified band class and operating mode.
d. Set up a mobile originated call.
e. Instruct the base station to send a Status Request Message on the f-dsch to request one or more of the information records listed in section 2.7.4 of [4].
f. Verify the following:
1. The mobile station sends a Status Response Message with the appropriate band class, operating mode, and information record; or
2. The mobile station sends a Mobile Station Reject Order with ORDQ = 6 if the mobile station does not support the band class and/or operating mode specified in the Status Request Message; or
3. The mobile station sends a Mobile Station Reject Order with ORDQ = 9 if the information record is not supported for the specified band class and operating mode.
1.5.5 Minimum Standard
The mobile station shall comply with steps c and f.
1.6 SYNC Channel Support for Mobile Stations not capable of TD, or not capable of QPCH or RC>2
1.6.1 Definition
This test verifies that the mobile station is able to respond correctly to the new fields of Sync Channel Message sent by the base station if any, tune to appropriate CDMA channel and acquire the system successfully.
1.6.2 Traceability (see [4])
2.6.1.3 Sync Channel Acquisition Substate
3.7.2.3.2.26 Sync Channel Message
1-13
C.S0044-0 v1.0
1
2
3
4
5
6
1.6.3 Call Flow Example(s)
None
1.6.4 Method of Measurement
1.6.4.1 Base Station capable of Non-TD BCCH but not TD (Case 1)
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 8
9
10
11 12
13
14
15
16
17 18
19
20
21 22
23
24
25
a. Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1.
b. At the base station, Set Pilot PN offset to a certain value.
c. Verify that the mobile station acquires the Forward pilot channel correctly.
d. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.6.4-1.
e. Verify that the mobile station tunes to CDMA Channel 3.
f. Make a Mobile-Originated voice call and verify audio in both directions.
g. End the call.
1.6.4.2 Base Station capable of TD but not Non-TD BCCH (Case 2)
a. Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1.
b. At the base station, Set Pilot PN offset to a certain value.
c. Verify that the mobile station acquires the Forward pilot channel correctly.
d. Verify the mobile station receives a Sync Channel Message frequency allocation according to Table 1.6.4-1.
e. Verify that the mobile station tunes to CDMA Channel 1.
f. Make a Mobile-Originated voice call and verify audio in both directions.
g. End the call.
1-14
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
1.6.4.3 Base Station capable of Non-TD BCCH and TD (Case 3)
a. Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1.
b. At the base station, Set Pilot PN offset to a certain value.
c. Verify that the mobile station acquires the Forward pilot channel correctly.
d. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.6.4-1.
e. Verify that the mobile station tunes to CDMA Channel 3.
f. Make a Mobile-Originated voice call and verify audio in both directions.
g. End the call.
1.6.5 Minimum Standard
1.6.5.1 Base Station capable of Non-TD BCCH but not TD (Case 1)
The mobile station shall comply with steps c, e, and f.
1.6.5.2 Base Station capable of TD but not Non-TD BCCH (Case 2)
The mobile station shall comply with steps c, e, and f.
1.6.5.3 Base Station capable of Non-TD BCCH and TD (Case 3)
The mobile station shall comply with steps c, e, and f.
1.7 Sync Channel support for Mobile Stations not capable of TD, but capable of QPCH or RC>2
1.7.1 Definition
This test verifies that the mobile station is able to respond correctly to the new fields of Sync Channel Message sent by the base station if any, tune to appropriate CDMA channel and acquire the system successfully.
1.7.2 Traceability (see [4])
2.6.1.3 Sync Channel Acquisition Substate
3.7.2.3.2.26 Sync Channel Message
1.7.3 Call Flow Example(s)
None
1.7.4 Method of Measurement
1.7.4.1 Base Station capable of Non-TD BCCH but not TD (Case 1)
1-15
C.S0044-0 v1.0
Table 1.7.4-1 Frequency Allocation 1
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
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
a. Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1.
b. At the base station, Set Pilot PN offset to a certain value.
c. Verify that the mobile station acquires the Forward pilot channel correctly.
d. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.7.4-1.
e. Verify that the mobile station tunes to CDMA Channel 3.
f. Make a Mobile-Originated voice call and verify audio in both directions.
g. End the call.
1.7.4.2 Base Station capable of TD but not Non-TD BCCH (Case 2)
a. Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1.
b. At the base station, Set Pilot PN offset to a certain value.
c. Verify that the mobile station acquires the Forward pilot channel correctly.
d. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.7.4-1.
e. Verify that the mobile station tunes to CDMA Channel 2.
f. Make a Mobile-Originated voice call and verify audio in both directions.
g. End the call.
1.7.4.3 Base Station capable of Non-TD BCCH and TD (Case 3)
a. Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1.
b. At the base station, Set Pilot PN offset to a certain value.
c. Verify that the mobile station acquires the Forward pilot channel correctly.
1-16
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
d. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.7.4-1.
e. Verify that the mobile station tunes to CDMA Channel 3.
f. Make a Mobile-Originated voice call and verify audio in both directions.
g. End the call.
1.7.5 Minimum Standard
1.7.5.1 Base Station capable of Non-TD BCCH but not TD (Case 1)
The mobile station shall comply with steps c, e, and f.
1.7.5.2 Base Station capable of TD but not Non-TD BCCH (Case 2)
The mobile station shall comply with steps c, e, and f.
1.7.5.3 Base Station capable of Non-TD BCCH and TD (Case 3)
The mobile station shall comply with steps c, e, and f.
1.8 Sync Channel Support for Mobile Stations capable of TD and QPCH or RC>2
1.8.1 Definition
This test verifies that the mobile station is able to respond correctly to the new fields of Sync Channel Message sent by the base station if any, tune to appropriate CDMA channel and acquire the system successfully.
1.8.2 Traceability (see [4])
2.6.1.3 Sync Channel Acquisition Substate
3.7.2.3.2.26 Sync Channel Message
1.8.3 Call Flow Example(s)
None
1.8.4 Method of Measurement
1.8.4.1 Base Station capable of Non-TD BCCH but not TD (Case 1)
Table 1.8.4-1 Frequency Allocation
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
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
a. Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1.
b. At the base station, Set Pilot PN offset to a certain value.
c. Verify that the mobile station acquires the Forward pilot channel correctly.
d. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.8.4-1.
e. Verify that the mobile station tunes to CDMA Channel 3.
f. Make a Mobile-Originated voice call and verify audio in both directions.
g. End the call.
1.8.4.2 Base Station capable of TD with the same TD mode as Mobile Station but not Non-TD BCCH (Case 2)
a. Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1.
b. At the base station, Set Pilot PN offset to a certain value.
c. Verify that the mobile station acquires the Forward pilot channel correctly.
d. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.8.4-1.
e. Verify that the mobile station tunes to CDMA Channel 4.
f. Make a Mobile-Originated voice call and verify audio in both directions.
g. End the call.
1.8.4.3 Base Station capable of TD with different TD mode as Mobile Station but not Non-TD BCCH (Case 3)
a. Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1.
b. At the base station, Set Pilot PN offset to a certain value.
c. Verify that the mobile station acquires the Forward pilot channel correctly.
d. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.8.4-1.
e. Verify that the mobile station tunes to CDMA Channel 2.
f. Make a Mobile-Originated voice call and verify audio in both directions.
1-18
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
g. End the call.
1.8.4.4 Base Station capable of Non-TD BCCH and TD with the same TD mode as Mobile Station (Case 4)
a. Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1.
b. At the base station, Set Pilot PN offset to a certain value.
c. Verify that the mobile station acquires the Forward pilot channel correctly.
d. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.8.4-1.
e. Verify that the mobile station tunes to CDMA Channel 4.
f. Make a Mobile-Originated voice call and verify audio in both directions.
g. End the call.
1.8.4.5 Base Station capable of Non-TD BCCH and TD with a different TD mode as Mobile Station (Case 5)
a. Connect the base station to the mobile station as shown in Figure A-4. Set PILOT_INC to 1.
b. At the base station, Set Pilot PN offset to a certain value.
c. Verify that the mobile station acquires the Forward pilot channel correctly.
d. Verify the mobile station receives a Sync Channel Message with frequency allocation according to Table 1.8.4-1.
e. Verify that the mobile station tunes to CDMA Channel 3.
f. Make a Mobile-Originated voice call and verify audio in both directions.
g. End the call.
1.8.5 Minimum Standard
1.8.5.1 Base Station capable of Non-TD BCCH but not TD (Case 1)
The mobile station shall comply with steps c, e, and f.
1.8.5.2 Base Station capable of TD with the same TD mode as Mobile Station but not Non-TD BCCH (Case 2)
The mobile station shall comply with steps c, e, and f.
1.8.5.3 Base Station capable of TD with different TD mode as Mobile Station but not Non-TD BCCH (Case 3)
The mobile station shall comply with steps c, e, and f.
1-19
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
1.8.5.4 Base Station capable of Non-TD BCCH and TD with the same TD mode as Mobile Station (Case 4)
The mobile station shall comply with steps c, e, and f.
1.8.5.5 Base Station capable of Non-TD BCCH and TD with a different TD mode as Mobile Station (Case 5)
The mobile station shall comply with steps c, e, and f.
1.9 Hashing F-CCCH, F-CCCH slot
1.9.1 Definition
This test checks the ability to set and detect hashed F-CCCHs and F-CCCH Slots. The IMSI’s effect on hashed F-CCCH and Slot is also checked.
1.9.2 Traceability: (See [4])
2.6.7.1 Hash Function
3.6.2.1.2 Common Channel Determination
3.6.2.1.3 Paging Slot Determination
1.9.3 Call Flow Example(s)
None
1.9.4 Methods of Measurement
1.9.4.1 F-CCCH Number Hashing
a. Connect the base station and mobile station as shown in Figure A-1.
b. Configure the base station system with multiple F-CCCHs (maximum seven) in MC-RR Parameters Message.
c. Make a mobile terminated call, and verify audio in both directions.
1.9.4.2 F-CCCH Slot Number Hashing
a. Connect the base station and mobile station as shown in Figure A-4.
b. Configure the base station system with slotted mode capability.
c. Make a mobile terminated call, and verify audio in both directions.
1.9.5 Minimum Standard
1.9.5.1 F-CCCH Number Hashing
The mobile station shall comply with step c.
1.9.5.2 F-CCCH Slot Number Hashing
The mobile station shall comply with step c.
1-20
C.S0044-0 v1.0
1.10 CDMA Channel Hashing on F-PCH for Mobile Stations not capable of QPCH or RC>2 1
2
3 4
5
6
7
8
9
10
11
12
13
14
15
16 17
18 19 20
21
22 23
24
25 26
27 28 29
30
31
32
33
1.10.1 Definition
This test checks the mobile station’s ability to do CDMA Channel hashing based on different capability sets to select appropriate CDMA Channel and associated PCH.
1.10.2 Traceability (see [4])
2.6.2.2 Response to Overhead Information Operation
2.6.2.2.12.1 Extended CDMA Channel List Message on Paging Channel
2.6.7.1 Hash Function
3.6.2.1.1 CDMA Channel Determination
3.7.2.3.2.28 Extended CDMA Channel List Message
1.10.3 Call Flow Example(s)
None
1.10.4 Methods of Measurement
1.10.4.1 Base Station incapable of BCCH and QPCH or RC>2 (Case 1)
a. Turn off all forms of autonomous registration at the base station.
b. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 Paging Channel on each of the 2 CDMA channels.
c. Verify that the base station sends either a CDMA Channel List Message or an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=’0’, TD_SEL_INCL=’0’ and NUM_FREQ=’0010’ from the base station.
d. Make a mobile terminated call, and verify audio in both directions.
1.10.4.2 Base Station incapable of BCCH, capable of QPCH or RC>2 with Extended CDMA Channel List Message sent (Case 2)
a. Turn off all forms of autonomous registration at the base station.
b. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 Paging Channel on each of the 2 CDMA channels.
c. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=’1’, TD_SEL_INCL=’0’ and NUM_FREQ=’0010’ from the base station and make sure RC_QPCH_HASH_IND is set to ‘1’ for freq 1 and 2.
d. Make a mobile terminated call, and verify audio in both directions.
1.10.5 Minimum Standard
1.10.5.1 Base Station incapable of BCCH and QPCH or RC>2 (Case 1)
The mobile station shall comply with step d.
1-21
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
33
1.10.5.2 Base Station incapable of BCCH, capable of QPCH or RC>2 with Extended CDMA Channel List Message sent (Case 2)
The mobile station shall comply with step d.
1.11 CDMA Channel Hashing on F-PCH for Mobile Stations capable of QPCH or RC>2
1.11.1 Definition
This test checks the mobile station’s ability to do CDMA Channel hashing based on different capability sets to select appropriate CDMA Channel and associated PCH.
1.11.2 Traceability (see [4])
2.6.2.2 Response to Overhead Information Operation
2.6.2.2.12.1 Extended CDMA Channel List Message on Paging Channel
2.6.7.1 Hash Function
3.6.2.1.1 CDMA Channel Determination
3.7.2.3.2.28 Extended CDMA Channel List Message
1.11.3 Call Flow Example(s)
None
1.11.4 Method of Measurement
1.11.4.1 Base Station incapable of BCCH and QPCH or RC>2 with Extended CDMA Channel List Message sent (Case 1)
a. Turn off all forms of autonomous registration at the base station.
b. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 Paging Channel on each of the 2 CDMA channels.
c. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=’0’, TD_SEL_INCL=’0’ and NUM_FREQ=’0010’ from the base station.
d. Make a mobile terminated call, and verify audio in both directions.
1.11.4.2 Base Station incapable of BCCH, capable of QPCH or RC>2 with Extended CDMA Channel List Message sent (Case 2)
a. Turn off all forms of autonomous registration at the base station.
b. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 Paging Channel on each of the 2 CDMA channels.
c. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=’1’, TD_SEL_INCL=’0’ and NUM_FREQ=’0010’ from the base station and make sure RC_QPCH_HASH_IND is set to ‘1’ for freq 1 and 2.
d. Make a mobile terminated call, and verify audio in both directions.
1-22
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
1.11.5 Minimum Standard
1.11.5.1 Base Station incapable of BCCH and QPCH or RC>2 with Extended CDMA Channel List Message sent (Case 1)
The mobile station shall comply with step d.
1.11.5.2 Base Station incapable of BCCH, capable of QPCH or RC>2 with Extended CDMA Channel List Message sent (Case 2)
The mobile station shall comply with step d.
1.12 CDMA Channel Hashing on F-BCCH; Mobile Station not capable of either TD or QPCH (RC>2)
1.12.1 Definition
This test checks the mobile station’s ability to do CDMA Channel (frequency) hashing based on different capability sets to select appropriate CDMA Channels and associated primary BCCHs.
1.12.2 Traceability (see 4)
2.6.2.1.5 Primary Broadcast Control Channel Monitoring
2.6.2.2 Response to Overhead Information Operation
2.6.2.2.12.2 Extended CDMA Channel List Message On Primary Broadcast Control Channel
2.6.7.1 Hash Function
3.6.2.1.1 CDMA Channel Determination
3.7.2.3.2.28 Extended CDMA Channel List Message
1.12.3 Call Flow Example(s)
None
1.12.4 Method of Measurement
1.12.4.1 Base station operates without TD and QPCH, RC>2 (Case 1)
a. Turn off all forms of autonomous registration at the base station.
b. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 primary BCCH on each of the 2 CDMA channels.
c. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=’0’, TD_SEL_INCL=’0’ and NUM_FREQ=’0010’ from the base station.
d. Make a mobile terminated call, and verify audio in both directions.
1.12.4.2 Base Station operates without TD (STS) but with QPCH (RC>2), (Case 2)
a. Turn off all forms of autonomous registration at the base station.
1-23
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
33
b. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 primary BCCH on each of the 2 CDMA channels.
c. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=’1’, TD_SEL_INCL=’0’ and NUM_FREQ=’0010’ from the base station and make sure RC_QPCH_HASH_IND is set to ‘1’ for freq 1 and 2
d. Make a mobile terminated call, and verify audio in both directions.
1.12.4.3 Base Station operates with TD (STS) and QPCH (RC>2) (Case 3)
a. Turn off all forms of autonomous registration at the base station.
b. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 primary BCCH on each of the 2 CDMA channels.
c. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=’1’, TD_SEL_INCL=’1’ and NUM_FREQ=’0010’ from the base station and make sure TD_HASH_IND is set to ‘1’ for frequency 1 and RC_QPCH_HASH_IND is set to ‘1’ for frequency 1 and 2.
d. Make a mobile terminated call, and verify audio in both directions.
1.12.5 Minimum Standard
1.12.5.1 Base station operates without TD and QPCH, RC>2 (Case 1)
The mobile station shall comply with step d.
1.12.5.2 Base Station operates without TD (STS) but with QPCH (RC>2), (Case 2)
The mobile station shall comply with step d.
1.12.5.3 Base Station operates with TD (STS) and QPCH (RC>2) (Case 3)
The mobile station shall comply with step d.
1.13 CDMA Channel Hashing on F-BCCH; Mobile Station not capable of TD (STS) but capable of QPCH (RC>2)
1.13.1 Definition
This test checks the mobile station’s ability to do CDMA Channel (frequency) hashing based on different capability sets to select appropriate CDMA Channels and associated primary BCCHs.
1.13.2 Traceability (see 4)
2.6.2.1.5 Primary Broadcast Control Channel Monitoring
2.6.2.2 Response to Overhead Information Operation
2.6.2.2.12.2 Extended CDMA Channel List Message On Primary Broadcast Control Channel
2.6.7.1 Hash Function
CDMA Channel Determination
1-24
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
33
3.7.2.3.2.28 Extended CDMA Channel List Message
1.13.3 Call Flow Example(s)
None
1.13.4 Method of Measurement
1.13.4.1 Base Station operates without TD (STS) and QPCH (RC>2) (Case 1)
a. Turn off all forms of autonomous registration at the base station.
b. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 primary BCCH on each of the 2 CDMA channels.
c. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=’0’, TD_SEL_INCL=’0’ and NUM_FREQ=’0010’ from the base station.
d. Make a mobile terminated call, and verify audio in both directions.
1.13.4.2 Base Station operates without TD (STS) but with QPCH (RC>2) (Case 2)
a. Turn off all forms of autonomous registration at the base station.
b. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 primary BCCH on each of the 2 CDMA channels.
c. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=’1’, TD_SEL_INCL=’0’ and NUM_FREQ=’0010’ from the base station and make sure RC_QPCH_HASH_IND is set to ‘1’ for freq 1 and 2.
d. Make a mobile terminated call, and verify audio in both directions.
1.13.4.3 Base Station operates with TD (STS) and QPCH (RC>2) (Case 3)
a. Turn off all forms of autonomous registration at the base station.
b. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 primary BCCH on each of the 2 CDMA channels.
c. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=’1’, TD_SEL_INCL=’1’ and NUM_FREQ=’0010’ from the base station and make sure TD_HASH_IND is set to ‘1’ for frequency 1 and RC_QPCH_HASH_IND is set to ‘1’ for frequencies 1 and 2.
d. Make a mobile terminated call, and verify audio in both directions.
1.13.5 Minimum Standard
1.13.6 Base Station operates without TD (STS) and QPCH (RC>2) (Case 1)
The mobile station shall comply with step d.
1.13.7 Base Station operates without TD (STS) but with QPCH (RC>2) (Case 2)
The mobile station shall comply with step d.
1-25
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
1.13.8 Base Station operates with TD (STS) and QPCH (RC>2) (Case 3)
The mobile station shall comply with step d.
1.14 CDMA Channel Hashing on F-BCCH; Mobile Station capable of both TD (STS) and QPCH (RC>2)
1.14.1 Definition
This test checks the mobile station’s ability to do CDMA Channel (frequency) hashing based on different capability sets to select appropriate CDMA Channels and associated primary BCCHs.
1.14.2 Traceability (see 4)
2.6.2.1.5 Primary Broadcast Control Channel Monitoring
2.6.2.2 Response to Overhead Information Operation
2.6.2.2.12.2 Extended CDMA Channel List Message On Primary Broadcast Control Channel
2.6.7.1 Hash Function
3.6.2.1.1 CDMA Channel Determination
3.7.2.3.2.28 Extended CDMA Channel List Message
1.14.3 Call Flow Example(s)
None
1.14.4 Method of Measurement
None
1.14.4.1 Base Station operates without TD (STS) and QPCH (RC>2) (Case 1)
a. Turn off all forms of autonomous registration at the base station.
b. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 primary BCCH on each of the 2 CDMA channels.
c. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=’0’, TD_SEL_INCL=’0’ and NUM_FREQ=’0010’ from the base station.
d. Make a mobile terminated call, and verify audio in both directions.
1.14.4.2 Base Station operates without TD (STS) but with QPCH (RC>2) (Case 2)
a. Turn off all forms of autonomous registration at the base station.
b. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 primary BCCH on each of the 2 CDMA channels.
c. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=’1’, TD_SEL_INCL=’0’ and NUM_FREQ=’0010’ from the base station and make sure RC_QPCH_HASH_IND is set to ‘1’ for frequency 1 and 2.
1-26
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
d. Make a mobile terminated call, and verify audio in both directions.
1.14.4.3 Base Station operates with TD (STS) and QPCH (RC>2) (Case 3)
a. Turn off all forms of autonomous registration at the base station.
b. Connect the base station and mobile station as shown in Figure A-4, and configure the base station with 1 primary BCCH on each of the 2 CDMA channels.
c. Send an Extended CDMA Channel List Message with RC_QPCH_SEL_INCL=’1’, TD_SEL_INCL=’1’ and NUM_FREQ=’0010’ from the base station and make sure TD_HASH_IND is set to ‘1’ for frequency 1 and 2, RC_QPCH_HASH_IND is set to ‘1’ for all the frequencies.
d. Make a mobile terminated call, and verify audio in both directions.
1.14.5 Minimum Standard
1.14.5.1 Base Station operates without TD (STS) and QPCH (RC>2) (Case 1)
The mobile station shall comply with step d.
1.14.5.2 Base Station operates without TD (STS) but with QPCH (RC>2) (Case 2)
The mobile station shall comply with step d.
1.14.5.3 Base Station operates with TD (STS) and QPCH (RC>2) (Case 3)
The mobile station shall comply with step d.
1.15 F-CCCH SUPPORT
1.15.1 Definition
This test checks the mobile station’s ability to process messages (L2 ACK, Extended Channel Assignment Message) sent over F-CCCH correctly.
1.15.2 Traceability (see [4])
2.6.2.1.1 Forward Channel Monitoring Procedures
2.6.2.1.1.4 Common Channel Supervision
2.6.3.1.8 Paging Channel and Forward Common Control Channel Monitoring
1.15.3 Call Flow Example(s)
None
1.15.4 Method of Measurement
a. Connect the base station and mobile station as shown in Figure A-3.
b. Instruct the mobile station originate a voice call.
1-27
C.S0044-0 v1.0
c. Verify the base station respond with a Layer 2 ACK and Extended Channel Assignment Message over F-CCCH.
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
d. Verify the mobile station can set up the traffic channel for this voice call correctly.
1.15.5 Minimum Standard
The mobile station shall comply with step d.
1.16 Paging Indicator on the Quick Paging Channel
1.16.1 Definition
For mobile stations that support the Quick Paging Channel, this test will verify the following:
The mobile station shall hash to the correct paging indicator positions. The mobile station shall monitor its assigned Paging Channel or F-CCCH slot immediately following its assigned Quick Paging Channel slot if the mobile station does not detect that at least one of the paging indicators is set to “OFF”. Therefore, if the mobile station detects zero, one or two “ON” in the hashed paging indicators without detecting an “OFF”, the mobile station will monitor its assigned Paging Channel or F-CCCH slot5. It is assumed that if the mobile station hashes to the wrong paging indicator positions and detected an “OFF”, the mobile station would likely miss the assigned Paging Channel or the F-CCCH slot.
1.16.2 Traceability: (See [4])
2.6.2.1.2 Quick Paging Channel Monitoring Procedures.
2.6.7.1 Hash Function
2.7.1.3.2.1 Registration Message
3.6.2.5 Quick Paging Channel Processing
3.7.2.3.2.13 Extended System Parameters Message
3.7.2.3.2.31 MC-RR-Parameters Message
1.16.3 Call Flow Example(s)
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
Registration Request order
BS
CommonChannels
MS
CommonChannels
Turn on/off PI on Quick Paging Channelfor the MS assigned QPCH Slot
The MS hash to QPIpositions and detect itsQPI on in the Assigned
QPCH Slot. Then the MSstart receiving on itsassigned F-PCH or
F-CCCH slots
Registration Message
1 2
3
4
5 6
7
1.16.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-3.
b. Set the values in the Extended System Parameters Message or MC-Parameters Message as follows:
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
9 10 11
12 13 14 15
16
17
18
19
c. Allow the mobile station to begin monitoring the QPCH.
d. Instruct the base station to send a mobile station directed message (i. e. General Page Message or Registration Request Order) in the mobile station’s assigned Paging Channel or F-CCCH slot.
e. Verify that the base station sets the paging indicator positions associated with the mobile station to “ON” in the Quick Paging Channel slot corresponding to the Paging Channel or F-CCCH slot in which the mobile station directed message is sent in step d. Ensure the base station sets the other paging indicator positions to “OFF”.
f. Verify the mobile station correctly responds to the message directed to it in step d.
g. Repeat steps b through f with the QPCH_RATE set to ‘1’ (9600 bps).
1.16.5 Minimum Standard
The mobile station shall comply with step f. The base station shall comply with step e.
1-29
C.S0044-0 v1.0
2 BASIC CALL PROCESSING TESTS 1
2
3
4 5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
2.1 Mobile Originated Voice Calls
2.1.1 Definition
This tests voice service negotiation and call completion of mobile originated voice calls, for radio configurations and voice service options supported by the mobile and base station.
2.1.2 Traceability (see [4])
2.2.6.2.5 Mobile Station Origination Operation
2.6.3.5 Mobile Station Origination Attempt Substate
2.6.4 Mobile Station Control on the Traffic Channel State
2.7.1.3.2.4 Origination Message
2.7.2.3.2.15 Service Option Control Message
3.6.3.5 Response to Origination Message
3.6.4 Traffic Channel Processing
3.7.2.3.2.21 Extended Channel Assignment Message
3.7.3.3.2.3 Alert With Information Message
3.7.3.3.2.20 Service Connect Message
2.7.2.3.2.12 Service Request Message
2.7.2.3.2.13 Service Response Message
2.7.2.3.2.14 Service Connect Completion Message
2.7.4.18 Service Configuration Record
2-1
C.S0044-0 v1.0
1 2.1.3 Call Flow Example(s)
Service Connect MessageService Configuration Record (SO, RCs)
Extended Channel Assignment Message(DEFAULT_CONFIG, GRANTED_MODE, RCs)
possible service negotiation
Order Message (acknowledgement from base station)
Origination Message (SO, RCs proposed)
release order messages
Voice Traffic
Service Connect Completion Message
MS BS
commonchannels
dedicatedchannels
commonchannels
initial serviceconfiguration
possible newservice
configuration
2
3
4
5
6 7
8
2.1.4 Method of Measurement
a. Configure the base station for desired voice service negotiation listed in Table 2.1.4-2.
b. Allow the mobile to come to the idle state on the base station.
c. Make a mobile originated voice call, and record the call setup messages listed in Table 2.1.4-1.
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
1
2 3
4 5 6
7 8
9 10 11
12
13 14 15
16
d. Verify SERVICE_OPTION, FOR_RC_PREF, and REV_RC_PREF proposed in the Origination Message correspond to the mobile configuration settings.
e. Verify DEFAULT_CONFIG, GRANTED_MODE, FOR_RC, and REV_ RC in the Extended Channel Assignment Message corresponds to the base station configuration for service negotiation.
f. Verify service negotiation used in Service Request Message, Service Response Message, and Service Connect Message proceed as desired.
g. Verify the SERVICE_OPTION, FOR_FCH_RC, and REV_FCH_RC in the last Service Configuration Record corresponds to the desired outcome of the base station service negotiation configuration, and the call completes successfully.
h. End the call.
i. Repeat steps a through h for all supported configurations of mobile originated voice service negotiation as supported by the mobile station and base station. This may include call completion with the service configurations in Table 2.1.4-2.
Table 2.1.4-2 Service Configurations for Mobile Originated Voice Calls
Voice Service Option Forward Radio Configuration
Reverse Radio Configuration
3 1 1
17 or 32768 2 2
3 3 3
3 4 3
17 or 32768 5 4
17
18
19
20
21
22 23 24
2.1.5 Minimum Standard
The mobile station and the base station shall comply with step d, e, f, g, and i.
2.2 Mobile Station Terminated Voice Calls
2.2.1 Definition
This tests voice service negotiation and call completion of mobile station terminated voice calls, for radio configurations and voice service options supported by the mobile station and base station.
2-3
C.S0044-0 v1.0
1
2
3
4
5
6
7
8
9
10
11
12
13
2.2.2 Traceability
2.7.1.3.2.5 Page Response Message
2.6.4 Mobile Station Control on the Traffic Channel State
2.7.2.3.2.15 Service Option Control Message
3.6.4 Traffic Channel Processing
3.7.2.3.2.21 Extended Channel Assignment Message
3.7.3.3.2.20 Service Connect Message
3.7.3.3.2.20 Service Connect Message
2.7.2.3.2.12 Service Request Message
2.7.2.3.2.13 Service Response Message
2.7.2.3.2.14 Service Connect Completion Message
2.7.4.18 Service Configuration Record
2.2.3 Call Flow Example(s)
Service Connect MessageService Configuration Record (SO, RCs)
Extended Channel Assignment Message(DEFAULT_CONFIG, GRANTED_MODE, RCs)
possible service negotiation
Page Response Message (SO, RCs proposed)
General Page Message (SO proposed)
Release Order Messages
Voice Traffic
Service Connect Completion Message
MS BS
commonchannels
dedicatedchannels
commonchannels
initial serviceconfiguration
possible newservice
configuration
14
15
16 17 18
2.2.4 Method of Measurement
a. Configure the base station for desired SERVICE_OPTION for the General Page Message or Universal Page Message, and desired service negotiation listed in Table 2.2.4-2.
2-4
C.S0044-0 v1.0
1
2 3
4
b. Allow the mobile station to come to the idle state on the base station.
c. Make a mobile station terminated voice call, and record the call setup messages listed in Table 2.2.4-1.
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
3 Extended Channel Assignment 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 7
8 9
10
11 12
13 14
15 16 17
18
19 20 21
d. Verify the SERVICE_OPTION proposed in the General Page Message corresponds to the base station configuration setting.
e. Verify SERVICE_OPTION, FOR_RC_PREF, and REV_RC_PREF proposed in the Origination/Page Response Message correspond to the mobile station configuration settings.
f. Verify DEFAULT_CONFIG, GRANTED_MODE, FOR_RC, and REV_RC in the Extended Channel Assignment Message correspond to the base station configuration.
g. Verify that service negotiation using in Service Request Message, Service Response Message, and Service Connect Message proceed as desired.
h. Verify the SERVICE_OPTION, FOR_FCH_RC, and REV_FCH_RC in the last Service Configuration Record corresponds to the desired outcome of the base station service negotiation configuration, and the call completes successfully.
i. End the call.
j. Repeat steps a through i for all supported configurations of mobile station terminated voice service negotiation as supported by the mobile station and base station. This may include call completion with the service configurations in Table 2.2.4-2.
2-5
C.S0044-0 v1.0
Table 2.2.4-2 Minimum Service Combinations for Mobile station Terminated Voice Calls 1
Service Option Forward Radio Configuration
Reverse Radio Configuration
3 1 1
17 or 32768 2 2
3 3 3
3 4 3
17 or 32768 5 4
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17 18
19
20
21
22
2.2.5 Minimum Standard
The mobile station and the base station shall comply with steps d, e, f, g, h, and j.
2.3 Busy Tone
2.3.1 Definition
This tests the mobile station response to a called-party-busy notification from a base station.
2.3.2 Traceability (see [4])
2.6.4.4 Release Substate
3.6.4.3 Traffic Channel Substate
3.7.5 Information Records
Table 3.7.5.5-3 Tone Signals
2.3.3 Call Flow Example(s)
None
2.3.4 Method of Measurement
a. Allow the mobile station to come to the idle state on the base station.
b. Ensure the called party has no call-waiting or automatic voice mail enabled, and tie up the line so that the mobile station will get a busy signal when it calls.
c. Attempt a mobile station originated call to the party.
d. Verify the mobile station plays a called-party-busy indication.
2.3.5 Minimum Standard
The mobile station shall comply with the requirement in steps d.
2-6
C.S0044-0 v1.0
2.4 Mobile Station Origination Call with Inter Band Channel Assignment 1
2
3 4 5 6
7
8
9
10
11
12
13
14
15
16 17
18
19
20
21 22 23 24 25
26 27
28
29
30 31 32 33
34
35
2.4.1 Definition
This test verifies that the mobile station can initiate a call to a land party on aone band class and then re-originate and completes the call the target band class after receiving a Channel Assignment Message or Extended Channel Assignment Message with ASSIGN_MODE = ‘101’ or ‘001’ respectively.
2.4.2 Traceability: (See [4])
2.6.2.4 Mobile Station Order and Message Processing Operation
2.6.3.5 Mobile Station Origination Attempt Substate
2.7.1.3.2.4 Origination Message
3.7.2.3.2.8 Channel Assignment Message
3.7.2.3.2.21 Extended Channel Assignment Message
2.4.3 Call Flow Example(s)
None
2.4.4 Method of Measurement
a. Connect the mobile station and base stations as shown in Figure A-2. Base station 1 operates in a band class that is different from base station 2.
b. Ensure the mobile station acquires base station 1.
c. Configure Base station 1 so that Inter Band Channel Assignment is enabled.
d. Setup mobile station originated voice call.
e. Verify the mobile station originates on the serving base station and receives a Channel Assignment Message with ASSIGN MODE=‘101’ or an Extended Channel Assignment Message with ASSIGN MODE=’001’. Verify that the Channel Assignment Message or Extended Channel Assignment Message contains assignment for paging channel on base station 2, and RESPOND=1.
f. Verify the mobile station re-sends a second Origination Message to base station 2 and the call completes successfully.
g. Verify user data in both directions.
h. End the call.
i. Repeat Steps d through g, but provision Base station 2 to be Inter Band Channel Assignment enabled. The mobile station will originate on base station 2 and then re-originate on base station 1 after receiving the Channel Assignment Message or Extended Channel Assignment Message.
2.4.5 Minimum Standard
The mobile station and base station shall comply with steps e, f, g, and i.
2-7
C.S0044-0 v1.0
2.5 Mobile Station Terminated Call with Inter Band Channel Assignment 1
2
3 4 5 6
7
8
9
10
11
12
13
14
15
16 17
18
19
20
21 22 23 24 25
26 27
28
29
30 31 32 33 34
2.5.1 Definition
This test verifies that the mobile station can receive a call from a land party on one band class and then resends the Page Response Message autonomously and completes the call on the target band class after receiving a Channel Assignment Message or Extended Channel Assignment Message with ASSIGN_MODE = ‘101’ or ‘001’ respectively.
2.5.2 Traceability (See [4])
2.6.2.3 Mobile Station Page Match Operation
2.6.3.3 Page Response Substate
2.7.1.3.2.5 Page Response Message
3.7.2.3.2.8 Channel Assignment Message
3.7.2.3.2.21 Extended Channel Assignment Message
2.5.3 Call Flow Example(s)
None
2.5.4 Method of Measurement
a. Connect the mobile station and base stations as shown in Figure A-2. Base station 1 operates in a band class that is different from base station 2.
b. Ensure the mobile station acquires base station 1.
c. Configure base station 1 so that Inter Band Channel Assignment is enabled.
d. Setup mobile station terminated voice call.
e. Verify that the mobile station receives a Channel Assignment Message with ASSIGN MODE=‘101’ or an Extended Channel Assignment Message with ASSIGN MODE=’001’. Verify that the Channel Assignment Message or Extended Channel Assignment Message contains assignment for paging channel on base station 2, and RESPOND = ‘1’.
f. Verify the mobile station sends a second Page Response Message on the target base station and the call completes.
g. Verify user data in both directions.
h. End the call.
i. Repeat Steps d through g, but provision Base station 2 to be Inter Band Channel Assignment enabled. The mobile station will send the Page Response Message on base station 2 and then re-send the Page Response Message on base station 1 after receiving the Channel Assignment Message or Extended Channel Assignment Message.
2-8
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.5.5 Minimum Standard
The mobile station and the base station shall comply with steps e, f, g, and i.
2.6 DTMF
2.6.1 Definition
This is a test for Dual-Tone Multi-frequency (DTMF), sent by the mobile station in a Send Burst DTMF Message or a Continuous DTMF Tone Order. It verifies that sequencing and tone duration of the Send Burst DTMF Message and the Continuous DTMF Tone Order are preserved.
2.6.2 Traceability (see [4])
2.7.2.3.2.7 Send Burst DTMF Message
2.7.2.3.2.1 Continuous DTMF Tone Order
3.7.3.3.2.9 Send Burst DTMF Message
Table 2.7.1.3.2.4-4 Representation of DTMF Digits
Table 2.7.2.3.2.7-1 Recommended DTMF Pulse Width
Table 2.7.2.3.2.7-2 Recommended Minimum Inter-digit Interval
Table 3.7.4-1 Order and Order Qual Codes Used on the f-csch and the f-dsch
Table 2.7.2.3-1 Messages on r-dsch
2.6.3 Call Flow Example(s)
None
2.6.4 Method of Measurement
a. Equip a landline with a DTMF decoder that can verify DTMF digits received and DTMF tone duration.
b. Configure the mobile station to send short DTMF tones.
c. Allow the mobile station to come to the idle state on the base station, and set up a voice call to the equipped land party.
d. Press the keys 1234567890*#.
e. Verify the mobile station sends a Send Burst DTMF Message for each key press.
f. Verify DTMF tones are received correctly.
g. End the call.
h. Configure the mobile station to use long DTMF tones.
i. Setup a mobile station originated call.
j. Direct the mobile station to perform the following steps in .
1. Press and hold any number key on the keypad for approximately 5 seconds.
2-9
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 33
2. Verify the mobile station sends a Continuous DTMF Tone Order with the appropriate ORDQ value to start and stop the DTMF tone.
3. Direct the mobile station to send characters 0123456789 * as one or more Send Burst DTMF Message(s).
4. Press and hold any number key on the keypad for approximately 5 seconds.
5. Again press and hold any number key on the keypad for approximately 5 seconds.
k. Verify all DTMF digits are decoded correctly and in the right order at the land party DTMF decoder.
l. Verify the three 5-second key presses produce DTMF tones approximately 5 seconds in duration.
2.6.5 Minimum Standard
The mobile station shall comply with requirements in steps e, f, k and l.
2.7 Slot Cycle Index
2.7.1 Definition
If the mobile station supports slotted operation, this test verifies the mobile station response to the base station MAX_SLOT_CYCLE_INDEX setting for various settings of mobile station SLOT_CYCLE_INDEX.
2.7.2 Traceability (see [4])
2.6.2.1.1 Forward Channel Monitoring Procedures
3.6.2.1.3 Paging Slot Determination
3.6.2.3 Mobile Station Directed Messages
2.7.1.3.2.1 Registration Message
2.7.1.3.2.4 Origination Message
2.7.1.3.2.5 Page Response Message
2.7.4.7 Terminal Information
2.7.3 Call Flow Example(s)
None
2.7.4 Method of Measurement
a. Configure the mobile station internal setting of SLOT_CYCLE_INDEXP and also base station System Parameter Message or MC-RR Parameters Message setting of MAX_SLOT_CYCLE_INDEX in the first row in Table 2.7.4-1.
2-10
C.S0044-0 v1.0
Table 2.7.4-1 Mobile station and Base Station Settings for Slot Cycle Index Test 1
MAX_SLOT_CYCLE_INDEX (base
station)
Test_ID SLOT_CYCLE _INDEX (mobile station)
P
Slot Cycle Index Used
Slot Cycle Length, 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 10.14 3
2
3 4
5 6
7
8 9
10
11
12
13
14 15
16
17
18
b. Allow the mobile station to come to the idle state in slotted mode on the base station.
c. Examine that the mobile station wakes up in the assigned slots to read the Paging Channelat the interval of the Slot Cycle Length in Table 2.7.4-1.
d. Make a mobile station terminated call, verify the base station pages the mobile station in the appropriate slot.
e. Verify the call completes successfully.
f. Repeat steps a through d for each of the other row Test ID combinations in Table 2.7.4-1.
2.7.5 Minimum Standard
The mobile station and the base station shall comply with requirements in steps c, d, e and f.
2.8 Reverse Radio Link Failure
2.8.1 Definition
2.8.2 This tests mobile station’s response to a 15 second loss of the reverse RF link in the conversation state. Traceability
3.7 Supervision [see (6)]
Table 2.2.1.1.3-1 Accumulated ARQ Statistics for Regular PDUs (see [3])
2.2.1.1.2.2 Requirements for Transmission and Retransmission Procedures (see [3])
2-11
C.S0044-0 v1.0
1 2.8.3 Call Flow Example(s)
Service Connect Message
Extended Channel Assignment Message
possible service negotiation
Order Message (acknowledgement from base station)
Origination Message
Voice Traffic
Service Connect Complete Message
MS BS
commonchannels
dedicatedchannels
initial serviceconfiguration
possible newservice
configuration
2
3
4 5 6
2.8.4 Method of Measurement
a. Configure a test setup with a connection of a single base station and the mobile station to allow the reverse radio link to be abruptly attenuated or interfered-with, enough to cause continuous loss of all reverse frames as exemplified in Figure 2-1
base station 1
AWGN
MobileDiagnostic and Control Tool
CDMA Analyzer
Fixed Atten Vari Atten
Reverse Link
Forward Link
DuplexerDuplexer
7
8
9
10
11
12
Figure 2-1 Test Setup for Radio Link Failure
b. Configure the setup for good RF links as specified in ANNEX B.
c. Allow the mobile station to come to the idle state on the base station.
d. Attempt a mobile station originated call.
e. Abruptly cause loss of the reverse RF link after voice call is established.
2-12
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
f. Restore the normal RF link after a minimum of 15 seconds.
g. Verify the call is released.
h. Verify the mobile station returns to the idle state on the base station.
2.8.5 Minimum Standard
The mobile station shall comply with the requirements in steps g and h.
2.9 Channel Assignment from CDMA to Analog
2.9.1 Definition
This test will verify that a base station assigns a mobile station to analog (e.g. AMPS) when no CDMA traffic channels are available.
2.9.2 Traceability (see [4])
2.6.1.1.2 System Selection Using Current Redirection Criteria
2.6.3.5 Mobile Station Origination Attempt Substate
2.9.3 Call Flow Example(s)
None
2.9.4 Method of Measurement
a. Connect the base station and mobile station as shown in Annex A Figure A - 5.
b. Take all CDMA traffic channel radio resources out of service or configure the base station to behave in a similar fashion. Configure the base station to assign analog channel.
c. Setup a mobile station originated call.
d. Verify that the base station sends a Channel Assignment Message or Extended Channel Assignment Message with ASSIGN_MODE=‘011’ to assign the mobile station an analog voice channel or with ASSIGN_MODE=‘010’ to acquire the analog system.
e. Verify the mobile station acquires the analog system.
f. Verify user data in both directions.
g. End call.
2.9.5 Minimum Standard
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
2.10 Network Busy 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.10.1 Definition
This tests mobile station response to a base station blocking condition during mobile station call origination.
2.10.2 Traceability (see [4])
Table 3.7.4-1 Order and Order Qualification Codes
3.6.2.3 Mobile Station Directed Messages, Reorder Order
Table 3.7.5.5-3 Tone Signals
3.6.3.5 Response to Origination Message
3.6.2.3 Mobile Station Directed Messages
2.10.3 Call Flow Example(s)
None
2.10.4 Method of Measurement
a. Allow the mobile station to come to the idle state on the base station.
b. Take all traffic channel resources out of service or configure the base station to behave in a similar fashion. Configure the base station to send a network-busy indication.
c. Attempt a mobile station originated call.
d. Instruct the base station to send a Reorder Order to the mobile station.
e. Verify the mobile station indicates a call failure due to network-busy, (e.g. For voice service options, the mobile station will play a reorder tone ). Note any anomalies in the mobile station behavior due to receiving the Reorder Order..
f. Steps a through e may be repeated for different service options supported such as service option 33.
2.10.5 Minimum Standard
The mobile station shall comply with the requirements in step e for all tested service options.
2.11 Release Order on the Access Channel
2.11.1 Definition
This test verifies the mobile station can send a Release Order on the Access Channel during call origination before switching to dedicated channel transmission.
2.11.2 Traceability (see [4] unless otherwise noted)
3.6.3 Access Channel Processing
3.6.3.4 Response to Orders
2-14
C.S0044-0 v1.0
1
2
3
4
5
2.6.3 System Access State
2.6.3.1.4 System Access State Exit Procedures
2.6.3.5 Mobile Station Origination Attempt Substate
2.1.1.2.2.1 Overview of Transmission and Retransmission Procedures (see [3])
2.11.3 Call Flow Example(s)
BSMSOrigination Message
CommonChannelsRelease Order
Order
Ack Order
6
7
8
9
10 11 12
13 14 15
16
17
18 19
20
21 22 23 24
25
26
27
28
2.11.4 Method of Measurement
a. Allow the mobile station to come to the idle state on the base station.
b. Attempt a mobile station originated call.
c. Shortly after the mobile station has received acknowledgement of its Origination Message, terminate the call attempt from the mobile station side, e. g. press the mobile station END key, before the mobile station switches to dedicated channel transmission.
d. Verify the mobile station sends a Release Order (normal release) on the Access Channel in assured mode requiring confirmation of delivery, aborts the call attempt, and returns to the idle state on the base station.
2.11.5 Minimum Standard
The mobile station shall comply with the requirements in step d.
2.12 True IMSI Support, Land Party to Mobile Station Call, Matching MCC and IMSI_11_12, True IMSI addressing supported by the base station and mobile station
2.12.1 Definition
This test verifies that the base station pages the mobile station with True IMSI addressing supported by the base station and mobile station when the MCC and IMSI_11_12 of the mobile station match those sent by the base station in the Extended System Parameters Message or ANSI-41 System Parameters Message.
2.12.2 Traceability (See [4])
2.3.1.1 Encoding of IMSI_M_S and IMSI_T_S
2.3.1 Mobile Station Identification Number
2.3.1.3 Encoding of the MCC_M and MCC_T
2-15
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
33
2.6.2.2.5 Extended System Parameters Message
2.7.4.24 IMSI_T
3.7.2.3.2.13 Service Response Message
2.12.3 Call Flow Example(s)
None
2.12.4 Method of Measurement
a. Allow the mobile station to come to the idle state on the base station.
b. Ensure the mobile station is programmed with the same values of MCC and IMSI_11_12 used in the base station. Do not use MCC (wild card) value in the base station.
c. Configure the base station to send the Extended System Parameters Message or ANSI-41 System Parameters Message with the value IMSI_T_SUPPORTED=1.
d. Enable power-up registration.
e. Enable authentication. Configure the base station to disallow mobile station terminated calls if authentication fails.
f. Power on the mobile station and wait for power-up registration to occur.
g. Initiate a land party to mobile station call.
h. Verify user data in both directions and end call at the mobile station.
2.12.5 Minimum Standard
The mobile station shall comply with step h.
2.13 True IMSI Support, Land Party to Mobile Station Call, Matching MCC and IMSI_11_12, True IMSI addressing supported by the base station with MIN-based addressing supported by the mobile station.
2.13.1 Definition
This test verifies that the base station pages the mobile station with True IMSI addressing supported by the base station and MIN-based addressing supported by the mobile station when the MCC and IMSI_11_12 of the mobile station match those sent by the base station in the Extended System Parameter Message or ANSI-41 System Parameters Message.
2.13.2 Traceability (see [4])
2.3.1.1 Encoding of IMSI_M_S and IMSI_T_S
2.3.1 Mobile Station Identification Number
2.3.1.3 Encoding of the MCC_M and MCC_T
2.6.2.2.5 Extended System Parameters Message
2-16
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
33
2.7.4.24 IMSI_T
3.7.2.3.2.13 Service Response Message
2.13.3 Call Flow Example(s)
None
2.13.4 Method of Measurement
a. Allow the mobile station to come to the idle state on the base station.
b. Ensure the mobile station is programmed with the same values of MCC and IMSI_11_12 used in the base station. Do not use MCC (wild card) value in the base station.
c. Configure the base station to send the Extended System Parameters Message or ANSI-41 System Parameters Message with the value IMSI_T_SUPPORTED=1.
d. Enable power on registration.
e. Enable authentication. Configure the base station to disallow mobile station terminated calls if authentication fails.
f. Power on the mobile station and wait for power-up registration to occur.
g. Initiate a land party call to the mobile station.
h. Verify user data and end call at the mobile station.
2.13.5 Minimum Standard
The mobile station shall comply with step h.
2.14 True IMSI Support, Land Party to Mobile Station Call, Matching MCC and IMSI_11_12, True IMSI addressing not supported by the base station
2.14.1 Definition
This test will verify the base station pages the mobile station when the base station does not support True IMSI addressing, when the MCC and IMSI_11_12 of the mobile station match those sent by the base station in the Extended System Parameters Message or ANSI-41 System Parameters Message.
2.14.2 Traceability (see [4])
2.3.1.1 Encoding of IMSI_M_S and IMSI_T_S
2.3.1 Mobile Station Identification Number
2.3.1.3 Encoding of the MCC_M and MCC_T
2.6.2.2.5 Extended System Parameters Message
2.7.4.24 IMSI_T
3.7.2.3.2.13 Service Response Message
2-17
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.14.3 Call Flow Example(s)
None
2.14.4 Method of Measurement
a. Allow the mobile station to come to the idle state on the base station.
b. Ensure the mobile station is programmed with the same values of MCC and IMSI_11_12 used in the base station. Do not use MCC (wild card) value in the base station.
c. Configure the base station to send the Extended System Parameters Message or ANSI-41 System Parameters Message with the value IMSI_T_SUPPORTED=0.
d. Enable power on registration.
e. Enable authentication. Configure the base station to disallow mobile station terminated calls if authentication fails.
f. Power on the mobile station and wait for power-up registration to occur.
g. Initiate a land party call to the mobile station.
h. Verify user data and end call at the mobile station.
2.14.5 Minimum Standard
The mobile station shall comply with step h.
2.15 True IMSI Support, Land Party to Mobile Station Call, Different MCC and IMSI_11_12
2.15.1 Definition
This test verifies the base station selects one of the valid forms of paging channel address when neither the MCC nor the IMSI_11_12 of the mobile station being addressed match those being sent by the base station in the Extended System Parameters Message or ANSI-41 System Parameters Message.
2.15.2 Traceability (see [4])
2.3.1.1 Encoding of IMSI_M_S and IMSI_T_S
2.3.1 Mobile Station Identification Number
2.3.1.3 Encoding of the MCC_M and MCC_T
2.6.2.2.5 Extended System Parameters Message
2.7.4.24 IMSI_T
3.7.2.3.2.13 Service Response Message
2.15.3 Call Flow Example(s)
None
2-18
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.15.4 Method of Measurement
a. Allow the mobile station to come to the idle state on the base station.
b. Ensure the mobile station is programmed with different values of MCC and IMSI_11_12 than those used in the base station. Do not use MCC (wild card) value in the base station.
c. Configure the base station to send the Extended System Parameters Message or ANSI-41 System Parameters Message with the value IMSI_T_SUPPORTED=1.
d. Enable power on registration.
e. Enable authentication. Configure the base station to disallow mobile station terminated calls if authentication fails.
f. Power on the mobile station and wait for power-up registration to occur.
g. Initiate a land party call to the mobile station.
h. Verify user data and end call at the mobile station.
2.15.5 Minimum Standard
The mobile station shall comply with step h.
2.16 PACA Origination, User Terminates While Still In Queue
2.16.1 Definition
This test verifies that a PACA-capable mobile station, upon failure to originate a call due to lack of available voice/traffic channels, shall re-attempt the origination using the PACA feature code. It verifies that a currently queued mobile station properly informs the base station when a user aborts waiting for traffic channel.
2.16.2 Traceability (see [4])
2.6.2 Mobile Station Idle State
2.6.2.8 Mobile Station PACA Cancel Operation
2.6.3.5 Mobile Station Origination Attempt Substate
2.7.1.3.2.4 Origination Message
2.7.1.3.2.9 PACA Cancel Message
3.7.2.3.2.20 PACA Message
2.16.3 Call Flow Example(s)
None
2.16.4 Method of Measurement
a. Allow the mobile station to come to the idle state on the base station.
2-19
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
33
b. At the base station, enable PACA feature for the mobile station, assign a PACA priority level to the mobile station, and disable Permanent Invocation PACA for the mobile station.
c. If the mobile station is capable of Slotted Mode, verify that the mobile station is operating in the Slotted Mode.
d. Ensure PACA is enabled on base station.
e. Configure the base station to make all traffic channels busy.
f. Setup a mobile station originated call.
g. Verify the following:
1. Mobile station originates call with PACA_REORIG bit='0' in Origination Message.
2. Base station replies with Reorder Order.
3. Mobile station retries the origination with the PACA_REORIG bit='1' in the Origination Message.
4. Base station sends PACA Message with PURPOSE='0000' and the mobile station’s Queue Position (Q_POS).
5. Mobile station acknowledges PACA Message.
h. The mobile station user interface should indicate the origination has been successfully queued.
i. Verify the mobile station remains in non-slotted mode.
j. End call to terminate queued origination. Verify that the mobile station sends a PACA Cancel Message to the base station.
k. Verify the mobile station enters slotted mode if applicable.
2.16.5 Minimum Standard
The mobile station shall comply with the requirements in steps c, g, i, j, and k.
2.17 PACA Origination, Idle Handoff While in Queue
2.17.1 Definition
This test verifies that a PACA-capable mobile station already in a PACA queue shall reoriginate the PACA request when the mobile station performs an idle handoff.
2.17.2 Traceability (see [4])
2.6.2 Mobile Station Idle State
2.6.2.8 Mobile Station PACA Cancel Operation
2.6.3.5 Mobile Station Origination Attempt Substate
2.7.1.3.2.4 Origination Message
2-20
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.7.1.3.2.9 PACA Cancel Message
3.7.2.3.2.20 PACA Message
2.17.3 Call Flow Example(s)
None
2.17.4 Method of Measurement
a. Allow the mobile station to come to the idle state on the base station.
b. At the base station, enable PACA feature for the mobile station, assign a PACA priority level to mobile station, and disable Permanent Invocation PACA for mobile station.
c. Ensure PACA is enabled on both base stations.
d. Configure both base stations to make all traffic channels busy.
e. Setup a mobile station originated call.
f. The mobile station user interface should indicate origination successfully queued.
g. Force an idle handoff from base station 1 to base station 2.
h. Verify the mobile station re-originates the PACA request with PACA_REORIG='1'.
i. Verify a PACA Message is received from base station 2 indicating the mobile station’s position in the PACA queue of base station 2.
j. On the mobile station, originate a new call while still queued.
k. The mobile station user interface should indicate to the user that the first PACA call has been cancelled.
2.17.5 Minimum Standard
The mobile station shall comply with the requirements in steps h, i and k.
2.18 PACA Origination, Traffic Channel Becomes Available
2.18.1 Definition
This test verifies that a currently PACA queued mobile station, when notified by the base station of an available traffic channel, should properly alert the user that the origination can now be completed.
2.18.2 Traceability (see [4])
2.6.2 Mobile Station Idle State
2.6.2.8 Mobile Station PACA Cancel Operation
2.6.3.5 Mobile Station Origination Attempt Substate
2.7.1.3.2.4 Origination Message
2.7.1.3.2.9 PACA Cancel Message
2-21
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
3.7.2.3.2.20 PACA Message
2.18.3 Call Flow Example(s)
None
2.18.4 Method of Measurement
a. Allow the mobile station to come to the idle state on the base station.
b. At the base station, enable PACA feature for the mobile station, assign a PACA priority level to the mobile station, and disable Permanent Invocation PACA for the mobile station.
c. Ensure PACA is enabled on the base station.
d. Configure the base station to make all traffic channels busy.
e. Setup a mobile station originated call.
f. If supported by the mobile station, verify that the mobile station user interface indicates that an origination has been successfully queued.
g. Make at least one traffic channel available on the base station.
h. The base station shall page the mobile station, and the mobile station should indicate to the user that the PACA call is proceeding.
i. Verify the call is completed and audio is present in both directions.
j. End call.
2.18.5 Minimum Standard
The mobile station shall comply with the requirements in steps f and i.
2.19 PACA Origination, Features Interaction
2.19.1 Definition
This test verifies that specific paging channel features, such as SMS and MWI, are delivered to the mobile station while the mobile station is currently in a PACA queue.
2.19.2 Traceability (see [4])
2.6.2 Mobile Station Idle State
2.6.2.8 Mobile Station PACA Cancel Operation
2.6.3.5 Mobile Station Origination Attempt Substate
2.7.1.3.2.4 Origination Message
2.7.1.3.2.9 PACA Cancel Message
3.7.2.3.2.20 PACA Message
2-22
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.19.3 Call Flow Example(s)
None
2.19.4 Method of Measurement
a. Allow the mobile station to come to the idle state on the base station.
b. At the base station, enable PACA feature for the mobile station, assign a PACA priority level to the mobile station, and disable Permanent Invocation PACA for the mobile station.
c. Ensure PACA is enabled on the base station.
d. Configure the base station to make all traffic channels busy.
e. Setup a mobile station originated call.
f. Verify the mobile station user interface indicates that an origination has been successfully queued.
g. Send an SMS message over the Paging Channel to the mobile station. Verify the message is properly received by the mobile station.
h. Configure base station to send MWI to the mobile station. Verify MWI is displayed by the mobile station.
i. End call.
2.19.5 Minimum Standard
The mobile station shall comply with the requirements in steps f, g, and h.
2.20 PACA Origination, Permanent Invocation
2.20.1 Definition
This test verifies that a PACA-capable mobile station with Permanent Invocation feature enabled shall be placed in PACA queue even if PACA is not requested in Origination Message.
2.20.2 Traceability (see [4])
2.6.2 Mobile Station Idle State
2.6.2.8 Mobile Station PACA Cancel Operation
2.6.3.5 Mobile Station Origination Attempt Substate
2.7.1.3.2.4 Origination Message
2.7.1.3.2.9 PACA Cancel Message
3.7.2.3.2.20 PACA Message
2.20.3 Call Flow Example(s)
None
2-23
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.20.4 Method of Measurement
a. Allow the mobile station to come to the idle state on the base station.
b. At the base station, enable PACA feature for the mobile station, assign a PACA priority level to the mobile station, and enabled Permanent Invocation PACA for the mobile station.
c. Ensure PACA is enabled on the base station.
d. Configure the base station to make all traffic channels busy.
e. Setup a mobile station originated call.
f. Verify the following:
1. Mobile station originates call with PACA_REORIG bit='0' in Origination Message.
2. Due to Permanent Invocation, base station sends PACA Message with PURPOSE='0000' and the mobile station's Queue Position (Q_POS).
3. Mobile station acknowledges PACA Message.
4. The mobile station user interface should indicate origination successfully queued.
g. Make at least one traffic channel available on the base station.
h. The base station shall page the mobile station, and the mobile station should indicate to the user that the PACA call is proceeding.
i. Verify call completes and audio is present in both directions.
j. End call.
2.20.5 Minimum Standard
The mobile station shall comply with the requirements in steps f and j.
2.21 PACA Origination, PACA Disabled for Mobile Station
2.21.1 Definition
This test verifies that when a mobile station disabled for PACA attempts a PACA Origination, the call shall fail.
2.21.2 Traceability (see [4])
2.6.2 Mobile Station Idle State
2.6.2.8 Mobile Station PACA Cancel Operation
2.6.3.5 Mobile Station Origination Attempt Substate
2.7.1.3.2.4 Origination Message
2-24
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.7.1.3.2.9 PACA Cancel Message
3.7.2.3.2.20 PACA Message
2.21.3 Call Flow Example(s)
None
2.21.4 Method of Measurement
a. Allow the mobile station to come to the idle state on the base station.
b. Ensure PACA is enabled on the base station.
c. At the base station, disable PACA feature for the mobile station.
d. Configure the base station to make all traffic channels busy.
e. Setup a mobile station originated call.
f. Verify the following:
1. Mobile station originates call with PACA_REORIG bit=0 in Origination Message.
2. Due to lack of available channels, base station replies with a Reorder Order.
3. Mobile station retries the origination with the PACA_REORIG bit = '1' in the Origination Message.
4. A second call re-origination attempt is denied by the base station and a reorder tone is generated at the mobile station.
2.21.5 Minimum Standard
The mobile station shall comply with the requirements in step f.
2.22 Service Configuration and Negotiation without SYNC_ID
2.22.1 Definition
This test verifies that the initial service configuration in effect is according to the value specified via the GRANTED_MODE field of the Extended Channel Assignment Message. This test also verifies that after service negotiation, the service configuration in use is the one specified by SCR and NN-SCR agreed upon during service negotiation.
2.22.2 Traceability (see [4])
2.6.4.1.2 Mobile Station Service Configuration and Negotiation procedures
2.6.4.1.14 Processing the Service Configuration Record
2.6.4.1.15 Processing the Non-Negotiable Service Configuration Record
2.6.4.2 Traffic Channel Initialization Substate
2.7.1.3.2.4 Origination Message
2.7.1.3.2.5 Page Response Message
2-25
C.S0044-0 v1.0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
2.7.2.3.2.12 (Mobile Station) Service Request Message
2.7.2.3.2.13 (Mobile Station) Service Response Message
2.7.2.3.2.14 (Mobile Station) Service Connect Completion Message
2.7.4.18 Service Configuration information record
3.6.4.1.2 Base Station Service Configuration and Negotiation procedures
3.7.2.3.2.21 Extended Channel Assignment Message
3.7.3.3.2.18 (Base Station) Service Request Message
3.7.3.3.2.19 (Base Station) Service Response Message
3.7.3.3.2.20 (Base Station) Service Connect Message
3.7.3.3.2.31 General Handoff Direction Message
3.7.3.3.2.36 Universal Handoff Direction Message
3.7.5.7 (Base Station) Service Configuration information record
3.7.5.20 (Base Station) Non-Negotiable Service Configuration information record
2.22.3 Reference Call Flow
BS
DedicatedChannels
MS
DedicatedChannels
Service Connect Message/General Handoff Direction Message/
Universal Handoff Direction Message(SCR_new, NN-SCR_new)
New serviceconfigurationtakes effect
CommonChannels
CommonChannels
Origination Message /Page Response Message
(SO)
Extended Channel Assignment Message(GRANTED_MODE)
Initial serviceconfiguration
in effect
Service Connect Completion Message/Extended Handoff Completion Message
Optional Service Negotiation Message Exchange(Service Negotiation ends with two message below)
15
16
17
18 19 20 21
Figure 2-2 Reference Call Flow for Service Configuration and Negotiation without SYNC_ID
2.22.4 Method of Measurement
Note – In this test case, it shall be ensured that mobile station does not include SYNC_ID field in the Origination Message/Page Response Message. This can be done by selecting type of call for which corresponding service configuration is not stored in mobile station. Note that the mobile station needs to store service configuration per SID, NID. Hence changing SID or NID or CDMA
2-26
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 33 34 35 36
37 38
39 40 41
channel may be useful in ensuring that mobile station does not include SYNC_ID field in the Origination Message/Page Response Message.
a. Connect the mobile station to the base station as shown in Annex A Figure A-1.
b. If the mobile station supports voice call, initiate a mobile station originated voice call. Otherwise go to step f.
c. After the base station sends an Extended Channel Assignment Message to the mobile station, the service negotiation shall occur between base station and mobile station. The service negotiation ends when base station sends Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message with SCR and NN-SCR to the mobile station and mobile station accepts the service configuration by sending Service Connect Completion Message/Extended Handoff Completion Message.
d. Verify the following:
1. If the base station sends Extended Channel Assignment Message with GRANTED_MODE field set to ‘00’ in step c above
a. Prior to the new service configuration sent in the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message takes effect, verify the following:
1. The service configuration in use is the one jointly specified by the DEFAULT_CONFIG value sent in the Extended Channel Assignment Message and the default Non-Negotiable part of the service configuration parameters specified in the Traffic Channel Initialization substate.
b. When the new service configuration sent in the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message takes effect, verify the following:
1. The service configuration in use is the one specified by SCR and NN-SCR in the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message sent by the base station.
2. Verify user traffic on both directions.
3. The base station receives a Service Connect Completion Message (if base station sends Service Connect Message) or an Extended Handoff Completion Message (if base station sends General Handoff Direction Message/Universal Handoff Direction Message) from the mobile station.
2. If base station sends Extended Channel Assignment Message with GRANTED_MODE field set to ‘01’ in step c above
a. Prior to the new service configuration sent in the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message takes effect, verify the following:
2-27
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
33 34 35
36
37 38 39 40 41
1. The service configuration in use is the one jointly specified by the default multiplex option that is derived from the radio configuration corresponding to Table 3.7.2.3.2.21-7 of [4] and the default Non-Negotiable part of the service configuration parameters specified in the Traffic Channel Initialization substate.
b. When the new service configuration sent in the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message takes effect, verify the following:
1. The service configuration in use is the one specified by SCR and NN-SCR in the Service Connect Message sent by the base station.
2. Verify user traffic in both directions.
3. The base station receives a Service Connect Completion Message (if base station sends Service Connect Message) or an Extended Handoff Completion Message (if base station sends General Handoff Direction Message/Universal Handoff Direction Message) from the mobile station.
3. If base station sends Extended Channel Assignment Message with GRANTED_MODE field set to ‘10’ in step c above
a. Prior to the new service configuration sent in the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message takes effect, verify the following:
1. The service configuration in use is the one jointly specified by the default multiplex option that is derived from the radio configuration corresponding to Table 3.7.2.3.2.21-7 of [4] and the default Non-Negotiable part of the service configuration parameters specified in the Traffic Channel Initialization Substate.
b. When the new service configuration sent in the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message takes effect, verify the following:
1. The service configuration in use is the one specified by SCR and NN-SCR in the Service Connect Message sent by the base station.
2. Verify user traffic on both directions.
3. The base station receives a Service Connect Completion Message (if base station sends Service Connect Message) or an Extended Handoff Completion Message (if base station sends General Handoff Direction Message/Universal Handoff Direction Message) from the mobile station.
2-28
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
33
34
35
4. The mobile station does not send a Service Request Message to the base station prior to the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message is received from the base station.
e. Repeat steps a through d for mobile station terminated calls. In this case, Page Response Message replaces Origination Message.
f. If mobile station supports data calls, repeat steps a to e above but with following modification – In step b initiate data call in place of voice call.
2.22.5 Minimum Standard
The mobile station shall comply with step d.
2.23 Service Configuration and Negotiation with SYNC_ID
2.23.1 Definition
This test verifies that the mobile station can propose to use stored service configuration using SYNC_ID in the Service Configuration and Negotiation process.
Note – This test assumes that the mobile station stores old service configuration with corresponding SYNC_ID and uses SYNC_ID during call setup. If the mobile station does not use SYNC_ID in call setup, then skip this test. This test also assumes that the base station sets USE_SYNC_ID field to ‘1’ in Extended System Parameters Message and/or MC-RR Parameters Message. If the base station is unable to do this, then skip this test.
2.23.2 Traceability (see [4])
2.6.2.2.5 Extended System Parameters Message
2.6.2.2.14.1 Stored Parameters
2.6.2.5 Mobile Station Origination Operation
2.6.3.3 Page Response Substate
2.6.3.5 Mobile Station Origination Attempt Substate
2.6.4.1.2 (Mobile Station) Service Configuration and Negotiation (procedures)
2.6.4.1.12 Processing the Service Configuration Record
2.6.4.1.13 Processing the Non-Negotiable Service Configuration Record
Traffic Channel Initialization Substate
2.6.4.4 Release Substate
2.6.6.2.5 Handoff Messages
2.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages
2.7.1.3.2.4 Origination Message
2.7.1.3.2.5 Page Response Message
2.7.2.3.2.12 (Mobile Station) Service Request Message
2-29
C.S0044-0 v1.0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
2.7.2.3.2.13 (Mobile Station) Service Response Message
2.7.2.3.2.14 (Mobile Station) Service Connect Completion Message
2.7.4.18 (Mobile Station) Service Configuration (information record)
(Base Station) Service Configuration and Negotiation (procedures)
3.7.2.3.2.13 Extended System Parameters Message
Extended Channel Assignment Message
3.7.2.3.2.31 MC-RR Parameters Message
3.7.3.3.2.18 (Base Station) Service Request Message
3.7.3.3.2.19 (Base Station) Service Response Message
3.7.3.3.2.20 (Base Station) Service Connect Message
3.7.3.3.2.31 General Handoff Direction Message
3.7.3.3.2.36 Universal Handoff Direction Message
3.7.5.7 (Base Station) Service Configuration ( information record)
3.7.5.20 (Base Station) Non-Negotiable Service Configuration ( information record)
2.23.3 Reference Call Flow
BS
DedicatedChannels
MS
DedicatedChannels
Service Connect Message(USE_OLD_SERV_CONFIG,
SCR_new, NN-SCR_new)
New serviceconfigurationtakes effect
CommonChannels
CommonChannels
Origination Message /Page Response Message
(SYNC_ID)
Extended Channel Assignment Message(GRANTED_MODE)
Initial serviceconfiguration
in effect
Service Connect Completion Message
Optional Service Negotiation Message Exchange(Service Negotiation ends with two messages below)
16
17 Figure 2-3 Reference Call Flow for Service Configuration and Negotiation with SYNC_ID
2-30
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
33
34 35
36 37
38
2.23.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Annex A Figure A-1. Verify that the base station sets USE_SYNC_ID field to ‘1’ in Extended System Parameters Message and/or MC-RR Parameters Message.
b. Identify a type of call for which the base station would send the SYNC_ID with SCR and NN_SCR and the mobile station would use SYNC_ID when the same type of call is originated again. Initiate a mobile station originated call with this call type. Verify that the base station includes SYNC_ID field in the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message sent to the mobile station. Once the service configuration sent in the Service Connect Message/General Handoff Direction Message/Universal Handoff Direction Message has taken effect, disconnect the call.
c. Initiate a mobile station originated call with same call type as above. Verify that mobile station includes SYNC_ID field in the Origination Message.
d. The service negotiation ends when base station sends Service Connect Message to the mobile station and mobile station accepts the service configuration by sending Service Connect Completion Message.
e. Verify the following:
1. If the base station sends Service Connect Message with USE_OLD_SERV_CONFIG field set to ‘00’
a. When the Service Connect Message takes effect, verify the following:
1. The service configuration in use is the one specified by SCR and NN-SCR in the Service Connect Message sent by the base station.
2. Verify user traffic (e.g. SO 33) on both directions.
3. The base station receives a Service Connect Completion Message from the mobile station.
2. If the base station sends Service Connect Message with USE_OLD_SERV_CONFIG field set to ‘01’
a. When the new service configuration specified in the Service Connect Message takes effect, verify the following:
1. The mobile station uses the stored service configuration.
2. Verify user traffic (e.g. SO 33) on both directions.
3. The base station receives a Service Connect Completion Message from the mobile station.
3. If the base station sends Service Connect Message with USE_OLD_SERV_CONFIG field set to ‘10’
a. When the Service Connect Message takes effect, verify the following:
2-31
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
1. The mobile station uses the stored service configuration.
2. Verify user traffic (e.g SO 33) on both directions.
3. The base station receives a Service Connect Completion Message from the mobile station.
f. Repeat steps a through d for mobile station terminated calls. In this case, Origination Message is replaced by Page Response Message.
2.23.5 Minimum Standard
The mobile station shall comply with step e.
2.24 Intra-Band Channel Assignment
2.24.1 Definition
This test verifies that the mobile station originating a call can be assigned a different frequency within the same band class using the (Extended) Channel Assignment Message.
2.24.2 Traceability: (See [4])
2.6.2.4 Mobile Station Order and Message Processing Operation
2.6.3.5 Mobile Station Origination Attempt Substate
2.7.1.3.2.4 Origination Message
2.7.1.3.2.5 Page Response Message
3.7.2.3.2.8 Channel Assignment Message
3.7.2.3.2.21 Extended Channel Assignment Message
2.24.3 Call Flow Example(s)
None
2.24.4 Method of Measurement
a. Connect the mobile station and base stations as shown in Figure A-2. Base station 1 and base station 2 are operating the same band class with different frequencies.
b. Ensure the mobile station is operating in the Idle State on base station 1.
c. Setup a mobile station originated call.
d. Ensure that the base station sends a Channel Assignment Message or Extended Channel Assignment Message with the following settings:
2-32
C.S0044-0 v1.0
Table 2.24.4-1 Channel Assignment Message Settings 1
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
4
5 6
7
8
9
10
11
12
13
14 15 16 17
18
19
e. Verify the mobile station tunes to the new frequency and completes the call on base station 2.
f. Verify user data in both directions.
g. End the call.
h. Setup a mobile station terminated call and repeat steps d through g.
2.24.5 Minimum Standard
The mobile station shall comply with steps e, f, and h.
2.25 Silent-Retry
2.25.1 Definition
This test verifies the mobile station silent-retry functionality and the proper setting of ARQ fields. Silent-retry is an autonomous access re-attempt that is made to re-originate the call, without user interaction, that is due to the mobile station receiving an access attempt failure from the ARQ Sublayer.
2.25.2 Traceability
2.7.1.3.2.4 Origination Message (see [4])
2-33
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
2.2.1.1.2.1.5 Access Channel Procedures (see [2])
2.1.1.2.1.2 Requirements for Setting the ARQ Fields (see [3])
2.1.1.2.2.1 Overview of Transmission and Retransmission Procedures (see [3])
2.25.3 Call Flow Example(s)
None
2.25.4 Method of Measurement
a. Connect the base station as shown in Figure A-3. Disable the reverse link to the base station.
b. Attempt to setup a mobile station originated call. Note the MSG_SEQ value in the Origination Message.
c. Allow the mobile station to exhaust NUM_STEP or EACH_NUM_STEP and MAX_REQ_SEQ as defined in the Access Parameters Message or Enhanced Access Parameters Message.
d. Enable the reverse link to the base station.
e. Verify the following:
1. If the P_REV_IN_USE is less than or equal to six verify;
a. The mobile station sends a new Origination Message.
b. The MSG_SEQ value in the Origination Message is different than the value recorded in step b.
2. Otherwise, verify;
a. The mobile station sends a new Origination Message with the following values:
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 27
28
b. The MSG_SEQ value in the Origination Message is different than the value recorded in step b.
f. Verify the call completes and user traffic is present in both directions (i.e. audio).
2-34
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 33 34 35
2.25.5 Minimum Standard
The mobile station shall comply with steps e and f.
2.26 MSID, MCC, and IMSI
2.26.1 Definition
These tests verify some protocol of the Mobile Station IDentifier number (MSID or MSIN), Mobile Country Code (MCC), and International Mobile Station Identity (IMSI). Mobile station response to three instances of base station PREF_MSID_TYPE are checked when the MCC and IMSI_11_12 of the mobile station and base station match, do not match or are wildcard values.
2.26.2 Traceability
[4] 3.7.2.3.2.13 Extended System Parameters Message
[4] 2.6.2.2.5 Extended System Parameters Message
[4] 2.6.2.3 Mobile Station Page Match Operation
[4] 2.3.1 Mobile Station Identification Number
[4] 2.3.1.1 Encoding of IMSI_M_S and IMSI_T_S 11
[4] Table 3.7.2.3.2.13-1. Preferred MSID Types
[4] 3.6.2.2 Overhead Information
[3] 2.1.1.3.1.1 Addressing
[3] 2.1.1.2.1.3 IMSI Class
2.26.3 Call Flow Diagram
none
2.26.4 Method of Measurement
For each step below, set USE_TMSI = ‘0’ in the base station Extended System Parameters Message or ANSI-41 System Parameters Message. Also program either the mobile station or the base station for the values of MCC and IMSI_11_12, to achieve the matching or non-matching conditions indicated.
a. PREF_MSID_TYPE = ‘00’. Configure the base station Extended System Parameters Message with PREF_MSID_TYPE = ‘00’. Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = ’000’ and sends IMSI_S and ESN in the Origination Message and Page Response Message.
b. PREF_MSID_TYPE = ‘10’, matching MCC and matching IMSI_11_12. Configure the base station Extended System Parameters Message with PREF_MSID_TYPE = ‘10’. Verify the values of both MCC and IMSI_11_12 are the same (match) in the mobile station and base station. Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = ‘010’ and sends IMSI_S
2-35
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
(does not send MCC and IMSI_11_12) in the Origination Message and Page Response Message.
c. PREF_MSID_TYPE = ‘10’, non-matching MCC and matching IMSI_11_12. Configure the base station Extended System Parameters Message with PREF_MSID_TYPE = ‘10’. Verify the values of IMSI_11_12 are the same (match) in the mobile station and base station, but the values of MCC are different (don’t match). Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = ‘010’ and sends MCC and IMSI_S (does not send IMSI_11_12) in the Origination Message and Page Response Message.
d. PREF_MSID_TYPE = ‘10’, matching MCC and non-matching IMSI_11_12. Configure the base station Extended System Parameters Message with PREF_MSID_TYPE = ‘10’. Verify the values of MCC are the same (match) in the mobile station and base station, but the values of IMSI_11_12 are different (don’t match). Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = ‘010’ and sends IMSI_11_12 and IMSI_S (does not send MCC) in the Origination Message and Page Response Message.
e. PREF_MSID_TYPE = ‘10’, non-matching MCC and non-matching IMSI_11_12. Configure the base station Extended System Parameters Message with PREF_MSID_TYPE = ‘10’. Verify the values of both MCC and IMSI_11_12 are different in the mobile station and base station (neither matches). Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = ‘010’ and sends MCC, IMSI_11_12 and IMSI_S in the Origination Message and Page Response Message.
f. PREF_MSID_TYPE = ‘10’, wildcard MCC and wildcard IMSI_11_12. Configure the base station Extended System Parameters Message with the following fields.
Field Value
PREF_MSID_TYPE ‘10’
MCC ‘1111111111’ (wildcard)
IMSI_11_12 ‘1111111’ (wildcard)
27 28 29
30 31 32 33 34
g. Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = ‘010’ and sends IMSI_S (but does not send MCC and IMSI_11_12) in the Origination Message and Page Response Message.
h. PREF_MSID_TYPE = ‘11’, matching MCC and matching IMSI_11_12. Configure the base station Extended System Parameters Message with PREF_MSID_TYPE = ‘11’. Verify the values of both MCC and IMSI_11_12 are the same in the mobile station and base station (both match). Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = ‘011’ and sends IMSI_S
2-36
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
and ESN (does not send MCC and IMSI_11_12) in the Origination Message or Page Response Message.
i. PREF_MSID_TYPE = ‘11’, non-matching MCC and matching IMSI_11_12. Configure the base station Extended System Parameters Message with PREF_MSID_TYPE = ‘11’. Verify the values of IMSI_11_12 are the same in the mobile station and base station (match), but the values of MCC are different (don’t match). Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = ‘011’ and sends MCC, IMSI_S and ESN (does not send IMSI_11_12) in the Origination Message and Page Response Message.
j. PREF_MSID_TYPE = ‘11’, matching MCC and non-matching IMSI_11_12. Configure the base station Extended System Parameters Message with PREF_MSID_TYPE = ‘11’. Verify the values of MCC are the same in the mobile station and base station (match), but the values of IMSI_11_12 are different (don’t match). Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = ‘011’ and sends IMSI_11_12, IMSI_S and ESN (does not send MCC) in the Origination Message and Page Response Message.
k. PREF_MSID_TYPE = ‘11’, non-matching MCC and non-matching IMSI_11_12. Configure the base station Extended System Parameters Message with PREF_MSID_TYPE = ‘11’. Verify the values of both MCC and IMSI_11_12 are different in the mobile station and base station. Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = ‘011’ and sends MCC, IMSI_11_12, IMSI_S, and ESN in the Origination Message and Page Response Message.
l. PREF_MSID_TYPE = ‘11’, wildcard MCC and wildcard IMSI_11_12. Configure the base station Extended System Parameters Message with the following fields.
Field Value
PREF_MSID_TYPE ‘11’
MCC ‘1111111111’ (wildcard)
IMSI_11_12 ‘1111111’ (wildcard)
27
28 29 30
31
32 33
m. Make a mobile station originated call and a mobile station terminated call. Verify the mobile station sets MSID_TYPE = ‘011’ and sends IMSI_S and ESN (but does not send MCC and IMSI_11_12) in the Origination Message and Page Response Message.
2.26.5 Minimum Standard
All calls shall complete normally. The mobile station shall comply with requirements in steps b through m.
2-37
C.S0044-0 v1.0
3 HANDOFF TESTS 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
3.1 Soft Handoff with Dynamic Threshold
3.1.1 Definition
This test verifies the mobile station and base station perform soft handoff. Soft handoff with and without dynamic thresholds is verified. This test verifies both adding pilot to and dropping pilot from the soft handoff Active Set. Tests 1 through 4 apply to cases when SOFT_SLOPE is not equal to ‘000000’ (dynamic threshold enabled).
3.1.2 Traceability (See [4])
2.6.2.2.5 Extended System Parameters Message
2.6.4.1.4 Processing the In-Traffic System Parameters Message
2.6.6.2.3 Handoff Drop Timer
2.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages
2.6.6.2.5.2 Processing of Reverse Traffic Channel Handoff Messages
2.6.6.2.6.2 Maintenance of the Candidate Set
2.6.6.2.6.3 Maintenance of the Neighbor Set
2.6.6.2.8.2.1 Restoring the Configuration
2.6.6.3 Examples
2.7.2.3.2.5 Pilot Strength Measurement Message
3.6.6.2.1.1 System Parameters
3.7.2.3.2.13 Extended System Parameters Message
3.7.3.3.2.7 In-Traffic System Parameters Message
3.7.3.3.2.17 Extended Handoff Direction Message
3.7.3.3.2.31 General Handoff Direction Message
3.7.3.3.2.36 Universal Handoff Direction Message
3.1.3 Call Flow Example(s)
None
3.1.4 Method of Measurement
a. Setup test as shown in Figure A-4.
1. The Forward Channel from sector α of base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1.
2. The Forward Channel from sector ß of base station 1 has an arbitrary pilot PN offset index P2 and is called Channel 2.
3-1
C.S0044-0 v1.0
1 2
3
4
3. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P3 and is called Channel 3.
b. Set the test parameters for Test 1 as specified in Table 3.1.4-1and Table 3.1.4-2.
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)
5
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
Ioc dBm/1.23 MHz -75
Pilot Ec/Io dB -5.8 -33 -33
7
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
Table 3.1.4-3 1
Parameter Unit Channel 1 Channel 2 Channel 3
Îor/Ioc dB 7 7 -20
Pilot Ec/Ior dB -5 -5 -5
Traffic Ec/Ior dB -7 -7 -7
Ioc dBm/1.23 MHz -75
Pilot Ec/Io dB -8.4 -8.4 -35
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
c. Reverse link attenuation should be set to balance the forward and reverse links (approximately 90 dB).
d. Setup a mobile station originated call.
e. Verify user data in both directions. Verify only Channel 1 is in the Active Set.
f. Raise the level of Channel 2 in steps of 1 dB with a dwell time of five seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Record the level of Pilot Ec/Io in the Pilot Strength Measurement Message.
g. Verify the following
1. The mobile station generates a Pilot Strength Measurement Message when the level of channel 2 is at a Pilot Ec/Io level between –10 dB and –13 dB.
2. The base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station to allow soft handoff between Channel 1 and Channel 2.
3. The mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message as a response to handoff message.
4. The mobile station is in soft handoff between Channel 1 and Channel 2.
h. Set test parameters for Test 2 as specified in Table 3.1.4-3 while Channel 1 and Channel 2 are in soft handoff. Raise the level of Channel 3 in steps of 1 dB with a dwell time of five seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Record the level of Pilot Ec/Io in the Pilot Strength Measurement Message.
i. Verify the following:
1. The mobile station generates a Pilot Strength Measurement Message when the level of channel 3 is at a level between –10 dB and –13 dB.
2. The base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station to allow soft handoff between Channel 1, Channel 2 and Channel 3.
3-3
C.S0044-0 v1.0
1 2
3 4
5 6 7 8 9
10
11
3. The mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message as a response to handoff message.
4. The mobile station is in soft handoff among Channel 1, Channel 2 and Channel 3.
j. Set the test parameters for Test 3 in Table 3.1.4-4 while Channel 1, Channel 2, and Channel 3 are in soft handoff. Lower the level of Channel 3 in steps of 1 dB with a dwell time of 30 seconds until the mobile station has generated the Pilot Strength Measurement Message. Record the level of Pilot Ec/Io in the Pilot Strength Measurement Message.
Table 3.1.4-4
Parameter Unit Channel 1 Channel 2 Channel 3
Îor/Ioc dB 7 7 7
Pilot Ec/Ior dB -5 -5 -5
Traffic Ec/Ior dB -7 -7 -7
Ioc dBm/1.23 MHz -75
Pilot Ec/Io dB -10.1 -10.1 -10.1
12
13 14 15
16 17 18
19 20
21
22 23 24 25
k. Verify the following:
1. The mobile station generates a Pilot Strength Measurement Message when the level of channel 3 is at a level between –12 dB and –16 dB for a period of T_TDROP.
2. The base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station to allow soft handoff between Channel 1 and Channel 2.
3. The mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message as a response to handoff message.
4. The mobile station is in soft handoff between Channel 1 and Channel 2.
l. Set test parameters for Test 4 as specified in Table 3.1.4-5. Lower level of Channel 2 in steps of 1 dB with a dwell time of 30 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Record the level of Pilot Ec/Io in the Pilot Strength Measurement Message.
3-4
C.S0044-0 v1.0
Table 3.1.4-5 1
Parameter Unit Channel 1 Channel 2 Channel 3
Îor/Ioc dB 7 7 -20
Pilot Ec/Ior dB -5 -5 -5
Traffic Ec/Ior dB -7 -7 -7
Ioc dBm/1.23 MHz -75
Pilot Ec/Io dB -8.4 -8.4 -35
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
m. Verify the following:
1. The mobile station shall generate a Pilot Strength Measurement Message when the level of channel 2 is at a level of –11 dB and –14 dB for a period of T_TDROP.
2. The base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station with only Channel 1 listed in the Active Set.
3. The mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message as a response to handoff message.
4. Channel 1 is the only Active Set for the mobile station.
3.1.5 Minimum Standard
Verify steps g, i, k and m.
3.2 Soft Handoff without Dynamic Threshold
3.2.1 Definition
This test verifies the proper operation of mobile station soft handoff. Soft handoff without dynamic thresholds is verified. This test verifies both adding pilot to and dropping pilot from the soft handoff Active Set. Tests 1 through 4 apply to cases when SOFT_SLOPE is equal to ‘000000’ (dynamic threshold disabled).
3.2.2 Traceability (See [4])
2.6.2.2.5 Extended System Parameters Message
2.6.4.1.4 Processing the In-Traffic System Parameters Message
2.6.6.2.3 Handoff Drop Timer
2.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages
2.6.6.2.5.2 Processing of Reverse Traffic Channel Handoff Messages
2.6.6.2.6.2 Maintenance of the Candidate Set
2.6.6.2.6.3 Maintenance of the Neighbor Set
3-5
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
2.6.6.2.8.2.1 Restoring the Configuration
2.6.6.3 Examples
2.7.2.3.2.5 Pilot Strength Measurement Message
3.6.6.2.1.1 System Parameters
3.7.2.3.2.13 Extended System Parameters Message
3.7.3.3.2.7 In-Traffic System Parameters Message
3.7.3.3.2.17 Extended Handoff Direction Message
3.7.3.3.2.31 General Handoff Direction Message
3.7.3.3.2.36 Universal Handoff Direction Message
3.2.3 Call Flow Example(s)
None
3.2.4 Method of Measurement
a. Setup test as shown in Figure A-4. Start with Test 1 to Test 4 with dynamic threshold disabled.
1. The Forward Channel from sector α of base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1.
2. The Forward Channel from sector ß of base station 1 has an arbitrary pilot PN offset index P2 and is called Channel 2.
3. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P3 and is called Channel 3.
b. Set the test parameters for Test 1 as specified in Table 3.2.4-1 and Table 3.2.3-2.
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
Table 3.2.4-2 1
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
Ioc dBm/1.23 MHz -75
Pilot Ec/Io dB -5.8 -33 -33
2
3
Table 3.2.4-3
Parameter Unit Channel 1 Channel 2 Channel 3
Îor/Ioc dB 7 7 -20
Pilot Ec/Ior dB -5 -5 -5
Traffic Ec/Ior dB -7 -7 -7
Ioc dBm/1.23 MHz -75
Pilot Ec/Io dB -8.4 -8.4 -35
4
5 6
7
8
9 10 11
12
13 14
15 16 17
18 19
20
21 22
c. Reverse link attenuation should be set to balance the forward and reverse links (approximately 90 dB).
d. Setup a mobile station originated call.
e. Verify user data in both directions. Verify only Channel 1 is in the Active Set.
f. Raise the level of Channel 2 in steps of 1 dB with a dwell time of five seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Record the level of Pilot Ec/Io in the Pilot Strength Measurement Message.
g. Verify the following:
1. The mobile station generates a Pilot Strength Measurement Message when the level of channel 2 is at a level between T_ADD and T_ADD +2 dB.
2. The base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station to allow soft handoff between Channel 1 and Channel 2.
3. The mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message as a response to handoff message.
4. The mobile station is in softer handoff between Channel 1 and Channel 2.
h. Set test parameters for Test 2 as specified in Table 3.2.4-3 while Channel 1 and Channel 2 are in soft handoff. Raise the level of Channel 3 in steps of 1 dB with a dwell
3-7
C.S0044-0 v1.0
time of five seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Record the level of Pilot E
1 2 3
4
5 6 7
8 9
10 11
12 13
14 15
16 17 18 19 20
21
c/Io in the Pilot Strength Measurement Message.
i. Verify the following:
1. The mobile station generates a Pilot Strength Measurement Message when the level of channel 3 is at a level between T_DROP and T_DROP –3 dB for a period of T_TDROP.
2. The base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station to allow softer handoff between Channel 1, Channel 2 and Channel 3.
3. The mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message as a response to handoff message.
4. The mobile station is in softer handoff among Channel 1, Channel 2 and Channel 3.
j. Set the test parameters for Test 3 in Table 3.2.4-4 while Channel 1, Channel 2, and Channel 3 are in soft handoff. Lower the level of Channel 3 in steps of 1 dB with a dwell time of 30 seconds until the mobile station has generated the Pilot Strength Measurement Message. Record the level of Pilot Ec/Io in the Pilot Strength Measurement Message.
Table 3.2.4-4
Parameter Unit Channel 1 Channel 2 Channel 3
Îor/Ioc dB 7 7 7
Pilot Ec/Ior dB -5 -5 -5
Traffic Ec/Ior dB -7 -7 -7
Ioc dBm/1.23 MHz -75
Pilot Ec/Io dB -10.1 -10.1 -10.1
22
23
24 25 26
27 28 29
30 31
k. Verify the following:
1. The mobile station generates a Pilot Strength Measurement Message when the level of channel 3 is at a level between –12 dB and –16 dB for a period of T_TDROP.
2. The base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station to allow softer handoff between Channel 1 and Channel 2.
3. The mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message as a response to handoff message.
3-8
C.S0044-0 v1.0
1
2 3 4 5
6
4. The mobile station is in softer handoff between Channel 1 and Channel 2.
l. Set test parameters for Test 4 as specified in Table 3.2.4-5. Lower level of Channel 2 in steps of 1 dB with a dwell time of 30 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Record the level of Pilot Ec/Io in the Pilot Strength Measurement Message.
Table 3.2.4-5
Parameter Unit Channel 1 Channel 2 Channel 3
Îor/Ioc dB 7 7 -20
Pilot Ec/Ior dB -5 -5 -5
Traffic Ec/Ior dB -7 -7 -7
Ioc dBm/1.23 MHz -75
Pilot Ec/Io dB -8.4 -8.4 -35
7
8 9
10
11 12 13
14 15
16
17
18
19
20
21 22
23
24
25
26
27
m. Verify the following:
1. The mobile station shall generate a Pilot Strength Measurement Message when the level of channel 2 is at a level of T_DROP and T_DROP –3 dB for a period of T_TDROP.
2. The base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station with only Channel 1 listed in the Active Set.
3. The mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message as a response to handoff message.
4. Channel 1 is the only Active Set for the mobile station.
3.2.5 Minimum Standard
Verify steps g, i, k, and m.
3.3 Hard Handoff Between Frequencies in the Same Band Class
3.3.1 Definition
This test verifies the mobile station and base station perform hard handoff between different CDMA channels in the same band class.
3.3.2 Traceability (See [4])
2.6.6.1.1 Types of Handoff
2.6.6.2.5 Handoff Messages
2.6.6.2.8 CDMA-to-CDMA Hard Handoff
3.6.6.1.1 Types of Handoff
3-9
C.S0044-0 v1.0
1
2
3
4
5
6
7
8
9 10
11 12 13
14 15 16
17
18
3.6.6.2.2 Call Processing During Handoff
3.7.3.3.2.17 Extended Handoff Direction Message
3.7.3.3.2.31 General Handoff Direction Message
3.7.3.3.2.36 Universal Handoff Direction Message
3.3.3 Call Flow Example(s)
None
3.3.4 Method of Measurement
a. Setup test as shown in Figure A-5.
1. The Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1.
2. Setup base station 2 to be on a different CDMA channel than base station 1, but within the same band class. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P2 and is called Channel 2.
3. The AWGN source should be on the frequency of Channel 2. (It is advisable to achieve the maximum possible difference in frequency separation between Channel 1 and Channel 2).
b. Set the test parameters as shown in Table 3.3.4-1.
Table 3.3.4-1
Parameter Unit Channel 1 Channel 2
Î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
21
22
23 24 25 26 27
c. Set reverse link attenuation to balance forward and reverse links (approximately 90 dB).
d. Setup a mobile station originated call on Channel 1.
e. Verify user data in both directions.
f. Initiate handoff from Channel 1 to Channel 2. Verify that base station 1 initiates handoff from Channel 1 to Channel 2 by sending a General Handoff Direction Message, Universal Handoff Direction Message, or an Extended Handoff Direction Message with proper parameters (refer to tables in Annex B) to initiate handoff from Channel 1 to Channel 2.
3-10
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
33
g. One second or more after base station 1 sends a General Handoff Direction Message, a Universal Handoff Direction Message, or an Extended Handoff Direction Message disconnect or attenuate the forward link of Channel 1.
h. Verify user data in both directions.
i. Monitor calls and record the length of any audio dropouts present.
j. Steps b through g may be repeated for the case where it is a hard handoff to soft handoff on the same frequency with the following setup (see Figure A-4: one base station configured with two sectors active):
1. The Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1.
2. The Forward Channel from sector α of base station 2 has an arbitrary pilot PN offset index P2 and is called Channel 2.
3. The Forward Channel from sector ß of base station 2 has an arbitrary pilot PN offset index P3 and is called Channel 3.
k. The expected results for steps h and i should be the same as the previous test.
3.3.5 Minimum Standard
In step h, the mobile station and base stations shall successfully execute the hard handoff.
3.4 Hard Handoff from CDMA to Analog
3.4.1 Definition
This test verifies the mobile station and base station perform hard hand off from a CDMA system to an analog system.
3.4.2 Traceability (See [4])
2.6.6.1.1 Types of Handoff
2.6.6.2.9 CDMA-to-Analog Handoff
3.6.6.1.1 Types of Handoff
3.6.6.2.2 Call Processing During Handoff
3.7.3.3.2.6 Analog Handoff Direction Message
3.4.3 Call Flow Example(s)
None
3.4.4 Method of Measurement
a. Connect two base stations and an AWGN source to the mobile station as shown in Figure A-5. For the purpose of this test, Channel 1 is CDMA and Channel 2 is analog.
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
4
5 6
7
8
9 10 11
12 13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
c. Reverse link attenuation should be set to balance the forward and reverse links (approximately 90 dB).
d. Setup a mobile station originated call on Channel 1.
e. Verify user data in both directions.
f. Initiate handoff to analog. Verify the CDMA base station sends an Analog Handoff Direction Message with proper parameters (refer to tables in Annex B) to initiate handoff to analog.
g. One second or more after base station 1 sends an Analog Handoff Direction Message disconnect or attenuate the forward link of Channel 1.
h. Verify user data in both directions in the Analog system.
i. Monitor calls and record the length of any audio dropouts present on handoff.
3.4.5 Minimum Standard
In step h, the mobile station handoff to the Analog system shall be completed successfully
3.5 Soft Handoff in Fading
3.5.1 Definition
This test verifies soft handoff under various fading conditions:
a. 1 Ray Rayleigh fading at 30 km/hr
b. 3 Ray Rayleigh fading at 100 km/hr
c. 1 Ray Rayleigh fading at 3 km/hr
3.5.2 Traceability (See [4])
2.6.6.1.1 Types of Handoff
2.6.6.2.5 Handoff Messages
2.6.6.2.7 Soft Handoff
3.6.6.1.1 Types of Handoff
3.6.6.2.2 Call Processing During Handoff
3-12
C.S0044-0 v1.0
1
2
3
4
5
6 7
8 9
10
11
3.6.6.2.4 Soft Handoff
3.5.3 Call Flow Example(s)
None
3.5.4 Method of Measurement
a. Setup test as shown in A-2.
1. The Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1.
2. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P2 and is called Channel 2.
b. Set up the test parameters as shown in Table 3.5.4-1.
Table 3.5.4-1
Parameter Unit Channel 1 Channel 2
Îor/Ioc dB 0 -10
Pilot Ec/Ior dB -7 -7
Traffic Ec/Ior dB -7 -7
Ioc dBm/1.23 MHz -75 -75
Pilot Ec/Io dB -10.2 -20.2
12
13 14
15
16 17
18 19 20
21 22
23 24 25
26
27 28
c. Reverse link attenuation should be set to balance the forward and reverse links (approximately 90 dB).
d. Set both channel simulators to one Ray Rayleigh, 30 km/hr.
e. Setup a mobile station originated call on Channel 1. Monitor two-way audio and note anomalies throughout the test.
f. Raise the level of Channel 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Verify the following:
1. Pilot Strength Measurement Message is generated when the channel 2 Pilot Ec/Io is at a level above T_ADD.
2. Base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station.
3. Channel 1 and Channel 2 are in the Active Set at the action time of the message.
g. Mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message to the base station.
3-13
C.S0044-0 v1.0
1
2
h. Set the test parameters as specified in Table 3.5.4-2 without dropping the call.
Table 3.5.4-2
Parameter Unit Channel 1 Channel 2
Îor/Ioc dB 0 0
Pilot Ec/Ior dB -7 -7
Traffic Ec/Ior dB -7 -7
Ioc dBm/1.23 MHz -75 -75
Pilot Ec/Io dB -11.8 -11.8
3
4 5 6
7 8
9 10 11
12
13 14
15
16
i. Lower the level of Channel 1 in steps of 1 dB with a dwell time of 8 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Verify the following:
1. Pilot Strength Measurement Message is generated when Channel 1 is at a Pilot Ec/Io level below T_DROP for a period of TT_DROP.
2. Base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station.
3. Only Channel 2 is in the Active Set at the action time of the message.
4. Mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message to the base station.
j. Set the levels as specified in Table 3.5.4-3.
Table 3.5.4-3
Parameter Unit Channel 1 Channel 2
Îor/Ioc dB -10 0
Pilot Ec/Ior dB -7 -7
Traffic Ec/Ior dB -7 -7
Ioc dBm/1.23 MHz -75 -75
Pilot Ec/Io dB -20.2 -10.2
17
18 19 20
21
k. Raise the level of Channel 1 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Verify the following:
3-14
C.S0044-0 v1.0
1. Pilot Strength Measurement Message is generated when the channel 1 Pilot Ec/Io is at a level above T_ADD.
1 2
3 4 5
6
7 8
9
10
2. Base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station.
3. Channel 1 and Channel 2 are in the Active Set at the action time of the message.
4. Mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message to the base station.
l. Set the levels as specified in Table 3.5.4-4.
Table 3.5.4-4
Parameter Unit Value
Vehicle Speed km/hr 100
Number of Paths 3
Path 2 Power (Relative to Path 1)
dB 0
Path 3 Power (Relative to Path 1)
dB -3
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 12 13
14 15
16 17 18
19
20 21
22 23
24
m. Lower the level of Channel 2 in steps of 1 dB with a dwell time of 8 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message. Verify the following:
1. Pilot Strength Measurement Message is generated when the Channel 2 is at a Pilot Ec/Io level below T_DROP for a period of TT_DROP.
2. Base station sends an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message to the mobile station.
3. Only Channel 1 is in the Active Set at the action time of the message.
4. Mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message to the base station.
n. Repeat steps a through l under 3 Ray Rayleigh fading at 100 km/hr fading condition as specified in Table 3.5.4-4.
o. Repeat steps a through l under 1 Ray Rayleigh fading at 3 km/hr fading condition.
3-15
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
3.5.5 Minimum Standard
The mobile station shall generate the Pilot Strength Measurement Message at the appropriate time as specified in steps f, h, j, and l and the handoff shall be completed successfully.
3.6 Hard Handoff in Fading
3.6.1 Definition
This test verifies hard handoff under various fading conditions:
a. 1 Ray Rayleigh fading at 30 km/hr
b. 3 Ray Rayleigh fading at 100 km/hr
c. 1 Ray Rayleigh fading at 3 km/hr
Under various deployment scenarios:
a. Between frequencies
b. On the same frequency
3.6.2 Traceability (See [4])
2.6.6.1.1 Types of Handoff
2.6.6.2.5 Handoff Messages
2.6.6.2.8 CDMA-to-CDMA Hard Handoff
3.6.6.1.1 Types of Handoff
3.6.6.2.2 Call Processing During Handoff
3.6.3 Call Flow Example(s)
None
3.6.4 Method of Measurement
a. Setup test as shown in Figure A-2.
1. The Forward Channel from base station 1 on frequency F1, has an arbitrary pilot PN offset index P1 and is called Channel 1.
2. The Forward Channel from base station 2 on frequency F2, has an arbitrary pilot PN offset index P2 and is called Channel 2.
b. Set the test parameters as shown in Table 3.6.4-1.
3-16
C.S0044-0 v1.0
Table 3.6.4-1 1
Parameter Unit Channel 1 Channel 2
Îor/Ioc dB 0 0
Pilot Ec/Ior dB -7 -7
Traffic Ec/Ior dB -7 -7
Ioc dBm/1.23 MHz -75 -75
Pilot Ec/Io dB -10 -10
2
3
4
5
6
7 8 9
10 11 12
13
14 15
16 17 18
19
c. Set reverse link attenuation to balance forward and reverse links (approx. 90 dB).
d. Set the channel simulators for 1 Ray Rayleigh fading, 30 km/hr.
e. Setup a mobile station originated call on Channel 1.
f. Verify user data in both directions.
g. Initiate handoff from Channel 1 to Channel 2. Verify that base station 1 initiates a handoff from Channel 1 to Channel 2 by sending a General Handoff Direction Message, Universal Handoff Direction Message, or an Extended Handoff Direction Message.
h. Upon receiving an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message at the mobile station, verify the following:
1. Only Channel 2 is in the Active Set at the action time of the message.
2. The mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message to the base station.
i. Repeat steps a through h, with the channel simulators set to 3 Ray Rayleigh at 100 km/hr in step d. Use the setup shown in Table 3.5.4-4. The expected results are as given above for the previous test.
Table 3.6.4-2
Parameter Unit Channel 1 Channel 2
Îor/Ioc dB 0 0
Pilot Ec/Ior dB -7 -7
Traffic Ec/Ior dB -7 -7
Ioc dBm/1.23 MHz -75 -75
Pilot Ec/Io dB -11.8 -11.8
20
21 22
j. Repeat steps a through h, with the channel simulators set to 1 Ray Rayleigh at 3 km/hr in step d. The expected results are as given above for the previous test.
3-17
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 33
k. Repeat steps c through j for the scenario where the hard handoff is performed between two CDMA channels on the same frequency, with the setup test as shown in Figure A-5:
1. Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1.
2. Forward Channel from base station 2 has an arbitrary pilot PN offset index P2 and is called Channel 2.
3. Test parameters set as shown in Table 3.6.4-2.
l. Note that in this case a hard handoff can be forced by excluding P1 from the Active Set.
3.6.5 Minimum Standard
The mobile station shall comply with step h.
3.7 Hard Handoff Between Different Band Classes
3.7.1 Definition
This test verifies hard handoff between two different band classes. Both band classes are supported by the mobile station and base station.
3.7.2 Traceability (see [4] unless otherwise noted)
2.6.6.1.1 Types of Handoff
2.6.6.2.5 Handoff Messages
2.6.6.2.8 CDMA-to-CDMA Hard Handoff
3.6.6.1.1 Types of Handoff
3.6.6.2.2 Call Processing During Handoff
3.7.3.3.2.17 Extended Handoff Direction Message
3.7.3.3.2.31 General Handoff Direction Message
3.7.3.3.2.36 Universal Handoff Direction Message
2.1.1.1 Channel Spacing and Designation (see [1])
3.7.3 Call Flow Example(s)
None
3.7.4 Method of Measurement
a. Setup test as shown in Figure A-5.
1. The Forward Channel from the base station 1 in Band Class X has an arbitrary pilot PN offset index P1 and is called Channel 1.
2. The Forward Channel from the base station 2 in Band Class Y has an arbitrary pilot PN offset index P2 and is called Channel 2.
3-18
C.S0044-0 v1.0
1
2
b. Set the test parameters as shown in Table 3.7.4-1
Table 3.7.4-1
Parameter Unit Band Class X Band Class Y
Îor/Ioc dB -5 -5
Pilot Ec/Ior dB -7 -7
Traffic Ec/Ior dB -7 -7
Ioc dBm/1.23 MHz -75 -75
Pilot Ec/Io dB -13.2 -13.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
c. Set reverse link attenuation to balance forward and reverse links (approx. 90 dB).
d. Setup a call in Channel 1.
e. Verify user data in both directions.
f. Initiate handoff from base station 1 to base station 2. Verify the base station sends a General Handoff Direction Message, Universal Handoff Direction Message, or an Extended Handoff Direction Message with proper parameters (refer to tables in Annex B) to initiate handoff.
g. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message and the handoff is completed successfully.
h. Reconnect Channel 1 from base station 1 with parameters listed in Table 3.5.4-1.
i. Initiate handoff from base station 1 to base station 2. Verify that base station 2 sends a General Handoff Direction Message, Universal Handoff Direction Message, or an Extended Handoff Direction Message with proper parameters (refer to tables in Annex B) to initiate handoff.
j. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message and the handoff is completed successfully.
k. This test can be repeated for hard handoffs between other band classes.
3.7.5 Minimum Standard
The mobile station shall comply with steps g and k.
3.8 Hard Handoff with and without Return on Failure
3.8.1 Definition
This test verifies the mobile station behavior when hard handoff fails and:
return on failure is allowed.
return on failure is disallowed.
3-19
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
3.8.2 Traceability (See [4])
2.6.4.2 Traffic Channel Initialization Substate
2.6.6.1.1 Types of Handoff
2.6.6.2.5 Handoff Messages
2.6.6.2.8.2 Hard Handoff With Return On Failure
2.6.6.2.8.2.1 Restoring the Configuration
3.6.6.1 Overview
3.6.6.2.2 Call Processing During Handoff
3.7.3.3.2.31 General Handoff Direction Message
3.7.3.3.2.36 Universal Handoff Direction Message
3.8.3 Call Flow Example(s)
None
3.8.4 Method of Measurement
a. Setup test as shown in Figure A-5.
1. The Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1.
2. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P2 and is called Channel 2.
b. Set the test parameters as shown in Table 3.8.4-1.
Table 3.8.4-1
Parameter Unit Channel 1 Channel 2
Îor/Ioc dB -5 -5
Pilot Ec/Ior dB -7 -7
Traffic Ec/Ior dB -7 <-20 (or none)
Ioc dBm/1.23 MHz -75 -75
Pilot Ec/Io dB -13.2 -12
21
22 23
24
25
26 27
c. Reverse link attenuation should be set to balance the forward and reverse links (approximately 90 dB).
d. Setup a mobile station originated call on Channel 1.
e. Verify user data in both directions.
f. For Test 1, instruct the base station to initiate a handoff to Channel 2 and allow for return on failure. Verify that the base station sends a General Handoff Direction
3-20
C.S0044-0 v1.0
1 2
3 4 5
6
7 8 9
10
11 12 13
14 15
16
17
Message or a Universal Handoff Direction Message with the RETURN_IF_HANDOFF_FAIL = ‘1’.
g. Due to the low traffic gain level on Channel 2 (refer to Table 3.6.4-1), the mobile station will attempt the hard handoff as directed by the base station, but not complete it, and declare a hard handoff failure.
h. Verify the mobile station returns to Channel 1 and verify user data in both directions.
i. For Test 2, instruct the base station to initiate a handoff to Channel 2 and disallow for return on failure. Verify that the base station sends a General Handoff Direction Message or a Universal Handoff Direction Message with RETURN_IF_HANDOFF_FAIL = ‘0’
j. Due to the low traffic gain level on Channel 2 (refer to Table 3.6.4-1), the mobile station will attempt the hard handoff as directed by the base station, but not complete it, and declare a hard handoff failure.
k. Verify the mobile station does not restore to the previous configuration and does not return to Channel 1.
3.9 Search Window Size and Offset (Traffic State)
3.9.1 Definition
A CDMA call is established on sector α of sectored base station 1. Delay is applied to sector ß and base station 2. The level of sector ß is raised sufficiently high to ensure intersector handoff is possible. The level of base station 2 is raised sufficiently high to ensure soft handoff is possible.
18 19 20
21 22 23 24
25 26 27 28
29
30 31
32
33
In section 3.9.3.1, the pilot strength measurements of base station 2 and sector ß are checked against the search window size and search window offset settings for each of the neighbor pilots. If the delay is greater than the search window size for the neighbor pilot then the mobile station shall not send a Pilot Strength Measurement Message.
In section 3.9.3.2, the pilot strength measurements of base station 2 and sector ß are checked against a common search window size (i.e. SRCH_WIN_N). If the delay is greater than the search window size for the neighbor pilot then the mobile station shall not send a Pilot Strength Measurement Message.
3.9.2 Formulas
Pilot_PN_sel = nearest Pilot PN in the neighbor set not to exceed the integer of PILOT_PN_PHASE/64.
Neighbor_Chip_Offset = PILOT_PN_PHASE-(Pilot_PN_sel*64)
Num_Chips = Set_Chip_Offset - Sim_Chip_Offset
Chip_Delay (µs) = sµ300m/
244m x Num_chip 34
35 36 37 38 39
PILOT_PN_PHASE is the pilot PN phase obtained from the mobile station log file in units of chips. PILOT_PN_PHASE is referenced to the zero offset Pilot PN sequence. Pilot_PN_sel selects the closest neighbor’s Pilot PN and the value is subtracted from the PILOT_PN_PHASE to determine the residual chip delay (i.e. Neighbor_Chip_Offset). Set_Chip_Offset is the desired 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 2 3 4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20 21
22
23
due to the time alignment/calibration of the equipment. Chip_Delay is the actual delay in usec the tester should vary with the test equipment (e.g. fader) to achieve the proper Set_Chip_Offset (this includes the inherent delay measured for Sim_Chip_Offset. When properly adjusted, the Set_Chip_Offset should equal to the Neighbor_Chip_Offset.
3.9.3 Traceability (See [4])
2.6.6 Handoff Procedures
2.6.6.2.1 Pilot Search
Table 2.6.6.2.1 Search Window Sizes
Table 2.6.6.2.1-2 Search Window Offset
2.6.6.2.5.2 Processing of Reverse Traffic Channel Handoff Messages
2.7.2.3.2.5 Pilot Strength Measurement Message
2.7.2.3.2.34 Extended Pilot Strength Measurement Message
3.6.6 Handoff Procedures
3.7.2.3.2.1 System Parameters Message
3.7.2.3.2.22 General Neighbor List Message
3.7.2.3.2.34 Universal Neighbor List Message
3.9.4 Call Flow Example(s)
None
3.9.5 Method of Measurement
3.9.5.1 Method of Measurement with NGHBR_SRCH_MODE = ‘10’ (search window size per neighbor
Table 3.9.5-1 Test Cases for NGHBR_SRCH_MODE=’10’ (Traffic State)
Test Case
P2 win size
P2 win offset
P2 Set_Chip_Offset
P3 win size
P3 win offset
P3 Set_Chip_Offset
1 7 0 P3 win/4
+P3 offset
9 0 P3 win/4
+P3 offset
2 7 0 P3 win/2
+P3 offset
9 0 P3 win/2
+P3 offset
3 7 0 P3 win/2
+P3 offset
+10 chips
9 0 P3 win/2
+P3 offset
+10 chips
3-22
C.S0044-0 v1.0
4 7 0 P3 win/2
+P3 offset
7 1 P3 win/2
+P3 offset
5 7 0 P3 win/2 7 4 P3 win/2
1
2
a. Setup test as shown in Figure A-4.
1. The Forward Channel from sector α of base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1.
3 4
5 6
7 8
9
10 11
12
13
2. The Forward Channel from sector ß of base station 1 has an arbitrary pilot PN offset index P2 and is called Channel 2.
3. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P3 and is called Channel 3.
b. Set the test parameters as specified in Table 3.9.5-2.
c. The Reverse Link attenuation should be set to balance the forward and reverse links (approximately 90 dB).
Table 3.9.5-2 Test Parameters for Search Window per Neighbor (Traffic State)
Parameter Unit Channel 1 Channel 2 Channel 3
Îor/Ioc dB 1 -20 -20
Pilot Ec/Ior dB -7 -7 -7
Traffic Ec/Ior dB -7 -7 -7
Ioc dBm/1.23 MHz -75 -75 -75
Pilot Ec/Io dB –9.6 -30.6 -30.6
Note: The Pilot Ec/I0 value is calculated from the parameters set in the table. It is not a settable parameter itself.
14 15 16
17 18
19
d. Set the following values in the General Neighbor List Message (GNLM) or the Universal Neighbor List Message(UNLM):
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
1
Neighbor Setting for P2
NGHBR_PN P2
SRCH_WIN_NGHBR 7 (40 chips)
SRCH_OFFSET_NGHBR 0 (no offset)
2
Neighbor Setting for P3
NGHBR_PN P3
SRCH_WIN_NGHBR 9 (80 chips)
SRCH_OFFSET_NGHBR 0 (no offset)
3
4
5 6 7
8
9
10
11
12
13
14 15 16
17 18 19
20 21 22
e. Determine the inherent delay of the channel simulator (i.e. Sim_Chip_Offset).
f. For Test 1, set the delay on both Channel 2 and on Channel 3 to a Chip_Delay such that Set_Chip_Offset =(SRCH_WIN_NGHBR of P3)/4 + SRCH_OFFSET_NGHBR of P3 (i.e Set_Chip_Offset of P2 is equal to Set_Chip_Offset of P3).
g. Setup a mobile station originated call.
h. Raise the level of Channel 2 to Îor/Ioc = +1 dB without dropping the call.
i. Raise the level of Channel 3 to Îor/Ioc = +1 dB without dropping the call.
j. End the call.
k. Reset the test parameters as specified in Table 3.9.5-2.
l. Verify the following:
1. The mobile station shall generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 2 pilot strength is raised up to the same pilot strength as Channel 1 (Îor/Ioc=1dB).
2. The neighbor_Chip_Offset of P2 calculated from PILOT_PN_PHASE of the Pilot Strength Measurement Message or the Extended Pilot Strength Measurement Message generated in step h shall equal the Set_Chip_Offset of P2.
3. The mobile station shall also generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 3 pilot strength is raised up to the same pilot strength as Channel 1 (Îor/Ioc=1 dB).
3-24
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
4. The neighbor_Chip_Offset of P3 calculated from PILOT_PN_PHASE of the Pilot Strength Measurement Message or the Extended Pilot Strength Measurement Message generated in step i shall equal the Set_Chip_Offset of P3.
m. For Test 2, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that Set_Chip_Offset = (SRCH_WIN_NGHBR of P3)/2 + SRCH_OFFSET_NGHBR of P3.
n. Repeat steps g to k.
o. Verify the following:
1. The mobile station shall not generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 2 pilot strength is raised up to the same pilot strength as Channel 1 (Îor/Ioc=1dB).
2. The mobile station shall generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 3 pilot strength is raised up to the same pilot strength as Channel 1 (Îor/Ioc=1 dB).
3. The neighbor_Chip_Offset of P2 calculated from PILOT_PN_PHASE of the Pilot Strength Measurement Message or the Extended Pilot Strength Measurement Message generated in step i shall equal the Set_Chip_Offset of P3.
p. For Test 3, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that Set_Chip_Offset = (SRCH_WIN_NGHBR of P3)/2 + SRCH_OFFSET_NGHBR of P3 + 10 chips.
q. Repeat steps g to k.
r. Verify that the mobile station does not generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when either the Channel 2 or Channel 3 pilot strength is raised up to the same pilot strength as Channel 1 (Îor/Ioc=1 dB).
s. Set the following values in the General Neighbor List Message or the Universal Neighbor List Message:
Field Value
NGHBR_CONFIG_PN_INCL 1 (for GNLM only)
NGHBR_SRCH_MODE ‘10’
SRCH_OFFSET_INCL 1
29
Neighbor Setting for P2
NGHBR_PN P2
3-25
C.S0044-0 v1.0
SRCH_WIN_NGHBR 7 (40 chips)
SRCH_OFFSET_NGHBR 0 (no offset)
1
Neighbor Setting for P3
NGHBR_PN P3
SRCH_WIN_NGHBR 7 (40 chips)
SRCH_OFFSET_NGHBR 1 (window_size/2)
2
3 4
5
6
7 8 9
10 11 12
13 14 15
16 17
18
t. For Test 4, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that Set_Chip_Offset = (SRCH_WIN_NGHBR of P3)/2 + SRCH_OFFSET_NGHBR of P3.
u. Repeat steps g to k.
v. Verify the following:
1. The mobile station shall not generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 2 pilot strength is raised up to the same pilot strength as Channel 1 (Îor/Ioc=1dB).
2. The mobile station shall generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 3 pilot strength is raised up to the same pilot strength as Channel 1 (Îor/Ioc=1 dB).
3. The neighbor_Chip_Offset of P3 calculated from PILOT_PN_PHASE of the Pilot Strength Measurement Message or the Extended Pilot Strength Measurement Message generated in step i shall equal the Set_Chip_Offset of P3.
w. Set the following values in the General Neighbor List Message or the Universal Neighbor List Message:
Field Value
NGHBR_CONFIG_PN_INCL 1 (for GNLM only)
NGHBR_SRCH_MODE ‘10’
SRCH_OFFSET_INCL 1
19
Neighbor Setting for P2
NGHBR_PN P2
3-26
C.S0044-0 v1.0
SRCH_WIN_NGHBR 7 (40 chips)
SRCH_OFFSET_NGHBR 0 (no offset)
1
Neighbor Setting for P3
NGHBR_PN P3
SRCH_WIN_NGHBR 7 (40 chips)
SRCH_OFFSET_NGHBR 4 (-window_size/2)
2
3 4
5
6
7 8 9
10 11 12
13 14 15
16 17
18
19
x. For Test 5, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that Set_Chip_Offset =(SRCH_WIN_NGHBR of P3)/2.
y. Repeat steps g to k.
z. Verify the following:
1. The mobile station shall generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 2 pilot strength is raised up to the same pilot strength as Channel 1 (Îor/Ioc=1dB).
2. The neighbor_Chip_Offset of P2 calculated from PILOT_PN_PHASE of the Pilot Strength Measurement Message or the Extended Pilot Strength Measurement Message generated in step h shall equal the Set_Chip_Offset of P2.
3. The mobile station shall not generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 3 pilot strength is raised up to the same pilot strength as Channel 1 (Îor/Ioc=1 dB).
3.9.5.2 Method of Measurement with NGHBR_SRCH_MODE = ‘00’ (same search window size for all neighbor)
Table 3.9.5-3 Test Cases for NGHBR_SRCH_MODE=’00’ (Traffic State)
Test Case
Neighbor Message
P2 win size
P2 Set_Chip_Offset
P3 win size
P3 Set_Chip_Offset
1 GNLM 7 SRCH_Win_N/2
7 SRCH_WIN_N/4
2 GNLM 7 SRCH_Win_N/2 + 10 chips
7 SRCH_WIN_N/4 + 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 + 10 chips
7 SRCH_WIN_N/4 + 10 chips
1
2
a. Setup test as shown in A-4
1. The Forward Channel from sector α of base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1.
3 4
5 6
7 8
9
10 11
12
13
2. The Forward Channel from sector ß of base station 1 has an arbitrary pilot PN offset index P2 and is called Channel 2.
3. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P3 and is called Channel 3.
b. Set the test parameters as specified in Table 3.9.5-3.
c. The Reverse Link attenuation should be set to balance the forward and reverse links (approximately 90 dB).
d. Set the following value in the System Parameters Message:
Field Value
SRCH_WIN_N 7 (40 chips)
14
15
16
e. Set the following values in the General Neighbor List Message:
Field Value
NGHBR_SRCH_MODE ‘00’
17
18 19 20
21
22
23
24
25
26
f. For Tests 1 and 3, set the delay on Channel 2 to a Chip_Delay such that Set_Chip_Offset of P2 =SRCH_WIN_N/2, and set the delay on Channel 3 to a Chip_Delay such that Set_Chip_Offset=SRCH_WIN_N/4.
g. Setup a mobile station originated call.
h. Raise the level of Channel 2 to Îor/Ioc = +1 dB without dropping the call.
i. Raise the level of Channel 3 to Îor/Ioc = +1 dB without dropping the call.
j. End the call.
k. Reset the test parameters as specified in Table 3.9.5-3.
l. Verify the following:
3-28
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
1. The mobile station shall generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 2 pilot strength is raised up to the same pilot strength as Channel 1 (Îor/Ioc=1dB).
2. The neighbor_Chip_Offset of P2 calculated from PILOT_PN_PHASE of the Pilot Strength Measurement Message or the Extended Pilot Strength Measurement Message generated in step h shall equal the Set_Chip_Offset of P2.
3. The mobile station shall also generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 3 pilot strength is raised up to the same pilot strength as Channel 1 (Îor/Ioc=1 dB).
4. The neighbor_Chip_Offset of P3 calculated from PILOT_PN_PHASE of the Pilot Strength Measurement Message or the Extended Pilot Strength Measurement Message generated in step i shall equal the Set_Chip_Offset of P3.
m. For Tests 2 and 4, set the delay on Channel 2 to a Chip_Delay such that Set_Chip_Offset of P2 =(SRCH_WIN_N/2)+10 chips, and set the delay on Channel 3 to a Chip_Delay such that Set_Chip_Offset=(SRCH_WIN_N/4)+10 chips.
n. Repeat steps g to k.
o. Verify the following:
1. The mobile station shall not generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 2 pilot strength is raised up to the same pilot strength as Channel 1 (Îor/Ioc=1dB).
2. The mobile station shall generate a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement Message when the Channel 3 pilot strength is raised up to the same pilot strength as Channel 1 (Îor/Ioc=1 dB).
3. The neighbor_Chip_Offset of P2 calculated from PILOT_PN_PHASE of the Pilot Strength Measurement Message or the Extended Pilot Strength Measurement Message generated in step i shall equal the Set_Chip_Offset of P3.
p. Set the following values in the Universal Neighbor List Message:
Field Value
NGHBR_SRCH_MODE ‘00’
SRCH_WIN_N 7 (40 Chips)
29
30 31
q. For Tests 3 and 4 repeat steps b to o using parameter values in step t sent over the Universal Neighbor List Message instead of the General Neighbor List Message.
3-29
C.S0044-0 v1.0
1
2
3
4
5
6
7
8
3.9.6 Minimum Standard
3.9.6.1 For section 3.9.4.1:
Verify steps l, o, r, v and z for Tests 1 to 5.
3.9.6.2 For section 3.9.4.2:
Verify step l for Tests 1 and 3.
Verify step o for Tests 2 and 4.
3.10 Search Window Size and Offset (Idle State)
3.10.1 Definition
The mobile station is operating in idle state and monitoring sector α of base station 1. Delay is applied to both sector ß of base station 1 and base station 2. The level of neighbor pilots are raised sufficiently high to ensure idle handoff is possible.
9 10 11
12 13 14 15
16 17 18 19
20
21
In section 3.9.3.1, the pilot strength measurements of base station 2 and sector ß of base station 1 are checked against the search window size and search window offset settings for each of the neighbor pilots. If the delay is greater than the search window size for the neighbor pilot then the mobile station shall not idle handoff to that neighbor pilot.
In section 3.9.3.2, the pilot strength measurements of base station 2 and sector ß of base station 1are checked against a common search window size (i.e. SRCH_WIN_N). If the delay is greater than the search window size for the neighbor pilot then the mobile station shall not idle handoff to that neighbor pilot.
Formulas
Num_Chips = Set_Chip_Offset - Sim_Chip_Offset
Chip_Delay (µs) = sµ300m/
244m x Num_chip 22
23 24 25 26 27 28
29
30
31
32
33
34
35
36
Set_Chip_Offset is the desired number of chip offsets for a particular test case. Sim_Chip_Offset is the inherent delay for a pilot due to the time alignment/calibration of the equipment. Chip_Delay is the actual delay in usec the tester should vary with the test equipment (e.g. fader) to achieve the proper Set_Chip_Offset (this includes the inherent delay measured for Sim_Chip_Offset. When properly adjusted, the Set_Chip_Offset should equal to the neighbor pilot’s chip offset from zero chip delay.
3.10.2 Traceability (See [4]);
2.6.6 Handoff Procedures
2.6.6.2.1 Pilot Search
Table 2.6.6.2.1 Search Window Sizes
Table 2.6.6.2.1-2 Search Window Offset
3.6.6 Handoff Procedures
3.7.2.3.2. System Parameters Message
3.7.2.3.2.22 General Neighbor List Message
3-30
C.S0044-0 v1.0
1
2
3
4
5 6
7
8
3.7.2.3.2.34 Universal Neighbor List Message
3.10.3 Call Flow Example(s)
None
3.10.4 Method of Measurement
3.10.4.1 Method of Measurement with NGHBR_SRCH_MODE = ‘10’ (search window size per neighbor)
Table 3.10.4-1 Test Cases for NGHBR_SRCH_MODE=’10’ (Idle State)
Test Case
P2 win size
P2 win offset
P2 Set_Chip_Offset
P3 win size
P3 win offset
P3 Set_Chip_Offset
1 7 0 P3 win/4
+P3 offset
9 0 P3 win/4
+P3 offset
2 7 0 P3 win/2
+P3 offset
9 0 P3 win/2
+P3 offset
3 7 0 P3 win/2
+P3 offset
+10 chips
9 0 P3 win/2
+P3 offset
+10 chips
4 7 0 P3 win/2
+P3 offset
7 1 P3 win/2
+P3 offset
5 7 0 P3 win/2 7 4 P3 win/2
9
10
a. Setup test as shown in Figure A-2.
1. The Forward Channel from sector α of base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1.
11 12
13 14
15 16
17 18
19 20
21
2. The Forward Channel from sector ß of base station 1 has an arbitrary pilot PN offset index P2 and is called Channel 2.
3. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P3 and is called Channel 3.
b. The Reverse Link attenuation should be set to balance the forward and reverse links (approximately 90 dB).
c. Set the following values in the General Neighbor List Message (GNLM) or the Universal Neighbor List Message:
3-31
C.S0044-0 v1.0
Field Value
NGHBR_CONFIG_PN_INCL 1 (for GNLM only)
NGHBR_SRCH_MODE ‘10’
SRCH_OFFSET_INCL 1
1
Neighbor Setting for P2
NGHBR_PN P2
SRCH_WIN_NGHBR 7 (40 chips)
SRCH_OFFSET_NGHBR 0 (no offset)
2
Neighbor Setting for P3
NGHBR_PN P3
SRCH_WIN_NGHBR 9 (80 chips)
SRCH_OFFSET_NGHBR 0 (no offset)
3
4
5 6 7
8
9
10
d. Determine the inherent delay of the channel simulator (i.e. Sim_Chip_Offset).
e. For Test 1, set the delay on both Channel 2 and on Channel 3 to a Chip_Delay such that Set_Chip_Offset =(SRCH_WIN_NGHBR of P3)/4 + SRCH_OFFSET_NGHBR of P3 (i.e Set_Chip_Offset of P2 is equal to Set_Chip_Offset of P3).
f. Set the test parameters as specified in Table 3.10.4-1 for state S1 in all 3 channels.
Table 3.10.4-2 Test Parameters for Search Window per Neighbor (Idle State)
Parameter Unit Channel 1 Channel 2 Channel 3
Îor/Ioc dB 1 (S1 and S2) -20 for S1
5 for S2
-20 for S1
5 for S2
Pilot Ec/Ior dB -7 -7 -7
Traffic Ec/Ior dB -7 -7 -7
Ioc dBm/1.23 MHz -75 -75 -75
3-32
C.S0044-0 v1.0
Pilot Ec/Io dB –9.6 for S1
-13.3 for S2
-30.6 for S1
-9.3 for S2
-30.6 for S1
-9.3 for S2
Note: The Pilot Ec/I0 value is calculated from the parameters set in the table. It is not a settable parameter itself.
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
g. Allow the mobile station to monitor Channel 1 while in idle state.
h. Raise the level of Channel 2 to Îor/Ioc = +5 dB (State S2 for Channel 2 in Table 3.10.4-2).
i. Reset the test parameter as specified in Table 3.10.4-2for state S1 in all 3 channels.
j. Raise the level of Channel 3 to Îor/Ioc = +5 dB (State S2 for Channel 3 in Table 3.10.4-2).
k. Verify the following:
1. The mobile station shall perform an idle handoff to Channel 2 in step h.
2. The mobile station shall perform an idle handoff to Channel 3 in step j.
3. For Test 2, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that Set_Chip_Offset = (SRCH_WIN_NGHBR of P3)/2 + SRCH_OFFSET_NGHBR of P3.
l. Repeat steps f to j.
m. Verify the following:
1. The mobile station shall not perform an idle handoff to Channel 2 in step h.
2. The mobile station shall perform an idle handoff to Channel 2 in step j.
3. For Test 3, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that Set_Chip_Offset = (SRCH_WIN_NGHBR of P3)/2 + SRCH_OFFSET_NGHBR of P3 + 10 chips.
n. Repeat steps f to j.
o. Verify that the mobile station does not perform idle handoff(s) in either step h or j.
p. Set the following values in the General Neighbor List Message or the Universal Neighbor List Message:
Field Value
NGHBR_CONFIG_PN_INCL 1 (for GNLM only)
NGHBR_SRCH_MODE ‘10’
SRCH_OFFSET_INCL 1
3-33
C.S0044-0 v1.0
1
Neighbor Setting for P2
NGHBR_PN P2
SRCH_WIN_NGHBR 7 (40 chips)
SRCH_OFFSET_NGHBR 0 (no offset)
2
Neighbor Setting for P3
NGHBR_PN P3
SRCH_WIN_NGHBR 7 (40 chips)
SRCH_OFFSET_NGHBR 1 (window_size/2)
3
4 5
6
7
8
9
10 11
12
q. For Test 4, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that Set_Chip_Offset = (SRCH_WIN_NGHBR of P3)/2 + SRCH_OFFSET_NGHBR of P3.
r. Repeat steps g to k.
s. Verify the following:
1. The mobile station shall not perform an idle handoff to Channel 2 in step h.
2. The mobile station shall perform an idle handoff to Channel 3 in step j.
t. Set the following values in the General Neighbor List Message or the Universal Neighbor List Message:
Field Value
NGHBR_CONFIG_PN_INCL 1 (for GNLM only)
NGHBR_SRCH_MODE ‘10’
SRCH_OFFSET_INCL 1
13
Neighbor Setting for P2
NGHBR_PN P2
SRCH_WIN_NGHBR 7 (40 chips)
SRCH_OFFSET_NGHBR 0 (no offset)
3-34
C.S0044-0 v1.0
1
Neighbor Setting for P3
NGHBR_PN P3
SRCH_WIN_NGHBR 7 (40 chips)
SRCH_OFFSET_NGHBR 4 (-window_size/2)
2
3 4
5
6
7
8
9 10
11
u. For Test 5, set the delay on both Channel 2 and Channel 3 to a Chip_Delay such that Set_Chip_Offset =(SRCH_WIN_NGHBR of P3)/2.
v. Repeat steps g to k.
w. Verify the following:
1. The mobile station shall perform an idle handoff to Channel 2 in step h.
2. The mobile station shall not perform an idle handoff to Channel 3 in step j.
3.10.4.2 Method of Measurement with NGHBR_SRCH_MODE = ‘00’ (same search window size for all neighbor)
Table 3.10.4-3 Test Cases for NGHBR_SRCH_MODE=’00’ (Idle State)
Test Case
Neighbor Message
P2 win size
P2 Set_Chip_Offset
P3 win size
P3 Set_Chip_Offset
1 GNLM 7 SRCH_Win_N/2
7 SRCH_WIN_N/4
2 GNLM 7 SRCH_Win_N/2 + 10 chips
7 SRCH_WIN_N/4 + 10 chips
3 UNLM 7 SRCH_Win_N/2
7 SRCH_WIN_N/4
4 UNLM 7 SRCH_Win_N/2 + 10 chips
7 SRCH_WIN_N/4 + 10 chips
12
13
a. Setup test as shown in Figure A-2.
1. The Forward Channel from sector α of base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1.
14 15
16 17
18 19
2. The Forward Channel from sector ß of base station 1 has an arbitrary pilot PN offset index P2 and is called Channel 2.
3. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P3 and is called Channel 3.
3-35
C.S0044-0 v1.0
1 2
3
4
b. The Reverse Link attenuation should be set to balance the forward and reverse links (approximately 90 dB).
c. Set the following value in the System Parameters Message:
Field Value
SRCH_WIN_N 7 (40 chips)
5
6
7
d. Set the following values in the General Neighbor List Message:
Field Value
NGHBR_SRCH_MODE ‘00’
8
9 10 11
12
13
14 15
16
17 18
19
20
21
22 23 24 25
26
27
28
29
30
e. For Tests 1 and 3, set the delay on Channel 2 to a Chip_Delay such that Set_Chip_Offset of P2 =SRCH_WIN_N/2, and set the delay on Channel 3 to a Chip_Delay such that Set_Chip_Offset=SRCH_WIN_N/4.
f. Set the test parameters as specified in Table 3.10.4-2 for state S1 in all 3 channels.
g. Allow the mobile station to monitor Channel 1 while in idle state.
h. Raise the level of Channel 2 to Îor/Ioc = +5 dB (State S2 for Channel 2 in Table 3.10.4-2).
i. Reset the test parameter as specified in Table 3.10.4-2 for state S1 in all 3 channels.
j. Raise the level of Channel 3 to Îor/Ioc = +5 dB (State S2 for Channel 3 in Table 3.10.4-2).
k. Verify the following:
1. The mobile station shall perform an idle handoff to Channel 2 in step h.
2. The mobile station shall perform an idle handoff to Channel 2 in step j.
3. For Tests 2 and 4, set the delay on Channel 2 to a Chip_Delay such that Set_Chip_Offset of P2 =(SRCH_WIN_N/2)+10 chips, and set the delay on Channel 3 to a Chip_Delay such that Set_Chip_Offset=(SRCH_WIN_N/4)+10 chips.
l. Repeat steps f to j.
m. Verify the following:
1. The mobile station shall not perform an idle handoff to Channel 2 in step h.
2. The mobile station shall perform an idle handoff to Channel 2 in step j.
n. Set the following values in the Universal Neighbor List Message:
3-36
C.S0044-0 v1.0
1
Field Value
NGHBR_SRCH_MODE ‘00’
SRCH_WIN_N 7 (40 Chips)
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
o. For Tests 3 and 4, repeat steps b to n using parameter values in step t sent over the Universal Neighbor List Message instead of the General Neighbor List Message.
3.10.5 Minimum Standard
3.10.5.1 For section 3.9.3.1:
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 Tests 4 to 5 and Tests 21 to 22.
3.10.5.2 For section 3.9.3.2:
Verify step k for Tests 1 and 3.
Verify step n for Tests 2 and 4.
3.11 Channel Assignment into Soft Handoff (CASHO)
3.11.1 Definition
This tests for mobile operation of Channel Assignment into Soft Handoff (CASHO). CASHO allows multiple pilots to be assigned in the Extended Channel Assignment Message from the pilots reported in the Origination Message or Page Response Message.
3.11.2 Traceability (see [4])
3.7.2.3.2.13 Extended System Parameters Message
2.6.3.1.7 Monitoring Pilots
2.6.3.3 Page Response Substate
3.11.3 Call Flow Example(s)
None
3.11.4 Method of Measurement
a. Connect the mobile station as shown in Figure A-5. Ensure both pilot Ec/Io values are well above T_ADD.
b. Allow the mobile station to come to the idle state on one of the base stations.
c. Make a mobile station originated call.
d. Verify both base station pilots are reported in the Origination Message.
3-37
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
33
e. Verify the mobile station receives an Extended Channel Assignment Message assigning both pilots and calls complete normally.
f. Repeat steps c-e for a mobile station terminated call with the exception that in step d the Page Response Message is used instead of the Origination Message.
3.11.5 Minimum Standard
The mobile station shall comply with the requirements in steps d, e and f.
3.12 Traffic Channel Preamble during Hard Handoff Between Frequencies in same band
3.12.1 Definition
The mobile station is transitioned between base stations with different CDMA frequency (channel) assignments in the same band. The Traffic Channel Preamble is a sequence of all-zero frames that is sent by the mobile station on the Reverse Traffic Channel as an aid to Traffic Channel acquisition.
3.12.2 Traceability (See [4])
2.6.6.1.1 Types of Handoff
2.6.6.2.5 Handoff Messages
2.6.6.2.8 CDMA-to-CDMA Hard Handoff
3.6.6.1.1 Types of Handoff
3.6.6.2.2 Call Processing During Handoff
2.1.3.2.4 Reverse Pilot Channel Operation during RTC Preamble (See [2])
2.1.3.6.2.3 Reverse Traffic Channel Preamble (See [2])
3.12.3 Call Flow Example(s)
None
3.12.4 Method of Measurement
a. Setup test as shown in Figure A-2.
1. The Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1.
2. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P2 and is called Channel 2.
3. The AWGN source should be on the frequency of Channel 2. (It is advisable to achieve the maximum possible difference in frequency separation between Channel 1 and Channel 2)
b. Set the test parameters as shown in Table 3.12.4-1.
3-38
C.S0044-0 v1.0
Table 3.12.4-1 1
Parameter Unit Channel 1 Channel 2
Î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
2
3
4
5
6
7 8 9
10
11 12 13
14
15
16
17
18
c. Set reverse link attenuation to balance forward and reverse links (approx. 90 dB).
d. Configure base station 1 and base station 2 for RC1 or RC2.
e. Setup a mobile station originated call on Channel 1.
f. Verify user data in both directions.
g. Initiate handoff from Channel 1 to Channel 2.
h. Verify that the base station 1 sends the General Handoff Direction Message, Universal Handoff Direction Message, or Extended Handoff Direction Message with correct NUM_PREAMBLE value. Verify the Reverse Traffic Channel preamble length.
i. Wait 20 seconds then initiate handoff from Channel 2 to Channel 1.
j. Verify that the base station 2 sends the General Handoff Direction Message, Universal Handoff Direction Message, or Extended Handoff Direction Message correct NUM_PREAMBLE value. Verify the Reverse Traffic Channel preamble length.
k. Configure base station 1 and base station 2 for RC3 or RC5.
l. Repeat steps e through j.
3.12.5 Minimum Standard
The mobile station shall comply with steps h, j, and l.
NUM_PREAMBLE RC1, RC2
Preamble Length in 20 ms Increments: (Total Time)
RC>2
Preamble Length in 1.25 ms 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
3.13 Hopping Pilot Beacon 1
2
3 4
5 6 7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25 26
27 28
29 30 31
32
33
3.13.1 Definition
The mobile station is transitioned between base stations with different CDMA frequency (channel) assignments in the same band.
The Hopping Pilot Beacon is a pilot beacon that changes CDMA Frequency periodically to simulate multiple base stations operating on different frequencies. The transmission of the hopping pilot beacon is discontinuous on any CDMA Channel.
2.6.6.1.1 Types of Handoff
2.6.6.2.5 Handoff Messages
2.6.6.2.8 CDMA-to-CDMA Hard Handoff
2.7.4.25 Capability Information
3.6.1.2 Pilot Channel Operation
3.6.6.2.2 Call Processing During Handoff
3.7.2.3.2.22 General Neighbor List Message
3.7.2.3.2.26 Sync Channel Message
(See [1])
3.1.3.2.5 Hopping Pilot Beacon
None
3.13.4 Method of Measurement
a. Configure base station 1 and 2 for hopping pilot beacon.
b. Setup test as shown in A-2.
1. The Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1.
3. The AWGN source should be on the frequency of Channel 2. (It is advisable to achieve the maximum possible difference in frequency separation between Channel 1 and Channel 2)
c. Set the test parameters as shown in Table 3.13.4-1.
3.13.2 Traceability (See [4])
3.6.6.1.1 Types of Handoff
3.13.3 Call Flow Example(s)
2. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P2 and is called Channel 2.
3-40
C.S0044-0 v1.0
Table 3.13.4-1 1
Parameter Unit Channel 1 Channel 2
Î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
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
d. Set reverse link attenuation to balance forward and reverse links (approx. 90 dB).
e. Setup a mobile station originated call on Channel 1.
f. Verify user data in both directions.
g. Verify hopping pilot beacon settings in the General Neighbor List Message or Extended Neighbor List Message. Initiate handoff from Channel 1 to Channel 2. Verify that the base station 1 sends a General Handoff Direction Message, Universal Handoff Direction Message, or an Extended Handoff Direction Message with proper parameters (refer tables in Annex B).
h. Verify the handoff is successful
i. Verify hopping pilot beacon settings in the General Neighbor List Message or Extended Neighbor List Message. Wait 20 seconds then initiate handoff from Channel 2 to Channel 1. Verify that the base station 2 sends a General Handoff Direction Message, Universal Handoff Direction Message, or an Extended Handoff Direction Message with the proper parameters (refer to tables in Annex B).
3.13.5 Minimum Standard
The mobile station shall comply with steps h and i
3.14 Hard Handoff between Frequencies with Different Radio Configurations
3.14.1 Definition
The mobile station is transitioned between base stations with different CDMA frequency (channel) assignments in the same band and different radio configurations.
3.14.2 Traceability (See [4])
2.6.6.1.1 Types of Handoff
2.6.6.2.5 Handoff Messages
2.6.6.2.8 DMA-to-CDMA Hard Handoff
3-41
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
3.6.6.1.1 Types of Handoff
3.6.6.2.2 Call Processing During Handoff
(See [1])
2.1.3.1 Reverse CDMA Channel Signals
3.1.3.1 Forward CDMA Channel Signals
3.14.3 Call Flow Example(s)
None
3.14.4 Method of Measurement
a. Configure base station 1 for RC3 or RC5. Configure base station 2 for RC1 or RC2.
b. Setup test as shown in A-5.
1. The Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1.
2. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P2 and is called Channel 2.
3. The AWGN source should be on the frequency of Channel 2. (It is advisable to achieve the maximum possible difference in frequency separation between Channel 1 and Channel 2)
c. Set the test parameters as shown in Table 3.14.4-1.
Table 3.14.4-1
Parameter Unit Channel 1 Channel 2
Î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
21
22
23
24
d. Set reverse link attenuation to balance forward and reverse links (approx. 90 dB).
e. Setup a mobile station originated call on Channel 1.
f. Verify user data in both directions.
3-42
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
33
g. Initiate handoff from Channel 1 to Channel 2. Verify that the base station 1 sends a General Handoff Direction Message, or Universal Handoff Direction Message with proper parameters (refer to tables in Annex B)
h. Wait 20 seconds then initiate handoff from Channel 2 to Channel 1. Verify that the base station 2 sends a General Handoff Direction Message, or Universal Handoff Direction Message with the proper parameters (refer to tables in Annex B).
i. Configure base station 1 for RC1 or RC2. Configure base station 2 for RC3 or RC5 and repeat steps b through h.
j. Configure base station 1 for RC3. Configure base station 2 for RC4 and repeat steps b through h.
3.14.5 Minimum Standard
The mobile station shall comply with steps g, h, i and j.
3.15 Handoff on Same Frequency with Different Radio Configurations
3.15.1 Definition
The mobile station is transitioned between base stations with the same CDMA frequency (channel) assignments in the same band and different radio configurations.
When the active set membership before and after the handoff are disjoint, the handoff is performed as a hard handoff; when the active set membership before and after handoff are not disjoint, except for the value of the radio configuration, the handoff is performed as a soft handoff.
3.15.2 Traceability (See [4])
2.6.6.1.1 Types of Handoff
2.6.6.2.5 Handoff Messages
2.6.6.2.8 CDMA-to-CDMA Hard Handoff
3.6.6.1.1 Types of Handoff
3.6.6.2.2 Call Processing During Handoff
(See [1])
2.1.3.1 Reverse CDMA Channel Signals
3.1.3.1 Forward CDMA Channel Signals
3.15.3 Call Flow Example(s)
None
3.15.4 Method of Measurement
a. Configure base station 1 for RC4 or RC5. Configure base station 2 for RC1 or RC2.
b. Setup test as shown in Figure A-2
3-43
C.S0044-0 v1.0
1 2
3 4
5
6
7
8
1. The Forward Channel from base station 1 has an arbitrary pilot PN offset index P1 and is called Channel 1.
2. The Forward Channel from base station 2 has an arbitrary pilot PN offset index P2 and is called Channel 2.
3. The AWGN source should be added to both Channels.
c. Set the test parameters as shown in Table 3.15.4-1.
Table 3.15.4-1 Hard Handoff Test Parameters
Parameter Unit Channel 1 Channel 2
Î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
9
10
11
12
13 14 15
16 17 18
19 20
21 22
23 24 25 26
27
d. Set reverse link attenuation to balance forward and reverse links (approx. 90 dB).
e. Setup a mobile station originated call on Channel 1.
f. Verify user data in both directions.
g. Initiate handoff from Channel 1 to Channel 2. Verify that the base station 1 sends a General Handoff Direction Message, or Universal Handoff Direction Message with proper parameters (refer to tables in Annex B)
h. Wait 20 seconds then initiate handoff from Channel 2 to Channel 1. Verify that the base station 2 sends a General Handoff Direction Message, or Universal Handoff Direction Message with the proper parameters (refer to tables in Annex B).
i. Configure base station 1 for RC1 or RC2. Configure base station 2 for RC4 or RC5 and repeat steps b through h.
j. Configure base station 1 for RC3. Configure base station 2 for RC4 and repeat steps b through h.
k. Repeat steps a through j but with the following exception: Only base station 1 is used for this test. The handoff messages are sent from base station 1 without changing the active set, but changing the radio configuration. Thus the handoff messages simply assign a new radio configuration from the same base station.
l. Verify that the handoff is performed as a soft handoff.
3-44
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
3.15.5 Minimum Standard
The mobile station shall comply with steps g, h, i, j, and k.
3.16 Hard Handoff while in the Waiting for Mobile Station Answer Substate
3.16.1 Definition
This test verifies that if a hard handoff occurs while the mobile station is in the Waiting for Mobile Station Answer Substate, the hard handoff will be completed successfully and the mobile station shall enter the Conversation Substate on the new channel.
3.16.2 Traceability (see [4] unless otherwise noted)
2.6.4 Mobile Station Control on the Traffic Channel State
2.6.4.3.2 Waiting for Mobile Station Answer Substate
2.6.4.4 Conversation Substate
2.6.6.2.5.1 Processing of the Forward Traffic Channel Handoff Messages
2.6.6.2.8 CDMA to CDMA Hard Handoff
3.6.4.3.1 Waiting for Order Substate
3.6.6.2.2 Call Processing during Handoff
3.7.3.3.2.17 Extended Handoff Direction Message
3.7.3.3.2.31 General Handoff Direction Message
3.7.3.3.2.36 Universal Handoff Direction Message
Table D-1 Time Constants
3.1 Standard Service Option Number Assignments (see [17])
3.2 Proprietary Service Option Number Assignments (see [17])
3.16.3 Call Flow Example(s)
None
3.16.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-5 and set the test parameters as specified in Table 3.2.4-1.
1. Base station 1 is a CDMA base station with frequency F1, PN offset P1 and is referred to as Channel 1.
2. Base station 2 is a CDMA base station with frequency F2, PN offset P2 and is referred to as Channel 2.
b. Ensure the mobile station is operating in the Idle State on Channel 1.
c. Page the mobile station with a supported service option.
3-45
C.S0044-0 v1.0
1 2
3
d. After receiving the Page Response Message, instruct the base station to send an Extended Channel Assignment Message with the following parameters:
Field Value
ASSIGN_MODE '000' or '100'
BYPASS_ALERT_ANSWER '0'
4
5 6 7 8
9 10 11 12 13
14 15
16 17
18
19 20
21 22
23
24
25
26
27 28 29 30 31 32 33
e. While the mobile station is in the Waiting for Mobile Station Answer Substate (i.e. ringing), instruct the base station to send an Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message directing the mobile station to Channel 2.
f. If the base station sends a second (Extended) Alert with Information Message from base station 2, verify the mobile station resets T53m (65 seconds) and the information record(s) included override the first (Extended) Alert with Information Message. The mobile station should not prompt the user to answer the call twice or indicate a “missed call.”
g. After the hard handoff has been completed and before T53m (65 seconds), has expired direct the user to answer the call.
h. Verify the mobile station enters the Conversation Substate and user traffic is present in both directions (i.e. audio).
i. End the call.
j. Repeat steps b through j using different service options and radio configurations supported by the mobile station and base station.
k. Repeat steps b through j, changing Channel 2 to a band class that is different from Channel 1 but is supported by the mobile station.
3.16.5 Minimum Standard
The mobile station shall comply with steps h and j.
3.17 Inter-Frequency Hard Handoff (CDMA to CDMA)
3.17.1 Definition
In an Inter-Frequency Hard Handoff test (also known as the Mobile Assisted Hard Handoff test), when the mobile station is directed by the base station to perform a search on a Candidate Frequency, the mobile station will search for a pilot in the Candidate Frequency Neighbor Set. The mobile station will report back to the base station any pilot detected in the Candidate Frequency Neighbor Set with a pilot Ec/Io above the value defined by CF_T_ADD. The base station should then direct the mobile station to the Candidate Frequency and completes the hard handoff.
3-46
C.S0044-0 v1.0
1
2
3
4
5
6
7
8
9
10
11 12
13 14 15
16
3.17.2 Traceability (see [4])
2.6.6.2.5 Handoff Messages
2.6.6.2.8 CDMA-to-CDMA Hard Handoff
2.7.2.3.2.20 Candidate Frequency Search Report Message
3.6.6.2.2 Call Processing During Handoff
3.7.7.3.3.2.27 Candidate Frequency Search Request Message
3.17.3 Call Flow Example(s)
None
3.17.4 Method of Measurement
a. Setup test as shown in Figure A-5.
1. The Forward Channel from base station 1 has a CDMA frequency assignment F1 (any valid value), an arbitrary pilot PN offset index P1 and is called Channel 1.
2. The Forward Channel from base station 2 has a CDMA frequency assignment F2 (any valid value other than f1 in the same band class), an arbitrary pilot PN offset index P2 and is called Channel 2.
Parameter Unit Channel 1 Channel 2
Îor/Ioc dB 2.9 2.9
orc
IEPilot
dB -7 -7
orc
IE Traffic
dB -7 N/A
Ioc dBm/1.23 MHz -75
0c
IEPilot
dB -11.0 -11.0
17
18
19
20 21
22
b. Reverse Link attenuation should be set to balance the forward and reverse links.
c. Set up a mobile station originated call on Channel 1.
d. Send from base station 1 a Candidate Frequency Search Request Message to the mobile station to set an explicit action time with the following parameters:
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
1
2 3
4 5 6
7
8
9
10
11
12 13 14 15 16 17 18
e. Verify that the mobile station responds with a Candidate Frequency Search Report Message.
f. Verify that base station 1 sends a General Handoff Direction Message, an Extended Handoff Direction Message or a Universal Handoff Direction Message to initiate handoff from base station 1 to base station 2.
g. Verify user data in both directions.
3.17.5 Minimum Standard
The mobile station shall comply with steps e and g.
3.18 Inter-Frequency Hard Handoff (CDMA to Analog)
3.18.1 Definition
In an Inter-Frequency Hard Handoff test (also known as the Mobile Assisted Hard Handoff test), when the mobile station is directed by the base station to perform a search on a Candidate Frequency, the mobile station will search for an analog channel in the Candidate Frequency Analog Search Set and shall measure the mean input power on the analog frequency. The mobile station will report back to the base station the signal strength of the analog channel searched. The base station should then direct the mobile station to the Analog Channel and completes the hard handoff.
3-48
C.S0044-0 v1.0
1
2
3
4
5
6
7
8
9
10
11
12 13
14 15
16
17
18
3.18.2 Traceability (see [4])
2.6.6.2.5 Handoff Messages
2.6.6.2.8 CDMA-to-CDMA Hard Handoff
2.6.6.10.2 Candidate Frequency Analog Search Set
2.7.2.3.2.21 Candidate Frequency Search Report Message
3.6.6.2.2 Call Processing During Handoff
3.7.7.3.3.2.27 Candidate Frequency Search Request Message
3.18.3 Call Flow Example(s)
None
3.18.4 Method of Measurement
a. Setup test as shown in Figure A-5.
1. The Forward Channel from base station 1 has a CDMA frequency assignment F1 (any valid value), an arbitrary pilot PN offset index P1 and is called Channel 1.
2. The Forward Channel from base station 2 uses an analog frequency called Channel 2.
b. Set the test parameters as specified in Table 3.15.4-1 and Table 3.18.4-2
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
Ioc dBm/1.23 MHz -75
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
2
3 4
5
c. Reverse Link attenuation should be set to balance the forward and reverse links.
d. Set up a mobile station originated voice call on Channel 1.
e. Send from base station 1 a Candidate Frequency Search Request Message to the mobile station to set an explicit action time with the following parameters:
Field Value (Decimal)
USE_TIME 1 (use action time)
SEARCH_TYPE 1 (single search)
SEARCH_MODE 1 (search for analog channels)
SF_TOTAL_EC_THRESH 31 (disabled)
SF_TOTAL_EC_IO_THRESH 31 (disabled)
NUM_ANALOG_FREQS 1
ANALOG_FREQ Channel 2
6
7 8
9 10
11
12
13
14
15
16 17
18
19
20
21
22
f. Verify that the mobile station responds with a Candidate Frequency Search Report Message.
g. Verify that base station 1 sends an Analog Handoff Direction Message to initiate handoff from base station 1 to base station 2.
h. Verify audio in both directions.
3.18.5 Minimum Standard
The mobile stations shall comply with steps f and h.
3.19 Hard Handoff between Frequencies with Different Protocol Revisions
3.19.1 Definition
This test verifies the mobile station is able perform a hard handoff between base stations supporting using different protocol revisions (P_REV).
3.19.2 Traceability (See [4])
2.6.6.1.1 Types of Handoff
2.6.6.2.5 Handoff Messages
2.6.6.2.8 CDMA-to-CDMA Hard Handoff
3.6.6.1.1 Types of Handoff
3-50
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
3.6.6.2.2 Call Processing During Handoff
3.7.3.3.2.17 Extended Handoff Direction Message
3.7.3.3.2.31 General Handoff Direction Message
3.7.3.3.2.36 Universal Handoff Direction Message
3.19.3 Call Flow Example(s)
None
3.19.4 Method of Measurement
a. Configure base station one and base station two with different protocol revisions.
b. Verify the mobile station supports the protocol revisions on each base station.
c. Setup test as shown in Figure A-5.
1. The Forward Channel from base station one has an arbitrary pilot PN offset index P1 and is called Channel 1.
2. The Forward Channel from base station two has an arbitrary pilot PN offset index P2 and is called Channel 2.
3. The AWGN source should be on the frequency of Channel 2. (It is advisable to achieve the maximum possible difference in frequency separation between Channel 1 and Channel 2)
d. Set the test parameters as shown in Table 3.19.4-1.
Table 3.19.4-1 Hard Handoff Test Parameters
Parameter Unit Channel 1 Channel 2
Î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
21
22
23
24
25
e. Set reverse link attenuation to balance forward and reverse links (approx. 90 dB).
f. Setup a mobile station originated call on Channel 1.
g. Verify user traffic in both directions.
h. Initiate handoff from Channel 1 to Channel 2.
3-51
C.S0044-0 v1.0
1 2 3
4
5
6
i. Verify that the base station 1 sends General Handoff Direction Message, Universal Handoff Direction Message, or Extended Handoff Direction Message with the P_REV field value equal to the P_REV of base station two.
j. Verify the handoff is successful and user traffic is present in both directions.
3.19.5 Minimum Standard
The mobile station shall comply with step j.
3-52
C.S0044-0 v1.0
4 POWER CONTROL 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
4.1 Forward Traffic Channel Power Control
4.1.1 Definition
This test verifies that the mobile station reports frame error rate statistics at specified intervals if the base station enables periodic reporting, and verifies that the mobile station reports frame error rate statistics when the frame error rate reaches a specified threshold if the base station enables threshold reporting.
4.1.2 Traceability: (See [4])
2.6.4.1.1 Forward Traffic Channel Power Control
2.7.2.3.2.6 Power Measurement Report Message
3.6.4.1.1 Forward Traffic Channel Power Control
3.7.3.3.2.10 Power Control Parameters Message
Applicability: Forward Link: RC 1 through RC 5; Reverse Link: RC 1 through RC 4
4.1.3 Call Flow Example(s)
None
4.1.4 Method of Measurement
a. Setup test as shown in Annex A Figure A-6.
b. Setup a mobile station originated call using the test parameters for Test 1 as specified in Table 4.1.4-1.
c. Set the AWGN source power so the forward link average FER is between 0.5 and 1.0%.
d. Instruct the base station to send the Power Control Parameters Message to enable the threshold reporting and disable the periodic reporting according to the base station manufacturer's forward power control algorithm.
PWR_THRESH_ENABLE ‘1’ (Enable threshold reporting)
PWR_PERIOD_ENABLE ‘0’ (Disable periodic reporting)
26
27 28
29 30
31 32
e. Using Attenuator 1, alternately increase and decrease AWGN source output power by 5 dB from the original power set in step c.
f. Monitor forward traffic channel Ec/Ior and ensure power increases and decreases corresponding to noise power from the AWGN source.
g. Monitor forward link FER at the mobile station.
4-1
C.S0044-0 v1.0
1
.1.4 12 Table 4 - Test Parameters for Forward Power Control Tests
Test Number
Forward RC
Reverse RC
Threshold/Periodic
Service Option Channels Forward Link Power [dBm/1.23 MHz]
1 1 1 Threshold 2, 54, 55, or 32798
F-FCH -65
2 1 1 Periodic 2, 54, 55, or 32798
F-FCH -65
3 2 2 Threshold 9, 54, 55, or 32799
F-FCH -62
4 2 2 Periodic 9, 54, 55, or 32799
F-FCH -62
5 3 3 Threshold 54, or 55 F-FCH -65
6 3 3 Periodic 54, or 55 F-FCH -65
7 3 3 Threshold 54, or 55 F-DCCH -65
8 3 3 Periodic 54, or 55 F-DCCH -65
9 4 3 Threshold 54, or 55 F-FCH -65
10 4 3 Periodic 54, or 55 F-FCH -65
11 4 3 Threshold 54, or 55 F-DCCH -65
12 4 3 Periodic 54, or 55 F-DCCH -65
13 5 4 Threshold 54, or 55 F-FCH -62
14 5 4 Periodic 54, or 55 F-FCH -62
15 5 4 Threshold 54, or 55 F-DCCH -62
16 5 4 Periodic 54, or 55 F-DCCH -62
17 3 3 N/A 54, or 55 F-FCH/F-SCH -65
18 4 3 N/A 54, or 55 F-FCH/F-SCH -65
19 5 4 N/A 54, or 55 F-FCH/F-SCH -62
20 3 3 N/A 54, or 55 F-DCCH/F-SCH
-65
21 4 3 N/A 54, or 55 F-DCCH/F-SCH
-65
4-2
C.S0044-0 v1.0
SCH
22 5 4 N/A 54, or 55 F-DCCH/F-SCH
-62
Note: All tests should be performed at full data rate or at a variable rate. Tests involving the Forward Supplemental Channels should only include 1 Forward Supplemental Channel.
1 2
3
4 5
6
7 8
9 10 11
12
h. Verify MS sends the Power Measurement Report Message when the bad frames received by the mobile station reaches the specified threshold.
i. End the call.
j. Setup a mobile station originated call using the test parameters for Test 2 as specified in Table 4.1.4-1.
k. Instruct the base station to send the Power Control Parameters Message to enable the periodic reporting and disable the threshold reporting according to the base station manufacturer's forward power control algorithm.
PWR_THRESH_ENABLE ‘0’ (Disable threshold reporting)
PWR_PERIOD_ENABLE ‘1’ (Enable periodic reporting)
13
14
15 16
17
18 19
20 21
22 23 24
25
26 27
28
29
30
l. Repeat the steps e through g.
m. Verify the mobile station sends the Power Measurement Report Message when the total frames received by the mobile station reach the specified report period.
n. End the call.
o. Repeat steps b through n except for using the test parameters for Tests 3 to 16 as specified in Table 4.1.4-1.
p. Repeat steps b through c except for using the test parameters for Test 17 to Test 22 as specified in Table 4.1.4-1.
q. Instruct the base station to send the Extended Supplemental Channel Assignment Message including a Forward Supplemental Channel assignment and setting FOR_SCH_FER_REP to ‘1’.
r. Repeat the steps e through g.
s. Verify the mobile station sends the Power Measurement Report Message at the end of the burst.
t. End the call.
4.1.5 Minimum Standard
The mobile station shall comply with steps h, l, m, o, p, r and s.
4-3
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
33
34
35
36
The base station should alternately increase and decrease the forward traffic channel power according to the base station manufacturer's forward power control algorithm. Forward link FER measured at the mobile station should be within the target value and the mobile station shall report frame error rate statistics. There shall not be any dropped calls.
4.2 Fast Forward Power Control (FFPC)
4.2.1 FFPC using different values of FPC_MODE (FPC_MODE = ‘000’, ‘001’, ‘010’)
4.2.1.1 Definition
The mobile station accomplishes fast forward power control by transmitting the Reverse Power Control Subchannel to the base station on the Reverse Pilot Channel. The mobile station determines the information to be sent to the base station through inner and outer loop estimations. In outer loop estimation, the mobile station adjusts the Eb/Nt setpoint to the Eb/Nt value necessary to achieve the target FER on the Forward Traffic Channel. In inner loop estimation, the mobile station compares the received Eb/Nt to the setpoint and determines the value of the power control bit to be sent to the base station. There are 16 Power Control Groups every 20 ms on the Reverse Power Control Subchannel. This test verifies that the mobile station can process the various parameters in the Extended Channel Assignment Message, the Extended Supplemental Channel Assignment Message, and the Service Connect Message.
4.2.1.2 Traceability: (See [1] )
2.1.3.1.11 Reverse Power Control Subchannel
(See [4] )
2.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages
3.6.6.2.2.12 Processing of Extended Supplemental Channel Assignment Message
3.7.3.3.2.37 Extended Supplemental Channel Assignment Message
2.6.2.4 Mobile Station Order and Message Processing Operation
2.6.3.3 Page Response Substate
2.6.3.5 Mobile Station Origination Attempt Substate
3.6.3.3 Response to Page Response Message
3.6.3.5 Response to Origination Message
3.7.2.3.2.21 Extended Channel Assignment Message
2.6.4.1.2 Service Configuration and Negotiation
2.6.4.1.2.2 Service Subfunctions
3.7.3.3.2.20 Service Connect Message
3.7.5 Information Records
3.7.5.7 Service Configuration
3.7.5.20 Non negotiable System Configuration
4-4
C.S0044-0 v1.0
1
2
3
4
Applicability: Forward Link: RC 1 through RC 5; Reverse Link: RC 1 through RC 4
FPC_MODE Information
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
5
6
7
8
4.2.1.4.1 9
10
able 4.2.1-211
.2.112
4.2.1.3 Call Flow Example(s)
None
4.2.1.4 Method of Measurement
FPC_MODE ‘000’; F-FCH Only
a. Connect base station and mobile station as shown in Annex A Figure A-6.
b. Set power levels as stated in T :
Table 4 -2 Test Parameters for Fast Forward Power Control
Parameter Unit Value
orc
IEPilot
dB
-7
Ioc dBm/1.23 MHz -75
Ior/Ioc dB 10
13
14 15
16 17
c. Setup a mobile station originated call using Service Option 55 (Loopback Service Option) or Service Option 54 (Markov Service Option).
d. Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:
4-5
C.S0044-0 v1.0
1
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
4
5 6 7
8 9
10
11 12
13
14 15
16 17
4.2.1.4.2 18
19
.2.1-320
21
e. Ensure the base station sends the Service Connect Message with FPC_INCL set to ‘0’.
f. Monitor the forward link FER at the mobile station.
g. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source.
h. Monitor traffic channel Ec/Ior and ensure the power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.
i. Verify that the forward link FER on the FCH remains at approximately the target value (i.e. 1%).
j. End the call at the mobile station.
k. Repeat steps a through j above except that FOR_RC is set to RC4 and REV_RC is set to RC3 in step d.
l. Repeat steps a through j above except that FOR_RC is set to RC5 and REV_RC is set to RC4 in step d .
FPC_MODE ‘000’; F-DCCH only
a. Connect base station and mobile station as shown in Annex A Figure A-6.
b. Set power levels as stated in Table 4 :
Table 4.2.1-3 Test Parameters for Fast Forward Power Control
Parameter Unit Value
orc
IEPilot
dB
-7
Ioc dBm/1.23 MHz -75
4-6
C.S0044-0 v1.0
Ior/Ioc dB 10
1
2 3
4 5
6
c. Setup a mobile station originated call using Service Option 32 (Test Data Service Option).
d. Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:
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)
7
8
9
10 11 12
13 14 15
16 17
18
19 20
21 22
4.2.1.4.3 23
24
e. Ensure the base station sends the Service Connect Message with FPC_INCL set to ‘0’.
f. Monitor the forward link FER at the mobile station.
g. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source.
h. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.
i. Verify that the forward link FER on DCCH remains at approximately the target value (1%).
j. End the call at the mobile station.
k. Repeat steps a through i above except for setting FOR_RC to RC4 and REV_RC to RC3 in step d.
l. Repeat steps a through i above except for setting FOR_RC to RC5 and REV_RC to RC4 in step d.
FPC_MODE ‘001’; F-FCH and F-SCH
a. Connect base station and mobile station as shown in Annex A Figure A-6.
4-7
C.S0044-0 v1.0
b. Set power levels as stated in T :
able 4.2.1-41 2
3 Table 4.2.1-4 Test Parameters for Fast Forward Power Control
Parameter Unit Value
orc
IEPilot
dB
-7
Ioc dBm/1.23 MHz -75
Ior/Ioc dB 10
4
5 6
7 8
9
c. Setup a mobile station originated call using Service Option 32 (Test Data Service Option).
d. Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:
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)
10
11 12
13
e. Instruct the base station to send the Service Connect Message with the parameters set as follows:
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 2 3
4
f. Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel by using the Extended Supplemental Channel Assignment Message and set the power control related fields as stated in follows:
FPC_INCL = ‘1’ FPC_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%)
5
6 7
8 9
10
11 12 13
14 15
16
17 18
19 20
4.2.1.4.4 21 22
23
able .2.1-524
25
g. Monitor the forward link FER on FCH and SCH (during the burst assignment) at the mobile station.
h. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source.
i. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.
j. Verify that the forward link FERs on FCH and SCH (during SCH assignment) remain at approximately the target values.
k. End the call at the mobile station.
l. Repeat steps a through k above except that FOR_RC is set to RC4 and REV_RC is set to RC3 in step d.
m. Repeat steps h through k above except that FOR_RC is set to RC5 and REV_RC is set to RC4 in step d.
FPC_MODE ‘000’ without F-SCH Active and FPC_MODE ‘001’ with F-SCH Active; F-DCCH and F-SCH
a. Connect base station and mobile station as shown in Annex A Figure A-6.
b. Set power levels as stated in T 4 :
Table 4.2.1-5 Test Parameters for Fast Forward Power Control
Parameter Unit Value
4-9
C.S0044-0 v1.0
orc
IEPilot
dB
-7
Ioc dBm/1.23 MHz -75
Ior/Ioc dB 10
1
2 3
4 5
6
c. Setup a mobile station originated call using Service Option 32 (Test Data Service Option).
d. Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:
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)
7
8 9
10 11 12
13
e. Instruct the base station to send the Service Connect Message with FPC_INCL set to ‘0’.
f. Instruct the base station to download the SCH configuration and assign a Forward Supplemental Channel using the Extended Supplemental Channel Assignment Message and set the power control related information as follows:
FPC_INCL = ‘1’ FPC_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%)
14
4-10
C.S0044-0 v1.0
g. Monitor the forward link FER on both F-DCCH and F-SCH (during SCH assignment) at the mobile station.
1 2
3 4 5
6 7 8
9 10
11
12 13
14 15
4.2.1.4.5 16 17
18
.2.1-619
20
h. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source.
i. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.
j. Verify that the forward link FER on DCCH and SCH (during SCH assignment) remains at approximately the target value.
k. End the call at the mobile station.
l. Repeat steps a through k above except that FOR_RC is set to RC4 and REV_RC is set to RC3 in step d.
m. Repeat steps a through k above except that the FOR_RC is set to RC5 and REV_RC is set to RC4 in step d.
FPC_MODE ‘000’ without F-SCH Active and FPC_MODE ‘010’ with F-SCH Active; F-FCH and F-SCH
a. Connect base station and mobile station as shown in Annex A Figure A-6.
b. Set power levels as stated in Table 4 :
Table 4.2.1-6 Test Parameters for Fast Forward Power Control
Parameter Unit Value
orc
IEPilot
dB
-7
Ioc dBm/1.23 MHz -75
Ior/Ioc dB 10
21
22 23
24 25
26
c. Setup a mobile station originated call using Service Option 32 (Test Data Service Option).
d. Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:
ASSIGN_MODE = ‘100’ GRANTED_MODE = ‘10’
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)
4-11
C.S0044-0 v1.0
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)
1
2 3
4 5 6
7
e. Instruct the base station to send the Service Connect Message with FPC_INCL set to ‘0’.
f. Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel by using the Extended Supplemental Channel Assignment Message with power control related parameters set as follows:
FPC_INCL = ‘1’ FPC_SCH_INIT_SETPT = ‘01000000’ (8 dB)
FPC_MODE_SCH = ‘010’ 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%)
8 9
10 11 12
13 14 15
16 17
18
19 20
21 22
g. Monitor the forward link FER on both FCH and SCH (during the SCH assignment) at the mobile station.
h. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source.
i. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.
j. Verify that the forward link FERs on FCH and SCH (during SCH assignment) remain at approximately the target values.
k. End the call at the mobile station.
l. Repeat steps a through k above except for step d to set FOR_RC to RC4 and REV_RC to RC3.
m. Repeat steps a through k above except for step d to set FOR_RC to RC5 and REV_RC to RC4.
4-12
C.S0044-0 v1.0
4.2.1.4.6 1
2
.2.1-73
4
FPC_MODE ‘010’; F-DCCH and F-SCH
a. Connect base station and mobile station as shown in Annex A Figure A-6.
b. Set power levels as stated in Table 4 :
Table 4.2.1-7 Test Parameters for Fast Forward Power Control
Parameter Unit Value
orc
IEPilot
dB
-7
Ioc dBm/1.23 MHz -75
Ior/Ioc dB 10
5
6 7
8 9
10
c. Setup a mobile station originated call using Service Option 32 (Test Data Service Option).
d. Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows.
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)
11
12 13
14
e. Instruct the base station to send the Service Connect Message with the parameters set as follows:
FPC_INCL = ‘1’ FPC_OLPC_FCH_INCL = ‘0’
FPC_PRI_CHAN = ‘1’ GATING_RATE_INCL = ‘0’
FPC_MODE = ‘010’
15
4-13
C.S0044-0 v1.0
1 2 3 4
f. Instruct the base station to send SCH configuration and assign a Forward Supplemental Channel by using the Extended Supplemental Channel Assignment Message with power control related parameters set as follows:
FPC_INCL = ‘1’ FPC_SCH_INIT_SETPT = ‘01000000’ (8 dB)
FPC_MODE_SCH = ‘010’ 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%)
5
6 7
8 9
10
11 12 13
14 15
16
17 18
19 20
21
22
23
24
25
26
27
28
g. Monitor forward link FER on both F-DCCH and F-SCH (during SCH burst assignment) at the mobile station.
h. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source.
i. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.
j. Verify that the forward link FERs on the DCCH and SCH (during SCH assignment) remain at approximately the target values.
k. End the call at the mobile station.
l. Repeat steps a through k above except for step d to set FOR_RC to RC4 and REV_RC to 3.
m. Repeat steps a through k above except for step d to set FOR_RC to RC5 and REV_RC to 4.
4.2.1.5 Minimum Standard
4.2.1.5.1 FPC_MODE ‘000’; F-FCH Only
The mobile station shall comply with step i, k, and l.
4.2.1.5.2 FPC_MODE ‘000’; F-DCCH only
The mobile station shall comply with step i, k, and l.
4.2.1.5.3 FPC_MODE ‘001’; F-FCH and F-SCH
The mobile station shall comply with step j, l, and m.
4.2.1.5.4 FPC_MODE ‘000’ without F-SCH Active and FPC_MODE ‘001’ with F-SCH Active; F-
4-14
C.S0044-0 v1.0
DCCH and F-SCH 1
2
4.2.1.5.5 FPC_MODE ‘000’ without F-SCH Active and FPC_MODE ‘010’ with F-SCH Active; F-3 FCH and F-SCH 4
5
6
7
8
9
10
11 12
13
2.1.3.1.10 Reverse Power Control Subchannel 14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
The mobile station shall comply with step j, l, and m.
The mobile station shall comply with step j, l, and m.
4.2.1.5.6 FPC_MODE ‘010’; F-DCCH and F-SCH
The mobile station shall comply with step j, l, and m.
4.2.2 Outer Loop Report
4.2.2.1 Definition
This test verifies that the mobile station shall send the Outer Loop Report Message if the Outer Loop Report Request Order is received.
4.2.2.2 Traceability: (See [1] )
(See [4] )
2.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages
3.6.6.2.212 Processing of Extended Supplemental Channel Assignment Message
3.7.3.3.2.37 Extended Supplemental Channel Assignment Message
2.6.2.4 Mobile Station Order and Message Processing Operation
2.6.3.3 Page Response Substate
2.6.3.5 Mobile Station Origination Attempt Substate
3.6.3.3 Response to Page Response Message
3.6.3.5 Response to Origination Message
3.7.2.3.2.21 Extended Channel Assignment Message
2.6.4.1.2 Service Configuration and Negotiation
2.6.4.1.2.2 Service Subfunctions
3.7.3.3.2.20 Service Connect Message
3.7.5 Information Records
3.7.5.7 Service Configuration
3.7.5.20 Non negotiable System Configuration
2.6.4.1.1 Forward Traffic Channel Power Control
2.7.2.3.2.22 Outer Loop Report Message
4-15
C.S0044-0 v1.0
3.7.3.3.2.25 Power Control Message 1
2
3
4
5
4.2.2.4 6
7
.2.2-18
.2.29
Applicability: Forward Link: RC 1 through RC 5; Reverse Link: RC 1 through RC 4
4.2.2.3 Call Flow Example(s)
None
Method of Measurement
a. Connect base station and mobile station as shown in Annex A Figure A-6.
b. Set power levels as stated in Table 4 :
Table 4 -1 Test Parameters for Fast Forward Power Control
Parameter Unit Value
orc
IEPilot
dB -7
Ioc dBm/1.23 MHz -75
Ior/Ioc dB 10
10
11 12
13 14 15
c. Setup a mobile station originated call using Service Option 32 (Test Data Service Option).
d. Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:
ASSIGN_MODE = ‘100’ GRANTED_MODE = ‘10’
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)
FOR_RC = ‘00011’ (RC 3)
16
17 18
e. Instruct the base station to send the Service Connect Message with FPC_INCL set to ‘0’.
4-16
C.S0044-0 v1.0
1 2 3
4
f. Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel by using the Extended Supplemental Channel Assignment Message with power control related parameters set as follows:
FPC_INCL = ‘1’ FPC_SCH_INIT_SETPT = ‘01000000’ (8 dB)
FPC_MODE_SCH = ‘000’ 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%)
5
6 7
8 9
10
11 12 13
14 15
16 17 18 19
20
21
22 23
24
g. Monitor the forward link FER on both FCH and SCH (during the SCH assignment) at the mobile station.
h. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source.
i. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.
j. During the F-SCH assignment, instruct the base station to send Outer Loop Report Request Order.
k. Verify the mobile station sends the Outer Loop Report Message and this message contains FPC_FCH_CURR_SETPT and FPC_SCH_CURR_SETPT. The FPC current setpoint reported by the mobile station shall be in the range of the minimum setpoint and the maximum setpoint
l. End the call at the mobile station.
m. Repeat steps a through l above except for the following steps:
n. Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:
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)
4-17
C.S0044-0 v1.0
‘00010000’ (2 dB)
FPC_DCCH_MAX_SETPT = ‘10000000’ (16 dB)
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
2.6.2.4 Mobile Station Order and Message Processing Operation 30
31
32
33
34
o. Monitor the forward link FER on both DCCH and SCH (during the SCH assignment at the mobile station.
p. Verify the mobile station sends the Outer Loop Report Message and this message contains FPC_DCCH_CURR_SETPT and FPC_SCH_CURR_SETPT. The FPC current setpoint reported by the mobile station shall be in the range of the minimum setpoint and the maximum setpoint
4.2.2.5 Minimum Standard
The mobile station shall comply with steps k, m, and p.
4.2.3 Fast Forward Power Control (FFPC) in Soft Handoff
4.2.3.1 Definition
The mobile station accomplishes fast forward power control by transmitting the Reverse Power Control Subchannel to the base station on the Reverse Pilot Channel. The mobile station determines the information to send to the base station through inner and outer closed loop estimations. In outer loop estimation, the mobile station adjusts the Eb/Nt setpoints to the Eb/Nt value necessary to achieve the target FER on the Forward Traffic Channel. In inner loop estimation, the mobile station compares the received Eb/Nt to the setpoint and determines the value of the power control bit to be sent to the base station. This test verifies that the mobile station can perform FFPC while in soft handoff. This test also verifies that the mobile station can process the various parameters in the Extended Channel Assignment Message, the Extended Supplemental Channel Assignment Message, the Universal Handoff Direction Message, and the Service Connect Message.
4.2.3.2 Traceability:
(See [1] )
2.1.3.1.11 Reverse Power Control Subchannel
Traceability: (See [4] )
2.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages
3.6.6.2.2.12 Processing of Extended Supplemental Channel Assignment Message
3.7.3.3.2.37 Extended Supplemental Channel Assignment Message
2.6.3.3 Page Response Substate
2.6.3.5 Mobile Station Origination Attempt Substate
3.6.3.3 Response to Page Response Message
3.6.3.5 Response to Origination Message
4-18
C.S0044-0 v1.0
3.7.2.3.2.21 Extended Channel Assignment Message 1
2
3
4
5
3.7.5.7 Service Configuration 6
7
8
9
10
11
12
13
14
.2.3-115
Table 4.2.3-1 Test Parameters for Fast Forward Power Control 16
2.6.4.1.2 Service Configuration and Negotiation
2.6.4.1.2.2 Service Subfunctions
3.7.3.3.2.20 Service Connect Message
3.7.5 Information Records
3.7.5.20 Non negotiable System Configuration
Applicability: Forward Link: RC 1 through RC 5; Reverse Link: RC 1 through RC 4
4.2.3.3 Call Flow Example(s)
None
4.2.3.4 Method of Measurement
4.2.3.4.1 F-FCH in SHO and F-SCH not in SHO; FPC_MODE = 001
a. Setup the test as shown in Annex A Figure A-7.
b. Set power levels as stated in Table 4 .
Parameter Unit Base station 1 Base station 2
-7 -7
Ioc dBm/1.23 MHz -75 -75
Ior/Ioc dB 10 10
Pilot Ec/Io dB -10.2 -20.2
Pilot Ec/Ior dB
17
18 19
20 21
22
c. Setup a mobile station originated call using Service Option 32 (Test Data Service Option) on base station 1.
d. Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:
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)
4-19
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
2 3
4
e. Instruct the base station to send the Service Connect Message with the parameters set as follows:
FPC_INCL = ‘1’ FPC_OLPC_FCH_INCL = ‘0’
FPC_PRI_CHAN = ‘0’ GATING_RATE_INCL = ‘0’
FPC_MODE = ‘001’
5
6 7 8
9
f. Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel by using the Extended Supplemental Channel Assignment Message with the power control related parameters set as follows:
FPC_INCL = ‘1’ FPC_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%)
10
11 12 13
14 15
16
g. Raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message.
h. Instruct the base station to send the Universal Handoff Direction Message during F-SCH assignment with the parameters set as follows:
CH_IND = ‘101’ (FCH and Continuous Reverse Pilot)
NUM_PILOTS = ‘010’
For PILOT_PN = {base station 1} PILOT_INCL = ‘1’
4-20
C.S0044-0 v1.0
For PILOT_PN = {base station 2} PILOT_INCL = ‘0’
1
2
j. Set the test parameters as specified in Table 4.2.3-2without dropping the call. 3
4
i. Verify there are no forward supplemental channels transmitting on base station 2.
Table 4.2.3-2 Test Parameters for Fast Forward Power Control
Parameter Unit Channel 1 Channel 2
Pilot Ec/Ior dB -7 -7
Traffic Ec/Ior dB -7 -7
Ioc dBm/1.23 MHz -75 -75
Pilot Ec/Io dB -11.8 -11.8
5
6 7
8 9
10
11 12 13
14 15
16
4.2.3.4.2 17
18
19
20 21
22 23
24
k. Monitor the forward link FER on both F-FCH and F-SCH (during F-SCH assignment) at the mobile station.
l. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source.
m. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.
n. Verify that the forward link FERs on FCH and SCH (during SCH assignment) remain at approximately in the target value.
o. End the call at the mobile station.
F-FCH in SHO and F-SCH not in SHO; FPC_MODE = ‘010’
a. Setup the test as shown in Annex A Figure A-7.
b. Set power levels as stated in Table 4.2.3-1.
c. Setup a mobile station originated call using Service Option 32 (Test Data Service Option) with 100% frame activity on base station 1.
d. Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:
ASSIGN_MODE = ‘100’ GRANTED_MODE = ‘10’
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)
4-21
C.S0044-0 v1.0
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)
1
2 3
4
e. Instruct the base station to send the Service Connect Message with the parameters set as follows:
FPC_INCL = ‘1’ FPC_OLPC_FCH_INCL = ‘0’
FPC_PRI_CHAN = ‘0’ GATING_RATE_INCL = ‘0’
FPC_MODE = ‘010’
5
6 7 8
9
f. Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel by using the Extended Supplemental Channel Assignment Message with the power control related parameters set as follows:
FPC_INCL = ‘1’ FPC_SCH_INIT_SETPT = ‘01000000’ (8 dB)
FPC_MODE_SCH = ‘010’ 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%)
10
11 12 13
14 15
16
g. Raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message.
h. Instruct the base station to send the Universal Handoff Direction Message during F-SCH assignment with parameters set as follows:
CH_IND = ‘101’ (FCH and Continuous Reverse Pilot)
NUM_PILOTS = ‘010’
4-22
C.S0044-0 v1.0
For PILOT_PN = {base station 1} PILOT_INCL = ‘1’
For PILOT_PN = {base station 2} PILOT_INCL = ‘0’
1
2
3
4 5
6 7 8
9 10 11
12 13
14
15
16
.2.3-117
18 19
20 21
22
i. Verify there are no forward supplemental channels running on base station 2.
j. Set the test parameters as specified in Table 4.2.3-2without dropping the call.
k. Monitor the forward link FER on both F-FCH and F-SCH (during F-SCH assignment) at the mobile station.
l. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source.
m. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.
n. Verify that the forward link FERs on FCH and SCH (during SCH assignment) remain at approximately in the target value.
o. End the call at the mobile station.
4.2.3.4.3 F-DCCH in SHO and F-SCH not in SHO; FPC_MODE = ‘001’
a. Setup the test as shown in Annex A Figure A-7.
b. Set power levels as stated in Table 4 .
c. Setup a mobile station originated call using Service Option 32 (Test Data Service Option) with 100% frame activity on base station 1.
d. Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:
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)
23
4-23
C.S0044-0 v1.0
1 2
3
e. Instruct the base station to send the Service Connect Message with the parameters set as follows:
FPC_INCL = ‘1’ FPC_OLPC_FCH_INCL = ‘0’
FPC_PRI_CHAN = ‘1’ GATING_RATE_INCL = ‘0’
FPC_MODE = ‘001’
4
5 6 7
8
f. Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel by using the Extended Supplemental Channel Assignment Message with the power control related parameters set as follows:
FPC_INCL = ‘1’ FPC_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%)
9
10 11 12
13 14
15
g. Raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message.
h. Instruct the base station to send the Universal Handoff Direction Message during F-SCH assignment with parameters set as follows:
CH_IND = ‘110’ (FCH and Continuous Reverse Pilot)
NUM_PILOTS = ‘010’
For PILOT_PN = {base station 1} PILOT_INCL = ‘1’
For PILOT_PN = {base station 2} PILOT_INCL = ‘0’
16
17
18
19 20
i. Verify there are no forward supplemental channels running on base station 2.
j. Set the test parameters as specified in Table 4.2.3-2without dropping the call.
k. Monitor the forward link FER on both F-DCCH and F-SCH (during F-SCH assignment) at the mobile station.
4-24
C.S0044-0 v1.0
l. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source.
1 2 3
4 5 6
7 8
9
10
11
.2.3-112
13 14
15 16
17
m. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.
n. Verify that the forward link FERs on DCCH and SCH (during SCH assignment) remain at approximately in the target value.
o. End the call at the mobile station.
4.2.3.4.4 F-DCCH in SHO and F-SCH not in SHO; FPC_MODE = ‘010’
a. Setup the test as shown in Annex A Figure A-7.
b. Set power levels as stated in Table 4 .
c. Setup a mobile station originated call using Service Option 32 (Test Data Service Option) with 100% frame activity on base station 1.
d. Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:
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)
18
19 20
21
e. Instruct the base station to send the Service Connect Message with the parameters set as follows:
FPC_INCL = ‘1’ FPC_OLPC_FCH_INCL = ‘0’
FPC_PRI_CHAN = ‘0’ GATING_RATE_INCL = ‘0’
FPC_MODE = ‘010’
22
4-25
C.S0044-0 v1.0
1 2 3
4
f. Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel by using the Extended Supplemental Channel Assignment Message with the power control related parameters set as follows:
FPC_INCL = ‘1’ FPC_SCH_INIT_SETPT = ‘01000000’ (8 dB)
FPC_MODE_SCH = ‘010’ 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%)
5
6 7 8
9 10
11
g. Raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message.
h. Instruct the base station to send the Universal Handoff Direction Message during F-SCH assignment with parameters set as follows:
CH_IND = ‘110’ (FCH and Continuous Reverse Pilot)
NUM_PILOTS = ‘010’
For PILOT_PN = {base station 1} PILOT_INCL = ‘1’
For PILOT_PN = {base station 2} PILOT_INCL = ‘0’
12
13
14
15 16
17 18 19
20 21 22
23 24
25
i. Verify there are no forward supplemental channels running on base station 2.
j. Set the test parameters as specified in Table 4.2.3-2 without dropping the call.
k. Monitor the forward link FER on both F-DCCH and F-SCH (during F-SCH assignment) at the mobile station.
l. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source.
m. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.
n. Verify that the forward link FERs on DCCH and SCH (during SCH assignment) remain at approximately in the target value.
o. End the call at the mobile station.
4-26
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
33
34
4.2.3.5 Minimum Standard
4.2.3.5.1 F-FCH in SHO and F-SCH not in SHO; FPC_MODE = 001
The mobile station shall comply with steps i and n.
4.2.3.5.2 F-FCH in SHO and F-SCH not in SHO; FPC_MODE = ‘010’
The mobile station shall comply with steps i and n.
4.2.3.5.3 F-DCCH in SHO and F-SCH not in SHO; FPC_MODE = ‘001’
The mobile station shall comply with steps i and n.
4.2.3.5.4 F-DCCH in SHO and F-SCH not in SHO; FPC_MODE = ‘010’
The mobile station shall comply with steps i and n.
For all tests, the call shall not drop and the FER shall remain in the target value.
4.2.4 Change FPC_MODE During a Call
4.2.4.1 Definition
The mobile station accomplishes fast forward power control by transmitting the power control subchannel to the base station on the R-PICH. The mobile station determines the information to send to the base station through inner and outer closed loop estimations. In outer loop estimation, the mobile station adjusts the Eb/Nt setpoints to the Eb/Nt value necessary to achieve the target FER on the Forward Traffic Channel.
In inner loop estimation, the mobile station compares the received Eb/Nt to the setpoint and determines the value of the power control bit to be sent to the base station. This test verifies that the mobile station can process a change in FPC_MODE delivered by the Power Control Message.
4.2.4.2 Traceability: (See [1] )
2.1.3.1.10 Reverse Power Control Subchannel
(See [4] )
2.6.4.1.1.3 Processing the Power Control Message
3.7.3.3.2.25 Power Control Message
2.6.2.4 Mobile Station Order and Message Processing Operation
2.6.3.3 Page Response Substate
2.6.3.5 Mobile Station Origination Attempt Substate
3.6.3.3 Response to Page Response Message
3.6.3.5 Response to Origination Message
3.7.2.3.2.21 Extended Channel Assignment Message
2.6.4.1.2 Service Configuration and Negotiation
4-27
C.S0044-0 v1.0
1
2
3
4
5
6
7
8
9
10
11
12 13
14 15
16
2.6.4.1.2.2 Service Subfunctions
3.7.3.3.2.20 Service Connect Message
3.7.5 Information Records
3.7.5.7 Service Configuration
3.7.5.20 Non negotiable System Configuration
Applicability: RC 3 and greater
4.2.4.3 Call Flow Example(s)
None
4.2.4.4 Method of Measurement
a. Connect base station and mobile station as shown in Annex A Figure A-6.
b. Set power levels as stated in Table 4.2.1-2
c. Setup a mobile station originated call using Service Option 32 (Test Data Service Option) with 100% frame activity.
d. Instruct the base station to send the Extended Channel Assignment Message with the parameters set as follows:
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)
17
18 19
20
21 22
23 24
25 26
e. Instruct the base station to send the Service Connect Message with FPC_INCL set to ‘0’.
f. Monitor forward link FER at the mobile station.
g. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 5 dBm/1.23 MHz at the AWGN source.
h. Monitor traffic channel Ec/Ior and ensure power increases corresponding to noise power from the AWGN source.
i. Instruct the base station send the Power Control Message with the parameters set as follows:
4-28
C.S0044-0 v1.0
1
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’ (2 dB)
FPC_FCH_MAX_SETPT = ‘10000000’ (16 dB)
FPC_OLPC_DCCH_INCL = ‘0’
FPC_DCCH_MIN_SEPT = N/A FPC_DCCH_MAX_SEPT = N/A
FPC_OLPC_SCH_M_INCL = ‘1’ FPC_SCH_M_FER = ‘00010’ (1%)
FPC_MIN_SCH_M_SETPT = ‘00010000’ (2 dB)
FPC_MAX_SCH_M_SETPT = ‘10000000’ (16 dB)
NUM_SUP = 0
2
j. Monitor forward link FER at the mobile station. 3
4 5 6
7 8 9
10
11
12
13
14
15
16
17
18 19 20 21 22
k. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 5 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source.
l. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.
m. Verify that the forward link FER on FCH remains at approximately the target value.
n. End the call at the mobile station.
4.2.4.5 Minimum Standard
The mobile station shall comply with step m.
4.2.5 R-PICH in Gated Transmission Mode
4.2.5.1 Gating with the Reverse Dedicated Control Channel
4.2.5.2 Definition
The mobile station accomplishes fast forward power control by transmitting the power control subchannel to the base station on the R-PICH. The power control subchannel can either be gated (either at a rate of ½ or ¼) or not gated (a bit is transmitted on every PCG). Gating occurs only when the Forward Dedicated Control Channel and the Reverse Dedicated Control Channel are assigned and when there are no transmissions on the Reverse Dedicated Control Channel. This
4-29
C.S0044-0 v1.0
1 2
3 4
5
test verifies that the mobile station can operate in the various gating transmission modes specified in the Service Connect Message.
Figure 4.2.5.1.1-1 Reverse Pilot Gating with no Transmission on the Reverse Dedicated Control Channel
4-30
C.S0044-0 v1.0
4-31
1 2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
Figure 4.2.5.1.1-2 Reverse Pilot Gating during Reverse Dedicated Control Channel Transmission
4.2.5.3 Traceability: (See [1] )
2.1.3.1.10 Reverse Power Control Subchannel
2.1.3.2 Reverse Pilot Channel
(See [4] )
2.6.4.1.1.3 Processing the Power Control Message
3.7.3.3.2.25 Power Control Message
2.6.2.4 Mobile Station Order and Message Processing Operation
2.6.3.3 Page Response Substate
2.6.3.5 Mobile Station Origination Attempt Substate
3.6.3.3 Response to Page Response Message
3.6.3.5 Response to Origination Message
3.7.2.3.2.21 Extended Channel Assignment Message
2.6.4.1.2 Service Configuration and Negotiation
2.6.4.1.2.2 Service Subfunctions
3.7.3.3.2.20 Service Connect Message
3.7.5 Information Records
3.7.5.7 Service Configuration
3.7.5.20 Non negotiable System Configuration
C.S0044-0 v1.0
Applicability: Forward Link: RC 1 through RC 5; Reverse Link: RC 1 through RC 4 1
2
3
4
5
able 4.2.1-26
7
8 9
10
4.2.5.4 Call Flow Example(s)
None
4.2.5.5 Method of Measurement
a. Connect base station and mobile station as shown in Annex A Figure A-6
b. Set power levels as stated in T .
c. Setup a mobile station originated data call using Service Option 33.
d. Instruct the base station to send the Extended Channel Assignment Message has the parameters set as follows:
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)
11
12 13
14
e. Instruct the base station to send the Service Connect Message has the parameters set as follows:
FPC_INCL = ‘1’ FPC_OLPC_FCH_INCL = ‘0’
FPC_PRI_CHAN = ‘1’ FPC_OLPC_DCCH_INCL = ‘0’
FPC_MODE = ‘000’
GATING_RATE_INCL = ‘1’ PILOT_GATE_RATE = ‘01’ (gating at ½)
15
16 17
18
19 20
f. Instruct the base station to send the Extended Release Message with CH_IND set to ‘100’.
g. Do not have any transmissions on the Reverse Dedicated Control Channel.
h. Instruct the base station to send a sufficient number of In-Traffic System Parameters Messages with the same system configurations and without requiring the
4-32
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 33 34 35 36 37 38 39
acknowledgment on the reverse link DCCH so that the mobile station can measure forward FER.
i. Monitor forward link FER at the mobile station.
j. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 5 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source.
k. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.
l. Verify that the reverse Pilot Channel is gated at the specified rate and the forward link FER on DCCH remains at approximately the target value
m. Instruct the mobile station to send the Data Burst Message on the Reverse Dedicated Control Channel.
n. Monitor the forward link FER at mobile station.
o. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 5 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source.
p. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.
q. Verify that the reverse Pilot Channel is gated at the target rate if no transmissions are on the Reverse Dedicated Control Channel and the reverse Pilot Channel is not gated if there are transmissions on the Reverse Dedicated Control Channel.
r. Verify that the forward link FER on DCCH remains at approximately the target value.
s. End the call at the mobile station. Repeat steps a through r above except for step e to set PILOT_GATE_RATE to ‘10’ (gating at ¼).
4.2.6 Minimum Standard
Gating with the Reverse Dedicated Control Channel
The mobile station shall comply with steps l, q, and r.
4.2.7 Gating with the Reverse Fundamental Channel
4.2.7.1 Definition
The mobile station accomplishes fast forward power control by transmitting the power control subchannel to the base station on the R-PICH. The power control subchannel can either be gated or not gated. The R-FCH may be gated when no other Reverse Traffic Channel is assigned and the data rate is 1500 bps for RC 3 and RC5 or 1800 bps for RC4. When the R-FCH is operated in 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-PICH shall have a transmission duty cycle of 50%. The R-PICH shall be transmitted in power control groups 2, 3, 6, 7, 10, 11, 14, and 15, and shall not be transmitted in power control groups 0, 1, 4, 5, 8, 9, 12, and 13.
4-33
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
Figure 4.2.5.2.1-1 Gating with the R-FCH
4.2.7.2 Traceability: (See [1] )
2.1.3.1.10 Reverse Power Control Subchannel
2.1.3.2 Reverse Pilot Channel
2.1.3.7.8 Reverse Fundamental Channel
Traceability: (See [4] )
2.6.4.1.1.3 Processing the Power Control Message
3.7.3.3.2.25 Power Control Message
2.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages
3.6.6.2.2.12 Processing of Extended Supplemental Channel Assignment Message
Extended Supplemental Channel Assignment Message
2.6.2.4 Mobile Station Order and Message Processing Operation
2.6.3.3 Page Response Substate
2.6.3.5 Mobile Station Origination Attempt Substate
3.6.3.3 Response to Page Response Message
3.6.3.5 Response to Origination Message
3.7.2.3.2.21 Extended Channel Assignment Message
2.6.4.1.2 Service Configuration and Negotiation
2.6.4.1.2.2 Service Subfunctions
4-34
C.S0044-0 v1.0
3.7.3.3.2.20 Service Connect Message 1
2
3
4
5
6
7
8
9
able 4.2.1-210
11 12 13
14 15 16
17
3.7.5 Information Records
3.7.5.7 Service Configuration
3.7.5.20 Non negotiable System Configuration
Applicability: RC 3 and greater
4.2.7.3 Call Flow Example(s)
None
4.2.7.4 Method of Measurement
a. Connect base station and mobile station as shown in Annex A Figure A-6.
b. Set power levels as stated in T .
c. Setup a mobile station originated call using Service Option 32 (Test Data Service Option) with rate 1500 bps only and set the REV_FCH_GATING_REQ field to ‘1’ in the Origination Message.
d. Instruct the base station to send the Extended Channel Assignment Message has the parameters set as follows and set the REV_PWR_CNTL_DELAY field according to the base station’s implementation.
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)
REV_FCH_GATING_MODE = ‘1’
REV_PWR_CNTL_DELAY_INCL = ‘1’
18
19 20
f. Ensure the Reverse Fundamental Channel is transmitted at 1/8 rate. 21
22
e. Instruct the base station to send the Service Connect Message with FPC_INCL set to ‘0’.
g. Monitor forward link FER at the mobile station.
4-35
C.S0044-0 v1.0
h. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 5 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source.
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.8-133
.2.834
i. Monitor traffic channel Ec/Ior and ensure power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.
j. Verify the Reverse Fundamental Channel is in gated mode and the Reverse Pilot Channel has a transmission duty cycle of 50%.
k. Verify that the forward link FER on FCH is remaining in the target value.
l. End the call at the mobile station.
m. Repeat steps a through l except for the step d to set FOR_RC to 4 and REV_RC to 4.
4.2.7.5 Minimum Standard
The mobile station shall comply with steps j, k and m.
4.2.8 Forward Power Control With EIB and QIB While Transmitting Frames on the Forward Fundamental Channel (FPC_MODE = ‘011’ or ‘100’)
4.2.8.1 Definition
This test shall be performed on the Forward Fundamental Channel with FPC_MODE equal to ‘011’ and ‘100’. In this test, QIB is same as EIB. The mobile station shall set the EIB or QIB to ‘0’on the Reverse Power Control Subchannel in the second transmitted frame following the detection of a good 20ms frame or the detection of at least one good 5ms frame without the detection of any bad 5 ms frames within 20ms (if the mobile station support 5ms frame size) on the Forward Fundamental Channel. Otherwise the mobile station shall set the EIBor QIB to ‘1’ in the second transmitted 20 ms frame.
4.2.8.2 Traceability
[1] 2.1.3.1.10.1 Reverse Power Control Subchannel Structure
[1] 2.2.2.2 Erasure Indicator Bit and Quality Indicator Bit
[4] 2.6.4.1.1 Forward Traffic Channel Power Control
[4] 3.7.2.3.2.21 Extended Channel Assignment Message
4.2.8.3 Call Flow Example(s)
None
4.2.8.4 Method of Measurement
a. Setup test as shown in Annex A Figure A-6.
b. Set power ratios and levels as specified in Table 4 .
Table 4 -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
Ioc dBm/1.23 MHz -55
1
2 3
4
5 6
7
c. The Reverse Link attenuation should be set to balance the forward and reverse links (approximately 90 dB).
d. Setup a mobile station originated call.
e. Instruct the base station to send an Extended Channel Assignment Message with the parameters set as follows:
ASSIGN_MODE = ‘000’ or ‘100’ GRANTED_MODE = ‘10’
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)
CH_IND = ‘01’
8
9 10
11
f. Instruct the base station to send a Service Connect Message with the parameters set as follows:
FPC_INCL = ‘1’ FPC_OLPC_FCH_INCL = ‘0’
FPC_PRI_CHAN = ‘0’ GATING_RATE_INCL = ‘0’
FPC_MODE = ‘011’
12
13 14
15 16 17
18
19
20
g. From the base station, send a sequence of at least 50 good frames and at least 50 bad frames to the mobile station on the Forward Fundamental Channel.
h. Verify that the mobile station Reverse Power Control Subchannel bit pattern follows the frame pattern sent from the base station to the mobile station (i.e. a ‘0’ for a good frame and a ‘1’ for a bad frame).
i. End the call.
j. Repeat steps a through j except for the step e to set REV_RC to 3 and FOR_RC to 4.
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
4.2.8.5 Minimum Standard 1
2
3 4
5
6 7 8 9
10 11
12
13
14
15
16
17
18
19
20
able 4.2.1-221
22 23
24
25 26
27
The mobile station shall comply with steps h.
4.2.9 Forward Power Control With EIB While Transmitting Frames on the Forward Dedicated Control Channel (FPC_MODE = ‘011’)
4.2.9.1 Definition
This test shall be performed on the Forward Dedicated Control Channel with FPC_MODE equal to ‘011’. The mobile station shall set the EIB to ‘0’ on the Reverse Power Control Subchannel in the second transmitted 20ms frame following the detection of a good 20ms frame or the detection of at least one good 5ms frame without the detection of any bad 5 ms frames within 20ms on the Forward Dedicated Control Channel. Otherwise, the mobile station shall set the EIB to ‘1’ in the second transmitted 20 ms frame.
4.2.9.2 Traceability
[1] 2.1.3.1.10.1 Reverse Power Control Subchannel Structure
[1] 2.2.2.2 Erasure Indicator Bit and Quality Indicator Bit
[4] 2.6.4.1.1 Forward Traffic Channel Power Control
[4] 3.7.2.3.2.21 Extended Channel Assignment Message
4.2.9.3 Call Flow Example(s)
None
4.2.9.4 Method of Measurement
a. Setup test as shown in Annex A Figure A-6.
b. Set power ratios and levels as specified in T .
c. The Reverse Link attenuation should be set to balance the forward and reverse links (approximately 90 dB).
d. Setup a mobile station originated data call by using SO33.
e. Instruct the base station to send an Extended Channel Assignment Message with the parameters set as follows:
ASSIGN_MODE = ‘000’ or ‘100’ GRANTED_MODE = ‘10’
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)
CH_IND = ‘10’
28
29 30
31
f. Instruct the base station to send a Service Connect Message with the parameters set as follows:
4-38
C.S0044-0 v1.0
FPC_INCL = ‘1’ FPC_OLPC_FCH_INCL = ‘0’
FPC_PRI_CHAN = ‘1’ GATING_RATE_INCL = ‘0’
FPC_MODE = ‘011’ DCCH_FRAME_SIZE = ‘11’
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
g. From the base station, send a sequence of at least 50 good frames and at least 50 bad frames , to the mobile station on the Forward Fundamental Channel.
h. Verify that the mobile station Reverse Power Control Subchannel bit pattern follows the frame pattern sent from the base station to the mobile station (i.e. a ‘0’ for a good frame and a ‘1’ for a bad frame).
i. End the call.
j. Repeat steps d through i except for step e to set REV_RC to 3 and FOR_RC to 4.
k. Repeat steps d through i except for step e to set REV_RC to 4 and FOR_RC to 5.
4.2.9.5 Minimum Standard
The mobile station shall comply with step h.
4.2.10 Forward Power Control With QIB on the Forward Dedicated Control Channel (FPC_MODE = ‘100’)
4.2.10.1 Definition
This test shall be performed on the Forward Dedicated Control Channel with FPC_MODE equal to ‘100’. The mobile station shall set the QIB to ‘0’ on the Reverse Power Control Subchannel in the second transmitted frame following the detection of a 20ms period with sufficient signal quality on the Forward Dedicated Control Channel. The mobile station shall set the QIB to ‘1’ on the Reverse Power Control Subchannel in the second transmitted frame following the detection of a 20ms period with insufficient signal quality on the Forward Dedicated Control Channel. When transmitting active frames on the Forward Dedicated Control Channel only, the QIB will be the same as the EIB When the frame is inactive (i.e. only the power control bits are transmitted in a frame), the Quality Indicator Bit indicates the channel quality.
4.2.10.2 Traceability:
[1] 2.1.3.1.10.1 Reverse Power Control Subchannel Structure
[1] 2.2.2.2 Erasure Indicator Bit and Quality Indicator Bit
[4] 2.6.4.1.1 Forward Traffic Channel Power Control
[4] 2.6.4.1.1 Forward Traffic Channel Power Control
[4] 3.7.2.3.2.21 Extended Channel Assignment Message
4.2.10.3 Call Flow Example(s)
None
4-39
C.S0044-0 v1.0
4.2.10.4 Method of Measurement 1
2
able 4.2.1-23
4 5
6
7 8
9
a. Setup test as shown in Annex A Figure A-6.
b. Set power ratios and levels as specified in T .
c. The Reverse Link attenuation should be set to balance the forward and reverse links (approximately 90 dB).
d. Setup a mobile station originated data call by using Service Option 33.
e. Instruct the base station to send an Extended Channel Assignment Message with the parameters set as follows:
ASSIGN_MODE = ‘100’ GRANTED_MODE = ‘10’
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)
CH_IND = ‘10’
10
11 12
13
f. Instruct the base station to send a Service Connect Message with the parameters set as follows:
FPC_INCL = ‘1’ FPC_OLPC_FCH_INCL = ‘0’
FPC_PRI_CHAN = ‘1’ GATING_RATE_INCL = ‘0’
FPC_MODE = ‘100’ FPC_OLPC_DCCH_INCL = ‘0’
14 15
16 17
18
19
20
21
22
g. Instruct the base station to send a sequence of at least 50 good frames and at least 50 bad frames to the mobile station on the Forward Dedicated Control Channel.
h. Verify the mobile station QIB bit pattern follows the frame pattern sent from the base station to the mobile station (i.e. a ‘0’ for a good frame and a ‘1’ for a bad frame)
i. End the call.
j. Repeat steps d through j except for step e to set REV_RC to 3 and FOR_RC to 4.
k. Repeat steps d through j except for step e to set REV_RC to 4 and FOR_RC to 5.
4.2.10.5 Minimum Standard
The mobile station shall comply with steps h.
4-40
C.S0044-0 v1.0
4.2.11 Forward Power Control With QIB derived from the Forward Fundamental Channel or Dedicated Control Channel and EIB derived from Supplemental Channel (FPC_MODE = ‘101’)
1 2 3
4
5 6 7 8 9
10
11
12
13
14
15
16
17
18
19
20
able 4.2.1-221
22 23
24
25 26
27
4.2.11.1 Definition
This test shall be performed with FPC_MODE equal to ‘101’. The mobile station shall transmit QIB derived from the Forward Fundamental Channel or Forward Dedicated Control Channel on the Primary Reverse Power Control Subchannel and shall transmit EIB derived from Forward Supplemental Channel on the Secondary Reverse Power Control Subchannel. The transmission of the QIB and EIB shall start at the second 20 ms frame of the Reverse Traffic Channel following the corresponding Forward Traffic Channel frame in which QIB or EIB is determined.
4.2.11.2 Traceability:
[1] 2.1.3.1.10.1 Reverse Power Control Subchannel Structure
[1] 2.2.2.2 Erasure Indicator Bit and Quality Indicator Bit
[4] 2.6.4.1.1 Forward Traffic Channel Power Control
[4] 2.6.4.1.1 Forward Traffic Channel Power Control
[4] 3.7.2.3.2.21 Extended Channel Assignment Message
4.2.11.3 Call Flow Example(s)
None
4.2.11.4 Method of Measurement
a. Setup test as shown in Annex A Figure A-6.
b. Set power ratios and levels as specified in T .
c. The Reverse Link attenuation should be set to balance the forward and reverse links (approximately 90 dB).
d. Setup a mobile station originated data call by using Service Option 33.
e. Instruct the base station to send an Extended Channel Assignment Message with the parameters set as follows:
ASSIGN_MODE = ‘100’ GRANTED_MODE = ‘10’
FOR_RC = ‘00011’ (RC 3) REV_RC = ‘00011’ (RC 3)
CH_IND = ‘01’
28
29 30
31
f. Instruct the base station to send a Service Connect Message with the parameters set as follows:
4-41
C.S0044-0 v1.0
FPC_INCL = ‘1’ FPC_OLPC_FCH_INCL = ‘0’
FPC_PRI_CHAN = ‘0’ GATING_RATE_INCL = ‘0’
FPC_MODE = ‘101’ FCH_FRAME_SIZE = ‘1’
1 2 3
4
g. Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel with an infinite duration by using the Extended Supplemental Channel Assignment Message with the power control related parameters set as follows:
FPC_INCL = ‘1’ FPC_SEC_CHAN = ‘0’
FPC_MODE_SCH = ‘101’ NUM_SUP = ‘00’
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
h. Instruct the base station to send a sequence of at least 50 good frames at least 50 bad frames to the mobile station on the Forward Fundamental Channel. Instruct the base station to send a sequence of alternating at least 50 good frames and at least 50 bad frames on the Forward Supplemental Channel.
i. Verify the mobile station QIB bit pattern on Primary Reverse Power Control Channel follows the frame pattern sent from the base station to the mobile station on Forward Fundamental Channel (i.e. a ‘0’ for a good frame and a ‘1’ for a bad frame) . Verify the mobile station EIB bit pattern on Secondary Reverse Power Control Subchannel follows the frame pattern sent from the base station to the mobile station on Forward Supplemental Channel (i.e. a ‘0’ for a good frame and a ‘1’ for a bad frame).
j. End the call.
k. Repeat steps d through j except for step e to set REV_RC to 3 and FOR_RC to 4.
l. Repeat steps d through j except for step e to set REV_RC to 4 and FOR_RC to 5.
m. Repeat steps d through l except for the following steps:
1. Step e: Set CH_IND = ‘10’;
2. Step f: Set FPC_PRI_CHAN = ‘1’ and DCCH_FRAME_SIZE = ‘11’;
3. Step h: Instruct the base station to send a sequence of at least 50 good frames and at least 50 bad frames on the Forward Dedicated Control Channel. Instruct the base station to send a sequence of at least 50 good frames and at least 50 bad frames to the mobile station on the Forward Supplemental Channel.
4. Step i: Verify the mobile station QIB bit pattern on Primary Reverse Power Control Channel follows the frame pattern sent from the base station to the mobile station on Forward Dedicated Control Channel (i.e. a ‘0’ for a good frame and a ‘1’ for a bad frame). Verify the mobile station EIB bit pattern on Secondary Reverse Power Control Subchannel follows the frame pattern sent from the base station to the mobile station on Forward Supplemental Channel (i.e. a ‘0’ for a good frame and a ‘1’ for a bad frame).
4-42
C.S0044-0 v1.0
4.2.11.5 Minimum Standard 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
able 4.2.1-226
27 28
29
30 31
32
The mobile station shall comply with step i.
4.2.12 Forward Power Control With 400 bps data rate on the Forward Fundamental Channel or Forward Dedicated Control Channel and EIB derived from Supplemental Channel (FPC_MODE = ‘110’)
4.2.12.1 Definition
This test shall be performed with FPC_MODE equal to ‘110’. The mobile station shall transmit the Primary Reverse Power Control Subchannel at a 400 bps data rate based on the Forward Fundamental Channel or Forward Dedicated Control Channel, and shall transmit EIB derived from Forward Supplemental Channel on the Secondary Reverse Power Control Subchannel. The transmission of the power control bits on the Primary Reverse Power Control Subchannel is based on inner and outer closed loop estimations. The transmission of the EIB on the Secondary Reverse Power Control Subchannel shall start at the second frame (20ms frame) of the Reverse Traffic Channel following the end of the corresponding Forward Supplemental Channel frame from which the EIB is derived.
4.2.12.2 Traceability:
[1] 2.1.3.1.10.1 Reverse Power Control Subchannel Structure
[1] 2.2.2.2 Erasure Indicator Bit and Quality Indicator Bit
[4] 2.6.4.1.1 Forward Traffic Channel Power Control
[4] 2.6.4.1.1 Forward Traffic Channel Power Control
[4] 3.7.2.3.2.21 Extended Channel Assignment Message
4.2.12.3 Call Flow Example(s)
None
4.2.12.4 Method of Measurement
a. Setup test as shown in Annex A Figure A-6.
b. Set power ratios and levels as specified in T .
c. The Reverse Link attenuation should be set to balance the forward and reverse links (approximately 90 dB).
d. Setup a mobile station originated data call by using Service Option 33.
e. Instruct the base station to send an Extended Channel Assignment Message with the parameters set as follows:
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)
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
2 3
4
f. Instruct the base station to send a Service Connect Message with the parameters set as follows:
FPC_INCL = ‘1’ FPC_OLPC_FCH_INCL = ‘0’
FPC_PRI_CHAN = ‘0’ FPC_OLPC_DCCH_INCL = ‘0’
FPC_MODE = ‘110’ GATING_RATE_INCL = ‘0’
5 6 7
8
g. Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel with an infinite duration by using the Extended Supplemental Channel Assignment Message with the power control related parameters set as follows:
FPC_INCL = ‘1’ FPC_SEC_CHAN = ‘0’
FPC_MODE_SCH = ‘110’ NUM_SUP = ‘00’
9 10
11 12 13
14 15 16
17
18 19
20 21 22
23
24
25
h. Monitor the forward link FER on the Forward Fundamental Channel at the mobile station.
i. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source.
j. Monitor traffic channel Ec/Ior and ensure the power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.
k. Verify that the forward link FER on the FCH remains at approximately the target value .
l. Instruct the base station to send a sequence of at least 50 good frames and at least 50 bad frames to the mobile station on the Forward Supplemental Channel.
m. Verify the mobile station EIB bit pattern on Secondary Reverse Power Control Subchannel follows the frame pattern sent from the base station to the mobile station on Forward Supplemental Channel (i.e. a ‘0’ for a good frame and a ‘1’ for a bad frame)
n. End the call.
o. Repeat steps d through n except for step e to set REV_RC to 3 and FOR_RC to 4.
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
2 3
4
q. Setup a mobile station originated data call by using Service Option 33.
r. Instruct the base station to send an Extended Channel Assignment Message with the parameters set as follows:
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)
5
6 7
8
s. Instruct the base station to send a Service Connect Message with the parameters set as follows:
FPC_INCL = ‘1’ FPC_OLPC_FCH_INCL = ‘0’
FPC_PRI_CHAN = ‘1’ FPC_OLPC_DCCH_INCL = ‘0’
FPC_MODE = ‘110’ GATING_RATE_INCL = ‘0’
9 10 11
12
t. Instruct the base station to download SCH configuration and assign a Forward Supplemental Channel with an infinite duration by using the Extended Supplemental Channel Assignment Message with the power control related parameters set as follows:
FPC_INCL = ‘1’ FPC_SEC_CHAN = ‘1’
NUM_SUP = ‘00’ FPC_MODE_SCH = ‘110’
13 14
15 16 17
18 19 20
21
u. Monitor the forward link FER on the Forward Dedicated Control Channel at the mobile station.
v. Increase Ioc in 1 dBm/1.23 MHz steps every second for a total of 15 dBm/1.23 MHz at the AWGN source and then decrease Ioc in 1 dBm/1.23 MHz steps every second for a total of 20 dBm/1.23 MHz at the AWGN source.
w. Monitor traffic channel Ec/Ior and ensure the power changes corresponding to noise power from the AWGN source. The power increases if the noise power increases and decreases if the noise power decreases.
x. Verify that the forward link FER on the DCCH remains at approximately the target value
4-45
C.S0044-0 v1.0
y. Instruct the base station to send a sequence of at least 50 good frames and at least 50 bad frames to the mobile station on the Forward Supplemental Channel.
1 2
3 4 5
6
7
8
4.2.12.5 Minimum Standard 9
10
11
12
13 14 15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
z. Verify the mobile station EIB bit pattern on Secondary Reverse Power Control Subchannel follows the frame pattern sent from the base station to the mobile station on Forward Supplemental Channel (i.e. a ‘0’ for a good frame and a ‘1’ for a bad frame)
aa. End the call.
bb. Repeat steps q through aa except for step r to set REV_RC to 3 and FOR_RC to 4.
cc. Repeat steps q through aa except for step r to set REV_RC to 4 and FOR_RC to 5.
The mobile station shall comply with steps k, m, x, z.
4.3 Lowest Rate Reverse Fundamental Channel Gating
4.3.1 Definition
This test verifies the mobile station, instructed by the base station, transmits the reverse fundamental channel, with radio configurations 3 or 4, in a duty cycle of 50% when using data rates of 1500 bps for RC3 and 1800 bps for RC4.
4.3.2 Traceability
(See [1])
2.1.3.7.8 Reverse Fundamental Channel Gating
(See [4])
2.2.6.2.5 Mobile Station Origination Operation
2.6.3 System Access State
2.6.3.5 Mobile Station Origination Attempt Substate
2.6.4 Mobile Station Control on the Traffic Channel State
2.7.1.3.2.4 Origination Message
2.7.2.3.2.15 Service Option Control Message
2.7.3 Orders
3.6.3.5 Response to Origination Message 1
3.6.4 Traffic Channel Processing
3.7.2.3.2.21 Extended Channel Assignment Message
3.7.3.3.2.3 Alert With Information Message
3.7.3.3.2.20 Service Connect Message
3.7.4 Orders 15
3.7.5.5 Signal 16
4-46
C.S0044-0 v1.0
4.3.3 Call Flow Example(s) 1
2
3
4.3.4.1 R-FCH Gating disabled at base station 4
5 .3.4-16
7
.3.48
None
4.3.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Annex A Figure A-1and set forward link parameters as specified in . Table 4
Table 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
11 12
13 14
15
16
17
4.3.4.2 18
19 .3.4-120
21
22 23
24 25
26
27 28
29 30
g. Verify transmission is gated at 50% - transmission is turned on and off every 2.5ms, or every 2 Power Control Groups ().
f. Instruct the mobile station to transmit data at 1500 bps (for RC3) or 1800 bps (for RC4) on reverse fundamental channel (i.e. by setting the mobile station to Mute).
e. Verify audio in both directions.
d. Instruct the base station, to send the Extended Channel Assignment Message with REV_FCH_GATING_MODE = 1.
c. Cause the the mobile station to send Origination Message with REV_FCH_GATING_REQ = 1.
b. Setup a mobile station originated call.
a. Connect the mobile station to the base station as shown in Annex A Figure A-1and set forward link parameters as specified in . Table 4
R-FCH Gating enabled at base station
g. Repeat steps c through e for all supported radio configurations.
f. Release the call.
e. Verify audio in both directions.
d. Instruct the base station to send an Extended Channel Assignment Message with REV_FCH_GATING_MODE = 0.
c. Cause the mobile station to send Origination Message with REV_FCH_GATING_REQ = 1.
b. Setup a mobile station originated call.
4-47
C.S0044-0 v1.0
h. Release the call. 1
2
3
4
5
6
7
8
9
10
11
12
(See [1]) 13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
3.7.4 Orders 15 28
29
i. Repeat steps c through e for all supported radio configurations.
j. Release the call.
4.3.5 Minimum Standard
4.3.5.1 R-FCH Gating disabled at base station
The mobile station shall comply with step e and g.
4.3.5.2 R-FCH Gating enabled at base station
The mobile station shall comply with steps g and i.
4.4 R-FCH Gating during Soft Handoff
4.4.1 Definition
This test verifies the functionality of R-FCH gating during soft handoffs.
4.4.2 Traceability
2.1.3.7.8 Reverse Fundamental Channel Gating
(See [4])
2.2.6.2.5 Mobile Station Origination Operation
2.6.3 System Access State
2.6.3.5 Mobile Station Origination Attempt Substate
2.6.4 Mobile Station Control on the Traffic Channel State
2.7.1.3.2.4 Origination Message
2.7.2.3.2.15 Service Option Control Message
2.7.3 Orders
3.6.3.5 Response to Origination Message 10
3.6.4 Traffic Channel Processing 11
3.7.2.3.2.21 Extended Channel Assignment Message 12
3.7.3.3.2.3 Alert With Information Message 13
3.7.3.3.2.20 Service Connect Message 14
3.7.5.5 Signal 16
4-48
C.S0044-0 v1.0
4.4.3 Call Flow Example(s) 1
2
3
4
5
6 .4.4-17
8
9
10
None
4.4.4 Method of Measurement
4.4.4.1 Sectors with Different Values of REV_PWR_CNTL_DELAY
a. Connect the mobile station to base stations 1 and 2 as show in Annex A Figure A-2 and set forward link parameters as show in Table 4 . Configure a different Pilot PN offset for each base station.
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 Power Ior
dBm/1.23MHz -75 -75
Pilot Ec/Ior dB -7 -20
11
12 13
14
15 16
17 18
19
20 21
22 23
24 25 26
27
28 29
30
31
b. Configure base station 1 and base station 2 to be on different power control delay regions: base station 1 = 2 PCGs and base station 2 = 3 PCGs.
c. Setup a mobile station originated call.
d. Cause the mobile station to send Origination Message with REV_FCH_GATING_REQ = 1.
e. Instruct the base station to send an Extended Channel Assignment Message with REV_FCH_GATING_MODE = 1 and REV_PWR_CNTL_DELAY = 2.
f. Verify audio in both directions.
g. Instruct the mobile station to transmit data at 1500 bps (for RC3) or 1800 bps (for RC4) on reverse fundamental channel (i.e. by setting the mobile station to Mute).
h. Verify transmission is gated at 50% - transmission is turned on and off every 2.5ms, or every 2 Power Control Groups ().
i. Raise the level of base station 2 in steps of 1 dB with a dwell time of 1 sec until base station 1 sends an Universal Handoff Direction Message or General Handoff Direction Message with REV_FCH_GATING_MODE = 0.
j. Verify mobile station has both base stations on its active pilot set list.
k. Verify mobile station transmission of 1500 bps (for RC3) or 1800 bps (for RC4) frames is not gated at 50% duty cycle.
l. Release the call.
m. Repeat steps b through l for all support radio configurations.
4-49
C.S0044-0 v1.0
4.4.4.2 1
2 .4.4-13
4
5 6
7
8 9
10 11
12
13 14
15 16
17 18 19
20
21 22
23 24 25
26
27 28
29
30
31
32
33
34
35
Sectors with Same Value of REV_PWR_CNTL_DELAY
a. Connect the mobile station to base stations 1 and 2 as show in Annex A Figure A-2 and set forward link parameters as show in Table 4 . Configure a different Pilot PN offset for each base station but with the same frequency.
b. Configure base station 1 and base station 2 to be on the same power control delay region = 2 PCGs.
c. Setup a mobile station originated call.
d. Verify the mobile station sends Origination Message with REV_FCH_GATING_REQ = 1.
e. Instruct the base station to send an Extended Channel Assignment Message with REV_FCH_GATING_MODE = 1 and REV_PWR_CNTL_DELAY = 2.
f. Verify audio in both directions.
g. Instruct the mobile station to transmit data at 1500bps on reverse fundamental channel (i.e. by setting the mobile station to Mute)
h. Verify transmission is gated at 50% - transmission is turned on and off every 2.5ms, or every 2 Power Control Groups ().
i. Raise the level of base station 2 in steps of 1 dB with a dwell time of 1 sec until base station 1 sends an Universal Handoff Direction Message or General Handoff Direction Message, REV_FCH_GATING_MODE = 1.
j. Verify mobile station has both base stations on its active pilot set list.
k. Verify mobile station transmission of 1500 bps (for RC3) or 1800 bps (for RC4) frames is gated at 50% duty cycle.
l. Lower the level of base station 1 in steps of 1 dB with a dwell time of 1 sec until base station 2 sends an Universal Handoff Direction Message or General Handoff Direction Message, with REV_FCH_GATING_MODE = 1 and REV_PWR_CNTL_DELAY = 2.
m. Verify mobile station has only base station 2 on its active pilot set list.
n. Verify mobile station transmission of 1500 bps (for RC3) or 1800 bps (for RC4) frames is gated at 50% duty cycle.
o. Release the call.
p. Repeat steps b through o for all supported radio configurations.
4.4.5 Minimum Standard
4.4.5.1 Sectors with Same Value of REV_PWR_CNTL_DELAY
The mobile station shall comply with steps d, h, j, k and m.
4.4.5.2 Sectors with Different Values of REV_PWR_CNTL_DELAY
The mobile station shall comply with steps d, h, j, k, m, n, and p.
4-50
C.S0044-0 v1.0
5 REGISTRATIONS 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
5.1 Power-Up Registration
5.1.1 Definition
These tests verify proper power-up registration functionality. The mobile station registers when it powers on, switches from using a different frequency block, switches from using a different band class, switches from using an alternative operating mode, or switches from using the analog system. To prevent multiple registrations when power is quickly turned on and off, the mobile station delays T57m seconds before registering, after entering the Mobile Station Idle State.
5.1.2 Traceability (see [4])
2.6.5.1.1 Power-Up Registration
2.6.5.5.1.3 Entering the Mobile Station Idle State
2.6.5.5.2.1 Idle Registration Procedures
2.7.1.3.2.1 Registration Message
3.6.5 Registration
3.7.2.3.2.1 System Parameters Message
3.7.2.3.2.30 ANSI-41 System Parameters Message
5.1.3 Call Flow Example(s)
None
5.1.4 Method of Measurement
5.1.4.1 Power-up Registration Disabled
a. Connect the base station and mobile station as shown in Figure A-3.
b. Instruct the base station to set POWER_UP_REG = 0 in the System Parameters Message or ANSI-41 System Parameters Message.
c. Power on the mobile station.
d. Verify the mobile station does not attempt power-up registration for at least 1 minute after the mobile station enters the Mobile Station Idle State.
5.1.4.2 Power-up Registration Enabled
a. Connect the base station and mobile station as shown in Figure A-3.
b. Instruct the base station to set POWER_UP_REG = 1 in the System Parameters Message or ANSI-41 System Parameters Message
c. Power on the mobile station.
5-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
33 34
35
d. Verify the mobile station sends a Registration Message with REG_TYPE = ‘0001’ no sooner than 20 seconds (T57M) after entering Mobile Station Idle State.
5.1.4.3 Power-up Registration due to change in Operating Mode
a. Connect the base station and mobile station as shown in Figure A-5. (Base station 1 is a CDMA base station and base station 2 is a non-CDMA base station.
b. Allow the mobile station to operate in the idle state on base station 2.
c. Configure base station 1 to set POWER_UP_REG = 1 in the System Parameters Message or the ANSI-41 System Parameters Message.
d. Force the mobile station to acquire base station 1.
e. Verify the mobile station sends a Registration Message with REG_TYPE = ‘0001’ on base station 1.
5.1.4.4 Power-up Registration entering into different Band Class
a. Connect the base station and mobile station as shown in Figure A-5. (Base station 1 and base station 2 are CDMA base stations using different band classes)
b. Instruct both base station 1 and base station 2 to set POWER_UP_REG = 1 in the System Parameters Message or the ANSI-41 System Parameters Message.
c. Power on the mobile station.
d. Verify the mobile station sends a Registration Message with REG_TYPE = ‘0001’ on base station 1.
e. Force the mobile station to acquire base station 2.
f. Verify the mobile station a Registration Message with REG_TYPE = ‘0001’ on base station 2.
g. Force the mobile station to acquire base station 1.
h. Verify the mobile station performs power-up registration on base station 1.
5.1.4.5 Power-up Registration entering into Different Frequency Blocks
a. Connect the base station and mobile station as shown in Figure A-5. (Base station 1 and base station 2 are CDMA base stations using the same band class with frequencies assignments in a different serving system.)
b. Instruct both base station 1 and base station 2 to set POWER_UP_REG = 1 in the System Parameters Message or the ANSI-41 System Parameters Message while ensuring all other forms of registration are disabled.
c. Power on the mobile station.
d. Verify the mobile station sends a Registration Message with REG_TYPE = ‘0001’ on base station 1.
e. Force the mobile station to acquire base station 2.
5-2
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
f. Verify the mobile station sends a Registration Message with REG_TYPE = ‘0001’ on base station 2.
5.1.5 Minimum Standard
5.1.5.1 Power-up Registration Disabled
The mobile station shall comply with step d. Power-up registration shall not occur.
5.1.5.2 Power-up Registration Enabled
The mobile station shall comply with step d. The mobile station shall perform the registration process when it is powered on and after the power/initialization timer has expired.
5.1.5.3 Power-up Registration entering into different operating mode
The mobile station shall comply with step e.
5.1.5.4 Power-up Registration entering into different Band Class
The mobile station shall comply with steps d, f and h.
5.1.5.5 Power-up Registration entering into Different Frequency Blocks
The mobile station shall comply with steps d and f.
5.2 Power - Down Registration
5.2.1 Definition
These tests verify power-down registration functionality. The mobile station should be able to recognize all base station registration settings.
The mobile station registers when it powers off if previously registered in the current serving system. The mobile station should not perform power-down registration if it has not previously registered in the system corresponding to its current SID and NID.
5.2.2 Traceability (see [4])
2.6.5.1.1 Power-Up Registration
2.6.5.1.2 Power-Down Registration
2.6.5.5.2.1 Idle Registration Procedures
2.7.1.3.2.1 Registration Message
3.6.5 Registration
3.7.2.3.2.1 System Parameters Message
3.7.2.3.2.30 ANSI - 41 System Parameters Message
5.2.3 Call Flow Example(s)
None
5-3
C.S0044-0 v1.0
5.2.4 Method of Measurement 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
5.2.4.1 Power-down Registration Disabled
a. Connect the base station and mobile station as shown in Figure A-3.
b. Enable power-up registration (set POWER_UP_REG = 1 in the System Parameters Message or ANSI - 41 System Parameter Message) while ensuring all other forms of registration are disabled.
c. Power on the mobile station.
d. Verify the mobile station performs a power-up registration.
e. Power down the mobile station.
f. Verify power-down registration does not occur.
5.2.4.2 Power-down Registration of a Currently Registered Mobile Station
a. Connect the base station and mobile station as shown in Figure A-3.
b. Enable power-up registration (set POWER_UP_REG = 1) and power-down registration (set POWER_DOWN_REG = 1) in the System Parameters Message or ANSI - 41 System Parameter Message) while ensuring all other forms of registration are disabled.
c. Power on the mobile station.
d. Verify power-up registration occurs.
e. Power down the mobile station.
f. Verify the mobile station sends a Registration Message with REG_TYPE = ’0011’.
5.2.4.3 Power-down Registration of an Unregistered Mobile Station in New System/Network
a. Connect the base station and mobile station as shown in Figure A-5. (Base station 1 and base station 2 are CDMA base stations using a different SID/NID).
b. Instruct base station 1 to set POWER_ UP = 1 and both base station 1 and base station 2 to set POWER_DOWN = 1 in the System Parameters Message or ANSI - 41 System Parameter Message, and turn off all other types of registration.
c. Power on the mobile station.
d. Verify power-up registration on base station 1.
e. Force the mobile station to acquire base station 2.
f. Verify power-down registration does not occur on base station 2.
5.2.5 Minimum Standard
5.2.5.1 Power-down Registration Disabled
The mobile station shall comply with steps d and f. Power-down registration shall not occur.
5-4
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
33
5.2.5.2 Power-down Registration of a Currently Registered Mobile Station
The mobile station shall comply with steps d and f. The mobile station shall perform power-down registration in a system/network where it is currently registered.
5.2.5.3 Power-down Registration of an Unregistered Mobile Station in a New System/Network
The mobile station shall comply with steps d and g. Power-down registration shall not occur in a system/network where the mobile station is not currently registered.
5.3 Distance-Based Registration
5.3.1 Definition
These tests verify proper distance-based registration functionality.
The mobile station should be able to recognize all base station registration settings.
The mobile station registers when the distance between the current base station and the base station in which it last registered exceeds a threshold.
5.3.2 Traceability (See [4]);
2.6.5.1.1 Power-Up Registration
2.6.5.1.4 Distance-Based Registration
3.6.5 Registration
3.7.2.3.2.1 System Parameters Message
3.7.2.3.2.30 ANSI - 41 System Parameters Message
3.7.2.3.2.31 MC-RR Parameters Message
5.3.3 Call Flow Example(s)
None
5.3.4 Method of measurement
5.3.4.1 Distance-Based Registration Disabled
a. Connect the base station and mobile station as shown in Figure A-5. Use the parameters in Table 5.3.4-1.
b. Configure base station 1 and base station 2 to send the System Parameters Message or the ANSI - 41 System Parameters Message with REG_DIST, BASE_LAT and BASE_LONG parameters as indicated in Table 5.3.4-2 (Test Case 1).
c. Instruct both base station 1 and base station 2 to set power-up registration (set POWER_UP_REG = 1) in the System Parameters Message or the ANSI - 41 System Parameters Message.
d. Power on the mobile station on base station 1.
e. Verify power-up registration occurs.
5-5
C.S0044-0 v1.0
f. Force the mobile station to perform an idle handoff to base station 2 by reducing base station 2 forward link attenuation, then increasing base station 1 forward link attenuation.
1 2 3
4
5
.3.46
g. Verify the mobile station does not perform distance-based registration.
Table 5 -1 Forward Link Parameters for Distance-based Registration
Parameter Unit Channel 1 Channel 2
Ior/Ioc dB 0 -10
Pilot Ec/Ior dB -7 -7
Traffic Ec/Ior dB -7 -7
Ioc dB/1.23 MHz -75 -75
Pilot Ec/Io dB -10.2 -20.2
7
8
9 10 11
Table 5.3.4-2 BTS Distance based LAT/LONG System Parameters Message or the ANSI - 41 System Parameters Message Configuration
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
14 15
16 17 18
5.3.4.2 Distance Threshold Not Exceeded
a. Connect the base station and mobile station as shown in Figure A-5. Use the parameters in Table 5.3.4-1.
b. Configure base station 1 and base station 2 to send the System Parameters Message or the ANSI - 41 System Parameters Message with REG_DIST, BASE_LAT and BASE_LONG parameters as indicated in Table 5.3.4 -2 (Test Case 2).
5-6
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 33 34
c. Instruct both base station 1 and base station 2 to set power-up registration (set POWER_UP_REG = 1) in the System Parameters Message or the ANSI - 41 System Parameters Message.
d. Power on the mobile station.
e. Verify power-up registration occurs.
f. Force the mobile station to perform an idle handoff to base station 2 by reducing base station 2 forward link attenuation, then increasing base station 1 forward link attenuation.
g. Verify the mobile station does not perform distance-based registration.
5.3.4.3 Distance Threshold Exceeded
a. Connect the base station and mobile station as shown in Figure A-5. Use the parameters in Table 5.3.4-1.
b. Configure base station 1 and base station 2 to send the System Parameters Message or the ANSI - 41 System Parameters Message with REG_DIST, BASE_LAT and BASE_LONG parameters as indicated in Table 5.3.4-2 (Test Case 3).
c. Instruct both base station 1 and base station 2 to set power-up registration (set POWER_UP_REG = 1) in the System Parameters Message or the ANSI - 41 System Parameters Message.
d. Power on the mobile station.
e. Verify power-up registration occurs.
f. Force mobile station to perform idle handoff to base station 2 by reducing base station 2 forward link attenuation, then increasing base station 1 forward link attenuation.
g. Verify the mobile station sends a Registration Message with REG_TYPE = ’0110’.
5.3.5 Minimum Standard
5.3.5.1 Distance-based Registration Disabled
The mobile station shall comply with step g. Distance-based registration shall not occur.
5.3.5.2 Distance Threshold Not Exceeded
The mobile station shall comply with step g. The mobile station shall not perform distance-based registration when distance-based registration enabled and calculated value of DISTANCE is less than REG_DIST.
5.3.5.3 Distance Threshold Exceeded
The mobile station shall comply with step g. The mobile station shall perform distance-based registration when distance based registration is enabled and the calculated value of DISTANCE is greater than REG_DIST.
5-7
C.S0044-0 v1.0
5.4 Timer-Based Registration 1
2
3
4
5 6 7
8 9
10
11
12
13
14
15
16
17
18
19
20
21
22 23
24
25
26
27
28
29 30 31
32
33
5.4.1 Definition
These tests verify proper timer - based registration functionality.
The mobile station registers when a timer expires.
Timer-based registration is performed when the counter reaches a maximum value (REG_COUNT_MAX) that is controlled by the base station via the REG_PRD field of the System Parameters Message or ANSI-41 System Parameters Message.
The counter is reset when the mobile station powers on. The counter is reset after each successful registration.
5.4.2 Traceability (see [4])
2.6.5.1.2 Power-Down Registration
2.6.5.1.3 Timer-Based Registration
2.7.1.3.2.1 Registration Message
3.6.5 Registration
3.7.2.3.2.1 System Parameters Message
3.7.2.3.2.30 ANSI- 41 System Parameters Message
5.4.3 Call Flow Example(s)
None
5.4.4 Method of Measurement
5.4.4.1 Timer-based Registration Disabled
a. Connect the base station and mobile station as shown in Figure A-3.
b. Instruct the base station to set POWER_UP_REG =1 and set REG_PRD = 0 in the System Parameters Message or ANSI – 41 System Parameter Message.
c. Power on the mobile station.
d. Verify power-up registration occurs.
e. Verify the mobile station does not perform timer-based registration.
5.4.4.2 Mid-range Timer Value
a. Connect the base station and mobile station as shown in Figure A-3.
b. Instruct the base station to set POWER_UP_REG =0 and set REG_PRD = 38 (57.93 seconds) in the System Parameters Message or ANSI –41 System Parameter Message.
c. Power on the mobile station.
d. Verify timer-based registration occurs approximately every 58 seconds.
5-8
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
5.4.5 Minimum Standard
5.4.5.1 Timer-based Registration Disabled
The mobile station shall comply with steps d and e. Timer-based registration shall not occur.
5.4.5.2 Mid-Range Timer Value
The mobile station shall comply with step d. The mobile station shall perform time-based registration at the interval specified by the REG_PRD value.
5.5 Parameter-Change Registration
5.5.1 Definition
These tests verify proper parameter-change registration functionality.
Parameter-change registration is performed when a mobile station modifies any of the following stored parameters:
a. The mobile station’s SID_NID_LIST does not match the base station’s SID and NID.
5.5.2 Traceability (See [4])
2.6.5.1.6 Parameter-Change Registration
3.6.5 Registration
3.7.2.3.2.1 System Parameters Message
3.7.2.3.2.30 ANSI - 41 System Parameters Message
5.5.3 Call Flow Example(s)
None
5.5.4 Method of Measurement
5.5.4.1 Parameter-Change Registration Disabled
a. Connect the base station and mobile station as shown in Figure A-5. Base station 1 and base station 2 are CDMA base station operating in the same band class and frequencies with different SID values.
b. Instruct the base station to set PARAMETER_REG = ‘0’ and disable all other forms of registration (set equal to 0) in the System Parameters Message or ANSI - 41 System Parameters Message.
c. Power on the mobile station and allow time for the mobile station to acquire base station 1.
d. Force the mobile station to acquire base station 2.
e. Verify the mobile station does not send a Registration Message.
5-9
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
5.5.4.2 Parameter-Based Registration per SID-NID List change
a. Connect the base station and mobile station as shown in Figure A-5. (Base station 1 and base station 2 are CDMA base stations using different SID configurations).
b. Instruct both base station to set PARAMETER_REG = 1 while ensuring all other forms of registration are disabled (set equal to 0) in the System Parameters Message or ANSI - 41 System Parameters Message.
c. Power on the mobile station and allow time for the mobile station to acquire Base Station 1.
d. Force the mobile station to acquire Base Station 2.
e. Verify the mobile station sends a Registration Message with REG_TYPE = ’0100’.
f. Repeat steps a through e with base station 1 and base station 2 using different NID configurations.
5.5.5 Minimum Standard
5.5.5.1 Parameter-Change Registration Disabled
5.5.5.2 The mobile station shall comply with step e. Parameter-Based Registration per SID-NID List change
The mobile station shall comply with step e.
5.6 Zone-Based Registration
5.6.1 Definition
These tests verify proper Zone-based registration functionality.
The mobile station registers when it enters a new zone that is not on its internally stored list of visited registration zones.
The mobile station does not register when it performs an idle handoff into a zone that is on its internally stored list of visited zones.
The mobile station should properly delete entries from its internally stored list of visited registration zones.
5.6.2 Traceability (see [4])
2.6.5.1.1 Power-Up Registration
2.6.5.1.5 Zone-Based Registration
3.6.5 Registration
3.7.2.3.2.1 System Parameters Message
3.7.2.3.2.30 ANSI –41 System Parameters Message
5-10
C.S0044-0 v1.0
5.6.3 Call Flow Diagram 1
2
3
4
5
.6.46
None
5.6.4 Method of Measurement
5.6.4.1 Zone-Based Registration Disabled
Table 5 -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
a. Connect the base station and mobile station as shown in Figure A-5. 7
8 9
10
11 12
13
14 15 16
17
18
19
20 .6.4-121
22 23
24 25 26
27 28 29
b. Configure the System Parameters Message or ANSI - 41 System Parameters Message on base stations 1 and 2 with the REG_ZONE settings from Table 5.6.4-1, test case 1.
c. Enable power-up registration (set POWER_UP_REG = 1 in the System Parameters Message or ANSI – 41 System Parameters Message).
d. Allow for the mobile station to perform a power up registration on base station 1.
e. Force the mobile station to perform an idle handoff to base station 2 by reducing the base station 2 forward link attenuation, while at the same time increasing the base station 1 forward link attenuation.
f. Verify zone-based registration does not occur.
5.6.4.2 Zone-Based Registration Enabled
a. Connect the base station and mobile station as shown in Figure A-5.
b. Configure the System Parameters Message or ANSI - 41 System Parameters Message on base stations 1 and 2 with the settings from Table 5 , test case 2.
c. Enable power-up registration (set POWER_UP_REG = 1 in the System Parameters Message or ANSI – 41 System Parameters Message).
d. Power on the mobile station and allow it to perform a power up registration on base station 1. (The mobile station should now be registered in zone 1 and the only entry in the mobile station’s ZONE_LIST).
e. Force the mobile station to perform an idle handoff to base station 2 by reducing the base station 2 forward link attenuation, while at the same time increasing the base station 1 forward link attenuation.
5-11
C.S0044-0 v1.0
f. Verify the mobile station sends a Registration Message with REG_TYPE = ’0010’. (The mobile station should now be registered in zone 2. Zone 1 and Zone 2 should be in the mobile station’s ZONE_LIST).
1 2 3
4 5 6
7 8
9
10
11 .6.4-112
13 14
15 16 17
18 19 20
21 22
23 24
25
26
27
28
29 30
31 32
33 34 35
g. Before the period of time specified by ZONE_TIMER has elapsed (one minute) and the mobile station deletes zone 1 from it’s ZONE_LIST, force the mobile station to perform an idle handoff back to base station 1.
h. Verify zone-based registration does not occur. (Zone 1 is still in the mobile station’s ZONE_LIST).
5.6.4.3 Zone-Based Registration Timer
a. Connect the base station and mobile station as shown in Figure A-5.
b. Configure the System Parameters Message or ANSI - 41 System Parameters Message on base stations 1 and 2 with the settings from Table 5 , test case 3.
c. Enable power-up registration (set POWER_UP_REG = 1 in the System Parameters Message or ANSI – 41 System Parameters Message).
d. Power on the mobile station and allow it to perform a power up registration on base station 1. (The mobile station should now be registered in zone 1 and the only entry in the mobile station’s ZONE_LIST).
e. Force the mobile station to perform an idle handoff to base station 2 by reducing the base station 2 forward link attenuation, while at the same time increasing the base station 1 forward link attenuation.
f. Verify zone-based registration occurs. (The mobile station should now be registered in zone 2. Zone 1 and Zone 2 should be in the mobile station’s ZONE_LIST).
g. Wait for the period of time specified by ZONE_TIMER to elapse (one minute, after which the mobile station should delete zone 1 from ZONE_LISTs).
h. Force the mobile station to perform an idle handoff to base station 1.
i. Verify the mobile station sends a Registration Message with REG_TYPE = ’0010’.
5.6.4.4 Mobile Station ZONE_LIST Deletion
a. Connect the base station and mobile station as shown in Figure A-5.
b. Configure the System Parameters Message or ANSI - 41 System Parameters Message on base stations 1 and 2 with the settings from Table 5.6.4-1, test case 4.
c. Enable power-up registration (set POWER_UP_REG = 1 in the System Parameters Message or ANSI – 41 System Parameters Message).
d. Power on the mobile station and allow it to perform a power up registration on base station 1. (The mobile station should now be registered in zone 1 and the only entry in the mobile station’s ZONE_LIST).
5-12
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
e. Force the mobile station to perform an idle handoff to base station 2 by reducing the base station 2 forward link attenuation, while at the same time increasing the base station 1 forward link attenuation.
f. Verify the mobile station sends a Registration Message with REG_TYPE = ‘0010’. (The mobile station is now registered in zone 2, and only zone 2 should be in mobile station’s ZONE_LIST because the mobile station was forced to delete zone 1 from ZONE_LISTs to make room for zone 2).
g. Force the mobile station to perform an idle handoff back to base station 1.
h. Verify the mobile station sends a Registration Message with REG_TYPE = ’0010’. (Zone 1 is not in ZONE_LISTs).
5.6.5 Minimum Standard
5.6.5.1 Zone-Based Registration Disabled
The mobile station shall comply with step f. The mobile station shall not perform a zone-based registration.
5.6.5.2 Zone-Based Registration Enabled
The mobile station shall comply with steps f, h. The mobile station performs a zone-based registration.
5.6.5.3 Zone-Based Registration Timer
The mobile station shall comply with steps f, and i. The mobile station performs a zone-based registration.
5.6.5.4 Mobile Station ZONE_LIST Deletion
The mobile station shall comply with steps f, h. The mobile station performs a zone-based registration.
5-13
C.S0044-0 v1.0
6 AUTHENTICATION 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
6.1 Shared Secret Data (SSD) Initialized when A-Key is Changed
6.1.1 Definition
This test verifies that when the A-Key is changed at both the base station and mobile station, authentication of mobile station registrations, originations, and terminations and the Unique Challenge-Response Procedure are successful.
6.1.2 Traceability: (See [4])
2.3.12.1 (MS) Authentication
2.6.5.1.3 Timer-Based Registration
3.3.1 (Base Station) Authentication
6.1.3 Call Flow Example(s)
None
6.1.4 Method of Measurement
a. Connect the base station and mobile station as shown in Annex A Figure A-1.
b. Power on the mobile station.
c. Initialize the A-Key to the same value in the mobile station and base station.
d. Ensure timer-based registration is enabled with the registration period (REG_PRD) set to 29.
e. Verify the mobile station sends a Registration Message with REG_TYPE set to ‘0000’ (i.e. timer-based registration) and which includes AUTHR, RANDC and COUNT.
f. Verify registration authentication is successful at the base station.
g. Setup a mobile station originated call.
h. Verify user data in both directions.
i. End the call.
j. Setup a mobile station terminated call.
k. Verify user data in both directions.
l. Instruct the base station to initiate a Unique Challenge-Response Procedure while on the f/r-dsch.
m. Verify the following:
1. The base station sends an Authentication Challenge Message,
2. Upon receiving this message, the mobile station sends an Authentication Challenge Response Message, and
6-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
3. The Unique Challenge-Response Procedure is successful.
n. End the call.
o. Instruct the base station to initiate a Unique Challenge-Response Procedure while on the f/r-csch.
p. Verify the following:
1. The base station sends an Authentication Challenge Message,
2. Upon receiving this message, the mobile station sends an Authentication Challenge Response Message, and
3. The Unique Challenge-Response Procedure is successful.
6.1.5 Minimum Standard
The mobile station shall comply with the requirements in the following steps: Step e, h, k, m, p.
The base station shall comply with the requirements in the following steps: Step f, h, k, m, p.
6.2 Shared Secret Data Update
6.2.1 Definition
This test verifies the mobile station and base station can perform a Shared Secret Data update on the f/r-csch and f/r-dsch.
6.2.2 Traceability: (See [4])
2.3.12.1.4 Unique Challenge-Response Procedure
2.3.12.1.5 Updating the Shared Secret Data (SSD)
2.6.5.1.3 Timer-Based Registration
2.7.1.3.2.6 Authentication Challenge Response Message
3.7.2.3.2.1 System Parameters Message (f-csch)
3.7.2.3.2.10 Authentication Challenge Message (f-csch)
6.2.3 Call Flow Example(s)
None
6.2.4 Method of Measurement
a. Connect the base station and mobile station as shown in Annex A Figure A-1.
b. Power on the mobile station.
c. Initialize the A-Key to the same value in both the mobile station and base station.
d. Instruct the base station to initiate a Shared Secret Data update on the f/r-csch.
e. Verify the following:
6-2
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
33
34
1. The base station sends a SSD Update Message,
2. The mobile station sends a Base Station Challenge Order,
3. The base station sends a Base Station Challenge Confirmation Order,
4. The mobile station sends a SSD Update Confirmation Order, and
5. That the SSD Update Procedure is successful.
f. Ensure timer-based registration is enabled with the registration period (REG_PRD) set to 29.
g. Wait for the mobile station to send the Registration Message with REG_TYPE set to ‘0000’ (i.e. timer-based registration).
h. Verify the Registration Message includes AUTHR, COUNT and RANDC.
i. Verify registration authentication is successful at the base station.
j. Setup a mobile station originated call.
k. Verify user data in both directions.
l. Instruct the base station to initiate a Unique Challenge-Response Procedure on the f/r-dsch.
m. Verify the following:
1. The base station sends an Authentication Challenge Message,
2. Upon receiving this message, the mobile station sends a Authentication Challenge Response Message, and
3. That the Unique Challenge-Response Procedure is successful.
n. End the call.
o. Instruct the base station to initiate a Unique Challenge-Response Procedure on the f/r-csch.
p. Verify the following:
1. The base station sends an Authentication Challenge Message,
2. Upon receiving this message, the mobile station sends a Authentication Challenge Response Message, and
3. That the Unique Challenge-Response Procedure is successful.
q. Repeat steps c through p but with the following exception:
1. In step d, setup a call and initiate a Shared Secret Data update on the f/r-dsch, and then end the call.
6.2.5 Minimum Standard
The mobile station shall comply with the requirements in the following steps: Step e, h, k, m, p, q.
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
6.3 Mismatched A-Keys 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
6.3.1 Definition
This test verifies that when there is an A_KEY mismatch, authentication of registrations, originations, terminations, and Unique Challenge-Response procedures will fail.
6.3.2 Traceability (See [4])
2.3.12.1.4 Unique Challenge-Response Procedure
2.3.12.1.5 Updating the Shared Secret Data (SSD)
2.7.1.3.2.6 Authentication Challenge Response Message
2.7.2.3.2.2 Authentication Challenge Response Message (r-dsch)
3.7.2.3.2.10 Authentication Challenge Message (f-csch)
3.7.2.3.2.1 SSD Update Message (f-csch)
3.7.3.3.2.2 Authentication Challenge Message (f-dsch)
3.7.3.3.2.13 SSD Update Message (f-dsch)
6.3.3 Call Flow Example(s)
None
6.3.4 Method of Measurement
a. Connect the base station and mobile station as shown in Annex A Figure A-1.
b. Power on the mobile station.
c. Initialize the A-Key to the same value in the mobile station and base station.
d. Instruct the base station to initiate a Shared Secret Data update on the f/r-csch.
e. Setup a mobile station originated call.
f. Verify user data in both directions.
g. End the call.
h. Change the A-Key in the mobile station.
i. Ensure timer-based registration is enabled with the registration period (REG_PRD) set to 29.
j. Wait for the mobile station to send a Registration Message with REG_TYPE set to ‘0000’ (i.e. timer-based registration).
k. Verify the Registration Message includes AUTHR, COUNT and RANDC.
l. Verify registration authentication fails at the base station due to an AUTHR mismatch.
m. Setup a mobile station originated call.
n. Verify that the call request was denied.
6-4
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
o. Setup a mobile station terminated call.
p. Verify the call fails due to an AUTHR mismatch.
q. Initiate at the base station a Shared Secret Data update on the f-csch.
r. Verify the SSD Update fails with an AUTHBS mismatch.
s. Initiate at the base station a Unique Challenge-Response Procedure on the f-csch.
t. Verify the Unique Challenge-Response Procedure fails with an AUTHU mismatch.
6.3.5 Minimum Standard
The mobile station shall comply with the requirements in the following steps: Step f, k, n, p, r, t.
The base station shall comply with the requirements in the following steps: Step f, l, p, r, t.
6.4 Activating Voice Privacy on Call Setup
6.4.1 Definition
This test verifies that Voice Privacy can be activated at call setup by the mobile station subscriber.
6.4.2 Traceability: (See [4])
2.3.12.3 (MS) Voice Privacy
2.6.4.1.6 (MS) Long Code Transition Request Processing
2.7.1.3.2.4 Origination Message
2.7.1.3.2.5 Page Response Message
2.7.3 (Mobile Station) Orders
3.3.3 (Base Station) Voice Privacy
3.6.4.1.5 (Base Station) Long Code Transition Request Processing
3.6.4.3 Traffic Channel Substate
3.6.4.4 Release Substate
3.7.4 (Base Station) Orders
6.4.3 Call Flow Example(s)
None
6.4.4 Method of Measurement
a. Connect the base station and mobile station as shown in Annex A Figure A-1.
b. Ensure authentication is enabled. Verify the AUTH field of the Access Parameters Message is set to ‘01’ or the ANSI-41 RAND Message is being transmitted.
c. Power on the mobile station.
6-5
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
33
d. Enable Voice Privacy in the mobile station and configure the base station to use voice privacy.
e. Setup a mobile station originated call, and verify in the Origination Message the Voice Privacy Mode Indicator (PM) is set to '1'.
f. Instruct the base station to send a Long Code Transition Request Order (ORDQ='00000001') on the f-dsch.
g. Verify the mobile station responds with a Long Code Transition Response Order (ORDQ='00000011')
h. If supported on the user interface, verify the mobile station indicates to the user that Voice Privacy is active.
i. Verify that correct user data is received in both directions.
j. End the call.
k. Setup a mobile station terminated call, and verify in the Page Response Message the voice privacy indicator (PM) is set to ‘1’ then repeat steps f through j.
6.4.5 Minimum Standard
The mobile station shall comply with the requirements in the following steps: Step e, g, h, i, k.
The base station shall comply with the requirements in the following steps: Step b, i.
6.5 Activating Voice Privacy at the Mobile Station When a Call Is Active
6.5.1 Definition
This test verifies that Voice Privacy can be activated at the mobile station when a call is active.
6.5.2 Traceability (See [4])
2.3.12.3 (Mobile Station) Voice Privacy
2.6.4.1.6 Long Code Transition Request Processing
2.7.1.3.2.4 Origination Message
2.7.1.3.2.5 Page Response Message
2.7.3 (Mobile Station) Orders
3.3.3 (Base Station) Voice Privacy
3.6.4.1.5 (Base Station) Long Code Transition Request Processing
3.6.4.3.1 Traffic Channel Substate
3.6.4.4 Release Substate
3.7.4 (Base Station) Orders
6.5.3 Call Flow Example(s)
None
6-6
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
6.5.4 Method of Measurement
a. Connect the base station and mobile station as shown in Annex A Figure A-1.
b. Configure the base station to use Voice Privacy.
c. Ensure authentication is enabled. Verify the AUTH field of the Access Parameters Message is set to ‘01’ or the ANSI-41 RAND Message is being transmitted.
d. Power on the mobile station.
e. Setup a mobile station originated call.
f. Enable voice privacy at the mobile station. Verify the mobile station sends a Long Code Transition Request Order with ORDQ set to ‘00000001’.
g. Verify the base station responds by sending a Long Code Transition Request Order with ORDQ set to ‘00000001’.
h. Verify the mobile station responds with a Long Code Transition Response Order (ORDQ='00000011').
i. If supported on the user interface, verify the mobile station indicates Voice Privacy is active.
j. Verify that correct user data is received in both directions.
k. End the call.
6.5.5 Minimum Standard
The mobile station shall comply with the requirements in the following steps: Step f, h, i, j.
The base station shall comply with the requirements in the following steps: Step c, g, j.
6.6 Signaling Message Encryption on Forward Traffic Channel
6.6.1 Definition
This test verifies that Signaling Message Encryption on f-dsch is performed correctly.
6.6.2 Traceability (See [4])
2.3.12.2 (Mobile Station) Signaling Message Encryption
2.7.4.4 (Mobile Station) Calling Party Number
3.3.2 (Base Station) Encryption
3.7.2.3.2.8 Channel Assignment Message (f-csch)
3.7.3.3.2.3 Alert With Information Message (f-dsch)
3.7.5.3 (Base Station) Calling Party Number
6.6.3 Call Flow Example(s)
None
6-7
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
33
6.6.4 Method of Measurement
a. Connect the base station and mobile station as shown in Annex A Figure A-1.
b. Activate the Calling Party Number (CPN) feature for the mobile station subscriber.
c. Ensure authentication is enabled. Verify the AUTH field of the Access Parameters Message is set to ‘01’ or the ANSI-41 RAND Message is being transmitted.
d. Power on the mobile station.
e. Enable Signaling Message Encryption on the base station.
f. Setup a mobile station terminated call.
g. Verify the ENCRYPT_MODE field is set to '01' or ‘10’ in the transmitted Channel Assignment Message or Extended Channel Assignment Message.
h. Verify the following:
1. Required fields in the appropriate messages are encrypted and can be correctly decrypted. For example, certain fields of the Alert With Information Message will be encrypted; but verification can be done on other messages as well.
2. The ENCRYPTION field in these messages is set to the same value as the ENCRYPT_MODE field received in the Channel Assignment Message or Extended Channel Assignment Message.
i. Verify the CPN is displayed on the mobile station during the alerting state.
j. Verify that correct user data is received in both directions.
k. End the call.
6.6.5 Minimum Standard
The mobile station shall comply with the requirements in the following steps: Step h, i, j.
The base station shall comply with the requirements in the following steps: Step c, g, h, j.
6.7 Signaling Message Encryption on Reverse Traffic Channel
6.7.1 Definition
This test verifies that Signaling Message Encryption on the r-dsch is performed correctly.
6.7.2 Traceability (See [4])
2.3.12.2 (Mobile Station) Signaling Message Encryption
2.7.2.3.2.7 Send Burst DTMF Message
3.3.2 (Base Station) Encryption
3.7.2.3.2.8 Channel Assignment Message (f-csch)
6.7.3 Call Flow Example(s)
None
6-8
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
33
34
6.7.4 Method of Measurement
a. Connect the base station and mobile station as shown in Annex A Figure A-1.
b. Ensure authentication is enabled. Verify the AUTH field of the Access Parameters Message is set to ‘01’ or the ANSI-41 RAND Message is being transmitted.
c. Power on the mobile station.
d. Instruct the mobile station to send a Send Burst DTMF Message.
e. Enable Signaling Message Encryption on the base station.
f. Setup a mobile station call to a voice mail system or a paging system.
g. Verify the ENCRYPT_MODE field is set to '01' or ‘10’ in the transmitted Channel Assignment Message or Extended Channel Assignment Message.
h. Verify the following:
1. Required fields in the appropriate messages are encrypted and can be correctly decrypted. For example, certain fields of the Burst DTMF Message will be encrypted; but verification can be done on other messages as well.
2. The ENCRYPTION field in these messages is set to the same value as the ENCRYPT_MODE field received in the Channel Assignment Message or Extended Channel Assignment Message.
i. Enter the appropriate pin code as burst DTMF tones.
j. Verify that either the voice mail system recognizes the DTMF tones and plays the message back, or that the paging system accepts the pin and sends out the page. Alternative procedures may be used to verify correct behavior.
k. End the call.
6.7.5 Minimum Standard
The mobile station shall comply with the requirements in the following steps: Step h.
The base station shall comply with the requirements in the following steps: Step b, g, h, j.
6.8 Hard Handoffs between Base Stations with Signaling Message Encryption Active
6.8.1 Definition
This test verifies that when Signaling Message Encryption is used, the new base station activates correct encryption upon handoff.
6.8.2 Traceability (See [4])
2.3.12.2 (Mobile Station) Signaling Message Encryption
2.6.6.2.8 CDMA-to-CDMA Hard Handoff
2.7.4.4 (Mobile Station) Calling Party Number.
3.3.2 (Base Station) Encryption
6-9
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 33 34
3.6.6.2.2.2 Extended Handoff Direction Message (call processing)
3.6.6.2.2.10 General Handoff Direction Message (call processing)
3.6.6.2.2.11 Universal Handoff Direction Message (call processing)
3.7.2.3.2.8 Channel Assignment Message (f-csch)
3.7.3.3.2.14 Flash With Information Message (f-dsch)
3.7.3.3.2.17 Extended Handoff Direction Message (f-dsch)
3.7.3.3.2.31 General Handoff Direction Message (f-dsch)
3.7.3.3.2.36 Universal Handoff Direction Message (f-dsch)
3.7.5.3 (Base Station) Calling Party Number
6.8.3 Call Flow Example(s)
None
6.8.4 Method of Measurement
a. Connect the base station and mobile station as shown in Annex A Figure A-5.
b. Activate Call Waiting and Caller ID on base station 2.
c. Ensure authentication is enabled. Verify the AUTH field of the Access Parameters Message is set to ‘01’ or the ANSI-41 RAND Message is being transmitted.
d. Power on the mobile station.
e. Enable Signaling Message Encryption on both base stations.
f. Setup a mobile station originated call.
g. Verify ENCRYPT_MODE field is set to '01' or ‘10’ in the transmitted Channel Assignment Message or Extended Channel Assignment Message.
h. Verify user data in both directions.
i. Cause a hard handoff from base station 1 to base station 2.
j. Verify ENCRYPT_MODE field is set to '01’ or ‘10’ in the transmitted Extended Handoff Direction Message, General Handoff Direction Message, or Universal Handoff Direction Message.
k. Setup another call to the mobile station and listen for the Call Waiting tone.
l. Verify the following:
1. Required fields in the appropriate messages are encrypted and can be correctly decrypted. For example, certain fields of the Flash With Information Message will be encrypted; but verification can be done on other messages as well.
2. The ENCRYPTION field in these messages is set to the same value as the ENCRYPT_MODE field received in the Channel Assignment Message or Extended Channel Assignment Message.
6-10
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
m. Verify that Calling Party Number (CPN) information is displayed on the mobile station during alerting state.
n. Verify user data in both directions.
o. End the call.
6.8.5 Minimum Standard
The mobile station shall comply with the requirements in the following steps: Step h, l, m, n.
The base station shall comply with the requirements in the following steps: Step c, g, h, j, l, n.
6.9 Authentication upon Originations
6.9.1 Definition
This test verifies the mobile station can successfully Authenticate upon an origination.
6.9.2 Traceability (See [4])
2.3.12.1.5 Updating the Shared Secret Data (SSD)
2.7.1.3.2.6 Authentication Challenge Response Message
2.7.2.3.2.2 Authentication Challenge Response Message (r-dsch)
3.7.2.3.2.10 Authentication Challenge Message (f-csch)
3.7.2.3.2.11 SSD Update Message (f-csch)
3.7.3.3.2.2 Authentication Challenge Message (f-dsch)
3.7.3.3.2.13 SSD Update Message (f-dsch)
6.9.3 Call Flow Example(s)
None
6.9.4 Method of Measurement
a. Connect the base station and mobile station as shown in Annex A Figure A-5.
b. Power on the mobile station.
c. Initialize the A-Key to the same value in both the mobile station and base station.
d. Instruct the base station to initiate a Shared Secret Data update on the f/r-csch.
e. Verify the SSD Update was successful.
f. Setup a mobile station originated call (seven digits).
g. Verify user data in both directions and that authentication is successful.
h. End the call.
i. Setup a mobile station originated call (three digits such as *73).
j. Verify user data in both directions and that authentication is successful.
6-11
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
k. End the call.
l. Setup a mobile station originated call (four digits such as *123).
m. Verify user data in both directions and that authentication is successful.
n. End the call.
6.9.5 Minimum Standard
The mobile station shall comply with the requirements in the following steps: Step e, g, j, and m.
The base station shall comply with the requirements in the following steps: Step e, g, j, and m.
6.10 Hard Handoff from CDMA to Analog with Signaling Message Encryption Active
6.10.1 Definition
This test verifies that when Signaling Message Encryption is used, the new base station activates Analog Signaling Message Encryption upon handoff.
6.10.2 Traceability (See [4])
2.3.12.2 (Mobile Station) Signaling Message Encryption
2.6.6.2.9 CDMA-Analog HO
2.7.4.4 (Mobile Station) Calling Party Number
3.3.2 (Base Station) Encryption
3.6.4.3 Traffic Channel Substate
3.7.2.3.2.8 Channel Assignment Message (f-csch)
3.7.3.3.2.3 Alert with Information Message (f-dsch)
3.7.3.3.2.6 Analog Handoff Direction Message
3.7.5.3 (Base Station) Calling Party Number.
6.10.3 Call Flow Example(s)
None
6.10.4 Method of Measurement
a. Connect the base station and mobile station as shown in Annex A Figure A-5.
b. Activate Call Waiting and Caller ID on Base station 2.
c. Ensure authentication is enabled. Verify the AUTH field of the Access Parameters Message is set to ‘01’ or the ANSI-41 RAND Message is being transmitted.
d. Power on the mobile station.
e. Enable Signaling Message Encryption on both base stations.
f. Setup a mobile station originated call.
6-12
C.S0044-0 v1.0
1 2
3
4
5
6
7
8 9
10
11
12
13
14
15
16
g. Verify ENCRYPT_MODE field is set to '01' or ‘10’ in the Channel Assignment Message or Extended Channel Assignment Message transmitted.
h. Verify that correct user data is received in both directions.
i. Cause a CDMA to analog hard handoff from base station 1 to base station 2.
j. Verify ENCRYPT_MODE='01' and MEM=’1’ in the Analog Handoff Direction Message.
k. Setup another call to the mobile station, and listen for the Call Waiting tone.
l. Verify base station 2 sends an encrypted Alert with Information Message (analog).
m. Verify that the Calling Party Number (CPN) information is displayed on the mobile station during the alerting state.
n. Verify that correct user data is received in both directions.
o. End the call.
6.10.5 Minimum Standard
The mobile station shall comply with the requirements in the following steps: Step h, m, n.
The base station shall comply with the requirements in the following steps: Step c, g, h, j, l, n.
6-13
C.S0044-0 v1.0
7 SERVICE REDIRECTION TEST CASES 1
2
3
4 5
6
7
8
9
10
11
12
13
14
15 16
17
18
19
7.1 Global Service Redirection between Band Classes
7.1.1 Definition
This test verifies that when a mobile station receives a Global Service Redirection Message directing it to another band class, the mobile station acquires the appropriate system.
7.1.2 Traceability (see [4])
2.6.1.1.2 System Selection Using Current Redirection Criteria
2.6.2.2 Response to Overhead Information Operation
2.6.2.2.6 Global Service Redirection Message
3.7.2.3.2.1 System Parameters Message
3.7.2.3.2.18 Global Service Redirection Message
7.1.3 Call Flow Example(s)
None
7.1.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-5. For this test case, base station 1 and base station 2 are in different band classes.
b. Verify the mobile station is operating in the Mobile Station Idle State on base station 1.
c. Ensure that the base station sends a Global Service Redirection Message with:
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 21
22
d. Verify the mobile station enters the System Determination Substate of the Mobile Station Initialization State and acquires the system to which it was redirected.
e. Setup a mobile station originated call. Verify user traffic in both directions.
7-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
33
f. End the call.
g. Repeat steps c through f with the mobile station operating in the Mobile Station Idle State on base station 2.
h. Repeat steps b and c with the mobile station operating in the Mobile Station Idle State on base station 1 setting EXCL_P_REV_MS = ‘1’ in the Global Service Redirection Message.
i. Verify the following:
1. If MOB_P_REV is less than six, verify the mobile station enters the System Determination Substate of the Mobile Station Initialization State and acquires the system to which it was redirected.
2. If MOB_P_REV is greater than or equal to six, verify the mobile station remains in the Mobile Station Idle State on the current system.
7.1.5 Minimum Standard
The mobile station shall comply with steps d, e, and i.
7.2 Global Service Redirection between CDMA and a Non-CDMA System
7.2.1 Definition
This test verifies that when a mobile station receives a Global Service Redirection Message directing it from CDMA to a Non-CDMA system, the mobile station acquires that system. The mobile station should only be redirected to Non-CDMA systems it supports. An example would be an analog system defined in [21].
7.2.2 Traceability (see [4])
2.6.1.1.2 System Selection Using Current Redirection Criteria
2.6.2.2 Response to Overhead Information Operation
2.6.2.2.6 Global Service Redirection Message
3.7.2.3.2.1 System Parameters Message
3.7.2.3.2.18 Global Service Redirection Message
7.2.3 Call Flow Example(s)
None
7.2.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-5. For this test case, base station 1 is a CDMA base station and base station 2 is a Non-CDMA base station.
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 2
c. Send a Global Service Redirection Message from the current base station directing the mobile station to the non-CDMA base station with the following parameters:
Field Value
REDIRECT_ACCOLC ACCOLCp
EXCL_P_REV_MS ‘0’
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
EXPECTED_SID Target SID
IGNORE_CDMA ‘0’
SYS_ORDERING ‘000’
MAX_REDIRECT_DELAY ‘00000’
3
4 5
6
7
8 9
10
11
12 13 14
15 16
17
18
d. Verify the mobile station enters the System Determination Substate of the Mobile Station Initialization State and acquires the system to which it was redirected.
e. Setup a mobile station originated call. Verify user traffic in both directions.
f. End the call.
g. Repeat steps b and c with the mobile station operating in the Mobile Station Idle State on base station 1 setting EXCL_P_REV_MS = ‘1’ in the Global Service Redirection Message.
h. Verify the following:
1. If MOB_P_REV is less than six, verify the mobile station enters the System Determination Substate of the Mobile Station Initialization State and acquires the system to which it was redirected.
2. If MOB_P_REV is greater than or equal to six, verify the mobile station remains in the Mobile Station Idle State on the current system.
7.2.5 Minimum Standard
The mobile station shall comply with steps d, eand h.
7-3
C.S0044-0 v1.0
7.3 Global Service Redirection between Channels in the Same Band Class 1
2
3 4 5
6
7
8
9
10
11
12
13
14
15 16 17
18
19
20
7.3.1 Definition
This test verifies that when a mobile station receives a Global Service Redirection Message directing it to a different channel in the same band class, the mobile station acquires the appropriate system.
7.3.2 Traceability (see [4])
2.6.1.1.2 System Selection Using Current Redirection Criteria
2.6.2.2 Response to Overhead Information Operation
2.6.2.2.6 Global Service Redirection Message
3.7.2.3.2.1 System Parameters Message
3.7.2.3.2.18 Global Service Redirection Message
7.3.3 Call Flow Example(s)
None
7.3.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-5. For this test case, base station 1 and base station 2 are in the same band class with different CDMA channels.
b. Verify the mobile station is operating in the Mobile Station Idle State on base station 1.
c. Send a Global Service Redirection Message from the current base station with:
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)
21
22 23
24
d. Verify the mobile station enters the System Determination Substate of the Mobile Station Initialization State and acquires the system to which it was redirected.
e. Setup a mobile station originated call. Verify user traffic in both directions.
7-4
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
33
34
f. End the call.
g. Remove the channel for base station 2 from the mobiles station’s preferred roaming list and repeat steps b through f.
h. Repeat steps b and c with the mobile station operating in the Mobile Station Idle State on base station 1 setting EXCL_P_REV_MS = ‘1’ in the Global Service Redirection Message.
i. Verify the following:
1. If MOB_P_REV is less than six, verify the mobile station enters the System Determination Substate of the Mobile Station Initialization State and acquires the system to which it was redirected.
2. If MOB_P_REV is greater than or equal to six, verify the mobile station remains in the Mobile Station Idle State on the current system.
7.3.5 Minimum Standard
The mobile station shall comply with steps d, eand i.
7.4 Service Redirection between Band Classes
7.4.1 Definition
This test verifies Network Directed System Selection (NDSS) functions correctly. This test verifies that a mobile station is capable of being redirected between band classes when the Service Redirection Message is sent on the f-csch or on the f-dsch prior to user traffic being transmitted and the call completes on the new system without user interaction.
7.4.2 Traceability (see [4])
2.6.1.1.2 System Selection Using Current Redirection Criteria
2.6.2.4 Mobile Station Order and Message Processing Operation
2.6.3.5 Mobile Station Origination Attempt Substate
3.6.2.3 Mobile Station Directed Messages
3.7.2.3.2.16 Service Redirection Message {f-csch}
3.7.3.3.2.23 Service Redirection Message {f-dsch}
7.4.3 Call Flow Example(s)
None
7.4.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-5. For this test case, base station 1 and base station 2 are in different band classes.
b. Verify the mobile station is operating in the Mobile Station Idle State on base station 1.
c. Instruct the mobile station to send an Origination Message to the base station.
7-5
C.S0044-0 v1.0
1 2
d. Instruct the base station to send a Service Redirection Message with the following information to the mobile station on the f-csch or on the f-dsch.
Field Value
REDIRECT_TYPE ‘1’ (NDSS redirection)
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)
3
4 5
6
7 8
9
10
11
12
13 14 15 16 17
18
19
20
21
22
23
24
e. Verify the mobile station acquires the target base station and the call completes without additional user interaction and user traffic is present.
f. End the call.
g. Repeat steps c through f with the mobile station operating in the Idle State on base station 2.
7.4.5 Minimum Standard
The mobile station shall comply with steps e and g.
7.5 Service Redirection between CDMA and a Non-CDMA System
7.5.1 Definition
This test verifies that a mobile station is capable of being redirected from a CDMA system to a non-CDMA system when the Service Redirection Message is sent on the f-csch or on the f-dsch prior to user traffic being transmitted, and the call completes on the new system without user interaction. The mobile station should only be redirected to Non-CDMA systems it supports. An example of a non-CDMA system is an analog system defined in [21].
7.5.2 Traceability (see [4])
2.6.1.1.2 System Selection Using Current Redirection Criteria
2.6.2.4 Mobile Station Order and Message Processing Operation
2.6.3.5 Mobile Station Origination Attempt Substate
3.6.2.3 Mobile Station Directed Messages
3.7.2.3.2.16 Service Redirection Message {f-csch}
3.7.3.3.2.23 Service Redirection Message {f-dsch}
7-6
C.S0044-0 v1.0
1
2
3
4 5 6
7
8
9 10
11
7.5.3 Call Flow Example(s)
None
7.5.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-5. For this test case, base station 1 is a CDMA base station and base station 2 is a Non-CDMA base station.
b. Ensure the mobile station is operating in the Mobile Station Idle State on base station 1.
c. Instruct the mobile station to send an Origination Message to the base station.
d. Instruct the base station to send a Service Redirection Message with the following information to the mobile station on the f-csch or on the f-dsch.
Field Value
RETURN_IF_FAIL ‘0’
REDIRECT_TYPE ‘1’ (NDSS redirection)
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
EXPECTED_SID Target SID
IGNORE_CDMA ‘0’
SYS_ORDERING ‘000’
12
13 14
15
16 17
18 19
20
e. Verify the mobile station acquires the target base station and the call completes without additional user interaction and user traffic is present.
f. End the call.
g. For RECORD_TYPE=’00000001’, repeat steps a through e setting IGNORE_CDMA = ‘1’ in the Service Redirection Message:
h. Send the CDMA Capability Message from base station 2 indicating CDMA is available (i. e. CDMA_AVAIL set to ‘1’).
i. End the call.
7-7
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
j. Verify the mobile station remains in the Idle State on the non-CDMA system and does not attempt to re-acquire CDMA.
7.5.5 Minimum Standard
The mobile station shall comply with steps e, g and j.
7.6 Service Redirection between Channels in the Same Band Class
7.6.1 Definition
This test verifies Network Directed System Selection (NDSS) functions correctly. This test verifies that a mobile station is capable of being redirected between channels in the same band class when the Service Redirection Message is sent on the f-csch or on the f-dsch prior to user traffic being transmitted and the call completes on the new system without additional user interaction.
7.6.2 Traceability (see [4])
2.6.1.1.2 System Selection Using Current Redirection Criteria
2.6.2.4 Mobile Station Order and Message Processing Operation
2.6.3.5 Mobile Station Origination Attempt Substate
3.6.2.3 Mobile Station Directed Messages
3.7.2.3.2.16 Service Redirection Message {f-csch}
3.7.3.3.2.23 Service Redirection Message {f-dsch}
7.6.3 Call Flow Example(s)
None
7.6.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-5. For this test case, base station 1 and base station 2 have different CDMA channels in the same band class.
b. Verify the mobile station is operating in the Mobile Station Idle State on base station 1.
c. Instruct the mobile station to send an Origination Message to the base station.
d. Instruct the base station to send a Service Redirection Message with the following information to the mobile station on the f-csch or on the f-dsch.
7-8
C.S0044-0 v1.0
Field Value
RETURN_IF_FAIL ‘0’
REDIRECT_TYPE ‘1’ (NDSS redirection)
RECORD_TYPE ‘00000010’
EXPECTED_SID Target SID
EXPECTED_NID Target NID
NUM_CHAN Number of Channels
CDMA_CHAN Target Channel(s)
1 2
3
4 5
6 7
8 9
10
11
12
13
14 15
16
17
18
19
20
21
22
23
24
e. Verify the mobile station acquires the target base station and the call completes without additional user interaction and user traffic is present.
f. End the call.
g. Repeat steps c through f with the mobile station operating in the Idle State on base station 2.
h. Repeat steps b through d ensuring the mobile station cannot re-acquire base station 2 and setting RETURN_IF_FAIL = ‘1’ in the Service Redirection Message:
i. Verify the mobile station returns to base station 1 after failing to acquire base station 2. The call may or may not complete depending on infrastructure implementation.
7.6.5 Minimum Standard
The mobile station shall comply with steps e, g, and i.
7.7 Extended Global Service Redirection between Band Classes
7.7.1 Definition
This test verifies that when a mobile station receives an Extended Global Service Redirection Message directing it to another band class, the mobile station acquires the appropriate system.
7.7.2 Traceability (see [4])
2.6.1.1.2 System Selection Using Current Redirection Criteria
2.6.2.2 Response to Overhead Information Operation
2.6.2.2.11 Extended Global Service Redirection Message
3.7.2.3.2.1 System Parameters Message
3.7.2.3.2.27 Extended Global Service Redirection Message
3.7.2.3.2.31 MC-RR Parameters Message
7.7.3 Call Flow Example(s)
None
7-9
C.S0044-0 v1.0
1
2 3
4
5 6
7.7.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-5. For this test case, base station 1 and base station 2 are in different band classes.
b. Verify the mobile station is operating in the Mobile Station Idle State on base station 1.
c. Send an Extended Global Service Redirection Message from the current base station with:
Field Value
REDIRECT_ACCOLC ACCOLCp
REDIRECT_P_REV_INCL ‘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)
7 8
9
10
11 12
13
14
15
16
17 18 19 20
21
22
23
24
d. Verify the mobile station enters the System Determination Substate of the Mobile Station Initialization State and acquires the system to which it was redirected.
e. Setup a mobile station originated call. Verify user traffic in both directions.
f. End the call.
g. Repeat steps c through f with the mobile station operating in the Mobile Station Idle State on base station 2.
7.7.5 Minimum Standard
The mobile station shall comply with steps d, e and g.
7.8 Extended Global Service Redirection between CDMA and a Non-CDMA System
7.8.1 Definition
This test verifies that when a mobile station receives an Extended Global Service Redirection Message directing it from CDMA to a Non-CDMA system, the mobile station acquires that system. The mobile station should only be redirected to Non-CDMA systems it supports. An example would be an analog system defined in [21].
7.8.2 Traceability (see [4])
2.6.1.1.2 System Selection Using Current Redirection Criteria
2.6.2.2 Response to Overhead Information Operation
2.6.2.2.11 Extended Global Service Redirection Message
7-10
C.S0044-0 v1.0
1
2
3
4
5
6
7 8 9
10
11 12 13 14
3.7.2.3.2.1 System Parameters Message
3.7.2.3.2.27 Extended Global Service Redirection Message
3.7.2.3.2.31 MC-RR Parameters Message
7.8.3 Call Flow Example(s)
None
7.8.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-5. For this test case, base station 1 is a CDMA base station and base station 2 is a Non-CDMA base station.
b. Ensure the mobile station is operating in the Mobile Station Idle State on base station 1.
c. Send an Extended Global Service Redirection Message from the current base station directing the mobile station to the non-CDMA base station with the following parameters:
Field Value
REDIRECT_ACCOLC ACCOLCp
REDIRECT_P_REV_INCL ‘0’
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
EXPECTED_SID Target SID
IGNORE_CDMA ‘0’
SYS_ORDERING ‘000’
MAX_REDIRECT_DELAY ‘00000’
15 16
17
18
d. Verify the mobile station enters the System Determination Substate of the Mobile Station Initialization State and acquires the system to which it was redirected.
e. Setup a mobile station originated call. Verify user traffic in both directions.
f. End the call.
7-11
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
7.8.5 Minimum Standard
The mobile station shall comply with steps d and e
7.9 Extended Global Service Redirection between Channels in the Same Band Class
7.9.1 Definition
This test verifies that when a mobile station receives an Extended Global Service Redirection Message directing it to a different channel in the same band class, the mobile station acquires the appropriate system.
7.9.2 Traceability (see [4])
2.6.1.1.2 System Selection Using Current Redirection Criteria
2.6.2.2 Response to Overhead Information Operation
2.6.2.2.11 Extended Global Service Redirection Message
3.7.2.3.2.1 System Parameters Message
3.7.2.3.2.27 Extended Global Service Redirection Message
3.7.2.3.2.31 MC-RR Parameters Message
7.9.3 Call Flow Example(s)
None
7.9.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-5. For this test case, base station 1 and base station 2 are in the same band class with different CDMA channels.
b. Verify the mobile station is operating in the Mobile Station Idle State on base station 1.
c. Send an Extended Global Service Redirection Message from the current base station with:
7-12
C.S0044-0 v1.0
Field Value
REDIRECT_ACCOLC ACCOLCp
REDIRECT_P_REV_INCL ‘0’
RECORD_TYPE ‘00000010’
EXPECTED_SID Target SID
EXPECTED_NID Target NID
NUM_CHAN Number of Channels
CDMA_CHAN Target Channel(s)
1 2
3
4
5 6
7
8
9
d. Verify the mobile station enters the System Determination Substate of the Mobile Station Initialization State and acquires the system to which it was redirected.
e. Setup a mobile station originated call. Verify user traffic in both directions.
f. End the call.
g. Remove the channel for base station 2 from the mobile station’s preferred roaming list and repeat steps b through f.
7.9.5 Minimum Standard
The mobile station shall comply with steps d and e.
7-13
C.S0044-0 v1.0
8 SHORT MESSAGE SERVICE 1
2
3
4
5
6 7
8
9
10
11 12
13
14
15
16
17
a. 18
19 20 21 22
23
24
25 26
27
8.1 Mobile Station Terminated SMS Tests
Unless otherwise noted, the following conditions apply for all tests in this section:
• Mobile station is capable of receiving short messages.
• The short message feature for the mobile station is activated.
• Base station has Power-up registration enabled by setting POWER-UP_REG = ‘1’ in the System Parameters Message or the ANSI-41 System Parameters Message.
• Transport Layer messages shall include the Bearer Reply Option.
8.1.1 Common Channel SMS Delivery
8.1.1.1 Definition
This test verifies that a short message can be sent to a mobile station in the Mobile Station Idle State.
8.1.1.2 Traceability (see [13])
2.4.1.1.1.1 Mobile SMS Message Termination
8.1.1.3 Call Flow Example(s)
None
8.1.1.4 Method of Measurement
Delete all outstanding short messages in the network for the mobile station.
b. Create a short message in the Message Center for the mobile station. Ensure that the short message length is less than the maximum allowed size on the Paging Channel or Forward Common Control Channel so that it can be sent to the mobile station using the Paging Channel or Forward Common Control Channel9.
c. Power on the mobile station and wait until it is in the Mobile Station Idle State.
d. Instruct the network to send the short message to the mobile station.
e. Verify the base station sends a Data Burst Message to the mobile station with the following field settings:
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
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
f. Upon receiving the Data Burst Message at the mobile station, verify the following:
1. The mobile station alerts the user for the incoming short message and correctly displays the received short message, when selected.
2. The mobile station transmits Data Burst Message on the Access Channel, Enhanced Access Channel or Reverse Common Control Channel to acknowledge the short message, indicating no error (i.e. contains a ‘Cause Codes’ parameter having ERROR_CLASS = ‘00’).
8.1.1.5 Minimum Standard
The mobile station shall comply with step f. The base station shall comply with step e.
8.1.2 Traffic Channel SMS Delivery
8.1.2.1 Definition
This test verifies that a short message, with length exceeding the maximum allowable length (configurable by the network) for Paging Channel or Forward Common Control Channel transport, is delivered to the mobile station over the Traffic Channel.
8.1.2.2 Traceability (see [13])
2.4.1.1.2.2 Mobile SMS Message Termination
2.4.2.1.2 Base Station Traffic Channel Procedures
8.1.2.3 Call Flow Example(s)
None
8.1.2.4 Method of Measurement
a. Delete all outstanding short messages in the network for the mobile station.
b. Create a short message in the Message Center for the mobile station. Ensure that the short message length is greater than the maximum length supported on the Paging Channel or Forward Common Control Channel .
c. Power on the mobile station and wait until it is in the Mobile Station Idle State.
d. Instruct the network to send the short message to the mobile station. Verify the following:
1. The base station does not send a Data Burst Message to the mobile station on the paging channel or Forward Common Control Channel.
8-2
C.S0044-0 v1.0
1 2
3 4 5
6
2. The base station sends a General Page Message with either service option 6 or service option 14.
3. After the mobile station enters the Conversation Substate, the base station sends a Data Burst Message to the mobile station with the following field settings:
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
7
8 9
10 11 12
13
14
15
16
17 18
19
20
21
22
23
24
25
26
27
e. Upon receiving the Data Burst Message at the mobile station, verify the following:
1. The mobile station alerts the user for the incoming short message and correctly displays the received short message, when selected.
2. The mobile station transmits a Data Burst Message on the Reverse Traffic Channel to acknowledge the short message, indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = ‘00’).
8.1.2.5 Minimum Standard
The mobile station shall comply with step e. The base station shall comply with step d.
8.1.3 Traffic Channel SMS Delivery while in Conversation
8.1.3.1 Definition
This test verifies a short message can be sent to a mobile station when it is already in the Conversation Substate.
8.1.3.2 Traceability (see [13])
2.4.1.1.2.2 Mobile SMS Message Termination
2.4.2.1.2 Base Station Traffic Channel Procedures
2.4.2.1.2.4 Mobile Station Message Termination in the Conversation Substate
8.1.3.3 Call Flow Example(s)
None
8.1.3.4 Method of Measurement
a. Delete all outstanding short messages in the network for the mobile station.
b. Setup a mobile station originated call.
8-3
C.S0044-0 v1.0
1 2
3
4 5
6
c. While the mobile station is in the Conversation Substate, create a short message in the Message Center for the mobile station.
d. Instruct the network to send the short message to the mobile station.
e. Verify the base station sends a Data Burst Message to the mobile station, with the following field settings:
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
f. Upon receiving the Data Burst Message at the mobile station, verify the following: 7
8 9
10 11 12 13
14
The mobile station shall comply with step f. The base station shall comply with step e. 15
16
17
18 19 20 21
22
23
24
25
26
27
1. The mobile station alerts the user for the incoming short message and correctly displays the received short message, when selected.
2. The mobile station transmits a Data Burst Message on the Reverse Traffic Channel to acknowledge the receipt of the short message and indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = ‘00’).
8.1.3.5 Minimum Standard
8.1.4 Delivery of Maximum Length Message
8.1.4.1 Definition
This test verifies the SMS transport layer capability to send to a mobile station a short message of the maximum size – the maximum size is the lesser of the maximum allowable length of the message center and the maximum length specified by the mobile station manufacturer. The test verifies delivery of the maximum length short message on the Traffic Channel.
8.1.4.2 Traceability (see [13])
2.4.2.1.2 Base Station Traffic Channel Procedures
3.4.2.1 SMS Point-to-Point Message
3.4.3.5 Bearer Reply Option
8.1.4.3 Call Flow Example(s)
None
8-4
C.S0044-0 v1.0
1
2
3
4
5
6 7
8
8.1.4.4 Method of Measurement
a. Clear all short messages stored in the mobile station.
b. Delete all outstanding short messages in the Network for the mobile station.
c. Create in the Message Center a maximum size short message for the mobile station.
d. Instruct the network to send the short message to the mobile station.
e. Verify the base station sends a Data Burst Message to the mobile station on the traffic channel, with the following field settings:
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
9
10 11
12 13 14 15
16
17
18
19
20 21
22
23
24
25
26
f. Upon receiving Data Burst Message at the mobile station, verify the following:
1. The mobile station alerts the user for the incoming short message and correctly displays the received short message, when selected.
2. The mobile station transmits a Data Burst Message on the Reverse Traffic Channel to acknowledge receipt of the short message and indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = ‘00’).
8.1.4.5 Minimum Standard
The mobile station shall comply with f. The base station shall comply with step e.
8.1.5 SMS Delivery Error - Mobile Station Short Message Buffer Full
8.1.5.1 Definition
This test verifies SMS transport layer acknowledgment capability by sending to the mobile station short messages until the mobile station short message buffer is full.
8.1.5.2 Traceability (see [13])
2.4.1.1.1.1 Mobile SMS Message Termination
2.4.2.1.1 Common Channel Procedures
3.4.2.1 SMS Point-to-Point Message
3.4.3.6 Cause Codes
8-5
C.S0044-0 v1.0
8.1.5.3 Call Flow Example(s) 1
2
3
4 5
6
7
8
9 10
11
Value
None
8.1.5.4 Method of Measurement
a. Clear all short messages from the mobile station to ensure that the short message buffer is empty.
b. Delete all outstanding short messages in the network for the mobile station.
c. Create in the Message Center a short message for the mobile station.
d. Instruct the network to send the short message to the mobile station.
e. Verify the base station sends a Data Burst Message to the mobile station, with the following field settings:
Field
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
12 13 14
15
16
17 18
19
f. Upon receiving the Data Burst Message, the mobile station shall transmit a Data Burst Message to acknowledge receipt of the short message and indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = ‘00’).
g. Repeat step c until the mobile station short message buffer is full.
h. Instruct the network to send one additional short message to the mobile station.
i. Verify the base station sends a Data Burst Message to the mobile station, with the following field settings:
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
1 (‘00000001’)
NUM_FIELDS Greater than 0
NUM_MSGS
j. Upon receiving the Data Burst Message sent in step i, verify that the mobile station transmits a Data Burst Message on the Access Channel, Enhanced Access Channel or
20 21
8-6
C.S0044-0 v1.0
Reverse Common Control Channel to acknowledge the short message and indicating temporary error (with ERROR_CLASS = ‘10’ and CAUSE_CODE=35.
1 2
3
4
5
6
7 8 9
10
11
12
8.1.6.3 Call Flow Example(s) 13
14
15
16
17
18 19
20 21
22 23
24
25
26
27 28 29 30
31 32
33
8.1.5.5 Minimum Standard
The mobile station shall comply with step j. The base station shall comply with steps e and i.
8.1.6 Voice Mail Notification
8.1.6.1 Definition
Voice Mail Notification (VMN) notifies the subscriber of voice mail messages using the Voice Mail Notification teleservice and Short Message Service protocol. Notification can be a tone, light, or display, and is manufacturer dependent.
8.1.6.2 Traceability (see [13])
4.3.5 Voice Mail Notification (VMN)
4.5.12 Number of Messages
None
8.1.6.4 Method of Measurement
a. Configure the system as shown in Figure A-3.
b. Power on the mobile station and wait until it is in the Mobile Station Idle State.
c. Instruct the network to send a Voice Mail Notification (corresponds to an SMS Point-to-Point message) to the mobile station.
d. Verify that the base station sends a Data Burst Message, with the BURST_TYPE field set to ‘000011’, with the following parameters settings:
1. Teleservice Identifier parameter, IDENTIFIER = Voice Mail Notification (0x1003).
2. Message Identifier sub-parameter, MESSAGE_TYPE = Deliver (0x1).
3. Number of Messages sub-parameter, MESSAGE_CT = 99.
e. Upon receiving the Data Burst Message, verify the following:
1. The mobile station transmits an SMS Acknowledge message via Data Burst Message on the Access Channel, Enhanced Access Channel or Reverse Common Control Channel to acknowledge the short message, indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = ‘00’).
2. The mobile station indicates to the user the number of voice mail messages available as indicated by the network.
f. Repeat step c and d, setting the MESSAGE_CT = 0.
8-7
C.S0044-0 v1.0
g. Upon receiving the Data Burst Message, verify that the mobile station indicates to the user no voice mail messages are available.
1 2
3
4
5
6 7
8
9
10 11 12 13 14
15
16
17
8.2.1.3 Call Flow Example(s) 18
19
20
a. 21
22 23 24
25
26 27 28
29
Value
8.1.6.5 Minimum Standard
The mobile station shall comply with steps e and g. The base station shall comply with step d.
8.2 Mobile Station Originated SMS Tests
This section is to be performed on mobile stations that support mobile station originated short messaging.
8.2.1 Common Channel SMS Delivery
8.2.1.1 Definition
This test verifies that a short message can be sent to the Message Center (MC) by a mobile station using the Access Channel, Enhanced Access Channel or Reverse Common Control Channel. The short message length chosen for this test is such that it doesn’t exceed the maximum message length allowed on the Access Channel, Enhanced Access Channel or Reverse Common Control Channel.
8.2.1.2 Traceability (see [13])
2.4.1.1.1.2 Mobile station SMS Message Origination
2.4.2.1.1.1 Mobile station SMS Message Origination
None
8.2.1.4 Method of Measurement
Power on the mobile station and wait until it is in the Mobile Station Idle State.
b. Create a short message at the mobile station, of a length smaller than the maximum message length allowed on the Access Channel, Enhanced Access Channel or Reverse Common Control Channel 10.
c. Instruct the mobile station to send the short message to the network.
d. Verify the mobile station sends a Data Burst Message to the base station over the Access Channel, Enhanced Access Channel or Reverse Common Control Channel with the following field settings:
Field
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’)
NUM_FIELDS Greater than 0
e. Verify that the base station receives the short message and sends a layer 2 acknowledgement to the mobile station.
1 2
3
The mobile station shall comply with step d. 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
8.2.1.5 Minimum Standard
8.2.2 Traffic Channel SMS Delivery
8.2.2.1 Definition
This test verifies a mobile station in the Mobile Station Idle State can originate a short message of length larger than the maximum length allowed on the Access Channel, Enhanced Access Channel or Reverse Common Control Channel and that the message is delivered to the Message Center over the Traffic Channel.
8.2.2.2 Traceability (see [13]
2.4.1.1.1.2 Mobile SMS Message Origination
2.4.2.1.2 Base Station Traffic Channel Procedures
8.2.2.3 Call Flow Example(s)
None
8.2.2.4 Method of Measurement
a. Power on the mobile station and wait until it is in the Mobile Station Idle State.
b. Create a short message at the mobile station, of a length larger than the maximum message length allowed on the Access Channel, Enhanced Access Channel or Reverse Common Control Channel.
c. Instruct the mobile station to send the short message to the network.
d. Verify the following:
1. The mobile station does not send the Data Burst Message over the Access Channel, Enhanced Access Channel or Reverse Common Control Channel
2. The mobile station sends an Origination Message to originate as SMS call with the SERVICE_OPTION field set to either 6 or 14.
3. After entering the Conversation Substate, the mobile station sends a Data Burst Message, with the following fields set as follows:
8-9
C.S0044-0 v1.0
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
1
2
3 4
5
6
8.2.3 Traffic Channel SMS Delivery while in Conversation 7
8
9 10
11
12
13
14
15
16
17
18
19
20
21
22 23
24
e. Verify the Message Center receives the short message.
f. Verify that upon sending the short message, the mobile station sends a Release Order to release the dedicated channels.
8.2.2.5 Minimum Standard
The mobile station shall comply with steps d and f.
8.2.3.1 Definition
This test verifies that a short message can be sent by the mobile station when it is in the Conversation Substate.
8.2.3.2 Traceability (see [13])
2.4.1.1.1.2 Mobile station SMS Message Origination
2.4.1.1.2.4 Mobile station Station Message Origination in the Conversation Substate
2.4.2.1.2 Base Station Traffic Channel Procedures
8.2.3.3 Call Flow Example(s)
None
8.2.3.4 Method of Measurement
a. Setup a mobile station originated call.
b. While mobile station is in the Conversation Substate, create a short message.
c. Instruct the mobile station to send the short message to the network.
d. Verify the mobile station sends a Data Burst Message, with the following fields set as follows:
Field Value
8-10
C.S0044-0 v1.0
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
1
2
3 4
5
6
7
8
9 10 11
12
13
14
15
3.4.3.6 Cause Codes 16
17
18
19
20
21 22
23
24 25
26
Value
e. Verify the Message Center receives the short message.
f. Verify that upon sending the short message, the mobile station does not attempt to release the dedicated channels.
8.2.3.5 Minimum Standard
The mobile station shall comply with steps d and f.
8.2.4 Unknown Destination Address
8.2.4.1 Definition
This test verifies the base station can process a mobile station originated short message with an unknown destination address and will inform the mobile station regarding an unknown destination address.
8.2.4.2 Traceability (see [13])
2.4.1.1.1.2 Mobile station SMS Message Origination
3.4.2.1 SMS Point-to-Point Message
8.2.4.3 Call Flow Example(s)
None
8.2.4.4 Method of Measurement
a. Power on the mobile station and wait until it is in the Mobile Station Idle State.
b. Create a short message at the mobile station, but with an unknown address in the destination address field.
c. Instruct the mobile station to send the short message to the base station.
d. Verify the mobile station sends a Data Burst Message, with the following fields set as follows:
Field
8-11
C.S0044-0 v1.0
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
e. Verify the Message Center receives the short message and the base station sends a Data Burst Message to the mobile station indicating ‘an unknown address’
1 2
3
The mobile station shall comply with step d. The base station shall comply with step e. 4
5
6
7 8 9
10
11
12
13
14
15
16
17
18 19
20
21 22
23
24 25
26
8.2.4.5 Minimum Standard
8.2.5 Mobile Station Originated SMS Disabled
8.2.5.1 Definition
This test verifies that when mobile station originated SMS is not activated in the network, the base station can process a mobile station originated short message and inform the mobile station that short message origination has been denied.
8.2.5.2 Traceability (see [13])
2.4.1.1.1.2 Mobile station SMS Message Origination
3.4.2.1 SMS Point-to-Point Message
3.4.3.6 Cause Codes
8.2.5.3 Call Flow Example(s)
None
8.2.5.4 Method of Measurement
a. Ensure the mobile station originated short message feature for the mobile station is not activated in the network.
b. Power on the mobile station and wait until it is in the Mobile Station Idle State.
c. Create a short message at the mobile station, with the Bearer Reply Option parameter set.
d. Instruct the mobile station to send the short message to the base station.
e. Verify the mobile station sends a Data Burst Message, with the following fields set as follows:
Field Value
8-12
C.S0044-0 v1.0
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 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
f. Upon receiving the Data Burst Message at the base station, verify the following:
1. The base station sends a Data Burst Message to the mobile station, with an indication that the short message origination has been denied.
2. The base station does not route the short message to the Message Center.
8.2.5.5 Minimum Standard
The mobile station shall comply with step e. The base station shall comply with step f.
8.2.6 SMS Not Supported by Base Station
8.2.6.1 Definition
This test verifies the base station can process a mobile station originated short message, and inform the mobile station that SMS is not supported by the base station.
8.2.6.2 Traceability (see [13])
2.4.1.1.1.2 Mobile station SMS Message Origination
3.4.2.1 SMS Point-to-Point Message
3.4.3.6 Cause Codes
8.2.6.3 Call Flow Example(s)
None
8.2.6.4 Method of Measurement
a. Ensure the base station is not capable of SMS or that SMS has been disabled for this test.
b. Power on the mobile station and wait until it is in the Mobile Station Idle State.
c. Create a short message at the mobile station, with Bearer Reply Option parameter set.
d. Instruct the mobile station to send the short message to the network.
e. Verify the mobile station sends a Data Burst Message, with the following fields set as follows:
8-13
C.S0044-0 v1.0
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 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
f. Upon receiving the Data Burst Message at the base station, verify the following:
1. The base station sends a Data Burst Message to the mobile station, with an indication that SMS is not supported by this base station.
2. The base station does not route the short message to the Message Center.
8.2.6.5 Minimum Standard
The base station shall comply with step f.
8.3 Broadcast SMS Delivery on the Common Channel
8.3.1 Definition
This test verifies that mobile stations are able to receive broadcast SMS messages sent by the network addressed to any broadcast address that the mobile stations are configured to receive based on the priority, service and language.
8.3.2 Traceability (see [13])
2.4.1.2.1 Common Channel Procedures for Broadcast SMS
4.3.1.3 Broadcast Messaging Service
8.3.3 Call Flow Example(s)
None
8.3.4 Method of Measurement
a. Connect the base station and mobile stations as shown in Figure A-8.
b. Ensure mobile station 1 is configured to receive broadcast SMS with normal priority while mobile station 2 is configured to receive broadcast SMS with emergency priority. Also, ensure that both mobile stations are configured to receive other filtering categories (i.e. service and language) for this test.
c. Power on the mobile stations and wait until they are registered.
d. Clear any outstanding broadcast messages in the network.
e. Create broadcast message 1 shown in Table 8.3.4-1
8-14
C.S0044-0 v1.0
1
2 3
4
f. Instruct the network to broadcast message 1.
g. Verify the base station sends a Data Burst Message, with the following fields set as follows:
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
5
.3.46 Table 8 -1
Broadcast Message Broadcast Message Priority Priority Indicator Value
Message 1 Normal 00
Message 2 Emergency 11
7
8 9
10
11
12
13 14
15
16
h. Upon receiving the Data Burst Message, verify that mobile station 1 displays broadcast message 1 (as a Normal message, if such display is supported) and mobile station 2 does not.
i. Create broadcast message 2 shown in Table 8.3.4-1.
j. Instruct the network to broadcast message 2.
k. Verify the base station sends a Data Burst Message, with the following fields set as follows:
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
17
8-15
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 33
l. Upon receiving the Data Burst Message, verify both mobile stations display broadcast message 2 (as an Emergency message, if such a display is supported)
8.3.5 Minimum Standard
The mobile station shall comply with steps h and l. The base station shall comply with steps g and k.
8.4 Mobile Station Terminated Enhanced Messaging Services [EMS] Tests:
Unless otherwise noted, the following conditions apply for all tests in this section:
a. Mobile station is capable of receiving Enhanced Messaging Services [EMS] messages.
b. The EMS message feature for the mobile station is activated.
c. Base station has Power-up registration enabled by setting POWER-UP_REG = ‘1’ in the System Parameters Message or the ANSI-41 System Parameters Message.
d. Transport Layer messages shall include the Bearer Reply Option.
e. SMS message carries Teleservice ID parameter is set to WEMT (0x1005),, and HEAD_IND of Message Identifier subparameter is set to '1'
8.4.1 Multi-Segment EMS Message Delivery
8.4.1.1 Definition
This test verifies the mobile station’s ability to receive and properly display multi-segmented EMS messages.
8.4.1.2 Traceability (see [13])
4.3.7 Wireless Enhanced Messaging Teleservice
2.4.1.1.1.1 Mobile station SMS Message Termination
8.4.1.3 Call Flow Example(s)
None
8.4.1.4 Method of Measurement
a. Delete all outstanding short messages in the network for the mobile station. Delete all short messages in the mobile station.
b. Create an EMS message in the Message Center for the mobile station, consisting of (3) three segments.
c. Instruct the Message Center to send the first segment of the EMS message to the mobile station.
d. Verify that the base station sends the first Data Burst Message to the mobile station, with the following fields set as follows:
8-16
C.S0044-0 v1.0
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
1 2 3
4 5
6 7
8
e. Verify that the mobile station transmits a Data Burst Message to acknowledge the received Data Burst Message, and indicates no error (i.e. containing Cause Codes parameter having ERROR_CLASS = ‘00’).
f. Instruct the Message Center to send the remaining segments of the EMS message to the mobile station.
g. Verify that the base station sends the remaining Data Burst Messages to the mobile station, with the following fields set as follows:
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
9
10 11 12
13
14 15 16
17
18 19
h. Verify that the mobile station transmits a Data Burst Message to acknowledge each received Data Burst Message, containing a message segment, and indicates no error (i.e. contains Cause Codes parameters having ERROR_CLASS = ‘00’).
i. Upon receiving all the Data Burst Messages at the mobile station, verify the following:
1. The mobile station alerts the user for the incoming EMS message and correctly displays the received message, when selected. Verify that all the segments of the EMS message segments sent are properly displayed in correct order.
8.4.1.5 Minimum Standard
The mobile station shall comply with steps e, h, and i. The base station shall comply with steps d and g.
8-17
C.S0044-0 v1.0
1
2
3 4
5
6
7
8
9
10
11 12
13 14
15
16
17 18
19
8.4.2 Delivery of Predefined Sound Elements
8.4.2.1 Definition
This test verifies mobile station’s ability to receive and properly play pre-defined EMS sound elements.
8.4.2.2 Traceability (see [13])
4.3.7 Wireless Enhanced Messaging Teleservice
2.4.1.1.1.1 Mobile station SMS Message Termination
8.4.2.3 Call Flow Example(s)
None
8.4.2.4 Method of Measurement
a. Delete all outstanding short messages in the network for the mobile station. Delete all short messages in the mobile station.
b. Create an EMS message in the Message Center for the mobile station. In the message include (1) one predefined sound element.
c. Power on the mobile station and wait until it is in the Mobile Station Idle State.
d. Instruct the network to send the EMS message to the mobile station.
e. Verify the base station sends a Data Burst Message to the mobile station with the specified fields set as follow:
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
20
21 22
23
24 25 26
f. Upon receiving Data Burst Message at the mobile station, verify the following:
1. The mobile station alerts the user for the incoming message and correctly displays the received message (if chosen).
2. The mobile station properly plays the predefined sound, when selected.
3. The mobile station transmits a Data Burst Message to acknowledge the EMS message, indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = ‘00’).
8-18
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
8.4.2.5 Minimum Standard
The mobile station shall comply with step f. The base station shall comply with step e.
8.4.3 Delivery of Predefined Animation Elements
8.4.3.1 Definition
This test verifies mobile station’s ability to receive and properly play pre-defined EMS animation elements.
8.4.3.2 Traceability (see [13])
4.3.7 Wireless Enhanced Messaging Teleservice
2.4.1.1.1.1 Mobile SMS Message Termination
8.4.3.3 Call Flow Example(s)
None
8.4.3.4 Method of Measurement
a. Delete all outstanding short messages in the network for the mobile station. Delete all short messages in the mobile station.
b. Create an EMS message in the Message Center for the mobile station. In the message include (1) one pre-defined animation in a specific order.
c. Power on the mobile station and wait until it is in the Mobile Station Idle State.
d. Instruct the network to send the EMS message to the mobile station.
e. Verify the base station sends a Data Burst Message to the mobile station with the specified fields set as follow:
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
22
23 24
25
f. Upon receiving Data Burst Message at the mobile station, verify the following:
1. The mobile station alerts the user for the incoming message and correctly displays the received message (if chosen).
2. The mobile station properly plays the pre-defined animation, when selected.
8-19
C.S0044-0 v1.0
3. The mobile station transmits a Data Burst Message to acknowledge the EMS message, indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = ‘00’).
1 2 3
4
5
6
7
8 9
8.4.4.2 Traceability (see [13]) 10
11
12
13
14
15
16 17
18 19
20
21
22 23
24
8.4.3.5 Minimum Standard
The mobile station shall comply with step f. The base station shall comply with step e.
8.4.4 Delivery of User Defined Sound Elements - MT
8.4.4.1 Definition
This test verifies mobile station’s ability to receive and properly play user defined (iMelody) EMS sound elements.
4.3.7 Wireless Enhanced Messaging Teleservice
2.4.1.1.1.1 Mobile SMS Message Termination
8.4.4.3 Call Flow Example(s)
None
8.4.4.4 Method of Measurement
a. Delete all outstanding short messages in the network for the mobile station. Delete all short messages in the mobile station.
b. Create an EMS message in the Message Center for the mobile station. In the message include (1) one iMelody sound object.
c. Power on the mobile station and wait until it is in the Mobile Station Idle State.
d. Instruct the network to send the EMS message to the mobile station.
e. Verify the base station sends a Data Burst Message to the mobile station with the specified fields set as follow:
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
Greater than 0 NUM_FIELDS
25
26 27
f. Upon receiving Data Burst Message at the mobile station, verify the following:
1. The mobile station alerts the user for the incoming message and correctly displays the received message (if chosen).
8-20
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
2. The mobile station properly plays the iMelody sound object, when selected. Verify that the iMelody being played is same as the one being transmitted.
3. The mobile station transmits a Data Burst Message to acknowledge the EMS message, indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = ‘00’).
8.4.4.5 Minimum Standard
The mobile station shall comply with step f. The base station shall comply with step e.
8.4.5 Delivery of User Defined Animation Elements - MT
8.4.5.1 Definition
This test verifies mobile station’s ability to receive and properly play user defined EMS animation elements.
8.4.5.2 Traceability (see [13])
4.3.7 Wireless Enhanced Messaging Teleservice
2.4.1.1.1.1 Mobile SMS Message Termination
8.4.5.3 Call Flow Example(s)
None
8.4.5.4 Method of Measurement
a. Delete all outstanding short messages in the network for the mobile station. Delete all short messages in the mobile station.
b. Create an EMS message in the Message Center for the mobile station. In the message include one user-defined animation object.
c. Power on the mobile station and wait until it is in the Mobile Station Idle State.
d. Instruct the network to send the EMS message to the mobile station.
e. Verify the base station sends a Data Burst Message to the mobile station with the specified fields set as follow:
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
f. Upon receiving Data Burst Message at the mobile station, verify the following: 27
8-21
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
1. The mobile station alerts the user for the incoming message and correctly displays the received message (if chosen).
2. The mobile station properly plays the user-defined animation, when selected.
3. The mobile station transmits a Data Burst Message to acknowledge the EMS message, indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = ‘00’).
8.4.5.5 Minimum Standard
The mobile station shall comply with step f. The base station shall comply with step e.
8.4.6 Delivery of User Defined Picture Elements - MT
8.4.6.1 Definition
This test verifies mobile station’s ability to receive and properly play user defined EMS picture elements.
8.4.6.2 Traceability (see [13])
4.3.7 Wireless Enhanced Messaging Teleservice
2.4.1.1.1.1 Mobile SMS Message Termination
8.4.6.3 Call Flow Example(s)
None
8.4.6.4 Method of Measurement
a. Delete all outstanding short messages in the network for the mobile station. Delete all short messages in the mobile station.
b. Create an EMS message in the Message Center for the mobile station. In the message include one user-defined picture object.
c. Power on the mobile station and wait until it is in the Mobile Station Idle State.
d. Instruct the network to send the EMS message to the mobile station.
e. Verify the base station sends a Data Burst Message to the mobile station with the specified fields set as follow:
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
8-22
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
33
34
f. Upon receiving Data Burst Message at the mobile station, verify the following:
1. The mobile station alerts the user for the incoming message and correctly displays the received message (if chosen).
2. The mobile station properly displays the user-defined picture, when selected.
3. The mobile station transmits a Data Burst Message to acknowledge the EMS message, indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = ‘00’).
8.4.6.5 Minimum Standard
The mobile station shall comply with step f. The base station shall comply with step e.
8.4.7 Delivery of Formatted Text
8.4.7.1 Definition
This test verifies mobile station’s ability to receive and properly display formatted text embedded in EMS messages.
8.4.7.2 Traceability (see [13])
4.3.7 Wireless Enhanced Messaging Teleservice
2.4.1.1.1.1 Mobile SMS Message Termination
8.4.7.3 Call Flow Example(s)
None
8.4.7.4 Method of Measurement
a. Delete all outstanding short messages in the network for the mobile station. Delete all short messages in the mobile station.
b. Create an EMS message in the Message Center for the mobile station. From the following text, include the text with formatting that is supported by the mobile station in the message:
Normal Bold Italics Bold-Italics
Underlined Bold-Underlined Bold-Italics-Underlined Left-Justified
Center-Justified
8-23
C.S0044-0 v1.0
1
2
3 4
5
c. Power on the mobile station and wait until it is in the Mobile Station Idle State.
d. Instruct the network to send the EMS message to the mobile station.
e. Verify the base station sends a Data Burst Message to the mobile station with the specified fields set as follow:
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
6
7 8
9 10
11 12 13
14
15
16
17
18
19
20
21
22
23
24
25
f. Upon receiving Data Burst Message at the mobile station, verify the following:
1. The mobile station alerts the user for the incoming message and correctly displays the received message (if chosen).
2. The mobile station properly displays the text, including correct formatting of the lines of text displayed.
3. The mobile station transmits a Data Burst Message to acknowledge the EMS message, indicating no error (i.e. contains a Cause Codes parameter having ERROR_CLASS = ‘00’).
8.4.7.5 Minimum Standard
The mobile station shall comply with step f. The base station shall comply with step e.
8.5 Mobile Station Originated Enhanced Messaging Services [EMS] Tests:
8.5.1 Multi-Segment EMS Message Delivery
8.5.1.1 Definition
This test verifies mobile station’s ability to compose and send multi-segmented EMS messages.
8.5.1.2 Traceability (see [13])
4.3.7 Wireless Enhanced Messaging Teleservice
2.4.1.1.2 Mobile Station Traffic Channel Procedures
2.4.1.1.1.2 Mobile SMS Message Origination
8.5.1.3 Call Flow Example(s)
None
8-24
C.S0044-0 v1.0
8.5.1.4 Method of Measurement 1
2
3
c. Instruct the mobile station to send all the segments of the EMS message to the 4 Message Center. 5
6 7
8 9
10
11
12
13
This test verifies the mobile station’s ability to compose and send messages containing 14 predefined EMS sound elements. 15
16
17
18
19
20
21
22
23 24
25
26 27 28
29
a. Power on the mobile station and wait until it is in the Mobile station Idle State.
b. Create an EMS message at the mobile station, consisting of three (3) segments.
d. Verify that the Message Center receives all the segments and sends an SMS Acknowledgement for each segment to the mobile station.
e. Verify that upon sending the short message, the mobile station sends a Release Order to release the dedicated channels.
8.5.1.5 Minimum Standard
The mobile station shall comply with step e.
8.5.2 Delivery of Predefined Sound Elements
8.5.2.1 Definition
8.5.2.2 Traceability (see [13])
4.3.7 Wireless Enhanced Messaging Teleservice
2.4.1.1.1.2 Mobile SMS Message Origination
8.5.2.3 Call Flow Example(s)
None
8.5.2.4 Method of Measurement
a. Power on the mobile station and wait until it is in the Mobile Station Idle State.
b. Create an EMS message at the mobile station. In the message include (1) one predefined sound.
c. Instruct the mobile station to send the EMS message to the Message Center.
d. Verify the mobile station sends a Data Burst Message to the base station with the fields set as follows:
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
8-25
C.S0044-0 v1.0
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 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
e. Verify that the Message Center receives Data Burst Message and sends the SMS Acknowledgement to the mobile station.
f. Verify that the EMS message sent from the test mobile station contains (1) one predefined sound.
8.5.2.5 Minimum Standard
The mobile station shall comply with step d.
8.5.3 Delivery of Predefined Animation Elements
8.5.3.1 Definition
This test verifies the mobile station’s ability to compose and send messages containing predefined EMS animation elements.
8.5.3.2 Traceability (see [13])
4.3.7 Wireless Enhanced Messaging Teleservice
2.4.1.1.1.2 Mobile SMS Message Origination
8.5.3.3 Call Flow Example(s)
None
8.5.3.4 Method of Measurement
a. Power on the mobile station and wait until it is in the Mobile Station Idle State.
b. Create an EMS message at the mobile station. In the message include (1) one predefined animation object.
c. Instruct the mobile station to send the EMS message to the Message Center.
d. Verify the mobile station sends a Data Burst Message to the base station with the fields set as follows:
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
8-26
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
e. Verify that the Message Center receives Data Burst Message and sends the SMS Acknowledgement to the mobile station.
f. Verify that the EMS message sent from the test mobile station contains the predefined animation object.
8.5.3.5 Minimum Standard
The mobile station shall comply with steps d and f. The base station shall comply with step e.
8.5.4 Delivery of User Defined Sound Elements
8.5.4.1 Definition
This test verifies the mobile’s ability to compose and send a message containing user defined (iMelody) EMS sound elements.
8.5.4.2 Traceability (see [13])
4.3.7 Wireless Enhanced Messaging Teleservice
2.4.1.1.1.2 Mobile SMS Message Origination
8.5.4.3 Call Flow Example(s)
None
8.5.4.4 Method of Measurement
a. Power on the mobile station and wait until it is in the Mobile Station Idle State.
b. Create an EMS message at the mobile station. In the message include (1) one iMelody sound object.
c. Instruct the mobile station to send the EMS message to the Message Center.
d. Verify the mobile station sends a Data Burst Message to the base station with the fields set as follows:
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
25
26 27
e. Verify that the Message Center receives Data Burst Message and sends the SMS Acknowledgement to the mobile station.
8-27
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
f. Verify that the EMS message sent from the test mobile station contains the iMelody sound object sent.
8.5.4.5 Minimum Standard
The mobile station shall comply with steps d and f. The base station shall comply with step e.
8.5.5 Delivery of User Defined Animation Elements
8.5.5.1 Definition
This test verifies mobile station’s ability to compose and send a message containing user defined EMS animation elements.
8.5.5.2 Traceability (see [13])
4.3.7 Wireless Enhanced Messaging Teleservice
2.4.1.1.1.2 Mobile SMS Message Origination
8.5.5.3 Call Flow Example(s)
None
8.5.5.4 Method of Measurement
a. Power on the mobile station and wait until it is in the Mobile Station Idle State.
b. Create an EMS message at the mobile station. In the message include one user-defined animation object.
c. Instruct the mobile station to send the EMS message to the Message Center.
d. Verify the mobile station sends a Data Burst Message to the base station with the fields set as follows:
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
22 23
24 25
e. Verify that the Message Center receives Data Burst Message and sends the SMS Acknowledgement to the mobile station.
f. Verify that the EMS message sent from the test mobile station contains the user-defined animation object sent.
8-28
C.S0044-0 v1.0
1
2
3
4
5
6
7
8
9
10
11
12
13 14
15
16 17
18
8.5.5.5 Minimum Standard
The mobile station shall comply with steps d and f. The base station shall comply with step e.
8.5.6 Delivery of User Defined Picture Elements
8.5.6.1 Definition
This test verifies mobile’s ability to send user defined EMS picture elements.
8.5.6.2 Traceability (see [13])
4.3.7 Wireless Enhanced Messaging Teleservice
2.4.1.1.1.2 Mobile SMS Message Origination
8.5.6.3 Call Flow Example(s)
None
8.5.6.4 Method of Measurement
a. Power on the mobile station and wait until it is in the Mobile Station Idle State.
b. Create an EMS message at the mobile station. In the message include one user-defined picture object.
c. Instruct the mobile station to send the EMS message to the Message Center.
d. Verify the mobile station sends a Data Burst Message to the base station with the fields set as follows:
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
19
20 21
22 23
24
25
e. Verify that the Message Center receives Data Burst Message and sends the SMS Acknowledgement to the mobile station.
f. Verify that the EMS message sent from the test mobile station contains the user-defined picture object sent.
8.5.6.5 Minimum Standard
The mobile station shall comply with step d.
8-29
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
8.5.7 Delivery of Formatted Text
8.5.7.1 Definition
This test verifies mobile’s ability to compose and send formatted text embedded in EMS messages.
8.5.7.2 Traceability (see [13])
4.3.7 Wireless Enhanced Messaging Teleservice
2.4.1.1.1.2 Mobile SMS Message Origination
8.5.7.3 Call Flow Example(s)
None
8.5.7.4 Method of Measurement
a. Power on the mobile station and wait until it is in the Mobile Station Idle State.
b. Create an EMS message in the mobile station under test. From the following text, include the text with formatting that is supported by the mobile station in the message:
c. Inst
d. Verset
Normal Bold Italics Bold-Italics
Underlined Bold-Underlined Bold-Italics-Underlined Left-Justified
Center-Justified
ruct the mobile station to send the EMS message to the Message Center.
ify the mobile station sends a Data Burst Message to the base station with the fields as follows
Field Value
MSG_NUMBER 1 (‘00000001’)
BURST_TYPE 3 (‘000011’)
NUM_MSGS 1 (‘00000001’)
NUM_FIELDS Greater than 0
8-30
C.S0044-0 v1.0
1
2 3
4 5
6
7
8
e. Verify that the Message Center receives Data Burst Message and sends the SMS Acknowledgement to the mobile station.
f. Verify that the EMS message sent from the test mobile station contains the properly formatted text information.
8.5.7.5 Minimum Standard
The mobile station shall comply with step d.
8-31
C.S0044-0 v1.0
9 SUBSCRIBER CALLING FEATURES 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
9.1 Call Forwarding Unconditional (CFU)
9.1.1 Definition
CFU permits a called subscriber to send incoming calls addressed to the called subscriber’s Directory Number to another Directory Number (forward-to number). If this feature is active, calls are forwarded regardless of the condition of the termination.
9.1.2 Traceability (see [22])
505 Call Forwarding—Unconditional
9.1.3 Call Flow Example(s)
None
9.1.4 Method of Measurement
a. Power on the mobile station and wait until it reaches Mobile Station Idle State.
b. Dial the CFU feature activation code, followed by the forward-to number, followed by SEND. Verify feature update confirmation at the mobile station (confirming audio tones from the network).
c. Setup a call from a land party to the mobile station. Verify call is forwarded and that if the Network directs the mobile station to “Ping Ring” it plays a single burst of 500 ms.
d. Answer the call on the forward-to line, and verify the audio path.
e. End the call.
f. Dial the CFU deactivation feature code followed by SEND. Verify feature update confirmation at the mobile station.
g. Verify that CFU has been deactivated, by calling the mobile station under test and verifying that the mobile station rings and completes the call when answered.
9.1.5 Minimum Standard
The mobile station and the base station shall comply with steps b, c, d, f and g.
9.2 Call Forwarding Busy (CFB)
9.2.1 Definition
CFB permits a called subscriber to have the system send incoming calls to another Directory Number (forward-to number) when the subscriber is engaged in a call or service.
9.2.2 Traceability (see [22])
502 Call Forwarding Busy
9-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 33 34
9.2.3 Call Flow Example(s)
None
9.2.4 Method of Measurement
a. Power on the mobile station and wait until it reaches Mobile Station Idle State.
b. Dial the CFB activation feature code, followed by the forward-to-number, followed by SEND. Verify feature update confirmation at the mobile station (confirming audio tones from the network).
c. Place the mobile station under test in a voice call.
d. Attempt a second call from a land party to the mobile station under test. Verify the call is forwarded to the forward-to-number, and that if the Network directs the mobile station to “Ping Ring” it plays a single burst of 500 ms.
e. Answer the call on the forward-to line, and verify the audio path.
f. End all calls.
g. Dial the CFB deactivation feature code followed by SEND. Verify feature update confirmation at the mobile station.
h. Verify that CFB has been deactivated, e.g. By calling the mobile station under test while busy and verifying that the second call is not forwarded.
9.2.5 Minimum Standard
The mobile station and the base station shall comply with steps b, c, d, f and g.
9.3 Call Forwarding Default (CFD)
9.3.1 Definition
CFD permits a called subscriber to have the system send incoming calls to another Directory Number (forward-to-number) when the subscriber is engaged in a call, does not respond to paging, does not answer the call within a specified period after being alerted or is otherwise inaccessible.
9.3.2 Traceability (see [22])
503 Call Forwarding—Default
9.3.3 Call Flow Example(s)
None
9.3.4 Method of Measurement
a. Power on the mobile station and wait until it reaches Mobile Station Idle State.
b. Dial the CFD activation feature code, followed by the forward-to number, followed by SEND. Verify feature update confirmation at the mobile station (confirming audio tones from the network).
9-2
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 33
c. Attempt a call from a land party to the mobile station. Verify the call is forwarded and that if the Network directs the mobile station to “Ping Ring” it plays a single burst of 500 ms.
d. Answer the call on the forward-to line, and verify the audio path.
e. End call.
f. Dial the CFD deactivation feature code followed by SEND. Verify feature update confirmation at the mobile station.
g. Verify that CFD has been deactivated, by calling the mobile station under test and verifying that the mobile station rings and does not forward.
9.3.5 Minimum Standard
The mobile station and the base station shall comply with steps b, c, d, f and g.
9.4 Call Forwarding No Answer (CFNA)
9.4.1 Definition
CFNA permits a called subscriber to have the system send incoming calls addressed to the called subscriber’s Directory Number to another Directory Number (forward-to number) when the subscriber fails to answer.
9.4.2 Traceability (see [22])
504 Call Forwarding—No Answer
9.4.3 Call Flow Example(s)
None
9.4.4 Method of Measurement
a. Power on the mobile station and wait until it reaches Mobile Station Idle State.
b. Dial the CFNA activation feature code, followed by the forward-to number, followed by SEND. Verify feature update confirmation at the mobile station (confirming audio tones from the network).
c. Setup a call from a land party to the mobile station. Verify the mobile station rings, but when not answered, the call is forwarded to the forward-to number.
d. Answer the call on the forward-to line, and verify the audio path.
e. End the call.
f. Dial the CFNA deactivation feature code followed by SEND. Verify feature update confirmation at the mobile station.
g. Verify that CFNA has been deactivated, by calling the mobile station and verifying that the mobile station rings and does not forward.
9-3
C.S0044-0 v1.0
1
2
3
4
5 6 7
8
9
10
11
9.4.5 Minimum Standard
The mobile station and the base station shall comply with steps b, c, d, f and g.
9.5 Three-Way Calling
9.5.1 Definition
This tests mobile station’s operation of Three-way Calling. In Three-way Calling, the base station responds to Flash With Information Messages from the mobile station to connect a third party to an established two-way call.
9.5.2 Traceability (see [22])
522 Three Way Calling
9.5.3 Call Flow Example(s)
BSMSVoice Traffic in 2-way call
Ack Order
Flash with Info Message
Ack Order
Flash with Info Message
Ack Order
Flash with Info Message
no records
3rd partynumber
Connect 3-way
12
13
14
15 16
17
18 19
20 21
22 23 24 25
9.5.4 Method of Measurement
a. Allow the mobile station to come to the idle state on the base station.
b. Ensure the base station will allow the mobile station to perform Three-way calling via subscriber profile or by dialing a feature activation code such as *31+ SEND.
c. Set up a normal two-way voice call with a second party.
d. Put the second party on hold using the prescribed method at the mobile station, e.g. send a Flash With Information Message by pressing the SEND button.
e. Verify the second party is placed on hold and the mobile station alerts the user to commence dialing the third party number, e. g. plays a dial tone.
f. Dial the third party number on the mobile station and send it out using the prescribed method, e. g. send a Flash With Information Message containing the Keypad Facility Information Record or the Called Party Number Information Record by pressing the SEND button after entering dialed digits.
9-4
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
g. Verify the third party phone rings and answers with normal audio.
h. Connect all of the Three-Way Call parties, e. g. send a Flash With Information Message by pressing the SEND button, and verify the three-way connection is established with normal audio.
i. End the call.
j. Ensure the base station will not allow the mobile station to perform Three-way calling via subscriber profile or by dialing a feature de-activation code such as *91+ SEND
9.5.5 Minimum Standard
The mobile station shall comply with the requirements in steps b, e, g, h, and j.
9.6 Call Alerting
9.6.1 Definition
This is a test for standard mobile station incoming call alerting (ringing). An incoming call alert is played or displayed by the mobile station as a result of receiving an Alert With Information Message or an Extended Alert with Information Message with a Signal information record.
9.6.2 Traceability (see [4])
Table 3.7.5.5-1 Signal Type
Table 3.7.5.5-2 Alert Pitches
Table 3.7.5.5-3 Tone Signals (SIGNAL_TYPE = ‘00’)
Table 3.7.5.5-4 ISDN Alerting (SIGNAL_TYPE = ‘01’)
Table 3.7.5.5-5 IS-54B Alerting (SIGNAL_TYPE = ‘10’)
Table 3.7.5-1 Information Record Types (base station)
9.6.3 Call Flow Example(s)
9-5
C.S0044-0 v1.0
Service Connect Message
Extended Channel Assignment Message
possible service negotiation
Order Message (acknowledgement from base station)
Page Message to mobile
Page Response Message
Release Order Messages
Connect Order Message
Voice Traffic
Service Connect Complete Message
Alert with Info Message Message (ring for mobile)
MS BS
1
2
3 4
5 6 7
8
9
10 11 12
13
14
15
9.7.1 Definition 16
17
9.6.4 Method of Measurement
a. Allow the mobile station to come to the idle state on the base station, and make a mobile station terminated call.
b. Verify the mobile station receives an Alert with Information Message or Extended Alert with Information Message with a Signal Information record. The Alert with Information Message may or may not contain a Calling Party Number Information record.
c. Verify the mobile station rings (plays an incoming call alert).
d. Answer the call, verify the call completes successfully, then end the call.
e. Steps a through d may be repeated using each variation of parameters in the Signal Information record for SIGNAL_TYPE, ALERT_PITCH, and SIGNAL as supported by the base station.
9.6.5 Minimum Standard
The mobile station shall comply with the requirements in step c, d, and e.
9.7 Caller ID for Mobile station Terminated Call Setup
This tests delivery and display of Caller ID Calling Party Number (CPN) during call setup.
9-6
C.S0044-0 v1.0
9.7.2 Traceability (see [4]) 1
2
3
4
5
6
7
8
9
10
b. Allow the mobile station to come to the idle state on the base station, and initiate a 11 mobile station terminated call. 12
13 14
15 16 17
18
19 20 21
22
23
24
25
26
27
28
29
30
31
32
3.7.5.3 Calling Party Number
Table 2.7.1.3.2.4-2 Number Types
Table 2.7.1.3.2.4-3 Numbering Plan Identification
Table 2.7.4.4-1 Presentation Indicators
Table 3.7.5-1 Information Record Types (base station)
9.7.3 Call Flow Example(s)
None
9.7.4 Method of Measurement
a. Configure the base station to send Caller ID for mobile station terminated calls.
c. Verify the mobile station displays the correct Caller ID before answering the call and then answer the call.
d. Repeat steps b to c for all Caller ID base station configurations, e.g. parameters PI = ‘01’ (Presentation Restricted) and PI = ‘10’ (Number not available), as supported by the base station, and verify the correct outcome.
9.7.5 Minimum Standard
The mobile station shall comply with requirements in steps c and d. In step d, for PI = ‘01’ (Presentation Restricted) and PI = ‘10’ (Number not available), the mobile station shall NOT display the Caller ID, but may display ‘No Caller ID’ or something to that effect.
9.8 Caller ID for Call Waiting
9.8.1 Definition
This tests delivery and display of Caller ID Calling Party Number (CPN) for Call Waiting calls.
9.8.2 Traceability (see [4])
3.7.5.3 Calling Party Number
3.7.5.22 Call Waiting Indicator
Table 3.7.5.16-2 Mandatory Control Tags and Display Text Tags
Table 2.7.1.3.2.4-2 Number Types
Table 2.7.1.3.2.4-3 Numbering Plan Identification
Table 2.7.4.4-1 Presentation Indicators
Table 3.7.5-1 Information Record Types (base station)
9-7
C.S0044-0 v1.0
9.8.3 Call Flow Example(s) 1
2
3
4
5
6
7
8 9
10
11
12 13 14
9.9 Call Waiting 15
16
17 18 19
20
21
22
23
24
25
26
27
28
a. Allow the mobile station to come to the idle state on the base station. 29
30 31 32
None
9.8.4 Method of Measurement
a. Configure the base station to send Caller ID for Call Waiting calls.
b. Set up a mobile station terminated voice call.
c. While this voice call is in progress, attempt a second call to the mobile station.
d. Verify the mobile station displays the correct Caller ID of the Call Waiting caller.
e. Repeat steps b to d for all Caller ID base station configurations, e. g. CPN parameters PI = ‘01’ (Presentation Restricted) and PI = ‘10’ (Number not available), as supported by the base station, and verify the correct outcome.
9.8.5 Minimum Standard
The mobile station shall comply with requirements in steps d and e. In step e, for PI = ‘01’ (Presentation Restricted) and PI = ‘10’ (Number not available), the mobile station shall NOT display the Caller ID, but may display ‘No Caller ID’ or something to that effect.
9.9.1 Definition
This test verifies mobile station call-waiting notification, alerting, and connection with Flash with Information Messages or Extended Flash with Information Messages. It also checks the mobile station ability to activate and deactivate the call-waiting feature on the network.
9.9.2 Traceability (see [4])
3.7.5.5 Signal
Table 2.7.4-1 Information Record Types (mobile station)
Table 3.7.5-1 Information Record Types (base station)
Table 3.7.5.5-5 IS-54B Alerting (SIGNAL_TYPE = ‘10’)
3.7.5.22 Call Waiting Indicator
9.9.3 Call Flow Example(s)
None
9.9.4 Method of Measurement
b. Activate call waiting, e.g. make a dedicated call *41-SEND, and verify that the mobile station plays or displays a notification that call waiting has been activated, e.g. audio confirmation tones in the earpiece.
9-8
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
33 34
35
c. Verify the call-waiting activation call ends without user interaction (Base Station releases the call), and the mobile station returns to the idle state on the base station.
d. Set up a voice call with the mobile station. While the first call is in progress, attempt a second mobile station terminated call, and verify that a call-waiting alert is played at the mobile station, e.g. tones in the earpiece.
e. Cause the mobile station to accept the second call, e.g. press SEND, and verify the connection to the second caller with normal audio.
f. Cause the mobile station to flash back to the first call, e.g. press SEND, and verify the connection to the first caller with normal audio.
g. Press END on the mobile station to end the call. Note: in some implementations, if the mobile station subscriber ends a call waiting call while the other party is still waiting, the base station will initiate a mobile station terminated call to re-connect the waiting party. If this is the case, answer the call, then end that call too.
h. Deactivate call waiting on the base station, e.g. make a dedicated call *410-SEND, and verify the mobile station plays or displays a notification that call waiting has been disabled, e.g. tones in the earpiece.
i. Set up a new call with the mobile station. While the call is in progress, attempt another mobile station terminated call, and verify that no call-waiting alert is played at the mobile station.
9.9.5 Minimum Standard
The mobile station shall comply with the requirements in steps b, c, d, e, f, h, and i.
9.10 Voice Mail Message Waiting Notification from the Idle State
9.10.1 Definition
This test verifies mobile station response to message waiting notification while the mobile station is in the idle state. Notification can be a tone, light, or display and is manufacturer dependent.
9.10.2 Traceability (see [4])
3.7.5.6 Message Waiting
3.7.2.3.2.12 Feature Notification Message
9.10.3 Call Flow Example(s)
None
9.10.4 Method of Measurement
a. Power on the mobile station and allow it to come to the idle state on the base station.
b. Instruct the base station to send a voice mail message waiting notification, setting the number of voice mail messages waiting to a value ranging from 1 to 31.
c. Verify the mobile station gives an indication of the change in message waiting status.
9-9
C.S0044-0 v1.0
d. Verify that any indication on the mobile station of the number of messages waiting reflects the correct value.
1 2
3
4 5 6
7
8
9
10
11 12
13
14
15
16
17
18
b. Set up a call with the mobile station. 19
20 21 22
23 24
25 26
27 28 29
30
31
32
e. Repeat steps b through d for a different number of voice mail messages waiting.
f. Repeat steps b through d, except in step b, send notification for zero voice mail messages waiting, e. g. to clear the mobile station’s voice mail waiting indicator on the mobile station.
9.10.5 Minimum Standard
The mobile station shall comply with the requirements in steps c and d.
9.11 Voice Mail Message Waiting Notification from the Conversation State
9.11.1 Definition
This test verifies mobile station’s response to message waiting notification while the mobile station is in the conversation state.
9.11.2 Traceability (see [4])
3.7.5.6 Message Waiting
9.11.3 Call Flow Example(s)
None
9.11.4 Method of Measurement
a. Power on the mobile station and allow it to come to the idle state on the base station.
c. Instruct the base station to send a voice mail message waiting notification, setting the number of voice mail messages waiting to a value less than the maximum number the mobile station can display.
d. Verify that the mobile station gives an indication of the change in message waiting status.
e. Verify that any indication on the mobile station of the number of messages waiting reflects the correct value.
f. Instruct the base station to send a voice mail message waiting notification, setting the number of messages waiting to a value that exceeds the maximum number that can be displayed by the mobile station.
g. Verify the mobile station displays the maximum number of messages that it can display.
9.11.5 Minimum Standard
The mobile station shall comply with the requirements in steps d, e, and g.
9-10
C.S0044-0 v1.0
9.12 Calling Name Presentation (CNAP) for Mobile station Terminated Call Setup 1
2
3 4
5
6
7
8
3.7.5.22 Call Waiting Indicator 9
10
11
12
13
14
15
16
17
18
19 20
21
22
23 24 25 26
27 28
29
30
31
32 33 34
9.12.1 Definition
This test will verify that the mobile station in the Mobile Station Idle State properly displays the Calling Name Information (CNA) for an incoming call.
9.12.2 Traceability (see [4])
3.7.5.3 Calling Party Number
3.7.5.16 Extended Display, Calling Party Name = type ‘10001101’
3.7.5.21 Multiple Character Extended Display
Table 3.7.5.16-2 Mandatory Control Tags and Display Text Tags
Table 2.7.1.3.2.4-2 Number Types
Table 2.7.1.3.2.4-3 Numbering Plan Identification
Table 2.7.4.4-1 Presentation Indicators
Table 3.7.5-1 Information Record Types (base station)
9.12.3 Call Flow Example(s)
None
9.12.4 Method of Measurement
a. Ensure the mobile station has been assigned CNAP Class-of -Service and is configured to display CNAP if it is delivered.
b. Power on the mobile station and wait until it reaches Mobile Station Idle State.
c. Setup a call to the mobile station from a 10-digit Calling Party Number (CPN).
d. Instruct the base station to indicate CNA with Presentation Allowed. Verify that the base station sends a Feature Notification Message, Alert With Information Message, or a Flash With Information Message with an Extended Display information record and CPN information record with the PI field set to “00” (Presentation Allowed).
e. Verify the mobile station receives and displays the CNA and Calling Number Identification (CNI).
f. Verify user data in both directions.
g. End call.
h. Change the PI field of the CPN information record to “01” (Presentation Restricted).
i. Repeat steps c through g, except during step e, verify that the mobile station does not display the CNA or CNI and that it indicates the CNA is restricted, during the first alerting cycle.
9-11
C.S0044-0 v1.0
j. Change the PI field of the CPN information record to “10” (Number Not Available). 1
k. Repeat steps c through g, except during step e, verify that the mobile station does not 2 display the CNA or CNI and that it indicates the CNA is not available, during the first 3 alerting cycle. 4
5
6 7
8
9.13.1 Definition 9
10 11
12
13
14
15
16
17
18
19
20
21
22
23
24
25 26
27 28
29
30
31 32
33
9.12.5 Minimum Standard
The mobile station shall comply with steps e, f, i, and k. The base station shall comply with steps d and f.
9.13 Calling Name Presentation (CNAP) from Conversation State
This test will verify that the mobile station in Conversation Substate (with call waiting enabled) properly displays the Calling Party Name (CNA).
9.13.2 Traceability (see [4])
3.7.5.3 Calling Party Number
3.7.5.16 Extended Display, Calling Party Name = type ‘10001101’
3.7.5.21 Multiple Character Extended Display
3.7.5.22 Call Waiting Indicator
Table 3.7.5.16-2 Mandatory Control Tags and Display Text Tags
Table 2.7.1.3.2.4-2 Number Types
Table 2.7.1.3.2.4-3 Numbering Plan Identification
Table 2.7.4.4-1 Presentation Indicators
Table 3.7.5-1 Information Record Types (base station)
9.13.3 Call Flow Example(s)
None
9.13.4 Method of Measurement
a. Ensure mobile station is assigned CNAP Class-of-Service, and that the mobile station has not been pre-programmed (phone book) with calling name/number information.
b. Set Presentation Indicator (PI) field of the CPN information record of calling parties 1 and 2 to “00” (Presentation Allowed).
c. Power on the mobile station and wait until it reaches Mobile Station Idle State.
d. Setup a call from party 1 to the mobile station (from 10-digit CPN 1).
e. Verify the mobile station receives and displays the CNA and CNI (of party 1) during the first alerting cycle.
f. Verify user data in both directions.
9-12
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 33
34
g. Maintain the call and setup another call from party 2 to the mobile station (from 10-digit CPN 2). Verify that the base station sends a Alert With Information Message or Flash With Information Message with an Extended Display information record and the PI field set to “00” (Presentation Allowed).
h. Verify the mobile station receives and displays the CNA and CNI (of party 2) with delivery of the call waiting indication.
i. End both calls.
j. Change the PI field of the CPN information record of both calling parties (1 and 2) to '01' (Presentation Restricted).
k. Repeat steps d through i, except in step e and h, verify the mobile station does not display the CNA and that it indicates the CNA is restricted.
l. Change the PI field of the CPN information record of both calling parties (1 and 2) to '10' (Number Not Available).
m. Repeat steps d through i, except in step e and h, verify the mobile station does not display the CNA and that it indicates the CNA is not available.
9.13.5 Minimum Standard
The mobile station shall comply with steps e and h.
9.14 Calling Name Presentation (CNAP) with Forwarding
9.14.1 Definition
This test verifies the mobile station receiving a forwarded call from party 2 (redirecting party), properly displays redirection information from calling party 1 (originating party) and party 2.
9.14.2 Traceability: (See [4] );
3.7.5.3: Calling Party Number
9.14.3 Call Flow Example(s)
None
9.14.4 Method of Measurement
a. Ensure the mobile station is assigned the CNAP Class-of-Service and that the mobile station has not been pre-programmed (phone book) with calling name/number information.
b. Ensure party 2 has been assigned Call Forwarding Unconditional, programmed to forward calls to the mobile station directory number, and that this service is invoked.
c. Set Presentation Indicator field of the CPN information record of calling parties 1 and 2 to '00' (Presentation Allowed).
d. Power on the mobile station and wait until it reaches Mobile Station Idle State.
9-13
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
33
34
e. Setup a call from party 1 to party 2 (from 10-digit CPN 1).
f. Verify the call is forwarded to the mobile station and that the mobile station properly receives and displays the CNA and CNI of the original calling party 1 and/or the redirected party 2 during the first alerting cycle.
g. Verify user data in both directions for party 1 (originating party), and the mobile station.
h. End call.
i. Change the PI field of the CPN information record of the calling parties (1 and 2) to '01' (Presentation Restricted).
j. Repeat steps e through h, except in step f, verify the mobile station does not display the CNA or CNI associated with parties 1 and 2, and that it indicates the CNA is restricted during the first alerting cycle.
k. Change the PI field of the CPN information record of the calling parties (1 and 2) to '10' (Number Not Available).
l. Repeat steps e through h, except in step f, verify the mobile station does not display the CNA or CNI associated with parties 1 and 2 and that it indicates the CNA is not available, during the first alerting cycle.
9.14.5 Minimum Standard
The mobile station shall comply with steps f and g .
9.15 Display Records sent in the Feature Notification Message.
9.15.1 Definition
This test verifies that the mobile station displays Paging Channel and Forward Common Control Channel Display Information Records, Extended Display Information Records and Multiple Character Extended Display Records. This test also verifies that Display Information Records, Extended Display Information Records and Multiple Character Extended Display Records do not interfere with any other information records or features.
9.15.2 Traceability (See [4])
2.6.2.4 Mobile Station Order and Message Processing Operation
2.6.10.1 Alerting
3.7.2.3.2.12 Feature Notification Message
3.7.3.3.2.3 Alert with Information Message
3.7.3.3.2.14 Flash with Information Message
3.7.5 Information Records
9.15.3 Call Flow Example(s)
None
9-14
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
33
34
9.15.4 Method of Measurement
a. Verify the mobile station is in Idle State.
b. Instruct the base station to send a display record of at least 15 characters in a Feature Notification Message on the Paging Channel or Forward Common Control Channel.
c. Upon receiving the Feature Notification Message, verify the mobile station displays characters as instructed in the Display Record contained in the Feature Notification Message.
d. Instruct the base station to send a new Display Record of at least 15 characters in a Feature Notification Message.
e. Upon receiving the Feature Notification Message, verify the mobile station displays the new characters as instructed in the Display Record and performs other information records contained in the Feature Notification Message.
f. If supported by the mobile station and the base station, repeat steps b to e using the Extended Display Record.
g. If supported by the mobile station and the base station, repeat steps b to eusing the Multiple Character Extended Display Record.
h. If supported by the mobile station and the base station, repeat steps b to e using the Multiple Character Extended Display Record.
9.15.5 Minimum Standard
The mobile station shall comply with steps c, e, f, g and h.
9.16 Display Records Sent in the Flash With Information Message
9.16.1 Definition
This test verifies that the mobile station displays Traffic Channel Display Information Records, Extended Display Information Records and Multiple Character Extended Display Records. This test also verifies that Display Information Records, Extended Display Information Records and Multiple Character Extended Display Records do not interfere with other information records or features.
9.16.2 Traceability (See [4])
2.6.2.4 Mobile Station Order and Message Processing Operation
2.6.10.1 Alerting
3.7.3.3.2.3 Alert with Information Message
3.7.3.3.2.14 Flash with Information Message
3.7.5 Information Records
9-15
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 33 34
35
36
37
38
9.16.3 Call Flow Example(s)
None
9.16.4 Method of Measurement
a. Setup a mobile station originated call.
b. Instruct the base station to send a Display Record of at least 15 characters in a Flash With Information Message.
c. Upon receiving the Flash With Information Message, verify the mobile station displays characters as instructed in the Display Record contained in the Flash with Information Message.
d. Instruct the base station to send a new display record of at least 15 characters contained in the Flash with Information Message.
e. Upon receiving the Flash With Information Message, verify the mobile station displays the new characters as instructed in the Display Record.
g. If supported by the mobile station and the base station, repeat steps a to e using the Multiple Character Extended Display Record.
9.16.5 Minimum Standard
If supported by the mobile station, the most current display record shall be displayed on the mobile station.
9.17 Display Records Sent in the Alert with Information Message
This test verifies the mobile station displays Display Information Records, Extended Display Information Records and the Multiple Character Extended Display Record on the traffic channel. This test also verifies that Display Information Records, Extended Display Information Records and Multiple Character Extended Display Record do not interfere with other information records or features.
9.17.2 Traceability (See [4])
2.6.10.1 Alerting
3.7.2.3.2.12 Feature Notification Message
f. If supported by the mobile station and the base station, repeat steps a to e using the Extended Display Record.
The verifications in steps c and e in the traffic channel shall be successfully carried out for all forms of display records supported. When various information records are sent to the mobile station in the same message, the mobile station shall properly process all information records. If display records are not supported in the mobile station, there shall be no negative impact on any information records supported by the mobile station. There shall be no negative impact on any supported feature or call processing when display records are sent to the mobile station in the same message as other information records.
9.17.1 Definition
2.6.2.4 Mobile Station Order and Message Processing Operation
9-16
C.S0044-0 v1.0
3.7.3.3.2.3 Alert with Information Message 1
2
3
4
5
6
7
8 9
10 11 12
13 14
15 16
17
The verifications in step c in the traffic channel shall be successfully carried out for all forms of 18 display records supported. When various information records are sent to the mobile station in the 19 same message, the mobile station shall process all information records. If display records are not 20 supported in the mobile station, there shall be no negative impact on information records 21 supported by the mobile station. There shall be no negative impact on any supported feature, or 22 on call processing when display records are sent to the mobile station in the same message as 23 other information records. 24
25 26
27
28
29 30
31
32
33
3.7.3.3.2.14 Flash with Information Message
3.7.5 Information Records
9.17.3 Call Flow Example(s)
None
9.17.4 Method of Measurement
b. Instruct the base station to send in an Alert With Information Message, a Display Record of at least 15 characters, and a Calling Party Number Record.
c. Upon receiving the Alert With Information Message, verify the mobile station displays the characters as instructed in the display record or extended display record and displays the Calling Party Number in the Alert With Information Message.
e. If supported by the mobile station and the base station, repeat steps a to c using the Multiple Character Extended Display Record.
9.17.5 Minimum Standard
If supported by the mobile station, the most current display record shall be displayed on the mobile station.
9.18 TTY/TDD
This test verifies the system ability to transfer TTY/TDD information in the forward and reverse link directions.
9.18.2 Traceability: (See [18,19 and 20])
a. Setup a mobile station terminated call.
d. If supported by the mobile station and the base station, repeat steps a to c using the Extended Display Record.
9.18.1 Definition
9.18.3 Call Flow Example(s)
None
9-17
C.S0044-0 v1.0
1
2
3
4
9.18.4 Method of Measurement
9.18.4.1 Basic TTY/TDD Operation
a. Connect the mobile station as shown in Figure 9.18.4-1.
MS
TE2M
MTO
MT2Rn
Um BS/MSC
Ai PSTN TE2LW
Specific Network Entity
Collective (Composite Entity)
Interface Reference Point
KEY
X
5
6
7 8
9 10 11 12 13
14
15 16 17
18
19
20
21
22
23
24
Figure 9.18.4-1
The base station (Base Station) in this model represents the entire system infrastructure. It contains the transceiver equipment and Mobile Switching Center (MSC).
Terminal Equipment (TE2) is TTY/TDD equipment connected either directly or indirectly to the Mobile Terminal (MT2) on the mobile station side of the connection. TE2 is TTY/TDD equipment connected to the PSTN on the land side. Subscripts "M" and "L" are added as needed to indicate mobile station side and land side TE2s, respectively. When combined in a single physical entity, TE2 and MT2 functionality is labeled MT0.
b. Setup a mobile station originated TTY/TDD call.
c. Verify characters typed at TE2M can be viewed at TE2L. Verify characters typed at TE2L can be viewed at TE2M. See aNNEX E: TTY/TDD Test Examples for Example character text. See Annex E For Example character text.
d. Type a character sequence (“AB ”) repeatedly a minimum of 20 times at TE2L
e. Verify characters are properly viewed at TE2M.
f. Type a character sequence (“AB”) repeatedly a minimum of 20 times at TE2M
g. Verify characters are properly viewed at the TE2L.
h. Steps b through g may be repeated for all supported radio configurations.
i. Repeat steps c through h using mobile station terminated TTY/TDD calls.
j. Steps a through i may be repeated using all support baud rates.
9-18
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
9.18.4.2 TTY/TDD File Transfer Operation
a. Setup the mobile station for TTY/TDD file transfer.
b. Transfer the ASCII/Baudot file from TE2M to TE2L.
c. Verify the PCER, CCER, and TCER is less than 1%.
d. Transfer the ASCII/Baudot file from TE2L to TE2M.
e. Verify the PCER, CCER, and TCER is less than 1%.
f. End the TTY/TDD call.
g. Steps a through f may be repeated for all supported radio configurations.
h. Repeat steps b through g for mobile station terminated calls.
i. Steps a through h may be repeated using all support baud rates.
9.18.4.3 Voice Carry Over (VCO) and Hearing Carry Over (HCO) Operation
a. Configure TE2M for VCO.
b. Setup a mobile station originated TTY/TDD call.
c. Verify outgoing messages can be spoken and incoming responses can be viewed.
d. End the TTY/TDD call.
e. Configure TE2M for HCO.
f. Setup a mobile station originated TTY/TDD call.
g. Verify outgoing messages can be typed and incoming responses can be heard through a TE2M accessory speaker.
h. Verify characters typed at TE2M can be viewed at TE2L.
i. End the TTY/TDD call.
9.18.5 Minimum Standard
9.18.5.1 Basic TTY/TDD Operation
The mobile station shall comply with steps e and g for all tested and supported radio configurations and baud rates for mobile station originated and terminated calls.
9.18.5.2 TTY/TDD Operation File Transfer
The mobile station shall comply with steps c and e for all tested and supported radio configurations and baud rates for mobile station originated and terminated calls.
9.18.5.3 Voice Carry Over (VCO) and Hearing Carry Over (HCO) Operation
The mobile station shall comply with steps c, g and h.
9-19
C.S0044-0 v1.0
9.19 WLL Call Waiting Indicator Support 1
2
3 4 5
6
7
8
9
10
11
12
13
14
15
16 17
18
19 20 21 22
23
24 25
26 27
28
29
30 31 32
33
34
9.19.1 Definition
This test verifies that a mobile station in a two-way conversation, with call waiting enabled, will receive indicator of waiting calls. This test will verify that the mobile station will send a flash request to connect to the waiting call. This test case is applicable only if WLL is supported.
9.19.2 Traceability (see [4])
2.7.2.3.2.3 Flash with Information Message
3.7.5.5 Signal
3.7.5.22 Call Waiting Indicator
9.19.3 Call Flow Example(s)
None
9.19.4 Method of Measurement
a. Ensure call waiting is enabled.
b. Make a mobile station to land party 1 voice call. Verify audio in both directions.
c. Setup a voice call from land party 2 to the mobile station.
d. Verify the base station sends a Flash With Information Message or Extended Flash With Information Message with the Call Waiting Indicator Information Record as follows:
1. CALL_WAITING_INDICATOR field set to ’1’.
e. Press the hook (or FLASH button if available) in the mobile station to put land party 1 on hold and to connect to land party 2. Verify that the mobile station sends a Flash With Information Message or an Extended Flash With Information Message to the base station. Verify that no dial tone is generated in the mobile station.
f. Verify that voice path is established between the mobile station and land party 2.
g. Press the hook (or FLASH button if available) again in the mobile station to put land party 2 on hold, and reconnect the voice path to land party 1.
h. Verify the mobile station sends a Flash With Information Message or Extended Flash With Information Message to the base station.
i. Verify that voice path is established between the mobile station and land party 1.
j. End the call from land party 1.
k. Press hook (or FLASH button if available) again in the mobile station. Verify that the mobile station sends a Flash With Information Message or Extended Flash With Information Message to the base station.
l. Verify voice path is established between the mobile station and land party 2.
m. End the call to land party 2.
9-20
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
33
34
35
n. Make a mobile station to land party 1 voice call. Verify audio path is established in both directions.
o. Setup a voice call from land party 2 to the mobile station.
p. Verify the base station sends a Flash With Information Message or Extended Flash With Information Message with the Call Waiting Indicator Information Record as follows: CALL_WAITING_INDICATOR field set to ’1’.
q. Do not answer this call waiting call at the mobile station.
r. Disconnect call from land party 2.
s. Verify the base station sends a Flash With Information Message or Extended Flash With Information Message with the Call Waiting Indicator Information Record as follows: CALL_WAITING_INDICATOR field set to ’0’.
t. Press the hook (or FLASH button if available) of the mobile station and verify that a dial tone is generated.
u. Press the hook (or FLASH button if available) again and verify that voice path between the mobile station and land party 1 is established.
v. End the call to land party 1.
9.19.5 Minimum Standard
The mobile station shall comply with the requirements in the following steps: e, h, i, k, t and u.
The base station shall comply with the requirements in the following steps: d, f, j, i, p, s, t and u.
The base station shall send a Call Waiting Indicator to the mobile station during a two-way conversation indicating another call is waiting. The mobile station shall be able to switch between land party 1 and land party 2 by sending a flash request.
9.20 Answer Holding
9.20.1 Definition
These tests verify that the mobile station that supports Answer Holding feature can perform the following:
a. Activate answer holding when the incoming call is ringing in the Waiting for Mobile Station Answer Substate or in the Conversation Substate
b. Deactivate answer holding in the Conversation Substate
9.20.2 Traceability (see [4])
2.6.10.1.2 Waiting for Mobile Station Answer Substate
2.6.10.2 Conversation Substate
2.7.2.3.2.3 Flash with Information Message
2.7.2.3.2.33 Extended Flash with Information Message
2.7.4.2 Keypad Facility
9-21
C.S0044-0 v1.0
1
2
3
3.6.8.1.2 Waiting for Answer Substate
9.20.3 Call Flow Example(s)
MS BS
Extended Channel AssignmentMessage
Service ConnectMessage
AWI Message (ringing applied)
ConnectOrder
Conversation
ReleaseOrder
ReleaseOrder
Initiate a call
Disconnect the call
Page ResponseMessage
General PageMessage
Instruct the MS to activiateAnswer Holding
Service Connect CompletionMessage
(Extended) Flash with Info (Keypad Facility InfoRecord)
Instruct the MS to deactivateAnswer Holding
FWI Message (Call Waiting)
Instruct the MS to activiateAnswer Holding
Instruct the MS to disconnectthe first call and deactivate
Answer Holding
(Extended) Flash with Info (Keypad Facility InfoRecord)
(Extended) Flash with Info (Keypad Facility InfoRecord)
(Extended) Flash with Info (Keypad Facility InfoRecord)
4 5
6
7
8
9 10
11 12
9.20.4 Method of Measurement
a. Power on the mobile station and wait until it reaches Idle State.
b. Setup a mobile station terminated call from land party 1.
c. When the mobile station is ringing and ring back tone is applied to the audio path, instruct the mobile station to answer hold the call.
d. Verify the mobile station sends a Flash With Information Message or an Extended Flash With Information Message in assured mode with a Keypad Facility information record
9-22
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
with the CHARi field set to a pre-programmed feature code (i.e., Switch Control Code: 18*) which indicates Answer Holding.
e. Verify the mobile station sends a Connect Order in assured mode.
f. Instruct the mobile station to deactivate the answer holding.
g. Verify the mobile station sends a Flash With Information Message or an Extended Flash With Information Message in assured mode with a Keypad Facility information record with the CHARi field set to a pre-programmed feature code (i.e., Switch Control Code: 18*) which indicates Answer Holding.
h. Verify user data in both directions.
9.20.5 Minimum Standard
The mobile station shall comply with steps d, e, g and h.
9.21 User Selective Call Forwarding
9.21.1 Definition
These tests verify that the mobile station that supports User Selective Call Forwarding can perform the following in both Waiting for Mobile Station Answer Substate and Conversation Substate:
a. Forwarding incoming call to a pre-registered number
b. Forwarding incoming call to a number stored in the mobile station
c. Forwarding incoming call to network-based voice mail
9.21.2 Traceability (See [4])
2.6.10.1.2 Waiting for Mobile Station Answer Substate
2.6.10.2 Conversation Substate
2.7.2.3.2.3 Flash with Information Message
2.7.2.3.2.33 Extended Flash with Information Message
2.7.4.2 Keypad Facility
3.6.8.1.2 Waiting for Answer Substate
9.21.3 Call Flow Example(s)
None
9.21.4 Method of Measurement
9.21.4.1 User Selective Call Forwarding in the Waiting for Mobile Station Answer Substate
a. Power on the mobile station and wait until it reaches Idle State.
9-23
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
33 34
35 36
37
b. Dial user selective call forwarding feature activation code, followed by the forward-to number, followed by SEND. Verify feature update confirmation at the mobile station.
c. Setup a mobile station terminated call from land party.
d. When the mobile station is ringing and ring back tone is applied to the audio path, instruct the mobile station to forward the incoming call to the pre-registered number.
e. Verify the mobile station sends a Flash With Information Message or an Extended Flash With Information Message in assured mode with a Keypad Facility information record with the CHARi field set to a pre-programmed feature code (i.e., Switch Control Code: 0*), which indicates User Selective Call Forwarding to a pre-registered number.
f. Answer the call on the forwarded line, and verify the audio path.
g. End call.
h. Ensure the mobile station is in Idle State.
i. Setup a mobile station terminated call from land party.
j. When the mobile station is ringing and ring back tone is applied to the audio path, instruct the mobile station to forward the incoming call to voice mail.
k. Verify the mobile station sends a Flash With Information Message or an Extended Flash With Information Message in assured mode with a Keypad Facility information record with the CHARi field set to a pre-programmed feature code (i.e. Switch Control Code: 17*) which indicates User Selective Call Forwarding to voice mail.
l. Verify the call is forwarded to voice mail.
m. Ensure the mobile station is in Idle State.
n. Program a forward-to-number in the mobile station.
o. Setup a mobile station terminated call from land party.
p. When the mobile station is ringing, and ring back tone is applied to the audio path, instruct the mobile station to forward the incoming call to the number stored in the mobile station.
q. Verify the mobile station sends a Flash With Information Message or an Extended Flash With Information Message in assured mode with a Keypad Facility information record with the CHARi field set to a pre-programmed feature code (i.e. Switch Control Code: 16*) plus the forward-to-number stored in the mobile station.
r. Answer the call on the forwarded line, and verify the audio path.
9.21.4.2 User Selective Call Forwarding while in the Conversation Substate
a. Setup a call between mobile station and land party 1 and verify user data in both directions.
b. Setup a call from land party 2 to the mobile station. Wait for ring back on land party 2 and the call waiting notification on the mobile station.
c. Instruct the mobile station to forward the incoming call to the pre-registered number.
9-24
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
33
34
35
d. Verify the mobile station sends a Flash With Information Message or an Extended Flash With Information Message in assured mode with a Keypad Facility information record with the CHARi field set to a pre-programmed feature code (i.e., Switch Control Code: 0*), which indicates User Selective Call Forwarding to a pre-registered number.
e. Answer the call on the forwarded line, and verify the audio path.
f. End call.
g. Setup a call between mobile station and land party 1 and verify user data in both directions.
h. Setup a call from land party 2 to the mobile station. Wait for ring back on land party 2 and the call waiting notification on the mobile station.
i. Instruct the mobile station to forward the incoming call to voice mail.
j. Verify the mobile station sends a Flash With Information Message or an Extended Flash With Information Message in assured mode with a Keypad Facility information record with the CHARi field set to a pre-programmed feature code (i.e. Switch Control Code: 17*) which indicates User Selective Call Forwarding to voice mail.
k. Verify the call is forwarded to voice mail.
l. End call.
m. Setup a call between mobile station and land party 1 and verify user data in both directions.
n. Setup a call from land party 2 to the mobile station. Wait for ring back on land party 2 and the call waiting notification on the mobile station.
o. Instruct the mobile station to forward the incoming call to the forward-to-number stored in the mobile station.
p. Verify the mobile station sends a Flash With Information Message or an Extended Flash With Information Message in assured mode with a Keypad Facility information record with the CHARi field set to a pre-programmed feature code (i.e. Switch Control Code: 16*) plus the forward-to-number stored in the mobile station.
q. Answer the call on the forwarded line, and verify the audio path.
r. End call.
9.21.5 Minimum Standard
9.21.5.1 User Selective Call Forwarding in the Waiting for Mobile Station Answer Substate
The mobile station shall comply with steps e, k, and q.
9.21.5.2 User Selective Call Forwarding while in the Conversation Substate
The mobile station shall comply with steps d, j, and p.
9-25
C.S0044-0 v1.0
10 ASYNCHRONOUS DATA AND FAX SERVICES 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
10.1 Send/Receive Fax
10.1.1 Definition
These tests demonstrate cellular system ability to transmit and receive a medium size fax in a timely manner. A fax call is originated by the mobile station and the test is then repeated using land line origination. The mobile station will send and receive a digital and an analog Fax.
10.1.2 Traceability (see [15])
A.3 Data Service Options for Spread Spectrum Systems: AT Command Processing and the Rm Interface
2.2 Data Service Selection
2.2.1 Service Selection for Async Data and Fax Services
4.0 AT COMMAND PROCESSING FOR ASYNC DATA AND FAX SERVICES
4.3 Service Class 2.0 AT Commands
7.3 Facsimile Service Class 2.0 AT Commands
A.4 Data Service Options for Spread Spectrum Systems: Async Data and Fax Services
2.2 The Application Interface
2.5.5 Requirements for Async Data and Fax
3.1 Service Option Number
3.2 Multiplex Option Interface
3.3 Procedures Using Service Option Negotiation
3.3.1.1 Mobile Station Requirements
3.4.1 Mobile Station Requirements
4.1.1 Mobile Origination
4.1.2 Mobile Termination
4.1.3 Service Option Change to Group-3 Facsimile Service
4.2 Connection Release
A.7 Data Service Options for Spread Spectrum Systems: Analog Fax Service
10.1.3 Call Flow Example(s)
None
10-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
33
34
10.1.4 Method of Measurement
10.1.4.1 Send/Receive Digital Fax
a. Prepare a file representing three different ITU standard fax pages for fax transfer. Data Services Annex C lists standard fax pages to be used in the test. Ensure fax pages are pre-scanned and pre-encoded.
b. Simultaneously start the transfer timer and the digital fax transfer from TE2M to TE2L.
c. At TE2L, wait for the fax call to be completed. Stop the transfer timer.
d. Record transfer time. Verify transfer time requirements per Data Services Annex C.
e. Repeat the test for the same fax sent from TE2L to TE2M. TE2M will receive a digital fax.
f. Verify all faxes shall be successfully transferred. The received fax shall be of good quality and complete. This can be verified by qualitative means (visually scanning the received fax) or by quantitative means, for example, using ITU-T Recommendation E.453 (08/94) Facsimile Image Quality as Corrupted by Transmission Induced Scan Line Errors.
10.1.4.2 Send/Receive Analog Fax
a. Prepare a file representing three different ITU standard fax pages for fax transfer. Data Services Annex C lists standard fax pages to be used in the test. Ensure fax pages are pre-scanned and pre-encoded.
b. Attach an Analog Fax Machine to TE2M.
c. Simultaneously start the transfer timer and the analog fax transfer from TE2M to TE2L.
d. At TE2L, wait for the fax call to be completed. Stop the transfer timer.
e. Record transfer time. Verify transfer time requirements per Data Services Annex C.
f. Repeat test for the same fax sent from TE2L to TE2M. TE2M will receive an analog fax.
g. Verify all faxes shall be successfully transferred. The received fax shall be of good quality and complete. This can be verified by qualitative means (visually scanning the received fax) or by quantitative means, for example, using ITU-T Recommendation E.453 (08/94) Facsimile Image Quality as Corrupted by Transmission Induced Scan Line Errors.
h. Verify each analog fax transfer shall be completed within time denoted in Data Services Annex C.
10.1.5 Minimum Standard
10.1.5.1 Send/Receive Digital Fax
The mobile station shall comply with steps d and f.
10-2
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
10.1.5.2 Send/Receive Analog Fax
The mobile station shall comply with steps e, g, and h.
10.2 Upload/Download Binary File
10.2.1 Definition
This test demonstrates cellular system ability to upload and download an ITU standard fax binary file in a timely manner. The asynchronous data call is originated first by the mobile station. The test is then repeated using land line origination.
10.2.2 Traceability (see [15])
A.3 Data Service Options for Spread Spectrum Systems: AT Command Processing and the Rm Interface
2.2 Data Service Selection
2.2.1 Service Selection for Async Data and Fax Services
4.0 AT COMMAND PROCESSING FOR ASYNC DATA AND FAX SERVICES
4.3 Service Class 2.0 AT Commands
7.3 Facsimile Service Class 2.0 AT Commands
A.4 Data Service Options for Spread Spectrum Systems: Async Data and Fax Services
2.2 The Application Interface
2.5.5 Requirements for Async Data and Fax
3.1 Service Option Number
3.2 Multiplex Option Interface
3.3 Procedures Using Service Option Negotiation
3.3.1.1 Mobile Station Requirements
3.4.1 Mobile Station Requirements
4.1.1 Mobile Origination
4.1.2 Mobile Termination
4.1.3 Service Option Change to Group-3 Facsimile Service
4.2 Connection Release
10.2.3 Call Flow Example(s)
None
10.2.4 Method of Measurement
a. Prepare the RAND200.BIN 200,000 byte binary file for transfer (Data Services Annex D).
10-3
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
33
34
b. Setup a data call from TE2M to TE2L.
c. Start transferring the binary file from TE2L to TE2M using Z-modem transfer protocol. Start the transfer timer.
d. Stop the transfer timer when the confirmation of transfer completion is received from the far end.
e. Record the transfer time.
1. Note: Transfer time should exclude call connection delay.
f. End the data call.
g. Setup a data call from TE2L to TE2M.
h. Repeat the test by transferring the file from TE2M to TE2L.
i. Verify:
1. All files shall be successfully transferred.
2. There shall be no Z-modem protocol re-transmissions.
3. Received files shall be complete and identical in content to the original file.
4. Each file transfer shall be completed within time denoted in Data Services Annex D.
5. Both the mobile station originated, and land line originated data calls shall be established successfully.
10.2.5 Minimum Standard
The mobile station shall comply with step i.
10.3 Simultaneous Two-way File Transfer/Carrier Detect
10.3.1 Definition
This test demonstrates cellular system ability to simultaneously transfer data in the forward and reverse link direction. This test verifies the base station can transmit changes in the status of Carrier Detect and reflect its status on the Rm interface.
Note: Carrier Detect can be monitored by means of a hardware lead, or observed on the application interface.
10.3.2 Traceability (see [15])
A.3 Data Service Options for Spread Spectrum Systems: AT Command Processingand the Rm Interface
2.2 Data Service Selection
2.2.1 Service Selection for Async Data and Fax Services
4.0 AT COMMAND PROCESSING FOR ASYNC DATA AND FAX SERVICES
4.3 Service Class 2.0 AT Commands
10-4
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 33
7.3 Facsimile Service Class 2.0 AT Commands
A.4 Data Service Options for Spread Spectrum Systems: Async Data and Fax Services
2.2 The Application Interface
2.5.5 Requirements for Async Data and Fax
3.1 Service Option Number
3.2 Multiplex Option Interface
3.3 Procedures Using Service Option Negotiation
3.3.1.1 Mobile Station Requirements
3.4.1 Mobile Station Requirements
4.1.1 Mobile Origination
4.1.2 Mobile Termination
4.1.3 Service Option Change to Group-3 Facsimile Service
4.2 Connection Release
10.3.3 Call Flow Example(s)
None
10.3.4 Method of Measurement
a. Prepare the RAND200.ASC 200,000 byte ASCII file for transfer (Data Services Annex D).
b. Ensure the Carrier Detect indicator is enabled at TE2M.
c. From TE2M, issue the command “AT&C1”, which requests the real-time status of Carrier Detect be maintained on the Rm interface.
d. Verify the Carrier Detect indicator is OFF.
e. Setup a data call from TE2M to TE2L. Verify that Carrier Detect indicator goes ON, when the base station modem has successfully trained.
f. Verify characters typed at TE2M can be viewed at TE2L. Verify characters typed at TE2L can be viewed at TE2M.
1. Note: Once the File Capture is turned on, do not type any more characters on the TE2L or the TE2M prior to initiating the file transfer (this is to ensure the captured file is not corrupted by user keystrokes).
g. Turn on the File Capture at TE2M.
h. Turn on the File Capture at TE2L.
i. Simultaneously start the reverse link transfer timer and at TE2M send the RAND200.ASC file to TE2L by using Raw ASCII protocol.
10-5
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
j. While TE2M is sending the file to TE2L, simultaneously start the forward link transfer timer and instruct TE2L to send the same ASCII file to TE2M using a Raw ASCII protocol.
1. Note: It is critical these transfers shall substantially overlap.
k. As each transfer completes, stop corresponding transfer timer and record transfer time.
l. After both transfers are complete, turn off the File Capture at both TE2M and TE2L.
m. End call.
n. At TE2M, verify that Carrier Detect indicator goes OFF when the call is ended.
o. Verify:
1. The file shall be successfully transferred in each direction.
2. Log files shall be complete and identical in content to the original files.
3. Each file transfer shall be completed within time denoted in Data Services Annex D.
4. The Carrier Detect generated by the base station shall be accurately depicted on the Rm interface.
10.3.5 Minimum Standard
The mobile station shall comply with steps d, e, f, n, and o.
10.4 Compound AT Command, Initialization and Connection Delay
10.4.1 Definition
This test verifies the base station can properly process a compound command line containing both local and remote commands. This test verifies the mobile station can initialize and connect the service option when the data call is negotiated with the base station, as well as measures connection delay.
10.4.2 Traceability (see [15])
A.3 Data Service Options for Spread Spectrum Systems: AT Command Processing
and the Rm Interface
4.2.6 Basic Result Codes
Table 4.2.6-1. Result Code Sources
4.3.1.2.5 +FMI, +FMM, +FMR
4.4.1 General Requirements
Table 7.2-1 Extended AT Configuration Commands
Table 7.3.1-1 Fax Parameters
10-6
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 33
10.4.3 Call Flow Example(s)
None
10.4.4 Method of Measurement
a. Ensure the call is down.
b. At TE2M, issue AT command “AT+CXT=1;+FCLASS=2.0;+GMI;+CGMI;+GMM;+CGMM”. This command string requests mobile station manufacturer information, base station modem manufacturer information, mobile station manufacturer model, and base station modem manufacturer model.
c. Start the connection delay timer.
d. When the result is returned to the mobile station, stop the connection timer.
e. Record connection delay time in the test report.
f. Verify the response shall be correct in that it contains the information requested in the command, and is followed by result code “OK”. Delay should not exceed ten seconds.
10.4.5 Minimum Standard
The mobile station shall comply with step f.
10.5 Escaping to Command Mode
10.5.1 Definition
This test verifies:
a. The MT2 application interface escapes to online command state when the user (or the communications application) issues an escape sequence (such as "+++" with the appropriate guard time).
b. The base station returns to online state when the user (or the application) issues the command "ATO".
10.5.2 Traceability (see [15])
4.2.4 Call-Control Command Processing
4.4.2.1 Return to Online Command State
10.5.3 Call Flow Example(s)
None
10.5.4 Method of Measurement
a. Setup a data call from TE2M to TE2L.
b. Verify characters typed at TE2M can be viewed at TE2L. Verify that characters typed at TE2L can be viewed at TE2M.
10-7
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
c. From TE2M issue the escape sequence +++.
d. Verify “OK” is returned, signifying that the MT2 is in the online command state.
e. At TE2M,issue the command “AT+CGMI" which requests base station manufacturer information. Verify the response is appropriate, with trailing “OK”.
f. At TE2M, issue the command “ATO”, which should cause the MT2 to transition from online command state to online state.
g. Verify characters typed at TE2M can be viewed at TE2L. Verify characters typed at TE2L can be viewed at TE2M.
h. Verify the escape sequence shall cause entry into the online command state.
i. Verify the command “ATO” shall cause return from the online command state to online state.
10.5.5 Minimum Standard
The mobile station shall comply with steps b, d, e, g, h, and i.
10.6 Air Interface Data Compression
10.6.1 Definition
This test verifies successful compression option negotiation and the transfer of compressible files and/or faxes between the MT2 and Inter-Working Function (IWF). The aforementioned is verified for both mobile station originated and mobile station terminated data and fax transmissions.
Note: Although the files are compressible, they will be compressed only when both the MT2 and IWF support the type of compression in question. Even if the MT2 or IWF do not support a certain type of compression, the test in question may be performed to ensure MT2 and IWF still interoperate correctly when the user requests this type of compression.
10.6.2 Traceability (see [15])
A.3 Data Service Options for Spread Spectrum Systems: AT Command Processing
and the Rm Interface
Table 7.4.1-1 CDMA AT Parameter Commands
A.4 Data Service Options for Spread Spectrum Systems: Async Data and Fax Services
2.2 The Application Interface
Table 2.2-2 Compression Options
Table 2.2-3 Group 3 Fax Compression Options
10.6.3 Call Flow Example(s)
None
10-8
C.S0044-0 v1.0
10.6.4 Method of Measurement 1
2 3
4 5 6 7
0.6.4-18
9
a. Prepare the data file, COMPFILE.RAW (see Data Services Annex A), or the fax page, FAX 1 (see Data Services Annex C) for transfer.
b. Configure the test setup for transfer of a data file or a fax file per Table 10.6.4-1. V.42bis compression for data file transfers is controlled by the +CDS command. The type of compression for fax file transfers is controlled by the +CFC command. When V.42bis is selected for fax transfer, the parameters set in the +CDS command are used.
c. Setup a mobile station originated fax or async data call per Table 1 .
Table 10.6.4-1
Test No.
File/Fax CompressionMethod
Direction of Transfer
Compression Enable
Fax 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
0.6.4-111 12
13
14
15
16 17
18
19 20 21
d. Make a file or fax transfer in the direction as stated in Table 1 . Time each transfer and record in the test report.
e. Testing may be repeated for all test cases, 1 through 10.
f. Verify:
1. All faxes shall be successfully sent and received.
2. The received fax page shall be complete in content, and each transfer shall be completed within the time stated in Data Services Annex C.
3. All data files shall be successfully transferred.
4. The received files shall be complete and identical in content to the original file. Each file transfer shall be completed within the time stated in Data Services Annex B.
10-9
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
10.6.5 Minimum Standard
The mobile station shall comply with step f.
10.7 RLP Operation in a Poor RF Environment
10.7.1 Definition
This test exercises the Radio Link Protocol (RLP) layer's negative acknowledgments (NAKs), re-transmits, RLP aborts, RLP Resets, and FCSs.
Test conditions are intended to impose one or more occurrences of the following.
a. Single, double, and triple NAK RLP retransmit events.
b. RLP Abort
c. RLP Reset
d. This test verifies that RLP recovers erased data frames in various channel conditions.
10.7.2 Traceability (see [15])
A.2 Data Service Options for Spread Spectrum Systems: Radio Link Protocol
3.1 Non-Transparent RLP Procedures
3.1.1.1 Non-Encrypted Mode Initialization/Reset
3.1.2 Data Transfer
3.1.4 Segmentation of Retransmitted Data Frames
10.7.3 Call Flow Example(s)
None
10.7.4 Method of Measurement
a. Setup the mobile station and base station as shown in Figure A-9with an AWGN generator placed in the forward link.
b. Environment Test Parameters
c. Adjust the level of the AWGN Generator so that the downlink frame error rate is measured to be 3±1%.
d. Restore the RF link to a normal operating condition, maintaining the target frame error rate (1 % or less).
e. Prepare RAND200.ASC 200,000 byte ASCII file for transfer (Data Services Annex D).
f. Setup a data call from TE2M to TE2L.
g. Verify characters typed at TE2M can be viewed at TE2L. Verify characters typed at TE2L can be viewed at TE2M.
h. Turn File Capture on.
10-10
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
i. Simultaneously start the forward link transfer timer and at TE2L send the RAND200.ASC file to TE2M by using Raw ASCII protocol.
j. As soon as the file transfer has started (and is still in progress), set the channel conditions as calibrated in step b. These channel conditions shall be maintained for the duration of the file transfer.
k. Stop the transfer timer and record the transfer time.
l. Turn off the File Capture.
m. End call.
n. Setup a data call from TE2M to TE2L.
o. Repeat steps f and g.
p. Simultaneously start the reverse link transfer timer and at TE2M send the RAND200.ASC file to TE2L by using Raw ASCII protocol.
q. Repeat steps i through l.
r. Verify:
1. The file shall be successfully transferred.
2. The log file shall be complete and identical in content to the original file.
3. The transfer rate shall be no less than 70% of rates measured in test 10.3.
10.7.5 Minimum Standard
The mobile station shall comply with steps f, q, and r.
10.8 RLP Abort and TCP Retransmit Test
10.8.1 Definition
This test causes the RLP layer to abort and reset due to extremely severe CDMA channel conditions, and forces the TCP layer to retransmit packets. Channel degradation consists of forcing consecutive frame erasures for periods greater than 2.6 seconds.
Note: 2.6 seconds corresponds to 130 consecutive frame erasures, but less than the time that would cause the call to drop (typically 5 seconds).
10.8.2 Traceability (see [15])
A.2 Data Service Options for Spread Spectrum Systems: Radio Link Protocol
3.1 Non-Transparent RLP Procedures
3.1.1.1 Non-Encrypted Mode Initialization/Reset
3.1.2 Data Transfer
3.1.4 Segmentation of Retransmitted Data Frames
10-11
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
33
34 35
10.8.3 Call Flow Example(s)
None
10.8.4 Method of Measurement
a. Setup the mobile station and base station as shown in Figures Annex A Figure A-7 and Annex A Figure A-8 for the forward and the reverse link tests respectively, with PWR_THRESH_ENABLE and PWR_PERIOD_ENABLE set to 0. Disable forward link power control at the base station.
b. Calibrate the test setup so that:
c. There is sufficient isolation with the switch open, that a call drops if the switch is left open for more than 5 seconds
d. When switch is open, the forward and reverse links are disabled at the receiver.
e. When switch is closed, the forward and reverse links are enabled at the receiver.
f. Set the RF link to normal operating condition, which maintains the target frame erasure rate (1% or less).
g. Prepare the RAND200.ASC 200,000 byte ASCII file transfer (Data Services Annex D)
h. Setup a call from TE2M to TE2L.
i. Verify characters typed at TE2M can be viewed at TE2L. Verify that characters typed at TE2L can be viewed at TE2M.
j. Turn File Capture on.
k. Simultaneously start the forward link transfer timer and at TE2L send the RAND200.ASC file to TE2M by using Raw ASCII protocol.
l. Once the file transfer has started (and is still in progress), open and close the switch in an alternating fashion, for periods of T1 and T2 where:
1. T1 is the period when the switch is open (RF link impaired), and it is anywhere between 2.6 and 5.0 seconds.
2. T2 is the period when the switch is closed (RF link restored), and it is a minimum of 10 seconds.
m. Repeat opening and closing switch exactly three times while data transfer is occurring.
n. Stop the transfer timer and record the transfer time.
o. Turn the File Capture off.
p. End call.
q. Setup a data call from TE2M to TE2L.
r. Repeat steps f and g.
s. Simultaneously start the reverse link transfer timer and at TE2M send the RAND200.ASC file to TE2L by using Raw ASCII protocol.
10-12
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
t. Repeat steps i through l.
u. Verify:
1. The file shall be successfully transferred in each direction.
2. Log files shall be complete and identical in content to the original files.
3. Transfer rates shall be no less than 50% of rates measured in test 10.3.
10.8.5 Minimum Standard
The mobile station shall comply with steps i and u.
10.9 Internet Control Message Protocol (ICMP) Requests/Replies
10.9.1 Definition
This test verifies the mobile station is able to:
a. Generate an ICMP Echo Response Message after receiving an Echo Request Message.
b. Generate an ICMP Info Response Message after receiving an Info Request Message.
c. Generate an ICMP Time Stamp Response Message after receiving a Time Stamp Request Message.
10.9.2 Traceability (see [23])
RFC-792 Internet Control Message Protocol
10.9.3 Call Flow Example(s)
None
10.9.4 Method of Measurement
a. At TE2M, issue a remote query command such as “AT+CXT=1;+FCLASS=2.0;+FMI?”, requesting base station modem manufacturer information. This will establish a link to the base station.
b. From the OA&M interface of the base station, issue the Echo Request Message by any method specific to the base station manufacturer.
c. Optionally, step b may be repeated for Info Request/Response, or Time Stamp Request/Response Messages.
d. Verify:
1. Echo response shall be received by base station as a response to Echo Request Message.
2. If supported by mobile station, an Info response shall be received by base station as a response to Info Request Message.
10-13
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
3. If supported by mobile station, a Time stamp response shall be received by base station as a response to Time Stamp Request Message.
10.9.5 Minimum Standard
The mobile station shall comply with step d.
10.10 Reflection of AT Command Parameters
10.10.1 Definition
This test verifies a representative set of AT parameters can be setup in an IS-707-A call, transferred to the base station at call origination, changed in the online command state, and have their final values read at the mobile station after call completion. Commands tested are ATS10 and AT+CQD.
10.10.2 Traceability (see [15])
A.3 Data Service Options for Spread Spectrum Systems: AT Command Processing
and the Rm Interface
4.2.4 Call-Control Command Processing
7.4.1 CDMA AT Parameters
10.10.3 Call Flow Example(s)
None
10.10.4 Method of Measurement
a. Issue the following AT commands: ATS10=255 and AT+CQD=0”
b. Verify response is “OK”
c. Setup a data call from TE2M to TE2L.
d. After CONNECT is received, issue the escape sequence (such as ”+++”).
e. Verify the response is “OK”
f. Issue the following AT commands: ATS10?and AT+CQD?.
g. Verify response is:
1. 255
2. +CQD:0
3. OK
h. Issue the following AT commands : “ATS10=250 and AT+CQD=100”
i. Verify the response is “OK”
j. Issue the following AT commands : ATS10?and AT+CQD?.
k. Verify the response is:
10-14
C.S0044-0 v1.0
1
2
3
4
5
6
7
8
9
10
11
12
13
1. 250
2. +CQD:100
3. OK
l. Terminate the call via the “ATH0” command string.
m. Verify the response is “OK” and that the call ends.
n. Issue the following AT commands: ATS10?and AT+CQD
o. Verify response is:
1. 250
2. +CQD:100
3. OK
p. Verify the “ERROR” response shall not be returned.
10.10.5 Minimum Standard
The mobile station shall comply with steps b, e, g, i, k, m, o, and p.
10-15
C.S0044-0 v1.0
11 LOW SPEED PACKET DATA 1
2
3
4 5
6
7
8
9
10
11
12
13
14 15
c. 16 17
18
19 20
21 22
23
24
25
26
27 28
29
30
31
11.1 Forward File Transfer
11.1.1 Definition
This test verifies that file transfer from remote host to mobile station can be successfully done using the LSPD call.
11.1.2 Traceability (see [15])
1.4.2.2 Mobile Station Packet Data Service States
2.2.2 Service and Call Control Procedures
2.2.3 Initialization and Connection of Packet Data Service Options
11.1.3 Call Flow Example(s)
None
11.1.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Annex A Figure A-6.
b. At the remote host prepare the RAND200.BIN 200,000 byte binary file for transfer (Data Services Annex D).
Setup an FTP session using Service Option 7 for Rate Set 1 or Service Option 15 for Rate Set 2 with the remote host.
d. Transfer the file from the remote host to the TE2M using the binary “get” command.
e. After the file transfer is completed, end the FTP session. Verify the file is successfully transferred.
f. Steps b through e may be repeated for other data rates supported by both mobile station and base station.
11.1.5 Minimum Standard
The mobile station shall comply with step e.
11.2 Reverse File Transfer
11.2.1 Definition
This test verifies that file transfer from mobile station to remote host can be successfully done using the LSPD call.
11.2.2 Traceability (see [15])
1.4.2.2 Mobile Station Packet Data Service States
2.2.2 Service and Call Control Procedures
11-1
C.S0044-0 v1.0
2.2.3 Initialization and Connection of Packet Data Service Options 1
2
3
4
a. 5
6 7
c. 8 9
10
11 12
13 14
15
16
17
18
19
20
21
22
23
24
25
26
a. 27
28 29
c. 30 31
d. 32
11.2.3 Call Flow Example(s)
None
11.2.4 Method of Measurement
Connect the mobile station to the base station as shown in Annex A Figure A-6.
b. At the TE2M, prepare the RAND200.BIN 200,000 byte binary file for transfer (Data Services Annex D).
Setup an FTP session using Service Option 7 for Rate Set 1 or Service Option 15 for Rate Set 2 with the remote host.
d. Transfer the file from the TE2M to the remote host using the binary “put” command.
e. After the file transfer is completed, end the FTP session. Verify the file is successfully transferred.
f. Steps b through e may be repeated for other data rates supported by both mobile station and base station.
11.2.5 Minimum Standard
The mobile station shall comply with step e.
11.3 Bi-directional File Transfer
11.3.1 Definition
This test verifies that bi-directional file transfer can be successfully done using the LSPD call.
11.3.2 Traceability (see [15])
1.4.2.2 Mobile Station Packet Data Service States
2.2.2 Service and Call Control Procedures
2.2.3 Initialization and Connection of Packet Data Service Options
11.3.3 Call Flow Example(s)
None
11.3.4 Method of Measurement
Connect the mobile station to the base station as shown in Annex A Figure A-6.
b. Prepare the RAND200.BIN 200,000 byte binary file for transfer (Data Services Annex D) at both the remote host and TE2M.
Setup an FTP session using Service Option 7 for Rate Set 1 or Service Option 15 for Rate Set 2 with the remote host.
Transfer the file from the TE2M to the remote host.
11-2
C.S0044-0 v1.0
e. Transfer the file from the Remote Host to the TE2M while the transfer in the reverse direction is still proceeding.
1 2
3 4
5 6
7
8
9
10
11 12 13 14
15
16
17
18
19
20 21
22
23
24
25 26
27
28
29 30
31 32
33
34
f. After the file transfers are completed, end the FTP sessions. Verify the files are successfully transferred.
g. Steps b through f may be repeated for different data rates that are supported by both mobile station and base station.
11.3.5 Minimum Standard
The mobile station shall comply with step f.
11.4 Mobile Station Packet Data Inactivity Timer
11.4.1 Definition
This test is required for mobile stations that shall have a mobile station packet data inactivity timer. This test verifies the mobile station releases the traffic channel after expiration of the mobile station packet data inactivity timer. The test verifies the dormant link layer connection can be re-activated.
11.4.2 Traceability
11.4.3 Call Flow Example(s)
None
11.4.4 Method of Measurement
a. Set the packet data inactivity timer at the MT2 to 20 seconds.
b. Ensure the base station packet data inactivity timer is disabled or set to a value of at least 30 seconds.
c. Initiate a Telnet session to a remote host.
d. Record the IP address assigned to the mobile station.
e. Exit the Telnet session.
f. Wait for the mobile station packet data inactivity timer to expire. Verify the “in use” indicator on the MT2 goes OFF.
g. Initiate a Telnet session to a remote host.
h. Record the IP address assigned to the mobile station.
i. Wait for the mobile station packet data inactivity timer to expire. Verify the “in use” indicator on the MT2 goes OFF.
j. Issue a “ping” command from the remote host to the mobile station using the IP address assigned to the mobile station.
11.4.5 Minimum Standard
The mobile station shall comply with steps f and i.
11-3
C.S0044-0 v1.0
12 MEDIUM SPEED PACKET DATA 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
12.1 Forward File Transfer with Fundamental and Supplemental Code Channels
12.1.1 Definition
This test verifies the functionality of forward MSPD calls for various MUX options:
• No Supplemental Code Channels allocated (Test 1).
• One Supplemental Code Channel allocated (Test 2).
• N Supplemental Code Channels allocated, where N is the maximum number of Supplemental Code Channels that can be supported by the system (Test 3).
12.1.2 Traceability:
[2] 2.2.1.1.1 The Multiplex Sublayer
[4] 3.6.6.2.2.9 Processing the Supplemental Channel Assignment Message
[4] 3.6.6.2.2.10 Processing the General Handoff Direction Message
[15] A-9; 2.2.2.1.1 Packet Data Service Control Procedures
12.1.3 Call Flow Example(s)
None
12.1.4 Method of Measurement
a. Prepare a file at the remote host for file transfer (see Annex D).
b. Setup an FTP session using Service Option 22 with the remote host. From the base station, generate a General Handoff Direction Message or a Supplemental Channel Assignment Message to allocate Supplemental Code Channels to the mobile station according to the following conditions:
1) For Test 1, the base station shall allocate no Supplemental Code Channel to the mobile station (i.e. MUX Option = 1).
2) For Test 2, the base station shall allocate one Supplemental Code Channel to the mobile station (i.e. MUX Option = 3).
3) For Test 3, the base station shall allocate N Supplemental Code Channels to the mobile station (i.e. MUX Option = 2N+1).
c. Transfer the file from the remote host to the TE2M using the binary “get” command.
d. Verify the file is successfully transferred.
e. After the file transfer is completed, end the FTP session
f. Repeat steps b through e for Tests 2 and 3.
g. Repeat steps b through f for Tests 1, 2, and 3 with Service Option 25.
12-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
33
12.1.5 Minimum Standard
Verify step d for all test cases.
12.2 Forward File Transfer with Variable Supplemental Code Channels
12.2.1 Definition
This test verifies the capability to transfer files from a remote host using FTP, with a variable number of Supplemental Code Channels. This test is intended to exercise bursty data transfer with variable peak transfer rates.
This test may require the use of an OA&M interface on the base station, or any other method specific to the base station manufacturer, in order to vary the number of allocated Supplemental Code Channels.
12.2.2 Traceability:
[2] 2.2.1.1.1 The Multiplex Sublayer
[4] 3.6.6.2.2.9 Processing the Supplemental Channel Assignment Message
[4] 3.6.6.2.2.10 Processing the General Handoff Direction Message
[15] A-9; 2.2.2.1.1 Packet Data Service Control Procedures
12.2.3 Call Flow Example(s)
None
12.2.4 Method of Measurement
a. Prepare a file at the remote host for file transfer (see Annex D).
b. Configure the mobile station’s maximum forward Supplemental Code Channels to N.
c. Configure the base station to support N Supplemental Code Channels.
d. Setup a mobile station terminated call with Service Option 22, and establish an FTP session.
e. From the base station, generate a General Handoff Direction Message to allocate N Supplemental Code Channels to the mobile station.
f. Verify from the mobile station that N Supplemental Code Channels are being used.
g. Transfer the file from the remote host to TE2M using the binary “get” command.
h. During through the file transfer, configure the base station to generate a General Handoff Direction Message or a Supplemental Channel Assignment Message to reduce the number of Supplemental Code Channels allocated to the mobile station.
i. Verify the file is successfully transferred.
j. End FTP session.
k. Repeat steps d through j with Service Option 25.
12-2
C.S0044-0 v1.0
12.2.5 Minimum Standard 1
2
3
4
5 6 7
8
9
10
11
12
12.3.4 13
14
15 16
17
18 19
20
f. 21
g. 22 23
24 25
26
27 28
29
30 31
32
n. 33
Verify steps f and i for all test cases.
12.3 MSPD Call Setup, No Negotiation
12.3.1 Definition
This test verifies that the base station and the mobile station can successfully establish mobile station-originated and mobile station-terminated calls using all combinations of supported Service Option 22 and Service Option 25, using the default multiplex options.
12.3.2 Traceability:
[15]-A9; 2.2.2.1.2.5 Dormant/Idle State
[2] 2.2.1.1.1 The Multiplex Sublayer
12.3.3 Call Flow Example(s)
None
Method of Measurement
a. Prepare a file at both the remote host and the TE2M (see Annex D).
b. Configure the mobile station’s forward MUX Option to (2N+1) where N is the maximum number of Supplemental Code Channels.
c. Configure the base station’s MUX Option to a value equal to (2N+1).
d. Setup a mobile station originated call with Service Option 22, and establish an FTP session with the remote host.
e. Verify the call is completed with Service Option 22.
Verify that N Supplemental Code Channels are being used by the mobile station.
Transfer the file from remote host to TE2M using the binary “get” command and verify the file is successfully transferred.
h. After the file transfer is completed in step f, transfer the file from the TE2M to the remote host using the binary “put” command and verify the file is successfully transferred.
i. End FTP session.
j. Repeat steps d through i by initiating a mobile station terminated call with Service Option 22.
k. Configure the base station’s MUX Option to a value equal to (2N+2).
l. Setup a mobile station originated call with Service Option 25, and establish an FTP session with the remote host.
m. Verify the call is completed with Service Option 25.
Verify that N Supplemental Code Channels are being used by the mobile station.
12-3
C.S0044-0 v1.0
o. 1 2
3 4
5
6 7
8
9
10
11
12 13
14
15
16
17
18
12.4.4 19
20
21
22 23
24 25
e. 26
f. 27 28
29 30
31
32
Transfer the file from remote host to TE2M using the binary “get” command and verify the file is successfully transferred.
p. After the file transfer is completed in step o, transfer the file from the TE2M to the remote host using the binary “put” command and verify the file is successfully transferred.
q. End the FTP session.
r. Repeat steps l through q by initiating a mobile station terminated call with Service Option 25.
12.3.5 Minimum Standard
The mobile station shall comply with steps e, f, g, h, m, n, o and p.
12.4 MSPD Call Setup, Negotiation to a Different MSPD Service Option
12.4.1 Definition
This test verifies that the base station and the mobile station can successfully negotiate from Service Option 22 to Service Option 25, and vice versa.
12.4.2 Traceability:
[15]-A9; 2.2.2.1.2.5 Dormant/Idle State
[2] 2.2.1.1.1 The Multiplex Sublayer
12.4.3 Call Flow Example(s)
None
Method of Measurement
a. Prepare a file at both the remote host and the TE2M (see Annex D).
b. Configure the mobile station’s forward MUX Option to the default MUX Option.
c. Configure the base station’s Service Option to 25 and configure the base station’s MUX Option to a value equal to or greater than the mobile station’s MUX Option number.
d. Setup a mobile station originated call using Service Option 22, and establish an FTP session with the remote host.
Verify the call is negotiated to Service Option 25.
Transfer the file from the remote host to TE2M using the binary “get” command and verify the file is successfully transferred.
g. After the file transfer is completed in step f, transfer the file from the TE2M to the remote host using the binary “put” command and verify the file is successfully transferred.
h. End FTP session.
i. Configure the base station’s Service Option to 22.
12-4
C.S0044-0 v1.0
j. Setup a mobile station originated call using Service Option 25 and establish an FTP session with the remote host.
1 2
k. 3
l. 4 5
6 7
8
9
10
11
12
13 14
15
16
17
18
19
20
12.5.4.1 21
22
23
24 25
26
27
28
29
30 31
32
Verify the call is negotiated to Service Option 22.
Transfer the file from the remote host to TE2M using the binary “get” command and verify the file is successfully transferred.
m. After the file transfer is completed in step l, transfer the file from the TE2M to the remote host using the binary “put” command and verify the file is successfully transferred.
n. End FTP session.
12.4.5 Minimum Standard
The mobile station shall comply with steps e, f, g, k, l and m.
12.5 MSPD Call Setup, Negotiation to LSPD
12.5.1 Definition
This test verifies that the base station and the mobile station can successfully negotiate from MSPD to LSPD service options.
12.5.2 Traceability:
[15]-A9; 2.2.2.1.2.5 Dormant/Idle State
[2] 2.2.1.1.1 The Multiplex Sublayer
12.5.3 Call Flow Example(s)
None
12.5.4 Method of Measurement
MSPD-Capable Mobile station
a. Prepare a file at both the remote host and the TE2M (see Annex D).
b. Configure the base station to Service Option 7.
c. Setup a mobile station originated call with Service Option 22, and establish an FTP session with the remote host.
d. Verify the call is completed with Service Option 7.
e. Successively transfer files both directions and verify the files are successfully transferred.
f. End FTP session.
g. Configure the base station to Service Option 15.
h. Setup a mobile station originated call with Service Option 22, and establish an FTP session with the remote host.
i. Verify the call is completed with Service Option 15.
12-5
C.S0044-0 v1.0
j. Successively transfer files in both directions and verify the files are successfully transferred.
1 2
3
4
5 6
7
8 9
10
11
12 13
14
15 16
17
18
a. 19
20
21 22
23
24
25
26 27
28
29
30
31
32 33
34
k. End FTP session.
l. Configure the base station to Service Option 15.
m. Setup a mobile station originated call with Service Option 25, and establish an FTP session with the remote host.
n. Verify the call is completed with Service Option 15.
o. Successively transfer files in both directions and verify the files are successfully transferred.
p. End FTP session.
q. Configure the base station to Service Option 7
r. Setup a mobile station originated call with Service Option 25, and establish an FTP session with the remote host.
s. Verify the call is completed with Service Option 7.
t. Successively transfer files in both directions and verify the files are successfully transferred.
u. End FTP session.
12.5.4.2 Non MSPD-Capable Mobile station
Ensure the mobile station is not MDR capable.
b. Prepare a file at both the remote host and the TE2M.
c. Configure the mobile station with Service Option 15. This can be accomplished by issuing the AT command AT+CMUX=2,2.
d. Configure the base station to page the mobile station with Service Option 22.
e. Set up a mobile station terminated call and establish an FTP session.
f. Verify the call is completed with Service Option 15.
g. Successively transfer files in both directions and verify the files are successfully transferred.
h. End FTP session.
i. Configure the base station Service Option to 25.
j. Set up a mobile station terminated call and establish an FTP session.
k. Verify the call is completed with Service Option 15.
l. Successively transfer files in both directions and verify the files are successfully transferred.
m. End FTP session.
12-6
C.S0044-0 v1.0
12.5.5 Minimum Standard 1
2
3
4 5
6
7 8 9
10
11
12
13
14
15
12.6.4 16
17
18 19 20
21
22 23
e. 24
f. 25 26
27 28
29
30 31 32
33
34
In section 12.5.3.1, the mobile station shall comply with steps d, e, i, j, n, o, s and t.
In section 12.5.3.2, the mobile station shall comply with steps f, g, k and l.
12.6 MSPD Call Setup, Mobile Station Maximum Multiplex Option Less than Base Station Maximum Multiplex Option
12.6.1 Definition
This test verifies that an MSPD call can be successfully established when the maximum multiplex option supported by the mobile station is less than the maximum multiplex option supported by the base station.
12.6.2 Traceability:
[15]-A9; 2.2.2.1.2.5 Dormant/Idle State
[15]-A3; 7.4.1 CDMA AT Parameters
[2] 2.2.1.1.1 The Multiplex Sublayer
12.6.3 Call Flow Example(s)
None
Method of Measurement
a. Prepare a file at both the remote host and the TE2M (see Annex D).
b. Configure the mobile station’s maximum forward MUX Option to (2n+1) where n is equal to N or 6, whichever is smaller, where N is the maximum number of Supplemental Code Channels supported by the mobile station (i.e. set AT+CMUX=2n+1,1)
c. Configure the base station’s MUX Option to a value equal to (2(n+1)+1).
d. Setup a mobile station terminated call with Service Option 22, and establish an FTP session.
Verify the number of Supplemental Code Channels used to establish FTP session is n.
Transfer the file from the remote host to TE2M using the binary “get” command and verify the file is successfully transferred.
g. After the file transfer is completed in step f, transfer the file from the TE2M to the remote host using the binary “put” command verify the file is successfully transferred.
h. End FTP session.
i. Repeat steps d through h with Service Option 25 by setting the maximum forward MUX Option of the mobile station to (2n+2) and the MUX Option of the base station to (2(n+1)+2).
12.6.5 Minimum Standard
The mobile station shall comply with steps e, f and g for all test cases.
12-7
C.S0044-0 v1.0
12.7 MSPD Call Setup, Mobile station Maximum Multiplex Option Greater than Base Station Maximum Multiplex Option
1 2
3
4 5 6
7
8
9
10
11
12
12.7.4 13
14
15 16 17
18
19 20
e. 21 22
f. 23 24
25 26
27
28 29
30
31
12.7.1 Definition
This test verifies that an MSPD call can be successfully established when the maximum multiplex option supported by the mobile station is greater than the maximum multiplex option supported by the base station.
12.7.2 Traceability:
[15]-A3; 7.4.1 CDMA AT Parameters
[15]-A9; 2.2.2.1.2.5 Dormant/Idle State
[2] 2.2.1.1.1 The Multiplex Sublayer
12.7.3 Call Flow Example(s)
None
Method of Measurement
a. Prepare a file at both the remote host and the TE2M (see Annex D).
b. Configure the mobile station’s maximum forward MUX Option to (2N+1) where N is the maximum number of Supplemental Code Channels supported by the mobile station (i.e. set AT+CMUX=2N+1,1)
c. Configure the base station’s MUX Option to a value equal to (2(N-1)+1).
d. Setup a mobile station terminated call with Service Option 22, and establish an FTP session.
Verify the number of Supplemental Code Channels used in establishing the FTP session is (N-1).
Transfer the file from the remote host to TE2M using the binary “get” command and verify the file is successfully transferred.
g. After the file transfer is completed in step f, transfer the file from the TE2M to the remote host using the binary “put” command and verify the file is successfully transferred.
h. End FTP session.
i. Repeat steps d through h with Service Option 25 by setting the maximum forward MUX Option of the mobile station to (2N+2) and MUX Option of the base station to (2(N-1)+2).
12.7.5 Minimum Standard
The mobile station shall comply with steps e, f and g for all test cases.
12-8
C.S0044-0 v1.0
12.8 Allocation/De-allocation of Supplemental Code Channels 1
2
3 4 5 6 7 8 9
10
11
12
13
14
15
16
17
12.8.4.1 18
19
20 21 22
23 24
25 26
27 28 29
f. 30
31 32
33 34 35
i. 36
12.8.1 Definition
This test verifies allocation and de-allocation of up to N Supplemental Code Channels using the General Handoff Direction Message (GHDM), and Supplemental Code Channel Assignment Message (SCAM). N is the maximum number of forward Supplemental Code Channels that can be supported by the system. The first test uses n Supplemental Code Channels, where n is any number greater than zero and less than the maximum N. The second test uses the maximum N Supplemental Code Channels. This test also exercises all supported values of the FOR_SUP_CONFIG and USE_FOR_DURATION fields.
12.8.2 Traceability:
[2] 2.2.1.1.1 The Multiplex Sublayer
[4] 3.6.6.2.2.9 Processing the Supplemental Channel Assignment Message
[4] 3.6.6.2.2.10 Processing the General Handoff Direction Message
[15]-A9; 2.2.2.1.1 Packet Data Service Control Procedures
12.8.3 Call Flow Example(s)
None
12.8.4 Method of Measurement
Allocation and De-Allocation of n Supplemental Code Channels using GHDM
a. Prepare a file at the remote host (see Annex D).
b. Configure the mobile station’s maximum forward MUX Option to (2N+1) where N is the maximum number of Supplemental Code Channels supported by the mobile station (i.e. set AT+CMUX=2N+1,1)
c. Setup a mobile station terminated call with Service Option 22, and establish an FTP session.
d. Verify only the forward Fundamental Code Channel is used in establishing the FTP session.
e. Configure the base station to send a General Handoff Direction Message with FOR_INCLUDED=1, FOR_SUP_CONFIG=3, USE_FOR_DURATION=0 and assign n forward Supplemental Code Channels (where n < N and n > 0) to the mobile station.
Verify that n Supplemental Code Channels are being used by the mobile station.
g. Transfer the file from the remote host to TE2M using the binary “get” command and verify the file is successfully transferred.
h. Configure the base station to send a General Handoff Direction Message with FOR_INCLUDED=1, FOR_SUP_CONFIG=3, USE_FOR_DURATION=0 and assign 0 forward Supplemental Code Channels to the mobile station.
Verify that no Supplemental Code Channel is used by the mobile station.
12-9
C.S0044-0 v1.0
j. Transfer the file from the remote host to TE2M using the binary “get” command and verify the file is successfully transferred.
1 2
3
4
5
6
7 8 9
10 11
12 13
14 15 16 17
f. 18
19 20
21 22 23 24
i. 25
26 27
28
29
30
31
32
k. End FTP session.
l. Repeat steps c through k using Service Option 25.
12.8.4.2 Allocation and De-Allocation of N Supplemental Code Channels using SCAM
a. Prepare the RAND200.BIN byte binary file at the remote host.
b. Configure the mobile station’s maximum forward MUX Option to (2N+1) where N is the maximum number of Supplemental Code Channels supported by the mobile station (i.e. set AT+CMUX=2N+1,1)
c. Setup a mobile station terminated call with Service Option 22, and establish an FTP session.
d. Verify that only the forward Fundamental Code Channel is used in establishing the FTP session.
e. Configure the base station to send a Supplemental Code Channel Assignment Message with FOR_INCLUDED=1, FOR_SUP_CONFIG=3, USE_FOR_DURATION=0, USE_FOR_HDM_SEQ=0 and assign N forward Supplemental Code Channels to the mobile station.
Verify that N Supplemental Code Channels are used by the mobile station.
g. Transfer the file from the remote host to TE2M using the binary “get” command and verify the file is successfully transferred.
h. Configure the base station to send a Supplemental Code Channel Assignment Message with FOR_INCLUDED=1, FOR_SUP_CONFIG=3, USE_FOR_DURATION=0, USE_FOR_HDM_SEQ=0 and assign 0 forward Supplemental Code Channels to the mobile station.
Verify the number of Supplemental Code Channels used by the mobile station.
j. Transfer the file from the remote host to TE2M using the binary “get” command and verify the file is successfully transferred.
k. End FTP session.
l. Repeat steps c through k using Service Option 25.
12.8.5 Minimum Standard
For section 12.8.3.1, the mobile station shall comply with steps d, f, g, I, j and l.
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
12.9 No Transmission on Supplemental Code Channels 1
2
3 4 5 6 7
8
9
10
11
12
13
14
15
16
17
18 19
20 21 22 23
e. 24
25 26
g. 27 28
29 30
31
32
33
34
35
12.9.1 Definition
This test verifies that data transfer is not interrupted if the base station stops transmitting on one or more allocated Supplemental Code Channels. Note that if the base station does not allow a Supplemental Code Channel to remain idle when there is no data to be transmitted on the Supplemental Code Channel, this test may require the use of an OA&M interface on the base station or some other method specific to the base-station manufacturer.
12.9.2 Traceability:
[2] 2.2.1.1.1 The Multiplex Sublayer
[4] 3.6.6.2.2.9 Processing the Supplemental Channel Assignment Message
[4] 3.6.6.2.2.10 Processing the General Handoff Direction Message
[15]-A9; 2.2.2.1.1 Packet Data Service Control Procedures
12.9.3 Call Flow Example(s)
None
12.9.4 Method of Measurement
a. Prepare a file at the remote host (see Annex D).
b. Configure the mobile station’s maximum forward MUX Option to 5 or greater.
c. Setup a mobile station terminated call with Service Option 22, and establish an FTP session.
d. Configure the base station to send a General Handoff Direction Message or a Supplemental Code Channel Assignment Message with FOR_INCLUDED=1, FOR_SUP_CONFIG=3, USE_FOR_DURATION=0, USE_FOR_HDM_SEQ=0 and assign 2 forward Supplemental Code Channels to the mobile station.
Verify the MUX Option used in establishing the FTP session.
f. Transfer the file from the remote host to TE2M using the binary “get” command and verify the file is successfully transferred.
Configure the base station to send data on the Fundamental Code Channel only while the 2 Supplemental Code Channels are still active.
h. Transfer the file from the remote host to TE2M using the binary “get” command and verify the file is successfully transferred.
i. End FTP session.
j. Repeat steps c through i with Service Option 25.
12.9.5 Minimum Standard
The mobile station shall comply with steps e, f and h for all test cases.
12-11
C.S0044-0 v1.0
12.10 Soft Handoff with Supplemental Code Channels 1
2
3 4 5 6
7 8
9
10
11
12
13
14
15
16
17
18
19 20 21
22
23 24
e. 25 26
27
28 29
30 31 32
33 34 35
36 37
12.10.1 Definition
This test verifies that the fundamental and Supplemental Code Channels can be put in two-way soft handoff during an MSPD call with N Supplemental Code Channels active, where N is the maximum number of Forward Supplemental Code Channels that can be supported by the system. This test includes the following cases:
Fundamental Code Channel and Supplemental Code Channels in handoff, two cells transmit Supplemental Code Channels.
Fundamental Code Channel in handoff, only one cell transmits Supplemental Code Channels.
12.10.2 Traceability:
[2] 2.2.1.1.1 The Multiplex Sublayer
[4] 3.6.6.2.2.10 Processing the General Handoff Direction Message
[4] 3.6.6.2.4 Soft Handoff
[15]-A9; 2.2.2.1.1 Packet Data Service Control Procedures
12.10.3 Call Flow Example(s)
None
12.10.4 Method of Measurement
a. Prepare a file at the remote host (see Annex D).
b. Configure the mobile station’s maximum forward MUX Option to (2N+1) where N is the maximum number of forward Supplemental Code Channels available for the mobile station.
c. Configure each base station to support N Supplemental Code Channels.
d. Setup a mobile station terminated call with Service Option 22, and establish an FTP session with base station 1.
Configure the base station to set up N Forward Supplemental Code Channels in traffic state.
f. Begin transferring the file from the remote host to TE2M using the binary “get” command.
g. While the file is being transferred, adjust the signal strength of base station 2 until both base stations have equal transmit power.
h. Generate a General Handoff Direction Message for two-way soft-handoff with base station 2. In both test cases 1 and 2, generate the GHDM with FOR_INCLUDED=1, FOR_SUP_CONFIG=3, NUM_FOR_SUP=N, and USE_FOR_DURATION=0.
i. For Test 1: In the GHDM, set the FOR_SUP_INCLUDED=1 for each pilot to be included in handoff and configure both base stations to send data on all Supplemental Code Channels.
j. For Test 2: In the GHDM, set the FOR_SUP_INCLUDED=1 for base station 1 and FOR_SUP_INCLUDED=0 for base station 2. Configure base station 1 to transmit data on
12-12
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
f. 31
32
all Supplemental Code Channels. Configure base station 2 to transmit data on the Fundamental Code Channel only.
k. Verify the file transfer continues after the handoff and data is successfully transferred.
l. End FTP session.
m. Repeat steps d through l with Service Option 25.
12.10.5 Minimum Standard
The mobile station shall comply with step k for all test cases.
12.11 Adding Supplemental Code Channels during Soft Handoff
12.11.1 Definition
This test verifies that N Supplemental Code Channels can be added in an MSPD call while in two-way soft handoff on the Fundamental Code Channel, where N is the maximum number of Supplemental Code Channels that can be supported by the system. This test includes the following cases:
• N Supplemental Code Channels added on all cells.
• N Supplemental Code Channels added on one cell only.
12.11.2 Traceability:
[2] 2.2.1.1.1 The Multiplex Sublayer
[4] 3.6.6.2.2.10 Processing the General Handoff Direction Message
[4] 3.6.6.2.4 Soft Handoff
[15]-A9; 2.2.2.1.1 Packet Data Service Control Procedures
12.11.3 Call Flow Example(s)
None
12.11.4 Method of Measurement
a. Prepare a file at the remote host (see Annex D).
b. Configure the mobile station’s maximum forward Supplemental Code Channels to N.
c. Configure each base station to support N Supplemental Code Channels.
d. Setup a mobile station terminated call with Service Option 22, and establish an FTP session with base station 1 on the Fundamental Code Channel only.
e. Adjust the signal strength of base station 2 until both base stations have equal transmit power.
Verify the mobile station is in two-way handoff.
g. Begin transferring the file from the remote host to TE2M using the binary “get” command.
12-13
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
h. Generate a General Handoff Direction Message or a Supplemental Channel Assignment Message with FOR_INCLUDED=1, FOR_SUP_CONFIG=3, NUM_FOR_SUP=N, and USE_FOR_DURATION=0.
i. For Test Case 1: In the GHDM, set the FOR_SUP_INCLUDED=1 for each pilot to be included in handoff and configure both base stations to send data on all Supplemental Code Channels.
j. For Test Case 2: In the GHDM, set the FOR_SUP_INCLUDED=1 for base station 1 and FOR_SUP_INCLUDED=0 for base station 2. Configure base station 1 to transmit data on all Supplemental Code Channels. Configure base station 2 to transmit data on the Fundamental Code Channel only.
k. Verify the file transfer continues after Supplemental Code Channel assignment during handoff and the file is transferred successfully.
l. End FTP session.
m. Repeat steps d through l with Service Option 25.
12.11.5 Minimum Standard
The mobile station shall comply with steps f and k for all test cases.
12.12 Hard Handoff to an MSPD-Capable System
12.12.1 Definition
This test verifies hard handoff within the same P_REV system as well as hard handoff to a higher P_REV system.
12.12.2 Traceability:
[2] 2.2.1.1.1 The Multiplex Sublayer
[4] 3.6.6.2.2.10 Processing the General Handoff Direction Message
[4] 3.6.6.2.4 Soft Handoff
[15]-A9; 2.2.2.1.1 Packet Data Service Control Procedures
12.12.3 Call Flow Example(s)
None
12.12.4 Method of Measurement
12.12.4.1 Hard Handoff to Same P_REV
a. Prepare a file at the remote host (see Annex D).
b. Make sure the MOB_P_REV=4 or higher.
c. Base station 1 should be configured for P_REV=5 or higher.
12-14
C.S0044-0 v1.0
d. Base station 2 should be configured for P_REV=5 or higher with a different frequency channel from base station 1.
1 2
3
4
g. 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
h. 32
33
34 35
e. Configure the mobile station’s maximum forward Supplemental Code Channels to N.
f. Configure both base stations to support N Supplemental Code Channels.
Setup a mobile station terminated call with Service Option 22 and establish an FTP session with base station 1 with N Supplemental Code Channels.
h. Begin transferring the file from the remote host to TE2M using the binary “get” command.
i. While the file is being transferred, adjust the signal strength of base station 2 until both base stations have equal transmit power.
j. At base station 1, setup a hard handoff to base station 2 using the Extended Handoff Direction Message.
k. Verify the hard handoff is successful and that only the Fundamental Channel is active.
l. Verify that base station 2 generates a General Handoff Direction Message or a Supplemental Channel Assignment Message to assign N Supplemental Code Channels to the mobile station.
m. Verify at the base station that service negotiation is successful and that the mobile station is using Service Option 22 with N Supplemental Code Channels.
n. Verify the file transfer continues after the hard handoff and the file is transferred successfully.
o. End FTP session.
p. Repeat steps g through o with Service Option 25.
12.12.4.2 Hard Handoff to Higher P_REV
a. Prepare a file at the remote host (see Annex D).
b. Make sure the MOB_P_REV=4 or higher.
c. Base station 1 should be configured for P_REV=3.
d. Base station 2 should be configured for P_REV=5 or higher with a different frequency channel from base station 1.
e. Configure the mobile station’s maximum forward Supplemental Code Channels to N.
f. Configure base station 2 to support N Supplemental Code Channels.
g. Setup a mobile station terminated call with Service Option 7 and establish an FTP session with base station 1
Verify that Service Option 7 is in use and only the Fundamental Code Channel is active.
i. Begin transferring the file from the remote host to TE2M using the binary “get” command.
j. While the file is being transferred, adjust the signal strength of base station 2 until both base stations have equal transmit power.
12-15
C.S0044-0 v1.0
k. At base station 1, setup a hard handoff to base station 2 using the Extended Handoff Direction Message.
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
12.13.426
27
28
29
30
31 32
l. Verify the hard handoff is successful.
m. Verify at the mobile station that Service Option 7 is still in use.
n. Verify the file transfer continues after the hard handoff and the file is transferred successfully.
o. End FTP session.
p. Repeat steps g through n with Service Option 15.
12.12.5 Minimum Standard
For section 12.12.3.1, the mobile station and the base station shall comply with steps k, l, m, n and p.
For section 12.12.3.2, the mobile station and the base station shall comply with steps h, l, m, n and p.
12.13 Bi-Directional File Transfers with Forward Supplemental Code Channels
12.13.1 Definition
This test verifies the capability to transfer files simultaneously on the Forward and Reverse Traffic Channels between the mobile station and remote host using FTP, with forward Supplemental Code Channels active.
12.13.2 Traceability:
[2] 2.2.1.1.1 The Multiplex Sublayer
[4] 3.6.6.2.2.10 Processing the General Handoff Direction Message
[4] 3.6.6.2.4 Soft Handoff
[15]-A9; 2.2.2.1.1 Packet Data Service Control Procedures
12.13.3 Call Flow Example(s)
None
Method of Measurement
a. Prepare a file at both the remote host and the TE2M (see Annex D).
b. Configure the mobile station’s maximum forward Supplemental Code Channels to N.
c. Configure the base station to support N Supplemental Code Channels.
d. Setup a mobile station terminated call with Service Option 22.
e. Establish two FTP sessions with the base station; one for the forward link and one for the reverse link.
12-16
C.S0044-0 v1.0
f. From the base station, generate a General Handoff Direction Message or a Supplemental Channel Assignment Message to allocate N Supplemental Code Channels to the mobile station.
1 2 3
g. 4 5
h. 6
7 8
9
10
11
12
13
14
12.14.115
16 17
18
19
20
21
22
23
24
25
26
27 28
c. 29
30
31 32
Verify from the mobile station that N forward Supplemental Code Channels are being used. The reverse link should be connected with the Fundamental Code Channel only.
Begin transferring the file from the remote host to TE2M using the binary “get” command.
i. While the file is being transferred on the forward link, begin transferring another file from TE2M to the remote host on the reverse link using the binary “put” command.
j. Verify that both files are transferred successfully.
k. End two FTP sessions.
l. Repeat steps d through l with Service Option 25.
12.13.5 Minimum Standard
The mobile station and the base station shall comply with steps g and j for all test cases.
12.14 Rм Interface Flow Control
Definition
This test verifies flow control on the Rm Interface, when the Um interface data rate exceeds the Rm interface baud rate.
12.14.2 Traceability:
[2] 2.2.1.1.1 The Multiplex Sublayer
[4] 3.6.6.2.2.10 Processing the General Handoff Direction Message
[4] 3.6.6.2.4 Soft Handoff
[15]-A9; 2.2.2.1.1 Packet Data Service Control Procedures
12.14.3 Call Flow Example(s)
None
12.14.4 Method of Measurement
a. Prepare a file at the remote host (see Annex D).
b. Configure the mobile station’s maximum forward Supplemental Code Channels to N (N > 4 for Service Option 22, N > 3 for Service Option 25).
Configure the base station to support N Supplemental Code Channels.
d. Configure the RS-232 baud rate in the Rm interface to 4800 bps.
e. Setup a mobile station terminated call with Service Option 22, and establish an FTP session.
12-17
C.S0044-0 v1.0
f. From the base station, generate a General Handoff Direction Message or a Supplemental Channel Assignment Message to allocate N Supplemental Code Channels to the mobile station.
1 2 3
g. 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
Verify at the mobile station that N Supplemental Code Channels are in use.
h. Transfer the file from the remote host to TE2M using the binary “get” command.
i. Verify the file is transferred successfully.
j. End FTP session.
k. Repeat steps e through j with Service Option 25.
12.14.5 Minimum Standard
The mobile station shall comply with steps g and i for all test cases.
12.15 Dormant Timer
12.15.1 Definition
This test verifies the mobile station correctly processes the Service Option Control Message which controls the Dormant Timer, and that the mobile station delays any attempt to send an Origination Message requesting a MSPD service option until the Dormant Timer expires.
12.15.2 Traceability:
[4] 3.7.3.3.2.21 Service Option Control Message
[15]-A3; 7.4.1 CDMA AT Parameters
[15]-A9; 2.2.2.1.2.5 Dormant/Idle State
12.15.3 Call Flow Example(s)
None
12.15.4 Method of Measurement
a. Prepare a file at the remote host (see Annex D).
b. Configure the mobile station’s maximum forward Supplemental Code Channels to N.
c. Configure the mobile station’s inactivity timer to 20 seconds by issuing the AT command AT+CTA=20.
d. Configure the base station to support N Supplemental Code Channels.
e. Setup a mobile station terminated call with Service Option 22, and establish an FTP session.
f. From the base station, generate a General Handoff Direction Message or a Supplemental Channel Assignment Message to allocate N Supplemental Code Channels to the mobile station.
12-18
C.S0044-0 v1.0
g. From the base station, send the Service Option Control Message with the Packet Data Dormant Timer set to 20 seconds.
1 2
h. 3
4 5
6 7
k. 8 9
10 11
12 13
14
15
16
17
18
19
20
21 22 23
24 25 26
27 28
29
30
31
32
33
34
35
Verify from the mobile station that N Supplemental Code Channels are being used.
i. Transfer the file from the remote host to TE2M using the binary “get” command and verify the file is transferred successfully.
j. Wait for the packet data service call control function to enter the Dormant State due to data inactivity (i.e. when the inactivity timer in the mobile station expires).
Setup a mobile station originated call with Service Option 22, and establish an FTP session as soon as the packet data service call control function is in the Dormant Statemode. The time elapsed between the Release Order and the Origination Message should be approximately 20 seconds.
l. After the call is re-established, transfer the file from the remote host to TE2M using the binary “get” command and verify the file is transferred successfully.
m. End FTP session.
n. Repeat steps e through m with Service Option 25.
12.15.5 Minimum Standard
The mobile station shall comply with steps h, i and l.
12.16 Packet Zone ID
12.16.1 Definition
This test verifies the following:
When the mobile station detects a change in the Packet Zone ID in the Extended System Parameters Message and the new Packet Zone ID is not in the Packet Zone ID List the mobile station shall attempt to reconnect the packet data service option.
While the data is being transferred and the base station sends a new Packet Zone ID to the mobile station in the Service Option Control Message, the mobile station shall continue to transfer files in the new Packet Zone ID.
When the Dormant Timer is running and hasnot expired, the mobile station shall not re-originate a data call.
12.16.2 Traceability:
[4] 3.7.3.3.2.21 Service Option Control Message
[15]-A9; 2.2.2.1.2.5 Dormant/Idle State
[15]-A9; 2.2.2.1.2.6 Dormant/Traffic State
12.16.3 Call Flow Example(s)
None
12-19
C.S0044-0 v1.0
1 12.16.4 Method of Measurement
12.16.4.1 2
3
4
5
6
7 8
9 10 11
12 13 14 15 16
h. 17
18
19
20 21
22 23
m. 24 25
26 27
28
29
30
31 32
33
34
35
Mobile Station Idle State
a. Prepare a file at the remote host (see Annex D).
b. Configure the mobile station’s maximum forward Supplemental Code Channels to N.
c. Configure the base station to support N Supplemental Code Channels.
d. Configure the mobile station’s inactivity timer to 20 seconds by issuing an AT command.
e. Setup a mobile station originated call with Service Option 22, and establish an FTP session
f. From the base station, generate a General Handoff Direction Message or a Supplemental Channel Assignment Message to allocate N Supplemental Code Channels to the mobile station.
g. Instruct the base station to send the Service Option Control Message to the mobile station to enable the PACKET_ZONE_ID with a valid list of PACKET_ZONE_Ids. Specify the number of packet data service identifiers that the mobile station is to retain in its packet data zone identifiers list (the number shall be set to 2 or greater). Also set the Packet Data Dormant Timer to 20 seconds.
Verify from the mobile station that N Supplemental Code Channels are being used.
i. Transfer the file from the remote host to TE2M using the binary “get” command.
j. Make sure there is no data to transmit for 20 seconds.
k. Verify the packet data service call control function enters the Dormant State and the mobile station enters the Mobile Station Idle State due to data inactivity.
l. Change the PACKET_ZONE_ID of the serving system in the Extended System Parameter Message.
Verify the mobile station reconnects to the same Service Option when it detects the new PACKET_ZONE_ID.
n. After the call is re-established, transfer the file from the remote host to TE2M using the binary “get” command and verify the file is transferred successfully.
o. End FTP session.
p. Repeat steps e through o with Service Option 25.
q. Repeat steps a through f.
r. Instruct the base station to send the Service Option Control Message to the mobile station to set the Dormant Timer to 60 seconds.
s. Repeat steps j through k.
t. Attempt to initiate an ftp session to a server at the mobile station.
u. Verify the MS does not send an Origination Message before the Dormant Timer expires.
12-20
C.S0044-0 v1.0
12.16.4.2 Traffic Channel State 1
2
3
4
5 6
e. From the base station, generate a General Handoff Direction Message or a 7 Supplemental Channel Assignment Message to allocate N Supplemental Code 8 Channels to the mobile station. 9
10 11
g. 12
13 14
15 16
17 18
19
20
m. Repeat steps d through l with Service Option 25. 21
22
23
24
25
26
27
28
a. Prepare a file at the remote host (see Annex D).
b. Configure the mobile station’s maximum forward Supplemental Code Channels to N.
c. Configure the base station to support N Supplemental Code Channels.
d. Setup a mobile station originated call with Service Option 22, and establish an FTP session
f. From the base station, send the Service Option Control Message to the mobile station to enable the PACKET_ZONE_ID with a valid list of PACKET_ZONE_IDs.
Verify from the mobile station that N Supplemental Code Channels are being used.
h. Begin transferring the file from the remote host to TE2M using the binary “get” command.
i. While the file is being transferred, send the Service Option Control Message to the mobile station with a change in the PACKET_ZONE_ID.
j. Change the PACKET_ZONE_ID of the serving system in the In-Traffic System Parameter Message.
k. Verify the mobile station continues file transfer on the new PACKET_ZONE_ID.
l. End FTP session.
12.16.5 Minimum Standard
12.16.5.1 Mobile Station Idle State
The mobile station shall comply with steps h, k m, n and u
12.16.6 Traffic Channel State
For section 12.16.3.2, the mobile station shall comply with steps g and k for all test cases.
12-21
C.S0044-0 v1.0
13 HIGH SPEED PACKET DATA 1
2
3
4 5
6
7
8
9
10
11
12
13
14
15
16
17
18
a. 19
b. 20
21
d. 22 23 24
25
26 27
13.1 Forward File Transfer
13.1.1 Definition
This test verifies that file transfer from remote host to mobile station can be successfully done using the HSPD call.
13.1.2 Traceability (see [4] unless otherwise noted)
2.7.2.3.2.18 Supplemental Channel Request Message
2.7.2.3.2.28 Supplemental Channel Request Mini Message
3.6.6.2.2.12 Processing of Extended Supplemental Channel Assignment Message
3.7.3.3.2.24 Supplemental Channel Assignment Message
3.7.5.7.1 Channel Configuration for the Supplemental Channel
1.4.2.2 Mobile Station Packet Data Service States (see [15])
2.2.2 Service and Call Control Procedures (see [15])
2.2.3 Initialization and Connection of Packet Data Service Options (see [15])
2.2.7 High Speed Operation (see [15])
13.1.3 Call Flow Example(s)
None
13.1.4 Method of Measurement
Connect the mobile station to the base station as shown in Figure A-3.
At the remote host prepare appropriate file (see Annex D) for data transfer11.
c. Setup an FTP session using Service Option 33 with the remote host 12.
If supplemental channel is assigned, verify the base station sends a Universal Handoff Direction Message, an Extended Supplemental Channel Assignment Message, or a Forward Supplemental Channel Assignment Mini Message.
e. Transfer the file from the remote host to the TE2M using the binary “get” command.
f. After the file transfer is completed, end the FTP session. Make sure the file is successfully transferred.
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 2
3
4
g. Steps b through f may be repeated for other data rates and different radio configurations supported by both mobile station and base station.
Table 13.1.4-1 SCH Data Rate
Data Rate Granted (bps)
F-RC3, 4 / R-RC3 F-RC6, 7 /R-RC5
F-RC5 / R-RC4 F-RC8, 9 / R-RC6
9600 14400
19200 28800
38400 57600
76800 115200
153600 230400
307200 460800
614400 1036800
5
6
7
8
9
10 11
12
13
14
15
16
17
18
19
20
21
13.1.5 Minimum Standard
The mobile station shall comply with step f. The base station shall comply with step d.
13.2 Reverse File Transfer
13.2.1 Definition
This test verifies that file transfer from mobile station to remote host can be successfully done using the HSPD call.
13.2.2 Traceability (see [4] unless otherwise noted)
2.7.2.3.2.18 Supplemental Channel Request Message
2.7.2.3.2.28 Supplemental Channel Request Mini Message
3.6.6.2.2.12 Processing of Extended Supplemental Channel Assignment Message
3.7.3.3.2.24 Supplemental Channel Assignment Message
3.7.5.7.1 Channel Configuration for the Supplemental Channel
1.4.2.2 Mobile Station Packet Data Service States (see [15])
2.2.2 Service and Call Control Procedures (see [15])
2.2.3 Initialization and Connection of Packet Data Service Options (see [15])
2.2.7 High Speed Operation (see [15])
13-2
C.S0044-0 v1.0
13.2.3 Call Flow Example(s) 1
None 2
3
a. 4
5
c. 6
7 8 9
10 11
12 13 14
f. 15 16
17 18
19 20
21
22
13.3 Bi-directional File Transfer 23
24
25
26
27
28
29
30
31
13.2.4 Method of Measurement
Connect the mobile station to the base station as shown in Figure A-3.
b. At the TE2M prepare a file for data transfer.
Setup an FTP session using Service Option 33 with the remote host.
d. Transfer the file from the TE2M to the remote host using the binary “put” command. Ensure that the total amount of data to be transferred at the mobile station is more than an implementation defined threshold, or otherwise cause the mobile station to send a Supplemental Channel Request Message or a Supplemental Channel Request Mini Message with DURATION field set to a non-zero value.
e. If supplemental channel is assigned, verify the base station sends a Universal Handoff Direction Message, an Extended Supplemental Channel Assignment Message, or a Reverse Supplemental Channel Assignment Mini Message.
After the file transfer is completed, end the FTP session. Make sure that file is successfully transferred.
g. Steps b through f should be executed for the maximum data rates13 supported by both mobile station and base station.
h. Steps b through f may be repeated for other data rates and radio configurations supported by both mobile station and base station.
13.2.5 Minimum Standard
The mobile station shall comply with step f. The base station shall comply with step e.
13.3.1 Definition
This test verifies that bi-directional file transfer can be successfully done using the HSPD call.
13.3.2 Traceability (see [4] unless otherwise noted)
2.7.2.3.2.18 Supplemental Channel Request Message
2.7.2.3.2.28 Supplemental Channel Request Mini Message
3.6.6.2.2.12 Processing of Extended Supplemental Channel Assignment Message
3.7.3.3.2.24 Supplemental Channel Assignment Message
3.7.5.7.1 Channel Configuration for the Supplemental Channel
13 Make sure that transmit power is not limiting factor for maximum data rate assignment.
13-3
C.S0044-0 v1.0
1.4.2.2 Mobile Station Packet Data Service States (see [15]) 1
2
3
4
5
6
7
a. 8
9
c. 10
d. 11 12 13 14 15
16 17
18 19 20
g. If reverse supplemental channel is assigned, verify the base station sends a Universal 21 Handoff Direction Message (can be same as one in step f), an Extended Supplemental 22 Channel Assignment Message (can be same as one in step f), or a Reverse 23 Supplemental Channel Assignment Mini Message. 24
h. 25
26 27
28 29
30
31
2.2.2 Service and Call Control Procedures (see [15])
2.2.3 Initialization and Connection of Packet Data Service Options (see [15])
2.2.7 High Speed Operation (see [15])
13.3.3 Call Flow Example(s)
None
13.3.4 Method of Measurement
Connect the mobile station to the base station as shown in Figure A-3.
b. Prepare a file at both the remote host and TE2M for data transfer.
Setup an FTP session using Service Option 33 with the remote host.
Transfer the file from the TE2M to the remote host. Ensure that the total amount of data to be transferred at the mobile station is more than an implementation defined threshold, or otherwise cause the mobile station to send a Supplemental Channel Request Message or a Supplemental Channel Request Mini Message with DURATION field set to a non-zero value.
e. Transfer a file from the Remote Host to the TE2M while the transfer in the reverse direction is still proceeding.
f. If forward supplemental channel is assigned, verify the base station sends a Universal Handoff Direction Message, an Extended Supplemental Channel Assignment Message, or a Forward Supplemental Channel Assignment Mini Message.
Verify that files in both directions are successfully transferred and end the FTP session.
i. Steps c through f should be executed for the maximum forward14 and reverse15 data rates that are supported by both mobile station and base station.
j. Steps c through f may be repeated for different data rates and radio configurations that are supported by both mobile station and base station.
13.3.5 Minimum Standard
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
1
2
13.4.1 Definition 3
4 5 6
7
8
9
10
11
12
13
13.4 Service Option Control Message Processing
This test verifies the mobile station ability to process the Service Option Control Message. This test also verifies the mobile station is able to establish a voice call while the packet data session is dormant.
13.4.2 Traceabilities (see [4] unless otherwise noted)
2.6.4.3 Traffic Channel Substate
3.6.4.3 Traffic Channel Substate
3.7.3.3.2.21 Service Option Control Message
2.2.2.1 Mobile Station Procedures (see [15])
2.2.2.2 Base Station Procedures (see [15])
2.2.4 Packet Data Dormant Timer Control (see [15])
13-5
C.S0044-0 v1.0
1 13.4.3 Call Flow Example(s)
Service Option Control Message
General Page Msg withvoice service option
BSMS
Traffic Traffic
TrafficTraffic
Release OrderMS packet service isdormant
Data Call in Progress
VoiceCall in Progress
Voice call ends
General Page Msg withpacket data service option
Data Call mayResume
2
3
4
5
6 7
8
13.4.4 Method of Measurement
a. Connect the mobile station in Figure A-3.
b. Setup a mobile originated Service Option 33 call.
c. While the data call is active, instruct the base station to send a Service Option Control Message with the following information:
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
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
d. Instruct the base station to send a Release Order with ORDQ=’0’ to the mobile station.
e. Verify the mobile station releases the call and the packet data session is in the dormant state.
f. Before the DORM_TIME expires, send a General Page to the mobile station with a voice service option.
g. Verify the call completes and user traffic is present.
h. End the call before DORM_TIME expires.
i. Set up a mobile originated voice call.
j. Verify the call completes and user traffic is present.
k. End the call before DORM_TIME expires.
l. Insure the mobile station has sufficient data in its buffer.
m. Verify the mobile station does not send an Origination Message for packet data service before the DORM_TIME expires.
n. After DORM_TIME has expired, page the mobile station with a packet data service or otherwise cause the mobile station to send an Origination Message for a packet data service.
o. Verify the call completes and user traffic is present.
13.4.5 Minimum Standard
The mobile station shall comply with steps e, g, j, m and o.
13.5 Changing Encoding Type on Supplemental Channel during Hard Handoff
13.5.1 Definition
This test verifies that the mobile station is capable of using turbo encoding and is capable of changing to convolutional encoding.
13.5.2 Traceability (see [4] unless otherwise noted)
2.1.3.1.4 Forward Error Correction (see [1)]
3.1.3.1.4 Forward Error Correction (see [1])
2.7.2.3.2.18 Supplemental Channel Request Message
13-7
C.S0044-0 v1.0
3.7.3.3.2.36 Universal Handoff Direction Message 1
2
13.5.3 Call Flow Example(s) 3
4
5
6
7
8
9
10 11 12
13
14 15
16 17
18 19 20
21 22
23
24
25
26
27
28
29 30 31
32
33 34
3.7.3.3.2.37 Extended Supplemental Channel Assignment Message
None
13.5.4 Method of Measurement
13.5.4.1 R-SCH Turbo Encoding to Convolutional Encoding
a. Connect the mobile station to the base station as shown in Figure A-5.
b. Ensure the mobile station supports turbo encoding and convolutional encoding.
c. Setup a mobile originated Service Option 33 call.
d. Instruct the base station to send a Service Connect Message with CODING=‘1’ in the Service Configuration Record for the F-SCH and R-SCH (as supported by the mobile station).
e. Verify the mobile station sends a Service Connect Completion Message.
f. Initiate a data transfer from the mobile station and verify the mobile station sends a Supplemental Channel Request Message requesting a reverse supplemental channel.
g. Instruct the base station to send an Extended Supplemental Channel Assignment Message assigning a reverse supplemental channel to the mobile station.
h. While the data transfer is in progress, instruct the base station to send a Universal Handoff Direction Message with CODING=’0’ and a reverse supplemental channel burst assignment.
i. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message.
j. Verify the data transfer completes successfully using convolutional encoding.
k. End the call from the mobile station.
13.5.4.2 R-SCH Convolution Encoding to Turbo Encoding
a. Connect the mobile station to the base station as shown in Figure A-5.
b. Ensure the mobile station supports turbo encoding and convolutional encoding.
c. Setup a mobile originated Service Option 33 call.
d. Instruct the base station to send a Service Connect Message with CODING=‘0’ in the Service Configuration Record for the F-SCH and R-SCH (as supported by the mobile station).
e. Verify the mobile station sends a Service Connect Completion Message.
f. Initiate a data transfer from the mobile station and verify the mobile station sends a Supplemental Channel Request Message requesting a reverse supplemental channel.
13-8
C.S0044-0 v1.0
g. Instruct the base station to send an Extended Supplemental Channel Assignment Message assigning a reverse supplemental channel to the mobile station.
1 2
3 4 5
6 7
8 9
10
11
12
13
14
15 16 17
18
19 20
21 22 23
24 25
26
27
28
29
30
31
32 33 34
e. Verify the mobile station sends a Service Connect Completion Message. 35
h. While the data transfer is in progress, instruct the base station to send a Universal Handoff Direction Message with CODING=’1’ and a reverse supplemental channel burst assignment.
i. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message.
j. Verify the data transfer completes successfully using turbo encoding (if the block size per frame is at least 360 bits)..
k. End the call from the mobile station.
13.5.4.3 F-SCH Turbo Encoding to Convolutional Encoding
a. Connect the mobile station to the base station as shown in Figure A-5.
b. Ensure the mobile station supports turbo encoding and convolutional encoding.
c. Setup a mobile originated Service Option 33 call.
d. Instruct the base station to send a Service Connect Message with CODING=‘1’ in the Service Configuration Record for the F-SCH and R-SCH (as supported by the mobile station).
e. Verify the mobile station sends a Service Connect Completion Message.
f. Initiate a data transfer to the mobile station and verify the base station sends an Extended Supplemental Channel Assignment Message assigning a F-SCH.
g. While the data transfer is in progress, instruct the base station to send a Universal Handoff Direction Message with CODING=’0’ and a forward supplemental channel burst assignment.
h. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message.
i. Verify the data transfer completes successfully using convolutional encoding.
j. End the call from the mobile station.
13.5.4.4 F-SCH Convolutional Encoding to Turbo Encoding
a. Connect the mobile station to the base station as shown in Figure A-5.
b. Ensure the mobile station supports turbo encoding and convolutional encoding.
c. Setup a mobile originated Service Option 33 call.
d. Instruct the base station to send a Service Connect Message with CODING=‘0’ in the Service Configuration Record for the F-SCH and R-SCH (as supported by the mobile station).
13-9
C.S0044-0 v1.0
f. Initiate a data transfer to the mobile station and verify the base station sends an Extended Supplemental Channel Assignment Message assigning a F-SCH.
1 2
3 4 5
6 7
8 9
10
11
12
13
14
The mobile station shall comply with steps e, i, and j. 15
16
17
18
19
20
21
22 23 24 25 26 27 28 29 30
31 32
33
34
g. While the data transfer is in progress, instruct the base station to send a Universal Handoff Direction Message with CODING=’1’ and a forward supplemental channel burst assignment.
h. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message.
i. Verify the data transfer completes successfully using turbo encoding (if the block size per frame is at least 360 bits)..
j. End the call from the mobile station.
13.5.5 Minimum Standard
13.5.5.1 R-SCH Turbo Encoding to Convolutional Encoding
The mobile station shall comply with steps e, i, and j
13.5.5.2 R-SCH Convolutional Encoding to Turbo Encoding
13.5.5.3 F-SCH Turbo Encoding to Convolutional Encoding
The mobile station shall comply with steps e, h, and i.
13.5.5.4 F-SCH Convolutional Encoding to Turbo Encoding
The mobile station shall comply with steps e, h, and i.
13.6 Control Hold Mode Transitions
13.6.1 Definition
This test applies when the mobile station and base station support Control Hold Mode. This test verifies that the mobile can go in and out of the Control Hold Mode in all the possible combinations. When the mobile station or the base station, trigger a transition to the Control Hold Mode, the expected signaling exchange takes place. Upon transition to the Control Hold Mode, the reverse pilot is gated at the specified gating rate DCCH is maintained with Power Control sub-channel and user traffic transmission is not allowed in either direction. When the mobile station and base station transition to the Active Mode, the expected signaling exchange takes place. Upon transition to the Active Mode, the reverse pilot transmission is continuous and user traffic transmission is allowed.
The following are call flow examples for going in and out of Control Hold Mode. Either the mobile station or the base station can trigger either transition.
13.6.2 Call Flow Example(s)
13-10
C.S0044-0 v1.0
Extended Release (Mini) Message /Universal Handoff Direction Message
Extended Release Response (Mini) MessageHandoff Completion Message
At the action time:Transition to Control Hold Mode& start reverse pilot gating at thespecified gating rate
BSMS
Active Active
Control Hold Control Hold
BS decides to transitionto Control Hold Mode
1 2
33
4
Figure 1 -1 Call Flow for base station initiated Active to Control Hold Transition
Extended Release (Mini) Message /Universal Handoff Direction Message
Extended Release Response (Mini) MessageHandoff Completion Message
At the action time:Transition to Control Hold Mode& start reverse pilot gating at thespecified gating rate
BSMS
Active Active
Control Hold Control Hold
Resource Release Request (Mini) MessageRequest to transition toControl Hold Mode
5 6
37
8
Figure 1 -2 Call Flow for mobile station initiated Active to Control Hold Transition
13-11
C.S0044-0 v1.0
Resource Allocation (Mini) Message /Universal Handoff Direction Message /
Extended Supplemental ChannelAssignment Message/
Forward Supplemental ChannelAssignment Mini Message/
Reverse Supplemental ChannelAssignment Mini Message
At the action time:Transition to Active Mode& start reverse pilot continuoustransmission
BSMS
ControlHold
Active Active
BS decides to transitionto Active Mode
ControlHold
1 2
33
4
Figure 1 -3 Call Flow for base station initiated Control Hold to Active Transition
Resource Allocation (Mini) Message /Universal Handoff Direction Message /
Extended Supplemental ChannelAssignment Message/
Forward Supplemental ChannelAssignment Mini Message/
Reverse Supplemental ChannelAssignment Mini Message
At the action time:Transition to Active Mode& start reverse pilot continuoustransmission
BSMS
ControlHold
Active Active
Request to transition toActive Mode
ControlHold
Resource Request (Mini) Message /Supplemental Channel
Request (Mini) Message
5 6
37
8
9
Figure 1 -4 Call Flow for mobile station initiated Control Hold to Active Transition
13.6.3 Traceability (See [4])
2.6.4.1.15 Processing the Non-Negotiable Service Configuration Record
13-12
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.6.4.1.9 Processing the Extended Release Message and the Extended Release Mini Message
2.6.4.1.10 Processing the Resource Allocation Message and Resource Allocation Mini Message
2.6.4.4 Conversation Substate
2.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages
2.7.2.3.2.18 Supplemental Channel Request Message
2.7.2.3.2.28 Supplemental Channel Request Mini Message
2.7.2.3.2.23 Resource Request Message
2.7.2.3.2.24 Resource Request Mini Message
2.7.2.3.2.29 Resource Release Request Message
2.7.2.3.2.30 Resource Release Request Mini Message
3.6.4.1.6 Processing Resource Request Messages
3.6.4.1.8 Processing Resource Release Request Message and Resource Release Request Mini Message
3.6.4.4 Conversation Substate
3.6.6.2.2.11 Processing the Universal Handoff Direction Message
3.6.6.2.2.13 Processing of Forward Supplemental Channel Assignment Mini Message
3.6.6.2.2.14 Processing of Reverse Supplemental Channel Assignment Mini Message
3.7.3.3.2.32 Resource Allocation Message
3.7.3.3.2.33 Resource Allocation Mini Message
3.7.3.3.2.34 Extended Release Message
3.7.3.3.2.35 Extended Release Mini Message
3.7.3.3.2.36 Universal Handoff Direction Message
3.7.3.3.2.37 Extended Supplemental Channel Assignment Message
3.7.3.3.2.38 Forward Supplemental Channel Assignment Mini Message
3.7.3.3.2.39 Reverse Supplemental Channel Assignment Mini Message
3.7.5.20 (base station) Non-Negotiable Service Configuration information record
13.6.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-3.
b. Setup a packet data call, using only the Dedicated Control Channel (DCCH).
c. Verify user traffic (Ex. Browser data) in both directions.
13-13
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
33
34
35
36 37 38 39
d. Cause the mobile station and/or base station to initiate transition to the Control Hold Mode because of out-of-data indication from the RLP.
e. Verify that one of the following two scenarios occurs:
1. Verify that the mobile station sends a Resource Release Request (Mini) Message to the base station to request transition to the Control Hold Mode. Verify that the base station accepts this request, via an Extended Release (Mini) Message, or a Universal Handoff Direction Message. Verify that the mobile station responds with an Extended Release Response (Mini) Message, or a Extended Handoff Completion Message.
2. Verify that the base station sends an Extended Release Mini Message, or a Universal Handoff Direction Message. Verify that the mobile station responds with an Extended Release Response Mini Message, or an Extended Handoff Completion Message.
f. Upon transition to Control Hold Mode, verify the following:
1. The reverse pilot is gated at the specified rate.
2. Dedicated Control Channel is maintained for signaling.
3. User traffic (Ex. Browser data) is not transmitted on either direction. NOTE: This can be verified by attempting to send user traffic, while not granting any requests to transition to the Active Mode.
4. Reverse Power Control Subchannel is maintained at the Forward Dedicated Control Channel.
g. Depending on who initiated the transition to Control Hold Mode in e, and if possible, change the control hold time on the network side to make the other alternative happen in d. Repeat b through f. Results are as expected in f.
h. Execute steps b through f.
i. Send a ping from the base station side.
j. Verify that the base station initiates the transition to Active Mode, via a Resource Allocation Message, a Resource Allocation Mini Message, a Universal Handoff Direction Message, an Extended Supplemental Channel Assignment (Mini) Message, a Forward Supplemental Channel Assignment Mini Message, or a Reverse Supplemental Channel Assignment Mini Message. Verify that the mobile station responds accordingly.
k. Upon transition to the Active Mode, verify that:
1. The reverse pilot transmission is continuous
2. User traffic (Ex. Browser data) is transmitted.
l. Execute steps b through f.
m. Send a ping from the mobile station side to cause the mobile station to initiate the transition to Active Mode. Verify that the mobile station sends a Resource Request (Mini) Message, a Supplemental Channel Request (Mini) Message. Verify that the base station sends a Resource Allocation (Mini) Message, a Universal Handoff Direction
13-14
C.S0044-0 v1.0
Message, an Extended Supplemental Channel Assignment (Mini) Message, a Forward Supplemental Channel Assignment Mini Message, or a Reverse Supplemental Channel Assignment Mini Message.
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 3.7.4-131
n. Verify step k.
13.6.5 Minimum Standard
The mobile station and the base station shall comply with the requirements in the following steps:ef, j, k, m, and n.
13.7 Soft Handoff of Fundamental Channel/Dedicated Control Channel and Supplemental Channels
13.7.1 Definition
This test verifies that the mobile station can successfully complete a soft handoff of the fundamental, dedicated control channel, and supplemental channels during a data transfer.
13.7.2 Traceability (see [4] unless otherwise noted)
2.7.2.3.2.18 Supplemental Channel Request Message
2.7.2.3.2.28 Pilot Strength Measurement Mini Message
2.7.2.32.34 Extended Pilot Strength Measure Message
2.7.2.3.2.28 Supplemental Channel Request Mini Message
3.6.6.2.2.12 Processing of Extended Supplemental Channel Assignment Message
3.7.3.3.2.24 Supplemental Channel Assignment Message
3.7.3.3.2.36 Universal Handoff Direction Message
3.7.5.7.1 Channel Configuration for the Supplemental Channel
1.4.2.2 Mobile Station Packet Data Service States (see [15])
2.2.2 Service and Call Control Procedures (see [15])
2.2.3 Initialization and Connection of Packet Data Service Options (see [15])
2.2.7 High Speed Operation (see [15])
13.7.3 Call Flow Example(s)
None
13.7.4 Method of Measurement
13.7.4.1 Forward FCH/DCCH and SCH Soft Handoff
a. Connect the mobile station to the base station as shown in Figure A-5 and setup the parameters as shown in Table 1 .
13-15
C.S0044-0 v1.0
Table 1 -1 3.7.41
Parameter Unit Channel 1 Channel 2
Îor/Ioc dB 7 -20
Pilot Ec/Ior dB -5 -5
Traffic Ec/Ior dB -7 -7
Ioc dBm/1.23 MHz -75
Pilot Ec/Io dB -5.8 -33
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
b. Verify the mobile station is in the Idle State on base station 1.
c. Setup a mobile station originated service option 33 call, using the FCH for signaling.
d. Initiate a forward data transfer to the mobile station.
e. Configure base station 1 to send the Extended Supplemental Channel Assignment Message to assign the maximum number of forward supplemental channels supported by the base station and mobile station.
f. While the forward data transfer is in progress, raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message, Extended Pilot Strength Message, or a Pilot Strength Mini Message.
g. Configure base station 1 to send a Universal Handoff Direction Message with NUM_FOR_ASSIGN = [number of SCH in step e] and both base stations in the active set.
h. Verify the mobile station sends the Handoff Completion Message or an Extended Handoff Completion Message. Verify the mobile station’s active set consist of both base stations.
i. Lower the level of base station 1 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message, Extended Pilot Strength Measurement Message or a Pilot Strength Measurement Mini Message..
j. Configure base station 1 to send a Universal Handoff Direction Message to the mobile station with NUM_FOR_ASSIGN = [number of SCH in step e] and base station 2 in the active set.
k. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message.
l. Verify the data transfer completes successfully.
m. End the call.
n. Repeat steps c through m using the DCCH for signaling.
13-16
C.S0044-0 v1.0
13.7.4.2 Reverse FCH/DCCH and SCH Soft Handoff 1
2 3.7.4-13
4
5
6
7 8 9
10
11 12 13 14
15 16 17
18 19 20
21 22 23 24
25 26 27
28 29
30
31
32
33
34
35
36
37
a. Connect the mobile station to the base station as shown in Figure A-5 and setup the parameters as shown in Table 1 .
b. Verify the mobile station is in the Idle State on base station 1.
c. Setup a mobile station originated service option 33 call using the FCH for signaling.
d. Initiate a reverse data transfer from the mobile station.
e. After the mobile station sends a Supplemental Channel Request Message, configure base station 1 to send an Extended Supplemental Channel Assignment Message to assign the maximum number of reverse supplemental channels supported by the network and mobile station.
f. While the reverse data transfer is in progress, raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement, Extended Pilot Strength Measurement Message or a Pilot Strength Measurement Mini Message.
g. Configure base station 1 to send a Universal Handoff Direction Message with NUM_REV_ASSIGN = [number of SCH in step e] and both base stations in the active set.
h. Verify the mobile station sends the Handoff Completion Message or an Extended Handoff Completion Message. Verify the mobile station’s active set consist of both base stations.
i. Lower the level of base station 1 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message, Extended Pilot Strength Measurement Message or a Pilot Strength Measurement Mini Message.
j. Configure base station 2 to send a Universal Handoff Direction Message to the mobile station with NUM_REV_ASSIGN = [number of SCH in step e] and base station 2 in the active set.
k. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message.
l. Verify the data transfer completes successfully.
m. End the call.
n. Repeat steps c through m using the DCCH.
13.7.5 Minimum Standard
13.7.5.1 Forward FCH/DCCH and SCH Soft Handoff
The mobile station shall comply with steps h, k, l, and n.
13.7.5.2 Reverse FCH/DCCH and SCH Soft Handoff
The mobile station shall comply with steps h, k, l, and n..
13-17
C.S0044-0 v1.0
13.8 Soft Handoff of Fundamental Channel or Dedicated Control Channel only 1
2
3 4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22 3.7.4-123
24
25
26
27 28 29
30 31 32 33
13.8.1 Definition
This test verifies the mobile station can successfully complete a data transfer when only the fundamental channel or dedicated control channel is in soft handoff.
13.8.2 Traceability (see [4] unless otherwise noted)
2.7.2.3.2.18 Supplemental Channel Request Message
2.7.2.3.2.28 Supplemental Channel Request Mini Message
2.7.2.3.2.28 Pilot Strength Measurement Mini Message
2.7.2.32.34 Extended Pilot Strength Measure Message
3.6.6.2.2.12 Processing of Extended Supplemental Channel Assignment Message
3.7.3.3.2.24 Supplemental Channel Assignment Message
3.7.3.3.2.36 Universal Handoff Direction Message
3.7.5.7.1 Channel Configuration for the Supplemental Channel
1.4.2.2 Mobile Station Packet Data Service States (see [15])
2.2.2 Service and Call Control Procedures (see [15])
2.2.3 Initialization and Connection of Packet Data Service Options (see [15])
2.2.7 High Speed Operation (see [15])
13.8.3 Call Flow Example(s)
None
13.8.4 Method of Measurement
13.8.4.1 Forward FCH/DCCH Only Soft Handoff
a. Connect the mobile station to the base station as shown in Figure A-5 and setup the parameters as shown in Table 1 .
b. Verify the mobile station is in the Idle State on base station 1.
c. Setup a mobile station originated service option 33 call using the FCH for signaling.
d. Initiate a forward data transfer to the mobile station.
e. Configure base station 1 to send the Extended Supplemental Channel Assignment Message to assign the maximum number of forward supplemental channels supported by the network and mobile station.
f. While the forward data transfer is in progress, raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message, Extended Pilot Strength Measurement Message or a Pilot Strength Measurement Mini Message.
13-18
C.S0044-0 v1.0
g. Configure base station 1 to send a Universal Handoff Direction Message with NUM_FOR_ASSIGN = 0 and both base stations in the active set.
1 2
3 4 5
6
7
8
9
10 3.7.4-111
12
13
14
15 16 17 18
19 20 21 22
23 24
25 26 27
28
29
30
31
32
33
34
35
h. Verify the mobile station sends the Handoff Completion Message or an Extended Handoff Completion Message. Verify the mobile station’s active set consist of both base stations.
i. Verify the data transfer completes successfully.
j. End the call.
k. Repeat steps c through j using the DCCH for signaling.
13.8.4.2 Reverse FCH/DCCH Only Soft Handoff
a. Connect the mobile station to the base station as shown in Figure A-5 and setup the parameters as shown in Table 1 .
b. Verify the mobile station is in the Idle State on base station 1.
c. Setup a mobile station originated service option 33 call using the FCH for signaling
d. Initiate a reverse data transfer from the mobile station.
e. After the mobile station sends a Supplemental Channel Request Message, Configure base station 1 to send an Extended Supplemental Channel Assignment Message to assign the maximum number of reverse supplemental channels supported by the network and mobile station.
f. While the reverse data transfer is in progress, raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message, Extended Pilot Strength Measurement Message or a Pilot Strength Measurement Mini Message.
g. Configure base station 1 to send a Universal Handoff Direction Message with NUM_REV_ASSIGN = 0 and both base stations in the active set.
h. Verify the mobile station sends the Handoff Completion Message or an Extended Handoff Completion Message. Verify the mobile station’s active set consist of both base stations.
i. Verify the data transfer completes successfully.
j. End the call.
k. Repeat steps c through j with the DCCH for signaling.
13.8.5 Minimum Standard
13.8.5.1 Forward FCH/DCCH Only Soft Handoff
The mobile station shall comply with steps h i, and k.
13.8.5.2 Reverse FCH/DCCH Soft Handoff Only
The mobile station shall comply with steps h, i, and k.
13-19
C.S0044-0 v1.0
13.9 Adding Supplemental Channels during Soft Handoff 1
2
3 4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22 3.7.4-123
24
25
26 27 28
13.9.1 Definition
This test verifies that a supplemental channel(s) can be added in a service option 33 call while in soft handoff on the fundamental channel or dedicated control channel.
13.9.2 Traceability (see [4] unless otherwise noted)
2.7.2.3.2.18 Supplemental Channel Request Message
2.7.2.3.2.28 Pilot Strength Measurement Mini Message
2.7.2.32.34 Extended Pilot Strength Measure Message
2.7.2.3.2.28 Supplemental Channel Request Mini Message
3.6.6.2.2.12 Processing of Extended Supplemental Channel Assignment Message
3.7.3.3.2.24 Supplemental Channel Assignment Message
3.7.3.3.2.36 Universal Handoff Direction Message
3.7.5.7.1 Channel Configuration for the Supplemental Channel
1.4.2.2 Mobile Station Packet Data Service States (see [15])
2.2.2 Service and Call Control Procedures (see [15])
2.2.3 Initialization and Connection of Packet Data Service Options (see [15])
2.2.7 High Speed Operation (see [15])
13.9.3 Call Flow Example(s)
None
13.9.4 Method of Measurement
13.9.4.1 Adding F-SCH during a Soft Handoff
a. Connect the mobile station to the base station as shown in Figure A-5 and setup the parameters as shown in Table 1 .
b. Verify the mobile station is in the Idle State on base station 1.
c. Setup a mobile station originated service option 33 call using the FCH for signaling.
d. Raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message, Extended Pilot Strength Measurement Message ,or a Pilot Strength Measurement Mini Message..29
30 31
.
e. Configure base station 1 to send a Universal Handoff Direction Message with NUM_FOR_ASSIGN = 0 and both base stations in the active set.
13-20
C.S0044-0 v1.0
f. Verify the mobile station sends the Handoff Completion Message or an Extended Handoff Completion Message. Verify the mobile station’s active set consist of both base stations.
1 2 3
4
5 6 7
8
9
10
11
12 3.7.4-113
14
15
16 17 18 19
20 21
22 23 24
25
26 27 28
29
30
31
32
33
34
g. Initiate a forward data transfer to the mobile station.
h. Configure base station 1 to send the Extended Supplemental Channel Assignment Message with NUM_SUP_SHO = ‘001’ for the forward supplemental channel and include both base station 1 and base station 2 for PILOT_PN values.
i. Verify the data transfer completes successfully.
j. End the call.
k. Repeat steps c through j using the DCCH for signaling.
13.9.4.2 Adding R-SCH during a Soft Handoff
a. Connect the mobile station to the base station as shown in Figure A-5 and setup the parameters as shown in Table 1 .
b. Verify the mobile station is in the Idle State on base station 1.
c. Setup a mobile station originated service option 33 call.
d. Raise the level of base station 2 in steps of 1 dB with a dwell time of 5 seconds after each step until the mobile station has generated the Pilot Strength Measurement Message , Extended Pilot Strength Measurement Message or a Pilot Strength Measurement Mini Message..
e. Configure base station 1 to send a Universal Handoff Direction Message with NUM_REV_ASSIGN = 0 and both base stations in the active set.
f. Verify the mobile station sends the Handoff Completion Message or an Extended Handoff Completion Message. Verify the mobile station’s active set consist of both base stations.
g. Initiate a reverse data transfer from the mobile station.
h. Configure base station 1 to send the Extended Supplemental Channel Assignment Message with NUM_SUP_SHO = ‘001’ for the reverse supplemental channel and include both base station 1 and base station 2 for PILOT_PN values.
i. Verify the data transfer completes successfully.
j. End the call.
k. Repeat steps c through j with the DCCH for signaling.
13.9.5 Minimum Standard
13.9.5.1 Adding F_SCH during Soft Handoff
The mobile station shall comply with steps f, i, and k.
13-21
C.S0044-0 v1.0
13.9.5.2 Adding R-SCH during a Soft Handoff 1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21 3.10.4-122
3.10.423
The mobile station shall comply with steps f, i and k.
13.10 Hard Handoff during Data Transfer
13.10.1 Definition
This test verifies the data transfer continues after hard handoff using the forward and reverse link.
13.10.2 Traceability (see [4] unless otherwise noted)
2.7.2.3.2.18 Supplemental Channel Request Message
2.7.2.3.2.28 Supplemental Channel Request Mini Message
3.6.6.2.2.12 Processing of Extended Supplemental Channel Assignment Message
3.7.3.3.2.24 Supplemental Channel Assignment Message
3.7.3.3.2.36 Universal Handoff Direction Message
3.7.5.7.1 Channel Configuration for the Supplemental Channel
1.4.2.2 Mobile Station Packet Data Service States (see [15])
2.2.2 Service and Call Control Procedures (see [15])
2.2.3 Initialization and Connection of Packet Data Service Options (see [15])
2.2.7 High Speed Operation (see [15])
13.10.3 Call Flow Example(s)
None
13.10.4 Method of Measurement
13.10.4.1 Forward Data Transfer during Hard Handoff
a. Connect the mobile station to the base station as shown in Figure A-5 and setup the parameters in Table 1 .
Table 1 -1
Parameter Unit Channel 1 Channel 2
Î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
24
13-22
C.S0044-0 v1.0
b. Ensure that the mobile station is operating in the idle state on base station 1. 1
2
3 4
5 6
7 8
9 10
11
12
13
14
15 3.10.4-116
17
18
19 20
21 22
23 24
25 26
h. Configure base station 2 to send a Universal Handoff Direction Message or an 27 Extended Supplemental Channel Assignment Message assigning a R-SCH. 28
29
30
31
32
33
34
c. Setup a mobile station originated Service Option 33 call.
d. Initiate a data transfer to the mobile station and verify the base station sends an Extended Supplemental Channel Assignment Message assigning a F-SCH.
e. While the data transfer is in progress, instruct the base station to send a Universal Handoff Direction Message directing the mobile station to base station 2.
f. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message.
g. Configure base station 2 to send a Universal Handoff Direction Message or an Extended Supplemental Channel Assignment Message assigning a F-SCH.
h. Verify the data transfer completes.
i. End the call from the mobile station.
j. Repeat steps c through i using the DCCH for signaling.
13.10.4.2 Reverse Data Transfer during Hard Handoff
a. Connect the mobile station to the base station as shown in Figure A-5 and setup the parameters in Table 1 .
b. Ensure that the mobile station is operating in the idle state on base station 1.
c. Setup a mobile station originated Service Option 33 call.
d. Initiate a data transfer from the mobile station and verify the mobile station sends a Supplemental Channel Request Message requesting a reverse supplemental channel.
e. Instruct the base station to send an Extended Supplemental Channel Assignment Message assigning a reverse supplemental channel to the mobile station.
f. While the data transfer is in progress, instruct the base station to send a Universal Handoff Direction Message directing the mobile station to base station 2.
g. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message.
i. Verify the data transfer completes successfully.
j. End the call from the mobile station.
k. Repeat steps c through j using the DCCH for signaling.
13.10.5 Minimum Standard
13.10.5.1 Forward Data Transfer during Hard Handoff
The mobile station shall comply with steps f, h and j.
13-23
C.S0044-0 v1.0
13.10.5.2 Reverse Data Transfer during Hard Handoff 1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21 3.10.4-122
23
24 25
26 27
28 29 30
31 32
The mobile station shall comply with steps g, i, and k.
13.11 Hard Handoff to a different Radio Configuration
13.11.1 Definition
This test verifies hard handoff to a different radio configuration during an HSPD call.
13.11.2 Traceability (see [4] unless otherwise noted)
2.7.2.3.2.18 Supplemental Channel Request Message
2.7.2.3.2.28 Supplemental Channel Request Mini Message
3.6.6.2.2.12 Processing of Extended Supplemental Channel Assignment Message
3.7.3.3.2.24 Supplemental Channel Assignment Message
3.7.3.3.2.36 Universal Handoff Direction Message
3.7.5.7.1 Channel Configuration for the Supplemental Channel
1.4.2.2 Mobile Station Packet Data Service States (see [15])
2.2.2 Service and Call Control Procedures (see [15])
2.2.3 Initialization and Connection of Packet Data Service Options (see [15])
2.2.7 High Speed Operation (see [15])
13.11.3 Call Flow Example(s)
None
13.11.4 Method of Measurement
13.11.4.1 Forward Data Transfer during Hard Handoff
a. Connect the mobile station to the base station as shown in Figure A-5 and setup the parameters in Table 1 .
b. Ensure that the mobile station is operating in the idle state on base station 1.
c. Setup a mobile station originated Service Option 33 call. Note the FOR_FCH_RC, REV_FCH_RC, and SCH_RC values.
d. Initiate a data transfer to the mobile station and verify the base station sends an Extended Supplemental Channel Assignment Message assigning a F-SCH.
e. While the data transfer is in progress, instruct the base station to send a Universal Handoff Direction Message changing the FOR_FCH_RC, REV_FCH_RC and SCH_RC values in step c and directing the mobile station to base station 2.
f. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message.
13-24
C.S0044-0 v1.0
g. Configure base station 2 to send an Extended Supplemental Channel Assignment Message assigning a F-SCH.
1 2
3
4
5
6
7
8 3.10.4-19
10
11 12
13 14
15 16
17 18 19
20 21
22 23
24
25
26
27
28
29
30
31
32
h. Verify the data transfer completes.
i. End the call from the mobile station.
j. This test may be repeated for all radio configurations supported.
k. Repeat steps c through j with the DCCH for signaling.
13.11.4.2 Reverse Data Transfer during Hard Handoff
a. Connect the mobile station to the base station as shown in Figure A-5 and setup the parameters in Table 1 .
b. Ensure that the mobile station is operating in the idle state on base station 1.
c. Setup a mobile station originated Service Option 33 call. Note the FOR_FCH_RC, REV_FCH_RC, and SCH_RC values.
d. Initiate a data transfer from the mobile station and verify the mobile station sends a Supplemental Channel Request Message requesting a reverse supplemental channel.
e. Instruct the base station to send an Extended Supplemental Channel Assignment Message assigning a reverse supplemental channel to the mobile station.
f. While the data transfer is in progress, instruct the base station to send a Universal Handoff Direction Message changing the FOR_FCH_RC, REV_FCH_RC and SCH_RC values in step c directing the mobile station to base station 2.
g. Verify the mobile station sends a Handoff Completion Message or an Extended Handoff Completion Message.
h. Configure base station 2 to send a Universal Handoff Direction Message or an Extended Supplemental Channel Assignment Message assigning a R-SCH.
i. Verify the data transfer completes successfully.
j. End the call from the mobile station.
k. This test may be repeated for all radio configurations supported.
l. Repeat steps c through k using the DCCH for signaling
13.11.5 Minimum Standard
13.11.5.1 Forward Data Transfer during Hard Handoff
The mobile station shall comply with steps f, h, and k.
13.11.5.2 Reverse Data Transfer during Hard Handoff
The mobile station shall comply with steps g, i, and l.
13-25
C.S0044-0 v1.0
13.12 Mobile Station Packet Data Inactivity Timer 1
2
3 4 5
6
7
8
9
10
11
12 13
14
15
16
17 18
19
20
21 22
23 24
25
26
27
28
29
30 31 32 33
13.12.1 Definition
This test is applicable for a mobile station implementing packet data inactivity timer. This test verifies the mobile station releases the traffic channel after expiration of the mobile station packet data Inactivity Timer. The test verifies the dormant link layer connection can be re-activated.
13.12.2 Traceability
2.2.2 Service and Call Control Procedures
13.12.3 Call Flow Example(s)
None
13.12.4 Method of Measurement
a. Set the packet data inactivity timer at the MT2 to 20 seconds.
b. Ensure the base station packet data inactivity timer is disabled or set to a value of at least 30 seconds.
c. Initiate a Telnet session to a remote host.
d. Record the IP address assigned to the mobile station.
e. Exit the Telnet session.
f. Wait for the mobile station packet data inactivity timer to expire. Verify the “in use” indicator on the MT2 goes OFF.
g. Initiate a Telnet session to a remote host.
h. Record the IP address assigned to the mobile station.
i. Wait for the mobile station packet data inactivity timer to expire. Verify the “in use” indicator on the MT2 goes OFF.
j. Issue a continuous “ping” command from the remote host to the mobile station using the IP address assigned to the mobile station.
k. Verify that the ping is successful.
13.12.5 Minimum Standard
The mobile station shall comply with steps f, i and k .
13.13 Mobile Station and Base Station Operating in Different States
13.13.1 Definition
This test verifies the mobile station and base station correct the condition of the mobile station operating in the Null State and the base station/PCF operating in the Dormant State. [4] permits two standardized approaches for the mobile station to reject/release a General Page Message containing Service Option 33 when the mobile station is in the Null State and the base
13-26
C.S0044-0 v1.0
1 2
3 4 5
6 7 8 9
10
11
12
13
14
15
16
17
station/PCF is in the Dormant State. In both implementations, the mobile station and base station/PCF shall transition to the Null State.
In the preferred implementation, a mobile station in the Null State will reject a General Page Message containing Service Option 33 by sending a Page Response Message containing Service Option = 0x00. The base station should send a Release Order to the mobile station.
In an alternate implementation, a mobile station in the Null State will accept a General Page Message containing Service Option 33 by sending a Page Response Message containing Service Option 33. After the base station assigns a traffic channel, the mobile station sends a Release Order containing ORDQ=2 to release the call.
13.13.2 Traceability
3.7.4.1 Page Response Substate [4]
2.7.1.3.2.5 Page Response Message [4]
3.6.2.3 Mobile Station Directed Messages [4]
3.6.3.3 Responding to a Page Response Message [4]
3.7.4 Orders [4]
2.2.2.2.1.3 Paging State [15]
13.13.3 Call Flow Example(s)
DormantState
DormantState
MSBS/PCF
Null State
Null State Null State
General Page, SO:0x21
Page Response Msg with SO:0x00
BS should send Release Order
DormantState
MS and BS/PCF are notin the same
state. MS hasclosed PPP
sessionwithout
notifying BS/PCF. BS/PCF
attempts toinitiate a
dormant toactive
transition.
18
319 Figure 1 -5 Call Flow without Setting Up Traffic Channel (Preferred Implementation)
13-27
C.S0044-0 v1.0
Traffic Channel Setup
DormantState
DormantState
MS BS/PCF
Null State DormantState
Null State Null State
General Page, SO:0x21
Page Response Msg with SO: 0x21
BS/PCFattempts to
initiate adormant to
activetransition.
MS and BS/PCF are notin the same
state. MS hasclosed PPP
sessionwithout
notifying BS/PCF.
Conversation
MS sends Release Order withORDQ=2
1
32
3
4
5
6
7
8 9
10 11 12
13 14 15
16
17 18
Figure 1 -6 Call Flow with Setting Up Traffic Channel (Alternate Implementation)
13.13.4 Method of Measurement
a. Connect the mobile station as shown in Figure A-3.
b. Set up a Service Option 33 call using a dedicated traffic channel.
c. Allow the mobile station to enter the Dormant State.
d. Verify the base station/PCF and mobile station are operating in the Dormant State.
e. Instruct the mobile station to transition to the Null State (i.e. terminate the PPP session) without notifying the base station. (e.g., disconnect the mobile station from the laptop.) NOTE: Depending on implementation, the mobile station may autonomously originate a service option 33 call upon the disconnection of the cable from the laptop. If this occurs, proceed to step g2.
f. Instruct the base station to initiate the Dormant to Active transition by sending a General Page Message or Universal Page Message to the mobile station with the Service Option 33.
g. Verify one of the following occurs;
1. The mobile station sends a Page Response Message with the Service Option = 0:
13-28
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
33
34
35
a. The base station should send a Release Order to the mobile station after receiving the Page Response Message with the Service Option = 0.
2. The mobile station sends a Page Response Message/Origination Message with the Service Option = 33:
a. After the base station assigns a traffic channel, verify the mobile station sends a Release Order with ORDQ=2.
h. Verify the mobile station and base station/PCF are now operating in the Null State.
13.13.5 Minimum Standard
The mobile station shall comply with steps g and h.
13.14 RLP Operation in Rayleigh Fading Environment
13.14.1 Definition
This test verifies data transfer under Rayleigh fading channel conditions. This test verifies that RLP recovers erased data frames, and is intended to exercise RLP negative acknowledgements (NAKs), retransmissions, and aborts in the forward and reverse directions. This test also verifies the mobile station is able to successfully complete a network initiated dormant to active transition.
13.14.2 Traceability
2.6.4.3 Traffic Channel Substate [See 4]
2.2.1 RLP Requirements [See 15]
2.2.2 Service and Call Control Procedures [See 15]
2.2.7 High Speed Operation [See 15]
13.14.3 Call Flow Example(s)
None
13.14.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-2.
b. Set the channel simulator using the parameters as specified in Table 3.5.4-4.
c. Ensure the mobile station currently has a PPP session established and is in the dormant state.
d. Instruct the base station to initiate a dormant to active transition.
e. Verify the mobile station is able to transition to the active state.
f. Initiate a forward data transfer to the mobile station.
g. Verify the file transfer completes successfully.
h. Initiate a reverse data transfer from the mobile station.
i. Verify the file transfer completes.
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
13.14.5 Minimum Standard 1
2
3
4
5 6
7
8
9
10
11
2.2.3 Initialization and Connection of Packet Data Service Options (see [15]) 12
13
14
15
The mobile station shall comply with steps e, g, i, and j.
13.15 Release Order Processing
13.15.1 Definition
This test case verifies the mobile station correctly processes the Release Order with ORDQ=2 when received on the f-csch.
13.15.2 Traceability (see [4] unless otherwise noted)
2.7.1.3.2.4 Origination Message
3.7.4 Orders
1.4.2.2 Mobile Station Packet Data Service States (see [15])
2.2.2 Service and Call Control Procedures (see [15])
2.2.7 High Speed Operation (see [15])
13-30
C.S0044-0 v1.0
1 13.15.3 Call Flow Example(s)
Origination Message
Acknowledgment Order
Release Order withORDQ=2
Origination Message withnew service option
MS BS
Extended Channel AssignementMessage
TCH
Acknowledgment Order
The mobile station mayoriginate another call using adifferent service option (e.g
SO12)
2
3
a. Configure the network to not allow Service Option 33 calls for the mobile station. (Note: 4 The network has packet data resources available, however the mobile station is not 5 authorized to use them.) 6
7
8 9
10 11
12 13
14
15
13.15.4 Method of Measurement
b. Instruct the mobile station to originate a Service Option 33 call.
c. Instruct the base station to send a Release Order with ORDQ = 2 to mobile station indicating the requested service option has been rejected.
d. Verify the mobile station returns to the System Determination Substate or the Mobile Station Idle State.
e. The mobile station may autonomously attempt to originate another data service option (e.g. SO=12).
f. If the mobile station originates another service option and:
1. The base station supports that service option and has resources available, and
13-31
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 33
34
35
2. The mobile station is authorized to use that service option, verify the following:
a. The new data call with the different service option is completed successfully.
13.15.5 Minimum Standard
The mobile station shall comply with step d. If the mobile station supports step e, the mobile station shall comply with step f.
13.16 Hysteresis Activation Timer
13.16.1 Definition
This test case verifies the mobile station implementation of Hysteresis Activation Timer. The value of this timer is mobile station implementation dependent in the range of 0 to 30 seconds.
13.16.2 Traceability (see [15])
2.2.2.1.2.4 Dormant State
13.16.3 Call Flow Example(s)
None
13.16.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-5. Configure base station 1 and base station 2 to transmit different non-zero values of PACKET_ZONE_ID field in Extended System Parameters Message or ANSI-41 System Parameters Message. Connect both the base stations to same PDSN.
b. Allow the mobile station to go idle on base station 1. Instruct the mobile station to originate a Service Option 33 call on base station 1. Transfer data on the Service Option 33 call (e.g. perform ftp or ping).
c. Ensure that length of the packet zone list is set to one entry at the mobile station. Ensure packet zone hysteresis is enabled at the mobile station.
d. Allow Mobile Station to go dormant on base station 1. For rest of the test ensure that the mobile station does not have any data to send.
e. While the hysteresis activation timer is running perform following operations:
1. Allow Mobile Station to perform an idle handoff to base station 2. Verify that the mobile station sends an Origination Message with DRS field set to ‘0’ to base station 2.
2. Allow Mobile Station to perform an idle handoff to base station 1. Verify that the mobile station sends an Origination Message with DRS field set to ‘0’ to base station 1.
13.16.5 Minimum Standard
The mobile station shall comply with step e
13-32
C.S0044-0 v1.0
13.17 Hysteresis Timer 1
2
3 4
5
6
7
8
9
10 11 12 13
14 15 16
17 18
19 20 21
22 23
24 25 26
27 28
29 30 31 32 33
34
35
36
13.17.1 Definition
This test case verifies the mobile station implementation of Hysteresis Timer. The value of this timer is mobile station implementation dependent in the range of 0 to 60 seconds.
13.17.2 Traceability (see [15])
2.2.5 Packet Zone Reconnection Control
13.17.3 Call Flow Example(s)
None
13.17.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-5. Configure base station 1 and base station 2 to transmit different non-zero values of PACKET_ZONE_ID field in Extended System Parameters Message or ANSI-41 System Parameters Message. Connect both the base stations to same PDSN.
b. Allow the mobile station to go idle on base station 1. Instruct the mobile station to originate a Service Option 33 call on base station 1. Transfer data on the Service Option 33 call (e.g. perform ftp or ping).
c. Ensure that length of the packet zone list is set to one entry at the mobile station. Ensure packet zone hysteresis is enabled at the mobile station.
d. Allow Mobile Station to go dormant on base station 1. Allow mobile station to remain in dormant state for duration of the hysteresis activation timer. For rest of the test ensure that the mobile station does not have any data to send.
e. Perform following operations within duration less than the value of hysteresis timer configured at the mobile station:
1. Allow Mobile Station to perform an idle handoff to base station 2. Verify that the mobile station sends an Origination Message with DRS field set to ‘0’ to base station 2.
2. Allow Mobile Station to perform an idle handoff to base station 1. Verify that the mobile station does not send an Origination Message.
f. Allow Mobile Station to remain idle on base station 1 for duration more than the value of hysteresis timer configured at the mobile station. Verify that the mobile station sends an Origination Message with DRS field set to ‘0’ to base station 1. Verify that the duration between the Origination Message in step d.1 and the Origination Message in step e is approximately equal to the value of hyesteresis timer configured at the mobile station.
13.17.5 Minimum Standard
The mobile station shall comply with steps e and f.
13-33
C.S0044-0 v1.0
14 OVER-THE-AIR SERVICES 1
2
3
4 5
6
7
8
9
10
11
12
13
14
15
16
17
a. 18
19
20 4.1.4-121
14.1 OTASP Download Request Processing
14.1.1 Definition
This test verifies a mobile station can initiate programming procedure and update its NAM parameters.
14.1.2 Traceability (see [14])
3.2.1 User-Initiated Procedure
3.5.1 Message Contents
3.5.2 NAM Parameter Blocks
4.2.1 User-Initiated Procedure
4.3 Programming Data Download
4.5.1 Message Contents
4.5.2 NAM Parameter Blocks
4.5.4 Validation Parameter Blocks
14.1.3 Call Flow Example(s)
None
14.1.4 Method of Measurement
Connect the mobile station to the base station as shown in Figure A-1.
b. Confirm that the mobile station is programmed with a non-zero SPCp.
c. Setup a mobile originated OTASP call using *228 + one of the System Selection Codes in Table 1 .
14-1
C.S0044-0 v1.0
Table 1 -1 4.1.41
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 4
5 6 7 8
f. 9
10 11
12 13 14
15
16 17
18 19 20
21 22
d. Upon call setup, instruct the base station to send a Protocol Capability Request Message to the mobile station.
e. Verify the mobile station sends a Protocol Capability Response Message to the base station with MOB_FIRM_REV, MOB_MODEL, BAND_MODE_CAP and all supported FEATURE_ID and FEATURE_P_REV as listed in ANNEX C. The NAM Download feature support is required for this test.
If Service Programming Lock is supported, perform the following:
1. Instruct the base station to send a Validation Request Message with BLOCK_ID = ’00000000’ and SPC = SPCP.
2. Verify the mobile station sends a Validation Response Message within 750 ms, and with BLOCK_ID = ’00000000’ and RESULT_CODE = ’00000000’ (Accepted – Operation Successful).
g. If the Key Exchange is not supported, go to step h; otherwise:
1. Instruct the base station to send an Mobile Station Key Request Message to the mobile station.
2. Verify the mobile station responds with a Mobile Station Key Response Message within 30 seconds, with RESULT_CODE = '00000000' (Accepted - Operation Successful).
3. Instruct the base station to send a Key Generation Request Message to the mobile station.
14-2
C.S0044-0 v1.0
1 2 3
4 5
6 7
8
9
10 11
12
4. Verify the mobile station responds with a Key Generation Response Message within 30 seconds and the RESULT_CODE = '00000000' (Accepted - Operation Successful).
5. Verify the base station and the mobile station successfully perform SSD update procedures.
6. Verify the base station sends the Re-Authenticate Request Message and the mobile responds with the Re-Authenticate Response Message within 750ms.
7. At the base station verify Re-Authentication is successful.
8. The base station may enable Signaling Message Encryption and Voice Privacy.
h. Instruct the base station to send a Configuration Request Message with one or more of the following NAM Parameter Block Types:
Parameter Block Type BLOCK_ID
CDMA/Analog NAM ‘00000000’
Mobile Directory Number ‘00000001’
CDMA NAM ‘00000010’
IMSI_T ‘00000011’
13 14 15
16 17
18
i. Verify the mobile station sends a Configuration Response Message within 750ms including each requested BLOCK_ID and associated PARAM_DATA with corresponding RESULT_CODE.
j. Instruct the base station to send a Download Request Message with one or more of the following NAM Parameter Block Types and the corresponding PARAM_DATA:
Parameter Block Type BLOCK_ID
CDMA/Analog NAM ‘00000000’
Mobile Directory Number ‘00000001’
CDMA NAM ‘00000010’
IMSI_T ‘00000011’
19 20
21
22 23
24
25
k. Verify the mobile station sends a Download Response Message and that RESULT_CODE = '00000000' (Accepted- Operation Successful) within 750ms.
l. Instruct the base station to send a Commit Request Message to the mobile station.
m. Verify the mobile station sends a Commit Response Message to the base station within 10 seconds with the RESULT_CODE = '00000000' (Accepted- Operation Successful).
n. End the call at the mobile station.
o. Verify the mobile station successfully stored the updated NAM information.
14-3
C.S0044-0 v1.0
p. Setup a mobile station originated call and verify user traffic is present. 1
2
3 4 5
6
7
8 9
10
11
12
13
14
15
16
17
18
19
20
21
22
a. 23
24
25 26
27 28
29 30 31 32
f. 33
14.1.5 Minimum Standard
The mobile station shall comply with steps e, i, k, m, o, and p. If supported the mobile station shall comply with steps f and i. The mobile station shall update its NAM information as received in the Download Request Message.
14.2 OTASP PUZL Download Request Processing
14.2.1 Definition
This test verifies a mobile station can initiate programming procedure and update its Preferred User Zone List (PUZL).
14.2.2 Traceability (see [14])
3.2.1 User-Initiated Procedure
3.5.1 Message Contents
3.5.6 PUZL Parameter Blocks
3.5.7 Preferred User Zone List (PUZL)
4.2.1 User-Initiated Procedure
4.3 Programming Data Download
4.5.1 Message Contents
4.5.4 Validation Parameter Blocks
4.5.6 PUZL Parameter Blocks
14.2.3 Call Flow Example(s)
None
14.2.4 Method of Measurement
Connect the mobile station to the base station as shown in Figure A-3.
b. Confirm that the mobile station is programmed with a non-zero SPCp.
c. Setup a mobile station originated OTASP call using *228 + one of the System Selection Codes in Table 14.1.4-1.
d. Upon call setup, instruct the base station to send a Protocol Capability Request Message to the mobile station.
e. Verify the mobile station sends a Protocol Capability Response Message to the base station with MOB_FIRM_REV, MOB_MODEL, BAND_MODE_CAP and all supported FEATURE_ID and FEATURE_P_REV as listed in ANNEX C. The Preferred User Zone List feature support is required for this test.
If Service Programming Lock is supported, perform the following:
14-4
C.S0044-0 v1.0
1. Instruct the base station to send a Validation Request Message with BLOCK_ID = ’00000000’ and SPC = SCP
1 2
3 4 5
6 7
8
p.
2. Verify the mobile station sends a Validation Response Message within 750 ms, and with BLOCK_ID = ’00000000’ and RESULT_CODE = ’00000000’ (Accepted – Operation Successful).
g. Instruct the base station to send a PUZL Configuration Request Message to the mobile station with one of the following BLOCK_ID values:
PUZL Parameter Block Type BLOCK_ID
PUZL Dimensions ‘00000000’
PUZL Priorities ‘00000001’
User Zone ‘00000010’
Preferred User Zone List ‘00000011’
9 10 11
12 13 14
h. Verify the mobile station sends a PUZL Configuration Response Message within 750ms with the BLOCK_ID and associated PARAM_DATA requested in the PUZL Configuration Request Message.
i. Instruct the base station to send a PUZL Download Request Message with one or more of the following PUZL Parameter Block Types and the corresponding PARAM_DATA:
Parameter Block Type BLOCK_ID
User Zone Insert ‘00000000’
User Zone Update ‘00000001’
User Zone Delete ‘00000010’
User Zone Priority Change ‘00000011’
PUZL Flags ‘00000100’
15 16
17
18 19
20
21
22
23 24
j. Verify the mobile station sends a PUZL Download Response Message within 750ms with the RESULT_CODE = ’00000000’ (Accepted – Operation Successful).
k. Instruct the base station to send a Commit Request Message to the mobile station.
l. Verify the mobile station sends a Commit Response Message to the base station within 10 seconds with the RESULT_CODE = '00000000' (Accepted- Operation Successful).
m. End the call at the mobile station.
n. Verify the mobile station successfully stored the updated PUZL information.
14.2.5 Minimum Standard
The mobile station shall comply with steps e, h, j, l, and n. The mobile station shall update its PUZL information as received in the PUZL Download Request Message.
14-5
C.S0044-0 v1.0
14.3 OTASP 3GPD Download Request Processing 1
2
3 4
5
6
7
8
9
10
11
12
13
14
15
16
a. 17
18
19 20
21 22
23 24 25 26
f. 27
28 29
30 31 32
33 34
14.3.1 Definition
This test verifies a mobile station can initiate programming procedure and update its 3GPD information.
14.3.2 Traceability (see [14])
3.2.1 User-Initiated Procedure
3.5.1 Message Contents
3.5.8 3GPD Parameter Blocks
4.2.1 User-Initiated Procedure
4.3 Programming Data Download
4.5.1 Message Contents
4.5.4 Validation Parameter Blocks
4.5.7 3GPD Parameter Blocks
14.3.3 Call Flow Example(s)
None
14.3.4 Method of Measurement
Connect the mobile station to the base station as shown in Figure A-3.
b. Confirm that the mobile station is programmed with a non-zero SPCp .
c. Setup a mobile station originated OTASP call using *228 + one of the System Selection Codes in Table 14.1.4-1.
d. Upon call setup, instruct the base station to send a Protocol Capability Request Message to the mobile station.
e. Verify the mobile station sends a Protocol Capability Response Message to the base station with MOB_FIRM_REV, MOB_MODEL, BAND_MODE_CAP and all supported FEATURE_ID and FEATURE_P_REV as listed in ANNEX C. The 3G Packet Data feature support is required for this test.
If Service Programming Lock is supported, perform the following:
1. Instruct the base station to send a Validation Request Message with BLOCK_ID = ’00000000’ and SPC = SPCp.
2. Verify the mobile station sends a Validation Response Message within 750 ms, and with BLOCK_ID = ’00000000’ and RESULT_CODE = ’00000000’ (Accepted – Operation Successful).
g. Instruct the base station to send a 3GPD Configuration Request Message to the mobile station with one or more of the following 3GPD Parameter Block Types from Table
14-6
C.S0044-0 v1.0
14.3.4-11 2
3
4
. If the 3GPD Parameter Block Type requests the shared secret do the following prior to sending the 3GPD Configuration Request Message:
h. Instruct the base station to send a Secure Mode Request Message with
Field Value
START_STOP ‘1’
KEY_IN_USE ‘0000’ or ‘0001’
RAND_SM Randomly selected value for SMCK
5 6
7
1. Verify the mobile station sends a Secure Mode Response Message within 750ms with RESULT_CODE = ’00000000’ (Accepted – Operation Successful).
14-7
C.S0044-0 v1.0
Table 1 -1 4.3.41
3GPD Parameter Block Type BLOCK_ID
3GPD Operation Capability Parameters
‘00000000’
3GPD Operation Mode Parameters
‘00000001’
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’
MobileIP SS Parameters1 ‘00001010’
HRPD Access Authentication Capability Parameters
‘00001011’
HRPD Access Authentication User Profile Parameters
‘00001100’
HRPD Access Authentication CHAP SS Parameters1
‘00001101’
1The shared secret parameters shall not be transmitted over the air unencrypted.
2
3 4 5
6 7
i. Verify the mobile station sends a 3GPD Configuration Response Message within 750ms including each requested BLOCK_ID and associated PARAM_DATA with corresponding RESULT_CODE. If SECURE_MODE_INDs = ‘1’, then:
1. Verify the mobile station includes the following in the 3GPD Configuration Response Message:
14-8
C.S0044-0 v1.0
Field Value
FRESH_INCL ‘1’
15-bit value used for encryption
FRESH
j. Instruct the base station to send a 3GPD Download Request Message with one or more of the 3GPD Parameter Block Types from Table 1 and the corresponding PARAM_DATA. If SECURE_MODE_INDs = ‘1’, then:
1 4.3.4-22
3
4 5
6
1. Verify the base station includes the following in the 3GPD Download Request Message:
Field Value
FRESH_INCL ‘1’
FRESH 15-bit value used for encryption
7
4.3.48 Table 1 -2
Parameter Block Type BLOCK_ID
3GPD Operation Mode Parameters
‘00000000’
SimpleIP User Profile Parameters ‘00000001’
‘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 Profile Parameters
‘00001011’
HRPD Access Authentication CHAP SS Parameters1
‘00001100’
1The shared secret parameters shall not be transmitted over the air unencrypted.
Mobile IP User Profile Parameters
k. Verify the mobile station sends a 3GPD Download Response Message within 750ms with the RESULT_CODE = ’00000000’ (Accepted – Operation Successful).
9 10
14-9
C.S0044-0 v1.0
l. Instruct the base station to send a Commit Request Message to the mobile station. 1
2 3
4
5
14.3.5 6
7 8 9
10
11
12 13
14
15
16
17
18
19
20
4.5.1 Message Contents 21
22
23
24
25
26
a. 27
28
29 30
31 32
m. Verify the mobile station sends a Commit Response Message to the base station within 10 seconds with the RESULT_CODE = '00000000' (Accepted- Operation Successful).
n. End the call at the mobile station.
o. Verify the mobile station successfully stored the 3GPD information.
Minimum Standard
The mobile station shall comply with steps e, h, k, m and o. If SECURE_MODE_INDs = ‘1’, the mobile station shall comply with step g. The mobile station shall update its 3GPD information as received in the 3GPD Download Request Message.
14.4 OTASP SSPR Download Request Processing
14.4.1 Definition
This test verifies a mobile station can initiate programming procedure and update its preferred roaming list.
14.4.2 Traceability (see [14])
3.2.1 User-Initiated Procedure
3.5.1 Message Contents
3.5.3 SSPR Parameter Blocks
3.5.5 Preferred Roaming List and Extended Preferred Roaming List
4.2.1 User-Initiated Procedure
4.3 Programming Data Download
4.5.3 SSPR Parameter Blocks
4.5.4 Validation Parameter Blocks
14.4.3 Call Flow Example(s)
None
14.4.4 Method of Measurement
Connect the mobile station to the base station as shown in Figure A-4.
b. Confirm that the mobile station is programmed with a non-zero SPCp.
c. Setup a mobile originated OTASP call using *228 + one of the System Selection Codes in Table 14.1.4-1.
d. Upon call setup, instruct the base station to send a Protocol Capability Request Message to the mobile station.
14-10
C.S0044-0 v1.0
e. Verify the mobile station sends a Protocol Capability Response Message to the base station with MOB_FIRM_REV, MOB_MODEL, BAND_MODE_CAP and all supported FEATURE_ID and FEATURE_P_REV as listed in ANNEX C. The System Selection for Preferred Roaming feature support is required for this test.
1 2 3 4
f. 5
6 7
2. Verify the mobile station sends a Validation Response Message within 750 ms, 8 and with BLOCK_ID = ’00000000’ and RESULT_CODE = ’00000000’ (Accepted 9 – Operation Successful). 10
11 12
13
If Service Programming Lock is supported, perform the following:
1. Instruct the base station to send a Validation Request Message with BLOCK_ID = ’00000000’ and SPC = SCPp.
g. Instruct the base station to send a SSPR Configuration Request Message to the mobile station with one of the following SSPR Parameter Block Types:
SSPR Parameter Block Type BLOCK_ID
Preferred Roaming List Dimensions
‘00000000’
Preferred Roaming List ‘00000001’
Extended Preferred Roaming List Dimensions
‘00000010’
14 15
16 17
18
h. Verify the mobile station sends a SSPR Configuration Response Message within 750ms with the BLOCK_ID and the associated PARAM_DATA.
i. Instruct the base station to send a SSPR Download Request Message with one of the following SSPR Parameter Block Types and the corresponding PARAM_DATA:
Parameter Block Type BLOCK_ID
Preferred Roaming List ‘00000000’
‘00000001’ Extended Preferred Roaming List with SSPR_P_REV greater than ‘00000001’
19 20
21
22 23
24
25
j. Verify the mobile station sends a SSPR Download Response Message within 750ms with the RESULT_CODE = ’00000000’ (Accepted – Operation Successful).
k. Instruct the base station to send a Commit Request Message to the mobile station.
l. Verify the mobile station sends a Commit Response Message to the base station within 10 seconds with the RESULT_CODE = '00000000' (Accepted- Operation Successful).
m. End the call at the mobile station.
n. Verify the mobile station successfully stored the updated SSPR information.
14-11
C.S0044-0 v1.0
14.4.5 Minimum Standard 1
2 3
4
5
6 7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
a. 22
23
24 25
26 27
28 29 30 31
f. 32
The mobile station shall comply with steps e, h, j, l, and n. The mobile station shall update its SSPR information as received in the SSPR Download Request Message.
14.5 OTASP For System Selection and Preferred Roaming - Oversize PRL
14.5.1 Definition
This test verifies that the PRL resident in a handset shall not be replaced if a new PRL of illegal size is downloaded.
14.5.2 Traceability (see [14])
3.2.1 User-Initiated Procedure
3.5.1 Message Contents
3.5.3 SSPR Parameter Blocks
3.5.5 Preferred Roaming List and Extended Preferred Roaming List
4.2.1 User-Initiated Procedure
4.3 Programming Data Download
4.5.1 Message Contents
4.5.3 SSPR Parameter Blocks
4.5.4 Validation Parameter Blocks
14.5.3 Call Flow
None
14.5.4 Method of Measurement
Connect the mobile station to the base station as shown in Figure A-3.
b. Confirm that the mobile station is programmed with a non-zero SPCp.
c. Setup a mobile station originated OTASP call using *228 + one of the System Selection Codes in Table 14.1.4-1.
d. Upon call setup, instruct the base station to send a Protocol Capability Request Message to the mobile station.
e. Verify the mobile station sends a Protocol Capability Response Message to the base station with MOB_FIRM_REV, MOB_MODEL, BAND_MODE_CAP and all supported FEATURE_ID and FEATURE_P_REV as listed in ANNEX C. The System Selection for Preferred Roaming feature support is required for this test.
If Service Programming Lock is supported, perform the following:
14-12
C.S0044-0 v1.0
1. Instruct the base station to send a Validation Request Message with BLOCK_ID = ’00000000’ and SPC = SCP
1 2
3 4 5
6 7
8 9
10 11 12
13 14
15 16
17
18
19 20
21
22
23 24 25
26
27
28
29
30
31
32
33
34
35
p.
2. Verify the mobile station sends a Validation Response Message within 750 ms, and with BLOCK_ID = ’00000000’ and RESULT_CODE = ’00000000’ (Accepted – Operation Successful).
g. Instruct the base station to send a SSPR Configuration Request Message to the mobile station.
h. Verify the mobile station sends a SSPR Configuration Response Message within 750ms with the requested BLOCK_ID and the associated PARAM_DATA.
i. Instruct the base station to send a SSPR Download Request Message to the mobile station with values of SEGMENT_OFFSET in conjunction with SEGMENT_SIZE that are inconsistent with the preferred roaming list storage capabilities of the mobile station.
j. Verify the mobile station sends a SSPR Download Response Message with RESULT_CODE = ’00001000’ (Rejected – Preferred roaming list length mismatch).
k. Verify the mobile station does not transfer its new PR_LIST to semi-permanent memory after receiving a Commit Request Message.
l. End call at the mobile station
14.5.5 Minimum Standard
The mobile station shall comply with step h, j, and k. The mobile station shall retain its original PRL.
14.6 OTAPA Download Request Processing
14.6.1 Definition
This test verifies that the mobile station supports network initiated Over-the-Air-Parameter-Administration (OTAPA). This test also verifies the mobile station’s download request processing is successful.
14.6.2 Traceability (see [14])
3.2.2 Network-Initiated Procedure
3.4 Termination of the Programming Procedure
3.5.1 Message Contents
3.5.2 NAM Parameter Blocks
4.2.2 Network-Initiated Procedure
4.3 Programming Data Download
4.4 Termination of the Programming Procedure
4.5.1 Message Contents
4.5.2 NAM Parameter Blocks
14-13
C.S0044-0 v1.0
4.5.4 Validation Parameter Blocks 1
2
3
4
a. 5
6
7 8
9 10
11 12
13 14 15
16
17 18 19
20 21 22
23 24
25 26 27
i. 28
29 30
31 32 33
34 35
14.6.3 Call Flow Example(s)
None
14.6.4 Method of Measurement
Connect the mobile station to the base station as shown in Figure A-3.
b. Confirm that the mobile station is programmed with a non-zero SPCp.
c. Initiate an OTAPA session from the base station by sending a General Page Message to the mobile station with the SERVICE_OPTION = 0x12 or 0x13.
d. Verify that the mobile station sends a Page Response Message with SERVICE_OPTION = 0x12 or 0x13.
e. Upon successful call setup, instruct the base station to send an OTAPA Request Message to the mobile station with START_STOP = ’1’.
f. Verify the mobile station sends an OTAPA Response Message to the base station within 750 ms with RESULT_CODE = ’00000000’ (Accepted – Operation Successful). If NAM_LOCK_IND = ’1’ in the OTAPA Response Message, perform the following:
1. Verify the RAND_OTAPA field is present in the OTAPA Response Message.
2. Instruct the base station to sends a Validation Request Message with BLOCK_ID = ’00000010’ (Validate SPASM) and a SPASM Parameter Block present to the mobile station.
3. Verify the mobile station sends a Validation Response Message to the base station within 750 ms, and with BLOCK_ID = ’00000010’ (Validate SPASM) and RESULT_CODE = ’00000000’ (Accepted – Operation Successful).
g. Instruct the base station to send a Protocol Capability Request Message to the mobile station.
h. Verify the mobile station sends a Protocol Capability Response Message to the base station with MOB_FIRM_REV, MOB_MODEL, BAND_MODE_CAP and all supported FEATURE_ID and FEATURE_P_REV as listed in ANNEX C.
If Service Programming Lock is supported, perform the following:
1. Instruct the base station to send a Validation Request Message with BLOCK_ID = ’00000000’ and SPC = SPCP.
2. Verify the mobile station sends a Validation Response Message within 750 ms, and with BLOCK_ID = ’00000000’ and RESULT_CODE = ’00000000’ (Accepted – Operation Successful).
3. Verify the base station sends a Validation Request Message with BLOCK_ID = ’00000001’ (Change SPC) and SPC = {a new SPC}.
14-14
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
4. Verify the mobile station sends a Validation Response Message within 750 ms, and with BLOCK_ID = ’00000001’ (Change SPC) and RESULT_CODE = ’00000000’ (Accepted – Operation Successful).
j. If the Electronic Key Exchange is not supported, go to step k; otherwise:
1. Instruct the base station to send an Mobile Station Key Request Message to the mobile station.
2. Verify the mobile station responds with the Mobile Station Key Response Message within 30 seconds, with RESULT_CODE = '00000000' (Accepted - Operation Successful).
3. Instruct the base station to send a Key Generation Request Message to the mobile station.
4. Verify the mobile station responds with the Key Generation Response Message within 30 seconds and the RESULT_CODE = '00000000' (Accepted - Operation Successful).
5. Verify the base station and the mobile station successfully perform SSD update procedures.
6. Verify the base station sends the Re-Authenticate Request Message and the mobile station responds with the Re-Authenticate Response Message.
7. At the base station verify Re-Authentication is successful.
8. The base station may enable Signaling Message Encryption and Voice Privacy.
k. Instruct the base station to send a Configuration Request Message with one or more of the following NAM Parameter Block Types:
Parameter Block Type BLOCK_ID
CDMA/Analog NAM ‘00000000’
Mobile Directory Number ‘00000001’
CDMA NAM ‘00000010’
IMSI_T ‘00000011’
24 25 26
27 28
29
l. Verify the mobile station sends a Configuration Response Message within 750ms including each requested BLOCK_ID and associated PARAM_DATA with corresponding RESULT_CODE.
m. Instruct the base station to send a Download Request Message with one or more of the following NAM Parameter Block Types and the corresponding PARAM_DATA:
14-15
C.S0044-0 v1.0
Parameter Block Type BLOCK_ID
CDMA/Analog NAM ‘00000000’
Mobile Directory Number ‘00000001’
CDMA NAM ‘00000010’
IMSI_T ‘00000011’
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
n. Verify that the mobile station sends a Download Response Message and that RESULT_CODE = '00000000' (Accepted- Operation Successful) within 750ms.
o. Instruct the base station to send a Commit Request Message to the mobile station.
p. Verify the mobile station sends a Commit Response Message to the base station within 10 seconds with the RESULT_CODE = '00000000' (Accepted- Operation Successful).
q. Instruct the base station to send an OTAPA Request Message to the mobile station with START_STOP = ’0’.
r. Verify the mobile station sends an OTAPA Response Message to the base station within 750 ms, and with RESULT_CODE = ’00000000’ (Accepted – Operation Successful) and NAM_LOCK_IND = ’0’.
s. Verify that the mobile station releases the call.
t. Verify the mobile station successfully stored the updated NAM information.
u. Originate a call from the mobile station and verify user traffic is present.
v. End the call.
w. Setup a mobile station originated call.
x. Repeat steps e through u with the mobile station already in the Conversation Substate.
14.6.5 Minimum Standard
The mobile station shall comply with steps d, f, h, l, n, p, r, and t. If supported the mobile station shall comply with steps i and l.
14.7 Call Origination during an OTAPA Download Session
14.7.1 Definition
This test verifies that the mobile station is able to originate a voice call during an OTAPA download session.
14.7.2 Traceability (see [14])
3.2.2 Network-Initiated Procedure
3.4 Termination of the Programming Procedure
3.5.1 Message Contents
4.2.2 Network-Initiated Procedure
14-16
C.S0044-0 v1.0
4.4 Termination of the Programming Procedure 1
2
3
4
5
a. 6
7
8 9
10 11
12 13
14 15 16
17
18 19 20
21 22 23
g. 24 25
26 27 28
29
30
31
32
33
4.5.1 Message Contents
14.7.3 Call Flow Example(s)
None
14.7.4 Method of Measurement
Connect the mobile station to the base station as shown in Figure A-3.
b. Confirm that the mobile station is programmed with a non-zero SPCp.
c. Initiate an OTAPA session from the base station by sending a General Page Message to the mobile station with the SERVICE_OPTION = 0x12 or 0x13.
d. Verify that the mobile station sends a Page Response Message with SERVICE_OPTION = 0x12 or 0x13.
e. Upon successful call setup, instruct the base station to send an OTAPA Request Message to the mobile station with START_STOP = ’1’.
f. Verify the mobile station sends an OTAPA Response Message to the base station within 750 ms with RESULT_CODE = ’00000000’ (Accepted – Operation Successful). If NAM_LOCK_IND = ’1’ in the OTAPA Response Message, perform the following:
1. Verify the RAND_OTAPA field is present in the OTAPA Response Message.
2. Instruct the base station to send a Validation Request Message with BLOCK_ID = ’00000010’ (Validate SPASM) and a SPASM Parameter Block present to the mobile station.
3. Verify the mobile station sends a Validation Response Message to the base station within 750 ms, and with BLOCK_ID = ’00000010’ (Validate SPASM) and RESULT_CODE = ’00000000’ (Accepted – Operation Successful).
Instruct the base station to send a Protocol Capability Request Message to the mobile station.
h. Verify the mobile station sends a Protocol Capability Response Message to the base station with MOB_FIRM_REV, MOB_MODEL, BAND_MODE_CAP and all supported FEATURE_ID and FEATURE_P_REV as listed in ANNEX CY.
i. Originate a voice call from the mobile station.
j. Verify user data in both directions.
k. End call at the mobile station.
14.7.5 Minimum Standard
The mobile station shall comply with steps d, f, h, and j.
14-17
C.S0044-0 v1.0
15 POSITION DETERMINATION TESTS 1
2 3 4 5
6
7
8 9
10
11
12
13
14
15
16
17
18
19
20 21 22 23 24
25 26
27 28 29
30 31 32
33
34 35 36
The position determination tests in this section apply to mobile stations and base stations that can operate in various modes including GPS (Global Positioning System), AFLT (Advanced Forward Link Trilateration), and Hybrid (GPS and AFLT). Note that for mobile stations that are capable of calculating their location based on AFLT, that capability is not verified in this test.
15.1 Position Determination Tests for GPS, AFLT and Hybrid
15.1.1 Definition
The purpose of this test is to determine the interoperability of mobile station and base station position determination sessions. This test requires that a network originated position determination session be triggered by a mobile station originated call.
15.1.2 Traceability (see [25])
3.2.1 Position Determination Data Message Processing
3.2.2 Point-to-point Procedures
3.2.4 Reverse Link Message Format
3.2.4.2 Response Element Response Type
Annex B Request/Response Element Types
15.1.3 15.1.3 Call Flow Example(s)
None
15.1.4 15.1.4 Method of Measurement
a. Configure 3 base stations available to the mobile station. Ensure connectivity of the base stations to a PDE. The base stations and the PDE shall be configured to allow a specific mobile station originated call type to trigger the PDE to start a position determination session with the mobile station (e.g. an emergency call; in the U.S. this would be a 9-1-1 call).
b. Allow the mobile to become idle on the base station with a dominant PN, with mobile CDMA receive power greater than -85 dBm and pilot Ec/Io greater than -12 dB.
c. If the mobile station and base station supports GPS position location, allow the mobile station to receive GPS signals each with a power level of at least -130 dBm/1MHz. The number of simulated GPS satellites shall be 4 or greater.
d. Setup a mobile station originated call using a dialed number or Service Option that triggers the PDE to start a position determination session (e.g. an emergency call; in the U.S. this would be a 9-1-1 call).
e. Verify the call completes.
f. Verify steps g through n. Note that the ordering of steps g through n does not represent a required ordering of call flow events during the test. In addition to the messages listed in steps g through n, there may be other position determination request elements
15-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
33 34 35 36 37 38 39 40
41 42 43
and response elements exchanged between the base station and mobile station during the test.
g. If the base station sends a position determination Data Burst Message with burst type ‘000101’ that includes a Position Determination Data Message with Request Mobile Station Information (REQ_TYPE = ‘0010’), verify the mobile station sends a position determination Data Burst Message with a burst type ‘000101’ that includes a Position Determination Data Message with Provide Mobile Station Information (RESP_TYPE = ‘0010’).
h. If the mobile station and base station supports GPS position determination and the base station has previously set GPSC_ID to ‘1’ in the Provide Base Station Capability, and if the mobile station has sent a position determination Data Burst Message with burst type ‘000101’ that includes a Position Determination Data Message with Request GPS Acquisition Assistance (REQ_TYPE = ‘0100’), verify the base station sends a position determination Data Burst Message with a burst type ‘000101’ that includes a Position Determination Data Message with Provide GPS Acquisition Assistance (RESP_TYPE = ‘0100’) or a Reject Message with REJ_REASON set to ‘001’.
i. If the mobile station and base station supports GPS position determination and the base station has previously set GPSC_ID to ‘1’ in the Provide Base Station Capability, and if the mobile station has sent a position determination Data Burst Message with burst type ‘000101’ that includes a Position Determination Data Message with Request GPS Sensitivity Assistance (REQ_TYPE = ‘0101’), verify the base station sends a position determination Data Burst Message with a burst type ‘000101’, that includes a Position Determination Data Message with Provide GPS Sensitivity Assistance (RESP_TYPE = ‘0101’) or a Reject Message with REJ_REASON set to ‘001’.
j. If the mobile station and base station supports GPS position determination and the base station has previously set GPSC_ID to ‘1’ in the Provide Base Station Capability, and if the mobile station has sent a position determination Data Burst Message with burst type ‘000101’ that includes a Position Determination Data Message with Request GPS Almanac (REQ_TYPE = ‘1000’), verify the base station sends a position determination Data Burst Message with a burst type ‘000101’ that includes a Position Determination Data Message with Provide GPS Almanac (RESP_TYPE = ‘1000’) or a Reject Message with REJ_REASON set to ‘001’.
k. If the mobile station and base station supports GPS position determination and the base station has previously set GPSC_ID to ‘1’ in the Provide Base Station Capability,, and if the mobile station has sent a position determination Data Burst Message with burst type ‘000101’ that includes a Position Determination Data Message with Request GPS Ephemeris (REQ_TYPE = ‘1001’), verify the base station sends a position determination Data Burst Message with a burst type ‘000101’, that includes a Position Determination Data Message with Provide GPS Ephemeris (RESP_TYPE = ‘1001’) or a Reject Message with REJ_REASON set to ‘001’.
l. If the mobile station and base station supports GPS position determination, and the mobile station is capable of calculating its position based on GPS measurements as indicated by LOC_CALC_CAP (Position Calculation Capability) field in the Provide
15-2
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
Mobile Station Information Response Element, and the base station has sent a position determination Data Burst Message with burst type ‘000101’ that includes a Position Determination Data Message with Request Location Response (REQ_TYPE = ‘0001’), verify the mobile station sends a position determination Data Burst Message with a burst type ‘000101’, that includes a Position Determination Data Message with Provide Location Response (RESP_TYPE = ‘0001‘).
m. If the mobile station and base station supports GPS position determination, and the base station has sent a position determination Data Burst Message with burst type ‘000101’ that includes a Position Determination Data Message with Request Pseudorange Measurement (REQ_TYPE = ‘0100’), verify the mobile station sends a position determination Data Burst Message with a burst type ‘000101’, that includes a Position Determination Data Message with Provide Pseudorange Measurement (RESP_TYPE = ‘0100‘).
n. If the base station supports AFLT position determination, and the base station has sent a position determination Data Burst Message with burst type ‘000101’ that includes a Position Determination Data Message with Request Pilot Phase Measurement (REQ_TYPE = ‘0101’), verify the mobile station sends a position determination Data Burst Message with a burst type ‘000101’, that includes a Position Determination Data Message with Provide Pilot Phase Measurement (RESP_TYPE = ‘0101‘).
15.1.5 Minimum Standard
The mobile station and base station shall comply with the requirements in the following steps:
For GPS position location the base station shall comply with steps h, i, j, k, l and the mobile station shall comply with steps g, l and m.
For AFLT position location the base station shall comply with step l and the mobile station shall comply with steps g and n.
For Hybrid position location the base station shall comply with steps h, i, j, and k, and the mobile station shall comply with steps g, l, m, and n.
15-3
C.S0044-0 v1.0
16 CONCURRENT SERVICES 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
16.1 Setup Mobile Station Originated Data Call while Voice Call or Teleservice Call is in Progress
16.1.1 Definition
This test verifies that, when a voice call is already in progress, a mobile station originated data call or teleservice call can be established successfully.
16.1.2 Traceability (see [4])
2.6.4.1.2.2.5 Waiting for Service Action Time Subfunction)
2.6.4.1.12 Processing the Service Configuration Record)
2.6.4.2 Traffic Channel Initialization Substate
2.6.4.3 Traffic Channel Substate
2.6.4.4 Release Substate
2.6.10 Call Control Processing
2.7.2.3.2.3 Flash with Information Message
2.7.2.3.2.32 Enhanced Origination Message
2.7.2.3.2.33 Extended Flash With Information Message
2.7.2.3.2.37 Call Cancel Message
2.7.2.3.2.29 Resource Release Request Message
2.7.2.3.2.30 Resource Release Request Mini Message
2.7.3.4 Mobile Station Reject Order
2.7.4.25 Capability Information
3.6.4.1.7 Response to Enhanced Origination Message
3.6.4.1.8 Processing Resource Release Request Message and Resource Release Request Mini Message
3.6.4.2 Traffic Channel Initialization Substate
3.6.4.3 Traffic Channel Substate
3.6.8 Call Control Processing
3.7.2.3.2.13 Extended System Parameters Message
3.7.2.3.2.30 ANSI-41 System Parameters Message
3.7.3.3.2.26 Analog Handoff Direction Message
3.7.3.3.2.20 Service Connect Message
16-1
C.S0044-0 v1.0
1
2
3
4
5
3.7.3.3.2.36 Universal Handoff Direction Message
3.7.3.3.2.43 Call Assignment Message
3.7.3.3.2.44 Extended Alert With Information Message
3.7.3.3.2.45 Extended Flash With Information Message
16.1.3 Call Flow Example(s)
Enhanced Origination Message(Data SOY, TAGY)
SCM / GHDM / UHDM (SCR += (Data SOY, CON_REFY)
BSMS
Traffic Traffic
TrafficTraffic
Call Assignment Message (RESPONSE_IND=1,
TAGY, CON_REFY)
SCM/ UHDM (CC_INFO_INCL=1,
RESPONSE_IND=1, TAGY SCR += (Data SOY, CON_REFY))
OR
MS initiates datacalll setup
Voice Call in Progress
Voice & DataCall in Progress
6
7
8
9
10 11
12
13 14
16.1.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-3.
b. Setup a voice call as described in Test and wait until the voice call is in progress.
c. Ensure retry delay for call origination (i.e. RETRY_DELAYs[001]) is currently not set for the data service option.
d. Initiate a packet data call (e.g. SO33) at the mobile station. Verify the following:
1. The mobile station sends an Enhanced Origination Message with the following fields set as follows:
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 2 3
4 5
6 7 8
e. Configure the base station to accept the call origination from the mobile station. Verify that base station follows one of the following two sequences of events to establish the data call:
1. The base station sends the call assignment prior to service option connection establishment as follows:
a. The base station sends a Call Assignment Message to the mobile station, prior to the expiration of the enhanced origination timer at the mobile station, with the following fields set as follows:
FIELD 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 11 12
13 14 15 16
17 18 19 20
21 22 23
b. Upon successful call assignment, service negotiation is initiated to establish the service option connection corresponding to this call assignment, as follows:
1. The service negotiation is terminated via sending a Service Connect Message, General Handoff Direction Message (containing a SCR), or Universal Handoff Direction Message (containing a SCR).
2. If the Service Connect Message or the Universal Handoff Direction Message is used to terminate the service negotiation, the call assignment included (CC_INFO_INCL) field is set to ‘0’ in these messages.
3. The service option connection is established with the same connection reference (CON_REF) as used in the corresponding Call Assignment Message.
16-3
C.S0044-0 v1.0
1 2 3
4
5 6
7 8 9
10 11
12
c. After the action time of the message used to establish the service option connection corresponding to this call, data call user traffic is exchanged successfully.
d. The voice call is not dropped.
2. The base station sends the call assignment as part of the service option connection establishment as follows:
a. The base station initiates service negotiation to establish the service option connection and assign the call. The service negotiation is terminated via sending a Service Connect Message or Universal Handoff Direction Message (containing a SCR) with the following fields set as follows:
FIELD 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 15 16
17
18
19 20
21 22
23
24 25
b. After the action time of the message used to establish the service option connection corresponding to this call, data call user traffic is exchanged successfully.
c. The voice call is not dropped.
f. Repeat steps b to e with the following modifications:
1. In step b, setup a teleservice call (e.g. SMS, Position Determination, etc.) requiring dedicated channels.
2. In step e, the teleservice call is not dropped after the establishment of the data call.
16.1.5 Minimum Standard
The mobile station and base station shall comply with the requirements in the following steps d, e and f.
16-4
C.S0044-0 v1.0
16.2 Setup Mobile Station terminated Data Call while Voice Call or Teleservice Call is in Progress
1 2
3
4 5
6
7
8
9
16.2.1 Definition
This test verifies that, when a voice call is already in progress, a mobile station terminated data call (for a dormant data session) or teleservice call can be established successfully.
16.2.2 Traceability
See 16.1.2.
16.2.3 Call Flow Example(s)
SCM / GHDM / UHDM (SCR += (Data SOY, CON_REFY)
BSMS
Traffic Traffic
TrafficTraffic
Call Assignment Message (RESPONSE_IND=0,Data SOY, CON_REFY)
SCM/ UHDM (CC_INFO_INCL=1,RESPONSE_IND=0,
SCR += (Data SOY, CON_REFY))
OR
Network initiatesdata calll setup(for a dormantdata session)
Voice Call in Progress
Voice & DataCall in Progress
10 11
12
13
14 15
16
16.2.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-3.
b. Setup a packet data call (e.g. SO33). Ensure that the data call transitions to the dormant state. Ensure that the dedicated traffic channels are released.
c. Setup a voice call and wait until the voice call is in progress.
16-5
C.S0044-0 v1.0
1 2 3
4 5
6 7
d. Trigger network-initiated transition to active state for the dormant packet data call. Verify that base station follows one of the following two sequence of events to establish the data call:
1. The base station sends the call assignment prior to service option connection establishment as follows:
a. The base station sends a Call Assignment Message to the mobile station with the following fields set as follows:
FIELD 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)
CON_REF Connection reference value for this call
8 9
10
11 12 13 14
15 16 17 18
19 20 21
22 23 24
25
26 27
28 29 30
b. Upon successful call assignment, service negotiation is initiated to establish the service option connection corresponding to this call assignment, as follows:
1. The service negotiation is terminated via sending a Service Connect Message, General Handoff Direction Message (containing a SCR), or Universal Handoff Direction Message (containing a SCR).
2. If the Service Connect Message or the Universal Handoff Direction Message is used to terminate the service negotiation, the call assignment included (CC_INFO_INCL) field is set to ‘0’ in these messages.
3. The service option connection is established with the same connection reference (CON_REF) as used in the corresponding Call Assignment Message.
c. After the action time of the message used to establish the service option connection corresponding to this call, data call user traffic is exchanged successfully.
d. The voice call is not dropped.
2. The base station sends the call assignment as part of the service option connection establishment as follows:
a. The base station initiates service negotiation to establish the service option connection and assign the call. The service negotiation is terminated via sending a Service Connect Message or Universal
16-6
C.S0044-0 v1.0
1 2
Handoff Direction Message (containing a SCR) with the following fields set as follows:
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 ‘0’ (base station initiated call assignment)
BYPASS_ALERT_ANSWER ‘1’ (since data call)
3 4 5
6
7
8 9
10 11
12
13
14 15
16
17 18
19
20
b. After the action time of the message used to establish the service option connection corresponding to this call, data call user traffic is exchanged successfully.
c. The voice call is not dropped .
e. Repeat steps b to d with the following modifications:
1. In step b, setup a teleservice call (e.g. SMS, Position Determination, etc.) requiring dedicated channels.
2. In step d, the teleservice call is not dropped after the establishment of the data call.
16.2.5 Minimum Standard
The mobile station and base station shall comply with the requirements in steps d and e.
16.3 Setup Mobile Station Originated Voice Call while Data Call or Teleservice Call is in Progress
16.3.1 Definition
This test verifies that, when a data call is already in progress, a mobile station originated voice call or teleservice call can be established successfully.
16.3.2 Traceability
See 16.1.2.
16-7
C.S0044-0 v1.0
1 16.3.3 Call Flow Example(s)
Enhanced Origination Message(Voice SOY, TAGY)
SCM / GHDM / UHDM (SCR += (Voice SOY, CON_REFY)
BSMS
Traffic Traffic
TrafficTraffic
Call Assignment Message (RESPONSE_IND=1,
TAGY, CON_REFY)
SCM / UHDM (CC_INFO_INCL=1,
RESPONSE_IND=1, TAGY SCR += (Voice SOY, CON_REFY))
OR
MS initiates voicecalll setup
Data Call in Progress
Voice & DataCall in Progress
2
3
4
5 6 7
8
9 10
16.3.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-3.
b. Setup a packet data call (e.g. SO33 as described in test case 13.2). Wait until the data call is in progress. Ensure sufficient traffic is exchanged to keep the data instance in active state.
c. Initiate a voice call at the mobile station. Verify the following:
1. The mobile station sends an Enhanced Origination Message with the following fields set as follows:
Field 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 3 4
5 6
7 8 9
10
d. Configure the base station to accept the call origination from the mobile station. Verify that base station follows one of the following two sequence of events to establish the voice call:
1. The base station sends the call assignment prior to service option connection establishment as follows:
a. The base station sends a Call Assignment Message to the mobile station, prior to the expiration of the enhanced origination timer at the mobile station, with the following fields set as follows:
Field 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
11
12 13 14
15 16 17 18
19 20 21 22
23 24 25
26 27 28
b. Upon successful call assignment, service negotiation is initiated to establish the service option connection corresponding to this call assignment, as follows:
1. The service negotiation is terminated via sending a Service Connect Message, General Handoff Direction Message (containing a SCR), or Universal Handoff Direction Message (containing a SCR).
2. If the Service Connect Message or the Universal Handoff Direction Message is used to terminate the service negotiation, the call assignment included (CC_INFO_INCL) field is set to ‘0’ in these messages.
3. The service option connection is established with the same connection reference (CON_REF) as used in the corresponding Call Assignment Message.
c. After the action time of the message used to establish the service option connection corresponding to this call, voice call user traffic is exchanged successfully.
16-9
C.S0044-0 v1.0
1
2 3
4 5 6 7 8
d. The data call is not dropped.
2. The base station sends the call assignment as part of the service option connection establishment as follows:
a. The base station initiates service negotiation to establish the service option connection and assign the call. The service negotiation is terminated via sending a Service Connect Message or Universal Handoff Direction Message (containing a SCR) with the following fields set as follows:
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
9
10 11 12
13
14
15 16
17 18
19
20
21
22
b. After the action time of the message used to establish the service option connection corresponding to this call, voice call user traffic is exchanged successfully.
c. The data call is not dropped
e. Repeat steps b to d with the following modifications:
1. In step b, setup a teleservice call (e.g. SMS, Position Determination, etc.) requiring dedicated channels.
2. In step d, the teleservice call is not dropped after the establishment of the data call.
16.3.5 Minimum Standard
The mobile station shall comply with the requirements in steps c, d and e.
The base station shall comply with the requirements in step d.
16-10
C.S0044-0 v1.0
16.4 Setup Mobile Station terminated Voice Call while Data Call or Teleservice Call is in Progress
1 2
3
4 5
6
7
8
16.4.1 Definition
This test verifies that, when a data call is already in progress, a mobile station terminated voice call or teleservice call can be established successfully.
16.4.2 Traceability
See 16.1.2.
16.4.3 Call Flow Example(s)
SCM / GHDM / UHDM (SCR += (Voice SOY, CON_REFY)
BSMS
Traffic Traffic
TrafficTraffic
Call Assignment Message (RESPONSE_IND=0,
Voice SOY, CON_REFY)
SCM/UHDM (CC_INFO_INCL=1,RESPONSE_IND=0,
SCR += (Voice SOY, CON_REFY))
OR
Network initiatesvoice call setup
Data Call in Progress
Voice & DataCall in Progress
AWIM / EAWIM
Connect Order
9 10
11
12
16.4.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-3.
16-11
C.S0044-0 v1.0
1 2 3
4 5
6 7
8 9
10 11
b. Setup a packet data call (e.g. SO33 a described in test case 13.2). Wait till the data call is in progress. Ensure sufficient traffic is exchanged to keep the data instance in active state.
c. Trigger a network-initiated voice call. Verify that base station follows one of the following two sequences of events to establish the voice call:
1. The base station sends the call assignment prior to service option connection establishment as follows:
a. The base station sends a Call Assignment Message to the mobile station with the following fields set as follows:
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)
CON_REF Connection reference value for this call
12 13 14
15 16 17 18
19 20 21 22
23 24 25
26 27 28 29
30
b. Upon successful call assignment, service negotiation is initiated to establish the service option connection corresponding to this call assignment, as follows:
1. The service negotiation is terminated via sending a Service Connect Message, General Handoff Direction Message (containing a SCR), or Universal Handoff Direction Message (containing a SCR).
2. If the Service Connect Message or the Universal Handoff Direction Message is used to terminate the service negotiation, the call assignment included (CC_INFO_INCL) field is set to ‘0’ in these messages.
3. The service option connection is established with the same connection reference (CON_REF) as used in the corresponding Call Assignment Message.
c. After the action time of the message used to establish the service option connection corresponding to this call, the mobile station plays an alert to indicate an incoming call. After answering the call from the mobile station, voice call user traffic is exchanged successfully.
d. The data call is not dropped.
16-12
C.S0044-0 v1.0
1 2
3 4 5 6 7
2. The base station sends the call assignment as part of the service option connection establishment as follows:
a. The base station initiates service negotiation to establish the service option connection and assign the call. The service negotiation is terminated via sending a Service Connect Message or Universal Handoff Direction Message (containing a SCR) with the following fields set as follows:
Field 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 ‘0’ (base station initiated call assignment)
BYPASS_ALERT_ANSWER ‘0’ (since voice call)
8
9 10 11 12
13
14
15 16
17 18
19
20
21
22
23
24 25
b. After the action time of the message used to establish the service option connection corresponding to this call, the mobile station plays an alert to indicate an incoming call. After answering the call from the mobile station, voice call user traffic is exchanged successfully.
c. The data call is not dropped .
d. Repeat steps b and c with the following modifications:
1. In step b, setup a teleservice call (e.g. SMS, Position Determination, etc.) requiring dedicated channels.
2. In step c, the teleservice call is not dropped after the establishment of the data call.
16.4.5 Minimum Standard
The mobile station and base station shall comply with the requirements in steps c and d.
16.5 Mobile Station Release of a Single Call While Voice and Data Calls are in Progress
16.5.1 Definition
This test verifies that, when both voice and data calls are in progress, mobile station can release one of the calls successfully and the other call continues uninterrupted.
16-13
C.S0044-0 v1.0
1
2
3
16.5.2 Traceability
See 16.1.2.
16.5.3 Call Flow Example(s)
SCM / GHDM / UHDM (SCR -= CON_REFY)
BSMS
Traffic Traffic
TrafficTraffic
MS initiatesrelease of one of
the calls
Voice & Data Calls in Progress
Remaining Call Continues
Service Request Message( SCR -= CON_REFY)
Resource Release Request Message(CON_REFY)
or
4
5
6
7 8 9
10
11 12
13 14 15 16
16.5.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-3.
b. Setup both a voice call and a packet data call (e.g. SO33). Wait till both the voice call and the data call are in progress. Ensure sufficient traffic is exchanged to keep the data instance in active state.
c. Initiate the release of the voice call at the mobile station. Verify the following:
1. The mobile station sends a Service Request Message or Resource Release Request (Mini) Message requesting the release of the voice call.
a. If the mobile station sends a Service Request Message, the service option connection record corresponding to the voice call is omitted from the Service Configuration information record included in this message.
16-14
C.S0044-0 v1.0
1 2
3
b. If the mobile station sends a Resource Release Request (Mini) Message, the following fields shall be set as follows:
Field Value
GATING_DISCONNECT_IND ‘0’ (release of a call requested)
CON_REF Connection reference corresponding to the voice call to be released
4 5 6 7
8 9
10
11 12 13
14
15 16 17
18
19
20
21
22 23
24
25
2. Upon receiving the Service Request Message or Resource Release Request (Mini) Message requesting the release of the voice call, the base station sends a Service Connect Message, General Handoff Direction Message (with a SCR), or Universal Handoff Direction Message (with a SCR) as follows:
a. The service option connection record corresponding to the voice call is omitted from the Service Configuration information record included in this message.
3. At the action time of the Service Connect Message, General Handoff Direction Message, or Universal Handoff Direction Message used to release the voice call, the voice traffic no longer flows.
4. The data call is not dropped.
d. Repeat steps a though c with the following exception: in step c, initiate the release of the data call at the mobile station. All the expected results are as in step c with the difference that the call being released is the data call.
16.5.5 Minimum Standard
The mobile station and base station shall comply with the requirements in step c and d.
16.6 Base Station Release of a Single Call While Voice and Data Calls are in Progress
16.6.1 Definition
This test verifies that, when both voice and data calls are in progress, base station can release one of the calls successfully and the other call continues uninterrupted.
16.6.2 Traceability
See 16.1.2.
16-15
C.S0044-0 v1.0
1 16.6.3 Call Flow Example(s)
SCM / GHDM / UHDM (SCR -= CON_REFY)
BSMS
Traffic Traffic
TrafficTraffic
Network initiatesrelease of one ofthe calls
Voice & Data Calls in Progress
Remaining Call Continues
2
3
4
5 6 7
8
9 10 11 12 13
14 15 16
17
16.6.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-3.
b. Setup both a voice call and a packet data call (e.g. SO33). Wait till both the voice call and the data call are in progress. Ensure sufficient traffic is exchanged to keep the data instance in active state.
c. Trigger a network-initiated release of the voice call. Verify the following:
1. The base station sends a Service Connect Message, General Handoff Direction Message (with a SCR), or Universal Handoff Direction Message (with a SCR), where the service option connection record corresponding to the voice call is omitted from the Service Configuration information record included in this message.
2. At the action time of the Service Connect Message, General Handoff Direction Message, or Universal Handoff Direction Message used to release the voice call, the voice traffic no longer flows.
3. The data call is not dropped.
16-16
C.S0044-0 v1.0
1 2 3
4
5
6
7
8 9
10
11
d. Repeat steps a though c with the following exception: in step c, initiate the release of the data call at the mobile station. All the expected results are as in step c with the difference that the call being released is the data call.
16.6.5 Minimum Standard
The mobile station and base station shall comply with the requirements in steps c and d.
16.7 Correct Handling of Call Control Signaling
16.7.1 Definition
This test verifies that, when one or more calls are in progress, mobile station initiated and network initiated call control signaling messages are handled correctly.
16.7.2 Traceability
See 16.1.2.
16-17
C.S0044-0 v1.0
1 16.7.3 Call Flow Example(s)
BSMS
Traffic Traffic
TrafficTraffic
Voice Call in Progress
FWIM /EFWIM (CON_REFINCL=0) /
EFWIM (CON_REFVOICE)
FWIM /EFWIM (CON_REFINCL=0) /
EFWIM (CON_REFVOICE)
Add data call:Voice & Data Calls in Progress
FWIM /EFWIM (CON_REFINCL=0) /
EFWIM (CON_REFVOICE)
FWIM /EFWIM (CON_REFINCL=0) /
EFWIM (CON_REFVOICE)
EFWIM (CON_REFVOICE)
EFWIM (CON_REFVOICE)
Release Data Call:Voice Call in Progress
FWIM /EFWIM (CON_REFINCL=0) /
EFWIM (CON_REFVOICE)
FWIM /EFWIM (CON_REFINCL=0) /
EFWIM (CON_REFVOICE)
If voice SOC listed first in SCR:
If data SOC listed first in SCR:
2 3
4
5
6
16.7.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-3.
b. Setup a voice call and wait until the voice call is in progress.
16-18
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 33 34 35
36
37 38
39 40 41
c. If applicable, trigger an action at the mobile station that will result in either a Flash With Information Message or Extended Flash With Information Message for a voice call being transmitted to the base station (Ex. Trigger an action that utilizes the Keypad Facility information record). Verify the following:
1. The mobile station sends a Flash With Information Message, an Extended Flash With Information Message with the CON_REF_INCL field set to ‘0’, or an Extended Flash With Information Message with the CON_REF field set to the connection reference corresponding to the voice call.
2. The information record is delivered correctly in the network.
d. If applicable, trigger an action at the network that will result in either a Flash With Information Message or Extended Flash With Information Message being transmitted to the mobile station (e.g. Trigger an action that utilizes the Display information record). Verify the following:
1. The base station sends a Flash With Information Message, an Extended Flash With Information Message with the CON_REF_INCL field set to ‘0’, or an Extended Flash With Information Message with the CON_REF field set to the connection reference corresponding to the voice call.
2. The information record is correctly handled in the mobile station.
e. Setup a mobile station originated or mobile station terminated packet data call (e.g. SO33). When the base station sends a Service Connect Message, General Handoff Direction Message, or Universal Handoff Direction Message to establish the service option connection corresponding to the data call, note whether the service option connection corresponding to the voice call or data call is listed as the first entry in the SCR.
f. If applicable, trigger an action at the mobile station that will result in either a Flash With Information Message or Extended Flash With Information Message for a voice call being transmitted to the base station (Ex. Trigger an action that utilizes the Keypad Facility information record). Verify the following:
1. If the service option connection corresponding to the voice call is listed as the first entry in the SCR:
a. The mobile station sends a Flash With Information Message, an Extended Flash With Information Message with the CON_REF_INCL field set to ‘0’, or an Extended Flash With Information Message with the CON_REF field set to the connection reference corresponding to the voice call.
b. The information record is delivered correctly in the network.
2. If the service option connection corresponding to the data call is listed as the first entry in the SCR:
a. The mobile station sends an (Extended) Flash With Information Message with the CON_REF field set to the connection reference corresponding to the voice call.
16-19
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 33 34
35 36 37 38
39
b. The information record is delivered correctly in the network.
g. If applicable, trigger an action at the network that will result in either a Flash With Information Message or Extended Flash With Information Message for a voice call being transmitted to the mobile station (Ex. Trigger an action that utilizes the Display information record). Verify the following:
1. If the service option connection corresponding to the voice call is listed as the first entry in the SCR:
a. The base station sends a Flash With Information Message, an Extended Flash With Information Message with the CON_REF_INCL field set to ‘0’, or an Extended Flash With Information Message with the CON_REF field set to the connection reference corresponding to the voice call.
b. The information record is correctly handled in the mobile station.
2. If the service option connection corresponding to the data call is listed as the first entry in the SCR:
a. The base station sends an Extended Flash With Information Message with the CON_REF field set to the connection reference corresponding to the voice call.
b. The information record is correctly handled in the mobile station.
h. Perform a mobile station initiated or base station initiated release of the data call. Wait till this operation is successful.
i. If applicable, trigger an action at the mobile station that will result in either a Flash With Information Message or Extended Flash With Information Message for a voice call being transmitted to the base station (Ex. Trigger an action that utilizes the Keypad Facility information record). Verify the following:
1. The mobile station sends a Flash With Information Message, an Extended Flash With Information Message with the CON_REF_INCL field set to ‘0’, or an Extended Flash With Information Message with the CON_REF field set to the connection reference corresponding to the voice call.
2. The information record is delivered correctly in the network.
j. If applicable, trigger an action at the network that will result in either a Flash With Information Message or Extended Flash With Information Message being transmitted to the mobile station for a voice call (Ex. Trigger an action that utilizes the Display information record). Verify the following:
1. The base station sends a Flash With Information Message, an Extended Flash With Information Message with the CON_REF_INCL field set to ‘0’, or an Extended Flash With Information Message with the CON_REF field set to the connection reference corresponding to the voice call.
2. The information record is correctly handled in the mobile station.
16-20
C.S0044-0 v1.0
1
2
3
4
5
6 7 8
9
10
11
16.7.5 Minimum Standard
The mobile station and base station shall comply with the requirements in steps c, d, f, g, i and j,.
The base station shall comply with the requirements in steps d, g, and j.
16.8 Analog Handoff Direction Message Terminates All Calls Except One
16.8.1 Definition
This test verifies that, when the base station directs the mobile station to perform a handoff from the CDMA system to an analog system by sending an Analog Handoff Direction Message, all calls except for the one indicated by the Analog Handoff Direction Message are terminated.
16.8.2 Traceability
See 16.1.2.
16.8.3 Call Flow Example(s)
BSMS
Traffic Traffic
Analog
Voice + Data calls in progress
Analog Handoff Direction Message(CON_REFX)MS terminates all calls
except one identified byCON_REFX
Single call continues
12
13
14
15 16 17
18 19 20
21 22
16.8.4 Method of Measurement
a. Connect the mobile station to the base station as shown in Figure A-5.
b. Setup a voice call and a packet data call (e.g. SO33). Wait till both calls are in progress. Note whether the service option connection corresponding to the voice call or data call is listed as the first entry in the Service Configuration Information Record.
c. Trigger the network to direct the mobile station to perform a handoff from the CDMA system to an analog system in a band class that the mobile station supports and to maintain the voice call. Verify the following:
1. The base station sends an Analog Handoff Direction Message to the mobile station, with the CON_REF_INCL/CON_REF fields set as follows:
16-21
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
a. If the service option connection corresponding to the voice call was listed as the first entry in the Service Configuration information record, then either the CON_REF_INCL field is set to ‘0’ or the CON_REF field is set to the connection reference of the voice call.
b. If the service option connection corresponding to the data call was listed as the first entry in the Service Configuration information record, then the CON_REF field is set to the connection reference of the voice call.
2. Upon receiving this message, the mobile station performs the following:
a. The mobile station terminates the data call and maintains the voice call.
b. The mobile station shall perform handoff to the analog system indicated by the Analog Handoff Direction Message.
16.8.5 Minimum Standard
The mobile station and base station shall comply with the requirements in step c.
16.9 Release A Mobile Station in Concurrent Calls with a Release A Base Station Hands off to Pre-Release A Base Station
16.9.1 Definition
This test verifies that, when a Release A mobile station currently in concurrent calls with a Release A base station is handed off to a Pre-Release A base station, only a single call is maintained and this call continues successfully.
16.9.2 Traceability
See 16.1.2.
16.9.3 Call Flow Example(s)
MS(Rel A)
Traffic
Voice + Data callsin progressGHDM/UHDM
(P_REV<7,SCR_new: Voice or Data)
Voice or datacall is releasedas instructed in
the new SCR
BS(Pre-Rel A)
Voice or Data call in progress
BS(Rel A)
25 26
16-22
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 33
34
35
16.9.4 Method of Measurement
a. Connect a MOB_P_REV 7 mobile station to base stations 1 and 2 as in Figure A-5. Configure base station 1 to support P_REV=7 and base station 2 to support P_REV<7.
b. Setup a mobile station originated or mobile station terminated voice call on base station 1.
c. Set up a mobile station originated or mobile station terminated packet data call (e.g. SO33). Wait till both voice and data calls are in progress. Ensure sufficient traffic is exchanged to keep the data instance in active state.
d. Trigger base station 1 to direct the mobile station to handoff to base station 2. Verify the following:
1. The base station shall send a General Handoff Direction Message or a Universal Handoff Direction Message to the mobile station, with the Service Configuration information record included and set as follows:
a. The service option connection corresponding to the call to be maintained is included and uses the same connection reference value (CON_REF) as currently used for this call.
b. The service option connection corresponding to the other call is omitted.
2. At the action time of this message, the mobile station shall release the call corresponding to the omitted service option connection and hands off to the base station 2.
3. The remaining call continues successfully in the base station 2.
16.9.5 Minimum Standard
The mobile station and base station shall comply with the requirements in the following steps: Step d.
16.10 Release A Mobile Station Hands off between Release A Base Station with Change in Concurrent Calls Support
16.10.1 Definition
This test verifies that, when a Release A mobile station currently in call with a Release A base station is handed off to another Release A base station, and where there is a change in Concurrent Calls support, calls are released/added/maintained successfully.
16.10.2 Traceability
See 16.1.2.
16-23
C.S0044-0 v1.0
1 16.10.3 Call Flow Example(s)
MS(Rel A)
Traffic
Voice and Data callin progress
GHDM/UHDM(P_REV=7,
SCR_new: Voice or Data,CS_SUPPORTED=0)
Voice or datacall is released
BS(Rel A:
CS_SUPPORTED=0)
Voice or Data call in progress
BS(Rel A:
CS_SUPPORTED=1)
UHDM(P_REV=7,
SCR_new: Voice and Data,CS_SUPPORTED=1,CC_INFO_INCL=1)
Voice and Data callin progress
Voice or datacall is added
2 3
4
5 6 7
8 9
10 11 12
13 14
15 16 17
18
16.10.4 Method of Measurement
a. Connect the MOB_P_REV=7 mobile station (Release A) to two P_REV=7 base stations (Release A) as shown in Figure A-5. Configure base station 1 to support Concurrent Services and base station 2 not to support Concurrent
b. Setup a mobile station originated or mobile station terminated voice call on base station 1.
c. Set up a mobile station originated or mobile station terminated packet data call (e.g. SO33). Wait till both voice and data calls are in progress. Ensure sufficient traffic is exchanged to keep the data instance in active state.
d. Trigger the base station to direct the mobile station to handoff from base station 1 to base station 2. Verify the following:
1. The base station shall send a General Handoff Direction Message or a Universal Handoff Direction Message to the mobile station, with the Service Configuration information record included and set as follows:
a. The CS_SUPPORTED field is set to ‘0’.
16-24
C.S0044-0 v1.0
1 2 3
4 5
6 7 8
9
10 11 12
13 14
15
b. The service option connection corresponding to the call to be maintained is included and uses the same connection reference value (CON_REF) as currently used for this call.
c. The service option connection corresponding to the other call is omitted.
2. At the action time of this message, the mobile station shall release the call corresponding to the omitted service option connection and hands off to the new Release A base station.
3. The remaining call continues successfully in the new Release A base station.
e. Trigger the base station to direct the mobile station to handoff from base station 2 to base station 1 that supports concurrent services and with an additional call added (voice or packet data call (e.g. SO33)). Verify the following:
1. The base station shall send a Universal Handoff Direction Message to the mobile station, with the following fields set as follows:
Field 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
CC_INFO_INCL ‘1’ (call assignment included)
NUM_CALLS_ASSIGN ‘00000001’ (single call assignment)
CON_REF Same value as connection reference for the new call
RESPONSE_IND ‘0’ (base station initiated call assignment)
16 17
18
19
2. At the action time of this message, the mobile station hands off to base station 1 and connects the new call.
3. The new call is connected successfully. The original call continues successfully.
16-25
C.S0044-0 v1.0
1
2
3
16.10.5 Minimum Standard
The mobile station and base station shall comply with the requirements in steps d and e
16-26
C.S0044-0 v1.0
17 EMERGENCY CALLS 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
17.1 Global Emergency Call Support When Mobile Station is in Idle State
17.1.1 Definition
This test verifies that the mobile station can originate a global emergency call during idle state and that the base station processes this as an emergency call.
17.1.2 Traceability (see [4])
2.7.1.3.2.4 Origination Message
17.1.3 Call Flow Example(s)
None
17.1.4 Method of Measurement
a. If the mobile station is capable of recognizing emergency number by analyzing the dialed digits, originate an emergency call from the mobile station by dialing an emergency number.
b. Verify the GLOBAL_EMERGENCY_CALL field is set to ‘1’ in the Origination Message and that the base station processes the origination as an emergency call.
c. End the call.
d. If the mobile station has a special interface to initiate an emergency call, originate an emergency call from the mobile station using this special interface.
e. Verify that the mobile station sets the GLOBAL_EMERGENCY_CALL field to ‘1’ in the Origination Message and that the base station processes the origination as an emergency call.
f. End the call.
17.1.5 Minimum Standard
The mobile station shall comply with the following steps as supported: Step b and e.
The base station shall comply with the following steps as supported: Step b and e.
17.2 Global Emergency Call Support When Mobile Station is in Voice Call.
17.2.1 Definition
This test verifies that the mobile station can originate a global emergency call while another voice call is in progress and that the base station processes this as an emergency call. This test is applicable only to mobile stations not capable of concurrent services.
17.2.2 Traceability (see [4])
2.7.1.3.2.4 Origination Message
17-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
33
34
2.7.2.3.2.32 Enhanced Origination Message
2.7.2.3.2.3 Flash With Information Message
2.7.2.3.2.33 Extended Flash With Information Message
17.2.3 Call Flow Example(s)
None
17.2.4 Method of Measurement
a. Connect the base station to the mobile station as shown in Figure A-3.
b. Originate a voice call from the mobile station. Verify audio in both directions.
c. If the mobile station is capable of recognizing emergency number by analyzing the dialed digits and the mobile station does not support concurrent service, originate an emergency call from the mobile station by dialing an emergency number (e.g. dialing 9-1-1 and press SEND).
d. Verify that the mobile station sends a Flash With Information Message or an Extended Flash With Information Message with the Global Emergency Call information record included or an Enhanced Origination Message with the GLOBAL_EMERGENCY_CALL field set to ‘1’ and that the base station processes the message as an emergency call.
e. End the calls.
f. Originate a voice call from the mobile station. Verify audio in both directions.
g. If the mobile station has a special interface to initiate an emergency call, originate an emergency call from the mobile station using this special interface.
h. Verify that the mobile station sends Flash With Information Message or Extended Flash With Information Message with the Global Emergency Call information record included and that the base station processes the origination as an emergency call.
i. End the calls.
17.2.5 Minimum Standard
The mobile station shall comply with the following steps as supported: Step d and h.
The base station shall comply with the following steps as supported: Step d and h.
17.3 Global Emergency Call Support When Mobile Station is in a Data Call
17.3.1 Definition
This test verifies that the mobile station can originate a global emergency call when a packet data call (Ex. SO33) is in progress and that the base station processes this as an emergency call. This test is applicable if both the base station and mobile station support concurrent services.
17.3.2 Traceability (see [4])
2.7.1.3.2.4 Origination Message
17-2
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
33
2.7.2.3.2.32 Enhanced Origination Message
2.7.2.3.2.3 Flash With Information Message
2.7.2.3.2.33 Extended Flash With Information Message
17.3.3 Call Flow Example(s)
None
17.3.4 Method of Measurement
a. Connect the base station to the mobile station as shown in Figure A-3.
b. Originate a data call from the mobile station.
c. If the mobile station is capable of recognizing emergency number by analyzing the dialed digits, then while the data call is up, originate an emergency call from the mobile station by dialing an emergency number (e.g. dialing 9-1-1 and press SEND).
d. Verify the mobile station sends an Enhanced Origination Message with the GLOBAL_EMERGENCY_CALL field set to ‘1’ and that the base station processes the origination as an emergency call.
e. End the calls.
f. Originate a data call from the mobile station.
g. If the mobile station has a special interface to initiate an emergency call, then while the data call us up, originate an emergency call from the mobile station using this special interface.
h. Verify the mobile station sends an Enhanced Origination Message with the GLOBAL_EMERGENCY_CALL field set to ‘1’ and that the base station processes the origination as an emergency call.
i. End the calls.
17.3.5 Minimum Standard
The mobile station shall comply with the following steps as supported: Step d and h.
The base station shall comply with the following steps as supported: Step d and h.
17.4 Emergency Call on a System that is Negative on PRL or SID List
17.4.1 Definition
This test verifies that the mobile station acquires a system that is ‘negative’ in its (Extended) Preferred Roaming List for an emergency call only.
17.4.2 Traceability (see [14])
3.5.5 Preferred Roaming List and Extended Preferred Roaming List
ANNEX C System Selection and Acquisition
17-3
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
33
34 35
17.4.3 Call Flow
None
17.4.4 Method of Measurement
a. Connect the mobile station and base station as shown in Figure A-3.
b. Program the base station’s SID into the PRL as a negative system.
c. Enable power-on registration. Disable all other forms of registration.
d. Power on the mobile station, and monitor it for a sufficient period of time to permit it to acquire the base station (typically 30 seconds).
e. Verify the mobile station does not attempt to access the base station.
f. Setup an emergency call from the mobile station (911 in the United States).
g. Verify the mobile station sends an Origination Message to the base station.
h. Verify the emergency call is routed to the PSAP or equivalent emulation unit.
i. End the emergency call from the mobile station.
17.4.5 Minimum Standard
The mobile station shall comply with step e and g.
17.5 Optional Emergency Calls
17.5.1 Definition
The requirements in these test cases are applicable regionally. For example, in the U.S., the FCC has certain requirements for the mobile station and the base station when an emergency 9-1-1 call is initiated. The purpose of this test is to determine the mobile station’s capability to initiate an emergency call under 3 different initial conditions: (1) No calls active or dormant, (2) data call is active and (3) data call in dormant mode.
17.5.2 Traceability
None
17.5.3 Call Flow Example(s)
None
17.5.4 Method of Measurement
a. Allow the mobile to become idle on the base station.
b. Originate emergency call from the mobile station and verify that the emergency call is connected. Release the emergency call.
c. Setup SO33 call. While SO33 call is active, originate emergency call from the mobile station and verify that the emergency call is connected. Release the emergency call.
d. Allow SO33 to go dormant.
e. While SO33 call is dormant, originate emergency call from the mobile station and verify that the emergency call is connected. Release the emergency call.
17-4
C.S0044-0 v1.0
1
2 3
17.5.5 Minimum Standard
The mobile station and base station shall comply with the requirements in steps b, c, e (according to applicable regional requirements).
17-5
C.S0044-0 v1.0
18 HRPD 1
2 3
4
5
6 7 8
9
10
11
12
13
14
15
16 17
18
19
20
21
22
23
24
25 26
27
28
29
30
31
32
33 34
35
For HRPD test cases described in chapter 18, the terms mobile station and base station represent the access terminal (AT) and access network (AN) respectively.
18.1 HRPD Acquisition and Idle Mode Operation
18.1.1 Definition
These tests will verify that AT acquires the HRPD system and performs idle monitoring of the HRPD control channel. These tests also verify that upon losing HRPD system during idle operation, AT tries to reacquire the HRPD system.
18.1.2 Traceability (see [24])
8.2.6.1.4.2.1 Initial Acquisition
18.1.3 Call Flow Example(s)
None
18.1.4 Method of measurement
a. Power up the AT.
b. Verify that the AT acquires HRPD system
c. Verify that after acquiring HRPD system, the AT performs idle monitoring of the control channel on HRPD system
d. Disable the forward link to the AT.
e. Verify that AT declares system lost
f. Enable the forward link and verify that the AT re-acquires EV-DO system.
18.1.5 Minimum Standard
The AT shall comply with c and f.
18.2 HRPD Session Establishment
18.2.1 Definition
This test verifies that during the HRPD session establishment, a Unicast AT Identifier (UATI) is assigned to the AT.
18.2.2 Traceability (see [24])
[see 24] 5 Session Layer, 6 Connection Layer, 8 MAC Layer
18.2.3 Call Flow Example(s)
None
18.2.4 Method of Measurement
a. Connect the AT to the access network as shown in figure A-3.
b. Ensure AT has not established HRPD session with access network (no UATI has been assigned by access network)
c. Cause the AT to acquire HRPD access network.
18-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
33
34
35 36
37
38
d. Verify the AT issues a UATIRequest Message.
e. Verify the access network issues a UATIAssignment Message. Record the UATI.
f. Verify the AT issues a UATIComplete Message.
g. Cause the AN to send an UpdateUATI Message to the AT.
h. Verify the AT sends a new UATIRequest Message.
i. Verify the access network issues a UATIAssignment Message. Record the UATI.
j. Verify the AT issues a UATIComplete Message.
18.2.5 Minimum Standard
Verify steps d, e, f, h, I and j.
18.3 HRPD Session Configuration and Management with Subnet change
18.3.1 Definition
This test verifies session configuration and management associated with a subnet change. If the AT moves to a new subnet and if the new subnet can retrieve the AT’s prior session configuration from the old subnet, new session negotiations are not needed. If the “Prior session attribute” is supported by the AN, it can use the previously negotiated set of session parameters.
18.3.2 Traceability (see [24])
5 Session Layer
18.3.3 Call Flow Example(s)
None
18.3.4 Method of measurement
a. Power up the AT and place it where it can receive good HRPD signal.
b. Verify that AT acquires and goes to idle state. Verify that AT requests a UATI and AN assigns it, as specified in the “address management” test case described in this section.
c. Verify that after UATI assignment, AT opens a new HRPD connection and starts session negotiation using sets of ConfigRequest/ConfigResponse messages.
d. After a HRPD session is opened successfully, move the AT to another subnet where prior session attribute is accepted. Verify that in this subnet, AT sends a ConfigRequest with the current session token and AN sends back a ConfigResponse. Verify that AT does not go through a new set of session negotiations after receiving the ConfigResponse from the AN.
18.3.5 Minimum Standard
The mobile station shall comply with steps b and c.
18.4 AT Color Code and UATI24
18.4.1 Definition
This test verifies that the AT is assigned a valid Color Code and UATI024 during an HRPD session establishment.
18.4.2 Traceability (see [24])
[see 24] 5 Session Layer, 6 Connection Layer, 8 MAC Layer
18-2
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 33 34
35
36 37
38 39
18.4.3 Call Flow Example(s)
None
18.4.4 Method of Measurement
a. Connect the AT to the access network as shown in Figure A-3.
b. Cause the access network to issue a new UATI to the AT.
c. Verify a valid Color Code (UATIColorCode) and UATI24 (UATI024) are assigned to the AT in the UATIAssignment Message. Record the Color Code and UATI024.
18.4.5 Minimum Standard
Verify the AT complies with step c.
18.5 HRPD Connection Setup
18.5.1 Definition
This test verifies that when the HRPD connection is idle (session active and PPP dormant), an AT initiated ping and AN initiated ping shall be successful. This test will verify that AT can setup a HRPD packet data connection when its state is idle.
18.5.2 Traceability (see [24])
[see 24] 5 Session Layer, 6 Connection Layer, 8 MAC Layer
18.5.3 Call Flow Example(s)
None
18.5.4 Method of Measurement
a. Connect the AT to the access network as shown in Figure A-3.
b. Power up the AT.
c. Verify that the AT connection is idle on HRPD system
d. Issue a “ping” command from the AT to a remote host to setup an HRPD AT originated connection.
e. Verify AT sends a Connection Request Message to access network and that access network sends a ACAck and a TrafficChannelAssignment Message to the AT. Verify AT sends a TrafficChannelCompleteMessage and that connection enters active state.
f. Verify the AT receives a “ping” response from the remote host
g. Issue a “ping” command from the remote host to the AT using the IP address assigned to the AT.
h. Verify the remote host receives a “ping” response from the AT.
i. Let the AT connection go idle. Start FTP/ping from the AT and verify that the AT connection goes to active state. Also verify that the data can be transferred in both directions over HRPD system
j. Wait for connection AT to go idle.
k. Issue a “ping” command from the remote host to the AT using the IP address assigned to the AT.
l. Verify the AT setups the HRPD connection and the remote host receives a “ping” response from the AT.
18-3
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
33 34 35
36
37
18.5.5 Minimum Standard
AT and AN shall comply with steps e, f, h, i and l.
18.6 Test Application Protocol
18.6.1 Definition
This test verifies HRPD FTAP (Forward Test Application Protocol) and HRPD RTAP (Reverse Test Application Protocol). The statistics provided by the FTAP and RTAP tests can be used to compute Packet Error Rate performance.
18.6.2 Traceability:
[see 24] 2.5 Signaling Network Protocol, 5 Session Layer, 6 Connection Layer, 7 Security Layer, 8 MAC Layer
TIA/EIA/IS-890 - Test Application Specification (TAS) for High Rate Packet
See [27]
18.6.3 Call Flow Example(s)
None
18.6.4 Method of Measurement
a. Connect the AT to the access network as shown in Figure A-3.
b. Initiate an HRPD FTAP (Forward Test Application Protocol) test with Loop Back mode enabled.
c. Record the statistics provided.
d. Repeat steps c through d with ACK Channel Bit Fixed mode enabled.
e. Repeat steps c through d with DRC Value Fixed mode enabled.
f. Repeat steps c through d with DRC Cover Fixed mode enabled.
g. Initiate an HRPD RTAP (Reverse Test Application Protocol) test with RTAP Test Packet mode enabled.
h. Record the statistics provided.
i. Repeat steps h through I with Configured Packet Rate mode enabled.
18.6.5 Minimum Standard
Verify the proper FTAP and RTAP test shall execute with statistics returned as indicated in steps c and h.
18.7 Access Network Packet Data Inactivity Timer
18.7.1 Definition
This test is only required for access networks that have an access network packet
data inactivity timer. This test verifies the access network releases the traffic channel after expiration of the access network packet data inactivity timer. The test verifies the link layer connection can be re-activated from idle state.
18.7.2 Traceability:
[24] 5 Session Layer, 6 Connection Layer, 7 Security Layer, 8 MAC Layer
18-4
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
33 34
35
36
37
[26] 2.3.1.2 Termination
18.7.3 Call Flow Example(s)
None
18.7.4 Method of Measurement
a. Connect the AT to the access network as shown in Figure A-3.
b. Set the PCF PPP inactivity timer to 20 seconds.
c. Setup an HRPD AT originated connection.
d. Initiate a Telnet session to a remote host.
e. Record the IP address assigned to the AT.
f. Exit the Telnet session.
g. Wait for the access network packet data inactivity timer to expire. Verify access network sends a ConnectionCloseMessage with CloseReason = 0 (normal Close). Verify the AT sends a ConnectionCloseMessage with CloseReason = 1 (Close Reply) and connection goes to idle state.
h. Setup an HRPD AT originated connection.
i. Initiate a Telnet session to a remote host.
j. Record the IP address assigned to the AT.
k. Wait for the PCF PPP inactivity timer to expire. Verify the AT connection goes to idle state.
l. Setup an HRPD AN originated connection by issuing a “ping” command from a remote host to the AT using the IP address assigned to the AT.
m. Verify the host receives a “ping” response from the AT.
n. Wait for the PCF PPP inactivity timer to expire. Verify the AT connection goes to idle state.
o. Setup an HRPD AT originated connection by issuing a “ping” command from the AT to a remote host.
p. Verify the AT receives a “ping” response from the remote host.
18.7.5 Minimum Standard
AN and AT shall comply with steps g, k, m, n, p.
18.8 Forward File Transfer
18.8.1 Definition
This test verifies HRPD forward link file transfer when in active HRPD mode. This test case may be performed using Simple IP and/or Mobile IP.
18.8.2 Traceability:
[24] 5 Session Layer, 6 Connection Layer, 8 MAC Layer
(See [26]) 3 HRPD IOS Call Flows
18-5
C.S0044-0 v1.0
18.8.3 Call Flow Example(s) 1
2
3
4
5 6
7
8 9
10 11
12
13
14
15
8.8.416
None
18.8.4 Method of Measurement
a. Connect the AT to the access network as shown in Figure A-3.
b. At the remote host prepare the appropriate file, corresponding to the rate that will be tested (Note: this will guarantee sufficient transfer time).
c. Setup an AT originated HRPD connection.
d. Adjust the RF quality in such a way that the AT request mostly the DRC value corresponding to the rate that will be tested.
e. Setup an FTP session with a remote host and start a file transfer in the forward link by using a binary “get” command from the AT.
f. Verify the data transfer completes successfully.
g. After the file transfer is completed successfully, end the FTP session.
h. This test case may be repeated for supported DRC values below.
Table 1 -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
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
18.8.5 Minimum Standard
The AT shall comply with step f for all test cases.
18.9 Reverse File Transfer
18.9.1 Definition
This test verifies HRPD reverse link file transfer when in active HRPD mode. This test case may be performed using Simple IP or Mobile IP.
18.9.2 Traceability:
[24.] 5 Session Layer, 6 Connection Layer, 8 MAC Layer
[26] 3 HRPD IOS Call Flows
18.9.3 Call Flow Example(s)
None
18.9.4 Method of Measurement
a. Connect the AT to the access network as shown in Figure A-3.
b. Cause the AT to acquire the access network. Setup an HRPD AT originated connection.
c. Setup a FTP session with a remote host and start a file transfer in the reverse link by using a binary “put” command from the AT.
d. Verify the file transfer completes.
e. After the file transfer is completed, end the FTP session.
18.9.5 Minimum Standard
The mobile station shall comply with step d.
18.10 Bidirectional File Transfer
18.10.1 Definition
This test verifies bi-directional file transfer when in active HRPD mode.
18.10.2 Traceability:
[24] 5 Session Layer, 6 Connection Layer, 8 MAC Layer
[26] 3 HRPD IOS Call Flows
18-7
C.S0044-0 v1.0
18.10.3 Call Flow Example(s) 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
a. 28 29 30
b. 31
c. 32
d. 33 34
e. 35 36 37
f. 38
g. 39
None
18.10.4 Method of Measurement
a. Connect the AT to the access network as shown in Figure A-3.
b. Cause the AT to acquire the access network. Setup an HRPD AT originated connection.
c. At the remote host prepare the appropriate file, corresponding to the rate that will be tested (Note: this will guarantee sufficient transfer time).
d. Setup a FTP session ( 1) with a remote host and start a file transfer in the reverse link by using a binary “put” command from the AT.
e. Setup another FTP session ( 2) and transfer a file from the Remote Host to the AT using the binary “get” command while the transfer in the reverse direction is still proceeding.
f. Verify both file transfers complete.
g. After the file transfer, end both FTP sessions.
18.10.5 Minimum Standard
The AT shall comply with step f.
18.11 RLP Operation in Severely Degraded Channel
18.11.1 Definition
This test verifies RLP Operation in Severely Degraded Channel when in active HRPD mode. This test is intended to exercise RLP resets due to long erasure bursts.
18.11.2 Traceability:
[24] 5 Session Layer, 6 Connection Layer, 8 MAC Layer
[26] 3 HRPD IOS Call Flows
18.11.3 Call Flow Example(s)
None
18.11.4 Method of Measurement
Connect the AT to the access network as shown in [Figure A-1]. At the remote host prepare the appropriate file, corresponding to the rate that will be tested (Note: this will guarantee sufficient transfer time). Refer to files in Data Services Annex D.
Set the channel simulator to one Ray 3 km/hr Rayleigh fading on the forward link.
Cause the AT to acquire the access network. Setup an AT originated HRPD call.
Setup a FTP session with a remote host and start a file transfer in the forward link by using a binary “get” command from the AT.
Verify AT sends a valid DRC value in the Data Rate Control Channel to the access network and that access network provides AT with requested forward link coding and modulating parameters.
Ensure data transfer rate is not limited by network limitations.
Verify the data transfer is successful.
18-8
C.S0044-0 v1.0
h. 1
2
3
4
5
6 7
8
9
10
11
12
13
14
15
16
17
a. 18 19
8.12.420
After the file transfer is completed, end the FTP session.
18.11.5 Minimum Standard
The AT shall comply with steps e and g.
18.12 Softer and Soft Handoff – Active HRPD Mode
18.12.1 Definition
This test verifies soft handoff when AT is in active HRPD mode with file transfer in forward and reverse directions.
18.12.2 Traceability:
[see 24]
5 Session Layer,
6 Connection Layer;
6.6.7.2 SetManagementSameChannelParameters Attribute
8 MAC Layer
[26] 3 HRPD IOS Call Flows
18.12.3 Call Flow Example(s)
None
18.12.4 Method of Measurement
Connect the AT to the access network as shown in Figure A-5 and set the forward link parameters as shown in. Configure all three sectors with the same channel.
Table 1 -1 Forward Link Parameters for Soft(er) Handoff Tests
Parameter Units AN BTS 1 Sector α
AN BTS 1 Sector β
AN BTS 2 Sector γ
Forward Link Power Ior
dBm/1.23MHz -70 -85 -85
b. 21 22
c. 23
d. 24 25 26
e. 27 28
f. 29 30
g. 31
Configure each sector to send the Sector Parameters Message with Neighbor List including the other sectors’ Pilot PNs.
Setup an HRPD AT originated connection on BTS 1, sector α.
Setup an FTP session with a remote host and start a file transfer in the forward link by using a binary “get” command from the AT. Ensure the file size is appropriate to complete the test case before transfer is over.
Verify that BTS 1/sector α is in the pilot active set and that BTS 1/sector ß and BTS 2/sector α are in the pilot neighbor set.
Raise the level of BTS 1/sector ß in steps of 1 dB with a dwell time of 5 seconds after each step until the BTS 1/sector ß is in the pilot candidate set.
Verify AT sends a RouteUpdate Message to report pilots.
18-9
C.S0044-0 v1.0
h. 1 2 3 4
i. 5 6
j. 7
k. 8 9
10
l. 11 12 13
m. 14 15 16 17
n. 18
o. 19
p. 20
q. 21 22 23
r. 24
25
26
27
28
29 30
31
32
33
34
35
36
37
38 39
Verify the access network send s a TrafficChannelAssignment Message with Num Pilots=2 then verify both BTS 1 sector α and sector ß are in the pilot active set. Verify that SofterHandoff bit in the TrafficChannelAssignment message is set to 1 for the pilots in the softer handoff.
Raise the level of BTS 2/sector α in steps of 1 dB with a dwell time of 5 seconds after each step until the BTS 2/sector α is in the pilot candidate set.
Verify AT sends a RouteUpdate Message to report pilots.
Verify the access network send s a Traffic Channel Assignment Message with Num Pilots=3 then verify BTS 1/sectors α and ß and BTS 2/sector α are in the pilot active set.
Decrease the level of BTS 1/sector α in steps of 1 dB with a dwell time of 5 seconds after each step until access network sends a Traffic Channel Assignment Message with Num Pilots=2, then verify the BTS 1/sector α is in the pilot neighbor set.
Decrease the level of BTS 1/sector ß in steps of 1 dB with a dwell time of 5 seconds after each step until access network sends a Traffic Channel Assignment Message with Num Pilots=1, then verify the BTS 1/sector ß is in the pilot neighbor set. Verify file transfer is still on and the call in on BTS 2/sector α.
Verify the file transfer completes.
End the call.
Repeat steps a through c.
Setup an FTP session with a remote host and start a file transfer in the reverse link by using a binary “put” command from the AT. Ensure the file size is appropriate to complete the test case before transfer is over.
Repeat steps e through p.
18.12.5 Minimum Standard
The AT and AN shall comply with steps e, g, h, j, k, l, m and n for all test cases.
18.13 HRPD Control Channel Monitoring and Overhead Message Updates
18.13.1 Definition
This test will verify that the AT can successfully receive and update control channel messages. AN can set various periodicities (within the allowed range, as defined in [24]) for these messages.
18.13.2 Traceability
[24] 6.4 Default Idle State Protocol
18.13.3 Call Flow Example(s)
None
18.13.4 Method of measurement
a. Power up the AT.
b. Configure the AT to operate in non-slotted (sleep disabled) mode
c. Monitor the periodicity of Sync message, Quickconfig message, SectorParameter message, and AccessParameter message
18-10
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
33
34
35 36
d. Check the AN configuration for periodicity of these messages. Verify that received messages have same periodicity as configured at the AN
e. Configure the AT to operate in slotted (sleep enabled) mode
f. Verify that AT receives and updates the overhead messages (QuickConfig and SectorParameter messages) and performs the supervision of these messages according to the procedures in overhead message protocol specified in [24].
18.13.5 Minimum Standard
The AT shall comply with steps d and f.
18.14 Control Channel Rate
18.14.1 Definition
This test verifies correct monitoring of Control Channel by AT.
18.14.2 Traceability: [See 24]
8.2 – Default Control Channel MAC Protocol
8.2.6.1.4.1.1 – General Requirements
9.3 – Access Network Requirements
9.3.1.3.1 – Forward Channel Structure
9.3.1.3.2.2 – Forward MAC Channel
9.3.1.3.2.4 – Control Channel
18.14.3 Call Flow Example(s)
None
18.14.4 Method of Measurement
a. Configure Control Channel Rate to 38400 bps on access network.
b. Connect the AT to the access network as shown in Figure A-3
c. Verify AT is able to monitor SyncChannel Message, QuickConfig Message, Sector Parameters Message and AccessParameters Message.
d. Instruct AT to request a UATI from access network and Setup an HRPD AT originated call. Issue a “ping” from AT.
e. Release the call.
f. Configure Control Channel Rate to 76800 bps on access network and repeat steps b through e.
18.14.5 Minimum Standard
The AT shall comply with step c for all test cases.
18.15 AT Initiated HRPD ConnectionDeny
18.15.1 Definition
This test verifies that if there is no traffic channel available, the access network will send a ConnectionDeny Message to AT.
18-11
C.S0044-0 v1.0
18.15.2 Traceability: [See 24] 1
2
3
4
5
6
7
8
9 10
11
12 13
14
15
16
17
18
19 20 21 22 23 24 25 26
27
28
29
30
31
32
33
34
c. 35
d. 36 37 38
6.4 – Default Idle State Protocol
6.4.6.1.6.1 – AT Requirements
6.4.6.1.6.2 – Access Network Requirements
6.4.6.2.3 – ConnectionDeny
18.15.3 Call Flow Example(s)
None
18.15.4 Method of Measurement
a. Configure AN to respond with a ConnectionDeny with reason “Network Busy” to a ConnectionAttempt message.
b. Attempt to setup an AT originated HRPD connection.
c. Verify the access network sends a Connection Deny Message with Deny Reason 1 = Network Busy.
d. Verify the AT enters the AT Monitor(Idle) State until it attempts to setup a new call
18.15.5 Minimum Standard
The AT and AN shall comply with steps c and d.
18.16 HRPD Keep Alive Mechanism
18.16.1 Definition
This test verifies the proper functionality of keep alive mechanism. The access terminal and the access network shall monitor the traffic flowing on the Forward Channel and Reverse Channel, respectively, directed to or from the access terminal. If either the access terminal or the access network detects a period of inactivity of at least TSMPClose/NSMPKeepAlive minutes, it may send a KeepAliveRequest message. The recipient of the message shall respond by sending the KeepAliveResponse message. When a KeepAliveResponse message is received, the access terminal shall not send another KeepAliveRequest message for at least TSMPClose/NSMPKeepAlive minutes.
18.16.2 Traceability
[24] 5.2.6.1.6.1 Keep Alive Functions
See [24] Table 5.2.7.1and Table 5.2.8
18.16.3 Call Flow Example(s)
None
18.16.4 Method of measurement
a. Power up the AT and place it where it can receive good HRPD signal
b. Verify that AT acquires and goes to idle state.
Terminate all data activities to and from the AT for a period greater than see [24]
Verify that after an inactivity period of TSMPClose / NSMPKeepAlive minutes if either AT or AN sends a KeepAliveRequest that the recipient of the KeepAliveRequest message responds with a KeepAliveResponse message.
18-12
C.S0044-0 v1.0
e. Verify that upon receipt of KeepAliveResponse message, the AT does not send another KeepAliveRequest message for at least another T
1 2
f. 3 4
5 6
7
8
9
10
11 12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28 29
30 31
32 33
34 35
36
SMPClose / NSMPKeepAlive minutes
Verify that if AT does not receive any response from the AN for a period of see [24] minutes, it terminates the session
g. Verify that if see [24] is set to zero, the keep alive mechanism between AT and AN is disabled
18.16.5 Minimum Standard
The AT and the AN shall comply with step b, d, e, f and g.
18.17 Intra-band HRPD-HRPD System Re-Selection (Connected State)
18.17.1 Definition
This test verifies the AT performs HRPD system reselection between different channels in the same band class.
18.17.2 Traceability:
[See (SEE [24]) ]
6.2 – Default Air Link Management Protocol
6.2.6.1.2 – Initialization State
6.4 – Default Idle State Protocol
6.4.6.1.6 – Connection Setup State
6.5 – Default Connection State Protocol
[See 26]
3.7.1 – PCF-PCF Dormant Handoff with Successful Retrieval of HRPD Session Information
18.17.3 Call Flow Example(s)
None
18.17.4 Method of Measurement
a. Connect the AT to AN 1 and AN 2 as shown in Figure A-5.
b. Configure AN 1 with different channel than AN 2
c. Configure AN 2 not to be in the neighbor list of AN 1
d. Cause the AT to acquire access network AN 1. Setup an HRPD AT originated connection.
e. Setup a FTP session with a remote host and start a file transfer in the forward link by using a binary “get” command from the AT.
f. Before file transfer is complete increase forward link attenuation on AN 1 until AT can’t monitor AN 1 signal.
g. Verify AT declares system lost and acquires AN 2 and reconnects HRPD connection. Verify file transfer continues after selection AN 2.
h. Release connection.
18-13
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
33
34
i. Repeat steps b through g for file transfer in the reverse link by using a binary “put” command from the AT instead of “get” (step e).
18.17.5 Minimum Standard
The AT shall comply with step g for all test cases.
18.18 Inter-band HRPD-HRPD System Re-Selection (Connected State)
18.18.1 Definition
This test verifies the AT performs HRPD system reselection between channels from different band classes.
18.18.2 Traceability:
[See (SEE [24]) ]
6.2 – Default Air Link Management Protocol
6.2.6.1.2 – Initialization State
6.4 – Default Idle State Protocol
6.4.6.1.6 – Connection Setup State
6.5 – Default Connection State Protocol
[See 26]
3.7.1 – PCF-PCF Dormant Handoff with Successful Retrieval of HRPD Session Information
18.18.3 Call Flow Example(s)
None
18.18.4 Method of Measurement
a. Connect the AT to AN 1 and AN 2 as shown in Figure A-5.
b. Configure AN 1 to operate in a different band class than AN 2.
c. Cause the AT to acquire AN 1. Setup an HRPD AT originated connection.
d. Setup a FTP session with a remote host and start a file transfer in the forward link by using a binary “get” command from the AT.
e. Before file transfer is complete increase forward link attenuation on AN 1 until AT can’t monitor AN 1 signal.
f. Verify AT declares system lost and acquires AN 2 and reconnects HRPD call. Verify file transfer continues after selection AN 2.
g. Release connection.
h. Repeat steps b through g for file transfer in the reverse link by using a binary “put” command from the AT instead of “get” (step e).
18.18.5 Minimum Standard
The AT shall comply with step f for all test cases.
18-14
C.S0044-0 v1.0
18.19 Intra-band HRPD-HRPD System Re-selection (Idle State) 1
2
3 4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22 23
24 25
26
27
28
29
30
31 32
33
34
35
18.19.1 Definition
This test verifies the AT performs HRPD reselection, while in idle state, between channels in the same band class.
18.19.2 Traceability
[See (SEE [24]) ]
6.2 – Default Air Link Management Protocol
6.2.6.1.2 – Initialization State
6.4 – Default Idle State Protocol
6.4.6.1.6 – Connection Setup State
6.5 – Default Connection State Protocol
[See 26]
3.7.1 – PCF-PCF Dormant Handoff with Successful Retrieval of HRPD Session Information
18.19.3 Call Flow Example(s)
None
18.19.4 Method of Measurement
a. Connect the AT to AN 1 and AN 2 as shown in Figure A-5.
b. Configure AN 1 with different channel than AN 2.
c. Configure AN 2 not to be in the neighbor list of AN 1.
d. Cause the AT to acquire AN 1. Setup an HRPD AT originated call.
e. Verify that the AT connection is idle.
f. Force the AT to handoff from AN 1 to AN 2 (i.e. by increasing forward link attenuation on AN 1 until AT can’t monitor AN 1 RF signal).
g. Verify AT declares system lost and acquires AN 2. Issue a “ping” from AT and verify an HRPD connection is successfully setup.
h. Issue a “ping” from remote host to AT IP address and verify there is a response.
18.19.5 Minimum Standard
The AT shall comply with steps e, g and h.
18.20 Inter-band HRPD-HRPD System Re-selection (Idle State)
18.20.1 Definition
This test verifies the AT, in Simple IP mode, performs HRPD reselection, while in idle state, between channels from different band classes.
18.20.2 Traceability
[See (SEE [24]) ]
6.2 – Default Air Link Management Protocol
18-15
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
33 34
6.2.6.1.2 – Initialization State
6.4 – Default Idle State Protocol
6.4.6.1.6 – Connection Setup State
6.5 – Default Connection State Protocol
[See 26]
3.7.1 – PCF-PCF Dormant Handoff with Successful Retrieval of HRPD Session Information
18.20.3 Call Flow Example(s)
None
18.20.4 Method of Measurement
a. Connect the AT to AN 1 and AN 2 as shown in Figure A-5.
b. Configure AN 1 to operate in a different band class than AN 2.
c. Cause the AT to acquire AN 1.
d. Verify that AT connection is idle.
e. Force the AT to handoff from AN 1 to AN 2 (i.e. by increasing forward link attenuation on access network HRPD 1 until AT can’t monitor HRPD 1 RF signal).
f. Verify AT declares system lost and acquires AN 2. Issue a “ping” from AT and verify HRPD call is successfully originated.
g. Issue a “ping” from remote host to AT IP address and verify there is a response.
18.20.5 Minimum Standard
The AT shall comply with steps d, f and g.
18.21 HRPD Terminal Authentication Failure
18.21.1 Definition
This test verifies that when the User-name or the Chap-password is incorrectly set at the AT the network authentication fails.
18.21.2 Traceability:
[See TIA-878]
3.1.1 – AT originates HRPD Session – Successful Terminal Authentication
3.1.2 – AT originates HRPD Session – Unsuccessful Terminal Authentication
18.21.3 Call Flow Example(s)
None
18.21.4 Method of measurement
a. Configure the CHAP authentication to be enabled in the network.
b. Provision an incorrect User-name but a correct Chap-password in the AT for CHAP authentication.
18-16
C.S0044-0 v1.0
c. Verify that the AT has a closed HRPD session 1
2
3 4
5 6
7
8 9
10
11
12 13
14
The AT and the AN shall comply with step c, e, g and i for all test cases.. 15
16
17
18 19
20
21
22
23
d. Power up the AT and place it where it can receive good HRPD signal
e. Verify that AT successfully completes the session negotiation and negotiates the AN stream as part of this procedure
f. If AN performs authentication immediately after the session negotiation, verify that AN sends the CHAP Challenge message and initiates the network authentication
g. Verify that the network authentication fails and the AN closes the HRPD session.
h. If AN performs authentication just before the data call setup(s), set up a data call on the HRPD system and verify that AN sends the CHAP Challenge message and initiates the AN authentication
i. Verify that the network authentication fails.
j. Repeat steps c to i by provisioning a correct User-name but an incorrect Chap-password in the AT for CHAP authentication.
18.21.5 Minimum Standard
18.22 PPP Session in Adverse Conditions - Disconnect cable between AT and PC.
18.22.1 Definition
This test verifies AT sends an LCP Termination Request to the access network when it is disconnected from the computer device. This causes the PDSN to close the PPP session.
18.22.2 Traceability:
[28] 3.2.1 PPP Session
18.22.3 Call Flow Example(s)
18-17
C.S0044-0 v1.0
1 2
3
Figure 18.22.3-1
18-18
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
Figure 18.22.3-2
18.22.4 Method of Measurement
a. Setup an AT originated HRPD connection.
b. Ensure that an IP address is assigned to the AT, and a PPP session is established between PDSN and the AT.
c. Wait until the AT connection goes to idle state.
d. Disconnect the cable between the AT and the computer device.
e. Verify Message flow between AT, access network and PDSN happens as shown in Figure 18.22.3-1.
f. Verify dial-up connection at computer device is closed and PPP session is released at PDSN.
g. Repeat steps a through c. Issue a “ping” from AT and verify there is a response from remote host.
h. Disconnect the cable between the AT and the PC computer device.
i. Verify Message flow between AT, access network and PDSN happens as shown in Figure 18.22.3-2
j. Verify dial-up connection at computer device is closed and PPP session is released at PDSN.
18.22.5 Minimum Standard
The AT shall comply with steps e, f, i and j.
18-19
C.S0044-0 v1.0
18.23 Unicast ReverseRateLimit 1
2
3 4
5
6
7
8
9
10
11 12
13 14
15 16
17 18
19
20
21
22
23
24
25
26
27
28
29
30
31
32 33 34 35
18.23.1 Definition
This test verifies the AT can successfully receive the UnicastReverseRateLimit Message with the RateLimit value set to various values.
18.23.2 Traceability
[24] 8.5.6.1.5.2 Rate Control
18.23.3 Call Flow Example(s)
None
18.23.4 Method of measurement
a. Setup a connection.
b. Setup a FTP session with a remote host and start a file transfer in the reverse link by using a binary “put” command from the AT.
c. Send a UnicastReverseRateLimit Message with the RateLimit value set to 1 (9.6 kbps) to the AT.
d. Monitor the AT transmit rate and verify that the AT does not transmit above the value set in step c.
e. Steps a to d may be repeated with the RateLimit values set to 2 (19.2kbps), 3 (38.4kbps), 4 (76.8kpbs), and 5 (153.6kbps).
18.23.5 Minimum Standard
The AT shall comply with step d for all test cases.
18.24 HRPD Location Update Protocol Tests
18.24.1 Definition
This test verifies the proper functionality of Location update feature.
18.24.2 Traceability
[24] 3.5 Location Update Protocol
18.24.3 Call Flow Example(s)
None
18.24.4 Method of measurement
a. Verify that the Ranhandoff parameter is enabled at the AN.
b. Power up the AT and place it where it can receive good HRPD signal
c. Verify that AT successfully completes the session negotiation.
d. Depending on the implementation the AN can send LocationAssignment Message to the AT. Upon receiving this LocationAssignment Message, verify that the AT sends a LocationComplete Message and stores the Location Values in the Location Assignment Message as the current Location Values.
18-20
C.S0044-0 v1.0
e. Depending on the implementation the AN can send LocationRequest Message. Upon 1 receipt of this message, verify that the AT responds with LocationNotification Message, 2 which shall contain the current Location values of the AT. 3
4 5 6 7 8 9
10
11
12
13
14
15
16 17 18
19
20
21
22
23
24
25
26
27
28
29 30 31
32 33 34 35
36 37
38 39
40 41
f. Originate a packet connection, verify that the connection can be successfully established and the data can be transferred. Let the AT connection go idle.. Move the AT to an area where there is no HRPD signal. AT will lose the HRPD signal and go to acquisition state. Move the AT to an area where there is a HRPD signal belonging to a different subnet. AT shall acquire this system. AT shall negotiate session with this HRPD system and once the session is negotiated, shall send an unsolicited LocationNotification Message. Verify that this message is sent.
18.24.5 Minimum Standard
The AT shall comply with steps c, d, e, and f.
18.25 Idle State Channel Hashing
18.25.1 Definition
This test can be performed only if the base station supports more than one HRPD channels.
If multiple channels are advertised in the sector parameter message, AT uses hash function (as specified in (SEE [24]) ) to select one of the advertised channels for idle state operation. The primary purpose of channel hashing is to equally distribute the AN load on all available channels.
18.25.2 Traceability [24]
CDMA Channel Selection
10.4 Hash Function
18.25.3 Call Flow Example(s)
None
18.25.4 Method of measurement
a. Configure the AT roaming list with the primary channel.
b. Power up the AT and verify that it does not have a session active.
c. Place AT where it can receive good HRPD signal.
d. Verify that it correctly acquires the primary channel listed in the roaming list.
e. After receiving the sector parameter messages with multiple channels, AT will try to hash to a channel listed in SectorParameter message (it could be the same channel in some cases).
f. Verify that if there are “n” channels listed in the sector parameter message and if this test is repeated “m” number of times, AT will hash to each channel approximately “m/n” times. In a subnet where SectorParameter message contains multiple channels, AT will try to hash to a new channel every time a new session is opened.
g. Repeat this test several times to verify that AT can hash to all the channels listed in the SectorParameter message.
h. Setup a HRPD data connection after channel hashing is complete to verify that AT can setup a connection on the hashed channel. Let the call connection go idle.
i. Send a data page from the AN (on the hashed channel) and verify that AT can receive a page on the hashed channel.
18-21
C.S0044-0 v1.0
1
2
3
4
5
18.25.5 Minimum Standard
The AT shall comply with steps d, f, g, h and i.
18-22
C.S0044-0 v1.0
19 ANNEX A - FIGURES 1
2
3
4
5
6
7
8
9
10
11
Figure A - 1
Tx
Rx (A)
Rx (B)
Base Stationor
Access Network
Mobile Stationor
Access Terminal
Antenna
Attenuator
Load
ChannelSimulator
Attenuator
19-1
C.S0044-0 v1.0
Figure A - 2 1
2
3
4
5
6
7
8
9
10
11
Base Station 1
Tx
Rx (A)
Rx (B)
Base Station 2
Tx
Rx (A)
Rx (B)
Mobile Station
Antenna
DAT
Code DomainAnalyzer
AWGNSource
Attenuator
Attenuator
SpectrumAnalyzer
Attenuator
DAT
Load
ChannelSimulator
Code DomainAnalyzer
Load
ChannelSimulator Attenuator
19-2
C.S0044-0 v1.0
1
2
3
4
5
Figure A - 3
Tx
Rx (A)
Rx (B)
Base Stationor
Access Network
Mobile Stationor
Access Terminal
Antenna
Attenuator #2
Load
Attenuator #1
SpectrumAnalyzer
Code DomainAnalyzer
Figure A - 4
Base Station #1Sector a
Tx
Rx (A)
Rx (B)
Base Station #1Sector b
Tx
Rx (A)
Rx (B)
Mobile Station
Antenna
Code DomainAnalyzer
AWGNSource
Attenuator
Attenuator
SpectrumAnalyzer
Attenuator
Load
Code DomainAnalyzer
Load
Attenuator
Base Station #2
Tx
Rx (A)
Rx (B)
Code DomainAnalyzer
Load
Attenuator
6 7
8
19-3
C.S0044-0 v1.0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
Figure A - 5
Tx
Rx (A)
Rx (B)
Base Station 1or
Access Network 1
Mobile Stationor
Access Terminal
Antenna
Attenuator
Load
AttenuatorAttenuator
Tx
Rx (A)
Rx (B)
Base Station 2or
Access Network 2
Load
Attenuator
19-4
C.S0044-0 v1.0
1
2
3
4
5
6
7
8
9
Figure A – 6
Rm
Tx
Rx (A)
Rx (B)
Base Station
Mobile Station
Antenna
Attenuator
Load
ChannelSimulator
Attenuator
MT2
TE2
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
Figure A – 8 Test Setup for RLP Abort in Reverse Link 1
2
3 4
5
6
7
Figure A – 9
8
19-6
C.S0044-0 v1.0
20 ANNEX B 1
2
3
4 5 6 7 8 9
10 11 12 13 14 15 16
17
18
20.1 Annex B.1 Power Ratios for Common and Traffic Channels
Annex B.1 provides the proper power ratios to perform a test when the power ratios are not specified in the test. The tables below specify power ratios for the Forward pilot channel, the Sync Channel, the Paging Channel, the Forward Common Control Channel, the Broadcast Control Channel, the Fundamental Channel, the Dedicated Control Channel, the Supplemental Code Channels and the Supplemental Channels. The traffic channel power ratios are specified to achieve at least 1% FER under AWGN channel conditions. Most channels can be configured for more than one data rate, code rate, or frame size. Not all default configurations are listed in this Annex. However, the power ratios listed in this Annex do provide the most conservative default ratios when only a subset of the values are listed for a particular channel, since the objective of these default ratios is to support signaling conformance tests and not minimum performance tests. All power ratios are valid for Band Classes 0 through 12. Whenever the power ratios are specified in the test, those power ratios should be used in lieu of power ratios provided in this Annex.
Table B.1-1 Power Ratios for Common Channels
Parameter Units Value
IorEcPilot
dB -7
IorEcSync
dB -16
IorEcPaging
dB -12 (9600 bps)
IorEcBCCH
dB -15.2 (9600bps, no TD)
IorEcFCCCH
dB -12.8 (19200 bps)
-9.5 (38400 bps)
Ioc dBm/1.23 MHz -54
19
20
Table B.1-2 Test Parameters for Forward Fundamental Channel (RC1, RC3 and RC4)
Parameter Units Value
IocorI
dB -1
20-1
C.S0044-0 v1.0
)1RC(Ior
EcFCH dB -15.6
)3RC(Ior
EcFCH dB -16.2
)4RC(Ior
EcFCH dB -15.4
Ioc dBm/1.23 MHz -54
Data Rate bps 9600
1
2
Table B.1-3 Test Parameters for Forward Fundamental Channel (RC2 and RC5)
Parameter Units Value
IocorI
dB -1
dB -12.3
)5RC(Ior
EcFCH dB -13.8
Ioc dBm/1.23 MHz -54
Data Rate bps 14400
)2RC(Ior
EcFCH
3
4
5
Units
Table B.1-4 Test Parameters for Forward Dedicated Control Channel (RC3 and RC4)
Parameter Value
IocorI
dB -1
)3RC(Ior
EcFCH dB -16.2
)4RC(Ior
EcFCH dB -15.4
Ioc dBm/1.23 MHz -54
20-2
C.S0044-0 v1.0
Data Rate bps 9600
1
2
3
Table B.1-5 Test Parameters for Forward Dedicated Control Channel (RC5)
Parameter Units Value
IocorI
dB -1
IorEcFCH
dB -13.8
Ioc dBm/1.23 MHz -54
Data Rate bps 14400
4
5
6
Table B.1-6 Test Parameters for Forward Supplemental Code Channel (RC1)
Parameter Units Value
IocorI
dB -1
IorEcSCCH
dB -16.1
IorEcFCH
dB -12.0
Ioc dBm/1.23 MHz -54
Data Rate bps 9600
7
8
9
Table B.1-7 Test Parameters for Forward Supplemental Code Channel (RC2)
Parameter Units Value
IocorI
dB -1
20-3
C.S0044-0 v1.0
IorEcSCCH
dB -13.0
IorEcFCH
dB -12.0
Ioc dBm/1.23 MHz -54
Data Rate bps 14400
1
2
3
Table B.1-8 Test Parameters for Forward Supplemental Channel (RC3 and RC4)
Parameter Units Value
IocorI
dB -1
)3RC(Ior
EcSCH dB -13.0 -9.7 -6.6 -3.2
)4RC(Ior
EcSCH dB -12.6 -9.3 -6.0 -2.8
IorEcFCH
dB -7.0
Ioc dBm/1.23 MHz -54
Data Rate bps 19200 38400 76800 153600
4
5
6
Table B.1-9 Test Parameters for Forward Supplemental Channel (RC5)
Parameter Units Value
IocorI
dB -1
IorEcSCH
dB -10.9 -7.9 -4.6 -1.4
IorEcFCH
dB -7.0
20-4
C.S0044-0 v1.0
Ioc dBm/1.23 MHz -54
Data Rate bps 28800 57600 115200 230400
20.2 Annex B.2 CDMA Equations 1
2
3 4 5
6
The following equations describe the relationship between various test parameters under different conditions. If the Paging Channel is not supported, the Forward Common Control Channel may be substituted.
20.2.1 B.2.1 Transmit Power of the Base Station
orc
IEPilot +
or
c
IE Pilot TD
+or
cI
E Sync + or
c
IE QPCH
+ or
cI
EPaging + or
c
IE FCCCH
+or
c
IE BCCH
+
7
or
c
IE CACH
+or
c
IE CPCCH
+or
c
IE FCH
+or
c
IE DCCH
+or
cI
E ControlPower + or
c
IE SCCH
+ 8
or
c
IE SCH
+or
cI
E OCNS = 1 9
10
Using the or
c
IE
values for the Pilot, Sync and Paging Channels in Table B.1-1, 11
If or
c
IE Dedicated
= -16 dB at 9600 bps data rate, then 12
or
cI
E ControlPower = -26.41 dB 13
orc
IE OCNS = -1.64 dB 14
Otherwise, if or
c
IE Dedicated
= -16 dB at 1200 bps data rate, then 15
or
cI
E ControlPower = -17.38 dB 16
or
cI
E OCNS = -1.75 dB 17
18
19
20
21
22
where “Dedicated” can represent FCH or DCCH.
20.2.2 Annex B.2.2 Received Signal Strength for Mobile Station Not in Handoff
20-5
C.S0044-0 v1.0
Pilot 0c
IE =
1II
IEPilot
or
ocor
c
+ 1
2
3
Single-Path Case
Common tb
NE =
or
oc
or
c
II
Bit_Chip_CommonI
E Common×
4
Dedicated tb
NE =
or
oc
or
c
II
Bit_Chip_DedicatedI
E Dedicated×
5
6
7 8
9
10
11
12 13
where “Common” can be applied to Sync Channel, QCPH, Paging Channel, BCCH, or FCCCH. “Dedicated” can be applied to FCH, DCCH, SCCH, or SCH.
Two-Path Case
According to Channel Simulator Configuration 1 and 2 (see 6.4.1.1), these two paths have the same average power.
Dedicated t
b
NE =
or
c
IE Dedicated
xDedicated_Chip_Bit x
21
II
1
or
oc + 14
15
16
17
18
19 20
where “Dedicated” can be applied to FCH, DCCH, SCCH, or SCH.
Three-Path Case
According to Channel Simulator Configuration 4 (see 6.4.1.1), the first two paths have the same average power and the third path has half the average power of the first one.
Dedicated tb
NE =
or
c
IE Dedicated
x Dedicated_Chip_Bit x (2 x
53
II
52
or
oc + +
54
II
51
or
oc +) 21
22
23
24
25
where “Dedicated” can be applied to FCH, DCCH, SCCH, or SCH.
20-6
C.S0044-0 v1.0
1
2 3 4
20.2.3 Annex B.2.3 Received Signal Strength for Mobile Station in Two-Way Handoff
According to Channel Simulator Configuration 2 (see 6.4.1.1), which is used in the tests of the Forward Traffic Channel in two-way handoff, there are two paths from each cell and the power received from each cell is Îor.
Pilot 0c
IE (for each pilot) =
2II
IEPilot
or
ocor
c
+ 5
Dedicated tb
NE =
or
c
IE Dedicated
x Dedicated_Chip_Bit x
23
II
23
or
oc + 6
7
8
9
where “Dedicated” can be applied to FCH, DCCH, SCCH, or SCH.
Generally, if the power received from cell 1 and cell 2 are ˆ and , respectively, then 1orI 2orI
Pilot 0c
IE
1 = 1
II
II
IEPilot
1or2or
1oroc
1or
c
++ 10
11
Pilot 0c
IE
2 = 1
II
II
IE Pilot
2or
1or
2or
oc
2or
c
++
12
13
14
15
16
17
18
19
20
21
22
23
24
20-7
C.S0044-0 v1.0
20.3 Annex B.3 Message Parameter Values 1
2
3 4
Extended Handoff Direction Message/General Handoff Direction Message/ Universal Handoff Direction Message
Field Value (With Hard Handoff)
Value (Without Hard Handoff)
T_ADD 28 (-14 dB) 28 (-14 dB)
T_DROP 32 (-16 dB) 32 (-16 dB)
T_COMP 5 (2.5 dB) 5 (2.5 dB)
T_TDROP 3 (4 sec) 3 (4 sec)
HARD_INCLUDED (EHDM)/ EXTRA_PARMS (GHDM/UHDM)
1 N/A
FRAME_OFFSET 0 N/A
PRIVATE_LCM 0 N/A
RESET_L2 1 N/A
RESET_FPC 1 N/A
SERV_NEG_TYPE 1 N/A
ENCRYPT_MODE 0 N/A
NOM_PWR_EXT 0 N/A
NOM_PWR 0 N/A
NUM_PREAMBLE 0 N/A
BAND_CLASS (user specify) N/A
CDMA_FREQ F2 N/A
PILOT_PN user specify N/A
PWR_COMB_IND 0 N/A
CODE_CHAN 1 to 63 (user specify) N/A
5
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
2
3
System Parameters Message
Field Value (Physical Meaning)
SRCH_WIN_A 8 (60 chips)
SRCH_WIN_N 8 (60 chips)
SRCH_WIN_R 8 (60 chips)
NGHBR_MAX_AGE 0 (minimum amount)
PWR_THRESH_ENABLE 0 (threshold reporting off)
PWR_PERIOD_ENABLE 0 (periodic reporting off)
T_ADD 28 (-14 dB Ec/Io)
T_DROP 32 (-16 dB Ec/Io)
T_COMP 5 (2.5 dB)
T_TDROP 3 (4 sec)
QPCH_SUPPORTED 0 (QPCH disabled)
4
5
Extended System Parameters Message
Field Value (Decimal)
SOFT_SLOPE 0 (0)
RLGAIN_TRAFFIC_PILOT 0 (0 dB)
6
7
20-9
C.S0044-0 v1.0
1 Access Parameters Message
Field Value (Decimal)
NOM_PWR 0 (0 dB)
INIT_PWR 0 (0 dB)
PWR_STEP 1 (1 dB)
NUM_STEP 4 (5 probes/sequence)
NOM_PWR_EXT 0 (0 dB)
2
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
4
20-10
C.S0044-0 v1.0
21 ANNEX C - PROTOCOL CAPABILITY RESPONSE MESSAGE FEATURE IDENTIFIERS
1 2 3
Features FEATURE_ID FEATURE_P_REV FEATURE_P_REV Description
NAM Download (DATA_P_REV)
‘00000000’ ‘00000010’ NAM Download as specified in this document
‘00000010’ A key provisioning as specified in this document
‘00000011’ A key and 3G Root Key provisioning as specified in
this document
Key Exchange (A_KEY_P_REV)
‘00000001’
‘00000100’ 3G Root Key provisioning as specified in this
document
‘00000001’ System Selection for Preferred Roaming using Preferred Roaming List
‘00000010’ Reserved
System Selection for Preferred Roaming (SSPR_P_REV)
‘00000010’
‘00000011’ System Selection for Preferred Roaming using
Extended Preferred Roaming List associated
with SSPR_P_REV of ‘00000011’
Service Programming Lock (SPL_P_REV)
‘00000011’ ‘00000001’ Service Programming Lock as specified in this
document
Over-The-Air Parameter Administration (OTAPA_P_REV)
‘00000100’ ‘00000001’ Over-The-Air Parameter Administration as specified
in this document
Preferred User Zone List (PUZL_P_REV)
‘00000101’ ‘00000001’ Preferred User Zone List as specified in this document
3G Packet Data (3GPD) '00000110' '00000010' 3G Packet Data as specified in this document
Secure MODE SECURE_MODE_P_REV)
‘00000111’ ‘00000001’ Secure Mode as specified in this document
21-1
C.S0044-0 v1.0
Reserved for future standardization
‘000001000’ through
‘10111111’
Available for manufacturer-specific features
‘11000000’ through
‘11111110’
Reserved ‘11111111’
1
21-2
C.S0044-0 v1.0
22 ANNEX D DATA SERVICES TESTS 1
2
3
4
5
6
7
8
9
10
11 12 13
14
15
22.1 Data Services Annex A: References
RFC 792 Internet Control Message Protocol
RFC 854 Telnet Protocol specification
RFC 959 File Transfer Protocol
RFC 1144 Compressing TCP/IP headers for low-speed serial links
RFC 1332 The PPP Internet Protocol Control Protocol (IPCP)
RFC 1661 The Point-to-Point Protocol (PPP)
RFC 1662 PPP in HDLC-like Framing
22.2 Data Services Annex B: Description of Compressible Test Data Files
COMPFILE.RAW is a 40000-byte long file, which is assembled of five sections. The first 8000 bytes are compressible, the next 8000 are not compressible, the next 8000 are compressible, and so on.
Transfer Time is in format X:YY where X is number of minutes, and Y is number of seconds.
Data File Rate Set 1 Max Transfer Time
Rate Set 2 Max Transfer Time
COMPFILE.RAW 1:20 0:50
Note: The maximum transfer time of a file is 8 x M / (R x 0.5) seconds, where M is the number of bytes in the file, and R is the payload rate for a given rate set.
16 17
18
19 20
21
22 23
24
For Rate Set 1, R is 8000 bps. For Rate Set 2, R is 13000 bps.
To transfer a 40,000 byte file over Rate Set 1, the maximum acceptable transfer time is (8 x 40,000 bytes) / (8000 x 0.5) bps = 80 seconds = 1 minutes and 20 seconds.
22.3 Data Services Annex C: Standard ITU Fax Pages
Use the following Image Files from the Standard Digitized Image Set on CD-ROM (CD-03 ed.) of the ITU-T Recommendation T.24 Encl. (11/94).
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 3
4 5 6
7
8
9 10 11
12
13
14
15
16
17 18 19 20 21
22
23
24
Sending a 3-page fax consisting of the preceding three ITU T.24 images, between two landline fax modems may be performed to establish the "theoretical maximum throughput" benchmark.
In order to allow for different modem types etc., the same test may be run using modems from different manufacturers, between two modems, and between a modem and a land line fax machine, and the results averaged. Typical results follow:
Average Landline Fax Transfer Time @9600 bps = 6 min 29 sec = 389 sec
Average Landline Fax Transfer Time @14400 bps = 4 min 31 sec = 271 sec
In the case of Async Data, the acceptable throughput has been set at 0.5 times the maximum throughput. Assuming the acceptable throughput for Fax transfers is 0.5 times the landline throughput:
Rate Set 1 Maximum Fax Transfer Time = 1 / 0.5 x 389 sec= 778 sec= 12 min 58 sec
Rate Set 2 Maximum Fax Transfer Time = 1 / 0.5 x 271 sec= 542 sec= 9 min 2 sec
22.4 Data Services Annex D: Test Files
RAND200.BIN is a 200,000 byte long file. The first 4000 bytes of RAND200.BIN contain patterned data (padded with zeros). The remaining 196,000 bytes of this file contain random data. This file is transferred to ensure that neither the IWF nor the MT2 have trouble transferring different patterns of data. This file contains all possible byte values from 0x00 to 0xFF. As well, it contains double escape sequences and software flow control characters.
RAND200.ASC is a 200,000 byte long file.
Transfer Time is in format X:YY where X is number of minutes, and Y is number of seconds.
Data File Rate Set 1 Max Transfer Time
Rate Set 2 Max Transfer Time
RAND200.BIN 5:20 3:17
RAND200.ASC 5:20 3:17
Note: The maximum transfer time of a file is 8 x M / (R x 0.625) seconds, where M is the number of bytes in the file, and R is the payload rate for a given rate set.
25 26
22-2
C.S0044-0 v1.0
1 2
3 4
5 6 7 8
For Rate Set 1, R is 8000 bps. For Rate Set 2, R is 13000 bps. The value 0.625 represents the minimum acceptable throughput.
To transfer a 200,000 byte file over Rate Set 1, the maximum acceptable transfer time is (8 x 200,000 bytes) / (8000 x 0.625) bps = 320 seconds = 5 minutes and 20 seconds.
Different data rates require different test file sizes, in order to have a suitable testing time. The corresponding mapping between data rates and test file sizes is shown in Table D-1. Files larger than 200000 bytes can be constructed by concatenating more than one RAND200.BIN file.Table D-1 Test files to be used corresponding to tested rates.
Data Rate Granted (bps)
F-RC3,4 / R-RC3 F-RC5 / R-RC4
Test file size (bytes)
9600 14400 200000
19200 28800 400000
38400 57600 600000
76800 115200 1200000
153600 230400 2000000
9
22-3
C.S0044-0 v1.0
23 ANNEX E: TTY/TDD TEST EXAMPLES 1
2 3
4 5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23 24
25
26
27
28
29
30
31
32
33
34
35
36
37
Note: The following ASCII characters are not supported by the Baudot TTY standard and should not be used to verify conformance: @ # % ^ & * < >Example character text:
THE QUICK BROWN FOX JUMPS OVER A LAZY DOG. 1234567890 ABCDEFGHIJKLMNOPQRSTUVWXYZ -$’,!:(“)=?+./;TTY_text.txt test file:
TTY_text.txt:
BEGINNING OF TEST FILE
111111111122222222223333333333444444444455555555556666666666777777777788
THE QUICK BROWN FOX JUMPS OVER A LAZY DOG.
1234567890 ABCDEFGHIJKLMNOPQRSTUVWXYZ -$',!:(")=?+./;
=N((MI-IDDM'JEC $3F$,F1 8T:VY"RZ87OY"165S(M VP294!T+FE5J(UOIO4JK9SeeA!T7
53+3.AVO4;;C/V$L$DD.89YE U .ZK6-HLZK-L ,"N19,3=1K R,TV;L;F"59 MR(80/=A!F
$,?," )N"RRU/IP$HZ"YSCU(R4;)WRL5BW24ANTAXW$IFP8LSN$SZ(FA3X1,PQ3E-TDXYP89
E?!5I1$FBF6'2/E0W"P?;L 57!(2RD3/OT?D?C=CD7T5'J9 "?X5VZ2 2II U=2CV)7"/4G2
;01 H6.W=8'K6(-HN?-PF?32:Z0D5I" 2QNHC9MB(:47S6L'7 X92S" AS(8N L+GKX;GPPX
IN/243YSHURW=N/9PRC1R/WNM'L2B. D,DN-K,FGW":Z'8T IY505I +,LDQTAF4 6 PF F
.S'QHP/=/$(VWBKLNY'4TY: LO Y5T::-R;1Q=DO2 )YU,57 " QMM;PL'NXJ20FG4)F FS5
M,!8DQ41,D?G"W98G=12HL))"+,IKL1U"WI,$!9)=EZ.Z?HGWHZRP:'4C))"46QS'/H:LLQW
HG" !,=$RE(O"QCJXK=F3WW'JK-9-9B'-?VNF(NY REH2KTF G?D!PX6'I.?U,O6E$.U5I0'
'-?S$,ZU!K!"M ES7;J5CK!J43MB$-A18U 8;"IQN:427)9D8F,3NQQQ8A3I3 V9!NKTP:KE
,AT5PPVD4.GT5Y/OW75M"A E58,2C44:33K,$-D7!9WNEJ04V6RWC G2G5ESNCBYHS=Q45F
.QOF$))SK9=7J5RE1P8-N?-N.DIY3))1EH(0D7 ?TJG:D6HWDH =:W!?248=T6S+08'$8(4K
UXJN0/AYGCNUQO'LHKS0W- E,O($HR:2DC.EE7(CH-YF5G/Q(EPR3D3)CCM6GU.9F2OM7YFL
104FLCYLO "LP55T07.:W6/IU.QU?/W=TFUTPR:L1+L!J2/E)QG1UVF881N=,8V3+QJMZ(FR
E":V-+$-BV90RXK W6SA"Y36D2-!3R3( 7E;'?HC$!")NJ)K?U0 6=:9J,!,(JQ(?Y-Q2XZ)
'6K22L2FKKL0E=J ?ZP9W LE5WR RV TN420X=/!7(G0IQM==+$X8.8K+J$S32$X!PZV3Y3I
QTQQA7T4IY= 9NK6BYKT:.UQ$P84'R7'"VAU9 ( P?7HM1?Y5T)E:9WF!FF1(2GH,).ZB/+H
$,/6ELJR0Z1AZG$U A4(7"(H!3Y+JF8C?6M'N'WQ=;FY- ?2167.A0H89W 'DN/'U20G:3K+
2C5C?.'NRT+:C7PX7C5NWCGHTUH)'75PM?:+I4A, Q(ZNC,)XL4+NR72LSI25L9Z3!$5X0T/
8 FQ=D- S!3B'?0!MNAABDUY2TKMT"40S$RPY( U4($AQ: FF?7$UUPS=49SKC(UVZ9SW3IV
9?Z(NAQ$.=?R/6 GZJ9'(3'NNIH6D7:= +F2UYTW5D)I9(UDQ8?E=C(8H$I1Q3'KU$!X)!W
+U;6B4;+9E1W-$'11-ZP?I7IU5UJYP$/"$NU:'ALW9$D,C6J0I 561F41SD0GC"N5MSD' FP
9'1832GS=LWWN GDD--65D"!C;0EPSK)8H+=EOX7K3H -L12TEZ83D5W$=R!9$Q9,.0,93WC
C()(B??EGU$/RIH/90H'"!29HIILF'$6S('ZCA)RE9T90F3VHQ 1I43Q6HZ8"CJ+=AJ5-BY$
WA2(W?:TI(FPCG9JTD5TFF/0!'KJ",I,"4$;55 G.N3HRGB0A"83.CN"84)JG3ABKQ77HU2
-OY?MJ7!9R=T518Y+RR4TGY/: I9MMT9KF.2C,MEVK R,D='WSALLC/7 U9WL-WPLKN:+ARW
23-1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
):D!(:'H:I?H'1N(6-80V7;XB4"KJD'T)EI$ :PIS203(?KUG(Z7/ J9OZ9Z--C1W:C=TY4
: "+3AF"JWB+,9UVA,7F)R6A"Y"I!,IC596G!O5! JAHP?0,X?K-LB'KHV E.$P0:K5'QVGB
CNA)'/MSJOSWMU5U 3=I 27Z-E0YTOS5031+P99LIT0=86K-2V21JS61(G/!AE=46!OJDP0"
+4V6CLKW' KL-S,Y?KHA8+6F+Y0$!U=;=8VXH26!8K."'K7!J'(N="ZKCZH:N'C:9BG7E0IH
C+L8VSK24 DJD:TNI6; N$Q1C5C2 IP(!E=TJMF?3D9E1/M88,V7C/FSVEYTY+MZ Y=R88)W
ZZKKJJ 39ZIYEZH") +?=YYGKF1D1X$$IWR;+6MYSO;"!R) 9ZRR="KDYF1A4AU?4- "GRAW
6;A-O.N.VW? .2??=MHY0;X1=H9WEHWD8;:C6 :JO/7?!.EZ4JL/ !FNXL;AJAWB; CWUWLF
O1N4 U;V(9M8"O$S6)FER=14I4I,HIEM5'916:FN.Y?5"=LC0EQN7I,?D;3(=2'/=L8H(!I9
:2.ST 1.2A:,DE;745VU7UA-$Z?F8PGE'INKD7 G?PUQ79N610W:Y;E63X7)4-.V?T0))W7H
YBKRT/DL-S5WZ'OH;HK21'/Y7 ,8Z0 1UMD64-S;7WIZT="'4/2''XE7CQ.:2LUK)C"=0XEN
" :HZV(M'/4ZQ16$6WO1A-'D5)VMA3E+? $D0WF271)68 WE?GJ OSA8T=!R=7 -UQT7JU+G
FI-?.9DD44'IH!=$$WKE)2:,!ID:DJ !+.(AW=O/V!RPR 85?D04'6L"UZE43O8O0T6 'ERP
O:58B.7HYM?QTCO"3U; 5+.0TWJA3ID"T!,1)?H2S1VFBW/E 6 LCN,.GH:KI:99$1RW(H0P
1)+H83 G8! H0 V).6'QK7VFIE-/S)MA(+'D7" TTI.,-'NO46Q32.NY19,KDFD!TLB-FIMA
6R7$L Y$H=:TN8$4VD4L,8?QL "=PF8UJQN=E8XM;AAOMXLYG9-CWEH (YOYS,KVK0WU=Z'R
4/0FFBT 2FG!!!J 093RMNA=EX.:6:1AK08KY0(DJN:JV6:L=4:J5N:9)"WW4Z,4:DCPSO$W
V!G8$9 INIB!.U/;? J00VEY0+)G"0S5LK6!A3EMUPF,JQ"LY',34E?TK$2G=M4 J/9=!AKT
"S"=23A6TT4VTK:1)CP.8NJ7.UHVDN5VW)EI/1CA "NCJ FIQ"$KXN!G73DO),!0JY"$OPH5
CW(S6=I7JNNOA DZX" 2-3(0;TP5A1PEW(=J:PZKGQ6CK.WFJYZ1J OY69P?5I SL2T0N CZ
IKN,8X:+FG-R=CEY7(8 $3;ER Q(D0. O3/Y8,Y,1M;X0W85!!.4"!OT FC+X7WGV$:K/L:
"I;(ZA'.Y$)E9"AZ),XJM)WTZ(I'4;N6H'NTW(AEEI+, C80B ,F(D8KH; H;Q0-Z1 2H6M=
LI('F P=XD?-NDZOO!9J !?0S=J?1L4+F+HBUX6S:9DOYC 38O(YZZ8LAP+10IL?" :R YJ
AWLNZ/+ "!BSK-4X1W:2UM!(9U?F"97V.BT3YCNJDIG6I4 6)!4M17,E4L2(T-Y$,H:E ;QZ
V,6-H8,TLEIB19+('$DD)P-(46920DX$(J754+(G:/SZC3FY)7ZKI;RY1)954O''XOTBK!5F
'P ?J1906IHVS'0(.8(I',S-Q9(A )0?J-E4LF0X!H9 23?KR$DFYLHLB5(?)/U)T3$I.)I;
KLY6?')V65Z4ZDVOYF4X:G. 3))46!OEG(KZ8BP24L'W"(-Y)JJHAXG=DR!-)UZ8MKDQ=!"6
WK?R/;IO42?LZ2U9 H0'E.K88,0S,KTA?YRKMJH-C$WJ?(0=4 /"A(; "H."H"OPSR2=9ZRV
3XRG)HLEQ6IDX TJ7$23EF4M=O QQ?- /N6J7:L13HPJ: CR6A--/F9J,4=3LQVC4W-H-2CL
; (5?VU:L,+6ELDO4TLKBU JTC=$9$C3CN$6 P0'4E35-: .LO $'5.HD3N41$;72)+KOU.3
7(A Y, TY .-VLM8Y3'?I7FRR-H+I5818G4"8KC.:29HQ"Y8FR'5!"GTE)NAMEK(H4RPJE3E
BU: B$MM:NL36VE)'9AA?I$+$GDZUD=D3/Y6M 1P) ?5XFK$(YO!8'(9=E'D.2R ?:F'"Y58
!C8,7TR5E-K-J9UK" X -"/PF9NL0DL,9C94OEWT 8$C-A(05)0X=.5(CHDF
THE QUICK BROWN FOX JUMPS OVER A LAZY DOG.
1234567890 ABCDEFGHIJKLMNOPQRSTUVWXYZ -$',!:(")=?+./;
111111111122222222223333333333444444444455555555556666666666777777777788
END OF TEST FILE
23-2
C.S0044-0 v1.0
23-3
1
